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. |
Preconditions | Indicates level of preconditions support for incoming (only) requests. For precondition support of outgoing requests, see Transmit Preconditions below. - None – (default)
- Required
- Supported
- Transparent
| Multiexcerpt include |
|---|
| MultiExcerptName | preconditions Notes |
|---|
| PageWithExcerpt | Reserving Network Resources |
|---|
|
|
Transmit Preconditions | Specifies the level of preconditions support for outgoing requests/responses.- 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
Note: Do not enable Precondition Intwk Using183 when End-to-End Prack is configured. | Multiexcerpt include |
|---|
| MultiExcerptName | preconditionIntwkUsing183 Notes |
|---|
| PageWithExcerpt | Reserving Network Resources |
|---|
|
|
| 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 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. |
| Hplmn Profile | Specifies the name of an HPLMN Profile to use in handling emergency calls from outbound roaming users when S8 Home Routing (S8HR) is in use. Refer to Emergency Call Handling for the Roaming Users in S8HR Model. |
| Vplmn Profile | Specifies the name of a VPLMN Profile to use in handling emergency calls from outbound roaming users when S8 Home Routing (S8HR) is in use. Refer to Emergency Call Handling for the Roaming Users in S8HR Model. |
Sip SIP Security Profile | Specifies the name of the SIP Security Profile. |
| Dynamic Blacklist Profile | Specifies the name of the Dynamic Blacklist Profile. |
| Enhanced DBL Profile | Specifies the name of the enhanced dynamic blacklist (DBL) profile for the SIP trunk group. Refer to Services - Enhanced DBL Profile for more information. |
Emergency Call Handling Mode | Use this parameter to specify how to handle emergency calls. Note: To use any of the first three options, Use Psx Route For Emergency Call must also be enabled. Emergency Reg Required – Use this option to reject the emergency session establishment without an emergency registration. Emergency Reg Supported – Use this option when emergency registrations are supported, but emergency session establishment is possible without an emergency registration. None (default) – Use this option when not using emergency registrations to perform PSX dip for registered user for emergency calls. - Reject With 380 – 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 the global level, the Trunk Group configuration will not be applied. The options are: - Disabled (default)
- Enabled
|
Remote EPreservation | If disabled at the 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. defaultJipProfile is the name of the default SIP JIP profile assigned to SIP trunk groups. You can select the name of a custom profile you created. Refer to Service Profiles - SIP JIP Profile. Note: This parameter is only supported when the SBC is configured to use an external PSX. |
SIP Jurisdiction Support | Enable this flag to allow sending JIP information in SIP-SIP, SIP-SIP-I and SIP-I to SIP scenarios. - Disabled (default)
- Enabled
Note: This parameter 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 Rec Metadata Profile | Specifies the name of a SIP Rec Metadata Profile to associate with the SIP Trunk Group. This type of profile should be assigned to the SIP Trunk Group for the SIP Session Recording Server. Refer to Services - SIP Rec Metadata Profile for more information. |
| SIP Call Notification Metadata Profile | Specifies the name of a SIPREC metadata profile that defines the mapping of a SIP header to the Session-Id XML element in NOTIFY messages. This parameter should be set on the trunk group used to send call notifications. Refer to Sending Unsolicited Call Notifications to Application Servers for more information on the SBC's call notification feature. Refer to Services - SIP Rec Metadata Profile for information on these profiles. |
| 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 option 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
|
| Colocated Pand Ecscf | Use this flag to support co-locating P-CSCF and E-CSCF on the ingress Trunk Group. - Disabled (default)
- Enabled
|
| Test Call Number Profile | The name (1-23 characters) of the Test Call Number Profile. The uses the Test Call Number Profile to verify PSX test data access. The uses this profile to determine whether to send a PSX query to a test PSX or to the production PSX. When the receives a call from one of the configured numbers in the Test Call Number Profile, the sends the PSX query to the test PSX, if available. When the receives a call from a number not included in the Test Call Number Profile, the sends the PSX query to the production PSX. |
| Retry Profile | The name of the SIP Retry Profile for configuring SRTP to RTP fallback behavior. Refer to Services - Retry Profile (SRF). |
| DNS Naptr Always | If enabled, NAPTR Query is always sent for the the SBC always sends a Naming Authority Pointer (NAPTR) query when an FQDN needs to resolvebe resolved. - Disabled (default)
- Enabled
|
| Privacy Profile | Select the name of Privacy Profile to apply to the SIP trunk group. Refer to Services - Privacy Profile for information. |
| Sti Profile | Select a Secure Telephone Identify (Sti) Profile to apply to the SIP trunk group. Refer to Services - Sti Profile for information. |
| SIP Adaptive Transparency Profile | The name of the SIP Adaptive Transparency Profile. Note: The SBC gives precedence to SIP Privacy handling when the SIP Adaptive Transparency Profile is enabled. For example, if the incoming SIP message has "privacy: Id" and the flag Apply Privacy Id under Profiles > Services > Privacy Profile is enabled, the SBC does not include a P-ASSERTED-ID header in the egress message. For information on SIP Adaptive Transparency Profiles, refer to Services - SIP Adaptive Transparency Profile. |