|
|
This chapter describes how to provision a sample Cisco SS7 Interconnect for Access Servers Solution (shown in Figure 3-1). The chapter describes a sample configuration for the illustration purpose only. Your configuration will vary and depend on your own network configuration.
 |
Tips Notes are used in this chapter to identify the procedures and other elements that differ in the Cisco media gateway controller software Release 7.3(x) and the Cisco media gateway controller software Release 7.4(x). However, most procedures are the same for both software releases. |
This chapter presents two ways of provisioning with MML:
To skip directly to the MML batch file used to provision the sample configuration, see "Creating and Processing an MML Batch File for Provisioning" section.
 |
Caution Do not use the sample values in this chapter to provision your system. You must research your network and obtain your own values for the network addresses, point codes, and other parameters used in your solution. If you use the sample values presented here, your configuration will not work. |
Perform the following steps to provision the sample Cisco SS7 Interconnect for Access Servers Solution.
Step | Section and Page | |
|---|---|---|
Provision SS7 signaling routes | ||
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
Provision signaling links | ||
|
| |
|
| |
|
| |
Provision NAS6 links | ||
|
| |
|
| |
|
| |
Provision trunks | ||
|
| |
|
| |
Deploy the session | ||
| 1OPC = origination point code 2DPC = destination point code 3APCs = adjacent point codes 4STPs = Signal Transfer Points 5Cisco SLTs = Cisco Signaling Link Terminals 6NAS = network access server |
 |
Note Trunk groups and trunk routing are not used in the Cisco SS7 Interconnect for Access Servers Solution. This solution uses nailed trunks between the NASs and the PSTN switch. The signaling controller does not perform trunk group selection in this solution. |
Table 3-1 shows a provisioning worksheet for the sample configuration shown in this chapter.
| Component | MML Name | Description | Parameters |
|---|---|---|---|
OPC | opc | Origination point code |
|
DPC | dpc1 | DPC of PSTN Switch A |
|
APC | apc1 | APC for STP A |
|
APC | apc2 | APC for STP B |
|
Linkset | ls01 | Linkset from signaling controller to STP A |
|
Linkset | ls02 | Linkset from signaling controller to STP B |
|
SS7 subsystem | subsys1 | Route between STP A and STP B |
|
SS7 route | ss7route1 | Route 1 to PSTN Switch A through LS1 |
|
SS7 route | ss7route2 | Route 2 to PSTN Switch A through LS2 |
|
SS7 signaling service | ss7sigsvc | SS7 service to PSTN Switch A |
|
Adapter (card) | encard1 | Ethernet Card 1 |
|
Adapter (card) | encard2 | Ethernet Card 2 |
|
Ethernet interface | enetif1 | Ethernet interface for encard1 |
|
Ethernet interface | enetif2 | Ethernet interface for encard2 |
|
C7 IP link | c7iplink1 | Link 1 in Linkset 1 |
|
C7 IP link | c7iplink2 | Link 2 in Linkset 1 |
|
C7 IP link | c7iplink3 | Link 1 in Linkset 2 |
|
C7 IP link | c7iplink4 | Link 2 in Linkset 2 |
|
NAS external node | nas1 | NAS 1 | none |
NAS external node | nas2 | NAS 2 | none |
NAS external node | nas3 | NAS 3 | none |
NAS signaling service | nassvc1 | Signaling service for |
|
NAS signaling service | nassvc2 | Signaling service for |
|
NAS signaling service | nassvc3 | Signaling service for |
|
IP link | iplink1 | IP link for NAS 1 |
|
IP link | iplink2 | IP link for NAS 2 |
|
IP link | iplink3 | IP link for NAS 3 |
|
IP link | iplink4 | IP link 2 for NAS 1 |
|
IP link | iplink5 | IP link 2 for NAS 2 |
|
IP link | iplink6 | IP link 2 for NAS 3 |
|
Log in to the signaling controller and start an MML session. For more information on MML commands, see the Cisco Media Gateway Controller Software Release 7 Reference Guide.
|
Caution Do not log in as root when starting MML. If you log in as root and attempt to start an MML session, you cause a core dump and MML does not start. |
To start an MML session:
|
Note If you log in as a user who is not in the transpath or mgcgrp group, you might need to enter the commands newgrp transpath (or newgrp mgcgrp) and source .cshrc after logging in. |
Step 2 Enter mml:
machine-name% mml copyright © 1998-2000, Cisco Systems, Inc. machine-name mml>
If another session is running, you receive a message similar to the following:
machine-name% mml copyright © 1998-2000, Cisco Systems, Inc. mml1: Already in use Failure to run MML, reason=Entry was already present machine-name%
To see other MML sessions that are running, enter ls /opt/TransPath/var (for Cisco media gateway controller software Release 7.4(x), enter ls /opt/CiscoMGC/var). MML session numbers range from 1 through 12. Depending on the number of MML sessions, you will see a list of files similar to the following:
mml0.LOCK mml1.LOCK mml2.LOCK
If MML is already running, enter mml -s x (x = the number of a session that does not appear as locked; range is 1 through 12):
machine-name% mml -s 2 Copyright © 1998-2000, Cisco Systems, Inc. machine-name mml>
Step 3 Start a provisioning session by entering the prov-sta::srcver="new",dstver="dialcfg1" command:
machine-name mml> prov-sta::srcver="new",dstver="dialcfg1" Media Gateway Controller 2000-04-04 15:00:57 M COMPLD "PROV-STA" ; machine-name mml>
This starts a new provisioning session ("new"), names it CFG_dialcfg1, and saves the configuration files in /opt/TransPath/etc/CONFIG_LIB.
|
Note In Cisco media gateway controller software Release 7.4(x), the files are saved in /opt/CiscoMGC/etc/CONFIG_LIB. |
|
Tips If another provisioning session is running, you cannot start a provisioning session. You receive an error similar to Example 3-1. |
machine-name mml> prov-sta::srcver="new",dstver="dial9" Media Gateway Controller 2000-04-04 15:02:42 M DENY SROF "PROV-STA: POM session is already in use by mml2" /* Status, Requested Operation Failed on the component */ ;
To see if another provisioning session is running, enter the prov-rtrv:session command:
machine-name mml> prov-rtrv:session Media Gateway Controller 2000-04-04 15:03:07 M RTRV "session=dialcfg1:session" /* Session ID = mml2 SRCVER = new DSTVER = dialcfg1 */ ;
This example shows that an active provisioning session named dialcfg1 is in use.
Refer to the Cisco Media Gateway Controller Software Release 7 Provisioning Guide for more information on provisioning with MML and general provisioning steps.
MML commands use the following syntax:
command_name:[target][, target][, target. . .][:Parameter_List][;comments]
When entering MML commands, remember the following:
To obtain on-line help in an MML session, enter help at the command prompt. For more information, refer to the Cisco Media Gateway Controller Release 7 Software Reference Guide.
|
Note Many procedures in this chapter refer to sections in Cisco Media Gateway Controller Software Release 7 Provisioning Guide. Keep that book handy when performing the procedures in this chapter. |
The SS7 signaling route is the path from the Cisco SC host to a service switching point (SSP) through the Cisco SLTs and signal transfer points (STPs). In the sample configuration in this chapter, the SSP is the PSTN switch. When you provision the SS7 signaling routes, you add the following components:
For more information on configuring SS7 signaling routes, see Cisco Media Gateway Controller Software Release 7 Provisioning Guide.
A point code is an SS7 network address that identifies an SS7 network node, such as an STP or an SSP.
|
Note ITU point codes contain 14 bits, and North American point codes contain 24 bits. |
The following procedure shows how to add the point code for the SC host shown in the shaded area in Figure 3-2.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:ptcode:name="opc",netaddr="171.1.4",netind=2,desc="Origination point code" Media Gateway Controller 2000-04-04 15:04:48 M COMPLD "ptcode" ; |
|
To verify that you have added the opc, enter the prov-rtrv:ptcode:name="opc" command:
machine-name mml> prov-rtrv:ptcode:name="opc" Media Gateway Controller 2000-04-04 15:05:44 M RTRV "session=dialcfg1:ptcode" /* NAME = opc DESC = Origination point code NETADDR = 171.1.4 NETIND = 2 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all point codes by entering the prov-rtrv:ptcode:"all" command as shown in Example 3-2. |
machine-name mml> prov-rtrv:ptcode:"all"
Media Gateway Controller 2000-04-04 15:05:32
M RTRV
"session=dialcfg1:ptcode"
/*
NAME NETADDR NETIND
---- ------- ------
opc 171.1.4 2
*/
;
The following procedure shows how to add the point code for the PSTN switch A, shown in the shaded area in Figure 3-3.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:ptcode:name="dpc1",netaddr= |
|
To verify that you have added the DPC, enter the prov-rtrv:ptcode:name="dpc1" command:
machine-name mml> prov-rtrv:ptcode:name="dpc1" Media Gateway Controller 2000-04-04 15:09:25 M RTRV "session=dialcfg1:ptcode" /* NAME = dpc1 DESC = PPC of PSTN Switch A NETADDR = 171.1.3 NETIND = 2 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all point codes by entering the prov-rtrv:ptcode:"all" command as shown in Example 3-3. |
machine-name mml> prov-rtrv:ptcode:"all" Media Gateway Controller 2000-04-04 15:10:47 M RTRV "session=dialcfg1:ptcode" /* NAME NETADDR NETIND ---- ------- ------ opc 171.1.4 2 dpc1 171.1.3 2 */ ;
The following procedure shows how to add the adjacent point codes for the STPs shown in the shaded area in Figure 3-4.
|
Note The sample configuration in this chapter uses A-links from the STPs for signaling to the Cisco SLTs. If you have a configuration where F-links come directly from the SSP to the Cisco SLTs, you do not need to add APCs. |
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:apc:name="apc1",netaddr="171.16.1",desc= |
|
| machine-name mml> prov-add:apc:name="apc2",netaddr="171.16.2",desc= |
|
To verify that you have entered the APCs, enter the prov-rtrv:apc:name="MML name" command for each APC. For example, to verify the first APC:
machine-name mml> prov-rtrv:apc:name="apc1" Media Gateway Controller 2000-04-04 15:13:54 M RTRV "session=dialcfg1:apc" /* NAME = apc1 DESC = APC for STP A NETADDR = 171.16.1 NETIND = 0 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all APCs by entering the prov-rtrv:apc:"all" command as shown in Example 3-4. |
machine-name mml> prov-rtrv:apc:"all" Media Gateway Controller 2000-04-04 10:45:12 M RTRV "session=dialcfg1:apc" /* NAME NETADDR NETIND ---- ------- ------ apc1 171.16.1 2 apc2 171.16.2 2 */ ;
A linkset is a logical set of one or more links originating from an SS7 node (STP) and connecting to an adjacent node. In this example, the linkset contains communication links that connect from the signaling controller to an adjacent STP.
You must provision one linkset for each connection through the STP to the signaling controller. The shaded area in Figure 3-5 shows the linksets you provision in this example.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:lnkset:name="ls01",apc="apc1",type= |
|
| machine-name mml> prov-add:lnkset:name="ls02",apc="apc2",type= |
|
To verify that you have entered the linksets, enter the prov-rtrv:lnkset:name="MML name" command for each linkset. For example, to verify the first linkset:
machine-name mml> prov-rtrv:lnkset:name="ls01" Media Gateway Controller 2000-04-04 15:18:40 M RTRV "session=dialcfg1:lnkset" /* NAME = ls01 DESC = Linkset from signaling controller to STP A APC = apc1 PROTO = SS7-ANSI TYPE = IP */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all linksets by entering the prov-rtrv:lnkset:"all" command as shown in Example 3-5. |
machine-name mml> prov-rtrv:lnkset:"all" Media Gateway Controller 2000-04-04 15:20:43 M RTRV "session=dialcfg1:lnkset" /* NAME APC PROTO TYPE ---- --- ----- ---- ls01 apc1 SS7-ANSI IP ls02 apc2 SS7-ANSI IP */ ;
|
Note After creating the linksets, you must create the C7 IP links for each linkset. See "Adding C7 IP Links to Cisco SLTs" section. |
You must add an SS7 subsystem that identifies each pair of mated STPs. This allows the signaling controller to route traffic over the C-links between the STPs in case of a failure between one of the STPs and an endpoint.
The shaded area in Figure 3-6 shows the STPs you must connect (STP A and STP B).
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:ss7subsys:name="subsys1",svc="apc1",matedapc="apc2",proto="SS7-ANSI",pri=3,ssn=0,desc="Route between STP A and STP B" Media Gateway Controller 2000-04-04 15:21:56 M COMPLD "ss7subsys" ; |
|
To verify that you have added the SS7 subsystem, enter the prov-rtrv:ss7subsys:name="subsys1" command:
machine-name mml> prov-rtrv:ss7subsys:name="subsys1" Media Gateway Controller 2000-04-04 15:22:44 M RTRV "session=dialcfg1:ss7subsys" /* NAME = subsys1 DESC = Route between STP A and STP B SVC = apc1 PRI = 3 MATEDAPC = apc2 SSN = 0 PROTO = SS7-ANSI STPSCPIND = 0 TRANSPROTO = SCCP */ ;
An SS7 route is a path through a linkset between the signaling controller and another signaling controller or TDM switch. In this example, the SS7 routes indicate the linksets that carry SS7 signals between the signaling controller and the PSTN switch A.
You must add an SS7 route for each signaling path from the signaling controller to the PSTN switch A. You provision a route for each linkset. The shaded area in Figure 3-7 shows the SS7 routes you provision for this example.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:ss7route:name="ss7route1",opc= |
|
| machine-name mml> prov-add:ss7route:name="ss7route2",opc= |
|
To verify that you have entered the SS7 routes, enter the prov-rtrv:ss7route:name="MML name" command for each SS7 route. For example, to verify the first SS7 route:
machine-name mml> prov-rtrv:ss7route:name="ss7route1" Media Gateway Controller 2000-04-04 15:32:21 M RTRV "session=dialcfg1:ss7route" /* NAME = ss7route1 DESC = Route 1 to PSTN Switch A through LS01 OPC = opc DPC = dpc1 LNKSET = ls01 PRI = 1 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all SS7 routes by entering the prov-rtrv:ss7route:"all" command as shown in Example 3-6. |
machine-name mml> prov-rtrv:ss7route:"all"
Media Gateway Controller 2000-04-04 11:01:18
M RTRV
"session=dialcfg1:ss7route"
/*
NAME OPC DPC LNKSET
PRI
---- --- --- ------
---
ss7route1 opc dpc1 ls01
1
ss7route2 opc dpc1 ls02
1
*/
;
The SS7 signaling service specifies the path and the protocol variant that the signaling controller uses to communicate with a remote switch (SSP) that sends bearer traffic to the NASs.
You must add an SS7 signaling service from the signaling controller to the PSTN switch. The shaded area in Figure 3-8 shows the signaling service you are adding.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml>prov-add:ss7path:name= |
|
To verify that you have added the SS7 signaling service, enter the prov-rtrv:ss7path:name="ss7sigsvc" command:
mml> prov-rtrv:ss7path:name="ss7sigsvc" Media Gateway Controller 2000-03-03 14:22:12 M RTRV "session=dialcfg1:ss7path" /* NAME = ss7sigsvc DESC = SS7 service to PSTN Switch A DPC = dpc1 MDO = ANSISS7_STANDARD CUSTGRPID = d125 CUSTGRPTBL = 0101 SIDE = network ASPPART = N */ ;
You must provision links for all physical connections bearing signals that enter and exit the signaling controller. This includes SS7 signals from the SSP (PSTN Switch A) and signals to the NASs. You must add the following components:
You must add a card component for each card in the signaling controller. For the example in this chapter, you add one Ethernet card for each connection to the IP network--one card for the 10-Mb signaling network and one for the 100-Mb signaling network. These cards permit SS7 signaling between the signaling controller and the Cisco SLTs. The shaded area in Figure 3-9 shows the Ethernet cards you provision in this sample.
|
Note You provision only one set of cards for one signaling controller (the primary), even though both signaling controllers are highlighted. |
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:card:name="encard1",type="EN",slot=0,desc= |
|
| machine-name mml> prov-add:card:name="encard2",type="EN",slot=1,desc= |
|
To verify that you have entered the cards, enter the prov-rtrv:card:name="MML name" command. For example, to verify the first Ethernet card:
machine-name mml> prov-rtrv:card:name="encard1" Media Gateway Controller 2000-03-03 20:38:44 M RTRV "session=dialcfg1:card" /* NAME = encard1 DESC = Ethernet Card 1 TYPE = EN SLOT = 0 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all cards by entering the prov-rtrv:card:"all" command as shown in Example 3-7. |
machine-name mml> prov-rtrv:card:"all" Media Gateway Controller 2000-04-04 11:10:24 M RTRV "session=dialcfg1:card" /* NAME TYPE SLOT ---- ---- ---- encard1 EN 0 encard2 EN 1 */ ;
|
Note You must provision the card before provisioning the card interfaces. |
The Ethernet interface provides the physical line interface between the signaling controller's Ethernet card and the physical Ethernet network. You must add an Ethernet interface if you have added an Ethernet card.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:enetif:name="enetif1",card="encard1",desc= |
|
| machine-name mml> prov-add:enetif:name="enetif2",card="encard2",desc= |
|
To verify that you have entered the Ethernet interfaces, enter the prov-rtrv:enetif:name="MML name" command. For example, to verify the first Ethernet interface:
va-testing mml> prov-rtrv:enetif:name="enetif1" Media Gateway Controller 2000-03-03 20:40:05 M RTRV "session=dialcfg1:enetif" /* NAME = enetif1 DESC = Ethernet interface for Card 1 CARD = encard1 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all Ethernet interfaces by entering the prov-rtrv:enetif:"all" command as shown in Example 3-8. |
machine-name mml> prov-rtrv:enetif:"all" Media Gateway Controller 2000-04-04 11:27:16 M RTRV "session=dialcfg1:enetif" /* NAME CARD ---- ---- enetif1 encard1 enetif2 encard2 */ ;
A C7 IP link component identifies a link between the Cisco SLT's IP address and port, and an SSP or an STP in the SS7 network. The C7 IP link identifies one of the links within a linkset.
|
Note Use C7 IP links only when your configuration has Cisco SLTs that carry SS7 signaling to the signaling controller over IP. If your configuration does not include Cisco SLTs and your links terminate from the STPs directly into TDM cards in the signaling controller, you must provision TDM links. For example, the Cisco SS7 Dial Access Solution Release 2.0 uses TDM cards and TDM links. |
You must add a C7 IP link for each physical SS7 link that is connected to the SS7 network through the Cisco SLT. These links correspond to the linksets you created in the "Adding Linksets" section. The shaded area in Figure 3-10 shows the C7 IP links you provision in this example.
You must add two links for linkset 1 and two links for linkset 2.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:c7iplnk:name="c7iplink1",if="enetif1", |
|
| machine-name mml> prov-add:c7iplnk:name="c7iplink2",if="enetif1", |
|
| machine-name mml> prov-add:c7iplnk:name="c7iplink3",if="enetif2", |
|
| machine-name mml> prov-add:c7iplnk:name="c7iplink4",if="enetif2", |
|
To verify that you have entered the C7 IP links, enter the prov-rtrv:c7iplnk:name="MML name" command. For example, to verify the first C7 IP link:
va-testing mml> prov-rtrv:c7iplnk:name="c7iplink1" Media Gateway Controller 2000-03-03 21:12:47 M RTRV "session=dialcfg1:c7iplnk" /* NAME = c7iplink1 DESC = Link 1 in Linkset 1 LNKSET = ls01 IF = enetif1 IPADDR = IP_Addr1 PORT = 5000 PEERADDR = 175.30.241.27 PEERPORT = 32767 SLC = 0 PRI = 1 TIMESLOT = 0 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all C7 IP links by entering the prov-rtrv:c7iplnk:"all" command as shown in Example 3-9. |
machine-name mml> prov-rtrv:c7iplnk:"all" Media Gateway Controller 2000-04-04 11:40:17 M RTRV "session=dialcfg1:c7iplnk" /* NAME LNKSET IF IPADDR PORT PEERADDR PEERPORT PRI SLC TIMESLOT ---- ------ -- ------ ---- -------- -------- --- --- -------- c7iplink1 ls01 enetif1 IP_Addr1 5000 175.30.241.27 32767 1 0 0 c7iplink2 ls02 enetif1 IP_Addr2 5000 175.30.238.28 32767 1 1 0 c7iplink3 ls01 enetif2 IP_Addr1 5000 175.30.241.27 32767 1 0 0 c7iplink4 ls02 enetif2 IP_Addr2 5000 175.30.238.28 32767 1 1 0 */ ;
NAS links indicate the communication path the signaling controller uses to control the bearer traffic that passes through each NAS.
To add links to the NASs in your network, you must add the following components:
You must add a NAS external node for each NAS in your network. The shaded areas in Figure 3-11 show the NAS external nodes.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:extnode:name="nas1",desc="NAS 1" Media Gateway Controller 2000-03-04 11:36:07 M COMPLD "extnode" ; |
|
| machine-name mml> prov-add:extnode:name="nas2",desc="NAS 2" Media Gateway Controller 2000-03-04 11:36:21 M COMPLD "extnode" ; |
|
| machine-name mml> prov-add:extnode:name="nas3",desc="NAS 3" Media Gateway Controller 2000-03-04 11:36:31 M COMPLD "extnode" ; |
|
To verify that you have entered the NASs, enter the prov-rtrv:extnode:name="MML name" command. For example, to verify the first NAS:
va-testing mml> prov-rtrv:extnode:name="nas1" Media Gateway Controller 2000-03-04 11:36:46 M RTRV "session=dialcfg1:extnode" /* NAME = nas1 DESC = NAS 1 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all NAS external nodes by entering the prov-rtrv:extnode:"all" command as shown in Example 3-10. |
machine-name mml> prov-rtrv:extnode:"all" Media Gateway Controller 2000-04-04 11:44:41 M RTRV "session=dialcfg1:extnode" /* NAME ---- nas1 nas2 nas3 */ ;
You must add a NAS signaling service for each NAS you created in the "Adding NAS External Nodes" section. The NAS signaling service indicates the Q.931 protocol path between the signaling controller and the NASs.
The shaded area in Figure 3-12 shows the NAS signaling services.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:naspath:name="nassvc1",extnode="nas1",mdo="BELL_1268_C3",desc="Signaling service for NAS 1" Media Gateway Controller 2000-03-04 11:40:11 M COMPLD "naspath" ; |
|
| machine-name mml> prov-add:naspath:name="nassvc2",extnode="nas2",mdo="BELL_1268_C3",desc="Signaling service for NAS 2" Media Gateway Controller 2000-03-04 11:41:07 M COMPLD "naspath" ; |
|
| machine-name mml> prov-add:naspath:name="nassvc3",extnode="nas3",mdo="BELL_1268_C3",desc="Signaling service for NAS 3" Media Gateway Controller 2000-03-04 11:41:49 M COMPLD "naspath" ; |
|
To verify that you have entered the NAS signaling services, enter the prov-rtrv:naspath:name="MML name" command. For example, to verify the first NAS signaling service was added:
va-testing mml> prov-rtrv:naspath:name="nassvc1" Media Gateway Controller 2000-03-04 11:42:36 M RTRV "session=dialcfg1:naspath" /* NAME = nassvc1 DESC = Signaling service for NAS 1 EXTNODE = nas1 MDO = BELL_1268_C3 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all NAS signaling services by entering the prov-rtrv:naspath:"all" command as shown in Example 3-11. |
machine-name mml> prov-rtrv:naspath:"all" Media Gateway Controller 2000-04-04 11:49:02 M RTRV "session=dialcfg1:naspath" /* NAME EXTNODE MDO ---- ------- --- nassvc1 nas1 BELL_1268_C3 nassvc2 nas2 BELL_1268_C3 nassvc3 nas3 BELL_1268_C3 */ ;
You must add an IP link from each NAS to each Ethernet card and interface in the signaling controller. In this example, you provision the following IP links:
|
Note If you are provisioning two links from the signaling controller to the same NAS, you need two different Ethernet IP addresses on both the signaling controller and the NAS. |
The shaded area in Figure 3-13 shows the links you are adding in this example.
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-add:iplnk:name="iplink1",if="enetif1",ipaddr="IP_Addr1",port=3001,peeraddr="175.30.241.2",peerport=3001,svc="nassvc1",desc="IP link for NAS 1 to Ethernet Interface 1" Media Gateway Controller 2000-03-04 11:48:54 M COMPLD "iplnk" ; |
|
| machine-name mml> prov-add:iplnk:name="iplink2",if="enetif2",ipaddr="IP_Addr1",port=3001,peeraddr="175.30.238.2",peerport=3001,svc="nassvc2",desc="IP link for NAS 1 to Ethernet Interface 2" Media Gateway Controller 2000-03-04 11:50:24 M COMPLD "iplnk" ; |
|
| machine-name mml> prov-add:iplnk:name="iplink3",if="enetif1",ipaddr="IP_Addr1",port=3001,peeraddr="175.30.241.3",peerport=3001,svc="nassvc3",desc="IP link for NAS 2 to Ethernet Interface 1" Media Gateway Controller 2000-03-04 11:51:35 M COMPLD "iplnk" ; |
|
| machine-name mml> prov-add:iplnk:name="iplink4",if="enetif2",ipaddr="IP_Addr2",port=3001,peeraddr="175.30.238.3",peerport=3001,svc="nassvc1",desc="IP link for NAS 2 to Ethernet Interface 2" Media Gateway Controller 2000-03-04 11:53:17 M COMPLD "iplnk" ; |
|
| machine-name mml> prov-add:iplnk:name="iplink5",if="enetif1",ipaddr="IP_Addr2",port=3001,peeraddr="175.30.241.4",peerport=3001,svc="nassvc2",desc="IP link for NAS 3 to Ethernet Interface 1" Media Gateway Controller 2000-03-04 11:54:20 M COMPLD "iplnk" ; |
|
| machine-name mml> prov-add:iplnk:name="iplink6",if="enetif2",ipaddr="IP_Addr2",port=3001,peeraddr="175.30.238.4",peerport= |
|
To verify that you have entered the IP links, enter the prov-rtrv:iplnk:name="MML name" command to verify the first IP link:
va-testing mml> prov-rtrv:iplnk:name="iplink1" Media Gateway Controller 2000-03-04 12:01:23 M RTRV "session=dialcfg1:iplnk" /* NAME = iplink1 DESC = IP link for NAS 1 to Ethernet Interface 1 SVC = nassvc1 IF = enetif1 IPADDR = IP_Addr1 PORT = 3001 PEERADDR = 175.30.241.2 PEERPORT = 3001 PRI = 1 SIGSLOT = 0 SIGPORT = 0 */ ;
|
Note In software Release 7.4(x), you can retrieve and verify all IP links by entering the prov-rtrv:iplnk:"all" command as shown in Example 3-12. |
machine-name mml> prov-rtrv:iplnk:"all" Media Gateway Controller 2000-04-04 12:05:43 M RTRV "session=dialcfg1:iplnk" /*
You must add trunks for each connection between the NAS and the PSTN switch. The shaded area in Figure 3-14 shows the T1 lines from the NAS to the PSTN switch that terminate bearer traffic. NAS 1 has four T1 lines, NAS 2 has four T1 lines, and NAS 3 has three T1 lines. Each T1 contains 24 trunks, or DS0s. For the examples in this section, you must provision 264 trunks (96 for NAS1, 96 for NAS2, and 72 for NAS3).
You can add trunks using any of the following methods:
|
Note This option is available in software Release 7.4(x) only. However, if you use the TCM with software Release 7.3(x), you can add 24 trunks at one time for T1 lines and 31 trunks at one time for E1 lines. See "Provisioning Trunks" section for more information on adding trunks with the TCM/CMM. |
|
Tips If you have a large number of trunks, use the text file method for adding trunks. |
Using a text file to add trunks requires you to create a text file that contains the following fields:
|
Note For nailed trunks in the signaling controller, this value is always ffff. |
|
Note The values used for destination span in the following examples are sample values. The real values for this parameter would match whichever PRI port the T1 is connected to on the NAS. Valid values are 0 through 3. |
The following example shows the trunk text file for the sample configuration in this chapter. The fields in the text file correspond to the fields described above.
#format2 100 ss7sigsvc ffff 1 nassvc1 1 1 101 ss7sigsvc ffff 2 nassvc1 1 2 102 ss7sigsvc ffff 3 nassvc1 1 3 103 ss7sigsvc ffff 4 nassvc1 1 4 104 ss7sigsvc ffff 5 nassvc1 1 5 105 ss7sigsvc ffff 6 nassvc1 1 6 106 ss7sigsvc ffff 7 nassvc1 1 7 107 ss7sigsvc ffff 8 nassvc1 1 8 108 ss7sigsvc ffff 9 nassvc1 1 9 109 ss7sigsvc ffff 10 nassvc1 1 10 110 ss7sigsvc ffff 11 nassvc1 1 11 111 ss7sigsvc ffff 12 nassvc1 1 12 112 ss7sigsvc ffff 13 nassvc1 1 13 113 ss7sigsvc ffff 14 nassvc1 1 14 114 ss7sigsvc ffff 15 nassvc1 1 15 115 ss7sigsvc ffff 16 nassvc1 1 16 116 ss7sigsvc ffff 17 nassvc1 1 17 117 ss7sigsvc ffff 18 nassvc1 1 18 118 ss7sigsvc ffff 19 nassvc1 1 19 119 ss7sigsvc ffff 20 nassvc1 1 20 120 ss7sigsvc ffff 21 nassvc1 1 21 121 ss7sigsvc ffff 22 nassvc1 1 22 122 ss7sigsvc ffff 23 nassvc1 1 23 123 ss7sigsvc ffff 24 nassvc1 1 24 124 ss7sigsvc ffff 25 nassvc1 1 25 125 ss7sigsvc ffff 26 nassvc1 1 26 126 ss7sigsvc ffff 27 nassvc1 1 27 127 ss7sigsvc ffff 28 nassvc1 1 28 128 ss7sigsvc ffff 29 nassvc1 1 29 129 ss7sigsvc ffff 30 nassvc1 1 30 130 ss7sigsvc ffff 31 nassvc1 1 31 131 ss7sigsvc ffff 32 nassvc1 1 32 132 ss7sigsvc ffff 33 nassvc1 1 33 133 ss7sigsvc ffff 34 nassvc1 1 34 134 ss7sigsvc ffff 35 nassvc1 1 35 135 ss7sigsvc ffff 36 nassvc1 1 36 136 ss7sigsvc ffff 37 nassvc1 1 37 137 ss7sigsvc ffff 38 nassvc1 1 38 138 ss7sigsvc ffff 39 nassvc1 1 39 139 ss7sigsvc ffff 40 nassvc1 1 40 140 ss7sigsvc ffff 41 nassvc1 1 41 141 ss7sigsvc ffff 42 nassvc1 1 42 142 ss7sigsvc ffff 43 nassvc1 1 43 143 ss7sigsvc ffff 44 nassvc1 1 44 144 ss7sigsvc ffff 45 nassvc1 1 45 145 ss7sigsvc ffff 46 nassvc1 1 46 146 ss7sigsvc ffff 47 nassvc1 1 47 147 ss7sigsvc ffff 48 nassvc1 1 48 148 ss7sigsvc ffff 49 nassvc1 1 49 149 ss7sigsvc ffff 50 nassvc1 1 50 150 ss7sigsvc ffff 51 nassvc1 1 51 151 ss7sigsvc ffff 52 nassvc1 1 52 152 ss7sigsvc ffff 53 nassvc1 1 53 153 ss7sigsvc ffff 54 nassvc1 1 54 154 ss7sigsvc ffff 55 nassvc1 1 55 155 ss7sigsvc ffff 56 nassvc1 1 56 156 ss7sigsvc ffff 57 nassvc1 1 57 157 ss7sigsvc ffff 58 nassvc1 1 58 158 ss7sigsvc ffff 59 nassvc1 1 59 159 ss7sigsvc ffff 60 nassvc1 1 60 160 ss7sigsvc ffff 61 nassvc1 1 61 161 ss7sigsvc ffff 62 nassvc1 1 62 162 ss7sigsvc ffff 63 nassvc1 1 63 163 ss7sigsvc ffff 64 nassvc1 1 64 164 ss7sigsvc ffff 65 nassvc1 1 65 165 ss7sigsvc ffff 66 nassvc1 1 66 166 ss7sigsvc ffff 67 nassvc1 1 67 167 ss7sigsvc ffff 68 nassvc1 1 68 168 ss7sigsvc ffff 69 nassvc1 1 69 169 ss7sigsvc ffff 70 nassvc1 1 70 170 ss7sigsvc ffff 71 nassvc1 1 71 171 ss7sigsvc ffff 72 nassvc1 1 72 172 ss7sigsvc ffff 73 nassvc1 1 73 173 ss7sigsvc ffff 74 nassvc1 1 74 174 ss7sigsvc ffff 75 nassvc1 1 75 175 ss7sigsvc ffff 76 nassvc1 1 76 176 ss7sigsvc ffff 77 nassvc1 1 77 177 ss7sigsvc ffff 78 nassvc1 1 78 178 ss7sigsvc ffff 79 nassvc1 1 79 179 ss7sigsvc ffff 80 nassvc1 1 80 180 ss7sigsvc ffff 81 nassvc1 1 81 181 ss7sigsvc ffff 82 nassvc1 1 82 182 ss7sigsvc ffff 83 nassvc1 1 83 183 ss7sigsvc ffff 84 nassvc1 1 84 184 ss7sigsvc ffff 85 nassvc1 1 85 185 ss7sigsvc ffff 86 nassvc1 1 86 186 ss7sigsvc ffff 87 nassvc1 1 87 187 ss7sigsvc ffff 88 nassvc1 1 88 188 ss7sigsvc ffff 89 nassvc1 1 89 189 ss7sigsvc ffff 90 nassvc1 1 90 190 ss7sigsvc ffff 91 nassvc1 1 91 191 ss7sigsvc ffff 92 nassvc1 1 92 192 ss7sigsvc ffff 93 nassvc1 1 93 193 ss7sigsvc ffff 94 nassvc1 1 94 194 ss7sigsvc ffff 95 nassvc1 1 95 195 ss7sigsvc ffff 96 nassvc1 1 96 196 ss7sigsvc ffff 97 nassvc2 2 97 197 ss7sigsvc ffff 98 nassvc2 2 98 198 ss7sigsvc ffff 99 nassvc2 2 99 199 ss7sigsvc ffff 100 nassvc2 2 100 200 ss7sigsvc ffff 101 nassvc2 2 101 201 ss7sigsvc ffff 102 nassvc2 2 102 202 ss7sigsvc ffff 103 nassvc2 2 103 203 ss7sigsvc ffff 104 nassvc2 2 104 204 ss7sigsvc ffff 105 nassvc2 2 105 205 ss7sigsvc ffff 106 nassvc2 2 106 206 ss7sigsvc ffff 107 nassvc2 2 107 207 ss7sigsvc ffff 108 nassvc2 2 108 208 ss7sigsvc ffff 109 nassvc2 2 109 209 ss7sigsvc ffff 110 nassvc2 2 110 210 ss7sigsvc ffff 111 nassvc2 2 111 211 ss7sigsvc ffff 112 nassvc2 2 112 212 ss7sigsvc ffff 113 nassvc2 2 113 213 ss7sigsvc ffff 114 nassvc2 2 114 214 ss7sigsvc ffff 115 nassvc2 2 115 215 ss7sigsvc ffff 116 nassvc2 2 116 216 ss7sigsvc ffff 117 nassvc2 2 117 217 ss7sigsvc ffff 118 nassvc2 2 118 218 ss7sigsvc ffff 119 nassvc2 2 119 219 ss7sigsvc ffff 120 nassvc2 2 120 220 ss7sigsvc ffff 121 nassvc2 2 121 221 ss7sigsvc ffff 122 nassvc2 2 122 222 ss7sigsvc ffff 123 nassvc2 2 123 223 ss7sigsvc ffff 124 nassvc2 2 124 224 ss7sigsvc ffff 125 nassvc2 2 125 225 ss7sigsvc ffff 126 nassvc2 2 126 226 ss7sigsvc ffff 127 nassvc2 2 127 227 ss7sigsvc ffff 128 nassvc2 2 128 228 ss7sigsvc ffff 129 nassvc2 2 129 229 ss7sigsvc ffff 130 nassvc2 2 130 230 ss7sigsvc ffff 131 nassvc2 2 131 231 ss7sigsvc ffff 132 nassvc2 2 132 232 ss7sigsvc ffff 133 nassvc2 2 133 233 ss7sigsvc ffff 134 nassvc2 2 134 234 ss7sigsvc ffff 135 nassvc2 2 135 235 ss7sigsvc ffff 136 nassvc2 2 136 236 ss7sigsvc ffff 137 nassvc2 2 137 237 ss7sigsvc ffff 138 nassvc2 2 138 238 ss7sigsvc ffff 139 nassvc2 2 139 239 ss7sigsvc ffff 140 nassvc2 2 140 240 ss7sigsvc ffff 141 nassvc2 2 141 241 ss7sigsvc ffff 142 nassvc2 2 142 242 ss7sigsvc ffff 143 nassvc2 2 143 243 ss7sigsvc ffff 144 nassvc2 2 144 244 ss7sigsvc ffff 145 nassvc2 2 145 245 ss7sigsvc ffff 146 nassvc2 2 146 246 ss7sigsvc ffff 147 nassvc2 2 147 247 ss7sigsvc ffff 148 nassvc2 2 148 248 ss7sigsvc ffff 149 nassvc2 2 149 249 ss7sigsvc ffff 150 nassvc2 2 150 250 ss7sigsvc ffff 151 nassvc2 2 151 251 ss7sigsvc ffff 152 nassvc2 2 152 252 ss7sigsvc ffff 153 nassvc2 2 153 253 ss7sigsvc ffff 154 nassvc2 2 154 254 ss7sigsvc ffff 155 nassvc2 2 155 255 ss7sigsvc ffff 156 nassvc2 2 156 256 ss7sigsvc ffff 157 nassvc2 2 157 257 ss7sigsvc ffff 158 nassvc2 2 158 258 ss7sigsvc ffff 159 nassvc2 2 159 259 ss7sigsvc ffff 160 nassvc2 2 160 260 ss7sigsvc ffff 161 nassvc2 2 161 261 ss7sigsvc ffff 162 nassvc2 2 162 262 ss7sigsvc ffff 163 nassvc2 2 163 263 ss7sigsvc ffff 164 nassvc2 2 164 264 ss7sigsvc ffff 165 nassvc2 2 165 265 ss7sigsvc ffff 166 nassvc2 2 166 266 ss7sigsvc ffff 167 nassvc2 2 167 267 ss7sigsvc ffff 168 nassvc2 2 168 268 ss7sigsvc ffff 169 nassvc2 2 169 269 ss7sigsvc ffff 170 nassvc2 2 170 270 ss7sigsvc ffff 171 nassvc2 2 171 271 ss7sigsvc ffff 172 nassvc2 2 172 272 ss7sigsvc ffff 173 nassvc2 2 173 273 ss7sigsvc ffff 174 nassvc2 2 174 274 ss7sigsvc ffff 175 nassvc2 2 175 275 ss7sigsvc ffff 176 nassvc2 2 176 276 ss7sigsvc ffff 177 nassvc2 2 177 277 ss7sigsvc ffff 178 nassvc2 2 178 278 ss7sigsvc ffff 179 nassvc2 2 179 279 ss7sigsvc ffff 180 nassvc2 2 180 280 ss7sigsvc ffff 181 nassvc2 2 181 281 ss7sigsvc ffff 182 nassvc2 2 182 282 ss7sigsvc ffff 183 nassvc2 2 183 283 ss7sigsvc ffff 184 nassvc2 2 184 284 ss7sigsvc ffff 185 nassvc2 2 185 285 ss7sigsvc ffff 186 nassvc2 2 186 286 ss7sigsvc ffff 187 nassvc2 2 187 287 ss7sigsvc ffff 188 nassvc2 2 188 288 ss7sigsvc ffff 189 nassvc2 2 189 289 ss7sigsvc ffff 190 nassvc2 2 190 290 ss7sigsvc ffff 191 nassvc2 2 191 291 ss7sigsvc ffff 192 nassvc2 2 192 292 ss7sigsvc ffff 193 nassvc3 3 193 293 ss7sigsvc ffff 194 nassvc3 3 194 294 ss7sigsvc ffff 195 nassvc3 3 195 295 ss7sigsvc ffff 196 nassvc3 3 196 296 ss7sigsvc ffff 197 nassvc3 3 197 297 ss7sigsvc ffff 198 nassvc3 3 198 298 ss7sigsvc ffff 199 nassvc3 3 199 299 ss7sigsvc ffff 200 nassvc3 3 200 300 ss7sigsvc ffff 201 nassvc3 3 201 301 ss7sigsvc ffff 202 nassvc3 3 202 302 ss7sigsvc ffff 203 nassvc3 3 203 303 ss7sigsvc ffff 204 nassvc3 3 204 304 ss7sigsvc ffff 205 nassvc3 3 205 305 ss7sigsvc ffff 206 nassvc3 3 206 306 ss7sigsvc ffff 207 nassvc3 3 207 307 ss7sigsvc ffff 208 nassvc3 3 208 308 ss7sigsvc ffff 209 nassvc3 3 209 309 ss7sigsvc ffff 210 nassvc3 3 210 310 ss7sigsvc ffff 211 nassvc3 3 211 311 ss7sigsvc ffff 212 nassvc3 3 212 312 ss7sigsvc ffff 213 nassvc3 3 213 313 ss7sigsvc ffff 214 nassvc3 3 214 314 ss7sigsvc ffff 215 nassvc3 3 215 315 ss7sigsvc ffff 216 nassvc3 3 216 316 ss7sigsvc ffff 217 nassvc3 3 217 317 ss7sigsvc ffff 218 nassvc3 3 218 318 ss7sigsvc ffff 219 nassvc3 3 219 319 ss7sigsvc ffff 220 nassvc3 3 220 320 ss7sigsvc ffff 221 nassvc3 3 221 321 ss7sigsvc ffff 222 nassvc3 3 222 322 ss7sigsvc ffff 223 nassvc3 3 223 323 ss7sigsvc ffff 224 nassvc3 3 224 324 ss7sigsvc ffff 225 nassvc3 3 225 325 ss7sigsvc ffff 226 nassvc3 3 226 326 ss7sigsvc ffff 227 nassvc3 3 227 327 ss7sigsvc ffff 228 nassvc3 3 228 328 ss7sigsvc ffff 229 nassvc3 3 229 329 ss7sigsvc ffff 230 nassvc3 3 230 330 ss7sigsvc ffff 231 nassvc3 3 231 331 ss7sigsvc ffff 232 nassvc3 3 232 332 ss7sigsvc ffff 233 nassvc3 3 233 333 ss7sigsvc ffff 234 nassvc3 3 234 334 ss7sigsvc ffff 235 nassvc3 3 235 335 ss7sigsvc ffff 236 nassvc3 3 236 336 ss7sigsvc ffff 237 nassvc3 3 237 337 ss7sigsvc ffff 238 nassvc3 3 238 338 ss7sigsvc ffff 239 nassvc3 3 239 339 ss7sigsvc ffff 240 nassvc3 3 240 340 ss7sigsvc ffff 241 nassvc3 3 241 341 ss7sigsvc ffff 242 nassvc3 3 242 342 ss7sigsvc ffff 243 nassvc3 3 243 343 ss7sigsvc ffff 244 nassvc3 3 244 344 ss7sigsvc ffff 245 nassvc3 3 245 345 ss7sigsvc ffff 246 nassvc3 3 246 346 ss7sigsvc ffff 247 nassvc3 3 247 347 ss7sigsvc ffff 248 nassvc3 3 248 348 ss7sigsvc ffff 249 nassvc3 3 249 349 ss7sigsvc ffff 250 nassvc3 3 250 350 ss7sigsvc ffff 251 nassvc3 3 251 351 ss7sigsvc ffff 252 nassvc3 3 252 352 ss7sigsvc ffff 253 nassvc3 3 253 353 ss7sigsvc ffff 254 nassvc3 3 254 354 ss7sigsvc ffff 255 nassvc3 3 255 355 ss7sigsvc ffff 256 nassvc3 3 256 356 ss7sigsvc ffff 257 nassvc3 3 257 357 ss7sigsvc ffff 258 nassvc3 3 258 358 ss7sigsvc ffff 259 nassvc3 3 259 359 ss7sigsvc ffff 260 nassvc3 3 260 360 ss7sigsvc ffff 261 nassvc3 3 261 361 ss7sigsvc ffff 262 nassvc3 3 262 362 ss7sigsvc ffff 263 nassvc3 3 263 363 ss7sigsvc ffff 264 nassvc3 3 264
When your file is complete, save it in the /opt/TransPath/etc/cust_specific directory by using filename.extension (for example, trunks.txt.) Then use the prov-add:files command to load the table.
|
Note In Cisco Media Gateway Controller software Release 7.4(x), save the file in the /opt/CiscoMGC/cust_specific directory. |
|
Caution When you import a trunk file, all the existing bearer channels are replaced by the bearer channels that you import. |
To provision the trunks:
Command/Action | Purpose | |||
|---|---|---|---|---|
|
|
| ||
|
|
| ||
|
|
| ||
|
|
|
To verify that you have added the trunks, exit MML and change to the /opt/TransPath/etc/CONFIG_LIB/CFG_dialcfg1 directory.
|
Note For Cisco Media Gateway Controller software Release 7.4(x), the bearChan.dat file is located in the /opt/CiscoMGC/etc/CONFIG_LIB/CFG_dialcfg1 directory. |
View the bearChan.dat file to ensure it contains the trunk information from the trunks.txt file you imported. The following example shows part of the bearChan.dat file:
machine-name% cd /opt/CiscoMGC/etc/CONFIG_LIB/CFG_dialcfg1 machine-name% more bearChan.dat 100 00130002 ffff 1 00140001 2 1 101 00130002 ffff 2 00140001 2 2 102 00130002 ffff 3 00140001 2 3 103 00130002 ffff 4 00140001 2 4 104 00130002 ffff 5 00140001 2 5 105 00130002 ffff 6 00140001 2 6 106 00130002 ffff 7 00140001 2 7 107 00130002 ffff 8 00140001 2 8 108 00130002 ffff 9 00140001 2 9 109 00130002 ffff a 00140001 2 a 110 00130002 ffff b 00140001 2 b 111 00130002 ffff c 00140001 2 c 112 00130002 ffff d 00140001 2 d 113 00130002 ffff e 00140001 2 e 114 00130002 ffff f 00140001 2 f 115 00130002 ffff 10 00140001 2 10 116 00130002 ffff 11 00140001 2 11 117 00130002 ffff 12 00140001 2 12 118 00130002 ffff 13 00140001 2 13 119 00130002 ffff 14 00140001 2 14 120 00130002 ffff 15 00140001 2 15
|
Note In software Release 7.4(x), you can retrieve and verify all trunks by entering the prov-rtrv:nailedtrnk:"all" command: |
machine-name mml> prov-rtrv:nailedtrnk:"all" Media Gateway Controller 2000-04-04 16:55:03 M RTRV "session=active:nailedtrnk" /* NAME SRCSVC SRCSPAN SRCTIMESLOT DSTSVC DSTSPAN DSTTIMESLOT ---- ------ ------ ----------- ------ ------- ----------- 100 ss7sigsvc ffff 1 nassvc1 2 1 101 ss7sigsvc ffff 2 nassvc1 2 2 102 ss7sigsvc ffff 3 nassvc1 2 3 103 ss7sigsvc ffff 4 nassvc1 2 4 104 ss7sigsvc ffff 5 nassvc1 2 5 105 ss7sigsvc ffff 6 nassvc1 2 6 106 ss7sigsvc ffff 7 nassvc1 2 7 107 ss7sigsvc ffff 8 nassvc1 2 8 108 ss7sigsvc ffff 9 nassvc1 2 9 109 ss7sigsvc ffff 10 nassvc1 2 10 110 ss7sigsvc ffff 11 nassvc1 2 11 111 ss7sigsvc ffff 12 nassvc1 2 12 112 ss7sigsvc ffff 13 nassvc1 2 13 113 ss7sigsvc ffff 14 nassvc1 2 14 114 ss7sigsvc ffff 15 nassvc1 2 15 115 ss7sigsvc ffff 16 nassvc1 2 16 116 ss7sigsvc ffff 17 nassvc1 2 17 117 ss7sigsvc ffff 18 nassvc1 2 18
Although you can add individual trunks with MML, doing so is not recommended if you have a large number of trunks to add. Using MML to add trunks requires that you enter the command to add individual trunks for each of the 264 trunks that you need to provision.
|
Note In software Release 7.4(x), you can add multiple trunks for a T1 or E1. See the following procedures for more information. |
To add individual trunks:
|
Note Adding individual trunks by using this command requires that you perform this action 24 times for each T1. |
To add multiple trunks in software Release 7.4(x):
Command/Action | Purpose | |
|---|---|---|
| mml>prov-add:nailedtrnk:name="100",srcsvc="ss7svc1", srctimeslot=1, dstsvc="signas1", dstspan=2,dsttimeslot=1, spansize=24,desc="Nailed trunk 1" |
The signaling controller provides the ability to create a dial plan to perform number analysis on both the A (calling) number and B (called) number. You can set up dial plans to perform routing, send calls to announcement servers, modify dialed digits, and perform other results.
You do not use the advanced features in the dial plan for the Cisco SS7 Interconnect for Access Servers Solution and the Cisco SS7 Interconnect for Voice Gateways Solution. In these solutions, the signaling controller routes calls directly over the IP network and does not perform routing or switching to
trunk groups.
In the Cisco SS7 Interconnect for Access Servers Solution, you might want to perform white and black list screening to include or exclude calls from certain numbers. You can provision white lists that specify allowed A-numbers (calling numbers) or B-numbers (called numbers). Black lists block specified A-numbers (calling numbers) or B-numbers (called numbers).
For instructions on using the CMM to provision a sample B white list, see "Configuring the B White List" section.
For information on using MML to provision black and white list screening, see Chapter 6, "Adding System Components with MML," in the Cisco Media Gateway Controller Software Release 7 Provisioning Guide.
The example used in this chapter features a continuous-service SC node. You must deploy the session to save it to the machine you are provisioning. The system then copies the files to the standby SC node.
|
Tips If you receive an error while trying to deploy, your connection between the active and standby SC nodes might be configured improperly. The communication between the active and standby SC nodes is configured in the XECfgParm.dat file on each machine. See the "Configuring the Execution Environment" section in Chapter 2 of Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information. |
Command/Action | Purpose | |
|---|---|---|
| machine-name mml> prov-dply Media Gateway Controller - VSC-01 2000-03-04 13:48:19 M COMPLD "PROV-DPLY" ; |
|
|
Note Restart the standby server after reconfiguration to apply changes. |
To verify that you have deployed the configuration, enter the prov-rtrv:all command and verify that the active configuration shown is the one you provisioned:
machine-name mml> prov-rtrv:all Media Gateway Controller - VSC-01 2000-03-04 13:50:06 M RTRV "session=active:all" /* NAME Parent Name TID Description ---- ----------- --- ----------- "encard1" "VSC-01" CARD "Ethernet Card 1" "encard2" "VSC-01" CARD "Ethernet Card 2" "enetif1" "encard1" ENETIF "Ethernet interface for Card 1" "enetif2" "encard2" ENETIF "Ethernet interface for Card 2" "ls01" "apc1" LNKSET "Linkset from signaling controller to STP A" "ls02" "apc2" LNKSET "Linkset from signaling controller to STP B" "iplink1" "nassvc1" IPLNK "IP link for NAS 1" "iplink2" "nassvc2" IPLNK "IP link for NAS 2" "iplink3" "nassvc3" IPLNK "IP link for NAS 3" "iplink4" "nassvc1" IPLNK "IP link 2 for NAS 1" "iplink5" "nassvc2" IPLNK "IP link 2 for NAS 2" "iplink6" "nassvc3" IPLNK "IP link 2 for NAS 3" "ss7route1" "VSC-01" SS7ROUTE "Route 1 to PSTN Switch A through LS1" "ss7route2" "VSC-01" SS7ROUTE "Route 2 to PSTN Switch A through LS1" "opc" "VSC-01" PTCODE "Origination point code" "dpc1" "VSC-01" PTCODE "DPC of PSTN Switch A" "nassvc1" "nas1" NASPATH "Signaling service for NAS 1" "nassvc2" "nas2" NASPATH "Signaling service for NAS 2" "nassvc3" "nas3" NASPATH "Signaling service for NAS 3" <Press Enter to continue OR Press * and Enter to quit output of command> "ss7sigsvc" "dpc1" SS7PATH "SS7 service to PSTN Switch A" "nas1" "VSC-01" EXTNODE "NAS 1" "nas2" "VSC-01" EXTNODE "NAS 2" "nas3" "VSC-01" EXTNODE "NAS 3" "c7iplink1" "ls01" C7IPLNK "Link 1 in Linkset 1" "c7iplink2" "ls02" C7IPLNK "Link 1 in Linkset 1" "c7iplink3" "ls01" C7IPLNK "Link 1 in Linkset 2" "c7iplink4" "ls02" C7IPLNK "Link 2 in Linkset 2" "apc1" "VSC-01" APC "APC for STP A" "apc2" "VSC-01" APC "APC for STP B" "subsys1" "VSC-01" SS7SUBSYS "Route between STP A and STP B" */ ;
You can create a file of MML provisioning commands for use as a batch file. All commands are in a single ASCII text file; when they are read by MML, the commands are executed sequentially.
|
Note It is important that the MML provisioning commands be in the correct provisioning sequence based on component dependencies. For example, a line interface cannot be provisioned before the card. |
|
Tips You can create batch files to define complete systems or modify parts of an existing system. |
To create a batch file, use an ASCII text editor to create a new file with one MML command on each line, ending with a carriage return. You can use any name for the file (follow UNIX file naming conventions), and you can store it in any location. However, the file must be accessible on the machine where you run MML sessions. The following example shows a sample MML batch file for the configuration in this chapter.
prov-sta::srcver="new",dstver="dialcfg1"; prov-add:ptcode:name="opc",netaddr="171.1.4",netind=2,desc="Origination point code"; prov-add:ptcode:name="dpc1",netaddr="171.1.3",netind=2,desc="DPC of PSTN Switch A"; prov-add:apc:name="apc1",netaddr="171.16.1",desc="APC for STP A"; prov-add:apc:name="apc2",netaddr="171.16.2",desc="APC for STP B"; prov-add:lnkset:name="ls01",apc="apc1",type="IP",proto="SS7-ANSI",desc="Linkset from signaling controller to STP A"; prov-add:lnkset:name="ls02",apc="apc2",type="IP",proto="SS7-ANSI",desc="Linkset from signaling controller to STP B"; prov-add:ss7subsys:name="subsys1",svc="apc1",matedapc="apc2",proto="SS7-ANSI",pri=3,ssn=0,desc="Route between STP A and STP B"; prov-add:ss7route:name="ss7route1",opc="opc",dpc="dpc1",lnkset="ls01",pri=1,desc="Route 1 to PSTN Switch A through LS1"; prov-add:ss7route:name="ss7route2",opc="opc",dpc="dpc1",lnkset="ls02",pri=1,desc="Route 2 to PSTN Switch A through LS1"; prov-add:ss7path:name="ss7sigsvc",mdo="ANSISS7_STANDARD",dpc="dpc1",desc="SS7 service to PSTN Switch A"; prov-add:card:name="encard1",type="EN",slot=0,desc="Ethernet Card 1"; prov-add:card:name="encard2",type="EN",slot=1,desc="Ethernet Card 2"; prov-add:enetif:name="enetif1",card="encard1",desc="Ethernet interface for Card 1"; prov-add:enetif:name="enetif2",card="encard2",desc="Ethernet interface for Card 2"; prov-add:c7iplnk:name="c7iplink1",if="enetif1",ipaddr="IP_Addr1",port=7000,peeraddr="175.30.241.27",peerport=32767,pri=1,slc=0,lnkset="ls01",desc="Link 1 in Linkset 1"; prov-add:c7iplnk:name="c7iplink2",if="enetif2",ipaddr="IP_Addr2",port=7000,peeraddr="175.30.238.28",peerport=32767,pri=1,slc=1,lnkset="ls02",desc="Link 2 in Linkset 1"; prov-add:c7iplnk:name="c7iplink3",if="enetif1",ipaddr="IP_Addr1",port=7000,peeraddr="175.30.241.27",peerport=32767,pri=1,slc=0,lnkset="ls01",desc="Link 1 in Linkset 2"; prov-add:c7iplnk:name="c7iplink4",if="enetif2",ipaddr="IP_Addr2",port=7000,peeraddr="175.30.238.28",peerport=32767,pri=1,slc=1,lnkset="ls02",desc="Link 2 in Linkset 2"; prov-add:extnode:name="nas1",desc="NAS 1"; prov-add:extnode:name="nas2",desc="NAS 2"; prov-add:extnode:name="nas3",desc="NAS 3"; prov-add:naspath:name="nassvc1",extnode="nas1",mdo="BELL_1268_C3",desc="Signaling service for NAS 1"; prov-add:naspath:name="nassvc2",extnode="nas2",mdo="BELL_1268_C3",desc="Signaling service for NAS 2"; prov-add:naspath:name="nassvc3",extnode="nas3",mdo="BELL_1268_C3",desc="Signaling service for NAS 3"; prov-add:iplnk:name="iplink1",if="enetif1",ipaddr="IP_Addr1",port=6001,peeraddr="172.16.0.2",peerport=6001,svc="nassvc1",desc="IP link for NAS 1"; prov-add:iplnk:name="iplink2",if="enetif1",ipaddr="IP_Addr1",port=6001,peeraddr="172.16.0.3",peerport=6001,svc="nassvc2",desc="IP link for NAS 2"; prov-add:iplnk:name="iplink3",if="enetif1",ipaddr="IP_Addr1",port=6001,peeraddr="172.16.0.4",peerport=6001,svc="nassvc3",desc="IP link for NAS 3"; prov-add:iplnk:name="iplink4",if="enetif2",ipaddr="IP_Addr2",port=6001,peeraddr="172.16.0.2",peerport=6001,svc="nassvc1",desc="IP link 2 for NAS 1"; prov-add:iplnk:name="iplink5",if="enetif2",ipaddr="IP_Addr2",port=6001,peeraddr="172.16.0.3",peerport=6001,svc="nassvc2",desc="IP link 2 for NAS 2"; prov-add:iplnk:name="iplink6",if="enetif2",ipaddr="IP_Addr2",port=6001,peeraddr="172.16.0.4",peerport=6001,svc="nassvc3",desc="IP link 2 for NAS 3"; numan-add:dialplan:custgrpid="t778"; numan-add:awhite:custgrpid="t778",cli="7034843000"; numan-dlt:awhite:custgrpid="t778",cli="7034843001"; prov-cpy;
The first command starts a provisioning session, and the last command terminates and commits the provisioning session. If you are not ready to commit a session, use the prov-stp command to save and stop the provisioning session.
The prov-cpy or prov-dply command makes the provisioning session active and automatically stops the provisioning session.
To process the batch file, use the mml -b path/filename UNIX command.
Command/Action | Purpose | |
|---|---|---|
|
|
|
After you enter the command, MML displays the result of each command as it is executed. When the batch file is done, the MML session is closed.
To verify that you have deployed the configuration, log in and begin an MML session. Enter the prov-rtrv:all command and verify that the active configuration shown is the one you provisioned.
|
Tips MML provides a log function that records the MML commands and responses for you in a log file. If you start this function before you start the provisioning session and stop it after you stop the provisioning session, you can let the batch file run unattended and then check the log file later for any error messages. The log command is called diaglog. For more information on using this command, refer to the Cisco Media Gateway Software Release 7 Reference Guide. |
Posted: Tue Aug 8 05:25:55 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.