Certainly.. Here's one I made earlier. Can do a more up to date and in
depth one if you want more.
recv 411 bytes from udp/[78.105.3.165]:54650 at 11:53:47.177619:
REGISTER sip:78.129.213.17 SIP/2.0
Via: SIP/2.0/UDP
192.168.1.14:5060;rport;branch=z9hG4bK-17288995091520442185
From: <sip:[EMAIL PROTECTED]>;tag=14010403471368437451
To: <sip:[EMAIL PROTECTED]>
Call-ID: [EMAIL PROTECTED]
CSeq: 1 REGISTER
Contact: <sip:[EMAIL PROTECTED]:5060>
Max-Forwards: 70
User-Agent: Rainbow R2821 VL[SIP-V3.3] SN/001870300007
Expires: 600
Content-Length: 0
sent 644 bytes to udp/[78.105.3.165]:54650 at 11:53:47.182659:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
192.168.1.14
:
5060
;rport=54650;branch=z9hG4bK-17288995091520442185;received=78.105.3.165
recv 661 bytes from udp/[78.105.3.165]:54650 at 11:53:47.515660:
REGISTER sip:78.129.213.17 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.14:5060;branch=z9hG4bK343144464537279199
From: <sip:[EMAIL PROTECTED]>;tag=14010403471368437451
To: <sip:[EMAIL PROTECTED]>
Call-ID: [EMAIL PROTECTED]
CSeq: 2 REGISTER
Contact: <sip:[EMAIL PROTECTED]:5060>
Authorization: Digest username="1000", realm="78.129.213.17",
nonce="3b442f98-becc-45eb-b079-21b6ce5e657e", uri="sip:78.129.213.17",
response="7558e0a1325c375d6921c1be6a701d82", algorithm=MD5, qop=auth,
cnonce="234abcc436e2667097e7fe6eia53e8dd", nc=00000001
Max-Forwards: 70
User-Agent: Rainbow R2821 VL[SIP-V3.3] SN/001870300007
Expires: 600
Content-Length: 0
sent 549 bytes to udp/[78.105.3.165]:5060 at 11:53:47.517710:
SIP/2.0 200 OK
Via: SIP/2.0/UDP
192.168.1.14:5060;branch=z9hG4bK343144464537279199;received=78.105.3.165
On 7 Jul 2008, at 14:44, Brian West wrote:
Sip trace..
TPORT_LOG=1 ./freeswitch
On Jul 7, 2008, at 7:46 AM, Alex Kinch wrote:
Hi gang,
Got a strange problem with a NAT'd device that's trying to connect to
FS. The first REGISTER arrives, without auth, and FS responds with
401
Unauthorized to the correct port on the external IP address of the
firewall. However when the second attempt to REGISTER, this time with
auth, comes in, FS responds with 200 OK to the local SIP port
specified on the device. The device obviously doesn't get the 200 OK
so keeps attempting to register.
Any ideas? Tried sip-force-contact but that doesn't seem to help.
Alex
Brian West
sip:[EMAIL PROTECTED]
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
_______________________________________________
Freeswitch-users mailing list
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
