<HTML dir=ltr><HEAD><TITLE>Re: [OpenSIPS-Users] *** correction *** Opensips is responding(SIP/2.0 503 No destinationavailable) to a CANCEL request.</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6001.18148" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText527 dir=ltr>
<DIV dir=ltr><FONT face="Courier New" size=2>Hi Bogdan,</FONT></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>Dynamic routing was not right, I was expecting that it would always be routed to the same target.</FONT></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>I should use this special block for handling CANCEL :</FONT><BR></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2># # #<BR>if ( is_method("CANCEL") ) {<BR> if ( t_check_trans() )<BR> t_relay();</FONT><FONT face="Courier New" size=2><BR> exit;<BR>}<BR></FONT></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>I was using :</FONT></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2># # # #---> Dynamic Routing<BR> if (!do_routing("0")) {<BR> sl_send_reply("503", "No destination available");<BR> exit;<BR> }</FONT></DIV></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>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>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> users-bounces@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>
<DIV>
<P><FONT size=2>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@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@atlastelecom.com<BR>> <<A href="mailto:jc@atlastelecom.com">mailto:jc@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@1.1.1.1:5060;user=phone SIP/2.0<BR>> Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK264faa44a34bd197c0-66c25-0<BR>> Max-Forwards: 69<BR>> Contact: <sip:2.2.2.2:5060 <<A href="http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>><BR>> To: <sip:15141234567@1.1.1.1:5060<BR>> <<A href="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="http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=39e771ca-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>> 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@3.3.3.3<BR>> <<A href="mailto:sip%3A222928023587914@3.3.3.3">mailto:sip%3A222928023587914@3.3.3.3</A>>>;tag=1190663040<BR>> Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK264faa44a34bd197c0-66c25-0<BR>> From: <sip:2.2.2.2:5060<BR>> <<A href="http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=39e771ca-co4209-INS026<BR>> Call-ID: 12345678<BR>> CSeq: 420901 INVITE<BR>> Record-Route: <sip:1.1.1.1;lr><BR>> Contact: sip:22215141234567@3.3.3.3:5060<BR>> <<A href="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@1.1.1.1:5060;user=phone SIP/2.0<BR>> Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK264faa44a34bd197c0-66c25-0<BR>> Max-Forwards: 69<BR>> To: <sip:15141234567@1.1.1.1:5060<BR>> <<A href="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="http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=39e771ca-co4209-INS026<BR>> Call-ID: 12345678<BR>> CSeq: 420901 CANCEL<BR>> User-Agent: ENSR2.5.47.9-IS26-RMRG106565-RG106565-CPO6500<BR>> 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=z9hG4bK264faa44a34bd197c0-66c25-0<BR>> To: <sip:15141234567@1.1.1.1:5060<BR>> <<A href="http://sip:15141234567@1.1.1.1:5060">http://sip:15141234567@1.1.1.1:5060</A>>>;tag=97b561d891fabb5de05c82496d3a199a.a955<BR>> From: <sip:2.2.2.2:5060<BR>> <<A href="http://2.2.2.2:5060/">http://2.2.2.2:5060/</A>>>;tag=39e771ca-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@lists.opensips.org<BR>> <A href="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@lists.opensips.org<BR><A href="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>