On Fri, Dec 7, 2018, 18:45 Vlad Patrascu <[email protected] wrote: > Hi Giovanni, > > Although I'm not claiming to be an expert at all in isup-sip interworking, > the ITU Q.1912.5 document seems to say that it is not necessary to > encapsulate REL in CANCEL. You can take a look at the example in Figure > III.13/Q.1912.5 from Appendix III section of the document. >
Thanks a lot Vlad! I will sure look into It. Btw, SIP-I module rocks! -Giovanni Regards, > > Vlad Patrascu > OpenSIPS Developerhttp://www.opensips-solutions.com > > On 12/07/2018 07:18 PM, Giovanni Maruzzelli wrote: > > On Fri, Dec 7, 2018 at 6:14 PM Bogdan-Andrei Iancu <[email protected]> > wrote: > >> Hi Giovanni, >> >> The CANCEL is hop-by-hop, which means each SIP hop will generate a >> completely new CANCEL (to be sent further) - there is not proxying, so the >> changes you do over the incoming CANCEL will not propagate into the >> outgoing CANCEL. >> > > Ciao Bogdan, > > yep, saw that > > >> >> I cannot recall it, but is there a standard case of pushing ISUP into >> CANCEL ? >> >> > Not sure at all, I am looking around in various (too much) documentation > around the intertube, not yet sure if you must put isup REL into CANCEL or > not... > > Have a nice wend! > -giovanni > > -- > Sincerely, > > Giovanni Maruzzelli > OpenTelecom.IT > cell: +39 347 266 56 18 > > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
