ENUM Query for n11 Services

Table Of Contents

Cisco BTS 10200 Softswitch ENUM Query for n11 Services Feature, Release 6.0.3

Contents

Overview

Provisioning the Feature

Managing the Feature

Measurement Counters

Billing Information

Additional References

Related Documents

Cisco BTS 10200 Softswitch ENUM Query for n11 Services Feature, Release 6.0.3

---

Last Updated: August 10, 2011

The support for Electronic Number mapping (ENUM) Query for n11 Services feature allows the Cisco BTS 10200 Softswitch to perform an ENUM query on the calling subscriber digits for n11 services such as REPAIR (611), BUSINESS (811), NON-EMG (311), and Directory Assistance (DA) (411). The call routing is based on the translated number received in the ENUM response from the ENUM server.

Contents

•Overview

•Provisioning the Feature

•Managing the Feature

•Additional References

Overview

The ENUM Query Support for n11 Services feature is based on the existing ENUM query framework in BTS 10200. For more information on ENUM capabilities and n11 services supported in BTS 10200, see Electronic Number Mapping and Routing chapter in the Routing and Dial Plan Guide. For more information on n11 Support, see the Network Features chapter in the Network and Subscriber Feature Descriptions Guide.

This feature allows BTS 10200 to perform an ENUM query on the calling subscriber number for n11 code types such as REPAIR (611), BUSINESS (811), NON-EMG (311), and Directory Assistance (DA) (411) only. The call routing is based on the translated number received in the ENUM response from the ENUM server.

Since the calling subscriber originating the n11 service may be from a different rate center or region, the ENUM query method uses the closest path to help route the call to the destination in a short time. If the ENUM query fails for any reason, the call is routed based on the default translated number specified in the POLICY-NXX table. If the default translated number is not provisioned in the POLICY_NXX table, the call is routed using destination-based routing.

Figure 1 illustrates ENUM based routing for n11 services.

Figure 1 ENUM Based Routing for n11 Services

Provisioning the Feature

This section explains how to provision the feature.

Note The commands shown in this section are only examples; you need to enter values that are appropriate for your network and service requirements. The CLI syntax allows you to use commands in uppercase or lowercase. It also allows you to enter hyphens (-) or underscores (_) interchangeably. (Exceptions, if any, are noted in the procedures.) For a complete list of tokens for each CLI table, as well as the allowed values, default values, and detailed descriptions for each token, see the Cisco BTS 10200 Softswitch CLI Database at this website: http://www.cisco.com/en/US/docs/voice_ip_comm/bts/6.0.3/BTS603_Mainpage.html

The ENUM query is enabled in BTS 10200 using the USE-ANI-FOR-ENUM token in the ENUM-PROFILE table. When this token is set to Y, the ENUM query is performed on the calling subscriber's number. This token provides the flexibility to the operator to disable ENUM query for n11 services. In such a scenario, the routing of the call is carried out using destination-based routing. The default value of this token is N.

SUMMARY STEPS

1. add enum_profile

2. change call_agent_profile

3. change ca_config

or

change destination

4. add policy_nxx

DETAILED STEPS

	Command	Purpose
Step 1	add enum_profile id=testENUM; ENUM_SERVER_DOMAIN=region1.enumsf; TOP_LEVEL_DOMAIN=311.e164.cisco.com; USE_ANI_FOR_ENUM=Y;	Add the ENUM profile for the call type. Note It is mandatory to specify the TOP_LEVEL_DOMAIN token.
Step 2	change call_agent_profile ID=ca146; CMS_ID=99999; MGC_ID=99999; PCMM_VERSION_MINOR=0; ENUM_SUPP=Y;	Change the call agent profile to support ENUM.
Step 3	add ca_config TYPE=DEFAULT-ENUM-PROFILE-ID; VALUE=testENUM; OR change destination DEST_ID=tbhrn17; CALL_TYPE=NON_EMG; ROUTE_TYPE=ROUTE; ROUTE_GUIDE_ID=n11; enum_profile_id=testENUM; ESRN_ROUTING=N; PERFORM_ENUM_ROUTING=Y; OVERLAP_SENDING_SUPP=Y;	Add the default ENUM profile ID in the CA-CONFIG table. This can also be added in the DESTINATION table.
		Add the ENUM profile ID and set PERFORM_ENUM_ROUTING to Y in the DESTINATION table.
Step 4	add policy-nxx id=normalroute; TRANSLATED_DN=2282229801;	Add the default translated DN. The call is routed based on the translated DN when the ENUM query fails.

Managing the Feature

This section provides information on managing the feature.

Measurement Counters

To track the number of ENUM queries launched by the BTS 10200 the call agent, the ENUM_QUERY_LAUNCHED counter is used. For more information on the measurements used in BTS 10200, see the Cisco BTS 10200 Softswitch Operations and Maintenance Guide.

Billing Information

The system captures the following information in the call detail records (CDR):

•Whether or not the ENUM query was performed for the call, and the result of the query (success/failure)

•Time stamp

•Universal Resource Identifier (URI) returned from the ENUM server

For more information, see the Cisco BTS 10200 Softswitch Billing Guide.

Additional References

Related Documents

Related Topic	Document Title
Summary of features and usage guidelines for this release	Cisco BTS 10200 Softswitch Release Notes
Reference listing of all CLI tables and tokens	Cisco BTS 10200 Softswitch CLI Database
ENUM Capability	Cisco BTS 10200 Softswitch Routing and Dial Plan Guide
ENUM Measurements	Cisco BTS 10200 Softswitch Operations and Maintenance Guide

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2011 Cisco Systems, Inc. All rights reserved.