|
|
The sections in this chapter provide a general overview of provisioning procedures, including:
This chapter describes how to provision the MGC for the Cisco SS7 Interconnect for Access Servers Solution and the Cisco SS7 Interconnect for Voice Gateways Solution, using the Cisco Media Gateway Controller Manager (CMM).
The CMM is an X-windows graphical user interface (GUI) that accesses MGC information using Simple Network Management Protocol (SNMP). You use the CMM to perform the following tasks:
The CMM can be used alone or with MML commands to provision your system. For more information on using MML, refer to "Configuring with MML."
The following task checklist presents the steps you should have performed before using this guide.
Step 1 | Plan your network configuration. A detailed network diagram is very helpful when provisioning. |
|
Step 2 | Set up your hardware components and install all required software.
|
|
Step 3 | Complete provisioning worksheets, including filling in names and IP addresses of machines, names, attributes, and properties of components, and other necessary information.
|
 |
Tips "Planning for Provisioning,"contains descriptions of the parameters and values contained in the CMM. You should review this document before you begin provisioning and keep it available to refer to for more information during provisioning. |
You should have the information described in "Provisioning Overview," before beginning your provisioning session:
The CMM provides a GUI that allows you to create provisioning sessions. The CMM saves your current provisioning session each time you click a set command. After you finish the provisioning session and choose commit or deploy, the CMM saves your configuration as the active configuration. After you have created the active configuration, you cannot modify it. To make changes, you must save it with another name and commit or deploy the new provisioning session to make it active.
The software allows only one active provisioning session. Therefore, you cannot have an active MML provisioning session open at the same time you are using the CMM. Other users can access the CMM, but will remain in read-only mode, and the create, modify, set, and delete buttons are not enabled.
 |
Note If you have changed the default directory value, use that value throughout this document where the /opt/CiscoMGC/etc directory is referred to. |
The number of configurations you can store might be limited by available disk space. Consider deleting old or unwanted configurations, or saving them to another machine if you do not have sufficient disk space.
To start the CMM, perform the following steps:
|
Note You must be logged in to the CMM server or access it from a machine with X-windows capability. |
Step 2 In the terminal window, enter:
cd /opt/CMM/bin
./start.sh cmm
The system opens the X-windows interface and the login screen appears, as shown in Figure 4-1.
|
Note The terminal window in which you originally started the CMM remains open, and due to software limitations, extraneous error messages can appear. |
cd /opt/CMM/bin
./start.sh cmm IPAddr/HostName SourceVersionName DestVersionName
Step 3 In the IP Address/Host Name field, enter the host name or the IP address of the Cisco MGC host. Typically, the Cisco MGC software resides on a different machine from the CMM provisioning tool, but it can reside on the same host.
Step 4 In the Read Community Name and Write Community Name fields, accept the Public default.
Step 5 In the Source Version Name field, enter one of the following:
|
Note When creating a new session and you use the same name as an existing, inactive session, the information in the inactive session will be overwritten. No error message prompt appears. |
|
Note To modify an existing inactive provisioning session, use the same provisioning session names for both the source and destination version names. |
Step 7 Press Connect to start the provisioning session. The main screen appears, as shown in Figure 4-2.
|
Tips Depending on the X-windows software you are using, when entering data in the CMM, you might need to press Shift when using the Backspace key. |
The CMM provides tabs to navigate through the system. You click on these tabs to add or change network components. The CMM contains the following tabs:
The left side of the screen displays a list of components that you select. The right panel of the screen displays fields in which you enter data. Click a component to select it. To see all components, click the + sign next to the component name to expand the component list.
The top of the screen contains the following information boxes shown in Figure 4-4.
The bottom left portion of the CMM screen provides status messages when you perform an action. For example, after you start the CMM, the message "Cisco Media Gateway Controller Manager started" appears. After you click the Create button when creating an external node, the message "extnode set successful" appears.
The CMM also provides a menu bar that remains constant throughout the provisioning session. Your choices depend on whether you are in read-only or read-write mode. The menu bar contains the following selections:
The Session menu contains the choices listed in Table 4-1.
| Command | Description | Mode | ||
|---|---|---|---|---|
Copies all configurations on the active1 Cisco MGC host machine to the standby Cisco MGC host (if you have a continuous-service configuration). | ||||
Ends the current configuration session. | ||||
Ends the session and saves the current configuration as the active configuration. Copies the configuration to the standby Cisco MGC (if you have a continuous-service configuration). | Read-write | |||
Ends the session and saves the current configuration as the active configuration.
| Read-write | |||
Stops any open provisioning session and exits the CMM. | Read-only and read-write |
| 1The active Cisco MGC in a continuous-service configuration is the machine that is processing calls. Do not confuse with the active provisioning session, which is located on the CMM host machine. |
The View menu contains the View Next option. Use this option to choose the number of data rows displayed in the CMM list boxes. For example, if you enter 10, the list boxes in the CMM display data 10 rows at a time. You can display a range of 1 through 999.
The Help menu contains only software copyright and version information at this time.
Your configuration is saved each time you click the create, modify, set, or delete buttons during your provisioning session.
To activate the provisioning session:
|
Note In a continuous-service configuration, the XECfgParm.dat file on each machine must be configured properly. If you experience problems, verify the XECfgParm.dat files on both machines with Chapter 2, "Installing the Cisco Media Gateway Controller Software," in Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide. |
You can exit the CMM at any time by performing one of these actions:
|
Note The CMM screen closes without you receiving a prompt message. |
To provision your system, you first provision the system components. The following sections describe all components. To provision components, you must first log in to the CMM as described in the "CMM Provisioning Overview" section, and select the Media Gateway Controller tab. The components are listed and defined in "Planning for Provisioning."
|
Note These components vary depending on which solution you are implementing. You will not use all components in a single configuration. For more information, see the solution-specific chapters in this guide. |
Components are structured hierarchically, although the structure that appears on the CMM screen does not reflect their true hierarchy. You must provision parent components (for example, the point code component) before provisioning children components (for example, the linkset). Figure 4-6 shows the component relationship.
You must enter an MML name and a description for each component you provision. MML names must have the following characteristics:
Use the external node component to add the following:
|
Note Cisco SLTs perform MTP layer 2 processing only. Therefore, you do not need to add them as external nodes when provisioning. |
For more information about external nodes, refer to the "Defining SS7 Network Addresses" section. To add an external node, perform the following steps:
Step 2 Enter the MML name.
Step 3 Enter the description.
Step 4 Click Create. The external node appears in the left display window under the ExtNode component.
Use the point code components to add the OPCs or DPCs in your network. For more information about point codes, refer to the "Defining SS7 Network Addresses" section. To add a point code, perform the following steps:
Step 2 Enter MML name.
Step 3 Enter description.
|
Note The point code examples used in this document follow the ANSI SS7 point code format. |
Step 4 Enter network address in dotted notation; for example, 147.26.1.
Step 5 Choose network indicator:
Step 6 Click Create. The point code appears in the left display window under the PointCode component.
Use the APC component to add the APCs in your network. For more information about adjacent point codes, refer to the "Defining SS7 Network Addresses" section. To add an APC, perform the following steps:
Step 2 Enter MML name.
Step 3 Enter description.
Step 4 Enter network address in dotted notation; for example, 147.26.1.
Step 5 Enter the network indicator:
Step 6 Click Create. The APC appears in the left display window under the APC component.
Use the adapter component to add a card for each card in your Cisco MGC host. For more information about adapter cards, refer to the "Planning Network Cards for Media Gateway Communications" section. To add a card, perform the following steps:
Step 2 Enter MML name.
Step 3 Choose type:
|
Note The cards referred to as "ITK" are now manufactured by Digi International AG (formerly known as ITK). |
Step 4 Enter description.
Step 5 Enter physical slot of card in the server. Value range: 0 through 16, depending on the host server configuration. The first slot is usually 0.
Step 6 Click Create. The card appears in the left display window under the Adapter component.
Add an Ethernet interface for each Ethernet card you added. The Ethernet interface represents a physical network connection on the card. To add an Ethernet interface, perform the following steps:
Step 2 Click Ethernet Adapter to choose the Ethernet card for this interface.
Step 3 Enter MML name.
Step 4 Enter description.
Step 5 Click Create. The Ethernet interface appears in the left display window under the EnetIf component.
Add a TDM interface for each T1/E1 or V.35 card in your server (refer to the "Adding Adapters (Cards)" section). The TDM interface represents a physical network connection on the card. To add a TDM interface for T1 or E1 cards, perform the following steps:
Step 2 Click TDM Adapter to choose the T1/E1 card for this interface.
Step 3 Enter MML name.
Step 4 Enter description.
Step 5 Choose control:
|
Note This is a bit-oriented synchronous data link layer protocol that specifies a data encapsulation method on synchronous serial links using frame characters and checksums. Most countries use this protocol. |
Step 6 Verify the Line Interface Number default value of 1; you cannot change this value for T1/E1 cards.
Step 7 Choose signal type:
Step 8 Enter resistance.
Step 9 Choose coding:
Step 10 Choose format:
Step 11 Click Create. The TDM interface appears in the left display window under the TDMIf component.
To add a TDM interface for a V.35 card, perform the following steps:
Step 2 Click TDM Adapter to choose the V.35 card for this interface.
Step 3 Enter MML name.
Step 4 Enter description.
Step 5 Note that HDLC is the default value for control; you cannot change this value for V.35 cards.
|
Note This is a bit-oriented synchronous data link layer protocol that specifies a data encapsulation method on synchronous serial links using frame characters and checksums. Most countries use this protocol. |
Step 6 Choose the Line Interface Number (1, 2, 3, or 4).
Step 7 Note that the signal type default value is V.35; you cannot change this value.
Step 8 Note that DTE is the default DTE/DCE value; you cannot change this value.
Step 9 Choose data rate:
Step 10 Note the default clock value of external; you cannot change this value.
Step 11 Click Create. The TDM interface appears in the left display window under the TDMIf component.
If you have a signaling service from the Cisco MGC to a PSTN switch, use the SigSS7 component to add it to your configuration. To add an SS7 signaling service, perform the following steps:
Step 2 Click Point Code to select the destination point code (the point code of the PSTN switch) for this signaling service.
Step 3 Enter MML name.
Step 4 Enter description.
Step 5 Click MDO File Name to choose the protocol for this signaling service; for example, ANSISS7_STANDARD.
Step 6 Enter Customer Group ID (formerly VNETID). This value is used in number analysis.
Step 7 Enter Customer Group Table.
Step 8 Choose side (Q.931 call model side):
Step 9 Click Create. The SS7 signaling service appears in the left display window under the SigSS7 component.
You can change the properties of the SS7 signaling services you have created. These properties apply to all SS7 signaling services you create. You do not have to change the default properties. For a list of signaling service properties, default values, and descriptions, refer to "Planning for Provisioning".
After you create a signaling service, the Properties button appears on the right screen panel. To change signaling service properties, perform the following steps:
Step 2 Click the property you want to change.
Step 3 In the value field, overwrite the property value with the desired value.
Step 4 Click Set. The property set message appears at the bottom left of the CMM screen.
Step 5 Click Close when you are finished.
|
Note You cannot modify properties until after you have created the signaling service. |
You must add a NAS signaling service for each NAS you created in your network under the ExtNode component. To add a NAS signaling service, perform the following steps:
Step 2 Click External Node to choose the access server for this signaling service.
Step 3 Enter the MML name.
Step 4 Enter the description.
Step 5 Click MDO File Name to choose the protocol for this signaling service. Currently, only BELL_1268_C3 is supported.
Step 6 Enter Customer Group ID (formerly VNETID).
Step 7 Enter Customer Group Table.
Step 8 Choose side (Q.931 call model side):
Step 9 Click Create. The NAS signaling service appears in the left display window under the SigNAS component.
You can change the properties of the NAS signaling services you have created. These properties apply to all NAS signaling services you create. You do not have to change the default properties. For a list of signaling service properties, default values, and descriptions, refer to "Planning for Provisioning".
After you create a NAS signaling service, the Properties button appears on the right screen panel. To change signaling service properties, perform the following steps:
Step 2 Click the property you want to change.
Step 3 In the value field, overwrite the property value with the desired value.
Step 4 Click Set. The property set message appears at the bottom left of the CMM screen.
Step 5 Click Close when you are finished.
|
Note You cannot modify properties until after you have created the NAS signaling service. |
For more information about an IPFAS signaling service, refer to the "Planning for the Media Gateway Signaling Service" section. To add an IPFAS signaling service, perform the following steps:
Step 2 Click External Node to choose the Cisco MGC for this signaling service.
Step 3 Enter the MML name.
Step 4 Enter the description.
Step 5 Click MDO File Name to choose the protocol for this signaling service; for example, ATT_41459.
Step 6 Enter Customer Group ID (formerly VNETID).
Step 7 Enter Customer Group Table.
Step 8 Choose side (Q.931 call model side):
Step 9 Choose A/B flag:
Step 10 Choose call reference length:
Step 11 Click Create. The IPFAS signaling service appears in the left display window under the SigIPFAS component.
You can change the properties of the IPFAS signaling services you have created. These properties apply to all IPFAS signaling services you create. You do not have to change the default properties. For a list of signaling service properties, default values, and descriptions, refer to "Planning for Provisioning".
After you create an IPFAS signaling service, the Properties button appears on the right screen panel. To change signaling service properties, perform the following steps:
Step 2 Click the property you want to change.
Step 3 In the value field, overwrite the property value with the desired value.
Step 4 Click Set. The property set message appears at the bottom left of the CMM screen.
Step 5 Click Close when you are finished.
|
Note You cannot modify properties until after you have created the IPFAS signaling service. |
Add a TCAPOverIP signaling service if you are provisioning an announcement server in your network, perform the following steps:
Step 2 Click External Node to choose the media gateway for this signaling service.
Step 3 Enter the MML name.
Step 4 Enter the description.
Step 5 Click Create. The TCAPOverIP signaling service appears in the left display window under the SigTCAPOverIP component.
You can change the properties of the TCAPOverIP signaling services you have created. These properties apply to all TCAPOverIP signaling services you create. You do not have to change the default properties. For a list of signaling service properties, default values, and descriptions, refer to "Planning for Provisioning."
After you create a TCAPOverIP signaling service, the Properties button appears on the right screen panel. To change signaling service properties, perform the following steps:
Step 2 Click the property you want to change.
Step 3 In the value field, overwrite the property value with the desired value.
Step 4 Click Set. The property set message appears at the bottom left of the CMM screen.
Step 5 Click Close when you are finished.
|
Note You cannot modify properties until after you have created the TCAPOverIP signaling service. |
For more information about a FAS signaling service, refer to the "Planning for the Media Gateway Signaling Service" section. To add a FAS signaling service, perform the following steps:
Step 2 Enter the MML name.
Step 3 Enter the description.
Step 4 Click MDO File Name to choose the protocol for this signaling service; for example, ATT_41459.
Step 5 Enter Customer Group ID (formerly VNETID).
Step 6 Enter Customer Group Table.
Step 7 Choose side (Q.931 call model side):
Step 8 Choose A/B flag:
Step 9 Choose call reference length:
Step 10 Click Create. The FAS signaling service appears in the left display window under the SigFAS component.
You can change the properties of the FAS signaling services you have created. These properties apply to all FAS signaling services you create. You do not have to change the default properties. For a list of signaling service properties, default values, and descriptions, refer to "Planning for Provisioning."
After you create a FAS signaling service, the Properties button appears on the right screen panel. To change signaling service properties, perform the following steps:
Step 2 Click the property you want to change.
Step 3 In the value field, overwrite the property value with the desired value.
Step 4 Click Set. The property set message appears at the bottom left of the CMM screen.
Step 5 Click Close when you are finished.
|
Note You cannot modify properties until after you have created the FAS signaling service. |
Add an EISUP signaling service if you have more than one Cisco MGC in your network. The Cisco MGCs use EISUP to communicate with each other. To add an EISUP signaling service, perform the following steps:
Step 2 Click External Node to choose the other Cisco MGC.
Step 3 Enter the MML name.
Step 4 Enter the description.
Step 5 Enter Customer Group ID (formerly VNETID).
Step 6 Enter Customer Group Table. This is used for DPNSS feature transparency.
Step 7 Choose side (Q.931 call model side):
Step 8 Click Create. The EISUP signaling service appears in the left display window under the SigEISUP component.
|
Note To ensure correct failover operation in a configuration with two local MGCs (one active and one standby) and a remote MGC, a minimum of two EISUP links are required from the remote VSC to each MGC redundant pair. |
You can change the properties of the EISUP signaling services you have created. These properties apply to all EISUP signaling services you create. You do not have to change the default properties. For a list of signaling service properties, default values, and descriptions, refer to "Planning for Provisioning".
After you create a EISUP signaling service, the Properties button appears on the right screen panel. To change signaling service properties, perform the following steps:
Step 2 Click the property you want to change.
Step 3 In the value field, overwrite the property value with the desired value.
Step 4 Click Set. The property set message appears at the bottom left of the CMM screen.
Step 5 Click Close when you are finished.
|
Note You cannot modify properties until after you have created the EISUP signaling service. |
Linksets are groups of links that connect two components. Linksets can consist of the following:
For more information about linksets, refer to the "Defining Linksets" section. To add a linkset, perform the following steps:
Step 2 Click Adjacent Point Code and Point Code and select the APC component for this linkset.
Step 3 Enter MML name.
Step 4 Enter the description.
Step 5 Choose Protocol Family:
Step 6 Choose the transport type:
Step 7 Click Create. The linkset appears in the left display window under the LinkSet component.
You can change the properties of the linksets you have created. These properties include message and timer values, and apply to all linksets you create. You do not have to change the default properties. For a list of linkset properties, default values, and descriptions, refer to "Planning for Provisioning".
After you create a linkset, the Properties button appears on the right screen panel. To change linkset properties, perform the following steps:
Step 2 Click the property you want to change.
Step 3 In the value field, overwrite the property value with the desired value.
Step 4 Click Set. The property set message appears at the bottom left of the CMM screen.
Step 5 Click Close when you are finished.
|
Note You cannot modify properties until after you have created the linkset. |
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.For more information about C7 IP links, refer to the "Planning A-Links Through Cisco SLTs" section. To add a linkset, perform the following steps:
Step 2 Click Link Set and choose the linkset for this link.
Step 3 Enter the MML name.
Step 4 Enter the description.
Step 5 Click Enet Line Interface to choose the Ethernet interface for this link.
Step 7 Choose the priority. Value range: 1 through 4. 1 is the highest priority.
|
Note To enable loadsharing, use the same priority (1) for each C7 IP link. Traffic will be routed equally over the links in case of failure. |
Step 8 Enter the IP address of the Cisco SLT in the peer address field.
Step 9 Enter 32767 in the peer port field. This is a dummy 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 Choose IP address of the Cisco MGC:
|
Note The numbered address for this value is found in the XECfgParm.dat file you set up during your initial system configuration. Refer to Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide for more information. |
Step 11 Enter the time slot. This is the physical port on the Cisco SLT.
|
Note The time slot number must be unique per 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 values 0 or 1 for the first link you configure. The second link on that WIC uses the remaining value. |
Step 12 Enter 1 in the link code field. This is the signaling link code (SLC) for the line between the Cisco SLT and the STP. The SLC can be any integer from 0 through 15.
Step 13 Click Create. The C7 IP link appears in the left display window under the C7IPLink component.
You need to add an IP link from each NAS to the Cisco MGC. For more information about IP links, refer to the "Planning IP Links" section. To add an IP link, perform the following steps:
Step 2 Click IP Signaling Services and choose the signaling service for this link.
Step 3 Enter the MML name.
Step 4 Enter the description.
Step 5 Click Enet Line Interface to choose the Ethernet interface for this link.
Step 7 Choose priority. Value range: 1 through 4. 1 is the highest priority.
Step 8 Enter the IP address of the NAS in the peer address field.
Step 9 Enter the port number in the peer port field. This is the port on the NAS and the value is port number + 1, where port number is the value you entered in Step 6.
Step 10 Choose the IP address of the Cisco MGC:
|
Note The numbered address for this value is found in the XECfgParm.dat file you set up during your initial system configuration. Refer to the Cisco Media Gateway Controller Software Release 7 Software Installation and Configuration Guide for more information. |
Step 11 Enter values in the signal slot/port fields.
Step 12 Click Create. The IP link appears in the left display window under the IPLink component.
You must add a TDM link for each path from the TDM to the Cisco MGC. You have one link for each T1/E1 card in the Cisco MGC host, which is associated with a TDM interface. These links are contained within the linksets you previously created. (Refer to the "Adding Linksets" section.) For more information about TDM links, refer to the "Planning A-Links to Signaling Points" section. To add a TDM link, perform the following steps:
Step 2 Click Linkset and choose the linkset for this link.
Step 3 Enter the MML name.
Step 4 Enter the description.
Step 5 Enter the link code.
Step 6 Choose the priority. Value range: 1 through 4. 1 is the highest priority.
Step 7 Click TDM Line Interface to choose the line interface for this link.
Step 9 Click Create. The TDM link appears in the left display window under the TDMLink component.
You must add an SS7 route for each signaling path from the Cisco MGC to the PSTN switch through the linksets you have created to the STPs. You should create two routes to the PSTN switch, with each route passing through a different STP of a mated pair. For more information about SS7 routes, refer to the "Defining SS7 Routes" section. To add an SS7 route, perform the following steps:
Step 2 Enter the MML name.
Step 3 Enter the description.
Step 4 Click Signal Destination or Adjacent Point Code and choose the DPC of the PSTN switch.
Step 5 Click Link Set to choose the linkset for this route.
Step 6 Click Originating Point Code to choose the origination point code for this route.
Step 7 Click Create. The SS7 route appears in the left display window under the SS7Route component.
SS7 subsystems are used by the MGC software to identify a pair of mated STPs connected by C-links. The SS7 Subsystem is also used to connect an STP to an SCP database for Advanced Intelligent Network (AIN) queries. In this case, there is no mated STP.
For more information about an SS7 subsystem, refer to the "Defining SS7 Subsystems" section. To add an SS7 subsystem, perform the following steps:
Step 2 Enter the MML name.
Step 3 Enter the description.
Step 4 If identifying mated STPs, click Adjacent Point Code to choose the APC of the first STP.
Step 5 If using the subsystem for AIN queries, click TCAPOverIP Service to choose the service you set up in the "Adding a TCAPOverIP Signaling Service" section.
Step 6 If identifying mated STPs, click Mated Adjacent Point Code to choose the APC of the second STP. If using the subsystem for AIN queries, choose None.
Step 7 Choose Protocol Family:
|
Note If you have multiple linksets to an STP that use different protocol families, you must also have multiple SS7 subsystems—one for each linkset that uses a certain protocol. |
Step 8 Choose the priority. Value range: 1 through 4. 1 is the highest priority.
|
Note When identifying mated STPs, enter 0, as this field is not used. |
The following SSN values are defined in the ANSI SCCP Spec. T1.112:
In the United States Public Switched Telephone Network (PSTN), the following conventions are followed:
Step 10 Enter the STP-SCP index field. When identifying mated STPs, the default is 0. When identifying AIN services, you are defining the index for the STP pair that is used by the TCAP subsystem to process TCAP requests.
Step 11 Choose transport protocol if identifying AIN services:
|
Note Not used when identifying mated STPs. |
Step 12 Click Create. The SS7 subsystem appears in the left display window under the SS7Subsys component.
To modify components, select the component in the left side of the screen. On the right side of the screen, modify the desired fields and click Modify. A set successful message appears in the lower left of the main CMM screen.
|
Note You cannot modify some fields in a component that are used by other components in the system. For example, you cannot change a card type, because the card type field is used in the interface component. Fields that you cannot modify appear gray, and you cannot enter information in them. |
|
Tips You cannot modify MML names once you have created a component. You must delete the component and enter a new component with a different name. |
To delete components, select the component and click Delete in the right screen panel. A dialog box asks you to confirm any deletions, and a message appears in the lower left of the main CMM screen telling you the component was deleted.
|
Note You cannot delete a component that is a parent of another component. For example, you cannot delete a linkset that contains links. You receive an error message when you try to delete a parent component. |
Trunks carry bearer traffic from destination switches to media gateways (MGWs).
For solutions that use switched trunks, you must provision trunk groups and configure trunk routing. For switched trunks, the Cisco MGC provides addressing information to the MGWs, such as the NASs. You need to create trunk groups, routes, and route groups for switched trunks.
|
Note If provisioning switched trunks, you must create trunk groups before creating any trunks. If provisioning nailed trunks, trunk groups are not used and trunks are created before routes. |
To add the trunk groups, first create a trunk group file, by performing the following steps:
Step 2 Click Trunk Group.
Step 3 Enter the filename for the trunk group.
Step 4 Click Create New File. The trunk group file appears in the left display window under the TrunkGroup component.
After creating the file, click the + sign next to the filename on the left side of the screen. The Trunk Group component appears.
To add a trunk group, perform the following steps:
Step 2 Enter the trunk group number. You can choose any four-digit number.
Step 4 Click Signaling Service. This corresponds to the signaling service you created when you set up your configuration in the Telephony Controller tab.
Step 5 Click Trunk Group Type and select the type. You can choose from the following types:
Step 6 Choose Yes or No for queuing. This indicates if the Cisco MGC uses queuing on the trunk during call processing.
Step 7 Enter the Ring No Answer value that is used in conjunction with queuing. You can choose the following values:
Step 8 Choose how the Cisco MGC will handle glare (simultaneous circuit seizure) by the Cisco MGC and the switch. You can choose the following values:
Step 9 Enter the COT percentage (0 to 100). This determines the percentage of calls on a trunk that are for continuity tests (SS7 only).
Step 10 Choose the Select Sequence used to determine trunk selection sequence. You can choose the following:
Step 11 Choose Yes or No for VSF priority. This is a PBX feature for storage and forward of voice messages.
Step 12 Choose Yes or No for Satellite. This indicates if a satellite link is used with the trunk group.
Step 13 Click Properties to set trunk group properties. The trunk group properties screen appears. You can set the following properties:
Step 14 Click Set. The Properties Trunk Group screen closes.
Step 15 In the Trunk Group screen, click Set.
After you add the trunk groups, you must process the trunk group file. To process the trunk group file, perform the following steps:
Step 2 Enter the filename.
Step 3 Enter your user ID and password. Only this user is allowed to modify the file.
Step 4 Click Set.
The system opens an FTP session to the Cisco MGC host and copies the file. In addition, SNMP sets the filename in the MIB and the file is post-processed.
|
Note Only one filename can be set in the MIB. If a new filename is set using SNMP, the old name is overwritten. |
|
Tips 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. |
To modify a trunk group, perform the following steps:
Step 2 Click TrunkGroup. The Trunk Group List appears on the right side of the screen.
Step 3 Select the trunk group from the list and click Modify. The trunk group screen appears.
Step 4 Make any desired changes in the Trunk Group screen and click Set.
Step 5 A screen appears that asks you to confirm the modification. Click Yes to modify the trunk group.
To delete a trunk group, perform the following steps:
Step 2 Click TrunkGroup. The Trunk Group List appears on the right side of the screen.
Step 3 Select the trunk group from the list and click Delete.
Step 4 A screen appears that asks you to confirm the deletion. Click Yes to delete the trunk group.
 |
Caution Deleting trunk groups deletes all trunks in that trunk group. |
You must add trunks for each connection between the media gateway and a destination switch. For the Cisco SS7 Interconnect for Access Servers Solution and the Cisco SS7 Interconnect for Voice Gateways Solution, these trunks are nailed. With nailed trunks, the Cisco MGC does not perform switching of trunks.
In the Cisco Packet Tandem Solution, the Cisco MGC provides addressing information to the media gateways. The Cisco MGC performs switching of trunks, using trunk groups, routes, and route groups.
|
Note You must create trunk groups before creating any trunks when provisioning switched trunks. |
To add trunks using the Traffic tab in the CMM, first create the trunk file that will be populated with your data. To create a trunk file, perform the following steps:
Step 2 Click Trunks. The Create Trunks File Name screen appears.
Step 3 Click Trunk Type and choose Nailed or Switched.
|
Note You can only have one trunk file (Nailed or Switched) at one time. |
Step 4 Enter the filename and click Create New File. The trunk file appears in the left display window under the Trunks component.
|
Note You can name the trunk file with any extension except .old (reserved for use by the CMM software). In this documentation, .txt is used. |
After you set the filename, the filename and BCFile components appear under the Trunks component in the left screen panel. Click the + sign next to the filename to display the Nailed or Switched component.
To add an individual nailed trunk, perform the following steps:
Step 2 The Nailed Bearer list appears and is empty. Click New.
Step 3 Enter the trunk ID (a three-digit identifier).
Step 4 Click Source Signaling Service and select the appropriate SS7 signaling service.
Step 5 Select Fixed for the Source Span.
Step 6 Enter ffff for the Source Span ID.
Step 7 Enter 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 the gateway signaling service.
Step 9 Select Fixed for the Destination Span. (This is the destination span type.)
Step 10 Enter the Destination Span ID. This value identifies the appropriate T1 or E1 line and T1 or E1 controller on the gateway. For example, it is the nfas_int value that is set in IOS on the NAS.
Step 11 Enter the Destination Time Slot/CIC field. This identifies the time slot on the T1 that terminates at the gateway.
Step 12 Select the line type:
Step 13 Enter the number of trunks in the multiple trunks field. For T1, you can enter 1 through 24. For E1, you can enter 1 through 31. The system automatically increments the trunk ID, source time slot/CIC, and the destination time slot/CIC.
Step 14 Click Set. A message in the lower left of the main CMM screen shows how many trunks you created.
To add the individual switched trunks, you must first create Trunk Groups. Refer to the "Provisioning Trunk Groups" section. After you have created the Trunk Groups, perform the following steps to add a switched trunk:
Step 2 The Switched Trunk Group List for All Trunk Groups appears, and is empty. Click New.
Step 3 Enter the trunk group number. This is the 4-digit number of the group you added in "Adding the Trunk Groups" section.
Step 4 Enter the trunk group member number.
Step 5 Select Increment or Fixed for the Span.
Step 6 Enter the Source Span ID. For most trunks, the value is ffff.
Step 7 Enter the CIC/Time Slot.
Step 8 Click External Node and choose the external node connected to these trunks.
Step 9 For End Point, enter the following values:
Step 10 Select the line type:
Step 11 Enter the number of trunks in the multiple trunks field. For T1, you can enter 1 through 24. For E1, you can enter 1 through 31. The system automatically increments the trunk group member number, CIC/time slot, and time slot in the end point field.
Step 12 Click Set.
After you add the trunks, you must process the trunk file. To process the trunk file, perform the following steps:
Step 2 Enter the filename.
Step 3 Enter your user ID and password. Only this user is allowed to modify the file.
Step 4 Click Set.
The system opens a File Transfer Protocol (FTP) session to the Cisco MGC 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 using SNMP, the old name is overwritten. |
To modify trunks, in the left side of the screen, select the name of the trunk filename you created in the "Creating the Trunk File" section. The right side of the screen displays the Nailed Bearer List or the Switched Bearer List.
To modify a trunk, perform the following steps:
Step 2 The system prompts you with a screen showing the changes you are requesting and asks you to confirm the modification. Click Yes to modify the trunk.
To delete trunks, in the left side of the screen, select the name of the trunk filename you created in the "Creating the Trunk File" section. The right side of the screen displays the Nailed Bearer List.
To delete a trunk, perform the following steps:
Step 2 A dialog box displays the line you want to delete and asks you to confirm the deletion. Click Yes to delete the trunk.
Although the CMM allows you to use only one trunk file at a time, you can retrieve trunk files you previously created. To retrieve a trunk file, perform the following steps:
Step 2 In the lower half of the screen, enter the filename of the file you want to retrieve.
Step 3 Enter the user name and password you gave the file when you created it.
Step 4 Click Get Existing.
You provision routes and route groups that are used by the Cisco MGC to direct traffic. Routes are different paths to the same destination, and route groups are user-defined sets of routes.
To create a routing file, perform the following steps:
Step 2 Click Routing.
Step 3 Enter the routing filename.
Step 4 Click Create New File. After creating the file, click the + sign next to the filename on the left side of the screen. The Routes and Route Groups components appear.
To add a route, perform the following steps:
Step 2 Click New. The Routes screen appears.
Step 3 Enter the route name.
Step 4 Click Trunk Group Number to display the available trunk groups.
Step 5 Choose the trunk group number and click Select.
Step 6 Click Set. The Route List screen appears with the route name you just created and the associated trunk group.
To add a route group, perform the following steps:
Step 2 Click New. The Route Group screen appears.
Step 3 Enter the route group name.
Step 4 Enter the carrier ID.
Step 5 In the Available Routes screen, select the route and click Add Route. The route you selected appears in the Associated Routes screen.
Step 6 After you add the routes you want, in the Associated Routes screen, click Set.
The route group list screen appears with the route group you just added.
After you add the trunks, you must process the routing file. To process a routing file, perform the following steps:
Step 2 Enter the filename in the filename field.
Step 3 Enter your user ID and password.
Step 4 Click Set.
The system opens an FTP session to the Cisco MGC host and copies the file. In addition, SNMP sets the filename in the MIB and the file is post-processed.
|
Note Only one filename can be set in the MIB. If a new filename is set using SNMP, the old name is overwritten. |
|
Tips 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. |
The MGC provides the ability to create a dial plan to perform number analysis on both the A (calling) number and B (called number). For more information on creating a dial plan, refer to the "Creating a Dial Plan for Release 7.4(x)" section. This chapter provides general guidelines for entering dial plan information into the CMM. You should already have your dial plan information recorded before beginning any data entry in the CMM.
To enter your dial plan information into the CMM, you must first create the dial plan file. To create a dial plan, perform the following steps:
Step 2 Click Number Analysis.
Step 3 Enter the Customer Group ID. (This is a 4-character alphanumeric name.)
Step 4 Click Create New. The Dial Plan component appears under the Customer Group ID you created in Step 3.
Step 5 Click the + sign next to the Dial Plan component. The following dial plan components appear:
Depending on your dial plan, you then add information for the type of analysis you want to perform. For example, for A-number and B-number analysis, first enter the results you want to achieve in the Results screen. Then enter the digits you want to analyze into the A_Digit_Tree or B_Digit_Tree screens. The Cisco MGC analyzes the number, one digit at a time, and performs the result or result set you specified.
A result set is a grouping of results that can be connected to an A-digit tree, a B-digit tree, pre-analysis, and cause analysis. Each result set consists of a grouping of one or more results. Each result set requires a unique name, and each result within a result set requires a unique name. The result set name can be as many as 20 alphanumeric characters in length. However, the result names do not need to be unique across result sets. It is the combination of both the result set name and the result name that must be unique.
You can have only one result set for each digit string; however, you can have multiple results in a result set. When determining the result types for a result set, enter them in logical order for example, from screening to route. The reason for this is that once a result set has result type with an endpoint analysis point, that is the end of the result set. You can have as many intermediate analysis point result types in a result set as you want. Refer to Table 2-47 for a list of the analysis point result types.
|
Note The result set table is used only for the purpose of configuration. |
In order for the dial plan to perform an action on a called or calling number, you must add a result for the action you want to occur. You must first create a result set. Your result set can contain one or more results that you want to occur in sequence.
To add a result set, perform the following steps:
Step 2 Click New Result Set.
Step 3 Enter the result set name and click Set. The Result Set screen appears.
To add a result to your result set, perform the following steps:
Step 2 Click Add Result Type to choose a result to add to the result set. You can choose a result from the following results:
Step 3 After you choose a result, enter the result name and any desired values in the displayed screen and click Set.
To modify a result, perform the following steps:
Step 2 Make desired changes to the fields in the results screen and click Set.
Step 3 A dialog box appears requesting verification. Click Yes to modify the result.
To delete a result, perform the following steps:
Step 2 A dialog box appears requesting verification. Click Yes to delete the result.
Pre-analysis is an initial analysis request made on a digit string after receiving the IAM or Setup message. Pre-analysis provides the ability to perform early analysis on the called (B-digit) number. Pre-analysis can be performed on the following results:
Using the incoming values for the NOA and NPI, pre-analysis can performed on the first digit in the B-digit string before any formal analysis is performed.
|
Note The result is processed from either the NOA table or the PNI table. |
Even though NOA preanalysis is performed first, the NPI must be provisioned first if the NOA refers to a NPI block.
To perform NPI provisioning, perform the following steps:
Step 2 Click New Block to add another block to the NPI. There are 16 NPI values (0 through 15) displayed for each NPI block added.
Step 3 Enter a value for New Block to add and click Set. The specified number of blocks are added to the NPI and the NPI screen is redisplayed with the specified number of blocks added.
|
Tips To keep the response time down, do not add more NPI blocks than are necessary. |
To modify an NPI, perform the following steps:
Step 2 Make desired changes to the NPI screen fields and click Set.
Step 3 A dialog box appears requesting verification. Click Yes to modify the selected NPI.
Step 4 The NPI screen is redisplayed with the selected NPI changed.
To perform NOA provisioning, perform the following steps:
Step 2 Click New. The NOA screen appears. See Figure 4-32.
Step 3 The NOA number appears in the top block. Enter the NPI Block value and the Result Set Name and click Set. The Nature of Address screen is redisplayed.
|
Note The NPI Block and/or the Result Set Name block must be filled in or an error message appears. |
To modify an NOA, perform the following steps:
Step 2 Make desired changes to the NOA screen fields and click Set.
Step 3 A dialog box appears requesting verification. Click Yes to modify the selected NOA.
Step 4 The NOA screen is redisplayed with the selected NOA changed.
To provision Cause, perform the following steps:
Step 2 Click New. This displays the Cause screen with the Cause Number displayed in the top box.
|
Note Location must be configured before provisioning Cause. |
Step 3 Enter the Location Block value and the Result Set Block and click Set. The Cause screen is redisplayed.
To modify a Cause, perform the following steps:
Step 2 Make desired changes to the Cause screen fields and click Set.
Step 3 A dialog box appears requesting verification. Click Yes to modify the selected Cause.
Step 4 The Cause screen is redisplayed with the selected Cause changed.
To provision the B-Digit Tree, perform the following steps:
Step 2 Click Originating.
Step 3 A warning message appears indicating that no filter is set and all configured digit strings will be displayed. You can enter a digit string in the filter box or click OK.
Step 4 Click OK. This displays all the digit strings on the B Digit Tree screen. See Figure 4-34.
Step 5 Click Add String. This displays the Add String box.
Step 6 Enter the digit string in the String box, the Result Set Name, and the Digits to Present value, and click Set.
Step 7 The B Digit Tree screen is redisplayed with the information entered in the Digit String box added.
Step 8 Repeat Step 5 and Step 6 for all the digit strings in your B-digit, originating dial plan.
To provision the B-Digit Tree, perform the following steps:
Step 2 Click Terminating.
Step 3 A warning message appears indicating that no filter is set and all configured digit strings will be displayed. You can enter a digit string in the filter box or click OK.
Step 4 Click OK. This displays all the digit strings on the B Digit Tree screen. See Figure 4-34.
Step 5 Click Add String. This displays the Add String box.
Step 6 Enter the digit string in the String box, the Result Set Name, and the Digits to Present value, and click Set.
Step 7 The B Digit Tree screen is redisplayed with the information entered in the Digit String box added.
Step 8 Repeat Step 5 and Step 6 for all the digit strings in your B-digit, terminating dial plan.
To provision the A-Digit Tree, perform the following steps:
Step 2 Click Originating.
Step 3 A warning message appears indicating that no filter is set and all configured digit strings will be displayed. You can enter a digit string in the filter box or click OK.
Step 4 Click OK. This displays all the digit strings on the A Digit Tree screen.
Step 5 Click Add String. This displays the Add String box.
Step 6 Enter the digit string in the String box, the Result Set Name, and the Digits to Present value, and click Set.
Step 7 The A Digit Tree screen is redisplayed with the information entered in the Digit String box added.
Step 8 Repeat Step 5 and Step 6 for all the digit strings in your A-digit, originating dial plan.
To provision the A-Digit Tree, perform the following steps:
Step 2 Click Terminating.
Step 3 A warning message appears indicating that no filter is set and all configured digit strings will be displayed. You can enter a digit string in the filter box or click OK.
Step 4 Click OK. This displays all the digit strings on the A Digit Tree screen.
Step 5 Click Add String. This displays the Add String box.
Step 6 Enter the digit string in the String box, the Result Set Name, and the Digits to Present value, and click Set.
Step 7 The A Digit Tree screen is redisplayed with the information entered in the Digit String box added.
Step 8 Repeat Step 5 and Step 6 for all the digit strings in your A-digit, terminating dial plan.
B-digit modification (BMODDIG) pre-analysis allows one or more digits to be removed from anywhere in the digit string and replace the removed digits with one or more digits.
Digit modification is found under the Number Analysis tab.
To add a result set that performs digit modification, perform the following steps:
Step 2 Click New. The Digit Modification screen appears. See Figure 4-36.
Step 3 Enter the digit modification name in the Name box, enter a value in the String box, and click Set. The Digit Modification String screen is redisplayed with the name and value from the Digit Modification screen added.
|
Note The String value indicates the number (or numbers) inserted at the application point of the MODDIG_B screen associated with the named result set. |
Step 4 Under the Dial Plan component, click Results. The Result Type Table screen appears.
Step 5 Click New Result Set.
Step 6 Enter the result set name and click Set. The Result Set screen is redisplayed with the new result set name added.
Step 7 Click Add Result Type and click MODDIG_B from the list of results. The MODDIG_B screen appears with the Result Set Name already added. See Figure 4-37.
Step 8 Enter a Result Name, Application Point (where the digit modification is to start), Number of Digits to Remove, Modification Name, and then click Set. The Result Set screen is redisplayed with the MODDIG_B information added.
|
Note The Modification Name entered must match (is case sensitive) the name entered (refer to Step 3) in the Digit Modification Table. |
Step 9 Click Add Result Type and click ROUTE from the list of results. The Route screen appears with the Result Set Name already added.
Step 10 Enter a Result Name, enter a Route Group Name, and click Set. The Result Set screen is redisplayed with another line with the ROUTE information added.
|
Note The Route Group Name must have been defined in the Routing File previously (refer to the "Adding Route Groups" section). If not already defined, an error message appears. |
To provision a Service Name, perform the following steps:
Step 2 Click New. This displays the Service Name screen shown in Figure 4-39.
Step 3 Enter a Service Name and click Set. The Service Screen is redisplayed with the entered Service Name listed in the Service Name column.
Step 4 Repeat Step 2 and Step 3 for all the service names required to support your dial plan.
To provision Location, perform the following steps:
Step 2 Click New Block. The New Location screen appears. See Figure 4-41.
Step 3 Enter a value for the Block Number. (Typically choose the next sequential number.)
Step 4 Click Set. This redisplays the Location screen with the Current Block showing the value entered in Step 3 and 16 entries (0 through 15) in the Location Value column.
Step 5 Click Modify Result Set. The Add String box appears.
Step 6 Repeat Step 2 through Step 5 for all the locations required to support your dial plan.
To modify a Location, perform the following steps:
Step 2 Make desired changes to the Location screen fields and click Set.
|
Note The Result Set Name must already exist in the Result Set table. |
Step 3 A dialog box appears requesting verification. Click Yes to modify the selected Location.
Step 4 The Location screen is redisplayed with the Location selected in Step 1 changed.
After you complete your dial plan, you must process the number analysis file. To process the number analysis file, perform the following steps:
Step 2 Enter the filename in the filename field.
Step 3 Enter your user ID and password.
Step 4 Click Set.
The system opens an FTP session to the Cisco MGC host and copies the file. In addition, SNMP sets the filename in the MIB, and the file is post-processed.
|
Note Only one filename can be set in the MIB. If a new filename is set using SNMP, the old name is overwritten. |
|
Tips 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. |
You can provision white and black lists 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).
To provision the white or black list, first create the list file, perform the following steps:
Step 2 If you have already entered a Customer Group ID, that component appears under the Number Analysis component. If you have not already entered a Customer Group ID, or want to enter a new one, perform the following steps:
a. Click Number Analysis.
b. Enter the Customer Group ID.
c. Click Create New.
Step 3 Click the Customer Group ID component to continue. The Number Analysis File Types screen appears.
Step 4 Click File Type and choose one of the following:
Step 5 Click Create File. The file type you created appears in the directory under the Customer Group ID.
After you create the white list or black list file, you must set up screening for the list. To provision the numbers for screening, perform the following steps:
Step 2 To add a new row to the screening table, click New Row. The Screening screen appears.
Step 3 Click Action and choose Insert.
Step 4 Enter the calling party number to add to the white list.
Step 5 Click Set. The number appears in the A White List screen.
Step 6 Add additional numbers following the previously described procedures.
After you complete your black or white list file, you must process the file. To process the white list or black list file, perform the following steps:
Step 2 Enter the filename in the filename field.
Step 3 Enter your user ID and password.
Step 4 Click Set.
The system opens an FTP session to the Cisco MGC host and copies the file. In addition, SNMP sets the filename in the MIB and the file is post-processed.
|
Note Only one filename can be set in the MIB. If a new filename is set using SNMP, the old name is overwritten. |
|
Tips 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. |
Posted: Wed Sep 27 12:53:04 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
