In this section:
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.
Note
The SBC supports globalizing the Request-URI by enabling globalization for the called number and enabling the To-Header Transparency flag. Thus, the Request-URI called number is not transmitted transparently to the egress leg (To-Header transparency flag will not affect Request-URI globalization). Note that Request-URI globalization is independent of the To-Header Transparency. This functionality applies to all scenarios where To-Header transparency is enabled, such as:
- Redirection scenarios
- Refer scenario
- Interaction with Undo LNP
- Modifying hostname of reqURI
To View and Edit Transparency Flags
On SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Ip Signaling Profile > Common Ip Attributes > Transparency Flags. The Transparency Flags window is displayed.
DEFAULT_H323
On the Transparency Flags window, choose the Ip Signaling Profile as DEFAULT_H323 to view the Transparency Flags for H323 Trunk Group.
Figure 1: Trunk Provisioning - Common Ip Attributes H323 Transparency Flags
There are no Transparency Flags for DEFAULT_H323 type of Common Ip Attributes.
DEFAULT_SIP
On the Transparency Flags window, choose the Ip Signaling Profile as DEFAULT_SIP to view the Transparency Flags for SIP Trunk Group.
The following fields are displayed:
Parameter | Description |
|---|---|
| Accept Contact Header | Set flag to allow P-CSCF to transparently pass the received Accept-Contact Header.
|
| Alert Information Header | Set this flag to transparently copy the ALERT INFO header from the ingress SIP INVITE method to the egress SIP INVITE message.
|
| Authcode Headers | Enable this flag to transparently copy the WWW Authentication header for SIP 401/407 response messages or SIP Authorization/Proxy Authorization headers.
You must enable statusCode4xx6xx relay flag when using authcodeHeaders transparency. |
| Pass Complete Contact Header | Enable flag at egress IPSP (with respect to message direction) to copy the Contact header and its parameters from the ingress message and insert in the egress message.
|
| Contact Header | Set flag to transparently pass the Contact Header Flag in egress leg with respect to the message direction.
|
| Error Info | Enable this flag to transparently copy the Error-Info header from the ingress leg to the egress leg.
|
| From Header | Enable this flag to transparently copy the userinfo@host component of the FROM header from the ingress SIP INVITE message to the egress SIP INVITE messag
Even when this flag is enabled, the IP port information is not included unless the "Include IP Ports in From and To Headers" flag, elsewhere in this IP Signaling Profile, is also enabled. |
| History Info | Controls History-info header transparency in SIP INVITE messages. When enabled, the SBC passes the History-Info header transparently from the ingress message to the egress message. When disabled, the SBC does not copy the history-info. Provision this flag on the egress leg with respect to the message direction.
|
| Max Forwards Header | Enable this flag to decrement the value in Max-Forwards header by 1 for requests traversing through the SBC. By default (Disable), the SBC populates the Max-Forwards header with the value configured in Max Fwds Default (default value is 70).
|
| Mwi Body | Enable flag to transparently copy the MWI body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision this flag on the egress leg with respect to message direction.
|
| P Access Network Info Header | Enable flag to transparently pass the p-Access-Network-Info (PANI) header from ingress to egress.
Enable this flag when SBC is configured as P-CSCF node. |
| P Called Party ID | Set flag to transparently pass the P-Called-Party-ID header from ingress to egress call leg.
|
| P Charging Vector Header | When enabled, the SBCtransparently copies the P-Charging-Vector header from the ingress message to the egress message. When disabled, the SBC does not copy the header. PCharging- Vector header transparency is supported in INVITE, REGISTER, SUBSCRIBE, OPTIONS, MESSAGE, PUBLISH, NOTIFY, REFER, and INFO messages.
|
| P Early Media | Controls P-Early Media header transparency in INVITE or non-100 RESPONSE requests and their responses if they are relayed. When enabled, the SBC transparently copies the P-Early Media header from the incoming message to the outgoing message. When disabled, the PEarly- Media header is not copied to the egress leg. Provision this flag on egress leg with respect to message direction.
|
| P Visited Network IDHeader | Enable flag to pass the P-Visited-Network-ID header transparently to the egress leg.
|
| Path Header | Enable flag to transparently copy the Path header from the ingress SIP message to the egress SIP message.
|
| Pidf Diff Body | Enable to send application/pidf-diff+xml body transparently.
|
| Qsig Body | Enable flag to transparently copy the QSIG body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision this flag on the egress leg with respect to message direction.
|
| Reason Header | When enabled, the ingress Reason header value is passed through unchanged.
|
| Referred By Header | When enabled, the SBC transparently copies the Referred-By Header (in INVITE requests/responses) from the incoming message to the outgoing message. When cleared, the Referred-By Header is not copied. Provision this flag on the egress leg (with respect to the message direction).
|
| Request URI | Enable flag to transparently copy the Request URI from the incoming message to the outgoing message for INVITE, REGISTER, SUBSCRIBE/NOTIFY. Provision this flag on the egress leg (with respect to the message direction).
|
| Route Header | Enable flag to transparently copy the Route header from the ingress SIP message to the egress SIP message.
|
| Service Route Header | Enable flag to transparently copy the Service-Route header from the ingress SIP message to the egress SIP message.
|
| Sip Body | Enable flag to transparently copy the SIP body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE, if relayed. Provision this flag on the egress leg with respect to the message direction.
|
| Sipfrag Body | Enable flag to transparently copy the SIPFRAG body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction.
|
| To Header | Enable flag to transparently copy the userinfo@host component of the TO header from the ingress SIP INVITE message to the egress SIP INVITE message. When flag is disabled, SBC generates its own TO header.
Even when this flag is enabled, the IP port information is not included unless the "Include IP Ports in From and To Headers" flag, elsewhere in this IP Signaling Profile, is also enabled. |
| Tone Body | Enable flag to transparently copy the Tone body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction.
|
| Unknown Body | Enable flag to transparently copy the Unknown body from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction.
|
| Unknown Header | Enable flag to transparently copy the Unknown header from the incoming message to the outgoing message for INVITE, REGISTER, BYE, INFO, OPTIONS, NOTIFY, REFER, and SUBSCRIBE. Provision flag on the egress leg with respect to the message direction.
|
| User To User Header | When the ingress INVITE contains the User-to-User header and this transparency flag is enabled, the User-to-User header passes through to the egress.
|
| Via Header | Use this flag to specify the behavior of VIA header, the source address of the call originator.
|
| Geolocation | Set flag to transparently pass Geolocation header, if present, in incoming message.
|
| Geolocation Routing | Set flag to transparently pass Geolocation-Routing header, if present, in incoming message.
|
| Geolocation Error | Set flag to transparently pass Geolocation-Error header, if present, in incoming message.
|
| Accept Header | Use this flag to determine Accept header behavior.
|
| Call Info Header | Set flag to transparently pass Call-Info header, if present, in the incoming message.
|
| Resource Priority Option Tag | Enable to transparently pass 'resource-priority' option tag received in Require or Supported header of SIP messages.
|
| Simple Filter Body | Enable to send application/simple-filter+xml content-type transparently.
|
| Pidf Body | Enable to send application/pidf+xml body transparently.
|
| Watcher Info Body | Enable to send application/watcherinfo+xml transparently.
|
| Rlmi Body | Enable to send application/rlmi+xml transparently.
|
| External Body | Enable to send message/external-body transparently.
|
| Warning Header | Enable to allow Warning Header transparency.
|
| External Body | Enable to send message/external-body transparently.
|
| Warning Header | Enable to allow Warning Header transparency.
|
| User Agent Header | Enable to allow User-Agent header transparency.
|
| Server Header | Enable to allow Server Header transparency.
|
| Accept Language Header | Enable to allow Accept-Language Header transparency.
|
| Resource List Body | Enable to send application/resource-lists+xml body transparently.
|
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
Overview
Content Tools