Introduction

Cisco Media Gateway Controller Software Overview

The Cisco Media Gateway Controller (MGC) Software Release 7 is part of solutions that enable the routing of time division multiplexing (TDM) traffic to or through an IP network. These solutions include:

•Cisco SS7 Interconnect for Access Servers Solution—Provides a gateway that allows dial-in users to dial in through a TDM network to access traditional data services on an IP network. This solution supports SS7 signaling through use of Cisco Signaling Link Terminals (SLTs).

•Cisco SS7 Interconnect for Voice Gateways Solution—Enables voice calls between the traditional TDM network and telephony services on an IP network. This solution also hosts voice calls between two TDM networks, but it uses two types of call routing: gatekeeper call routing and MGC call routing.

In both of these solutions, the Cisco MGC software is combined with one or two Sun hosts, Cisco SLTs, and network interface cards in the Sun hosts. This combination of hardware and software is known as the Cisco SC2200 product.

Terminology

The following terms are used in this document:

•Cisco SC host—A Sun host server running Cisco MGC software.

•Cisco SC node—The combination of the Cisco SC2200 product and the control signaling network. The SC node consists of all solution components except the media gateway.

•Simplex SC node—A node that uses a single SC host. Typically, this type of node is used for solution evaluation tests or for small installations. In a simplex configuration, any loss of service in the Cisco SC host disrupts all call traffic.

•Continuous-service SC node—A node that uses two SC hosts to prevent system down time caused by failure of a single SC host. Calls in progress are maintained when one SC host fails. Continuous-service nodes use SLTs to preprocess SS7 signaling and distribute signaling to both SC hosts. If a failover occurs, all stable calls are maintained.

Provisioning Tools

Three provisioning tools are distributed with the Cisco MGC software:

•Cisco Telephony Controller Manager (TCM), distributed with software Release 7.3(x)

•Cisco Media Gateway Controller Manager (CMM), distributed with software Release 7.4(x)

•Man-Machine Language (MML), distributed with software Release 7.3(x) and 7.4(x)

Tip Notes are used in this chapter to identify the procedures and other elements that differ in the TCM (used with Cisco media gateway controller software Release 7.3[x]) and the CMM (used with software Release 7.4[x]). However, most procedures are the same for both tools. See Table 1-1.

The TCM/CMM can be used alone or in conjunction with MML commands to provision your system. Table 1-1 shows the differences between provisioning methods.

Table 1-1 TCM/CMM and MML Specifications/Features
Specification/Feature	TCM/CMM	MML
System basics	X Window System GUI¹ front end, SNMP back end. Note Any client software supporting X, such as Reflection for remote management, can be used.	CLI² that interacts directly with the SC host.
System hardware/software requirements	Sun Sparc station running Solaris 2.6. Note Running the CMM on the same host as the MGC can adversely impact performance. We recommend using a separate server.	Runs on the SC host.
Batch file support	No.	Yes.
Level of network/telephony experience required	Little experience required; very easy to use.	Requires a high level of experience with MML and the Cisco MGC software.
Best used for	•Setting up a single configuration or few configurations on individual machines. •Modifying an existing configuration.	•Creating batch files to provision many Cisco SC nodes or retrieve measurements. •Modifying configurations (experienced users).

¹GUI = graphical user interface.

²CLI = command line interface.

See Cisco Media Gateway Controller Software Release 7 Provisioning Guide for basic information on provisioning your system, including:

•Using the TCM/CMM and MML tools

•Provisioning solution components

•Creating worksheets to use during provisioning

Table 1-1 lists the differences between the TCM and the CMM.

Table 1-2 TCM and CMM Differences
Component	TCM	CMM
General	•After creating components, Set Successful message displays. •Each window displays the TransPath field (not used) at the top.	•Set Successful message does not display. •TransPath field is removed.
Terminology	•Main window: Telephony Controller Manager •Telephony Controller tab	•Main window: Media Gateway Controller Manager •Media Gateway Controller Tab
Login command	cd /opt/VSCprov/bin ./start.sh	cd /opt/CMM/bin ./start.sh cmm
External node component	Contains MML name and description fields.	Adds new type field. For the solutions in this document, you can choose one of the following: •AS5200 •AS5300 •AS5800 •MGC •SCP
SS7 signaling service component	Contains ASP part field.	Does not contain ASP part field.
IP FAS signaling service	Contains ASP part field.	Does not contain ASP part field.
FAS signaling service	Contains ASP part field.	Does not contain ASP part field.
EISUP signaling service	Contains ASP part field.	Does not contain ASP part field.
C7 IP Link component	Contains peer port field (not used).	Does not contain peer port field.
Trunk tab, nailed bearer list	The nailed bearer list only displays the trunk ID.	The nailed bearer list displays the trunk ID, source signaling service, and destination signaling service.
BCFile component	You must enter the name of the trunk file you used.	The name of the trunk file you used is filled in automatically in the file name field.
Number analysis tab, Dial Plan component	•Results field: Values you enter when creating results are displayed as table fields. These include data words (1 through 4) and the next result. •Nature of Address field: The Index, NPI index, and Result Index fields are shown. •A Digit Tree and B Digit Trees: You must enter each digit as a separate node. •Digit Modification field: You use an index for digit modification. •Cause field: The cause index, location index, and result index are used.	•Results field: To create a result, you must first create a result set. You can add one or more results to the result set. The table fields are no longer visible or necessary. •Nature of address field: The NOA number, NPI block, and Result Set name fields are shown. •A Digit Tree and B Digit Trees: You can now enter a string of digits, rather than enter each digit as a separate node. Also, when viewing these trees, you can enter a filter to shorten the time it takes to display the trees. •Digit Modification field: You use a name (rather than an index) for digit modification. •Location field: The result set name (rather than the index) is displayed. •The cause number, location block, and result set name are used.
NumAnFile component	Your filename must be xxxx.dialPlan, where xxxx is the customer group ID you used for your dial plan.	The name of the dial plan file is filled in automatically in the file name field.

TCM/CMM Overview

The TCM/CMM is an X Window System GUI that accesses Cisco SC node information by using SNMP. You use the TCM/CMM to perform the following tasks:

•Setting up your initial system configuration

•Adding or deleting system components (for example, point codes, gateways, switches, and other nodes)

•Setting up links and signaling services between components

•Provisioning component properties

•Setting up number analysis and routing

•Saving or changing subsequent provisioning sessions

See Cisco Media Gateway Controller Software Release 7 Provisioning Guide for more information.

MML Overview

MML is a CLI that is used to directly interface with the Cisco SC host through a terminal. You can access MML through a console attached to the Cisco SC host, or through a Telnet session to the Cisco SC host.

See Cisco Media Gateway Controller Software Release 7 Provisioning Guide for more information on provisioning with MML. See Chapter 1, "MML Command Reference," in Cisco Media Gateway Controller Software Release 7 Reference Guide for more information on MML commands.

Before You Start

The following task checklist presents the steps you should have performed before using this guide.


	Task	Documentation
Step 1	Become familiar with the Cisco SS7 Interconnect for Access Servers Solution or the Cisco SS7 Interconnect for Voice Gateways Solution. You should have a general idea of what components each solution contains.	•Cisco SS7 Interconnect for Access Servers Solution Overview •Cisco SS7 Interconnect for Voice Gateways Solution Overview
Step 2	Know how to install and configure the gateways used in these solutions.	•Cisco SS7 Interconnect for Access Servers and Voice Gateways Solutions Media Gateway Guide
Step 3	Briefly review general Cisco MGC software information, such as software installation procedures, operating procedures, and release notes.	•Cisco Media Gateway Controller Software Release 7 Installation and Configuration Guide •Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide •Cisco Media Gateway Controller Software Release 7 MML Command Reference Guide •Cisco Media Gateway Controller Software Release 7 Messages Reference Guide •Cisco Media Gateway Controller Software Release 7 Billing Interface Guide •Cisco Media Gateway Controller Software Release 7 Management Information Base Guide •Release Notes for Cisco Media Gateway Controller Software Release 7
Step 4	Read the general provisioning guide to obtain an overview of the provisioning process, know how to use the provisioning tools, and know how to provision components by using the TCM/CMM and MML.	•Cisco Media Gateway Controller Software Release 7 Provisioning Guide •Cisco Media Gateway Controller Software Release 7 Dial Plan Guide