"Voiceline service" of Net2Phone and Blocked UDP p

[tc!]

Hello out there,

New to Voxilla from South America, hoping for some advice.

Net2phone's PC2phone service has been my lifeline since arriving in the Southern Hemisphere in the fall of 04. I have been very pleased with the pc2phone service but decied to try net2phone's "Voiceline service," a full VOiP deal.

To use this service, I had to buy an InnoMedia MTA 3328-2 TA. Since it arrived last month, though, I haven't been able to get it to work. I get a dialtone and can call to the US and hear the other party perfectly, they just CAN'T hear me (or I break up consistently).

One of my techie friends tells me that the problem appears to be blocked UDP ports or something like that. Not sure why pc2phone worked superbly but the "Voiceline" service doesn't?

My tech pal also lent me a Cisco ATA 186 and set up a test account on a VoIP startup company he is putting together and that works perfectly! Why would the Cisco work but not the Innomedia, if the prob. is really blocked UDP ports? (whatever that is!)

I apologize for the rookie question/ignorance but hope somebody might be able to help.

I am using a 128 KBPS Adsl connection. (This connection occasionally runs slower than advertised, but I average about 90+ KBS.) Both ta's were/are plugged into a Linksys BEFsr41 4 port router. Know it doesn't matter but I'm running on an HP with 2.0 GHZ, 512 mbs Ram and 120 Gig HD. Appreciate any help.

thanks,
tc!

[PhoneBoy]

Blocked UDP ports is a possiblityi if you never got *any* audio in one direction. However, the fact that they can *sometimes* hear you (and the audio quality is poor) suggests something else, perhaps the SIP gateways used by the Innomedia device or the Innomedia device itself.

[Anonymous]

Phoneboy,

Thanks for the note. I kind of doubted the blocked UDP port explanation, too. If it's the SIP gateway, what do you suggest? My tech friend with the VoIP biz tested the Innomedia device and thought it was functioning....Any thoughts on how to proceed?

many, many thanks
TC

[mena]

Hi,
Try logging in the Linksys and enble port forwarding for the following ports to your MTA's Ip address:


Signaling needs: UDP 5060
RTP (Voice) needs: UDP From 9000-9004

[tc!]

Mena,

I'm sorry to be an idiot...So all I do is go into the Linksys settings then enable portforwarding? is that it? And the ports I want to forward to are:

UDP 5060
UDP From 9000-9004


Sorry, I'm a moron.
tc

Hi,
Try logging in the Linksys and enble port forwarding for the following ports to your MTA's Ip address:


Signaling needs: UDP 5060
RTP (Voice) needs: UDP From 9000-9004

[mena]

Yes, port forward these ports to the IP used by the MTA.
Keep in mind that the MTA will change IP if you reboot it, unless you restrict the DHCP.

[rizsher]

Check in the MTA's settings for the RTP Ports, I've used the Cisco ATA and SPA3000 with IConnecthere and a British VoIP Proiver, both were in the range 16300-16480 or so. Also, to ensure proper operation, you should initially try to connect the MTA directly to the Modem (remove the router) and see how things go. If that works well, then put the router back in, and put the MTAs IP in the DMZ. If that works, THEN, remove it from the DMZ and start playing with Port Forwarding.

Look at the MTAs Manual, there must be a way to assign a static IP to it, othwerwise, everytime the router reboots, there is a chance the IP assigned by the router to the various devices connected to it may change.

One last thing, with Linksys, I've notcied on some forums that just putting the device in the DMZ is not enough, you still have to manually forward the ports. I've forwarded ports 5060-5065 and 16200-16500 just to be sure.

If on connecting the modem direcltly to the MTA device makes it work well, then you know you don't have any ISP blocking, then it'll just be a matter of configuring the router, which I'm sure you'll find plenty of help on here.