Guest

Cisco PGW 2200 Softswitch

Generic LNP Protocol Enhancements

  • Viewing Options

  • PDF (245.6 KB)
  • Feedback
Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping

Table Of Contents

Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping

Feature Overview

Benefits

Restrictions

Related Documents

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites

Provisioning Tasks

Planning for Provisioning

Provisioning the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature

Verifying the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature

Troubleshooting Tips

Regular Operations

Provisioning Examples

Reference Information

Properties

Cause and Location Codes

Glossary


Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping


Document Release History

Publication Date
Comments

September 16, 2003

Initial version of this document.


Feature History

Release
Modification

9.4(1)

This feature was introduced on the PGW 2200 (MGC) in software Release 9.4(1).


The Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature is described in the following sections.

Feature Overview

Supported Platforms

Supported Standards, MIBs, and RFCs

Prerequisites

Provisioning Tasks

Provisioning Examples

Reference Information

Glossary

Feature Overview

The purpose of this feature is to extend previous protocol-specific developments to all supported protocols for 32-digits and overdecadic digits, and to support number portability when receiving and generating Cause 14.

Benefits

Enabling the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature provides the following benefits.

32 digit and overdecadic support

Supports up to 32 digits and overdecadic digits (A through F) in called and calling numbers across all supported protocols for all number parameters listed in Table 1. This includes support for all call types (redirecting, redirected, ported, and so on).

Mapping of Cause 14

As per ITU-T Q.850 Addendum 1, Cause 14 was introduced in Annex C/Q.769.1, for the query on release (QoR) capability in number portability. Switches must act on or generate external Cause 14 releases to pass interconnect. Therefore, the MGC needs to map external Cause 14 releases to an internal release cause code.

The MGC must support Number portability when operating as an originating switch, transit switch, recipient switch, or donor switch, supporting the following two scenarios.

a) MGC receives a Cause 14—In a QoR scenario, the MGC may receive a Cause 14 from the terminating switch if the number has been ported. The MGC needs to be able to pass the Cause 14 back to the originating switch. It is possible in this scenario that the MGC could initiate an LNP query based on the receipt of a Cause 14, but that is supported via dial plan set ups and does not require any development or testing for this feature.

b) MGC generates a Cause 14—If the MGC dial plan analysis determines that the dialed number has been ported, the MGC must be capable of generating a release Cause 14 back to the originating switch which performs the destination LNP lookup. This scenario is also already presumed to be supported via the dial plan functionality and should not explicitly require testing as long as the Cause 14 mapping is supported.

Restrictions

The overdecadic digits support is applied to all ANSI protocol variants and all ITU protocol variants that conform to the Q.721, Q.761, and Q.767 Recommendations.

The 32-digit support is applied to all ANSI protocol variants and all ITU protocol variants that conform to the Q.761 and Q.767 Recommendations.


Note Man Machine Language (MML) targets of AWHITE, BWHITE, ABLACK, BBLACK, TERMTBL, ANUMDPSEL, and ACHGORIGIN only support the Calling Line Identity (CLI) up to 20 digits. The MML target of PORTTBL supports the called number and routing number up to 20 digits as well.



Note For the Called Party Number (CDPN) parameter, the existing global property "TmaxDigits" has to be set to 32 as well so that up to 32 digits can be sent out by the MGC, since this property determines how many digits are sent out. In other words, even if the terminating side protocol variant maximum number of digits is equal to 32, only as many digits are included in the CDPN parameter as this property allows.


Handling Cause 14 (QoR: ported number) for the Query on Release used in the number portability functionality involves the following:

Generating the cause code as part of the Release (REL) message being sent to the preceding exchange or network.

Passing on the received cause code contained in the backward REL message to the preceding exchange or network if the MGC determines that the CDPN has been ported based on the Local Number Portability (LNP) functionality, but that the CDPN is not in the ported table.

Performing an LNP table lookup on the received cause code if the MGC determines that the CDPN has been ported and route the call if the CDPN is in the ported table.


Note The 32-digit functionality does not apply to the protocol variants of the Q.721 protocol, since these protocols have a 4-bit field for the number (length) of the address signals contained in each parameter, thus it is not possible to have any parameter with more than 16 digits.


Refer to Table 1 for a list of supported parameters per protocol family.

Table 1 Parameters Affected by Overdecadic and 32 Digits Support 

Protocol Family
Parameters
32 Digits Support
Overdecadic
Digits Support

ANSI

 

 

 

 

Called Party Number

Yes

Yes

 

Calling Party Number

Yes

Yes

 

Carrier Identification

No (3 or 4 digits)

No (see Note 1)

 

Charge Number

Yes

Yes

 

Generic Address

Yes

Yes

 

Jurisdiction Information

No (6 digits)

No

 

Original Called Number

Yes

Yes

 

Outgoing Trunk Group Number

No (6 digits)

No

 

Redirecting Number

Yes

Yes

 

Redirection Number

Yes

Yes

 

Transit Network Selection

No (3 or 4 digits)

No (see Note 1)

Q.721

 

 

 

 

Additional Identity* (French ISUP)

No (see Note 2)

Yes

 

Called Party Number

No (see Note 2)

Yes

 

Calling Line Identity (Calling Party Number)

No (see Note 2)

Yes

 

Original Called Number

No (see Note 2)

Yes

 

Subsequent Address Message (Subsequent Number)

No (see Note 2)

Yes

 

Subsequent Address Message with One signal

No (1 digit)

Yes

 

Transit Exchange Identity

No (see Note 2)

No

Q.761

 

 

 

 

Called Party Number

Yes

Yes

 

Calling Party Number

Yes

Yes

 

Carrier Selection* (German ISUP)

No (3 or 4 digits)

Yes

 

Charge Area Information (Japanese ISUP)

Yes

Yes

 

Connected Number

Yes

Yes

 

Contract Number* (Japanese ISUP)

Yes

Yes

 

Generic Number

Yes

Yes

 

Last Diverting Line Identity* (UK ISUP)

Yes

Yes

 

Location Number

Yes

Yes

 

Original Called Number

Yes

Yes

 

Presentation Number* (UK ISUP)

Yes

Yes

 

Redirecting Number

Yes

Yes

 

Redirection Number

Yes

Yes

 

Subsequent Number

Yes

Yes

 

Transit Network Selection

No (3 or 4 digits)

Yes

Q.767

 

 

 

 

Called Party Number

Yes

Yes

 

Calling Party Number

Yes

Yes

 

Connected Number

Yes

Yes

 

Generic Number* (Italian Interconnect and Russian ISUPs)

Yes

Yes

 

Location Number* (Colombia, Russian, Spanish and Swedish ISUPs)

Yes

Yes

 

Original Called Number* (Colombia, Indonesia, Mexican, Russian, Spanish and Swedish ISUPs)

Yes

Yes

 

Redirecting Number* (Colombia, Indonesia, Mexican, Russian, Spanish and Swedish ISUPs)

Yes

Yes

 

Redirection Number* (Colombia, Indonesia, Mexican, Russian, Spanish and Swedish ISUPs)

Yes

Yes

 

Subsequent Number

Yes

Yes

 

Transit Network Selection* (Colombia and Mexican ISUPs)

No (3 or 4 digits)

Yes

Note 1: The overdecadic support for the listed parameters was introduced previously in software Release 9. Overdecadic support only applies when the MGC (configured for Signaling Mode) receives an SS7 call and terminates to the Network Access Server (NAS) gateway or vice versa; and does not apply to an SS7-to-SS7 call, which does not support overdecadic digits.

Note 2: There is a 4-bit length field associated with the number of address signals (digits) within the bit string of the parameter, thus not making it possible to have more than 16 digits.

Parameters marked with an (*), are only specific to the protocol variants that appear in parenthesis meaning that the base variant of the protocol family does not support the parameter. The Japanese ISUP consists of the NTT, TOKYO, JAPAN, and JAPAN_JT protocol variants.


Related Documents

This document contains information that is related strictly to the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 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 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

The following recommendations are supported by this feature.

Standards

ITU-T Q.850, Addendum 1. Addition of Cause 14 for QoR: ported number

Recommendation Q.850 - Usage of Cause and Location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part. Addendum 1

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

For this feature to work., the TMaxDigits property must be set to 32 to allow 32-digit called number. The.TMaxDigits property is set on the sigpath. After opening a provisioning session, you can use MML to set the TMaxDigit property to 32 by using the following MML command:

mml>prov-add:sigsvcprop="ss7svc1",TMaxDigits="32" 

Provisioning Tasks

This section provides information on how to provision the MGC using MML.

Planning for Provisioning

When provisioning the MGC, to support

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 Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature

Perform the following steps to provision the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature.


Note The OD32DigitSupport property can be provisioned from any provisioning session.



Step 1 Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="lnpprov",dstver="mml_01"


Caution 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.

Step 2 Dynamically change the OD32DigitSupport property for 32-digit and overdecadic support.
mml>prov-add:trnkgrpprop:name="1000",OD32DigitSupport="0"


Note Setting the value of the OD32DigitSupport property to 0 disables overdecadic 32 digit support. The default property value is 1 (enabled).


Step 3 A response similar to the following is returned:
Media Gateway Controller - MGC-03 2003-02-17 14:25:56

M COMPLD 
"trnkgrp" 

Step 4 Commit the changes.
mml>prov-cpy


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.

Verifying the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature

After you have provisioned the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature, perform the following steps to verify its setting.


Step 1 Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="01",dstver="mml_02"

Step 2 Use prov-rtrv:trnkgrpprop:name="1000" to verify the trunk group property is correctly provisioned.
mml>prov-rtrv:trnkgrpprop:name="1000"

Step 3 A response, similar to the following, is returned:

Media Gateway Controller - MGC-03 2003-02-17 14:27:52
M RTRV
"session=trnkgrpprop"
/*
BOrigStartIndex = 0
BTermStartIndex = 1
CarrierIdentity = 0
CLLI = STEVE
CompressionType = 1
CotPercentage = 0
CustGrpId = 0000
EchoCanRequired = 0
ExtCOT = Loop
GLARE = 0
Npa = 0
RingNoAnswer = 255000
SatelliteInd = 0
ScreenFailAction = 0
·
·
·
OD32DigitSupport = 1 
*/
;

Troubleshooting Tips

The 32-digit functionality does not apply to the protocol variants of the Q.721 protocol, since these protocols have a 4-bit field for the number (length) of the address signals contained in each parameter, thus it is not possible to have any parameter with more than 16 digits.

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.

Regular Operations

Introduction of this feature requires the following types of regular operation:

Managing MML sessions

Managing Signaling Channels

Managing Bearer Channels

Provisioning your Cisco MGC

Managing your Cisco MGC platform

Provisioning Examples

This section provides the following example of provisioning for this feature:

Perform the following steps to provision the Generic LNP Protocol Enhancements: 32 Digits, Overdecadics, and Cause 14 Mapping Feature.


Step 1 Open a provisioning session by using the following MML command:
mml>prov-sta::srcver="lnp02",dstver="mml_01"

Step 2 If the OD32DigitSupport is disabled, dynamically change the OD32DigitSupport property for 32-digit and overdecadic support.
mml>prov-add:trnkgrpprop:name="1000",OD32DigitSupport="1"

A response similar to the following is returned:
Media Gateway Controller - MGC-03 2003-02-17 14:25:56

M COMPLD 
"trnkgrp" 

Step 3 Commit the changes.
mml>prov-cpy


Additional examples of provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

Reference Information

The following sections contain reference material related to this feature. Information is included on the following areas:

Properties

Properties

The following property is added for this feature.

OD32DigitSupport — This property can be specified for a sigpath or a trunk group. The OD32DigitSupport property allows 32 digits and overdecadic digits support for the ANSI, Q.761, and Q.767 protocol variants for the ANSI, SS7-ITU, SS7-China, SS7-Japan, and SS7-UK protocol families. Valid values are: 0 and 1 (default).

This property is used to set an integer variable to the constant value of 32 and also accept digits 0 through 9 along with the IA5 representation of the characters A through F.

The default value of 1 (enabled) allows the overdecadic and 32-digit support. However, it is possible to maintain previous functionality by setting this property value to 0 (disabled) on a sigpath or trunk group basis.

The 32-digit support is applied to all ANSI protocol variants and all ITU protocol variants that conform to the Q.761 and Q.767 Recommendations.


Note The 32-digit functionality does not apply to the protocol variants of the Q.721 Recommendation, since there is a 4-bit field for the number (length) of the address signals contained in each parameter, thus it is not possible to have any parameter with more than 16 digits.


The overdecadic digits support is applied to all ANSI protocol variants and all ITU protocol variants that conform to the Q.721, Q.761, and Q.767 Recommendations.

For information on other properties for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

Cause and Location Codes

The following cause and/or location codes are added, modified, or deleted for this feature.

Cause 14 (Query on Release: ported number) is mapped to the internal cause code value of 164 (IC_NP_QOR_NUM_NOT_FOUND).

For information on other cause and location codes for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide for table setup examples for cause and location codes.

Glossary

Table 2 contains acronym definitions and technical terms used in this feature module.

Table 2 Acronyms and Definitions 

Acronym
Definition

BCD

Binary Coded Decimal

CC

Call Context

CDPN

Called Party Number

CGPN

Calling Party Number

CDPN

Called Party Number

CLI

Calling Line Identity

GTD

Generic Transparency Descriptor

IA5

International Alphabet Number 5

IAM

Initial Address Message

INAP

Intelligent Network Application Protocol

ITU-T

International Telecommunications Union - Telecommunications Standard

LNP

Local Number Portability

MGC

Media Gateway Controller

MML

Man Machine Language

NOA

Nature of Address

PGW

PSTN Gateway

PGW 2200

PGW in Call Control Mode or Signaling Mode

PSTN

Public Switched Telephone Network

QoR

Query on Release

REL

Release message

SC

Signaling Controller

SCP

Service Control Point

SW

Software

VSC

Virtual Switch Controller


The migrateTKGfile is modified to add the OD32DigitSupport property when migrating from old versions of the import file

The migrate_9.3001_9.4001 is modified to add the OD32DigitSupport property to properties.dat.