Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_docset_workflow
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85b00e8, userName='null'}
DEV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c87a0103, userName='null'}
LDEV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ccf70901, userName='null'}
SVT1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c90601df, userName='null'}
LSVT1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7cd0042, userName='null'}

Panel

In this section:

Table of Contents
maxLevel4

Info
iconfalse

Related articles:

Overview

The

Spacevars
0product
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. 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.

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

Anchor
Signaling Interface
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 Static Routes Currently Configured for an ENUM Server [optional]

    Code Block
    % show addressContext default staticRoute

    Sample Output for IPV4

    Code Block
    staticRoute 10.54.78.21 32 10.54.24.1 LIG001 LIF1_v4 {
preference 100;
}

    Sample Output for IPV6

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

  2. Adding a Static Route for an ENUM Server

    Note
    iconfalse
    titleNote:

    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
    languagenone
     % set addressContext default staticRoute 10.128.254.116 32 10.54.4.1 LIG001 LIF1_v4 preference 120
commit

    For 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. Setting lwresdProfile to ip

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

  4. Viewing the lwresdProfile [optional]

    Code Block
    % show global servers lwresdProfile DEFAULT

    Sample Output

    Code Block
    description                       DEFAULT;
ENUMDomainNameLabel               DEFAULT_ZONE_LABEL;
enableLwresdLog                   disable;
type                              ip;
addressContext                    default;
ipInterfaceGroup                  LIG001;
    Note
    iconfalse
    titleNote:

    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.

  5. Adding an ACL Rule

    For 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

    For IPV6

    Code Block
    % 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 the Existing Static Routes for an ENUM Server

    Note
    iconfalse
    titleNote:

    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.


    For IPV4

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

    For IPV6

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

  2. Setting lwresdProfile to mgmt

    Code Block
    % set global servers lwresdProfile DEFAULT type mgmt
commit

  3. Viewing the Settings of lwresdProfile [optional]

    Code Block
    % show global servers lwresdProfile DEFAULT

    Sample output:

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

  4. Adding an ACL Rule

    For IPV4

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

    For IPV6

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

Pagebreak