|
|
This chapter describes how to add system components, describes how to verify the addition of the components, and gives tips that can help you solve problems. It provides information about:
Before starting an actual configuration, please refer to "Planning for Provisioning" for instructions and worksheets for configuring your system.
"Planning for Provisioning" describes the system components that need to be configured on the MGC. Each component has a specified type, name, and description, and may have additional configuration parameters.
Your first task is to configure SS7 signaling routes that link the MGC to the SS7 network nodes (signaling points). You typically do this by:
To add a system component, do the following:
Step 2 Start a provisioning session as described in the"Starting a Provisioning Session" section. The source configuration that you chose during startup determines the configuration to which you can add components.
Step 3 Enter the following command:
prov-add:componentType:name="name", desc="description", paramName=value
Replace the componentType parameter with the type of component you want to create. To define more than one parameter, enter the additional paramName=value descriptions on the command line.
Provide a description. The description can be as many as 128 alphanumeric characters in length.
Replace the name parameter with the name you want to give to the component. The name can be as many as 10 characters (or 20 characters for Release 7.4) long and can only be number and letter symbols, and the dash (-) symbol.
When adding SS7 system components, there is an order in which components should be created. Certain components must be created before other components. As an example before you add a point code, you must define the external nodes.
A point code is an SS7 network address that identifies an SS7 network node, such as a switch, SCP, STP, or SSP. Its MML name is PTCODE. This can be the MGC's originating point code (OPC), or the destination point code (DPC) of a remote node with which the MGC communicates.
For information on point code parameters, refer to Table 2-1.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:ptcode:name="OPC",netaddr="214.1 10.80", netind=2,desc="Own Pointcode" |
|
| mml>prov-add:ptcode:name="dpc1",netaddr="214. 110.90", netind=2,desc="Dest Switch 1" |
|
Use the PROV-RTRV command to verify.
 |
Tips Point codes provide the addressing scheme for the SS7 network. ITU point codes are 14 bits long, and ANSI point codes are 24 bits long. |
An adjacent point code (APC) defines an SS7 STP through the MGC that it connects to. The APC is the SS7 network address of the STP. Its MML name is APC.
For information on point code parameters, refer to Table 2-1.
Command | Purpose |
|---|---|
mml>prov-add:apc:name="STP-A",netaddr="214.11 1.0",desc="STP A pointcode",netind=2 |
|
Use the PROV-RTRV command to verify.
A linkset is the group of all signaling links between two point codes. Its MML name is LNKSET.
For information on linkset parameters, refer to Table 2-4.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:lnkset:name="linkset1",desc="lin kset 1 to STP-A",apc="STP-A",type="IP", proto="SS7-ANSI" |
|
| mml>prov-add:lnkset:name="linkset2",desc="lin kset 2 to STP-B",apc="STP-B",type="IP", proto="SS7-ANSI" |
|
Use the PROV-RTRV command to verify.
|
Tips Setting up linksets is a two-step process that consists of first adding the linkset and then adding links to the linkset. |
The SS7 subsystem is a logical entity that mates two STPs. When two STPs are defined as mates within the MGC, the controller can use either STP for communications to a destination device. Its MML name is SS7SUBSYS.
For information on SS7 subsystem parameters, refer to Table 2-7.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:ss7subsys:name="mate1",svc="STP- A",matedapc="STP-B",proto="SS7-ANSI",pri=1,de sc="mate STP-A to STP-B" |
|
| mml>prov-add:ss7subsys:name="mate2",apc="STP- B",matedapc="STP-A",proto="SS7-ANSI",pri=2,de sc="mate STP-B to STP-A" |
|
Use the PROV-RTRV command to verify.
|
Tips Protocol families must be the same for mated subsystems. If one pair of STPs handles both ITU and ANSI variants, you must configure two pairs of STPs: one for ITU and the other for ANSI. |
You can also use the SS7 subsystem to define an SCP using TCAP. For TCAP applications, TRANSPROTO is set to TCPIP and the subsystem number is set to a a value greater than 0 to support AIN. You also must set STPSCPIND to route to the appropriate SCP. For information on SS7 subsystem parameters including STPSCPIND, refer to Table 2-7.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:ss7subsys:name="LNP-1",svc="stpa ",transproto="SCCP",proto="SS7-ANSI",pri=1,ss n=231,desc="LNP231 for STP A" |
|
| mml>prov-add:ss7subsys:name="AIN-1",svc="stpb ",transproto="SCCP",proto="SS7-ANSI",pri=1,ss n=241,desc="AIN8xx for STP B" |
|
Use the PROV-RTRV command to verify.
An SS7 route is a path from the MGC to another MGC or SSP switch. Its MML name is SS7ROUTE.
For information on SS7 route parameters, refer to Table 2-9.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:ss7route:name="rte1DPC1",opc="OP C", dpc="DestSW1PC", lnkset="linkset1", pri=1,desc= "route 1 to DestSW1 thru STP-A" |
|
| mml>prov-add:ss7route:name="rte2DPC1",opc="OP C", dpc="DestSW1PC", lnkset="linkset2", pri=1,desc= "route 2 to DestSW1 thru STP-B" |
|
Use the PROV-RTRV command to verify.
|
Tips You must create a route for each DPC-OPC combination. |
An SS7 signaling service specifies the protocol variant and the path that the MGC uses to communicate with a remote switch (SSP) sending bearer traffic to the MGWs. Its MML name is SS7PATH.
For information on signaling service parameters, refer to Table 2-11.
Command | Purpose |
|---|---|
mml>prov-add:ss7path:name="ss7svc1",mdo="ANSI SS7_STANDARD",dpc="dpc1",desc="SS7 svc to dpc1" |
|
Use the PROV-RTRV command to verify.
|
Tips Do not change the default values for CUSTGRPID and CUSTGRTBL; they are used for DPNSS feature transparency. |
CUSTGRPID also associates variants and dial plans. Use rtrv-variants to see valid variants.
This is the TCAP over IP signaling service path to an STP/SCP. Its MML name is TCAPIPPATH.
For information on signaling service parameters, refer to Table 2-27.
Command | Purpose |
|---|---|
mml>prov-add:TCAPIPPATH:name="tcapipsrv1",ext node="scp2",desc="TCAPIP Service to SCP 2" |
|
Use the PROV-RTRV command to verify.
|
Tips When defining a new ITU service for SCCP/TCAP, you must first enter a "dummy" DPC. This DPC is not used for routing calls, but is used internally by the software. |
To define a dummy DPC, refer to the ""Adding a Point Code" section and add a DPC with the following parameters:
You will also select this dummy DPC when provisioning the SS7 route for the ITU service. Refer to the "Adding an SS7 Route" section.
This is the FAS (facility associated signaling) service or signaling path to a particular destination using either ISDN-PRI or DPNSS. Its MML name is FASPATH.
For information on signaling service parameters, refer to Table 2-27.
Step | Command | Purpose |
|---|---|---|
| mml>PROV-ADD:FASPATH:NAME="FASPATH1",SIDE="ne twork",MDO="ETSI_300_102",ASPPART="N",DESC="F ASPATH 1",ABFLAG="a",CRLEN=1 |
|
Use the PROV-RTRV command to verify.
After configuring the SS7 signaling routes, you need to configure the signaling link components. These components link the MGC, to the STPs, and to the MGWs. You will typically do this by:
This is a network card or adapter that is operating in the MGC. Its MML name is CARD.
For information on card parameters, refer to Table 2-15.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:card:name="Ethernet1",type="EN", slot=0, desc="Ethernet Card 1". |
|
| mml>prov-add:card:name="Ethernet2",type="EN", slot=1, desc="Ethernet Card 2" |
DESCRIPTION: Ethernet Card 2 |
Use the PROV-RTRV command to verify.
|
Tips You must configure the adapter card before you configure its corresponding interface. |
The Ethernet interface provides the physical line interface between a MGC Ethernet network card/adapter and the physical Ethernet network. You configure parameters that control communications between the network card/adapter and the Ethernet. Its MML name is ENETIF.
For information on Ethernet interface parameters, refer to the Table 2-17.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:enetif:name="EtherIF1", desc="Ethernet IF 1",card="Ethernet1" |
|
| mml>prov-add:enetif:name="EtherIF2", desc="Ethernet IF 2",card="Ethernet2" |
|
Use the PROV-RTRV command to verify.
|
Tips You must configure the adapter/card before configuring the interface. |
A C7 IP link component identifies a link between a Cisco SLT IP address and port and the SS7 network (SSP or STP). Its MML name is C7IPLNK.
For information on C7 IP link parameters, refer to Table 2-21.
Command | Purpose |
|---|---|
mml>prov-add:c7iplnk:name="lkset1SLC0",if="Et herIF1", ipaddr="IP_Addr1",port=7000, peeraddr="10.15.4.23", peerport=32767,pri=1,slc=0, lnkset="linkset1",desc= "linkset1 SLC 0 thru SLT-23 ser0/0",timeslot=0 |
|
Use the PROV-RTRV command to verify.
|
Tips Use this component only when the MGC uses Cisco SLTs to communicate SS7 messages over IP. |
The peerport must be set to 32767. The peerport value is contained in the XECfgParm field stPort. For more information, refer to the Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide.
The TDM interface provides the physical line interface between a MGC TDM network card/adapter and the physical TDM network. Its MML name is TDMIF.
For information on TDM interface parameters, refer to Table 2-32.
Command | Purpose |
|---|---|
mml>prov-add:tdmif:name="card1lif1",desc="V35 LIF 1", card="card1", lifnum=2, sigtype="V.35", datarate=64 |
|
Use the PROV-RTRV command to verify.
|
Tips Table 6-1 shows typical parameters based on card type. |
| Card Type | LIFNUM | RESIST | Data Rate/ Clock | DTEDCE | Line Coding | Format/ Framing | Signal Type | I/HDLC |
|---|---|---|---|---|---|---|---|---|
ITK (T1) | 1 | 75 |
| NA | B8ZS | ESF | T1 | IHDLC |
ITK (E1) | 1 | 120 |
| NA | HDB3 | CRC4 | CEPT | IHDLC |
V.35 | 2 | 0 | 64/EXT | DTE | NA | NA | V.35 | DEFAULT |
A TDM link is a communications link between a TDM interface card on the MGC and TDM hardware element. For each link, you need to specify the card interface to which the link connects. Its MML name is TDMLNK.
For information on TDM link parameters, refer to Table 2-23.
Command | Purpose |
|---|---|
mml>prov-add:tdmlnk:name="tdmlink1",if="card1 lif1",pri=2,slc=2,svc="ls-1",desc="signal link 1" |
|
Use the PROV-RTRV command to verify.
Now you need to configure MGW control links. The MGC uses these links to control the bearer traffic that passes between each MGW. You typically do this by:
An external node is a MGW with which the MGC communicates. Its MML name is EXTNODE.
For information on external node parameters, refer to Table 2-25.
Command | Purpose |
|---|---|
mml>prov-add:extnode:name="DestSW1",desc="Des tination Switch 1 - Jane" |
|
Use the PROV-RTRV command to verify.
|
Tips You must create an external node for each media gateway. |
This is a network card or adapter that is operating in the MGC. Its MML name is CARD.
The Ethernet interface provides the physical line interface between an MGC Ethernet network card/adapter and the physical Ethernet network. You configure parameters that control communications between the network card/adapter and the Ethernet. Its MML name is ENETIF.
Each SS7 link in the node must be associated with an Ethernet interface component, which must be associated with a network card. The Ethernet interface represents a physical network connection on the network card.
 |
Note In the MGC, the same cards and interfaces can be used for communication with Cisco SLTs and media gateways. When configured this way, separate links are assigned for Cisco SLT and media gateway communications. |
This is the EISUP signaling service or signaling path to an externally located MGC (destination). Its MML name is EISUPPATH.
For information on signaling service parameters, refer to Table 2-27.
Command | Purpose |
|---|---|
mml>prov-add:eisuppath:name="eisupsrv1",extno de="extseq1",desc="EISUP Service to Ext Seq Node1" |
|
Use the PROV-RTRV command to verify.
|
Note To ensure correct failover operation in a configuration with two local MGCs (one active and one standby) and a remote MGC, a minimum of two EISUP links are required from the remote VSC to each MGC redundant pair. |
This is the SGCP protocol path between the MGC and the MGW. Its MML name is SGCPPATH.
For information on signaling service parameters, refer to Table 2-27.
Command | Purpose |
|---|---|
mml>prov-add:SGCPPATH:name="sgcppsrv1",extnod e="mgw2",desc="SGCP Service to mgw 2" |
|
Use the PROV-RTRV command to verify.
For SGCP 1.0 only.
This is the FAS over IP transport service or signaling path from a Gateway to an MGC. Its MML name is IPFASPath.
For information on signaling service parameters, refer to Table 2-27.
Command | Purpose |
|---|---|
mml>prov-add:ipfaspath:name="ipfassvc1",extno de="nas1",desc="PRI Backhaul Service to NAS1", mdo="ETSI_300_172", custgrpid="1111", custgrptbl="0101", asppart="Y", abflag="a", crlen=1 |
|
Use the PROV-RTRV command to verify.
This is the MGCP signaling service or signaling path to a trunking gateway. Its MML name is MGCPPATH.
For information on signaling service parameters, refer to Table 2-27.
Command | Purpose |
|---|---|
mml>prov-add:mgcppath:name="mgcpsrv1",extnode ="cu1",desc="MGCP Service to CU 1" |
|
Use the PROV-RTRV command to verify.
This is the Q.931 protocol path between the MGC and the MGW. Its MML name is NASPATH.
For information on signaling service parameters, refer to Table 2-27.
Command | Purpose |
|---|---|
mml>prov-add:naspath:name="nassrv1",extnod="n as1",desc="Service to NAS1",mdo="BELL_1268_C3" |
|
Use the PROV-RTRV command to verify.
|
Tips For the NASPATH component, there is only one protocol: Bell_1268_C3. |
This is an IP connection between an MGC's Ethernet interface and an MGW. Its MML name is IPLNK.
For information on IP link parameters, refer to Table 2-35.
Command | Purpose |
|---|---|
mml>prov-add:iplnk:name= "Iplink1",if="en-1lif1",ipaddr="IP_Addr1",por t=3001, peeraddr="192.12.214.10",peerport=3001,svc="i pfassvc1",sigslot=1,sigport=1,desc="IP link for IPFAS service to NAS1" |
|
Use the PROV-RTRV command to verify.
|
Tips When configuring two IP links to the same NAS, you need to configure two different Ethernet IP addresses on both the MGC and the NAS. |
To configure the D channels on a Cisco MGX8260, you have to provision one IPFAS path and two IP links for each D channel. The MML component for provisioning multiple IPFAS paths and associated IP links on the Cisco MGX8260 is MLTIPFAS.
For information on signaling service parameters, refer to Table 2-27.
The procedure adds two IPFAS paths using FAS type signaling and four IP links (two per IPFAS path).
Step | Command | Purpose |
|---|---|---|
| mml>PROV-ADD:MLTIPFAS:NAME="BSC1",PATHSIZE=2, MDO="BELL_1268",EXTNODE="MGX-BH",PORT=7007,PE ERPORT=7007,SIGPORT=1,SIGSLOT=10,IF1="ENIF1", IF2="ENIF2",IPADDR1="IP_Addr1",IPADDR2="IP_Ad dr2",PEERADDR1="10.15.26.20",PEERADDR2="10.15 .27.20",SIDE="network",CUSTGRPID="V123" |
|
Use the PROV-RTRV command to verify.
MLTIPFAS supports add and delete operations only.
You must specify only the NAME and PATHSIZE parameters to remove several IPFAS paths and associated IP links. The following example deletes two IPFAS paths and associated IP links.
Command | Purpose |
|---|---|
mml>prov-add:mltipfas:name="bh531",pathsize=" 2" |
|
Use the PROV-RTRV command to verify.
You now need to configure trunks, trunk groups, and routing. The MGC uses this information for determining the call traffic on each trunk between the switches and the MGWs. You typically do this using the following.
The FILES component consists of customer-specific flat files that you can use to provision trunk groups, routing, trunks, and dial plans. The MML name is FILES.
For information on routing parameters, refer to the "Provisioning Trunk Groups and Trunks" section.
Command | Purpose |
|---|---|
mml>prov-add:files:name="BCFile",file="trunkC ust.dat",action="import" |
|
|
Note When importing screening files, for example AWhite list or BBlack list, the import file name must be one of the following: <custGrpId>.awhite, <custGrpId>.bwhite, <custGrpId>.ablack, or <custGrpId>.bblack. |
Use the PROV-RTRV command to verify.
This is the nailed trunk component for provisioning individual nailed bearer channels in a Dial Access configuration. Its MML name is NAILEDRNK.
For information on routing parameters, refer to the "Provisioning Trunk Groups and Trunks" section.
Command | Purpose |
|---|---|
mml>prov-add:nailedtrnk:name="101",srcsvc="ss 7svc1", srctimeslot=101,dstsvc="nassrv1", dstspan=3, dsttimeslot=1 |
|
Use the PROV-RTRV command to verify.
|
Tips Use the FILES component with flat files to provision trunks; use the NAILEDTRNK component with an individual trunk. |
This is the trunk group component for provisioning individual trunk groups. Its MML name is TRNKGRP.
For information on TRNKGRP parameters, refer to Table 2-38.
Command | Purpose |
|---|---|
mml>prov-add:trnkgrp:name="1000",clli="tttt-s s-bb-xxx", svc="ss7svc1", type="tdm_gen", selseq="lidl", qable="n" Virtual Switch Controller 1999-11-10 15:32:25 M COMPLD "TRNKGRP" |
|
Use the PROV-RTRV command to verify.
This section is used to configure the routing file. Three components are necessary to configure routing. Their MML names are RTLIST, RTTRNK, and RTTRNKGRPT.
For information on routing parameters, refer to the Table 2-41.
Step | Command | Purpose |
|---|---|---|
| mml>prov-add:rtlist:listindex=1,name="rtlist5 01910",rtname="rt501910",carrierid=333 |
|
| mml>prov-add:rttrnk:name="rt513913",trnkgrpnu m=513913 |
|
| mml>prov-add:rttrnkgrp:name="501910",type=7,r eattempts=1,queuing=0,cutthrough=2 |
|
Use the PROV-RTRV command to verify.
|
Tips All the route lists, route trunks, and route trunk groups information can be retrieved by using the prov:rtrv :rtlist:"ALL" command. The ALL option cannot be used with other parameters. |
This is the trunk group component for provisioning trunk group properties. Its MML name is TRNKGRPPROP. The following command overrides the trunk group property NPA for trunk group number 1000.
For information on TRNKGRPPROP properties, refer to Table 2-39.
Command | Purpose |
|---|---|
mml>prov-add:TRNKGRPPROP:NAME="1000",NPA="703" Virtual Switch Controller 1999-11-10 15:32:25 M COMPLD "TRNKGRPPROP" |
|
Use the PROV-RTRV command to verify.
This is the trunk (switched bearer channel) component for provisioning multiple switched trunks. Its MML name is SWITCHTRNK.
For information on SWITCHTRNK parameters, refer to the "Creating the Trunk Group" section.
The following command adds the six switched trunks shown in Table 6-2.
Command | Purpose |
|---|---|
mml>prov-add:switchtrnk:name="1",trnkgrpnu="1 000",span="ffff",cic="25",cu="gw1",spansize=6 ,endpoint="S0/DS1-1/6@li-5300-3" Virtual Switch Controller 1999-11-30 08:54:50 M COMPLD Virtual Switch Controller 1999-11-10 15:32:25 M COMPLD "switchtrnk" |
|
| Trunk Group Number | Trunk Group Member | Span | CIC | Endpoint | CLI |
|---|---|---|---|---|---|
1000 | 1 | ffff | 25 | S0/DS1-1/7@li-5300-3 | gw1 |
1000 | 2 | ffff | 26 | S0/DS1-1/8@li-5300-3 | gw1 |
1000 | 3 | ffff | 27 | S0/DS1-1/9@li-5300-3 | gw1 |
1000 | 4 | ffff | 28 | S0/DS1-1/10@li-5300-3 | gw1 |
1000 | 5 | ffff | 29 | S0/DS1-1/11@li-5300-3 | gw1 |
1000 | 6 | ffff | 30 | S0/DS1-1/12@li-5300-3 | gw1 |
Use the PROV-RTRV command to verify.
To retrieve multiple switched trunks based on the trunk group number, span, or CU name, use the PROV-RTRV command as follows.
Command | Purpose |
|---|---|
mml> prov-rtrv:switchtrnk:trnkgrpnum="1000" Virtual Switch Controller 1999-11-29 10:13:10 M RTRV "session=cujo:switchtrnk" /* NAME SPAN CIC TRNKGRPNUM CU ENDPOINT 25 --ffff--25---1000----gw1-S0/DS1-1/1@li5300-3 26 --ffff--26---1000----gw1-S0/DS1-1/2@li5300-3 27 --ffff--27---1000----gw1-S0/DS1-1/3@li5300-326 |
|
Use the PROV-RTRV command to verify.
To add multiple nailed trunks based on source svc, source span, dest-svc, and dest-span, use the PROV-ADD command as follows:
Command | Purpose |
|---|---|
mml>prov-add:nailedtrnk:name="100",srcsvc="SC-1", dstsvc="PC-7-200-7",srcspan="0",dstspan="ffff", srctimeslot="1",dsttimeslot="4065", spansize=6 Virtual Switch Controller 1999-11-30 08:54:50 M COMPLD "nailedtrnk" |
|
The previous command adds the six nailed trunks shown in Table 6-3.
| Name | SRCSVC | SRCSPAN | SRCTIMESLOT | DSTSVC | DSTSPAN | DSTTIMESLOT |
|---|---|---|---|---|---|---|
1 | SC-1 | 0 | 1 | PC-7-200-7 | ffff | 4065 |
2 | SC-1 | 0 | 2 | PC-7-200-7 | ffff | 4066 |
3 | SC-1 | 0 | 3 | PC-7-200-7 | ffff | 4067 |
4 | SC-1 | 0 | 4 | PC-7-200-7 | ffff | 4068 |
5 | SC-1 | 0 | 5 | PC-7-200-7 | ffff | 4069 |
6 | SC-1 | 0 | 6 | PC-7-200-7 | ffff | 4070 |
Use the PROV-RTRV:nailedtrnk:srcsvc="sc-1" command to verify.
To retrieve multiple nailed trunks, use the PROV-RTRV command as follows:
Command | Purpose |
|---|---|
mml>prov-rtrv:nailedtrnk:srcsvc="SC-1" Virtual Switch Controller 1999-11-29 12:47:41 M RTRV "session=xxx:nailedtrnk" |
|
Observe the screen to verify the command.
Only one of source service or destination service or source span or destination span is allowed at a time.
This is the component for provisioning multiple PRI trunk groups and bearer channels. Its MML name is MLTTRNKGRP.
Command | Purpose |
|---|---|
mml>prov-add:mlttrnkgrp:name="1000",svc="bsc1", clli="5300E4011",numtrnkgrp=2,spansize=4,trnkmemum= 1,span=0,cic=1,endpoint="S10/DS1-0/1@mgx-826,cu="mg x-east" |
|
Use the PROV-RTRV:mlttrnkgrp:name="1000",nextrttrnkgrp=2 command to verify.
You cannot provision other trunk group types (for example, TDM or IP) with MLTTRNKGRP.
You only need to specify the NAME and NUMTRNKGRP parameters to remove several multiple trunk groups and associated bearer channels.
Command | Purpose |
|---|---|
mml>prov-dlt:mlttrnkgrp:name="1000",numtrnkgrp=2 |
|
Use the PROV-RTRV command to verify.
You now need to configure the dial plan components. The MGC uses this information to perform different types of number analysis. You typically do this using the following:
|
Note Configure any dial plan components in the order shown above. |
All dial plan components are tables that have a name parameter, which is the MML name, and a description, which is a text description. The parameter's values are either an integer or a string. The dial plan provisioning is contained in the file customer group ID.dialPlan where the customer group ID is four alphanumeric characters.
For information on dial plan component parameters, refer to the "Release 7.4(x) Dial Plan Parameter Descriptions" section.
This is the dial plan component. Its MML name is DIALPLAN.
To add a dial plan, use the NUMAN-ADD command as follows:
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The digit modification table is accessed by the RESULTTABLE to yield a string of numbers to apply to an A-number or B-number. Its MML name is DIGMODSTRING.
To add appropriate values to a DIGMODSTRING table in a dial plan, use the NUMAN-ADD command as follows.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
|
Tips The DIGMODSTRING table is accessed by an implied index that contains a single string of numbers to be applied to calling or called number. |
The service table contains user-defined services for screening. Its MML name is SERVICE.
To build a service table, use the NUMAN-ADD file as follows:
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
|
Tips The service table acts as a slave to the result table. |
The results table contains the results of number analysis. It could, for example, point to screening or to an SCP/STP index. Its MML name is RESULTTABLE.
To build a results table in a dial plan based on the result type and data word parameters entered, use the NUMAN-ADD command as follows:
Step | Command | Purpose | ||
|---|---|---|---|---|
|
|
| ||
|
|
| ||
|
|
| ||
| ||||
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The A-digit tree table contains entries, in blocks of ten, for each calling (A-) number. Its output is an index to the result table or an indication that no further action is necessary. Its MML name is ADIGTREE.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The B-digit tree table contains entries, in blocks of ten, for each called (B-) number. Its output is an index to the result table or an indication that no further action is necessary. Its MML name is BDIGTREE.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The NPI (numbering plan indicator) table provides an index into the RESULTTABLE. It provides the capability to carry out early or pre-analysis before formal A-number and B-number analysis are requested. Its MML name is NPI.
Command | Purpose |
|---|---|
|
|
The NOA (nature of address) table provides an index into the NPI table. It provides the capability to carry out early or pre-analysis before formal A-number and B-number analysis are requested. Its MML name is NOA.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The location table identifies the type of network that originates a call. The MGC uses values from the CAUSE and LOCATION tables to determine result actions. Its MML name is LOCATION.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
|
Tips The LOCATION table contains 16 groups. |
The cause table provides an index into the location table to provide cause analysis. The MGC uses values from the cause and location tables to determine result actions. Its MML name is CAUSE.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4).
The AWhite list contains calling numbers that will be processed. If the presented A-number is not found in the database, then the screening is deemed to have failed and the call is released. Its MML name is AWHITE.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The ABlack list table contains calling numbers that will not be processed. If the presented A-number is found in the database, then the call is released. Its MML name is ABLACK.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The BWhite list table contains calling numbers that will be processed. If the presented B-number is not found in the database, the screening is deemed to have failed and the call is released. Its MML name is BWHITE.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4)
The BBlack list table contains calling numbers that will not be processed. If the presented B-number is found in the database, the call is released. Its MML name is BBLACK.
Command | Purpose |
|---|---|
|
|
To verify the change, use the NUMAN-RTRV command. (VALID ONLY for Release 7.4).
Posted: Wed Sep 27 12:55:42 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.