Juha,
I believe this is handled in RFC3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks, RFC4497: Interworking between the Session Initiation Protocol (SIP) and QSIG, and RFC3323: A Privacy Mechanism for the Session Initiation Protocol (SIP) which is the "Privacy" header.
RFC4497 section 9 says: "A gateway MAY implement the P-Asserted-Identity header in accordance with [14]. If a gateway implements the P-Asserted-Identity header, it SHALL also implement the Privacy header in accordance with [13]. If a gateway does not implement the P-Asserted-Identity header, it MAY implement the Privacy header."
[13] is RFC3323 [14] is RFC3325
/a
Juha Heinanen wrote:
Alan Crosswell writes:
RPID never made it out of draft. We've been doing the UAC_from rewrites with no problems. We still use RPID with our cisco media GWs but plan to switch to P-Asserted-Identity at some point.
i don't have good enough net access to check, but does pai header also support controlling of display of calling number like rpid does with its privacy parameter? if not, then it cannot be used as a replacement of rpid header
-- juha