Thread: [OpenSIPStack] opensbc and Nokia IMS problem
Brought to you by:
joegenbaclor
Menu
▾
▴
opensipstack-devel
|
From: <lma...@mi...> - 2007-10-02 13:10:57
|
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)
|
|
From: <lma...@mi...> - 2007-10-02 13:27:16
|
SF removed the attachment, it's here: http://home.mik.bme.hu/~madarassy/opensbc/b2bua-2007-10-02-30752.log Laszlo Madarassy ----- Original Message ----- From: "Madarassy László" <lma...@mi...> To: <ope...@li...> Sent: Tuesday, October 02, 2007 3:10 PM Subject: [OpenSIPStack] opensbc and Nokia IMS problem 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 > |
|
From: Joegen E. B. <joe...@gm...> - 2007-10-02 14:31:27
|
From the point of view of OpenSBC ACK for the 487 has never arrived. =20 Thus, it kept on retransmitting the 487. You sure ACK is sent to=20 exactly the same port (5064) as the original INVITE? Madarassy L=E1szl=F3 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= 02...@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= 02...@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:6002@m= ik.bme.hu > 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 Cancel= led > 5.063144 152.66.87.200 -> 10.0.1.2 SIP Request: CANCEL sip:6002@m= ik.bme.hu: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:6002@mik.= bme.hu > 5.298664 10.0.1.2 -> 152.66.87.200 SIP Status: 487 Request Termin= ated > 5.302208 152.66.87.200 -> 10.0.1.2 SIP Request: ACK sip:6002@mik.= bme.hu:5060 > 5.315231 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 5.347474 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > 6.315403 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 6.337643 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > 8.315561 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 8.338102 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > 12.315907 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 12.338144 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > 16.316108 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 16.338346 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > 20.316413 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 20.338605 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > 24.316693 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 24.339418 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > 28.317090 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request Cancel= led > 28.339596 10.0.2.42 -> 152.66.87.200 SIP Request: ACK sip:6002@mik.= bme.hu > > > Level 5 debug log attached. > > Best regards, > Laszlo Madarassy (madar) > > =20 > -----------------------------------------------------------------------= - > > -----------------------------------------------------------------------= -- > 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 > =20 > -----------------------------------------------------------------------= - > > No virus found in this incoming message. > Checked by AVG Free Edition.=20 > Version: 7.5.488 / Virus Database: 269.13.37/1042 - Release Date: 10/1/= 2007 6:59 PM > =20 |
|
From: Jack D. <455...@gm...> - 2007-10-02 18:04:49
|
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=E1szl=F3 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 > |
|
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
|
|
From: Joegen E. B. <joe...@gm...> - 2007-10-03 01:54:30
|
Your OpenSBC is listening on port 5064 based on the logs you sent last=20 time. Jack is correct, there are some implementations that sends ACK to = 5060 when the server is using none standard ports. Madarassy L=E1szl=F3 wrote: > I made a detailed trace and it shows, the remote port is 5060, the same= as=20 > 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 -----=20 > From: "Jack Damn" <455...@gm...> > To: <jb...@so...>; <ope...@li...urceforge.= net> > 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: > =20 >> 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=E1szl=F3 wrote: >> =20 >>> 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 cance= l >>> =20 >> the call. The Request cancelled and the ACK starts repeating 10-20 tim= es >> between OpenSBC and Nokia IMS. >> =20 >>> Here is the call flow: >>> >>> >>> 3.263009 10.0.2.42 -> 152.66.87.200 SIP/SDP Request: INVITE >>> =20 >> sip:60...@mi..., with session description >> =20 >>> 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 >>> =20 >> sip:60...@mi...:5060, with session description >> =20 >>> 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 >>> =20 >> sip:60...@mi... >> =20 >>> 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 >>> =20 >> Cancelled >> =20 >>> 5.063144 152.66.87.200 -> 10.0.1.2 SIP Request: CANCEL >>> =20 >> sip:60...@mi...:5060 >> =20 >>> 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 >>> =20 >> sip:60...@mi... >> =20 >>> 5.298664 10.0.1.2 -> 152.66.87.200 SIP Status: 487 Request >>> =20 >> Terminated >> =20 >>> 5.302208 152.66.87.200 -> 10.0.1.2 SIP Request: ACK >>> =20 >> sip:60...@mi...:5060 >> =20 >>> 5.315231 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 5.347474 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> 6.315403 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 6.337643 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> 8.315561 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 8.338102 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> 12.315907 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 12.338144 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> 16.316108 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 16.338346 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> 20.316413 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 20.338605 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> 24.316693 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 24.339418 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> 28.317090 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>> =20 >> Cancelled >> =20 >>> 28.339596 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>> =20 >> sip:60...@mi... >> =20 >>> Level 5 debug log attached. >>> >>> Best regards, >>> Laszlo Madarassy (madar) >>> >>> >>> ---------------------------------------------------------------------= --- >>> >>> >>> =20 >> ----------------------------------------------------------------------= --- >> =20 >>> 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: >>> =20 >> 10/1/2007 6:59 PM >> =20 >> >> ----------------------------------------------------------------------= --- >> 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 >> >> =20 > -----------------------------------------------------------------------= -- > 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 > > > > =20 |
|
From: <lma...@mi...> - 2007-10-03 07:04:49
|
I'm using OpenSBC on port 5060, it's sure. In the config: Interface Address: sip:152.66.87.200:5060 I checked the log and it seems, the 5064 port is for calea trunk. ----- Original Message ----- From: "Joegen E. Baclor" <joe...@gm...> To: <ope...@li...> Sent: Wednesday, October 03, 2007 3:54 AM Subject: Re: [OpenSIPStack] opensbc and Nokia IMS problem Your OpenSBC is listening on port 5064 based on the logs you sent last time. Jack is correct, there are some implementations that sends ACK to 5060 when the server is using none standard ports. Madarassy László wrote: > 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 > > > ------------------------------------------------------------------------- > 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 |
|
From: <jo...@op...> - 2007-10-03 07:35:57
|
I see. I guess the next question would be is if the ACK reaches=20 OpenSBC. Can you capture on the OpenSBC interface to be sure? Madarassy L=E1szl=F3 wrote: > I'm using OpenSBC on port 5060, it's sure. In the config: > Interface Address: sip:152.66.87.200:5060 > > I checked the log and it seems, the 5064 port is for calea trunk. > ----- Original Message -----=20 > From: "Joegen E. Baclor" <joe...@gm...> > To: <ope...@li...> > Sent: Wednesday, October 03, 2007 3:54 AM > Subject: Re: [OpenSIPStack] opensbc and Nokia IMS problem > > > Your OpenSBC is listening on port 5064 based on the logs you sent last > time. Jack is correct, there are some implementations that sends ACK t= o > 5060 when the server is using none standard ports. > > Madarassy L=E1szl=F3 wrote: > =20 >> I made a detailed trace and it shows, the remote port is 5060, the sam= e 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 -----=20 >> From: "Jack Damn" <455...@gm...> >> To: <jb...@so...>;=20 >> <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 instea= d >> 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: >> >> =20 >>> 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=E1szl=F3 wrote: >>> >>> =20 >>>> 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 canc= el >>>> >>>> =20 >>> the call. The Request cancelled and the ACK starts repeating 10-20 ti= mes >>> between OpenSBC and Nokia IMS. >>> >>> =20 >>>> Here is the call flow: >>>> >>>> >>>> 3.263009 10.0.2.42 -> 152.66.87.200 SIP/SDP Request: INVITE >>>> >>>> =20 >>> sip:60...@mi..., with session description >>> >>> =20 >>>> 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 >>>> >>>> =20 >>> sip:60...@mi...:5060, with session description >>> >>> =20 >>>> 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 >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 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 >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 5.063144 152.66.87.200 -> 10.0.1.2 SIP Request: CANCEL >>>> >>>> =20 >>> sip:60...@mi...:5060 >>> >>> =20 >>>> 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 >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 5.298664 10.0.1.2 -> 152.66.87.200 SIP Status: 487 Request >>>> >>>> =20 >>> Terminated >>> >>> =20 >>>> 5.302208 152.66.87.200 -> 10.0.1.2 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi...:5060 >>> >>> =20 >>>> 5.315231 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 5.347474 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 6.315403 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 6.337643 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 8.315561 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 8.338102 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 12.315907 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 12.338144 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 16.316108 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 16.338346 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 20.316413 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 20.338605 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 24.316693 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 24.339418 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> 28.317090 152.66.87.200 -> 10.0.2.42 SIP Status: 487 Request >>>> >>>> =20 >>> Cancelled >>> >>> =20 >>>> 28.339596 10.0.2.42 -> 152.66.87.200 SIP Request: ACK >>>> >>>> =20 >>> sip:60...@mi... >>> >>> =20 >>>> Level 5 debug log attached. >>>> >>>> Best regards, >>>> Laszlo Madarassy (madar) >>>> >>>> >>>> --------------------------------------------------------------------= ---- >>>> >>>> >>>> >>>> =20 >>> ---------------------------------------------------------------------= ---- >>> >>> =20 >>>> 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: >>>> >>>> =20 >>> 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 >>> >>> >>> =20 >> ----------------------------------------------------------------------= --- >> 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 >> >> >> >> >> =20 > > > > -----------------------------------------------------------------------= -- > 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 > > > > =20 |
|
From: voice <vo...@ne...> - 2007-10-31 19:43:04
|
Hi Joe So what am i buying if you purchase your "24x7 OpenSBC: Cost: $150 per instance/per month" Do i have to buy any of your equipment? Can we use our own? The devil is always in the details. "For a small monthly fee, the Solegy Service Control Center will remotely manage an instance of OpenSBC running on your network. All configuration issues, upgrades, etc. will be handled by the Solegy SCC staff. Get all of the benefits of a scalable and resilient session border controller without worrying about the application itself" Will you configure it to work with our sipXecs Proxy? r. |
|
From: Joegen E. B. <joe...@gm...> - 2007-11-01 04:36:33
|
Please direct this email to sa...@so.... Commercial support is not supposed to be discussed in the development mailing list. voice wrote: > Hi Joe > > So what am i buying if you purchase your > > "24x7 OpenSBC: Cost: $150 per instance/per month" > > Do i have to buy any of your equipment? > > Can we use our own? > > The devil is always in the details. > > "For a small monthly fee, the Solegy Service Control Center will remotely > manage an instance of OpenSBC running on your network. All configuration > issues, upgrades, etc. will be handled by the Solegy SCC staff. Get all of > the benefits of a scalable and resilient session border controller without > worrying about the application itself" > > Will you configure it to work with our sipXecs Proxy? > > r. > > > > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X