RichP Posted August 18, 2009 Author Posted August 18, 2009 Ping 192.168.1.4: packets sent 4, received 4, lost 0 Ping 192.168.1.1: packets sent 4, received 4, lost 0 Ping 64.111.80.5: timed out Quote
Blatman Posted August 18, 2009 Posted August 18, 2009 So the phone and D/G appear to be OK, and the DNS has been set up to not respond. Nothing wrong there. You have PM... Quote
Emma Posted August 19, 2009 Posted August 19, 2009 Ok, has anyone else tried to follow this and thought EH??? Quote
Bob Green Posted August 19, 2009 Posted August 19, 2009 I struggle to understand how the light switch works, never mind all this malarky! I may ping the dishwasher later then pong the iron Quote
Blatman Posted August 19, 2009 Posted August 19, 2009 Ok, has anyone else tried to follow this and thought EH??? Even I'm lost now... Bob, try pinging the microwave instead Nurse, I need an espresso... Quote
RichP Posted August 19, 2009 Author Posted August 19, 2009 It's got me foxed as well! Fantastic timing for the return of Blatman though - I'd have filed the lot under "bin" before now otherwise! Quote
philfarey Posted August 19, 2009 Posted August 19, 2009 If the phone is not registering, i would think the router is forwarding correctly.... the type of VoIP you are using uses Port 5060, forward that port to your phones IP. You did mention that you put the phone in a DMZ, so of course this might not work ) Quote
philfarey Posted August 19, 2009 Posted August 19, 2009 Just read back, and your phone's DNS needs to be set to either your router (usual setup), or a DNS address that your ISP uses. I use 208.67.222.222 which is an open free service. Quote
Blatman Posted August 19, 2009 Posted August 19, 2009 Forgot to ask... can you ping the phones public IP address, assuming it's NAT-ed, what's the translated (ie the public) IP address of the phone? Can you see it? Can you ping it? Gotta say at this point, VOIP is not realy my strong suit. Security is much more my bag Quote
RichP Posted August 19, 2009 Author Posted August 19, 2009 Thanks all - will try some of this tonight. Response from ACN Tech support: "We are not aware of any specific issues regarding the VP and your particular router model. However, I notice from looking on the net that many people have had issues with VoIP/SIP and the WNR2000. In particular I have seen one report where a user could not get VoIP working after upgrading the firmware in the router to the lastest version. Have you upgraded yours? Which firmware are you on? He was able to sort his issue after downgrading to version 1.139. Another user could not get VoIP working at all: “We eventually got the phone to ring by effectively using alternative SIP ports (5070-5071) instead of the standard (5060-5061) but still no voice would come through (this was with port forwarding as well as with the box in DMZ). Eventually we gave up, him (customers ISP support) saying it was the WNR2000s SIP ALG that was doing something wrong, and it cannot be disabled in the router interface.” If this last report is correct then the VP will not work with your router as the VP requires the standard SIP signaling ports, 5060-5066, to be open. Here is the full list of ports used by the VP: SIP signaling: 5065-5066 TCP/UDP Video RTP: 5000-5001 UDP Audio RTP: 9000-9201 UDP Firmware upgrade: 5514 UDP/TCP There is one router I know for sure that is not compatible because of a SIP algorithm that is incompatible with the ACN network (Linksys 610N) so it could be that this is the issue you are experiencing with the Netgear WNR2000. We do have many customers using Netgear routers successfully (putting the VP into a DMZ and disabling the SPI firewall). Our recommended router is a Linksys 160N." I'm a bit worried that they say the one router known not to work with the phone is the Linksys 610N, and then they go on to recommend the (similarly coded) Linksys 160N. Dodgy? Can't recall how to identify the phone's public IP address? Many thanks again Rich Quote
ACW Posted August 19, 2009 Posted August 19, 2009 Only sped read this...... but Your router will need to be able to inspect SIP signalling and then dynamically open up the RTP ports for the Voice Media ports (these are dynamic). In addition it will need potentially to change the SIP messages data if the SIP device is on a private inside address and not a real public ip. An alternative is to put the phone on a real IP, and then usually most devices can have a specific range of ports defined for RTP. You can then set up port forwarding for signaling (UDP/TCP 5060) and the RTP ports (UDP) Quote
ACW Posted August 19, 2009 Posted August 19, 2009 How do blaters - ru well. This would be a lot simpler question if it were Cisco IOS eh ? Quote
ACW Posted August 19, 2009 Posted August 19, 2009 Ok - I read the post a bit more, Can you on the netgear define a DMZ with real public ip addressing. Ie set it up so the phone has a real IP address. This will remove NAT from the equation. I suspect the netgears ability to handle Nating of SIP. Once you have done this you could open all IP for a test. If this works then it will be a case of locking down the RTP ports on the SIP endpoint and setting up the firewall for these. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.