Guest

Cisco PGW 2200 Softswitch

Call Limiting

  • Viewing Options

  • PDF (850.8 KB)
  • Feedback
Call Limiting

Table Of Contents

Call Limiting

Feature Overview

Precedence Rules for Location Label Use

Location Label Handling During Rerouting

Location Label Handling During Service Actions

Location Label Provisioning

Removing and Adding Location Labels

Enabling or Disabling Call Limiting

System Actions at Start Up

System Actions at the Start of Call Handling

System Actions at Switchover

System Actions with INAP Calls

Normal Basic INAP CS1 Call with Call Limiting Rejection

Call Processing with Location Labels

Call Limiting Check with Location Labels Present, Call Permitted

Call Limiting Check with no Location Label Data Present

Call Limiting Check with Location Labels Present, Call Rejected

Benefits

Related Documents

Supported Platforms

Prerequisites for Using This Feature

XECfgParm.dat Configuration Tasks

Verifying the XECfgParm.dat Configuration

Provisioning Tasks

Enabling the Call Limiting Functions

Enabling the Call Limiting Control Parameter the First Time

Dynamically Enabling Call Limiting

Adding a Location Label

Dynamically Disabling Call Limiting

Modifying Call Limiting Components

Modifying a Label Call Limit

Retrieving Location Labels

Deleting Call Limiting Components

Provisioning Examples

Applying Call Limiting Over DPNSS

Applying Call Limiting to Incoming and Outgoing Trunk Groups

B-number Based Call Limiting Scenario

Applying Call Limiting to a SIP Trunk Group

Applying Call Limiting to an H.323 Trunk Group

Applying Call Limiting to the DPNSS Trunk Groups

Applying Call Limiting to an SS7 ISUP Trunk Group

Applying Call Limiting to Digit Strings in a Dial Plan

Applying Call Limiting to Multiple Trunk Groups

Applying Call Limiting to IP Addresses

Applying Call Limiting to an MGCP Gateway

Playing an Announcement when the Call Limiting Threshold is Exceeded

Dial Plans

Dial Plan Provisioning

Provisioning Call Limiting for an A-number

Provisioning Call Limiting for a B-number

Provisioning the OVERRIDE_CALLIM Result Type for Number Analysis

Dial Plan Examples

Troubleshooting Provisioning Data

Alarm Troubleshooting Procedures

locLabelNotFound

locTable AccessFail

Command Reference

New MML Commands

SET-CALLIM—Sets the Call Limiting Function

RTRV-CALLIM—Retrieves the Call Limiting Function Status

PROV-ADD:LOCLABEL—Adds the Location Label

PROV-DLT:loclabel—Deletes the Location Label

PROV-ED:loclabel—Edits the Location Label

PROV-RTRV:loclabel—Retrieves the Location Label

Stopping a Call

Killing a Call

Reference Information

XECfgParm.dat Parameters

Alarms

New Alarms

Internal Cause Codes

Logs

New Logs

Measurements

Billing Interface

Rejecting Location Label (Tag: 4232)

Rejecting Location Label Direction (Tag: 4233)

Components

New Components

Modified Components

Result Types

Result Type Definitions

Provisioning Worksheets

Monitoring and Maintaining the Feature

Obtaining Documentation and Submitting a Service Request

Glossary


Call Limiting


Document Release History

Publication Date
Comments

July 12, 2005

Initial release of this document.


Feature History

Release
Modification

9.6(1)

This feature was introduced on the PGW 2200.


This document describes the Call Limiting feature in the following sections:

Feature Overview

Supported Platforms

Prerequisites for Using This Feature

XECfgParm.dat Configuration Tasks

Provisioning Tasks

Dial Plans

Monitoring and Maintaining the Feature

Provisioning Examples

Provisioning Call Limiting for an A-number

Command Reference

Reference Information

Obtaining Documentation and Submitting a Service Request

Glossary

Feature Overview

The Call Limiting feature on the Cisco Media Gateway Controller (MGC) allows a service provider to limit the number of simultaneous calls across telephony interfaces. The telephony interfaces include SS7, Session Initiation Protocol (SIP), H.323, ISDN User Part (ISUP), E-ISUP, DPNSS, QSIG, and PRI. Call Limiting allows the service provider to limit calls for quality purposes (for example, bandwidth limitations) or to limit the number of simultaneous calls to a total agreed upon by the service provider and its customers.

Through the use of as many as 3000 location labels, the Call Limiting feature enables the MGC to limit the number of simultaneous calls sent to or accepted from a specific destination or source. This includes calls made to a Public Switched Telephone Network (PSTN) E.164 number, or a specified SIP device, H.323 device, a route to DPNSS, QSIG, or PRI gateway, as well another MGC or an HSI using E-ISUP.

Emergency and priority calls can be permitted, even though a call limit might have been reached. The OVERRIDE_CALLIM result type makes that possible. It may also be necessary to allow calls from a certain origin to have priority and avoid call limiting actions. The presence of the OVERRIDE_CALLIM result type indicates that for such calls, any call limiting actions are ignored and the call is allowed to set up as soon as possible.

The Call Limiting feature uses a location label concept. A location is a label associated with one or more sources and destinations, so calls can be limited to or from one or more interfaces. As many as 4 location labels can be applied to a call, with two location labels on the inbound call leg and two location labels on the outbound call leg.

The location label has a call threshold limit that can be set. Once the call threshold for a location is exceeded, all other calls to or from that location are rejected.

Call limit counters are incremented on the incoming and outgoing call sides after successful outgoing circuit selection and are decremented at call release.


Note For a trunk group or sigPath, there can be a different location label in each direction, allowing call limiting on incoming or outgoing calls.


The same label identifier can be assigned to single or multiple instances of:

Trunk groups or sigPathsThis allows users to limit the number of calls to E1, or a combination of E1s. It also allows the control of calls between MGCs and the number of calls to and from VoIP networks using H.323 and SIP.

Formal number analysis (A-number or B-number)Call Limiting allows calls to certain destinations to be limited, based on leading digits, such as area code or full B-number analysis for services like Tele-voting. This also allows calls from specific IP addresses to be limited by combining the use of dial plan switching based on incoming source address with A-number analysis location label assignment.

Precedence Rules for Location Label Use

The incoming call leg can use two separate location labels, one label assigned to the incoming trunk group or sigPath and one label assigned during the A-number analysis phase in the dial plan.

If there are multiple instances of a result type, the analysis location label used is the last location label result type encountered in A-number analysis.

Similarly, the outgoing call leg can also use two separate location labels, one assigned to the outgoing trunk group or sigPath and one returned during B-number analysis. The B-number analysis location label is the last found label result type encountered during the B-number analysis process.

Location Label Handling During Rerouting

If a call undergoes rerouting, the incoming call leg limit counter is unaffected. However, both the B-number analysis delivered counter (if present) and the outgoing call leg limited counter are decremented. A new label check is performed (against both the B-number label and the new outgoing call leg label) at the end of the subsequent route analysis. If the call is permitted on this new attempt, both the B-number analysis delivered counter (if present) and the outgoing call leg limited counter are incremented.

Location Label Handling During Service Actions

When the call instance is handling a call with service layer actions involved could result in a new trunk group. For example, if route optimization or call back when free is enabled, then an existing terminating call control (TCC) or originating call control (OCC) call leg could be disconnected, making way for a half-leg call or reconnection to a new OCC or TCC side, resulting in a new trunk group. For call limiting to be permitted, the call limiting actions are performed at a level outside of any service layer controls. Thus the call limiting actions are driven by incoming call requests and outgoing call attempts, regardless of any higher level service actions that provoked them. If a call leg is deleted, the call limit counters are decremented and the label discarded. And if a new call leg is set up, the call limiting actions apply when the outgoing call is attempted on the new call leg.

When call legs are deleted, any location labels associated with that call leg side and any number analysis location labels (if present) have their active call counters decremented. Thus:

If an originating side call leg is deleted, both the A-number analysis location label (if present) and the location label pertaining to the originating side trunk group or sigPath have their active call counters decremented.

If a terminating side call leg is deleted, both the B-number analysis location label (if present) and the location label pertaining to the terminating side trunk group or sigPath have their active call counters decremented.

Location Label Provisioning

Provision a location label by using the MML command for every label defined on the system and its associated call limit.

Once provisioning is complete, the label data is assigned to a trunk group or sigPath, where it appears as new columns in trunkGroups.dat or sigPath.dat as appropriate.

If the location labels are required as a result of A-number or B-number analysis, the associated MML provisioning commands populate the dial plan with the LOC_LABEL result type. This result type provides the componentId that is used to identify the location label.

Removing and Adding Location Labels

Location labels can be added and removed at any time, but are subject to the following conditions:

You cannot remove a location label when there are calls associated with that label. Attempting to delete a label while there is a call associated with the label causes the provisioning to be rejected with the message, "This Label is in use by calls in the system. Ensure there is no call using this label."

You cannot remove a location label of the same name (string) and then added back onto the system without manually switching the call limiting functionality off and back on. This is to help prevent label counter corruption from occurring.

You can add a location label at any time, because it is only used when the label is assigned against the trunk group or in analysis and starts cleanly with the call counters at 0.

Enabling or Disabling Call Limiting

The call limiting feature is started the first time when you set the XECfgParm.dat parameter CallLimitingControl to enable. Once the call limiting capability is enabled, you can enable or disable it by using the set-callim MML command without stopping and starting the MGC software.

Additionally, if the XECfgParm.dat parameter CallLimitingControl is set to disable, once the MGC is running, you can enable the call limiting functionality by using the set-callim:enable MML command. Thus the call limiting functionality can be enabled or disabled through the set-callim MML command regardless of the initial value of CallLimitingControl.

System Actions at Start Up

Once the system starts up, the locationLabel.dat file is read and a table is built in local memory containing the following fields for each label:

Location label (actually the componentId identifying that label)

Call limit for the label

Active call counter value for this label (initially 0)

System Actions at the Start of Call Handling

At the start of every call instance, the MGC verifies the CallLimitingControl parameter value (which is the value of call limiting for the whole platform), or the set-callim MML command value.

System Actions at Switchover

In the event of switchover for active to standby MGCs, there is no preservation of call limiting data. As a result, when the standby MGC is started, the location label table is rebuilt with all counters starting from 0.

When the existing calls are restarted on the newly active (formerly the standby side), call limiting is set to off for these calls, so that any counter corruption during failover is avoided.

System Actions with INAP Calls

When the MGC is handling a call involving Intelligent Network Application Protocol (INAP) Capability Set 1 (CS1) interchanges with a Service Control Point (SCP), call limiting can still be used. Thus, when a call is ready to go forward on the terminating side of the MGC, a call limiting check is applied with all involved labels at this point in the call. At call answer, the successful call measurement counters are incremented; and at call release, the active call counters are decremented.

The call-counter action co-exists with any event reporting to the SCP, as required in normal INAP CS1-related call handling.

Normal Basic INAP CS1 Call with Call Limiting Rejection

At the point when the call to the MGC terminating side is to be forwarded, the call limiting check is applied. If the call is rejected, then the action taken depends on the monitoring mode for the route select failure event. The monitoring modes for a route select failure event are:

Interrupted

Notify and continue

Monitor Mode Is Interrupted

An event report (route select failure) is made to the SCP and a response is awaited, because the SCP must supply further instructions. The SCP responds with one of the following:

A ReleaseCall message prompting the MGC to clear the call. When the call is fully cleared, a CDR captures the rejecting label information.

A new connect operation that provokes a new call attempt (new B-number and possibly new A-number). The MGC clears the TCC side, and both channel connections are reset to a condition ready to invoke number analysis again. New number analysis might provide new location labels (or none), leading to Route analysis. For a valid call, circuit selection is performed on the returned trunk group, and both originating and terminating call sides are seized and ready to process the call. At this point, a new call limiting check is performed, and all the location labels from Number analysis are submitted for validation. If everything is valid, the call progresses normally and at answer the successful measurement counters for all involved labels are incremented. At call clear down, the active call counters are decremented.

Monitor Mode Is Notify and Continue

An event report (route select failure) is made to the SCP; but as is the case with Notify mode, there is no need to wait for an SCP response. As a result, the action taken depends on whether or not further routing options (routes and trunk groups) are available in analysis. Either of the following actions can apply:

No further routing option—In this case, the MGC clears the call by Cause analysis (having internally set the cause to IC_CALL_LIMIT_REJ). Upon full call clearing, a CDR captures the rejecting location label information.

Further routing options exist—In this case, the MGC can try again by clearing the terminating call side and then requesting new routing, which is effectively an advance trunk group operation. The MGC clears the TCC side and the terminating side channel connection and resets it to a condition ready to invoke new Route analysis. Successful routing analysis provides a new trunk group to try. Circuit selection is also performed on the new trunk group. Then both the originating and terminating sides are seized to be ready to go forward with the call. At this point, a new call limiting check is made. In this case, the existing labels from Number analysis are retained and any B-number labels resubmitted in this second call limiting request. If everything is valid, the call progresses normally; and at answer, the successful measurement counters for all involved location labels are incremented. At call clear down, the active call counters are decremented.

Call Processing with Location Labels

The processing of location labels is integrated into normal call handling and is broken down into specific activities according to the point in the call.

At the point in a call where analysis has been carried out and before the call is sent to the terminating (TCC) side, a check is performed of the location label (if present) for the originating side, terminating side, any A-number analysis delivered label, and any B-number analysis delivered label. At this point, the call can be rejected, permitted, or released; and the call actions are summarized as follows:

For rejected calls, a result is generated, indicating the call is rejected and includes the name and componentId of the rejecting label. The call is then subjected to Cause analysis for possible re-routing. However, if the rejection is caused by the originating side label or the A-number or B-number analysis location label, no route is applied, and the call is cleared, even if Cause analysis delivers a routing result. When the call is cleared, the rejected calls measurement counter for the location label (componentId) that caused the call rejection is incremented. In addition, the rejecting label name is included in a call context variable ready for CDR collection.

For permitted calls, when the MGC is receiving the answer indication from the terminating side, the successful calls measurement counters for all location labels present are incremented.

For a released terminating side call, when the final internal release signal is received, a check is made for any B-number analysis delivered label, and then the active call counter decrements for the termSideLabel and the B-number label (if present).

For a released originating side call, when the final internal signal is received, a check is made for any A-number analysis delivered label, and then the active call counter decrements for the origSideLabel and the A-number label (if present).

Call Limiting Check with Location Labels Present, Call Permitted

Normal call handling takes place up to the point when a call is made to Generic analysis for A-number or B-number analysis and Routing analysis. On switched calls, a routing result from B-number analysis occurs, and the analysis continues with the Routing analysis stage. After that, if a call is successful, analysis returns a trunk group and optional data results back to the Universal Call Model (UCM) module. On signaling (that is, nailed) calls, an indication of analysis performed from Generic analysis is returned, along with any optional data results. In each case, the optional data results include any LOC_LABEL results that have been collected.

In both A-number and B-number analysis, the LOC_LABEL result type can be collected and stored.

Call Limiting Check with no Location Label Data Present

When the engine is making the post-analysis, call limiting request, where no location labels have been found in A-number or B-number analysis, there is no data input. For the engine to determine if any location labels are present for the originating or terminating sides, the trunkGroup.dat or sigPath.dat files (as appropriate) are read. If no labels are found against either side, then the call is permitted, and no originating or terminating label parameters are populated.

Also, if call limiting is disabled, no further call limiting actions are taken for this call. If there is no call limiting action required for this call, the call is processed normally. No further call limiting counter update requests by the engine are invoked because there is no location label data.

Call Limiting Check with Location Labels Present, Call Rejected

The call can be rejected for call limiting when the engine is checking against the labels found for the originating side, terminating side, or as a result of A-number or B-number analysis. This check is made when the UCM is preparing to start sending to the TCC side.

The originating and terminating sides are checked by the engine for location labels by reading the trunkGroup.dat or sigPath.dat data files, as appropriate. Any defined location labels are collected to determine the call viability with respect to the location labels. The order of location label checking performed by the engine is origSideLabel, A-number label, B-number label, and termSideLabel. The first label to reject is the label returned and saved for CDR purposes. If a label is present against both the sigPath and the trunk group, the trunk group label is the label used and checked against.

With one or more location labels present, the Engine validates the call according to the current active call counter level for each label present. This is done by a reading of the internal table. For each label found, the Engine checks that the new call request does not put the value in the active call counter field over its limit. For example, if the call limit is set to 100, call number 99 and call 100 are allowed. But call attempt 101 is rejected.

If a new call request would cause the value in the active call counter field to be exceeded a rejection result is returned, accompanied by both the location label componentId and the location label string (not the componentId) of the label that caused the rejection. When the Engine receives this information, the rejecting location label name is captured for later CDR use by saving the rejecting label name into call context.

A rejected call can be referred by the UCM for Cause analysis, which can return a result that provokes rerouting or a reattempt. The routing or reattempt is allowed, as long as the label rejection was against the terminating side trunk group or sigPath. If any other label caused the rejection, then the result is ignored and call clear down continues. If Cause analysis does deliver a routing result (or maybe a dial plan change leading to a routing result), then (providing this is an allowed action) the call is handled as normal. But once again when preparing to send to the TCC side, the B-number analysis location label and terminating side label are checked by the Engine.

Once a rejection has been detected, the rejecting label measurement counter for the rejecting label is incremented.


Note If a call is rejected, the active call counters are not incremented for any of the labels present.


Once clearing is completed for each side, the identity (name string) of the rejecting location label is saved for use in CDR collection.

Benefits

This feature provides the following main benefit areas.

Improved Network Planning

The service provider can better plan the IP network by limiting the number of calls.

Improved QoS for Permitted Calls

The service provider can ensure a better QoS for the calls that are allowed by not allowing bandwidth allocation to be exceeded.

Improved Contractual Control

The service provider can control the number of calls that are contractually allowed to/from a certain destination/origination. A service provider can then charge for each simultaneous call allowed on a certain IP link.

Improved Device Allocating

Certain devices support only a limited number of calls, for example an IP-based announcement device. Once the device limit is reached, the MGC can select a route to another IP-based announcement device.

Related Documents

This document contains information that is related strictly to this feature. The documents that contain additional information related to the Cisco MGC are listed below:

Release Notes for Cisco Media Gateway Controller Software Release 9.6(1)

Cisco Media Gateway Controller Hardware Installation Guide

Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller

Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide

Cisco Media Gateway Controller Software Release 9 Provisioning Guide

Cisco Media Gateway Controller Software Release 9 Dial Plan Guide

Cisco Media Gateway Controller Software Release 9 MML Command Reference

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

Cisco Media Gateway Controller Node Manager User's Guide

Supported Platforms

The hardware platforms supported for the Cisco MGC software Release 9.6(1) are described in the Cisco Media Gateway Controller Hardware Installation Guide.

No new standards, MIBs, or RFCs are supported by the Call Limiting feature.

Prerequisites for Using This Feature

You must have Cisco MGC software Release 9.6(1). Prerequisites for this release can be found in the Release Notes for Cisco Media Gateway Controller Software Release 9.6(1).

XECfgParm.dat Configuration Tasks

This section presents the steps necessary for configuration of the Cisco MGC software to support this feature. If you are installing and configuring the Cisco MGC software on your system for the first time, use the procedures in the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide, coming back to this section once you encounter the engine.CallLimitingControl parameter in the XECfgParm.dat file.


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


Caution Do not modify the other XECfgParm.dat parameters.

To enable Call Limiting control on the MGC, 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 MGC hosts using a text editor, such as vi.

Step 2 Search for the engine.CallLimitingControl parameter and enter 1 on the active and standby Cisco MGC hosts to enable the Call Limiting feature.

Step 3 If you are installing and configuring your Cisco MGC software for the first time, return to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide and continue from where you left off.


Verifying the XECfgParm.dat Configuration

Use the procedure below if you believe the Call Limiting feature value you have entered in XECfgParm.dat is incorrect. 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.

To verify the XECfgParm.dat setting for the Call Limiting feature, perform the following steps.


Caution Do not modify the other XECfgParm.dat parameters. Stopping the MGC software causes a loss of all service.


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 file using a text editor, such as vi.

Step 3 Search for the engine.CallLimitingControl parameter and enter a 1 to enable call limiting; or enter a 0 to disable call limiting.

Step 4 Save your changes and close the text editor.

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

/etc/init.d/CiscoMGC stop 

Step 6 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 7 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 8 Repeat Step 2 through Step 7 for the newly standby Cisco MGC host.


Provisioning Tasks

The Call Limiting feature can be provisioned on:

A-numbers

B-numbers

sigPaths

Trunk groups

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

Enabling the Call Limiting Functions

Modifying Call Limiting Components

Provisioning Examples

If you are not familiar with provisioning the MGC, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for more information on MGC provisioning. If you are already familiar with MGC provisioning, you may refer to the "Dynamically Enabling Call Limiting" section to begin provisioning the Call Limiting feature.

Enabling the Call Limiting Functions

This section contains the procedures that you must perform to enable the Call Limiting feature on your Cisco MGC. When provisioning the components that enable the Cisco MGC to support Call Limiting, perform the procedures in the following order:

Enabling the Call Limiting Control Parameter the First Time

Dynamically Enabling Call Limiting

Adding a Location Label

Dynamically Disabling Call Limiting

Enabling the Call Limiting Control Parameter the First Time

When enabling the Call Limiting feature for the first time, you change the CallLimitingControl parameter setting in the XECfgParm.dat file. To do this, perform the following procedure.

If you have already enabled the Call Limiting feature, you can go to "Dynamically Enabling Call Limiting" section.


Caution Performing this procedure stops the functioning of the Cisco MGC software. Perform this step only while in contact with Cisco Technical Assistance Center (TAC) personnel.


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 file using a text editor, such as vi.

Step 3 Search for the engine.CallLimitingControl parameter and ensure its value is set to 1 (enable call limiting).

Step 4 Set the engine.CallLimitingControl parameter to 1 (enable call limiting).

Step 5 Save your changes and close the text editor.

Step 6 Manually stop the Cisco MGC software on your standby Cisco MGC by logging in to your active Cisco MGC as root and enter the following command:

/etc/init.d/CiscoMGC stop 

This action disables the automated startup script.

Step 7 Once the software shutdown is complete, manually start the Cisco MGC software on your standby Cisco MGC by logging in to your active Cisco MGC as root and enter the following command:

/etc/init.d/CiscoMGC start 

Step 8 Perform a manual switchover from the active Cisco MGC, by logging in to the active Cisco MGC, starting an MML session, and entering the following command:

mml> sw-over::confirm 

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


Caution Switchover operations cause the loss of all SS7 messages transmitted to the Cisco MGC for approximately 3 seconds. This affects unstable in-progress calls as well as new calls. Stable in-progress calls are not affected.

Step 9 Repeat Step 1 through Step 8 for the newly standby Cisco MGC.


Dynamically Enabling Call Limiting

Once the Call Limiting feature has been enabled in XECfgparm.dat, you can dynamically change the feature status.

After you have dynamically disabled call limiting, while the MGC is running, you can also reenable this feature. To enable the Call Limiting feature while the MGC is running, use the set-callim MML command to set its property value to enable. This action allows safe clear-down of existing calls, but it does not corrupt the label counter values.

Once the MML command to enable call limiting is executed, all new calls are processed according to the call limiting settings for each call (counters initially starting from 0).

For calls in progress before restarting call limiting, no counters are decremented. At the start of a call for which call limiting is active, the MGC saves a checksum value; and if the call limiting status changes during a call, then the checksum value is updated. When the call is to be cleared, first the call limiting functionality is checked. If the parameter is enabled, then the MGC compares the original checksum value with the current checksum value. If the values are different, the counters are not decremented.

Use the following step to enable call limiting:


Step 1 Enable the OverrideCallLimiting parameter for the whole MGC by using the following MML command.

mml> set-callim:enable 


Adding a Location Label

To add a location label, perform the following steps:


Step 1 Open a provisioning session by using the syntax in the following MML command:

mml> prov-sta::srcver="callim1",dstver="callim2" 

Step 2 Name the location labels and set the call limits by using the following MML commands:

mml> prov-add:loclabel:name="loclbl1",desc="local label 1",calllimit=25 
mml> prov-add:loclabel:name="loclbl2",desc="local label 2",calllimit=60 

Step 3 Repeat Step 2 for the remaining location labels.

Step 4 Save and activate your changes, on the active and standby MGCs in a continuous-service system, using the prov-dply MML command. Use the prov-cpy MML command to save and activate your changes on a simplex MGC (single-host) system. Both of these MML commands automatically end the provisioning session.


Dynamically Disabling Call Limiting

Once the Call Limiting feature has been enabled in XECfgparm.dat, you can dynamically disable the feature status.

To dynamically disable call limiting while the MGC is still running, use the set-callim MML command to toggle the value to 0 (disable).

When this command is entered to disable call limiting, the MGC also resets the active call counters for all labels to 0.

From a call processing point of view, once the set-callim MML command is executed, all new calls that deal with a call limiting request are trapped, and an indication that call limiting is disabled is returned. For calls already in progress when call limiting is disabled, no counters are decremented (as they are all reset to 0 in readiness for the call limiting re-start). Not decrementing counters allows existing calls with labels to clear down normally.

Perform the following step to disable call limiting:


Step 1 Disable the OverrideCallLimiting parameter for the whole MGC by using the following MML command.

mml> set-callim:disable 


Modifying Call Limiting Components

The following section contains the procedures for modifying the call limiting location label in your Cisco MGC provisioning data:

Modifying a Label Call Limit

Modifying a Label Call Limit

To add a label call limit, perform the following steps:


Step 1 Start a provisioning session.

Step 2 Enter the following command to add the location label to the location table:

mml> prov-add:loclabel:name="locationlabel01",calllimit=10 

Where:

name—MML name of the label to be added.

description—An assigned name. It can be as many as 128 alphanumeric characters in length.

For example, to modify a label named locationlabel01 by setting its call limit to 100, which was previously set to 10, enter the following MML command:

mml> prov-ed:loclabel:name="locationlabel01",calllimit=100 


Note To enable a provisioned switch to disable call limiting for a particular label, enter the following value for call limit, which effectively allows all calls just for the specified label:

mml>
prov-ed:loclabel:name="locationlabel01",call limit=99999999

A value of 99999999 for the call limit causes the associated location label to be ignored when the MGC performs validation during call processing.


Step 3 Verify the label. To do so, select either a single label by using the following MML command:

mml> prov-rtrv:loclabel:name="locationlabel01" 

or verify all labels by using the following MML command:

mml> prov-rtrv:loclabel:all 

Step 4 Repeat Step 2 and Step 3 for each location label you want to modify in your provisioning data.

Step 5 If there are no other components that you need to provision, save and activate your changes, on the active and standby MGCs in a continuous-service system, using the prov-dply MML command. Use the prov-cpy MML command to save and activate your changes on a simplex MGC (single-host) system. Both of these MML commands automatically end the provisioning session.


Retrieving Location Labels

To retrieve location labels, perform one or more of the following steps:


Step 1 Retrieve a single location label by using the syntax in the following MML command:

prov-rtrv:loclabel:name="loclbl1" 

Step 2 Repeat Step 1 for the remaining location labels you wish to retrieve. The result returned from a single label is shown in the response shown in the Provisioning Examples. This command is performed on the sigPath or trunk group level.

or

Step 3 Retrieve all location labels by using the syntax in the following MML command:

prov-rtrv:loclabel:all 

or

Step 4 Retrieve all location labels (for both sigPath and trunk group) of a specified name by using the syntax in the following MML command:

prov-rtrv:loclabel:name="loc-1","comp" 

The result returned is:

MGC-01 - Media Gateway Controller 2005-06-01 13:11:39.353 EDT
M  RTRV
   "session=test:loclabel"
   /* 
Components
----------
ss7svc1
tg-1000
tg-2000
   */


Deleting Call Limiting Components

The following section contains the procedure for deleting call limit location labels in your Cisco MGC provisioning data:


Note When location labels and their associated measurements are deleted and new labels are added, the associated measurement locations are not deleted and could hold part of the data for the previous label and part relevant to the new label. After label changes, you can expect odd measurement results until a 24-hour settling period has passed.


A location label cannot be deleted when there are calls associated with it. The prov-dlt command is rejected with the message This Label is in use by calls in the system. Ensure there is no call using this label displayed if such action is attempted.

mml> prov-dlt:loclabel:name="loclbl2"
   MGC-01 - Media Gateway Controller 2005-04-02 17:02:47.393 PST
M  DENY
   SROF
   "loclabel:loclbl2:Can not be removed. It is referenced by sigPath"
   /* Status, Requested Operation Failed on the component */
   ;
mml> prov-dlt:loclabel:name="loclbl3"
   MGC-01 - Media Gateway Controller 2005-04-02 15:26:32.274 PST
M  DENY
   SROF
   "loclabel:loclbl3:Can not be removed. It is referenced by trunkGroup"
   /* Status, Requested Operation Failed on the component */
   ;

Provisioning Examples

This section provides a provisioning example for this feature. Additional provisioning examples for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

The following MML commands were used to provision example location labels at sigPath and trunk group levels and is the first provisioning session started on the MGC:


Caution Do not name the destination directory "active" or "new." The names "active" and "new" have special meanings in the Cisco MGC software. Starting a provisioning session with a source version name of "new", is to be done only the first time provisioning is performed.

prov-stp

prov-sta::srcver="new",dstver="ver1"

prov-add:loclabel:name="loclbl1",desc="local label 1",calllimit=2345
prov-add:loclabel:name="loclbl2",desc="local label 2",calllimit=6000

prov-rtrv:loclabel:name="loclbl1"
prov-rtrv:loclabel:name="loclbl2"

prov-rtrv:loclabel:"all"

locationLabel.dat 
005f0001  2345  
005f0002  6000 


prov-add:OPC:NAME="opc",DESC="The PGW point code",NETADDR="1.1.1",NETIND=2,TYPE="TRUEOPC"
prov-add:DPC:NAME="dpc1",DESC="Orig. point code",NETADDR="2.2.2",NETIND=2
prov-add:DPC:NAME="dpc2",DESC="Dest. point code",NETADDR="3.3.3",NETIND=2
prov-add:EXTNODE:NAME="dpnss-gw1",DESC="nas 2600 Backhaul",TYPE="C2600", 
ISDNSIGTYPE="IUA",GROUP=0
prov-add:EXTNODE:NAME="eisup1",DESC="external node - eisup",TYPE="MGC", 
ISDNSIGTYPE="N/A",GROUP=0
prov-add:EXTNODE:NAME="ipfas1",DESC="external node - ipfas",TYPE="C2600", 
ISDNSIGTYPE="N/A",GROUP=0
prov-add:EXTNODE:NAME="ss7sg1",DESC="external node - ss7sg",TYPE="TALISS7", 
ISDNSIGTYPE="N/A",GROUP=0

prov-add:SS7PATH:NAME="ss7svc1",DESC="SS7 service to DPC-2-2-2",MDO="ANSISS7_STANDARD", 
CUSTGRPID="1111",SIDE="network",DPC="dpc1",OPC="opc",M3UAKEY="",ORIGLABEL="loclbl1", 
TERMLABEL="loclbl2"

prov-add:DPNSSPATH:NAME="dpnss1",DESC="backhaul to nas2600",EXTNODE="dpnss-gw1", 
MDO="DPNSS_BTNR188",CUSTGRPID="1111",SIGSLOT=2,SIGPORT=1,ORIGLABEL="loclbl1", 
TERMLABEL="loclbl2"

prov-add:EISUPPATH:NAME="eisup-mgc01",DESC="signal service - mgc",EXTNODE="eisup1", 
CUSTGRPID="1111",ORIGLABEL="loclbl1",TERMLABEL="loclbl2"

prov-add:ipfaspath:name="ipfas-sigpath",mdo="dummy",desc="IPFAS sigpath",EXTNODE="ipfas1", 
ORIGLABEL="loclbl1",TERMLABEL="loclbl2"

prov-add:SGNode:NAME="sgnode1",TYPE="TALISS7"
prov-add:SGNode:NAME="sgnode2",TYPE="TALISS7"
prov-add:SGPair:NAME="sgpair1",SGNODE="sgnode1",MATEDSGNODE="sgnode2"

prov-add:ss7sgpath:name="ss7sg-sigpath",mdo="ANSISS7_STANDARD",desc="SS7SGP sigpath", 
CUSTGRPID="1111",SIDE="network",DPC="dpc2",OPC="opc",SGPAIR="sgpair1", 
ORIGLABEL="loclbl1",TERMLABEL="loclbl2"

prov-add:sippath:name="sip-sigpath",mdo="IETF_SIP",desc="SIP sigpath",ORIGLABEL="loclbl1", 
TERMLABEL="loclbl2"

prov-rtrv:sippath:name="sip-path"
 
   MGC-2 - Media Gateway Controller 2005-07-06 16:22:32.107 EDT
M  RTRV
   "session=egw-2:sippath"
   /* 
NAME = sip-path
DESC = sip path
MDO = IETF_SIP
ORIGLABEL =
TERMLABEL =
   */
   ;

sigPath.dat 
00150001 SS7-ANSI  ANSISS7_STANDARD  1111  0101  0  network  n  2  00130002  00130001  
00000000  00000000  0 005f0001 005f0002 
00190001 EISUP  EISUP  0000  0101  0  network  n  2  00000000  00000000  00000000  
00000000  0 005f0001 005f0002 
00340001   dummy  0000  0101  0  network  n  2  00000000  00000000  00000000  00000000  0 
005f0001 005f0002 
003e0001 SIP  IETF_SIP  0000  0101  0  network  n  2  00000000  00000000  00000000  
00000000  0 005f0001 005f0002 
00420001 SS7-ANSI  ANSISS7_STANDARD  1111  0101  0  network  n  2  00130003  00130001  
00410001  00000000  0 005f0001 005f0002 
00550001 DPNSS  DPNSS_BTNR188  1111  0101  26  network  n  2  00000000  00000000  00000000  
00000000  513 005f0001 005f0002 


prov-add:trnkgrp:name="3000",svc="sip-sigpath",type="SIP_IN",ORIGLABEL="loclbl1", 
TERMLABEL="loclbl2",selSeq="LIDL"

prov-rtrv:trnkgrp:name="3000"

MGC-01 - Media Gateway Controller 2005-07-06 16:25:36.691 EDT
M  RTRV
   "session=begon-base1:trnkgrp"
   /*
NAME = 3000
CLLI = stim-dpnss1
SVC = sip-sigpath
TYPE = SIP_IN
SELSEQ = LIDL
ORIGLABEL =
TERMLABEL =
   */
   ;

trunkGroup.dat 
00200001  3000  0000  0000  003e0001  SIP_IN  LIDL  0  N  0/0/0/0  0/0/0/0  005f0001  
005f0002 


components.dat

00570001 00010001 "LI"                 "LI Radius Protocol Family"
005f0001 00010001 "loclbl1"            "local label 1" 
005f0002 00010001 "loclbl2"            "local label 2" 


Note The XECfgParm.dat parameter, engine.CallLimitingControl controls call limiting for the MGC platform. The parameter default value is 0, where 0 is false (call limiting disabled) and 1 is true (call limiting enabled). The following provisioning examples require engine.CallLimitingControl to be enabled (set to 1).


Applying Call Limiting Over DPNSS

The following provisioning example, see Figure 1, shows two gateways that are configured to be redundant with a total of 60 DS0s to PBX-2. The following sample provision shows that the service provider sets the call limiting of 10 toward PBX-2 over DPNSS from Cisco Call Managers (CCM) CCM-X and CCM-Y.

prov-add:loclabel:name="location2",calllimit=10
prov-add:DPNSSPATH:NAME="dpnss-path1",DESC="dpnss va-3745-2",EXTNODE="va-3745-2", 
MDO="DPNSS_BTNR188",CUSTGRPID="1111",SIGSLOT=1,SIGPORT=0
prov-add:trnkgrp:name="7000",type="TDM_DPNSS",svc="dpnss_path1",clli="7000',selseq="ASC", 
qable="N",origlabel="location2",termlabel="location2"

Figure 1 DPNSS Call Limiting Scenario

Applying Call Limiting to Incoming and Outgoing Trunk Groups

The following provisioning scenario, see Figure 2, is useful when multiple enterprises are sending their traffic through the same trunking media gateway. Call limiting used in this example can enforce limits so a certain enterprise cannot use too many trunking ports to the exclusion of other enterprises connected to the PSTN by the MGC.

To provision this, create a label, for example LABELCCMY with a value of 12, then in the B-number analysis, set the LOC_LABEL to the label (LABELCCMY) you just created. In the A-number analysis, select a dial plan based on the LOC_LABEL to the XX LABEL.

If the CCM has a prefix of 300XXX, the incoming calling limit for 300XXXX is 100 and the outgoing calling limit for 300XXXX is 12.

This allows you to define the incoming and outgoing trunk group call limiting separately.

//For outgoing call limit
prov-add:loclabel:name="location1",calllimit=12
numan-add:resultset:custgrpid="1111",name="set300"
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location1",setname="set300", 
custgrpid="1111",name="resultloc300"
numan-add:resulttable:custgrpid="1111",name="result300",resulttype="ROUTE",dw1="rtlist3", 
setname="set300"
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="300", 
setname="set300"   

//For incoming call limit
numan-add:Numan-add:resultset:custgrpid="1111"?name="set301"
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location1",setname="set301", 
custgrpid="1111",name="resultloc301"
numan-add:adigtree:custgrpid="1111",callside="originating",digitstring="300", 
setname="set301" 

Figure 2 Incoming and Outgoing Trunk Group Call Limiting Scenario

B-number Based Call Limiting Scenario

The following provisioning scenario, see Figure 3, is useful when limiting the number of calls based on B-numbers. If the B-number is 300XXX and call limiting for 300XXXX is 100.

prov-add:loclabel:name="location1",calllimit=100
numan-add:resultset:custgrpid="1111",name="set300"
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location1",setname="set300", 
custgrpid="1111",name="resultloc300"
numan-add:resulttable:custgrpid="1111",name="result300",resulttype="ROUTE",dw1="rtlist3", 
setname="set300"
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="300", 
setname="set300"

Figure 3 B-number Based Call Limiting Scenario

Applying Call Limiting to a SIP Trunk Group

The following provisioning example shows that call limiting of 10 is applied to the incoming and outgoing SIP trunk groups.

//location label for call limiting of 10 
prov-add:loclabel:name="location1",calllimit=10  
//provision SIP path 
prov-add:SIPPATH:NAME="sip-path",DESC="SIP path",MDO="IETF_SIP",ORIGLABEL="",TERMLABEL="" 
//provision SIP link
prov-add:SIPLNK:NAME="sip-link",DESC="SIP link",SVC="sip-path",IPADDR="IP_Addr1", 
PORT=5060,PRI=1 
//provision SIP route trunk 
prov-add:siprttrnkgrp:name="7000",url="10.0.1.2",version="2.0",cutthrough=2,srvrr=2, 
extsupport=1  
//provision outgoing call limit for SIP trunk group 
prov-add:trnkgrp:name="7000",type="IP_SIP",svc="sip-path",clli="",selseq="LIDL", 
origlabel="location1",termlabel="location1" 
//provision incoming call limit for SIP trunk group 
prov-add:trnkgrp:name="7000",type="SIP_IN",svc="sip-path",clli="",selseq="LIDL", 
origlabel="location1",termlabel="location1" 

Applying Call Limiting to an H.323 Trunk Group

The following provisioning example shows that call limiting is applied to an H.323 trunk group for both incoming and outgoing trunk groups (for example, call limit for the H.323 side is 20).

prov-add:loclabel:name="location2",calllimit=20
//provision EISUP path to HSI, PGW are connected with H.323 network by HSI 
prov-add:EISUPPATH:NAME="eisup-hsi",DESC="to orchid",EXTNODE="sh-hsi",CUSTGRPID="1111" 
//provision call limit for H.323 trunk group
prov-add:trnkgrp:name="6000",CLLI="sh-daisy",svc="eisup-hsi",type="IP",selseq="ASC", 
qable="N",origlabel="location2",termlabel="location2" 

Note Either the EISUP path or the HSI trunk group can be provisioned with location label.


Applying Call Limiting to the DPNSS Trunk Groups

The following provisioning example shows that call limiting is applied to the DPNSS trunk groups (for example, call limit for dpnss trunk group is 30) on both terminating and originating trunk groups.

prov-add:loclabel:name="location3",calllimit=30
//provision DPNSS path
prov-add:DPNSSPATH:NAME="dpnss-path2",DESC="dpnss va-3745-2",EXTNODE="va-3745-2", 
MDO="DPNSS_BTNR188",CUSTGRPID="1111",SIGSLOT=1,SIGPORT=1,ORIGLABEL="",TERMLABEL="" 
//provision call limit for DPNSS trunk group
prov-add:trnkgrp:name="5331",type="TDM_DPNSS",svc="dpnss-path1",clli="va-3745-2", 
selseq="ASC",qable="N",origlabel="location3",termlabel="location3" 

Applying Call Limiting to an SS7 ISUP Trunk Group

The following provisioning example shows that call limiting is applied to SS7 (for example, the call limit for the SS7 trunk group is 40) either incoming or outgoing, and make an announcement when the number of calls exceeds the call limit threshold.

//call limit is 10 
prov-add:loclabel:name="location1",calllimit=10 
//provision both incoming and outgoing call limit for SS7 trunk group
prov-add:trnkgrp:name="7000",type="TDM_ISUP",svc="ss7svc1",clli="7000',selseq="ASC", 
qable="N",origlabel="location1",termlabel="location1" 

//The following is to provision incoming call limiting

//provision incoming call limit for SS7 trunk group
prov-add:trnkgrp:name="7000",type="TDM_ISUP",svc="ss7svc1",clli="7000',selseq="ASC", 
qable="N",origlabel="location1",termlabel="" 

//The following is to provision outgoing call limiting 

//provision outgoing call limit for SS7 trunk group
prov-add:trnkgrp:name="7000",type="TDM_ISUP",svc="ss7svc1",clli="7000',selseq="ASC", 
qable="N",origlabel="",termlabel="location1" 

//The following is to play an announcement when calls are rejected due to exceeding 
threshold set by limiting

//announcement provisioning 
numan-add:announcement:annid=123,gwtype="AS5400",duration="60",repeat="2",interval="3", 
locationstring="xyz.aud" 
//provision local announcement
numan-add:resulttable:custgrpId="1111",name="result60",resulttype="ANNOUNCEMENT", 
dw1="123",dw2="0",dw4="1",setname="set1" 
//call limit reject internal code is "171"
numan-add:cause:custgrpid="1111",causevalue="171",setname="set1" 

Applying Call Limiting to Digit Strings in a Dial Plan

The following provisioning examples show that call limiting applied to A- and B-numbers by the dial plan and digits analysis.

1. This is the example that all incoming calls that B-numbers have prefix of 300XXX, calling limiting for 300XXXX is set to 100.

prov-add:loclabel:name="location2",calllimit=100
// provision a resultset 
numan-add:resultset:custgrpid="1111",name="set200"
//provision call limit location label in resultset 
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location2",setname="set200", 
custgrpid="1111",name="resultloc200" 
//provision route resulttable
numan-add:resulttable:custgrpid="1111",name="result200",resulttype="ROUTE",dw1="rtlist2", 
setname="set200" 
//provision Bdigtree for B-number 300XXX
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="300", 
setname="set200"

2. For example, if all incoming calls that A-numbers have prefix of 300XXX, calling limiting for 300XXXX is set to 100.

numan-add:resultset:custgrpid="1111"ÅCname="set201" 
//provision call limit location label in resultset 
numan-add:resulttable:resulttype="LOC_LABEL",dw1="location2",setname="set201", 
custgrpid="1111",name="resultloc201" 
//provision Adigtree for A-number 300XXX
numan-add:adigtree:custgrpid="1111",callside="originating",digitstring="300", 
setname="set201" 

Applying Call Limiting to Multiple Trunk Groups

The following provisioning example shows that one calling label can be applied to multiple trunks and trunk groups, which are either incoming or outgoing.

prov-add:loclabel:name="location3",calllimit=100
//location label 3 can be used as SIP incoming trunk group 7000 
prov-add:trnkgrp:name="7000",type="IP_SIP",svc="sip-path",clli="",selseq="LIDL", 
origlabel="location3" 
//location label 3 can be used as SIP outgoing trunk group 8000 
prov-add:trnkgrp:name="8000",type="IP_SIP",svc="sip-path",clli="",selseq="LIDL", 
termlabel="location3" 
//location label 3 can be used as DPNSS trunk group 9000
prov-add:trnkgrp:name="9000",type="TDM_DPNSS",svc="dpnss-path1",clli="va-3745-2", 
selseq="ASC",qable="N",origlabel="location3",termlabel="location3" 

Applying Call Limiting to IP Addresses

The following provisioning example shows that the call limiting feature can be applied to source and destination IP addresses indirectly by the dial plans.

1. Call limiting to the other peer PGW IP addresses.

Assuming a peer MGC IP address is 10.0.1.1, call limiting for EISUP is 100, call limiting can be provisioned in EISUP for the sigPath or trunk group.

Option 1: Setting call limiting with an EISUP sigPath.

prov-add:loclabel:name="location5",calllimit=100
//provision call limit in EISUP path 
prov-add:EISUPPATH:NAME="eisup-orkid",DESC="to 
orchid",EXTNODE="sh-orchid",CUSTGRPID="1111",ORIGLABEL="location5",TERMLABEL="location5" 
//provision EISUP IP link 
prov-add:IPLNK:NAME="elinkorchid1",DESC="Link to orchid",SVC="eisup-orchid", 
IPADDR="IP_Addr1",PORT=8001,PEERADDR="10.0.1.1",PEERPORT=8001,PRI=1,IPROUTE=""

Option 2: Set call limiting with an EISUP trunk group, for example, the trunk group is 6000.

prov-add:loclabel:name="location5",calllimit=100
prov-add:EISUPPATH:NAME="eisup-orkid",DESC="to orchid",EXTNODE="sh-orchid", 
CUSTGRPID="1111"
//provision EISUP IP link 
prov-add:IPLNK:NAME="elinkorchid1",DESC="Link to orchid",SVC="eisup-orchid", 
IPADDR="IP_Addr1",PORT=8001,PEERADDR="10.0.1.1",PEERPORT=8001,PRI=1,IPROUTE=""
//provision call limit in EISUP trunk group
prov-add:trnkgrp:name="6000",type="IP",svc="eisup-daisy",clli="sh-daisy",selseq="ASC", 
origlabel="location5",termlabel="location5" 

2. Call limiting for other SIP servers.

Assuming a SIP proxy IP address is 10.0.1.2, call limiting is set to 100, call limiting can be provisioned in the trunk group, for example, trunk group 7000.

prov-add:loclabel:name="location6",calllimit=100
//provision SIP path 
prov-add:SIPPATH:NAME="sip-path",DESC="SIP path",MDO="IETF_SIP",ORIGLABEL="",TERMLABEL="" 
//provision SIP link
prov-add:SIPLNK:NAME="sip-link",DESC="SIP link",SVC="sip-path",IPADDR="IP_Addr1", 
PORT=5060,PRI=1 
//provision SIP route trunk 
prov-add:siprttrnkgrp:name="7000",url="10.0.1.2",version="2.0",cutthrough=2,srvrr=2, 
extsupport=1 
//provision call limit in SIP trunk group
prov-add:trnkgrp:name="7000",type="IP_SIP",svc="sip-path",clli="",selseq="LIDL", 
origlabel="location6",termlabel="location6"

Applying Call Limiting to an MGCP Gateway

The following example shows that call limiting is applied to an MGCP gateway with IP address of 10.0.1.4, the gateway has 4 trunk groups, which are controlled by ss7svc1, and the call limiting is set to 20.

prov-add:loclabel:name="location8",calllimit=20
//provision MGCP path 
prov-add:MGCPPATH:NAME="mgcp530011",DESC="MGCP service to AS-5300-11",EXTNODE="va-5300-11" 
//provision IP link
prov-add:IPLNK:NAME="clink11-1",DESC="MGCPlink to sh-5300-11",SVC="mgcp530011", 
IPADDR="IP_Addr1",PORT=2427,PEERADDR="10.0.1.4",PEERPORT=2427,PRI=1,IPROUTE="" 
//provision call limit for SS7 sigPath
prov-add:ss7path:name="ss7svc1",desc="ss7 path",dpc="dpc1",opc="opc",mdo="Q761_BASE", 
SIDE="network",origlabel="location8",termlabel="location8" 

Playing an Announcement when the Call Limiting Threshold is Exceeded

The following example shows that an announcements can be made when calls are rejected due to exceeding the threshold set by call limiting.

//announcement provisioning 
numan-add:announcement:annid=123,gwtype="AS5400",duration="60",repeat="2",interval="3", 
locationstring="xyz.aud" 
//local announcement
numan-add:resulttable:custgrpId="1111",name="result60",resulttype="ANNOUNCEMENT", 
dw1="123",dw2="0",dw4="1",setname="set1" 
//call limit reject internal code is "171"
numan-add:cause:custgrpid="1111",causevalue="171",setname="set1" 

Dial Plans

The following sections describe the tasks related to creating dial plan data for this feature:

Dial Plan Provisioning

Dial Plan Examples

Dial Plan Provisioning

If you are not familiar with creating dial plans for the Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Provisioning Call Limiting for an A-number

The following procedure lists the steps for provisioning call limiting for an A-number.


Step 1 Enter the following MML command to add a result set:
numan-add:resultset:custgrpid="5555",name="setloc1"

Step 2 Enter the following MML command to add a result table:
numan-add:resulttable:custgrpid="5555",name="resultloc",resulttype="loc_label",dw1="location1",setname="setloc1"

Step 3 Enter the following MML command to add an A-number digit tree:
numan-add:adigtree:custgrpid="5555",callside="originating",digitstring="301",setname="setloc1"


Provisioning Call Limiting for a B-number

The following procedure lists the steps for provisioning call limiting for a B-number.


Step 1 Enter the following MML command to add a result set:
numan-add:resultset:custgrpid="5555",name="setloc2"

Step 2 Enter the following MML command to add a result table:
numan-add:resulttable:custgrpid="5555",name="resultloc2",resulttype="loc_label",dw1="location1",setname="setloc2"

Step 3 Enter the following MML command to add a B-number digit tree:
numan-add:bdigtree:custgrpid="5555",callside="originating",digitstring="306",setname="setloc2"


Provisioning the OVERRIDE_CALLIM Result Type for Number Analysis

The following procedure lists the steps for provisioning the OVERRIDE_CALLIM result type for number analysis. This included Pre-analysis (CPC, ANOA, and BNOA) and formal analysis (A-number and B-number).


Step 1 Enter the following MML command to add a result set:
numan-add:resultset:custgrpid="5555",name="setloc3"

Step 2 Enter the following MML command to add the OVERRIDE_CALLIM result type to the result set.
numan-add:resulttable:custgrpid="5555",name="resultoverride",resulttype="override_callim",setname="setloc3"

Step 3 Use one of the following MML commands to associate the OVERRIDE_CALLIM result type with:

CPC

numan-add:cpc:custgrpid="5555",cpcvalue=9,setname="setloc3"

A-number NOA

numan-add:anoa:custgrpid="5555",noavalue=4,setname="setloc3"

B-number NOA

numan-add:bnoa:custgrpid="5555",noavalue=4,setname="setloc3"

A Digit Tree

numan-add:adigtree:custgrpid="5555",callside="originating",digitstring="302",setname="setloc3"

B Digit Tree

numan-add:bdigtree:custgrpid="5555",callside="originating",digitstring="307",setname="setloc3"

Dial Plan Examples

This section provides the following MML command examples of dial plan provisioning for this feature. Additional examples of dial plan provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; provision a location label
;;;;;;;;;;;;;;;;;;;;;;;;;;;;
mml> prov-add:loclabel:name="location1",calllimit=1
mml> prov-add:loclabel:name="location2",calllimit=1

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; add resulttype="loc_label" and assign these labels to the A digit tree
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
mml> numan-add:resultset:custgrpid="5555",name="setloc"
mml> numan-add:resulttable:custgrpid="5555",name="resultloc", 
resulttype="loc_label",dw1="location1",setname="setloc"
mml> numan-add:adigtree:custgrpid="5555",callside="originating", 
digitstring="301",setname="setloc"

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; assign the location labels to dpnss sigPath
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
mml> prov-ed:dpnsspath:name="dpnss-3745-2-0",origlabel="location1",termlabel="location2"

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; assign the location labels to dpnss trunk group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
mml> prov-ed:trnkgrp:name="3702",origlabel="location1",termlabel="location2"

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; add resulttype="override_callim" and associate it with a set
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
mml> numan-add:resulttable:custgrpid="5555",name="resultloc",resulttype="override_callim", 
setname="setloc"

Troubleshooting Provisioning Data

The following section contains troubleshooting procedures related to provisioning:

Alarm Troubleshooting Procedures

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.

Alarm Troubleshooting Procedures

The alarms listed below are the new alarms for this feature that require user action to be cleared. For a complete list of Cisco MGC alarms, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.

locLabelNotFound

This alarm occurs at any point in the call when a location label cannot be found in the local table.

Corrective Action

Check provisioning for the presence of the label concerned.

locTable AccessFail

This alarm occurs at any point in the call when access to the location label table failed.

Corrective Action

To correct the problem identified by this alarm, capture traces and engine logs where possible and forward them to your Cisco support representative. If an urgent traffic handling situation occurs with constant call limiting rejections, the Call Limiting feature can be disabled to restore the call service.

Command Reference

This section documents new, modified, or deleted MML commands. All other MML commands are documented in the Cisco Media Gateway Controller Software Release 9 MML Command Reference.

New MML Commands

This section contains the MML commands that are new for this feature:

set-callim:: enable or disable—the Call Limiting feature and switches it off or on for the whole MGC.

rtrv-callim—displays the current setting for the Call Limiting feature.

prov-add/ed/dlt/rtrv:loclabel—add, edit, delete, or retrieve a location label.


SET-CALLIM—Sets the Call Limiting Function

Purpose:

This MML command sets the Call Limiting function for the whole MGC.

Syntax:

set-callim:lim_status

Input Description:

lim_status—Sets the Call Limiting function for the MGC to enabled or disabled.

enable | disable—Instructs the MGC to either enable or disable call limiting.

Output Description:

Varies

Example:

The MML command shown in the following example sets the state of this feature:

mml> set-callim:enable 

devmgc122 mml> set-callim:enable
    MGC-01 - Media Gateway Controller 2004-03-22 19:40:47.595 PST M  RTRV
    "ENGG-01"
    ;

Comments:

Performance Impact Category: A


RTRV-CALLIM—Retrieves the Call Limiting Function Status

Purpose:

This MML command retrieves the Call Limiting function status for the whole MGC.

Syntax:

rtrv-callim 

Input Description:

 

Output Description:

ENABLE | DISABLE—Instructs the MGC to either enable or disable call limiting.

Example:

The MML command shown in the following example displays the state of this feature:

devmgc122 mml> rtrv-callim:
    MGC-01 - Media Gateway Controller 2004-03-22 19:49:54.998 PST M  RTRV
    "ENGG-01:ENABLE"
    ;

Comments:

Performance Impact Category: A


PROV-ADD:LOCLABEL—Adds the Location Label

Purpose:

Adds the location labels.

Syntax:

prov-add:loclabel:name="name", desc="description", calllimit=call limit

Input Description:

name—The MML name of the location label being provisioned. The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.

desc—An assigned name. It can be as many as 128 alphanumeric characters in length.

calllimit—Maximum number of calls allowed on one location label. Integer value of 0 through 6000. The default is 0.

Output Description:

Varies

Example:

The MML command shown in the following example adds the location label named loclabl1:

mml> prov-add:loclabel:name="loclbl1",desc="local label 4", 
calllimit=4567 

devmgc122 mml> prov-add:loclabel:name="loclbl1",desc="local label 4", 
calllimit=4567 
    MGC-01 - Media Gateway Controller 2004-03-22 19:40:47.595 PST M  RTRV
    "ENGG-01"
    ;

Comments:

Performance Impact Category: A


PROV-DLT:loclabel—Deletes the Location Label

Purpose:

Deletes a location label.

Syntax:

prov-dlt:loclabel:name="name"

Input Description:

name—The MML name of the location label being provisioned. The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.

Output Description:

Varies

Example:

The MML command shown in the following example adds the location label named loclabl1:

mml> prov-dlt:loclabel:name="loclbl1"

MGC-01 - Media Gateway Controller 2004-03-22 19:40:47.595 PST M  RTRV
    "ENGG-01"
    ;

Comments:

Performance Impact Category: A


PROV-ED:loclabel—Edits the Location Label

Purpose:

Modifies the location labels.

Syntax:

prov-ed:loclabel:name="name", desc="description", calllimit=call limit 

Input Description:

name—The MML name of the location label being provisioned. The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter. The name cannot be modified.

desc—An assigned name. It can be as many as 128 alphanumeric characters in length.

calllimit—Maximum number of calls allowed on one location label. Integer value of 0 through 6000. The default is 0.

Output Description:

Varies

Example:

The MML command shown in the following example modifies the location label named loclabl1:

mml> prov-ed:loclabel:name="loclbl1",desc="local label 4", 
calllimit=4567 
 
MGC-01 - Media Gateway Controller 2004-03-22 19:40:47.595 PST M  RTRV
    "ENGG-01"
    ;

Comments:

Performance Impact Category: A


PROV-RTRV:loclabel—Retrieves the Location Label

Purpose:

Retrieves the location labels.

Syntax:

prov-rtrv:loclabel:name="name", desc="description", calllimit=call limit 

Input Description:

name—The MML name of the location label being provisioned. The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.

desc—An assigned name. It can be as many as 128 alphanumeric characters in length.

calllimit—Maximum number of calls allowed on one location label. Integer value of 0 through 6000. The default is 0.

Output Description:

Varies

Example:

The MML command shown in the following example displays the location label named loclabl1:

mml> prov-rtrv:loclabel:name="loclbl1",desc="local label 4", 
calllimit=4567 
 
MGC-01 - Media Gateway Controller 2004-03-22 19:40:47.595 PST M  RTRV
    "ENGG-01"
    ;

Comments:

Performance Impact Category: A


Stopping a Call

The MML stp-call command terminates calls by sending a special signal that causes a proper release sequence to be initiated for each active call leg. Therefore, normal call records are written and the normal connection-deletion processing is conducted with the gateways. This is sometimes referred to a graceful release.

For a graceful release, call instances receive the internal signal that provokes call clearing. As each call side clears normally, the call counters associated with that side are released.

Killing a Call

The kill-call command is not commonly used, but is used to deal with serious or emergency situations (usually as directed by Cisco personnel). If this command is issued, then the MGC when handling the command checks its internal data for the presence of location labels. If any location labels are present, the active call counter for each label is decremented by 1 as the call is deleted.


Note Whether using the stp-call command or kill-call command, if the active call terminated has a location label, the location label counter is also decremented.


Reference Information

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

XECfgParm.dat Parameters

Alarms

Internal Cause Codes

Logs

Measurements

Billing Interface

Components

Result Types

Provisioning Worksheets

Monitoring and Maintaining the Feature

Obtaining Documentation and Submitting a Service Request

XECfgParm.dat Parameters

The XECfgParm.dat file configuration parameters added for this feature are in the table below. For information on the other XECfgParm.dat parameters, refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide.

Configuration Parameter
Definition

engine.CallLimitingControl

Allows enabling or disabling the call limiting capability on the MGC.

Valid values: 0 = call limiting off (default) or 1 = call limiting on

*.maxLocationLabels

Specifies the maximum number of location labels that can be provisioned.

Valid value: 3000

Note Do not change this value.

 


Alarms

This section lists the alarms that are added and modified to support this feature. For information on the other alarms for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.

New Alarms

The alarms that are added for this feature are listed below.

locTableAcessFail

This alarm is raised at any point in the call if the engine cannot access the local location label table to make a call limiting request or to decrement counters. It is a sign of possible counter corruption, and the system user needs to be made aware of the situation. Logs are also raised to indicate the labels involved.

· Description The MGC failed to access the location label table.

Severity Informational

Cause This alarm is reported when the MGC is trying to access its internal location label table to make a call limiting check or to update active call counters. If it indicates a failure in executing the counter decrement for one or more labels, associated logs identify the labels involved. Failure to carry out this counter decrement could later lead to false rejection of calls and possible traffic handling problems.

Type 1 (Communication alarm)

Action This typically points to an internal processing error. Capture traces and engine logs where possible, and forward them to your Cisco support representative. If an urgent traffic handling situation occurs, with constant call limiting rejections, the Call Limiting feature can be disabled so service can be restored.

locLabelNotFound

This alarm is raised at any point in the call if the a collected location label is missing from the internal location label table. This could point to a label being removed while still being assigned in analysis or at the trunk group or SigPath level. Logs are also raised to indicate the labels involved.

·· Description The location label was not found in the internal table.

Severity Informational

Cause This alarm can occur when the MGC reads its internal label to check or update counters for a label. If the label is not found, this alarm is generated.

Type 1 (Communication alarm)

Action This typically points to a provisioning error where a label has been removed, but references to it are not removed from Analysis, the trunk group, or SigPath. Check provisioning for the presence of the label concerned.

Internal Cause Codes

An internal cause code, listed in Table 1, was added to support the Call Limiting feature.

Table 1 Internal Cause Code Values 

Internal Cause Code
Value
Internal Cause Code
Value

IC_CALL_LIMIT_REJ

171

   

Logs

This section lists the logs that are added or deleted to support this feature. For information on the other logs, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.

New Logs

This section contains the logs that are added to support the Call Limiting feature.

locTableAccessFail:

Failed to access the location label table

locLabelNotFound:

A-number label xxxx (label component id) is not found

or

B-number label xxxx (label component id) is not found

or

origSide label xxxx (label component id) is not found

or

termSide label xxxx (label component id) is not found


Measurements

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

Table 2 New Operational Measurements

MML Counter Group:Name
Description
Related Components
Logging Interval

LABEL GROUP

LABEL:LabelRej TOT

LABEL:LabelSucc TOT

Label message statistics

The number of calls (that is, occurrences) rejected against this call limiting location label

The number of successful calls (that is, occurrences) against this call limiting location label

Label

15, 60, 24

15, 60, 24


The Measurement manager must collect at regular periods (15 minutes, 60 minutes, or 24 hours) the "Successful" and "Rejected" measurement counters for every location label (componentId) defined on the system. The engine updates and stores this data in the location common to other measurement data.


Note When location labels and their associated measurements are deleted and new labels are added, the associated measurement locations are not deleted and could hold part of the data for the previous label and part relevant to the new label. After a label changes, you can expect odd measurement results until a 24-hour settling period has passed.


For each location label defined on the Cisco MGC, two measurement counters must be created. One measurement counter is for successful calls per label, and the other measurement counter is for rejected calls per label.

For the label measurements to be accurate, the successful calls counter increments only when the call has reached the Answered state.

If a call is rejected due to call limiting, the rejected calls counter is incremented.

Should failover occur, when the standby side is brought up, the measurement counters are not replicated and hence start cleanly from 0.

Billing Interface

This section identifies the call detail record (CDR) data added for this feature. For billing interface information for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide.

Rejecting Location Label (Tag: 4232)

Table 3 Rejecting Location Label Description Form 

Name: Rejecting Location Label

Tag: 4232

Source: MDL

Description/Purpose: Name of the Call-limiting location label which caused the call rejection.

Format: IA5 (string)

Length in Octets: 1-20

Data Value:

String

Example: londonVpnUser652

ANSI/ITU Variations: None.

Extended Data Value: No extended value.

General Information: For calls with location labels defined, a call limiting check must be made once the terminating side is set up. This involves reading internal tables to get call limit data and active call counter data. If the call limit threshold is reached, then the call is rejected against that location label. This record provides the identity of the location label that failed the call.

This tag is only added to the CDB if the call limiting check results in rejection.

MGC Release: Release 9.6 and later.

 

Answered (1010)

Deselected (1020)

Aborted (1030)

Release (1040)

Interrupted (1050)

Ongoing (1060)

Maintenance (1070)

External DB (1080)

End of Call (1110)

N

Y

Y

N

N

N

N

N

Y


Rejecting Location Label Direction (Tag: 4233)

Table 4 Rejecting Location Label Direction Form 

Name: Rejecting Location Label Direction

Tag: 4233

Source: MDL

Description/Purpose: Indication of whether or not the call was rejected by a location label relating to the MGC originating (incoming) or terminating (outgoing) side.

Format: BE

Length in Octets: 1

Data Value:

1 = Inbound (MGC originating side)

2 = Outbound (MGC terminating side)

ANSI/ITU Variations: None.

Extended Data Value: No extended value.

General Information: For calls with location labels defined, a call admission check must be made once the terminating side is set up. This involves reading internal tables to get call limit data and active call counter data. If the call limit threshold is reached, then the call is rejected against that location label. This record provides an indication of whether or not this call rejection was assigned to the MGC originating (inbound) or MGC terminating (outbound) side.

This tag is added to the CDB only if the call admission check results in rejection.

MGC Release: Release 9.6 and later.

 

Answered (1010)

Deselected (1020)

Aborted (1030)

Release (1040)

Interrupted (1050)

Ongoing (1060)

Maintenance (1070)

External DB (1080)

End of Call (1110)

N

Y

Y

N

N

N

N

N

Y


Components

The sections below discuss the provisioning components that are added, modified, and deleted 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.

New Components

The following LABEL provisioning component is added for this feature.

LABEL

The LABEL component represents the number of calls allowed on a location. Its MML name is as follows:

MML name—LABEL

The LABEL component structure is shown in Table 5.

Table 5 LABEL Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

NAME

Unique component name used in MML commands

The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.

DESC

Component description

The description can be up to 128 characters.

CALL LIMIT

Maximum number of calls allowed on one location label

0 through 6000, integer value

0 (default)



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


Modified Components

The following components are modified for this feature by adding the ORIG LABEL and TERM LABEL parameter to each component. The component tables list only the parameters changed to support the Call Limiting feature.

DPNSSPATH

EISUP Signaling Service (sigPath)

IPFAS Transport Service (previously PRI Signaling Backhaul)

Multiple IPFAS Services (sigPath)

SIP Signaling Service

SS7 SG Signaling Service

SS7 Signaling Service (sigPath)

Trunk Group Provisioning

DPNSSPATH

The DPNSS signaling service component type represents a DPNSS signaling path that is backhauled over IP to or from a network access server (destination). Its MML name is as follows:

MML name—DPNSSPATH

The DPNSS signaling service component structure is shown in Table 6.

Table 6 DPNSS Signaling Service Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


EISUP Signaling Service (sigPath)

The EISUP Signaling Service (sigPath) component is a network element that represents an EISUP signaling service or signaling path to another NE (destination). Its MML name is as follows:

MML name—EISUPPATH

The signaling service path component structure is shown in Table 7.

Table 7 EISUPPATH Signaling Service Path Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


IPFAS Transport Service (previously PRI Signaling Backhaul)

The IPFAS transport service component type represents the FAS over IP transport service or signaling path from a media gateway to an MGC. Its MML name is as follows:

MML name—IPFASPath

The IPFAS transport service component structure is shown in Table 8.

Table 8 IPFAS Transport Service Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


Multiple IPFAS Services (sigPath)

The multiple IPFAS signaling service component type is used to create multiple IPFAS or IPNFAS signaling paths and D-channels to a particular destination using either ISDN-PRI or DPNSS. Its MML name is as follows:

MML name—MLTIPFAS

The multiple IPFAS Signaling Service component structure is shown in Table 9.

Table 9 MLTIPFAS Signaling Service Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


SIP Signaling Service

This component type represents the SIP signaling service or signaling path to SIP proxy servers. Its MML name is as follows:

MML name—SIPPATH

The SIP signaling service component structure is shown in Table 10.

Table 10 SIP Path Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


SS7 SG Signaling Service

This is the MGC NE component type and represents an SS7 signaling gateway signaling service. Its MML name is as follows:

MML name—SS7SGPATH

The SS7 SG signaling service component structure is shown in Table 11.

Table 11 SS7 SG Signaling Service Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


SS7 Signaling Service (sigPath)

The SS7 Signaling Service (sigPath) component type represents an SS7 signaling service or signaling path to a particular SS7 switch (destination). Its name is as follows:

MML name—SS7PATH

The SS7 signaling service component structure is shown in Table 12.

Table 12 SS7 Signaling Service Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


Trunk Group Provisioning

The trunk group provisioning component type represents a trunk group. This component is supported by MML only. Its MML name is as follows:

MML name—TRNKGRP

The trunk group provisioning interface component structure is shown in Table 13.

Table 13 Trunk Group Provisioning Component Structure 

Parameter MML Name
Parameter Description
Parameter Values (Default)

ORIG LABEL

Originating call control (OCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).

TERM LABEL

Terminating call control (TCC) side location label. Used for Call Limiting feature.

As many as 20-character alphanumeric string. This parameter is added in software Release 9.6(1).


Result Types

The result type definitions shown in Table 14 are added for this feature. For information on other result type definitions for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Table 14 Added Result Types 

Result Number.
Result Type
Dataword1
Dataword2
Dataword3
Dataword4
Analysis Points
Result Type Valid For
Intermediate
End Point
A-digit analysis
B-digit analysis
Cause
Pre-analysis

66

LOC_LABEL

Location Label

0 (not used)

0 (not used)

0 (not used)

X

 

X

X

 

 

67

OVERRIDE_CALLIM

0 (not used)

0 (not used)

0 (not used)

0 (not used)

X

 

X

X

 

X


Result Type Definitions

The following paragraphs contain definitions of the result types listed in Table 14.

LOC_LABEL

The LOC_LABEL result type is returned from A-number analysis (the calling number) or B-number analysis (the called number) and indicates the location label.

Dataword1 is the location label name, and may be as many as 20 alphanumeric characters.

OVERRIDE_CALLIM

The OVERRIDE_CALLIM result type indicates the location label call overrides the call limiting value. Presence of the OVERRIDE_CALLIM result type indicates that for this call, any call limiting actions are ignored allowing it to set up as soon as possible.

The OVERRIDE_CALLIM result type is available to Pre-analysis, A-number analysis, and B-number analysis. Since OVERRIDE_CALLIM is available to these analysis areas, the override indicator can be set for tho following:

Calling Party Category (CPC) - Pre-analysis

Calling party number Nature of Address (NOA) - Pre-analysis

Called party number Nature of Address (NOA) - Pre-analysis

Calling party number address digits - A-number analysis

Called party number address digits - B-number analysis

The OVERRIDE_CALLIM result type is for use when an emergency call or other high-priority call, allowing that call type to switch with a minimum of processing and without any obstacles, such as call limiting. So, even if LOC_LABEL results are collected, the presence of the OVERRIDE_CALLIM result type means that no call limiting actions are applied for this call.

Provisioning Worksheets

This section contains worksheets for the provisioning components required for this feature. For worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

Table 15 Label Worksheet 

Name
Description
Call Limit

loclbl1

locationlabel01

10

loclbl1

locationlabel02

50

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Table 16 DPNSSPATH Worksheet Example  

Name
Desc
MDO
ExtNode
CustGrpId
ABFlag
SigSlot
SigPort
Orig
Label
Term Label

dpnssvc1

AS3660

DPNSS_BTNR188

AS3660

0002

a

10

45

loclbl1

loclbl2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Table 17 SS7PATH Worksheet Example  

Name
Desc
MDO
Side
CustGrpId
DPC
OPC
M3UA-KEY
Orig
Label
Term Label

sigsvc1

AS3660

Q761_BASE

network

0002

dpc
mgw1

pgw1

m3ua
key1

loclbl1

loclbl2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Table 18 SS7SGPATH Worksheet Example  

Name
Desc
MDO
Side
CustGrpId
DPC
OPC
M3UA-KEY
Orig
Label
Term Label

sigsvc1

SS7 svc to dpc1

Q761_BASE

network

0002

dpc
mgw1

pgw1

m3ua
key1

loclbl1

loclbl2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Table 19 SCTP Association Worksheet Example 

Parameter
Parameter Value

Name

nasassoc1

 

 

 

 

 

Description

DPNSS IUA association 1

 

 

 

 

 

Signaling Type

IUA

 

 

 

 

 

SGP name

 

 

 

 

 

 

First local address

IP_Addr1

 

 

 

 

 

Second local address (optional)

IP_Addr2

 

 

 

 

 

Local SCTP port number (optional)

 

 

 

 

 

 

Highest priority destination address

10.82.80.30

 

 

 

 

 

Lowest priority destination address (optional)

10.82.81.30

 

 

 

 

 

Destination SCTP port number (optional)

 

 

 

 

 

 

External node name

va-3600-37

 

 

 

 

 

First IP route name (optional)

iprte1

 

 

 

 

 

Second IP route name (optional)

iprte2

 

 

 

 

 

Number of bytes to advertise for the local receive window. (optional)

 

 

 

 

 

 

Maximum number of times to retransmit SCTP INIT message (optional)

 

 

 

 

 

 

Maximum initial timer retransmission value (optional)

 

 

 

 

 

 

Maximum number of retransmissions over all destination address before the association is declared failed (optional)

 

 

 

 

 

 

Maximum time after a datagram is received before a SCPT SACK is sent (optional)

 

 

 

 

 

 

Maximum time SCTP will wait for other outgoing datagrams for bundling (optional)

 

 

 

 

 

 

Minimum value allowed for the retransmission timer (optional)

 

 

 

 

 

 

Maximum value allowed for the retransmission timer (optional)

 

 

 

 

 

 

Time between heartbeats (optional).

 

 

 

 

 

 

IP Precedence (optional)

 

 

 

 

 

 

Differential Service Code Point (optional)

 

 

 

 

 

 

Maximum number of retransmissions to either peer address 1 or 2 before it is declared failed (optional)

 

 

 

 

 

 


Monitoring and Maintaining the Feature

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

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation at

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Glossary

Table 20 contains definitions of acronyms and technical terms used in this feature module.

Table 20 Acronyms and Definitions 

Acronym
Definition

CCM

Cisco Call Manager

CDB

Call Detail Block

CPC

Calling Party Category

CS1

Capability Set 1

DPNSS

Digital Private Network Signaling System No. 1(DPNSS) is a set of proprietary standards (defined in BT Standard BTNR 188)

E-ISUP

Enhanced-ISUP (Cisco proprietary)

ETC

Establish Temporary Connection

H.323

ITU-T recommendation for packet based video, audio, and conferencing. It refers to H.245, H.225, and Q.931 to describe its protocol

INAP

Intelligent Network Application Protocol

ISDN

Integrated Services Digital Network

ISUP

ISDN User Part

MDL

Message Definition Language

MGC

Cisco Media Gateway Controller

MML

Man-Machine Language

NANP

North American Numbering Plan

NOA

Nature of Address

NE

Network Element

NPI

Number Plan Indicator

OCC

Originating call control

PGW

PSTN Gateway

PRI

Primary Rate Interface. An interface to an integrated service digital network (ISDN) that includes 23 ISDN 64 kbps B channels for information and 1 ISDN D channel for signaling

PSTN

Public Switched Telephone Network

QSIG

Common channel signaling protocol based on ISDN.93 standards and used by many digital PBXs., also known as Private Signaling System Number 1 (PSS1). (spec ETSI_300_172)

SCCP

Signaling Connection Control Part

SCP

Service Control Point

TCAP

Transaction Capabilities Application Part

TCC

Terminating call control

TMR

Transmission Medium Requirement

TNS

Transit Network Selection

UCM

Universal Call Model

VoIP

Voice over Internet Protocol

VSC

Virtual Switch Controller