On Mon, 2009-03-02 at 14:11 -0500, Joly, Robert (CAR:9D30) wrote: > > On Mon, 2009-03-02 at 13:37 -0500, Robert Joly wrote: > > > Hi, > > > I'm looking at ways to address the problem raised in > > > http://track.sipfoundry.org/browse/XECS-2233 whereby the unexpected > > > caller ID is being presented by the gateway. > > > > > > I had a look at that issue and I see that the sipXproxy correctly > > > modifies the From: header to show the user-supplied Caller ID > > > information however the message carries a > > P-Asserted-Identity that is > > > left untouched.
> > What about alternative 3: > > > > - Configure the gateway to use From and ignore PAI? > > > > What do we know about how this is done and how configurable it is? > > I could not find a way to do this with the AudioCodes gateways that I > have to. I also did a bit of googling - this does not appear to be a > typical configuration knob of gateways. That being the case, then I think #2 is the way to go: > > > Solution #2: strip off the P-Asserted-Identity as the > > request leaves > > > sipXproxy after is has completed its spiraling. I think this amounts to writing an authplugin late in the chain that strips PAI if the domain part of the request uri is not the SIP Domain of the proxy. Ranga - will this cause a problem for sipXbridge? It would no longer get the PAI headers from the proxy. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
