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. Use the SIP trunk group Services window to edit parameters associated with various enhanced services and features for a selected SIP trunk group. On the SBC main screen, follow one of these paths: The Services window is displayed. For the trunk group you want to edit, use the drop-down boxes to select the appropriate address context, zone, and SIP trunk group name. The Edit Services window is displayed for the selected trunk group. Use the following table to configure the options and then click Save. SIP Trunk Group - Services Parameters 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 NOTE: During an ingress precondition interworking scenario, if the remote precondition is met in PRACK, the SBC processes it and sends the INVITE towards the egress. Transmit Preconditions 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. Note: Do not enable Precondition Intwk Using183 when End-to-End Prack is configured. NOTE: Enable this flag to prevent the SBC from incrementing the redirection counter and from updating the redirection information (RDI) parameter. The RDI counter value and RDI parameter could be used to update the (diversion headers or ISUP IAM MIME content) in the subsequent SIP INVITE for the SBX or GSX, or it could also be used to update the ISUP IAM parameter if the call gets redirected over the GSX. The options include: Enable this flag to prevent the SBX from generating a call forward progress (CPG) message towards the ingress side of the call. This could be mapped to an ISUP CPG on the GSX ISUP trunk or a 183 message if the ingress side is SIP. The options include: 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. 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 SIP Security Profile 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. See Emergency Registration for emergency registration functionality. Remote EPreservation If disabled at the global level, the Trunk Group configuration will not be applied. The options are: 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. Enable this option to latch on Previous Learned IP Address before performing SRV DNS Lookups, while sending mid-dialog SIP requests. Specifies the name (1-23 characters) of the HPC Call Profile. The possible states are: Use this flag to support notification for a SUBSCRIBE with dialog event in this Trunk Group. The ERE is not supported for this configuration. You must use an external PSX. Use this flag to support co-locating P-CSCF and E-CSCF on the ingress Trunk Group. The ERE is not supported for this configuration. You must use an external PSX. 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. If enabled, the SBC always sends a Naming Authority Pointer (NAPTR) query when an FQDN needs to be resolved. 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. Use the SIP Notruf Profile to enable the SIP Notruf feature. Notruf uses Ribbon SBC call processing to collect information from the caller. Set the value of this parameter (0-50) to control the maximum number of egress routing attempts. Set on ingress TG, this parameter is a TG level configuration that restricts the maximum number of egress routing attempts for calls arriving on the ingress TG. This parameter can have a value from 0 to 50, with 0 allowing an unlimited number of egress routing attempts. You must use this parameter in conjunction with the Egress IP Signaling Profile control "Force Requery For Redirection". For more details, refer to Redirect - Flags. The SBC stores the base64 decoded Identity headers received and sent in the SIP INVITE message. Use this flag to specify the Identity headers to store in the CDR record. You can specify all the identity headers in the list to store them in the CDR, or choose the ones you require. However, if you select 'none' and another option, for example 'shaken', 'none' takes precedence and no identity headers are stored in the CDR. Similarly, if you select 'all' and another identity header, for example 'shaken'. The choice 'all' takes precedence and all the identity headers in the list are stored in the CDR. When more than one SHAKEN header arrives in the Ingress INVITE, then the following is the order of precedence in which the Identity header is picked: Send Refer Transferor Number To PSX Use this parameter to send the transferor party number to the PSX. Modified: for 12.1.2
IMPORTANT
To View and Edit Services Parameters
Indicates level of preconditions support for incoming (only) requests. For precondition support of outgoing requests, see Transmit Preconditions below.Specifies the level of preconditions support for outgoing requests/responses. 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.preConditionIntwkUsing183 when End-to-End Prack is configured.No RDIUpdate On3xx Block Progress on 3XXResponse Honor Sdp Clock Rate 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. 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.
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 Hpc Call Profile Dialog Event Notification Supported
Note
Colocated Pand Ecscf
Note
Test Call Number Profile Retry Profile The name of the SIP Retry Profile for configuring SRTP to RTP fallback behavior. Refer to Services - Retry Profile. DNS Naptr Always 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 SIP Notruf Profile Max Route Attempts
Note
Store Identity Hdrto CDR
Note
The values are a comma-separated list of categories. The priority order for writing in the CDR from the highest to the lowest is, SHAKEN, RPH, RCD, DIVs and OTHER. A maximum of nine identity headers are logged in the CDR for ingress and egress. If the higher priority headers take up all the space, then the lower priority headers are not written in the CDR.
Overview
Content Tools