Servers - CLI

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

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