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.

Use this object to specify parameters associated with various enhanced services and features for this SIP trunk group.

To View and Edit Services

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.

Sip Trunk Group - Services

 

The following fields are displayed:

Sip Trunk Group - Services

 

Parameter

Description

DNS Support Type

Indicates whether to use the DNS server for just A-record lookups, or for full NAPTR/SRV/A lookup as specified in RFC3263.

  • A-only
  • A-srv-naptr

Preconditions

 Indicates level of preconditions support for incoming (only) requests. For precondition support of outgoing requests, see Transmit Preconditions flag below.
  • None – (default)
  • Required
  • Supported
  • Transparent

Note
  • If Preconditions interworking is configured as “Use UPDATE”, configure the Allow UPDATE flag as well.
  • If Preconditions interworking is configured as “Use UPDATE” but a 183 from the peer does not have UPDATE in the Allow header, the SBC will not send an UPDATE and does not take any other action, thus a call timeout timer generates to terminate the call.
  • Do not set Preconditions to "Required" for interworking scenarios.

  • 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.


Transmit Preconditions

Indicates level of preconditions support for outgoing request/response.
  • none – When set to "none",  SBC does not add SIP precondition attributes in SDP of outgoing request even if attributes are present in the SDP of incoming requests.
  • required – Use this option to add SIP precondition attributes in SDP of outgoing request even if attributes are NOT present in the SDP of incoming requests. If precondition attributes are added by SBC, the local preconditions are set to ‘met’ and remote preconditions are set to ‘not-met’.
  • supported – (default) Use this option to ensure backward compatibility behavior. Use this option to add SIP precondition attributes in SDP of outgoing request only if attributes are present in the incoming request.

Precondition Intwk Using183

(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.

  • Disabled (default)
  • Enabled

Do not enable Precondition Intwk Using183 when End-to-End Prack is configured.

Note
  • If both Preconditions Profile and the flag preconditionIntwkUsing183 are configured, the Preconditions Profile takes a higher precedence. Settings of “preconditions=transparent”/”100rel support=yes” on both legs is the only supported configuration for proper precondition interworking functionality.
  • Do not enable preConditionIntwkUsing183 when End-to-End Prack is configured.

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.

  • Disabled (default)
  • Enabled

Sip Ars Profile

Specifies the name of the SIP ARS (Address Reachability Service) profile.

Disconnect Treatment Profile

Specifies the name of the Disconnect Treatment Profile.

Emergency Call Profile

Specifies the name of the Emergency Call Profile.

Sip Security Profile

Specifies the name of the SIP Security Profile.
Dynamic Blacklist ProfileSpecifies the name of the Dynamic Blacklist Profile.

Emergency Call Handling Mode

Use this parameter to specify how to handle emergency calls.

  • emergencyRegRequired – Use this option to reject the emergency session establishment without an emergency registration.

    “Use Psx Route For Emergency Call” must also be enabled to use this option.

  • emergencyRegSupported – Use this option when emergency registrations are supported, but emergency session establishment is possible without an emergency registration.

    “Use Psx Route For Emergency Call” must also be enabled to use this option.

  • none (default) – Use this option when not using emergency registrations to perform PSX dip for registered user for emergency calls.

    “Use Psx Route For Emergency Call” must also be enabled to use this option.

  • rejectWith380 – Use this option to reject an INVITE request with ‘380 Alternate Service’ response code from Ingress leg when the request is identified as emergency request and redirection flag is set to redirection mode.

See Emergency Registration for emergency registration functionality.

JSRC Bandwidth Reservation

If disabled at global level, the Trunk Group configuration will not be applied. The options are:

  • Disabled (default)
  • Enabled

Remote EPreservation

If disabled at global level, the Trunk Group configuration will not be applied. The options are:

  • Disabled (default)
  • Enabled

SIP JIP Profile

Specifies the name of the Sip Jip Profile.

This parameter is only supported when the SBC is configured to use an external PSX.

SIP Jurisdiction Support

Enable this flag to allow insertion of JIP parameter in SIP trunk group ingress and egress headers.

  • Disabled (default)
  • Enabled

This flag is only supported when the SBC is configured to use an external PSX.


Transparency ProfileSpecifies the name of the Transparency Profile to associate with this SIP Trunk Group.
SIP Param Filter ProfileSpecifies 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.

  • Disabled (default)
  • Enabled
Hpc Call Profile

Specifies the name (1-23 characters) of the HPC Call Profile. The possible states are:

  • Disabled (default)
  • Enabled
Dialog Event Notification Supported

Use this flag to support notification for a SUBSCRIBE with dialog event in this Trunk Group.

  • Disabled (default)
  • Enabled

Note

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.

  • Disabled (default)
  • Enabled

 

Note

This configuration is not supported on ERE and is intended for use only with an external PSX.


Test Call Number Profile

<profile name> – The name (1-23 characters) of the 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: