opensipstack-devel Mailing List for OpenSIPStack (Page 41)
Brought to you by:
joegenbaclor
Menu
▾
▴
opensipstack-devel
You can subscribe to this list here.
| 2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(12) |
Jul
(4) |
Aug
(3) |
Sep
(24) |
Oct
(45) |
Nov
(41) |
Dec
(67) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(51) |
Feb
(93) |
Mar
(54) |
Apr
(76) |
May
(114) |
Jun
(133) |
Jul
(124) |
Aug
(180) |
Sep
(53) |
Oct
(41) |
Nov
(109) |
Dec
(92) |
| 2008 |
Jan
(52) |
Feb
(40) |
Mar
(29) |
Apr
(40) |
May
(83) |
Jun
(68) |
Jul
(30) |
Aug
(72) |
Sep
(50) |
Oct
(48) |
Nov
(25) |
Dec
(80) |
| 2009 |
Jan
(9) |
Feb
(2) |
Mar
(32) |
Apr
(67) |
May
|
Jun
(7) |
Jul
(7) |
Aug
(4) |
Sep
(3) |
Oct
|
Nov
(6) |
Dec
(2) |
| 2010 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
(10) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: voice <vo...@ne...> - 2007-10-23 15:55:18
|
Hi Joegen OpenSBC is essessially a sipNAT router. Can i have openSBC with two ethernet cards running on a Linux server urunning a DHCP service. One card pointing to the Internet and the other pointing to the DHCP address? Or do i need to a router and a second Linux box providing DHCP. i.e. openSBD <==> router <==> Linux DHCP. r |
|
From: Whit T. <de...@wh...> - 2007-10-23 15:30:35
|
Hey guys, Where and when should the ringing sounds be generated? I use Asterisk so when a call is launched, asterisk generates the ringing sound. If I don't disable the PlayRingingSound methods, I get "double" rings. Should this be a configurable setting in the ATLSIP library? Whit |
|
From: <jo...@op...> - 2007-10-17 23:54:42
|
Of course. See how RFC3265Agent and RFC3680Package is used in=20 RegisterSessionManager. sebastian pastor wrote: > Thanks, Joegen. > > > > Anyway, I'd like to know a bit more=85 > > My aim is, as developer, add a *new service* to the phone (for acceedin= g to > media contents) and this will be based on exchange of SUBs and NTFYs wi= th > event=3Ddialog but with a diferent xml body than the standard. > > > > So, do you think it would be feasible or *realistic* trying to program = this > whole behaviour based on existent OpenSipStack code ? It would be an st= ate > machine regarding to SUBSCRIBEs, renews, NTFYs, response codes=85 that = I could > catch from the REGISTER one. > > Or it's better waiting for you to have this functionality implemented? > > > > How much *time* do you estimate that we are talking about? > > > > Best Regards, > > > > -Sebasti=E1n Pastor- > > Junior Telecomunications Engineer (Malaga, Spai= n) > > > > p.s BTW, *Lalith *you are a bit off-topic. But i attached a quick doc t= hat > i've elaborated explaining steps to download latest versions of the cod= es > using CVS. Hope to help you. > > > 2007/10/17, Joegen E. Baclor <joe...@gm...>: > =20 >> Hi Sebastian, >> >> I am sorry but this feature has not made it yet to the mile stone >> release because SIP Trunking was deemed a more popular need of users o= f >> OpenSBC. >> >> >> =20 >> ----------------------------------------------------------------------= -- >> >> ----------------------------------------------------------------------= --- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser= =2E >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> ----------------------------------------------------------------------= -- >> >> _______________________________________________ >> 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.14.13/1074 - Release Date: 10/1= 6/2007 2:14 PM >> =20 |
|
From: sebastian p. <seb...@gm...> - 2007-10-17 23:32:23
|
Thanks, Joegen.
Anyway, I'd like to know a bit more=85
My aim is, as developer, add a *new service* to the phone (for acceeding to
media contents) and this will be based on exchange of SUBs and NTFYs with
event=3Ddialog but with a diferent xml body than the standard.
So, do you think it would be feasible or *realistic* trying to program this
whole behaviour based on existent OpenSipStack code ? It would be an state
machine regarding to SUBSCRIBEs, renews, NTFYs, response codes=85 that I co=
uld
catch from the REGISTER one.
Or it's better waiting for you to have this functionality implemented?
How much *time* do you estimate that we are talking about?
Best Regards,
-Sebasti=E1n Pastor-
Junior Telecomunications Engineer (Malaga, Spain)
p.s BTW, *Lalith *you are a bit off-topic. But i attached a quick doc that
i've elaborated explaining steps to download latest versions of the codes
using CVS. Hope to help you.
2007/10/17, Joegen E. Baclor <joe...@gm...>:
>
> Hi Sebastian,
>
> I am sorry but this feature has not made it yet to the mile stone
> release because SIP Trunking was deemed a more popular need of users of
> OpenSBC.
>
>
|
|
From: Joegen E. B. <joe...@gm...> - 2007-10-17 10:35:26
|
Hi Sebastian, I am sorry but this feature has not made it yet to the mile stone=20 release because SIP Trunking was deemed a more popular need of users of=20 OpenSBC. sebastian pastor wrote: > Hi, > > I read that you were going to implement dialog events in 1.4.release. > > Which effect will it have in OSSPhone or ATLSIP?? I remember that i alr= eady > saw a namespace called RFC3265 in opensipstack some months ago. So, was= it > included and now you've ust debugged it? > > When i talk about effects i mean, for example, will it be added any fea= ture > like *monitoring* line state, *callback*, *Pick-up*... tipically associ= ated > to the exchange of SUBs and NTFYs with event=3Ddialog? Or the phone wil= l just > be able to understand (and answering) SUBSCRIBEs launched by other UA??= ? > > Also I'd like to know when you estimate that this release will be ready= > > Regards, > > -Sebasti=E1n Pastor- > -----------------------------------------------------------------------= -- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser.= > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > =20 |
|
From: Joegen E. B. <joe...@gm...> - 2007-10-17 10:33:31
|
This is a cross post. --- Hi, SIP Trunking is not prime time yet but you may already try it using the latest CVS copy of OpenSBC/OpenSIPStack. To Enable Trunking, you must provide an XML configuration in "SIP Trunk Config". Below is a template XML config. In this sample config, sip:win32.opensipstack.org is assumed to be the internal domain of OpenSBC while sip:opteron.opensipstack.org is the domain of your SIP Provider. [SIPTrunk] * trunk-name: This is the unique name OpenSBC will use to identify you SIP Trunk * route-set: This is the DNS resolvable domain or IP address of your trunk provider * sip-domain: This is the SIP Domain used as the host part of the To and From URIs * expires: Global expire interval for trunk registrations in seconds [Trunk-Accounts] * account - An instance of a virtual UA that will register to the Trunk Provider domain ** user-name - The user part of the From-URI ** auth-user-name - User name used for Authorization and Authentication ** auth-password - Password used for Authorization and Authentication ** inbound-route - URI specifying the identity of the UA in the internal domain ** expires - If set, this will be the expires used when the virtual UA registers to the Trunk Provider [Transient-Accounts] - Transient accounts are similar to normal Trunk-Account in terms of the parameters. The only difference is that they are also meant to be shared (in round robin fashion) by calls which are not defined in the normal trunk-accounts. This is normally used if you have a few accounts with a Trunk Provider and is meant to be shared by all your external users. ------------------------START OF XML CONFIG---------------------------------- <root> <siptrunk trunk-name="opteron.opensipstack.org" route-set="opteron.opensipstack.org" sip-domain="opteron.opensipstack.org" expires="10"> <trunk-accounts> <account user-name="1001" auth-user-name="1001" auth-password="1001" inbound-route="sip:90...@wi..." expires="3600" /> <account user-name="1002" auth-user-name="1002" auth-password="1002" inbound-route="sip:90...@wi..." expires="3600" /> <account user-name="1003" auth-user-name="1003" auth-password="1003" inbound-route="sip:90...@wi..." expires="3600" /> </trunk-accounts> <transient-accounts> <account user-name="1001" auth-user-name="1001" auth-password="1001" inbound-route="sip:90...@wi..." /> <account user-name="1002" auth-user-name="1002" auth-password="1002" inbound-route="sip:90...@wi..." /> <account user-name="1003" auth-user-name="1003" auth-password="1003" inbound-route="sip:90...@wi..." /> </transient-accounts> </siptrunk> </root> Joegen Dinesh Dialani wrote: > > Hi All, > > > > I want to use Open SBC for *SIP TRUNKING*. > > > > Here is the scenario. > > > > Internal LAN External LAN > > ------------------------------------ > > | > > Softphone ----> PBX ------|----> OpenSBC -----> Voip Provider > > > | > > | > > ------------------------------------- > > > > I wish that only OpenSBC should be visible to external world and thus > it should be able to register itself to VoipProvider. > > > > Also I want that OpenSBC should use Enum lookup first for E-164 > numbers on our enum server and if OpenSBC does not receive any > response from Enum server then it should be able to connect the call > through Voip Provider. > > > > Now here are the questions. > > > > 1. How to register OpenSBC with VoipProvider irrespective of PBX? > > t means that there should be fields in Web GUI to enter registration > request for Voip Provider and the moment OpenSBC service is started, > it should register itself with Voip Provider. > > 2. How to set preference order between Enum lookup and normal call > through VoipProvider? > > It means whenever an Sip INVITE is sent from PBX to OpenSBC for long > distance calls, OpenSBC should first search that number in our enum > servers and if it is found, call is made directly to the Receiver else > OpenSBC should direct the call to VoipProvider and create a normal call. > > 3. What are the entries to be given on B2B routing page for above > Enum and normal call to VoipProvider? > > > > Thanks in advance for you help. > > > > Dinesh > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > Opensipstack-osbcdevel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-osbcdevel > > ------------------------------------------------------------------------ > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.13/1074 - Release Date: 10/16/2007 2:14 PM > |
|
From: Lalith G. <la...@sl...> - 2007-10-17 02:48:49
|
Dear Pastor
I am very new to souceforge
Now I am developing activex for a softphone using c#
So please be kind enough to send me the sample code for using of =
ATLSIPLib
Thanks
Lalith
System Developer
Sri LankaTelecom
Sri lanka
-----Original Message-----
From: ope...@li... =
[mailto:ope...@li...] On Behalf Of =
sebastian pastor
Sent: Wednesday, October 17, 2007 1:09 AM
To: ope...@li...
Subject: Re: [OpenSIPStack] Dialog events
Hi,
I read that you were going to implement dialog events in 1.4.release.
Which effect will it have in OSSPhone or ATLSIP?? I remember that i =
already
saw a namespace called RFC3265 in opensipstack some months ago. So, was =
it
included and now you've ust debugged it?
When i talk about effects i mean, for example, will it be added any =
feature
like *monitoring* line state, *callback*, *Pick-up*... tipically =
associated
to the exchange of SUBs and NTFYs with event=3Ddialog? Or the phone will =
just
be able to understand (and answering) SUBSCRIBEs launched by other UA???
Also I'd like to know when you estimate that this release will be ready
Regards,
-Sebasti=E1n Pastor-
-------------------------------------------------------------------------=
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
|
|
From: sebastian p. <seb...@gm...> - 2007-10-16 19:38:32
|
Hi,
I read that you were going to implement dialog events in 1.4.release.
Which effect will it have in OSSPhone or ATLSIP?? I remember that i already
saw a namespace called RFC3265 in opensipstack some months ago. So, was it
included and now you've ust debugged it?
When i talk about effects i mean, for example, will it be added any feature
like *monitoring* line state, *callback*, *Pick-up*... tipically associated
to the exchange of SUBs and NTFYs with event=3Ddialog? Or the phone will ju=
st
be able to understand (and answering) SUBSCRIBEs launched by other UA???
Also I'd like to know when you estimate that this release will be ready
Regards,
-Sebasti=E1n Pastor-
|
|
From: Gaurav K. <gkh...@is...> - 2007-10-15 10:36:50
|
Joegen, It was indeed a problem with the regular expression specified by me in the B2BUA routes. The filter was not matching the URI with 'user=phone' parameter. It worked fine after I changed the configuration as per your suggestion. As always, thanks a lot for your help! Regards, Gaurav > -----Original Message----- > From: ope...@li... > [mailto:ope...@li...] On Behalf Of > Joegen E. Baclor > Sent: Monday, October 15, 2007 3:15 PM > To: ope...@li... > Cc: an...@de... > Subject: Re: [OpenSIPStack] user=phone support > > try this in B2BUA Routes [sip:*@69.90.209.57*] sip:YouDestinationDomain > > notice the "*" after .57. It should allow your filter to match uris > with parameters > > > Gaurav Kheterpal wrote: > > Hello, > > > > > > > > I'm using OpenSBC 1.1.4 and would like to confirm whether it support > > "User=phone" as part of URI. I'm having some routing issues when the URI > > contains "user=phone". > > > > > > > > 38:21.155 PWL: [CID=0x0000] Using Iface: 192.168.96.115 to send to > > Dest: 69.90.209.57 > > > > 38:21.157 INF: [CID=0x0de3] *** NO UPSTREAM ROUTE *** URI > > sip:2069220355@69.90.209.57;user=phone > > > > 38:21.157 INF: [CID=0x0de3] *** NO REGISTRATION FOUND *** Fetching > > route through local database URI sip:2069220355@69.90.209.57;user=phone > > > > 38:21.159 PWL: [CID=0x0000] *** NO MATCH *** sip:5000@* --> > > sip:2069220355@69.90.209.57;user=phone > > > > 38:21.159 PWL: [CID=0x0000] *** NO MATCH *** > sip:*@sip3.voipvoip.com > > --> sip:2069220355@69.90.209.57;user=phone > > > > 38:21.160 PWL: [CID=0x0000] *** NO MATCH *** sip:*@69.90.209.57 --> > > sip:2069220355@69.90.209.57;user=phone > > > > 38:21.160 INF: [CID=0x0de3] *** NO STATIC ROUTE *** URI > > sip:2069220355@69.90.209.57;user=phone > > > > 38:21.161 INF: [CID=0x0de3] *** Using To URI *** > > sip:2069220355@69.90.209.57;user=phone as route > > > > > > > > It looks to me that in the attached logs, since opensipstack is not able > to > > interpret "user=phone" so all route matching fails and it decides to > route > > the request based on TO URI. Is that correct? > > > > > > > > I tried to grep through the OpenSBC and OpenSIPStack code and did not > find > > any references to "user=phone". > > > > > > > > I would like to confirm whether it's supported or not? > > > > > > > > The log file is attached for reference: > > > > > > > > Thanks in advance for an early response. > > > > > > > > Regards, > > Gaurav > > > > > > > > P.S -> http://www.opensipstack.org/ seems to be down for the past 12 > hours > > or so? Is it due to any scheduled maintenance? > > > > > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------ > - > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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.14.10/1070 - Release Date: > 10/14/2007 9:22 AM > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel |
|
From: Joegen E. B. <joe...@gm...> - 2007-10-15 09:44:52
|
try this in B2BUA Routes [sip:*@69.90.209.57*] sip:YouDestinationDomain notice the "*" after .57. It should allow your filter to match uris with parameters Gaurav Kheterpal wrote: > Hello, > > > > I'm using OpenSBC 1.1.4 and would like to confirm whether it support > "User=phone" as part of URI. I'm having some routing issues when the URI > contains "user=phone". > > > > 38:21.155 PWL: [CID=0x0000] Using Iface: 192.168.96.115 to send to > Dest: 69.90.209.57 > > 38:21.157 INF: [CID=0x0de3] *** NO UPSTREAM ROUTE *** URI > sip:2069220355@69.90.209.57;user=phone > > 38:21.157 INF: [CID=0x0de3] *** NO REGISTRATION FOUND *** Fetching > route through local database URI sip:2069220355@69.90.209.57;user=phone > > 38:21.159 PWL: [CID=0x0000] *** NO MATCH *** sip:5000@* --> > sip:2069220355@69.90.209.57;user=phone > > 38:21.159 PWL: [CID=0x0000] *** NO MATCH *** sip:*@sip3.voipvoip.com > --> sip:2069220355@69.90.209.57;user=phone > > 38:21.160 PWL: [CID=0x0000] *** NO MATCH *** sip:*@69.90.209.57 --> > sip:2069220355@69.90.209.57;user=phone > > 38:21.160 INF: [CID=0x0de3] *** NO STATIC ROUTE *** URI > sip:2069220355@69.90.209.57;user=phone > > 38:21.161 INF: [CID=0x0de3] *** Using To URI *** > sip:2069220355@69.90.209.57;user=phone as route > > > > It looks to me that in the attached logs, since opensipstack is not able to > interpret "user=phone" so all route matching fails and it decides to route > the request based on TO URI. Is that correct? > > > > I tried to grep through the OpenSBC and OpenSIPStack code and did not find > any references to "user=phone". > > > > I would like to confirm whether it's supported or not? > > > > The log file is attached for reference: > > > > Thanks in advance for an early response. > > > > Regards, > Gaurav > > > > P.S -> http://www.opensipstack.org/ seems to be down for the past 12 hours > or so? Is it due to any scheduled maintenance? > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > 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.14.10/1070 - Release Date: 10/14/2007 9:22 AM > |
|
From: Gaurav K. <gkh...@is...> - 2007-10-15 06:41:23
|
Hello, I'm using OpenSBC 1.1.4 and would like to confirm whether it support "User=phone" as part of URI. I'm having some routing issues when the URI contains "user=phone". 38:21.155 PWL: [CID=0x0000] Using Iface: 192.168.96.115 to send to Dest: 69.90.209.57 38:21.157 INF: [CID=0x0de3] *** NO UPSTREAM ROUTE *** URI sip:2069220355@69.90.209.57;user=phone 38:21.157 INF: [CID=0x0de3] *** NO REGISTRATION FOUND *** Fetching route through local database URI sip:2069220355@69.90.209.57;user=phone 38:21.159 PWL: [CID=0x0000] *** NO MATCH *** sip:5000@* --> sip:2069220355@69.90.209.57;user=phone 38:21.159 PWL: [CID=0x0000] *** NO MATCH *** sip:*@sip3.voipvoip.com --> sip:2069220355@69.90.209.57;user=phone 38:21.160 PWL: [CID=0x0000] *** NO MATCH *** sip:*@69.90.209.57 --> sip:2069220355@69.90.209.57;user=phone 38:21.160 INF: [CID=0x0de3] *** NO STATIC ROUTE *** URI sip:2069220355@69.90.209.57;user=phone 38:21.161 INF: [CID=0x0de3] *** Using To URI *** sip:2069220355@69.90.209.57;user=phone as route It looks to me that in the attached logs, since opensipstack is not able to interpret "user=phone" so all route matching fails and it decides to route the request based on TO URI. Is that correct? I tried to grep through the OpenSBC and OpenSIPStack code and did not find any references to "user=phone". I would like to confirm whether it's supported or not? The log file is attached for reference: Thanks in advance for an early response. Regards, Gaurav P.S -> http://www.opensipstack.org/ seems to be down for the past 12 hours or so? Is it due to any scheduled maintenance? |
|
From: Roland A. <ope...@op...> - 2007-10-11 07:32:11
|
You probably may try to access some internal headers on the SIPMessage, like
SipMessage.GetInternalHeader("RCVADDR")
SipMessage.GetInternalHeader("RCVPORT")
also you can find out on which interface you've receied the message by using
SipMessage.GetInternalHeader("IFACE-ADDR")
hope that helps
|
|
From: Ilian J. C. P. <ip...@so...> - 2007-10-10 11:09:22
|
Hi, It's not always possible to get the callee's IP especially if a B2BUA is involved. You could however get the callee's URI (if this is sufficient for you). Check Event_OutgoingCallConnected. The target URI is passed there. Regards, Ilian Woo Chen wrote: > I'm working on an UA project. > Mime-Version: 1.0 > Content-Transfer-Encoding: 7bit > Content-Type: text/plain; charset=us-ascii > > Is there a function that returns the callee's ip address after the call is established? > > Regards, > GCC > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
|
From: Woo C. <vir...@in...> - 2007-10-10 10:19:26
|
I'm working on an UA project. Is there a function that returns the callee's ip address after the call is = established? Regards, GCC |
|
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: <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: 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-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: 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: 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: <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: <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: Roland A. <ope...@op...> - 2007-10-01 18:59:49
|
Hi,
I just analysed the SIP traffic a bit more in my scenario. The invite is sent from a UA behind a NAT with private address 192.168.0.5 and public address 84.151.207.89. When OpenSBC receives teh INVITE it detects the source IP address as 84.151.207.89 which is correct but the transport layer in the SIP stack in OpenSBC sends the 100 Trying to 192.168.0.5. According to RFC3261 section 18.2.1 the 100 Trying must follow the soruce IP address. Here from the spec
{noformat}+When the server transport receives a request over any transport, it
MUST examine the value of the "sent-by" parameter in the top Via
header field value. If the host portion of the "sent-by" parameter
contains a domain name, or if it contains an IP address that differs
from the packet source address, the server MUST add a "received"
parameter to that Via header field value. This parameter MUST
contain the source address from which the packet was received. This
is to assist the server transport layer in sending the response,
*since it must be sent to the source IP address from which the request
came.*+{noformat}
|
|
From: <na...@yu...> - 2007-10-01 16:32:13
|
Open SBC has one Ethernet card with a public address and one Ethernet
card private. The private Ethernet card connects to my own Sip server
Don
-----Original Message-----
From: ope...@li...
[mailto:ope...@li...] On Behalf Of
Joegen E. Baclor
Sent: Sunday, September 30, 2007 9:36 PM
To: ope...@li...
Subject: Re: [OpenSIPStack] Open SBC Configuration
Is OpenSBC residing in public space or is it also behind your NAT
router? So far, OpenSBC has only been tested as a far end media
anchor in public space. If you are trying to use OpenSBC to proxy media
via NAT pin holes, then OpenSBC is not equipped to deal with that
scenario as of now.
you flow should be:
SIP Client (Private) ---> NAT Router ----> {{{{ WAN / Public
Internet}}}} ---> OpenSBC (Public) ---> SIP Provider (Public)
na...@yu... wrote:
> Hi,
>
> Open SBC came right up following the build instructions. The
> application is Nat transversal and RTP proxy. Here is the
> configuration:
>
> SIP Server <- ----------------> OSBC <-
> -------------------------------> Internet<- ------------------->
Router
> <- ----------------------> Sip Client
>
> PrivateIP A PrivateIP B and Public IP A
> Public IP B and PrivateIP C Private IP D
>
>
> I have tried changing every field that made sense to me though the
OSBC
> web interface and so far have only been able to make the Sip Client
ring
> and have one way voice.
>
> What setting on the OSBC need to be changed to make this work? What
> values/syntax need to be used?
>
> Thanks,
>
> Don
>
------------------------------------------------------------------------
-
> 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
!DSPAM:16,470081ee42199297821393!
|
|
From: Joegen E. B. <joe...@gm...> - 2007-10-01 05:13:09
|
Is OpenSBC residing in public space or is it also behind your NAT
router? So far, OpenSBC has only been tested as a far end media
anchor in public space. If you are trying to use OpenSBC to proxy media
via NAT pin holes, then OpenSBC is not equipped to deal with that
scenario as of now.
you flow should be:
SIP Client (Private) ---> NAT Router ----> {{{{ WAN / Public
Internet}}}} ---> OpenSBC (Public) ---> SIP Provider (Public)
na...@yu... wrote:
> Hi,
>
> Open SBC came right up following the build instructions. The
> application is Nat transversal and RTP proxy. Here is the
> configuration:
>
> SIP Server <- ----------------> OSBC <-
> -------------------------------> Internet<- -------------------> Router
> <- ----------------------> Sip Client
>
> PrivateIP A PrivateIP B and Public IP A
> Public IP B and PrivateIP C Private IP D
>
>
> I have tried changing every field that made sense to me though the OSBC
> web interface and so far have only been able to make the Sip Client ring
> and have one way voice.
>
> What setting on the OSBC need to be changed to make this work? What
> values/syntax need to be used?
>
> Thanks,
>
> Don
> -------------------------------------------------------------------------
> 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
>
>
>
|
18 messages has been excluded from this view by a project administrator.
