In this section:


The global servers object allows you to configure ENUM and E911 servers as well as global DNS, call recording criteria and SRS Group Profile configurations. The 'servers' object includes global configurations for DNS servers used for SIP NAPTR, SRV, and A-record lookups.

When the ERE receives multiple records with the same order value and preference for a NAPTR query, the ERE considers only the first record received to resolve the route. If it does not find a route for the chosen record, it returns a 'no route found' response, and will not consider other records to resolve the route.

However, in the case where the order value and preference are different for the received records, the record chosen to resolve the route is based on the RFC rule. In this scenario, if the ERE/PSX does not find the route for the chosen record, it returns a 'no route found' response, and will not consider other records to resolve the route. 

The ENUM server returns a NAPTR response with an IP address to the SBC. To route a call to the IP Peer associated with this IP address, ensure the following is provisioned in ERE.

  1. Configure a SIP Domain with the IP address of the IP Peer.
  2. Create an IP Peer using the IP address above, and associate this IP peer to a routing label.
  3. Configure a Username Routing entry using SIP Domain from step 1, and attach the routing label created in step 2.

The SBC supports load balancing across ENUM servers for individual ENUM zones using enumDomainName, lwresdProfile and enumDomainNameLabel parameters described in this section. ENUM client routes the query to ENUM servers based on the load balancing scheme configured for that zone. ENUM client uses the following load balancing schemes to route the requests to ENUM servers. For details, refer to ENUM Support.

  • Sequential
  • Round Robin
  • Proportional

Global DNS Servers

High Level Command Syntax

% set global servers
	adService 
	callRecordingCriteria
	dmpmRuleService <DM/PM Rule Service name>
		criteria triggerCriteria <???>
		flags active <disable | enable>
		priority <???>
		translationOrder <callingNumber | calledNumber | calledAndCalling | callingAndCalled>
	dns
	domainController <server name> 
		description <description> 
		ldapQueryCriteria <criteria>
		password <password>
		userName <username> 
		primaryIP <x.x.x.x>
		remote port (remote port>
		searchScope <search scope>
		secondary IP <x.x.x.x>
		useTLS <enable | disable>
		userName <username>
	e911 
	e911VpcDevice <device_name>
	enumDomainName <domain_name>
	enumDomainNameLabel DEFAULT_ZONE_LABEL 
		enumDomainNameId <enumDomainName's name>
	enumMessageDefinition
	enumService <name>
	lwresdProfile <profile name>
	srsGroupCluster
	srsGroupProfile

Command Parameters

Global Servers Parameters

Parameter

Length/Range

Description

adService1-23AD Service name used for AD service trigger. This is a mandatory parameter.
callRecordingCriteria0-23Unique Call Recording Criteria name.
dmpmRuleServiceN/A

<DM/PM Rule Service name> – Use this object to enable/disable a new DMPM service, which will execute DM/PM rules to normalize the usernames in the ingress INVITE to E.164.

  • criteria – ???
  • priority <???> – 
  • flags active – Choose to enable/disable this service. 
    • disable <default???>
    • enable
  • translationOrder – Specify a translation order for this DM/PM Rule Service. <is there a default???>
    • callingNumber
    • calledNumber
    • calledAndCalling
    • callingAndCalled

NOTE: Enable the "continueDmPmService" flag (go to Feature Control Profile - CLI) if you want PES to process the DM/PM Rule Service for a Feature Control Profile even if the route is determined prior to the PreRouter Layer.

Modified: for 9.2.3

dns

N/A

Use this object to configure global DNS settings. (Refer to Servers - DNS Global - CLI for parameter details)

domainController1 - 23

Name of the AD Domain Controller server. Complete the Domain Controller configuration to fetch the data from the remote server. The domainController entity holds data related to the remote Active Directory Server.

description- Optional description of the AD Domain Controller

ldapQueryCriteria-LDAP ((Lightweight Directory Access Protocol) query to retrieve data from the AD Domain Controller

password- Password to access the AD Domain Controller

primaryIP- Primary IP address of the AD Domain Controller

remotePort- Port on the remote AD Domain Controller server (optional).

searchScope- Scope of the AD search when retrieving data

secondaryIP- Secondary IP address of the AD Domain Controller

useTLS- If enabled, the SBC uses TLS to communicate with the AD Domain Controller. Options are:

  • disable (default)
  • enable

userName – Username to access the AD Domain Controller

e911

N/A

Use this parameter to configure enhanced 911 service. (Refer to Servers - E911 - CLI for parameter details)

e911VpcDevice

N/A

Use this object to configure the IP address and port number of the E911 VoIP Positioning Center (VPC) device. This parameter is used  for queries to one or more E911 VPCs for the Emergency Services Routing Number of the Public Services Answering Point nearest the current location of the caller.

(Refer to Servers - E911 - CLI for parameter details)

enumARSProfile 1-23Use this object to name an ENUM ARS profile.  This profile applies to ENUM servers and specifies behavior for managing device failover to a secondary or backup ENUM server in the form of blacklisting and whitelisting critieria.
enumDomainName 1-63 characters

The name of the ENUM domain containing forwarderIP entries for load balancing.

(Refer to Servers - ENUM - CLI for parameter details)

enumDomainNameLabelN/A

A collection of ENUM domains used by SLWRESD process for performing ENUM queries. The default enumDomainNameLabel value is "DEFAULT_ZONE_LABEL".

(Refer to Servers - ENUM - CLI  for parameter details)

enumMessagedefinitionN/AThis table contains information about Enum Message Definitions.

enumService

1-23 characters

The ENUM Service name.

(Refer to Servers - ENUM - CLI  for parameter details)

lwresdProfileN/A

LWRESD Profile configuration which uses ENUM zones configured for sending ENUM queries against an enumDomainLabel (and receives responses) using either the management or signaling interfaces, depending upon the LWRESD Profile type setting. 

(Refer to Servers - LWRESD Profile - CLI for parameter details)

srsGroupCluster0-23

SRS Group Cluster name. The options are:

  •  SRS Group Cluster Id- Select the name of an SRS Group Profile to associate with the cluster.
  • PER60690s_RECCluster - ClusterForRec
srsGroupProfile0-23

SRS Group Profile name. The options are:

description - Descriptive text about this SRS Group Profile.

loadDistribution - The load distribution scheme for this SRS Group Profile.

          • Round Robin
          • Sequence (default)

numSimultaneousStream- range is 1-2.The number of simultaneous media streams for this SRS Group Profile. (default = 1)

srsGroupData- Data rows for SRS group. The options are:

  • ipAddress - Signaling IP address (IPv4 or IPv6) of this SRS (The values "0.0.0.0" or "0::0" are not allowed).
  • ipPort - TCP/TLS/UDP port for this SRS.
  • ipTGId - IP Trunk Group ID used to initiate the session towards the SRS.

Command Examples

To configure E911 server, execute the following CLI commands:

% set global country 1 listOfNumberOfDigitsToMatch criteria 10,6,3,0  
% commit 
% set profiles digitParameterHandling numberTranslationCriteria DEFAULT_E911 none Sonus_NULL Sonus_NULL 4451211022 1 lookupType e911 
% set global servers e911 DEFAULT_E911 flags active enable 
% set global servers e911VpcDevice DEFAULT_E911 deviceData 0 ipAddress 10.6.30.137 portNumber 9000 
% set global servers e911 DEFAULT_E911 vpcDevice DEFAULT_E911 
% set global servers e911 DEFAULT_E911 criteria triggerCriteria DEFAULT_E911
% set global servers domainController adaserver userName rbbn password ribbon1 searchScope CN=Users,dc=sonusqa,dc=net ldapQueryCriteria cn=* primaryIP 10.50.10.20
 % commit


To configure global ENUM service, execute the following CLI commands:

  1. Configure numberTranslationCriteria for calledUri as below

    % set profiles digitParameterHandling numberTranslationCriteria ENUM_CR calledUri ims.comcast.com Sonus_NULL 9876543210 1 lookupType enumCnam

  2. Provision enumService:

    % set global servers enumService ENUMSER1 criteria triggerCriteria ENUM_CR 
% set global servers enumService ENUMSER1 serviceType cnam flags active enable

  3. Configure the private domain 'ims.comcast.com' for ENUM service.

    % set global servers enumService ENUMSER1 enumDefinitions privateDomainNameForEnumLookups ims.comcast.com


    Configure the ACL rule and management interface static route for the domain controller’s IP. This is to ensure that the management interface is used to send the LDAP query and packets from the AD server are allowed reach the application. The following is an example:

    set global servers domainController adaserver userName rbbn password ribbon1 searchScope CN=Users,dc=sonusqa,dc=net ldapQueryCriteria cn=* primaryIP 10.50.10.20

    The following is an example of how to Create Ad Service and associate trigger criteria:

    set global servers adService ADSERV1 priority 10
set global servers adService ADSERV1  criteria triggerCriteria Test
set global servers adService ADSERV1  flags active enable