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:* [email protected] 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 <[email protected] > <mailto:[email protected]>> > > 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:[email protected]:5060;user=phone SIP/2.0 > Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK264faa44a34bd197c0-66c25-0 > Max-Forwards: 69 > Contact: <sip:2.2.2.2:5060 <http://2.2.2.2:5060/>> > To: <sip:[email protected]:5060 > <http://sip:[email protected]:5060>> > From: <sip:2.2.2.2:5060 > <http://2.2.2.2:5060/>>;tag=39e771ca-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:[email protected] > <mailto:sip%[email protected]>>;tag=1190663040 > Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK264faa44a34bd197c0-66c25-0 > From: <sip:2.2.2.2:5060 > <http://2.2.2.2:5060/>>;tag=39e771ca-co4209-INS026 > Call-ID: 12345678 > CSeq: 420901 INVITE > Record-Route: <sip:1.1.1.1;lr> > Contact: sip:[email protected]:5060 > <http://sip:[email protected]: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:[email protected]:5060;user=phone SIP/2.0 > Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK264faa44a34bd197c0-66c25-0 > Max-Forwards: 69 > To: <sip:[email protected]:5060 > <http://sip:[email protected]:5060>> > From: <sip:2.2.2.2:5060 > <http://2.2.2.2:5060/>>;tag=39e771ca-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=z9hG4bK264faa44a34bd197c0-66c25-0 > To: <sip:[email protected]:5060 > > <http://sip:[email protected]:5060>>;tag=97b561d891fabb5de05c82496d3a199a.a955 > From: <sip:2.2.2.2:5060 > <http://2.2.2.2:5060/>>;tag=39e771ca-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 > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
