3.2 MMI Managed Objects for ENUM Support

MMI information associated with ENUM can be configured from a DSR NOAM or SOAM from Main Menu, and then MMI API Guide.

Once the MMI API Guide gets opened, use the application navigation to locate specific ENUM managed object information.

The following table lists the managed objects and operations supported for ENUM:

Managed Object Name	Supported Actions
Enum ACLs	POST, DELETE
Enum Options	PUT

Enum ACLs

The Enum ACLs MO supports the following parameters:

Table 3-1 Enum ACLs Parameters

Parameter Name	Description
ipAddress	IPv4 or IPv6 addresses which are to be allowed or blocked for ENUM feature. Valid entries are valid IPv6 and IPv4 addresses.
prefix	Specifies number of bits in netmask. Allowed values are: 1-31 for IPv4 32,40,48,56,64 or 96 for IPv6
filter	Specifies whether the configured IP is to be allowed or blocked. Blocked filter takes precedence over Allowed, if an IP falls in both ranges.

Example- Insert

Create a file with following content to set values of the parameters. File name could be anything, for example option name can be used as filename:

{
"filter": "BLOCKED",
"ipAddress": "10.75.219.180",
"prefix": "24"
}

Execute the following command on Active SOAM to insert the data:

/venum/enumacls/ -v POST –r <filename>.json

Execute the following command to display the content:

venum/enumacls
{
"filter": "BLOCKED",
"ipAddress": "10.75.219.180",
"prefix": "24"
}

Enum Options

The Enum Options MO supports the following parameters:

Table 3-2 Enum Options Parameters

Parameter Name	Description
congestionNotification	Congestion Notification Flag for response, valid values are Yes, No
congestionResCode	RCODE values in ENUM error response message to be sent due to congestion on ENUM application. Range [5,15] Default: 5
maxDnDigits	Max number of DN digits from an incoming ENUM query. Range [8,15] Default: 15
defaultProfileType	It identifies the profile used to generate the ENUM response for each resource record type.
defaultNaptrSrvc	Service parameter. This parameter specifies the supported ENUM services. This parameter is only valid for NAPTR response type.
defaultNSDomain	This parameter specifies the domain name of the name server in the NS record. This parameter is only valid for the NS response type.
defaultNaptrFlag	A containing flags to control aspects of the rewriting and interpretation of the fields in the record. This parameter is only valid for NAPTR response type.
defaultNaptrRegex	NAPTR Regex Response. This parameter is only valid for NAPTR response type.

Example- Update

Create a file with following content to set values of the parameters. File name could be anything, for example option name can be used as filename:

{
            "addRnContext": "No",
            "congestionNotification": "No",
            "congestionResCode": 5,
            "defaultNSDomain": "abc2.com",
            "defaultNaptrFlag": "U",
            "defaultNaptrRegex": "!^.*$!sip:[e-mail]!",
            "defaultNaptrSrvc": "SIP",
            "defaultProfileType": "NAPTR",
	     "maxDnDigits": 15
        }

Execute the following command on Active SOAM to insert the data:

/venum/enumoptions -v PUT –r <filename>.json

Execute the following command to display the content:

venum/enumoptions{
            "addRnContext": "No",
            "congestionNotification": "No",
            "congestionResCode": 5,
            "defaultNSDomain": "abc2.com",
            "defaultNaptrFlag": "U",
            "defaultNaptrRegex": "!^.*$!sip:[e-mail]!",
            "defaultNaptrSrvc": "SIP",
            "defaultProfileType": "NAPTR",
	      "maxDnDigits": 15
        }