Anybody Having Trouble Today?

[JimDog]

Russell,

I'm using VOIPo on U-verse and my configuration is a little different than yours. Instead of forwarding ports I have the Residential Gateway configured to give my PAP2T its external IP address and to forward all traffic not destined for another system on my network to it (DMZplus). You can configure DMZplus in the RG in Settings -> Firewall -> Applications, Pinholes and DMZ. Select your adapter from the list of devices, click the radio button near the bottom for Allow all applications and then click Save. To assign it the external IP address go to Settings -> LAN -> IP Address Allocation. Find your adapter in the list, change Address Assignment to Public and change WAN IP Mapping to Router WAN IP address. I haven't had any issues with this setup. I'm still able to forward specific traffic (Remote Desktop, Peer-to-peer, etc.) to other systems using firewall rules; just anything that doesn't match a firewall rule or isn't a reply to an outbound request gets sent to the VOIPo adapter.

[Russell]

Russell,

I'm using VOIPo on U-verse and my configuration is a little different than yours. Instead of forwarding ports I have the Residential Gateway configured to give my PAP2T its external IP address and to forward all traffic not destined for another system on my network to it (DMZplus). You can configure DMZplus in the RG in Settings -> Firewall -> Applications, Pinholes and DMZ. Select your adapter from the list of devices, click the radio button near the bottom for Allow all applications and then click Save. To assign it the external IP address go to Settings -> LAN -> IP Address Allocation. Find your adapter in the list, change Address Assignment to Public and change WAN IP Mapping to Router WAN IP address. I haven't had any issues with this setup. I'm still able to forward specific traffic (Remote Desktop, Peer-to-peer, etc.) to other systems using firewall rules; just anything that doesn't match a firewall rule or isn't a reply to an outbound request gets sent to the VOIPo adapter.

Thanks, JimDog. Your instructions are excellent and if I've got to move to the DMZ I'll do it and the instructions will most certainly help. However, on principle I dislike putting my ATA in the DMZ, but that's a different thread :-).

I had another call this evening where I couldn't hear the caller. Since then I tech support remotely accessed my RT31P2 and say, "We've applied a few adjustments to the account to aid in stabilizing the service. No further action is needed at this time. " So, I'm hoping all is well.

[stevech]

, "We've applied a few adjustments to the account to aid in stabilizing the service. No further action is needed at this time. " So, I'm hoping all is well.

one always wonders why such adjustments, if not mere guesses, were not previously applied!

[Russell]

one always wonders why such adjustments, if not mere guesses, were not previously applied!

Having suffered through the glitches, I would have loved to have known why I (with a very vanilla setup) merited those changes. But, I'm going to assume they work, assume they don't tell the average customer what has been done, and not take any of their time pursuing the subject in the ticket.

[Russell]

So far the "adjustments" appear to be working. Not many calls, but no issues with the calls that have been made or received.

[VOIPoTim]

So far the "adjustments" appear to be working. Not many calls, but no issues with the calls that have been made or received.

Glad to see. See, sometimes opening a ticket really does work.

[Russell]

Glad to see. See, sometimes opening a ticket really does work.

Tim,

Now that you've had the satisfaction of saying, "I told you so" :-), would you be kind enough to let me (and other curious readers) know what kind of "adjustments" were made on my account? As previously mentioned my setup could not be more vanilla: RT31P2 connected directly to the UVerse router (which Brandon has successfully tested with numerous devices). 12Mbps/1.5Mbps service UVerse service.