[sr-dev] Need help with "SIP 401 Unauthorized" massage from the server
Auro Tripathy
Auro.Tripathy at wdc.com
Thu Jun 28 22:58:54 CEST 2012
Daniel:
Thank you for responding. That issue is resolved (the response never made it in that case).
I have a new issues. I'm getting a "403 Not Relaying" which is a server issue.
It coming from the code fragment below. How do I debug this? I'm looking for ways to print "from_uri" and "uri".
if (from_uri!=myself && uri!=myself)
{
sl_send_reply("403","Not relaying");
exit;
}
--
2012-06-28 13:34:39.951000 [blink.exe 5304]: RECEIVED: Packet 4, +2:50:25.714000
12.0.67.48:5060 -(SIP over UDP)-> 192.168.0.102:54780
SIP/2.0 403 Not relaying
Via: SIP/2.0/UDP 192.168.0.102:54780;rport=54780;branch=z9hG4bKPj39c8c0f780c24486b9991e250d961c10
From: "test" <sip:romeo at 12.0.67.48>;tag=f55f29ebe75648969d29fefb1ebc4c3e
To: "test" <sip:romeo at 12.0.67.48>;tag=b27e1a1d33761e85846fc98f5f3a7e58.9899
Call-ID: 08e58b75f83d447e8cd2b1ecbce0b1fb
CSeq: 2 REGISTER
Server: kamailio (3.3.0 (x86_64/linux))
Content-Length: 0
---Complete sequence-------------------------
2012-06-28 13:34:39.946000 [blink.exe 5304]: SENDING: Packet 1, +2:50:25.709000
192.168.0.102:54780 -(SIP over UDP)-> 12.0.67.48:5060
REGISTER sip:12.0.67.48 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:54780;rport;branch=z9hG4bKPj0983bd6fabe94548aa0039fb9ce03b42
Max-Forwards: 70
From: "test" <sip:romeo at 12.0.67.48>;tag=f55f29ebe75648969d29fefb1ebc4c3e
To: "test" <sip:romeo at 12.0.67.48>
Contact: <sip:jvdwexqr at 192.168.0.102:54780>
Call-ID: 08e58b75f83d447e8cd2b1ecbce0b1fb
CSeq: 1 REGISTER
Expires: 600
User-Agent: Blink 0.2.7 (Windows)
Content-Length: 0
--
2012-06-28 13:34:39.947000 [blink.exe 5304]: RECEIVED: Packet 2, +2:50:25.710000
12.0.67.48:5060 -(SIP over UDP)-> 192.168.0.102:54780
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.102:54780;rport=54780;branch=z9hG4bKPj0983bd6fabe94548aa0039fb9ce03b42
From: "test" <sip:romeo at 12.0.67.48>;tag=f55f29ebe75648969d29fefb1ebc4c3e
To: "test" <sip:romeo at 12.0.67.48>;tag=b27e1a1d33761e85846fc98f5f3a7e58.3e31
Call-ID: 08e58b75f83d447e8cd2b1ecbce0b1fb
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="12.0.67.48", nonce="T+zA0E/sv6QyV/dvYk/gV7h5tk4tHiB/"
Server: kamailio (3.3.0 (x86_64/linux))
Content-Length: 0
--
2012-06-28 13:34:39.947000 [blink.exe 5304]: SENDING: Packet 3, +2:50:25.710000
192.168.0.102:54780 -(SIP over UDP)-> 12.0.67.48:5060
REGISTER sip:12.0.67.48 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:54780;rport;branch=z9hG4bKPj39c8c0f780c24486b9991e250d961c10
Max-Forwards: 70
From: "test" <sip:romeo at 12.0.67.48>;tag=f55f29ebe75648969d29fefb1ebc4c3e
To: "test" <sip:romeo at 12.0.67.48>
Contact: <sip:jvdwexqr at 192.168.0.102:54780>
Call-ID: 08e58b75f83d447e8cd2b1ecbce0b1fb
CSeq: 2 REGISTER
Expires: 600
User-Agent: Blink 0.2.7 (Windows)
Authorization: Digest username="romeo", realm="12.0.67.48", nonce="T+zA0E/sv6QyV/dvYk/gV7h5tk4tHiB/", uri="sip:12.0.67.48", response="33300003681261f95e2a5be622da6177"
Content-Length: 0
--
2012-06-28 13:34:39.951000 [blink.exe 5304]: RECEIVED: Packet 4, +2:50:25.714000
12.0.67.48:5060 -(SIP over UDP)-> 192.168.0.102:54780
SIP/2.0 403 Not relaying
Via: SIP/2.0/UDP 192.168.0.102:54780;rport=54780;branch=z9hG4bKPj39c8c0f780c24486b9991e250d961c10
From: "test" <sip:romeo at 12.0.67.48>;tag=f55f29ebe75648969d29fefb1ebc4c3e
To: "test" <sip:romeo at 12.0.67.48>;tag=b27e1a1d33761e85846fc98f5f3a7e58.9899
Call-ID: 08e58b75f83d447e8cd2b1ecbce0b1fb
CSeq: 2 REGISTER
Server: kamailio (3.3.0 (x86_64/linux))
Content-Length: 0
From: Daniel-Constantin Mierla [mailto:miconda at gmail.com]
Sent: Thursday, June 28, 2012 1:46 PM
To: Development mailing list of the sip-router project
Cc: Auro Tripathy
Subject: Re: [sr-dev] Need help with "SIP 401 Unauthorized" massage from the server
Hello,
you have to look at jitsi log files to see if the reply is received and if there are any debug messages saying what is the isssue. From kamailio point of view, all was done.
Cheers,
Daniel
On 6/28/12 5:07 PM, Auro Tripathy wrote:
I'm using the latest version of Kamailio.(3.3.0)
I don't see a Authorization Digest Response from the client. I don't.
The pattern below repeats for about 9 or 10 times and stops.
-Auro
[registration request]
U 2012/06/27 18:05:19.013685 129.253.54.224:27706 -> 192.168.102.48:5060
REGISTER sip:12.0.67.48 SIP/2.0.
Call-ID: 3063651d409c378fe801f1b8ceecf6fc at 0:0:0:0:0:0:0:0.
CSeq: 1 REGISTER.
From: "romeo" <sip:romeo at 12.0.67.48>;tag=3deb256c.
To: "romeo" <sip:romeo at 12.0.67.48>.
Via: SIP/2.0/UDP 10.101.62.62:55274;branch=z9hG4bK-333430-4b40775d090f0e6b00dc4ee7de6eca76.
Max-Forwards: 70.
User-Agent: Jitsi1.0-build.3967Windows 7.
Expires: 600.
Contact: "romeo" <sip:romeo at 10.101.62.62:55274;transport=udp;registering_acc=12_0_67_48>;expires=600.
Content-Length: 0.
.
[registration response]
U 2012/06/27 18:05:19.014111 192.168.102.48:5060 -> 129.253.54.224:55274
SIP/2.0 401 Unauthorized.
Call-ID: 3063651d409c378fe801f1b8ceecf6fc at 0:0:0:0:0:0:0:0.
CSeq: 1 REGISTER.
From: "romeo" <sip:romeo at 12.0.67.48>;tag=3deb256c.
To: "romeo" <sip:romeo at 12.0.67.48>;tag=b27e1a1d33761e85846fc98f5f3a7e58.f443.
Via: SIP/2.0/UDP 10.101.62.62:55274;branch=z9hG4bK-333430-4b40775d090f0e6b00dc4ee7de6eca76;received=129.253.54.224.
WWW-Authenticate: Digest realm="12.0.67.48", nonce="T+uu+k/rrc74I84EQbgflUNqaxyq34UH".
Server: kamailio (3.3.0 (x86_64/linux)).
Content-Length: 0.
[missing Authorization Digest Response from client or lost]
_______________________________________________
sr-dev mailing list
sr-dev at lists.sip-router.org<mailto:sr-dev at lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20120628/a57b9f12/attachment-0001.htm>
More information about the sr-dev
mailing list