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.
Use this object to specify parameters associated with various enhanced services and features for this SIP trunk group.
On the SBC main screen, go to Configuration > System Provisioning > Category: Trunk Provisioning > Trunk Group > Sip Trunk Group > Services.
The Services window is displayed. The services can be checked for each Address Context, for each Zone, for each Sip Trunk Group created or for all the Address Contexts, Zones and Sip Trunk Groups created. Use the drop-down box to select the desired Address Context, Zone and Sip Trunk Group.
The Edit Services window is displayed.
The following fields are displayed:
Parameter | Description |
---|---|
| Indicates whether to use the DNS server for just A-record lookups, or for full NAPTR/SRV/A lookup as specified in RFC3263.
|
| Indicates level of preconditions support for incoming (only) requests. For precondition support of outgoing requests, see Transmit Preconditions flag below.
During an ingress precondition interworking sceanario, if the remote precondition is met in PRACK, the SBC will be able to process it and send the INVITE towards egress. |
| Indicates level of preconditions support for outgoing request/response.
|
| (This flag is for specific call flows and is not intended for generic use) Enable this flag to locally generate first 183 responses for preconditions interworking before egressing INVITE. If disabled, these responses are dropped.
Do not enable
|
Honor Sdp Clock Rate | Enable this flag to allow the mapping of up to five DTMF Payload Types (PT), each with a different clock rate of a preferred or selected payload type for audio. If the flag is disabled, all DTMF PTs except 8 kHz (both send and receive) are dropped.
|
| Specifies the name of the SIP ARS (Address Reachability Service) profile. |
| Specifies the name of the Disconnect Treatment Profile. |
| Specifies the name of the Emergency Call Profile. |
| Specifies the name of the SIP Security Profile. |
Dynamic Blacklist Profile | Specifies the name of the Dynamic Blacklist Profile. |
| Use this parameter to specify how to handle emergency calls.
See Emergency Registration for emergency registration functionality. |
| If disabled at global level, the Trunk Group configuration will not be applied. The options are:
|
| If disabled at global level, the Trunk Group configuration will not be applied. The options are:
|
| Specifies the name of the Sip Jip Profile. This parameter is only supported when the SBC is configured to use an external PSX. |
| Enable this flag to allow insertion of JIP parameter in SIP trunk group ingress and egress headers.
This flag is only supported when the SBC is configured to use an external PSX. |
Transparency Profile | Specifies the name of the Transparency Profile to associate with this SIP Trunk Group. |
SIP Param Filter Profile | Specifies the name of the SIP Param Filter Profile (SPF). The SPF defines the Allowed, Supported and Required headers parameter is filter/passed. |
Use Previous Learned IP Address | Enable this flag to latch on Previous Learned IP Address before performing SRV DNS Lookups, while sending mid dialog SIP requests.
|
Hpc Call Profile | Specifies the name (1-23 characters) of the HPC Call Profile. The possible states are:
|
Dialog Event Notification Supported | Use this flag to support notification for a SUBSCRIBE with dialog event in this Trunk Group.
This configuration is not supported on ERE and is intended for use only with an external PSX. |
Colocated Pand Ecscf | Use this flag to support co-locating P-CSCF and E-CSCF on the ingress Trunk Group.
This configuration is not supported on ERE and is intended for use only with an external PSX. |
Test Call Number Profile | < The SBC uses the Test Call Number Profile to verify PSX test data access. The SBC uses this profile to determine whether to send a PSX query to a test PSX or to the production PSX. When the SBC receives a call from one of the configured numbers in the Test Call Number Profile, the SBC sends the PSX query to the test PSX, if available. When the SBC receives a call from a number not included in the Test Call Number Profile, the SBC sends the PSX query to the production PSX. |
Make the required changes and click Save at the right hand bottom of the panel to save the changes made.
Additional topics: