You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

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

Prior to release 7.1, when the To-Header Transparency flag is set, the Request-URI is sent transparently even when the globalization flag of the Number Globalization Profile is enabled. In this case, the To-Header Transparency does not send the called number in the Request-URI locally.

Henceforth, 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.

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.

Trunk Provisioning - Common Ip Attributes SIP Transparency Flags

 

The following fields are displayed:

Transparency Flags Parameters

 

Parameter

Description

Accept Contact HeaderSet flag to allow P-CSCF to transparently pass the received Accept-Contact Header.
  • disable (default)
  • enable
Alert Information HeaderSet this flag to transparently copy the ALERT INFO header from the ingress SIP INVITE method to the egress SIP INVITE message.
  • disable (default)
  • enable
Authcode HeadersEnable this flag to transparently copy the WWW Authentication header for SIP 401/407 response messages or SIP Authorization/Proxy Authorization headers.
  • disable (default)
  • enable

 

You must enable statusCode4xx6xx relay flag when using authcodeHeaders transparency.


Pass Complete Contact HeaderEnable 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.
  • disable (default)
  • enable
 
Contact Header Set flag to transparently pass the Contact Header Flag in egress leg with respect to the message direction.
  • disable (default)
  • enable
Errror InfoEnable this flag to transparently copy the Error-Info header from the ingress leg to the egress leg.
  • disable (default)
  • enable
 
From HeaderEnable 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
  • disable (default)
  • enable

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.
  • disable (default)
  • enable
 Max Forwards HeaderEnable 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).
  • disable (default)
  • enable
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.
  • disable (default)
  • enable
P Access Network Info HeaderEnable flag to transparently pass the p-Access-Network-Info (PANI) header from ingress to egress.
  • disable – (default) 
    Unable to show "metadata-from": No such page "_space_variables"
    suppresses the PANI header towards egress messages when the incoming message contains PANI header.
  • enable – 

    Unable to show "metadata-from": No such page "_space_variables"
    transparently passes PANI header from ingress to egress.

Enable this flag when 

Unable to show "metadata-from": No such page "_space_variables"
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.
  • disable (default)
  • enable
P Charging Vector HeaderWhen enabled, the 
Unable to show "metadata-from": No such page "_space_variables"
transparently 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.
  • disable (default)
  • enable
P Early MediaControls 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.
  • disable (default)
  • enable
P Visited Network IDHeaderEnable flag to pass the P-Visited-Network-ID header transparently to the egress leg.
  • disable (default)
  • enable
Path HeaderEnable flag to transparently copy the Path header from the ingress SIP message to the egress SIP message.
  • disable (default)
  • enable
Pidf Diff BodyEnable to send application/pidf-diff+xml body transparently.
  • disable (default)
  • enable
Qsig BodyEnable 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.
  • disable (default)
  • enable
Reason HeaderWhen enabled, the ingress Reason header value is passed through unchanged.
  • disable (default)
  • enable
Referred By HeaderWhen 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).
  • disable (default)
  • enable
Request URIEnable 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).
  • disable (default)
  • enable
Route HeaderEnable flag to transparently copy the Route header from the ingress SIP message to the egress SIP message.
  • disable (default)
  • enable
Service Route HeaderEnable flag to transparently copy the Service-Route header from the ingress SIP message to the egress SIP message.
  • disable (default)
  • enable
Sip BodyEnable 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.
  • disable (default)
  • enable
Sipfrag BodyEnable 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.
  • disable (default)
  • enable
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.

  • disable (default)
  • enable

 

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 BodyEnable 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.
  • disable (default)
  • enable
Unknown BodyEnable 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.
  • disable (default)
  • enable
Unknown HeaderEnable 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.
  • disable (default)
  • enable
User To User HeaderWhen 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.
  • disable (default)
  • enable
Via HeaderUse this flag to specify the behavior of VIA header, the source address of the call originator.
  • disable – (default) Default behavior where IP address on the VIA header is the local SIP signaling address.
  • enable – Transparently pass all the VIA headers received in original INVITE or REGISTER. With only the transparency flag enabled,  the SBC will still include the local SIP signaling address and port as the top most VIA header.
GeolocationSet flag to transparently pass Geolocation header, if present, in incoming message.
  • disable (default)
  • enable
Geolocation Routing
Set flag to transparently pass Geolocation-Routing header, if present, in incoming message.
  • disable (default)
  • enable
Geolocation Error
Set flag to transparently pass Geolocation-Error header, if present, in incoming message.
  • disable (default)
  • enable
Accept HeaderUse this flag to determine Accept header behavior.
  • disable – (default) Accept header includes: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed information.
  • enable – Accept header is transparently passed from ingress to egress.
Call Info Header
Set flag to transparently pass Call-Info header, if present, in the incoming message.
  • disable (default)
  • enable
Resource Priority Option TagEnable to transparently pass 'resource-priority' option tag received in Require or Supported header of SIP messages.
  • disable (default)
  • enable
Simple Filter BodyEnable to send application/simple-filter+xml content-type transparently.
 
  • disable (default)
  • enable
Pidf BodyEnable to send application/pidf+xml body transparently.
  • disable (default)
  • enable
Watcher Info BodyEnable to send application/watcherinfo+xml transparently.
  • disable (default)
  • enable
Rlmi BodyEnable to send application/rlmi+xml transparently.
  • disable (default)
  • enable
External BodyEnable to send message/external-body transparently.
  • disable (default)
  • enable
Warning HeaderEnable to allow Warning Header transparency.
  • disable (default)
  • enable
External BodyEnable to send message/external-body transparently.
  • disable (default)
  • enable
Warning HeaderEnable to allow Warning Header transparency.
  • disable (default)
  • enable
User Agent HeaderEnable to allow User-Agent header transparency.
  • disable (default)
  • enable
Server HeaderEnable to allow Server Header transparency.
 
  • disable (default)
  • enable
Accept Language HeaderEnable to allow Accept-Language Header transparency.
 
  • disable (default)
  • enable
Resource List BodyEnable to send application/resource-lists+xml body transparently.
 
  • disable (default)
  • enable

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.

  • No labels