Support for QSIG and DPNSS Signaling Interworking for Cisco Unity

Transcription

1 Support for QSIG and DPNSS Signaling Interworking for Cisco Unity Document Release History Publication Date June 11, 2004 Comments Initial version of the document. Feature History Release Release 9.4(1) Release 9.5(2) Modification This feature is introduced as part of a patch to this release. 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 1

2 Feature Overview Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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. 2

3 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 3

4 Feature Overview Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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 4

5 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). 5

6 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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 6

7 Support for QSIG and DPNSS Signaling Interworking for Cisco Unity Provisioning Tasks Collecting SIP IP Link Data, page 11 Data Collection Procedures Collecting External Node Data Collecting Session Set Data The sections below are the various data collection procedures you must perform before you provision this feature. 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. 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 Collecting MGCP Path Data Peer port Type You can define the parameters for your session set in Table 5. 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. 7

8 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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 Collecting DPNSS Path Property Data Collecting SIP Path Data Collecting SIP Path Property Data 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. 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. 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. 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. 8

9 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 Collecting IP FAS Path Property Data Collecting IP Route Data (optional) Collecting MGCP IP Link Data Call reference length (0 through 2 bytes) You can define the parameters for your ISDN FAS signaling services in Table 11. 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. 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. 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 9

10 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity Collecting D-Channel Data Collecting Association Data Priority IP address Associated MGCP signaling service You can define the parameters for your MGCP IP links in Table 14. 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. 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). 10

11 Support for QSIG and DPNSS Signaling Interworking for Cisco Unity Provisioning Tasks Collecting SIP IP Link Data 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. 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 Provisioning Basics 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 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 11

12 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity Starting a Provisioning Session For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide. 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. 12

13 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 Retrieving Provisioning Data 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. 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 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 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. 13

14 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity Retrieving Data for All Components 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. 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 :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 14

15 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 Adding Cisco VoIP External Nodes, page Adding MGCP Signaling Services, page Adding DPNSS Signaling Services, page Modifying DPNSS Properties for Communications with DPNSS PBXs, page Adding IP Routes (Optional), page Adding IP Routes (Optional), page Adding MGCP IP Links, page Adding Associations, page Adding a SIP IP Link, page 24 Enabling Signaling Interworking for Cisco Unity and QSIG PBX Procedures 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 Adding Cisco VoIP External Nodes, page Adding Session Sets, page Adding MGCP Signaling Services, page Adding IP FAS Signaling Services, page Adding IP Routes (Optional), page Modifying IP FAS and SIP Properties for Communication with QSIG PBXs, page Adding IP Routes (Optional), page Adding MGCP IP Links, page Adding D-Channels, page Adding a SIP IP Link, page 24 The sections that follow are the provisioning procedures used to enable signaling interworking between the Cisco Unity and a DPNSS/QSIG PBX. 15

16 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity Preparing Platforms for Integration Adding Cisco VoIP External Nodes 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. 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 , enter the following command: mml>prov-add:extnode:name="va ", desc="qsig PBX 3640", type="c3640", isdnsigtype= na Step 3 Step 4 Repeat Step 2 for each Cisco BRI voice gateway external node you want to add to your provisioning data. 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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. 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. 16

17 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 paddr1 First remote IP address. Default value: This may also be specified as a hostname or a DNS name. paddr2 Second remote IP address. Default value: This may also be specified as a hostname or a DNS name. pnum Remote port number. Valid values: 1025 through 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="c ",extnode="va-2600-stim1",ipaddr1="ip_addr1", PEERADDR1=" ",PORT=7000,PEERPORT=7000, TYPE="BSMV0" Step 3 Step 4 Repeat Step 2 for each DPNSS signaling service you want to add to your provisioning data. 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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. Enter the following command to add a MGCP signaling service: mml>prov-add:mgcppath:name="name", desc="description", extnode= mgw Where: 17

18 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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 ",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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. 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). 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 ", abflag= a, sigport=45, sigslot=10 Step 3 Step 4 Repeat Step 2 for each DPNSS signaling service you want to add to your provisioning data. 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

19 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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. 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 Step 5 Repeat steps 2 through 3 for each DPNSS signaling service that support your DPNSS PBXs. 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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. 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. 19

20 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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 Step 4 Repeat Step 2 for each IP FAS signaling service you want to add to your provisioning data. 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 Step 2 Step 3 Step 4 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. 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. Repeat Step 2 for each SIP signaling service you want to add to your provisioning data. 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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. Enter the following command to set the duration for the MWI invoke timer: prov-add:sigsvcprop:name="sigsrv", MWIInvokeTimerT1="timval" 20

21 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 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 to 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" Step 5 Step 6 Step 7 Step 8 Where sigsrv is the MML name of a previously provisioned IP FAS signaling service. Repeat steps 2 through 4 for each IP FAS signaling service that support your QSIG PBXs. 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. Repeat Step 6 for each SIP signaling service that supports your QSIG PBXs. 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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. 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. 21

22 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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 ). 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=" ", ipaddr= IP_Addr1, netmask=" ", nexthop=" " Step 3 Step 4 Repeat Step 2 for each IP route you want to add to your provisioning data. 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

23 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 For MGCP IP links, we recommend that you use rpnum Remote IP port number. Valid value is any integer above For MGCP IP links, we recommend that you use 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= , svc="mgcpsvc1", port=2427, peerport=2427, iproute1=iproute1, pri=1, desc="mgcp sigchan 1" Step 2 Step 3 Repeat Step 1 for each MGCP IP link you want to provision. 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

24 Provisioning Tasks Support for QSIG and DPNSS Signaling Interworking for Cisco Unity 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 Step 2 If you do not already have an active provisioning session, start one as described in the Starting a Provisioning Session section on page 12. 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. 24

25 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 Default value varies based on the protocol type selected. Default for IUA is Default for M3UA is Default for SUA is paddr1 Highest priority destination address, expressed in dot notation. 25