Support of Partial CLI and CLI Code of Practice
Edition 3
Document Release History
Publication Date
Comments
May 17, 2004
Initial version of the document.
Feature History
Release
Modification
9.5(2)
This feature was introduced on the Cisco PGW 2200 software
Release 9.5(2).
This document describes the support of the partial calling line identity (PCLI) and calling line identity
(CLI) code of practice (COP) Edition 3 (COP3) feature.
This feature is described in the following sections:
•
Feature Overview, page 2
•
Supported Platforms, page 4
•
Supported Standards, MIBs, and RFCs, page 4
•
Prerequisites for Using This Feature, page 4
•
Configuration Tasks, page 5
•
Provisioning Tasks, page 5
•
Configuration Examples, page 11
•
Reference Information, page 12
•
Obtaining Documentation, page 15
•
Documentation Feedback, page 16
•
Obtaining Technical Assistance, page 16
•
Obtaining Additional Publications and Information, page 18
•
Glossary, page 18
Cisco MGC Software Release 9.5(2)
1
Support of Partial CLI and CLI Code of Practice Edition 3
Feature Overview
Feature Overview
This feature provides support on the Media Gateway Controller (MGC) for the PCLI and CLI COP
edition 3 (COP3).
Provisioning of the CLI display information requires end-to-end availability and control of the caller
information and that this information be generated in a consistent way. Unless consistently rendered,
these services cannot be provided efficiently, because the status of the displayed messages cannot be
guaranteed by the provider of the display service. Therefore, consistency is required between the
network where the messages are generated and the network where the messages are displayed.
When two or more networks are interconnect, there must be a way to ensure that all networks adhere to
the same rules for displaying messages. The Support of Partial CLI and CLI Code of Practice Edition 3
feature supports PCLI and CLI presentation. It also supports COP3 to ensure consistent CLI information
presentation.
To that end, the COP:
Note
•
Encourages the adoption of a consistent set of rules for customer line identities to enable the support
of display services across network boundaries
•
Provides for the rules adopted to ensure that the requirements of the Data Protection Act are met
•
Provides a reasonable balance between consumer and producer interests
•
Provides flexibility so that any set of rules can evolve in an efficient manner to reflect technological
developments and other changes
The CLI COP3 functionality is performed only if the calling party number (CgPN) and presentation
number (PN) parameters have valid field values, that is, if they are not placed in the out of range
parameter buffer when they arrive as part of the Initial Address Message (IAM).
Benefits
The Support of Partial CLI and CLI Code of Practice Edition 3 feature provides the following benefits:
•
PCLI is used in the ISDN User Part (ISUP) signaling information and is typically generated where
a full CLI cannot be provided, for example where an analog system is connected to a digital network.
•
The PCLI field includes a two-digit number to identify the type of switch. The operator may allocate
values in this field for network use.
•
The PCLI field also includes a three-digit number, which uniquely identifies the public network
operators (PNOs). Some operators can have more than one PNO identity. The PNO identity is
included in a register of PNO identities so that operators can be identified for administrative
purposes, such as malicious call identification.
•
The operator's individual switch is identified by a three-digit number that is allocated by the central
administration.
Use of the information included in the PCLI fields enables a call to be traced back to an individual
switch. Table 1 provides an indication of the parameters presented for single (when the
CliSelectionForCodeofPractice3 property is set to 1) and dual (when the
CliSelectionForCodeofPractice3 property is set to 2) CLI configurations.
Cisco MGC Software Release 9.5(2)
2
Support of Partial CLI and CLI Code of Practice Edition 3
Feature Overview
Table 1
Property Selection and Output Presentation
PN
GN
CLI
Property
Value
Parameters Presented
PN
GN
CLI
1
CLI (PN)
PN
—
CLI
1
CLI (PN)
—
GN
CLI
1
CLI (GN)
—
—
CLI
1
CLI (CLI)
—
—
—
1
—
PN
GN
CLI
2
CLI
GN (PN)
PN
—
CLI
2
CLI
GN (PN)
—
GN
CLI
2
CLI
GN (GN)
—
—
CLI
2
CLI
—
—
—
2
—
CLI - calling line identification
GN - generic number (includes additional calling number or
presentation number, if present
PN - presentation number
COP can achieve the following objectives:
•
Providing the PCLI information to a succeeding exchange if the originating side of the call to an
MGC does not contain any CLI-related information and the terminating side of the call uses the UK
ISUP protocol variant.
•
Providing the CLI-related information, based on the COP Edition 3 (COP3), to a succeeding
exchange if the originating side of the call to an MGC uses the UK ISUP protocol variant.
For a single-host MGC configuration, the information needed to generate the PCLI and CLI COP3 data
is available from the originating call side. It is to be used by the terminating call side of the MGC.
For a continuous-service (redundant) host MGC configuration, the parameter contents used in the egress
MGC before the call reaches the terminating side’s protocol, are placed inside the Generic Parameter
Carrier (GPC) parameter that is sent from the ingress MGC by an EISUP link. The GPC parameter allows
protocol-specific parameters to be visible in the Extended ISUP (EISUP) message and prevents the
parameter ID conflict, which arises because national parameters are carried within the Unrecognized
Parameter (UP) buffer.
The UK ISUP Partial CLI (PCLI), Presentation Number (PN), and National Forward Call Indicator
(NFCI) parameters are placed in the GPC parameter and carried by the outgoing Initial Address Message
(IAM) from the ingress MGC to the egress MGC.
Related Documents
This document contains information that is related strictly to this 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.5(2)
•
Cisco Media Gateway Controller Hardware Installation Guide
Cisco MGC Software Release 9.5(2)
3
Support of Partial CLI and CLI Code of Practice Edition 3
Supported Platforms
•
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
•
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 Management Information Base Guide
•
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide
Supported Platforms
The hardware platforms supported for the Cisco MGC software Release 9.5(2) are described in the Cisco
Media Gateway Controller Hardware Installation Guide.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature. However, the following standard provides
information regarding PCLI management.
•
NICC Document, ND1108: 2000/09, PNO-ISC/INFO/008—Management of Partial Calling Line
Identity
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 Software Release 9 Management Information Base Guide.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites for Using This Feature
You must have Cisco MGC software Release 9.5(2). Prerequisites for this release can be found in the
Release Notes for the Cisco Media Gateway Controller Software Release 9.5(2).
Cisco MGC Software Release 9.5(2)
4
Support of Partial CLI and CLI Code of Practice Edition 3
Configuration Tasks
Configuration Tasks
This section contains the steps necessary for configuration of the Cisco MGC software to support this
feature. If you are installing and configuring the Cisco MGC software on your system for the first time,
use the procedures in the Cisco Media Gateway Controller Software Release 9 Installation and
Configuration Guide. Come back to this section once you encounter the *.PartialCliTypeOfSwitch
parameter in the XECfgParm.dat file.
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 shutdown. In a continuous service system, your system
loses the ability to maintain calls during a critical event if the system software on one of the PGW hosts
is shut down.
Caution
Do not modify the other XECfgParm.dat parameters associated with this feature.
To configure the XECfgParm.dat parameters, perform the following steps:
Step 1
If you have not already done so, open the /opt/CiscoMGC/etc/XECfgParm.dat file on the active and
standby Cisco PGW hosts, using a text editor, such as vi.
Step 2
If you have not already done so, ensure that the pom.dataSync parameter is set to false on the active and
standby Cisco PGW hosts.
Step 3
Search for the *.PartialCliTypeOfSwitch parameter and enter the switch type value on the active and
standby Cisco PGW hosts.
Step 4
Search for the *.PartialCliPnoIdentity parameter and enter the 3-digit PNO identity value on the active
and standby Cisco PGW hosts.
Step 5
Search for the *.PartialCliSwitchNumber parameter and enter the 3-digit switch number value on the
active and standby Cisco PGW hosts.
Step 6
If you are installing and configuring your Cisco MGC software for the first time, return to the Cisco
Media Gateway Controller Software Release 9 Installation and Configuration Guide and continue from
where you left off.
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
•
Provisioning Prerequisites, page 6
•
Provisioning Procedures, page 6
•
Platform Troubleshooting, page 10
Cisco MGC Software Release 9.5(2)
5
Support of Partial CLI and CLI Code of Practice Edition 3
Provisioning Tasks
Provisioning Prerequisites
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.
Collecting PCLI Data
The Support of Partial CLI and CLI Code of Practice Edition 3 feature represents the process performed
when incoming calling information is not present or is incomplete. When provisioning this feature, you
must be ready to enter the following data:
•
MML name
•
Type of switch
•
PNO identity
•
Switch number
•
CLI selection for COP3
You can define the parameters for your PCLI in Table 5 in the “New and Modified Properties” section
on page 13.
Provisioning Procedures
Provision the Support of Partial CLI and CLI Code of Practice Edition 3 feature for calls that enter or
exit the Cisco PGW 2200.
The provisioning determines that action that is taken for calls that ingress or egress the Cisco PGW 2200.
This section covers the following provisioning topics:
•
Provisioning Basics, page 11
Provisioning Basics
The procedures described in this section tell you how to start a provisioning session and how to save and
activate the changes you have made.
•
Starting a Provisioning Session, page 6
•
Saving and Activating Your Provisioning Changes, page 7
•
Ending a Provisioning Session Without Saving and Activating Your Changes, page 8
•
Retrieving Provisioning Data, page 8
For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
If you need to start a provisioning session as part of your system operations, log in to the active Cisco
MGC, start an MML session, and enter the following command:
mml> prov-sta::srcver=”curr_ver”,dstver=”mod_ver”
Where:
Cisco MGC Software Release 9.5(2)
6
Support of Partial CLI and CLI Code of Practice Edition 3
Provisioning Tasks
•
curr_ver—The name of the current configuration version. In place of the name of the current
configuration version, you can also enter:
– new—A new default session configuration; no existing source configuration is available.
– active—Selects the active configuration as the source for configuration changes.
Note
•
Caution
If you do not know the name of your current configuration session, you can use the procedure
described in the “Retrieving Data on the Current Provisioning Session” section on page 7.
mod_ver—The name of a new configuration version that contains your provisioning changes.
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.
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you
would enter the following command:
mml> prov-sta::srcver=”ver1”,dstver=”ver2”
Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML
commands to add, modify, and delete components on your system. This document describes how to
provision this feature. For more information on provisioning other components on your Cisco MGC,
refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session:
•
Saving and activating your provisioning changes, as described in the “Saving and Activating Your
Provisioning Changes” section on page 7
•
Ending your provisioning session without saving and activating your changes, as described in the
“Ending a Provisioning Session Without Saving and Activating Your Changes” section on page 8
Saving and Activating Your Provisioning Changes
When you have completed making provisioning changes in your session, you must enter a command to
save and activate your changes. There are two different provisioning MML commands that do this:
prov-cpy and prov-dply.
Caution
Using the prov-cpy and prov-dply MML commands can severely impact your system’s call processing
performance, depending on the extent of your provisioning changes. We recommend that these
commands be issued during a maintenance window when traffic is minimal.
The prov-cpy MML command is used to save and activate your changes on simplex Cisco MGC
(single-host) systems.
Note
When you enter the prov-cpy command, your provisioning session is also automatically ended. If you
want to make additional provisioning changes, you must start a new provisioning session, as described
in the “Starting a Provisioning Session” section on page 6.
Cisco MGC Software Release 9.5(2)
7
Support of Partial CLI and CLI Code of Practice Edition 3
Provisioning Tasks
Caution
Do not use the prov-cpy command to save and activate your changes on a continuous-service
Cisco MGC system (one with active and standby hosts). Saving and activating using prov-cpy on such
a system would require using the prov-sync MML command to synchronize the provisioning data on the
active and standby hosts. The system does not indicate when the synchronization process fails, which
would create problems when a switchover operation occurs.
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs in a continuous-service system. Do not use this command on a Cisco MGC in a simplex
configuration.
Note
When you enter the prov-dply command, your provisioning session is also automatically ended, unless
an error occurs during execution. If you want to make additional provisioning changes, you must start a
new provisioning session, as described in the “Starting a Provisioning Session” section on page 6.
Ending a Provisioning Session Without Saving and Activating Your Changes
If you want to end a provisioning session without saving and activating the changes you have entered,
enter the prov-stp MML command. This command ends your current provisioning session, and your
changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning
settings. The ways you can use this command to retrieve provisioning data are described in the following
sections:
•
Retrieving Data for an Individual Component, page 8
•
Retrieving Data for All Components, page 9
•
Retrieving Data for All Components of a Particular Type, page 9
•
Retrieving Data on the Current Provisioning Session, page 9
•
Retrieving Data on Supported Signaling Protocols, page 9
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component on your system. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:component:name=MML_name
Where:
•
component—The MML component type associated with the desired component. You can find a
complete list of MML component types in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
•
MML_name—The MML name for the desired component. You can determine the MML names for
the various components using the prov-rtrv:all MML command.
For example, to view the provisioning data for an SS7 signaling service called ss7svc1, you would enter
the following command:
mml> prov-rtrv:ss7path:name="ss7svc1"
Cisco MGC Software Release 9.5(2)
8
Support of Partial CLI and CLI Code of Practice Edition 3
Provisioning Tasks
The response to the command depends on the component type associated with the desired component.
For example, to view the properties for an SUA routing key called suakey1, you would enter the
following command:
mml> prov-rtrv:suakey:name="suakey1"
Retrieving Data for All Components
You can retrieve data on all of the components provisioned on your system. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:all
Retrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log
in to the active Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:component:”all”
Where:
•
component—The MML component type associated with the desired component group. You can find
a complete list of MML component types in the Cisco Media Gateway Controller Software
Release 9 Provisioning Guide.
For example, to view the provisioning data for all SS7 signaling services, you would enter the following
command:
mml> prov-rtrv:ss7path:"all"
Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:session
The system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2003-01-13 13:39:19
M RTRV
"session=jtest:session"
/*
Session ID = mml1
SRCVER = active
DSTVER = jtest
*/
Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
mml> prov-rtrv:variants
Cisco MGC Software Release 9.5(2)
9
Support of Partial CLI and CLI Code of Practice Edition 3
Provisioning Tasks
Modifying Components
The following section contains the procedure for modifying the various PCLI parameters in your
Cisco MGC provisioning data:
•
Modifying CliSelectionForCodeOfPractice3, page 10
Modifying CliSelectionForCodeOfPractice3
To edit the CliSelectionForCodeOfPractice3 of a Cisco MGC, perform the following steps:
Step 1
Start a provisioning session, as described in the “Starting a Provisioning Session” section on page 6.
Step 2
Modify the CliSelectionForCodeOfPractice3 methods on a trunk group with the following command:
mml> prov-ed:trnkgrpprop:name="trnkgrpnum",custgrpid="grpid",
CliSelectionForCodeOfPractice3=2
For example, to enable the CliSelectionForCodeOfPractice3 using single CLI selection on a trunk group
named 3333, you would enter the following command:
mml> prov-ed:trnkgrpprop:name="3333",custgrpid="1111",CliSelectionForCodeOfPractice3=1
If there are no other components that you need to provision, end your provisioning session.
Step 3
Repeat Step 2 for each Cisco MGC trunk group you want to modify in your provisioning data before
proceeding to the next step.
Step 4
If there are no other components that you need to provision, end your provisioning session, as described
in the “Saving and Activating Your Provisioning Changes” section on page 7.
Platform Troubleshooting
The following section contains procedure related to resolving problems with the Cisco MGC platform:
•
Rebooting Software to Modify Configuration Parameters, page 10
Rebooting Software to Modify Configuration Parameters
Sometimes you might need to change your configuration settings in the XECfgParm.dat file while the
system is in-service. To do this, perform the following procedure:
Caution
Step 1
Performing this procedure stops the functioning of the Cisco MGC software. Perform this step only
while in contact with Cisco Technical Assistance Center (TAC) personnel. Refer to the “Obtaining
Technical Assistance” section on page 16 for information on contacting the Cisco TAC.
Log in to the standby Cisco MGC and change directories to the etc subdirectory by entering the
following UNIX command:
cd /opt/CiscoMGC/etc
Step 2
Open the XECfgParm.dat file using a text editor, such as vi.
Cisco MGC Software Release 9.5(2)
10
Support of Partial CLI and CLI Code of Practice Edition 3
Configuration Examples
Step 3
Search for the partial CLI parameters and verify that their values are set correctly. If they are set
correctly, proceed to Step 10. Otherwise, proceed to Step 4 to begin correcting your configuration.
Step 4
Modify the incorrect parameter values identified in Step 3 to match their correct values.
Step 5
Save your changes and close the text editor.
Step 6
Stop the Cisco MGC software on your standby Cisco MGC by entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 7
Restart the Cisco MGC software on your standby Cisco MGC, manually start the Cisco MGC software
on the standby Cisco MGC by entering the following command:
/etc/init.d/CiscoMGC start
Step 8
Perform a manual switchover from the active Cisco MGC by starting an MML session, and entering the
following command:
mml> sw-over::confirm
Site alarms are automatically set until the out-of-service (OOS) Cisco MGC host is returned to an
in-service (IS) state.
Caution
Step 9
Switchover operations cause the loss of all SS7 messages transmitted to the Cisco MGC for
approximately three seconds. This affects unstable in-progress calls as well as new calls. Stable
in-progress calls are not affected.
Repeat Step 1 through Step 8 for the newly standby Cisco MGC.
If that resolves the problem, the procedure is complete. Otherwise, proceed to Step 10.
Step 10
Contact the Cisco TAC to further analyze the problem and determine a solution. For more information
about contacting the Cisco TAC, refer to the “Obtaining Technical Assistance” section on page 16.
Configuration Examples
This section provides a configuration example for the XECfgParm.dat parameters associated with this
feature. Additional configuration examples for the Cisco MGC software can be found in the Cisco Media
Gateway Controller Software Release 9 Installation and Configuration Guide.
Note
Configuration of XECfgParm.dat parameters for this feature is required only when the Cisco MGC is
configured for PCLI operation. The following example indicates the default values for PCLI support.
*.PartialCliTypeOfSwitch = 0
*.PartialCliPnoIdentity = 0
*.PartialCliSwitchNumber = 0
Cisco MGC Software Release 9.5(2)
11
Support of Partial CLI and CLI Code of Practice Edition 3
Reference Information
Reference Information
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
XECfgParm.dat Parameters, page 12
•
Billing Interface, page 12
•
New and Modified Properties, page 13
•
Provisioning Worksheets, page 14
XECfgParm.dat Parameters
The XECfgParm.dat file configuration parameters added for this feature are in the table below. For
information on the other XECfgParm.dat parameters, refer to the Cisco Media Gateway Controller
Software Release 9 Installation and Configuration Guide.
Note
The following XECfgParm.dat parameters are used only if the PCLI parameter is not received in the
incoming IAM.
Configuration Parameter
Definition
*.PartialCliTypeOfSwitch
Contains a 2-digit integer representing the Type of Switch
field of the partial CLI parameter.
Valid values: 0 (default) through 99
*.PartialCliPnoIdentity
Contains a 3-digit integer representing the PNO Identity
field of the partial CLI parameter.
Valid values: 0 (default) through 999
*.PartialCliSwitchNumber
Contains a 3-digit integer representing the Switch Number
field of the partial CLI parameter.
Valid values: 0 (default) through 999
Billing Interface
This section identifies the call detail record (CDR) data added for this feature. For billing interface
information for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller
Software Release 9 Billing Interface Guide.
Note
The 4220 CDR tag is populated only when the terminating side protocol is UK ISUP (ISUPV3_UK) and
contains the optional parameter (partial calling party number). CDR 4220 is generated when partial
calling party number is received in the incoming IAM; or when no partial calling party number is
received All this is valid for only UK ISUP when the PCLI feature is enabled.
Cisco MGC Software Release 9.5(2)
12
Support of Partial CLI and CLI Code of Practice Edition 3
Reference Information
Partial CLI (Tag: 4220)
Table 2
Partial CLI Description Form
Name: Partial CLI
Tag: 4220
Source: MDL
Description/Purpose: The partial calling line identity, being sent out on line by the MGC, is recorded in this tag. This value
is generated by the MGC in the event that no CLI information is received from the incoming call.
Format: Hex
Length in Octets: 9
Data Value:
The PCLI field holds the partial CLI parameter context, which has the format shown in Figure 1.
The “For bilateral agreement” octets contain either the IP address or the trunk group and member of the incoming call.
ANSI/ITU Variations: None.
Extended Data Value: No extended value.
General Information:
MGC Release: Release 9.5 and later.
Answered
(1010)
Deselected
(1020)
Aborted
(1030)
Release
(1040)
Interrupted
(1050)
Ongoing
(1060)
Maintenance
(1070)
External DB End of Call
(1080)
(1110)
Y
N
Y
N
N
Y
N
N
Figure 1
Y
PCLI Field Structure
8
7
6
5
4
3
2
1
Type of Switch (BCD)
1
D2 (units digit)
D1 (tens digit)
2
D2 (tens digit)
D1 (hundreds digit)
Switch Number (BCD)
PNO Identity (BCD)
PNO Identity (BCD)
3
D1 (hundreds digit)
D3 (units digit)
Switch Number (BCD)
D3 (units digit)
D2 (tens digit)
5
For bilateral agreement
6
For bilateral agreement
7
For bilateral agreement
8
For bilateral agreement
9
For bilateral agreement
116347
4
New and Modified Properties
The properties in this section are used for the Support of Partial CLI and CLI Code of Practice Edition
3 feature. For information on other properties for the Cisco MGC software, refer to the Cisco Media
Gateway Controller Software Release 9 Provisioning Guide.
Cisco MGC Software Release 9.5(2)
13
Support of Partial CLI and CLI Code of Practice Edition 3
Reference Information
The parent objects for the properties involved in this feature are found in Table 3.
Table 3
Software Properties Related to this Feature
CliSelectionForCodeOfPractice3
VSI
TrunkGroup
TCAPOverIP
TALI-IOCC
SS7-UK
SS7-Japan
SS7-ITU
SS7-China
SS7-ANSI
SGCP
SESSION
RLM
MGCP
ISDNPRI
IOCC
EISUP
Property Name
DPNSS
AVM
Parent Object
X
The new and modified properties used for the Support of Partial CLI and CLI Code of Practice Edition
3 feature are listed in Table 4.
Table 4
Properties
Property
Definition
CliSelectionForCodeOfPractice3
Provisions on a per trunk group basis the level of CLI selection
that is used when sending the calling line identities (such as
Calling Party Number or Generic Number parameter) to the
succeeding exchange. Valid range: 0 through 2.
Valid Values: 0—Indicates no specific CLI selection (default)
1—Indicates single CLI selection. Sends only the CLI.
2—Indicates dual CLI selection. Sends the CLI; or the CLI and
the PN.
Default value: 0
This property is supported in Cisco MGC software
Release 9.5(2) and higher.
CLISelect
For the UK ISUP protocol variant, this property has no effect,
beginning in MGC software Release 9.5(2).
Provisioning Worksheets
This section contains worksheets for the provisioning components required for this feature. For
worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Table 5
Partial CLI Code of Practice Worksheet Example
Name
CustgrpId
COP3 Selection Switch Type
PNO Identity
Switch Number
3333
1111
2
4
37
Cisco MGC Software Release 9.5(2)
14
2
Support of Partial CLI and CLI Code of Practice Edition 3
Obtaining Documentation
Table 5
Partial CLI Code of Practice Worksheet Example (continued)
Name
CustgrpId
COP3 Selection Switch Type
PNO Identity
Switch Number
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical
resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
http://www.cisco.com
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM
package, which may have shipped with your product. The Documentation CD-ROM is updated regularly
and may be more current than printed documentation. The CD-ROM package is available as a single unit
or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number
DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order annual or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
Click Subscriptions & Promotional Materials in the left navigation bar.
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
Cisco MGC Software Release 9.5(2)
15
Support of Partial CLI and CLI Code of Practice Edition 3
Documentation Feedback
You can order Cisco documentation in these ways:
•
Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from
the Networking Products MarketPlace:
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Nonregistered Cisco.com users can order documentation through a local account representative by
calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in
North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit e-mail comments about technical documentation to [email protected].
You can submit comments by using the response card (if present) behind the front cover of your
document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco
Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services,
online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for
technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
Cisco TAC Website
The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical
issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365
days a year. The Cisco TAC website is located at this URL:
http://www.cisco.com/tac
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you
have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet
access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2
cases to help keep your business operations running smoothly.
Cisco MGC Software Release 9.5(2)
16
Support of Partial CLI and CLI Code of Practice Edition 3
Obtaining Technical Assistance
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Opening a TAC Case
Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are
those in which your network is minimally impaired or for which you require product information.) After
you describe your situation, the TAC Case Open Tool automatically recommends resources for an
immediate solution. If your issue is not resolved using the recommended resources, your case will be
assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:
http://www.cisco.com/tac/caseopen
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely
degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers
are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You
and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your
business operation are negatively affected by inadequate performance of Cisco products. You and Cisco
will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations
remain functional. You and Cisco will commit resources during normal business hours to restore service
to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or
configuration. There is little or no effect on your business operations.
Cisco MGC Software Release 9.5(2)
17
Support of Partial CLI and CLI Code of Practice Edition 3
Obtaining Additional Publications and Information
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online
and printed sources.
•
The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as
ordering and customer support services. Access the Cisco Product Catalog at this URL:
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
Cisco Press publishes a wide range of general networking, training and certification titles. Both new
and experienced users will benefit from these publications. For current Cisco Press titles and other
information, go to Cisco Press online at this URL:
http://www.ciscopress.com
•
Packet magazine is the Cisco quarterly publication that provides the latest networking trends,
technology breakthroughs, and Cisco products and solutions to help industry professionals get the
most from their networking investment. Included are networking deployment and troubleshooting
tips, configuration examples, customer case studies, tutorials and training, certification information,
and links to numerous in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/packet
•
iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet
business strategies for executives. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
•
Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering
professionals involved in designing, developing, and operating public and private internets and
intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
Training—Cisco offers world-class networking training. Current offerings in network training are
listed at this URL:
http://www.cisco.com/en/US/learning/index.html
Glossary
Table 6 contains definitions of acronyms and technical terms used in this feature module.
Table 6
Acronyms and Definitions
Acronym
Definition
CC
call context
CgPN
calling party number
CLI
calling line identity
COP
Code of Practice
COP3
COP Edition 3
GPC
Generic Parameter Carrier
GTD
Generic Transparency Descriptor
IAM
Initial Address Message
Cisco MGC Software Release 9.5(2)
18
Support of Partial CLI and CLI Code of Practice Edition 3
Glossary
Table 6
Acronyms and Definitions
Acronym
Definition
MGC
Cisco Media Gateway Controller
NFCI
National Forward Call Indicators
PCLI
partial CLI
PGW
PSTN gateway
PN
presentation number
PNO
public network operators
SC
signaling controller
UP
unrecognized parameter
VSC
virtual switch controller
Cisco MGC Software Release 9.5(2)
19