![]() ![]() Sip debug will show ANY traffic that hit’s the sip port (5060). Most firewalls do not do/allow this (cisco pix and asa’s are the exception to that if the loopback option is enabled). When you are behind a firewall you can’t use the external IP as it would have to go out the firewall and loop back on the same interface. Nobody has asked if there is a firewall on the remote side? Sometimes port 5060 needs to be forwarded on that to the phone (older non-sip aware firewalls for example). I don’t know the firewall you are using it might not properly forward udp? So are you SURE you forwarded UDP ports and NOT TCP ports? as sip is a UDP based forwarding TCP ports will get you nowhere which is basically what you have now. That’s the problem with editing config files you are removing a important part of the info.īasically if the firewall is setup properly then packets would be forwarded to the asterisk box and you WOULD have output, since you have none the firewall is not forwarding properly. The sip_nat.conf looks with assuming the IP EDITED is the external IP of the firewall that has the ports being forwarded. But when the the phone is external it does not work then it is a firewall/router issue. If the phone works internal then the userID and password parts are right, the extension is configured correctly. The phone is now setup and ready to use with your Vonage Business extension.I agree with bubba on this, it is a network/router issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |