Feature Overview

This feature enables the PGW 2200 to support interworking between a DPNSS PBX and Cisco CallManager for DPNSS Call Back When Free (CBWF), Call Back When Next Used (CBWNU), and Extension Status supplementary service features. This feature is supported across up to eight Cisco CallManager clusters.

Call Back When Free

The Call Back When Free (CBWF) feature allows a user who receives a busy signal (i.e. extension busy or network congestion) when trying to establish a call in the Private Network to request an automatic call back. The calling party can register the feature with the originating PBX which requests the terminating PBX to monitor the called extension. When the called extension and a transmission path across the network become free, the user who invoked the feature is notified by an audible and visual alert that the called extension is available. The user has the option at that time to accept the call back and a call will be set up from the user to the extension that becomes free.

Note Cisco PGW supports this feature for DPNSS to CCM calls, CCM to DPNSS calls, and calls within a CCM cluster.

Call Back When Next Used

The Call Back When Next Used (CBWNU) feature allows a user who receives no reply when trying to establish a call in the Private Network to request an automatic call back. The calling party can clear the call and invoke Call Back When Next Used. When the called extension becomes free after having been used, the user that invoked the feature is notified by an audible and visual alert. The user has an option at that time to accept the call back and a call will be set up from the user to the extension that becomes free.

Note Cisco PGW supports this feature for DPNSS to CCM calls, CCM to DPNSS calls, and calls within a CCM cluster.

Extension Status

The Extension Status feature allows the user to determine, on request, the status of an extension. This service permits the establishment of a Virtual Call to an extension to determine its state (free, busy, out of service, call waiting on, call forward all on) without calling the extension.

The PGW supports this feature for DPNSS PBX to CCM calls.

Support for Up to 8 Call Manager Clusters

This feature adds support for up to eight call manager clusters. It is used with features such as DPNSS CallBack and Extension Status.

Restrictions

CBWF and CBWNU features will not be supported under the following conditions:

•For calls to or from CCM phones and DPNSS, or using CCM phones going through Cisco PGW

•There are some additional limitations with the interworking of the Call Diversion feature with CCM, explained in the following two scenarios:

–Scenario 1: There is a PBX phone A which registered a Call Diversion on-busy service and the forwarded-to party is PBX phone B in another PBX. A CCM IP phone calls PBX phone A, but phone A busy, so this call is forwarded to phone B. But phone B does not answer. The CCM IP phone invokes the Call Back When Next Used (CBWNF) feature. The expected result is that the CBWNU should target the phone A and CBWNU should be converted to Call Back When Free (CBWF). The actual result is that the CBWNU feature is targeted on phone A, not the CBWF.

–Scenario 2: A CCM IP phone calls PBX phone A. Since PBX phone A has call forward immediate, this call is forwarded to phone B in another PBX, but phone B happens to be busy. So the CCM IP phone invokes the Call Back When Free feature. This Call Back When Free should be sent to PBX phone B. But the actual result is that it is sent to PBX phone A.

Related Features and Technologies

The following documentation is available to describe additional features on the PGW 2200 (MGC) and IOS Gateways that enable interworking between DPNSS PBXs and Cisco CallManager.

Related Documentation

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 and can be found at:

New MIBs are available for this feature. There is a new MIB for each new measurement. You can find a list of the new measurements in
Measurements. For more information on the MIBs used in the Cisco MGC software, refer to the
Cisco Media Gateway Controller Software Release 9 Management Information Base Guide at:

Configuring The XECfgParm.dat File For This Feature

This section contains the steps necessary for configuration of the next hop IP address in the XECfgParm.dat file to support this feature. If you are installing and configuring the Cisco MGC software on your system for the first time, use the procedures in the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide at:

Come back to this section once you encounter the *.IP_NextHop1 parameter in the XECfgParm.dat file.

Note You need to configure the *.IP_NextHop parameters when the Cisco MGC hosts are on different subnets. If your hosts are on the same subnet, do not perform the procedure below.

Caution Configuration of the Cisco MGC software requires that the system software be shut down. In a simplex system, calls cannot be processed during system shutdown. In a continuous service system, your system loses the ability to maintain calls during a critical event while the system software on one of the PGW hosts is shut down.

Caution Do not modify the other XECfgParm.dat parameters associated with this feature.

To configure the next hop IP addresses, perform the following steps:

Step 1 If you have not already done so, open the /opt/CiscoMGC/etc/XECfgParm.dat file on the active and standby Cisco PGW hosts using a text editor, such as vi.

Step 2 If you have not already done so, ensure that the pom.dataSyncparameter is set to falseon the active and standby Cisco PGW hosts.

Step 3 Search for the *.IP_NextHop1parameter and enter the IP address of your first next hop destination on the active and standby Cisco PGW hosts.

Step 4 Repeat Step 3 for every next hop destination (*.IP_NextHop2, *.IP_NextHop3, etc.) you want to identify on the active and standby Cisco PGW hosts. Up to eight next hop IP addresses can be specified.

and continue from where you left off. You will need to go to Adding DPNSS Connections in this document later if you intend to use an IUA interface for data backhaul between your Cisco PGW 2200 and your associated Cisco access gateway(s).

Verifying the XECfgParm.dat Changes

To verify the XECfgParm.dat settings for this feature, perform the following steps:

Caution Do not modify the other XECfgParm.dat parameters associated with this feature.

Step 1 Log in to the standby Cisco MGC as root and change directories to the etc subdirectory by entering the following UNIX command:

cd /opt/CiscoMGC/etc

Step 2 Open the XECfgParm.dat using a text editor, such as vi.

Step 3 Search for the *.IP_NextHop1parameter and verify that the IP address of your first next hop destination is correct.

If the next hop IP address is correct, proceed to Step 4. Otherwise, correct the IP address and then proceed to Step 4.

Step 4 Repeat Step 3 for every next hop destination (*.IP_NextHop2, *.IP_NextHop3, and so forth) that you want to verify. You can specify up to eight next hop IP addresses.

Step 5 If all of your next hop destinations were correct, proceed to Step 9. Otherwise, proceed to Step 6.

If the next hop IP addresses you have entered are incorrect, perform the following steps. For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide at:

To ensure proper functioning of this feature, you must enter next hop IP addresses in the XECfgParm.dat file. These IP addresses are used when the next hop router IP addresses on the Cisco PGW hosts do not match. To enter next hop IP addresses, perform the following steps:

Step 6 Save your changes and close the text editor.

Step 7 Manually stop the Cisco MGC software on the standby Cisco MGC by entering the following UNIX command:

/etc/init.d/CiscoMGC stop

Step 8 Once the software shutdown is complete, manually start the Cisco MGC software on the standby Cisco MGC by entering the following command:

/etc/init.d/CiscoMGC start

Step 9 Log in to the active Cisco MGC, start an MML session, and enter the following command:

mml>sw-over::confirm

Site alarms are automatically set until the out-of-service (OOS) Cisco MGC host is returned to an in-service (IS) state.

Step 10 Repeat steps 2 through 9 for the newly standby Cisco MGC host. Once you have verified the settings on both hosts, the procedure is complete.

Provisioning Procedures

You must modify the provisioning data of your system to enable this feature. Before you begin provisioning this feature, we recommend that you plan your provisioning changes as described in Planning for Provisioning.

Tip You can find information on starting and ending provisioning sessions and retrieving provisioning data in Provisioning Basics.

The following sections describe the provisioning tasks related to this feature:

Provisioning This Feature

Provision the transport path for DPNSS data between the Cisco PGW 2200 and the external Cisco access gateway nodes to provide a reliable communication path between the two platforms.

Perform this provisioning when an external node is modified to use an SCTP-based protocol or when a new external node is added to the Cisco PGW 2200. This section covers the following provisioning topics:

The following sections describe the provisioning tasks related to this feature:

Adding DPNSS Connections

This section contains the procedures that you must perform to support DPNSS connections with your Cisco PGW 2200 provisioning data. When provisioning the components that enable the Cisco PGW 2200 to support DPNSS, perform the procedures in the following order.

Otherwise, proceed to Adding IP Routes (Optional)if your Cisco PGW 2200 is on a different subnet from the associated access gateway, or proceed to the "Adding SCTP Associations" section if they are on the same subnet..

Modifying DPNSS Signaling Services

You can modify the description, DPNSS side identification, signaling port number, and signaling slot number in a DPNSS signaling service. To modify DPNSS signaling services, perform the following steps:

Step 1 Shut down the D-channel(s) on the associated access gateway(s). See the documentation for the access gateway for more information on shutting down D-channels.

Step 2 Set the DPNSS signaling services to be modified to the Out-of-Service (OOS) state by entering the following MML command:

set-dest:sig_srv:OOS

Where sig_srv is the MML name of the DPNSS signaling services to be modified.

Step 3 Repeat Step 2 for each of the DPNSS signaling services to be modified.

Deleting Cisco Access Gateway External Nodes

Step 1 Set the interface on the external node that is associated with the Cisco MGC software to the OOS state. See the documentation for your media gateway for more information on taking interfaces OOS.

For example, to delete an SCTP association named nasassoc1, you would enter the following command:

prov-dlt:ASSOCIATION:NAME="nasassoc1"

Step 3 Repeat the above steps for each SCTP association you want to delete from your provisioning data.

Provisioning Example

This section provides an examples of provisioning for the DPNSS feature. Additional examples of provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide at:

CTI connections failed

CTI Connection to the cluster has failed. PGW tries to establish CTI link to CTI Manager in a call manager cluster. If CTI link to a CTI manager fails, PGW automatically tries to establish the CTI link to an alternate CTI Manager in the cluster. This alarm indicates that PGW has not established a CTI link to any CTI Manager in the cluster.

Note Only one CTI Manager can be active (IS) at one time. Other CTI Managers are set in state OOS. In this case, OOS does not mean that the CTI Manager is Out Of Service, it means that it is not currently used.

Corrective Action

You might see this alarm while PGW is trying to connect to an alternate CTI Manager. If you have configured more than one CTI Managers for the cluster wait for few minutes to see if PGW can re-establish the CTI connection automatically.

Step 1 Verify that all the configured CTI Managers in the CCM cluster are operating normally.

Step 2 Verify that Ethernet interfaces between PGW and CTI Managers are working properly.

Step 3 Check if there is "CTI Version mismatch" alarms for the CTI Managers. If so, fix that problem.

Step 4 Contact the Cisco TAC for further analysis of the problem.

CTI version mismatch

The CTI version of the CTI Manager component configured on the PGW is not compatible with the version on the CTI Manager. PGW uses a CTI protocol to communicate with the CTI Manager. CTI protocol version is checked during establishing the CTI connection. The CTI connection can not be established if the versions are not compatible.

Corrective Action

Check the version of CTI Manager and install the appropriate patches on the PGW to make it compatible with the version on CTI Manager.

MDL Call Back feature insertion failure

MDL failed to insert Call Back feature entry to the times ten data base. MDL inserts entries to the times ten data base to keep track of the lists of users requesting Call Back service on a particular DN. If the insertion fails, the Call Back feature will not work.

Corrective Action

Check to see if the times ten data base is functioning correctly.

MDL Call Back feature deletion failure

MDL failed to delete the Call Back feature entry from the times ten data base. MDL deletes entries from the times ten data base when the Call Back request is fulfilled; after notifying the requesting user the called extension becomes free. If the deletion fails, the Call Back feature will not function correctly.

Corrective Action

Check to see if the times ten data base is functioning correctly.

Signaling Channel Troubleshooting Procedures

The following signaling channel troubleshooting procedures are new for this feature:

Resolving an Association Alarm

When you are referred to this section by an alarm indicating a failure on an association, perform the following steps:

Step 1 If this alarm occurs along with a LIF FAIL alarm on the local IP address (ADDR1 and ADDR2), proceed to Step 2. Otherwise, proceed to Step 4.

Step 2 Check the functioning of the cabling between the Cisco MGC and the LAN switch.

If the cables are functioning properly, proceed to Step 3.

If you find bad cable(s), replace them. If that resolves the problem, the procedure is complete. Otherwise, proceed to Step 3.

Step 3 Check the functioning of the associated LAN switch. See the documentation for your LAN switch for the steps necessary to verify its proper functioning.

If the LAN switch is functioning properly, proceed to Step 6.

If the LAN switch is not functioning properly, refer to documentation for the LAN switch for the appropriate troubleshooting procedures. If that corrects the problem, the procedure is complete. Otherwise, proceed to Step 6.

Step 4 Debug the IP connectivity between the Cisco MGC and the associated access gateway.

If the IP connectivity is working correctly, proceed to Step 5.

If the IP connectivity is not working correctly, make the necessary repairs. If that corrects the problem, the procedure is complete. Otherwise, proceed to Step 5.

Step 5 Determine the health of the associated access gateway.

If the access gateway is working correctly, proceed to Step 6.

If the access gateway is not healthy, fix it using the procedures in the user documentation for the access gateway. If that corrects the problem, the procedure is complete. Otherwise, proceed to Step 6.

Step 6 Contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, see Obtaining Technical Assistance.

Changing the Service State of an Association

To change the service state of an association, log in to the active Cisco MGC, start an MML session, and enter the following command:

set-association:assoc_name:serv_state[,confirm]

Where:

•assoc_name—MML name of the association you want to modify.

•serv_state— The service state to which you want to change. Valid values for IP links are IS, OOS, and FOOS.

•confirm—This parameter is required when you are setting the service state to OOS or FOOS.

Note This command cannot be used on the standby Cisco MGC.

For example, to set the service state of the association, assoc1, to OOS, enter the following command:

Monitoring and Maintaining

Step 7 The following sections contain the procedures required for proper monitoring and maintenance of this feature. For more information on operational tasks for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide at:

Managing Signaling Channels

Retrieving the Service State of an Association

To retrieve the service state for an individual association, log in to the active Cisco MGC, start an MML session, and enter the following command:

rtrv-association:assoc_name

For example, to retrieve the service state of an association called assoc1, enter the following command:

rtrv-association:assoc1

The system returns a message similar to the following:

Media Gateway Controller 2000-03-26 20:26:18

M RTRV

"assoc1:IS"

To retrieve attributes for all of the associations, log in to the active Cisco MGC, start an MML session, and enter the following command:

rtrv-association:all

The system returns a message similar to the following:

Media Gateway Controller 2000-03-26 19:23:23

M RTRV

"assoc1:OOS

"assoc2:OOS

"assoc3:OOS

"assoc4:OOS

The valid service states for an association are described in the following sections. If the association is in any state other than IS, attempt to bring it into service, as described in Resolving an Association Alarm.

Primary Service State of an Association

The PST field shows the current primary service state of the association. Table 1 lists the valid primary service state values.

Table 1 Primary Service State of an Association

Link State ID

Link State

Description

INB

Install busy

When a system is first configured, all associations default to this state.

IS

In-service

Association is IS and fully operational. This is its normal operating state.

OOS

Out-of-service

Association is OOS. The system is actively trying to restore the association.

Secondary Service State of an Association

The SST field shows the current secondary service state of the specified association. Table 2 lists the valid secondary service state values.

Table 2 Association Secondary Service States of an Association

Link State ID

Link State

Description

COOS

Commanded out-of-service

Association has been commanded OOS by the operator.

STBY

Standby

Association is on the standby Cisco MGC.

CONF

Configuration

Association is OOS due to a configuration failure.

Retrieving the Service State of an IP Route

To retrieve the service state for an individual IP route, log in to the active Cisco MGC, start an MML session, and enter the following command:

rtrv-iproute:iproute_name

For example, to retrieve the service state of an IP route called iprte1, enter the following command:

rtrv-iproute:iprte1

The system returns a message similar to the following:

Media Gateway Controller 2000-03-26 20:26:18

M RTRV

"iprte1:IS"

To retrieve attributes for all of the IP routes, log in to the active Cisco MGC, start an MML session, and enter the following command:

rtrv-iproute:all

The system returns a message similar to the following:

Media Gateway Controller 2000-03-26 19:23:23

M RTRV

"iprte1:IS

"iprte2:IS

The valid service states for an IP route are described in the following sections. If the route is in any other state than IS, attempt to bring it into service, as described in Changing the Service State of an IP Route.

Primary Service State of an IP Route

The PST field shows the current primary service state of the IP route. Table 3 lists the valid primary service state values:

Table 3 IP Route Primary Service States

Link State ID

Link State

Description

IS

In-service

Route is IS and fully operational. This is its normal operating state.

OOS

Out-of-service

Route is OOS. The system is actively trying to restore the link.

Secondary Service State of an IP Route

The SST field shows the current secondary service state of the specified IP route. Table 4 lists the valid secondary service state values:

Planning for Provisioning

This section lists the data that you must gather to successfully provision this feature. For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide at:

Collecting DPNSS Path Data

The path data represents an DPNSS signaling service to a particular Cisco access gateway. See Restrictions for more information on the Cisco access gateways that require the use of a DPNSS signaling service. 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

Collecting IP Route Data (optional)

The IP route represents a static IP route. IP routes are required for this feature only when the Cisco PGW hosts are not on the same subnet as the Cisco access gateways. If your system requires IP routes, you must be ready to enter the following data:

•mod_ver—A new configuration version name for a version 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 may use the prov-add, prov-ed, or prov-dlt MML commands to add, modify, and delete components on your system. This document describes how to add, modify, and delete M3UA and SUA components. For more information on provisioning other components on your Cisco PGW 2200, see the Cisco Media Gateway Controller Software Release 9 Provisioning Guide at:

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.

Once a provisioning session is underway, you may use the prov-add, prov-ed, or prov-dlt MML commands to add, modify, and delete components on your system. This document describes how to add, modify, and delete M3UA and SUA components. For more information on provisioning other components on your Cisco PGW 2200, see the Cisco Media Gateway Controller Software Release 9 Provisioning Guide at:

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.

Using the prov-cpy or prov-dply MML commands can severely impact your system's call processing performance, depending on the extent of your provisioning changes. We recommend that you issue these commands during a maintenance window when traffic is minimal.

Use the prov-cpy MML command to save and activate your changes on the active Cisco MGC. This command is typically used to save and activate changes on a Cisco MGC in a simplex configuration. However, you can use the prov-cpy MML command on Cisco MGCs in high-availability or continuous-service configurations, to save and activate your changes on the active Cisco MGC. If you choose to do this, you should enter the prov-sync MML command immediately afterwards, to have your changes saved and activated on the standby Cisco MGC.

Note When you enter the prov-cpy command, your provisioning session is automatically ended. If you want to make additional provisioning changes, you must start a new provisioning session as described in Starting a Provisioning Session.

Using the prov-sync MML command can severely impact your system's call processing performance. We recommend that you issue these during a maintenance window when traffic is minimal.

Note When the prov-sync MML command is used to synchronize the provisioning settings on the standby MGC host with current settings on the active MGC host, the system does not indicate when the synchronization process has failed.

Use the prov-dply MML command to save and activate your changes on the active and standby Cisco MGCs. This command is typically used to save and activate changes on Cisco MGCs in a high-availability or continuous-service configurations. Do not use this command on a Cisco MGC in a simplex configuration.

Note When you enter the prov-dply command, your provisioning session is 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 Starting a Provisioning Session.

Ending a Provisioning Session Without Activating Your Changes

You may 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:

You cannot use this command for components that are used to retrieve signaling or routing properties (that is sigsvcprop, lnksetprop, and trnkgrpprop). The properties for only one signaling or routing component can be listed per command instance. Use the following format:

prov-rtrv:propComp:name="compName" | name="ss7famName"

Where:

propComp—MML component name appropriate to the property type you want to retrieve, as listed below:

sigsvcprop—Provides maintenance access to the properties of signaling services trnkgrpprop—Provides maintenance access to the properties of trunk groups lnksetprop—Provides maintenance access to the properties of linksets

compName—MML name of a previously provisioned signaling service or trunk groupss7famName—MML name of the SS7 family associated with the desired linkset

For example, to view the provisioning data for all signaling services, you would enter the following command:

prov-rtrv:naspath:"all"

The system returns a response similar to the following:

<< get system response >>

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 at:

Note You cannot use this command for components that are used to retrieve signaling or routing properties (that is sigsvcprop, lnksetprop, and trnkgrpprop). The properties for only one signaling or routing component can be listed per command instance. Use the following format:

prov-rtrv:propComp:name="compName" | name="ss7famName"

Where:

propComp—MML component name appropriate to the property type you want to retrieve, as listed below:

sigsvcprop—Provides maintenance access to the properties of signaling services trnkgrpprop—Provides maintenance access to the properties of trunk groups lnksetprop—Provides maintenance access to the properties of linksets

compName—MML name of a previously provisioned signaling service or trunk groupss7famName—MML name of the SS7 family associated with the desired linkset

For example, to view the provisioning data for all signaling services, you would enter the following command:

prov-rtrv:naspath:"all"

The system returns a response similar to the following:

<< get system response >>

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

The system returns a response similar to the following:

<< get system response >>

Measurements

Table 5 contains the system measurements that are added to support this feature. For information on the other system measurements, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide at:

Service ID (Tag: 4221)

Description/Purpose: Indicates the feature id for the supplementary service.

Format: Integer

Length in Octets: 1

Data Value:

CAll Back Request = 8

Call Back Cancellation = -9

Call Back Notification = 10

Extension Status = 11

ANSI/ITU Variations: None.

Extended Data Value: No extended value.

General Information: This id is the enumeration of the supplementary service performed for the call.

MGC Release: Release 9.6(1) and later.

Answered (1010)

Deselected (1020)

Aborted (1030)

Release (1040)

Interrupted (1050)

Ongoing (1060)

Slave Long Duration Call (1061)

Maintenance (1070)

External DB (1080)

End of Call (1110)

Slave End of Call (1111)

N

N

N

Y

N

N

N

N

N

Y

N

Components

The sections below describe the provisioning components that are added and modified for this feature. For information on the rest of the components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide at:

The following rules apply when you create or edit DPNSS signaling paths:

•The maximum number of combined DPNSSPATHs and IUA NASPATHs per IUA external node is 112.

•An ASSOCIATION must be defined with the same EXTNODE attribute as the DPNSSPATH. If this ASSOCIATION has not been defined when the DPNSSPATH is added/edited, a warning is issued. If the ASSOCIATION still has not been defined when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

•If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning message is issued to inform you that the DPNSSPATH must also be deleted. If it has not been deleted when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

Note NAME is the only parameter for this command that cannot be modified.

To create or edit IP routes, follow these rules:

•The NETMASK attribute is validated by the system. For your provisioning setup to work correctly, its value (when converted to binary) must have at least one leading 1 and cannot have any trailing 1s after the first 0. The values 255.255.0.0 and 255.255.255.128 are valid. The values 0.0.255.255, 255.0.0.255, and 0.0.0.0 are invalid.

•Ensure that the destination resolves to a non-zero address.

•When the resolved destination address is bit ORed with the netmask value, the result is equal to the netmask. For example, a destination of 10.11.12.13 and a netmask of 255.255.0.0 are invalid because the ORed result would be 255.255.12.13, which is not equal to 255.255.0.0.

•The combination of DESTINATION, NETMASK, and IPADDR must be unique for each IP route.

•The combination of DESTINATION, NETMASK, and PRI must be unique for each IP route.

•When an IP route is specified in a link object (for example, IPLNK, SESSIONSET, or ASSOCIATION), the IP address resolved from the PEERADDR attribute must be checked against the DESTINATION and NETMASK attributes to verify that the IPROUTE is valid.

•When an IP route is specified in a link object (for example, IPLNK, SESSIONSET, or ASSOCIATION), the IPADDR must match the IPADDR of the link.

•When an IPROUTE is not specified for a link object (having that option), the IP address resolved from the PEERADDR attribute must be checked against the defined IPROUTES to verify that it should not be assigned an IPROUTE. If the PEERADDR is on the same subnet as the DESTINATION (based on the NETMASK), and if the IPADDR matches the IPADDR of the link object, then use IPROUTE.

•If the NEXTHOP attribute is a host name or symbolic name from XECfgParm.dat, it can resolve to the address 0.0.0.0, which indicates that the IPROUTE is not used. The IPROUTE status shows up in the rtrv-iproute:all command output when in the OOS, OFF_DUTY state.

•If the resolved NEXTHOP address is not 0.0.0.0, it must be on the same subnet as the IPADDR.

•Only one association with a type of IUA can be assigned to an external node.

•If the type of the association is IUA, the associated external node must have its ISDN signaling type set to IUA, and that external node must be able to support IUA signaling.

•If two associations have the same port value, the values of IPADDR1 and IPADDR2 must either be the same or both must be different.

•The values of IPADDR1 and IPADDR2 must be different.

•If the value of IPPRECEDENCE is not ROUTINE, the value of DSCP must be N/A.

•If the value of DSCP is not N/A, the value of IPPRECEDENCE must be ROUTINE.

•The value of MAXRTO must be greater than or equal to the value of MINRTO.

•When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or IPADDR2, that peer IP address cannot be on the subnet of any other local interface, even if it is not defined within the Cisco MGC software.

•When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or IPADDR2, an IP route (IPROUTE1 or IPROUTE2, respectively) must be specified.

•When an IP route is specified, the values set in PEERADDR1 and PEERADDR2 are checked against the DESTINATION and NETMASK values of the IP route(s) to verify that the IP route is valid.

•When an IP route is specified, its value for IPADDR must match the related IP address of the association. In other words, IPROUTE1 should have an IPADDR that matches IPADDR1 on the association, and IPROUTE 2 should have an IPADDR that matches IPADDR2 on the association.

•When an IP route is not specified, the IP address resolved from the PEERADDR1 or PEERADDR2 parameter is checked against the defined IP routes to verify that it should not be assigned to one of those IP routes. If the peer address is on the same subnet as an IP route, the link should use that IP route.

•The value of PEERADDR1 cannot be 0.0.0.0 or 255.255.255.255, and the value of PEERADDR2 cannot be 255.255.255.255.

•When a host name is specified for a peer IP address, the host name must resolve to an IP address.

•PEERADDR1 and PEERADDR2 can resolve to the same IP address. If the external node has only one IP address and two IP addresses (IPADDR1 and IPADDR2) are defined, PEERADDR2 should be set to the same value as PEERADDR1.

•When you are deleting an association and a NASPATH uses the same external node, a warning message is issued to inform you that the NASPATH must also be deleted. If it has not been deleted when the provisioning session is copied or deployed, an error message is generated and the copy or deployment stops.

•The value of PORT cannot be set to the same value as the PORT attribute of any IP link, session set, SIP link, or SS7 signaling gateway link.

•If a value for IPADDR2 or PEERADDR2 is specified, values for IPADDR1 and PEERADDR1 must also be specified. In other words, you cannot have one local address and two remote addresses, or two local addresses and one remote address.

•An IP link, session set, SS7 signaling gateway link, or another association with a different external or signaling gateway node cannot use the resolved value set in PEERADDR1 or PEERADDR2.

•Only one association can be defined to an SS7 signaling gateway process (SGP).

•A value for EXTNODE can be defined only when the association type is IUA.

•A value for SGP can be defined only when the association type is M3UA or SUA.

•The maximum number of associations with a type of M3UA is defined in the XECfgParm.dat parameter, M3UA.maxSgp.

•The maximum number of associations with a type of SUA is defined in the XECfgParm.dat parameter, SUA.maxSgp.

Properties

CallBackDBCleanUpTimer

This property defines the timeout value for Call Back DB cleanup in milliseconds.

Valid Values:

600000-10800000 (10 minutes to 3 hours)

Default Value:

3600000 (1 hour)

Domain:

_XE Parameter _X_SigPath _LinkSet X_Trunk Group _MGC (Choose one)

Example:

mml>prov-ed:sigsvcprop:name="stisigpath",MaxCBRequest ="9"

MaxCBRequest

Purpose:

This property defines the maximum number of Call Back requests allowed in the queue per CTI sigpath.

Valid Values:

1-50

Default Value:

10

Domain:

_XE Parameter _X_SigPath _LinkSet X_Trunk Group _MGC (Choose one)

Example:

mml>prov-ed:sigsvcprop:name="stisigpath",MaxCBRequest ="9"

TimeOutCBNU

Purpose:

This property defines the timeout value for Call Back When Not Used against QBE sigpath measured in minutes.

Valid Values:

60-480

Default Value:

480

Domain:

_XE Parameter _X_SigPath _LinkSet X_Trunk Group _MGC (Choose one)

Example:

mml>prov-ed:sigsvcprop:name="ctisigpath",TimeOutCBNU ="200"

TimeOutCBWF

Purpose:

This property defines the timeout value for Call Back When Free against QBE sigpath measured in minutes.

Valid Values:

60-180

Default Value:

180

Domain:

_XE Parameter _X_SigPath _LinkSet X_Trunk Group _MGC (Choose one)

Example:

mml>prov-ed:sigsvcprop:name="ctisigpath", TimeOutCBWF = "100"

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 at:

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco TAC Website

The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:

For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

•Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

•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: