search

zling2001 / imsdroid

Automatically exported from code.google.com/p/imsdroid
0 stars 0 forks source link

Register failed #272

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
when I use imsdroid on my HTC phone to register to our SIP proxy server.
I find  the register failed.
and the sip log is this:
REGISTER sip:121.28.50.153 SIP/2.0
Via: SIP/2.0/UDP 
192.168.1.100:36468;branch=z9hG4bK1641107955;rport;comp=sigcomp;sigcomp-id="urn:
uuid:6591e8ef-3fa5-41c9-ad07-11eb36f969b0"
From: <sip:01098002051@121.28.50.153>;tag=253309060
To: <sip:01098002051@121.28.50.153>
Contact: 
<sip:01098002051@192.168.1.100:36468;transport=udp;sigcomp-id=urn:uuid:6591e8ef-
3fa5-41c9-ad07-11eb36f969b0>;expires=1700;+g.oma.sip-

im;language="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio;+g.3gpp.icsi
-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.cs-voice
Call-ID: d567f299-3113-f105-1157-4336ceef9ffb
CSeq: 1653045469 REGISTER
Content-Length: 0
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 android-ngn-stack/v2.0.448 (doubango r635)
P-Preferred-Identity: <sip:johndoe@doubango.org>
Supported: path

SIP/2.0 407 Unauthorized
Via: SIP/2.0/UDP 
192.168.1.100:36468;branch=z9hG4bK1641107955;rport;comp=sigcomp;sigcomp-id="urn:
uuid:6591e8ef-3fa5-41c9-ad07-11eb36f969b0"
From: <sip:01098002051@121.28.50.153>;tag=253309060
To: <sip:01098002051@121.28.50.153>
Call-ID: d567f299-3113-f105-1157-4336ceef9ffb
CSeq: 1653045469 REGISTER
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Proxy-Authenticate: Digest realm="POSTERITY", nonce="164112218"
Content-Length: 0

REGISTER sip:121.28.50.153 SIP/2.0
Via: SIP/2.0/UDP 
192.168.1.100:36468;branch=z9hG4bK92807790;rport;comp=sigcomp;sigcomp-id="urn:uu
id:6591e8ef-3fa5-41c9-ad07-11eb36f969b0"
From: <sip:01098002051@121.28.50.153>;tag=253309060
To: <sip:01098002051@121.28.50.153>
Contact: 
<sip:01098002051@192.168.1.100:36468;transport=udp;sigcomp-id=urn:uuid:6591e8ef-
3fa5-41c9-ad07-11eb36f969b0>;expires=1700;+g.oma.sip-

im;language="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio;+g.3gpp.icsi
-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.cs-voice
Call-ID: d567f299-3113-f105-1157-4336ceef9ffb
CSeq: 1653045470 REGISTER
Content-Length: 0
Max-Forwards: 70
Proxy-Authorization: Digest 

username="01098002051@121.28.50.153",realm="POSTERITY",nonce="164112218",uri="si
p:121.28.50.153",response="27a841755331cf6366c2666e8aa0c372",algorithm=MD5
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 android-ngn-stack/v2.0.448 (doubango r635)
P-Preferred-Identity: <sip:johndoe@doubango.org>
Supported: path

and my sip server return 603 decline . and it says the hash code is not same.
SIP/2.0 603 Decline
Via: SIP/2.0/UDP 
192.168.1.100:36468;branch=z9hG4bK92807790;rport;comp=sigcomp;sigcomp-id="urn:uu
id:6591e8ef-3fa5-41c9-ad07-11eb36f969b0"
From: <sip:01098002051@121.28.50.153>;tag=253309060
To: <sip:01098002051@121.28.50.153>
Call-ID: d567f299-3113-f105-1157-4336ceef9ffb
CSeq: 1653045470 REGISTER
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Content-Length: 0

So I want to know how imsdroid canculate the hash code ,and why the register is 
failed . 
Thanks !

Original issue reported on code.google.com by guanxian...@gmail.com on 9 Aug 2011 at 4:20

GoogleCodeExporter commented 9 years ago 
Do you really want to enable SigComp?

Original comment by boss...@yahoo.fr on 7 Sep 2011 at 9:25

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 27 Feb 2012 at 11:35