Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.
Refer to the SBC SIP Transparency Implementation Guide for additional information.
The SBC acting as P-CSCF transparently passes the P-Called-Party-ID header towards UE when pCalledPartyIdHeader transparency flag is enabled.
If the dialog initiating or out-of-dialog request contains "P-Called-Party-ID" header, the SBC stores the value of this header before forwarding the request to the next hop. If the corresponding response contains P-Preferred-Identity or P-P-Preferred-IdentityAsserted-Identity header, SBC removes these headers and inserts a P-Asserted-Identity header containing the stored value of P-Called-Party-ID header.
The SBC adds P-Asserted-Identity header in 1xx or 2xx response received from UE before forwarding the response to IMS CN. The P-Asserted-Identity is set to the saved P-Called-Party-ID header while sending the request message towards UE.
If P-Called-Party-ID header does not have Display Name, the associated URI’s display name stored at the time of registration is used (received in P-Associated-URI header in 200 OK to REGISTER).
The SBC removes P-Preferred-Identity or P-Asserted-Identity header field, if present in the ingress SIP response message from UE.
The SBC acting as IBCF exhibits following behavior:
The CLI syntax to enable/disable and transparently pass P-Called-Party-ID header is shown below.
% set profiles signaling ipSignalingProfile <Profile Name> commonIpAttributes flags pCalledPartyIDSupport <disable | enable> % set profiles signaling ipSignalingProfile <SIGNALING_PROFILE_NAME> commonIpAttributes transparencyFlags pCalledPartyIdHeader <enable | disable>
Refer to IP Signaling Profile - CLI for details of this command.