IPWorks DNS, ASDNS, ENUM Parameter Description

Contents

1Introduction
1.1Related Information

2
Basic Concept

3
Object Format
3.1Data Types
3.2Enumerations
3.3Structures
3.3.1AINDigits
3.3.2CarrierFormat
3.3.3gsmSCF

4
Managed Objects
4.1DNS Objects
4.1.1DnsServer
4.1.2View
4.1.3Zones
4.1.4DNS Resource Records
4.1.5ACL
4.1.6TSIGKeys
4.1.7Area
4.1.8DnsContact
4.2ActiveSelect DNS Objects
4.2.1ASDNSSite
4.2.2ASDNSPolicy
4.2.3ASDNSRecord
4.2.4Monitor
4.2.5MonitorMethod
4.2.6MonitorResource
4.2.7MonitorScript
4.3ENUM Objects
4.3.1AINLNPData
4.3.2AINNode
4.3.3AINTollFreeData
4.3.4CountryCode
4.3.5DestNode
4.3.6EnumAcl
4.3.7EnumDnRange
4.3.8EnumDnSched
4.3.9EnumNSRecord
4.3.10EnumServer
4.3.11EnumSOARecord
4.3.12EnumView
4.3.13EnumZone
4.3.14EnumZVRel
4.3.15INAPData
4.3.16INAPNode
4.3.17MAPData
4.3.18MAPNode
4.3.19EnumOperator
4.3.20EnumClientRealm
4.3.21SCCPAddress

Reference List

1   Introduction

This document describes the attributes used by IPWCLI for DNS and ENUM configuration in IPWorks.

Scope

This document covers the following topics:

Target Groups

This document is intended for personnel configuring and fine-tuning the IPWorks. It is assumed that readers of this document are familiar with basic concepts and operations of IPWCLI. For more information, refer to Command Line Interface User Guide for IPWorks SS.

1.1   Related Information

Trademark information, typographic conventions, definition, and explanation of acronyms and terminology can be found in the following documents:

2   Basic Concept

This section describes the following:

The MOM presents a view of manageable resources in IPWorks, as well as attributes and actions associated with these resources.

An MO is an entity presented to the user for controlling the aspects of a function. The object carries attributes that reflect the behavior of the function.

The MOs are identified by a naming attribute, also called the Relative Distinguished Name (RDN). The ID part of this attribute is defined when the MO is created, and cannot be changed afterwards. A Local Distinguished Name (LDN) is a sequence of RDNs, which forms a unique name within the node.

3   Object Format

This section describes the format used to display information about objects.

Key The key is an identifier of an object. The combination of the key field values must be unique for an object.
Required The required field indicates that the field must be configured, otherwise the CLI generates an error.
Note:  
If the field Partition is required, unless the user wants to work within a different partition, the partition being worked on does not need to be specified. IPWorks assumes the active partition always. For more information, see the Partition section of IPWorks Configuration Management.

3.1   Data Types

Address An IPv4 address (in dotted decimal notation) or an IPv6 address. An IPv6 address can be specified using the standard abbreviated forms, but the address is stored in its fully expanded form.
BindTimeValue A numeric value that represents the number of seconds. Operators can enter this value as a numeric value, or use a shorthand notation for specifying times. The basic format is #w#d#h#m#s, where w (or W) is preceded by the number of weeks, d (or D) by number of days, and so on. A number without units is accepted as the time interval in seconds.
Blob A large text string. The theoretic maximum size of this data type is 2 GB.
BooleanTrueFalse A Boolean value that is either true or false. Operators can enter yes/no or 1/0 and they are converted to true/false as appropriate.
DnsName A domain name with maximum length not exceeding 128 characters.
DnsOption A DNS configuration option, where each option setting is in the form "option value [value...]". The option and subsequent value are separated by a single space. The "option" is specified by the option tag.
Int16 A 16-bit unsigned integer value, between -32768 and 32767.
IPv4Address An IPv4 address in dotted decimal notation.
IPv6Address An IPv6 address, which can be specified using the standard abbreviated forms, but the address is stored in the fully expanded form.
MailboxDnsName A dnsname in the email address format.
Name The name of the object.
SRVDnsName A dnsname that defines the symbolic service name prepended with a '_' (underscore).
UInt8 An 8-bit unsigned integer value, from 0 through 255.
UInt16 A 16-bit unsigned integer value, from 0 through 65535.
UInt32 A 32-bit unsigned integer value.
ZoneId A string that is a unique identifier for a zone managed by IPWorks. The id consists of the name of the server, followed by a colon (:), followed by the name of the view that contains the zone, followed by a colon (:) followed by the DNS name for the zone. This combination of 3 values is unique for each IPWorks managed zone.

3.2   Enumerations

AlgMode Load, Status, Prefix-match
FixedZoneType Hint, Loopback, Localhost, SDB
MasterZoneType File, Database
MonitorType Load, Status
RrClass IN, Hesiod, Chaos, HS
RrType ANY, A, A6, AAAA, AFSDB, ATMA, CNAME, DNAME, EID, GPOS, HINFO, ISDN, KEY, KX, LOC, MB, MD, MF, MG, MINFO, MR, MX, NAPTR, NIMLOC, NS, NSAP, NSAPPTR, NULL, NXT, PTR, PX, RP, RT, SIG, SOA, SRV, TXT, WKS, X25
RrTypeAsdns A, AAAA
RrTypeGenRecord A, AAAA, CNAME, DNAME, NS, PTR
ServParaValue E2U+pstn:tel, E2U+pstn:sip
View All existing views stored in the database
ZoneType Master, Slave, Stub, Forward

3.3   Structures

3.3.1   AINDigits

The AINDigits structure has the element types, as shown in the following table:

Table 1    Element Types of AINDigits

Element Type

Value

Nature of Number

The range is 1, 2, 3, 113, 114, 115, 116, 117, 118, 119. Refer to GR-1299-Core for the meaning of each number.

Numbering Plan

  • 1: ISDN numbering plan

  • 5: private

Presentation restriction indicator

  • 0: presentation allowed

  • 1: presentation restricted (default)

  • 2: number unavailable

Screening indicator

  • 0: no screening

  • 1: passing network screening

  • 2: fail network screening

  • 3: network provided

Digits

Each digit is represented by 4 bits. The range of every digit is 0~9.

The inputting format via CLI is:

AINDigits=nn:xxx:np:x:pres:x:scr:x:dig:xxxxx...

Where:

3.3.2   CarrierFormat

According to GR, the data structure of carrier parameters is CarrierFormat which is composed of Carrier Selection and Carrier ID. The Carrier ID is composed of Nature of Carrier, Number of Digits and Digits. The Number of Digits is automatically calculated and does not need to be specified by the user. The following inputting format is used:

Carrier=cs:x:nc:x:dig:xxxx

Where:

3.3.3   gsmSCF

The gsmSCF structure has the element types, as shown in the following table:

Table 2    Element Types of gsmSCF

Element Type

Value

Nature of Number

  • 0: Unknown

  • 1: International number

  • 2: National number

  • 3: Network-specific number

  • 4: Short number

Numbering Plan

  • 0: Unknown

  • 1: ISDN/telephone numbering plan (E.164/E.163)

  • 3: Data numbering plan (X.121)

  • 4: Telex numbering plan

  • 8: National numbering plan

  • 9: Private numbering plan

  • 15: Reserved for extension

Address

An address consists of 1 to 18 digits represented by 4 bits each. The valid values for each digit are 0~9, a, b, c, * and #.

The inputting format via CLI is:

GsmSCFAddress=tn:x:np:xx:dig:xxxxx...

Where:

4   Managed Objects

For the IMS solution, the following four records are configured.

A Record An A record maps a hostname into 32-bit IPv4 address.
SRV Record An SRV record, or service record, is defined in RFC 2782. This type of record is a category of data in DNS specifying information on available services.
NAPTR Record An NAPTR record, or Naming Authority Pointer record, is relatively new type of DNS record that supports regular expression based rewriting. NAPTR records could be organized in groups, creating sophisticated URI rewriting rules. There are terminal and non-terminal NAPTR records. This type of record is described in details in RFC 3403.
EnumDNSched Record EnumDNSched Record, or telephone number mapping - IETF have defined a mechanism for converting an e.164 number into an URI, which could be used in IP network environment.

4.1   DNS Objects

This section describes the DNS objects and their fields.

4.1.1   DnsServer

A DnsServer object represents a DNS Server that is running on the network.

Key Partition, Name
Required Partition, Name

4.1.2   View

The View object is used for supporting multiple (different) definitions of a zone within DNS. In some cases of DNS configuration, there is no need to use any views. The classic reason for using views in the DNS configuration is to implement Split DNS (having a zone with different internal and external definitions).

Key Partition, Server, Name
Required Partition, Server, Name

4.1.3   Zones

4.1.3.1   MasterZone

A MasterZone is an object defined within a server which is considered as the master (or primary) authority for the zone.

Key Partition, Server, View, Name
Required $keys

4.1.3.2   SlaveZone

A SlaveZone is a replica of a MasterZone. The master list specifies one or more IP addresses of master servers that the slave contacts to update its copy of the zone.

Key Partition, Server, View, Name
Required $keys, Source

4.1.3.3   FixedZone

A fixed zone represents a special zone whose contents are not directly managed by IPWorks. A fixed zone can be associated with more than one server, or with more than one view within a server. One of the key characteristics of the fixed zone is that its contents are the same for ALL servers.

Key Partition, Name
Required Partition, Name
Note:  
If fixed zones are not associated with the DNS Server, MasterZone objects for the zones that are commonly implemented as fixed zones can be created, such as the localhost or loopback zones.

4.1.3.4   HintZone

A HintZone object defines the location of the root dns servers that this server should use for queries that it cannot resolve.

Key Partition, Name
Required $keys

4.1.3.5   LocalhostZone

An object that defines the standard forward lookup interface for the localhost name (normally 127.0.0.1 for IPv4). IPWorks includes a standard definition for this zone (called localhost) for both IPv4 and IPv6.

Key Partition, Name
Required $keys

4.1.3.6   LoopbackZone

An object that defines the reverse lookup interfaces for the loopback address (127.0.0.1 in DHCPv4). IPWorks includes standard definitions for both IPv4 (called loopback) and IPv6 (called v6loopback).

Key Partition, Name
Required $keys

4.1.3.7   ForwardZone

A forward zone can be used in a server to designate that any queries for a specific zone should be forwarded to another server or set of servers.

Key Partition, Server, View, Name
Required $keys

4.1.3.8   StubZone

An object that is similar to a SlaveZone, except that it replicates only the NSRecords and SOARecords of a master zone instead of the entire zone. StubZones are not a standard part of the DNS; they are a feature specific to the BIND implementation.

Key Partition, Server, View, Name
Required $keys, Source

4.1.4   DNS Resource Records

4.1.4.1   ARecord

ARecords are used in the DNS to define an address binding for a dnsname. For a given dnsname, it is possible to have multiple ARecords if the dnsname in question has multiple address bindings.

Key Partition, Container, DnsName, Address
Required Partition, Container, DnsName, Address

4.1.4.2   AAAARecord

AAAARecords are used to define an IPv6 address binding for a dnsname.

Key Partition, Container, DnsName, Address
Required $keys

4.1.4.3   CNAMERecord

CNAMERecords are used in the reference on DNS to define a canonical name for a dnsname.

Key Partition, Container, DnsName
Required Partition, Container, DnsName, CName

4.1.4.4   HINFORecord

HINFO records are used to acquire general information about a host.

Key Partition, Container, DnsName, Cputype, Opsys
Required Partition, Container, DnsName, Cputype, Opsys

4.1.4.5   MXRecord

A MXRecord is a resource record for a DNS name. They define the "mail exchanger" (a system that handles mail) for the specified domain.

Key Partition, Container, DnsName, Preference, Exchange
Required $keys

4.1.4.6   NAPTRRecord

NAPTRRecord is a resource record that defines a Naming Authority Pointer for a DNS name, as defined in RFC 2915

Key Partition, Container, DnsName, Order, Preference
Required $keys, Replacement

4.1.4.7   NSRecord

The NS resource record states that the named host should be expected to be an authoritative server for the zone starting at the specified 'owner' DNS name.

Key Partition, Container, DnsName, NameServer
Required $keys

4.1.4.8   SOARecord

SOARecords are used within DNS to define the relationships between different servers for each of the zones that they manage.

Key Partition, Container, DnsName, NameServer
Required Partition, Container, DnsName, NameServer

4.1.4.9   PTRRecord

The PTR resource record(s) for a DNS name. These resource records are used in special domains (such as the INADDR.ARPA domain) to point to some other location in the domain space.

Although PTRRecords are not required by the DNS protocol, they are desirable because they are still widely used. IPWorks provides mechanisms that can be used to configure policies for automatic creation of PTRRecords in the data. These mechanisms are discussed in this section, however it is assumed that the purpose of PTRRecords is understood. If not, refer to an external reference on the DNS for more information.

In some sites, a PTRRecord is created for each ARecord that exists. In others sites PTRRecords are never created. In some it is determined on a per-instance basis. The goal of IPWorks is to support whatever policy an administrator feels is best for their network.

IPWorks never automatically creates a PTRRecord if there is no zone that could contain the record. Therefore, the first thing is to automate the creation of PTRRecords in any situation, that is, the zones must be defined by the user.

The other thing to keep in mind when defining polices for creating PTRRecords is the default product behavior. In many sites, the default behavior may be just what is desired.

  1. When an ARecord or AAAARecord is created, the data that would be used to create an associated PTRRecord is calculated. If the resulting dnsname for the PTRRecord is not contained in any managed zone, no attempt is made to create a PTRRecord.
  2. If the dnsname for the PTRRecord does fall within a managed zone, the default behavior is to ask the user if a PTRRecord should be created using this data.

The following are strategies that can be used to manage PTRRecords.

Key Partition, Container, DnsName, PtrName
Required Partition, Container, DnsName, PtrName

4.1.4.10   GenRecord

The GenRecord object is used to define resource records that are generated in a zone when it is loaded by the DNS server. The generated records are not managed by IPWorks, but rather they are created dynamically in the DNS server.

Key Partition, Area, Start, DnsNameTemplate
Required Partition, Area, Start, End, DnsNameTemplate, Type, RDataTemplate

4.1.4.11   SRVRecord

SRVRecord is a resource record for a DNS name that defines the owner name, where the owner name has the format. <service>.<pronto>. Name.

Key Partition, Container, DnsName, Priority, Weight, Port, Target
Required $keys

4.1.4.12   IncludeRecord

IPWorks supports the $INCLUDE directive. $INCLUDE allows inclusion in-situ of an external file containing additional directives. It is typically used to assist in maintenance of larger DNS files, for example, you can distribute the maintenance of individual zone files to clients without exposing the global parameters or other client zones to inspection. This functionality is based on the $INCLUDE directive supported in BIND 9 and only supports masterzone in IPWorks.

To use this functionality, the IncludeRecord and IncludeFile objects must be created. IncludeRecord is used to define which masterzone uses $INCLUDE directive; IncludeFile is used to define which file in local disk (persistence storage device, such as HD, CD, or SD) is used for included file. Each IncludeFile describes the content of included file and the alias of the file. The relation key between IncludeRecord and IncludeFile is FileAlias. This field in IncludeRecord represents which file masterzone uses.

For more details about IncludeFile, see Section 4.1.4.13. With IncludeRecords, the generated resource records only exist in the DNS Server, which means, they do not exist in the IPWorks database.

There are some additional features that can be used to further customize the inclusion procedure, but they are not discussed here. Online help for the IncludeRecord class may be consulted.

Key Partition, Area, BaseDnsName, FileAlias
Required Partition, Area, BaseDnsName, FileAlias

4.1.4.13   IncludeFile

An IncludeFile object is used to define which file in disk is used for included file.

Key FileAlias
Required FileAlias, LoadFrom

4.1.5   ACL

An ACL is a named access control list, or address match list that is used to specify sets of incoming clients in the configuration options that are used for controlling the server's security.

Key Partition, Name
Required Partition, Name, MatchList

4.1.6   TSIGKeys

A TSIG Key is used for TSIG-based authentication.

Key Partition, Name
Required Partition, Name, Secret

4.1.7   Area

An area is similar to an OSPF area, in that it is a "virtual container" used for organizing some of the managed objects in IPWorks. An area contains all the objects (such as resource records, DNS names, addresses, and policies) that define a namespace and address-space.

Key Partition, Name
Required Partition, Name

4.1.8   DnsContact

A DNS Server contact object defines the information that is necessary to contact a DNS Server. A single server can have multiple contact objects defined for it. It is also possible for a contact object to be defined for a DNS server that is not managed by IPWorks. DnsContacts can be used in the configuration of a DNS Server (when it needs to contact other servers) or in the configuration of a Monitor.

Key Partition, Name
Required Partition, Name, Address

4.2   ActiveSelect DNS Objects

This section describes the ASDNS objects and their fields.

4.2.1   ASDNSSite

An ASDNSsite object is used to define a collection of nodes on the network (based on their addresses) that are configured together with ActiveSelect. The nodes in the network are grouped based on the IP addresses of the nodes and this usually reflects either the geographical or topological layout of the network.

Key Partition, Area, Name
Required Partition, Area, Name

4.2.2   ASDNSPolicy

An ASDNSPolicy object defines a rule for how the DNS Server resolves a query for a domain name that has ActiveSelect enabled. It represents a mapping from one or more source addresses (for a DNS resolver query) to the preferred ActiveSelect sites that should be returned for those addresses. Once the policies are defined, they can be applied to one (or more) domain names by creating ASDNSRecords for those names.

Key Partition, Area, Name
Required Partition, Area, Name, Prefer

4.2.3   ASDNSRecord

An ASDNSRecord object is used to enable ActiveSelect DNS for a particular DNS name and specify the policy that is used to resolve queries for that dnsname.

Key Partition, Area, Type, DnsName
Required Partition, Area, Type, DnsName, Policy

4.2.4   Monitor

A Monitor object represents an ActiveSelect monitor that is running on the network. The ActiveSelect Monitor is used to track the status or load or both the information for systems on the network that are ActiveSelect enabled (these are called monitored resources). The Monitor tracks the status of the resources and reports it to the DNS servers that are authoritative for the resource's dnsnames. Those servers then use this information to apply ActiveSelect rules when resolving queries.

Key Partition, Name
Required Partition, Name

4.2.5   MonitorMethod

A MonitorMethod object defines information about how a MonitorScript is invoked. This includes information, such as which parameters to pass to the script, how they is passed and how often the script run. This is defined as a separate object from the MonitorScript because it allows to use the same script to perform different types of monitoring.

Key Partition, Name
Required Partition, Name, Filename

4.2.6   MonitorResource

A MonitorResource object defines a resource on the network that is monitored by an ActiveSelect Monitor.

Key Partition, Monitor, Name
Required Partition, Monitor, Name, Address, ReportContact, Method

4.2.7   MonitorScript

A MonitorScript object represents the shell script run by a Monitor when it is trying to determine the status or load or both the information for a resource being monitored. IPWorks has two predefined MonitorScripts that can be developed or used.

The two predefined MonitorScripts includes one that uses PING to determine a resource's availability (status); it cannot measure any load information for a resource. The second script uses SNMP and can be used to determine status or load for a resource, if the measure of the load is available as an SNMP statistic.

MonitorScripts can also be customized to monitor a resource. If the script determines that the service is available, it returns an exit status of zero. If the script determines that the service is unavailable, it returns a non-zero exit status and write any error text (describing the failure condition) to standard output (stdout). If there are different types of failure conditions, these are distinguished with different (non-zero) exit status and different error text written to standard output.

If the script is used with monitoring methods to also report load, it must report this load by writing out an integer or floating point number (in ASCII) to standard output (stdout) only if the service is available (exit status of 0). The reported load is compared to the threshold (see the threshold option for the monitor statement, refer to the Configuring MonitorMethods section in Configure DNS and ENUM) to determine whether the service is overloaded or not.

Customized scripts can be written so that it accepts arguments (either on the command line, or by setting environment variables). Different monitoring methods can be used with the same script and each method can be configured to send information to the script.

Note:  
If the mechanism is being used where the MonitorScript is passed the IP address of the system to monitor and the resources are being monitored with IPv6 addresses, it must be ensured that the script can handle the standard IPv6 address formats.

Key Filename
Required Filename

4.3   ENUM Objects

This section describes the ENUM objects that can be configured through IPWorks CLI.

4.3.1   AINLNPData

An AINLNPData object holds configuration data that applies for each ENUM number series to facilitate the AIN event message for LNP and format the response from external legacy database. The object is used in the process of the NP queries and responses.

Key ProtocolSettingName
Required ProtocolSettingName

4.3.2   AINNode

This object holds AIN configuration data to be used by the ENUM server on calling site when generating AIN queries that are to be sent to the external SS7 database.

Key EnumServerId, AINUserId, LocalSSN, LocalSPC
Required EnumServerId, AINUserId, LocalSSN, LocalSPC, BearerCapability, NPSwitch

4.3.3   AINTollFreeData

An AINTollFreeData contains AIN configuration data for each ENUM number series. The object is used in the process of the TollFree queries and responses.

Key ProtocolSettingName
Required ProtocolSettingName, TranslationType, ChargeNumber, ChargepartyStationType, Carrier, Lata (Local Access and Transport Area)

4.3.4   CountryCode

This object holds standard international country codes for transforming international number to national number before ENUM query via external legacy database.

Key ccode
Required ccode

4.3.5   DestNode

A DestNode object represents information about Logical Destinations in the IP Telephony network.

The EnumDNsched objects and EnumDN objects may be configured to point to common DestNode which provides information about the common algorithm that will be used to generate the response to the ENUM query. The simplest DestNode type identifies a RtgSchedule object that identifies a list of call Servers that may be used to route the call.

Key destNodeName
Required destNodeName,type

4.3.6   EnumAcl

EnumAcl stands for the ENUM Access Control List (ACL), which is a set of client source IP addresses allowed or blocked, or both, to access the specific ENUM View(s). An EnumAcl object can be used in different views and servers.

Key AclId
Required AclId, AclName, MatchList

4.3.7   EnumDnRange

An EnumDnRange object represents a range of directory numbers. This object allows a destination node or a call server to be identified within the range of directory numbers. The associated objects are DestNode and CallServer. ENUM requests associated with all calls to numbers in the range are processed using the data of these associated objects.

EnumDnRange also provides NAPTRRecords for endpoints with IP connections to the network like EnumDnSched. The difference is that the EnumDnSched object contains the complete (neither sub- nor super-) set of dialed digits that identify an endpoint in the network, while EnumDNRange contains the super-set of it.

Accordingly EnumDnRange has two types of configuration: one is for NP which associates with fields destnode, callserver or olialias; the other is for NAPTRRecord, which associates with the fields NaptrFlags, NaptrOrder, NaptrPreference, NaptrService and NaptrTxt.

An EnumDnRange object can only have one type of configuration, either for NP or for NAPTRRecord. Therefore, if an EnumDnRange object is configured with fields NaptrFlags, NaptrOrder, NaptrPreference, NaptrService, NaptrTxt, it cannot be configured with fields destnode, callserver, olialias, and vice versa.

If an EnumDnRange is configured for NAPTRRecord.

Key rrflag, updateLevel, viewId, enumZoneId, enumDnRange
Required enumZoneId, enumDnRange

4.3.8   EnumDnSched

An EnumDnSched object provides the entry point for routing calls to an e.164 directory number, and also provides NAPTRRecords for endpoints with IP connections to the network.

The EnumDnSched object contains the complete (neither sub- nor super-) set of dialed digits that identify an endpoint in the network.

In the CLI view, each instance of the EnumDnSched corresponds to one NAPTRRecord. Each instance has different values for NaptrFlags, NaptrOrder, NaptrPreference, NaptrService and NaptrTxt parameters. All instances with the same series URI are combined into a set. Each set has a maximum of five such instances.

In the CLI view, the NaptrFlags, NaptrOrder, NaptrPreference, NaptrService and NaptrTxt fields are treated as part of the key of the EnumDnSched object. This means that to identify an instance of EnumDnSched on the CLI, the user must specify the value for each of these fields in addition to the EnumDn string (for example, 441012341234.e164.iptelco.com or 4.3.2.1.4.3.2.1.0.1.4.4.e164.iptelco.com), and the combination of all six values must be unique.

Key updateLevel, enumZoneId, enumDn
Required enumZoneId, enumDn, updateLevel, naptrFlags, naptrOrder, naptrPreference, naptrTxt

4.3.9   EnumNSRecord

The EnumNSRecord is for future use.

Key serverID, nameserver, dnsname
Required dnsname, serverID, nameserver

4.3.10   EnumServer

The EnumServer object is used to hold ENUM Server configuration data.

Key enumServerId
Required enumServerId

4.3.11   EnumSOARecord

The EnumSOARecord is used for DNS Negative Cache.

Key serverID, dnsname
Required dnsname, serverID, nameserver

4.3.12   EnumView

An EnumView object provides an access control mechanism for a defined set of ENUM Zones. The EnumView can also be used together with EnumDnRange to implement split namespace.

Key ViewId
Required ViewId, ViewName, Rank

4.3.13   EnumZone

The top level domains (for example, e164.iptelco.com) hosted by the ENUM Server.

Key enumZoneId
Required enumZoneId, enumZoneName

4.3.14   EnumZVRel

ENUM Zone View Relationship (EnumZVRel) defines the relationship between an ENUM Zone and an ENUM View.

Key ZoneId, ViewId
Required ZoneId, ViewId

4.3.15   INAPData

The INAPData object holds configuration data that applies for each ENUM number series to facilitate the INAP event message and format the response to ENUM client.

Key ProtocolSettingName
Required ProtocolSettingName , AddressName

4.3.16   INAPNode

The INAPNode object holds INAP configuration data to be used by the ENUM server on calling site when generating INAP queries that are to be sent to external SS7 database.

Key EnumServerId
Required EnumServerId, ServiceKey, LocalSSN, LocalSPC

4.3.17   MAPData

This object holds configuration data that applies for each ENUM number series to facilitate the MAP event message and format the response to ENUM client.

Key ProtocolSettingName
Required ProtocolSettingName and TranslationType

4.3.18   MAPNode

The MAPNode object holds MAP configuration data to be used by the ENUM server on calling site when generating MAP queries that are to be sent to external SS7 database.

Key EnumServerId
Required EnumServerId, GsmScfAddress, LocalSSN, LocalSPC

4.3.19   EnumOperator

The EnumOperator object holds the operator configuration data to be used by the ENUM server.

Key: OperatorName
Required: OperatorName, OperatorMCC, OperatorMNC, and OperatorType

4.3.20   EnumClientRealm

The EnumClientRealm object is to distinguish the original eTier2 ENUM server as three categories: a local, nation, or international eTier2 server.

Key: Name
Required: LocalClients, NationalClients, and InternationalClients
Note:  
The IP address range of attribute LocalClients, NationalClients, or InternationalClients consists of one of the following specific items:
  • Client IP address: such as 10.170.15.10 or !10.170.15.10.
    • 10.170.15.10: Indicates a specific IP included in the Client IP address list.
    • !10.170.15.10: Indicates a specific IP excluded in the Client IP address list.
  • Special value of IP address with only two options, either "any" or "none".
  • Subnetwork: such as 10.170.0.0/16 or !10.150.1.0/8.
    • 10.170.0.0/16: Indicates a specific subnetwork included in the Client IP address list.
    • !10.150.1.0/8: Indicates a specific subnetwork excluded in the Client IP address list.

4.3.21   SCCPAddress

The SCCPAddress object holds INAP configuration data to be used in SCCP layer when generating query/response.

Key: AddressName
Required: AddressName , GlobalTitleIndicator

Reference List

[1] Trademark Information.
[2] Glossary of Terms and Acronyms.
[3] Typographic Conventions.
[4] Command Line Interface User Guide for IPWorks SS.
[5] Configure DNS and ENUM.


Copyright

© Ericsson AB 2017, 2018. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design, and manufacturing.

Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in IPWorks Trademark Information.

    IPWorks DNS, ASDNS, ENUM Parameter Description