Support for QSIG and DPNSS Signaling
Interworking for Cisco Unity
Document Release History
Publication Date
Comments
June 11, 2004
Initial version of the document.
Feature History
Release
Modification
Release 9.4(1)
This feature is introduced as part of a patch to this release.
Release 9.5(2)
This feature is included in the software with this release.
This document describes the Support for Q Signaling (QSIG) and Digital Private Network Signaling System
(DPNSS) Signaling Interworking for Cisco Unity feature. This feature is described in the following sections:
•
Feature Overview, page 2
•
Supported Platforms, page 5
•
Supported Standards, MIBs, and RFCs, page 5
•
Prerequisites for Using This Feature, page 5
•
Provisioning Tasks, page 6
•
Provisioning Examples, page 27
•
Reference Information, page 29
•
Obtaining Documentation, page 40
•
Documentation Feedback, page 41
•
Obtaining Technical Assistance, page 41
•
Obtaining Additional Publications and Information, page 43
•
Glossary, page 43
Cisco MGC Software Release 9.5(2)
1
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Feature Overview
Feature Overview
This feature provides enables Cisco Unity to provide unified messaging services to QSIG and DPNSS
private branch exchanges (PBXs). The Cisco Media Gateway Controller (MGC) provides the signaling
interworking between the platforms, providing a Session Initiation Protocol (SIP) interface to the
Cisco Unity and an E1/QSIG or DPNSS interface to the Voice over IP (VoIP) gateway connected to the
PBX.
SIP Method Support
The following SIP methods are used by this feature:
•
REFER—Indicates that the recipient (identified by the Request-URI) should contact a third party
using the contact information provided in the request.
•
Unsolicited NOTIFY—Used to transport subscribed event notification.
You can find more information on the these methods in the SIP Service Enhancements feature module.
QSIG Support
This feature supports ECMA QSIG version 2.0. QSIG support on the Cisco MGC is enhanced to support
the following:
•
Message waiting indicator (MWI)—This supplementary service enables a Served User to be sent a
MWI and also enables this MWI to be cancelled. This feature enables the transport of QSIG MWI
strings towards a QSIG PBX to support the MWI supplementary service.
•
MWI facility message support—The implementation of MWI on some PBXs deviates from the
QSIG MWI standard. This feature introduces a MWI facility information element message values
flag that can be set to ensure proper MWI functioning with these PBXs.
•
Blind Transfer Support—Also known as Single-Step Call Transfer (SSCT). This supplementary
service enables a user (user A) to transfer (or transform) an existing call between two parties (user
A and user B) into a new call between the other user (user B) and a new user (user C). SSCT permits
this call transformation to occur prior to a formal call establishment between user A and user C.
SSCT enables access the Auto Attendant features of the Cisco Unity.
DPNSS Support
DPNSS support on the Cisco MGC is enhanced to support the following:
•
MWI via Non-Specified Information (NSI) supplementary service—The NSI supplementary service
enables you to use DPNSS to implement network-dependent features and functions. This feature
uses this supplementary service to deliver DPNSS MWI strings from the Cisco Unity to the DPNSS
PBX.
•
MWI NSI value string support—This feature enables you to set MWI NSI string values.
You can find more information on MWI via NSI in the DPNSS Supplementary Services Interworking
with Cisco CallManager feature module.
Cisco MGC Software Release 9.5(2)
2
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Feature Overview
Benefits
This feature provides the benefit described below.
Expansion of messaging services for legacy PBXs
.This feature enables owners of QSIG and DPNSS PBXs to provide current unified messaging services
to their end-users through the Cisco Unity.
Restrictions
This feature requires a data pathway to a VoIP gateway connected to a QSIG/DPNSS PBX. The
following VoIP gateways are supported by this feature:
Note
The MML names for the VoIP gateways listed below can be found in the “External Node Types” section
on page 31.
•
QSIG PBX
– Cisco 1751
– Cisco 1760
– Cisco 2600
– Cisco 2610 XM
– Cisco 2611 XM
– Cisco 2620 XM
– Cisco 2621 XM
– Cisco 2650 XM
– Cisco 2651 XM
– Cisco 2691
– Cisco 3600 access server
– Cisco 3640
– Cisco 3640 A
– Cisco 3660
– Cisco 3660 access server
– Cisco 3725
– Cisco 3745
– Cisco 5300 access server
– Cisco 5350 access server
– Cisco 5400 access server
– Cisco 5800 access server
– Cisco 5850 access server
– Cisco 7200 access server
Cisco MGC Software Release 9.5(2)
3
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Feature Overview
•
DPNSS PBX
– Cisco 1751
– Cisco 1760
– Cisco 2600
– Cisco 2610 XM
– Cisco 2611 XM
– Cisco 2620 XM
– Cisco 2621 XM
– Cisco 2650 XM
– Cisco 2651 XM
– Cisco 2691
– Cisco 3600 access server
– Cisco 3640
– Cisco 3640 A
– Cisco 3660
– Cisco 3660 access server
– Cisco 3725
– Cisco 3745
– Cisco 5300 access server
– Cisco 5350 access server
– Cisco 5400 access server
Related Features
This feature is related to the following features:
•
SIP Service Enhancements
•
DPNSS Supplementary Services
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
•
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.5(2)
4
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Supported Platforms
•
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 that support the Cisco MGC software are described in the Cisco Media Gateway
Controller Hardware Installation Guide.
Supported Standards, MIBs, and RFCs
Standards
The following standards are associated with this feature:
•
BTNR-188, Section 15, “Non-Specified Information Supplementary Service
•
ECMA-242, “Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol Message Waiting Indication Supplementary Service (QSIG-MWI) “
•
ECMA-299, “Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Single Step Call Transfer Supplementary Service (SSCT-SD)”
•
ECMA-300, “Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Single
Step Call Transfer Supplementary Service (QSIG-SSCT)”
MIBs
No new or modified MIBs are supported by this feature. Existing MIBs are used to support this feature.
For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway
Controller Release 9 Management Information Base Guide.
RFCs
The following RFCs are associated with this feature:
•
RFC-3265, “SIP NOTIFY Method”
•
RFC-3515, “SIP REFER Method”
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)
5
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
•
Provisioning Prerequisites, page 6
•
Provisioning Procedures, page 11
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 Data to Provision DPNSS PBX Interworking
To prepare for provisioning signaling interworking between the Cisco Unity and a DPNSS PBX, perform
the following data collection procedures:
•
Collecting External Node Data, page 7
•
Collecting MGCP Path Data, page 7
•
Collecting DPNSS Path Data, page 8
•
Collecting DPNSS Path Property Data, page 8
•
Collecting SIP Path Data, page 8
•
Collecting SIP Path Property Data, page 8
•
Collecting IP Route Data (optional), page 9
•
Collecting MGCP IP Link Data, page 9
•
Collecting Association Data, page 10
•
Collecting SIP IP Link Data, page 11
Collecting Data to Provision QSIG PBX Interworking
To prepare for provisioning signaling interworking between the Cisco Unity and a QSIG PBX, perform
the following data collection procedures:
•
Collecting External Node Data, page 7
•
Collecting Session Set Data, page 7
•
Collecting MGCP Path Data, page 7
•
Collecting IP FAS Path Data, page 9
•
Collecting IP FAS Path Property Data, page 9
•
Collecting SIP Path Data, page 8
•
Collecting SIP Path Property Data, page 8
•
Collecting IP Route Data (optional), page 9
•
Collecting MGCP IP Link Data, page 9
•
Collecting D-Channel Data, page 10
Cisco MGC Software Release 9.5(2)
6
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
Collecting SIP IP Link Data, page 11
Data Collection Procedures
The sections below are the various data collection procedures you must perform before you provision
this feature.
Collecting External Node Data
This component type represents another node with which the MGC communicates. You must be ready
to enter the following data about the node:
•
MML name
•
Component description
•
The type of the external node
•
ISDN signaling type
You can define the parameters for your external nodes in Table 4.
Collecting Session Set Data
This component type represents another node with which the MGC communicates. You must be ready
to enter the following data about the session set:
•
MML name
•
Component description
•
MML name of the associated external node
•
IP address
•
Peer IP address
•
Port
•
Peer port
•
Type
You can define the parameters for your session set in Table 5.
Collecting MGCP Path Data
This component type represents a MGCP signaling service to a particular Cisco voice gateway. Refer to
the “Restrictions” section on page 3 for more information on the Cisco VoIP gateway that can be used
to setup this feature. You must be ready to enter the following data:
•
MML name
•
Component description
•
MML name of the associated external node
You can define the parameters for your MGCP signaling services in Table 6.
Cisco MGC Software Release 9.5(2)
7
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Collecting DPNSS Path Data
This component type represents a DPNSS signaling service to a particular Cisco VoIP gateway. Refer to
the“Restrictions” section on page 3 for more information on the Cisco VoIP gateways that can be used
for this feature. You must be ready to enter the following data:
•
Unique ID of this component and component name used in MML commands
•
Component description
•
MML name of the associated external node
•
Customer group ID
•
Identification of the DPNSS path as either A side, B side, or neither
•
Signaling port number (physical port on the Cisco access server)
•
Signaling port slot (physical slot on the Cisco access server)
You can define the parameters for your DPNSS signaling services in Table 7.
Collecting DPNSS Path Property Data
This component type represents properties for an existing DPNSS signaling service. All of the DPNSS
signaling service properties have default values. You must be ready to enter data for the properties you
are going to modify. For information on all of the DPNSS signaling service properties, refer to the Cisco
Media Gateway Controller Software Release 9 Provisioning Guide.
You can define the new values for the DPNSS signaling service properties in Table 8.
Collecting SIP Path Data
This component type represents a SIP data pathway. You must be ready to enter the following data:
•
Unique ID of this component and component name used in MML commands
•
Component description
•
MML name of the associated external node
•
Customer group ID
•
Identification of the DPNSS path as either A side, B side, or neither
•
Signaling port number (physical port on the Cisco access server)
•
Signaling port slot (physical slot on the Cisco access server)
You can define the parameters for your SIP pathways in Table 9.
Collecting SIP Path Property Data
This component type represents properties for an existing SIP data pathway. All of the SIP pathway
properties have default values. You must be ready to enter data for the properties you are going to
modify. For information on all of the SIP pathway properties, refer to the Cisco Media Gateway
Controller Software Release 9 Provisioning Guide.
You can define the new values for the SIP data pathway service properties in Table 10.
Cisco MGC Software Release 9.5(2)
8
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Collecting IP FAS Path Data
This component type represents an IP Feature Associated Signaling (FAS) signaling service to a
particular Cisco VoIP gateway. Refer to the “Restrictions” section on page 3 for more information on the
Cisco VoIP gateways that can be used for this feature. You must be ready to enter the following data:
•
MML name
•
Component description
•
MML name of the associated external node
•
Q.931 call model side (user or network)
•
MDO file name
•
Customer group ID
•
A-B flag
•
Call reference length (0 through 2 bytes)
You can define the parameters for your ISDN FAS signaling services in Table 11.
Collecting IP FAS Path Property Data
This component type represents properties for an existing IP FAS signaling service. All of the IP FAS
signaling service properties have default values. You must be ready to enter data for the properties you
are going to modify. For information on all of the IP FAS signaling service properties, refer to the Cisco
Media Gateway Controller Software Release 9 Provisioning Guide.
You can define the new values for the IP FAS signaling service properties in Table 12.
Collecting IP Route Data (optional)
This component type represents a static IP route. IP routes are required for this feature only when the
Cisco MGC hosts are not on the same subnet as the Cisco media gateways. If your system requires IP
routes, you must be ready to enter the following data for each route:
•
MML name
•
Component description
•
Destination host name or IP address
•
Subnet mask of destination (optional)
•
Next hop router IP address
•
Local IP address
•
Priority
You can define the parameters for your IP routes in Table 13.
Collecting MGCP IP Link Data
This component type represents a link to a media gateway control protocol (MGCP) device. You must
be ready to enter the following data:
•
MML name
•
Component description
•
Port
Cisco MGC Software Release 9.5(2)
9
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
Priority
•
IP address
•
Associated MGCP signaling service
You can define the parameters for your MGCP IP links in Table 14.
Collecting D-Channel Data
This component type represents the connection between the Cisco MGC and a Cisco VoIP gateway. You
must be ready to enter the following data:
•
MML name
•
Description of this component
•
Signaling type
•
Priority
•
MML name of associated MGCP IP link
•
Physical slot number on voice gateway
•
Physical port number for slot on voice gateway
•
Local subunit
You can define the parameters for your D-channels in Table 15.
Collecting Association Data
This component type represents the connection between the Cisco MGC and a Cisco access server. You
must be ready to enter the following data:
•
MML name of the association.
•
Description of this component.
•
Signaling type.
•
MML name of the signaling gateway process.
•
First local address.
•
Second local address (optional).
•
Local port number (optional).
•
The highest priority destination address.
•
The lowest priority destination address (optional).
•
Destination port number. (optional).
•
MML name of the external node.
•
MML name of first IPROUTE (optional).
•
MML name of second IPROUTE (optional).
•
Number of bytes to advertise for the local receive window (optional).
•
Maximum number of times to retransmit INIT message (optional).
•
Maximum initial timer retransmission value (optional).
•
Maximum number of retransmissions over all destination addresses before the association is
declared failed (optional).
Cisco MGC Software Release 9.5(2)
10
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
Maximum time after a datagram is received before a SACK is sent (optional).
•
Maximum time waits for other outgoing datagrams for bundling (optional).
•
Minimum value allowed for the retransmission timer (optional).
•
Maximum value allowed for the retransmission timer (optional).
•
Time between heartbeats. The heartbeat is this value plus the current retransmission timeout value
(optional).
•
Internet protocol precedence. This value is placed in the IP PRECEDENCE portion of the Type Of
Service field for outgoing datagrams (optional).
•
Differential Service Code Point (DSCP). This value is placed in the DSCP portion of the Type Of
Service field for outgoing datagrams (optional).
•
Maximum number of retransmissions to either PEERADDR1 or PEERADDR2 before it is declared
failed (optional).
The SCTP association component structure is shown in Table 16.
Collecting SIP IP Link Data
This component type represents a link to a SIP device. You must be ready to enter the following data:
•
MML name
•
Component description
•
Port
•
Priority
•
IP address
•
Associated SIP data pathway
You can define the parameters for your SIP IP links in Table 17.
Provisioning Procedures
This section covers the following provisioning topics:
•
Provisioning Basics, page 11
•
Enabling Signaling Interworking for Cisco Unity and DPNSS PBX, page 15
•
Enabling Signaling Interworking for Cisco Unity and QSIG PBX, page 15
•
Procedures, page 15
Provisioning Basics
The procedures in this section describe how to start a provisioning session and how to save and activate
the changes you have made.
•
Starting a Provisioning Session, page 12
•
Saving and Activating Your Provisioning Changes, page 12
•
Ending a Provisioning Session Without Activating Your Changes, page 13
•
Retrieving Provisioning Data, page 13
Cisco MGC Software Release 9.5(2)
11
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
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
You might need to start a provisioning session as part of your system operations. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
prov-sta::srcver=”curr_ver”,dstver=”mod_ver”
Where:
•
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
•
If you do not know the name of your current configuration session, you can use the procedure in
the “Retrieving Data on the Current Provisioning Session” section on page 14.
mod_ver—A new configuration version name that contains your provisioning changes.
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:
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 12 or ending
your provisioning session without saving and activating your changes, as described in the “Ending a
Provisioning Session Without Activating Your Changes” section on page 13.
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 or prov-dply MML command 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.
Cisco MGC Software Release 9.5(2)
12
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
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 12.
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 for any future switchover operations.
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. This command should not be used 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 12.
Ending a Provisioning Session Without Activating Your Changes
You may find that you want to end a provisioning session without saving and activating the changes you
have entered during your session. If this is the case, you can 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 in which you can use this command to retrieve provisioning data are described in the
following sections:
•
Retrieving Data for an Individual Component, page 13
•
Retrieving Data for All Components, page 14
•
Retrieving Data for All Components of a Particular Type, page 14
•
Retrieving Data on the Current Provisioning Session, page 14
•
Retrieving Data on Supported Signaling Protocols, page 14
Retrieving Data for an Individual Component
You can retrieve provisioning data for any individual component of your system. To do this, log in to the
active Cisco MGC, start an MML session, and enter the following command:
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.
Cisco MGC Software Release 9.5(2)
13
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
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 a SS7 signaling service called ss7svc1, you would enter
the following command:
prov-rtrv:ss7path:name="ss7svc1"
The response to the command is dependent upon the component type associated with the desired
component.
Retrieving Data for All Components
You can retrieve data for 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:
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:
prov-rtrv:component:”all”
Where component is 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:
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:
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:
prov-rtrv:variants
Cisco MGC Software Release 9.5(2)
14
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Enabling Signaling Interworking for Cisco Unity and DPNSS PBX
This section contains the procedures that you must perform to enable signaling interworking between
the Cisco Unity and a DPNSS PBX. When provisioning the components that enable the Cisco MGC to
support this type of signaling interworking, perform the procedures below:
1.
Preparing Platforms for Integration, page 16
2.
Adding Cisco VoIP External Nodes, page 16
3.
Adding MGCP Signaling Services, page 17
4.
Adding DPNSS Signaling Services, page 18
5.
Modifying DPNSS Properties for Communications with DPNSS PBXs, page 19
6.
Adding IP Routes (Optional), page 21
7.
Adding IP Routes (Optional), page 21
8.
Adding MGCP IP Links, page 23
9.
Adding Associations, page 25
10. Adding a SIP IP Link, page 24
Enabling Signaling Interworking for Cisco Unity and QSIG PBX
This section contains the procedures that you must perform to enable signaling interworking between
the Cisco Unity and a QSIG PBX. When provisioning the components that enable the Cisco MGC to
support this type of signaling interworking, perform the procedures below:
1.
Preparing Platforms for Integration, page 16
2.
Adding Cisco VoIP External Nodes, page 16
3.
Adding Session Sets, page 16
4.
Adding MGCP Signaling Services, page 17
5.
Adding IP FAS Signaling Services, page 19
6.
Adding IP Routes (Optional), page 21
7.
Modifying IP FAS and SIP Properties for Communication with QSIG PBXs, page 20
8.
Adding IP Routes (Optional), page 21
9.
Adding MGCP IP Links, page 23
10. Adding D-Channels, page 23
11. Adding a SIP IP Link, page 24
Procedures
The sections that follow are the provisioning procedures used to enable signaling interworking between
the Cisco Unity and a DPNSS/QSIG PBX.
Cisco MGC Software Release 9.5(2)
15
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Preparing Platforms for Integration
For this feature to work properly, the Cisco Unity and the selected PBX must be prepared to integrate
with the Cisco MGC. To do this, perform the procedures in the QSIG/DPNSS Phone System with Cisco
EGW 2200 Integration Guide for Cisco Unity 4.0. Once you reach the procedures for preparing the Cisco
EGW, return to this document and perform the Cisco MGC provisioning procedures.
Adding Cisco VoIP External Nodes
To add Cisco media gateway external nodes to your provisioning data, perform the following steps:
Step 1
Start a provisioning session as described in the “Starting a Provisioning Session” section on page 12.
Step 2
Enter the following command to add a Cisco VoIP gateway external node:
mml>prov-add:extnode:name="name", desc="description", type=”as”, isdnsigtype=”na”
Where:
•
name—The name you want to give to the external node. The name can be as many as 20 characters
long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
•
as—The MML name for the type of Cisco VoIP gateway. The valid values for this feature can be found
in the “Restrictions” section on page 3.
For example, to add a Cisco VoIP gateway external node named va-3640-01, enter the following
command:
mml>prov-add:extnode:name="va-3640-01", desc="QSIG PBX 3640", type="C3640",
isdnsigtype=”na”
Step 3
Repeat Step 2 for each Cisco BRI voice gateway external node you want to add to your provisioning data.
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 12.
Adding Session Sets
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to add a session set:
prov-add:sessionset:name="name", desc="description", extnode=”mgw”, ipaddr1=”addr1”,
[ipaddr2=”addr2”,] port=num, peeraddr1=”paddr1”, [peeraddr2=”paddr2”,] peerport=pnum,
[iproute1=”iprte1”, iproute2=”iprte2”,] type=stype
Where:
•
name—The name you want to give to the signaling service. The name can be as many as 20
characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin
with a letter.
•
description—The long name you assign to the service. It can be as many as 128 alphanumeric
characters in length.
•
mgw—MML name of a previously defined external node.
Cisco MGC Software Release 9.5(2)
16
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
addr1—First local IP address. The IP address should be one of the following property names defined
in the XECfgParm.dat file:
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
•
addr2—Second local IP address (optional). The IP address should be one of the following property
names defined in the XECfgParm.dat file (not including the value used for addr1):
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
•
num—Local port number. Valid values: 1025 through 65535.
•
paddr1—First remote IP address. Default value: 0.0.0.0. This may also be specified as a hostname
or a DNS name.
•
paddr2—Second remote IP address. Default value: 0.0.0.0. This may also be specified as a hostname
or a DNS name.
•
pnum—Remote port number. Valid values: 1025 through 65535.
•
iprte1—MML name of a previously defined IP route (optional).
•
iprte2—MML name of a previously defined IP route (optional).
•
stype—Session set type. Valid values: BSMV0 or IPFAS.
For example, to add a DPNSS signaling service named dpnsvc1, you would enter the following
command:
mml>prov-add:sessionset:NAME="c7-2600-1",EXTNODE="va-2600-stim1",IPADDR1="ip_addr1",
PEERADDR1="10.82.80.129",PORT=7000,PEERPORT=7000, TYPE="BSMV0"
Step 3
Repeat Step 2 for each DPNSS signaling service you want to add to your provisioning data.
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 12.
Adding MGCP Signaling Services
To add MGCP signaling services to your provisioning data, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to add a MGCP signaling service:
mml>prov-add:mgcppath:name="name", desc="description", extnode=”mgw”
Where:
Cisco MGC Software Release 9.5(2)
17
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
name—The name you want to give to the MGCP signaling service. The name can be as many as 20
characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin
with a letter.
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
•
mgw—MML name of a previously defined VoIP gateway external node.
For example, to add an MGCP signaling service named mgcpsvc1, you would enter the following
command:
mml>prov-add:mgcppath:name="mgcpsvc1",extnode="va-3640-01",desc="MGCP service to DPNSS
PBX"
Step 3
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 12.
Adding DPNSS Signaling Services
To add DPNSS signaling services, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to add a DPNSS signaling service:
prov-add:dpnsspath:name="name", desc="description", extnode=”mgw”, abflag=”side”,
sigport=portnum, sigslot=slotnum
Where:
•
name—The name you want to give to the signaling service. The name can be as many as 20
characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin
with a letter.
•
description—The long name you assign to the service. It can be as many as 128 alphanumeric
characters in length.
•
mgw—MML name of a previously defined external node.
•
side—DPNSS side for this signaling service (optional). Value values are A (for A side), B (for B
side), and N (for not applicable) (N).
•
portnum—Number for physical port on the access server (optional). Valid values: 0-167 (0).
•
slotnum—Number for physical slot on the access server (optional). Valid values: 0-63 (0).
For example, to add a DPNSS signaling service named dpnsvc1, you would enter the following
command:
mml>prov-add:dpnsspath:NAME="dpnsvc1",DESC="DPNSS PBX path", extnode="va-3660-20",
abflag=”a”, sigport=45, sigslot=10
Step 3
Repeat Step 2 for each DPNSS signaling service you want to add to your provisioning data.
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 12.
Cisco MGC Software Release 9.5(2)
18
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Modifying DPNSS Properties for Communications with DPNSS PBXs
To modify the DPNSS signaling service properties that enable interworking between Cisco Unity and
DPNSS PBXs, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to set the MWI activation number:
prov-add:sigsvcprop:name="sigsrv", MWIStringON="actnum"
Where:
•
sigsrv—MML name of a previously provisioned DPNSS signaling service.
•
actnum—MWI activation number. This value is a string, with a minimum length of 1 and a
maximum length of 32 characters.
For example, to set the MWI activation number to *171B#, you would enter the following command:
mml>prov-add:sigsvcprop:name="dpnss2", MWIStringON="*171B#"
Step 3
Enter the following command to set the MWI deactivation number:
prov-add:sigsvcprop:name="sigsrv", MWIStringOFF="deactnum"
Where:
•
sigsrv—MML name of a previously provisioned DPNSS signaling service.
•
deactnum—MWI activation number. This value is a string, with a minimum length of 1 and a
maximum length of 32 characters.
For example, to set the MWI deactivation number to *172B#, you would enter the following command:
mml>prov-add:sigsvcprop:name="dpnss2", MwiStringOFF="*172B#"
Step 4
Repeat steps 2 through 3 for each DPNSS signaling service that support your DPNSS PBXs.
Step 5
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 12.
Adding IP FAS Signaling Services
To add IP FAS signaling services to your provisioning data, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to add an IP FAS signaling service:
mml>prov-add:ipfaspath:name="name", desc="description", extnode=”mgw”, mdo=variant,
side=qside, custgrpid=”idnum”, abflag=”flag”, crlen=”callref”
Where:
•
name—The name you want to give to the signaling service. The name can be as many as 20
characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin
with a letter.
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
Cisco MGC Software Release 9.5(2)
19
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
mgw—MML name of a previously defined VoIP gateway external node.
•
variant—MDO filename.
•
qside—Q.931 call model side, user for user side and network for network side; (network).
•
idnum—VNET ID, a four-digit ID; (0000).
•
flag—IP FAS side; Valid values: ’a’ or ‘b’ side, ‘n’ for not applicable; (n).
•
callref—Call reference length; Valid values: 0 through 2. The value indicates the number of bytes
in the call reference length (0).
For example, to add an IP FAS signaling service named qsig1, you would enter the following command:
mml>prov-add:IPFASPATH:NAME="qsig1", DESC="backhaul", EXTNODE="qsig-gw1",
MDO="ETS_300_172", CUSTGRPID="1111", SIDE="network", ABFLAG="n", CRLEN=2
Step 3
Repeat Step 2 for each IP FAS signaling service you want to add to your provisioning data.
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 12.
Adding a SIP Signaling Service
The SIP signaling service is the connection between an MGC and a SIP server. To add a SIP signaling
service, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to add a SIP signaling service:
mml>prov-add:sippath:name="name", desc="description", mdo=”IETF_SIP”
Where:
•
name—The name you want to give to the IP route. The name can be as many as 20 characters long
and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
Step 3
Repeat Step 2 for each SIP signaling service you want to add to your provisioning data.
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 12.
Modifying IP FAS and SIP Properties for Communication with QSIG PBXs
To modify the IP FAS and SIP signaling service properties that enable interworking between Cisco Unity
and QSIG PBXs, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to set the duration for the MWI invoke timer:
prov-add:sigsvcprop:name="sigsrv", MWIInvokeTimerT1="timval"
Cisco MGC Software Release 9.5(2)
20
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Where:
•
sigsrv—MML name of a previously provisioned IP FAS signaling service.
•
timval—Value of the MWI invoke timer in milliseconds. The default value is 15,000 ms. The range
of valid values is any integer from 0 to 20000.
For example, to set the MWI invoke timer to 10,000 ms, you would enter the following command:
prov-add:sigsvcprop:name="qsig1", MWIInvokeTimerT1="10000"
Step 3
Enter the following command to set the duration for the SSCT invoke timer:
prov-add:sigsvcprop:name="sigsrv", SSCTInvokeTimerT1="timval"
Where:
•
sigsrv—MML name of a previously provisioned IP FAS signaling service.
•
timval—Value of the SSCT invoke timer in milliseconds. The default value is 50,000 ms. The range
of valid values is any integer from 50000 to 180000.
For example, to set the SSCT invoke timer to 10,000 ms, you would enter the following command:
prov-add:sigsvcprop:name="qsig1",SSCTInvokeTimerT1="55000"
Step 4
If the implementation of MWI on your QSIG PBX conforms to the ECMA standard, proceed to Step 5.
Otherwise, enter the following command to set tranfer await connect flag to support MWI on your PBX:
prov-add:sigsvcprop:name="sigsrv", TransferAwaitConnect="1"
Where sigsrv is the MML name of a previously provisioned IP FAS signaling service.
Step 5
Repeat steps 2 through 4 for each IP FAS signaling service that support your QSIG PBXs.
Step 6
Enter the following command to enable special handling of SSCT:
prov-add:sigsvcprop:name="sigsrv", SIPReferforSinglestepXfer="1"
Where sigsrv is the MML name of a previously provisioned SIP signaling service.
Step 7
Repeat Step 6 for each SIP signaling service that supports your QSIG PBXs.
Step 8
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 12.
Adding IP Routes (Optional)
IP routes are required in your provisioning data if your Cisco MGC hosts are not on the same subnet as
the Cisco media gateways. To add IP routes, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to add an IP route:
mml>prov-add:iproute:name="name", desc="description", netmask=”mask”, nexthop=”nhop”,
ipaddr=”addr”, dest=”destination”
Where:
•
name—The name you want to give to the IP route. The name can be as many as 20 characters long
and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
Cisco MGC Software Release 9.5(2)
21
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
•
mask—Subnet mask of the destination (optional). The value should be expressed as an IP address in
dotted decimal notation (default is 255.255.255.255).
•
nhop—Next hop router host name, IP address, or one of the following property names defined in the
XECfgParm.dat file:
– IP_NextHop
– IP_NextHop2
– IP_NextHop3
– IP_NextHop4
– IP_NextHop5
– IP_NextHop6
– IP_NextHop7
– IP_NextHop8
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
The IP address should be in dotted decimal notation, and the host name must be less than or equal
to 32 characters.
•
addr—Local IP address. The IP address should be one of the following property names defined in
the XECfgParm.dat file:
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
•
destination—Destination host name or IP address. The IP address should be in dotted decimal
notation and the host name must be less than or equal to 32 characters.
For example, to add an IP route named iprte1, you would enter the following command:
mml>prov-add:IPROUTE:NAME="iprte1", DESC="IP Route 1", dest="10.82.80.0",
ipaddr=”IP_Addr1”, netmask="255.255.255.0", nexthop="10.82.82.1"
Step 3
Repeat Step 2 for each IP route you want to add to your provisioning data.
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 12.
Cisco MGC Software Release 9.5(2)
22
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Adding MGCP IP Links
To provision MGCP IP links, perform the following steps:
Step 1
Enter the following command to provision a MGCP IP link:
mml>prov-add:iplnk:name="name", desc="description", ipaddr="addr1", peeraddr="addr2",
svc="sigsrv", port=lpnum, peerport=rpnum, iproute1="iprte1", pri=priority
Where:
•
name—The name you want to give to the component. The name can be as many as 20 characters
long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•
description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•
addr1—Local IP address for a LAN/WAN interface. IP address should be one of the following
property names defined in the XECfgParm.dat file:
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
•
addr2—Remote IP address, expressed in dotted decimal format. This value may also be specified as
a hostname or a DNS name.
•
sigsrv—The MML name of a previously provisioned MGCP signaling service.
•
lpnum—Local IP port number. Valid value is any integer above 1024. For MGCP IP links, we
recommend that you use 2427.
•
rpnum—Remote IP port number. Valid value is any integer above 1024. For MGCP IP links, we
recommend that you use 2427.
•
iprte1—MML name of a previously entered IP route (optional).
•
priority—Priority setting for this MGCP IP link. Valid value is any integer above 0. Default value
is 1.
For example, to provision a MGCP IP link, you would enter the following command:
mml>prov-add:splnk:name="mgcpsigchan1", ipaddr="IP_Addr1", peeraddr=”147.28.210.65”,
svc="mgcpsvc1", port=2427, peerport=2427, iproute1=iproute1, pri=1, desc="MGCP sigchan 1"
Step 2
Repeat Step 1 for each MGCP IP link you want to provision.
Step 3
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 12.
Adding D-Channels
To add D-channels to your provisioning data, perform the following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Cisco MGC Software Release 9.5(2)
23
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Step 2
Enter the following command to add a D-channel:
mml>prov-add:dchan:name="name", desc="description", svc="sigsrv", pri="priority",
sessionset="sset", sigslot="sslot", sigport="sport"
Where:
•
name—The name you want to give to the D-channel. The name can be as many as 20 characters long
and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
•
priority—Priority setting for this D-channel link. Valid value is any integer above 0. Default value
is 1.
•
sset—MML name of a previously provisioned session set.
•
sslot—Physical slot on the Cisco VoIP gateway on which the link is terminated. Valid values are
integers from 0 to 63. Default value is 0.
•
sport—Physical port of the associated slot on the Cisco VoIP gateway. Valid values are 0 and 1.
Default value is 0.
For example, to add a D-channel named dchan1, enter the following command:
mml>prov-add:DCHAN:NAME="dchan1", DESC="D Channel 1", SVC="qsig1", PRI=1,
SESSIONSET="sess1", SIGSLOT=1, SIGPORT=1
Step 3
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 12.
Adding a SIP IP Link
The SIP IP link is the connection between an MGC and a SIP server. To add a SIP IP link perform the
following steps:
Step 1
If you do not already have an active provisioning session, start one as described in the “Starting a
Provisioning Session” section on page 12.
Step 2
Enter the following command to add a SIP IP link:
mml>prov-add:siplnk:name="name", desc="description", ipaddr="addr", svc="sigsrv",
port="5060", pri="priority"
Where:
•
name—The name you want to give to the SIP IP link. The name can be as many as 20 characters
long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•
description—An assigned name. It can be as many as 128 alphanumeric characters in length.
•
addr—Local IP address for a LAN/WAN interface. IP address should be one of the following
property names defined in the XECfgParm.dat file:
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
•
sigsrv—MML name of a previously provisioned SIP signaling service.
Cisco MGC Software Release 9.5(2)
24
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
•
priority—Priority setting for this SIP IP link. Valid value is any integer above 0. Default value is 1.
For example to add a SIP IP link called sip-sipchan to your provisioning data, you would enter the
following command:
mml> prov-add:siplnk:name="sip-sipchan", ipaddr="IP_Addr1", svc="sip-sigpath", port=5060,
pri=1, desc="SIP sigchan"
Step 3
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 12.
Adding Associations
To add associations, perform the following steps:
Step 1
Enter the following command to add an association:
mml>prov-add:ASSOCIATION:NAME="name", DESC="description",E XTNODE="node", TYPE="IUA",
IPADDR1="addr1", IPADDR2="addr2", PORT=num, PEERADDR1="paddr1",PEERADDR2="paddr2",
[PEERPORT=pnum, IPROUTE1="iprte1", IPROUTE2="iprte2", RCVWIN=rcv,
MAXINITRETRANS=rtxinitmsg, MAXINITRTO=rtxinittim, MAXRETRANS=rtx, CUMSACKTO=sactm,
BUNDLETO=bundtm, MINRTO=minrtx, MAXRTO=maxrtx, HBTO=hp, IPPRECEDENCE="ipprec",
DSCP="dscp", MAXRETRANSDEST=prtx]
Where:
•
name—The name you want to give to the component. The name can be as many as 20 characters
long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•
description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•
node—MML name of a previously defined external node.
•
addr1—First local IP address, as defined by the XECfgParm.dat parameters IP_Addr1, IP_Addr2,
IP_Addr3, or IP_Addr4. Valid values are:
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
•
addr2—Second local IP address, as defined by the XECfgParm.dat parameters IP_Addr1,
IP_Addr2, IP_Addr3, or IP_Addr4. This parameter is optional. Valid values are:
– IP_Addr1
– IP_Addr2
– IP_Addr3
– IP_Addr4
– N/A (default value)
•
num—Local port number (optional). Valid value is from 1024 to 65535. Default value varies based
on the protocol type selected. Default for IUA is 9900. Default for M3UA is 2905. Default for SUA
is 14001.
•
paddr1—Highest priority destination address, expressed in dot notation.
Cisco MGC Software Release 9.5(2)
25
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Tasks
Note
•
paddr2—Lowest priority destination address, expressed in dot notation. This parameter is optional.
The default value for this parameter is 0.0.0.0.
•
pnum—Destination port number (optional). Valid value is from 1024 to 65535. Default value varies
based on the protocol type selected. Default for IUA is 9900. Default for M3UA is 2905. Default
for SUA is 14001.
•
iprte1—MML name of first IP route (optional). Valid value is the MML name of a previously
provisioned IP route.
•
iprte2—MML name of second IP route (optional). Valid value is the MML name of a previously
provisioned IP route.
•
rcv—Number of bytes to advertise for the local receive window (optional). Valid value is the range
from 1500 to 65535. The default value is 18000.
•
rtxinitmsg—Maximum number of times to retransmit INIT message (optional). Valid value is the
range from 0 to 100. The default value is 10. A value of 0 means that the internal default value is
used.
•
rtxinittim—Maximum initial time retransmission value (optional). Valid value is the range from 300
to 3000, and 0. The default value is 2000. A value of 0 means that the internal default value is used.
•
prtx—Maximum number of retransmissions to either PEERADDR1 or PEERADDR2 before the
association is declared failed (optional). Valid value is the range from 1 to 10. The default value is 3.
•
rtx—Maximum number of retransmissions over all destination address before the association is
declared failed (optional). Valid value is the range from 1 to 10. The default value is 5.
The value of this parameter cannot exceed the value of the MAXRETRANSDEST parameter times the
number of destinations.
•
sacktm—Maximum time after a datagram is received before a SACK message is sent (optional).
Valid value is the range from 100 to 500 ms. The default value is 300 ms.
•
bundtm—Maximum time waits for other outgoing datagrams for bundling (optional). Valid value is
the range from 100 to 600 ms. The default value is 100 ms.
•
minrtx—Minimum value allowed for the retransmission timer (optional). Valid value is the range
from 300 to 3000 ms. The default value is 300 ms.
•
maxrtx—Maximum value allowed for the retransmission timer (optional). Valid value is the range
from 1000 to 3000 ms. The default value is 3000 ms.
•
hb—Time between heartbeats (optional). The heartbeat is this value plus the current retransmission
timeout value. Valid value is the range from 300 to 10000 ms, or 0. A value of 0 means that the
heartbeat is disabled. The default value is 2000 ms.
•
ipprec—IP precedence (optional). The value for this parameter is inserted in place of the IP
precedence portion of the Type of Service field in outing datagrams. Valid values are as follows:
– ROUTINE (default) 000
– PRIORITY 001
– IMMEDIATE 010
– FLASH 011
– FLASH-OVERRIDE 100
– CRITICAL 101
– INTERNET 110
Cisco MGC Software Release 9.5(2)
26
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Examples
– NETWORK 111
•
dscp—Time between heartbeats (optional). The heartbeat is this value plus the current
retransmission timeout value. Valid value is the range from 300 to 10000 ms, or 0. A value of 0
means that the heartbeat is disabled. The default value is 2000 ms.
– EF 101110—Expedited Forwarding
– AF11 001010—Assured Forwarding Class 1 Low Drop Precedence
– AF12 001100—Assured Forwarding Class 1 Medium Drop Precedence
– AF13 001110—Assured Forwarding Class 1 High Drop Precedence
– AF21 010010—Assured Forwarding Class 2 Low Drop Precedence
– AF22 010100—Assured Forwarding Class 2 Medium Drop Precedence
– AF23 010110—Assured Forwarding Class 2 High Drop Precedence
– AF31 011010—Assured Forwarding Class 3 Low Drop Precedence
– AF32 011100—Assured Forwarding Class 3 Medium Drop Precedence
– AF33 011110—Assured Forwarding Class 3 High Drop Precedence
– AF41 100010—Assured Forwarding Class 4 Low Drop Precedence
– AF42 100100—Assured Forwarding Class 4 Medium Drop Precedence
– AF43 100110—Assured Forwarding Class 4 High Drop Precedence
– N/A (default)
For example, to add an association named assoc2, you would enter the following command:
prov-add:ASSOCIATION:NAME="assoc2",DESC="",EXTNODE="dpnss-gw2",SGP="",TYPE="IUA",
IPADDR1="IP_Addr1",IPADDR2="N/A",PORT=9900,PEERADDR1="172.22.121.206",PEERADDR2="0.0.0.0",
PEERPORT=9900,IPROUTE1="",IPROUTE2="",RCVWIN=18000,MAXINITRETRANS=10,MAXINITRTO=2000,
MAXRETRANS=5,CUMSACKTO=300,BUNDLETO=100,MINRTO=300,MAXRTO=3000,HBTO=2000,
IPPRECEDENCE="ROUTINE",DSCP="AF31",MAXRETRANSDEST=3
Step 2
Repeat Step 1 for each association you want to add to your provisioning data.
Step 3
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 12.
Provisioning Examples
This section provides provisioning examples for this feature. Additional provisioning examples for the
Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
Interworking with a DPNSS PBX
The following example is for setting up signaling interworking between a Cisco Unity and a DPNSS
PBX.
prov-add:EXTNODE:NAME="dpnss-gw1",DESC="nas 2600 Backhaul", TYPE="AS3600",
ISDNSIGTYPE="IUA", GROUP=0
Cisco MGC Software Release 9.5(2)
27
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Provisioning Examples
prov-add:EXTNODE:NAME="dpnss-gw2",DESC="nas 2600 Backhaul", TYPE="C2600",I
SDNSIGTYPE="IUA", GROUP=0
prov-add:MGCPPATH:NAME="dpnss-mgcp1",DESC="signal service - mgcp1",EXTNODE="dpnss-gw1"
prov-add:MGCPPATH:NAME="dpnss-mgcp2",DESC="signal service - mgcp1",EXTNODE="dpnss-gw2"
prov-add:ASSOCIATION:NAME="assoc1",DESC="",EXTNODE="dpnss-gw1",SGP="",TYPE="IUA",IPADDR1="
IP_Addr1",IPADDR2="N/A",PORT=9900,PEERADDR1="172.22.121.17",PEERADDR2="0.0.0.0",PEERPORT=9
900,IPROUTE1="",IPROUTE2="",RCVWIN=18000,MAXINITRETRANS=10,MAXINITRTO=2000,MAXRETRANS=5,CU
MSACKTO=300,BUNDLETO=100,MINRTO=300,MAXRTO=3000,HBTO=2000,IPPRECEDENCE="ROUTINE",DSCP="N/A
",MAXRETRANSDEST=3
prov-add:ASSOCIATION:NAME="assoc2",DESC="",EXTNODE="dpnss-gw2",SGP="",TYPE="IUA",IPADDR1="
IP_Addr1",IPADDR2="N/A",PORT=9900,PEERADDR1="172.22.121.206",PEERADDR2="0.0.0.0",PEERPORT=
9900,IPROUTE1="",IPROUTE2="",RCVWIN=18000,MAXINITRETRANS=10,MAXINITRTO=2000,MAXRETRANS=5,C
UMSACKTO=300,BUNDLETO=100,MINRTO=300,MAXRTO=3000,HBTO=2000,IPPRECEDENCE="ROUTINE",DSCP="AF
31",MAXRETRANSDEST=3
prov-add:DPNSSPATH:NAME="dpnss1",DESC="backhaul to nas2600", EXTNODE="dpnss-gw1",
MDO="DPNSS_BTNR188", CUSTGRPID="1111",SIGSLOT=0,SIGPORT=1
prov-add:sigsvcprop:name="dpnss1",MwiStringON="*58*CH*K#"
prov-add:sigsvcprop:name="dpnss1",CustomerVPNid="0001"
prov-add:sigsvcprop:name="dpnss1",CustomerVPNOnNetTblNum="1"
prov-add:sigsvcprop:name="dpnss1",MwiStringOFF="*58*CH*L#"
prov-add:DPNSSPATH:NAME="dpnss2",DESC="backhaul to nas2600", EXTNODE="dpnss-gw2",
MDO="DPNSS_BTNR188", CUSTGRPID="1111",SIGSLOT=2,SIGPORT=1
prov-add:sigsvcprop:name="dpnss2",CustomerVPNOffNetTblNum="1"
prov-add:sigsvcprop:name="dpnss2",CustomerVPNid="0001"
prov-add:sigsvcprop:name="dpnss2",CustomerVPNOnNetTblNum="1"
prov-add:sigsvcprop:name="dpnss2",MwiStringON="*171B#"
prov-add:sigsvcprop:name="dpnss2",MwiStringOFF="*172B#"
prov-add:SIPPATH:NAME="sip-sigpath",DESC="SIP sigpath",MDO="IETF_SIP"
prov-add:sigsvcprop:name="sip-sigpath",SIPReferforSinglestepXfer="1"
prov-add:IPLNK:NAME="sc1-dpnss1",DESC="sigchannel 1 for mgcp sig path
1",SVC="dpnss-mgcp1",IPADDR="IP_Addr1",PORT=2427,PEERADDR="172.22.121.17",PEERPORT=2427,
PRI=1,IPROUTE=""
prov-add:IPLNK:NAME="sc1-dpnss2",DESC="sigchannel 1 for mgcp sig path 1",
SVC="dpnss-mgcp2",IPADDR="IP_Addr1",PORT=2427,PEERADDR="172.22.121.206",PEERPORT=2427,
PRI=1,IPROUTE=""
prov-add:SIPLNK:NAME="sip-sigchan",DESC="SIP sigchan", SVC="sip-sigpath",
IPADDR="IP_Addr1", PORT=5060,PRI=1
Interworking with a QSIG PBX
The following example is for setting up signaling interworking between a Cisco Unity and a DPNSS
PBX.
prov-add:EXTNODE:NAME="qsig-gw1",DESC="nas 2600 Backhaul", TYPE="AS3600",
ISDNSIGTYPE="N/A", GROUP=0
prov-add:EXTNODE:NAME="qsig-gw2",DESC="nas 2600 Backhaul", TYPE="C2600",
ISDNSIGTYPE="N/A", GROUP=0
prov-add:SESSIONSET:NAME="sess1",EXTNODE="qsig-gw1",IPADDR1="IP_Addr1",PEERADDR1="172.22.1
21.252",PORT=1100,PEERPORT=1100,TYPE="IPFAS"
prov-add:SESSIONSET:NAME="sess2",EXTNODE="qsig-gw2",IPADDR1="IP_Addr1",PEERADDR1="172.22.1
21.59",PORT=1100,PEERPORT=1100,TYPE="IPFAS"
prov-add:MGCPPATH:NAME="qsig-mgcp1",DESC="signal service - mgcp1",EXTNODE="qsig-gw1"
prov-add:MGCPPATH:NAME="qsig-mgcp2",DESC="signal service - mgcp1",EXTNODE="qsig-gw2"
prov-add:IPFASPATH:NAME="qsig1",DESC="backhaul",EXTNODE="qsig-gw1",MDO="ETS_300_172",
CUSTGRPID="1111",SIDE="network",ABFLAG="n",CRLEN=2
prov-add:sigsvcprop:name="qsig1",MWIInvokeTimerT1="10000"
prov-add:sigsvcprop:name="qsig1",SSCTInvokeTimerT1="55000"
prov-add:sigsvcprop:name="qsig1",TransferAwaitConnect="0"
prov-add:IPFASPATH:NAME="qsig2",DESC="backhaul",EXTNODE="qsig-gw2",MDO="ETS_300_172",
CUSTGRPID="1111",SIDE="network",ABFLAG="n",CRLEN=2
prov-add:sigsvcprop:name="qsig2",MWIInvokeTimerT1="10000"
Cisco MGC Software Release 9.5(2)
28
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
prov-add:sigsvcprop:name="qsig2",SSCTInvokeTimerT1="50000"
prov-add:sigsvcprop:name="qsig2",TransferAwaitConnect="1"
prov-add:SIPPATH:NAME="sip-sigpath",DESC="SIP sigpath",MDO="IETF_SIP"
prov-add:sigsvcprop:name="sip-sigpath",SIPReferforSinglestepXfer="1"
prov-add:DCHAN:NAME="dchan1",DESC="",SVC="qsig1",PRI=1,SESSIONSET="sess1",SIGSLOT=1,
SIGPORT=1
prov-add:DCHAN:NAME="dchan2",DESC="",SVC="qsig2",PRI=1,SESSIONSET="sess2",SIGSLOT=6,
SIGPORT=0
prov-add:IPLNK:NAME="qs1-mgcp1",DESC="sigchannel 1 for mgcp sig path
2",SVC="qsig-mgcp1",IPADDR="IP_Addr1",PORT=2427,PEERADDR="172.22.121.252",PEERPORT=2427,
PRI=1
prov-add:IPLNK:NAME="qs1-mgcp2",DESC="sigchannel 1 for mgcp sig path
2",SVC="qsig-mgcp2",IPADDR="IP_Addr1",PORT=2427,PEERADDR="172.22.121.59",PEERPORT=2427,
PRI=1
prov-add:SIPLNK:NAME="sip-sigchan",DESC="SIP sigchan", SVC="sip-sigpath",
IPADDR="IP_Addr1", PORT=5060,PRI=1
Reference Information
The following sections contain reference material related to this feature. Information is included on the
following areas:
•
Properties, page 29
•
External Node Types, page 31
•
Provisioning Worksheets, page 32
Properties
The properties in this section are used for this feature. For information on other properties for the Cisco
MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
The parent objects for the properties involved in this feature are found in Table 1.
Table 1
Parent Objects for Software Properties
MWIInvokeTimerT1
VSI
TrunkGroup
TCAPOverIP
TALI-IOCC
SS7-UK
SS7-Japan
SS7-ITU
SS7-China
SS7-ANSI
SIP
SESSION
RLM
X
MWIStringOFF
X
MWIStringON
X
SipReferForSimpleStepXfer
SSCTInvokeTimerT1
MGCP
ISDNPRI
IOCC
EISUP
DPNSS
Property Name
AVM
Parent Object
X
X
Cisco MGC Software Release 9.5(2)
29
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
TransferAwaitConnect
VSI
TrunkGroup
TCAPOverIP
TALI-IOCC
SS7-UK
SS7-Japan
SS7-ITU
SS7-China
SS7-ANSI
SIP
SESSION
RLM
MGCP
ISDNPRI
IOCC
EISUP
Property Name
DPNSS
AVM
Parent Object
X
The properties added for this feature are described in Table 2.
Table 2
Properties
Property
Definition
MWIInvokeTimerT1
A millisecond timer, as specified by ROSE, that is used to
invoke the message waiting indicator (MWI) supplementary
service. This property is used for communication with a VoIP
gateway connected to a QSIG PBX.
Valid Values: any integer from 0 to 20000 (this value is in
milliseconds)
Default Value: 15000
MWIStringOFF
Number used within the network to turn off a message waiting
indicator, specific to DPNSS signaling services. This property
is used for communication with a VoIP gateway connected to a
DPNSS PBX.
Valid Values: a string, with a minimum length of 1 and a
maximum length of 32 characters.
Default Value: NULL
MWIStringON
Number used within the network to turn on a message waiting
indicator, specific to DPNSS signaling services. This property
is used for communication with a VoIP gateway connected to a
DPNSS PBX.
Valid Values: a string, with a minimum length of 1 and a
maximum length of 32 characters.
Default Value: NULL
SipReferForSimpleStepXfer
Enables/disables special handling for SIP REFER, which is
required to support the single-step call transfer (SSCT)
supplementary service. This property is used for SIP signaling
services when supporting communication with a VoIP gateway
connected to a QSIG PBX.
Valid values:
•
0—Standard SIP REFER
•
1—SIP REFER to support SSCT
Default Value: 0
Cisco MGC Software Release 9.5(2)
30
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 2
Properties (continued)
Property
Definition
SSCTInvokeTimerT1
A millisecond timer, as specified by ROSE, that is used to
invoke the single-step call transfer (SSCT) supplementary
service. This property is used for communication with a VoIP
gateway connected to a QSIG PBX.
Valid Values: any integer from 50000 to 180000 (this value is
in milliseconds)
Default Value: 50000
Transfer Await Connect
Await connection flag, which is used to determine when a QSIG
PBX releases a call. This property is used for communication
with a VoIP gateway connected to a QSIG PBX, when the
implementation of MWI on the PBX deviates from the ECMA
standard.
Valid Values:
•
0—(false) QSIG PBX releases original call after receiving
ALERT
•
1—(true) QSIG PBX releases original call after receiving
CONNECT)
Default Value: NULL
External Node Types
Table 3 lists the external node types, the software release in which they were introduced, and the
signaling service types they support.
Table 3
External Node Types
External Node MML Name
Valid Release
Supported Signaling Service Type
AS3600
Release 9.1(5) and up
MGCP IPFAS NAS IUA
AS3660
Release 9.1(5) and up
MGCP IPFAS NAS IUA
AS5200
Release 9.1(5) and up
IPFAS NAS
AS5300
Release 9.1(5) and up
MGCP IPFAS NAS IUA
AS5350
Release 9.2(2) and up
MGCP IPFAS NAS BSMV0 IUA
AS5400
Release 9.2(2) and up
MGCP IPFAS NAS BSMV0 IUA
AS5800
Release 9.1(5) and up
IPFAS NAS
AS5850
Release 9.1(5) and up
IPFAS NAS
AS7200
Release 9.1(5) and up
MGCP IPFAS NAS
CAT8510
Release 9.1(5) and up
MGCP
CAT8540
Release 9.1(5) and up
MGCP
C1751
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C1760
Release 9.5(2) and up
MGCP IPFAS IUA BRI
Cisco MGC Software Release 9.5(2)
31
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 3
External Node Types (continued)
External Node MML Name
Valid Release
Supported Signaling Service Type
C2600
Release 9.4(1) and up
MGCP IPFAS IUA BRI
C2610XM
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C2611XM
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C2620XM
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C2621XM
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C2650XM
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C2651XM
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C2691
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C3640
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C3640A
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C3660
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C3725
Release 9.5(2) and up
MGCP IPFAS IUA BRI
C3745
Release 9.5(1) and up
MGCP IPFAS IUA BRI
H323
Release 9.1(5) and up
EISUP
ITP
Release 9.4(1) and up
M3UA SUA
LS1010
Release 9.1(5) and up
MGCP
MC3810
Release 9.1(5) and up
MGCP IPFAS
MGC
Release 9.1(5) and up
EISUP
MGX8260
Release 9.1(5) and up
MGCP IPFAS NAS
MGX8850
Release 9.1(5) and up
MGCP SGCP IPFAS
SLT
Release 9.2(2) and up
BSMV0
TALISS7
Release 9.1(5) and up
SS7SG
UNKNOWN
Release 9.1(5) and up
UNKNOWN
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 4
External Node Worksheet Example
Name
Type
ISDN Signaling Type Group
Description
va-3640-01
C3640
—
TCP conn to va-3640-01
Cisco MGC Software Release 9.5(2)
32
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 4
Name
Table 5
External Node Worksheet Example (continued)
Type
ISDN Signaling Type Group
Description
Session Set Worksheet Example
Name
Ext Node
IP Address 1
va-3640-01
C3640
—
Table 6
Peer Address Port
Peer Port
Type
Description
TCP conn to va-3640-01
MGCP Signaling Service Worksheet Example
Name
Ext Node
Description
MGCpth1
Gw1
MGCP path to Gw1
Cisco MGC Software Release 9.5(2)
33
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 6
MGCP Signaling Service Worksheet Example (continued)
Name
Table 7
Ext Node
DPNSS Signaling Service Worksheet Example
Name
External
Node
dpnsvc2
va-3660-20
Table 8
Customer
Group ID
DPNSS
Side
Signaling
Port
Signaling
Slot
Description
A
0
0
IUA DPNSSpath to GW
DPNSS Signaling Service Properties Worksheet Example
Property Name
Cisco MGC Software Release 9.5(2)
34
Description
Value
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 8
DPNSS Signaling Service Properties Worksheet Example (continued)
Property Name
Table 9
Value
SIP Data Pathway Worksheet Example
Name
MDO File Name
Description
sipsrv1
va-3660-20
path to Unity
Table 10
SIP Data Pathway Properties Worksheet Example
Property Name
Value
Cisco MGC Software Release 9.5(2)
35
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 10
SIP Data Pathway Properties Worksheet Example (continued)
Property Name
Value
Table 11
IP FAS Signaling Service Worksheet Example
Name
External
Node
brisvc1
va-3640-01
Q.931
Call Model
Side
MDO File
ETS_300_102
Cisco MGC Software Release 9.5(2)
36
Customer
Group ID
A-B
Flag
Call
Reference
Length
Description
1
BRI path to va-3640-01
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 12
IP FAS Signaling Service Properties Worksheet Example
Property Name
Table 13
Value
IP Route Worksheet Example (Optional)
Name
Destination
Subnet Mask
Next Hop
IP Address
Priority
Description
iproute1
va-3640-01
255.255.255.0
va-3640-02
175.25.211.17
1
IP route to
va-3640-01
Cisco MGC Software Release 9.5(2)
37
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 14
MGCP IP Link Worksheet
Name
Port
Priority
IP Address
MGCP Path
Peer
Port
IP Route
Peer IP
Address
Description
mgcplnk1
2427
1
IP_Addr1
mgcpsvc1
2427
iproute1
146.29.64.101
MGCP IP link 1
Table 15
Name
D-Channel Worksheet Example
Signaling Type
brichan1 bri
Table 16
Priority
Link
Slot
Port
Subunit
Description
1
britcp1
0
4
1
bri d-channel 1
SCTP Association Worksheet Example
Parameter
Parameter Value
Name
assoc1
Description
association 1
Cisco MGC Software Release 9.5(2)
38
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Reference Information
Table 16
SCTP Association Worksheet Example (continued)
Parameter
Parameter Value
Signaling Type
M3UA
SGP name
sgp1
First local address
175.23.211.15
Second local address
(optional)
n/a
Local SCTP port number
(optional)
2905
Highest priority destination
address
117.52.16.20
Lowest priority destination
address (optional)
Destination SCTP port
number (optional)
External node name
itp1
First IP route name (optional) iproute1
Second IP route name
(optional)
iproute2
Number of bytes to advertise
for the local receive window.
(optional)
Maximum number of times to
retransmit SCTP INIT
message (optional)
Maximum initial timer
retransmission value
(optional)
Maximum number of
retransmissions over all
destination address before the
association is declared failed
(optional)
Maximum time after a
datagram is received before a
SCPT SACK is sent (optional)
Maximum time SCTP will
wait for other outgoing
datagrams for bundling
(optional)
Minimum value allowed for
the retransmission timer
(optional)
Cisco MGC Software Release 9.5(2)
39
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Obtaining Documentation
Table 16
SCTP Association Worksheet Example (continued)
Parameter
Parameter Value
Maximum value allowed for
the retransmission timer
(optional)
Time between heartbeats
(optional).
IP Precedence (optional)
Differential Service Code
Point (optional)
Maximum number of
retransmissions to either peer
address 1 or 2 before it is
declared failed (optional)
Table 17
SIP Link Worksheet Example
Name
Signaling Service
Priority
IP Address
Port
Description
brichan1
bri
1
britcp1
4
bri d-channel 1
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several
ways to obtain 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 at this URL:
http://www.cisco.com/univercd/home/home.htm
Cisco MGC Software Release 9.5(2)
40
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Documentation Feedback
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from
the Ordering tool:
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 send 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, Cisco
Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical
Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical
Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service
contract, contact your reseller.
Cisco MGC Software Release 9.5(2)
41
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Obtaining Technical Assistance
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and
resolving technical issues with Cisco products and technologies. The website is available 24 hours a day,
365 days a year at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password.
If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3
and S4 service requests are those in which your network is minimally impaired or for which you require
product information.) After you describe your situation, the TAC Service Request Tool automatically
provides recommended solutions. If your issue is not resolved using the recommended resources, your
service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at
this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone.
(S1 or S2 service requests are those in which your production network is down or severely degraded.)
Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business
operations running smoothly.
To open a service request 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 list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity
definitions.
Severity 1 (S1)—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.
Severity 2 (S2)—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.
Severity 3 (S3)—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.
Severity 4 (S4)—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)
42
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
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.
•
Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit
Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•
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://cisco.com/univercd/cc/td/doc/pcat/
•
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 at this URL:
http://www.ciscopress.com
•
Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and
networking investments. Each quarter, Packet delivers coverage of the latest industry trends,
technology breakthroughs, and Cisco products and solutions, as well as network deployment and
troubleshooting tips, configuration examples, customer case studies, certification and training
information, and links to scores of in-depth online resources. You can access Packet magazine at this
URL:
http://www.cisco.com/packet
•
iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies
learn how they can use technology to increase revenue, streamline their business, and expand
services. The publication identifies the challenges facing these companies and the technologies to
help solve them, using real-world case studies and business strategies to help readers make sound
technology investment decisions. 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/ipj
•
World-class networking training is available from Cisco. You can view current offerings at
this URL:
http://www.cisco.com/en/US/learning/index.html
Glossary
Table 18 contains definitions of acronyms and technical terms used in this feature module.
Table 18
Acronyms
Acronym
Definition
DPNSS
Digital Private Network Signaling System
FAS
Facility Associated Signaling
Cisco MGC Software Release 9.5(2)
43
Support for QSIG and DPNSS Signaling Interworking for Cisco Unity
Glossary
Table 18
Acronyms (continued)
Acronym
Definition
IP
Internet Protocol.
ISDN
Integrated Services Digital Network. Communication protocol offered by
telephone companies that permits telephone networks to carry data, voice,
and other source traffic.
MGC
(Cisco) Media Gateway Controller.
MGCP
Media Gateway Control Protocol.
MWI
Message Waiting Indicator
NSI
Non-Specified Information
PBX
Private Branch Exchange
Q.931
ISDN Level 3 ITU standard.
QSIG
Q Signaling
SIP
Session Initiation Protocol
SSCT
Single-Step Call Transfer
VoIP
Voice over Internet Protocol
Cisco MGC Software Release 9.5(2)
44