Table Of Contents
Provisioning the Cisco SS7 Interconnect for Voice Gateways Solution by Using CMM
Provisioning Outline
Provisioning Worksheet
Before You Begin
Provisioning SS7 Signaling Routes
Adding the Origination Point Code
Adding the Destination Point Code
Adding the Adjacent Point Codes
Adding Linksets
Adding the SS7 Subsystem
Adding SS7 Routes
Adding SS7 Signaling Services
Provisioning Signaling Links
Adding Adapters (Cards)
Adding Ethernet Interfaces
Adding C7 IP Links to Cisco SLTs
Provisioning NAS Links
Adding NAS External Nodes
Adding NAS Signaling Services
Adding IP Links
Provisioning Trunks
Creating the Trunk File
Adding Individual Trunks
Processing the Trunk File
Provisioning the Dial Plan/Number Analysis
Provisioning White and Black List Screening
Sample Scenario
Configuring the B White List
Deploying the Session
Provisioning the Cisco SS7 Interconnect for Voice Gateways Solution by Using CMM
This chapter describes how to provision a sample Cisco SS7 Interconnect for Voice Gateways Solution (see Figure 2-1). The chapter describes a sample configuration for illustration purposes only. Your configuration will vary and depend on your own network configuration.
The Cisco Media Gateway Controller Manager (CMM) tool is used with Cisco MGC software Release 7.3(x) and Release 7.4(x). You can also use the Cisco Voice Services Provisioning Tool (VSPT) to provision Cisco MGC software Release 7.4(x). Refer to the "Provisioning the Cisco SS7 Interconnect for Voice Gateways Solution by Using VSPT" chapter for more information on the Cisco VSPT.
Figure 2-1 Sample Cisco SS7 Interconnect for Voice Gateways Solution
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.
Provisioning Outline
Perform the following steps to provision the sample Cisco SS7 Interconnect for Voice Gateways Solution.
Note Trunk groups and trunk routing are not used in the Cisco SS7 Interconnect for Voice Gateways Solution. This solution uses nailed trunks between the voice gateways and the PSTN switch. The signaling controller does not perform trunk group selection in this solution.
Figure 2-2 shows a flow chart of the provisioning steps discussed in this chapter. After the component, the CMM name of the component is shown in parenthesis.
Figure 2-2 Provisioning Steps
Provisioning Worksheet
Table 2-1 shows a provisioning worksheet for the sample configuration shown in this chapter.
Table 2-1 Provisioning Worksheet
Component
|
Parent Component
|
MML Name
|
Description
|
Parameters
|
OPC
|
None
|
opc
|
Origination point code
|
•Network address: 171.1.4
•Network indicator: National Network
|
DPC
|
None
|
dpc1
|
DPC of PSTN Switch A
|
•Network address: 171.1.3
•Network indicator: National Network
|
APC
|
None
|
apc1
|
APC for STP A
|
•Network address: 171.16.1
•Network indicator: National Network
|
APC
|
None
|
apc2
|
APC for STP B
|
•Network address: 171.16.2
•Network indicator: National Network
|
Linkset
|
apc1
|
ls01
|
Linkset from signaling controller to STP A
|
•Protocol family: SS7-ANSI
•Transport type: IP
|
Linkset
|
apc2
|
ls02
|
Linkset from signaling controller to STP B
|
•Protocol family: SS7-ANSI
•Transport type: IP
|
SS7 subsystem
|
•apc1
•apc2
|
subsys1
|
Route Between STP A and STP B
|
•Adjacent point code: apc1
•Mated adjacent point code: apc2
•Protocol Family: SS7-ANSI
•Priority: 3
•Subsystem Number: 0
•STP-SCP index: 0
•Transport protocol: SCCP
|
SS7 route
|
•dpc1
•ls01
•opc
|
ss7route1
|
Route 1 to PSTN Switch A through LS1
|
•Signal Destination Point: dpc1
•Linkset: ls01
•Originating point code: opc
•Priority: 1
|
SS7 route
|
•dpc1
•ls02
•opc
|
ss7route2
|
Route 2 to PSTN Switch A through LS2
|
•Signal Destination Point: dpc1
•Linkset: ls02
•Originating point code: opc
•Priority: 1
|
SS7 signaling service
|
dpc1
|
ss7sigsvc
|
SS7 Service to PSTN Switch A
|
•MDO File Name: ANSISS7_STANDARD
•Customer Group ID: D123
•Customer Group Table: 0101
•Side: Network
•ASP Part: N
|
Adapter (card)
|
None
|
encard1
|
Ethernet card 1
|
Card slot: 0
|
Adapter (card)
|
None
|
encard2
|
Ethernet card 2
|
Card slot: 1
|
Ethernet interface
|
encard1
|
enetif1
|
Ethernet interface for encard1
|
None
|
Ethernet interface
|
encard2
|
enetif2
|
Ethernet interface for encard2
|
None
|
C7 IP link
|
ls01
|
c7iplnk1
|
Link 1 in Linkset 1
|
•Enet Line Interface: enetif1
•Port: 5000
•Priority: 1
•Peer address: 175.30.241.27
•Peer port: 5000
•IP address: IPAddr1
•Time slot: 0
•Link code: 0
|
C7 IP link
|
ls01
|
c7iplnk2
|
Link 2 in Linkset 1
|
•Enet Line Interface: enetif1
•Port: 5000
•Priority: 1
•Peer address: 175.30.238.28
•Peer port: 5000
•IP address: IPAddr2
•Time slot: 0
•Link code: 1
|
C7 IP link
|
ls02
|
c7iplnk3
|
Link 1 in Linkset 2
|
•Enet Line Interface: enetif2
•Port: 5000
•Priority: 1
•Peer address: 175.30.241.27
•Peer port: 7000
•IP address: IPAddr1
•Time slot: 0
•Link code: 0
|
C7 IP link
|
ls02
|
c7iplnk4
|
Link 2 in Linkset 2
|
•Enet Line Interface: enetif2
•Port: 5000
•Priority: 1
•Peer address: 175.30.238.28
•Peer port: 5000
•IP address: IPAddr2
•Time slot: 0
•Link code: 1
|
NAS external node
|
None
|
nas1
|
NAS 1
|
None
|
NAS external node
|
None
|
nas2
|
NAS 2
|
None
|
NAS external node
|
None
|
nas3
|
NAS 3
|
None
|
NAS signaling service
|
nas1
|
signas1
|
Signaling service for
NAS 1
|
MDO file name: BELL_1268_C3
|
NAS signaling service
|
nas2
|
signas2
|
Signaling service for
NAS 2
|
MDO file name: BELL_1268_C3
|
NAS signaling service
|
nas3
|
signas3
|
Signaling service for
NAS 3
|
MDO file name: BELL_1268_C3
|
IP link
|
signas1
|
iplink1
|
IP link for NAS 1 to Ethernet IF 1
|
Enet line interface: enetif1
Port: 3001
Priority: 1
Peer address: 175.30.241.2
Peer port: 3001
IP address: IPAddr1
Signal slot: 0
Signal port: 0
|
IP link
|
signas1
|
iplink2
|
IP link for NAS 1 to Ethernet IF 2
|
Enet line interface: enetif2
Port: 3001
Priority: 1
Peer address: 175.30.238.2
Peer port: 3001
IP address: IPAddr2
Signal slot: 0
Signal port: 0
|
IP link
|
signas2
|
iplink3
|
IP link for NAS 2 to Ethernet IF 1
|
Enet line interface: enetif1
Port: 3001
Priority: 1
Peer address: 175.30.241.3
Peer port: 3001
IP address: IPAddr1
Signal slot: 0
Signal port: 0
|
IP link
|
signas2
|
iplink4
|
IP link for NAS 2 to Ethernet IF 2
|
Enet line interface: enetif2
Port: 3001
Priority: 1
Peer address: 175.30.238.3
Peer port: 3001
IP address: IPAddr2
Signal slot: 0
Signal port: 0
|
IP link
|
signas3
|
iplink5
|
IP link for NAS 3 to Ethernet IF 1
|
Enet line interface: enetif1
Port: 3001
Priority: 1
Peer address: 175.30.241.4
Peer port: 3001
IP address: IPAddr1
Signal slot: 0
Signal port: 0
|
IP link
|
signas3
|
iplink6
|
IP link for NAS 3 to Ethernet IF 2
|
Enet line interface: enetif2
Port: 3001
Priority: 1
Peer address: 175.30.238.4
Peer port: 3001
IP address: IPAddr2
Signal slot: 0
Signal port: 0
|
Before You Begin
Log in to the signaling controller and start the CMM as described in Cisco Media Gateway Controller Software Release 7 Provisioning Guide.
Note Many procedures in this chapter refer to sections in Cisco Media Gateway Controller Software Release 7 Provisioning Guide or the Cisco Media Gateway Controller Software Release 7 Dial Plan Guide. Keep these books handy when performing the procedures in this chapter.
Provisioning SS7 Signaling Routes
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:
•OPC—Origination point code or the point code of the signaling controller 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 STPs
•Linksets
•SS7 subsystems (to identify mated STPs)
•SS7 routes
•SS7 signaling services
For more information on configuring SS7 signaling routes, see Cisco Media Gateway Controller Software Release 7 Provisioning Guide.
Adding the Origination Point Code
A point code is an SS7 network address that identifies an SS7 network node, such as a switch, STP, or 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.
Step 1 In the Media Gateway Controller Tab, click PointCode.
Step 2 Enter MML name opc.
Step 3 Enter description Origination point code.
Step 4 Enter network address 171.1.4.
Step 5 Click Network Indicator and choose National Network.
Step 6 Click Create.
Step 7 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Adding the Destination Point Code
The following procedure shows how to add the point code for the PSTN switch.
Step 1 Click PointCode.
Step 2 Enter MML name dpc1.
Step 3 Enter description DPC of PSTN Switch A.
Step 4 Enter network address 171.1.3.
Step 5 Click Network Indicator and choose National Network.
Step 6 Click Create.
Step 7 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Adding the Adjacent Point Codes
The following procedure shows how to add the adjacent point codes for the STPs.
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.
Step 1 Click APC.
Step 2 Enter MML name apc1.
Step 3 Enter description APC for STP A.
Step 4 Enter network address 171.16.1.
Step 5 Click Network Indicator and choose National Network.
Step 6 Click Create.
Step 7 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Step 8 Repeat for apc2, entering APC for STP B for the description and 171.16.2 for the network address.
Adding Linksets
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 join the signaling controller to an adjacent STP.
You must provision one linkset for each connection through the STP to the signaling controller.
Step 1 Click Link Set.
Step 2 Click Adjacent Point Code and select the apc1 component you provisioned in the "Adding the Adjacent Point Codes" section.
Step 3 Enter the MML name ls01.
Step 4 Enter the description Linkset from signaling controller to STP A.
Step 5 Click Protocol Family and choose SS7-ANSI.
Step 6 Click the IP transport type.
Step 7 Click Create.
Step 8 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Step 9 Repeat to add a linkset from the signaling controller to STPB, choosing the apc2 component and changing the MML name and description accordingly.
Note After creating the linksets, you must create the C7 IP links for each linkset. See "Adding C7 IP Links to Cisco SLTs" section.
Adding the SS7 Subsystem
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 in case of a failure between one of the STPs and an endpoint.
Step 1 Click SS7SubSys.
Step 2 Enter the MML name subsys1.
Step 3 Enter the description Route Between STP A and STP B.
Step 4 Click Adjacent Point Code to choose apc1 (the component you created for the STP A in the "Adding the Adjacent Point Codes" section).
Step 5 Click Mated Adjacent Point Code to choose the apc2 component you created for STP B.
Step 6 Click Protocol Family to choose SS7-ANSI.
Step 7 Click 3 for Priority.
Tip The priority for the SS7 subsystem should always be lower than the priority for the C7 IP links between the signaling controller and the STPs (which you provision in the "Adding C7 IP Links to Cisco SLTs" section). You do not want signaling traffic on the C-links, because they are used only if the F-links go down. If the priority for the C-links (SS7 subsystem) is higher than or equal to the priority for the C7 IP links, the signaling controller routes signaling traffic over those links. If you set the SS7 subsystem priority lower than the priority for the C7 IP links, the signaling controller routes traffic over the C-links between the STPs only if the links with a higher priority are not available.
Step 8 Enter 0 in the Sub System Number field. This value is not used when you are identifying mated STPs.
Step 9 Enter 0 in the STP-SCP index field. This value is not used when you are identifying mated STPs.
Step 10 Click SCCP for transport protocol.
Step 11 Click Create.
Step 12 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Adding SS7 Routes
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.
Step 1 Click SS7Route.
Step 2 Enter the MML name ss7route1.
Step 3 Enter the description Route 1 to PSTN Switch A through LS1.
Step 4 Click Signal Destination Point Code and choose dpc1 (the DPC for PSTN Switch A that you provisioned in the "Adding the Destination Point Code" section).
Step 5 Click Link Set to choose ls01 as the linkset for this route.
Step 6 Click Originating Point Code to choose opc as the origination point code for this route (the OPC for the signaling controller that you added in the "Adding the Origination Point Code" section).
Step 7 Choose 1 for priority.
Note Routes can share signaling traffic. You can set loadsharing by making the priorities the same for all routes.
Step 8 Click Create.
Step 9 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Step 10 Repeat Step 1 through Step 9 to add another route using Linkset 2, changing the MML name and description, and selecting ls02 as the linkset.
Adding SS7 Signaling Services
The SS7 signaling service specifies the path and the protocol variant that the signaling controller uses to communicate with a remote switch (SSP) that is sending bearer traffic to the NASs. You must add an SS7 signaling service from the signaling controller to the PSTN switch.
Step 1 Click SigSS7.
Step 2 Click Point Code to select the dpc1 point code for this signaling service. (You provisioned dpc1 as your destination point code for the PSTN switch in the "Adding the Destination Point Code" section.)
Enter MML name ss7sigsvc.
Step 3 Enter description SS7 Service to PSTN Switch A.
Step 4 Click MDO File Name and choose ANSISS7_STANDARD as the protocol for this signaling service.
Step 5 Enter D123 for the Customer Group ID. This is the name of the dial plan file you use for screening. See "Provisioning White and Black List Screening" section.
Note We recommend that you go ahead and 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.
Step 6 Click network for Side.
Step 7 Click N for ASP Part. This is used for DPNSS feature transparency.
Note The ASP Part field does not appear in software Release 7.4(x).
Step 8 Click Create.
Step 9 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Step 10 After you create the signaling service, click Properties and enter values for the following properties:
•BOrigStartIndex: 1
•BTermStartIndex: 2
These values are used in the screening process.
Step 11 Click Set.
Provisioning Signaling Links
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:
•Ethernet cards in the signaling controller that provide an interface from the Cisco SLT
•Ethernet interfaces for the cards you provision
•C7 IP links to the Cisco SLTs
Adding Adapters (Cards)
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.
Note You provision only one set of cards for one signaling controller (the primary), even though both signaling controllers are highlighted.
Step 1 Click Adapter.
Step 2 Enter MML name encard1.
Step 3 Click Type and choose EN (Ethernet).
Step 4 Enter description Ethernet card 1.
Step 5 Enter 0 for the card slot.
Step 6 Click Create.
Step 7 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Step 8 Repeat Step 1 through Step 7 for the second Ethernet card connected to the second signaling network, changing the MML name, description, and slot accordingly.
Note You must provision the card before provisioning the card interfaces.
Adding Ethernet 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. To add the interface for your first Ethernet card (encard1):
Step 1 Click EnetIf.
Step 2 Click Ethernet Adapter to choose the Ethernet card for this interface. Choose encard1.
Step 3 Enter MML name enetif1.
Step 4 Enter description Ethernet interface for Card 1.
Step 5 Click Create.
Step 6 Click OK. A message appears in the lower left corner of the main CMM window telling you what action was performed.
Step 7 Repeat Step 1 through Step 6 to add the interface for your second Ethernet card (encard2).
Adding C7 IP Links to Cisco SLTs
A C7 IP link component identifies a link between a Cisco SLT's IP address and port and the SS7 network (SSP or STP). The C7 IP link component 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 from the STPs terminate directly into ITK cards in the signaling controller, you must provision TDM links for the ITK cards. For example, the Cisco SS7 Dial Access Solution Release 2.0 uses ITK 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.
Adding Links for Linkset 1
Adding the First Link
You must add two links for linkset 1. To add the first link:
Step 1 Click C7IPLink.
Step 2 Click Link Set and choose ls01 as the linkset for this link.
Step 3 Enter the MML name c7iplink1.
Step 4 Enter the description Link 1 in Linkset 1.
Step 5 Click Enet Line Interface to choose the enetif1 Ethernet interface for this link. (You provisioned the Ethernet interfaces for each Ethernet card in the "Adding Ethernet Interfaces" section.)
Step 6 Enter 5000 in the Port field. This is the UDP port on the signaling controller. You can use any unused UDP port number, but do not use 1 through 1024 (these are reserved for other applications).
Step 7 Click 1 for priority.
Note To enable loadsharing, use the same priority (1) for each C7 IP link. Traffic is routed equally over the links in case of failure.
Step 8 Enter 175.30.241.27 in the peer address field. This is the IP address of SLT A.
Step 9 Enter 5000 in the peer port field. This is a placeholder value and is not used by the software.
Note The actual peer port value is found in the *.stPort field in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 10 Click IPAddr1. This is the IP address of the signaling controller.
Note The numbered address for this value is found in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 11 Enter 0 in the time slot field. The time slot field is the physical port on the Cisco SLT.
Note The time slot number must be unique for a given link on a particular Cisco SLT. For example, if you have a 2T WAN interface card (WIC) in slot 0 of the Cisco SLT, you can use time slot value 0 or 1 for the first link you provision. The second link on that WIC uses the remaining value.
Step 12 Enter 0 in the link code field. This is the signaling link code for the line between the Cisco SLT and the STP.
Step 13 Click Create.
Step 14 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Adding the Second Link
To add the second link:
Step 1 Click C7IPLink again.
Step 2 Click Link Set and choose ls01 as the linkset for this link.
Step 3 Enter the MML name c7iplink2.
Step 4 Enter the description Link 2 in Linkset 1.
Step 5 Click Enet Line Interface to choose the enetif1 Ethernet interface for this link. (You provisioned the Ethernet interfaces for each Ethernet card in the "Adding Ethernet Interfaces" section.)
Step 6 Enter 5000 in the Port field. This is the UDP port on the signaling controller. You can use any unused UDP port number, but do not use 1 through 1024 (these are reserved for other applications).
Step 7 Click 1 for priority.
Note To enable loadsharing, use the same priority (1) for each C7 IP link. Traffic is routed equally over the links in case of failure.
Step 8 Enter 175.30.238.28 in the peer address field. This is the IP address of SLT B.
Step 9 Enter 5000 in the peer port field. This field is a placeholder value and is not used by the software.
Note The actual peer port value is found in the *.stPort field in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 10 Click IPAddr2. This is the IP address of the signaling controller.
Note The numbered address for this value is found in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 11 Enter 0 in the time slot field. This field is the physical port on the Cisco SLT. (You used port 0 when you created the first link.)
Step 12 Enter 1 in the link code field. This is the signaling link code for the line between the Cisco SLT and the STP.
Step 13 Click Create.
Step 14 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Adding Links for Linkset 2
Adding the First Link
You must add two links for linkset 2. To add the first link:
Step 1 Click C7IPLink.
Step 2 Click Link Set and choose ls02 as the linkset for this link.
Step 3 Enter the MML name c7iplink3.
Step 4 Enter the description Link 1 in Linkset 2.
Step 5 Click Enet Line Interface to choose the enetif2 Ethernet interface for this link. (You provisioned the Ethernet interfaces for each Ethernet card in the "Adding Ethernet Interfaces" section.)
Step 6 Enter 5000 in the Port field. This is the UDP port on the signaling controller. You can use any unused UDP port number, but do not use 1 through 1024 (these are reserved for other applications).
Step 7 Click 1 for priority.
Note To enable loadsharing, use the same priority (1) for each C7 IP link. Traffic is routed equally over the links in case of failure.
Step 8 Enter 175.30.241.27 in the peer address field. This is the IP address of SLT A.
Step 9 Enter 32767 in the peer port field. This field is a placeholder value and is not used by the software.
Note The actual peer port value is found in the *.stPort field in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 10 Click IPAddr1. This is the IP address of the signaling controller.
Note The numbered address for this value is found in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 11 Enter 0 in the time slot field. This field is the physical port on the Cisco SLT.
Step 12 Enter 0 in the link code field.
Step 13 Click Create.
Step 14 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Adding the Second Link
To add the second link:
Step 1 Click C7IPLink.
Step 2 Click Link Set and choose ls02 as the linkset for this link.
Step 3 Enter the MML name c7iplink4.
Step 4 Enter the description Link 2 in Linkset 2.
Step 5 Click Enet Line Interface to choose the enetif2 Ethernet interface for this link. (You provisioned the Ethernet interfaces for each Ethernet card in the "Adding Ethernet Interfaces" section.)
Step 6 Enter 5000 in the Port field. This is the UDP port on the signaling controller. You can use any unused UDP port number, but do not use 1 through 1024 (these are reserved for other applications).
Step 7 Click 1 for priority.
Note To enable loadsharing, use the same priority (1) for each C7 IP link. Traffic is routed equally over the links in case of failure.
Step 8 Enter 175.30.238.28 in the peer address field. This is the IP address of SLT B.
Step 9 Enter 32767 in the peer port field. This is a placeholder value and is not used by the software.
Note The actual peer port value is found in the *.stPort field in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 10 Click IPAddr2. This is the IP address of the signaling controller.
Note The numbered address for this value is found in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 11 Enter 0 in the time slot field. This is the physical port on the Cisco SLT.
Step 12 Enter 1 in the link code field.
Step 13 Click Create.
Step 14 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Provisioning NAS Links
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:
•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.
Step 1 Click ExtNode.
Step 2 Enter MML name nas1.
Step 3 Enter description NAS 1.
Step 4 Click Type and choose the type of NAS (for this example, choose AS5300).
Step 5 Click Create.
Step 6 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Step 7 Repeat Step 1 through Step 5 for nas2 and nas3.
Adding NAS Signaling Services
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.
Step 1 Click SigNAS.
Step 2 Click External Node to choose the access server nas1 for this signaling service.
Step 3 Enter the MML name signas1.
Step 4 Enter the description Signaling service for NAS1.
Step 5 Click MDO File Name to choose the BELL_1268_C3 protocol for this signaling service.
Step 6 Click Create.
Step 7 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Step 8 Repeat Step 1 through Step 8 for each NAS, changing the MML names and descriptions accordingly.
Adding IP Links
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:
•NAS 1 to enetif1
•NAS 1 to enetif2
•NAS 2 to enetif1
•NAS 2 to enetif2
•NAS 3 to enetif1
•NAS 3 to enetif 2
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.
Step 1 Click IPLink.
Step 2 Click IP Signaling Services and choose signas1 as the signaling service for this link. (You provisioned the NAS signaling services in the "Adding NAS Signaling Services" section.)
Step 3 Enter the MML name iplink1.
Step 4 Enter the description IP link for NAS1 to Ethernet IF 1.
Step 5 Click Enet Line Interface to choose the enetif1 Ethernet interface for this link. (You provisioned the Ethernet interfaces for each Ethernet card in the "Adding Ethernet Interfaces" section.)
Step 6 Enter 3001 in the Port field. This is the UDP port on the signaling controller. You can use any unused UDP port number, but do not use 1 through 1024 (these are reserved for other applications).
Step 7 Click 1 for priority.
Note To enable loadsharing, use the same priority (1) for each C7 IP link. Traffic is routed equally over the links in case of failure.
Step 8 Enter 175.30.241.2 in the peer address field. This is the IP address of NAS1.
Step 9 Enter 3001 in the peer port field. This is the port on the signaling controller.
Step 10 Click IPAddr1. This is the IP address of the signaling controller.
Note The numbered address for this value is found in the XECfgParm.dat file you set up during your initial system configuration. See Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information.
Step 11 Enter 0 in the signal slot/port fields.
Step 12 Click Create.
Step 13 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Step 14 Repeat the procedures to add the second IP link from NAS 1 to enetif2, changing the MML name, Ethernet interface, and peer address accordingly.
Step 15 Repeat the steps 1 through 14 to add two links from each remaining NAS to the signaling controller, selecting the appropriate IP signaling service and changing the MML name, description, and peer address accordingly.
Note The provisioning example in this section creates two redundant link manager (RLM) links (forming an RLM group) for each NAS. As of Release 7.4(12) of the Cisco MGC software, you can create multiple RLM groups for each NAS. To create multiple RLM groups for each NAS, repeat steps 1 through 14 for each link in each RLM group. Ensure that the IP links in any multiple RLM groups use the following values defined in the associated NAS: the IP address of the loopback interfaces as the peer address value and the port number of the loopback interfaces as the peer port value.
Provisioning Trunks
You must add trunks for each connection between the NAS and the PSTN switch. 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, you must remove these spans from service on the NAS using the shutdown command, before you provision the trunks on the Cisco SC2200.
Creating the Trunk File
To add trunks using the Traffic tab in the CMM, first create the trunk file that will be populated with your data.
Step 1 Click the Traffic tab.
Step 2 Click Trunks.
Step 3 Choose Nailed from the trunk type menu.
Step 4 Enter trunks.txt as the filename and click Set.
Note For the trunk file name, you can use any extension except .old (reserved for use by the CMM software). In this example, .txt is used.
Step 5 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
Step 6 After you set the filename, the trunk.txt and BCFile components appear. Click the + sign next to the trunks.txt filename to see the Nailed component. In the next section, you click on the Nailed component to add individual trunks.
Adding Individual Trunks
Note The values used for the destination span ID 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.
To add the individual trunks, use this procedure:
Step 1 Click Nailed. The Nailed Bearer List appears and is empty.
Step 2 Click New.
Step 3 Enter 100 for the trunk ID.
Step 4 Click Source Signaling Service and select ss7sigsvc. (You created this signaling service in the "Adding SS7 Signaling Services" section.)
Step 5 Select Fixed for the Source Span.
Step 6 Enter ffff for the Source Span ID.
Step 7 Enter 1 for the Source Time Slot/CIC. This identifies the time slot on the T1 at the destination (PSTN switch).
Step 8 Click Destination Signaling Service and choose signas1. (You created this service in the "Adding NAS Signaling Services" section.)
Step 9 Select Fixed for the Destination Span. (This is the destination span type.)
Step 10 Enter 1 for the Destination Span ID. This sample value identifies the appropriate T1 line and T1 controller on the NAS. This value matches the nfas_int value that is set in IOS on the NAS.
Step 11 Enter 1 in the Destination Time Slot/CIC field. This identifies the time slot on the T1 that terminates at the NAS.
Step 12 Select T1 as the line type.
Step 13 Enter 24 in the multiple trunks field.
Step 14 Click Set.
Step 15 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
The system creates 24 trunks for this T1, automatically incrementing the Trunk ID each time, so that you have created trunk IDs 100 through 123.
The system automatically shows the Nailed Bearer List after successfully creating the trunks. The number of trunks shown depends on your value in the View Next menu. To see a different number of trunks, click the View Next menu and enter the desired value. To scroll through the Nailed Bearer List, click Next 10 and Previous 10.
After creating the trunks for the first T1, you must repeat the process to add trunks for the second, third, and fourth T1 that are connected to NAS1:
Step 1 From the Nailed Bearer List, click New.
Step 2 Enter 124 for the trunk ID.
Step 3 Click Source Signaling Service and select ss7sigsvc. (You created this signaling service in the "Adding SS7 Signaling Services" section.)
Step 4 Select Fixed for the Source Span.
Step 5 Enter ffff for the Source Span ID.
Step 6 Enter 25 for the Source Time Slot/CIC. This identifies the time slot on the T1 at the destination (PSTN switch).
Step 7 Click Destination Signaling Service and choose signas1. (You created this service in the "Adding NAS Signaling Services" section.)
Step 8 Select Fixed for the Destination Span. (This is the destination span type.)
Step 9 Enter 2 for the Destination Span ID. This sample value identifies the appropriate T1 line and T1 controller on the NAS. This value matches the nfas_int value that is set in IOS on the NAS.
Step 10 Enter 25 in the Destination Time Slot/CIC field. This identifies the time slot on the T1 that terminates at the NAS.
Step 11 Select T1 as the line type.
Step 12 Enter 24 in the multiple trunks field.
Step 13 Click Set.
Step 14 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
The system creates 24 trunks for this T1, automatically incrementing the Trunk ID each time, so that you have created trunk IDs 124 through 147.
Add the trunks for the third T1:
Step 1 From the Nailed Bearer List, click New.
Step 2 Enter 148 for the trunk ID.
Step 3 Click Source Signaling Service and select ss7sigsvc. (You created this signaling service in the "Adding SS7 Signaling Services" section.)
Step 4 Select Fixed for the Source Span.
Step 5 Enter ffff for the Source Span ID.
Step 6 Enter 49 for the Source Time Slot/CIC. This identifies the time slot on the T1 at the destination (PSTN switch).
Step 7 Click Destination Signaling Service and choose signas1. (You created this service in the "Adding NAS Signaling Services" section.)
Step 8 Select Fixed for the Destination Span. (This is the destination span type.)
Step 9 Enter 3 for the Destination Span ID. This sample value identifies the appropriate T1 line and T1 controller on the NAS. This value matches the nfas_int value that is set in IOS on the NAS.
Step 10 Enter 49 in the Destination Time Slot/CIC field. This identifies the time slot on the T1 that terminates at the NAS.
Step 11 Select T1 as the line type.
Step 12 Enter 24 in the multiple trunks field.
Step 13 Click Set.
Step 14 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
The system creates 24 trunks for this T1, automatically incrementing the Trunk ID each time, so that you have created trunk IDs 148 through 171.
Add the trunks for the fourth T1:
Step 1 From the Nailed Bearer List, click New.
Step 2 Enter 172 for the trunk ID.
Step 3 Click Source Signaling Service and select ss7sigsvc. (You created this signaling service in the "Adding SS7 Signaling Services" section.)
Step 4 Select Fixed for the Source Span.
Step 5 Enter ffff for the Source Span ID.
Step 6 Enter 73 for the Source Time Slot/CIC. This identifies the time slot on the T1 at the destination (PSTN switch).
Step 7 Click Destination Signaling Service and choose signas1. (You created this service in the "Adding NAS Signaling Services" section.)
Step 8 Select Fixed for the Destination Span. (This is the destination span type.)
Step 9 Enter 2 for the Destination Span ID. This value identifies the appropriate T1 line and T1 controller on the NAS. It is the nfas_int value that is set in IOS on the NAS.
Step 10 Enter 73 in the Destination Time Slot/CIC field. This identifies the time slot on the T1 that terminates at the NAS.
Step 11 Select T1 as the line type.
Step 12 Enter 24 in the multiple trunks field.
Step 13 Click Set.
Step 14 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
The system creates 24 trunks for this T1, automatically incrementing the Trunk ID, so that you have created trunk IDs 172 through 195.
After you have created trunks for the four T1s that terminate at NAS1, you must add trunks for the four T1s that terminate at NAS2 and the three T1s that terminate at NAS3. Follow the previous instructions but make the changes outlined in Table 2-2 and Table 2-3.
Table 2-2 NAS2 Trunks
Field
|
Trunk 1 Value
|
Trunk 2 Value
|
Trunk 3 Value
|
Trunk 4 Value
|
Trunk ID
|
196
|
220
|
244
|
268
|
Source Time Slot/CIC
|
97
|
121
|
145
|
169
|
Mated Signaling Service
|
NAS2
|
NAS2
|
NAS2
|
NAS2
|
Mated Span ID
|
3
|
3
|
3
|
3
|
Mated Time Slot/CIC
|
97
|
121
|
145
|
169
|
Table 2-3 NAS3 Trunks
Field
|
Trunk 1 Value
|
Trunk 2 Value
|
Trunk 3 Value
|
Trunk ID
|
292
|
316
|
340
|
Source Time Slot/CIC
|
193
|
217
|
241
|
Mated Signaling Service
|
NAS3
|
NAS3
|
NAS3
|
Mated Span ID
|
4
|
4
|
4
|
Mated Time Slot/CIC
|
193
|
217
|
241
|
Processing the Trunk File
After you add the trunks, you must process the trunk file. To process the file, perform the following steps:
Step 1 Under trunks.txt, click BCFile.
Step 2 Enter trunks.txt in the filename field.
Step 3 Enter your user ID and password. Only this user is allowed to modify the file.
Step 4 Click Set.
Step 5 Click OK. A message appears in the lower left corner of the main CMM window that tells you what action was performed.
The system opens a File Transfer Protocol (FTP) session to the signaling controller host and copies the file. In addition, Simple Network Management Protocol (SNMP) sets the filename in the Management Information Base (MIB) and the file is post-processed.
Note Only one filename can be set in the MIB. If a new filename is set through use of SNMP, the old name is overwritten.
Tip If you receive an error message indicating that the file cannot be processed, your SNMP session might not be running. The SNMP session times out after 30 minutes of inactivity. Exit the CMM and restart it before trying to process the file.
Note If you have already provisioned the spans on the NAS to be associated with these trunks, you can now return those spans to service on the NAS using the no shutdown command.
Provisioning the Dial Plan/Number Analysis
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.
Provisioning White and Black List Screening
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).
The CMM allows you to enter numbers that are collected in a batch file. When you set the white or black list file and the file is post-processed, the commands in the file are applied to the black and white list databases. For example, if you added numbers to the white list, the numbers are inserted into the database when the file is post-processed.
Note Because the CMM white and black list provisioning is done by batch file, adding or removing a row during the provisioning session does not mean the row has been added to or removed from the database.
Sample Scenario
This section provides procedures for provisioning a sample B white list. In this scenario, assume that a company offering dialup service has two telephone numbers: one for regular customers and one for reduced-rate customers. Regular customers call (703) 484-3000 for dialup service. Reduced-rate customers call (703) 484-6000 and receive discount rates; for example, they could pay a monthly fee in exchange for cheaper per-minute charges. So the company wants to analyze calls made to (703) 484-6000 and route calls to the IP network only if they are from reduced-rate customers, or those customers on the white list. The SC host uses a dial plan result of screening to screen the A-number to see if the call is permitted.
Configuring the B White List
To configure a B whit e list, perform the steps in the following sections:
• "Setting Number Analysis Properties" section
• "Creating the Dial Plan File" section
• "Setting the Service Name" section
• "Adding the Screening Result Set and Result" section
• "Adding Numbers to the White List" section
• "Processing the Dial Plan File" section
• "Processing the White List File" section
These events occur during the screening:
1. Calls are made to (703) 484-6000.
2. The SC host receives a call and performs analysis based on the called number.
3. As a result of analysis, the SC host sees that calls directed to that number must be screened for the calling party number (A-number).
4. The SC host checks the A-number against the B white list to see if the calling party is authorized.
5. If the calling party does appear in the B white list database, the call is put through.
6. If the calling party does not appear in the B white list database, the call is disconnected.
Setting Number Analysis Properties
Before you set up the screening, make sure you have set number analysis properties for your NAS signaling services. You set these properties in "Adding SS7 Signaling Services" section. These values are:
•BOrigStartIndex: 1
•BTermStartIndex: 2
Creating the Dial Plan File
Perform the following steps to create the dial plan file:
Step 1 Click the Number Analysis tab.
Step 2 Click Number Analysis.
Step 3 Enter D123 for the Customer Group ID.
Step 4 Click Create New.
Step 5 In the Number Analysis File Types window, click File Type and choose DialPlan.
Step 6 Click Create File. The file type you created appears in the directory under the customer group ID.
Creating the White List File
Perform the following steps to create the white list file:
Step 1 Click the D123 component.
Step 2 In the Number Analysis File Types window, click File Type and choose BWhiteList.
Step 3 Click Create File. The file type you created appears in the directory under the customer group ID.
Setting the Service Name
To set up the service name, perform the following steps:
Step 1 Under the D123 component, click the + next to DialPlan.
Step 2 Click Service_Name to set up a service name (the name of the screening database) to link to the result.
Step 3 Click New. Enter onerate as the Service Name and click Set.
Adding the Screening Result Set and Result
Perform the following steps to add a result set and result of screening:
Step 1 Click Results.
Step 2 Click New Result Set. Enter 1ratescreen as the result set name and click Set.
Step 3 Click Add Result Type and choose Screening.
Step 4 Enter bwhite for Result Name and 1 for Screen Type. The value of 1 indicates that the screen type is a white list—if the presented A-number is not found in the database, then the screening is considered to have failed and the call is released.
Step 5 Enter onerate as the Service Name and click Set.
Step 6 Click the + next to B_Digit_Tree. Click Originating.
Note Because this is a small example, you can leave the filter field blank and display all numbers.
Step 7 Click Add String and enter 7034846000 in the string field.
Step 8 Click Result Set Name, choose 1ratescreen, and click Select.
Adding Numbers to the White List
Perform the following steps to add numbers to the white list:
Step 1 Under D124, click the + sign next to BWhiteList to expand the tree. Click Screening.
Step 2 Click New Row.
Step 3 Click Action and choose Insert.
Step 4 Enter onerate for the Service Name.
Step 5 Enter 7035552222 for the Calling Party Number. This is the number of a reduced-rate customer authorized to use the (703) 484-6000 number.
Step 6 Repeat to add a few sample numbers.
Processing the Dial Plan File
To process the dial plan file:
Step 1 Under DialPlan, click NumAnFile.
Step 2 Enter your user ID and password and click Set.
The system opens an FTP session to the Cisco SC host and copies the file. In addition, SNMP sets the filename in the MIB and the file is post-processed. At this time, the insertions and deletions are made in the white and black list databases.
Note Only one filename can be set in the MIB. If a new filename is set through use of SNMP, the old name is overwritten.
Tip If you receive an error message indicating that the file cannot be processed, your SNMP session might not be running. The SNMP session times out after 30 minutes of inactivity. Exit the CMM and restart it before trying to process the file.
Processing the White List File
To process the white list file:
Step 1 Under BWhiteList, click BWhiteFile.
Step 2 Enter your user ID and password and click Set.
The system opens an FTP session to the Cisco SC host and copies the file. In addition, SNMP sets the filename in the MIB and the file is post-processed. At this time, the insertions and deletions are made in the white and black list databases.
Note Only one filename can be set in the MIB. If a new filename is set through use of SNMP, the old name is overwritten.
Tip If you receive an error message that the file cannot be processed, your SNMP session might not be running. The SNMP session times out after 30 minutes of inactivity. Exit the CMM and restart it before trying to process the file.
Deploying the Session
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.
To deploy the session:
Step 1 Use the TCM/CMM to build your configuration by following the steps in this chapter.
Step 2 Choose Deploy from the Session menu to save the current configuration as active and copy the configuration to the second host server.
Tip If you receive an error while trying to deploy the session, 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.
Step 3 Restart the standby server after reconfiguration to apply changes.
