On Fri, Sep 12, 2008 at 11:38 AM, Dale Worley <[EMAIL PROTECTED]> wrote: > On Thu, 2008-09-11 at 15:18 -0400, Robert Joly wrote: >> My thought is that if >> we know of ITSPs that have special needs when PAI is present then the >> best place to address these ITSP-specific needs is in the sipXbridge >> itself as it is its main function. > > I agree with Robert here. The ITSPs aren't likely to be conformant to > the specs (that is, accept everything that the specs permit), and it's > quite possible that important ITSPs want to use these headers in ways > that are incompatible with how sipX wants to use them. So it is > probably best to consider it to be one of sipX's responsibilities to > massage the relevant identity headers into the format that the ITSP > needs.
Agreed. I need the actual caller-id that the ITSP knows to be sent to me when the INIVITE is forwarded so I can construct the PAI header. as [EMAIL PROTECTED] The following does not suffice: From: [EMAIL PROTECTED] P-A-I: [EMAIL PROTECTED] Perhaps the answer is for sipxBridge to do its own Caller-ID management as you suggest (and that is what I had in mind initially). > > Dale > > > -- 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
