A little more testing. I noticed that the Authorization field differs when TCP or UDP: UDP (fails) Digest username=\"2010\", realm=\"mydns.dyndns.org\", nonce=\"e5f119c6-19e9-11df-bd09-773b7a755f78\", uri=\"sip:mydns.dyndns.org:5060\", response=\"e37be3e49c159d4f98e8bd04b36f2bd7\", algorithm=MD5, qop=\"1fffcc9f\" TCP (works) Digest username=\"2010\",realm=\"mydns.dyndns.org\",nonce=\"5d9e75c2-19ea-11df-bd0b-773b7a755f78\",uri=\"sip:mydns.dyndns.org:5060\",algorithm=MD5,response=\"45ba55d3fbafcbf2bc2aa6418656ecc2\",qop=auth,nc=00000001,cnonce=\"3a650454\" Is qop = 1fffcc9f valid in SIP? Does a cnonce need to be included also? FS sends qop=auth in the Unauthorized response. Thanks On Mon, Feb 15, 2010 at 3:17 PM, Mark Campbell-Smith <mcampbellsmith@gmail.com> wrote:
FS and the ATA are on different networks. FS is nat'd (192.168.1.120, upnp enabled on the router) and the ATA is on the internet at another location.
Any other ideas?
On Mon, Feb 15, 2010 at 3:07 PM, Brian West <brian@freeswitch.org> wrote:
Is the device behind nat with your FreeSWITCH? If so disable stun on the device. If FS is 192.168.1.120 and your device is 121.x.x.x something then I suspect its doing a hair pin thru your router. Your network is busted which is my final answer.
/b
On Feb 14, 2010, at 7:08 PM, Mark Campbell-Smith wrote:
Hi,
The sip trace provided only contains 4 SIP messages. Do you need the IP's to decode the messages?
from udp/[121.xxx.xxx.xxx] is the SPA3102 from (udp/192.168.1.120:5060) is FS server
I can register the device to all my voip providers successfully using UDP but it will not register to FS using UDP. It can register using TLS and TCP.
Very confusing as to why that would be.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org