On Fri, Oct 10, 2008 at 6:19 PM, Scott Lawrence <[EMAIL PROTECTED]> wrote: > > On Fri, 2008-10-03 at 14:28 -0400, M. Ranganathan wrote: >> On Mon, Sep 29, 2008 at 5:06 PM, Scott Lawrence >> <[EMAIL PROTECTED]> wrote: > >> > Ranga - could you please summarize any changes that the sipXbridge can >> > currently do to the To, From, and PAI headers and how they are >> > configured? > >> Please see attached spread sheet. Please let me know if it is clear enough. > > I've reviewed the spreadsheet and have a couple of hypothetical > questions: > > 1. In some cases, you remove any PAI header coming from the > sipXproxy. If sipXbridge were _always_ to send a PAI header to > the ITSP containing the exact same identity sipXbridge had used > to register with the ITSP, do you know of any ITSPs that would > object?
I do not know of an ITSP that would object. That transformation would be the correct thing to do. (Actually Registration with the ITSP does not have a bearing in this matter. ) > 2. Do all ITSPs that you've tested strip PAI and present the From > header information as PSTN caller-id? No. For inbound calling, bt.com for example, does not use a P-A-I header. Cbeyond.net and AT&T send me a PAI header in the inbound call which has the same information as the From header. > > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
