Re: [OpenSIPStack] opensbc and Nokia IMS problem
Brought to you by:
joegenbaclor
Menu
▾
▴
Re: [OpenSIPStack] opensbc and Nokia IMS problem
|
From: <lma...@mi...> - 2007-10-02 22:10:14
|
I made a detailed trace and it shows, the remote port is 5060, the same as
used in the INVITE:
The request cancelled message sent by OpenSBC to Nokia IMS:
Protocol: UDP (0x11)
Source: 152.66.87.200 (152.66.87.200)
Destination: 10.0.2.42 (10.0.2.42)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Source port: sip (5060)
Destination port: sip (5060)
Length: 816
Checksum: 0x8a96 [correct]
Session Initiation Protocol
Status-Line: SIP/2.0 487 Request Cancelled
The ACK message sent back from Nokia IMS to OpenSBC
Protocol: UDP (0x11)
Source: 10.0.2.42 (10.0.2.42)
Destination: 152.66.87.200 (152.66.87.200)
User Datagram Protocol, Src Port: 49998 (49998), Dst Port: sip (5060)
Source port: 49998 (49998)
Destination port: sip (5060)
Length: 349
Checksum: 0x4adc [correct]
Session Initiation Protocol
Request-Line: ACK sip:60...@mi... SIP/2.0
----- Original Message -----
From: "Jack Damn" <455...@gm...>
To: <jb...@so...>; <ope...@li...>
Sent: Tuesday, October 02, 2007 8:04 PM
Subject: Re: [OpenSIPStack] opensbc and Nokia IMS problem
I ran into the same issue because ACK replies were sent to 5060 instead
of the one from the original INVITE beacuse of a bozo UAS sip stack.
Your call flow does not show the ports.
JD
On 10/2/07, Joegen E. Baclor <joe...@gm...> wrote:
>
> From the point of view of OpenSBC ACK for the 487 has never arrived.
> Thus, it kept on retransmitting the 487. You sure ACK is sent to
> exactly the same port (5064) as the original INVITE?
>
>
> Madarassy László wrote:
> > Hi,
> >
> > Situation:
> > User 1 is behind Nokia IMS (IMS ip address: 10.0.2.42)
> > User 2 is behind Huawei IMS (IMS ip address: 10.0.1.2)
> > OpenSBC is between them.
> >
> > User 1 calls User 2 through OpenSBC. The phone rings and User 1 cancel
> the call. The Request cancelled and the ACK starts repeating 10-20 times
> between OpenSBC and Nokia IMS.
> >
> > Here is the call flow:
> >
> >
> > 3.263009 10.0.2.42 -> 152.66.87.200 SIP/SDP Request: INVITE
> sip:60...@mi..., with session description
> > 3.267592 152.66.87.200 -> 10.0.2.42 SIP Status: 100 Trying
> > 3.283042 152.66.87.200 -> 10.0.1.2 SIP/SDP Request: INVITE
> sip:60...@mi...:5060, with session description
> > 3.305314 10.0.1.2 -> 152.66.87.200 SIP Status: 100 Trying
> > 3.593619 10.0.1.2 -> 152.66.87.200 SIP Status: 180 Ringing
> > 3.601167 152.66.87.200 -> 10.0.2.42 SIP Status: 180 Ringing
> > 5.050239 10.0.2.42 -> 152.66.87.200 SIP Request: CANCEL
> sip:60...@mi...
> > 5.057885 152.66.87.200 -> 10.0.2.42 SIP Status: 200 OK
> > 5.062168 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 5.063144 152.66.87.200 -> 10.0.1.2 SIP Request: CANCEL
> sip:60...@mi...:5060
> > 5.081024 10.0.1.2 -> 152.66.87.200 SIP Status: 200 OK
> > 5.088118 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 5.298664 10.0.1.2 -> 152.66.87.200 SIP Status: 487 Request
> Terminated
> > 5.302208 152.66.87.200 -> 10.0.1.2 SIP Request: ACK
> sip:60...@mi...:5060
> > 5.315231 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 5.347474 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 6.315403 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 6.337643 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 8.315561 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 8.338102 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 12.315907 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 12.338144 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 16.316108 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 16.338346 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 20.316413 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 20.338605 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 24.316693 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 24.339418 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> > 28.317090 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request
> Cancelled
> > 28.339596 10.0.2.42 -> 152.66.87.200 SIP Request: ACK
> sip:60...@mi...
> >
> >
> > Level 5 debug log attached.
> >
> > Best regards,
> > Laszlo Madarassy (madar)
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > opensipstack-devel mailing list
> > ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
> >
> > ------------------------------------------------------------------------
> >
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.5.488 / Virus Database: 269.13.37/1042 - Release Date:
> 10/1/2007 6:59 PM
> >
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
|
