Hi guys, just some useful info:
in pre 1.3.0, TM was not implementing hop-by-hop cancel (as generating the requests), but it was doing just forward. In this case you had to manually mangle the CANCEL request also, similar to INVITE one. starting with 1.3.0, TM implements hop-by-hop cancel - it construct a new CANCEL request instead of forwarding the received one. Here, the FROM hdr changes (from INVITE) should be automatically reflected in the newly generated CANCEL.....If not, it means two things: - your CANCEL does not match any INVITE request - it is a bug.. I will run some tests on trunk .... Regards, Bogdan Bai Shi wrote: > Hi Andreas, > > Actually it is different issue =P. You can manually change From in CANCEL in > 1.2.2, however, in 1.3.0/1 even if you do manually modification, it won't > work at all =). > > I think since TM module will take care of the uri rewriting, it should smart > enough up replace the From/To/Contact headers correct? > > Rgds, > Bai Shi > > -----Original Message----- > From: Andreas Granig [mailto:[EMAIL PROTECTED] > Sent: 2008年3月12日 19:00 > To: Bogdan-Andrei Iancu > Cc: Bai Shi; [email protected] > Subject: Re: [OpenSER-Users] Is it a bug? TM module is sending CANCEL > requestregardless what the script do with the From Header since 1.3.0 > > Hi Bogdan, > > >> you say that in 1.3 (opposite to 1.2), the forwarded CANCELs preserve >> the received FROM hdr instead of using the changed FROM, right? >> > > I use 1.2.2 and I face the same issue. I do change the From in the > INVITE, but in CANCEL the unchanged header is sent out. Do I manually > have to replace From in the CANCEL as well, or should OpenSER > automatically take care of that? > > Andreas > > > >> Regards, >> Bogdan >> >> Bai Shi wrote: >> >>> I’m not sure if it is a bug. Currently our set up need to do >>> masquerading on the From header for all invite requests. It used to >>> work okie when we process for the CANCEL request in the routing logic. >>> But after upgrading to openser 1.3.0, the TM module is sending CANCEL >>> out using local cached From info rather than the info processed by >>> uac_replace_from. May I know is this by design or it is a bug? >>> >>> Rgds, >>> >>> BS >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.openser.org/cgi-bin/mailman/listinfo/users >>> >>> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.openser.org/cgi-bin/mailman/listinfo/users >> > > _______________________________________________ Users mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/users
