Cisco PGW 2200 Softswitch Release 9 MML Command Reference
Chapter 4 - PROV: Commands for Provisioning Signaling and Trunking Components
Downloads: This chapterpdf (PDF - 863.0KB) The complete bookPDF (PDF - 2.86MB) | Feedback

Table of Contents

PROV: Commands for Provisioning Signaling and Trunking Components

Command Syntax for Provisioning Signaling and Trunking Components

ACCRESPCAT—Automatic Congestion Control (ACC) Response Categories

APC—Adjacent Point Code

ASSOCIATION—SCTP Association

ATMPROFILES—ATM Profiles

AXLSERVER—AXL Server

BEARERCAP—Bearer Capability

BRIPATH—BRI Signaling Service

C7IPLNK—C7 IP Link

CHARGE—Charge Table

CODECSTRING—Codec Selection

CONDRTE—Conditional Routing Table

CONDRTEDESC—Conditional Routing Table Description

CTIMGR—CTI Manager

CTIPATH—CTI Path

DCHAN—D-Channel

DNSPARAM—Domain Name System Parameters

DOMAINPROF—Domain Profile (Release 9.8(1))

DPC—Destination Point Code

DPNSSPATH—DPNSS Signaling Service

EISUPPATH—EISUP Sigpath

EXTNODE—External Node

EXTNODETYPES—External Nodes

FILES—File Importing or Exporting

GTDPARAM—Generic Transparency Descriptor (GTD) Parameters

GWPOOL—Gateway Pool (Release 9.8(1))

H248PATH—H.248 Signaling Protocol Service

HOLIDAY—Charge Holiday

INSERVICE —Intelligent Network Service

INSIPHEADER—Inbound SIP Header (Release 9.8(1))

IPFASPATH—IPFAS Transport Service

IPGW—IP Gateway (Release 9.8(1))

IPINMAPPING—IP In Trunk Mapping

IPLNK—IP Link

IPROUTE—Static IP Route

LINEXLATE—Line Translation

LIPATH—Lawful Intercept Signaling Service

LNKSET—Link Set

LNKSETPROP—Linkset Properties

LOCLABEL—Location Label

M3UAKEY —M3UA Routing Key

M3UAROUTE —M3UA Route

MCLCALLREJECT—Machine Congestion Level Percentage

MCLTHRESHOLD—Machine Congestion Level Thresholds

METERTARIFF—Meter Tariff

MGCPPATH—MGCP Signaling Service

MLTIPFAS—Multiple IPFAS Signaling Services

MLTTRNKGRP—Multiple Trunk Groups

NAILEDTRNK—Nailed Trunks

NASPATH—Signaling Path Between the Cisco PGW 2200 Softswitch and a NAS

OPC—Originating Point Code

OUTSIPHEADER—Outbound SIP Header (Release 9.8(1))

PERCRTE—Percentage-Based Routing Table

PRICHARGE—PRI Charge Table

PRITARIFF—PRI Tariff Table

PROFILE—Profile (Release 9.8(1))

RAPATH—RADIUS Accounting Server Signal Path (Release 9.7(3))

RASERVER—RADIUS Accounting Server (Release 9.7(3))

RTLIST—Route Lists

RTTRNK—Route Trunk

RTTRNKGRP—Route Trunk Group

SESSIONPROP—SS7 Session Property

SESSIONSET—Sessionset

SGP—SS7 Signaling Gateway Process

SIGPATHPROF—Signaling Service Profile

SIGSVCPROP—Signaling Service Properties

SIPIVERSION—SIP-I Version and MDO Variant (Release 9.8(1))

SIPLNK—SIP IP Link

SIPPATH—SIP Signaling Service

SIPRTTRNKGRP—SIP Routing Trunk

SS7PATH—SS7/M3UA Signaling Service

SS7ROUTE —SS7 Route

SS7SUBSYS —SS7 Subsystem

SUAKEY—SUA Routing Key

SUAROUTE—SUA Route

SWITCHTRNK—Multiple Switched Trunks

TARIFF—Tariff

TCPLNK—TCP Link

TOS—TOS Value (Release 9.7(3))

TRNKGRP—Trunk Group

TRNKGRPPROF—Trunk Group Profile

TRNKGRPPROP—Trunk Group Properties

PROV: Commands for Provisioning Signaling and Trunking Components

Revised: Aug 30, 2011, OL-1116-24

This chapter describes the Machine-Man Language (MML) commands for provisioning components on the Cisco PGW 2200 Softswitch Release 9. After the introductory section, the commands for each component are grouped together, and the information is displayed in alphabetical order by component.


Tip The prov-add command adds (creates) an instance of a component.
The prov-dlt command deletes (removes) an instance of a component.
The prov-ed command edits (modifies) an instance of a component.
The prov-rtrv command retrieves (displays) information about one or more instances of a component.


The first section provides general information about the MML command syntax. The remaining sections are in alphabetical order by component.

Command Syntax for Provisioning Signaling and Trunking Components

This section shows the general syntax for component provisioning commands.

 

Purpose:

Provisions a component to the Cisco PGW 2200 Softswitch configuration.

Syntax:

prov-add:<comp>:name =”< MML name >”,< param name >=< param value >,...
prov-dlt:<comp>:name =”< MML name >”,...
prov-ed:<comp>:name =”< MML name >”,< param name >=< param value >,...
prov-rtrv:<comp>:name =”< MML name >”,< param name >=< param value >,...
prov-rtrv:<comp>:name =”< MML name >”|” all ”,...
prov-rtrv: all

Input Description:

  • comp —MML component name for the type of configuration you are creating. The component type must match one of the component types listed in Cisco PGW 2200 Softswitch Release 9 Provisioning Guide . For software Release 7.4(8) and later, <comp> can be EXTNODE. If <comp> is EXTNODE, then the <param name> TYPE must be present and needs to take a set of values (see the second example below).
  • name —MML component name for the new object you are creating (as many as ten characters).
  • param name —The name of a valid configuration parameter for the specified component type. Parameter names are listed in Cisco PGW 2200 Softswitch Release 9 Provisioning Guide .
  • param value —The value you want to assign to the parameter. If the parameter value is a string, it should be surrounded by quotation marks.

To define more than one parameter, enter additional param name=param value descriptions on the command line.

Examples:

The MML command shown in the following example adds the origination point code for the Cisco PGW 2200 Softswitch configuration:

mml> PROV-ADD:opc:NAME="opc",DESC="Point code of CP1",netaddr="0.0.1", netind=2,type=”TRUEOPC”
Media Gateway Controller - MGC-01 2000-01-12 15:19:51
M COMPLD
"opc"
;
 

The MML command shown in the following example adds an external node to the Cisco PGW 2200 Softswitch configuration:

mml> PROV-ADD:EXTNODE:NAME="TOTO2",DESC="TATA",TYPE="MGX8260"
Media Gateway Controller - MGC-02 2000-05-08 18:05:55
M COMPLD
"extnode"
;

Comments:

Performance Impact Category: B

See Cisco PGW 2200 Softswitch Release 9 Provisioning Guide for a description of using the PROV commands for provisioning and for information about components, parameter names, parameter descriptions, and parameter values.

ACCRESPCAT—Automatic Congestion Control (ACC) Response Categories

 

Purpose:

Provision an ACC response category.

Syntax:

prov-add:accrespcat:name =" cat_name "[, field_name = value , field_name = value ...]
prov-dlt:accrespcat:name =" cat_name "
prov-ed:accrespcat:name =" cat_name "[, field_name = value , field_name = value ...]
prov-rtrv:accrespcat:name =" cat_name "
prov-rtrv:accrespcat: " all "

Input Description:

  • cat_name —MML name for the ACCRC.
  • field_name —ACCRC field that is used to specify a percentage of calls that are released when a congestion indication of a particular ACL level is received from an adjacent signaling point. The following fields can be configured:

acl1drcant—Specifies the percentage of calls defined in value that are released when an ACL indication of 1 is received from an adjacent signaling point and this trunk group is configured as a direct route from that signaling point.

acl1drskip—Specifies the percentage of calls defined in value that are re-routed to an alternate trunk group when an ACL indication of 1 is received from an adjacent signaling point.

acl1arcant—Specifies the percentage of calls defined in value that are released when an ACL indication of 1 is received from an adjacent signaling point and this trunk group is configured as an alternate route from that signaling point.

acl1arskip—Specifies the percentage of calls defined in value that are re-routed to an alternate trunk group when an ACL indication of 1 is received from an adjacent signaling point.

acl2drcant—Specifies the percentage of calls defined in value that are released when an ACL indication of 2 is received from an adjacent signaling point and this trunk group is configured as a direct route from that signaling point.

acl2drskip—Specifies the percentage of calls defined in value that are re-routed to an alternate trunk group when an ACL indication of 2 is received from an adjacent signaling point.

acl2arcant—Specifies the percentage of calls defined in value that are released when an ACL indication of 2 is received from an adjacent signaling point and this trunk group is configured as an alternate route from that signaling point.

acl2arskip—Specifies the percentage of calls defined in value that are re-routed to an alternate trunk group when an ACL indication of 2 is received from an adjacent signaling point.

acl3drcant—Specifies the percentage of calls defined in value that are released when an ACL indication of 3 is received from an adjacent signaling point and this trunk group is configured as a direct route from that signaling point.

acl3drskip—Specifies the percentage of calls defined in value that are re-routed to an alternate trunk group when an ACL indication of 3 is received from an adjacent signaling point.

acl3arcant—Specifies the percentage of calls defined in value that are released when an ACL indication of 3 is received from an adjacent signaling point and this trunk group is configured as an alternate route from that signaling point.

acl3arskip—Specifies the percentage of calls defined in value that are re-routed to an alternate trunk group when an ACL indication of 3 is received from an adjacent signaling point.

  • value —Percentage of calls that are released. The valid range is 0 through 100.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example adds an ACC response category:

mml> prov-add:accrespact:name="cat1",acl1drcant=20,acl1drskip=20,acl1arcant=10,acl1arskip=10
 
MGC-01 - Media Gateway Controller 2009-11-25 10:47:38.222 EST
M COMPLD
"accrespcat"
;

APC—Adjacent Point Code

 

Purpose :

Add, delete, or edit an APC.

Syntax:

prov-add:apc:name=" name ", desc=" description ", netaddr=” addr”, netind=num
prov-dlt:apc:name=" name "
prov-ed:apc:name=" name ", desc=" description ", netaddr=” addr”, netind=num

Input Description:

  • name—Enter a name for the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
  • desc—Enter a long name up to 128 alphanumeric characters in length.
  • netaddr—Enter the network address in dot notation.
  • netind —Enter the network indicator number. The default value is 0.

Example :

To add an APC named apc1, enter the following command:

mml> prov-add:apc:NAME="apc1",DESC="apc1",NETADDR="1.2.4",NETIND=2
 

To delete an APC named apc1 , enter the following command:

mml> prov-dlt:apc:NAME="apc1"
 

To edit an APC named apc1 , enter the following command:

mml> prov-ed:apc:NAME="apc1",DESC="apc1",NETADDR="1.2.5",NETIND=3

ASSOCIATION—SCTP Association

Purpose :

Configures an SCTP association between the Cisco PGW 2200 Softswitch and an external node.

Syntax:

prov-add:association:name =” association name ”, desc= description ”, type= signaling type ”, sgp= process ”, ipaddr1= ip address ”, <ipaddr2= ip address ”, >port= value ,peeraddr1= ip address ”, <peeraddr2= ip address >,<peerport= value >,extnode= external node ”, <iproute1= ip route >, <iproute2= ip route >,<rcvwin= value >,<maxinitretrans= value >,<maxinitrto= value >, <maxretrans= value >,<cumsackto= timeout value >,<bundleto= timeout value >, <minrto= timeout value >,<maxrto= timeout value >,<hbto= value >,ipprecedence= precedence ,dscp= code point , <maxretransdest= value >

Input Description:

  • Name—Name of the association. Enter an alphanumeric string up to 20 characters in length.
  • Desc—Description of the association. This parameter can be up to 128 characters in length.
  • Type—Association type. Enter one of the following:

IUA

M3UA

SUA

H248 (The option “H248” is introduced in software Release 9.7(3). Configures the H.248 transport protocol as SCTP. The type in “association.dat” can be used to indicate H.248.)

  • SGP—MML name of a previously configured Signaling Gateway Process. (Enter “N/A” for H.248 SCTP connection.)
  • Port—Local Stream Control Transmission Protocol (SCTP) port. Enter an integer in the range 1025 to 65535. The default varies based on the protocol type selected.

The default is 9900 for IUA.

The default is 2905 for M3UA.

The default is 14001 for SUA.

This is an optional parameter.

  • Peeraddr1—Highest priority destination address, expressed in dot notation.
  • Peeraddr2—(Optional) Lowest priority destination address, expressed in dot notation. The default value for this parameter is 0.0.0.0.
  • Ipaddr1—First local address represented by one of the following property names defined in the XECfgParm.dat file:

IP_Addr1

IP_Addr2

IP_Addr3

IP_Addr4

  • Ipaddr2—(Optional) Second local address represented by one of the following property names defined in the XECfgParm.dat file:

IP_Addr1

IP_Addr2

IP_Addr3

IP_Addr4

  • Peerport—(Optional) Destination (peer) SCTP port:

Enter a number. Range is 1025 to 65535.

The default is 9900 for IUA.

The default is 2905 for M3UA.

The default is 14001 for SUA.

 

  • Extnode—MML name of a previously configured external node.
  • Iproute1—(Optional) MML name of a previously configured IP route.
  • Iproute2—(Optional) MML name of a previously configured IP route.
  • Rcvwin—(Optional) Number of bytes to advertise for the local receive window.

Enter a number in the range 1500 to 65535.

The default is 18000.

  • Maxinitretrans—(Optional) Maximum number of times to retransmit SCTP INIT message.

Enter a number in the range 0 to 100.

An entry of 0 chooses the SCTP internal default.

The default is 10.

  • Maxinitrto—(Optional) Maximum initial timer retransmission value.

Enter a number in the range 300 to 3000.

An entry of 0 chooses the SCTP internal default.

The default is 2000.

  • Maxretrans—(Optional) Maximum number of retransmissions over all destination addresses before the association is declared to have failed.

Enter a number in the range 1 to 10

This value must not exceed MAXRETRANSDEST * the number of destinations.

The default is 5.

  • Cumsackto—(Optional) Maximum time after a datagram is received before a SCPT SACK is sent, in milliseconds.

Enter a number in the range 100 to 500.

The default is 300.

  • Bundleto—(Optional) Maximum time SCTP waits for other outgoing datagrams for bundling, in milliseconds.

Enter a number in the range 100 to 600.

The default is 100.

  • Minrto—(Optional) Minimum value for the retransmission timer, in milliseconds.

Enter a number in the range 300 to 3000.

The default is 300.

 

  • Maxrto—(Optional) Maximum value for the retransmission timer, in milliseconds.

Enter a number in the range 1000 to 10,000.

The default is 3000.

  • Hbto—(Optional) Time between heartbeats, in milliseconds. The heartbeat is this value plus the current retransmission timeout value.

Enter a number in the range 300 to 10,000.

Enter 0 to disable this parameter.

The default is 2000.

  • Ipprecedence—Internet Protocol Precedence. Enter one of the following:

ROUTINE (default)

PRIORITY

IMMEDIATE

FLASH

FLASH-OVERRIDE

CRITICAL

INTERNET

NETWORK

  • DSCP—(Optional) Time between heartbeats, in milliseconds. The heartbeat is this value plus the current retransmission timeout value. Valid values are in the range from 300 to 10000, or 0. A value of 0 means that the heartbeat is disabled. The default value is 2000.

EF 101110—Expedited Forwarding

AF11 001010—Assured Forwarding Class 1 Low Drop Precedence

AF12 001100—Assured Forwarding Class 1 Medium Drop Precedence

AF13 001110—Assured Forwarding Class 1 High Drop Precedence

AF21 010010—Assured Forwarding Class 2 Low Drop Precedence

AF22 010100—Assured Forwarding Class 2 Medium Drop Precedence

AF23 010110—Assured Forwarding Class 2 High Drop Precedence

AF31 011010—Assured Forwarding Class 3 Low Drop Precedence

AF32 011100—Assured Forwarding Class 3 Medium Drop Precedence

AF33 011110—Assured Forwarding Class 3 High Drop Precedence

AF41 100010—Assured Forwarding Class 4 Low Drop Precedence

AF42 100100—Assured Forwarding Class 4 Medium Drop Precedence

AF43 100110—Assured Forwarding Class 4 High Drop Precedence

N/A (default)

  • Maxretransdest—(Optional) Maximum number of retransmissions to a destination address (PEERADDR1 or PEERADDR2) before it is declared failed. Enter a value in the range 1 to 10; the default is 3.

Example:

The MML command shown in the following example creates an association between an Cisco PGW 2200 Softswitch and a NAS:

mml> prov-add:association:name="nasassoc2",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2",
peeraddr1="10.82.80.30",peeraddr2="10.82.81.30",extnode="va-5300-37",type="IUA",
iproute1="iprte1",iproute2="iprte2"
 

The MML command shown in the following example configures the H.248 transport protocol as SCTP:

mml> prov-add:association: NAME="h248-sctp1",DESC="link 1 to VXSM-01",type="H248", ipaddr1="IP_Addr1", port=2944, peeraddr1="10.0.0.3",peerport=2944, extnode="h248-VXSM-01"

Comments:

Performance Impact Category: A

ATMPROFILES—ATM Profiles

 

Purpose:

Add, delete, edit, or retrieve an ATM profile in routeAnalysis.dat.

Syntax:

prov-add:atmprofiles:name =" atm profiles name ", atmprofiles =" ATM profiles string "
prov-dlt:atmprofiles:name =" atm profiles name "
prov-ed:atmprofiles:name =" atm profiles name ", atmprofiles =" ATM profiles string "
prov-rtrv:atmprofiles:name =" atm profiles name ", atmprofiles =" ATM profiles string "

Input Description:

  • name—The MML name of the ATM profile. It has a string length 1 to 20 in quotes. Alphanumerics and dashes are allowed. The name must start with a character.
  • atmprofiles—ATM profiles string. It has a string length of 0 to 128.

Example:

The MML command shown in the following example adds the atmprofile atmprof1 to ITU1.

mml> prov-add:atmprofiles:name="atmprof1",atmprofiles="ITU1;custom100"
$ATMProfiles
# CiscoMGC: 01
#name ATMProfiles
atmprof1 ITU1;custom100
 

The MML command shown in the following example deletes the atm profile.

mml> prov-dlt:atmprofiles:name="atmprof1"
 

The MML command shown in the following example edits the atm profile.

mml> prov-ed:atmprofiles:name="atmprof1",atmprofiles="ITU1;custom200"
 

The MML command shown in the following example displays the atm profile.

mml> prov-rtrv:atmprofiles:name="atmprof1",atmprofiles="ITU1;custom100"

AXLSERVER—AXL Server

 

Purpose:

Add—Sets the AXL server on the PGW to IS/OS.

Delete—Deletes the AXL server on the PGW.

Edit—Changes the state of the AXL server on the PGW.

Retrieve—Retrieves the state of the AXL server on the PGW.

Note A ctipath cannot have more than two AXL servers.

Syntax:

prov-add:axlserver : name =" name ", desc =" description ", ctipath =” ctisigpath ”, ipaddr1 =“ localipaddr ”, < ipaddr2 =” ipaddress ”>, port = value , peeraddr1 =” ipaddress ”, peeraddr2 =” ipaddress ”, peerport =” ctimgrport ”, iproute1 =” iproute1 ”[, iproute2 =” iproute2 ”] , username =” username ”, password =” password
prov-dlt:axlserver: name =" name "
prov-ed:axlserver: name =" name ", desc =" description ", username =” username ”, password =” password
prov-rtrv:axlserver: name =" name "|" all "

Input Description:

  • name—MML name of the AXL server.
  • desc—Description of the AXL server.
  • ctipath—Name of an existing CTI sigpath.
  • ipaddr1—Local IP address of the CTI manager.
  • ipaddr2—(Optional) Second local IP address of the CTI manager.
  • port—IP port.
  • peeraddr1—First peer address of the CTI manager.
  • peeraddr2—Second peer address of the CTI manager.
  • peerport—Peer CTI manager port.
  • iproute1—Name of the first IP route.
  • iproute2—(Optional) Name of the second IP route.
  • username—User’s name. Can be a string up to 128 characters.
  • password —User’s password. Can be a string up to 128 characters.

Example:

The MML command shown in the following example sets the AXL server:

mml> prov-add:axlserver:name="axlserver", desc ="AXL server",ctipath =”ctisigpath”, ipaddr1=“IP_addr1”, ipaddr2=“IP_addr2”, port=1, peeraddr1=”161.44.1.1”, peeraddr2=”161.44.1.5”, iproute1=”ip1”, iproute2="iprte2", username=”admin”, password =”cisco”
 

The MML command shown in the following example deletes the AXL server:

mml> prov-dlt:axlserver:name="axlserver"
 

The MML command shown in the following example modifies the AXL server:

mml> prov-ed:axlserver:name="axlserver",desc ="AXL server",username =”admin”,password =”cisco”
 

The MML command shown in the following example retrieves the state of the AXL server:

mml> prov-rtrv:axlserver:name="axlserver"

Comments:

Property Domain—SIGPATH

Protocol Family—CTI

BEARERCAP—Bearer Capability

 

Purpose :

Add—Configures the bearer capability.

Delete—Deletes components or parameters in the bearer capability function.

Edit—Edits the bearer capability function.

Retrieve—Retrieves either all or a specified set of configured bearer capability attributes.

Syntax:

prov-add:bearercap: name =” one ”, bearercap =” tmrvalue1;tmrvalue2;tmrvalue3
prov-dlt:bearercap: name =” name
prov-ed:bearercap: name =” one ”, bearercap =” tmrvalue1;tmrvalue2;tmrvalue3
prov-rtrv:bearercap: {”all”| name =” bearer1 ”}

Input Description:

  • name—Bearer capability name. Up to 20 alphanumeric characters.
  • bearercap—Series of transmission medium requirements (TMR) values separated by semicolons.
  • all —Specifies all configured bearer capability attributes.

Example :

The MML commands shown in the following example provision bearer capability attributes:

mml> PROV-ADD:bearercap:name=”bearer1”,bearercap=”12;05;31”
mml> PROV-ADD:siprttrnkgrp:name=”2222”,url=”128.107.132.143”,svrr=0,sipproxyport=5060, version=”2.0”,cutthrough=1,extsupport=1,bearercapname=”bearer1”
mml> PROV-ADD:rttrnkgrp:name=”1”,type=1,reattempts=3,queuing=0,cutthrough=1, bearercapname=”bearer1”
 

The MML command shown in the following example deletes bearer capability functionality:

mml> PROV-DLT:bearercap:name=”one”
 

The MML command shown in the following example changes the TMR values in the bearer capability function:

mml> PROV-ED:bearercap:name=”one”,bearercap=”4;5;6”

BRIPATH—BRI Signaling Service

 

Purpose:

Create a BRI signaling service.

Syntax:

prov-add:bripath:name =" BRI Path Name ", extnode =" External Node Name ",
desc =" Description of the BRI Path ", mdo =" MDO ", side =" Call Side ",
custgrpid =" Customer Group ID ", crlen = Call Reference Length

Input Description:

  • name —The name you want to give to the QSIG/Q.931 over BRI Backhaul signaling service. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
  • desc —An assigned name. It can be as many as 128 alphanumeric characters in length.
  • extnode —MML name of a previously defined QSIG/Q.931 BRI voice gateway external node.
  • mdo —MDO filename, from the following list:

ETS_300_102

Q931

ETS_300_172

  • side —Q.931 call model side, user for user side and network for network side; (network).
  • custgrpid —VNET ID, a four-digit ID; (0000).
  • crlen —Call reference length; Valid values: 0 through 2. The value indicates the number of bytes in the call reference length (0).

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example adds a BRI path:
mml> prov-add:bripath:name="brisvc1",extnode="bri-2600-1",desc="BRI service to C2600",mdo="ETS_300_172",side="network",custgrpid="V123",crlen=2
 
MGC-01 - Media Gateway Controller 2009-11-25 10:47:38.222 EST
M COMPLD
"bripath"
;

C7IPLNK—C7 IP Link

 

Purpose:

Create a C7 IP link.

Syntax:

prov-add:c7iplnk:name =" C7 IP Link Name ", desc =" C7 IP Link Description ",
sessionset =" Session Set Name ", lnkset =" Link Set Name ", slc = Signaling Link Code , pri = Priority , timeslot = Timeslot

Input Description:

  • name—MML name of the C7 IP link. Up to 10 alphanumeric characters with an alpha character at the beginning.
  • desc—The description of the C7 IP link. Up to 128 alphanumeric characters.
  • sessionset —The name of sessionset that encapsulates the SS7 messages for this link.
  • lnkset—Displays the linkset to which this link belongs.
  • slc—Unique identifier for the link. Corresponds to the Signaling Link Code (SLC) received from the carrier. (Default = 0.)
  • pri —Identifies the priority value of the link. Give links same priority for load sharing. (Default = 1.)
  • timeslot —Identifies the WIC port of the Cisco SLT for the link. (Default = 0.)

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example creates a C7 IP link
mml> prov-add:c7iplnk:name="C7Ip-1",desc="C7Iplink-1 in ls1",pri=1,slc=0,lnkset="ls1", sessionset="SessionSet-1",timeslot=0
MGC-01 - Media Gateway Controller 2008-03-04 10:47:38.222 EST
M COMPLD
"c7iplnk"
;

CHARGE—Charge Table

 

Purpose:

Create an entry in the charge table.

Syntax:

prov-add:charge:chorig=" value ",chdest=1,dow = Day of Week ,tariffdesc=" Tariff Description "

Input Description:

  • chorig —Charge origins are integer values (1-9999). The value can be set incrementally when planning the data build or you can choose to use any valid value at any time.
  • chdest —Charge destination.
  • dow —(Optional) Day of the Week, or holiday1 through 3. Default = 0.
  • tariffdesc —Tariff descriptor for Advice of Charge (AOC). Up to 62 alphanumeric characters. You can use a signal tariff descriptor, or space-separated tariff descriptor and timechange (for example, trfId1 tmChg1) with maximum 11 tariff descriptors. The timechange values must be divisable by 15.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

In the following example, calls from charge origin 1000 to charge destination 1000 use a tariff ID of 3 from 0000-0700, 4 from 0700-1800 and 3 from 1800 to 2400 from Monday to Friday. Saturday and Sunday are charged at a fixed rate using tariff Id 3.

mml> prov-add:charge:chorig=1000,chdest=1000,tariffdesc="3 0700 4 1800 3"
mml> prov-add:charge:chorig=1, chdest=1, dow=”SATURDAY”, tariffdesc="3"
mml> prov-add charge:chorig=1, chdest=1, dow=”SUNDAY”, tariffdesc="3"
MGC-01 - Media Gateway Controller 2009-11-25 10:47:38.222 EST
M COMPLD
"charge"
;

CODECSTRING—Codec Selection

 

Purpose :

Add, delete, edit, or retrieve a codec selection.

Syntax:

prov-add:codecstring:name =” name of codec ”, codecstring =” codecstring
prov-dlt:codecstring:name =” name of codec
prov-ed:codecstring:name =” name of codec ,codecstring =” codecstring
prov-rtrv:codecstring:name =” name of codec

Input Description:

  • name—Name of the codec, a string that can be up to 20 alphanumeric characters in length.
  • codecstring—A series of codec choices separated by semicolons. This entry can be up to 140 characters in length.

Example :

The MML commands shown in the following example provisions the codec result type:

mml> PROV-ADD:codecstring:name=”codec1”,codecstring=”G.726-32;G.729b-L”
mml> NUMAN-ADD:resulttable:custgrpid=”T001”,resulttype=”codec”,dw1=”codec1”,dw2=”1”, setname=”ra1”,name=”res1”
 

The MML command shown in the following example deletes the codec string “codec1”:

mml> PROV-DLT:codecstring:name=”codec1”
 

The MML command shown in the following example edits the codec string choices:

mml> PROV-ED:codecstring:name=”codec1”,codecstring=”G.726-32;G.729b-L”

Comments:

Specified codecs are not validated.

CONDRTE—Conditional Routing Table

 

Purpose :

Add—Configures the conditional routing table.

Delete—Deletes an entry from the conditional routing table or deletes the entire table.

Edit—Edits the conditional routing table.

Retrieve—Retrieves the conditional route, an entry in the conditional routing table, or all entries in the table.

Syntax:

prov-add:condrte:name=” one ”,dow=” day ”,condrtedesc=” descone
prov-dlt:condrte:name=” condName ”,<dow=” default ”>
prov-ed:condrte:name=” one ”,dow=” day ”,condrtedesc=” descone
prov-rtrv:condrte:name=” condName
prov-rtrv:condrte:name=” condName ”, dow=” default
prov-rtrv:condrte:” all

Input Description:

  • name—Conditional routing name; up to 20 alphanumeric characters.
  • dow—Day of the week. For the PROV-ADD command, enter Default. Valid values:

DEFAULT

MONDAY

TUESDAY

WEDNESDAY

THURSDAY

FRIDAY

SATURDAY

HOL1

HOL2

HOL3

  • condrtedesc—Description of the conditional routing table (previously configured).

Example :

The MML commands shown in the following example configure the conditional routing table:

mml> PROV-ADD:condrte:name=”one”, dow=”default”, condrtedesc=”descone”
 

The MML command shown in the following example deletes the conditional routing table:

mml> PROV-DLT:CONDRTE:NAME=”condName1”
 

The MML command shown in the following example adds an entry for hol1 to conditional route one:

mml> PROV-ED:condrte:name=”one”, dow=”hol1”, condrtedesc=”descone”
 

The MML command shown in the following example displays the named conditional route:

mml> PROV-RTRV:CONDRTE:NAME=”condName”

Comments:

A conditional route description name must be configured before any conditional route can be connected to it.

Performance Impact Category: B, C. Impact depends on the size of the current configuration and what information is retrieved.

CONDRTEDESC—Conditional Routing Table Description

 

Purpose :

Add, edit, or retrieve the conditional routing table description.

Syntax:

prov-add:condrtedesc:name=” descone ”,primary=” ON ”,rtlistname=” three ”|percname=” name ”}
prov-ed:condrtedesc:name=” descone ”,starttime=” 0000 ”,endtime=” 1200 ”[,primary=” ON ”]
{,rtlistname=”
name ”|perc=” name ”}
prov-rtrv:condrtedesc:name=” descone

Input Description:

  • name—Conditional routing table description.
  • starttime—Enter a value from 0000 to 2359.
  • primary—The primary entry for the percentage-based routing name.

For the PROV-ADD command, either enter ON, or do not specify this component.

For the PROV-ED command, this entry specifies the primary route. Either STARTTIME and ENDTIME or PRIMARY with a value of ON is supported.

  • rtlistname—Routing list name. Enter up to 20 alphanumeric characters (previously configured).
  • percname—Percentage-based routing name (previously configured).

Example :

The MML command shown in the following example configures the conditional routing table:

mml> PROV-ADD:condrtedesc:name:”descone”,rtlistname=”three”
 

The MML command shown in the following example adds another time period to the conditional route description “desctwo”:

mml> PROV-ED:condrtedesc:name=”desctwo”,starttime=”1200”,endtime=”2345”,rtlistname=”three”

Comments:

A conditional route description name must be configured before any conditional route can be connected to it.

A total of five route list names and percentage-based routing names can be configured in a conditional route description.

CTIMGR—CTI Manager

 

Purpose:

Add, delete, edit, or retrieve the CTI manager on the PGW to IS/OS.

Note A CTI path cannot have more than two CTI managers.

Syntax:

prov-add:ctimgr : name =" name ", desc =" description ", ctipath =” ctisigpath ”, ipaddr1 =“ localipaddr ” [, ipaddr2 =” ipaddress ”], port = value , peeraddr1 =” ipaddress ”, peeraddr2 =” ipaddress ”, peerport =” ctimgrport ”, iproute1 =” iproute1 ”[, iproute2 =” iproute2 ”], username =” username ”, password =” password ”, ctiversion =“ version
prov-dlt:ctimgr : name =" name "
prov-ed:ctimgr:name =" name ", desc =" description ", ctipath =" ctisigpath ", ipaddr1 =" localipaddr ", peeraddr1 =" ipaddress ", iproute1 =" iproute1 ", username =" username ", password =" password ", ctiversion =" version "
prov-rtrv:ctimgr : name =" name "

Input

Description:

  • name—The MML name of the CTI manager.
  • desc—The description of the CTI manager.
  • ctisigpath—The name of an existing CTI sigpath.
  • ipaddr1—The local IP address of the CTI manager.
  • ipaddr2—(Optional) The second local IP address of the CTI manager.
  • port—IP port.
  • peeraddr1—The first peer address of the CTI manager.
  • peeraddr2—(Optional) The second peer address of the CTI manager.
  • peerport—Peer CTI manager port.
  • iproute1—The name of the first IP route.
  • iproute2—The name of the second IP route. This is an optional parameter.
  • username—The name of the user. Can be a string up to 128 characters.
  • password —The password used by the user. Can be a string up to 128 characters.
  • ctiversion —The version of the CTI manager. Can be a string up to 20 characters.

Example:

The MML command shown in the following example enables the CTI Manager on the PGW:

mml> prov-add:ctimgr:name="ctimgr",desc ="CTI manager 1",ctipath=”ctisigpath”, ipaddr1=“IP_addr1”,peeraddr1 =”161.44.1.1”,iproute1=”ip1”,username=”admin”,password=”cisco”, ctiversion=”5”
 

The MML command shown in the following example deletes the CTI Manager on the PGW:

mml> prov-dlt:ctimgr:name="axlserver"
 

The MML command shown in the following example enables the CTI Manager on the PGW:

mml> prov-ed:ctimgr:name="ctimgr",desc ="CTI manager 1",ctipath="ctisigpath", ipaddr1="IP_addr1",peeraddr1="161.44.1.1",iproute1="ip1",username="admin",password="cisco", ctiversion="5"
 

The MML command shown in the following example retrieves the state of the CTI Manager:

mml> prov-rtrv:ctimgr:name="axlserver"

Comments:

Property domain—SIGPATH

Protocol family—CTI

CTIPATH—CTI Path

 

Purpose:

Add, delete, edit, or retrieve the CTI sigPath.

Note The CTI sigPath can have up to eight CTI paths. Only one CTI path is allowed per CCM cluster.

Syntax:

prov-add:ctipath : name =" name ”, desc =" description ", extnode =” clustername ”, MDO =” QBE
prov-dlt:ctipath : name =" name
prov-ed:ctipath : name =" name ”, desc =" description "
prov-rtrv:ctipath : name =" name ”|" all

Input

Description:

  • name—The MML name of the CTI path.
  • description—The description of the CTI path.
  • extnode—The MML name of a previously defined external node.
  • mdo —The QBE sigpath. QBE is the default. PGW creates a QBE channel controller for each CTI path.

Example:

The MML command shown in the following example enables the CTI Manager on the PGW:

mml> prov-add:ctipath:name="ctipath”,desc="CTI path",extnode=”CCMCLUSTER”,MDO=”QBE”
 

The MML command shown in the following example deletes the CTI manager on the PGW:

mml> prov-dlt:ctipath:name="ctipath”
 

The MML command shown in the following example modifies the CTI sigPath on the PGW:

mml> prov-ed:ctipath:name ="ctipath"
 

The MML command shown in the following example retrieves information on an existing CTI sigpath on the PGW:

mml> prov-rtrv:ctipath:name="ctipath”

Comments:

Property Domain—SIGPATH

Protocol Family—CTI

DCHAN—D-Channel

Purpose :

Add, delete, edit, or retrieve a D-channel used on the Cisco PGW 2200 Softswitch.

Syntax:

prov-add:dchan : name =" name ", desc =" description ", svc =" BRI ", pri = 1 , [ sessionset ="ssetname"| tcplink ="lnkname"], sigslot =sslot, sigport =sport, subunit =sunit
prov-dlt:dchan : name =" name "
prov-ed:dchan: name =" name ", desc =" description ", svc =" BRI ", pri = 1 , [ sessionset ="ssetname"| tcplink ="lnkname"], sigslot =sslot, sigport =sport, subunit =sunit
prov-rtrv:dchan : name =" name "|”all”

Input Description:

  • name —Name you want to give to the D-channel. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
  • desc —Description of the D-channel.
  • pri —Priority. 1 through 65535. Default value is 1.
  • svc —MML name of previously configured signaling service (IPFAS or QSIG/Q.931 over BRI Backhaul only).
  • sessionset —MML name of a previously provisioned session set (used for PRI connections only). This parameter is used only for D-channels associated with IPFAS signaling services.
  • tcplink —MML name of a previously provisioned backhaul TCP link (used for BRI connections only). This parameter is used only for D-channels associated with QSIG/Q.931 over BRI Backhaul signaling services.
  • sigslot—Physical slot on the Cisco media gateway on which the link is terminated.

For Cisco 2600, 3600, and 3700 series MGWs, the valid values are integers from 0 to 63. Default value is 0.

For all other MGWs, the valid values are integers from 0 to 15. Default value is 0.

Note This parameter must be set to 0 for QSIG/Q.931 over BRI backhaul D-channels when the associated external node is a Cisco 17xx.

Note This parameter must be set to 0 when VXSM is the external node TYPE selection.

  • sigport—Physical port of the associated slot on the Cisco media gateway. Valid values are integers from 0 to 336. Must be 0–167 for non-VXSM external node types, or 1–336 for VXSM external node type. Default value is 0.

Note This parameter can be set to either 0 or 1 for QSIG/Q.931 Over BRI Backhaul D-channels.

Note When VXSM is the selected external node TYPE parameter, SIGSLOT must be set to 0, and the SIGPORT value is an integer of 1 through 336.

  • subunit—Physical subunit on the Cisco MGW. Valid values are 0 through 3, and 99. The value 99 is added in software Release 9.7(3). The value 99 is only for onboard 2-tuple T1/E1 controller on NM-HDV2-1T1/E1, NM-HDV2-2T1/E1, and so on. Default value is 0.

Provisioning Rules:

The following rules apply when you are creating or editing D-channels:

  • Backup D-channels for QSIG/Q.931 Over BRI Backhaul signaling services are not supported.
  • The priority for QSIG/Q.931 Over BRI Backhaul D-channels should be set to 1.
  • Session sets are used only in support of IPFAS D-channels.
  • TCP links are used only in support of QSIG/Q.931 Over BRI Backhaul D-channels.
  • Up to 1000 D-channels can be provisioned against a single IP address and port combination used by your Backhaul TCP links. Because the Cisco PGW 2200 Softswitch supports a maximum of two IP address and port combinations, you can provision a maximum of 1000 D-channels for a QSIG/Q.931 Over BRI Backhaul signaling service.
  • For an external node TYPE selection of VXSM, the SIGPORT range is 1-336 and SIGSLOT must be set to 0.

Example :

The MML command shown in the following example provisions an IP link:

mml> prov-add:dchan:NAME="bridchan1",DESC="QSIG BRI D channel 1", SVC="BRI", PRI="1", TCPLINK="britcp1", sigslot="4", sigport="1", subunit="1"
 

The MML command shown in the following example deletes a D-channel:

mml> prov-dlt:dchan:NAME="bridchan1"
 

The MML commands shown in the following examples modify D-channels:

mml> prov-ed:dchan:name=''ipfas-pod1-1x'',sigport=1
MGC-01 - Media Gateway Controller 2008-02-18 11:28:24.016 CST
M COMPLD
''dchan''
 
mml> prov-ed:dchan:name=''ipfas-pod1-1x'',sigport=336
MGC-01 - Media Gateway Controller 2008-02-18 11:28:26.290 CST
M COMPLD
''dchan''
;
mml> prov-ed:dchan:name= " ipfas-pod1-1x " ,sigport=338 SIGSLOT:
mml> prov-ed:DCHAN:NAME="ipfas-pod1-1x",sigport=0
MGC-01 - Media Gateway Controller 2007-11-13 04:57:39.901 EST
M DENY
SROF
"DCHAN:ipfas-pod1-1x:SIGPORT should be 1-336"
/* Status, Requested Operation Failed on the component */

DNSPARAM—Domain Name System Parameters

 

Purpose:

Provision domain name system (DNS)-related parameters to support SIP URL.

Syntax:

prov-add:dnsparam:dnsserver1 =" DNS Server 1 " ,dnsserver2 =" DNS Server 2 ",
cachesize =" Cache Size " ,ttl =" DNS Time to Live " , policy =" Policy ",
querytimeout =" Query Timeout " ,keepalive =" Keep Alive Time "

Input Description:

  • dnsserver1— IP address of primary DNS server.
  • dnsserver2— IP address of secondary DNS server. This is an optional parameter.
  • cachesize— Maximum number of cache entries used to hold DNS entries. Valid value is any integer greater than 0. The default value is 500.
  • ttl— Time-to-live interval for DNS entries, expressed in seconds. Valid value is any integer greater than 0. The default value is 3600.
  • policy— Policy type used for selecting DNS entries. Valid values are hierarchy and round-robin. The default value is hierarchy.
  • querytimeout— Timeout interval for DNS queries, expressed in milliseconds. Valid value is any integer greater than 0. The default value is 1000.
  • keepalive— Time interval to determine whether DNS server is responding, expressed in seconds. Valid value is any integer greater than 0. The default value is 30.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example provisions DNS parameters:

mml> prov-add:dnsparam:dnsserver1="serv1",dnsserver2="serv2",cachesize="500", ttl="3600",policy="hierarchy,querytimeout="1000",keepalive="30"
MGC-01 - Media Gateway Controller 2009-11-25 10:47:38.222 EST
M COMPLD
"dnsparam:
WARNING: Restart is needed to activate property(s): DnsServer1 DnsServer2 CacheSize TTL QueryTimeout KeepAlive”
;

DOMAINPROF—Domain Profile (Release 9.8(1))

 

Purpose:

Create an entry in the domain table.

Syntax:

prov-add:domainprof:domain =” Domain Name ", type =" Inbound or Outbound ",
profile =” Domain Profile Name

Input Description:

  • domain—Domain name used to analyze traffic
  • type—Direction of the profile (inbound or outbound)
  • profile —Name of a domain profile that is used for the domain name

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example creates a domain profile:

mml> prov-add:domainprof:domain=''cisco.com'',type=''INBOUND'',profile=”dpf1”
MGC-01 - Media Gateway Controller 2008-03-04 10:47:38.222 EST
M COMPLD
''domainprof''
;

Comments:

Performance impact category A applies to the commands used to manage the domain table.

DPC—Destination Point Code

 

Purpose :

Add, delete, or edit a DPC.

Syntax:

prov-add:dpc:name=" name ", desc=" description ", netaddr=” addr”, netind=num
prov-dlt:dpc:name=" name "
prov-ed:dpc:name=" name ", desc=" description ", netaddr=” addr”, netind=num

Input Description:

  • name—Name for the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
  • desc—Description up to128 alphanumeric characters in length.
  • netaddr—Network address in dot notation.
  • netind —Network indicator number. The default value is 0.

Example :

To add a DPC named dpc1, enter the following command:

mml> prov-add:dpc:NAME="dpc1",DESC="dpc1",NETADDR="1.1.5",NETIND=2
 

To delete a DPC named dpc1, enter the following command:

mml> prov-dlt:dpc:NAME="dpc1"
 

To edit a DPC named dpc1, enter the following command:

mml> prov-ed:dpc:NAME="dpc1",DESC="dpc1",NETADDR="1.2.3",NETIND=2

DPNSSPATH—DPNSS Signaling Service

Purpose :

Add, delete, or edit a DPNSS path backhauled over IP to a media gateway.

Syntax:

prov-add:dpnsspath:name=" name ", desc=" description ", extnode=” mgw ”, mdo= ”dpnss_btnr188”, custgrpid=”idnum”, s igslot=sslot, sigport=sport, subunit=sunit
prov-dlt:dpnsspath:name=" name "
prov-ed:dpnsspath:name=" name ", desc=" description ", custgrpid=”idnum”, s igslot=sslot, sigport=sport, subunit=sunit
prov-dlt:dpnsspath:name=" name "|”all”

Input Description:

  • name —Name you want to give to the DPNSS signaling service. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
  • desc —Description. It can be as many as 128 alphanumeric characters in length.
  • extnode—MML name of a previously defined DPNSS external node.
  • custgrpid—vnet ID (virtual network identification) a four-digit ID; (0000).
  • sigslot—Physical slot on the Cisco media gateway on which the link is terminated.

For Cisco 2600, 3600, and 3700 series media gateways, the valid values are integers from 0 to 63. Default value is 0.

For all other media gateways, the valid values are integers from 0 to 15. Default value is 0.

  • sigport—Physical port of the associated slot on the Cisco media gateway. Valid values are integers from 0 to 167. Default value is 0.
  • subunit—Physical subunit on the Cisco MGW. Valid values are 0 through 3, and 99. The value 99 is added in software Release 9.7(3). The value 99 is only for onboard 2-tuple T1/E1 controller on NM-HDV2-1T1/E1, NM-HDV2-2T1/E1, and so on. Default value is 0.

Provisioning Rules:

The following attributes cannot be modified:

  • NAME
  • EXTNODE

The following rules apply when you are creating or editing DPNSS signaling paths:

  • The maximum number of combined DPNSSPATHs and NASPATHs per IUA External Node is IUA.maxSigPathsPerExtNode=112 from XECfgParm.dat. Because DPNSSPATHs and NASPATHs can share the same association, the existing IUA.maxNasPathsPerExtNode is renamed to IUA.maxSigPathsPerExtNode to support both.
  • The maximum number of combined DPNSSPATHs and IUA NASPATHs is IUA.maxSigPaths=1500 from XECfgParm.dat. The existing IUA.maxNasPaths is renamed to IUA.maxSigPaths to support both with the same validation limit.
  • Check the maximum number of external nodes with IUA type using the parameter IUA.maxExtNodes=256. This parameter is shared by both naspath and dpnsspath. The existing parameter IUA.maxNasExtNodes is renamed to IUA.maxExtNodes.
  • An ASSOCIATION must be defined with same EXTNODE attribute as the DPNSSPATH. If this ASSOCIATION hasn’t been defined when the DPNSSPATH is added/edited, a warning is issued. If the ASSOCIATION still has not been defined when provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.
  • If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning message is issued to inform the user that the DPNSSPATH must also be deleted. If it has not been deleted when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.

Example :

mml> prov-add:dpnsspath:name="brisvc1”, extnode="dpnss-01", desc="DPNSS service", mdo=”dpnss_btnr188”, custgrpid=”V123”, sigslot=4, sigport=1, subunit=1
mml> prov-dlt:dpnsspath:name="brisvc1"
mml> prov-ed:dpnsspath:name="brisvc1", sigslot=3

EISUPPATH—EISUP Sigpath

 

Purpose :

Add an EISUP sigpath.

Syntax:

prov-add:EISUPPATH : name ="name", desc ="description", EXTNODE ="eisup1", MDO ="EISUP|EISUP_96VER", custgrpid ="custgrpid", origlabel ="origlabel", termlabel ="termlabel"

Input Description:

  • name—Name of the EISUP sigpath. Enter as many as 20 alphanumeric characters and enclose in straight quotes. Begin the name with a letter character. The name can be as many as 20 characters and can contain numbers, letters, and the dash (-) symbol.
  • desc—Name up to128 alphanumeric characters in length.
  • EXTNODE—External node name assigned to the media gateway you are configuring.
  • MDO —Valid message definition object (MDO) file protocol name. You can use either EISUP or EISUP_96VER. Use EISUP with PGW 2200 Release 9.7 or later, and use EISUP_96VER with PGW 2200 Release 9.6.
  • custgrpid —Customer Group ID. Enter a four-digit ID; the default is 0000.
  • origlabel —Origination Location Label.
  • termlabel —Termination Location Label.

Example :

To add an E-ISUP signaling service to the media gateway configuration, use the PROV-ADD command as follows:

mml> prov-add:eisuppath:name="eisupsrv1",extnode="extseq1",desc="EISUP Service to Ext Seq Node1

EXTNODE—External Node

Purpose :

Provisions the external node with which the Cisco PGW 2200 Softswitch communicates.

Syntax:

prov-add:extnode : name =” name ”, desc =” description ”, type =” external node type”,
isdnsigtype =” ISDN signaling type ”, group = group number
prov-dlt:extnode : name =” name
prov-ed:extnode : name =” name ”, desc =” description
prov-rtrv:extnode : name =” name

Input Description:

  • Name—MML name of the external node. Enter an alphanumeric value up to 20 characters in length that starts with an alphabetic character.
  • Desc—Description of the external node. Enter a value up to 128 characters in length.
  • Type—One of the valid external node type. This parameter is case sensitive. Valid values are listed in Table 1-1 .
  • Isdnsigtype—ISDN signaling type. Enter one of the following:

IUA

Note The maximum number of external nodes with an ISDNSIGTYPE of IUA is 256.

– N/A (default)

  • Group—M3UA or SUA group number.

Enter a number in the range 1 to 100 for M3UA or SUA nodes.

Enter 0 for nodes that do not support M3UA or SUA nodes.

Example :

The MML command shown in the following example provisions an AS5300 NAS, va-5300-37, as an external node:

mml> prov-add:extnode:name=”va-5300-37”,type=”AS5300",desc="IUA",isdnsigtype="IUA"
 

The following command adds a RADIUS accounting server as an external node:

mml> prov-add:extnode:name=”ranode1”
mml> prov-rtrv:extnode:name=”ranode1”
MGC-01 - Media Gateway Controller 2006-11-22 02:26:30.736 EST
M RTRV
''session=radius-magnolia:extnode''
/*
NAME = ranode1
DESC = notSet
TYPE = RACLUSTER
ISDNSIGTYPE = N/A
GROUP = 0
*/

The MML command shown in the following example deletes the external node:

mml> prov-dlt:extnode:name="va-5300-37"
 

The MML command shown in the following example edits the external node:

mml> prov-ed:extnode:name="va-5300-37",desc="IUA"

Comments:

Only one racluster type extnode is supported. This is checked at the add operation.

Table 1-1 lists the external node types. supported by the Cisco PGW 2200 Softswitch. In the prov-add:extnode command, the valid values for the TYPE parameter are listed in the first column (ExtNode MML Type). The other columns indicate which sigpath types the Cisco PGW 2200 Softswitch supports for the external node.


Tip You can retrieve this same information by looking at the extnode.dat file on your system. The file is typically saved in the directory /opt/CiscoMGC/etc/.


 

Table 1-1 External Node Types for Cisco PGW 2200 Softswitch Software

ExtNode MML Type
SGCP
MGCP
IPFAS
IUA
BRI
NAS
MGCP
ANNO
MGCP
IVR
SUA
Other

AS5200

IPFAS

NAS

AS5300

SGCP

MGCP

IPFAS

IUA

NAS

MGCP
ANNO

MGCP
IVR

AS5350

SGCP

MGCP

IPFAS

IUA

NAS

MGCP
ANNO

MGCP
IVR

BSMV0

AS5400

SGCP

MGCP

IPFAS

IUA

NAS

MGCP
ANNO

MGCP
IVR

BSMV0

AS5800

IPFAS

NAS

MGCP
ANNO

AS5850

MGCP

IPFAS

IUA

NAS

MGCP
ANNO

MGCP
IVR

AS7200

SGCP

MGCP

IPFAS

NAS

ASR1000

MGCP

IPFAS

IUA

BRI

H248, DTMF, UDP, TCP, ETSI_NAPT, ITU_IPNAPT, EVPND

C1751

MGCP

IPFAS

IUA

BRI

C1760

MGCP

IPFAS

IUA

BRI

C2600

SGCP

MGCP

IPFAS

IUA

BRI

C2610XM

MGCP

IPFAS

IUA

BRI

C2611XM

MGCP

IPFAS

IUA

BRI

C2620XM

MGCP

IPFAS

IUA

BRI

C2621XM

MGCP

IPFAS

IUA

BRI

C2650XM

MGCP

IPFAS

IUA

BRI

C2651XM

MGCP

IPFAS

IUA

BRI

C2691

MGCP

IPFAS

IUA

BRI

C2801

MGCP

IPFAS

IUA

BRI

C2811

MGCP

IPFAS

IUA

BRI

C2821

MGCP

IPFAS

IUA

BRI

C2851

MGCP

IPFAS

IUA

BRI

C3600

SGCP

MGCP

IPFAS

C3640

MGCP

IPFAS

IUA

BRI

C3640A

MGCP

IPFAS

IUA

BRI

C3660

SGCP

MGCP

IPFAS

IUA

BRI

NAS

C3725

MGCP

IPFAS

IUA

BRI

C3745

MGCP

IPFAS

IUA

BRI

C3825

MGCP

IPFAS

IUA

BRI

C3845

MGCP

IPFAS

IUA

BRI

C7200

MGCP

IPFAS

IUA

BRI

H248, DTMF, UDP, TCP, ETSI_NAPT, ITU_IPNAPT, EVPND

C7600

MGCP

IPFAS

IUA

BRI

H248, DTMF, UDP, TCP, ETSI_NAPT, ITU_IPNAPT, EVPND

C12000

MGCP

IPFAS

IUA

BRI

H248, DTMF, UDP, TCP, ETSI_NAPT, ITU_IPNAPT, EVPND

CAT8510

SGCP

MGCP

CAT8540

SGCP

MGCP

CRS1

MGCP

IPFAS

IUA

BRI

H248, DTMF, UDP, TCP, ETSI_NAPT, ITU_IPNAPT, EVPND

H323

EISUP

ITP

SUA

M3UA

LIMD

LI

LS1010

SGCP

MGCP

MC3810

MGCP

IPFAS

MGC

EISUP

MGX8260

MGCP

IPFAS

NAS

MGX8850

SGCP

MGCP

IPFAS

RACLUSTER

RA

SCP

TCAPIP

SLT

BSMV0

UNKNOWN

UNKNOWN

VISM

SGCP

MGCP

IPFAS

VXSM

SGCP

MGCP

IPFAS

IUA

MGCPANNO

M3UA, H248, IPANNO, IPTONE, CODEC, DTMF, UDP, SCTP

EXTNODETYPES—External Nodes

 

Purpose:

Retrieves the external nodes connected to the media gateway.

Syntax:

prov-rtrv:extnodetypes

Output Description:

MGC-01 -- Media Gateway Controller 2010-02-25 10:44:40.285 PST
M RTRV
“Session = 0312:extnodetypes”
/*
External Node Type Supported Sigpath Type(s)
------------------ -------------------------
AS5200 IPFAS NAS
AS5300 SGCP MGCP IPFAS NAS IUA MGCPANNO MGCPIVR
AS5350 SGCP MGCP IPFAS NAS BSMV0 IUA MGCPANNO MGCPIVR
AS5400 SGCP MGCP IPFAS NAS BSMV0 IUA MGCPANNO MGCPIVR
AS5800 IPFAS NAS MGCPANNO
AS5850 IPFAS NAS MGCPANNO MGCP IUA MGCPIVR
AS7200 SGCP MGCP IPFAS NAS
ASR1000 H248 DTMF UDP TCP ETSI_NAPT ITU_IPNAPT EVPND
C12000 H248 DTMF UDP TCP ETSI_NAPT ITU_IPNAPT EVPND
C1751 MGCP IPFAS IUA BRI
C1751_OLD MGCP IPFAS IUA BRI
C1760 MGCP IPFAS IUA BRI
C1760_OLD MGCP IPFAS IUA BRI
C2600 SGCP MGCP IPFAS IUA BRI
C2600_OLD SGCP MGCP IPFAS IUA BRI
C2610XM MGCP IPFAS IUA BRI
C2610XM_OLD MGCP IPFAS IUA BRI
C2611XM MGCP IPFAS IUA BRI
C2611XM_OLD MGCP IPFAS IUA BRI
C2620XM MGCP IPFAS IUA BRI
C2620XM_OLD MGCP IPFAS IUA BRI
C2621XM MGCP IPFAS IUA BRI
C2621XM_OLD MGCP IPFAS IUA BRI
C2650XM MGCP IPFAS IUA BRI
C2650XM_OLD MGCP IPFAS IUA BRI
C2651XM MGCP IPFAS IUA BRI
C2651XM_OLD MGCP IPFAS IUA BRI
C2691 MGCP IPFAS IUA BRI
C2691_OLD MGCP IPFAS IUA BRI
C2801 MGCP IPFAS IUA BRI
C2811 MGCP IPFAS IUA BRI
C2821 MGCP IPFAS IUA BRI
C2851 MGCP IPFAS IUA BRI
C3600 SGCP MGCP IPFAS NAS IUA
C3640 MGCP IPFAS IUA BRI
C3640A MGCP IPFAS IUA BRI
C3660 SGCP MGCP IPFAS NAS IUA BRI
C3725 MGCP IPFAS IUA BRI
C3725_OLD MGCP IPFAS IUA BRI
C3745 MGCP IPFAS IUA BRI
C3745_OLD MGCP IPFAS IUA BRI
C3825 MGCP IPFAS IUA BRI
C3745 MGCP IPFAS IUA BRI
C7200 H248 DTMF UDP TCP ETSI_NAPT ITU_IPNAPT EVPND
C7600 H248 DTMF UDP TCP ETSI_NAPT ITU_IPNAPT EVPND
CAT8510 MGCP SGCP
CAT8540 MGCP SGCP
CCMCLUSTER N/A
CRS1 H248 DTMF UDP TCP ETSI_NAPT ITU_IPNAPT EVPND
H323 EISUP
ITP M3UA SUA
LTMD LI
LS1010 MGCP SGCP
MC3810 MGCP IPFAS
MGC EISUP
MGX8260 MGCP IPFAS NAS
MGX8850 MGCP SGCP IPFAS

 

RACLUSTER RA
SCP TCAPIP
SLT BSMV0
TALISS7 SS7SG
UNKNOWN UNKNOWN
VISM MGCP SGCP IPFAS
VXSM MGCP SGCP IPFAS IUA H248 MGCPANNO M3UA IPANNO IPTONE CODEC DTMF UDP SCTP
*/
;

Example:

The MML command shown in the following example displays the external nodes:

mml> PROV-RTRV:extnodetypes

Comments:

The prov-rtrv:extnodetypes command is a special retrieve command that is used in the same MML help session as other special retrieve commands such as:

  • prov-rtrv:session —Retrieves provisioning session information.
  • prov-rtrv:variants —Retrieves all variants.
  • prov-rtrv:profiletypes —Retrieves all profile types.

FILES—File Importing or Exporting

 

Purpose:

Import or export a file. The following .dat files are affected:

  • files.dat
  • trunkGroup.dat
  • bearerChan.dat
  • bearerChanSwithced.dat,
  • dialplan.dat
  • <custGrpId>.dialPlan (<custGrpId> = customer group ID)

Database can also be affected by the files component.

Syntax:

prov-add:files:name =" File Type " ,type =" File Name " ,action =" Action on the File "

Input Description:

  • name—File type.

bcfile = bearer channel file

tkgfile = trunk group file

awhitefile = A-number white list file

bwhitefile = B-number white list file

ablackfile = A-number black list file

bblackfile = B-number black list file

portnumfile = ported number file

numanfile = dial plan file

achgoriginfile = A-number charge origin file

anumdpselfile = A-number dial plan selection file

announcementfile = announcement file

scriptfile = script file

cliprefixfile = calling line identity (CLI) prefix file

ipaddrfile = IP address file

h323idfile = H.323 ID file

fullnumtransfile = full number translation file

taglistfile = tag list file

tagvaluefile = tag value file

desttransfile = destination translation file

routeselectionfile = route selection file

  • file—File name. The file should be present in the etc/cust_specific directory.
  • action —Action on the file, import or export. Importing a file is converting customer files into .dat files. Exporting a file is converting .dat files into customer files.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:files:name="bcfile",file="trunkCust.dat",action="import"
MGC-01 - Media Gateway Controller 2008-03-04 10:47:38.222 EST
M COMPLD
"files:WARNING: All existing trunk groups have been replaced with the ones in the imported file.
All existing bearer channels have been deleted. Please import bearer channels associated with new trunk groups."
;

GTDPARAM—Generic Transparency Descriptor (GTD) Parameters

 

Purpose:

Provision the GTD parameters.

Syntax:

prov-add:gtdparam:name =" MML Name ", gtdparamstring =" GTD Parameter String ", overridestring =" OverrideString "
prov-dlt:gtdparam:name =" MML Name "
prov-ed:gtdparam:name =" MML Name ", gtdparamstring =" GTD Parameter String ", overridestring =" OverrideString "
prov-rtrv:gtdparam:name =" MML Name "
prov-rtrv:gtdparam: " all "

Input Description:

  • name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
  • gtdparamstring—A string of parameters that defines the ISUP messages and parameters that are transparently transported by the Cisco PGW 2200 Softswitch. The maximum length of the string is 460 characters. The valid values are as follows:

ALL

Individual ISUP parameter codes (a complete list of valid ISUP parameter codes can be found in Table 1-2 ).

  • overridestring —GTD override fields string. The maximum length of the string is 256 characters.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:gtdparam:name="ISUP",gtdparamstring="All"
MGC-01 - Media Gateway Controller 2008-03-04 10:47:38.222 EST
M COMPLD
"gtdparam"
;

Table 1-2 lists the GTD parameters in alphabetical order.

 

Table 1-2 GTD Parameters

GTD Parameter
GTD Parameter Description

ACL

Automatic Congestion Level

ADI

Access Delivery Information

APP

Application Transport

ATP

Access Transport

BCI

Backward Call Indicators

BSG

Business Group

BVN

Backward GVNS

CAI

Cause Indicators

CCN

CCNR Possible Indicator

CCS

Call Completion Service Setup

CDI

Call Diversion Information

CDN

Called Directory Number

CDT

Call Diversion Treatment Indicators

CGL

Calling Geodetic Location

CGN

Calling Party Number

CHI

Call History Information

CHN

Charge Number

CIC

Circuit Identification (Call Instance) Code

CID

Carrier Identification

CIN

Called IN Number

CMI

Call Modification Indicators

CNF

Conference Treatment Indicator

CNN

Connected Number

CNR

Connection Request

COL

Collect Call Request

COR

Correlation Identity

CPC

Calling Party Category

CPN

Called Party Number

CRF

Call Reference

CSI

Carrier Selection Information

CSP

Carrier Service Provider Information

CTI

Continuity Indicators

CTN

Call Transfer Number

CTR

Call Transfer Reference

DIS

Display Information

ECI

Echo Control Information

EGR

Egress

EVI

Event Information Indicators

FAI

Facility Indicators

FCI

Forward Call Indicators

FDC

Known Field Compatibility Information

FVN

Forward GVNS

GCI

Global Call Identification

GEA

Generic Address

GED

Generic Digits

GEN

Generic Name

GIC

Closed User Group Interlock Code

GNO

Generic Notification

GRF

Generic Reference

HOC

Hop Counter

HTR

Hard To Reach

INI

Information Indicators

IRI

Information Request Indicators

ISC

Originating ISC point Code

JUR

Jurisdiction

LON

Location Number

LPI

Loop Prevention Indicator

LSP

Local Service Provider Information

MCI

Message Compatibility Information

MCR

MCID Response indicator

MLP

MLPP precedence

MRI

MCID Request Indicator

NET

Network Transport

NMC

Network Management Controls

NOC

Nature of Connection Indicators

NPF

Number Portability Forward Information

NRN

Network Routing Number

NSF

Network Specific Facilities

OBI

Optional Backward Call Indicators

OCI

Original Called IN Number

OCN

Original Called Number

OCT

Call Offering Treatment Indicators

OFI

Optional Forward Call Indicators

OLI

Originating Line Information

OSI

Operator Services Information

OTN

Outgoing Trunk Group Number

PBI

Pivot Backward Information

PCA

Pivot Capability

PCI

Parameter Compatibility Information

PCT

Pivot Counter

PDC

Propagation Delay Counter

PFI

Pivot Forward Information

PRI

Pivot Routing Indicator

PRN

Protocol Name

PVS

Pivot Status

QOR

Query On Release Capability

RBI

Redirect Backward Information

RCT

Redirect Counter

RDC

Redirect Capability

RDS

Redirect Status

RFI

Redirect Forward Information

RGN

Redirecting Number

RMO

Remote Operations

RNI

Redirection Information

RNN

Redirection Number

RNR

Redirection Number Restriction

SCF

SCF ID

SCI

Service Code Indicator

SEA

Service Activation

SEG

Segmentation Indicator

SPC

Signaling Point Code

SPR

Special Processing Request

SRI

Suspend/Resume Indicators

SUN

Subsequent Number

TID

Transaction ID

TMP

Transmission Medium Required Prime

TMR

Transmission Medium Required

TMU

Transmission Medium Used

TNS

Transit Network Selection

TRR

Transaction Request

UCI

UID Capability Indicators

UFC

Unknown Field Compatibility Information

UID

UID Indicators

USI

User Service Information

USP

User Service Information Prime

UTI

User Teleservice Information

UUI

User-To-User Indicators

UUS

User-To-User Information

VER

Version of GTD

GWPOOL—Gateway Pool (Release 9.8(1))

 

Purpose:

Adds a gateway pool in the Cisco PGW 2200 Softswitch.

Syntax:

prov-add:GWPOOL:NAME= ”gatewaypoolid” , DESC= ”description” , PROFILE= ”gateway pool profile”

Input Description:

  • NAME—Gateway pool ID, which is an integer in the range 1–9999. The values 2–100 are reserved for future use.
  • DESC—Gateway pool description, this description can be up to 128 characters long.
  • PROFILE—MML name of a previously configured gateway pool.

Example:

prov-add:GWPOOL:NAME=”101”, DESC=”DBE gateway pool”, PROFILE=”GWPool_profile1”

Comments:

  • Gateway pool ID 1 identifies the global default VXSM gateway pool.
  • Customer can use the MML command prov-ed to change the gateway pool profile. In this case, the new gateway pool profile is checked against all gateways in this gateway pool. Also, you can use the command prov-ed to change the gateway pool description.
  • prov-dlt:GWPOOL. The associated board gateways are disassociated with this gateway pool first.

H248PATH—H.248 Signaling Protocol Service

 

Purpose:

Provisions the H.248 signaling protocol service. The parameters are stored in sigPath.dat, which contains the EXTNODE compID.

Syntax:

prov-add:H248PATH: NAME =” path name ”, DESC =” H248 path description ”, EXTNODE =” external node ”, LABEL =” loclbl1

Note The parameter “LABEL“ is added in software Release 9.8(1).

Input Description:

  • NAME —MML name of a H.248 path. This name can be up to 20 alphanumeric characters in length.

Special characters allowed are quotes (“).

The name must start with an alphabetic character.

  • DESC —H.248 path description. This description can be up to 128 characters in length.
  • EXTNODE —MML name of a previously configured external node.
  • LABEL —Call limiting label for this gateway. The parameter “LABEL“ is added in software Release 9.8(1).

Example:

The MML command shown in the following example provisions the sigpath h249-sigpath-01 for the EXTNODE h248-VXSM-01:

mml> prov-add:H248PATH:NAME=”h248-sigpath-01”, DESC=”Service to H248”, EXTNODE=”h248-VXSM-01”
mml> prov-add:H248PATH:NAME=”h248-sigpath-01”, DESC=”Service to H248”,EXTNODE=”h248-VXSM-01”, LABEL=”loclbl1”

Comments:

Performance Impact Category: A

  • LABEL is used only to control the simultaneous contexts on a gateway. The same label cannot be used elsewhere on a sigPath/trunk group/dialplan.
  • Only the IP-IP context is counted for this label. Provision LABEL only for DBE.

Note Because a VXSM can be used simultaneously as a TDM gateway, never add LABEL for a VXSM gateway.

HOLIDAY—Charge Holiday

 

Purpose:

Provision the Charge Holiday List.

Syntax:

prov-add:holiday:date =” date ", hday =" hday "
prov-dlt:holiday:date =” date "
prov-ed:holiday:date =” date ", hday =" hday "
prov-rtrv:holiday:date =” date "
prov-rtrv:holiday: all

Input Description:

  • date—The date of holiday, in the form at YYYY.MM.DD.
  • hday—The holiday value. Valid values: HOL1, HOL2, and HOL3.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example inserts a holiday date into the Charge Holiday list and designates it as a "hol1," "hol2," or "hol3":

mml> prov-add:holiday:date="2001.12.25",hday="hol1"
 

The MML command shown in the following example deletes the existing holiday date (2001.12.31) from the Charge Holiday list:

mml> prov-dlt:holiday:date="2001.12.31"
 

The MML command shown in the following example changes the holiday date (2001.12.25) from "hol1" to a "hol2":

mml> prov-ed:holiday:date="2001.12.25",hday="hol2"
 

The MML command shown in the following example retrieves the existing holiday date (2001.12.31) from the Charge Holiday list:

mml> prov-rtrv:holiday:date="2001.12.31"
 

The MML command shown in the following example retrieves all existing holiday dates from the Charge Holiday list:

mml> prov-rtrv:holiday:"all"

INSERVICE—Intelligent Network Service

Purpose :

Provisions intelligent network service information.

Syntax:

prov-add:inservice: name =” name ”, skortcv = value , gtorssn =” routebygt | routebyssn ”, gtformat =” nogt | gtttnbrenc | gttt | gtonly | unknown |”, msname =” generic_lnp
prov-dlt:inservice: name =” name
prov-ed:inservice : name =” name ”, skortcv = value , gtorssn =” title or number ”, gtformat =” format ”, msname =” name
prov-rtrv:inservice: < name =” file name ”>|<“ all ”>

Input Description:

  • name—Name of the intelligent network service. Enter an alphanumeric string up to 20 characters in length.
  • skortcv—Service key. Range is 0 to 65535. Default is 0.
  • gtorssn—Global title or subsystem number. Enter one of the following:

routebygt —Routes by global title.

routebyssn —Routes by subsystem number. With this value, GTFORMAT must be NOGT.

  • gtformat—Global title format. Enter one of the following:

nogt —No global title. Enter this value when routing by subsystem number. This value must be NOGT if the GTORSSN parameter is ROUTEBYSSN.

gtttnbrenc —Uses the global title translation type numbering encoding scheme.

gttt —Uses the global title translation type.

gtonly —Uses the global title only.

unknown —Unknown.

  • msname—Message sending name. Enter an alphanumeric string up to 20 characters in length.

This name must already exist in the MessageSendingName table in trigger.dat.

Each MSNAME can only have one entry in the intelligent network service table.

  • All—All intelligent network services.

Example :

mml> prov-add:inservice:name=”serviceone”,skortcv=37,gtorssn=”routebygt”, gtformat=”gttt”, msname=”generic_lnp”
mml> prov-dlt:inservice:name=”serviceone”
mml> prov-ed:inservice:name=”serviceone”,skortcv=255
mml> prov-rtrv:inservice:”all”
MGC-01 - Media Gateway Controller 2003-01-01 18:57:26
M RTRV
NAME SKORTCV GTORSSN GTFORMAT MSNAME
ansi-aix-800-npa 4 ROUTEBYGT GTTT ansi-aix-800-npa
ansi-aim-800-npa-nxxx 5 ROUTEBYGT GTTT ansi-aim-800-npa-nxxx
cs1-inap-cli-initdp 1 ROUTEBYSSN NOGT cs1-inap-cli-initdp
inap-freephon-initdpp 0 ROUTEBYSSN NOGT inap-freephon-initdpp

INSIPHEADER—Inbound SIP Header (Release 9.8(1))

 

Purpose:

Adds an inbound SIP header table.

Syntax:

prov-add:insipheader: name =" Header Table Name ", header =” Header Name ”, message =" Message Name ", index =” Index ”, cond =” Condition ”, cdw1 =” Condition Word 1 ”, cdw2 =” Condition Word 2 ”, cdw3 =” Condition Word 3 ”, cdw4 =” Condition Word 4 ”, treat =” treatment ”, tdw1 =” treatment word 1 ”, tdw2 =” treatment word 2 ”, tdw3 =” treatment word 3 ”, tdw4 =” treatment word 4

Input Description:

  • name —Name of the SIP header table.
  • header —Name of a SIP header that the PGW uses to modify traffic.
  • message name —Name of the SIP message that triggers a customized action. The value must be the name of a SIP request or response message.
  • index —Order in which the PGW applies SIP header table entries. If a SIP header matches more than one entry in the SIP Header Table, the PGW applies the entry with the lowest index value.
  • cond —Defines how the PGW uses the SIP header table entry to analyze traffic. This field requires one or more entries in the Condition DW fields.
  • cdw1–4 —Tags the PGW uses to analyze SIP traffic.
  • treat —Action that the PGW takes when the SIP header is present.
  • tdw1–4 —Data words that describe how the PGW applies the treatment settings.

Note For more information about applying inbound SIP headers, see SIP Profiles feature module.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:insipheader:name="insipht1",message="INVITE",cond=2,treat=1, cdw1="user=phone", header="User-Agent"
MGC-01 - Media Gateway Controller 2008-03-04 10:47:38.222 EST
M COMPLD
''insipheader''
;

Comments:

Performance impact category C applies to the commands used to create, delete, and edit inbound SIP header tables.

IPFASPATH—IPFAS Transport Service

 

Purpose:

Provision the FAS over IP transport service or signaling path from a media gateway to a Cisco PGW 2200 Softswitch.

Syntax:

prov-add:ipfaspath:name =” name ", desc =" description ", extnode =” External Node Name ”,
mdo =” Protocal Variant ", custgrpid =” Cusomer Group ID ", side =” call model side ",
abflag =” DPNSS side ", crlen =” Call Reference Length ", origlabel =” Origination Location Label ", termlabel =” Termination Location Label "
prov-dlt:ipfaspath:name =” name "
prov-ed:ipfaspath:name =” name ", desc =" description ", mdo =” Protocal Variant ",
custgrpid =” Cusomer Group ID ", side =” call model side ", abflag =” DPNSS side ",
crlen =” Call Reference Length ", origlabel =” Origination Location Label ",
termlabel =” Termination Location Label "
prov-rtrv:ipfaspath:name =” name "
prov-rtrv:ipfaspath: " all "

Input Description:

  • name—Unique component name used in MML commands. The name can be up to 20 alphanumeric characters. No special characters other than hyphen are allowed. The name should begin with an alphabetic character.
  • desc—Description. The description can be up to 128 alphanumeric characters. No special characters other than hyphen are allowed. The name should begin with an alphabetic character.
  • extnode—External node name. MML name of a previously defined external node or index of the external node for SNMP.
  • mdo—MDO file name. Valid protocol name from variants.dat.
  • custgrpid—Customer group ID. Four digit ID; (0000).
  • side—Q.931 call model side. User for user side and network for network side; (network).
  • abflag—DPNSS side. a or b side, n for not applicable; (n).
  • crlen—Call reference length. 1 for 1 byte or 2 for 2 byte call reference length; (0).
  • origlabel—Originating call control (OCC) side location label. Used for Call Limiting feature.
  • termlabel—Terminating call control (TCC) side location label. Used for Call Limiting feature.

Note The parameters, origlabel and termlabel, are added in software Release 9.6(1).

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example adds an IPFAS transport service to the media gateway configuration:

mml> prov-add:ipfaspath:name="ipfassvc1",extnode="nas1",desc="PRI Backhaul Service to NAS1", mdo="ETSI_300_172",custgrpid="1111",abflag="a",crlen=1

IPGW—IP Gateway (Release 9.8(1))

 

Purpose:

Add a border gateway to a gateway pool.

Syntax:

prov-add:IPGW:POOLID =” gateway pool id ”, GW =” external node ”, VRF =” VRF name

Input Description:

  • POOLID—Gateway pool ID, which is an integer in the range of 1–9999.
  • GW—MML name of previously configured gateway.
  • VRF—VRF name. This description can be up to 30 characters long.

Example:

mml> prov-add: IPGW:POOLID=”100", GW=”dbe-01”, VRF=”sip_in_100”

Comments:

  • For a VXSM gateway, never provision the VRF field.
  • The parameters are stored in the data file gwPools.dat, which contains the EXTNODE compID.
  • To add a gateway to the global default VXSM gateway pool, enter DEFAULT in the POOLID field.
  • Use the MML command prov-dlt:IPGW to remove a border gateway from the gateway pool. If a gateway is going to be removed, it should be removed from each gateway pool first.
  • To change the VRF field use the MML command prov-ed:IPGW.

IPINMAPPING—IP In Trunk Mapping

 

Purpose:

Provision mapping between a single SIP or EISUP interface and multiple IP trunk groups using incoming IP address, subnet mask, and port number.

Syntax:

prov-add:ipinmapping:name =” name ", desc =" description ", sigsvc =” SIP/EISUP sigpath ", allowedIP =" Allowed IP Address ", allowedIPNetMask =" Allowed Net Mask ",
sipport =” Allowed SIP Port ”, trnkgrpnum =” Trunk Group Number
prov-dlt:ipinmapping:name =” name "
prov-ed:ipinmapping:name =” name ", desc =" description ", allowedIP =" Allowed IP Address ", allowedIPNetMask =" Allowed Net Mask ", sipport =” Allowed SIP Port ”,
trnkgrpnum =” Trunk Group Number
prov-rtrv:ipinmapping:name =” name "
prov-rtrv:ipinmapping: all "

Input Description:

  • name—A unique name used to describe the ipinmapping rule entry.
  • desc—Description.
  • sigsvc—SIP sigpath or EISUP sigpath. The signal path to which the ipinmapping rule applies.
  • allowedIP—Allowed IP Address. The incoming SIP IP address allowed on the trunk. This parameter is optional.
  • allowedIPNetMask—Allowed Net Mask. The subnet mask allowed on the trunk. This parameter is optional. If this parameter is blank, the Cisco PGW 2200 Softswitch uses the default subnet mask value of 255.255.255.255.
  • sipport—Allowed SIP Port. The SIP TCP or UDP port number allowed on the trunk. This parameter is for SIP sigpaths only. The sipport parameter is optional.
  • Trnkgrpnum—Trunk group number.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example maps IP traffic to a trunk group:

mml> Prov-add:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1", allowedIP="10.0.14.145", sipport=5063, trnkgrpNum=1000
 

The MML command shown in the following example maps Multiple IP ranges to a single trunk group:

mml> prov-add:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1", allowedIP="10.0.14.145", allowedIPNetmask="255.255.255.128", trnkgrpNum=1040

IPLNK—IP Link

Purpose :

Provisions an IP link used by the Cisco PGW 2200 Softswitch to communicate with an access control device.

Syntax:

prov-add:iplnk: name =” association name “, desc =“ description “, port = number , pri = priority , peeraddr =“ remote IP address “, peerport = remote port , ipaddr =“ local address “, svc =“ sig service “, iproute =“ IP route

Input Description:

  • name—Association name. Alphanumeric string up to 20 characters in length.
  • desc—IP link description. String up to 128 characters in length.
  • port— Local port number. IP port number. Range: 1 to 1024.
  • pri—Priority. Integer greater than 0. Default is 1.
  • peeraddr—Remote IP address; the default is 0.0.0.0. This can be specified as a hostname or as a DNS name.
  • peerport—Remote port number. Enter a valid IP port number in the range 1025 to 65535. Enter 2427 for MGCP.
  • ipaddr—Local logical IP address.
  • svc—Signaling service that this IP link supports. Enter the MML name of a previously defined signaling service:

NASPATH

EISUPPATH

MGCPPATH

H248PATH (Added in Release 9.7(3))

  • iproute—MML name of a previously defined IP route.

Example :

The MML command shown in the following example provisions an IP link:

mml> prov-add:iplnk:name="nas1-lnk1",ipaddr="IP_Addr1",port=3001,peeraddr="10.82.80.29", peerport=3001,pri=1,iproute="iprte1",svc="nassvc1"
 

The MML command shown in the following example configures the H.248 transport protocol as UDP:

mml> prov-add:IPLNK:NAME="h248-udp1",DESC="link 1 to VXSM-01",SVC=" h248-sigpath-01", IPADDR="IP_Addr1",PORT=2944,PEERADDR="10.82.81.194", PEERPORT=2944,PRI=1

Comments:

Performance Impact Category: A

The support of provisioning H.248 Transport Protocol as UDP was added in Release 9.7(3). There is a new parameter SVC that refers to H248PATH. This property uses sigChanDevIp.dat and sigChanDev.dat. The sessionset type in sigChanDevIp.dat could be used to indicate H248_UDP.

IPROUTE—Static IP Route

Purpose :

Provisions a static IP route.

Syntax:

prov-add:iproute: name =” IP route name “, desc =” IP route description ”, dest =" IP address ", netmask =" IP address ", nexthop =" IP address ", ipaddr =" local IP address ", pri =" priority "
prov-dlt: iproute : name =” IP route name
prov-ed:iproute : name =” IP route name “, desc =” IP route description ”, dest =" IP address ", netmask =" IP address ", nexthop =" IP address ", ipaddr =" local IP address ", pri =" priority "

Input Description:

  • Name—IP route name. Alphanumeric string up to 20 characters in length.
  • Desc—Description of IP route. String up to 128 characters in length.
  • Dest—IP address or hostname of destination. IP address in decimal dot notation or a hostname that is up to 32 characters in length.
  • Netmask—(Optional) Subnet mask of destination. IP address in decimal dot notation; the default is 255.255.255.255.
  • Nexthop—IP address of next hop router or one of the following property names defined in the XECfgParm.dat file:

IP_NextHop

IP_NextHop2

IP_NextHop3

IP_NextHop4

IP_NextHop5

IP_NextHop6

IP_NextHop7

IP_NextHop8

IP_Addr1

IP_Addr2

IP_Addr3

IP_Addr4

The IP Address should be in decimal dot notation and the hostname must be less than or equal to 32 characters.

  • IPAddr—Local IP address represented by one of the following property names defined in the XECfgParm.dat file:

IP_Addr1

IP_Addr2

IP_Addr3

IP_Addr4

  • Pri—Priority. Integer in the range 1 to 65535; the default is 1.

Example :

The MML command shown in the following example provisions a static IP route:

mml> prov-add:iproute:name="iprte1",desc="IP Route 1",dest="10.82.80.0", netmask="255.255.255.0",nexthop="10.82.82.1", ipaddr="IP_Addr1",
 

The MML command shown in the following example deletes a static IP route:

mml> prov-dlt:iproute:name="iprte1"
 

The MML command shown in the following example edits a static IP route:

mml> prov-ed:iproute:name="iprte1",dest="10.82.80.0",netmask="255.255.255.0", nexthop="10.82.82.1", ipaddr="IP_Addr1",desc="IP Route 1"

LINEXLATE—Line Translation

Purpose :

Add, delete, or, edit—Add, delete, or edit the linexlate.dat file.

Retrieve—Retrieves one or all NOA translate table entries.

Syntax:

prov-add:linexlate: name =” file name ”, desc =” file description ”, svc =” signal path ”, parameter =” value ”, direction =” value ”, number =” value ”, intnoa = value , extnoa = value
prov-dlt:linexlate: name =” file name
prov-ed:linexlate: name =” file name ”, desc =” file description
prov-rtrv:linexlate : name =” file name ”|” all

Input Description:

  • Name—Name of the file. Alphanumeric string up to 20 characters in length.
  • Desc—Description of the file. This parameter can be up to 128 characters in length.
  • SVC—MML name of a previously defined signal service.
  • Parameter—Parameter or field in the protocol message. 1 for Nature of Address (NOA).
  • Direction—Direction of the message in relation to the PGW.

IN for messages entering the PGW.

OUT for messages leaving the PGW.

  • Number—Represents a string in the protocol message.

called

calling

original called

redirecting

redirection

generic

  • Intnoa—Any valid internal call context NOA value in the range 0 to 127.
  • Extnoa—The external value of the NOA in the range 0 to 127.
  • All—All NOA table entries.

Example :

mml> prov-add:linexlate:name=”noa1”,desc=”noa in calling 10”, svc=”ss7svc1”,parameter=”1”, direction=”in”,number=”calling”,intnoa=17,extnoa=10
mml> prov-dlt:linexlate:name=”noa1”
mml> prov-ed:linexlate:name=”noa1”,desc=”noa in calling 10”
mml> prov-rtrv:linexlate:name=”all”
Name ExtNum SvcName Parameter Direction Number IntNum
noa1 10 ss7svc1 NOA IN Called 17
noa2 11 ss7svc2 NOA OUT Called 17
noa3 8 ss7svc1 NOA IN Calling 29

Comments:

For a list of internal call context NOA values, see Appendix A of Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide .

LIPATH—Lawful Intercept Signaling Service

 

Purpose:

Provision the LI signaling service.

Syntax:

prov-add:lipath:name =” Name ", desc =" description ", extnode =” External Node Name
prov-dlt:lipath:name =” Name "
prov-ed:lipath:name =” Name ", desc =" description "
prov-rtrv:lipath:name =” Name "
prov-rtrv:lipath: all "

Input Description:

  • name—Unique ID of this component and component name used in MML commands.
  • desc—Component description.
  • extnode —The name of a previously defined external node.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:LIPATH:NAME="SigPath_Name", DESC="description", EXTNODE="LI_node_name"

LNKSET—Link Set

 

Purpose:

Provision a link set.

Syntax:

prov-add:lnkset:name =" Link Set Name " ,desc =" Description " ,apc =" Adjacent Point Code Name " , proto =" Protocol Family Name " , type =" Link Set Type "
prov-dlt:lnkset:name =" Link Set Name "
prov-ed:lnkset:name =" Link Set Name " ,desc =" Description " ,proto =" Protocol Family Name " , type =" Link Set Type "
prov-rtrv:lnkset:name =" Link Set Name "
prov-rtrv:lnkset: " all "

Input Description:

  • name—MML name of the link set. Up to 10 alphanumeric characters with an alpha character at the beginning.
  • desc—The description of the linkset. Up to 128 alphanumeric characters.
  • apc —Identifies the adjacent point codes components for the SS7 node providing the linkset.
  • proto —Identifies the protocol family associated with this linkset. (Default = SS7-ANSI.)
  • type —Identifies how the signaling link is terminating on the Cisco PGW 2200 Softswitch.

TDM

IP

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:lnkset:name="ls1",desc="Link Set to apc1",apc="apc1",proto="SS7-China", type="TDM"
MGC-01 - Media Gateway Controller 2009-11-25 10:47:38.222 EST
M COMPLD
"lnkset"
;

LNKSETPROP—Linkset Properties

Purpose :

Provisions linkset properties.

Syntax:

prov-add:lnksetprop: name =” name “, layerRetries =” retries “, layerTimer =” time “, sendAfterRestart =” messages “, slsTimer =” time “, sstTimer =” time “, dialogRange =” range “, standard =” version
prov-dlt:lnksetprop : name =”< protocol family >”
prov-rtrv:lnksetprop : name =”< protocol family >”

Input Description:

  • Name—Protocol family name.
  • layerRetries—Number of times to resend request to adjacent layer without getting a response.
  • layerTimer—Time (in tenths of a second) to wait for a response from adjacent layer.
  • sendAfterRestart—Number of queued messages to send (in one group) to MTP3 after restart end.
  • slsTimer— Time (in tenths of a second) to maintain the same signal linkset in class 1 (connectionless) messages.
  • sstTimer—Time (in tenths of a second) between the sending of consecutive Subsystem StatusTest (SST) messages to an unavailable remote subsystem.
  • dialogRange—TCAP transaction ID range.
  • Standard—Version of protocol standard supported.

Example :

The MML command shown in the following example provisions linkset properties:

mml> prov-add:lnksetprop:name="SS7-ITU",layerRetries="6",layerTimer="6", sendAfterRestart="6",slsTimer="6",sstTimer="302",dialogRange="2",standard="ITU90"
 

The MML command shown in the following example displays information about linkset properties:

mml> prov-rtrv:LNKSETPROP:name="ss7-itu"
MGC-01 - Media Gateway Controller 2002-04-19 16:12:54.469 EST
M RTRV
"session=Mist915-S10P15-22MAR02:LNKSETPROP"
/*
mtp2AermEmgThr = 1
mtp2AermNrmThr = 4
mtp2CongDiscard = false
mtp2LssuLen = 1
mtp2MaxAlignRetries = 5
mtp2MaxMsuFrmLen = 272
mtp2MaxOutsFrames = 127
mtp2ProvingEmgT4 = 6
mtp2ProvingNormalT4 = 23
mtp2SuermThr = 64
mtp2T1 = 450
mtp2T2 = 250
mtp2T3 = 20
mtp2T5 = 1
mtp2T6 = 60
mtp2T7 = 10
;

Note To determine the protocol family associated with a linkset, use the PROV-RTRV:LNKSET:”ALL” command.

Comments:

Performance Impact Category: B, C. Impact depends on the size of the current configuration and what information is retrieved.

LOCLABEL—Location Label

 

Purpose:

Add, delete, edit, or retrieve the location labels.

Syntax:

prov-add:loclabel : name =”name”, desc =”description”, calllimit =call limit
prov-dlt:loclabel : name =”name”
prov-ed:loclabel : name =”name”, desc =”description”, calllimit =call limit
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 hyphen 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. Range: 0 to 6000. Default is 0.

Example:

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

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"
;

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

mml> prov-dlt:loclabel:name=”loclbl1”
MGC-01 - Media Gateway Controller 2004-03-22 19:40:47.595 PST M RTRV
"ENGG-01"
;

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

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"
;

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

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

M3UAKEY—M3UA Routing Key

Purpose :

Add, delete, or edit an M3UA routing key.

Syntax:

prov-add:m3uakey: name =” key name ”, desc =” key description ”, opc =” origination ”, dpc =” destination ”, routingcontext = value , si = service indicator , networkappearance = value
prov-dlt:m3uakey: name =” key name
prov-ed:m3uakey: name =” key name ”, desc =” key description

Input Description:

  • Name—Name of the M3UA routing key. Alphanumeric string up to 20 characters in length.
  • Desc—Description of the M3UA routing key. This parameter can be up to 128 characters in length.
  • OPC—MML name of a previously defined origination point code.
  • DPC—(Optional) MML name of a previously defined destination point code.
  • RoutingContext—This value must be a unique integer in the range 0 to 4294967295. Two M3UAKEYs or SUAKEYs cannot have the same routing context value. The default is 0.
  • SI—Service indicator. Enter one of the following:

ISUP

TUP

N/A (default)

This is an optional parameter.

  • NetworkAppearance—(Optional) This value must be in the range 0 to 32767. The default is 0, which indicates an invalid network appearance.

Example :

mml> prov-add:m3uakey:name=”key1”,desc=”first key”,opc=”opc2”,dpc=”dpc2”,routingcontext=23, si=ISUP,networkappearance=8387
mml> prov-dlt:m3uakey:name=”key1”
mml> prov-ed:m3uakey:name=”key1”,desc=”first key”

M3UAROUTE—M3UA Route

 

Purpose :

Add, delete, or edit an M3UA route.

Syntax:

prov-add:m3uaroute: name =” route name ”, desc =” route description ”, dpc =” destination ”, extnode =” external node ”, opc =” origination ”, pri = priority
prov-dlt:m3uaroute: name =” route name
prov-ed:m3uaroute: name =” route name ”,< desc =” route description ”,>< dpc =” destination ”,> < extnode =” external node ”,>< opc =” origination ”,> < pri = priority >

Input Description:

  • Name—Name of the M3UA route. Alphanumeric string up to 20 characters in length.
  • Desc—Description of the M3UA route. This parameter can be up to 128 characters in length.
  • DPC—MML name of a previously defined destination point code. The DPC must have an SS7PATH service with the M3UAKEY defined.
  • Extnode—MML name of a previously defined external node which supports M3UA signaling.
  • OPC—MML name of a previously defined origination point code.
  • PRI —M3UA Route Priority. This parameter is a 1- to 2-integer value: 1 is the default value, 1 is higher priority, 2 is lower priority.

Example :

mml> prov-add:m3uaroute:name=”route1”,desc=”first”,dpc=”dpc1”,extnode=”mgx-8260”,opc=”opc1”, pri=1
mml> prov-dlt:m3uaroute:name=”route1”
mml> prov-ed:m3uaroute:name=”route1”,desc=”first”,dpc=”dpc1”,extnode=”mgx-8260”,opc=”opc1”, pri=1

MCLCALLREJECT—Machine Congestion Level Percentage

 

Purpose :

Edit or retrieves the machine congestion level call rejection percentage value.

Syntax:

prov-ed:mclcallreject:name =” MCL name ”, callreject =” value
prov-rtrv:mclcallreject: { name =” MCL name ”|” all ”}

Input Description:

  • name—One of the following MCL names:

MCL1

MCL2

MCL3

  • callreject—Percentage of incoming calls to drop because of congestion when local machine congestion level is MCL1, MCL2, or MCL3.
  • all —All MCL values.

Example :

The MML command shown in the following example changes the percentage of calls to reject for this MCL name:

mml> PROV-ED:mclcallreject:name=”mcl1”,callreject=”25”
 

The MML command shown in the following example retrieves the percentage of calls rejected for MCL1, MCL2, and MCL3:

mml> prov-rtrv:mclcallreject:"all"
MGC-01 - Media Gateway Controller 2003-03-06 10:07:22.096 PST
M RTRV
"session=1221:mclcallreject"
/*
Name CallReject
-------------------- ----------
mcl1 25
mcl2 50
mcl3 100
*/
;

Comments:

The Cisco PGW 2200 Softswitch maintains an internal measurement of its own current congestion level referred to as the machine congestion level (MCL). The mclCallReject.dat file contains a value that defines the call reject percentage in different MCLs.

The calculation of the current MCL value (in the mclCallReject.dat file) is based on several factors, including queue lengths, call rate, and CPU utilization.

Note Because the MCL call reject values are set to system defaults, there are no PROV-ADD or PROV-DLT versions of this command.

MCLTHRESHOLD—Machine Congestion Level Thresholds

 

Purpose :

Edit or retrieve the onset and abatement MCL threshold values.

Syntax:

prov-ed:mclthreshold: name =” MCL name ”, < mcl1onset = value , mcl1abate = value ,>| < mcl2onset = value , mcl2abate = value ,>|< mcl3onset = value , mcl3abate = value >
prov-rtrv:mclthreshold: { name =” threshold factor ”|” all ”}

Input Description:

  • name—Existing threshold factor name:

callrate

cpu

memoryaddress

queuelen

virtualmemory

Enter an alphanumeric string up to 16 characters in length.

  • mcl1onset—Exceeding this value causes MCL1 onset because of the specified threshold factor.
  • mcl1abate —Falling below this value causes MCL1 to change to MCL0 because of the specified threshold factor.
  • mcl2onset—Exceeding this value causes MCL2 onset because of the specified threshold factor.
  • mcl2abate —Falling below this value causes MCL2 to change to MCL1 because of the specified threshold factor.
  • mcl3onset—Exceeding this value causes MCL3 onset because of the specified threshold factor.
  • mcl3abate —Falling below this value causes MCL3 to change to MCL2 because of the specified threshold factor.

Example :

The MML command shown in the following example changes the onset and abatement thresholds for MCL1 CPU utilization:

mml> PROV-ED:mclthreshold:name=”memoryaddress”,mcl1onset=84,mcl1abate=80,mcl2onset=88, mcl2abate=82,mcl3onset=93,mcl3abate=85
 

The MML command shown in the following example retrieves the onset and abatement thresholds for all MCL factors:

mml> prov-rtrv:mclthreshold:"all"
MGC-01 - Media Gateway Controller 2003-03-06 10:08:46.692 PST
M RTRV
"session=1221:mclthreshold"
/*
Name Mcl1Onset Mcl1Abate Mcl2Onset Mcl2Abate Mcl3Onset Mcl3Abate
------------- --------- --------- --------- --------- --------- ---------
callrate 0 0 0 0 0 0
cpu 82 75 90 77 95 85
memoryaddress 84 80 88 82 93 85
queuelen 75 60 80 70 85 75
virtualmemory 80 75 85 80 90 80
*/
;

Comments

The Cisco PGW 2200 Softswitch maintains an internal measurement of its own current congestion level referred to as the machine congestion level (MCL). The mclThreshold.dat table contains default onset and abate values of different contributing factors for MCL.

Note Because the threshold values are set to system defaults, there are no PROV-ADD or PROV-DLT versions of this command.

METERTARIFF—Meter Tariff

 

Purpose :

Populates the meterTariff table.

Syntax:

prov-add:meterTariff: tariffid =<0-511>, pulseOnAns =<0-15>, interval =< integer range >, numPulses =<0-255>, chargeApp =<0/1>, aocInd =<0/1>, MaxCalllen =<0-240>, tariffType =<0-15>
prov-dlt:meterTariff : tariffid =< id >
prov-ed:meterTariff : tariffid =< id >, pulseOnAns =<>, interval =<>, numPulses =<>, chargeApp =<>, aocInd =<>, MaxCalllen =<>, tariffType =<>
rov-rtrv:metertariff: tariffid =< id >
prov-rtrv:metertariff: all

Input Description:

  • tariffid— Independently definable integer (0–511).
  • pulseOnAns— Number of pulses on Answer.
  • interval— Interval between consecutive MPMs. The integer range is 500 to 3600000.
  • numPulses— Number of periodic pulses that are sent when the timing interval expires.
  • chargeApp— At timer expiration, the associated pulses are sent, and then the normal periodic interval timer is initiated.
  • aocInd— Indicates whether the charge data is used by the receiving switch for charging purposes or for advice of charge. This parameter is used to populate the backward MPM and is not acted upon by the PGW 2200.
  • MaxCalllen— Represents the number of call minutes the call can last.
  • tariffType— Tariff type. Only tariff type 0000 (tariff type not indicated) is used.

Example :

mml> prov-add:metertariff:tariffid=1,pulseOnAns=5, interval=1000,numPulses=5,chargeApp=1,aocInd=1,MaxCalllen=100,tariffType=0
mml> prov-dlt:m3uaroute:name=”route1”
mml> prov-ed:metertariff:traiffid=”1”,pulseOnAns=”5”,interval=”10”,numPulses=”5”,chargeApp=”1”, aocInd=”1”,MaxCalllen=”100”,tariffType=”0”
mml> prov-rtrv:metertariff:”all”
mml> prov-rtrv:metertariff:tariffid=”1”

MGCPPATH—MGCP Signaling Service

 

Purpose :

Adds an MGCP signaling service or signaling path to a trunking gateway.

Syntax:

prov-add:mgcppath:name=” name ”,extnode=” node name ”,desc=” description

Input Description:

  • name –Unique name for this signaling service. Enter up to 20 alphanumeric characters and enclose in straight quotes. You can use hyphens (-). Begin the name with a letter character.
  • extnode –External node name assigned to the media gateway you are configuring.
  • desc –Description.

Example :

The MML command in the following example adds the MGCP signaling link mgcpsrv1 to the cu1 media gateway configuration:

mml> prov-add:mgcppath:name="mgcpsrv1",extnode="cu1",desc="MGCP Service to CU 1"

Comments:

Use the PROV-RTRV command to verify that the MGCP signaling service was added.

MLTIPFAS—Multiple IPFAS Signaling Services

 

Purpose:

Provision multiple IPFAS or IPNFAS signaling paths and D-channels to a particular destination using either ISDN-PRI or DPNSS.

Syntax:

prov-add:mltipfas:name =" name ", desc =" description ", extnode =” External Node Name ”,
mdo =” Protocal Variant ", custgrpid =” Cusomer Group ID ", side =” call model side ",
pathsize =” Path Size ", sessionset =” Session Set Name ", sigslot =” Sigslot ", sigport =” Sigport ", origlabel =” origlabel ”, termlabel =” termlabel

Input Description:

  • name—Name used to derive IPFAS or IPNFAS and D-channel MML names.
  • desc—Component description.
  • extnode—External node name. MML name of a previously defined external node or index of the external node for SNMP.
  • mdo—MDO file name. Valid protocol name from variants.dat. Limited to any MDO variant from either the ISDNPRI or DPNSS protocol families.
  • custgrpid—Customer group ID. Four digit ID; (0000).
  • side—Q.931 call model side. User for user side and network for network side; (network).
  • pathsize—Number of IPFAS paths.
  • sessionset—Name of a previously configured Session Set.
  • sigslot—Physical slot on the gateway where the T1/E1 is plugged.
  • sigport—Physical port on the gateway on the slot.
  • origlabel —Originating call control (OCC) side location label. Used for Call Limiting feature.
  • termlabel —Terminating call control (TCC) side location label. Used for Call Limiting feature.

Note The parameters, origlabel and termlabel, are added in software Release 9.6(1).

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:MLTIPFAS:NAME="bhsvc1",extnode="bh1",SIDE="user",mdo="ETS_300_102", custgrpid="2222",pathsize=2,sigslot=1,SIGPORT=0,IPADDR1="IP_Addr1",PORT=7007, PEERADDR1="17.0.0.11",PEERPORT=7007

MLTTRNKGRP—Multiple Trunk Groups

 

Purpose:

Provision multiple PRI trunk groups and bearer channels.

Syntax:

prov-add:trnkgrp:name= " name ", clli= " clli ", svc= " signalling serviece ",
numtrnkgrp= " number of trunk groups ", spansize= " span size ", cic= " cic ", cu= external node name ”, endpoint= end point

Input Description:

  • name —A numeric identifier for the trunk group. An integer from 1 through 9999.
  • clli —Common language location identifier that identifies the trunk group. This can be up to 11 alphanumerical digits.
  • svc —The MML name of the signaling service associated with or controlling the trunk group.
  • numtrnkgrp —Number of trunk groups.
  • spansize —Number of trunks per span.
  • cic —Circuit Identifier Code.
  • cu —MML name of previously defined Coding nit.
  • endpoint —Text description of the trunk endpoint. An endpoint value is typically composed of an interface, a timeslot, and a domain nam.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:mlttrnkgrp:name="1000",svc="bsc1",clli="5300E4011",numtrnkgrp=2,spansize=4, trnkmemnum=1,span=0,cic=1,endpoint="S10/DS1-0/1@mgx-8850,cu="mgx-east"

NAILEDTRNK—Nailed Trunks

 

Purpose :

Adds nailed trunks.

Syntax:

prov-add:nailedtrnk:name=" Trunk ID ",srcsvc=" source service ",srctimeslot= source timeslot , dstsvc=" destination service ",srcspan= source span ,dstspan= destination span , dsttimeslot= destination timeslot, spansize= Span Size

Input Description:

  • name —Trunk group ID. A numeric identifier for the trunk group. Value range: an integer from 0 through 65535.
  • srcsvc —Used to look up the source service component ID. The MML name of a previously defined signaling service.
  • srcspan —Corresponds to the source span ID. Value range: an integer from 1 through 65535 or ffff (default). This value is converted from decimal to hexadecimal, except when the value is ffff.
  • srctimeslot —Corresponds to the source time slot. Value range: an integer from 1 through 65535. This value is converted from decimal to hexadecimal, except when the value is ffff.
  • dstsvc —Used to look up the destination service component ID. The MML name of a previously defined signaling service.
  • dstspan —Corresponds to the destination span ID. Value range: an integer from 1 through 65535 or ffff (default). This value is converted from decimal to hexadecimal, except when the value is ffff.
  • dsttimeslot —Corresponds to the destination time slot. Value range: an integer from 0 through 65535. This value is converted from decimal to hexadecimal, except when the value is ffff.
  • spansize —Span size. Indicates the number of trunks per span. Value: 1 (default) through 24 for T1, or 1 through 31 for E1.

Example :

The MML command in the following example adds a nailed trunk named “101”:

mml> prov-add:nailedtrnk:name="101",srcsvc="ss7svc1",srctimeslot=101, dstsvc="nassrv1",dstspan=3,dsttimeslot=1

Comments:

Use the PROV-RTRV command to verify that the nailed trunk was added.

NASPATH—Signaling Path Between the Cisco PGW 2200 Softswitch and a NAS

Purpose :

Provisions a signaling path between the Cisco PGW 2200 Softswitch and a NAS.

Syntax:

prov-add:naspath: name =” naspath name ”, desc =” description ”, extnode =" node ", custgrpid =” group id ”, sigslot = slot number , sigport = port number
prov-dlt:naspath: name =” naspath name

Input Description:

  • Name—NASPath name.
  • Desc—Description of the NASPath. This parameter can be up to 128 characters in length.
  • Extnode—MML name of a previously defined external node.
  • Custgrpid—Customer group ID. Enter a four-digit ID; the default is 0000.
  • Sigslot—Physical slot on the NAS defining the NFAS group. Enter an integer in the range 0 to 63; the default is 0. This is an optional parameter.
  • Sigport— Physical port on the NAS defining the NFAS group. Enter an integer in the range 0 to 167; the default is 0. This is an optional parameter.

Example :

The MML command shown in the following example provisions a NASPath between the Cisco PGW 2200 Softswitch and an external node:

mml> prov-add:naspath:name="nassvc2",desc=”second path”,extnode="va-5300-37",sigslot=0, sigport=0
 

The MML command shown in the following example deletes a naspath between the Cisco PGW 2200 Softswitch and an external node:

mml> prov-dlt:naspath:name="nassvc2"

OPC—Originating Point Code

 

Purpose :

Add or delete an OPC.

Syntax:

prov-add:opc: name =" name ", desc =" description ", netaddr =” addr ”, netind = num , type =” trueopc
prov-dlt:opc: name =" name "

Input Description:

  • name—Enter a name for the component. The name can be as many as 20 characters long and can contain numbers, letters, and the hyphen (-) symbol. The name should begin with a letter.
  • desc—Enter a long name up to 128 alphanumeric characters in length.
  • netaddr—Enter the network address in dot notation.
  • netind —Enter the network indicator number. The default value is 0.
  • type —Set to trueopc to support M3UA and SUA interfaces.

Example :

To add an OPC named opc1, enter the following command:

mml> prov-add:opc:NAME="opc1",DESC="originating pc 1",NETADDR="1.2.4",NETIND=2,type=”trueopc”
 

To delete an OPC named opc1, enter the following command:

mml> prov-dlt:opc:NAME="opc1"

OUTSIPHEADER—Outbound SIP Header (Release 9.8(1))

 

Purpose:

Adds an outbound SIP header table.

Syntax:

prov-add:outsipheader:name =" Header Table Name ", header =” Header Name ”, message =" Message Name ", policy =” Policy ”, index =” Index ”, cond =” Condition ”, cdw1 =” ConditionWord1 ”, cdw2 =” ConditionWord2 ”, cdw3 =” ConditionWord3 ”, cdw4 =” ConditionWord4 ”, treat =” treatment ”, tdw1 =” treatmentword1 ”, tdw2 =” treatmentword2 ”, tdw3 =” treatmentword3 ”, tdw4 =” treatmentword4

Input Description:

  • name —The name of the SIP header table.
  • header —The name of a SIP header that the PGW uses to modify traffic.
  • message name —The name of the SIP message that triggers a customized action. The value must be the name of a SIP request or response message.
  • policy —Defines the B2BUA mode applied to the call/trunk group.
  • index —Defines the order in which the PGW applies SIP header table entries. If a SIP header matches more than one entry in the SIP Header table, the PGW applies the entry with the lowest Index value.
  • cond —Defines how the PGW uses the SIP header table entry to analyze traffic. This field requires one or more entries in the Condition DW fields.
  • cdw1–4 —The tags the PGW uses to analyze SIP traffic. You can define up to four tags for each row in the SIP header table. SIP table header treatments take effect only if a message matches all the Condition DW fields.
  • treat —The action that the PGW takes when the SIP header is present.
  • tdw1–4 —Data words that describe how the PGW applies the treatment settings. For values 2–3 in the Treatment field, Treatment DW1 defines the response code used to reject the request. For values 4–6 in the Treatment field, Treatment DW1–4 define the tag the PGW applies. You can apply up to four tags for each row in the SIP header table.

Note For more information about applying inbound SIP headers, see SIP Profiles feature module.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:outsipheader:name=''outsipht1'',header=''Diversion'',message=''INVITE'',cond=1, treat=1,cdw1=''xyf2'',policy=0,index=1
MGC-01 - Media Gateway Controller 2008-03-04 10:51:22.260 EST
M COMPLD
''outsipheader''
;

Comments:

Performance impact category C applies to the commands used to create, delete, and edit outbound SIP header tables.

PERCRTE—Percentage-Based Routing Table

 

Purpose :

Add—Provisions a percentage-based routing table.

Delete—Deletes components or parameters in the percentage-based routing table.

Edit—Edits the percentage-based routing table.

Retrieve—Retrieves either all percentage-based routes or one specific (configured) percentage-based route.

Syntax:

prov-add:percrte: name =” desctwo ”{, rtlistname =” name ”| condrtename =” name ”}[, ovrflwset =” ON ”] [, primary =” ON ”]
prov-dlt:percrte: name =” desctwo
prov-ed:percrte: name =” desctwo ”[, load =” value ”][, rtlistname =” name ”][, condrtename =” name ”] [, ovrflwset =” ON ”][, overflow =” ON ”][, primary =” ON ”]
prov-rtrv:percrte: {” all ”| name =” routename ”}

Input Description:

  • name—Percentage-based routing name. Up to 20 alphanumeric characters.
  • load—Enter a value from 0 to 100 (percentage). Either LOAD or OVERFLOW must be specified.
  • rtlistname—Route list name which was previously configured.

A percentage route can have up to five entries for load, and each load has a rtlistname or a condrtename. You can add more loads (up to five) by using the PROV-ED command.

  • condrtename—Conditional route name (previously configured).
  • ovrflwset—Selects overflow support. Enter ON or OFF; the default is ON.
  • overflow—Overflow entry for the percentage-based routing table.

In a PROV-ED command, this entry specifies the overflow route. Enter OFF or ON; the default is OFF. Either LOAD or OVERFLOW with a value of ON is supported.

  • primary—Primary entry for the percentage-based routing table. Enter ON or OFF; the default is ON.

In a PROV-ADD command, either do not specify this component or set it to ON.

  • all —Specifies all configured percentage-based routes.

Example :

The MML command shown in the following example provisions a percentage-based route:

mml> PROV-ADD:percrte:name=”one”,rtlistname=”one”,ovrflwset=”ON”,primary=”ON”
 

The MML command shown in the following example deletes route list “three” from percentage-based route “two”:

mml> PROV-DLT:percrte:name=”two”,rtlistname=”three”
 

The MML command in the following example deletes the entire percentage-based routing table.

mml> PROV-DLT:percrte:name=”two”
 

The MML commands shown in the following example allocate load among percentage-based routes:

mml> PROV-ED:percrte:name=”one”,rtlistname=”three”,load=25
mml> PROV-ED:percrte:name=”one”,condrtename=”todtwo”,load=25
mml> PROV-ED:percrte:name=”one”,condrtename=”todthree”,overflow=”ON”
 

The following MML command retrieves all the configured percentage-based routes:

mml> PROV-RTRV:percrte:”all”
 

The following MML command retrieves percentage-based route “one”:

mml> PROV-RTRV:percrte:name=”one”

Comments:

Entries in the percentage-based route table are stored in ascending order.

PRICHARGE—PRI Charge Table

 

Purpose:

Add, edit, delete, and retrieve an entry in the PRI Charge table for PRI AOC supplementary services.

Syntax:

prov-add:pricharge:chorig =<1-9999>, chdest =<1-9999>, dow ="< monday-sunday, hol1, hol2, hol3 >", stariffdesc ="< tariff 1 timeChange 1 - tariff n timeChange n >",
dtariffdesc ="< tariff 1 timeChange 1 - tariff n timeChange n >",
etariffdesc ="< tariff 1 timeChange 1 - tariff n timeChange n >"
 
prov-ed:pricharge:chorig =<1-9999>, chdest =<1-9999>, dow ="< monday-sunday, hol1, hol2, hol3 >", stariffdesc ="< tariff 1 timeChange 1 - tariff n timeChange n >",
dtariffdesc ="< tariff 1 timeChange 1 - tariff n timeChange n >",
etariffdesc ="< tariff 1 timeChange 1 - tariff n timeChange n >"
 
prov-dlt:pricharge:chorig =<1-9999>, chdest =<1-9999>, dow ="< monday-sunday, hol1, hol2, hol3 >"
prov-rtrv:pricharge:chorig =<1-9999>, chdest =<1-9999>, dow ="< monday-sunday, hol1, hol2, hol3 >"
prov-rtrv:pricharge: “all”

Input Description:

  • chorig—The charge origin. Indicates the numeric designation for the charge origin of the call. Value range: 1 through 9999.

Note If no value is entered for chorig, then the charge origin is assumed to be 0 for any origin that has the same destination and no other charge origin specified.

  • chdest—The charge destination. Indicates the numeric designation for the charge destination of the call. Value range: 1 through 9999.
  • dow —The day of week. Indicates the day of week for which the charge applies. Value range: Default, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, HOL1, HOL2, or HOL3.

Note If no value is entered for dow, then the charge is assumed to be 0 for any day of the week where no other indication is given.

  • stariffdesc —The AOC-S tariff description. The tariff description indicates to the calling private branch exchange (PBX) or end office of the charge for the call through the network, from the start of the call.
  • dtariffdesc —The AOC-D tariff description. The tariff description indicates to the calling PBX or end office of the charge for the call through the network, during the call.
  • etariffdesc —The AOC-E tariff description. The tariff description indicates to the calling PBX or end office of the charge for the call through the network, at the end of the call.

Note The tariffs to be applied are from the Tariff table with their associated durations. Up to five tariff changes can be specified per day. The format for the time change field is HHMM, where MM must be divisible by 15 (that is, 15-minute increments; for example, 2015). The time change value must be 2400 if the last field is a time change value.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:pricharge:chorig=2,chdest=2,dow="HOL1",stariffdesc="1 1815 3 2100 2"

Comments:

The Charge table entry format for the preceding MML command is:

2 2 8 "1 1815 3 2100 2"

This indicates that the Charge Origin is 2; the Charge Destination is 2; the Day of week is HOL1, Tariff ID 1 is applicable until 1815; Tariff ID 3 is applicable until 2100; and Tariff ID 2 is applicable until the end of the day. A time change does not have to be entered as the last change value, but if it is entered, it must be 2400.

PRITARIFF—PRI Tariff Table

 

Purpose:

Add, edit, delete, and retrieve an entry in the PRI Tariff table for PRI AOC supplementary services.

Syntax:

prov-add:pritariff:tariffid =<range 1-9999>, schargeditem =< AocSChargedItemRange >, dcallstate =< AocDCallStateRange >, ecallstate =< AocECallStateRange >, sca =<1-10>, srecchrg =< AocSRecordedChrgRange >, drecchrg =< AocDRecordedChrgRange >, erecchrg =< AocERecordedChrgRange >, currency =< IA51-10 >, amount =<0-16777215>, amtmult =< AmountMultiplierRange >, timelen =<0-16777215>, timescale =< TimeScaleRange >, granularity =<0-16777215>, granularityscale =< GranularityTimeScaleRange >, vol =< VolumeRange >, scu =<1-32767>, billingid =< BillingIdRange >, chargingunits =<0-16777215>, duration =<0-16777215>, ratetype =<0-1>, initialtariff =< up to 3 tariffs >
 
prov-ed:pritariff:tariffid =<range 1-9999>, schargeditem =< AocSChargedItemRange >, dcallstate =< AocDCallStateRange >, ecallstate =< AocECallStateRange >, sca =<1-10>, srecchrg =< AocSRecordedChrgRange >, drecchrg =< AocDRecordedChrgRange >, erecchrg =< AocERecordedChrgRange >, currency =< IA51-10 >, amount =<0-16777215>, amtmult =< AmountMultiplierRange >, timelen =<0-16777215>, timescale =< TimeScaleRange >, granularity =<0-16777215>, granularityscale =< GranularityTimeScaleRange >, vol =< VolumeRange >, scu =<1-32767>, billingid =< BillingIdRange >, chargingunits =<0-16777215>, duration =<0-16777215>, ratetype =<0-1>, initialtariff =< up to 3 tariffs >
 
prov-dlt:pritariff:tariffid =<range 1-9999>
prov-rtrv:pritariff:tariffid =<range 1-9999>|“all”

Input Description:

  • tariffid —The tariff ID. This is the tariff identifier configured as part of the tariff descriptor. Value range: 1 through 9999.
  • schargeditem —The AOC-S charged item. Indicates the function for which the caller is billed. Value range: 0 through 4. Where 0 = Basic Communication; 1 = Call Attempt; 2 = Call Setup; 3 = User-to-user information; 4 = Operation of Supplemental Services.
  • sca —Special Charging Agreement. Indicates the AOC-S special charging arrangement. Value range: 1 through 10. Where the user defines each value.
  • srecchrg —The AOC-S recorded charge. Indicates the AOC-S charge recording configuration. Value range: 1 through 6. Where 1 = Duration rate; 2 = Flat Rate; 3 = Volume Rate; 4 = Free Of Charge; 5 = Info Not Available; 6 = Special.
  • drecchrg —The AOC-D recorded charge. Indicates the AOC-D charge recording configuration. Values: 1 through 3. Where: 1 = Charging Unit; 2 = Currency Unit, and 3 = Free Of Charge.
  • erecchrg —The AOC-E recorded charge. Indicates the AOC-E charge recording configuration. Values: 1 through 3. Where: 1 = Charging Unit; 2 = Currency Unit, and 3 = Free Of Charge.
  • currency —The currency used for billing. Indicates the currency name used for billing the call. Value range: 1 through 10 alphabetical characters.
  • amount —The amount of currency billed. Indicates the amount of the charge in the selected currency. Value range: 0 through 16777215.
  • amtmult —The amount multiplier. The currency amount multiplier for billing. Value range: 0 through 6. Where: 0 = 0.001; 1 = 0.01; 2 = 0.1; 3 = 1; 4 = 10; 5 = 100; 6 = 1000.
  • timelen —The time length. The time length is the time duration for the call charge. The scale representing this time length is determined by the timescale field. Value range: 0 through 16,777,215.
  • timescale —The time scale. Indicates the time units used for billing the call. Value range: 0 through 6. Where: 0 = 0.01 second; 1 = 0.1 second; 2 = 1 second; 3 = 10 seconds; 4 = 1 minute; 5 = 1 hour; 6 = 24 hours.
  • granularity —The granularity length. Indicates the number of time units (in granularity time scale) for the call duration. Value range: 0 through 16777215.
  • granularityscale —The granularity time scale. Indicates the time scale granularity used to measure the call duration. Value range: 0 through 6. Value range: 0 = 0.01 second; 1 = 0.1 second; 2 = 1 second; 3 = 10 seconds; 4 = 1 minute; 5 = 1 hour; 6 = 24 hours.
  • vol —The volume unit. Indicates the unit used for measuring the call. Where: 0 = Octet; 1 = Segment; 2 = Message.
  • scu —The special charging unit. The special charging unit indicates the charging association. Value range: 0 through 32767.
  • billingid —The ID of the billing type being used. Value range: 0 through 7. Where 0 = Normal; 1 = Reverse; 2 = Credit Card; 3 = Call Forwarding Unconditional; 4 = Call Forwarding Busy; 5 = Call Forwarding No Response; 6 = Call Deflection; 7 = Call Transfer.
  • chargingunits —The charging units. The number of charging units for the defined time length. Value range: 1 through 16777215.
  • duration —The duration. Time period, in milliseconds, this tariff remains in effect. A 0 value indicates an ongoing tariff (the tariff does not expire after a fixed duration). Value range: 0 through 16777215.
  • ratetype —The rate type. The rate type is either a flat rate (0), or a duration-based rate (1).
  • initialtariff —The initial tariff. A list of up to 3 tariffs that are applied before this tariff is applied.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:pritariff:tariffid=99,schargeditem=2,sca=1,srecchrg=2, 4zzzdrecchrg=<1-3>, erecchrg=<1-3>,currency=<IA51-10>,amount=<0-16777215>, amtmult=<0-6>,timelen=<0-16777215>, timescale=<0-6>,granularity=<0-16777215>,granularityscale=<GranularityTimeScaleRange>, vol=<0-2>,scu=<0-32767>,billingid=<0-7>,chargingunits=<0-16777215>,duration=<0-16777215>, ratetype=<0-1>,initialtariff=<up to 3 tariffs>

PROFILE—Profile (Release 9.8(1))

 

Purpose:

Creates a profile.

Syntax:

prov-add:profile:name =“ profile name ”, type =“ PROFILE TYPE ”, variant= variant “, validation =“ ON ”, base =“ existing profile ”, cat =“ Category ”, topologyhidingenabled =“ enablevalue ”, trustlevel =“ level

Input Description:

  • name—Name of the new profile.
  • type— Type of profile you wish to create. The available options are:

GRPROFILE—Trunk group profile

ISUPTMRPROFILE—ISUP signal path profile

SIPPROFILE

EISUPPROFILE

DOMAINPROFILE

COMMONPROFILE

GWPOOLPROFILE

Note SIPPROFILE, EISUPPROFILE, DOMAINPROFILE, COMMONPROFILE, AND GWPOOLPROFILE were added in software Release 9.8(1).

  • Variant —Valid protocol name from the variants.dat file. Variant is needed only for ISUPTMRPROFILE.
  • validation —Indicates if profile property validation is enabled or disabled. Valid values are ON and OFF.

Note Validation can be disabled only for ISUP timer profiles.

  • base —The name of an existing profile used to create the new profile. The properties of the existing profile are copied to the new profile. This parameter was added in software Release 9.8(1).
  • cat —A property category name which is used to filter the provisioning properties. This parameter allows you to apply a command to a subset of provisioning properties. Valid values are:

A&R

Billing

Media

Misc

Number

SIP

Timer

  • topologyhidingenabled— Indicates if topology hiding is enabled. Valid values are:

0 (based on trustLevel value)

1 (disabled)

2 (enabled)

  • trustlevel—Defines the trust level assigned to a profile. Valid values are:

0 (trusted)

1 (nontrusted)

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example provisions ISUP properties T1 and T2 for the Q767_Singapore protocol variant:

mml> prov-add:profile:name="set1",type="ISUPTMRPROFILE", variant="Q767_Singapore",T1="5",T2=”7”
 

The MML command shown in the following example provisions a SIP profile:

mml> prov-add:profile:name=”spf1”, type=”SIPPROFILE”, validation=”ON”, cat=”SIP”, topologyhidingenabled="2", trustlevel="1"
MGC-01 - Media Gateway Controller 2008-03-04 10:47:38.222 EST
M COMPLD
''profile''
;

The MML command shown in the following example provisions a new gateway pool profile:

mml> prov-add:PROFILE:NAME=”VXSM-Profile1”,TYPE=”GWPOOLPROFILE”, VALIDATION=”ON”, Cat=”Profile”,GatewayAnnSupport=”1”, GatewayToneSupport=”1”,GatewayDTMFSupport="1", GatewayCodecSupport=”1”, GatewaySelectionMethod="1"

Comments:

After an ISUPTMRPROFILE is created, it must be attached to a signal path by the PROV-ADD command.

prov-add:sigpathprof:name=”<signal path name>”,isuptmrprofile=”<ISUP signal path profile name>”
 

For the preceding example, the command to attach the profile to the signal path ss7svc1 is:

prov-add:sigpathprof:name=”ss7svc1”,isuptmrprofile=”set1”
 

Use the PROV-RTRV:VARIANTS command for a list of protocol variants (configured for your system), and see the ISUP properties configurable for a specific variant.

The base property is new in Release 9.8(1) and allows you to create a new profile based on an existing profile. To use this property, set the base property to the name of an existing profile. You can set additional properties to override the values copied from the original profile.

The parameters are stored in the data file profiles.dat.

RAPATH—RADIUS Accounting Server Signal Path (Release 9.7(3))

 

Purpose:

Adds a RADIUS accounting server signal path.

Syntax:

prov-add:rapath:name= sigpath , desc= description , extnode= ra-name

Input Description:

  • sigpath —The MML name of the RADIUS accounting server signal path. Enter an alphanumeric value up to 20 characters in length that starts with an alphabetic character.
  • description —An assigned name. It can be as many as 128 alphanumeric characters in length.
  • ra-name —The MML name of a previously defined external node.

Output Description:

  • COMPLD—Provision succeeds
  • DENY— Provision fails

Example:

mml> prov-add:rapath:name=”racluster1”
MGC-01 - Media Gateway Controller 2006-11-22 02:31:57.559 EST
M RTRV
''session=radius-magnolia:rapath''
/*
NAME = racluster1
DESC = Radius accounting server cluster
EXTNODE = ranode1
*/

Comments:

The following rules apply when creating, deleting, or editing of the rapath:

  • Only one rapath is allowed. This check is done at the add operation.
  • The rapath cannot be edited.
  • A racluster type extnode must be added before the rapath can be added. This check is done at the add rapath operation.
  • A raserver must be defined when rapath is defined. This check is done at prov-cpy time.
  • All raservers that are associated with rapath must be deleted before a rapath can be deleted. This check is done at the rapath delete operation.

RASERVER—RADIUS Accounting Server (Release 9.7(3))

 

Purpose:

Adds a RADIUS accounting server.

Syntax:

prov-add:raserver:name = server-name , desc= description , svc= sigpath , ipaddr= local-address , port= local-port , peeraddr= ra-address , peerport= ra-port , [ iproute= iproute ], order= order , key= key ,[ timeout= timeout ],[ retrycount= retrycount ]

Input Description:

  • server-name —Name of the RADIUS server.
  • description —Assigned name. It can be as many as 128 alphanumeric characters in length.
  • sigpath —Name of RAPATH (RADIUS Accounting Server Signal Path). The raserver component supports this command and associates a RADIUS accounting sigpath to this channel.
  • local-address —Local IP address of the Cisco PGW 2200 Softswitch.
  • local-port —Local port number.
  • ra-address —IP address of the RADIUS server, expressed in dot notation.
  • ra-port —Remote port number of the RADIUS server.
  • iproute —MML name of a previously defined IP route. This is an optional parameter.
  • order —Order of the server as primary server. The range is 1 to 99. The order with the lowest value is selected as primary server. PGW does not allow equal order and displays an error to prevent a provision of same order. This check is done when a raserver is added.
  • key —Shared key for encryption used for this server. The length of the key is 1 to 20. Alphanumerics and dashes are allowed. The key must start with a character.
  • timeout —Duration in seconds before the RADIUS packet is retransmitted. Timeout is equal to or greater than 1.This is an optional parameter.
  • retrycount —Number of times that PGW retransmits a packet before giving up. The range is 1 to 10. The default value is 2. This is an optional parameter.

Output Description:

  • COMPLD—Provision succeeds
  • DENY—Provision fails

Example:

mml> prov-add:raserver:name=”raserver1”
MGC-01 - Media Gateway Controller 2006-11-22 02:30:05.403 EST
M RTRV
“session=radius-magnolia:raserver”
/*
NAME = raserver1
DESC = radius accounting server1
SVC = racluster1
IPADDR = IP_Addr2
PORT = 9595
PEERADDR = 10.74.50.171
PEERPORT = 1646
IPROUTE =
ORDER = 1
KEY = Cisco-h323
TIMEOUT = 5
RETRYCOUNT = 2
*/

Comments:

The following rules apply when you are creating, deleting, or editing a RASERVER:

  • The maximum number of RASERVERs is 5.
  • RAPATH must be added before RASERVER can be added. This is checked at the add RASERVER operation.
  • To delete the only RASERVER, you must also delete the RAPATH. This is checked at the prov-cpy or prov-dply time.
  • For you to add or edit the second RASERVER, the PORT must match the port for the first RASERVER. This is checked at the add/edit RASERVER operation.
  • The PGW uses PORT from <local-port> to <local-port + <number of port>>.
  • The Operator must try to prevent PORT conflict from <local-port> to <local-port + <number of port>>
  • IPADDR, PORT, PEERADDR, PEERPOT, ORDER, KEY, TIMEOUT, and RETRYCOUNT are mandatory. IPROUTE is optional.

RTLIST—Route Lists

Purpose :

Provision a route list.

Syntax:

prov-add:rtlist:name= ”route list name“ , rtname= ”route name“ , distrib= ”OFF|ON“
prov-dlt:rtlist:name= ”route list name“ , rtname= ”route name“
prov-ed:rtlist:name= ”route list name“ , rtname= ”route name“ , nextrtname= ”next route name“ , distrib= ”OFF|ON“
prov-rtrv:rtlist:name = ”route list name“
prov-rtrv:rtlist: all

Input Description:

  • Name—Route list name.
  • Rtname—Route name. Name of an existing route.
  • Nextrtname—Next route name. Name of an existing route.
  • Distrib—Sequential distribution. Values are Off (default) for sequential trunk group selection or On for random trunk group selection.

Example :

The MML command shown in the following example provisions a route list:

mml> prov-add:rtlist:name=”rtlist1910“,rtname=”rt1910“,distrib=”OFF“

RTTRNK—Route Trunk

 

Purpose :

Associating a route with a trunk group.

Syntax:

prov-add:rttrnk:name =” name ”, trnkgrpnum =” trunk group number ”, weightedtg =” weighted trunk group
prov-dlt:rttrnk:name =” name ”, trnkgrpnum =” trunk group number
prov-ed:rttrnk:name =” name ”, trnkgrpnum =” trunk group number ”, nexttrkgrp =” next trunk group ”, weightedtg =” weighted trunk group
prov-rtrv:rttrnk:name =” name
prov-rtrv:rttrnk: all

Input Description:

  • Name—Route name.
  • Trnkgrpnum—Trunk group number
  • Nexttrkgrp—Next trunk group.
  • Weightedtg—Weighted trunk group indicator.

Example :

The MML command shown in the following example provisions a route list:

mml> prov-add:rttrnk:name="rt1910",trnkgrpnum=501910
mml> prov-ed:rttrnk:name="route1",trnkgrpnum=2222,weightedtg="ON"

RTTRNKGRP—Route Trunk Group

 

Purpose :

Add—Specifies the percentage of trunks in a routing trunk group that are reserved for incoming calls.

Edit—Edits the routing trunk group.

Syntax:

prov-add:rttrnkgrp: name =” one ”[, type = trunk group type ][, reattempts = number ][, queuing = seconds ] [, cutthrough = number ][, bearercapname =” name ”]
prov-ed:rttrnkgrp: name =” one ”{[, type =” trunk group type ”][, reattempts =” number ”] [, queuing =” seconds ”][, cutthrough =” number ”][, bearercapname =” name ”]}

Input Description:

  • Name—Trunk group number.
  • Type—Trunk group type. Valid values are:

0—General

1—ISUP

3—TUP

4—IP

5—ATM

6—DPNSS

7—PRI

8—BTNUP

9—IP_SIP

10—SIP_IN

  • Reattempts—Number of times to reattempt trunk group selection. Valid values are 0 through 5.
  • Queuing— Time (in seconds) that the call will be queued. Valid values are 0 through 120.
  • Cutthrough—Identifies the point in the call process where the trunk is seized from end point to end. Ranges from 0 to 3. the default is 0.
  • Resincperc—Percentage of bandwidth reserved for incoming calls. Valid values are 0 through 100.
  • bearercapname—Bearer capability name (previously configured).

Example :

The MML command shown in the following example provisions the percentage of trunks in routing trunk group 1000 to 80:

mml> prov-add:rttrnkgrp:name="1000",type="0",reattempts="5",queuing="1",cutthrough="1", resincperc="80"
 

The MML commands shown in the following example provision bearer capability attributes:

mml> PROV-ADD:bearercap:name=”bearer1”,bearercap=”12;05;31”
mml> PROV-ADD:siprttrnkgrp:name=”2222”,url=”128.107.132.143”,svrr=0,sipproxyport=5060, version=”2.0”,cutthrough=1,extsupport=1,bearercapname=”bearer1”
mml> PROV-ADD:rttrnkgrp:name=”1”,type=1,reattempts=3,queuing=0,cutthrough=1, bearercapname=”bearer1”
 

The MML command shown in the following example changes the bearer capability name for the routing trunk group:

mml> PROV-ED:rttrnkgrp:name=”one”,bearercapname=”bearer3”

SESSIONPROP—SS7 Session Property

 

Purpose:

Provisions an SS7 session property component.

Syntax:

prov-add:sessionprop:name=” name ”, rudpNumRetx=” rudpnumretx ”,rudpRetxTimer=” rudpretxtimer ”, rudpwindowsz= value

Input Description:

  • name—Name of the SS7 session; up to 20 alphanumeric characters.
  • rudpnumretx —The maximum number for retransmission count; range: 1-100; Def=2.
  • rudpretxtimer—The retransmission timeout value; range: 2 through 100.
  • rudpwindowsz —The maximum number of unacknowledged segments in the RUDP window. Value range: 2 through 64.

Example:

The MML command shown in the following example creates a session property:

mml> prov-add:sessionprop:name=”sess8-2”, rudpNumRetx=”8”, rudpRetxTimer=”8”, rudpwindowsz=5

Comments:

Performance Impact Category: B

SESSIONSET—Sessionset

Purpose :

Add, delete, or edit a sessionset, a pair of backhaul IP links used by the Cisco PGW 2200 Softswitch to communicate with an external node that supports IPFAS or BSMV0.

Syntax:

prov-add:sessionset: name =” sessionset name “, ipaddr1 =” ipaddress ”, ipaddr2 =” ipaddress ”, port = number , peeraddr1 =” ipaddress ”, peeraddr2 =” ipaddress ”, peerport =” peer ip port ”, extnode =” external node ”, iproute1 =” iproute ”, iproute2 =” iproute ”, type =” external node type
prov-dlt:sessionset : name =” sessionset name
prov-ed:sessionset: name =” sessionset name “, desc =” sessionset description ”, ipaddr1 =” ipaddress ”, ipaddr2 =” ipaddress ”, port = number , peeraddr1 =” ipaddress ”, peeraddr2 =” ipaddress ”,
peerport =” peer ip port ”, iproute1 =” iproute ”, iproute2 =” iproute

Input Description:

  • Name—MML name of a sessionset. This name can be up to 20 alphanumeric characters in length.

Special characters allowed are quotes (" ").

The name must start with an alphabetic character.

  • Desc—Sessionset description. This description can be up to 128 characters in length.
  • IPAddr1—Local logical IP address 1.
  • IPAddr2—Local logical IP address 2.
  • Port—Local port number in the range 1025 to 65535.

Enter a value that is different from that specified for any ASSOCIATION, IPLNK, or SIPLNK command.

Enter a value that is different from that specified for another session set.

  • Peeraddr1—Destination IP address 1. You can also specify a hostname or DNS name. The default is 0.0.0.0.
  • Peeraddr2—Destination IP address 2. You can also specify a hostname or DNS name. The default is 0.0.0.0.
  • Peerport—Destination port number in the range 1025 to 65535.
  • Extnode—MML name of previously configured external node.
  • IProute1—MML name of previously configured IP route. The IPADDR value must match IPADDR1 of the session set.
  • IProute2—MML name of previously configured IP route. The IPADDR value must match IPADDR2 of the session set.
  • Type—External node type for this sessionset.

Enter BSMV0 for C7 session sets.

Enter IPFAS for IPFAS session sets.

Example :

The MML command shown in the following example provisions a sessionset used by the Cisco PGW 2200 Softswitch to communicate:

mml> prov-add:sessionset:name="slt1",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2",port=7000, peeraddr1="10.82.80.188",peeraddr2="10.82.81.165",peerport=7000, extnode="va-2600-165", type="BSMV0",iproute1="iprte1",iproute2="iprte2"
 

The MML command shown in the following example deletes a session set:

mml> prov-dlt:sessionset:name="slt1"
 

The MML command shown in the following example edits a sessionset used by the Cisco PGW 2200 Softswitch to communicate with an external node:

mml> prov-ed:sessionset:name="slt1",ipaddr1="ip_addr1",ipaddr2="ip_addr2", port=7000, peeraddr1="10.82.80.188",peeraddr2="10.82.81.165",peerport=7000,extnode="va-2600-165", type="bsmv0",iproute1="iprte1", iproute2="iprte2"

SGP—SS7 Signaling Gateway Process

 

Purpose:

Add, delete, or edit an SS7 Signaling Gateway Process (SGP).

Syntax:

prov-add:sgp:name =” key name ", desc =" key description ", extnode =" external node "
prov-dlt:sgp:name =” key name "
prov-ed:sgp:name =” key name "<, desc =" key description ">

Input Description:

  • name—Name of the SGP. Enter an alphanumeric string up to 20 characters in length.
  • desc —Description of the SGP. This parameter can be up to 128 characters in length.
  • extnode—MML name of previously configured external node.

Example:

mml> prov-add:sgp:name="sgp1",desc="first sgp",extnode="va-2600-165"
mml> prov-dlt:sgp:name="sgp1"
mml> prov-ed:sgp:name="sgp1",desc="first sgp"

SIGPATHPROF—Signaling Service Profile

 

Purpose:

Provision the signaling service profile.

Syntax:

prov-add:sigpathprof:name =” Name ", isuptmrprofile =" Inbound or Outbound "

Input Description:

  • name— Signaling service name.
  • isuptmrprofile—ISUP timer profile name.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML commands shown in the following example create an ISUP timer profile and attach it to a signaling service:

mml> prov-add:profile:name="mtp3profile1",type="isuptmrprofile",variant="ISUPV2_FRENCH", T1="14000",T12="14000",T13="20000",T14="70000",T15="200000",T16="50000",T17="950000",T18="70000",T19="50000",T2="280000",T20="70000",T21="20000",T22="70000",T23="50000",T24="900",T25="900",T26="50000",T27="200000",T28="9000",T33="16000",T34="1000",T35="10000",T36="16000",T38="120000",T5="50000",T6="70000",T7="40000",T8="25000",T9="50000"
mml> prov-add:sigpathprof:name="ss7svc1",isuptmrprofile="mtp3profile1"

Comments:

ISDN User Part (ISUP) timer profile properties allow property values, listed in “ISUP Timers” section to be overridden for the specified protocol.

When configuring an ISUP timer profile, you can attach a profile to a signaling service, but both the profile and the signaling service must belong to the same variant (see the “Protocol Variants” section for a list of variant names). However, you can create a profile even though the signaling service does not exist.

A profile must be created before a signaling service can be associated with the profile.

SIGSVCPROP—Signaling Service Properties

 

Purpose :

Provision signaling service properties.

Syntax:

prov-add:sigsvcprop:name= " 111 " ,gninclude= gninclude ,od32digitsupport= value ”, SipToIsupRatio =" value ", IsupToSipRatio =" value "
prov-dlt:sigsvcprop:name= name , property name
prov-ed:sigsvcprop:name= name , AllowH323Hairpin ="{0|1}", od32digitsupport =” value ”, CustomerVPNid =" id ”, CallForwardRerouteDisabled =“ int ”, ContactListOrder =” value , SipToIsupRatio =" value ", IsupToSipRatio =" value ", SipRedirAnalysisMethod = value
prov-rtrv:sigsvcprop:name= name

Input Description:

  • Name—Name of an existing signaling service. Enter an alphanumeric string up to 20 characters in length.
  • AllowH323Hairpin—enable or disable H.323 inter working on the H.323 signal path. Valid values are:

0—Disable

1—Enable

  • gninclude —Indicates whether or not to include the generic number in an IAM. Values: 0 or 1. This parameter was added in software Release 9.8(1).

0 does not include the generic number. This is the default.

1 includes the generic number.

  • OD32digitsupport—Enter one of the following:

1 enables overdecadic and 32-digit support. This is the default.

0 disables overdecadic and 32-digit support.

  • CustomerVPNid—A string of 1 to 8 alphanumeric characters. The default value is 00000000. If no value is given, the system responds as if no VPN ID were present.
  • CallForwardRerouteDisabled—Valid property values. Default value is 0.

0 = Call forwarding reroute enabled

1= Call forwarding reroute disabled

  • ContactListOrder —The ContactListOrder defines the order in which the target list is appended, once a new Contact header is received in another 300, 301, 0r 302 response message. Values are:

1—At the beginning of the list. This is the default.

2—At the end of the list.

3—Replace the list with the new list.

  • SipRedirAnalysisMethod —Defines how the PGW handles the SIP redirection target. Values are:

0—Conditional analysis, which performs digit analysis if the host in the 302 response message is the PGW domain; otherwise route the call directly to the 302 address. This is the default.

1—Always perform digit analysis.

2—Never perform digit analysis.

  • SipToIsupRatio —The SIP to ISUP ratio property. Values are:

0—The mapping is disabled.

1 through 4—The mapping ratio value.

  • IsupToSipRatio —The ISUP to SIP ratio property. Values are:

0—The mapping is disabled.

1 through 4—The mapping ratio value.

Example :

The MML command shown in the following example enables H.323 inter working on the EISUP-HSI-1 signal path:

mml> PROV-ED:sigsvcprop:name="EISUP-HSI-1",AllowH323Hairpin="1"
 
The MML commands shown in the following example provision signaling service properties:
mml> prov-add:sigsvcprop:name="111",gninclude=1"
mml> prov-add:sigsvcprop:name=”1000”,od32digitsupport=”1”
mml> prov-dlt:sigsvcprop:name=”1000”,”od32digitsupport”
mml> prov-ed:sigsvcprop:name=”1000”,od32digitsupport=”1”, CustomerVPNid ="AB1GB1Z1”, CallForwardRerouteDisabled ="1"
 

The MML commands shown in the following example sets and retrieves the state of the ContactListOrder:

sh-bamboo mml> prov-ed:sigsvcprop:name="sip-path",contactlistorder="2"
MGC-01 - Media Gateway Controller 2005-11-01 09:56:29.916 EST
M COMPLD
"sigsvcprop"
;
sh-bamboo mml> prov-rtrv:sigsvcprop:name="sip-path"
MGC-01 - Media Gateway Controller 2005-11-01 09:56:42.654 EST
M RTRV
"session=chgcontac:sigsvcprop"
/*
ContactListOrder = 2
*/
 

The MML commands shown in the following example sets and retrieves the state of the SipRedirAnalysisMethod:

sh-bamboo mml> prov-ed:sigsvcprop:name="sip-path",SipRedirAnalysisMethod="2"
MGC-01 - Media Gateway Controller 2005-11-01 09:56:29.916 EST
M COMPLD
"sigsvcprop"
;
sh-bamboo mml> prov-rtrv:sigsvcprop:name="sip-path"
MGC-01 - Media Gateway Controller 2005-11-01 09:56:42.654 EST
M RTRV
"session=chgcontac:sigsvcprop"
/*
SipRedirAnalysisMethod = 2
*/
 

The MML command shown in the following example sets the SIP to ISUP ratio to 1 and the ISUP to SIP ratio 2:

mml> prov-ed:sigsvcprop:name="sip-path",SipToIsupRatio="1",IsupToSipRatio="2"

SIPIVERSION—SIP-I Version and MDO Variant (Release 9.8(1))

 

Purpose:

Add—Adds an entry in the sipIVersion.dat file.

Delete—Deletes an entry within a SIP-I mapping profile in the sipIVersion.dat file.

Edit—Edits an entry within a SIP-I mapping profile in the sipIVersion.dat file.

Retrieve—Displays the information for one entry within a SIP-I mapping profile in the sipIVersion.dat file.

Syntax:

prov-add:sipiversion: profilename =" SIP-I mapping profile name ",
version =" SIP-I version in Content-Type ", mdo =" SIP-I variant name "
prov-dlt:sipiversion: profilename =" SIP-I mapping profile name ",
version =" SIP-I version in Content-Type "
prov-ed:sipiversion: profilename =" SIP-I mapping profile name ",
version =" SIP-I version in Content-Type ", mdo =" SIP-I variant name "
prov-rtrv:sipiversion: profilename =" SIP-I mapping profile name ",
version =" SIP-I version in Content-Type "

Input Description:

  • PROFILENAME —MML name of a SIP-I mapping profile. This name can be up to 20 alphanumeric characters in length.

The name must start with an alphabetic character.

  • VERSION — SIP-I version defined by the operator and used in the SIP-I message Content-Type header field. One SIP-I mapping profile can have more than one SIP-I version defined on the PGW. This parameter value can be up to 128 characters in length.
  • MDO —SIP-I variant name mapped to the SIP-I message ParamContent field. This name can be up to 40 alphanumeric characters.

Example:

The MML command shown in the following example adds a mapping from SIP-I version X-UKISUP to SIP-I variant ISUPV3_UK_SIPI in the SIP-I mapping profile BT:

mml> prov-add:sipiversion:profilename="BT", version="X-UKISUP",mdo="ISUPV3_UK_SIPI"
 

The MML command shown in the following example deletes the mapping for the SIP-I version X-UKISUP in the SIP-I mapping profile BT:

mml> prov-dlt:sipiversion:profilename="BT",version="X-UKISUP"
 

The MML command shown in the following example edits the mapping from SIP-I version “X-UKISUP” to SIP-I variant ISUPV3_UK_SIPI in the SIP-I mapping profile BT:

mml> prov-ed:sipiversion:profilename="BT",version="X-UKISUP", mdo="ISUPV3_UK_SIPI"
 

The MML command shown in the following example displays the information of the entry for SIP-I version X-UKISUP in the SIP-I mapping profile BT:

mml> prov-rtrv:sipiversion:profilename="BT",version="X-UKISUP"

Comments:

Performance Impact Category: A

SIPLNK—SIP IP Link

 

Purpose :

Edits a SIP IP link used by the Cisco PGW 2200 Softswitch to communicate with a SIP proxy server.

Note The PROV-ED:siplnk command is no longer supported as of Release 9.7(3)

Syntax:

prov-ed:siplnk:name=“ sip ip link name ”,desc=” sip ip link description ”,port= number , pri= priority ,IPAddr=” IP address

Input Description:

  • Name—MML name of SIP IP link. Enter up to 20 alphanumeric characters.

Special characters allowed are quotes (“ “).

The name must start with an alphabetic character.

  • Desc—Description of SIP IP link. Enter up to 128 characters.
  • Port—Local port number.

Enter a valid port number up to 1024.

For SIP, enter 5060.

  • Pri—Priority. Enter an integer greater than 0.
  • IPAddr—Local logical IP address.

Example :

The MML command shown in the following example edits a SIP IP link:

mml> prov-ed:siplnk:name=”siplnk-1”,ipaddr=”IP_Addr1”,port=5060,pri=1

SIPPATH—SIP Signaling Service

 

Purpose:

Provision SIP signaling service or signaling path to SIP proxy servers.

Syntax:

prov-add:sippath:name =” Name ", desc =" description ", mdo =" Protocal Variant ",
origlabel =" Origination Location Label ", termlabel =” Termination Location Label
prov-dlt:sippath:name =” Name "
prov-ed:sippath:name =” Name ", desc =" description ", origlabel =" Origination Location Label ", termlabel =” Termination Location Label
prov-rtrv:sippath:name =” Name "
prov-rtrv:sippath: all "

Input Description:

  • name—Unique component name used in MML commands. The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
  • desc—Description. The description can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
  • mdo—MDO file name. Valid protocol name from variants.dat.
  • origlabel—Originating call control (OCC) side location label. Used for Call Limiting feature.
  • termlabel—Terminating call control (TCC) side location label. Used for Call Limiting feature.

Note The parameters, origlabel and termlabel, are added in software Release 9.6(1).

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

mml> prov-add:sippath:name="sip-path",mdo="IETF_SIP",desc="SIP sigpath"

SIPRTTRNKGRP—SIP Routing Trunk

 

Purpose :

Add or edit the SIP routing trunk group.

Syntax:

prov-add:siprttrnkgrp: name =” one ”, url =” ipaddress ”, srvrr = number , sipproxyport = udp port , version =” sip version ”[, cutthrough = number ][, extsupport = sip extension ][, bearercapname =” name ”]
prov-ed:siprttrnkgrp: name =” one ”, url =” ipaddress ”|, srvrr =” srv dns name ”|,
sipproxyport =” udp port ”|, version =” sip version ”|, cutthrough =” number ”|,
extsupport =” sip extension ”|, bearercapname =” name ”}

Input Description:

  • name—SIP Route Trunk Group Name.
  • url—SIP proxy service address in the format of IP address, host name, or DNS name.
  • srvrr—URL is SRV DNS Name. Enter 0 or 1; the default is 0.
  • sipproxyport—Sip Proxy Port.
  • sipver—SIP version of the SIP proxy server.
  • cutthrough—Enter a value in the range 0 to 3; the default is 0.
  • extsupport—Supported SIP extension. Enter 0 or 1; the default is 0.
  • bearercapname—Bearer capability name (previously configured).
  • domainbasedrtgsupport —Support for Domain based routing (non E164).0=False (non-E.164 calls not permitted), 1=True (non-E.164 calls permitted), Default is 0. This parameter was added in software Release 9.8(1).

Note Ensure that the remote trunk matches this configuration.

Example :

The MML commands shown in the following examples provision bearer capability attributes:

mml> PROV-ADD:bearercap:name=”bearer1”,bearercap=”12;05;31”
mml> PROV-ADD:siprttrnkgrp:name=”2222”,url=”128.107.132.143”,svrr=0,sipproxyport=5060, version=”2.0”,cutthrough=1,extsupport=1,bearercapname=”bearer1”
mml> PROV-ADD:rttrnkgrp:name=”1”,type=1,reattempts=3,queuing=0,cutthrough=1, bearercapname=”bearer1”
mml> prov-add:siprttrnkgrp:name="TgName",type=9,sipurl="<sipurl>",portnum=<portnum>, sipver="<sipver>",cutthrough=<cutthrough>,extsupport=<extsupport>,issvr=<issvr>, bearercapindex=<bearercapindex>,domainbasedrtgsupport=<domainbasedrtgsupport>
 

The MML command shown in the following example changes the bearer capability name for the SIP routing trunk group:

mml> PROV-ED:siprttrnkgrp:name=”2222”,bearercapname=”bearer2”

SS7PATH—SS7/M3UA Signaling Service

Purpose :

Provisions an SS7/M3UA signaling service.

  • For SS7 service, set OPC.
  • For M3UA service, set M3UAKEY.

Syntax:

prov-add:ss7path: name =” node name ”, desc =” node description ”, dpc =” destination point code ”, opc =” origination point code ”, mdo =” variant ”, custgrpid =” id ”, side =” call model ”,
m3uakey =” name of key ”, origlabel =" loclbl1 ", termlabel =" loclbl2 "
prov-ed:ss7path: name =” node name ”, desc =” node description ”, opc =” origination point code ”, mdo =” variant ”, custgrpid =” id ”, side =” call model ”, m3uakey =” name of key

Input Description:

  • name—Name of the signaling service. Enter an alphanumeric string up to 20 characters in length.
  • desc—Description of the signaling service. This parameter can be up to 128 characters in length.
  • side—Q.931 call model side.

Enter User for the user side.

Enter Network for the network side (default).

  • MDO—MDO file name. Enter any MDO variant from the SS7 protocol family.
  • DPC—MML name of a previously defined destination point code.
  • custgrpid—Customer group ID. Enter a four-digit ID; the default is 0000.
  • OPC—MML name of a previously defined origination point code.
  • M3uakey—MML name of a previously configured M3UAKEY.
  • origlabel —MML name for a previously configured LOCLABEL.
  • termlabel —MML name for a previously configured LOCLABEL.

Example :

mml> prov-add:ss7path:name=”ss7path1”,desc=”ss7 path”,dpc=”dpc1”,mdo=”ANSI SS7_STANDARD”, custgrpid=”3343”,side=”network”,m3uakey=”key3”
mml> prov-ed:ss7path:name=”ss7path1”,desc=”ss7 path”,opc=”opc1”,mdo=”ANSI SS7_STANDARD”, custgrpid=”3343”,side=”network”,m3uakey=”key3”

SS7ROUTE—SS7 Route

Purpose :

Provisions an SS7 route.

Syntax:

prov-add:ss7route:name=” name ”,desc=” description ”,dpc=” destination point code ”,
opc=”
origination point code ”,lnkset=” link set ”,PRI=” priority

Input Description:

  • name—Unique name for this route. Enter as many as 20 alphanumeric characters and enclose in straight quotes. Hyphens (-) can be used.
  • desc—Text description of this route. Enter as many as 128 characters and enclose in straight quotes.
  • DPC—Destination point code. Enter the MML name of a previously defined destination point code for a remote switch.
  • OPC—Originating point code (must be a true OPC). Enter the MML name of a previously defined originating point code for this MGC node.
  • LNKSET—Linkset that leads to the destination device. Enter the MML name of a previously defined linkset.
  • PRI —SS7 route priority. Enter an integer that is greater than 0. One (1) is the highest priority level. When two SS7 routes share the same priority level, traffic is shared by both routes. Default = 1.

Example :

mml> prov-add:ss7route:name="rte1DPC1",opc="OPC",dpc="DestSW1PC",lnkset="linkset1",pri=1, desc="route 1 to DestSW1 thru STP-A"

SS7SUBSYS—SS7 Subsystem

 

Purpose :

Add, delete, or edit an SS7 subsystem. It is used for specifying mated STPs and for providing LNP support through an SCP.

Syntax:

prov-add:ss7subsys: name =” subsystem name ”, desc =” subsystem description ”, svc =” service ”, proto =” protocol family ”, matedapc =” adjacent point of apc ”, pri = priority , localssn = subsystem , stpscpind = index , transproto =” transport protocol ”,< remotessn = subsystem >
prov-dlt:ss7subsys: name =” subsystem name
prov-ed:ss7subsys: name =” subsystem name ”, desc =” subsystem description ”, proto =” protocol family ”, matedapc =” adjacent point of apc ”, pri = priority , localssn = subsystem ,
transproto =” transport protocol ”,< opc =” origination ”|, suakey =” routing key ”>,< remotessn = subsystem >

Input Description:

  • Name—Name of the SS7 subsystem. Enter an alphanumeric string up to 20 characters in length.
  • Desc—Description of the SS7 subsystem. This parameter can be up to 128 characters in length.
  • SVC—Enter one of the following:

MML name of a previously defined adjacent point code

MML name of a previously defined TCAP/IP service

  • PROTO—Protocol family.

When creating an AIN subsystem, enter either SS7-ANSI or SS7-ITU.

When mating STP pairs, enter one of the following: SS7-ANSI, SS7-China, SS7-ITU, SS7-Japan, or SS7-UK.

  • Matedapc—MML name of a previously defined adjacent point code. This parameter is used only when you are mating STP pairs.
  • Pri—Priority entered as an integer that is greater than 0. The default is 1. This parameter is used only when you are creating AIN subsystems.
  • Localssn—Subsystem number entered as an integer in the range 2 to 254.

For SS7-ANSI, SS7-ETSI, or SS7-ITU, enter any value other than 0.

For mating two STPs, enter 0.

The default is 0.

  • Stpscpind—The STP/SCP index used for IN triggers. Enter an integer greater than 0; the default is 0. This parameter is used only when you are creating AIN subsystems.
  • Transproto—Transport protocol. Enter one of the following:

SCCP (default)

SUA

This parameter is used only when creating AIN subsystems.

  • OPC—MML name of a previously defined origination point code. This parameter is not used if SUAKEY is specified.
  • Suakey—MML name of a previously defined routing key. This is an optional parameter used only for SUA. This parameter is not used if OPC is specified.
  • Remotessn—(Optional) Subsystem number entered as an integer in the range 2 to 254.

For SS7-ANSI, SS7-ETSI, OR SS7-ITU, enter any value other than 0.Default is 0.

Example :

mml> prov-add:ss7subsys:name=”prepaid”,desc=”prepaid rte-ssn 48”,svc=”scp”,proto=”ss7-itu”, stpscpind=2,transproto=”sua”,suakey=”suakey1”,remotessn=48
mml> prov-dlt:ss7subsys:name=”prepaid”
mml> prov-ed:ss7subsys:name=”prepaid”,desc=”prepaid rte-ssn 48”,proto=”ss7-itu”, transproto=”sua”,suakey=”suakey1”,remotessn=48

SUAKEY—SUA Routing Key

 

Purpose :

Add, delete, or edit an SUA routing key.

Syntax:

prov-add:suakey: name =” key name ”, desc =” key description ”, opc =” origination ”, apc =” adjacent point ”, localssn = value , routingcontext = value , networkappearance = value
prov-dlt:suakey: name =” key name
prov-ed:suakey: name =” key name ”, desc =” key description

Input Description:

  • Name—Name of the SUA routing key. Enter an alphanumeric string up to 20 characters in length.
  • Desc—Description of the SUA routing key. This parameter can be up to 128 characters in length.
  • OPC—MML name of a previously defined origination point code.
  • APC—MML name of a previously defined adjacent point code. This is an optional parameter.
  • Localssn—Enter a value in the range 2 to 254.
  • Routingcontext—This value must be a unique integer in the range 0 to 2147483647. Two M3UAKEYs or SUAKEYs cannot have the same routing context value.The default is 0.
  • Networkappearance—This value must be in the range 0 to 32767. The default is 0, which indicates an invalid network appearance. This is an optional parameter.

Example :

mml> prov-add:suakey:name=”key1”,desc=”first key”,opc=”opc7”’apc=”apc77”,localssn=123, routingcontext=7054,networkappearance=80
mml> prov-dlt:suakey:name=”key1”
mml> prov-ed:suakey:name=”key1”,desc=”first key”

SUAROUTE—SUA Route

 

Purpose :

Add—Uses SUA to sends an SS7 message to a particular destination.

Delete—Deletes an SUA route.

Edit—Edits an SUA route.

Syntax:

prov-add:suaroute: name =” route name ”, desc =” route description ”, apc =” destination ”, extnode =” external node ”, opc =” origination ”, remotessn =” ssn of destination
prov-dlt:suaroute: name =” route name
prov-ed:suaroute: name =” route name ”, desc =” route description ”<, apc =” destination ”> <, extnode =” external node ”><, opc =” origination ”><, remotessn =” ssn of destination ”>

Input Description:

  • Name—Name of the SUA route. Enter an alphanumeric string up to 20 characters in length.
  • Desc—Description of the SUA route. This parameter can be up to 128 characters in length.
  • APC—MML name of a previously defined adjacent point code. The APC must have an SS7SUBSYS service with an SUAKEY defined.
  • Extnode—MML name of a previously defined external node.
  • OPC—MML name of a previously defined origination point code.
  • Remotessn—Remote subsystem number of destination. Enter either 0 or a number in the range 2 to 254.

Example :

mml> prov-add:suaroute:name=”route1”,desc=”first”,apc=”apc1”,extnode=”mgx-8260”,opc=”opc1”, remotessn=”7”
mml> prov-dlt:suaroute:name=”route1”
mml> prov-ed:suaroute:name=”route1”,desc=”first”,apc=”apc1”,extnode=”mgx-8260”,opc=”opc1”, remotessn=”7”

SWITCHTRNK—Multiple Switched Trunks

 

Purpose :

Add, delete, edit, or retrieve multiple switched trunks to the Cisco PGW 2200 Softswitch configuration. The trunk (switched bearer channel) component is used for provisioning multiple switched trunks.

Syntax:

prov-add:switchtrnk: name ="1", trnkgrpnum =" 1000 ", span =" ffff ", cic =25, cu =" gw1 ", spansize =6, endpoint =" S0/DS1-1/6@li-5300-3 "
prov-dlt:switchtrnk: name ="1",
prov-ed:switchtrnk: name ="1", trnkgrpnum =" 1000 ", span =" ffff ", cic =25, cu =" gw1 ", spansize =6, endpoint =" S0/DS1-1/6@li-5300-3 "
prov-rtrv:switchtrnk: name="1", trnkgrpnum =" 1000 ", span =" ffff ", cic =25, cu =" gw1 ", spansize =6, endpoint =" S0/DS1-1/6@li-5300-3 "

Input Description:

  • Name—A numeric identifier for the trunk group. Range is from 1–9999.
  • trnkgrpnum —Trunk group number. The integer range is >= 0 and < 65536. This parameter is mandatory for all operations;
  • span —Span ID. Value range: an integer from 1 through 65535 or ffff. (Not required for TDM.)
  • cic —Circuit identifier code. Identifies the trunk time slot or circuit identification code. Value range: an integer from 0 through 65535.
  • cu —Coding unit. Identifies the coding unit MML name that was previously defined for the VISM card (this is the external node created for MGCP or SGCP).
  • spansize —Span size. Indicates the number of trunks per span. Value: 1 through 24 for T1, or 1 through 31 for E1.
  • endpoint —End point. Text description of the trunk end point (typically a VISM card). Enter as many as 128 characters and enclose in straight quotes.

Example :

mml> prov-add:switchtrnk:name="1",trnkgrpnum="1000",span="ffff",cic=25,cu="gw1",spansize=6, endpoint="S0/DS1-1/6@li-5300-3"
mml> prov-dlt:switchtrnk:name="1",
mml> prov-ed:switchtrnk:name="1",trnkgrpnum="1000",span="ffff",cic=25,cu="gw1",spansize=6, endpoint="S0/DS1-1/6@li-5300-3"
mml> prov-rtrv:switchtrnk:name="1",trnkgrpnum="1000",span="ffff",cic=25,cu="gw1",spansize=6, endpoint="S0/DS1-1/6@li-5300-3"

TARIFF—Tariff

 

Purpose:

Provision entries in the Tariff table.

Syntax:

prov-add:tariff:tariffid =” Tariff ID ", tariffrate =" Tariff rate ", scalefactor =” Scale factor
prov-dlt:tariff:tariffid =” Tariff ID "
prov-ed:tariff:tariffid =” Tariff ID ", tariffrate =" Tariff rate ", scalefactor =” Scale factor
prov-rtrv:tariff:tariffid =” Tariff ID "
prov-rtrv:tariff: all "

Input Description:

  • tariffid —Tariff ID. Integer from 1 through 9999.
  • tariffrate —Tariff rate. Integer from 1 through 999999.
  • scalefactor —A multiplication factor that is applied to the tariff rate. Integer; 0, 1, 2, 3, 249, 250, 251, 252, 253, 254, or 255.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example inserts an entry in the Tariff list:

mml> prov-add:tariff:tariffid=1010,tariffrate=1010,scalefactor=3
 

The MML command shown in the following example changes the previous entry from "scalefactor3" to "scalefactor2":

mml> prov-ed:tariff:tariffid=1010,tariffrate=1020,scalefactor=2
 

The MML command shown in the following example deletes the existing entry from the Tariff list:

mml> prov-dlt:tariff:tariffid=1010
 

The MML command shown in the following example retrieves the specified entry from the Tariff list:

mml> prov-rtrv:tariff:tariffid=1010
 

The MML command shown in the following example retrieves all existing entries from the Tariff list:

mml> prov-rtrv:tariff:”all”

Comments:

Performance impact category A applies to the commands used to manage the domain table.

TCPLNK—TCP Link

 

Purpose:

Provision the backhaul TCP link, which represents a static IP route.

Syntax:

prov-add:tcplnk:name =” Name ", desc =” description ", extnode =” External Node Name ",
ipaddr =” Local IP Address ", port =” IP Port ", peeraddr =” Peer Address ",
peerport =” Peer IP Port ", type =" TCP Link Type ", iproute =” IP Route Name
prov-dlt:tcplnk:name =” Name "
prov-ed:tcplnk:name =” Name ", ipaddr =” Local IP Address ", port =” IP Port ",
peeraddr =” Peer Address ", peerport =” Peer IP Port ", iproute =” IP Route Name
prov-rtrv:tcplnk:name =” Name "
prov-rtrv:tcplnk: all "

Input Description:

  • name—Unique component name used in MML commands.
  • desc—Component description.
  • extnode—Name of a previously provisioned Cisco BRI voice gateway.
  • ipaddr—Local IP address. IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.
  • port—Port number. Integer1024 through 65535.
  • peeraddr—Highest priority destination address.
  • peerport—Destination port number. Integer1024 through 65535.
  • type—Identifies the type of signaling service associated with this link. Must be set to BRI.
  • iproute —(Optional) Name of a previously provisioned IP route.

Output Description:

  • COMPLD—Provision succeeds.
  • DENY— Provision fails.

Example:

The MML command shown in the following example deletes a Backhaul TCP link named britcp1:

mml> prov-dlt:tcplnk:NAME="britcp1"

Comments:

The following rules apply when you are creating or editing ISDN BRI signaling services:

  • You must define the TYPE parameter as PRI. If the TYPE parameter is not defined as PRI when the TCPLINK is added/edited, a warning is issued. If the TYPE parameter is not defined as PRI when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.
  • You must define the TCPLINK parameter with the same EXTNODE attribute that its associated BRIPATH has. If the TCPLNK is not defined when the BRIPATH is added/edited, a warning is issued. If the TCPLINK is not defined when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.
  • If the TCPLINK with the same EXTNODE value as the BRIPATH is deleted, a warning message is issued to inform you that the BRIPATH must also be deleted. If the BRIPATH is not deleted when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.
  • Only two combinations of local IP address and port number can be used per Cisco PGW 2200 Softswitch. Once you have identified two unique local IP address and port number combinations, all subsequent Backhaul TCP links must use one of those combinations.

TOS—TOS Value (Release 9.7(3))

 

Purpose:

Add—Sets a global dscp value to signaling traffic.

Delete—Deletes changes and sets the global dscp value of signaling traffic to the default CS3.

Edit—Changes the global dscp value for the signaling traffic.

Retrieve—Retrieves the global dscp value of the signaling traffic.

Syntax:

PROV-ADD:tos:dscp= cs3
prov-dlt:tos:assoc_name | all
prov-ed:tos:dscp= cs3
PROV-RTRV:tos:

Input Description:

  • assoc_name —MML name of a previously configured SCTP association.
  • all —All QoS values

Output Description:

tos—QoS value.

dscp—differential service code point; valid values are:

  • BE
  • CS1
  • CS2
  • CS3
  • CS4
  • AF11
  • AF21
  • AF31
  • AF41

Default value is CS3.

Example:

The MML command shown in the following example adds the default value of CS3 to the signaling traffic:

mml> prov-add:tos:dscp=CS3
 

The MML command shown in the following example deletes the existing dscp value for signaling traffic and sets it back to the default value of CS3:

mml> prov-dlt:tos
 

The MML command shown in the following example changes the value of signaling traffic to AF31:

mml> prov-ed:tos:dscp=AF31
 

The MML command shown in the following example retrieves the dscp value for the signaling traffic:

mml> prov-rtrv:tos:dscp=CS3

Comments:

Performance Impact Category: A

TRNKGRP—Trunk Group

 

Purpose:

Add, delete, or edit a trunk group to the Cisco PGW 2200 Softswitch configuration.

Syntax:

prov-add:trnkgrp:name= " trunk group number ", clli= " clli ", svc= " signalling serviece ", type= " trunk group type ", selseq= " selection sequence ", qable= " queuable ", origlabel= origination location label ”, termlabel= termination location label
prov-dlt:trnkgrp:name= "trunk group number"
prov-ed:trnkgrp:name= " trunk group number ", clli= " clli ", svc= " signalling serviece ", type= " trunk group type ", selseq= " selection sequence ", qable= " queuable ", origlabel= origination location label ”, termlabel= termination location label

Input Description:

  • name —A numeric identifier for the trunk group. An integer from 1 through 9999.
  • clli —Common language location identifier that identifies the trunk group. This can be up to 11 alphanumerical digits.
  • svc —The MML name of the signaling service associated with or controlling the trunk group.
  • type —Identifies the trunk group type. Values:

TDM_GEN—Used with SS7 signaling services with switch types not equal to 0, 5, 20, 23, or 40.

TDM_ISUP—Used with SS7 signaling services with switch types of 0, 20, 23, or 40.

TDM_CAS—Currently not supported.

TDM_TUP—Used with SS7 signaling services with switch type of 5.

IP—Used with EISUP signaling service.

ATM—Used with VSI path signaling service.

TDM_DPNSS—Used with DPNSS protocol family signaling services

TDM_ PRI—Used with ISDN PRI protocol family signaling services.

TDM_BTNUP—Used with SS7 signaling services with switch type of 5.

IP_SIP—Used for SIP signaling services at the terminating side.

SIP_IN—Used for SIP signaling services at the originating side (only one such trunk group can be configured on each MGC node).

CTI—Used with CTI signaling services.

Switch type values are:

0 = No switch-specific logic for the signaling path.

5 = BTNUP

10 = SS7 Japan

17 = 5ESS

20 = SS7 Clear

22 = NI2

23 = SS7 ANSI

26 = DPNSS

27 = NET5

29 = QSIG MASTER

30 = QSIG SLAVE

40 = SS7 ITU

  • selseq —Specifies the trunk selection sequence. The Cisco PGW 2200 Softswitch uses the CICs within a trunk group according to the sequence specified by the SELSEQ value. You can provision this value to reduce the chance of glare when the system selects a trunk.

ASC = Ascending. The system selects the available CICs in ascending order starting from the lowest CIC number (for example, 1, 2, 3 ...).

 

CASC = Cyclic ascending. The system selects the next available CIC in ascending order based on the most recently selected CIC. For example, if the most recently selected CIC is CIC 5, the system selects CIC 6, even if CIC 1 is available.

CDESC = Cyclic descending. Similar to CASC, but in descending order based on the most recently selected CIC. For example, if the last selected CIC is number 18, the system selects CIC 17, even if CIC 31 is available.

DESC = Descending. Similar to ASC, but in descending order starting from the highest CIC number (for example, 31, 30, 29 ...).

EASC = Even ascending, then odd ascending. The system selects the first available even CIC in ascending order (for example, 2, 4, 6 ...). If no even CIC is available in the trunk group, the system selects the first available odd CIC in ascending order (for example, 1, 3, 5 ...).

EDECS = Even descending, then odd descending. Similar to EASC, but in descending order. The system selects the first available even CIC in descending order (for example, 30, 28, 26 ...). If no even CIC is available in the trunk group, the system selects the first available odd CIC in descending order (for example, 31, 29, 27 ...).

ITU2 = ITU method 2. The system selects the trunk according to the procedure in ITU-T Recommendation Q.764, paragraph 2.9.1.3 Method 2.

LIDL = Least idle (default). The system selects the least idle (most recently used) CIC.

MIDL = Most idle. The system selects the most idle (least recently used) CIC.

OASC = Odd ascending, then even ascending. The system selects the first available odd CIC in ascending order (for example, 1, 3, 5 ...). If no odd CIC is available in the trunk group, the system selects the first available even CIC in ascending order (for example, 2, 4, 6...).

ODESC = Odd descending, then even descending. Similar to OASC, but in descending order. The system selects the first available odd CIC in descending order (for example, 31, 29, 27 ...). If no odd CIC is available in the trunk group, the system selects the first available even CIC in descending order (for example, 30, 28, 26 ...).

RDM = Random. The system selects a CIC at random.

Note When the trunk selection sequence (SELSEQ) is set to its default value, LIDL (least idle), there is a risk that the Cisco PGW 2200 Softswitch will select a significant number of temporarily unavailable trunks, which causes calls to fail. This kind of call failure can happen when an overloaded media gateway responds to the Cisco PGW 2200 Softswitch with a temporary MGCP error (400 to 499), or the Cisco PGW 2200 Softswitch does not receive a response from the media gateway in time. We recommend that you set SELSEQ to a value other than LIDL.

  • qable —Determines if queuing is used on the trunk during call processing. Value range: Y for yes or N for no (default).
  • origlabel —Defines the originating label for the trunk group.
  • termlabel —Defines the terminating label for the trunk group.

Example:

To add a trunk group to the Cisco PGW 2200 Softswitch configuration, use the PROV-ADD command as follows:

mml> prov-add:trnkgrp:name="1000",clli="tttt-ss-xxx",svc="ss7svc1",type="tdm_gen", selseq="lidl",qable="n"
 

The MML command shown in the following example deletes the specified trunk group:

mml> prov-dlt:trnkgrpprof:name="1000"
 

To modify a trunk group, use the PROV-ED command as follows:

mml> prov-ed:trnkgrp:name="1000",clli="tttt-ss-xxx",svc="ss7svc1",type="tdm_gen", selseq="lidl",qable="n"

TRNKGRPPROF—Trunk Group Profile

 

Purpose:

Attaches a trunk group profile to a trunk group.

Syntax:

prov-add:trnkgrpprof:name= " trunk group number ", grprofile= " GR profile name " (For Release 9.7(3))
prov-add:trnkgrpprof:name= " trunk group number ", profile= " trunk group profile name " (For Release 9.8(1))

Input Description:

  • name —Name of an existing trunk group.
  • grprofile —Name of an existing GR profile.
  • profile —Name of an existing trunk group profile.

Note A profile must be created before a trunk group can be associated with the profile.

Example:

The MML command shown in the following example attaches the trunk group profile “profile1“ to the trunk group “1000“:

mml> prov-add:trnkgrpprof:name="1000",grprofile="profile1"
 

The MML command shown in the following example attaches the trunk group profile “spf1“ to the trunk group “1“:

mml> prov-add:trnkgrpprof:name="1",profile="spf1"

TRNKGRPPROP—Trunk Group Properties

 

Purpose :

Provisions trunk group properties.

Syntax:

prov-add:trnkgrpprop:name=” name ”,AOCInvokeType=” value “,AOCDefaultTariffId=” value “, custgrpid=” <customer group ID> “,npa=” <trunkgroup npa> “,cotpercentage=” [0-255] “, ringnoanswer=” value “, Ta1TimePeriod=” value “,Ta2TimePeriod=” value “,Ta3TimePeriod=” value “, ExpiryWarnToneType=” value “, ExpiryWarnToneDur=” value ”, SubscribeNotifySupport= subvalue , UnsolicitedNotifyMethod= unsolvalue , MinEventSubscribeDuration= minvalue , MaxSubscriptionDuration= maxvalue ,sipMimebodySupport= value , gtdcaptypeprop=” string ”, GtdMsgFmt=” format ”,IsupTransEarlyBackwardDisabled= value , od32digitsupport=” value ”, populateSDPInfoInCDR= value ,InSessionTimer= value , OutSessionTimer= value ,defaultpn=” value ”, defaultpnnoa=” value ”,defaultpnnpi=” value ”, defaultpnpres=” value ”,enableipscreening=” value ”, sipipsource=” value ”,GtdCapTypeProp=” string ”,IsupTransparencyDisabled= value ,
CustomerVPNid =" id ",CustomerVPNOnNetTblNum=" int ",CustomerVPNOffNetTblNum =" int ", FeatureTransparencyDisabled=“ int ”, CallForwardRerouteDisabled =" int ",adigitccrm =“adigitccrm”, DtmfCap =” DtmfCap ”, GWDefaultCodecString=" GWDefaultCodecString "
 
prov-ed:trnkgrpprop:name=” name ”,AOCInvokeType=” value “,AOCDefaultTariffId=” value “, custgrpid=” <customer group ID> “,npa=” <trunkgroup npa> “,cotpercentage=” [0-255] “, ringnoanswer=” value “, Ta1TimePeriod=” value “,Ta2TimePeriod=” value “,Ta3TimePeriod=” value “, ExpiryWarnToneType=” value “, ExpiryWarnToneDur=” value ”, SubscribeNotifySupport= subvalue , UnsolicitedNotifyMethod= unsolvalue , MinEventSubscribeDuration= minvalue , MaxSubscriptionDuration= maxvalue ,sipMimebodySupport= value , gtdcaptypeprop=” string ”, GtdMsgFmt=” format ”,IsupTransEarlyBackwardDisabled= value , od32digitsupport=” value ”, populateSDPInfoInCDR= value ,InSessionTimer= value , OutSessionTimer= value ,defaultpn=” value ”, defaultpnnoa=” value ”,defaultpnnpi=” value ”, defaultpnpres=” value ”,enableipscreening=” value ”, sipipsource=” value ”,GtdCapTypeProp=” string ”,IsupTransparencyDisabled= value ,
CustomerVPNid =" id ",CustomerVPNOnNetTblNum=" int ",CustomerVPNOffNetTblNum =" int ", FeatureTransparencyDisabled=“ int ”, CallForwardRerouteDisabled =" int ",adigitccrm =“adigitccrm”, DtmfCap =” DtmfCap ”, GWDefaultCodecString=" GWDefaultCodecString "
 
prov-dlt:trnkgrpprop:name=” name ”,” property name 1 ”[,” property name 2 ”],...[,” property name n ”]
prov-rtrv:trnkgrpprop:name=” name

Input Description:

  • Name—Name of an existing trunk group. Enter an alphanumeric string up to 20 characters in length.
  • AOCInvokeType —Allows configuration of whether or not the AOC Supplementary services are applicable on a per call basis or for all calls. Values: 1 (on a per call basis the default) or 2 (for all calls).
  • AOCDefaultTariffId —Allows configuration of the default tariff ID to be applied when AOCInvokeType is configured for all calls (that is, AOCInvokeType = 2). Value range: 1 (default) through 9999.
  • Custgrpid—Customer group ID.
  • NPA—Numbering plan area associated with the trunk group.
  • Cotpercentage—Continuity test percentage. Valid value is between 0 and 100.
  • ringNoanswer—Indicates the time, in seconds, ringing is allowed to occur. Valid value is an integer between 0 and 255 seconds.
  • Ta1TimePeriod—Period of time before credit expiration that the SCP is notified. Valid values are between 1 and 180 seconds.
  • Ta2TimePeriod—Period of time before credit expiration that a warning tone/announcement is played. Valid values are between 1 and 180 seconds.
  • Ta3TimePeriod— Period of time before credit expiration that the SSF waits for an SCP response. Valid values are between 1 and 180 seconds.
  • ExpiryWarnToneType— String value of the expiration warning tone. Valid values are any MGCP event names.
  • ExpiryWarnToneDur—Duration of the expiration warning. Valid values are between 1 and 5 seconds.
  • Subscribenotifysupport—Enter one of the following:

0 disables the subscribe/notify method (default).

1 enables the subscribe/notify method.

  • Unsolicitednotifymethod—Enter one of the following:

0 disables the unsolicited notify method (default).

1 enables the unsolicited notify method.

  • Mineventsubscribeduration—Enter an integer within the range 40 milliseconds (default) to 3600 milliseconds.
  • Maxsubscriptionduration—Enter an integer within the range 0 milliseconds (default) to 3600 milliseconds.
  • Sipmimebodysupport—Specifies the type of data processing required. Enter one of the following:

0—None (default).

1—SIP-T supported. All trunk groups on the SIP-T call must have this value selected.

2—SIP-GTD supported. All trunk groups on the SIP-GTD call must have this value selected.

3—Only SIP-I supported on the incoming trunk group, SIP and SIP-I supported on the outgoing trunk group.

4—SIP and SIP-I supported on both the incoming and outgoing trunk groups.

  • Gtdcaptypeprop—Points to a subset of GTD parameters.

t0—No GTD parameter string.

Any other string points to an entry in the gtdParam.dat file.

  • Gtdmsgfmt—Specifies the GTD message format mode. Enter one of the following:

c—Compact mode (default).

v—Verbose mode.

Input Description:

  • Isuptransparency disabl e—Enables disabling of the ISUP transparency feature for a particular trunk group. Enter one of the following:

1—True; ISUP transparency feature is disabled (default).

0—False; ISUP transparency feature is enabled.

  • Isuptransearlybackwarddisabled—Specifies whether the egress Cisco PGW 2200 Softswitch is to send an early backward message immediately after receiving the call setup message with GTD information about the outgoing protocol variant. Enter one of the following:

0—Enable (default)

1—Disable

  • OD32digitsupport—Enter one of the following:

1 enables overdecadic and 32-digit support. This is the default.

0 disables overdecadic and 32-digit support.

  • Populatesdpinfoincdr —Enables or disables the extraction of SDP information from SDP. Extracted SDP information is placed in call detail records (CDRs). Enter one of the following:

0—Disable SDP information extraction (default).

1—Enable SDP information extraction.

  • InSessionTimer—Specifies the maximum session time (in milliseconds) allowed for a SIP call originated by the Cisco PGW 2200 Softswitch. This value affects performance. Enter any value greater than 0. The default is 1800000 milliseconds.
  • OutSessionTimer—Specifies the maximum session time (in milliseconds) allowed for a SIP call terminated by the Cisco PGW 2200 Softswitch. This value affects performance. Enter any value greater than 0. The default is 1800000 milliseconds.
  • Defaultpn—Specifies a default presentation number for the incoming trunk group. Enter an overdecadic digit string consisting of 1 through 20 digits.

If this property is not specified, the default is NULL.

 

  • Defaultpnnoa—Specifies the default presentation number NOA value. The default is 0. Enter one of the following:

1—NOA_NONE

2—NOA_UNKNOWN

3—NOA_SUBSCRIBER

4—NOA_NATIONAL

5—NOA_INTERNATIONAL

6—NOA_NETWORK

7—NOA_MERIDIAN

8—NOA_ABBR

9—NOA_UNIQUE_3DIG_NAT_NUM

10—NOA_ANI

11—NOA_NO_ANI_RECD

12—NOA_NON_UNIQUE_SUBSCRIBER

13—NOA_NON_UNIQUE_NATIONAL

14—NOA_NON_UNIQUE_INTERNATIONAL

15—NOA_OPRREQ_TREATED

16—NOA_OPRREQ_SUBSCRIBER

17—NOA_OPRREQ_NATIONAL

18—NOA_OPRREQ_INTERNATIONAL

19—NOA_OPRREQ_NO_NUM

20—NOA_CARRIER_NO_NUM

21—NOA_950_CALL

22—NOA_TEST_LINE_CODE

23—NOA_INT_INBOUND

24—NOA_NAT_OR_INTL_CARRIER_ACC_CODE_INC

25—NOA_CELL_GLOBAL_ID_GSM

26—NOA_CELL_GLOBAL_ID_NMT_900

27—NOA_CELL_GLOBAL_ID_NMT_450

28—NOA_CELL_GLOBAL_ID_AUTONET

29—NOA_PORTED_NUMBER

30—NOA_PISN_SPECIFIC_NUMBER

31—NOA_UK_SPECIFIC_NUMBER

32—NOA_SPARE

33—NOA_MCI_VNET

34—NOA_INTERNATIONAL_OPR_TO_OPR_OUTSIDE_WZI

35—NOA_INTERNATIONAL_OPR_TO_OPR_INSIDE_WZI

 

 

36—NOA_DIRECT_TERMINATION_OVERFLOW

37—NOA_ISN_EXTENDED_INTERNATIONAL_TERMINATION

38—NOA_TRANSFER_ISN_TO_ISN

39—NOA_CREDIT_CARD

40—NOA_DEFINED_IN_SSUTR

41—NOA_DEFINED_IN_SSUTR2

42—RESERVED

43—NOA_DISCARDED

  • Defaultpnnpi—Specifies the default presentation number NPI value. The default is 0. Enter one of the following:

0—Not used

1—NPI_NONE

2—NPI_E164

3—NPI_DATA

4—NPI_TELEX

5—NPI_PNP

6—NPI_NATIONAL

7—NPI_TELEPHONY

8—NPI_MARITIME_MOBILE

9—NPI_LAND_MOBILE

10—NPI_ISDN_MOBILE

  • Defaultpnpres—Specifies the default presentation number value. The default is 0. Enter one of the following:

0—Not used

1—PRES_NO_INDICATION

2—PRES_ALLOWED

3—PRES_RESTRICT

4—PRES_UNAVAIL

  • Enableipscreening—Instructs the incoming trunk group to select dial plan based on IP address, source ID, and CLI prefix tables. The default is 0. Enter one of the following:

0—No dial plan lookup

1—Requires dial plan lookup

  • Sipipsource—Instructs MDL to use IP packet source address or IP address from SDP in INVITE message to select the dial plan for SIP calls.

0—IP packet source address

1—IP address from SDP

 

  • id—A string of 1–8 alphanumeric characters. The default value is 00000000. An absence of property is treated as if no VPN ID were present.
  • int—Valid property values are 0–8. The default value is 0. Absence of property is treated as if no VPN on-net table number were present.

1—Dictates that completely transparent operation is required or the call does not complete.

2—Sets to feature transparency preferred by a nontransparent destination. Can be used if necessary to complete the call.

3—Sets to feature transparency preferred by a nontransparent destination. Can be used if necessary to complete the call.

4—Sets to feature transparency preferred by a nontransparent destination. Can be used if necessary to complete the call.

5—Sets to indicate that the attempted feature is removed from the onward routed call, and the indicator is informed of this.

6—Sets to release a feature call.

7—Sets to release a feature call.

8—Sets to remove the feature string and continue.

  • int—Valid property values. Default value is 0.

0 = Feature Transparency enabled

1= Feature Transparency disabled

  • adigitccrm —The matching digits to remove from the A-number. This parameter was added in software Release 9.7(3).
  • DtmfCap-Sets the DTMF capability of the specified egress trunk group. This parameter was added in software Release 9.7(3). Valid values are:

0—Ignore DTMF capability

1—RFC 2833 DTMF capability

2—Out of band DTMF capability

  • GWDefaultCodecString —Enables the IOCC-MGCP or IOCC-H248 to send the ordered series of codec choices separated by semicolons. Values are: NULL, G.711u, G.711a, G.726-32, G.726-24, G.726-16, G.729, G.729a, G.729b, G.729b-L, G.723.1-H, G.723.1-L, G.723.1a-L, G.GSM-F, G.GSM-H, or G.GSM-eF. String length 1 to 140. This parameter was added in software Release 9.7(3).

Example :

The MML command shown in the following example provisions INAP properties:

mml> prov-add:trnkgrpprop:name="1000",custgrpid="V123",npa="703", cotpercentage="10", ringnoanswer="200",Ta1TimePeriod="40",Ta2TimePeriod="50", Ta3TimePeriod="5",ExpiryWarnToneType="TEST",ExpiryWarnToneDur="3"
 
The MML command shown in the following example provisions the trunk group properties:
mml> prov-add:trnkgrpprop:name=”3333”,SubscribeNotifySupport=1, UnsolicitedNotifyMethod=1, MinEventSubscribeDuration=200,MaxSubscriptionDuration=3600, custgrpid=”1111”, sipmimebodysupport=1,gtdcaptypeprop=”t3”,gtdmsgfmt=”c”,isuptransearlybackwarddisabled=0, od32digitsupport=”1”, CustomerVPNid ="ABIGBIZ1", CustomerVPNOnNetTblNum ="2", CustomerVPNOffNetTblNum ="5",FeatureTransparencyDisabled =”2”, CallForwardRerouteDisabled ="1"
 

The MML command shown in the following example retrieves the state of trunk group properties for a specific trunk group.

mml> prov-rtrv: trnkgrpprop :name=”8000”
MGC-01 - Media Gateway Controller 2005-09-22 11:22:27.176 EDT
M RTRV
''session=adigitccrm1:trnkgrpprop''
/*
ACCRespCatName = default
ACCRespCntlInhibit = 0
ACLDur = 5
ADigitCCPrefix = 0
ADigitCCrm = 12345
AInternationalPrefix = NULL
...
...
...

The MML command shown in the following example sets the specified egress trunk group DTMF capability:

mml> prov-add:trnkgrpprop:name="1111",DtmfCap="1"
 

The MML command shown in the following example provisions CODEC G.723 on a trunk group:

mml> prov-add:trnkgrpprop:name="1100",custgrpid="1111", GWDefaultCodecString="G723"