Page History
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Additional Sections:
|
| Panel | ||||
|---|---|---|---|---|
In this section:
|
SBC can define a set of SIP Tags and Method names and assign that profile to a Trunk Group (TG). The SIP headers configured in this table are transparently passed on to the Egress TG if received in the Ingress SIP message. This configuration is used in concert with a number of new internal arrays and tables to provide the new transparency functionality within the SBC.
SIP tags are avaialble only for unknown SIP parameter transparency. Known SIP parameter transparency is still determined using existing SBC application logic (from Ingress leg to Egress leg) and configuration.
These profile have precedence of existing mechanism/flags when it comes to passing through content of Allow/Supported/Require headers but it does not impact corresponding semantics exeremoveded by SBC. It is the responsibility of the user to configure the system properly so that passed through values do not conflict with semantics. For example, 100rel should not be configured as pass-through if 100rel support for SIP Trunk Group Signaling is disabled.
The profile both for Ingress and Egress legs determines the actual pass-through result. It is possible to control pass-through for individual values for each header.
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
To View SIP Param Filter Profile
...
Overview
Content Tools