In such case proxy needs to re frame the entire message keeping the branch ids and tags intact, or better approach is treat the implement B2B instead of a proxy so that these kind of services handled correctly.
Madhav On Thu, Feb 21, 2008 at 2:34 PM, anil n <[EMAIL PROTECTED]> wrote: > Hi All, > I have a query wrt some services being handled by proxy. > The example of *69 (LAST CALL RETURN) , the proxy keeps track of the last > person to call an AOR or the last person the AOR called. Then when the proxy > receives an invite with a URI of "sip:[EMAIL PROTECTED]" , it looks up the > information and forwards the call appropriately. > In the following case should the proxy change the To header information > also ? If yes, then wont this be against the proxy behavoiur. The problem is > that if the To header information (sip:[EMAIL PROTECTED]) is not changed, then > when the callee originates a BYE message, the proxy will not be able to > authenticate it as the From header information(*69) will not help in > identifying the callee as the subscriber. > > How the above problem can be solved in a proxy. > > UAC PROXY > UAS > > --INVITE sip: [EMAIL PROTECTED] ---> | ---INVITE sip: > [EMAIL PROTECTED]> > To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] | > > | > > | <-----------BYE----------------------- > > | From: [EMAIL PROTECTED] > > > regds > Anil N > > > > > --------------------------------- > Never miss a thing. Make Yahoo your homepage. > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
