IMPORTANT
The Transparency Profile is the recommended method of configuring transparency on the SBC Core for new deployments as well as when 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
Unable to show "metadata-from": No such page "_space_variables"
supports sending authenticated INVITE with same call ID as an INVITE challenged with 401 (Unauthorized) or 407 (Proxy Authentication Required) response using the "Same Call Id for Required Authorization" flag which is set in Egress IP Attributes for IP Signaling Profile. This flag is only available to configure when both of the following flags are enabled:- "Status Code 4xx-6xx" relay flag
- "Authcode Headers" transparency flag
This feature is supported via both PSX and ERE routing using the configuration settings described below.
PSX Routing
From the PSX IP Signaling Profile associated with the trunk group, set the following flags:
- Enable "AuthCode Headers" flag in the transparency section.
- Enable "Status code 4xx-6xx" relay flag.
- Enable "Same Call Id for Required Authorization" egress flag.
- Under SIP headers and parameters, set "Generate Call-ID Using" to "Do not use ingress call-id".
ERE Routing
From the SBC IP Signaling Profile associated with the trunk group, set the following flags:
- Enable "AuthCode Headers" transparency flag.
- Enable "Status Code4xx6xx" relay flag.
- Enable "Same call Id for Required Authorization" egress flag.
The default behavior of the
Unable to show "metadata-from": No such page "_space_variables"
is to not use ingress call id in IP Signaling Profile for this configuration.For detailed configuration commands, please refer to following:
- PSX configuration: PSX Documentation
- ERE configuration:
Overview
Content Tools