I just got the Uverse service with a NVG589. I already had a VOIP service using a Grandstream Handy Tone 286. The Uverse gateway will not let the VOIP device communicate with the provider. I have tried numerous configurations without success.
I tried identifying the VOIP device as an IP passthrough with no success. I have added a seondary router per several posts in this forum. I have the secondary router identified as an IP passthrough and the VOIP adapter conneted to it and identified as DMZ without success. The device works fine at my office which has the exact same secondary router connected to a Cable internet service so it has to be the Uverse Gateway.
I also got the ports used from the VOIP provider and using the Game/NAT options forwarded all of the sets of ports to the device as well as the router. Still no success.
I apologize about the inconveniences you are having with your Grandstream Handy Tone 286. To make sure the router is recognizing the device, what IP address is the NVG589 assigning the VOIP device? You can check on the Grandstream or you can login to the NVG589 at http://192.168.1.254 and check the device list. If it is not seeing the device, it may be worth rebooting the equipment or trying a different Ethernet cable or port on the NVG589.
Hope this helps.
AT&T Customer Care
Need help with an account specific question? Post a new question here on the forums by clicking the "Ask a Question" button. For additional support, please visit us at our AT&T services hub. Follow us on: Twitter @ATTHelp
*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.
FWIW, I just got the NVG589 a couple of days ago as I am going to be getting a NAS and need giagbit.
I use Ooma, a VOIP device and a problem surfaced when I was on the phone, my Interent dropped. Did a restart in the device settings, unplugged it, rescanned for devices. None of that worked. Finally I treated the NVG589 as a router and pressed and held the red reset button for a few seconds. It immediately found my Ooma device and the problem disappeared.
Just wanted to post in this thread in case it can help somone else using a VOIP device.