Page History

Overview

The

Spacevars
0 product

sends ENUM queries and receive responses, using the Signaling Interface. The user can configure the Signaling Interface for sending ENUM queries and receive responses, using the packet interface port 988 to 1023. The packets from the Signaling Interface are prioritized over the packets from the Management Interface.

Info
The default behavior of the SBC is to use the Management Interface for sending ENUM queries and receiving responses. The ports used for this purpose are in the range of 49152 to 65535.

Info
title Note
The addressContext and ipInterfaceGroup parameters are available when the type is set to ip. The ip interface uses ports 988 to 1023 to send and receive the ENUM queries. The addressContext, zone, sipSigPort, and ipInterfaceGroupName parameters are available when the type is set to signalingIp.

Configure the servers lwresdProfile type with the following options for ENUM queries:

• mgmt: For management interface (default).
• ip: For packet interface.
• signalingIp: For signaling interface using sipSigPort IP address.

Info
title Note
IPv4 and IPv6 IP addresses can be configured for ENUM queries.

The addressContext adds the staticRoute parameter for the ENUM server. Static routes are configured between the ENUM server and the signaling interface in order to provide a gateway to the destination ENUM server.

The SBC uses the Management Interface as default for handling ENUM queries. There are two ways to handle ENUM queries:

• Handling the ENUM Queries Using the Pkt Interface
• Handling the ENUM Queries Using the Management Interface
• Handling the ENUM Queries Using the Signaling Interface

Anchor
Signaling Interface Signaling Interface

Handling the ENUM Queries Using the Pkt Interface

To configure the SBC for sending the ENUM queries and receive responses using the Pkt Interface, perform the following steps:

1. Checking

   Check Static Routes Currently Configured for an ENUM Server [optional].

   Code Block
   % show addressContext default staticRoute

   Sample Output for IPV4

   
   

   code

   Code Block
   title Example: IPv4 output
   staticRoute 10.54.78.21 32 10.54.24.1 LIG001 LIF1_v4 { preference 100; }

   Sample Output for IPV6

   
   

   code

   Code Block
   title Example: IPv6 output
   staticRoute fd00:10:6b50:44e0::15 60 fd00:10:6b50:4180::1 LIG001 LIF1_v4 { preference 100; }

   
   

2. Adding

   Add a Static Route for an ENUM Server.

   Note
   icon false title Note:
   It is not necessary to add a Static Route for an ENUM server, if it is already configured and shown in the output of the command "show addressContext <addressContext_Name> staticRoute". For example, if the ENUM server IP 10.128.254.116 is already added as a static route, then the output of the "show addressContext default staticRoute" command displays the following information: staticRoute 10.128.254.116 32 10.54.4.1 LIG001 LIF1_v4 {     preference 120; }

   For IPV4

   
   

   Code Block
   languagetitle noneFor IPv4
   % set addressContext default staticRoute 10.128.254.116 32 10.54.4.1 LIG001 LIF1_v4 preference 120 commit

   
   

   Code Block
   title For

   IPV6

   IPv6
   Code Block
   % set addressContext DEFAULT staticRoute fd00:10:6b50:44e0::15 60 fd00:10:6b50:4180::1 LIG001 LIF1_v4 preference 177 commit

   
   

3. Configuring

   Configure ENUM Domain Name.

   Code Block
   set global servers enumDomainName somevaliddomain.com forwardersData 0 eDNSType yes commit

   
   

   Code Block
   set global servers enumDomainName somevaliddomain.com forwardersData 0 eDNSBufferSize 517 commit

   
   

4. Setting lwresdProfile to ip

   Set LWRESD Profile type to 'ip.'

   Code Block
   % set global servers lwresdProfile DEFAULT type ip addressContext default ipInterfaceGroup LIG001 commit

   The following is an example of how to set

   
   

   Code Block
   title Example: Setting the eDnsGlobalBufferSize parameter

   .code

   set global servers lwresdProfile DEFAULT eDnsGlobalBufferSize 524 commit

   The following is an example of how to set

   
   

   Code Block
   title Example: Setting the eDnsMonitorInterval parameter

   .

   Code Block
   set global servers lwresdProfile DEFAULT eDnsMonitorInterval 66 commit

   
   

5. Viewing

   View the

   lwresdProfile

   LWRESD [optional].

   Code Block
   % show global servers lwresdProfile DEFAULT

   
   

   Code Block

   Sample Outputcode

   title

   Example

   description DEFAULT; enumDomainNameLabel DEFAULT_ZONE_LABEL; enableLwresdLog disable; type mgmt; eDnsGlobalBufferSize 524; eDnsMonitorInterval 66;

   
   

   Note
   icon false title Note:
   The parameters addressContext and ipInterfaceGroup appears in the results of the command "show global servers lwresdProfile DEFAULT", only if the parameter lwresdProfile type is set to ip.

   
   

6. Adding

   Add an ACL Rule.

   Code Block
   title For

   IPV4

   IPv4
   Code Block
   % set addressContext default ipAccessControlList rule DNS1 precedence 9 ipInterfaceGroup LIG2 ipInterface LIF2_v4 sourceIpAddress 10.128.254.1 sourceAddressPrefixLength 24 state enabled commit

   
   

   Code Block
   title For

   IPV6code

   IPv6

   % set addressContext DEFAULT ipAccessControlList rule DNS1 precedence 11 ipInterfaceGroup LIG001 ipInterface LIF1_v4 sourceIpAddress fd00:10:6b50:4020::99 sourceAddressPrefixLength 60 state enabled commit

   
   

Anchor
Management Interface Management Interface

Handling the ENUM Queries Using the Management Interface

To configure the SBC for sending the ENUM queries and receive responses using the Management Interface, perform the following steps:

1. Deleting

   Delete the Existing Static Routes for an ENUM Server.

   Note
   icon false title Note:
   The SBC selects the interface based on priority of the static route configured for interface. To enable the Management Interface for handling ENUM queries, delete static routes configured for the ENUM server.

   
   

   Code Block
   title For

   IPV4

   IPv4
   Code Block
   % delete addressContext default staticRoute 10.128.254.116 32 10.54.4.1 LIG001 LIF1_v4 commit

   For IPV6

   
   

   code

   Code Block
   title For IPv6
   % delete addressContext default staticRoute fd00:10:6b50:44e0::15 60 fd00:10:6b50:4180::1 LIG001 LIF1_v4 commit

   
   

2. Configuring

   Configure ENUM Domain Name.

   Code Block
   set global servers enumDomainName somevaliddomain.com forwardersData 0 eDNSType yes commit

   
   

   Code Block
   set global servers enumDomainName somevaliddomain.com forwardersData 0 eDNSBufferSize 517 commit

   
   

3. Setting lwresdProfile

   Set LWRESD Profile to 'mgmt.'

   Code Block
   % set global servers lwresdProfile DEFAULT type mgmt commit

   The following is an example of how to set

   
   

   Code Block
   title Example: Setting the eDnsGlobalBufferSize parameter

   .

   Code Block
   set global servers lwresdProfile DEFAULT eDnsGlobalBufferSize 524 commit

   The following is an example of how to set

   
   

   Code Block
   title Example: Setting the eDnsMonitorInterval parameter

   .code

   set global servers lwresdProfile DEFAULT eDnsMonitorInterval 66 commit

   
   

4. Viewing

   View the Settings of lwresdProfile [optional].

   Code Block
   % show global servers lwresdProfile DEFAULT

   
   

   Code Block
   title

   Sample

   Example output

   :code

   description DEFAULT; ENUMDomainNameLabel DEFAULT_ZONE_LABEL; enableLwresdLog disable; type mgmt;

   
   

5. Adding

   Add an ACL Rule.

   For IPV4

   code

   Code Block
   title For IPv4
   % set addressContext default ipAccessControlList rule DNS1 precedence 9 sourceIpAddress 10.54.92.180 sourceAddressPrefixLength 24 state enabled commit

   
   

   Code Block
   title For

   IPV6code

   IPv6

   % set addressContext DEFAULT ipAccessControlList rule DNS1 precedence 11 sourceIpAddress fd00:10:6b50:4020::99 sourceAddressPrefixLength 60 state enabled commit

   
   

Anchor
Handling the ENUM Queries Using the Signaling Interface Handling the ENUM Queries Using the Signaling Interface

Handling the ENUM Queries Using the Signaling Interface

To configure the SBC for sending the ENUM queries and receive responses using the Signaling Interface, perform the following steps:

1. Checking

   Check Static Routes Currently Configured for an ENUM Server [optional]

   The following is an example of how to view

   .

   
   

   Code Block
   title Example: Viewing the staticRoute for the ENUM server

   .

   Code Block
   title Example
   show addressContext DEFAULT staticRoute staticRoute 10.54.78.21 32 10.54.24.1 LIG1 LIF1_v4 { preference 100; }

   
   

2. Adding

   Add a Static Route for an ENUM Server.

   The following is an example Example of how to add a staticRoute for the ENUM server.:

   Code Block
   title Example
   set addressContext DEFAULT staticRoute 10.128.254.116 32 10.54.4.1 LIG1 LIF1_v4 preference 120

   
   

3. Configuring

   Configure ENUM Domain Name.

   Code Block
   set global servers enumDomainName somevaliddomain.com forwardersData 0 eDNSType yes commit

   
   

   Code Block
   set global servers enumDomainName somevaliddomain.com forwardersData 0 eDNSBufferSize 517 commit

   
   

4. Setting lwresdProfile

   Set lwresdProfile to SignalingIp Parameter.The following is an example

• • Example of how to set and configure the signalingIp parameter

.

• • :

    Code Block
    set global servers lwresdProfile DEFAULT type signalingIp addressContext ADDR_CONTEXT_1 zone ZONE_IAD sipSigPort 1 ipInterfaceGroup LIG1

The following is an example

• • 
    

  • Example of how to set the eDnsGlobalBufferSize parameter

.

• • :

    Code Block
    set global servers lwresdProfile DEFAULT eDnsGlobalBufferSize 524 commit

The following is an example

• • 
    

  • Example of how to set the eDnsMonitorInterval parameter

.

• • :

    Code Block
    set global servers lwresdProfile DEFAULT eDnsMonitorInterval 66 commit

    
    

ENUM ARS Profile

The Address Reachability Service (ARS) profile applies to ENUM servers when attached to the LWRESD profile, and provides device failover to the secondary or backup server. The servers lwresdProfile configuration adds the enumArsProfileId parameter.

The ENUM ARS profile is applicable to the following interfaces to handle the ENUM queries:

• mgmt: For management interface (default).
• ip: For packet interface.
• signalingIp: For signaling interface using sipSigPort IP address.

Configure the enumArsProfileId in the enumArsProfile parameter, which is added to the global servers configuration and determines the behavior of the blacklisting and whitelisting parameters.

To check if an ENUM server is reachable or not, you must whitelist or blacklist the ENUM ARS Profile.
The following is an example of how

• Example: How to attach the enumArsProfileId to the lwresdProfile

.

• :

  Code Block
  title Example
  set global servers lwresdProfile DEFAULT enumArsProfileId Test

The following is an example of how

• 
  

• Example: How to configure the enumArsProfile for black listing

.

• :

  Code Block
  title Example
  set global servers enumArsProfile Test blackListing numberOfFailures 5 duration 60

The following is an example of how

• 
  

• Example: How to configure the enumArsProfile for white listing

.

• :

  Code Block
  title Example
  set global servers enumArsProfile Test whiteListing numberOfResponses 1 pingInterval 5 highWaterMarkTimer 86000

 

•