Exactly. In 1.2 the forwarded Cancels will preserve the modified attribute according to routing logic. However in 1.3, no matter what is in the routing block. The Cancel will derive information from the original request send by the UAC. Actually I guess it is not only the FROM, all the header fields are all sending out according to the original received information. No change will take effect.
I just saw the openser change log for 1.3.1, I wonder if it is the problem of message cloning. I'll update you after I test with 1.3.1. -----Original Message----- From: Bogdan-Andrei Iancu [mailto:[EMAIL PROTECTED] Sent: 2008年3月12日 1:32 To: Bai Shi Cc: [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 Bai Shi, 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? 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
