Re: [OpenSIPStack] Problem with OnOutgoingCallConnected
Brought to you by:
joegenbaclor
From: Ilian J. C. P. <ip...@so...> - 2007-06-22 07:10:29
|
Hi, ATLSIP does reply with a Proxy-Authorization header in response to a "407 Proxy Authentication Required" message. Here are my logs from OSSPhone. SEND: enc=0 747 Bytes to 192.168.0.107:11000:UDP (INVITE sip:302@192.168.0.107 SIP/2.0) Interface Address=192.168.0.107 INVITE sip:302@192.168.0.107 SIP/2.0 From: 301 <sip:301@192.168.0.107>;tag=5c022811fcf8181085d3df71ad1fd0c5 To: sip:302@192.168.0.107 Via: SIP/2.0/UDP 192.168.0.107:5060;iid=2258;branch=z9hG4bK5c022811fcf8181085d2df71ad1fd0c5;uas-addr=192.168.0.107;rport CSeq: 4711 INVITE Call-ID: 5c022811-fcf8-1810-9162-df71ad1fd0c5 Contact: "301" <sip:301@192.168.0.107:5060> User-Agent: OpenSIPStack-1.1.6-166 Max-Forwards: 10 Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS Content-Type: application/sdp Content-Length: 205 v=0 o=- 1182495843 1182495843 IN IP4 192.168.0.107 s=OSS RTP Session c=IN IP4 192.168.0.107 t=0 0 m=audio 5000 RTP/AVP 101 4 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:4 G723/8000 ----------------2:13:29.134---------------- RCV: enc=0 322 Bytes from RCVADDR: 192.168.0.107:RCVPORT: 11000:UDP (SIP/2.0 100 Trying) SIP/2.0 100 Trying From: 301 <sip:301@192.168.0.107>;tag=5c022811fcf8181085d3df71ad1fd0c5 To: sip:302@192.168.0.107 Via: SIP/2.0/UDP 192.168.0.107:5060;iid=2258;branch=z9hG4bK5c022811fcf8181085d2df71ad1fd0c5;uas-addr=192.168.0.107 CSeq: 4711 INVITE Call-ID: 5c022811-fcf8-1810-9162-df71ad1fd0c5 Content-Length: 0 ----------------2:13:29.216---------------- RCV: enc=0 567 Bytes from RCVADDR: 192.168.0.107:RCVPORT: 11000:UDP (SIP/2.0 407 Proxy Authentication Required) SIP/2.0 407 Proxy Authentication Required From: 301 <sip:301@192.168.0.107>;tag=5c022811fcf8181085d3df71ad1fd0c5 To: <sip:302@192.168.0.107>;tag=b4512811fcf818109ff790ed26e13033 Via: SIP/2.0/UDP 192.168.0.107:5060;iid=2258;branch=z9hG4bK5c022811fcf8181085d2df71ad1fd0c5;uas-addr=192.168.0.107;rport=5060;received=192.168.0.107 CSeq: 4711 INVITE Call-ID: 5c022811-fcf8-1810-9162-df71ad1fd0c5 Proxy-Authenticate: Digest realm=192.168.0.107, nonce="530e7db0dbb55accddef8327d684c2ca", opaque="c9d379cc8f16ee0ac7fa8a1993816fc7", algorithm=MD5 Content-Length: 0 ----------------2:13:29.257---------------- SEND: enc=0 543 Bytes to 192.168.0.107:11000:UDP (ACK sip:302@192.168.0.107 SIP/2.0) Interface Address=192.168.0.107 ACK sip:302@192.168.0.107 SIP/2.0 From: 301 <sip:301@192.168.0.107>;tag=5c022811fcf8181085d3df71ad1fd0c5 To: <sip:302@192.168.0.107>;tag=b4512811fcf818109ff790ed26e13033 Via: SIP/2.0/UDP 192.168.0.107:5060;iid=2258;branch=z9hG4bK5c022811fcf8181085d2df71ad1fd0c5;uas-addr=192.168.0.107;rport CSeq: 4711 ACK Call-ID: 5c022811-fcf8-1810-9162-df71ad1fd0c5 Contact: "301" <sip:301@192.168.0.107:5060> User-Agent: OpenSIPStack-1.1.6-166 Max-Forwards: 10 Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS Content-Length: 0 ----------------2:13:29.240---------------- RCV: enc=0 567 Bytes from RCVADDR: 192.168.0.107:RCVPORT: 11000:UDP (SIP/2.0 407 Proxy Authentication Required) SIP/2.0 407 Proxy Authentication Required From: 301 <sip:301@192.168.0.107>;tag=5c022811fcf8181085d3df71ad1fd0c5 To: <sip:302@192.168.0.107>;tag=b4512811fcf818109ff790ed26e13033 Via: SIP/2.0/UDP 192.168.0.107:5060;iid=2258;branch=z9hG4bK5c022811fcf8181085d2df71ad1fd0c5;uas-addr=192.168.0.107;rport=5060;received=192.168.0.107 CSeq: 4711 INVITE Call-ID: 5c022811-fcf8-1810-9162-df71ad1fd0c5 Proxy-Authenticate: Digest realm=192.168.0.107, nonce="530e7db0dbb55accddef8327d684c2ca", opaque="c9d379cc8f16ee0ac7fa8a1993816fc7", algorithm=MD5 Content-Length: 0 ----------------2:13:29.310---------------- SEND: enc=0 945 Bytes to 192.168.0.107:11000:UDP (INVITE sip:302@192.168.0.107 SIP/2.0) Interface Address=192.168.0.107 INVITE sip:302@192.168.0.107 SIP/2.0 From: 301 <sip:301@192.168.0.107>;tag=5c022811fcf8181085d3df71ad1fd0c5 To: sip:302@192.168.0.107 Via: SIP/2.0/UDP 192.168.0.107:5060;iid=2258;branch=z9hG4bK6e7c2811fcf8181085d3df71ad1fd0c5;uas-addr=192.168.0.107;rport CSeq: 4712 INVITE Call-ID: 5c022811-fcf8-1810-9162-df71ad1fd0c5 Contact: "301" <sip:301@192.168.0.107:5060> User-Agent: OpenSIPStack-1.1.6-166 Max-Forwards: 10 Proxy-Authorization: Digest username="301", realm="192.168.0.107", nonce="530e7db0dbb55accddef8327d684c2ca", uri="sip:302@192.168.0.107", response="2f4837e25f547ca1d87b548a0c232986", algorithm=MD5 Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS Content-Type: application/sdp Content-Length: 205 v=0 o=- 1182495843 1182495843 IN IP4 192.168.0.107 s=OSS RTP Session c=IN IP4 192.168.0.107 t=0 0 m=audio 5000 RTP/AVP 101 4 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:4 G723/8000 tomach wrote: > Hello! > > Thanks a lot for the answer. > Right now I can register. The problem is that after I am registered and try to make call ATLSIP do not send "Proxy-Authorization" information: > for example: > Proxy-Authorization: Digest username="107", realm="192.168.2.69", nonce="00027556963e1f5da6b506f697a3907f2f53637b", uri="sip:00586820726@192.168.2.69", response="0e2bd6b0a8cc2c19a7a4ad744d4e017b", algorithm=MD5 > Authentication Scheme: Digest > Username: "107" > Realm: "192.168.2.69" > Nonce Value: "00027556963e1f5da6b506f697a3907f2f53637b" > Authentication URI: "sip:00586820726@192.168.2.69" > Digest Authentication Response: "0e2bd6b0a8cc2c19a7a4ad744d4e017b" > Algorithm: MD5 > > Above is the example what is missing in INVITE that ALTSIP is sending to sipServer. > Is there any chance to add it, that INVITE would be complete? > > Best Regards, > Tom > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |