Configurable NOA Mapping
Document Release History
Publication Date
Comments
October 6, 2003
Initial version of the document.
October 7, 2003
Incorporated comments received and changed the section headings on
page 7 and page 8.
October 28, 2003
Changed the value range for INTNOA and EXTNOA on page 6 and added
the note on page 6.
Feature History
Release
Modification
9.4(1)
This feature was introduced on the Cisco PGW 2200.
The Configurable NOA Mapping Feature is described in the following sections:
•
Feature Overview, page 2
•
Supported Platforms, page 4
•
Supported Standards, MIBs, and RFCs, page 4
•
Prerequisites, page 4
•
Configuration Tasks, page 4
•
Provisioning Tasks, page 5
•
Creating Dial Plan Data, page 8
•
Provisioning Examples, page 10
•
Provisioning Examples, page 10
•
Command Reference, page 10
•
Command Reference, page 10
•
Reference Information, page 11
•
Glossary, page 13
Cisco MGC Software Release 9.4(1)
1
Configurable NOA Mapping
Feature Overview
Feature Overview
In some environments, certain protocols receive ported calls with an incoming Nature of Address (NOA)
value of 8. The Cisco MGC rejects this call because an NOA value of 8 is designated as a spare value.
Customers typically do not want the switch to restrict or reject calls that do not comply with applicable
signaling specifications. Thus, in some cases, the service provider uses NOA=8 to indicate a local
number portability (LNP) call. As a result, when NOA=8, the service provider wants the Cisco MGC to
perform a digit translation to remove the LNP prefix and transit the call into the SIP network. The service
provider’s concern is to transit the call, not police compliance with the signaling specifications.
From ITU-T Recommendation Q.763, NOAs with values of 6 through 111 are listed as being spare.
There is a generally accepted understanding that this can be interpreted as free to use. Large ranges of
NOA values are being used by service providers in different countries throughout Europe. It is common
practice among the European switch manufacturers to allow NOA values to be used freely within the full
range listed in Recommendation Q.763.
As a result, it may be necessary for the Cisco MGC to allow all protocols the ability to stop blocking
calls if an unknown NOA value (that is, designated as spare) is received.
For Inbound Calls
The translation of NOA values from line values to internal call context (CC) NOA values is done using
maps in the software. Different maps are used for different protocols. #IFDEF statements are used within
protocols for country variants. If there is no mapping for a particular line NOA value, an error is
generated, which may cause the parameter to be dropped; or in the case of a called number, the call to
be rejected.
To prevent a called number from being rejected, the following functionality is added.
Before translating the NOA value with the internal map, a check is made to ensure the line NOA value
exists in the Configurable (NOA) Translation Table (CTT).
If the number does exist in the CTT, the configured value for the internal NOA value is used. The return
value is placed into CC for further call processing, and the call handling continues. No map translation
occurs.
However, if the number does not exist in the CTT, (or the CTT does not exist), an attempt to translate
the line NOA value using the existing maps is performed. The result is then processed.
For Outbound Calls
The translation of internal CC NOA values to NOA line values is also performed using internal maps.
Different maps are used for different protocols. #IFDEF statements are used within protocols for country
variants.
The maps contain a default entry, which is used if the internal CC NOA value is not found, this ensures
that a valid line NOA value is available for constructing the line message.
Before translating the NOA value with the map, the internal CC NOA value is checked to ensure it exists
in the CTT.
If the NOA value does exist, the configured value for the line NOA value is used. The return value is
placed into CC and is used for message construction. Thus, no map translation occurs.
If the NOA value does not exist, (or the CTT does not exist), an attempt is made to translate the internal
CC NOA value using the existing maps.
Cisco MGC Software Release 9.4(1)
2
Configurable NOA Mapping
Feature Overview
Benefits
The Configurable NOA Mapping Feature allows all protocols to stop blocking NOA values designated
as spare to prevents customers from experiencing problems with calls.
Restrictions
This feature is limited to protocols (and variants) that support NOA, which are: Q.761, Q.761-97, Q.767,
and ANSI.
The Configurable NOA Mapping Feature is determined by configuration. The configuration tables
define CTT for inbound line values to internal CC NOA values and internal CC NOA values to outbound
line values. The CTT can be added on a per sigpath basis.
Since the NOA is present in many parameters in different protocols, to limit the scope of this feature,
only the following numbers are supported:
•
Called party number
•
Calling party number
•
Original called party number
•
Redirecting number
•
Redirection number
•
Generic number
Each number has an inbound and outbound CTT. Although in most cases the inbound and out bound
NOA translation values would be the same, they can be different.
Depending on the CTT configuration, Type B (calls between the same SS7 protocol variant) exchange
operation may be affected. For example, without CTT configured, for some non-called party numbers, a
line NOA value may be out of range, and this information would be passed from the ingress to the egress
and populated in the egress message.
However, if an inbound CTT is configured that translates the inbound line out-of-range NOA value to a
value that is in range, the call is then handled as a normal call. The outbound message on the egress side
may or may not contain the same line NOA value as the ingress depending on the outbound CTT.
If the translation tables are not populated, there is no significant impact to performance; and depending
on the number of tables that are populated, the impact may be only minimal.
Related Documents
This document contains information that is related strictly to the Configurable NOA Mapping Feature.
The documents that contain additional information related to the Cisco Media Gateway Controller
(MGC) are listed below:
•
Release Notes for Cisco Media Gateway Controller Software Release 9.4(1)
•
Cisco Media Gateway Controller Hardware Installation Guide
•
Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller
•
Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
•
Cisco Media Gateway Controller Software Release 9 Provisioning Guide
•
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide
Cisco MGC Software Release 9.4(1)
3
Configurable NOA Mapping
Supported Platforms
•
Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide
•
Cisco Media Gateway Controller Software Release 9 Messages Reference Guide
•
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
•
Cisco Media Gateway Controller Software Release 9 MIB Guide
•
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Release Notes for
Cisco Media Gateway Controller Software Release 9.4(1).
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway
Controller Release 9 MIB Guide.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
You must have Cisco Media Gateway Controller (MGC) software Release 9.4(1) installed. Prerequisites
for this software release can be found in the Release Notes for the Cisco Media Gateway Controller
Software Release 9.4(1).
Configuration Tasks
The following section contains the steps necessary for configuration of the Cisco MGC software to
support the Configurable NOA Mapping Feature.
The CTTs are derived from the linexlate.dat file. Configuration of the linexlate.dat file is dynamically
configurable. Each sigpath can have as many as 12 NOA CTTs, (6 numbers x 2 directions).
Cisco MGC Software Release 9.4(1)
4
Configurable NOA Mapping
Provisioning Tasks
Caution
Configuration of the Cisco MGC software requires that the system software be shut down. In a simplex
system, calls cannot be processed during system shut down. In a continuous service system, your system
loses the ability to maintain calls during a critical event while the system software on one PGW hosts is
shut down.
For more information on configuring the rest of the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Installation and Configuration Guide.
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
• Planning for Provisioning, page 5
•
Provisioning the NOA Configurable Mapping Feature, page 6
Planning for Provisioning
This section lists the data that you must gather to successfully provision this feature. For more
information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco
Media Gateway Controller Software Release 9 Provisioning Guide.
Table 1 lists the parameters used when provisioning the Configurable NOA Mapping Feature.
Table 1
NOA Provisioning Parameters
Parameter MML
Name
Parameter Description
Parameter Values (Default)
NAME
Unique ID of this component and The name can be up to any 20 alphanumeric
component name used in MML characters. No special characters other than
commands
“-” are allowed. Names should begin with an
alphabetic character.
DESC
Component description
The description can be as many as 128
characters.
SVC
Signal path MML name.
MML name of previously defined signal
service.
PARAMETER
This indicates the parameter or
field in the protocol message to
which this entry refers.
Currently NOA is the only parameter
supported.
DIRECTION
1 = NOA
Direction in which the message 0 = in
is going, either into or out of the 1 = out
MGC.
Note
This is not ingress or
egress.
Cisco MGC Software Release 9.4(1)
5
Configurable NOA Mapping
Provisioning Tasks
Table 1
NOA Provisioning Parameters (continued)
Parameter MML
Name
Note
Parameter Description
Parameter Values (Default)
NUMBER
A number representing a specific 0 = called
number type in the protocol
1 = calling
message.
2 = original called
3 = redirecting
4 = redirection
5 = generic
INTNOA
Internal NOA value.
EXTNOA
The value of the NOA field in the Any 7-bit value, 0 through 127, no
protocol message.
restrictions.
Any 7-bit value, 0 through 127, no
restrictions.
If you do not configure custom NOA mapping tables, the default NOA mapping listed in Appendix A of
the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide is used.
For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Provisioning the NOA Configurable Mapping Feature
The following MML command syntax is used to add an entry to the linexlate.dat file.
mml>prov-add:linexlate:name=<MML name>,DESC=<Description>,SVC=<MML name>,PARAMETER=<param
value>,DIRECTION=<param value>,NUMBER=<param value>,INTNOA=<param value>,EXTNOA=<param value>
where:
MML name = an NOA translate table entry name, as many as 20 characters in length, or “all”
Description = a more descriptive name for the entry, which can be as many as 128 characters in length
Parameter = 1
Direction = 0 or 1
Number = 0 through 5
Intnoa = 0 through 127
Extnoa = 0 through 127
For adding an entry, none of the parameters are optional, all must be present, as shown in the following
example.
mml>prov_add:linexlate:name=”noa1”,desc=”noa in calling 10”,svc=”ss7svc1”,
parameter=”1”,direction=”in”,number=”calling”,intnoa=17,extnoa=10
The following MML command syntax is used to delete an entry from the linexlate.dat file.
mml>prov-dlt:linexlate:name=<MML name>
Where MML name is the NOA translate table entry.
For example:
mml>prov-dlt:linexlate:name=“noa1”
Cisco MGC Software Release 9.4(1)
6
Configurable NOA Mapping
Provisioning Tasks
The following MML command syntax is used to retrieve an entry in the linexlate.dat file.
prov-rtrv:linexlate:name=<MML name>
Where the MML name is the name of an NOA translate table entry.
Note
The line translation table contains no default entries, since all parameters must be entered to create a
configuration entry.
Adding an NOA Value to the LineXlate File for Inbound Calls
Perform the following steps to provision the Configurable NOA Mapping Feature.
Step 1
Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="linexlt1",dstver="mml_01"
Caution
Step 2
Do not name the destination directory “active” or “new.” The names “active” and “new” have special
meanings in the Cisco MGC software. Starting a provisioning session with a source version name of
“new”, is to be done only the first time provisioning is performed.
Dynamically add the internal NOA and line NOA property for LineXlate.
mml>prov-add:linexlate:name=”noa1”,desc=”noa in calling 10”,svc=”ss7svc1”,
direction=”in”,number=”calling”,intnoa=17,extnoa=10
Step 3
Commit the changes.
mml>prov-cpy
Step 4
Use prov-rtrv:linexlate:name=”noa1” to verify the property was added correctly.
mml>prov-rtrv:linexlate:name=”noa1”
For more information on provisioning for the rest of the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Provisioning Guide.
Deleting an NOA Value from the LineXlate File
Perform the following steps to delete the configured provisioned LineXlate entry dynamically.
Step 1
Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="01",dstver="mml_02"
Step 2
Dynamically delete the internal NOA and line NOA property for LineXlate.
mml>prov-dlt:linexlate:name=”noa1”
Step 3
Commit the changes.
mml>prov-cpy
Step 4
Use prov-rtrv:linexlate:name=”noa1” to verify the property was deleted correctly.
mml>prov-rtrv:linexlate:name=”noa1”
Cisco MGC Software Release 9.4(1)
7
Configurable NOA Mapping
Creating Dial Plan Data
Adding an NOA Value to the LineXlate File for Outbound Calls
Perform the following steps to provision the line NOA and internal NOA property for an outbound
message.
Step 1
Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="02",dstver="mml_03"
Step 2
Dynamically add the internal NOA and line NOA property for LineXlate.
mml>prov-add:linexlate:name=”noa2”,desc=”noa in calling 10”,svc=”ss7svc1”,
direction=”out”,number=”called”,intnoa=17,extnoa=10
Step 3
Commit the changes.
mml>prov-cpy
Step 4
Use prov-rtrv:linexlate:name=”noa2” to verify the property was added correctly.
mml>prov-rtrv:linexlate:name=”noa2”
Deleting an NOA Value from the LineXlate File
Perform the following steps to delete the configured provisioned LineXlate entry dynamically.
Step 1
Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="03",dstver="mml_04"
Step 2
Dynamically delete the LineXlate table entry.
mml>prov-dlt:noaxlate:name=”noa2”
Step 3
Commit the changes.
mml>prov-cpy
Step 4
Use prov-rtrv:linexlate:name=”noa2” to verify the property is deleted correctly.
mml>prov-rtrv:linexlate:name=”noa2”
Validation Rules
Note
•
All parameters must be present.
•
The sigpath must have been provisioned.
•
Parameter, direction, number, intnoa, and linenoa are range validated.
•
A check is made to verify there is not a duplicate entry.
The table contains no default entries since all parameters must be entered to create a configuration entry.
Creating Dial Plan Data
Using the numan-add:noa MML command, you can control the NOA mapping of incoming to outgoing
values.
Cisco MGC Software Release 9.4(1)
8
Configurable NOA Mapping
Creating Dial Plan Data
Planning for a Dial Plan
The following sections provide the MML commands and examples for mapping the incoming to
outgoing NOA values. You can refer to Appendix A in the Cisco Media Gateway Controller Software
Release 9 Dial Plan Guide for a list of internal call context NOA values.
For more information on planning dial plans for other functions of the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Creating a Dial Plan to Support the Configurable NOA Mapping Feature
Perform the following steps to provision the Linexlate table in your dial plan.
Verify a line NOA value translation using a dial plan for SS7-to-SS7 calls.
Step 1
Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="04",dstver="mml_05"
Step 2
Provision the Cisco MGC for a line NOA value to the dial plan of incoming calls trunk group, using the
following MML command:
mml>numan-add:noa:custgrpid=”1111”,noavalue=4,setname=”rset1”
Step 3
Provision the Cisco MGC for a line NOA value to the dial plan of outgoing calls trunk group, using the
following MML command:
mml>numan-add:noa:custgrpid=”1111”,noavalue=14,setname=”rset2”
Step 4
Commit the changes.
mml>prov-cpy
Step 5
Use prov-rtrv:linexlate:name=”noa2” to verify the property is added correctly.
mml>prov-rtrv:linexlate:name=”noa2”
Verify that the line NOA value translation has occurred correctly. For example, line value 4, added at the
incoming trunk group, is converted to an internal NOA value 14 at the outgoing trunk group and is
received at the PSTN side.
Verify a line NOA value translation for Calling, Called Party, and Redirection Number parameters for
Type B calls.
For more information on creating dial plans for other functions of the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Troubleshooting Tips
When configuring incoming NOA values, ensure the mapping matches for the protocol and variant being
used.
For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Cisco MGC Software Release 9.4(1)
9
Configurable NOA Mapping
Monitoring and Maintaining
Monitoring and Maintaining
The following sections contain the procedures required for proper monitoring and maintenance of this
feature. For more information on operational tasks for the rest of the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting
Guide.
Provisioning Examples
This section provides the following example of provisioning for this feature:
mml>prov-add:linexlate:name=”noa1”,desc=”noa in calling 10”,svc=”ss7svc1”,
parameter=”1”,direction=”in”,number=”calling”,intnoa=17,extnoa=10
Additional examples of provisioning for the Cisco MGC software can be found in the Cisco Media
Gateway Controller Software Release 9 Provisioning Guide.
Command Reference
This section documents new, modified, or deleted Man-Machine Language (MML) commands. All other
commands are documented in the Cisco Media Gateway Controller Software Release 9 MML Command
Reference Guide.
New MML Commands
This section contains the MML commands that are new for the Configurable NOA Mapping Feature. The
following three MML commands have been added to support this feature and populate the linexlate.dat
file.
prov-add:linexlate:name=<MML name>,DESC=<Description>,SVC=<MML name>,PARAMETER=<param value>,DIRECTION=<param
value>,NUMBER=<param value>,INTNOA=<param value>,EXTNOA=<param value>
For adding an entry in the linexlate.dat file:
Note
None of the parameters are optional. Therefore all parameters must be present.
mml>prov-add:linexlate:name=”noa1”,desc=”noa in calling 10”,svc=”ss7svc1”,
parameter=”1”,direction=”in”,number=”calling”,intnoa=17,extnoa=10
For deleting an entry from the linexlate.dat file:
mml>prov-dlt:linexlate:name=<MML name>
where MML name is the line NOA value translate table entry
For example:
mml>prov-dlt:linexlate:name=”noa1”
For retrieving an entry in the linexlate.dat file:
mml>prov-rtrv:linexlate:name=<MML name>
Cisco MGC Software Release 9.4(1)
10
Configurable NOA Mapping
Reference Information
where MML name could be the name of a line NOA value translate table entry or “all”.
For example:
mml>prov-rtrv:linexlate:name=”noa2”
Note
There is no prov-ed command since you include all parameter need to add an entry. Thus there is no
option to edit an entry. If an entry is incorrect, delete the entry line (prov-dlt), and add the correct entry
(prov-add).
Reference Information
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
Components, page 11
•
NOA Codes, page 12
•
Dial Plan Worksheets, page 12
Components
The following component is added for this feature.
Linexlate
The linexlate (line translation) component provides the ability to translate incoming NOA values to the
same or different value for Q.761, Q.761-97, Q.767, and ANSI protocols (and variants) that support
NOA. Its MML name is as follows:
•
MML Name—LINEXLATE
The structure of this component is shown in Table 2.
Note
Since all parameters need to be entered to add an entry, there is no prov-ed command. Thus there is no
option to edit an entry. If the entry is wrong, delete it (prov-dlt) and add the correct entry (prov-add).
Table 2
Line Translate Component MML Parameters
Parameter MML
Name
Parameter Description
Parameter Values (Default)
NAME
Unique ID of this component and The name can be up to any 20 alphanumeric
component name used in MML characters. No special characters other than
commands
“-” are allowed. The name should begin with
an alphabetic character.
DESC
Component description
The description can be as many as 128
characters.
Cisco MGC Software Release 9.4(1)
11
Configurable NOA Mapping
Reference Information
Table 2
Line Translate Component MML Parameters (continued)
Parameter MML
Name
Parameter Description
Parameter Values (Default)
SVC
Signal path MML name.
MML name of previously defined signal
service.
PARAMETER
This indicated the parameter or
field in the protocol message to
which this entry refers.
Currently the only parameter is NOA.
DIRECTION
1 = NOA
Direction in which the message 0 = in
is going, either into or out of the 1 = out
MGC.
Note
This is not ingress or
egress.
NUMBER
A number representing a specific 0 = called
number type in the protocol
1 = calling
message.
2 = original called
3 = redirecting
4 = redirection
5 = generic
INTNOA
Internal NOA value.
EXTNOA
The value of the NOA field in the Any 7-bit value, 0 through 127, no
protocol message.
restrictions.
Any 7-bit value, 0 through 127, no
restrictions.
For information on the rest of the components in the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Provisioning Guide.
NOA Codes
For information on the NOA codes for the Cisco MGC software, refer to Appendix A in the Cisco Media
Gateway Controller Software Release 9 Dial Plan Guide.
Dial Plan Worksheets
The tables in this section are for planning your dial plan data, specific to this feature.
Table 3
NOA Mapping Table
Incoming NOA Value
Cisco MGC Software Release 9.4(1)
12
Internal NOA Value
Outgoing NOA Value
Configurable NOA Mapping
Glossary
Table 3
NOA Mapping Table (continued)
Incoming NOA Value
Internal NOA Value
Outgoing NOA Value
For worksheets covering the rest of the dial plan components in the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Glossary
Table 4 contains definitions of acronyms and technical terms used in this Configurable NOA Mapping
Feature module.
Table 4
Acronyms and Definitions
Acronym
Definition
CC
Call Context
CTT
Configurable (NOA) Translation Table
LNP
Local Number Portability
MGC
Cisco Media Gateway Controller
NOA
Nature of Address
PGW
PSTN Gateway
PSTN
Public Switched Telephone Network
PTCC
Packet Telephony Call Control
SC
Signaling Controller
VSC
Virtual Switch Controller
Cisco MGC Software Release 9.4(1)
13
Configurable NOA Mapping
Glossary
Cisco MGC Software Release 9.4(1)
14