I wonder if SIP ALG is re-writing the packet to use your public IP as opposed to using NAT and discarding the original. Does your traffic decrease with SIP ALG disabled?
I wonder if SIP ALG is re-writing the packet to use your public IP as opposed to using NAT and discarding the original. Does your traffic decrease with SIP ALG disabled?
While I await a response from Cradlepoint tech support, all I can say is what the log says
"SIP ALG rejected packet from 192.168.1.51:5079 to 72.51.46.124:5060"
where the source is the VoIP device and the destination is the SIP server I am assigned. One must assume that the packet would get NATed to my public IP address had ALG not rejected it as formatted by the Grandstream.
EDIT: I did find this statement from a lay-person:
"As most modern sip clients are NAT aware, there really isn't a need for the sip alg."
But I wonder if this applies to the NAT traversal techniques in the Grandstream client?
To be clear: The VoIPo service works OK, this is an admin issue.
Last edited by stevech; 03-15-2011 at 11:44 AM.
Bookmarks