DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.


IMPORTANT

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 Core acting as P-CSCF transparently passes P-Access-Network-Info header, if present, in SIP request or response received from UE (as long as it does not contain “network-provided” parameter) before forwarding the message towards the next-hop (i.e. IMS core) when pAccessNetworkInfoHeader transparency flag is set to “enable”.

The SBC can add the P-Access-Network-Info header if not present in request or response received from UE and does contain “network-provided” parameter. The SBC can also delete the P-Access-Network-Info header, if present, in SIP request or response received from UE and it contains “network-provided” parameter, before the message is forwarded to next-hop. This behavior is applicable for INVITE message and its responses, as well as non-INVITE message and its responses.

The SBC acting as IBCF can transparently pass P-Access-Network-Info header, if present, in SIP request or response received from UE, including the “network-provided” parameter. SBC can also delete P-Access-Network-Info header if it is received in ingress SIP message (applies to SIP request message).

The CLI syntax to enable/disable the P-Access-Network-Info header is shown below:

% set profiles signaling ipSignalingProfile <SIGNALING_PROFILE_NAME> commonIpAttributes transparencyFlags pAccessNetworkInfoHeader <enable | disable>

 

  • No labels