PAI Header Manipulation

You can configure the realm-config element with PAI manipulation behavior that applies to the realm's egress traffic.

You set the P-Asserted-Identity parameter in conjunction with the P-Asserted-Identity-For parameter to insert PAI headers into that realm's egress traffic. You specify the methods that you want to include by configuring the P-Asserted-Identity-For parameter for any or all of the following methods:

• INVITE
• ACK
• BYE
• REGISTER

You enable the behavior by configuring the P-Asserted-Identity parameter with the PAI value you want to insert. If you do not set both of these parameters, the ESBC does not insert the headers. This manipulation deals with the selected headers for egress INVITE and REGISTER flows, and does not interfere with PRACK INVITE flows.

If the originating message does not include any PAI headers, the ESBC inserts the headers per configuration. If PAI headers are already present, inserted by an upstream device, the ESBC:

• Adds any P-Asserted-Identity parameter headers to the top of the header list.
• Replaces any existing sip:PAI headers with the sip:PAI headers you configure with the P-Asserted-Identity parameter.
• Replaces any existing tel:PAI headers with the tel:PAI headers you configure with the P-Asserted-Identity parameter.
• The ESBC retains any existing tel:PAI headers or sip:PAI headers at the bottom of the PAI list that are not replaced by P-Asserted-Identity tel:PAI or sip:PAI values, as above.

Example configuration syntax includes:

ORACLE(realm-config)# P-Asserted-Identity sip:MyPai

ORACLE(realm-config)# P-Asserted-Identity-For INVITE, BYE

Examples

Example 1—When you configure the P-Asserted-Identity as a TEL URI and there is a tel URI PAI header in the incoming message, the ESBC replaces the incoming TEL URI with the PAI header configured in the P-Asserted-Identity parameter in the egress messages specified in the P-Asserted-Identity-For parameter.

• Incoming PAI: tel:56789
• P-Asserted-Identity configured: tel:12345
• P-Asserted-Identity-For: INVITE
• Output: Egress PAI: tel:12345

Example 2—When you configure the P-Asserted-Identity parameter as a TEL URI and there is a SIP URI in the incoming message, the ESBC inserts the SIP URI with the PAI header configured in the p-asserted-identity parameter in the egress messages specified in the P-Asserted-Identity-For parameter.

• Incoming PAI headers: sip:[e-mail]
• P-Asserted-Identity configured: tel:12345
• P-Asserted-Identity-For: INVITE
• Output Egress PAI: tel:12345 sip:[e-mail]