search

just50415 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 0 forks source link

SIP OPTIONS rejected with error 482 (Loop detected) #67

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create 2 sip2sip.info accounts: 33xxxxxxxx7@sip2sip.info & 
33xxxxxxxx8@sip2sip.info
2. Install 2.4.3 RCSe applications on two Android phones
3. Provision both stacks accordingly
4. Two phones able to register with proxy.sipthor.net

What is the expected output? What do you see instead?
After the registration phase, SIP OPTIONS (Capabilities request) are rejected 
by SIP server with error 482 (Loop detected).

What version of the product are you using? On what operating system?
RCS Core, Provisioning, and RI applications version 2.4.3 on Android 2.3.3

Please provide any additional information below.

SIP OPTIONS and received response extracted from logcat output:

V/[RCS][SipInterface]( 2054): >>> Send SIP OPTIONS
I/System.out( 2054): >>> OPTIONS sip:911398042222@sip2sip.info;user=phone 
SIP/2.0
I/System.out( 2054): Call-ID: xwXEycTtAA@192.168.2.4
I/System.out( 2054): CSeq: 1 OPTIONS
I/System.out( 2054): From: <sip:33xxxxxxxx7@sip2sip.info>;tag=xwXEycTuAA
I/System.out( 2054): To: <sip:33xxxxxxxx8@sip2sip.info;user=phone>
I/System.out( 2054): Via: SIP/2.0/UDP 
192.168.2.4:5060;branch=z9hG4bK128c567c51c2f60bd1d0ad0cb5d311f6343339;rport
I/System.out( 2054): Max-Forwards: 70
I/System.out( 2054): Contact: 
<sip:192.168.2.4:5060>;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari
.rcse.im,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.ft"
I/System.out( 2054): Accept: application/sdp
I/System.out( 2054): Accept-Contact: 
*;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.im,urn%3Aurn-7%
3A3gpp-application.ims.iari.rcse.ft"
I/System.out( 2054): Allow: 
INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER
I/System.out( 2054): Route: <sip:85.17.186.7:5060;lr;transport=UDP>
I/System.out( 2054): P-Preferred-Identity: <sip:33659890277@sip2sip.info>
I/System.out( 2054): User-Agent: IM-client/OMA1.0 OrangeLabs-RCS-client/2.4.3
I/System.out( 2054): Content-Length: 0
I/System.out( 2054): 
I/System.out( 2054): 
-----------------------------------------------------------------------------
I/[RCS][OptionsRequestTask]( 2054): Wait response
V/[RCS][SipInterface]( 2054): <<< Receive SIP 482 response
I/System.out( 2054): <<< SIP/2.0 482 Loop detected
I/System.out( 2054): Call-ID: xwXEycTtAA@192.168.2.4
I/System.out( 2054): CSeq: 1 OPTIONS
I/System.out( 2054): From: <sip:33xxxxxxxx7@sip2sip.info>;tag=xwXEycTuAA
I/System.out( 2054): To: 
<sip:33xxxxxxxx8@sip2sip.info;user=phone>;tag=ac7e0189ab09b4fde10c77c8597b662a.6
11b
I/System.out( 2054): Via: SIP/2.0/UDP 
192.168.2.4:5060;received=92.103.84.66;branch=z9hG4bK128c567c51c2f60bd1d0ad0cb5d
311f6343339;rport=1070
I/System.out( 2054): Server: SIP Thor on OpenSIPS XS 1.8.0
I/System.out( 2054): Content-Length: 0
I/System.out( 2054): 
I/System.out( 2054): 
-----------------------------------------------------------------------------

Original issue reported on code.google.com by ericserr...@gmail.com on 11 May 2012 at 9:39

GoogleCodeExporter commented 8 years ago 
Your SIP OPTIONS seems to be strange because the request line is different as 
in my following traces (Request-line and To have the same URI):

OPTIONS tel:+33607274437 SIP/2.0
Call-ID: ejzT7cToBA@10.29.67.18
CSeq: 1 OPTIONS
From: <sip:+33679053947@sip.xxxxx.com>;tag=ejzT7cTpBA
To: <tel:+33607274437>
Via: SIP/2.0/UDP
Max-Forwards: 70
...
Content-Length: 0

Original comment by jmauffret@gmail.com on 11 May 2012 at 10:04

GoogleCodeExporter commented 8 years ago 
Yes, you are right this was a "reworked" trace.

Please find below the original one:

V/[RCS][SipInterface]( 2057): >>> Send SIP OPTIONS
I/System.out( 2057): >>> OPTIONS sip:+33659890278@sip2sip.info;user=phone 
SIP/2.0
I/System.out( 2057): Call-ID: ylMy7cTUCA@192.168.2.4
I/System.out( 2057): CSeq: 1 OPTIONS
I/System.out( 2057): From: <sip:33659890277@sip2sip.info>;tag=ylMy7cTVCA
I/System.out( 2057): To: <sip:+33659890278@sip2sip.info;user=phone>
I/System.out( 2057): Via: SIP/2.0/UDP 
192.168.2.4:5060;branch=z9hG4bK9e8a5d53df6e12f4c32d24038b965192373338;rport
I/System.out( 2057): Max-Forwards: 70
I/System.out( 2057): Contact: 
<sip:192.168.2.4:5060>;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari
.rcse.im,urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.ft"
I/System.out( 2057): Accept: application/sdp
I/System.out( 2057): Accept-Contact: 
*;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcse.im,urn%3Aurn-7%
3A3gpp-application.ims.iari.rcse.ft"
I/System.out( 2057): Allow: 
INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER
I/System.out( 2057): Route: <sip:81.23.228.129:5060;lr;transport=UDP>
I/System.out( 2057): P-Preferred-Identity: <sip:33659890277@sip2sip.info>
I/System.out( 2057): User-Agent: IM-client/OMA1.0 OrangeLabs-RCS-client/2.4.3
I/System.out( 2057): Content-Length: 0
I/System.out( 2057): 
I/System.out( 2057): 
-----------------------------------------------------------------------------
I/[RCS][OptionsRequestTask]( 2057): Wait response
I/ActivityManager( 1523): Displayed 
com.orangelabs.rcs.ri/.capabilities.CapabilitiesDiscovery: +588ms
V/[RCS][SipInterface]( 2057): <<< Receive SIP 482 response
I/System.out( 2057): <<< SIP/2.0 482 Loop detected
I/System.out( 2057): Call-ID: ylMy7cTUCA@192.168.2.4
I/System.out( 2057): CSeq: 1 OPTIONS
I/System.out( 2057): From: <sip:33659890277@sip2sip.info>;tag=ylMy7cTVCA
I/System.out( 2057): To: 
<sip:+33659890278@sip2sip.info;user=phone>;tag=f2f36c970cbb772c79daadc5c9d6e415.
474a
I/System.out( 2057): Via: SIP/2.0/UDP 
192.168.2.4:5060;received=92.103.84.66;branch=z9hG4bK9e8a5d53df6e12f4c32d24038b9
65192373338;rport=1128
I/System.out( 2057): Server: SIP Thor on OpenSIPS XS 1.8.0
I/System.out( 2057): Content-Length: 0
I/System.out( 2057): 
I/System.out( 2057): 
-----------------------------------------------------------------------------

Original comment by ericserr...@gmail.com on 11 May 2012 at 12:07

GoogleCodeExporter commented 8 years ago 
For me it's a configuration problem on your server. In my side I test with 
several IMS platforms and also with Kamailio SIP server without this kind of 
problem.

Original comment by jmauffret@gmail.com on 11 May 2012 at 12:29

GoogleCodeExporter commented 8 years ago 
I tried also with ekiga.net but I ran into Issue #41 where SIP REGISTER is 
rejected with error 606 (not Acceptable):

V/[RCS][SipInterface]( 2011): Create a transaction context 
Wp8r1cTwAA@10.174.104.235
V/[RCS][SipInterface]( 2011): >>> Send SIP REGISTER
I/System.out( 2011): >>> REGISTER sip:ekiga.net SIP/2.0
I/System.out( 2011): Call-ID: Wp8r1cTwAA@10.174.104.235
I/System.out( 2011): CSeq: 1 REGISTER
I/System.out( 2011): From: <sip:+33659890277@ekiga.net>;tag=Zp8r1cTyAA
I/System.out( 2011): To: <sip:+33659890277@ekiga.net>
I/System.out( 2011): Via: SIP/2.0/UDP 
10.174.104.235:5060;branch=z9hG4bK06a753bfded0493a685a5cfbc255367a343831;rport
I/System.out( 2011): Max-Forwards: 70
I/System.out( 2011): Contact: 
<sip:10.174.104.235:5060>;+g.oma.sip-im;+g.3gpp.cs-voice;+g.3gpp.iari-ref="urn%3
Aurn-7%3A3gpp-application.ims.iari.gsma-is"
I/System.out( 2011): Supported: path
I/System.out( 2011): Allow: 
INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER
I/System.out( 2011): Route: <sip:86.64.162.35:5060;lr;transport=UDP>
I/System.out( 2011): Expires: 3600
I/System.out( 2011): User-Agent: IM-client/OMA1.0 OrangeLabs-RCS-client/2.4.3
I/System.out( 2011): Content-Length: 0
I/System.out( 2011): 
I/System.out( 2011): 
-----------------------------------------------------------------------------
I/[RCS][RegistrationManager]( 2011): Wait response
D/CPDD_SS ( 1367): 900714262: cpdSocketClientOpen(localhost:4121)
E/CPDD_SS ( 1367): 900714263: cpdSocketClientOpen(connect failed)=-1
D/CPDD_SS ( 1367): 900714263: cpdSocketClose()
D/CPDD_SM ( 1367): 900714266:cpdGetSystemPowerState()=1
V/[RCS][SipInterface]( 2011): <<< Receive SIP 606 response
I/System.out( 2011): <<< SIP/2.0 606 Not Acceptable
I/System.out( 2011): Call-ID: Wp8r1cTwAA@10.174.104.235
I/System.out( 2011): CSeq: 1 REGISTER
I/System.out( 2011): From: <sip:+33659890277@ekiga.net>;tag=Zp8r1cTyAA
I/System.out( 2011): To: 
<sip:+33659890277@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.ba96
I/System.out( 2011): Via: SIP/2.0/UDP 
10.174.104.235:5060;branch=z9hG4bK06a753bfded0493a685a5cfbc255367a343831;rport=1
1822;received=80.214.5.43
I/System.out( 2011): Server: Kamailio (1.5.3-notls (i386/linux))
I/System.out( 2011): Content-Length: 0
I/System.out( 2011): 
I/System.out( 2011): 
-----------------------------------------------------------------------------

According to the logs, it seems that ekiga.net is using Kamailio SIP server.

Do you have some provisioning examples ?

Original comment by ericserr...@gmail.com on 11 May 2012 at 1:23