IMS: Authorization header(s)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi pjsip'ers!

I'm struggling with IMS client based on pjsip. As usual pjsip is ahead of
others and some IMS features are supported already. Great job again!
Back to my problem: I register using AKA Authentication API (#define
PJSIP_HAS_DIGEST_AKA_AUTH 1) and so initial Register contains Authorization
header. The server responds with 401 Unauthorized and in the next Register
pjsip sends 2 Authorization headers. And this is something our server
doesn't like :-(
Now I'm wondering if this is the correct behaviour? Is it possible to
configure pjsip to include one Auth. header only or I have to edit pjsip
sources manualy (as mentioned in a discussion months ago) to prevent two
headers. What do you suggest? I've tested it on a trunk and version 0.8.0.

See below for pjsip.log:

REGISTER sip:ims.itpsa SIP/2.0
Via: SIP/2.0/UDP 192.168.60.124:5060
;rport;branch=z9hG4bKPj3d062379d0384e339d9a33d54c8bc682
Route: <sip:192.168.77.15:5070;lr>
Max-Forwards: 70
From: <sip:3904@ims.itpsa>;tag=4d7886eaf9ac4f65b1353767ed5d35d6
To: <sip:3904 at ims.itpsa>
Call-ID: e0c63e2838494f17b68df5485ba9c0fe
CSeq: 6960 REGISTER
Authorization: Digest username="3904", realm="ims.itpsa", nonce="",
uri="sip:ims.itpsa", response=""
User-Agent: SIPek on PJSUA v0.8.0-trunk/win32
Contact: <sip:3904 at 192.168.60.124:5060>
Expires: 3600
Content-Length:  0


--end msg--
 15:19:36.353    tsx04D5F7DC State changed from Null to Calling,
event=TX_MSG
 15:19:36.353    pjsua_acc.c Registration sent
 15:19:36.399 sip_endpoint.c Processing incoming message: Response msg
401/REGISTER/cseq=6960 (rdata04D2DEC4)
 15:19:36.399   pjsua_core.c RX 518 bytes Response msg
401/REGISTER/cseq=6960 (rdata04D2DEC4) from UDP 192.168.77.15:5070:
SIP/2.0 401 Unauthorized
Call-ID: e0c63e2838494f17b68df5485ba9c0fe
Contact: <sip:3904 at 192.168.60.124:5060>;expires=3600
CSeq: 6960 REGISTER
Expires: 3600
From: <sip:3904@ims.itpsa>;tag=4d7886eaf9ac4f65b1353767ed5d35d6
To: <sip:3904 at ims.itpsa>;tag=u3xmfswr4l
Via: SIP/2.0/UDP 192.168.60.124:5060
;branch=z9hG4bKPj3d062379d0384e339d9a33d54c8bc682;rport
WWW-Authenticate: Digest
realm="ims.itpsa",nonce="5a8ca54b1d4d312ad0f201d908acde91",opaque="VUMzTkhQSzZEdzlXeG53RTJVSXU1Mk1HMExvbWtpWGZW"
Content-Length: 0


--end msg--
 15:19:36.399    tsx04D5F7DC Incoming Response msg 401/REGISTER/cseq=6960
(rdata04D2DEC4) in state Calling
 15:19:36.399    tsx04D5F7DC State changed from Calling to Completed,
event=RX_MSG
 15:19:36.399    tsx04D60F8C Transaction created for Request msg
REGISTER/cseq=6961 (tdta04D5E770)
 15:19:36.399    tsx04D60F8C Sending Request msg REGISTER/cseq=6961
(tdta04D5E770) in state Null
 15:19:36.399  sip_resolve.c Target '192.168.77.15:5070' type=Unspecified
resolved to '192.168.77.15:5070' type=UDP (UDP transport)
 15:19:36.399   pjsua_core.c TX 782 bytes Request msg REGISTER/cseq=6961
(tdta04D5E770) to UDP 192.168.77.15:5070:
REGISTER sip:ims.itpsa SIP/2.0
Via: SIP/2.0/UDP 192.168.60.124:5060
;rport;branch=z9hG4bKPj9354f89f90614467b06e1b243866c33e
Route: <sip:192.168.77.15:5070;lr>
Max-Forwards: 70
From: <sip:3904@ims.itpsa>;tag=4d7886eaf9ac4f65b1353767ed5d35d6
To: <sip:3904 at ims.itpsa>
Call-ID: e0c63e2838494f17b68df5485ba9c0fe
CSeq: 6961 REGISTER
Authorization: Digest username="3904", realm="ims.itpsa", nonce="",
uri="sip:ims.itpsa", response=""
User-Agent: SIPek on PJSUA v0.8.0-trunk/win32
Contact: <sip:3904 at 192.168.60.124:5060>
Expires: 3600
Authorization: Digest username="3904", realm="ims.itpsa",
nonce="5a8ca54b1d4d312ad0f201d908acde91", uri="sip:ims.itpsa",
response="85687d8db9b16465902e4bbe0489d807",
opaque="VUMzTkhQSzZEdzlXeG53RTJVSXU1Mk1HMExvbWtpWGZW"
Content-Length:  0


--end msg--
 15:19:36.399    tsx04D60F8C State changed from Null to Calling,
event=TX_MSG
 15:19:36.446 sip_endpoint.c Processing incoming message: Response msg
403/REGISTER/cseq=6961 (rdata04D2DEC4)
 15:19:36.446   pjsua_core.c RX 376 bytes Response msg
403/REGISTER/cseq=6961 (rdata04D2DEC4) from UDP 192.168.77.15:5070:
SIP/2.0 403 Forbidden
Call-ID: e0c63e2838494f17b68df5485ba9c0fe
Contact: <sip:3904 at 192.168.60.124:5060>;expires=3600
CSeq: 6961 REGISTER
Expires: 3600
From: <sip:3904@ims.itpsa>;tag=4d7886eaf9ac4f65b1353767ed5d35d6
To: <sip:3904 at ims.itpsa>;tag=p2cdjkihvo
Via: SIP/2.0/UDP 192.168.60.124:5060
;branch=z9hG4bKPj9354f89f90614467b06e1b243866c33e;rport
Content-Length: 0


--end msg--
 15:19:36.446    tsx04D60F8C Incoming Response msg 403/REGISTER/cseq=6961
(rdata04D2DEC4) in state Calling
 15:19:36.446    tsx04D60F8C State changed from Calling to Completed,
event=RX_MSG
 15:19:36.446    pjsua_acc.c SIP registration failed, status=403 (Forbidden)
 15:19:39.556   sound_port.c EC suspended because of inactivity


Kind regards,
Sasa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080402/1eaf851a/attachment-0001.html 


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux