12 Mar
2008
12 Mar
'08
1:55 p.m.
Hi Andreas,
Just saw ur other thread regarding the PGW's 481 Call Leg does not exist. I think
since the RFC requires the From number to be identical with the initial invite and the
cancel. TM should take the modified version sent out rather than the original version
received from the UAT. So that same db operation and algorithm need not to be redo. And
the TM is anyway storing the SIP message, even if avp can be stored across the
transaction, it will cause side effect on the performance. So store a copy of the modified
message might be a good idea?
Plus the automatic ACK to negative Invite face the same problem also. And even worse,
because the routing logic doesn't have any control of it. Though it shouldn't
cause problem, but ACK to a non-existing call leg may cause UAS 487 retransmission,
doesn't it?
Rgds,
Bai Shi
-----Original Message-----
From: Andreas Granig [mailto:agranig@sipwise.com]
Sent: 2008年3月12日 19:10
To: Bai Shi
Cc: Bogdan-Andrei Iancu; users(a)lists.openser.org
Subject: Re: [OpenSER-Users] Is it a bug? TM module is sending CANCEL
requestregardlesswhat the script do with the From Header since 1.3.0
Hi,
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 see. Well, problem is that you normally do quite some processing in
INVITE, loading stuff from DB and so on, which then can for example end
up in the From header. So is there a way to preserve AVPs so they're
available in the CANCEL as well? Or do I manually have to fetch all that
stuff again for the CANCEL?
I think since TM module will take care of the uri
rewriting, it should smart enough up replace the From/To/Contact headers correct?
Agreed.
Andreas
Rgds,
Bai Shi
-----Original Message-----
From: Andreas Granig [mailto:agranig@sipwise.com]
Sent: 2008年3月12日 19:00
To: Bogdan-Andrei Iancu
Cc: Bai Shi; users(a)lists.openser.org
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
>> Users(a)lists.openser.org
>> http://lists.openser.org/cgi-bin/mailman/listinfo/users
>>
>
> _______________________________________________
> Users mailing list
> Users(a)lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/users