Chapter 4: Configuring the Cisco Media Gateway Controller Software Release 7.4

Available Languages

Download Options

PDF (543.1 KB)
View with Adobe Reader on a variety of devices

Updated:June 29, 2007

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Configuring the Cisco Media Gateway Controller Software Release 7.4

Table Of Contents

Configuring the Cisco Media Gateway Controller Software Release 7.4

Before You Start

Configuring Groups and Users

Verifying the mgcgrp Group

Adding a User with Full MML Privileges

Adding a User with Minimal MML Privileges

Configuring SNMP Support Resources

Configuring the Execution Environment

Changing XECfgParm.dat File Parameters

Changing XECfgParm.dat File Parameters in a Running Continuous-Service or High-Availability System

Configuring Basic System Information

Specifying IP Addresses

Configuring Engine Parameters

Configuring Automatic Congestion Control

Overload Level Percentage Parameters

CPU Timer Interval Parameter

Maximum ACL Value

Enabling Call Screening

Configuring Call Detail Record File Output

Configuring the System Type

Configuring the Clearing Location and Default Location Parameters

Configuring *.GWClearChannelAlgorithm Parameter

Configuring Switchover

Initializing the Provisioning Object Manager

Configuring SCP Queries

Before You Start

Configuring the trigger.dat File Attributes

Configuring the Global Title Translation Attribute

Configuring the Service Key Value Attribute

Configuring the Translation Type Attribute

Sample trigger.dat File

Initializing the Call Screening Database

.odbc.ini File Information

Setting Up Replication

Initializing Database Replication

Initializing Replication and Copying the Database to Another Host

Verifying Database Replication

Troubleshooting

Configuring the Cisco Media Gateway Controller Software Release 7.4

This chapter describes how to configure Release 7.4 of the Cisco Media Gateway Controller (MGC) software.

This chapter contains the following sections:

•Before You Start

•Configuring Groups and Users

•Configuring SNMP Support Resources

•Configuring the Execution Environment

•Configuring SCP Queries

•Initializing the Call Screening Database

Note For more information on configuring the Cisco MGC software, see the following publication: Cisco Media Gateway Controller Software Release 7 Provisioning Guide

Before You Start

Before you start, perform the following steps:

•Review the hardware and software requirements found in the document Release Notes for
Cisco Media Gateway Controller Software Release 7.

•Have your company's internal support and Cisco support contact information readily available so you can get help with the configuration if needed. (If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Cisco support contact information.)

•Ensure that you have access to the console port on your Cisco MGC host.

Perform your configuration according to the steps below.

Note For the software to work properly, you must reboot the system every time you modify any file in the /etc directory.

Configuring Groups and Users

You must set up groups and users for the Cisco MGC software on each host server. A user must be a member of the "mgcgrp" group to use certain Cisco MGC software functions, such as Man-Machine Language (MML). (MML is an interface that enables you to communicate with the Cisco MGC. Users with full MML privileges have monitor and control access; users with minimal MML privileges have only monitor access. For more information on MML, see Cisco Media Gateway Controller Software Release 7 Provisioning Guide.

Verifying the mgcgrp Group

To verify the mgcgrp group, complete the following steps:

Step 1 Verify that you are logged in to the Cisco MGC host as root. At the # prompt, type the following command:
# cat /etc/passwd
Step 2 Change to the /etc directory.

Step 3 Edit the group file to verify the entry for the mgcgrp group. The file should contain the following line:
mgcgrp::20000:
Step 4 Add a user called "mgcusr" to the mgcgrp group. For example:
mgcgrp::20000:mgcusr
Step 5 Save and close the group file.

Step 6 Edit the passwd file to verify the entry for the mgcusr user. The file should contain the following line:
mgcusr:x:20000:20000::/opt/CiscoMGC/local:/bin/csh
If the file does not contain the line, add it.

Step 7 Save and close the password file.

Adding a User with Full MML Privileges

To add a user with full MML privileges, complete the following steps:

Step 1 Log in to the Cisco MGC host as root.

Step 2 Enter the following command:
# useradd -u UID -g mgcgrp -d /opt/CiscoMGC/local -s /bin/csh -m username
UID is a user ID that is an integer from 0 through 2147483647 (excluding the numbers 0, 1, 2, 3, 4, 5, 9, 37, 71, 60001, 60002, and 65534, because they are used by the operating system).

Step 3 Add the new username to the mgcgrp group in the group file:
# mgcgrp::20000:username
Note The group file is a comma-separated list of user names. If you add more than one user, use a comma (with no spaces) to separate consecutive names in the list from each other.

Step 4 Enter the following command and press Enter:
passwd username
Step 5 Type the user's password and press Enter twice when prompted.

Caution If your home directory differs from /opt/CiscoMGC/local, you must perform the following steps before using MML.Log in to the Cisco MGC.

Step 6 Enter the following command and press Enter:
cd /opt/CiscoMGC/local
Step 7 Enter the following command and press Enter:
source .cshrc
Step 8 Enter the following command and press Enter:
mml
Adding a User with Minimal MML Privileges

To add a user with minimal MML privileges, follow the steps in the "Adding a User with Full MML Privileges" section, but do not add the user to the mgcgrp group.

This completes the group and user configuration. Continue to the "Configuring SNMP Support Resources" section. If you have questions or need assistance, see the "Obtaining Technical Assistance" section.

Configuring SNMP Support Resources

The Cisco MGC software includes a Simple Network Management Protocol (SNMP) agent subsystem that provides an alarm management interface on the Cisco MGC. It uses SNMP to report events, or traps (such as alarms), to your SNMP Manager and to provide access to the Cisco MGC Management Information Base (MIB).

Note See "Sample Cisco Media Gateway Controller Configuration Files" for an example of a configured snmpd.cnf file. This sample configuration enables both snmpv1 and snmpv2 traps. Therefore, you will see two coldStart traps when the software is initialized—one for version 1 and one for
version 2.

The SNMP agent subsystem reports the following event categories to your SNMP Manager:

1. Communications

2. Quality of Service

3. Processing

4. Equipment

5. Environment

In a continuous-service or high-availability configuration, the SNMP agent subsystem runs on both the active and standby machines.

Note SNMP MIB measurements are only valid only on the active node. They are not replicated on the standby node.

To configure the SNMP resources, complete the following steps:

Step 1 Log in to the Cisco MGC and change to the /etc directory.

Step 2 Verify that the services file lists the following default SNMP ports:
snmp      161/udp
snmp-trap 162/udp
If the ports are listed, proceed to Step 9. If not, continue to Step 3.

Step 3 If the default SNMP ports are not listed (not present), edit the /etc directory by using an editor such as vi to add these two lines for snmp and snmp-trap port information.
# vi services
snmp 161/udp
snmp-trap 162/udp
Step 4 Verify that the file is properly edited by typing the following command and pressing Enter:
#more services
The following lines should display among other port entries (otherwise, repeat Step 3):
snmp      161/udp
snmp-trap 162/udp
Step 5 Verify that the SNMP process is running by entering the following command and pressing Enter:
ps -ef | grep snmpd
Step 6 Stop the existing SNMP process by typing the following command then pressing Enter. This command automatically restarts the SNMP process with a new ID.
kill -HUP <process ID>
Step 7 Verify that the SNMP process is running by entering the following command and pressing Enter:
ps -ef | grep snmpd
Step 8 Verify that the SNMP process is no longer generating errors by checking the snmpd.log. Type the following command and press Enter:
# more/tmp/snmpd.log
If no errors are found, this means the process is working and you can use the ports for SNMP configuration and trap generation.

Step 9 Using FTP, transfer the following MIBs (located in /opt/CiscoMGC/snmp) from the Cisco MGC to the machine on which the SNMP Manager runs:

•CISCO-SMI.my

•v3-tgt.my

•tp.my

•provisioning.my

•measurement.my

Step 10 Load the MIBs into the SNMP Manager. (For example, you can use the xnmnloadmib -load command from HP OpenView.)

Tips For more detailed information about configuring HP OpenView, see "HP OpenView Sample SNMP Configuration."

Note See your SNMP Manager documentation for more information. We do not recommend an SNMP Manager; however, this chapter gives examples using the Hewlett-Packard (HP) OpenView Network Node Manager.

Example 4-1 HP OpenView Example
If you are using HP OpenView Network Node Manager as your SNMP manager, follow these 
procedures to load your MIB:
(a) Select Options from the File Menu and choose Load/Unload MIBs:SNMP.
(b) From the Load/Unload MIBs: SNMP window (on the lower left of your screen).
(c) Click the Load... button.
(c) From the "Load/Unload MIBs:SNMP /Load MIB from File" window, select the MIB to load 
(for example, tp.my).
(d) Click OK.
Step 11 Connect the SNMP events to an event category to display the event. As Cisco MGC events are connected, you can alter the format of the event messages for easier viewing.

Note On many SNMP Managers, event categories can be added so that customer-specific events can be mapped to corresponding categories.

Example 4-2 HP OpenView Event Configuration Example
If you are using HP OpenView Network Node Manager, follow these procedures to configure an 
event:
(a) Select Options from the File Menu and choose Event Configuration.
(b) From the Event Configuration window, in the Enterprise Identification list, select 
transpath.
(c) In the Event Identification list, double click on each of the event types, one at a 
time.
(d) If desired, change the event information display. To change the format of an event, 
from the Event Configurator / Modify Event window, enter a format in the Event Log Message 
Box to change the format and labels for received events of this type. 
The following example shows how an event can be reformatted using the HP OpenView Network 
Node Manager.
ID# $13   Name $12   Set $10   MMLname $4   CatDesc    $11  \nCompDesc $3   Severity $8   
CompID $6   CompType $5   CatID $14\nAlarmNotify $9   AlarmTime$1   ParentID $2   
AlarmReported $7\n$o
Tips For more detailed information about configuring HP OpenView, see "HP OpenView Sample SNMP Configuration."

Step 12 To verify that SNMP is working, log in to the Cisco MGC as root and enter the traprcv command.

The traprcv window shows traps being sent from the SNMP daemon. Following is an example of a traprcv session:
Traprcv Session 
Waiting for traps.
     Received SNMPv2c Trap:
     Community: public
     From: 127.0.0.1
     sysUpTime.0 = 304785432
     snmpTrapOID.0 = processingError
     tpAlarmTime.0 = 0xef68e93c00159dc8
     tpComponentParentId.0 = 131079
     tpComponentDesc.0 = Measurement Manager
     tpComponentName.0 = MM-01
     tpComponentType.0 = 3
     tpComponentId.0 = 196611
     tpAlarmReported.0 = yes(2)
     tpAlarmSeverity.0 = major(3)
     tpAlarmNotify.0 = no(1)
     tpAlarmSet.0 = clear(1)
     tpAlarmCatDesc.0 = Required process MOOS
     tpAlarmCatName.0 = MAJOR M-OOS
     tpAlarmCatId.0 = 64
     tpAlarmId.0 = 0
      
     Received SNMPv2c Trap:
     Community: public
     From: 127.0.0.1
     sysUpTime.0 = 304786908
     snmpTrapOID.0 = processingError
     tpAlarmTime.0 = 0xef68e93c00159dc8
     tpComponentParentId.0 = 131079
     tpComponentDesc.0 = Measurement Manager
     tpComponentName.0 = MM-01
     tpComponentType.0 = 3
     tpComponentId.0 = 196611
     tpAlarmReported.0 = yes(2)
     tpAlarmSeverity.0 = major(3)
     tpAlarmNotify.0 = no(1)
     tpAlarmSet.0 = clear(1)
     tpAlarmCatDesc.0 = Required Process Failure
     tpAlarmCatName.0 = SOFTW REQ
     tpAlarmCatId.0 = 5
     tpAlarmId.0 = 0
     _
Step 13 Verify that your SNMP Manager shows the same traps as the traprcv session. If you do not see the events in your SNMP Manager, you might have a port mismatch or an incorrect IP address in your configuration.

Note Traprcv can receive trap events from multiple Cisco MGCs. To send trap events from a Cisco MGC to the machine where traprcv is running, set the SNMP target IP address (snmpTargetAddrEntry in the snmpd.cnf file) in the Cisco MGC Manager (CMM) and load the new configuration.

This completes the SNMP support resource configuration. Continue to the next section to configure the execution environment. If you have questions or need assistance, see the "Obtaining Technical Assistance" section.

Configuring the Execution Environment

This section provides instructions for configuring the Cisco MGC execution environment and contains the following topics:

•Changing XECfgParm.dat File Parameters

•Changing XECfgParm.dat File Parameters in a Running Continuous-Service or High-Availability System

•Configuring Basic System Information

•Specifying IP Addresses

•Configuring Engine Parameters

•Enabling Call Screening

•Configuring Call Detail Record File Output

•Configuring the System Type

•Configuring the Clearing Location and Default Location Parameters

•Configuring Switchover

•Configuring Switchover

•Initializing the Provisioning Object Manager

The configuration data file, or XECfgParm.dat file (located in /opt/CiscoMGC/etc/XECfgParm.dat), lists all of the components in the Cisco MGC and defines how it operates. You must manually edit the execution environment parameters in the XECfgParm.dat file to initialize and configure the Cisco MGC software application. (For more detailed information on XECfgParm.dat parameters, refer to "XECfgParm.dat File Parameters" and Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.)

Note For an example of a configured XECfgParm.dat file, see "Sample Cisco Media Gateway Controller Configuration Files".

Caution To ensure that your system will work as intended, do not edit any XECfgParm.dat file parameters that are not listed below, and remember that all parameters are case-sensitive.

Do not modify the processes.dat file. This XECfgParm.dat file should remain unmodified, as delivered with the MGC software. If this file is modified, procM may core dump when you start the MGC software.

Changing XECfgParm.dat File Parameters

For a complete list of parameters, their functions, definitions, and sample values, see "XECfgParm.dat File Parameters".

If you have a continuous-service or high-availability system with two Cisco MGC hosts, the XECfgParm.dat files are different for each host. See "Sample Cisco Media Gateway Controller Configuration Files".

To change the XECfgParm.dat file parameters, perform the following steps:

Step 1 Log in as root and go to the # prompt.

Step 2 If the Cisco MGC software is running, enter the following command:
/etc/init.d/CiscoMGC stop
Wait until the system returns the following response:
Signalling procM to shut down
...shutdown complete 
Step 3 Change to the /opt/CiscoMGC/etc directory, which contains the XECfgParm.dat file used by your system.

Step 4 Open the XECfgParm.dat file with any text editor, such as vi.

Step 5 Save your changes and close the editor.

Step 6 Restart the Cisco MGC software by entering the following command:
/etc/init.d/CiscoMGC start
Note Do not restart the software yet if you need to configure SCP queries or initialize the call screening database. Complete the instructions in the appropriate sections of this chapter before restarting the software.

This completes the XE configuration. Continue to the "Configuring SCP Queries" section to configure Service Control Point (SCP) queries using transaction capabilities application part (TCAP). If you have questions or need assistance, see the "Obtaining Technical Assistance" section.

Changing XECfgParm.dat File Parameters in a Running Continuous-Service or High-Availability System

To change parameters in a running continuous-service or high-availability system without call interruption, perform the following steps:

Step 1 Log in to the standby host (Host Y) and stop the Cisco MGC software by entering the following command:
/etc/init.d/CiscoMGC stop
Step 2 Open the XECfgParm.dat file, change the parameters, and save your changes. See "Changing XECfgParm.dat File Parameters" section for more specific instructions.

Step 3 Restart the Cisco MGC software by entering the following command:
/etc/init.d/CiscoMGC start
Step 4 Log in to the active host (Host X) and stop the Cisco MGC software by entering the following command:
/etc/init.d/CiscoMGC stop
Stopping the software on Host X causes switchover to the standby, Host Y. Host Y becomes active and takes over call processing.

Tips If Host Y does not take over call processing after switchover, restart the software on Host X to take over the calls. Check the parameters you changed on Host Y and make sure you have the correct values.

Step 5 On Host X, open the XECfgParm.dat file, change the parameters, and save your changes. See the "Changing XECfgParm.dat File Parameters" section for more specific instructions.

Step 6 Restart the Cisco MGC software on Host X by entering the following command:
/etc/init.d/CiscoMGC start
Step 7 On Host Y, the currently active host, enter the MML command SW-OVER::CONFIRM to switch call processing from Host Y to the newly changed Host X. Host X becomes active.

Tips If Host X does not take over call processing after switchover, restart the software on Host Y to take over the calls. Check the parameters you changed on Host X and make sure you have the correct values.

Configuring Basic System Information

To configure basic system information required for your system to function, modify the following parameters in the first section of the XECfgParm.dat file:

Parameter

Modification

*.transpathId

To identify the local Cisco MGC host in a continuous-service or high-availability system, enter any one- or two-digit integer.

Note If you have two Cisco MGC hosts in a continuous-service or high-availability system, this number must be different in the XECfgParm.dat file for each host.

*.ownTranspathId

To identify the local Cisco MGC host in a continuous-service or high-availability system, enter the same value that you used for *.transpathID.

Note If you have two Cisco MGC hosts in a continuous-service or high-availability system, enter this value in the *.peerTranspathID field in the XECfgParm.dat file on the second host server. If you have a simplex system, leave this field blank.

*.peerTranspathId

To identify the peer Cisco MGC host in a continuous-service or high-availability system, enter any one- or two-digit integer. The IDs must be unique in an active and a standby pair.

Note If you have two Cisco MGC hosts in a continuous-service or high-availability system, enter the same value that you used for *.transpathID in the XECfgParm.dat file of the second host server in this field. If you have a simplex system, leave it blank.

*.desiredPlatformState

To determine the desired platform state at initialization, enter one of the following values:

•master—If you have two (active and standby) Cisco MGC hosts, and you are editing the file on the active host

•slave—If you have two (active and standby) Cisco MGC hosts, and you are editing the file on the standby host

•standalone—If you have a simplex system

Note If you have two Cisco MGC hosts in a continuous-service or high-availability system, make sure that the active Cisco MGC is set to master and the standby host is set to slave.

*.SysCheckpointEnabled

To enable or disable checkpointing, enter one of the following values:

•false—Disables checkpointing. Calls are not preserved during a switchover, and status messages are not sent to the replicator (default).

•true—Enables checkpointing. Calls that are in the talking state are preserved and survive a control switchover. All status checkpointing information is sent to the replicator on the active side.

Note If you have two Cisco MGC hosts in a switchover configuration, enter true. If you have a standalone configuration, enter false.

*.numberOfThreads

To specify the number of threads generated by multithreaded processes such as the engine and the log master, enter one of the following values:

•0—Single CPU (default)

•1—Two CPUs

•2—Four CPUs

Note If you have a multi-CPU system, the engine.SysGeneratedCode parameter must be left as true (the default).

*.stPort

Port number used between peer components or processes.

Enter any unused port number greater than 1024; for example, 7000.

Note If you have two Cisco MGC hosts in a continuous-service or high-availability configuration, enter a different number for this value in the XECfgParm.dat file on the secondary host; for example, 7001.

*.OwnClli

Common language location identifier. To initiate circuit query validation if circuit queries are supported, enter an alphanumeric string of as many as 24 characters.

Default: TTT-SS-BB-XXX

Example: 1-22-33-444

Specifying IP Addresses

To specify IP addresses, modify the following parameters in the first section of the XECfgParm.dat file:

Note If there are two Ethernet interfaces defined on the Cisco MGC, it is mandatory to have these on distinct subnets.

For example, consider the following configuration:
*.ipAddrLocalA = 172.22.119.108
*.ipAddrLocalB = 172.22.119.54
This is not a valid combination because the Ethernet interfaces are on the same subnet. The following example illustrates a valid combination:
*.ipAddrLocalA = 172.22.119.108
*.ipAddrLocalB = 172.22.120.54
If the two Ethernet interfaces are on the same subnet, then one of them must be physically disconnected from the existing subnet and then connected to a different subnet. The new IP address must be appropriately configured on the system. Refer to the manual pages for the UNIX command ifconfig for more information.

Parameter

Modification

*.ipAddrLocalA

Enter the first local IP address; used for checkpointing and switchover heartbeats.

Note This address is the same value as *.IP_Addr1, and is the hme0 interface.

Caution No other machine on the network should have *.ipAddrLocalA set to 0.0.0.0.

*.ipAddrPeerA

Enter the first corresponding peer IP address; used for checkpointing and switchover heartbeats.

Note If you have two Cisco MGC hosts in a continuous-service or high-availability configuration, this value is set to the IP address of the second host.

*.ipAddrLocalB

Enter the second local IP address; used for checkpointing and switchover heartbeats. This is the address of the hme1 interface.

Note If your configuration does not use a secondary Ethernet adapter, leave this address set to the default value, 0.0.0.0.

*.ipAddrPeerB

Enter the second corresponding peer IP address; used for checkpointing and switchover heartbeats. This is the address of the hme1 interface on the second host.

Note If your configuration does not use a secondary Ethernet adapter, leave this address set to the default value, 0.0.0.0.

*.IP_Addr1

Enter the IP address of the hme0 interface.

*.IP_Addr2

Enter the IP address of the hme1 interface (if configured).

*.IP_Addr3

Enter the IP address of the hme2 interface (if configured).

*.IP_Addr4

Enter the IP address of the hme3 interface (if configured).

Configuring Engine Parameters

In order for the engine to run correctly, you must modify the following parameters in the Engine section of the XECfgParm.dat file:

Parameter

Modification

engine.CALL_MEM_BLOCK_SIZE

Block of memory allocated per call.

Used by MDL.

Default: 0

•For memory-critical configurations, use the default value.

•For performance-critical configurations, set this value to 110000.

engine.CALL_MEM_CHUNK_SIZE

Memory chunks allocated from the block of memory designated with engine.CALL_MEM_BLOCK_SIZE.

Default: 0

•For memory-critical configurations, use the default value.

•For performance-critical configurations, set this value to 110000.

engine.SysCdrCollection

To designate the format of call detail records (CDRs), enter one of the following values:

•true—Generates fold-style nontagged CDRs

•false—Generates new tag, length, and value (TLV) format CDRs (default)

Note Typically, this value should be false.

engine.SysVirtualSwitch

To indicate whether the Cisco MGC host functions as a signaling controller or a virtual switch controller, enter one of the following values:

•0—Signaling controller (nailed trunks, no auditing is initiated)

•1—Virtual switch controller (switched trunks)

engine.SysGRSTimerInterval

To specify the interval between blocks of Circuit Group Reset (GRS) messages when the engine.SysGRSBlockSize parameter is used, set to the value required (in milliseconds).

engine.SysGRSBlockSize

Many GRS messages can become due for sending at the same time. This situation occurs if you have set the *.GRSEnabled parameter to true during provisioning. The *.GRSEnabled parameter is a property that is set on an SS7 signaling service (in the CMM) or an SS7 path (in MML).

GRS messages can be staggered if you send them in blocks. Set the engine.SysGRSBlockSize parameter to the number of messages to be sent in each block. Use the engine.SysGRSTimerInterval parameter to set the time from the start of one block to the start of the next.

Default: 0

Note This parameter operates independently for each SS7 route (each OPC/DPC pair).

engine.SysGeneratedCode

To determine whether compiled or interpreted code is used, enter one of the following values:

•true—System uses compiled code (default).

•false—System uses interpreted code (used only for engineering and debugging).

Note Compiled code runs faster than interpreted code. Typically, this value should be true. If your configuration uses multiple CPUs, this value must be true.

Configuring Automatic Congestion Control

As of release 7.4(11), the Cisco MGC supports Automatic Congestion Control (ACC). ACC regulates traffic to levels that can be handled effectively by the network by rejecting traffic when the system is congested. This increases the throughput of completed calls through the telephone network during periods of overload.

When the Cisco MGC is congested, an Automatic Congestion Level (ACL) indication is sent to adjacent signaling points using SS7 ISUP. Until the congestion abates, a certain percentage of calls are rejected. Detection of congestion is based on the measurement of the Cisco MGC's CPU utilization level.

ACC is controlled by parameters that are found in the XECfgParm.dat file and by a property associated with the signaling service, which are described in the following sections:

•Overload Level Percentage Parameters

•CPU Timer Interval Parameter

•Maximum ACL Value

Overload Level Percentage Parameters

Use the following XECfgParm.dat parameters to set the overload level percentages:

Parameter

Description

Default Value

Valid Range

Ovl1OnsetThresh

Percentage of total CPU utilization at which overload level 1 is reached.

82

0 through 100

Ovl1AbateThresh

Percentage of total CPU utilization at which overload level 1 abates.

75

0 through 100

Ovl1RejectPercent

Percentage of calls that are rejected while overload level 1 is active.

25

0 through 100

Ovl2OnsetThresh

Percentage of total CPU utilization at which overload level 2 is reached.

90

0 through 100

Ovl2AbateThresh

Percentage of total CPU utilization at which overload level 2 abates.

77

0 through 100

Ovl2RejectPercent

Percentage of calls that are rejected while overload level 2 is active.

50

0 through 100

Ovl2OnsetThresh

Percentage of total CPU utilization at which overload level 2 is reached.

93

0 through 100

Ovl2AbateThresh

Percentage of total CPU utilization at which overload level 2 abates.

85

0 through 100

Ovl2RejectPercent

Percentage of calls that are rejected while overload level 2 is active.

100

0 through 100

CPU Timer Interval Parameter

The CPUTimerInterval parameter is used to specify the interval, in milliseconds, at which the CPU utilization level of the Cisco MGC is sampled. The default value is 1000. We recommend that you stay within the range of 500 to 2000 milliseconds.

Maximum ACL Value

Another component in ACC is the maximum ACL value. Since ANSI- and ITU-based signaling points have different maximum ACL values, the Cisco MGC uses a property, MaxACL, associated with an SS7 signaling service or trunk group to map the internal maximum ACL value to the value used by the adjacent signaling point.

When the Cisco MGC is congested, its congestion level can be reported to adjacent signaling points by the ACL value in the release message. ANSI-based signaling points use a range of 0 through 3 to define congestion and ITU-based signaling points use a range of 0 through 2 to define congestion. When MaxACL is set to 3, the internal maximum ACL value is mapped to the ANSI standard (the default value for MaxACL is 3). When MaxACL is set to 2, the internal maximum ACL value is mapped to the ITU standard. MaxACL also has a third possible setting, 0, which disables the sending of ACL indications in the Release message.

The procedure to set this property can be found in the Cisco MGC Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Enabling Call Screening

To initialize the database that stores call screening information, modify the following parameter in the Engine section of the XECfgParm.dat file:

Parameter

Modification

engine.SysScreeningCheck

To enable or disable the A-number and B-number analysis in the call screening database, enter one of the following values:

•If you do not have the database environment set with all the required data populated, set this value to false (default).

•If you have the database and want the system to access it, set this value to true.

Configuring Call Detail Record File Output

To configure call detail record (CDR) file output, modify the following parameters in the Data Dumper and Engine sections of the XECfgParm.dat file:

Parameter

Modification

engine.CDRencodingFormat

To specify the call detail record (CDR) file encoding format, enter one of the following values:

•AnsiCDB—North American (default)

•ItuCDB—European

engine.CDRtimeStamp

To specify the CDR file time-stamp unit, enter one of the following values:

•S—Seconds (default).

•M—Milliseconds; use this parameter if your configuration uses TCAP.

Note If you use 1110 in the engine.CDRmessageTypes parameter (for TCAP), you must specify milliseconds for the CDRtimeStamp value.

engine.CDRmessageTypes

To specify which call detail blocks (CDBs, statistics taken at various points in a call) are recorded during a call, enter one of the two following sets of values (each number represents a point in a call):

•1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080—Use this value if your CDR files will be read by a measurement server or by another CDR reader.

•1060, 1110—Use this value if you will use the TLV converter to view CDR files.

1110—Generates a CDR file containing all CDBs for a call (end of call). If you choose 1110, you must specify milliseconds in the CDRtimeStamp parameter.

1060—Required.

1080—An external value, used for TCAP.

CDRDmpr.CDR

To indicate whether the standard data dumper writes out CDR files, enter one of the following values:

•true—Standard data dumper opens a CDR file and logs call detail blocks (CDBs).

•false—Standard data dumper does not open a CDR file and does not log CDBs.

Note The default CDR file format has been changed from an ASCII format in Release 4 to a binary format in Release 7. Use the dmpr.callDetail parameter to convert the files to an ASCII format, if necessary.

CDRDmpr.callDetail

If your configuration requires ASCII-formatted CDR files, enter /opt/CiscoMGC/bin/converter.

Default: /opt/CiscoMGC/local/cdbscript.sh

Use this value if you have created a script to process CDRs; this script is stored as cdbscript.sh.

Optional: /opt/CiscoMGC/bin/converter

Use this value if binary CDR files need to be converted to ASCII.

For maximum performance, change this value to none, as follows:

cdrDmpr.callDetail = #

Note The default CDR file format is binary format. The command above automatically generates CDR files in an ASCII, comma-delimited format in addition to the default, binary format. The ASCII file has a .csv extension. For more information on generating and viewing CDR files, as well as detailed descriptions of CDR file elements, see Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Configuring the System Type

To configure system alarm information, modify the following parameter in the XE section of the XECfgParm.dat file:

Parameter

Modification

XE.systemType

To specify the system type for alarm LEDs, enter one of the following values:

•NETRA—Sun Solaris Netra t 1100, t 1120 (internal LEDs, alarm relays)

•SPARC—Generic box (no alarm relays)

•SPARC-ARU—Generic box (external alarm relays)

Default: SPARC

Configuring the Clearing Location and Default Location Parameters

This property overrides the Clearing Location and Default Location fields in Call Context. Change the clearing location value if you need a value other than the default to be sent to the switch. Change the default location value if you need to define a customer-specific default location for your system that can differ from the default location set in the type definition of the protocol.

Parameter

Modification

ClearingLocation

This property overrides the Clearing Location field in Call Context. Change this value if you need a value other than the default to be sent to the switch. Valid values are:

•0—The Cisco MGC software uses the default Clearing Location in Call Context.

•1—The Cisco MGC software overrides the Clearing Location in Call Context with LOCATION_USER.

•2—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PRIVATE_LOCAL.

•3—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PUBLIC_LOCAL.

•4—The Cisco MGC software overrides the Clearing Location in Call Context with LOCATION_TRANSIT.

•5—The Cisco MGC software overrides the Clearing Location in Call Context with LOCATION_ PUBLIC_REMOTE.

•6—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PRIVATE_REMOTE.

•7—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ INTERNATIONAL.

•8—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ INTERWORKING.

•9—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ LOCAL_INTERFACE.

•10—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ LOCAL_LOCAL.

•11—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ LOCAL_REMOTE.

•12—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PACKET_MANAGER.

•13—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ UNKNOWN.

DefaultLocation

This property overrides the Default Location field in Call Context. Change this value if you need to define a customer-specific default location for your system that can differ from the default location set in the type definition of the protocol. Valid values are:

•0—The Cisco MGC software uses the Default Location in Call Context.

•1—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_USER.

•2—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PRIVATE_LOCAL.

•3—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PUBLIC_LOCAL.

•4—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_TRANSIT.

•5—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PUBLIC_REMOTE.

•6—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PRIVATE_REMOTE.

•7—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ INTERNATIONAL.

•8—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ INTERWORKING.

•9—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ LOCAL_INTERFACE.

•10—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ LOCAL_LOCAL.

•11—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ LOCAL_REMOTE.

•12—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PACKET_MANAGER.

•13—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ UNKNOWN.

Configuring *.GWClearChannelAlgorithm Parameter

Clear channel calls get through only if you set the *.GWClearChannelAlgorithm parameter to a value other than null. This parameter is sent to the Cisco MGC when the connection is created and matches the Cisco MGC's clear channel parameter.

Configuring Switchover

To configure switchover, modify the following parameters in the Foverd section of the XECfgParm.dat file:

Parameter

Modification

foverd.conn1Type

To set the connection type for connection number 1, enter serial or socket.

Note Typically, set this value to socket.

foverd.ipLocalPortA

To define the local port number used for IP communication, enter a unique number, keeping the following in mind:

•Typically, if Type is socket, set this value to 1051.

•If you have two Cisco MGC hosts in a continuous-service or high-availability configuration, enter the foverd.ipLocalPortA value in the foverd.ipPeerPortA field in the XECfgParm.dat file on the secondary host.

Caution The value of foverd.ipLocalPortA must be unique for every host on the network. Otherwise, active and standby hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipLocalPortA set to 1051. If another machine does have that value, the active and standby hosts cannot perform proper switchover.

foverd.ipPeerPortA

To define the peer port number used for IP communication, enter a unique number, keeping the following in mind:

•Typically, if Type is socket, set this value to 1052.

•If you have two Cisco MGC hosts in a switchover configuration, enter the foverd.ipPeerPortA value in the foverd.ipLocalPortA field in the XECfgParm.dat file on the secondary host.

Caution The value of foverd.ipPeerPortA must be unique for every host on the network. Otherwise, active and standby hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipPeerPortA set to 1052. If another machine does have that value, the active and standby hosts cannot perform proper switchover.

foverd.conn2Type

To set the connection type for connection number 2, enter serial or socket.

Note Typically, set this value to socket.

foverd.ipLocalPortB

To define the secondary local port number used for IP communication, enter a unique number, keeping the following in mind:

•Typically, if Type is socket, set this value to 1053.

•If you have two Cisco MGC hosts in a switchover configuration, enter this value in the foverd.ipPeerPortB field in the XECfgParm.dat file on the secondary host.

Caution The value of foverd.ipLocalPortB must be unique for every host on the network. Otherwise, active and standby hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipLocalPortB set to 1053. If another machine does have that value, the active and standby hosts cannot perform proper switchover.

foverd.ipPeerPortB

To define the secondary local port number used for IP communication, enter a unique number, keeping the following in mind:

•Typically, if Type is socket, set this value to 1054.

•If you have two Cisco MGC hosts in a switchover configuration, enter this value in the foverd.ipLocalPortB field in the XECfgParm.dat file on the secondary host.

Caution The value of foverd.ipPeerPortB must be unique for every host on the network. Otherwise, master and slave hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipPeerPortB set to 1054. If another machine does have that value, the master and slave hosts cannot perform proper switchover.

foverd.conn3Type

To set the connection type for connection number 3, enter serial or socket.

Note Typically, set this value to serial.

foverd.conn3Addr

To specify the address of the peer system, enter a location; for example, /dev/term/a.

If your configuration does not use connection number 3, enter /dev/null (default).

Note If your configuration uses an 8-port connector as a serial connection for switchover, you must modify the read-write permissions for the connection. For more information, see Release Notes for Cisco Media Gateway Controller Software Release 7.

foverd.abswitchPort

To specify the port used for communication with the A/B switch, enter a location; for example, /dev/term/a.

Note If your configuration does not use an A/B switch, use the default value (/dev/null).

foverd.heartbeatInterval

Specifies the maximum time in milliseconds between heartbeat messages from the peer switchover daemon. This interval defines the frequency with which the switchover daemon exchanges heartbeat messages with its peer.

Default: 4000 milliseconds (4 seconds).

:

Note For more information on switchover, see Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Initializing the Provisioning Object Manager

To configure the Provisioning Object Manager (POM), modify the following parameters in the POM section of the XECfgParm.dat file:

Parameter

Modification

pom.dataSync

Used in a continuous-service or high-availability system to indicate that the POM should synchronize the provisioning data at startup.

•If you have a standalone system, set this value to false.

•If you have a continuous-service or high-availability system, this value is true (default).

Caution If pom.dataSync is set to true for a continuous-service or high-availability system, you must ensure that you are running the same version of the Cisco MGC software on both active and standby machines. Otherwise, the wrong version of your data files might be copied to the other machine.

pom.port

Used in a continuous-service or high-availability configuration to indicate the port number that the POM uses to communicate with its peer. Enter any integer from 4001 through 4050, or default.

Note This is a platform-specific value and depends on your system installation. You should modify this value only if the default port (4001) is being used by another process or application.

Configuring SCP Queries

The SCP translates routing information for the Advanced Intelligent Network (AIN) database queries over TCAP. This section provides instructions for selecting the type of translation you use to enable SCP database queries. If your site or network requires changes, you can enable SCP queries by manually editing the parameters in the trigger.dat file. The trigger.dat file (located in /opt/CiscoMGC/etc) contains the message-sending table that contains translation values.

This section contains the following topics:

•Before You Start

•Configuring the trigger.dat File Attributes

•Sample trigger.dat File

Warning Do not edit trigger.dat file parameters that are not listed below, and remember that all parameters are case-sensitive. Otherwise, your system might not work as intended.

Before You Start

If you are changing an ANSI query and you need a different Translation Type, you need to know the Translationtype value from the Global Title Translation tables on the Signal Transfer Point (STP). Get this value from the administrator of your STP.

Configuring the trigger.dat File Attributes

Note The trigger.dat file is not overwritten during software installation. All changes to the trigger.dat file are contained in a file called trigger.template that is installed with the new software. If you modify the trigger.dat file after installing a new software release, you need to view the trigger.template file and copy any changes in that file to your trigger.dat file.

Caution Improper editing of the trigger.dat file can cause service interruption and prevent the Cisco MGC from correctly performing SCP database queries.

You can configure the following Cisco MGC trigger.dat file attributes to perform a Transaction Capabilities Application Part (TCAP) query:

•Global Title Translation

•Service Key Value

•Translation Type

Configuring the Global Title Translation Attribute

Perform the following steps to configure the Global Title Translation attribute:

Step 1 Back up the trigger.dat file.

Step 2 Determine the Trigger Number that you need to edit. You can get this information from your network administrator.

Step 3 Navigate to directory /opt/CiscoMGC/etc.

Step 4 Open the trigger definition file in an ASCII text editor and search for the string $TriggerTable.

Step 5 Starting after the $TriggerTable line, count the number of rows equal to the TriggerType beginning from the number 1.

Note Do not count any row that is blank or that begins with a pound sign (#).

Step 6 When you find your row, note down the second number in that row. This number is the index to the $MessageSending table.

Step 7 Edit the file as follows:

a. In the $MessageSending table, select column 9, gtSsn (see Table 4-1).

b. In the table for your translation type, change the Global Title Translation value (column F9) to either 0 or 1. You can get this information from your network administrator. If the number is 0, use GTT. If the number is 1, use PC/SSN.

c. If you change the gtSsn value to 0, you must go to gtFormat in column 16 and reset the value to 0. If you set the value to 1, you must also set column 16 to a non-zero value.

Note See Table 4-1 for table values.

Step 8 Save your changes and close the editor.

Step 9 For your changes to take effect you must reboot the Cisco MGC by entering the following command:
# /etc/init.d/CiscoMGC start
Configuring the Service Key Value Attribute

Perform the following steps to configure the Service Key Value (tcv_sk) attribute:

Step 1 Back up the trigger.dat file.

Step 2 Determine the Trigger Number that you need to edit. You can get this information from your network administrator.

Step 3 Navigate to directory /opt/CiscoMGC/etc.

Step 4 Open the trigger definition file in an ASCII text editor and search for the string $TriggerTable.

Step 5 Starting after the $TriggerTable line, count the number of rows equal to the TriggerType beginning from the number 1.

Note Do not count any row that is blank or that begins with a pound sign (#).

Step 6 When you find your row, note down the second number in that row. This number is the index to the $MessageSending table.

Caution Do not change TCVs. You must verify that column 2 is equal to 1 before changing tcv_sk. If column 2 is not equal to 1, this is not an ETSI trigger and column 6 is a TCV, not an SK.

Step 7 Edit the file as follows:

a. In the $MessageSending table, select tcv_sk, in column 6 (see Table 4-1).

b. In the table, change the value for tcv_sk to a value from 0 through 255. You can get this information from your network administrator.

Step 8 Save your changes and close the editor.

Step 9 Restart the Cisco MGC software by entering the following command:
# /etc/init.d/CiscoMGC start
Configuring the Translation Type Attribute

Perform the following steps to configure the Translation Type (translationType) attribute:

Step 1 Back up the trigger.dat file.

Step 2 Determine the Trigger Number that you need to edit. You can get this information from your network administrator.

Step 3 Navigate to directory /opt/CiscoMGC/etc.

Step 4 Open the trigger definition file in an ASCII text editor and search for the string $TriggerTable.

Step 5 Starting after the $TriggerTable line, count the number of rows equal to the TriggerType beginning from the number 1.

Note Do not count any row that is blank or that begins with a pound sign (#).

Step 6 When you find your row, note down the second number in that row. This number is the index to the $MessageSending table.

Caution You must verify that column 2 is equal to 2 or 3 before changing Translation Type. If column 2 is not equal to 2 or 3, this is not an ANSI trigger and Translation Type is not used.

Step 7 Edit the file as follows:

a. In the $MessageSending table, select translationType, in column 7 (see Table 4-1).

b. In the table for your translation type, change the value for translationType to a value from 0 through 255. You can get this information from your network administrator.

Step 8 Save your changes and close the editor.

Step 9 For your changes to take effect you must reboot the Cisco MGC by entering the following command:
# /etc/init.d/CiscoMGC start
Table 4-1
F1

F2

F3

F4

F5

F6

F7

F8

F9

F10

F11

F12

F13

F14

F15

F16

F17

F18

F19

F20

F21

Transport

tcapType

stpScpGroupIndex

msg

asn1Encoding

tcv_sk

translationType

tcapBodyType

gtSsn

dpcPres

ssnPres

dpcNetwork

dpcCluster

dpcMember

ssn

gtFormat

OS1

OS2

OS3

OS4

OS5

# MS 1: xxxxxx LNP
1
2
0
6
0
0
255
1
0
0
1
0
0
0
0
2
1
0
0
0
0
# MS 2: Generic LNP
1
2
0
6
0
37
255
1
0
0
1
0
0
0
0
2
2
0
0
0
0
# MS 3: xxxxxxx 800
2
1
1
1
0
0
0
1
0
0
1
0
0
0
0
2
3
0
0
0
0
# MS 4: ANSI AIN 800 NPA
1
2
0
6
0
4
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0
# MS 5: ANSI AIN 800 NPA-NXX
1
2
0
6
0
5
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0
# MS 6: ANSI AIN 800 NPA-NXX-XXX
1
2
0
6
0
8
255
1
0
0
1
0
0
0
0
2
4
0
0
0
0
# MS 7: ANSI AIN 800 Termination information
1
2
0
5
0
0
255
1
0
0
1
0
0
0
0
2
5
0
0
0
0
# MS 8: ANSI PRE AIN 800
1
3
0
6
0
0
254
2
0
0
1
0
0
0
0
2
6
0
0
0
0
# MS 9: ANSI PRE AIN 800 Termination information
1
3
0
5
0
0
254
2
0
0
1
0
0
0
0
2
7
0
0
0
0
$MessageSending Table Values
Sample trigger.dat File
#--//******************************************************************************
#--//* Table_9.trigger                                                            *
#--//*                                                                            *
#--//* TRIGGER TABLES                                                             *
#--//*                                                                            *
#--//* (c) 1999-2000 CISCO SYSTEMS, INC..  ALL RIGHTS RESERVED.                   *
#--//* THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF       *
#--//* CISCO SYSTEMS, INC..  USE, DISCLOSURE, OR REPRODUCTION IS PROHIBITED       *
#--//* WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF THE CISCO SYSTEMS, INC..   *
#--//*                                                                            *
#--//******************************************************************************
# "$Id: Table_9.trigger,v 1.11.2.3 1999/09/20 18:20:51 xxxxxxxx Exp $";
# "(c) 1999-2000 Cisco Systems, Inc..  All Rights Reserved."
#############
$TriggerTable
#############
# All fields are pointers to records of other types
# F1   F2   F3   F4   F5   F6   F7
# MA   MS   RR1  RR2  RR3  RR4  RR5
#----------------------------------
# TT 1: xxxxxx LNP
#----------------------------------
  1    1    1    2    0    0    0
#----------------------------------
# TT 2: Generic LNP
#----------------------------------
  2    2    1    3    0    0    0
#----------------------------------
# TT 3: xxxxxxx 800
#----------------------------------
  3    3    10   4    5    0    0
#----------------------------------
# TT 4: ANSI AIN 800 NPA
#----------------------------------
  4    4    10   6    7    0    0
#----------------------------------
# TT 5: ANSI AIN 800 NPA-NXX
#----------------------------------
  4    5    10   6    7    0    0
#----------------------------------
# TT 6: ANSI AIN 800 NPA-NXX-XXXX
#----------------------------------
  4    6    10   6    7    0    0
#----------------------------------
# TT 7: ANSI AIN 800 Termination Information
#----------------------------------
  5    7    10   0    0    0    0
#----------------------------------
# TT 8: ANSI PRE AIN AIN 800
#----------------------------------
  4    8    10   8    9    0    0
#----------------------------------
# TT 9: ANSI PRE AIN 800 Termination Information
#----------------------------------
  5    9    10   0    0    0    0
##############
$MessageAction
##############
#
# F1   F2   F3   F4   F5   F6   F7   F8   F9   F10
# ACT1 REQ  ACT2 REQ  ACT3 REQ  ACT4 REQ  ACT5 REQ
#-------------------------------------------------
# MA 1: xxxxxx LNP
#-------------------------------------------------
  1    1    3    0    0    0    0    0    0    0
#-------------------------------------------------
# MA 2: Generic LNP
#-------------------------------------------------
  1    1    2    1    3    0    0    0    0    0
#-------------------------------------------------
# MA 3: xxxxxxx 800
#-------------------------------------------------
  1    1    3    0    0    0    0    0    0    0
#-------------------------------------------------
# MA 4: ANSI AIN 800 / ANSI PRE AIN 800
#-------------------------------------------------
  1    1    3    0    0    0    0    0    0    0
#-------------------------------------------------
# MA 5: ANSI AIN 800 Termination Information / PRE AIN 800 Termination Information
#-------------------------------------------------
  4    1    0    0    0    0    0    0    0    0
###############
$MessageSending
###############
#
# gtFormat Values
# GTFORMAT_DO_NOT_USE_GLOBAL_TITLE                 := 0
# GTFORMAT_USE_GLOBAL_TITLE_TRANSLATION_TYPE_NUMBERING_SCHEME_ENCODING_SCHEME := 1
# GTFORMAT_USE_GLOBAL_TITLE_TRANSLATION_TYPE       := 2
# GTFORMAT_USE_GLOBAL_TITLE_ONLY                   := 3
# GTFORMAT_UNKNOWN                                 := 4
#
Note To see proper formatting for the table below, see Table 4-1.
# F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 F13 F14 F15 F16 F17 F18 F19 F20 F21
# transport tcapType stpScpGroupIndex msg asn1Encoding tcv_sk translationType tcapBodyType 
gtSsn dpcPres ssnPres dpcNetwork dpcCluster dpcMember ssn gtFormat OS1 OS2 OS3 OS4 OS5
#----------------------------------------------------------------------------------------
# MS 1: xxxxxx LNP
#----------------------------------------------------------------------------------------
1 2 0 6 0 0 255 1 0 0 1 0 0 0 0 2 1 0 0 0 0
#----------------------------------------------------------------------------------------
# MS 2: Generic LNP
#----------------------------------------------------------------------------------------
1 2 6 37 255 0 1 0 0 2 0 0 0 0
#----------------------------------------------------------------------------------------
# MS 3: xxxxxxx 800
#----------------------------------------------------------------------------------------
2 1 1 0 1 0 0 0 2 0 0
#----------------------------------------------------------------------------------------
# MS 4: ANSI AIN 800 NPA
#----------------------------------------------------------------------------------------
1 2 0 6 0 4 255 1 0 0 1 0 0 0 0 2 4 0 0 0 0
#----------------------------------------------------------------------------------------
# MS 5: ANSI AIN 800 NPA-NXX
#----------------------------------------------------------------------------------------
1 2 0 0 255 0 1 0 0 4 0 0
#----------------------------------------------------------------------------------------
# MS 6: ANSI AIN 800 NPA-NXX-XXX
#----------------------------------------------------------------------------------------
1 2 0 6 0 8 255 1 0 0 1 0 0 0 0 2 4 0 0 0 0
#----------------------------------------------------------------------------------------
# MS 7: ANSI AIN 800 Termination information
#----------------------------------------------------------------------------------------
1 2 0 5 0 0 255 1 0 0 1 0 0 0 0 2 5 0 0 0 0
#----------------------------------------------------------------------------------------
# MS 8: ANSI PRE AIN 800
#----------------------------------------------------------------------------------------
1 3 0 6 0 0 254 2 0 0 1 0 0 0 0 2 6 0 0 0 0
#----------------------------------------------------------------------------------------
# MS 9: ANSI PRE AIN 800 Termination information
#----------------------------------------------------------------------------------------
1 3 0 5 0 0 254 2 0 0 1 0 0 0 0 2 7 0 0 0 0
################
$OperationSending
#################
#
# F1            F2            F3            F4              F5        
# componentType opClass       opCodeFamily  opCodeSpecifier opCodeFlag 
# F6                   F7
# correlationRequired  PS
#----------------------------------------------------------------------------------------
# OS 1: xxxxxx LNP
#----------------------------------------------------------------------------------------
6 1 3 0
#----------------------------------------------------------------------------------------
# OS 2: Generic LNP
#----------------------------------------------------------------------------------------
6 100 4 2
#----------------------------------------------------------------------------------------
# OS 3: xxxxxxx 800
#----------------------------------------------------------------------------------------
1 0 4 3
#----------------------------------------------------------------------------------------
# OS 4: ANSI AIN 800
#----------------------------------------------------------------------------------------
6 100 4 0 4
#----------------------------------------------------------------------------------------
# OS 5: ANSI AIN 800 Termination Information Should have correlationRequired = 1
#----------------------------------------------------------------------------------------
6 1 103 4 4 0 5
#----------------------------------------------------------------------------------------
# OS 6: ANSI PRE AIN 800
#----------------------------------------------------------------------------------------
6 1 3 1 3 0 6
#----------------------------------------------------------------------------------------
# OS 7: ANSI PRE AIN 800 Termination Information
#----------------------------------------------------------------------------------------
2 1 0 0 0 0 7
################
$ParameterSending
#################
#
# F1   F2   F3   F4   F5   F6   F7   F8   F9   F10  F11  F12  F13  F14  F15  F16  F17 F18
# PA1  REQ  PA2  REQ  PA3  REQ  PA4  REQ  PA5  REQ  PA6  REQ  PA7  REQ  PA8  REQ  PA9 REQ
# F19  F20
# PA10 REQ
#----------------------------------------------------------------------------------------
# PS 1: xxxxxx LNP
#----------------------------------------------------------------------------------------
100 1 101 1 102 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#----------------------------------------------------------------------------------------
# PS 2: Generic LNP
#----------------------------------------------------------------------------------------
100 1 101 1 102 1 103 1 0 0 0 0 0 0 0 0 0 0 0 0
#----------------------------------------------------------------------------------------
# PS 3: xxxxxxx 800
#----------------------------------------------------------------------------------------
200 1 201 1 202 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#----------------------------------------------------------------------------------------
# PS 4: ANSI AIN 800 (All types)
#----------------------------------------------------------------------------------------
100 1 101 1 102 1 103 1 104 1 109 0 110 0 111 0 112 0 113 0
#----------------------------------------------------------------------------------------
# PS 5: ANSI AIN 800 Termination Information
#----------------------------------------------------------------------------------------
105 1 106 1 107 0 108 0 0 0 0 0 0 0 0 0 0 0 0 0
#----------------------------------------------------------------------------------------
# PS 6: ANSI PRE AIN 800
#----------------------------------------------------------------------------------------
17 1 2 1 16 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#----------------------------------------------------------------------------------------
# PS 7: ANSI PRE AIN 800 Termination Information
#----------------------------------------------------------------------------------------
21 1 20 1 22 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
#################
$ReceivedResponse
#################
#
# F1   F2
# MR   RA
#----------------------------------------------------------------------------------------
# RR 1: xxxxxx LNP / Generic LNP Default
#----------------------------------------------------------------------------------------
0    1
#----------------------------------------------------------------------------------------
# RR 2: xxxxxx LNP 1st expected
#----------------------------------------------------------------------------------------
1    2
#----------------------------------------------------------------------------------------
# RR 3: Generic LNP 1st expected
#----------------------------------------------------------------------------------------
1    3
#----------------------------------------------------------------------------------------
# RR 4: xxxxxxx 800 1st expected (Result)
#----------------------------------------------------------------------------------------
2    1
#----------------------------------------------------------------------------------------
# RR 5: xxxxxxx 800 2st expected (Error)
#----------------------------------------------------------------------------------------
3    4
#----------------------------------------------------------------------------------------
# RR 6: ANSI AIN 800 With termination status notification
#----------------------------------------------------------------------------------------
4    5
#----------------------------------------------------------------------------------------
# RR 7: ANSI AIN 800
#----------------------------------------------------------------------------------------
5    6
#----------------------------------------------------------------------------------------
# RR 8: ANSI PRE AIN 800 With termination status notification
#----------------------------------------------------------------------------------------
6    7
#----------------------------------------------------------------------------------------
# RR 9: ANSI PRE AIN 800
#----------------------------------------------------------------------------------------
7    8
#----------------------------------------------------------------------------------------
# RR 10: ANSI AIN 800 / PRE AIN 800 Default
#----------------------------------------------------------------------------------------
0    9
#################
$MessageReceiving
#################
#
# F1   F2   F3   F4   F5   F6   F7   F8   F9   F10  F11
# MSG  OR1  REQ  OR2  REQ  OR3  REQ  OR4  REQ  OR5  REQ
#------------------------------------------------------
# MR 1: xxxxxx LNP / Generic LNP
#------------------------------------------------------
  8    1    1    0    0    0    0    0    0    0    0
#------------------------------------------------------
# MR 2: xxxxxxx 800 (Result)
#------------------------------------------------------
  3    2    1    0    0    0    0    0    0    0    0
#------------------------------------------------------
# MR 3: xxxxxxx 800 (Error)
#------------------------------------------------------
  3    3    1    0    0    0    0    0    0    0    0
#------------------------------------------------------
# MR 4: ANSI AIN 800 with termination status notification
#------------------------------------------------------
  8    4    1    5    1    0    0    0    0    0    0
#------------------------------------------------------
# MR 5: ANSI AIN 800
#------------------------------------------------------
  8    4    1    0    0    0    0    0    0    0    0
#------------------------------------------------------
# MR 6: ANSI PRE AIN 800 with termination status notification
#------------------------------------------------------
  8    6    1    7    1    0    0    0    0    0    0
#------------------------------------------------------
# MR 7: ANSI PRE AIN 800
#------------------------------------------------------
  8    6    1    0    0    0    0    0    0    0    0
###################
$OperationReceiving
###################
#
# F1            F2           F3              F4           F5         F6
# componentType opClass      opCodeFamily opCodeSpecifier opCodeFlag PR
#----------------------------------------------------------------------
# OR 1: xxxxxx LNP / Generic LNP
#----------------------------------------------------------------------
  6             1            101          1               4          1
#----------------------------------------------------------------------
# OR 2: xxxxxxx 800 (Result)
#----------------------------------------------------------------------
  1             1            0            20              4          2
#----------------------------------------------------------------------
# OR 3: xxxxxxx 800 (Error)
#----------------------------------------------------------------------
  3             1            0            0               4          3
#----------------------------------------------------------------------
# OR 4: ANSI AIN 800
#----------------------------------------------------------------------
  6             1            101          1               4          4
#----------------------------------------------------------------------
# OR 5: ANSI AIN 800 Request for status notification
#----------------------------------------------------------------------
  6             1            103          5               4          5
#----------------------------------------------------------------------
# OR 6: ANSI PRE AIN 800
#----------------------------------------------------------------------
  6             1            4            1               3          6
#----------------------------------------------------------------------
# OR 7: ANSI PRE AIN 800 Request for status notification
#----------------------------------------------------------------------
  6             1            6            1               4          7
###################
$ParameterReceiving
###################
# F1   F2   F3   F4   F5   F6   F7   F8   F9   F10  F11  F12  F13  F14  F15  F16 
# PA1  REQ  ACT  PA2  REQ  ACT  PA3  REQ  ACT  PA4  REQ  ACT  PA5  REQ  ACT  PA6 
  REQ  F17  F18  F19  F20  F21  F22  F23  F24  F25  F26  F27  F28  F29  F30
  ACT  PA7  REQ  ACT  PA8  REQ  ACT  PA9  REQ  ACT  PA10 REQ  ACT
#----------------------------------------------------------------------------------------
# PR 1: xxxxxx LNP / Generic LNP
#----------------------------------------------------------------------------------------
102  1    1    0    0    0    0    0    0    0    0    0    0    0    0    0    0    0    
0    0    0    0    0    0    0    0    0    0    0    0
#----------------------------------------------------------------------------------------
# PR 2: xxxxxxx 800 (Result)
#----------------------------------------------------------------------------------------
205  1    1    206  1    1    204  1    3    0    0    0    0    0    0    0    0    0    
0    0    0    0    0    0    0    0    0    0    0    0
#----------------------------------------------------------------------------------------
# PR 3: xxxxxxx 800 (Error)
#----------------------------------------------------------------------------------------
205  1    1    206  1    1    204  1    3    0    0    0    0    0    0    0    0    0    
0    0    0    0    0    0    0    0    0    0    0    0
#----------------------------------------------------------------------------------------
# PR 4: ANSI AIN 800 Result
#----------------------------------------------------------------------------------------
102  1    1    110  0    2    113  0    2    114  1    2    115  1    2    0    0    0    
0    0    0    0    0    0    0    0    0    0    0    0
#----------------------------------------------------------------------------------------
# PR 5: ANSI AIN 800 Status request
#-----------------------------------------------------------------------------------------
------------------------------------------------------------
105  1    4    0    0    0    0    0    0    0    0    0    0    0    0    0    0    0    
0    0    0    0    0    0    0    0    0    0    0    0
#-----------------------------------------------------------------------------------------
------------------------------------------------------------
# PR 6: ANSI PRE AIN 800 Result
#-----------------------------------------------------------------------------------------
------------------------------------------------------------
8    0    2    4    1    1    18   0    2    0    0    0    0    0    0    0    0    0    
0    0    0    0    0    0    0    0    0    0    0    0
#----------------------------------------------------------------------------------------
# PR 7: ANSI PRE AIN 800 Status request
#----------------------------------------------------------------------------------------
20   1    4    0    0    0    0    0    0    0    0    0    0    0    0    0    0    0    
0    0    0    0    0    0    0    0    0    0    0    0
###############
$ResponseAction
###############
#
# F1   F2   F3   F4   F5   F6   F7   F8   F9   F10  F11  F12  F13  F14  F15
# ACT1 REQ  DAT  ACT2 REQ  DAT  ACT3 REQ  DAT  ACT4 REQ  DAT  ACT5 REQ  DAT
#--------------------------------------------------------------------------
# RA 1: xxxxxx LNP Default & Generic LNP Default
#--------------------------------------------------------------------------
  4    1    2    0    0    0    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 2: xxxxxx LNP 1st Expected
#--------------------------------------------------------------------------
  4    1    2    0    0    0    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 3: Generic LNP 1st Expected
#--------------------------------------------------------------------------
  1    1    0    4    1    2    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 4: xxxxxxx (Error)
#--------------------------------------------------------------------------
  0    0    0    0    0    0    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 5: ANSI AIN 800 with termination status notification
#--------------------------------------------------------------------------
  2    0    1    4    1    3    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 6: ANSI AIN AIN 800
#--------------------------------------------------------------------------
  4    1    3    0    0    0    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 7: ANSI PRE AIN 800 with termination status notification
#--------------------------------------------------------------------------
  2    0    4    4    1    3    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 8: ANSI PRE AIN 800
#--------------------------------------------------------------------------
  4    1    3    0    0    0    0    0    0    0    0    0    0    0    0
#--------------------------------------------------------------------------
# RA 9: 800 Default
#--------------------------------------------------------------------------
  4    1    3    0    0    0    0    0    0    0    0    0    0    0    0
###########
$ActionData
###########
#
# F1   F2   F3   F4   F5
#-----------------------
# AD 1: ANSI AIN 800  Data for RESULT_ACTION_RE_TRIGGER_VIA_LCM (to send termination 
information)
# Trg  Pic   Null Null Null
#--------------------------
  7    13    0    0    0
# AD 2: ANSI LNP Data for RESULT_ACTION_SEND_ACTION_TO_LCM
# Act  Null Null Null  NULL
#--------------------------
  1    0     0    0    0
# AD 3: ANSI AIN / PRE AIN 800 Data for RESULT_ACTION_SEND_ACTION_TO_LCM
# Act  Null Null Null  NULL
#--------------------------
  2    0     0    0    0
# AD 4: ANSI PRE AIN 800  Data for RESULT_ACTION_RE_TRIGGER_VIA_LCM (to send termination 
information)
# Trg  Pic   Null Null Null
#--------------------------
  9    13    0    0    0
This completes the SCP configuration. Continue to the next section to initialize the call-screening database. If you have questions or need assistance, see the "Obtaining Technical Assistance" section.

Initializing the Call Screening Database

During installation, the installation script (install.sh) installs and initializes a database that the Cisco MGC can use to store call-screening information for calling- and called-number analysis.

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 call screening database is stored in the /opt/TimesTen32/datastore directory. The database name is howdydb. The maximum database size, 256 MB, is specified in the .odbc.ini file shown in the ".odbc.ini File Information" section.

This section contains the following topics:

•.odbc.ini File Information

•Setting Up Replication

•Verifying Database Replication

•Troubleshooting

•Installing and Removing Release 7.4(x) Patches Manually

•Installing the Cisco MGC Software on a Separate Host

Note You cannot change the database name.

.odbc.ini File Information

The .odbc.ini file specifies the location of the database storage. Unless you installed the software in other than the default directory, the .odbc.ini file is located in the /opt/CiscoMGC/local directory. The following is an example of an .odbc.ini file:
[ODBC Data Sources]
howdydb=TimesTen 3.2 Driver
[howdydb]
Driver=/opt/TimesTen32/32/lib/libtten.so
DataStore= /opt/TimesTen32/datastore/howdydb
DurableCommits=0
ExclAccess=0
ThreadSafe=1
WaitForConnect=0
Size=256
[ODBC]
Trace=0
TraceFile=
Installdir=/opt/TimesTen32/32
Setting Up Replication

If you have two Cisco MGC hosts in a continuous-service or high-availability system, you must set up database replication between the two hosts. During replication, any updates applied to the database on one host are replicated on the other. Data is transferred real time and does not require the committing or deploying of a configuration.

Replication copies data changes to either database after the initial setup. However, if you have data on one host, and you want the same data on another host, you must back up and move the data over, in addition to configuring replication.

If this is the initial installation of the software, and you do not have any data in the database, perform the following steps. If you do have data in one database, and want to copy it to the other host, proceed to the "Initializing Replication and Copying the Database to Another Host" section.

Note Before you can initialize the databases, you must install the Cisco MGC software on both machines.

If you have data in both databases, and the databases do not match, contact the TAC for assistance in merging the databases.

Initializing Database Replication

To set up the initial replication, perform the following steps:

Step 1 Log in to the active host as the root user and enter the following command:

setup_replication.sh standbyhost howdydb

where standbyhost is the name (not IP address) of your standby host. In Example 3-8, the active host is hostx and the standby host is hosty.

Caution Do not use IP addresses when setting up database replication. If you do, replication fails.

Example 4-3 Initializing Database Replication on the Active Host
hostx% setup_replication.sh hosty howdydb
   Setting up replication to node hosty for DSN howdydb
   Adding cisco.whitelist_a
   Adding cisco.blacklist_a
   Adding cisco.whitelist_b
   Adding cisco.blacklist_b
   Adding cisco.portednumbers
   Adding cisco.numberterm
RAM Residence Policy            : inUse
RAM Residence Grace (Secs)      : 0
Manually Loaded In Ram          : False
Purge Logs for Data Store       : True
Logging Enabled                 : True
Replication Manually Started    : True
Step 2 Log in to the standby host as the root user and enter the following command:

setup_replication.sh activehost howdydb

where activehost is the name (not IP address) of your active host. In the Example 3-9, the active host is hostx and the standby host is hosty.

Caution Do not use IP addresses when setting up database replication. If you do, replication fails.

Example 4-4 Initializing Database Replication on the Standby Host
hosty% setup_replication.sh hostx howdydb
   Setting up replication to node hostx for DSN howdydb
   Adding cisco.whitelist_a
   Adding cisco.blacklist_a
   Adding cisco.whitelist_b
   Adding cisco.blacklist_b
   Adding cisco.portednumbers
   Adding cisco.numberterm
RAM Residence Policy            : inUse
RAM Residence Grace (Secs)      : 0
Manually Loaded In Ram          : False
Purge Logs for Data Store       : True
Logging Enabled                 : True
Replication Manually Started    : True
Proceed to the "Verifying Database Replication" section.

Initializing Replication and Copying the Database to Another Host

If you have existing data in one database and want to copy the data to another machine—for example, from the active to standby machine—perform the following steps:

Step 1 Log in to the active host as the root user and enter the following command:

setup_replication.sh standbyhost howdydb

where standbyhost is the name (not IP address) of your standby host. In the Example 3-10, the active host is hostx and the standby host is hosty.

Caution Do not use IP addresses when setting up database replication. If you do, replication fails.

Example 4-5 Initializing Database Replication on the Active Host
hostx% setup_replication.sh hosty howdydb
   Setting up replication to node hosty for DSN howdydb
   Adding cisco.whitelist_a
   Adding cisco.blacklist_a
   Adding cisco.whitelist_b
   Adding cisco.blacklist_b
   Adding cisco.portednumbers
   Adding cisco.numberterm
RAM Residence Policy            : inUse
RAM Residence Grace (Secs)      : 0
Manually Loaded In Ram          : False
Purge Logs for Data Store       : True
Logging Enabled                 : True
Replication Manually Started    : True
Step 2 Create a directory for the database backup files using the mkdir command. For example:

mkdir /backupdb

Step 3 Create the backup files by entering the following command:

ttRepAdmin -dsn howdydb -receiver -name standbyhost -backup dirname

where standbyhost is the name (not IP address) of the standby host and dirname is the name of the directory you created in Step 2.

For example:
ttRepAdmin -dsn howdydb -receiver -name hosty -backup backupdb
Step 4 Transfer the backup files from the active host to the standby host (for example, use FTP to transfer the directory).

Step 5 Log in to the standby host as the root user and destroy the database that has been created during the initial setup of replication. Enter the following command:

ttDestroy /opt/TimesTen32/datastore/howdydb

Step 6 Restore using the backed-up files from the active host that you transferred. Enter the following command:

ttRestore -fname replica -dir dirname DSN=howdydb

where dirname is the name of the directory you created. For example:
ttRestore -fname replica -dir backupdb DSN=howdydb
The restore process is being initiated
Restore complete
Step 7 To set up replication of the standby host, enter the following commands:

ttRepAdmin -dsn howdydb -self -restored dirname

ttRepAdmin -dsn howdydb -self -swap standbyhost

For example:
hosty% ttRepAdmin -dsn howdydb -self -restored backupdb
hosty% ttRepAdmin -dsn howdydb -self -swap hosty
Self swap with peer hosty successful
Step 8 Enter the following commands to complete the restoration:
ttRepAdmin -dsn howdydb -table cisco.whitelist_a -sendto activehost
ttRepAdmin -dsn howdydb -table cisco.whitelist_b -sendto activehost
ttRepAdmin -dsn howdydb -table cisco.blacklist_b -sendto activehost
ttRepAdmin -dsn howdydb -table cisco.blacklist_a -sendto activehost
ttAdmin -repPolicy manual howdydb
ttAdmin -repStart howdydb
For example:
hosty% ttRepAdmin -dsn howdydb -table cisco.whitelist_a -sendto hostx
hosty% ttRepAdmin -dsn howdydb -table cisco.whitelist_b -sendto hostx
hosty% ttRepAdmin -dsn howdydb -table cisco.blacklist_b -sendto hostx
hosty% ttRepAdmin -dsn howdydb -table cisco.blacklist_a -sendto hostx
hosty% ttAdmin -repPolicy manual howdydb
RAM Residence Policy            : inUse
RAM Residence Grace (Secs)      : 0
Manually Loaded In Ram          : False
Purge Logs for Data Store       : True
Logging Enabled                 : True
Replication Manually Started    : False
hosty% ttAdmin -repStart howdydb
RAM Residence Policy            : inUse
RAM Residence Grace (Secs)      : 0
Manually Loaded In Ram          : False
Purge Logs for Data Store       : True
Logging Enabled                 : True
Replication Manually Started    : True
Step 9 Verify that the database replication is working. See the "Verifying Database Replication" section.

Verifying Database Replication

To verify that replication is working, perform the following steps:

Step 1 Log in to the active host and start an MML session by entering mml.

Step 2 Enter the prov-sta MML command to being a provisioning session. For example:
hostx mml> prov-sta::srcver="new",dstver="test",confirm
   VSC-01 - Media Gateway Controller 2000-08-30 11:31:15
M  COMPLD
   "PROV-STA"
   ;
Step 3 Add an entry into the B white list database using the numan-add MML command. For example:
hostx mml> numan-add:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"
   VSC-01 - Media Gateway Controller 2000-08-30 11:31:25
M  COMPLD
   "bwhite"
   ;
Step 4 Enter the prov-stp MML command to end the provisioning session. For example:
hostx mml> prov-stp 
   VSC-01 - Media Gateway Controller 2000-08-30 11:31:43
M  COMPLD
   "PROV-STP"
Step 5 Log in to the standby host and start an MML session by entering mml.

Step 6 Enter the prov-sta MML command to being a provisioning session. For example:
hosty mml>  prov-sta::srcver="new",dstver="test",confirm
   VSC-01 - Media Gateway Controller 2000-08-30 11:33:38
M  COMPLD
   "PROV-STA"
   ;
Step 7 Enter the numan-rtrv MML command to verify the entry you added in Step 3 was replicated to the database on the standby host. For example:
hosty mml> numan-rtrv:bwhite:custgrpid="S018",svcname="testsvc",cli="9998"
   VSC-01 - Media Gateway Controller 2000-08-30 11:33:52
M  RTRV
   "session=test:bwhite"
   /* The cli :9998: exists.   */
   ;
Step 8 Enter the prov-stp MML command to end the provisioning session. For example:
hosty mml> prov-stp 
   VSC-01 - Media Gateway Controller 2000-08-30 11:35:33
M  COMPLD
   "PROV-STP"
Troubleshooting

If you have problems during replication, try stopping and restarting the replication as follows:

Step 1 Stop the replication by entering:
# /etc/init.d/ttreplic stop
Step 2 Restart the replication by entering:
# /etc/init.d/ttreplic start
If you still have problems, retry the commands listed in the "Verifying Database Replication" section. If your output differs from the example in that section, or if you suspect problems or errors in the database installation, try the following:

Step 1 Ensure that the database is installed in the /opt/TimesTen32 directory.

Step 2 Check the log file for installation errors. (The log file is in the directory /opt/TimesTen32/datastore.)

If necessary, remove and reinstall the CSCOga002 package. Use this procedure:

Step 1 Remove the CSCOga002 package using the pkgrm command. To remove the package file, type the following command and press Enter:
# pkgrm CSCOga002
Step 2 Reinstall the package using the pkgadd command by typing the following command and pressing Enter:
# pkgadd -d CSCOga002.pkg
This completes the Cisco MGC software configuration. If you have questions or need assistance, see the "Obtaining Technical Assistance" section. .

Parameter	Modification
*.transpathId	To identify the local Cisco MGC host in a continuous-service or high-availability system, enter any one- or two-digit integer. Note If you have two Cisco MGC hosts in a continuous-service or high-availability system, this number must be different in the XECfgParm.dat file for each host.
*.ownTranspathId	To identify the local Cisco MGC host in a continuous-service or high-availability system, enter the same value that you used for .transpathID. Note* If you have two Cisco MGC hosts in a continuous-service or high-availability system, enter this value in the *.peerTranspathID field in the XECfgParm.dat file on the second host server. If you have a simplex system, leave this field blank.
*.peerTranspathId	To identify the peer Cisco MGC host in a continuous-service or high-availability system, enter any one- or two-digit integer. The IDs must be unique in an active and a standby pair. Note If you have two Cisco MGC hosts in a continuous-service or high-availability system, enter the same value that you used for *.transpathID in the XECfgParm.dat file of the second host server in this field. If you have a simplex system, leave it blank.
*.desiredPlatformState	To determine the desired platform state at initialization, enter one of the following values: •master—If you have two (active and standby) Cisco MGC hosts, and you are editing the file on the active host •slave—If you have two (active and standby) Cisco MGC hosts, and you are editing the file on the standby host •standalone—If you have a simplex system Note If you have two Cisco MGC hosts in a continuous-service or high-availability system, make sure that the active Cisco MGC is set to master and the standby host is set to slave.
*.SysCheckpointEnabled	To enable or disable checkpointing, enter one of the following values: •false—Disables checkpointing. Calls are not preserved during a switchover, and status messages are not sent to the replicator (default). •true—Enables checkpointing. Calls that are in the talking state are preserved and survive a control switchover. All status checkpointing information is sent to the replicator on the active side. Note If you have two Cisco MGC hosts in a switchover configuration, enter true. If you have a standalone configuration, enter false.
*.numberOfThreads	To specify the number of threads generated by multithreaded processes such as the engine and the log master, enter one of the following values: •0—Single CPU (default) •1—Two CPUs •2—Four CPUs Note If you have a multi-CPU system, the engine.SysGeneratedCode parameter must be left as true (the default).
*.stPort	Port number used between peer components or processes. Enter any unused port number greater than 1024; for example, 7000. Note If you have two Cisco MGC hosts in a continuous-service or high-availability configuration, enter a different number for this value in the XECfgParm.dat file on the secondary host; for example, 7001.
*.OwnClli	Common language location identifier. To initiate circuit query validation if circuit queries are supported, enter an alphanumeric string of as many as 24 characters. Default: TTT-SS-BB-XXX Example: 1-22-33-444

Parameter	Modification
*.ipAddrLocalA	Enter the first local IP address; used for checkpointing and switchover heartbeats. Note This address is the same value as .IP_Addr1, and is the hme0 interface. Caution* No other machine on the network should have *.ipAddrLocalA set to 0.0.0.0.
*.ipAddrPeerA	Enter the first corresponding peer IP address; used for checkpointing and switchover heartbeats. Note If you have two Cisco MGC hosts in a continuous-service or high-availability configuration, this value is set to the IP address of the second host.
*.ipAddrLocalB	Enter the second local IP address; used for checkpointing and switchover heartbeats. This is the address of the hme1 interface. Note If your configuration does not use a secondary Ethernet adapter, leave this address set to the default value, 0.0.0.0.
*.ipAddrPeerB	Enter the second corresponding peer IP address; used for checkpointing and switchover heartbeats. This is the address of the hme1 interface on the second host. Note If your configuration does not use a secondary Ethernet adapter, leave this address set to the default value, 0.0.0.0.
*.IP_Addr1	Enter the IP address of the hme0 interface.
*.IP_Addr2	Enter the IP address of the hme1 interface (if configured).
*.IP_Addr3	Enter the IP address of the hme2 interface (if configured).
*.IP_Addr4	Enter the IP address of the hme3 interface (if configured).

Parameter	Modification
engine.CALL_MEM_BLOCK_SIZE	Block of memory allocated per call. Used by MDL. Default: 0 •For memory-critical configurations, use the default value. •For performance-critical configurations, set this value to 110000.
engine.CALL_MEM_CHUNK_SIZE	Memory chunks allocated from the block of memory designated with engine.CALL_MEM_BLOCK_SIZE. Default: 0 •For memory-critical configurations, use the default value. •For performance-critical configurations, set this value to 110000.
engine.SysCdrCollection	To designate the format of call detail records (CDRs), enter one of the following values: •true—Generates fold-style nontagged CDRs •false—Generates new tag, length, and value (TLV) format CDRs (default) Note Typically, this value should be false.
engine.SysVirtualSwitch	To indicate whether the Cisco MGC host functions as a signaling controller or a virtual switch controller, enter one of the following values: •0—Signaling controller (nailed trunks, no auditing is initiated) •1—Virtual switch controller (switched trunks)
engine.SysGRSTimerInterval	To specify the interval between blocks of Circuit Group Reset (GRS) messages when the engine.SysGRSBlockSize parameter is used, set to the value required (in milliseconds).
engine.SysGRSBlockSize	Many GRS messages can become due for sending at the same time. This situation occurs if you have set the .GRSEnabled parameter to true during provisioning. The .GRSEnabled parameter is a property that is set on an SS7 signaling service (in the CMM) or an SS7 path (in MML). GRS messages can be staggered if you send them in blocks. Set the engine.SysGRSBlockSize parameter to the number of messages to be sent in each block. Use the engine.SysGRSTimerInterval parameter to set the time from the start of one block to the start of the next. Default: 0 Note This parameter operates independently for each SS7 route (each OPC/DPC pair).
engine.SysGeneratedCode	To determine whether compiled or interpreted code is used, enter one of the following values: •true—System uses compiled code (default). •false—System uses interpreted code (used only for engineering and debugging). Note Compiled code runs faster than interpreted code. Typically, this value should be true. If your configuration uses multiple CPUs, this value must be true.

Parameter	Description	Default Value	Valid Range
Ovl1OnsetThresh	Percentage of total CPU utilization at which overload level 1 is reached.	82	0 through 100
Ovl1AbateThresh	Percentage of total CPU utilization at which overload level 1 abates.	75	0 through 100
Ovl1RejectPercent	Percentage of calls that are rejected while overload level 1 is active.	25	0 through 100
Ovl2OnsetThresh	Percentage of total CPU utilization at which overload level 2 is reached.	90	0 through 100
Ovl2AbateThresh	Percentage of total CPU utilization at which overload level 2 abates.	77	0 through 100
Ovl2RejectPercent	Percentage of calls that are rejected while overload level 2 is active.	50	0 through 100
Ovl2OnsetThresh	Percentage of total CPU utilization at which overload level 2 is reached.	93	0 through 100
Ovl2AbateThresh	Percentage of total CPU utilization at which overload level 2 abates.	85	0 through 100
Ovl2RejectPercent	Percentage of calls that are rejected while overload level 2 is active.	100	0 through 100

Parameter	Modification
engine.SysScreeningCheck	To enable or disable the A-number and B-number analysis in the call screening database, enter one of the following values: •If you do not have the database environment set with all the required data populated, set this value to false (default). •If you have the database and want the system to access it, set this value to true.

Parameter	Modification
engine.CDRencodingFormat	To specify the call detail record (CDR) file encoding format, enter one of the following values: •AnsiCDB—North American (default) •ItuCDB—European
engine.CDRtimeStamp	To specify the CDR file time-stamp unit, enter one of the following values: •S—Seconds (default). •M—Milliseconds; use this parameter if your configuration uses TCAP. Note If you use 1110 in the engine.CDRmessageTypes parameter (for TCAP), you must specify milliseconds for the CDRtimeStamp value.
engine.CDRmessageTypes	To specify which call detail blocks (CDBs, statistics taken at various points in a call) are recorded during a call, enter one of the two following sets of values (each number represents a point in a call): •1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080—Use this value if your CDR files will be read by a measurement server or by another CDR reader. •1060, 1110—Use this value if you will use the TLV converter to view CDR files. 1110—Generates a CDR file containing all CDBs for a call (end of call). If you choose 1110, you must specify milliseconds in the CDRtimeStamp parameter. 1060—Required. 1080—An external value, used for TCAP.
CDRDmpr.CDR	To indicate whether the standard data dumper writes out CDR files, enter one of the following values: •true—Standard data dumper opens a CDR file and logs call detail blocks (CDBs). •false—Standard data dumper does not open a CDR file and does not log CDBs. Note The default CDR file format has been changed from an ASCII format in Release 4 to a binary format in Release 7. Use the dmpr.callDetail parameter to convert the files to an ASCII format, if necessary.
CDRDmpr.callDetail	If your configuration requires ASCII-formatted CDR files, enter /opt/CiscoMGC/bin/converter. Default: /opt/CiscoMGC/local/cdbscript.sh Use this value if you have created a script to process CDRs; this script is stored as cdbscript.sh. Optional: /opt/CiscoMGC/bin/converter Use this value if binary CDR files need to be converted to ASCII. For maximum performance, change this value to none, as follows: cdrDmpr.callDetail = # Note The default CDR file format is binary format. The command above automatically generates CDR files in an ASCII, comma-delimited format in addition to the default, binary format. The ASCII file has a .csv extension. For more information on generating and viewing CDR files, as well as detailed descriptions of CDR file elements, see Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Parameter	Modification
XE.systemType	To specify the system type for alarm LEDs, enter one of the following values: •NETRA—Sun Solaris Netra t 1100, t 1120 (internal LEDs, alarm relays) •SPARC—Generic box (no alarm relays) •SPARC-ARU—Generic box (external alarm relays) Default: SPARC

Parameter	Modification
ClearingLocation	This property overrides the Clearing Location field in Call Context. Change this value if you need a value other than the default to be sent to the switch. Valid values are: •0—The Cisco MGC software uses the default Clearing Location in Call Context. •1—The Cisco MGC software overrides the Clearing Location in Call Context with LOCATION_USER. •2—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PRIVATE_LOCAL. •3—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PUBLIC_LOCAL. •4—The Cisco MGC software overrides the Clearing Location in Call Context with LOCATION_TRANSIT. •5—The Cisco MGC software overrides the Clearing Location in Call Context with LOCATION_ PUBLIC_REMOTE. •6—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PRIVATE_REMOTE. •7—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ INTERNATIONAL. •8—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ INTERWORKING. •9—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ LOCAL_INTERFACE. •10—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ LOCAL_LOCAL. •11—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ LOCAL_REMOTE. •12—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ PACKET_MANAGER. •13—The Cisco MGC overrides the Clearing Location in Call Context with LOCATION_ UNKNOWN.
DefaultLocation	This property overrides the Default Location field in Call Context. Change this value if you need to define a customer-specific default location for your system that can differ from the default location set in the type definition of the protocol. Valid values are: •0—The Cisco MGC software uses the Default Location in Call Context. •1—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_USER. •2—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PRIVATE_LOCAL. •3—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PUBLIC_LOCAL. •4—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_TRANSIT. •5—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PUBLIC_REMOTE. •6—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PRIVATE_REMOTE. •7—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ INTERNATIONAL. •8—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ INTERWORKING. •9—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ LOCAL_INTERFACE. •10—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ LOCAL_LOCAL. •11—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ LOCAL_REMOTE. •12—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ PACKET_MANAGER. •13—The Cisco MGC software overrides the Default Location in Call Context with LOCATION_ UNKNOWN.

Parameter	Modification
foverd.conn1Type	To set the connection type for connection number 1, enter serial or socket. Note Typically, set this value to socket.
foverd.ipLocalPortA	To define the local port number used for IP communication, enter a unique number, keeping the following in mind: •Typically, if Type is socket, set this value to 1051. •If you have two Cisco MGC hosts in a continuous-service or high-availability configuration, enter the foverd.ipLocalPortA value in the foverd.ipPeerPortA field in the XECfgParm.dat file on the secondary host. Caution The value of foverd.ipLocalPortA must be unique for every host on the network. Otherwise, active and standby hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipLocalPortA set to 1051. If another machine does have that value, the active and standby hosts cannot perform proper switchover.
foverd.ipPeerPortA	To define the peer port number used for IP communication, enter a unique number, keeping the following in mind: •Typically, if Type is socket, set this value to 1052. •If you have two Cisco MGC hosts in a switchover configuration, enter the foverd.ipPeerPortA value in the foverd.ipLocalPortA field in the XECfgParm.dat file on the secondary host. Caution The value of foverd.ipPeerPortA must be unique for every host on the network. Otherwise, active and standby hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipPeerPortA set to 1052. If another machine does have that value, the active and standby hosts cannot perform proper switchover.
foverd.conn2Type	To set the connection type for connection number 2, enter serial or socket. Note Typically, set this value to socket.
foverd.ipLocalPortB	To define the secondary local port number used for IP communication, enter a unique number, keeping the following in mind: •Typically, if Type is socket, set this value to 1053. •If you have two Cisco MGC hosts in a switchover configuration, enter this value in the foverd.ipPeerPortB field in the XECfgParm.dat file on the secondary host. Caution The value of foverd.ipLocalPortB must be unique for every host on the network. Otherwise, active and standby hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipLocalPortB set to 1053. If another machine does have that value, the active and standby hosts cannot perform proper switchover.
foverd.ipPeerPortB	To define the secondary local port number used for IP communication, enter a unique number, keeping the following in mind: •Typically, if Type is socket, set this value to 1054. •If you have two Cisco MGC hosts in a switchover configuration, enter this value in the foverd.ipLocalPortB field in the XECfgParm.dat file on the secondary host. Caution The value of foverd.ipPeerPortB must be unique for every host on the network. Otherwise, master and slave hosts cannot communicate properly. In the instance discussed here, no other machine on the network can have foverd.ipPeerPortB set to 1054. If another machine does have that value, the master and slave hosts cannot perform proper switchover.
foverd.conn3Type	To set the connection type for connection number 3, enter serial or socket. Note Typically, set this value to serial.
foverd.conn3Addr	To specify the address of the peer system, enter a location; for example, /dev/term/a. If your configuration does not use connection number 3, enter /dev/null (default). Note If your configuration uses an 8-port connector as a serial connection for switchover, you must modify the read-write permissions for the connection. For more information, see Release Notes for Cisco Media Gateway Controller Software Release 7.
foverd.abswitchPort	To specify the port used for communication with the A/B switch, enter a location; for example, /dev/term/a. Note If your configuration does not use an A/B switch, use the default value (/dev/null).
foverd.heartbeatInterval	Specifies the maximum time in milliseconds between heartbeat messages from the peer switchover daemon. This interval defines the frequency with which the switchover daemon exchanges heartbeat messages with its peer. Default: 4000 milliseconds (4 seconds).

Parameter	Modification
pom.dataSync	Used in a continuous-service or high-availability system to indicate that the POM should synchronize the provisioning data at startup. •If you have a standalone system, set this value to false. •If you have a continuous-service or high-availability system, this value is true (default). Caution If pom.dataSync is set to true for a continuous-service or high-availability system, you must ensure that you are running the same version of the Cisco MGC software on both active and standby machines. Otherwise, the wrong version of your data files might be copied to the other machine.
pom.port	Used in a continuous-service or high-availability configuration to indicate the port number that the POM uses to communicate with its peer. Enter any integer from 4001 through 4050, or default. Note This is a platform-specific value and depends on your system installation. You should modify this value only if the default port (4001) is being used by another process or application.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

F1	F2	F3	F4	F5	F6	F7	F8	F9	F10	F11	F12	F13	F14	F15	F16	F17	F18	F19	F20	F21
Transport	tcapType	stpScpGroupIndex	msg	asn1Encoding	tcv_sk	translationType	tcapBodyType	gtSsn	dpcPres	ssnPres	dpcNetwork	dpcCluster	dpcMember	ssn	gtFormat	OS1	OS2	OS3	OS4	OS5
# MS 1: xxxxxx LNP
1	2	0	6	0	0	255	1	0	0	1	0	0	0	0	2	1	0	0	0	0
# MS 2: Generic LNP
1	2	0	6	0	37	255	1	0	0	1	0	0	0	0	2	2	0	0	0	0
# MS 3: xxxxxxx 800
2	1	1	1	0	0	0	1	0	0	1	0	0	0	0	2	3	0	0	0	0
# MS 4: ANSI AIN 800 NPA
1	2	0	6	0	4	255	1	0	0	1	0	0	0	0	2	4	0	0	0	0
# MS 5: ANSI AIN 800 NPA-NXX
1	2	0	6	0	5	255	1	0	0	1	0	0	0	0	2	4	0	0	0	0
# MS 6: ANSI AIN 800 NPA-NXX-XXX
1	2	0	6	0	8	255	1	0	0	1	0	0	0	0	2	4	0	0	0	0
# MS 7: ANSI AIN 800 Termination information
1	2	0	5	0	0	255	1	0	0	1	0	0	0	0	2	5	0	0	0	0
# MS 8: ANSI PRE AIN 800
1	3	0	6	0	0	254	2	0	0	1	0	0	0	0	2	6	0	0	0	0
# MS 9: ANSI PRE AIN 800 Termination information
1	3	0	5	0	0	254	2	0	0	1	0	0	0	0	2	7	0	0	0	0

Chapter 4: Configuring the Cisco Media Gateway Controller Software Release 7.4

Available Languages

Download Options

Bias-Free Language

Table Of Contents

Configuring the Cisco Media Gateway Controller Software Release 7.4

Before You Start

Configuring Groups and Users

Verifying the mgcgrp Group

Adding a User with Full MML Privileges

Adding a User with Minimal MML Privileges

Configuring SNMP Support Resources

Configuring the Execution Environment

Changing XECfgParm.dat File Parameters

Changing XECfgParm.dat File Parameters in a Running Continuous-Service or High-Availability System

Configuring Basic System Information

Specifying IP Addresses

Configuring Engine Parameters

Configuring Automatic Congestion Control

Overload Level Percentage Parameters

CPU Timer Interval Parameter

Maximum ACL Value

Enabling Call Screening

Configuring Call Detail Record File Output

Configuring the System Type

Configuring the Clearing Location and Default Location Parameters

Configuring *.GWClearChannelAlgorithm Parameter

Configuring Switchover

Initializing the Provisioning Object Manager

Configuring SCP Queries

Before You Start

Configuring the trigger.dat File Attributes

Configuring the Global Title Translation Attribute

Configuring the Service Key Value Attribute

Configuring the Translation Type Attribute

Sample trigger.dat File

Initializing the Call Screening Database

.odbc.ini File Information

Setting Up Replication

Initializing Database Replication

Initializing Replication and Copying the Database to Another Host

Verifying Database Replication

Troubleshooting

Was this Document Helpful?

Contact Cisco

This Document Applies to These Products