NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
VoIP phone not working with R8000 Router
Hello! I purchased a R8000 router for my home network a few weeks ago. I have been using a $60 Belkin router for last couple years and thought an upgrade was in order especially since this year my ...
I see there has been a couple new postings on this topic. Recently I finally got my R8000 to work with Polycom VoIP phone! (after nearly 4 months)
I hadn’t tried anything in several weeks, mostly because I had nothing new to try. But I had an opportunity to look at things again. Two things that immediately noticed when I reconnected the router into my home network and VoIP phone. First there was a firmware update for the R8000 router, and coincidently an update was recently loaded into the phone. It appeared things were acting differently now. One sysmtom was the display on the phone shows the date. When you forward the phone to another phone number, this display cycles back and forth between the date and the phone number that the phone was forwarded to. When things were not working before, the display would not cycle, it would only show the forwarded number and not the date. Anyway, now the phone display was cycling as it should!
I took screen shots of my Netgear setup. But in short, I fixed the phones MAC to an IP address. I set up a DMZ Server for that port. I enabled dynamic QoS, giving the phone the “Highest” Device Priority. I have port 6670 set for port forwarding, though this is left over when I was trying things earlier, so not sure it’s doing anything, but the phone works now, so I left it alone!
I don’t know if this will help anyone, but this is what I know. Just happy everything is working nicely now and has been for the last couple weeks.
-Carl Lester
Below is 5 screen shots of my R8000 set up.
Let me make a follow-up on your open case.
Thank you. By the way, I had spoken to Netgear tech support and they suggested port forwarding, which I have since tried and it did not work. Just FYI: the support case number is/was #27600753, but I believe it may of timed out and is closed now.
I have 7 Yealinks behind the Nighthawk X6. Registration interval is every 60 seconds. SIP ALG ,QOS and upnp are turned off. No port forwarding or triggering. I find that at any one time, the UDP SRC port received at the SIP proxy server for one or more of the devices is 5060. The others are a unique (non 5060) port as expected. The problem moves between devices every few minutes. As a result, responses from the server for those with SRC Port 5060 do not find their way back to the correct device. If I watch registrations of a device currently on a unique port, one registration cycle is missing before I see the SRC port change to 5060. I see 4 byte UDP keep-alives at the SIP proxy server every 30 seconds.
As a test, I replaced the router with a model from a different vendor and my issue was resolved for the same 7 phones.
Can anyone explain why this is happening and what the solution is?
jrmont wrote:No port forwarding or triggering. I find that at any one time, the UDP SRC port received at the SIP proxy server for one or more of the devices is 5060. The others are a unique (non 5060) port as expected. The problem moves between devices every few minutes. As a result, responses from the server for those with SRC Port 5060 do not find their way back to the correct device.
Depedns widely on the SIP infrastructure you are talking to. Any normal router will map the LAN subnet 5060/UDP source ot a random UDP port on the WAN interface. The content of the SIP packet is not changed, so it still contains 5060/UDP.
Or you try to explain us that multiple VoIP phones LAN IP source 5060/UDP will be translated 1:1 for multiple clients on the LAN? Then soemthing would be baldy wrong with the NAT in place on the router.
WIth a NAT"-dumb" SIP environment, enabling the SIP ALG _should_ allow to rewrite the SIP packets accordig to the effectively used ports.
My concern is with the phones who's source port is NOT mapped to some random value. 1 to 3 of the phones at any time use src port 5060 as seen at the SBC. This moves between phones every few minutes. SIP ALG is disabled as it will likely cause other issues if I enable it.
I see there has been a couple new postings on this topic. Recently I finally got my R8000 to work with Polycom VoIP phone! (after nearly 4 months)
I hadn’t tried anything in several weeks, mostly because I had nothing new to try. But I had an opportunity to look at things again. Two things that immediately noticed when I reconnected the router into my home network and VoIP phone. First there was a firmware update for the R8000 router, and coincidently an update was recently loaded into the phone. It appeared things were acting differently now. One sysmtom was the display on the phone shows the date. When you forward the phone to another phone number, this display cycles back and forth between the date and the phone number that the phone was forwarded to. When things were not working before, the display would not cycle, it would only show the forwarded number and not the date. Anyway, now the phone display was cycling as it should!
I took screen shots of my Netgear setup. But in short, I fixed the phones MAC to an IP address. I set up a DMZ Server for that port. I enabled dynamic QoS, giving the phone the “Highest” Device Priority. I have port 6670 set for port forwarding, though this is left over when I was trying things earlier, so not sure it’s doing anything, but the phone works now, so I left it alone!
I don’t know if this will help anyone, but this is what I know. Just happy everything is working nicely now and has been for the last couple weeks.
-Carl Lester
Below is 5 screen shots of my R8000 set up.
