The
Unable to show "metadata-from": No such page "_space_variables"
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
Unable to show "metadata-from": No such page "_space_variables"
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 Unable to show "metadata-from": No such page "_space_variables"
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
Unable to show "metadata-from": No such page "_space_variables"
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. Unable to show "metadata-from": No such page "_space_variables"
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>
Overview
Content Tools