On Thu, Sep 11, 2008 at 3:24 PM, Michael Jerris <[EMAIL PROTECTED]> wrote: > I have been searching for some sort of spec that describes order of > precedence and how we should find caller id information between the from, > rpid, pai headers but have not been abled to find any guidance. Is there > such a beast out there? > > Mike
>From what I know RPID is an identifier for the remote party you are trying to call ( maybe carries a token encrypted in the public key of the called party). This would be useful for called party hiding from intermediate hops. PAI is for the caller. This can be used to hide the identity of the caller from downstream proxy servers when forwarding calls. Hence for caller ID you would use PAI if present. If that is not present, use From. I dont think you would care about RPID unless you are at the receiving end of the call ( for example the terminating proxy server). Somebody please set my understanding straight if it is not correct. Regards Ranga > > > > On Sep 11, 2008, at 12:23 PM, M. Ranganathan wrote: > >> Hello >> >> The p-asserted Identity patch is confusing freeswitch it seems and >> this is having a negative impact on interop testing. Moreover, it does >> not support the header in the way ITSPs want. >> >> What ITSPs want is - if the From header is [EMAIL PROTECTED], the >> p-asserted-identity header should contain the specific caller-id that >> they want to see (normally placed in the from header and present in >> the Dial plan). Otherwise, the signaling should not contain such a >> header. This is not what the p-asserted-id change currently does. May >> I suggest a revision of this feature to work as above. >> >> >> Thank you >> >> Ranga >> >> -- >> 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 > > -- 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
