Uniden UIP1869V behind a NAT/Firewall router

Posts: 15 · Vonage Forum Associate Joined: Jun 04, 2006 Posts: 15

orient_guy wrote:

to put the Vonage device in DMZ, you need to assign first a static ip to it (including subnet mask and default gateway).

Yes and the device has been configured with a static private IP address. Regardless if the IP address is assigned to a DMZ or not, the UIP1869V device will have no problem to register to Vonage servers and got a dialtone. However, when placing a call to any number always yields with no audio streams. Calling to the number assigned to this UIP1869V goes directly to the voicemail.

Quote:

check first the connections: from ethernet of modem to internet of router. from ethernet of router to WAN port of Vonage device.

All computers/devices (i.e. Linksys PAP2T-NA) as well as this UIP1869V attached to the main NAT/Firewall router are able to access to the Internet without any problem. BTW, just to make sure you won't ask, she has a Comcast cable modem connection and it has been steadily rocking for the past two years without any major problems. Her PAP2T-NA units work just fine using STUN options with other VoSPs that support BYOD.

Quote:

before doing the DMZ, try first resetting your router. press and hold the the reset button for 10 seconds while power is on. reset also the Vonage device by 30 seconds.

These had been done even before I had posted asking for help here and the problem still persists, i.e. no audio streams. On top of this, we had done more as follows:

Temporarily disabled her WiFi and other features after a factory reset on the main router.
Re-flashed the router back with the original Linksys released firmware and perform a 40 seconds factory reset.
Purchased a new Linksys WRT350N router to replace the current one.
Went back to the store to replace the UIP1869V device (at least twice, i.e. tested three new different units).
Borrowed a friend's fully-working UIP1869V device and reconfigured it with a static/dynamic private IP address.

However, we still have no audio streams on the UIP1869V. if we were to replace the main NAT/Firewall router with this UIP1869V device, it sure works without a problem; however, this is NOT an option to her (as I already mentioned here several times). If Uniden/Vonage were to add a STUN option to this device through a new firmware, I am sure this problem of having no audio streams would have been a history.

FYI, a Linksys/Vonage locked WRTP54G that runs on a firmware v1.00.6x without a STUN option support will also run into this no audio streams problem when configured as a 2nd NAT/Firewall router. However, once the Linksys released WRTP54G-NA firmware has been modded and uploaded to this Linksys/Vonage locked WRTP54G device, it won't have any audio streams problem when configured as a 2nd NAT/Firewall router mainly because the device can be configured with a STUN option supported by the WRTP54G-NA firmware. I know this because I have done so and seen many Linksys/Vonage locked WRTP54G devices runing flawlessly behind a non-symmetrical NAT/Firewall router with a Linksys released WRTP54G-NA firmware. If Uniden has released a firmware for this UIP1869 device that supports STUN options, I am sure it will solve this problem easily. I have asked Uniden and the response was negative because it doesn't produce any UIP1869 device other than the UIP1869V device for Vonage. The firmware source code without the voice-module sources released by Uniden contains a firmware for this UIP1869V device and it still doesn't support STUN options. So, this is also not a solution.

We haven't tried the suggestion posted by Ezco yet mainly because this port range will probably cause more problem to the other PAP2T-NA devices that also use some of the ports within the range. We will reserve this as the last resort.

Besides all the above, I believe the only solution for my friend is to return the UIP1869V device back to the merchant. At least, this is what I see from the responses I have gotten so far to this post here. Sad

Posts: 10 · Vonage Forum Associate Joined: Feb 14, 2007 Posts: 10

I'm running the same device behind a Juniper/Netscreen 5GT Fw. There was no problem with the setup whatsoever, since all connection are opened from the inside.
I traced traffic a bit and after a couple of DNS, NTP (for the time) and a TFTP connection (for updates?), the device uses a persistent port 10000 inside to port 10000 outside to place and receive calls it seems. Since my UDP timeout is 1 minute, the device has to keep the connection open somehow, maybe by sending a packet every 30 seconds or so. After receiving a call via port 10000, there will be another port used for the actual data stream, opened from inside somewhere in the 10k port range to the announced port at the Vonage server, which is also in the 10k port range.
Hope this helps....

Posts: 15 · Vonage Forum Associate Joined: Jun 04, 2006 Posts: 15

DucatiGT wrote:

..., the device uses a persistent port 10000 inside to port 10000 outside to place and receive calls it seems. Since my UDP timeout is 1 minute, the device has to keep the connection open somehow, maybe by sending a packet every 30 seconds or so. After receiving a call via port 10000, there will be another port used for the actual data stream, opened from inside somewhere in the 10k port range to the announced port at the Vonage server, which is also in the 10k port range.

Thank you for the above information. I sure will tell my friend to give this a try to see if that will do the trick.

Posts: 533 · Posted: Fri Jun 15, 2007 12:54 pm Post subject:

Mazilo wrote:

DucatiGT wrote:

..., the device uses a persistent port 10000 inside to port 10000 outside to place and receive calls it seems. Since my UDP timeout is 1 minute, the device has to keep the connection open somehow, maybe by sending a packet every 30 seconds or so. After receiving a call via port 10000, there will be another port used for the actual data stream, opened from inside somewhere in the 10k port range to the announced port at the Vonage server, which is also in the 10k port range.

Thank you for the above information. I sure will tell my friend to give this a try to see if that will do the trick.

Give what a try? Everything DucatiGT describes is what the ATA does, not external equipment.

Posts: 10 · Vonage Forum Associate Joined: Feb 14, 2007 Posts: 10

Judging from the description of the problem, it looks like the firewall doesn't do stateful inspection, which is necessary for using UDP here, or is dropping the connection too soon. Is it possible to look at/change Fw params to comply these needs ?
Needless to say i'm NATing to the outside...

Posts: 15 · Vonage Forum Associate Joined: Jun 04, 2006 Posts: 15

I was able to unlock this UIP1869V device as well as saved a copy of the encryption key and where to download its provision XML file from a Vonage server. Then, I downloaded/decrypted the provision XML file and found what TCP/UDP ports used for this device. I opened up these TCP/UDP ports, i.e. 10000, 10050 - 10150, for the IP address statically assigned to the UIP1896V and it still has the same problem, i.e. no audio streams. Just out of curiosity, we tested the UIP1869V with a public IP address and worked without any problem. Since this is not an option to my friend, we trashed away this option.

My friend will have about a week before the last day to return the product to get her money back. I believe she will return this device ASAP. So, I would like to say thank you to all of you who had helped here even though we didn't manage to solve the problem.

Posts: 15 · Vonage Forum Associate Joined: Jun 04, 2006 Posts: 15

Just an update.

I managed to get a unit of this UIP1869V for free. I have unlocked the unit, configured it with two SIPGate accounts using its SIP and Registrar Address servers. The device is connected behind my NAT/Firewall router and function properly without any NAT options. Thanks to the Registrar Address server that makes NAT problems an issue in the past.

So, if anyone out here is trying to configure an ATA device that doesn't support for an Outbound Proxy server nor STUN options, except the Registrar Address server, then it should work if the VoSP also supports and provides for a Registrar Address server to use.