Cisco PGW 2200 Signaling Mode Design Guide

Transcription

1 This guide describes how to provision a signaling-mode PGW 2200 and other related devices (shown in Figure 1). The document describes a sample configuration (for illustration purposes only). Your configuration will vary and depend on your own network. This guide presents two ways of provisioning with MML: Using MML commands individually to provision your system. (This can be time consuming if you have a large configuration.) Creating a simple MML batch file in ASCII format and processing it with MML. To skip directly to the MML batch file used to provision the sample configuration, see the Creating and Processing an MML Batch File for Provisioning section on page 51. Figure 1 shows an overview of Cisco PGW 2200 signaling mode solution. Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA 2008 Cisco Systems, Inc. All rights reserved.

2 Provisioning Outline Figure 1 PGW 2200 Signaling Mode Solution LAN switches Cisco ITP-L PGW 2200 Cisco ITP-L PSTN switch Cisco AS5X00 Cisco AS5X00 Telephone exchange Cisco AS5X00 Gateway router QoS packet network IMT = InterMachine Trunk Caution Do not use the sample values in this document 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. Provisioning Outline Perform the following steps to provision the sample Cisco SS7 Interconnect for Access Servers Solution. Step Section and Page Provision SS7 signaling routes Step 1 Add the OPC 1 in your network. Adding the OPC, page 12 Step 2 Add the DPC 2 to identify the destination switch. Adding the DPC, page 14 Step 3 Step 4 Add the APCs 3 to identify the s 4 with which the signaling controller communicates signaling information. Add linksets to connect the Cisco ITP-Ls 5 to the s. Adding the APCs, page 16 Adding Linksets, page 18 2

3 Provisioning Worksheet Step Section and Page Step 5 Add the SS7 subsystem to identify the mated s. Adding the SS7 Subsystem, page 22 Step 6 Add the SS7 routes for each signaling path from the signaling controller to the destination switch. Adding the SS7 Signaling Service, page 24 Step 7 Add the SS7 signaling service from the PGW to the destination switch. Adding the SS7 Signaling Service, page 24 Provision signaling links Step 1 Add the external nodes for Cisco ITP-Ls. Adding ITP-L External Nodes, page 26 Step 2 (Optional) Add IP routes. Adding IP Routes to Cisco ITP-Ls (Optional), page 28 Step 3 Add sessionsets for PGW-ITP-L communication. Adding Sessionsets for PGW-ITP-L Communication, page 30 Step 4 Add C7 IP Links to Cisco ITP-Ls Adding C7 IP Links to Cisco ITP-Ls, page 32 Provision NAS 6 links Step 1 Add external nodes for the NASes in your network. Adding NAS External Nodes, page 35 Step 2 Add NAS signaling services for each NAS. Adding NAS Signaling Services, page 37 Step 3 Add IP links for each NAS to PGW. Adding IP Links, page 39 Provision trunks Step 1 Create the trunk file and add trunks from each NAS to the signaling controller. Using a Text File to Add Trunks, page 42 Step 2 Import the trunk file. Using a Text File to Add Trunks, page 42 Deploy the session 1. OPC = origination point code 2. DPC = destination point code 3. APCs = adjacent point codes 4. s = Signal Transfer Points 5. Cisco ITP-Ls = Cisco IP Transfer Point - LinkExtender (previously named Cisco Signaling Link Terminal (SLT)) 6. NAS = 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. Provisioning Worksheet Table 1 shows a provisioning worksheet for the sample configuration shown in the document. The parameter values in the Parameters column are for illustration purposes only. Use the real parameter values to replace them when you perform the configuration. 3

4 Provisioning Worksheet Table 1 Provisioning Worksheet Component MML Name Description Parameters OPC opc Origination point code netaddr: netind: 2 (national network) type:trueopc DPC dpc1 DPC of PSTN Switch A netaddr: netind: 2 (national network) APC apc1 APC for A netaddr: netind: 2 (national network) APC apc2 APC for B netaddr: netind: 2 (national network) Linkset ls01 Linkset from signaling apc: apc1 controller to A type: IP Linkset ls02 Linkset from signaling controller to B SS7 route ss7route1 Route 1 to PSTN Switch A through LS1 SS7 route ss7route2 Route 2 to PSTN Switch A through LS2 proto: SS7-ANSI apc: apc2 type: IP proto: SS7-ANSI opc: opc dpc: dpc1 lnkset: ls01 pri: 1 opc: opc dpc: dpc1 lnkset: ls02 pri: 1 SS7 subsystem subsys1 Mate A to B svc: apc1 matedapc: apc2 proto: SS7-ANSI pri: 3 opc: opc SS7 subsystem subsys2 Mate B to A svc: apc2 matedapc: apc1 proto: SS7-ANSI pri: 3 opc: opc 4

5 Provisioning Worksheet Table 1 Provisioning Worksheet (continued) Component MML Name Description Parameters SS7 signaling service ITP-L external node ITP-L external node (Optional) ITP-L IP route (Optional) ITP-L IP route (Optional) ITP-L IP route ss7sigsvc SS7 signaling path to PSTN Switch A mdo: ANSISS7_STANDARD opc: opc dpc: dpc1 custgrpid: d125 itp-l-1 External node ITP-L-1 type: SLT isdnsigtype: N/A group: 0 itp-l-2 External node ITP-L-2 type: SLT iproute-1-toitp-l-1 iproute-2-toitp-l-1 iproute-1-toitp-l-2 IP route 1 from PGW to ITP-L-1. The ITP-L IP route is required when the PGW and Cisco ITP-Ls are not in the same subnet. The PGW communicates with the ITP-L with the help of a gateway provisioned in the nexthop parameter. IP route 2 from PGW to ITP-L-1. The ITP-L IP route is required when the PGW and Cisco ITP-Ls are not in the same subnet. The PGW communicates with the ITP-L with the help of a gateway provisioned in nexthop parameter. IP route 1 from PGW to ITP-L-2. The ITP-L IP route is required when PGW and Cisco ITP-Ls are not in the same subnet. The PGW communicates with the ITP-L with the help of a gateway provisioned in nexthop parameter. isdnsigtype: N/A group: 0 dest: nexthop: (in the same subnet with IP_Addr1) ipaddr: IP_Addr1 pri: 1 dest: nexthop: (in the same subnet with IP_Addr2) ipaddr: IP_Addr2 pri: 1 dest: nexthop: (in the same subnet with IP_Addr1) ipaddr: IP_Addr1 pri: 1 5

6 Provisioning Worksheet Table 1 Provisioning Worksheet (continued) Component MML Name Description Parameters (Optional) ITP-L IP route iproute-2-toitp-l-2 IP route 2 from PGW to ITP-L-2. The ITP-L IP route is required when the PGW and Cisco ITP-Ls are not in the same subnet. The PGW communicates with the ITP-L with the help of a gateway provisioned in nexthop parameter. dest: nexthop: (in the same subnet with IP_Addr2) ipaddr: IP_Addr2 pri: 1 Sessionset sessionset-1 Sessionset for itp-l-1 port: 7000 peeraddr1 = peeraddr2 = peerport: 7000 ipaddr1: IP_Addr1 ipaddr2: IP_Addr2 iproute1:iproute-1-to-itp-l-1 iproute2:iproute-2-to-itp-l-1 extnode: itp-l-1 type: BSMV0 Sessionset sessionset-2 Sessionset for itp-l-2 port: 7000 peeraddr1 = peeraddr2 = peerport: 7000 ipaddr1: IP_Addr1 ipaddr2: IP_Addr2 iproute1:iproute-1-to-itp-l-2 iproute2:iproute-2-to-itp-l-2 extnode: itp-l-2 type: BSMV0 C7 IP link c7iplink1 Link 1 in Linkset 1 pri: 1 slc: 0 lnkset: ls01 sessionset: sessionset-1 timeslot: 0 6

7 Provisioning Worksheet Table 1 Provisioning Worksheet (continued) Component MML Name Description Parameters C7 IP link c7iplink2 Link 2 in Linkset 1 pri: 1 slc: 1 lnkset: ls01 sessionset: sessionset-2 timeslot: 0 C7 IP link c7iplink3 Link 1 in Linkset 2 pri: 1 slc: 0 lnkset: ls02 sessionset: sessionset-1 timeslot: 0 C7 IP link c7iplink4 Link 2 in Linkset 2 pri: 1 slc: 1 lnkset: ls02 sessioinset: sessionset-2 timeslot: 0 NAS external nas1 NAS 1 type: AS5300 node isdnsigtype: N/A NAS external node NAS external node NAS signaling service NAS signaling service NAS signaling service group: 0 nas2 NAS 2 type: AS5300 isdnsigtype: N/A group: 0 nas3 NAS 3 type: AS5300 nassvc1 nassvc2 nassvc3 Signaling service for NAS 1 Signaling service for NAS 2 Signaling service for NAS 3 isdnsigtype: N/A group: 0 extnode: nas1 MDO: BELL_1268_C2 extnode: nas2 MDO: BELL_1268_C2 extnode: nas3 MDO: BELL_1268_C2 7

8 Provisioning Worksheet Table 1 Provisioning Worksheet (continued) Component MML Name Description Parameters IP link nas1link1 IP link 1 for NAS 1 svc: nassvc1 ipaddr: IP_Addr1 port: 3001 peeraddr: peerport: 3001 pri: 1 IP link nas1link2 IP link 2 for NAS 1 svc: nassvc1 ipaddr: IP_Addr2 port: 3001 peeraddr: peerport: 3001 pri: 1 IP link nas2link1 IP link 1 for NAS 2 svc: nassvc2 ipaddr: IP_Addr1 port: 3001 peeraddr: peerport: 3001 pri: 1 IP link nas2link2 IP link 2 for NAS 2 svc: nassvc2 ipaddr: IP_Addr2 port: 3001 peeraddr: peerport: 3001 pri: 1 8

9 Starting the Provisioning Session Table 1 Provisioning Worksheet (continued) Component MML Name Description Parameters IP link nas3link1 IP link 1 for NAS 3 svc: nassvc3 ipaddr: IP_Addr1 port: 3001 peeraddr: peerport: 3001 pri: 1 IP link nas3link2 IP link 2 for NAS 3 svc: nassvc3 ipaddr: IP_Addr2 port: 3001 peeraddr: peerport: 3001 pri: 1 Starting the Provisioning Session Log in to the PGW and start an MML session. For more information on MML commands, see the Cisco Media Gateway Controller Software Release 9 MML Command Reference at Caution Do not log in as root when starting MML. If you log in as root, you cannot start an MML session. To start an MML session: Step 1 Step 2 Log in to the signaling controller as a user who is a member of the mgcgrp group. Enter mml: machine-name% mml copyright , Cisco Systems, Inc. machine-name mml> You can still log in if another session is running: machine-name% mml copyright , Cisco Systems, Inc. Session 1 is in use, using session 2 machine-name mml> Step 3 Start a provisioning session by entering the prov-sta::srcver="new",dstver="ver1" command: machine-name mml> prov-sta::srcver="new",dstver="ver1" 9

10 MML Tips Media Gateway Controller :00:57 "PROV-STA" machine-name mml> This starts a new provisioning session ( new ), names it CFG_ver1, and saves the configuration files in /opt/ciscomgc/etc/config_lib/cfg_ver1. Note To modify an existing configuration and save it as another version, use the prov-sta command. prov-sta::srcver= ver1, dstver= ver2. This command starts a provisioning session, opens the existing configuration named ver1, and saves the configuration as ver2. Tip If another provisioning session is running, you cannot start a provisioning session. You receive an error message like the one shown in Example 1. Example 1 Provisioning Session Error machine-name mml> prov-sta::srcver="new",dstver="ver1" Media Gateway Controller :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 :03:07 "session=ver1:session" Session ID = mml2 SRCVER = new DSTVER = ver1 This example shows that an active provisioning session named ver1 is in use. See the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for more information on provisioning with MML and general provisioning steps. The Provisioning Guide is at MML Tips MML commands use the following syntax: command_name:[target][, target][, target...][:parameter_list][comments] 10

11 MML Tips When entering MML commands, remember the following: In general, MML commands are not case sensitive. However, file names are case sensitive when used as arguments in MML commands (for example, TKGFile, BCFile, RoutingFile). Use only one MML command on each line. Anything entered after a semicolon () is treated as a comment (this is primarily useful for MML command scripts). Do not use punctuation (such as the period character) for target names for example, do not use test.log as a logging destination. After you start a provisioning session, MML displays COMPLD, indicating success. The COMPLD message is displayed after successful commands. For failed commands, MML displays DENY. If the session continues without activity for 5 more minutes, it terminates: POM session is idle, the session will be closed in 5 min. if it continues to be idle If a session is inactive for 35 minutes, this warning is displayed: POM session has been closed as it was idle for 35 min. As many as 12 MML sessions can exist at any given time however, only one provisioning session is allowed. You can create an ASCII text file for batch processing of provisioning commands. You can create batch files for individual segments of provisioned data. During batch file execution, each MML command response echoes to the terminal. You can log command responses for later review so that the file can run unattended. Place quotation marks around all value strings in your commands. For example, card="interface1". The keyword card does not have to be enclosed in quotation marks. The value Interface1 is being assigned to keyword card and must be enclosed in quotations. Press Tab key when you are typing an MML command to get the hints and the tips for the command. To obtain on-line help in an MML session, enter help at the command prompt. For more information on MML commands, see the Cisco Media Gateway Controller Software Release 9 MML Command Reference at Tip To repeat the last MML command you entered, use the up arrow. To scroll through all previously entered MML commands, continue to use the up arrow. To modify and reenter a previously entered command, use the up arrow to display the command and then the left- and right-arrows, Backspace, Delete, and alphanumeric keys to edit the command. Press Enter to reenter the command. Note Many procedures in this document refer to sections in Cisco Media Gateway Controller Software Release 9 Provisioning Guide. Keep that book handy when performing the procedures in this chapter. 11

12 Provisioning SS7 Signaling Routes Provisioning SS7 Signaling Routes The SS7 signaling route is the path from the Cisco MGC host to a service switching point (SSP) through the Cisco ITP-Ls and signal transfer points (s). 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: OPC Origination point code or the point code of the Cisco MGC in your network DPC Destination point code or the point code of the PSTN switch A to which you are connecting APCs Adjacent point codes or the point codes of the adjacent s Linksets SS7 subsystems (to identify mated s) SS7 routes SS7 signaling services For more information on configuring SS7 signaling routes, see the Cisco Media Gateway Controller Software Release 9 Provisioning Guide at Adding the OPC A point code is an SS7 network address that identifies an SS7 network node, such as an or an SSP. Note ITU point codes contain 14 bits, and North American point codes contain 24 bits. Use the correct format when you add the origination point code (OPC). Use the following command to add the point code for the PGW shown in the shaded area in Figure 2. 12

13 Provisioning SS7 Signaling Routes Figure 2 Adding the OPC LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Command/Action machine-name mml> prov-add:opc:name="opc", netaddr=" ",netind=2,type="trueopc",de sc="origination point code" Media Gateway Controller :04:48 "opc" Purpose Adds a point code and assigns the name opc to the PGW Verifying the Added OPC To verify that you have added the OPC, use the prov-rtrv:opc command: machine-name mml> prov-rtrv:opc:name="opc" Media Gateway Controller :05:44 "session=ver1:opc" NAME = opc DESC = origination point code 13

14 Provisioning SS7 Signaling Routes NETADDR = NETIND = 2 TYPE = TRUEOPC You can retrieve all the OPCs by using the prov-rtrv:opc:"all" command, as shown in Example 2. Example 2 Retrieving All OPCs machine-name mml> prov-rtrv:opc:"all" Media Gateway Controller :05:32 "session=ver1:opc" NAME NETADDR NETIND TYPE TRUEOPC opc TRUEOPC Adding the DPC Use the following command to add the point code for the PSTN switch A, shown in the shaded area in Figure 3. 14

15 Provisioning SS7 Signaling Routes Figure 3 Adding the DPC LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Command/Action machine-name mml> prov-add:dpc:name="dpc1", netaddr=" ",netind=2,desc="dpc of PSTN Switch A" Media Gateway Controller :08:41 "dpc" Purpose Adds a point code and assigns the name dpc1 to switch Verifying the Added DPC To verify that you have added the DPC, use the prov-rtrv:dpc command: machine-name mml> prov-rtrv:dpc:name="dpc1" Media Gateway Controller :09:25 "session=ver1:dpc" NAME = dpc1 DESC = DPC of PSTN Switch A 15

16 Provisioning SS7 Signaling Routes NETADDR = NETIND = 2 You can retrieve all the DPCs by using the prov-rtrv:dpc:"all" command, as shown in Example 3. Example 3 Retrieving All DPCs machine-name mml> prov-rtrv:dpc:"all" Media Gateway Controller :10:47 "session=ver1:dpc" NAME NETADDR NETIND dpc Adding the APCs Use the following procedure to add the adjacent point codes (APCs) for the s shown in the shaded area in Figure 4. Note The sample configuration in this chapter uses A-links from the s for signaling to the Cisco ITP-Ls. If you have a configuration where F-links come directly from the SSP to the Cisco ITP-Ls, you do not need to add APCs. 16

17 Provisioning SS7 Signaling Routes Figure 4 Adding the APCs LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Step 2 Command/Action machine-name mml> prov-add:apc:name="apc1", netaddr=" ",netind=2,desc="apc for A" Media Gateway Controller :11:51 "apc" machine-name mml> prov-add:apc:name="apc2", netaddr=" ",netind=2,desc="apc for B" Media Gateway Controller :12:36 "apc" Purpose Adds a point code and assigns the name apc1 to A, Adds a point code and assigns the name apc2 to B, Verifying the Added APCs To verify that you have entered the APCs, use the prov-rtrv:apc command for each APC. For example, to verify that the first APC was added: machine-name mml> prov-rtrv:apc:name="apc1" Media Gateway Controller :13:54 17

18 Provisioning SS7 Signaling Routes "session=ver1:apc" NAME = apc1 DESC = APC for A NETADDR = NETIND = 2 You can retrieve all the APCs by using the prov-rtrv:apc:"all" command, as shown in Example 4. Example 4 Retrieving All APCs machine-name mml> prov-rtrv:apc:"all" Media Gateway Controller :45:12 "session=ver1:apc" NAME NETADDR NETIND apc apc Adding Linksets A linkset is a logical set of one or more links originating from an SS7 node () and connecting to an adjacent node. In the example used in this section, the linkset contains communication links that connect from the signaling controller to an adjacent. You must provision one linkset for each connection through the to the signaling controller. The shaded area in Figure 5 shows the linksets you provision in this example. 18

19 Provisioning SS7 Signaling Routes Figure 5 Adding Linksets LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Step 2 Command/Action machine-name mml> prov-add:lnkset:name="ls01", apc="apc1",type="ip",proto="ss7-ansi",desc="li nkset from PGW to A" Media Gateway Controller :16:42 "lnkset" machine-name mml> prov-add:lnkset:name="ls02", apc="apc2",type="ip",proto="ss7-ansi",desc="li nkset from PGW to B" Media Gateway Controller :17:16 "lnkset" Purpose Defines a linkset ls01 to A. Defines a linkset ls02 to B. 19

20 Provisioning SS7 Signaling Routes Verifying the Added Linksets To verify that you have entered the linksets, use the prov-rtrv:lnkset command for each linkset. For example, to verify that the first linkset was added: machine-name mml> prov-rtrv:lnkset:name="ls01" Media Gateway Controller :18:40 "session=ver1:lnkset" NAME = ls01 DESC = Linkset from PGW to A APC = apc1 PROTO = SS7-ANSI TYPE = IP You can retrieve all linksets by using the prov-rtrv:lnkset: all command, as shown in Example 5. Example 5 Retrieving All Linksets machine-name mml> prov-rtrv:lnkset:"all" Media Gateway Controller :20:43 "session=ver1: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 the Adding C7 IP Links to Cisco ITP-Ls section on page 32. Adding SS7 Routes An SS7 route is a path through a linkset between the PGW and another PGW or TDM switch. In this example, the SS7 routes indicate the linksets that carry SS7 signals between the PGW and the PSTN switch A. You must add an SS7 route for each signaling path from the PGW to the PSTN switch A. You provision a route for each linkset. The shaded area in Figure 6 shows the SS7 routes that you provision for the example that follows. 20

21 Provisioning SS7 Signaling Routes Figure 6 Adding SS7 Routes LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Step 2 Command/Action machine-name mml> prov-add:ss7route:name= "ss7route1",opc="opc",dpc="dpc1",lnkset="l s01",pri=1,desc="route 1 to PSTN Switch A through LS01" Media Gateway Controller :24:14 "ss7route" machine-name mml> prov-add:ss7route:name= "ss7route2",opc="opc",dpc="dpc1",lnkset="l s02",pri=1,desc="route 2 to PSTN Switch A through LS02" Media Gateway Controller :25:44 "ss7route" Purpose Defines an SS7 route from the PGW (opc) to PSTN Switch A through the previously defined linkset through A (ls01). Defines an SS7 route from the PGW (opc) to PSTN Switch A through the previously defined linkset through B (ls02). 21

22 Provisioning SS7 Signaling Routes Verifying the Added SS7 Routes To verify that you have entered the SS7 routes, use the prov-rtrv:ss7route command for each SS7 route. For example, to verify that the first SS7 route was added: machine-name mml> prov-rtrv:ss7route:name="ss7route1" Media Gateway Controller :32:21 "session=ver1:ss7route" NAME = ss7route1 DESC = Route 1 to PSTN Switch A through LS01 OPC = opc DPC = dpc1 LNKSET = ls01 PRI = 1 You can retrieve all SS7 routes by using the prov-rtrv:ss7route: all command, as shown in Example 6. Example 6 Retrieving All SS7 Routes machine-name mml> prov-rtrv:ss7route:"all" Media Gateway Controller :01:18 "session=ver1:ss7route" NAME OPC DPC LINKSET PRI ss7route1 opc dpc1 ls01 1 ss7route2 opc dpc1 ls02 1 Adding the SS7 Subsystem You must add an SS7 subsystem that identifies each pair of mated s. This allows the PGW to route traffic over the C-links between the s in case of a failure between one of the s and an endpoint. The shaded area in Figure 7 shows the s you must connect ( A and B). 22

23 Provisioning SS7 Signaling Routes Figure 7 Adding the SS7 Subsystem LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Step 2 Command/Action machine-name mml>prov-add:ss7subsys:name= "subsys1",desc="mate A to B", svc="apc1",proto="ss7-ansi",matedapc="apc2", pri=3,opc= opc Media Gateway Controller :21:56 "ss7subsys" machine-name mml>prov-add:ss7subsys:name= "subsys2",desc="mate B to A", svc="apc2",proto="ss7-ansi",matedapc="apc1", pri=3,opc= opc Media Gateway Controller :21:56 "ss7subsys" Purpose Defines a mated subsystem from A to B. Defines a mated subsystem from B to A. 23

24 Provisioning SS7 Signaling Routes Verifying the Added SS7 Subsystem To verify that you have added the SS7 subsystem, use the prov-rtrv:ss7subsys command: machine-name mml> prov-rtrv:ss7subsys:name="subsys1" Media Gateway Controller :22:44 "session=ver1:ss7subsys" NAME = subsys1 DESC = Mate A to B SVC = apc1 PRI = 3 MATEDAPC = apc2 SSN = 0 PROTO = SS7-ANSI SCPIND = 0 TRANSPROTO = SCCP OPC = opc SUAKEY = REMOTESSN = 0 You can retrieve all SS7 subsystems by entering the prov-rtrv:ss7subsys:"all" command, as shown in Example 7. Example 7 Retrieving All SS7 Subsystems machine-name mml> prov-rtrv:ss7subsys:"all" Media Gateway Controller :01:18 "session=ver1:ss7subsys" NAME SVC PRI MATEDAPC LOCALSSN PROTO SCPIND TRANSPROTO OPC SUAKEY REMOTESSN subsys1 apc1 3 apc2 0 SS7-ANSI 0 SCCP opc 0 subsys2 apc2 3 apc1 0 SS7-ANSI 0 SCCP opc 0 Adding the SS7 Signaling Service The SS7 signaling service specifies the path and the protocol variant that the PGW uses to communicate with a remote switch (SSP) that sends bearer traffic to the NASs. You must add an SS7 signaling service from the PGW to the PSTN switch. The shaded area in Figure 8 shows the signaling service you are adding. 24

25 Provisioning SS7 Signaling Routes Figure 8 Adding the SS7 Signaling Service LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Command/Action machine-name mml>prov-add:ss7path:name= "ss7sigsvc",mdo="ansiss7_standard",opc= opc, dpc="dpc1",custgrpid="d125",desc="ss7 signaling path to PSTN Switch A" Media Gateway Controller :21:04 "ss7path" Purpose Defines the SS7 path and protocol between the PGW and PSTN Switch A. Note We recommend that you provision a customer group ID for your SS7 signaling service, even if you are not planning on currently using the screening tools. This is because once the SS7 signaling service is placed in service, you would have to take it out-of-service to add a customer group ID. 25

26 Provisioning Signaling Links Verifying the Added SS7 Signaling Service To verify that you have added the SS7 signaling service, use the prov-rtrv:ss7path command: mml> prov-rtrv:ss7path:name="ss7sigsvc" Media Gateway Controller :22:12 "session=ver1:ss7path" NAME = ss7sigsvc DESC = SS7 signaling path to PSTN Switch A MDO = ANSISS7_STANDARD CUSTGRPID = d125 SIDE = network DPC = dpc1 OPC = opc M3UAKEY = ORIGLABEL = TERMLABEL = Provisioning Signaling Links You must provision links for all physical connections bearing signals that enter and exit the PGW. This includes SS7 signals from the SSP (PSTN Switch A) and signals to the NASs. You must add the following components: ITP-L external node IP Routes to the Cisco ITP-Ls Sessionsets for PGW-ITP-L communication C7 IP links to the Cisco ITP-Ls Adding ITP-L External Nodes You must add an ITP-L external node for each ITP-L in your network. The shaded areas in Figure 9 show the ITP-L external nodes you are adding. In this configuration there are two ITP-Ls. 26

27 Provisioning Signaling Links Figure 9 Adding ITP-L External Nodes LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network Step 1 Step 2 Command/Action machine-name mml>prov-add:extnode:name= "itp-l-1",desc="external Node ITP-L-1", type="slt",isdnsigtype="n/a",group=0 Media Gateway Controller :21:04 "extnode" machine-name mml>prov-add:extnode:name= "itp-l-2",desc="external Node ITP-L-2", type="slt",isdnsigtype="n/a",group=0 Media Gateway Controller :21:04 "extnode" Purpose Adds an ITP-L external node itp-l-1. Adds an ITP-L external node itp-l-1. Verifying the Added ITP-L External Nodes To verify that you have added the ITP-L external nodes, use the prov-rtrv:extnode command. For example, to verify that you have added the first ITP-L node: 27

28 Provisioning Signaling Links mml> prov-rtrv:extnode:name="itp-l-1" Media Gateway Controller :22:12 "session=ver1:extnode" NAME = itp-l-1 DESC = External Node itp-l-1 TYPE = SLT ISDNSIGTYPE = N/A GROUP = 0 You can retrieve all the external nodes using the prov-rtrv:extnode:"all" command, as shown in Example 8. Example 8 Retrieving All External Nodes machine-name mml> prov-rtrv:extnode:"all" Media Gateway Controller :01:18 "session=ver1:extnode" NAME TYPE ISDNSIGTYPE GROUP itp-l-1 SLT N/A 0 itp-l-2 SLT N/A 0 Adding IP Routes to Cisco ITP-Ls (Optional) The IP route component specifies a set of static routes that PGW uses to deliver packets to nondirect devices. IP routes are used when ITP-Ls are not in the same subnet with PGW. PGW communicates with Cisco ITP-Ls with the help of a nexthop gateway. You can ignore this section if your ITP-Ls are in the same subnets with PGWs. Step 1 Step 2 Command/Action machine-name mml>prov-add:iproute:name= "iproute-1-to-itp-l-1", desc="first IP Route to itp-l-1",dest=" ",netmask=" ",ipaddr="ip_addr1",pri=1, nexthop=" " Media Gateway Controller :21:04 "iproute" machine-name mml> prov-add:iproute:name= "iproute-2-to-itp-l-1", desc="second IP Route to itp-l-1",dest=" ",netmask=" ",ipAddr="IP_Addr2",pri=1, nexthop=" " Media Gateway Controller :21:04 "iproute" Purpose Adds the first IP route to the external node itp-l-1. Nexthop and IP_Addr1 must be in the same subnet. Adds the second IP route to the external node itp-l-1. Nexthop and IP_Addr2 must be in the same subnet. 28

29 Provisioning Signaling Links Step 3 Step 4 Command/Action machine-name mml>prov-add:iproute:name= "iproute-1-to-itp-l-2", desc="first IP Route to itp-l-2",dest=" ",netmask=" ",ipaddr="ip_addr1",pri=1, nexthop=" " Media Gateway Controller :21:04 "iproute" machine-name mml>prov-add:iproute:name= "iproute-2-to-itp-l-2", desc="second IP Route to itp-l-2",dest=" ",netmask=" ",ipAddr="IP_Addr2",pri=1, nexthop=" " Media Gateway Controller :21:04 "iproute" Purpose Adds the first IP route to the external node itp-l-2. Nexthop and IP_Addr1 must be in the same subnet. Adds the second IP route to the external node itp-l-2. Nexthop and IP_Addr2 must be in the same subnet. Note The IP address of the nexthop parameter should be on the same subnet with the IP address of the ipaddr parameter. IP_Addr1 and IP_Addr2 are configured in the XECfgParm.dat file in the fold /opt/ciscomgc/etc. For more information on how to configure XECfgParm.dat, see Configuring the Execution Environment section in Chapter 4 of the Cisco Media Gateway Controller Software Installation and Configuration (Release 9.7) at Verifying the Added IP Routes to Cisco ITP-Ls To verify that you have added the IP routes to Cisco ITP-Ls, use the prov-rtrv:iproute command. For example, to verify that you have added the IP route to itp-l-1: mml> prov-rtrv:iproute:name="iproute-1-to-itp-l-1" Media Gateway Controller :22:12 "session=ver1:iproute" NAME = iproute-1-to-itp-l-1 DESC = First IP route to itp-l-1 DEST = NETMASK = NEXTHOP = IPADDR = IP_Addr1 PRI= 1 You can retrieve all the IP routes using the prov-rtrv:iproute:"all" command, as shown in Example 9. Example 9 Retrieving All IP Routes machine-name mml> prov-rtrv:iproute:"all" Media Gateway Controller :01:18 29

30 Provisioning Signaling Links "session=ver1:iproute" NAME DEST NETMASk NEXTHOP IPADDR PRIORITY iproute-1-to-itp-l IP_Addr1 1 iproute-1-to-itp-l IP_Addr1 1 iproute-2-to-itp-l IP_Addr2 1 iproute-2-to-itp-l IP_Addr2 1 Adding Sessionsets for PGW-ITP-L Communication In order to communicate with ITP-L, the PGW must set up sessions with ITP-Ls. Use the sessionset component (a set of sessions) to define one sessionset for each of the two ITP-Ls. The shaded areas in Figure 10 show the sessionsets you are adding for PGW-ITP-L communication. Figure 10 Adding Sessionsets for PGW-ITP-L Communication LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network

31 Provisioning Signaling Links Step 1 Step 2 Command/Action machine-name mml>prov-add:sessionset:name= "sessionset-1",port=7000,peeraddr1=" ", peeraddr2=" ",peerport=7000, ipaddr1="ip_addr1",ipaddr2="ip_addr2", [iproute1="iproute-1-to-itp-l-1", iproute2="iproute-2-to-itp-l-1",] extnode="itp-l-1",type="bsmv0" Media Gateway Controller :21:04 "sessionset" machine-name mml>prov-add:sessionset:name= "sessionset-2",port=7000,peeraddr1=" ", peeraddr2=" ",peerport=7000, ipaddr1="ip_addr1",ipaddr2="ip_addr2", [iproute1="iproute-1-to-itp-l-2", iproute2="iproute-2-to-itp-l-2",] extnode="itp-l-2",type="bsmv0" Media Gateway Controller :21:04 "sessionset" Purpose Adds a sessionset for the external node itp-l-1. In this configuration, IPRoute1 and IPRoute2 are optional. They are required when PGW and Cisco ITP-Ls are not in the same subnet. Adds a sessionset for the external node itp-l-2. In this configuration, IPRoute1 and IPRoute2 are optional. They are required when PGW and Cisco ITP-Ls are not in the same subnet. Verifying the Added Sessionsets To verify that you have added the IP routes to Cisco ITP-Ls, use the prov-rtrv:sessionset command. For example, to verify that the sessionset of itp-l-1 was added: mml> prov-rtrv:sessionset:name:"sessionset-1" Media Gateway Controller :01:18 "session=ver1:sessionset" NAME = sessionset-1-1 DESC = Session Set sessionset-1 Backhaul Link 1 EXTERNAL NODE = itp-l-1 IPADDR = IP_Addr1 PORT = 7000 PEERADDR = PEERPORT = 7000 TYPE = BSMV0 IPROUTE = [iproute-1-to-itp-l-1] NAME = sessionset-1-2 DESC = Session Set sessionset-1 Backhaul Link 2 EXTERNAL NODE = itp-l-1 IPADDR = IP_Addr2 PORT = 7000 PEERADDR = PEERPORT = 7000 TYPE = BSMV0 IPROUTE = [iproute-2-to-itp-l-1] You can retrieve all the sessionsets using the prov-rtrv:sessionset:"all" command, as shown in Example

32 Provisioning Signaling Links Example 10 Retrieving All Sessionsets machine-name mml> prov-rtrv:sessionset:"all" Media Gateway Controller :01:18 "session=ver1:sessionset" NAME BACKHAUL LINK EXTNODE IPADDR PORT PEERADDR PEERPORT TYPE IPROUTE sessionset-1 sessionset-1-1 itp-l-1 IP_Addr BSMV0 [iproute-1-to-itp-l-1] sessionset-1 sessionset-1-2 itp-l-1 IP_Addr BSMV0 [iproute-2-to-itp-l-1] sessionset-2 sessionset-2-1 itp-l-2 IP_Addr BSMV0 [iproute-1-to-itp-l-2] sessionset-2 sessionset-2-2 itp-l-2 IP_Addr BSMV0 [iproute-2-to-itp-l-2] Adding C7 IP Links to Cisco ITP-Ls A C7 IP link component identifies a link between the Cisco ITP-L IP address and port, and an SSP or an 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 ITP-Ls that carry SS7 signaling to the signaling controller over IP. If your configuration does not include Cisco ITP-Ls and your links terminate from the s 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 ITP-L. These links correspond to the linksets you created in the Adding Linksets section on page 18. The shaded area in Figure 11 shows the C7 IP links you provision in this example. 32

33 Provisioning Signaling Links Figure 11 Adding C7 IP Links LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network You must add two links for linkset 1 and two links for linkset 2. Step 1 Step 2 Command/Action machine-name mml>prov-add:c7iplnk:name="c7iplink1", desc="c7iplink-1 in ls 1",pri=1,slc=0,lnkset="ls01", sessionset="sessionset-1",timeslot=0 Media Gateway Controller :05:46 "c7iplnk" machine-name mml>prov-add:c7iplnk:name="c7iplink2", desc="c7iplink-2 in ls 1",pri=1,slc=1,lnkset="ls01", sessionset="sessionset-2",timeslot=0 Media Gateway Controller :07:15 "c7iplnk" Purpose Defines an SS7 link from the PGW through Cisco ITP-L 1 ( ) to A. Uses the ls01 linkset. Defines an SS7 link from the PGW through Cisco ITP-L 2 ( ) to A. Uses the ls01 linkset. 33

34 Provisioning Signaling Links Step 3 Step 4 Command/Action machine-name mml> prov-add:c7iplnk:name="c7iplink3", desc="c7iplink-3 in ls 2",pri=1,slc=0,lnkset="ls02", sessionset="sessionset-1",timeslot=0 Media Gateway Controller :08:51 "c7iplnk" machine-name mml> prov-add:c7iplnk:name="c7iplink4", desc="c7iplink-4 in ls 2",pri=1,slc=1,lnkset="ls02", sessionset="sessionset-2",timeslot=0 Media Gateway Controller :10:52 "c7iplnk" Purpose Defines an SS7 link from the PGW through Cisco ITP-L 1 ( ) to B. Uses the ls02 linkset. Defines an SS7 link from the PGW through Cisco ITP-L 2 ( ) to B. Uses the ls02 linkset. Verifying the Added C7 IP Links To verify that you have entered the C7 IP links, use the prov-rtrv:c7iplnk command. For example, to verify that the first C7 IP link was added: machine-name mml> prov-rtrv:c7iplnk:name="c7iplink1" Media Gateway Controller :12:47 "session=ver1:c7iplnk" NAME = c7iplink1 DESC = C7IPlink-1 in ls 1 LNKSET = ls01 SLC = 0 PRI = 1 TIMESLOT/SLOT = 0 SESSIONSET = sessionset-1 You can retrieve all the C7 IP links using the prov-rtrv:c7iplnk:"all" command, as shown in Example 11. Example 11 Retrieving All C7 IP Links machine-name mml> prov-rtrv:c7iplnk:"all" Media Gateway Controller :40:17 "session=ver1:c7iplnk" NAME LNKSET PRI SLC TIMESLOT SESSIONSET c7iplink1 ls sessionset-1 c7iplink2 ls sessionset-2 c7iplink3 ls sessionset-1 c7iplink4 ls sessionset-2 34

35 Provisioning NAS Links Provisioning NAS Links NAS links indicate the communication path the PGW 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: NAS external node NAS signaling service IP links Adding NAS External Nodes You must add a NAS external node for each NAS in your network. The shaded areas in Figure 12 show the NAS external nodes. Figure 12 Adding NAS External Nodes LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network

36 Provisioning NAS Links Step 1 Step 2 Step 3 Command/Action machine-name mml> prov-add:extnode:name="nas1", desc="nas 1",type="AS5300",isdnsigtype="N/A",group=0 Media Gateway Controller :36:07 "extnode" machine-name mml> prov-add:extnode:name="nas2", desc="nas 2",type="AS5300",isdnsigtype="N/A",group=0 Media Gateway Controller :36:21 "extnode" machine-name mml> prov-add:extnode:name="nas3", desc="nas 3",type="AS5300",isdnsigtype="N/A",group=0 Media Gateway Controller :36:31 "extnode" Purpose Defines network access server NAS 1 as an external node. Defines network access server NAS 2 as an external node. Defines network access server NAS 3 as an external node. Verifying the Added NAS External Nodes To verify that you have entered the NASs, use the prov-rtrv:extnode command. For example, to verify that you have added the first NAS: machine-name mml> prov-rtrv:extnode:name="nas1" Media Gateway Controller :36:46 "session=ver1:extnode" NAME = nas1 DESC = NAS 1 TYPE = AS5300 ISDNSIGTYPE = N/A GROUP = 0 You can retrieve all the NAS external nodes using the prov-rtrv:extnode:"all" command, as shown in Example 12. Example 12 Retrieving All External Nodes machine-name mml> prov-rtrv:extnode:"all" Media Gateway Controller :44:41 "session=ver1:extnode" NAME TYPE ISDNSIGTYPE GROUP itp-l-1 SLT N/A 0 itp-l-2 SLT N/A 0 nas1 AS5300 N/A 0 nas2 AS5300 N/A 0 nas3 AS5300 N/A 0 36

37 Provisioning NAS Links Adding NAS Signaling Services You must add a NAS signaling service for each NAS you created in the Adding NAS External Nodes section on page 35. The NAS signaling service indicates the Q.931 protocol path between the PGW and the NASs. The shaded area in Figure 13 shows the NAS signaling services. Figure 13 Adding NAS Signaling Services LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network

38 Provisioning NAS Links Step 1 Step 2 Step 3 Command/Action machine-name mml> prov-add:naspath:name="nassvc1", extnode="nas1",desc="signaling service for NAS 1",custgrpid="0000",sigslot=0,sigport=0 Media Gateway Controller :40:11 "naspath" machine-name mml> prov-add:naspath:name="nassvc2", extnode="nas2",desc="signaling service for NAS 2",custgrpid="0000",sigslot=0,sigport=0 Media Gateway Controller :41:07 "naspath" machine-name mml> prov-add:naspath:name="nassvc3", extnode="nas3",desc="signaling service for NAS 3",custgrpid="0000",sigslot=0,sigport=0 Media Gateway Controller :41:49 "naspath" Purpose Adds the communications path between the PGW and network access server nas1. Adds the communications path between the PGW and network access server nas2. Adds the communications path between the PGW and network access server nas3. Verifying the Added NAS Signaling Services To verify that you have entered the NAS signaling services, use the prov-rtrv:naspath command. For example, to verify that the first NAS signaling service was added: va-testing mml> prov-rtrv:naspath:name="nassvc1" Media Gateway Controller :42:36 "session=ver1:naspath" NAME = nassvc1 DESC = Signaling service for NAS 1 EXTNODE = nas1 MDO = BELL_1268_C2 CUSTGRPID = 0000 SIGSLOT = 0 SIGPORT = 0 You can retrieve all the NAS signaling services using the prov-rtrv:naspath:"all" command, as shown in Example 13. Example 13 Retrieving All the NAS Signaling Services machine-name mml> prov-rtrv:naspath:"all" Media Gateway Controller :49:02 "session=ver1:naspath" NAME EXTNODE MDO CUSTGRPID SIGSLOT SIGPORT nassvc1 nas1 BELL_1268_C nassvc2 nas2 BELL_1268_C

39 Provisioning NAS Links nassvc3 nas3 BELL_1268_C Adding IP Links You must add an IP link from each NAS to PGW. In this example, you provision the following IP links: NAS 1 to PGW NAS 2 to PGW NAS 3 to PGW Note If you are provisioning two links from the PGW to the same NAS, you need two different Ethernet IP addresses on both the PGW and the NAS, for a total of four new addresses. The shaded area in Figure 14 shows the links you are adding in this example. Figure 14 Adding IP Links LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network

40 Provisioning NAS Links Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Command/Action machine-name mml> prov-add:iplnk:name="nas1link1", ipaddr="ip_addr1",port=3001,peeraddr=" ",peerport=3001,svc="nassvc1",desc="IP link for NAS 1 to PGW" Media Gateway Controller :48:54 "iplnk" machine-name mml> prov-add:iplnk:name="nas1link2", ipaddr="ip_addr2",port=3001,peeraddr=" ",peerport=3001,svc="nassvc2",desc="ip link 2 for NAS 1 to PGW" Media Gateway Controller :50:24 "iplnk" machine-name mml> prov-add:iplnk:name="nas2link1", ipaddr="ip_addr1",port=3001,peeraddr=" ",peerport=3001,svc="nassvc2",desc="IP link 1 for NAS 2 to PGW" Media Gateway Controller :51:35 "iplnk" machine-name mml> prov-add:iplnk:name="nas2link2", ipaddr="ip_addr2",port=3001,peeraddr=" ",peerport=3001,svc="nassvc2",desc="ip link 2 for NAS 2 to PGW" Media Gateway Controller :53:17 "iplnk" machine-name mml> prov-add:iplnk:name="nas3link1", ipaddr="ip_addr1",port=3001,peeraddr=" ",peerport=3001,svc="nassvc3",desc="IP link 1 for NAS 3 to PGW" Media Gateway Controller :54:20 "iplnk" machine-name mml> prov-add:iplnk:name="nas3link2", ipaddr="ip_addr2",port=3001,peeraddr=" ",peerport=3001,svc="nassvc3",desc="ip link 2 for NAS 3 to PGW" Media Gateway Controller :55:33 "iplnk" Purpose Defines IP link nas1link1 between the PGW and network access server nas1 for the previously defined NAS signaling service nassvc1. Defines IP link nas1link2 between the PGW and network access server nas1 for the previously defined NAS signaling service nassvc1. Defines IP link nas2link1 between the PGW and network access server nas2 for the previously defined NAS signaling service nassvc2. Defines IP link nas2link2 between the PGW and network access server nas2 for the previously defined NAS signaling service nassvc2. Defines IP link nas3link1 between the PGW and network access server nas3 for the previously defined NAS signaling service nassvc3. Defines IP link nas3link2 between the PGW and network access server nas3 for the previously defined NAS signaling service nassvc3. Verifying the Added IP Links To verify that you have entered the IP links, use the prov-rtrv:iplnk command: va-testing mml> prov-rtrv:iplnk:name="nas1link1" Media Gateway Controller :01:23 40

41 Provisioning Trunks "session=ver1:iplnk" NAME = nas1link1 DESC = IP link for NAS 1 to PGW SVC = nassvc1 IPADDR = IP_Addr1 PORT = 3001 PEERADDR = PEERPORT = 3001 PRI = 1 IPROUTE = 0 You can retrieve all the IP links by entering the prov-rtrv:iplnk:"all" command, as shown in Example 14. Example 14 Retrieving All the IP Links machine-name mml> prov-rtrv:iplnk:"all" Media Gateway Controller :05:43 "session=ver1:iplnk" NAME SVC IPADDR PORT PEERADDR PEERPORT PRI IPROUTE nas1link1 nassvc1 IP_Addr nas1link2 nassvc1 IP_Addr nas2link1 nassvc2 IP_Addr nas2link2 nassvc2 IP_Addr nas3link1 nassvc3 IP_Addr nas3link2 nassvc3 IP_Addr Provisioning Trunks You must add trunks for each connection between the NAS and the PSTN switch. The shaded area in Figure 15 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). Note If you have already provisioned the spans on the NAS to be associated with these trunks, use the shutdown command to remove these spans from service on the NAS before you provision the trunks on the Cisco PGW

42 Provisioning Trunks Figure 15 Adding Trunks LAN switches A Cisco ITP-Ls B PGW 2200 PSTN switch A NAS1 NAS2 Telephone exchange NAS3 Gateway router QoS packet network You can add trunks using any of the following methods: Importing a text file you create that contains all of your trunks Adding trunks individually with an MML command Adding up to 24 trunks for T1 lines or 31 trunks for E1 lines with an MML command Tip If you have a large number of trunks, use the text file method for adding trunks. Using a Text File to Add Trunks Using a text file to add trunks requires you to create a text file that contains the following fields: Trunk ID A unique identifier that maps to NAME (trunk ID). Source Service Name The signaling service that you created in the Adding the SS7 Signaling Service section on page 24 it is used to look up SRCSVC. Source Span ID Maps to SRCSPAN. (The value in the field is converted from decimal to hexadecimal except when the value is ffff.) 42