No subject
Tue May 11 03:46:02 CEST 2010
sent exactly like INVITE Request-URI, etc. , so the explanation was not =
there.
________________________________
From: users-bounces at lists.opensips.org on behalf of Bogdan-Andrei Iancu
Sent: Fri 21/05/2010 5:22 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] *** correction *** Opensips is =
responding(SIP/2.0 503 No destinationavailable) to a CANCEL request.
Hi Julien,
first of all ,you should not do dispatching for CANCEL - it should be
automatically routed by TM in order to go where the INVITE was sent (at
transaction level). You do not need to manually route the CANCEL.
Regards,
Bogdan
Julien Chavanton wrote:
> I am wandering if UA1 when generating a CANCEL should have set the =
Request-URI to the Contact-Header in the provisional response ?
> Like in an ACK and BYE ?
> I can not find the information about this in the RFC 3261
>
> =
------------------------------------------------------------------------
> *From:* users-bounces at lists.opensips.org on behalf of Laszlo
> *Sent:* Fri 21/05/2010 1:39 PM
> *To:* OpenSIPS users mailling list
> *Subject:* Re: [OpenSIPS-Users] *** correction *** Opensips is
> responding(SIP/2.0 503 No destinationavailable) to a CANCEL request.
>
>
>
> 2010/5/21 Julien Chavanton <jc at atlastelecom.com
> <mailto:jc at atlastelecom.com>>
>
> Just noticed there was an error in my last email with the address
> of the UA and Proxy
>
> Hi, I am trying to find wy Opensips is responding (SIP/2.0 503 No
> destination available) to a CANCEL request.
>
> UA1(2.2.2.2) -> P1(1.1.1.1) -> UA2(3.3.3.3)
>
> -----------------------------
>
> UA1(2.2.2.2) -> P1(1.1.1.1)
>
> INVITE sip:15141234567 at 1.1.1.1:5060;user=3Dphone SIP/2.0
> Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0
> Max-Forwards: 69
> Contact: <sip:2.2.2.2:5060 <http://2.2.2.2:5060/>>
> To: <sip:15141234567 at 1.1.1.1:5060
> <http://sip:15141234567@1.1.1.1:5060>>
> From: <sip:2.2.2.2:5060
> <http://2.2.2.2:5060/>>;tag=3D39e771ca-co4209-INS026
> Call-ID: 12345678
> CSeq: 420901 INVITE
> Content-Type: application/sdp
> Date: Fri, 23 Apr 2010 12:51:12 GMT
> Supported: 100rel
> User-Agent: ENSR2.5.47.9-IS26-RMRG20056-RG106565-CPO6500
> Content-Length: 282
>
> -----------------------------
>
> P1(1.1.1.1) -> UA1(2.2.2.2)
>
> SIP/2.0 183 Session Progress
> To: "22215141234567" <sip:222928023587914 at 3.3.3.3
> <mailto:sip%3A222928023587914 at 3.3.3.3>>;tag=3D1190663040
> Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0
> From: <sip:2.2.2.2:5060
> <http://2.2.2.2:5060/>>;tag=3D39e771ca-co4209-INS026
> Call-ID: 12345678
> CSeq: 420901 INVITE
> Record-Route: <sip:1.1.1.1;lr>
> Contact: sip:22215141234567 at 3.3.3.3:5060
> <http://sip:22215141234567@3.3.3.3:5060>
> Max-Forwards: 70
> Content-Type: application/sdp
> Content-Length: 186
> P-hint: Route[6]: mediaproxy
>
> -----------------------------
>
> UA1(2.2.2.2) -> P1(1.1.1.1)
>
> CANCEL sip:15141234567 at 1.1.1.1:5060;user=3Dphone SIP/2.0
> Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0
> Max-Forwards: 69
> To: <sip:15141234567 at 1.1.1.1:5060
> <http://sip:15141234567@1.1.1.1:5060>>
> From: <sip:2.2.2.2:5060
> <http://2.2.2.2:5060/>>;tag=3D39e771ca-co4209-INS026
> Call-ID: 12345678
> CSeq: 420901 CANCEL
> User-Agent: ENSR2.5.47.9-IS26-RMRG106565-RG106565-CPO6500
> Content-Length: 0
>
> -----------------------------
>
> P1(1.1.1.1) -> UA1(2.2.2.2)
>
> SIP/2.0 503 No destination available
> Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0
> To: <sip:15141234567 at 1.1.1.1:5060
> =
<http://sip:15141234567@1.1.1.1:5060>>;tag=3D97b561d891fabb5de05c82496d3a=
199a.a955
> From: <sip:2.2.2.2:5060
> <http://2.2.2.2:5060/>>;tag=3D39e771ca-co4209-INS026
> Call-ID: 12345678
> CSeq: 420901 CANCEL
> Server: OpenSIPS (1.5.1-notls (x86_64/linux))
> Content-Length: 0
>
>
>
>
> Hi,
>
> Can you post the full trace where the whole message flow can be =
checked?
>
> -Laszlo
>
> =
------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> =20
--
Bogdan-Andrei Iancu
www.voice-system.ro
_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
------_=_NextPart_001_01CAF904.CA49CCA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML dir=3Dltr><HEAD><TITLE>Re: [OpenSIPS-Users] *** correction *** =
Opensips is responding(SIP/2.0 503 No destinationavailable) to a CANCEL =
request.</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.6001.18148" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText527 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Hi =
Bogdan,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Dynamic routing was =
not right, I was expecting that it would always be routed to the same =
target.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>I should use =
this special block for handling CANCEL :</FONT><BR></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2># # #<BR>if ( =
is_method("CANCEL") ) {<BR> if ( t_check_trans() )<BR> =
t_relay();</FONT><FONT face=3D"Courier New" =
size=3D2><BR> exit;<BR>}<BR></FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>I was using =
:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2># # # #---> =
Dynamic Routing<BR> if (!do_routing("0")) =
{<BR> sl_send_reply("503", "No =
destination available");<BR> =
exit;<BR> }</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>From my reading I =
found out that ACK is not handled like BYE or ACK, but sent exactly like =
INVITE Request-URI, etc. , so the explanation was not there.</FONT></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> =
users-bounces at lists.opensips.org on behalf of Bogdan-Andrei =
Iancu<BR><B>Sent:</B> Fri 21/05/2010 5:22 PM<BR><B>To:</B> OpenSIPS =
users mailling list<BR><B>Subject:</B> Re: [OpenSIPS-Users] *** =
correction *** Opensips is responding(SIP/2.0 503 No =
destinationavailable) to a CANCEL request.<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi Julien,<BR><BR>first of all ,you should not do =
dispatching for CANCEL - it should be<BR>automatically routed by TM in =
order to go where the INVITE was sent (at<BR>transaction level). You do =
not need to manually route the =
CANCEL.<BR><BR>Regards,<BR>Bogdan<BR><BR>Julien Chavanton wrote:<BR>> =
I am wandering if UA1 when generating a CANCEL should have set the =
Request-URI to the Contact-Header in the provisional response ?<BR>> =
Like in an ACK and BYE ?<BR>> I can not find the information about =
this in the RFC 3261<BR>><BR>> =
------------------------------------------------------------------------<=
BR>> *From:* users-bounces at lists.opensips.org on behalf of =
Laszlo<BR>> *Sent:* Fri 21/05/2010 1:39 PM<BR>> *To:* OpenSIPS =
users mailling list<BR>> *Subject:* Re: [OpenSIPS-Users] *** =
correction *** Opensips is<BR>> responding(SIP/2.0 503 No =
destinationavailable) to a CANCEL =
request.<BR>><BR>><BR>><BR>> 2010/5/21 Julien Chavanton =
<jc at atlastelecom.com<BR>> <<A =
href=3D"mailto:jc at atlastelecom.com">mailto:jc at atlastelecom.com</A>>>=
;<BR>><BR>> Just noticed there was an =
error in my last email with the address<BR>> =
of the UA and Proxy<BR>><BR>> Hi, I am =
trying to find wy Opensips is responding (SIP/2.0 503 =
No<BR>> destination available) to a CANCEL =
request.<BR>><BR>> UA1(2.2.2.2) -> =
P1(1.1.1.1) -> UA2(3.3.3.3)<BR>><BR>> =
-----------------------------<BR>><BR>> =
UA1(2.2.2.2) -> P1(1.1.1.1)<BR>><BR>> =
INVITE sip:15141234567 at 1.1.1.1:5060;user=3Dphone =
SIP/2.0<BR>> Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0<BR>> &nbs=
p; Max-Forwards: 69<BR>> Contact: =
<sip:2.2.2.2:5060 <<A =
href=3D"http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>><BR>>&nb=
sp; To: =
<sip:15141234567 at 1.1.1.1:5060<BR>> <<A =
href=3D"http://sip:15141234567@1.1.1.1:5060">http://sip:15141234567@1.1.1=
.1:5060</A>>><BR>> From: =
<sip:2.2.2.2:5060<BR>> <<A =
href=3D"http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=3D39e7=
71ca-co4209-INS026<BR>> Call-ID: =
12345678<BR>> CSeq: 420901 =
INVITE<BR>> Content-Type: =
application/sdp<BR>> Date: Fri, 23 Apr 2010 =
12:51:12 GMT<BR>> Supported: =
100rel<BR>> User-Agent: =
ENSR2.5.47.9-IS26-RMRG20056-RG106565-CPO6500<BR>> &nb=
sp; Content-Length: 282<BR>><BR>> =
-----------------------------<BR>><BR>> =
P1(1.1.1.1) -> UA1(2.2.2.2)<BR>><BR>> =
SIP/2.0 183 Session Progress<BR>> To: =
"22215141234567" =
<sip:222928023587914 at 3.3.3.3<BR>> <<A =
href=3D"mailto:sip%3A222928023587914 at 3.3.3.3">mailto:sip%3A22292802358791=
4 at 3.3.3.3</A>>>;tag=3D1190663040<BR>> =
Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0<BR>> &nbs=
p; From: =
<sip:2.2.2.2:5060<BR>> <<A =
href=3D"http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=3D39e7=
71ca-co4209-INS026<BR>> Call-ID: =
12345678<BR>> CSeq: 420901 =
INVITE<BR>> Record-Route: =
<sip:1.1.1.1;lr><BR>> Contact: =
sip:22215141234567 at 3.3.3.3:5060<BR>> <<A =
href=3D"http://sip:22215141234567@3.3.3.3:5060">http://sip:22215141234567=
@3.3.3.3:5060</A>><BR>> Max-Forwards: =
70<BR>> Content-Type: =
application/sdp<BR>> Content-Length: =
186<BR>> P-hint: Route[6]: =
mediaproxy<BR>><BR>> =
-----------------------------<BR>><BR>> =
UA1(2.2.2.2) -> P1(1.1.1.1)<BR>><BR>> =
CANCEL sip:15141234567 at 1.1.1.1:5060;user=3Dphone =
SIP/2.0<BR>> Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0<BR>> &nbs=
p; Max-Forwards: 69<BR>> To: =
<sip:15141234567 at 1.1.1.1:5060<BR>> <<A =
href=3D"http://sip:15141234567@1.1.1.1:5060">http://sip:15141234567@1.1.1=
.1:5060</A>>><BR>> From: =
<sip:2.2.2.2:5060<BR>> <<A =
href=3D"http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=3D39e7=
71ca-co4209-INS026<BR>> Call-ID: =
12345678<BR>> CSeq: 420901 =
CANCEL<BR>> User-Agent: =
ENSR2.5.47.9-IS26-RMRG106565-RG106565-CPO6500<BR>> &n=
bsp; Content-Length: 0<BR>><BR>> =
-----------------------------<BR>><BR>> =
P1(1.1.1.1) -> UA1(2.2.2.2)<BR>><BR>> =
SIP/2.0 503 No destination available<BR>> =
Via: SIP/2.0/UDP =
2.2.2.2:5060;branch=3Dz9hG4bK264faa44a34bd197c0-66c25-0<BR>> &nbs=
p; To: =
<sip:15141234567 at 1.1.1.1:5060<BR>> <<A =
href=3D"http://sip:15141234567@1.1.1.1:5060">http://sip:15141234567@1.1.1=
.1:5060</A>>>;tag=3D97b561d891fabb5de05c82496d3a199a.a955<BR>>&n=
bsp; From: =
<sip:2.2.2.2:5060<BR>> <<A =
href=3D"http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=3D39e7=
71ca-co4209-INS026<BR>> Call-ID: =
12345678<BR>> CSeq: 420901 =
CANCEL<BR>> Server: OpenSIPS (1.5.1-notls =
(x86_64/linux))<BR>> Content-Length: =
0<BR>><BR>><BR>><BR>><BR>> Hi,<BR>><BR>> Can you =
post the full trace where the whole message flow can be =
checked?<BR>><BR>> -Laszlo<BR>><BR>> =
------------------------------------------------------------------------<=
BR>><BR>> _______________________________________________<BR>> =
Users mailing list<BR>> Users at lists.opensips.org<BR>> <A =
href=3D"http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://=
lists.opensips.org/cgi-bin/mailman/listinfo/users</A><BR>> =
<BR><BR><BR>--<BR>Bogdan-Andrei =
Iancu<BR>www.voice-system.ro<BR><BR><BR>_________________________________=
______________<BR>Users mailing list<BR>Users at lists.opensips.org<BR><A =
href=3D"http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://=
lists.opensips.org/cgi-bin/mailman/listinfo/users</A><BR></FONT></P></DIV=
></BODY></HTML>
------_=_NextPart_001_01CAF904.CA49CCA0--
More information about the Users
mailing list