Installing the Cisco Media Gateway Controller Software Release 7.4

Note The Cisco telephony controller software is called the Cisco Media Gateway Controller software for Release 7.4 and later. If you are uninstalling a software release prior to Release 7.4, the Cisco MGC (formerly "telephony controller") software files and processes are located in the /opt/TransPath directory of your host server. In Release 7.4, they are in the /opt/CiscoMGC directory.

This chapter contains the following sections:

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

Before You Start

Caution To prevent the system from running out of disk space during installation and removing data files and databases to compensate, verify that there is enough hard disk space to support your intended installation. You can delete unnecessary log files (platform*.log), user-generated trace files (*.btr), call detail record (CDR) files (.bin or .csv), or user-generated toolkit files (in the /var/cust_specific/toolkit directory) to free space. You also need at least 4 GB of disk space for the /opt file system.

Before you start, perform the following steps:

Review the hardware and software requirements found in the document Release Notes for the
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 installation if needed. (If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface for Cisco support contact information.)
Perform your installation according to the steps below:

Step 1 If the Sun Solaris 2.6 operating system is not already installed, start with "Installing the Sun Solaris 2.6 Operating System."

Step 2 With the Sun Solaris 2.6 operating system installed, go to the correct section in this chapter:

If you are upgrading from a previous release, follow the procedures found in the "Upgrading from a Previous Release" section.
If you are installing the software for the first time, follow the procedures found in the "Installing the Cisco Media Gateway Controller Software Release 7.4(x)" section.

Tips Allow for system downtime as follows:
- At least 2 hours to install the Sun Solaris 2.6 operating system.
- Approximately 1 hour to install the Cisco MGC software.

Note Monitor system output frequently for error messages during the installation process and correct any error conditions before continuing with the installation.

Upgrading from a Previous Release

This section covers the following topics:

Note If you are upgrading from Release 4.(X) version of the Cisco telephony controller software, see Cisco SS7 Interconnect for Access Servers Solution Upgrade Guide.

Upgrading from Software Release 7.3 to 7.4

If you are upgrading from Software Release 7.3 to Software Release 7.4, follow these steps:

Step 1 Uninstall the Software Release 7.3 software by following the instructions in "Removing a Previous Version of the Cisco Telephony Controller Software" section.

Step 2 Make sure you have removed the transpath group and transpath user from the /etc/group and /etc/passwd files.

Step 3 Install Software Release 7.4 by following the instructions in "Installing the Cisco Media Gateway Controller Software Release 7.4(x)" section.

If you have a continuous-service or high-availability system with two Cisco MGC hosts, you cannot upgrade from Software Release 7.3 to Software Release 7.4 without call interruption. You must shut down the Cisco MGC hosts before upgrading.

Upgrading within Software Release 7.4

Before you can upgrade the telephony controller software, you must first uninstall any previous version of the software. To uninstall a previous version, follow the instructions in the "Removing a Previous Version of the Cisco Media Gateway Controller Software" section.

If you are upgrading within a software release (for example, upgrading from Software Release 7.4(8) to 7.4(9), perform the following steps:

Step 1 Back up your system data. See "Backing Up System Data" section.

Step 2 If you have a continuous-service or high-availability system, log in to the standby host (Host Y) as the root user. If you have a simplex configuration, log in to the host as the root user.

Step 3 Stop the Cisco MGC software by entering the /etc/init.d/CiscoMGC stop command.

Step 4 Remove the Cisco MGC software. See "Removing a Previous Version of the Cisco Media Gateway Controller Software" section.

Step 5 Install the new software. See "Installing the Cisco Media Gateway Controller Software Release 7.4(x)" section. If you have a simplex system, you have completed the necessary steps. If you have a continuous-service or high-availability system, proceed to the next step.

Step 6 On Host Y, edit the XECfgParm.dat file in the/opt/CiscoMGC directory to set the pom.dataSync parameter to false.

Step 7 Save changes to the XECfgParm.dat file and restart the software by entering the /etc/init.d/CiscoMGC start command.

Step 8 Log in to the active host (Host X) as the root user. Stop the telephony controller software by entering the /etc/init.d/CiscoMGC stop command. Call processing will switch over from Host X to the standby host (Host Y).

Step 9 On Host Y, check that switchover succeeded and the upgraded server is processing calls.

Step 10 On Host X, remove the telephony controller software. See "Removing a Previous Version of the Cisco Media Gateway Controller Software" section.

Step 11 On Host X, install the new software. See "Installing the Cisco Media Gateway Controller Software Release 7.4(x)" section.

Step 12 On Host Y, enter the MML command sw-over::confirm to switch call processing to Host X. Verify that Host X is processing calls.

Step 13 On Host Y (now the standby host), stop the software by entering the /etc/init.d/CiscoMGC stop command.

Step 14 Edit the XECfgParm.dat file in the/opt/CiscoMGC directory to set the pom.dataSync parameter to true.

Step 15 Save changes to the XECfgParm.dat file and restart the software by entering the /etc/init.d/CiscoMGC start command.

Step 16 On Host X, make sure the pom.dataSync parameter is set to true.

Backing Up System Data

To back up system data before you upgrade, make copies of the following directories:

/opt/CiscoMGC/etc
/opt/CiscoMGC/dialPlan
/opt/CiscoMGC/CONFIG_LIB

For instructions on backing up your system data, see "Cisco MGC Backup and Restore Procedures" section in Chapter 3 of the Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.

Removing a Previous Version of the Cisco Media Gateway Controller Software

Note For a sample output listing from the install.sh script, see the "Sample Output from uninstall.sh" section.

Before upgrading an existing release of the Cisco MGC software, you must first uninstall the previous software version.

Note If you are removing Software Release 7.3, follow the instructions in "Removing a Previous Version of the Cisco Telephony Controller Software" section.

To remove the Cisco MGC software, complete the following steps:

Step 1 Log in at the console as the root user.

Step 2 To stop the Cisco MGC software, enter the following command:

# /etc/init.d/CiscoMGC stop

Wait until the system returns the following response:

Signalling procM to shut down
...shutdown complete

Caution Stopping the Cisco MGC software on the active host takes all processes and links out of service.

Step 3 Insert the Cisco MGC Software Version 7.4 CD-ROM into the CD-ROM drive and enter the following commands:

# cd /cdrom/cdrom0
# ./uninstall.sh

Step 4 If you are upgrading from a previous version of software Release 7, answer y to the following prompt. If this is an initial installation, answer n:

If you answer no to the following question you will lose all new provisioning work.
Is the uninstall being done in order to upgrade to a new version of the software? [y] [y,n,?,q]

Step 5 The system asks if you want to use the supplied administrative file to perform an unattended package removal. This process removes all the packages automatically.

TimeSaver If you do not accept the unattended removal, the system prompts you before removing each package individually.

Step 6 Type y (yes) and press Enter to accept unattended package removal. The system displays a list of packages as it removes them.

When package removal is finished, the following message appears:

Uninstallation log can be found in /tmp/uninstall.log.

Step 7 Enter the following command:

cd /etc

Step 8 Open the group file with your editor.

Step 9 Make sure that the "transpath" and "mgcgrp" groups are removed. These groups must be removed in order to accept default software installation later.

Step 10 Save any changes to the group file and close it.

This completes the removal of the previous version of the Cisco MGC software. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.

Sample Output from uninstall.sh

Example 3-1 shows sample output from the uninstall script.

Example 3-1: Sample Output from the Uninstall Script

va-cerulean# cd /cdrom/cdrom0
va-cerulean# ./uninstall.sh
 
Use supplied admin file for unattended removal? [n] [y,n,?,q] y
Restoring saved /opt/TransPath/bin/mml
Restoring saved /opt/TransPath/bin/pom
 
Removal of <CSCOgp009> was successful.
Removal of <CSCOgc001> was successful.
Removal of <CSCOgt002> was successful.
Removal of <CSCOgt001> was successful.
Removal of <CSCOgg008> was successful.
Removal of <CSCOgg007> was successful.
Removal of <CSCOgg006> was successful.
Removal of <CSCOgg005> was successful.
Removal of <CSCOgg004> was successful.
Removal of <CSCOgg003> was successful.
Removal of <CSCOgg002> was successful.
Removal of <CSCOgg001> was successful.
Removal of <CSCOgg000> was successful.
Removal of <CSCOgi008> was successful.
Removal of <CSCOgi007> was successful.
Removal of <CSCOgi006> was successful.
Removal of <CSCOgi005> was successful.
Removal of <CSCOgi004> was successful.
Removal of <CSCOgi003> was successful.
Removal of <CSCOgi002> was successful.
Removal of <CSCOgi001> was successful.
Removal of <CSCOgi000> was successful.
Uninstalling /opt/VSCprov/tcl/tcl.tar.gz
Uninstalling /opt/VSCprov/properties/properties.tar.gz
Uninstalling /opt/VSCprov/mibs/common/common.tar.gz
Uninstalling /opt/VSCprov/gif/gif.tar.gz
Uninstalling /opt/VSCprov/bytecode/bytecode.tar.gz
 
Removal of <CSCOga004> was successful.
Modifying /etc/inittab
 
Removal of <CSCOga003> was successful.
Sun Microsystems Inc.   SunOS 5.6       Generic August 1997
Exporting database contents for DSN=howdydb into /opt/TransPath/etc/export.ttdb
The Backup process is being initiated for the datastore howdydb
Files for /opt/TimesTen32/datastore/howdydb are being backed up onto standard output
Backup Complete
The 32-bit daemon has stopped successfully.
Modifying /etc/syslog.conf
 
Removal of <CSCOga002> was successful.
Removal of <CSCOga001> was successful.
Removal of <CSCOga000> was successful.
Removal of <CSCOgu000> was successful.

Installing the Cisco Media Gateway Controller Software Release 7.4(x)

Note For a sample output listing from the install.sh script, see the "Sample Output from install.sh" section.

Installing on a Simplex System

To install the Cisco MGC software on a simplex system (a system with one Cisco MGC host), complete the following steps:

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

Step 2 Enter the following command:

cd /etc

Step 3 Open the password file with your editor.

Step 4 Check that /opt/TransPath does not appear in the path of any user; if it does, change the path to /opt/CiscoMGC.

Step 5 Save any changes to the password file.

Step 6 Close the password file.

Step 7 Insert the Cisco MGC Software Release 7.4(x) CD into the CD-ROM drive.

Step 8 To install the Release 7.4(x) Cisco MGC software, enter the following comma nds:

# cd /cdrom/cdrom0
# ./install.sh

Step 9 The following prompt appears:

Use supplied admin file for unattended install? [n] [y,n,?,q]

Answer y to perform an unattended installation. If you answer n, you must answer prompts and press Enter for each package that is installed.

Note The initial installation takes approximately 1 hour.

Step 10 The following prompt appears:

Install Cisco Media Gateway Controller Manager (CMM/Toolkit) package?
[n] [y,n,?,q]

Answer y if you want to install the CMM and the Toolkit applications on this host.

Tips To install the CMM on a separate host, follow the steps in "Installing the Cisco Media Gateway Controller Manager Software on a Separate Host" section.

Step 11 The following prompt appears:

Base directory for CMM/Toolkit (default /opt/CMM) [?,q]

Press Enter to accept the default directory, /opt/CMM. We recommend you do not change the directory.

Step 12 The following prompt appears:

The CSCOgu000 utilities package must be installed prior to other components but has not been detected on your system.
Would you like to install it now? [y] [y,n,?,q]

Answer y to install the utilities package. This package must be installed before installing the rest of the software.

Caution Before accepting the default user ID and group ID as recommended in the step below, you must make sure old transpath IDs are deleted in the /etc/group directory. We recommend that the group directory itself be deleted.

Step 13 The following prompts appear:

Base directory for CiscoMGC (default /opt/CiscoMGC) [?,q] 
Enter CiscoMGC user name [mgcusr] 
Enter CiscoMGC UID [20000] 
Enter CiscoMGC group name [mgcgrp]

We recommend that you accept the default values (by pressing Enter).

You can, however, specify a different user ID and a group ID. If the ID you specify already exists on the system, the corresponding ID will be determined and reused, or you will be prompted to enter another ID.

Caution No validation is performed on the IDs you enter. If you enter an invalid ID, the utilities package does not add any accounts.

The system returns a message that the CSCOgu000 utilities package was successfully installed.

Step 14 Rebooting after a successful utilities package installation might or might not be necessary, based on your system configuration.

If a reboot is not required, the installation continues uninterrupted. When the installation is finished, continue to Step 16.

If a reboot is required, perform the following steps when prompted:

a. Type the command displayed on the screen and press Enter.

Note If the command shown on the screen does not work, you can enter the /usr/sbin/reboot command to reboot the system.

b. After the reboot finishes, restart install.sh to install the remaining packages. To restart install.sh, type each of the following commands at the # prompt and press Enter:

# cd /cdrom/cdrom0
# ./install.sh

c. When the package installation is finished, continue to Step 16.

Step 15 The system checks the memory and CPUs in the host. If you do not have enough memory or CPUs, a caution appears. After the check is complete, the following prompt appears:

Configure System for (1) Maximum Sustained Calls (2) High Call Throughput 
Enter 1 or 2 or q to quit

Enter 1 or 2 to choose the option you want and press Enter.

Step 16 I f your system uses IT Telekommunications AG (ITK, now Digi International AG) cards, you must install the drivers package using the pkgadd command.

Note When an ITK card is on an SS7 link set to run at 64 kbps, expect a download data rate of approximately 52 kbps, and an uplink data rate of approximately 40 kbps.

The drivers directory contains the following driver packages:

CSCOgd001: Drivers for ITK T1/E1 cards
CSCOgd002: Drivers for PTI V.35 cards
CSCOgd003: Drivers for PTK T1/E1 cards (Reserved for future use; do not use.)

Enter the pkgadd -d package name command to add the appropriate driver for your card.
Example:

# pkgadd -d /cdrom/cdrom0/DRIVERS/CSCOgd001.pkg

The following text appears:

The following packages are available:
  1  CSCOgd001     Cisco Media Gateway Controller Software ITK PCI E1/T1 Driver
                   (sparc) 7.4(7)G

Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:

Step 17 Press Enter to install the selected package. The installation script installs the drivers and reboots the host.

This completes the installation of the Cisco MGC software for a standalone configuration. For a sample install.sh log file, see the "Sample Output from install.sh" section.

If you have a redundant configuration, continue to the "Installing on a Continuous-Service or High-Availability System" section.

Otherwise, go to the "Configuring Groups and Users" section.

If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.

Installing on a Continuous-Service or High-Availability System

To install the Cisco MGC software on a continuous-service system (with two Cisco MGC hosts and Cisco SLTs) or a high-availability system (with two Cisco MGC hosts and E1/T1 signaling cards), complete the following steps:

Step 1 Exit server 1.

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

Step 3 Insert the Cisco MGC Software Release 7.4(x) CD into the server 2 CD-ROM drive.

Step 4 Follow the instructions in Step 8 through Step 17 of the "Installing on a Simplex System" section.

Step 5 Configure the execution environment parameters and database replication for continuous-service or high-availability systems, using the following sections:

Sample Output from install.sh

Example 3-2 shows sample output from the install script.

Example 3-2: Sample Output from the Install Script

va-cerulean# cd /cdrom/cdrom0
# ./install.sh
 
Use supplied admin file for unattended install? [n] [y,n,?,q] y
 
Install Cisco Media Gateway Controller Manager (CMM/Toolkit) package?
[n] [y,n,?,q] y
 
Base directory for CMM/Toolkit (default /opt/CMM) [?,q] 
 
The CSCOgu000 utilities package must be installed prior to other components
but has not been detected on your system.
 
Would you like to install it now? [y] [y,n,?,q] y
 
Base directory for CiscoMGC (default /opt/CiscoMGC) [?,q] 
Enter CiscoMGC user name [mgcusr] 
Enter CiscoMGC UID [20000] 
Enter CiscoMGC group name [mgcgrp] 
[mgcgrp] group added
[mgcusr] user added
Modifying /etc/init.d/inetinit
 
Installation of <CSCOgu000> was successful.
 
(c)1998 Cisco Systems, Inc. All Right Reserved.
Unpublished -- rights reserved under the copyright
laws of the United States.
 
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the Government
is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013 or subparagraphs
(c)(1) and (2) of Commercial Computer Software --
Restricted Rights at 48 CFR 52.227-19, as applicable. 
 
Cisco Systems, Inc.
13615 Dulles Technology Drive
Herndon, VA 20171
 
 
Installation of <CSCOga000> was successful.
Uncompressing ASP
Uncompressing DPNSS
Uncompressing EISUP
Uncompressing IOCCIP
Uncompressing IOCCTCP
Uncompressing ISDNIP
Uncompressing ISDNL3
Uncompressing ISDNPRI
Uncompressing LogServerd
Uncompressing MGCP
Uncompressing SS7
Uncompressing TCAP
Uncompressing almM
Uncompressing amDmpr
Uncompressing cdrDmpr
Uncompressing cfgM
Uncompressing cmsEventFwd
Installing converter
Uncompressing engine.no_smartalloc
Uncompressing engine.smartalloc
Uncompressing foverd
Uncompressing ioChanMgr
Uncompressing measMgr
Uncompressing mmBldCfg
Uncompressing mmdbd
Uncompressing mml
Uncompressing pom
Uncompressing procM
Uncompressing replicator
Installing libACE.so
Uncompressing libconvutil.so
Uncompressing libmmdb.so
Uncompressing libpol.so
Uncompressing libpxe.so
Uncompressing libpxelog.so
Uncompressing librudp.so
Uncompressing libsa.so
Installing libsunmath.so.1
Installing libtten.so
Uncompressing libxe.so
Updating parameters for CiscoMGC
Updating parameters for SW_Layout.cfg
Updating parameters for getConfig
Updating parameters for log_rotate.sh
Updating parameters for startAudit.sh
Updating parameters for diagdata
Updating parameters for .cshrc
Updating parameters for .dump-prov
Updating parameters for actDPlan
Updating parameters for backup.sh
Updating parameters for cdbscript.sh
Updating parameters for cmd_failover.sh
Updating parameters for config-lib
Updating parameters for diskmonitor.sh
Updating parameters for failover_nfs.sh
Updating parameters for getDPlan
Updating parameters for init.tcl
Updating parameters for listDPlan
Updating parameters for migrateDPlan.sh
Updating parameters for perf_config
Updating parameters for pmctrl
Updating parameters for reconfig-all.mml
Updating parameters for rmsem.sh
Updating parameters for startAudit.mml
Updating parameters for stop-all
Installing /opt/CiscoMGC/man/mml.help.tar.gz
 
Installation of <CSCOga001> was successful.
Modifying /etc/syslog.conf
Updating parameters for .odbc.ini
Updating parameters for backupDb.sh
Updating parameters for restoreDb.sh
Uncompressing acroread.tar
Uncompressing doc.tar
Uncompressing timesten.tar
Uncompressing ttclient.tar
Uncompressing ttserver.tar
   Preparing to install TimesTen 3.2 in /opt on va-cerulean
   Executing TimesTen installation script...
   
   Of the three components:
 
     [1] TimesTen Client/Server and Data Manager
     [2] TimesTen Data Manager Only
     [3] TimesTen Client Only
   
   Install in /opt/TimesTen32
   Creating /opt/TimesTen32 ...
   extracting /opt/ttdb-install/SunOS251/ttserver.tar ...
System logging appears to be configured correctly.
(TimesTen syslog messages seem to be recorded in the file '/var/adm/messages')
   Starting the daemon for solaris ...
   Server startup scripts not required - ignored
   Installing TimesTen Server...
What is the DNS name, host name, or IP address of the server [va-cerulean]: 
What is the TCP/IP port number that you want the TimesTen Server to listen on [23232]: 
What is Filename and Location of server.odbc.ini file [/var/TimesTen32/32/server
/server.odbc.ini]: 
TimesTen Connect Configuration completed.
   extracting /opt/ttdb-install/SunOS251/doc.tar ...
   
Install complete
   TimesTen installation script returned status 0
Sun Microsystems Inc.   SunOS 5.6       Generic August 1997
You have new mail.
Restoring database contents for DSN=howdydb from /opt/CiscoMGC/etc/export.ttdb
Restoring file /opt/TimesTen32/datastore/howdydb.ds1 from backup
Restoring file /opt/TimesTen32/datastore/howdydb.log1 from backup
The restore process is being initiated
Restore complete
 
Installation of <CSCOga002> was successful.
Uncompressing mmSAgt
Uncompressing provSAgt
Uncompressing sagt
Updating parameters for snmpd
 
Installation of <CSCOga003> was successful.
Installing /opt/CMM/Packages/Packages.tar.gz
Installing /opt/CMM/bytecode/am/am.tar.gz
Installing /opt/CMM/bytecode/cdr/cdr.tar.gz
Installing /opt/CMM/bytecode/cmm/cmm.tar.gz
Installing /opt/CMM/bytecode/log/Viewer.tar.gz
Installing /opt/CMM/bytecode/toolbar/toolbar.tar.gz
Installing /opt/CMM/bytecode/tv/tv.tar.gz
Installing /opt/CMM/gif/gif.tar.gz
Installing /opt/CMM/mibs/common/common.tar.gz
Installing /opt/CMM/tcl/tcl.tar.gz
Updating parameters for init.tcl
Updating parameters for start.sh
Updating parameters for version.dat
 
Installation of <CSCOga004> was successful.
Uncompressing ASP_NotRealProtocol.mdo
Uncompressing CALLVER.mdo
Uncompressing CALLVER_GENERIC_ANALYSIS.mdo
Installing CALLVER_LCM.mdo
Uncompressing CDR_MAN.mdo
Uncompressing CONNECTION_PLANE_MANAGER.mdo
Uncompressing EISUP.mdo
Uncompressing GENERIC_ANALYSIS.mdo
Uncompressing IN_TRIGGER.mdo
Uncompressing cc.mdo
Uncompressing dummy.mdo
Uncompressing lcm.mdo
 
Installation of <CSCOgi000> was successful.
Uncompressing ISUPV2_FINNISH96.mdo
Uncompressing ISUPV2_FRENCH.mdo
Uncompressing ISUPV2_GERMAN.mdo
Uncompressing ISUPV2_JAPAN.mdo
Uncompressing ISUPV2_NTT.mdo
Uncompressing ISUPV2_SPANISH.mdo
Uncompressing ISUPV2_SWISS.mdo
Uncompressing ISUPV2_TOKYO.mdo
 
Installation of <CSCOgi001> was successful.
Uncompressing ISUPV1_POLI.mdo
Uncompressing Q767_BASE.mdo
Uncompressing Q767_ITAL.mdo
Uncompressing Q767_ITAL_INTERCONNECT.mdo
Uncompressing Q767_MEXICAN.mdo
Uncompressing Q767_RUSS.mdo
Uncompressing Q767_SPAN.mdo
Uncompressing Q767_SWED.mdo
Uncompressing Q767_TELSTRA.mdo
 
Installation of <CSCOgi002> was successful.
Uncompressing Q721_BASE.mdo
Uncompressing Q721_CHINA.mdo
Uncompressing Q721_FRENCH.mdo
Uncompressing Q721_PHILLIPINE.mdo
 
Installation of <CSCOgi003> was successful.
Uncompressing ANSISS7_92.mdo
Uncompressing ANSISS7_CLEAR.mdo
Uncompressing ANSISS7_STANDARD.mdo
Uncompressing T113_BELL.mdo
 
Installation of <CSCOgi004> was successful.
Uncompressing ISUPV3.mdo
Uncompressing ISUPV3_UK.mdo
 
Installation of <CSCOgi005> was successful.
Uncompressing BTNUP_BTNR167.mdo
Uncompressing BTNUP_IUP.mdo
 
Installation of <CSCOgi006> was successful.
Uncompressing ATT_41459.mdo
Uncompressing ATT_41459_C2.mdo
Uncompressing BELL_1268.mdo
Uncompressing BELL_1268_C3.mdo
Uncompressing ETS_300_102.mdo
Uncompressing ETS_300_121.mdo
Uncompressing ETS_300_172.mdo
Uncompressing ETS_300_356.mdo
Uncompressing NTT_INS_1500.mdo
 
Installation of <CSCOgi007> was successful.
Uncompressing DPNSS_BTNR188.mdo
 
Installation of <CSCOgi008> was successful.
Uncompressing Q761_ARGENTINA.mdo
Uncompressing Q761_AUSTRL.mdo
Uncompressing Q761_BASE.mdo
Uncompressing Q761_CHILE.mdo
Uncompressing Q761_CHINA.mdo
Uncompressing Q761_JAPAN.mdo
Uncompressing Q761_KOREAN.mdo
Uncompressing Q761_SINGAPORE.mdo
Uncompressing Q761_TAIWAN.mdo
Uncompressing Q761_THAILAND.mdo
 
Installation of <CSCOgi009> was successful.
Uncompressing ASP_NotRealProtocol.so
Uncompressing CDR_MAN.so
Uncompressing CONNECTION_PLANE_MANAGER.so
Uncompressing EISUP.so
Uncompressing GENERIC_ANALYSIS.so
Uncompressing IN_TRIGGER.so
Uncompressing cc.so
Uncompressing dummy.so
Uncompressing lcm.so
 
Installation of <CSCOgg000> was successful.
Uncompressing ISUPV2_FINNISH96.so
Uncompressing ISUPV2_FRENCH.so
Uncompressing ISUPV2_GERMAN.so
Uncompressing ISUPV2_JAPAN.so
Uncompressing ISUPV2_NTT.so
Uncompressing ISUPV2_SPANISH.so
Uncompressing ISUPV2_SWISS.so
Uncompressing ISUPV2_TOKYO.so
 
Installation of <CSCOgg001> was successful.
Uncompressing ISUPV1_POLI.so
Uncompressing Q767_BASE.so
Uncompressing Q767_ITAL.so
Uncompressing Q767_ITAL_INTERCONNECT.so
Uncompressing Q767_MEXICAN.so
Uncompressing Q767_RUSS.so
Uncompressing Q767_SPAN.so
Uncompressing Q767_SWED.so
Uncompressing Q767_TELSTRA.so
 
Installation of <CSCOgg002> was successful.
Uncompressing Q721_BASE.so
Uncompressing Q721_CHINA.so
Uncompressing Q721_FRENCH.so
Uncompressing Q721_PHILLIPINE.so
 
Installation of <CSCOgg003> was successful.
Uncompressing ANSISS7_92.so
Uncompressing ANSISS7_CLEAR.so
Uncompressing ANSISS7_STANDARD.so
Uncompressing T113_BELL.so
 
Installation of <CSCOgg004> was successful.
Uncompressing ISUPV3.so
Uncompressing ISUPV3_UK.so
 
Installation of <CSCOgg005> was successful.
Uncompressing BTNUP_BTNR167.so
Uncompressing BTNUP_IUP.so
 
Installation of <CSCOgg006> was successful.
Uncompressing ATT_41459.so
Uncompressing ATT_41459_C2.so
Uncompressing BELL_1268.so
Uncompressing BELL_1268_C3.so
Uncompressing ETS_300_102.so
Uncompressing ETS_300_121.so
Uncompressing ETS_300_172.so
Uncompressing ETS_300_356.so
Uncompressing NTT_INS_1500.so
 
Installation of <CSCOgg007> was successful.
Uncompressing DPNSS_BTNR188.so
 
Installation of <CSCOgg008> was successful.
Uncompressing Q761_ARGENTINA.so
Uncompressing Q761_AUSTRL.so
Uncompressing Q761_BASE.so
Uncompressing Q761_CHILE.so
Uncompressing Q761_CHINA.so
Uncompressing Q761_JAPAN.so
Uncompressing Q761_KOREAN.so
Uncompressing Q761_SINGAPORE.so
Uncompressing Q761_TAIWAN.so
Uncompressing Q761_THAILAND.so
 
Installation of <CSCOgg009> was successful.
Uncompressing ca
Uncompressing callver
Installing get_trc.sh
Uncompressing sim
Uncompressing simWriter
Uncompressing sp
 
Installation of <CSCOgt001> was successful.
Uncompressing gen
Uncompressing mdl
 
Installation of <CSCOgt002> was successful.
Updating parameters for XECfgParm.dat
Updating parameters for trigger.template
Updating parameters for migrate
Updating parameters for migrateTKGFile
Installing /opt/CiscoMGC/etc/CONFIG_LIB/migrate_mod.tar.gz
Installing /opt/CiscoMGC/etc/migrate/migrate_scr.tar.gz
Migrating .dat files in /opt/CiscoMGC/etc
Checking dialPlan dir: /opt/CiscoMGC/dialPlan/*.dialPlan
Backing up .dat file
Backing up database
Sun Microsystems Inc.   SunOS 5.6       Generic August 1997
You have new mail.
migrate_XECfgParm: setting *.transpathId = 01
migrate_XECfgParm: setting *.ownTranspathId = 01
migrate_XECfgParm: setting *.peerTranspathId = 02
migrate_XECfgParm: setting foverd.conn1Type = socket
migrate_XECfgParm: setting foverd.conn2Type = socket
migrate_XECfgParm: setting *.IP_Addr1 = 172.24.238.27
migrate_XECfgParm: setting *.IP_Addr2 = 0.0.0.0
migrate_XECfgParm: setting *.IP_Addr3 = 0.0.0.0
migrate_XECfgParm: setting *.IP_Addr4 = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrLocalA = 172.24.238.27
migrate_XECfgParm: setting *.ipAddrLocalB = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrPeerA = 0.0.0.0
migrate_XECfgParm: setting *.ipAddrPeerB = 0.0.0.0
migrate_XECfgParm: setting foverd.abswitchPort = /dev/null
migrate_XECfgParm: setting XE.ARUWriteDevice = /dev/null
migrate_XECfgParm: setting XE.systemType = SPARC
migrate_XECfgParm: setting foverd.ipLocalPortA = 0
migrate_XECfgParm: setting foverd.ipLocalPortB = 0
migrate_XECfgParm: setting foverd.ipPeerPortA = 0
migrate_XECfgParm: setting foverd.ipPeerPortB = 0
migrate_XECfgParm: setting replicator.portDataChannelSend = 2968
migrate_XECfgParm: setting replicator.portDataChannelRecv = 2970
migrate_XECfgParm: setting replicator.portCommChannelSend = 2972
migrate_XECfgParm: setting replicator.portCommChannelRecv = 2974
migrate_XECfgParm: setting *.SyscheckpointEnabled = false
migrate_XECfgParm: setting *.desiredPlatformState = standalone
migrate_XECfgParm: setting *.stPort = 0
migrate_XECfgParm: setting pom.dataSync = false
migrate_XECfgParm: setting *.chkPtPort = 2001
migrate_XECfgParm: setting engine.SysPropagateChanAvail = false
migrate_XECfgParm: setting engine.SysGeneratedCode = false
migrate_XECfgParm: setting engine.SysScreeningCheck = false
migrate_XECfgParm: setting engine.SysVirtualSwitch = 0
migrate_XECfgParm: setting diskmonitor.Limit = 7
migrate_XECfgParm: setting diskmonitor.Threshold = 80
migrate_XECfgParm: setting diskmonitor.SoftLimit = false
migrate_XECfgParm: setting *.logPrio = Error
migrate_XECfgParm: setting *.logDirectory = ../var/log
migrate_XECfgParm: setting *.logFileNamePrefix = platform
migrate_XECfgParm: setting engine.SysCdrCollection = false
migrate_XECfgParm: setting engine.CDRencodingFormat = AnsiCDB
migrate_XECfgParm: setting engine.CDRtimeStamp = S
migrate_XECfgParm: setting engine.CDRmessageTypes = "1010,1020,1030,1040,1050,1060,1070"
migrate_XECfgParm: setting *.numberOfThreads = 0
migrate_XECfgParm: setting *.dataSourceName = howdydb
migrate_XECfgParm: setting *.maxNumLinks = 32
migrate_XECfgParm: setting *.maxNumMGCPLinks = 1000
migrate_XECfgParm: setting *.dataCommitTime = 10
migrate_XECfgParm: setting MML.timeout = 10000
migrating version.dat
migrating propSet.dat
migrating variant.dat
migrating alarmCats.dat
migrating compTypes.dat
migrating tables.dat
migrating buckets.dat
migrating alarmTable.dat
migrating thresholds.dat
migrating measProfs.dat
migrating measCats.dat
migrating mdlProcess.dat
migrating extProcess.dat
migrating extNodeTypes.dat
migrating processes.dat
migrating properties.dat
migrating bearChanSwitched.dat
migrating dial plan and route analysis files
 
migrating XECfgParm.dat ...
 
 
starting migration ...
 
migrating from version 7.1004 to version 7.1005 ...
 
migration completed successfully
No data file changes required to support CMS
 
Installation of <CSCOgc001> was successful.
Beginning Check of System Performance Requirements
 
Number of CPUs in system  1
Memory size: 128 Megabytes
The sparc processor operates at 248 MHz,
 
 
WARNING Insufficient Memory to run CiscoMGC - should be at least 2048 Megabytes!!
 
 
Swap is total: 16720k bytes allocated + 9992k reserved = 26712k used, 591808k available
Please Verify that you have over 4000000K Available swap
 
install.sh: setting *.numberOfThreads = 0
 
Configure System for (1) Maximum Sustained Calls (2) High Call Throughput 
Enter 1 or 2 or q to quit 1
 
Optimize for Maximum Sustained Calls
install.sh: setting engine.SysMdlMemoryReduction = 1
install.sh: setting engine.CALL_MEM_BLOCK_SIZE = 0
install.sh: setting engine.CALL_MEM_CHUNK_SIZE = 0
 
Installation completed Fri Aug 18 16:31:35 EDT 2000 
Installation log can be found in /tmp/install.log

Note For Software Release 7.4(10) and later, the install.log is renamed as MGC-install.log and stored in the /var/adm directory. In addition, the pkgerrors.log is renamed to MGC_pkgerrors.log and moved to the /var/adm directory.

This completes the installation of the Cisco MGC software. Continue to the "Configuring Groups and Users" section to configure groups and users. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.

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 and Cisco Media Gateway Controller Software Release 7 Reference Guide.)

Verifying the mgcgrp Group

To verify the mgcgrp group, complete the following steps:

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

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 commas (with no spaces) to separate one name in the list from another.

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 user's home directory differs from /opt/CiscoMGC/local, they must perform the following steps before using MML.

Step 1 Log in to the Cisco MGC.

Step 2 Enter the following command and press Enter:

cd /opt/CiscoMGC/local

Step 3 Enter the following command and press Enter:

source .cshrc

Step 4 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 of the Preface.

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).

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

Step 3 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 4 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 3-3: 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 5 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 3-4: 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 6 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 7 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 of the Preface.

Sample Configured snmpd.cnf File

Example 3-5 shows a sample snmpd.cnf file.

Note This sample configuration enables both snmpv1 and snmpv2 traps. Therefore, you will see two coldStart traps when the software is initialized—one for version1 and one for
version 2.

Example 3-5: Sample snmpd.cnf File

TSK# Entry type:sysDescr 
# Entry format:octetString
sysDescr  "SNMPv3 agent from Cisco Systems, Inc."
 
 
# Entry type:sysObjectID 
# Entry format:OID
sysObjectID  enterprises.10.999
 
 
# Entry type:sysLocation 
# Entry format:octetString
sysLocation  "Herndon, Virginia"
 
 
# Entry type:sysContact 
# Entry format:octetString
sysContact  "Cisco Systems, Inc.  +1 703 484 3000"
 
 
# Entry type:sysName 
# Entry format:octetString
sysName  "TISU - VSC"
 
 
# Entry type:snmpEnableAuthenTraps 
# Entry format:integer
snmpEnableAuthenTraps  1
 
# Entry type:MAX_THREADS 
# Entry format:integer
MAX_THREADS  20
 
# Entry type:MAX_PDU_TIME 
# Entry format:integer
MAX_PDU_TIME  2500
 
 
# Entry type:MAX_OUTPUT_WAITING 
# Entry format:integer
MAX_OUTPUT_WAITING  65536
 
 
# Entry type:MAX_SUBAGENTS 
# Entry format:integer
MAX_SUBAGENTS  10
 
 
# Entry type:subagent 
# Entry format:octetString
 
#Entry type:srCommunityEntry
#Format: srCommunityAuthSnmpID  (octetString)
#         srCommunityName  (text)
#         srCommunityGroupName  (text)
#         srCommunityContextSnmpID  (octetString)
#         srCommunityContextName  (text)
#         srCommunityTransportLabel  (text)
#         srCommunityMemoryType  (nonVolatile, permanent, readOnly)
communityEntry  localSnmpID public Anyone localSnmpID default - nonVolatile
 
 
# Entry type:snmpBoots 
# Entry format:integer
snmpBoots  76
 
 
#Entry type:userNameEntry
#Format: userAuthSnmpID  (octetString)
#         userName  (text)
#         userGroupName  (text)
#         userTransportLabel  (text)
#         userMemoryType  (nonVolatile, permanent, readOnly)
 
 
# Entry type:snmpEngineBoots 
# Entry format:integer
snmpEngineBoots  76
 
 
#Entry type:usmUserEntry
#Format: usmUserEngineID  (octetString)
#         usmUserName  (text)
#         usmUserAuthProtocol  (OID)
#         usmUserPrivProtocol  (OID)
#         usmUserStorageType  (nonVolatile, permanent, readOnly)
#         usmTargetTag  (text)
 
 
#Entry type:vacmAccessEntry
#Format: vacmGroupName  (text)
#         vacmAccessContextPrefix  (text)
#         vacmAccessSecurityModel  (snmpv1, snmpv2c, snmpv2s, usm)
#         vacmAccessSecurityLevel  (noAuthNoPriv, authNoPriv, authPriv)
#         vacmAccessContextMatch  (exact, prefix)
#         vacmAccessReadViewName  (text)
#         vacmAccessWriteViewName  (text)
#         vacmAccessNotifyViewName  (text)
#         vacmAccessStorageType  (nonVolatile, permanent, readOnly)
vacmAccessEntry  Guest - usm noAuthNoPriv exact DemoRead DemoWrite DemoRead \
    nonVolatile
vacmAccessEntry  Guest - snmpv2s noAuthNoPriv exact DemoRead DemoWrite \
    DemoRead nonVolatile
vacmAccessEntry  Anyone - snmpv1 noAuthNoPriv exact All All All nonVolatile
vacmAccessEntry  Anyone - snmpv2c noAuthNoPriv exact All All All nonVolatile
vacmAccessEntry  DayOperator - usm noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry  DayOperator - snmpv2s noAuthNoPriv exact All - All \
    nonVolatile
vacmAccessEntry  DayOperator UPS usm noAuthNoPriv prefix All - All nonVolatile
vacmAccessEntry  DayOperator UPS snmpv2s noAuthNoPriv prefix All - All \
    nonVolatile
vacmAccessEntry  SystemAdmin - usm noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry  SystemAdmin - snmpv2s noAuthNoPriv exact All - All \
    nonVolatile
vacmAccessEntry  SystemAdmin UPS usm noAuthNoPriv prefix All - All nonVolatile
vacmAccessEntry  SystemAdmin UPS snmpv2s noAuthNoPriv prefix All - All \
    nonVolatile
vacmAccessEntry  NightOperator - usm noAuthNoPriv exact All - All nonVolatile
vacmAccessEntry  NightOperator - snmpv2s noAuthNoPriv exact All - All \
    nonVolatile
vacmAccessEntry  NightOperator UPS usm noAuthNoPriv prefix All - All \
    nonVolatile
 
vacmAccessEntry  NightOperator UPS snmpv2s noAuthNoPriv prefix All - All \
    nonVolatile
 
 
#Entry type:vacmSecurityToGroupEntry
#Format: vacmSecurityModel  (snmpv1, snmpv2c, snmpv2s, usm)
#         vacmSecurityName  (text)
#         vacmGroupName  (text)
#         vacmSecurityToGroupStorageType  (nonVolatile, permanent, readOnly)
vacmSecurityToGroupEntry  snmpv1 public Anyone nonVolatile
vacmSecurityToGroupEntry  snmpv2c public Anyone nonVolatile
vacmSecurityToGroupEntry  usm Guest Guest nonVolatile
vacmSecurityToGroupEntry  usm AnneXPert HelpDesk nonVolatile
vacmSecurityToGroupEntry  usm EarlERiser DayOperator nonVolatile
vacmSecurityToGroupEntry  usm WyleUSleep NightOperator nonVolatile
vacmSecurityToGroupEntry  usm TonyaTTyper Staff nonVolatile
vacmSecurityToGroupEntry  usm CharlieDChief SystemAdmin nonVolatile
vacmSecurityToGroupEntry  usm BobBBookkeeper Staff nonVolatile
vacmSecurityToGroupEntry  usm ShawnNShipping Staff nonVolatile
 
#Entry type:vacmViewTreeFamilyEntry
#Format: vacmViewTreeFamilyViewName  (text)
#         vacmViewTreeFamilySubtree  (OID)
#         vacmViewTreeFamilyMask  (octetString)
#         vacmViewTreeFamilyType  (included, excluded)
#         vacmViewTreeFamilyStorageType  (nonVolatile, permanent, readOnly)
vacmViewTreeFamilyEntry  All iso - included nonVolatile
vacmViewTreeFamilyEntry  All 0.0 - included nonVolatile
vacmViewTreeFamilyEntry  Network mib_2 - included nonVolatile
vacmViewTreeFamilyEntry  Network snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  Network snmpTraps - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead system - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead srExamples - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead snmpTraps - included nonVolatile
vacmViewTreeFamilyEntry  DemoRead ifEntry.0.2 ff:bf included nonVolatile
vacmViewTreeFamilyEntry  HtmlPage htmlpage - included nonVolatile
vacmViewTreeFamilyEntry  Unsecure system - included nonVolatile
vacmViewTreeFamilyEntry  Unsecure snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  Unsecure snmpTraps - excluded nonVolatile
vacmViewTreeFamilyEntry  DemoWrite srBasics - included nonVolatile
vacmViewTreeFamilyEntry  Confidential enterprises - included nonVolatile
vacmViewTreeFamilyEntry  Confidential system - included nonVolatile
vacmViewTreeFamilyEntry  Confidential snmpTrap - included nonVolatile
vacmViewTreeFamilyEntry  Confidential snmpTraps - included nonVolatile
 
 
#Entry type:snmpNotifyEntry
#Format: snmpNotifyName  (text)
#         snmpNotifyTag  (text)
#         snmpNotifyType  (trap(1), inform(2))
#         snmpNotifyStorageType  (nonVolatile, permanent, readOnly)
snmpNotifyEntry  31 Console trap nonVolatile
snmpNotifyEntry  32 va-primerib trap nonVolatile
 
 
 
#Entry type:snmpTargetAddrEntry
#Format: snmpTargetAddrName  (text)
#         snmpTargetAddrTDomain  (snmpUDPDomain, snmpIPXDomain, etc.)
#         snmpTargetAddrTAddress  (transport address,i.e. 192.147.142.254:0)
#         snmpTargetAddrTimeout  (integer)
#         snmpTargetAddrRetryCount  (integer)
#         snmpTargetAddrTagList  (text)
#         snmpTargetAddrParams  (text)
#         snmpTargetAddrStorageType  (nonVolatile, permanent, readOnly)
#         tgtAddressMask  (transport mask, i.e. 255.255.255.255:0)
snmpTargetAddrEntry  31 snmpUDPDomain 127.0.0.1:0 100 3 Console \
    v1ExampleParams nonVolatile 255.255.255.255:0
snmpTargetAddrEntry  32 snmpUDPDomain 127.0.0.1:0 100 3 Console \
    v2cExampleParams nonVolatile 255.255.255.255:0
snmpTargetAddrEntry  33 snmpUDPDomain 172.24.233.82:0 100 3 va-primerib \
    v1ExampleParams nonVolatile 255.255.255.255:0
snmpTargetAddrEntry  34 snmpUDPDomain 172.24.233.82:0 100 3 va-primerib \
    v2cExampleParams nonVolatile 255.255.255.255:0
 
#Entry type:snmpTargetParamsEntry
#Format: snmpTargetParamsName  (text)
#         snmpTargetParamsMPModel  (integer)
#         snmpTargetParamsSecurityModel  (snmpv1, snmpv2c, snmpv2s, usm)
#         snmpTargetParamsSecurityName  (text)
#         snmpTargetParamsSecurityLevel  (noAuthNoPriv,authNoPriv,authPriv)
#         snmpTargetParamsStorageType  (nonVolatile, permanent, readOnly)
snmpTargetParamsEntry  v1ExampleParams 0 snmpv1 public noAuthNoPriv \
    nonVolatile
snmpTargetParamsEntry  v2cExampleParams 1 snmpv2c public noAuthNoPriv \
    nonVolatile
 
 
#Entry type:snmpNotifyFilterProfileEntry
#Format: snmpTargetParamsName  (text)
#         snmpNotifyFilterProfileName  (text)
#         snmpNotifyFilterProfileStorageType  (nonVolatile,permanent,readOnly)
 
 
#Entry type:snmpNotifyFilterEntry
#Format: snmpNotifyFilterProfileName  (text)
#         snmpNotifyFilterSubtree  (OID)
#         snmpNotifyFilterMask  (octetString)
#         snmpNotifyFilterType  (included, excluded)
#         snmpNotifyFilterStorageType  (nonVolatile, permanent, readOnly)

Configuring the Execution Environment

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

The configuration data file, or XECfgParm.dat file (located in /opt/CiscoMGC/etc/XECfgParm.dat), lists all 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 Cisco Media Gateway Controller Software Release 7 Reference Guide and Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide.)

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

Changing XECfgParm.dat File Parameters

For a complete list of parameters, their functions, definitions, and sample values, see Cisco Media Gateway Controller Software Release 7 Reference Guide.

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 Example 3-6 and Example 3-7.

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 of the Preface.

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 "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 value 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 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; for example, 7000. If your configuration uses a Cisco SLT, enter the port number on the Cisco SLT.

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 they 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 non-tagged 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 Circuit Group Reset (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 by sending 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.

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 other 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.

Note   The default CDR file format has changed from an ASCII format in Release 4 to a binary format in Release 7. 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 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 that happens, 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 that happens, 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 that happens, 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 that happens, 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 the 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, set this value to 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 may 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.

Sample Configured XECfgParm.dat Files

The following sample XECfgParm.dat files are configured for a continuous-service system that has two Cisco MGC hosts. Pay close attention to the values shown in bold, as these values differ on each host.

Example 3-6: Active Host XECfgParm.dat File

# File:  XECfgParm.dat
#
# Purpose:
#
# This file contains configuration parameters that may be accessed by
# XE application programs at run-time.
#
# All lines beginning with a '#' are comments and WILL NOT BE READ BY
# PROGRAMS.  Thus application overrides of the default parameter values
# can be easily added and removed by removing/added a '#'.
#
#------------------------------------------------------------------------------
# Default parameter values have a facility name of "*" and
# will be used if no match is found on a specific facility name
#------------------------------------------------------------------------------
# Specific Facility names are as follows:
#
# logger    - Log Server
# foverd    - Failover Daemon
# MML       - MML
# procM     - Process Manager
# cdrDmpr   - CDR Dumper
# cfgM      - Configuration Manager
# engine    - call processing engine
# ioChanMgr - I/O Channel Managers
# pom       - Provisioning Object Manager
# measM     - Measurement Manager
# OPERSAGT  - Operational SNMP Agent 
# PROVSAGT  - Provisioning SNMP Agent
# mmSAgt    - Measurement Manager SNMP Agent
# almM      - Alarm Manager
# replicator- Replicator
# mmdb      - TimesTen Main Memory Data Base Process
# amDmpr    - Alarm / Measurement Dumper
# ioChanCtl - controls all channel controllers
#
#----Special Paremeter Section----
# callver     - call verification utility
# diskmonitor - disk monitor shell script
# XE          - Execution Environment
#
#------------------------------------------------------------------------------
 
*.disableMeas =	false	            # T ==> Don't accumulate meas in shared mem
*.sm_meas_baseaddr = 3400           # shared memory based address
 
*.platformId =                      1
*.transpathId =			    01      # Transpath Id for ASN
*.tempDir =                         /tmp    # temporary directory
*.dataDir =                         ../var  # volatile data directory
*.homeDirRoot =			    /opt/CiscoMGC
*.logDirectory =                    ../var/log   # NEW log directory
*.logFileNamePrefix =               platform     # NEW log prefix
*.logPrio     =                     Error
*.logMsgDrop =                      false
*.eventTrace =                      false
*.debugLevel =                      high
*.tablesFile =                      ../etc/tables.dat  # tables that can be loaded
*.autonomous   =                    false
*.runAsDaemon =                     true  
*.ownTranspathId =                  01
*.peerTranspathId =                 02
*.desiredPlatformState =            master
*.SyscheckpointEnabled =            true
*.chkPtPort =                       2001
*.maxNumLinks =                     32
*.maxNumPRIL3Links =                504
*.maxNumMGCPLinks =                 1000
*.numberOfThreads = 2    
*.dataSourceName = 	            howdydb
*.dataCommitTime =                  10        # in millisecs
*.VSCNetworkPlacement =             0         # string values do not require quotes
*.ClearingLocation =                0         # 0 = LCM will not override this field
*.DefaultLocation =                 0         # 0 = LCM will not override this field
*.detailedCallEventCapture =        0         # detailed event capture on     
		 
*.ipAddrLocalA =                    172.24.233.67   # Should be same as *.IP_Addr1
*.ipAddrLocalB =                    10.10.11.80
*.ipAddrPeerA =                     172.24.233.225   # Failover peer's address
*.ipAddrPeerB =                     10.10.11.90
 
 
*.IP_Addr1 =                        172.24.233.67   # Address of interface on motherboard
*.IP_Addr2 =                        10.10.11.80
*.IP_Addr3 =                        0.0.0.0
*.IP_Addr4 =                        0.0.0.0
 
*.stPort =                          7000
 
#------------------------------------------------------------------------
# Log Server logfile locations
#------------------------------------------------------------------------
# run as daemon
logger.runAsDaemon = false 
 
# daemonAddr is socket port for logger daemon
logger.daemonAddr = ../var/lsd_addr
 
# NEW logfile rotation size max in Megabytes
logger.fileRotateSize = 100     
 
# NEW logfile rotation interval in minutes (24 hrs default)
logger.fileRotateInterval = 1440
 
# numThreads can be 0 or 1, if 1 then logger client runs in its
# own thread
logger.numThreads = 0
 
# category log files to be used with caution due to performance impact
#logger.gen = ../var/log/gen.log
#logger.env = ../var/log/env.log
#logger.tios = ../var/log/tios.log
#logger.cp = ../var/log/cp.log
#logger.prot = ../var/log/prot.log
#logger.mgmt = ../var/log/mgmt.log
#logger.mml = ../var/log/mml.log
 
#-------------------------------------------------------------------------
# Facility specific parameters
#   The remainder of this file pertains to parameters and parameter overrides
#   for individual facilitites.
#
# LogPrio and autonomous are changed for debug testing only.  Otherwise
# everyone should use the defaults above (except MML, see below.)
#-------------------------------------------------------------------------
 
# Specialized logging level for debug, fault isolation
#
# Usage of these debug parameters could cause the system to use up
# space more rapidly than normal.  If the DISK alarm is activated because
# of this activity, certain files in /opt/CiscoMGC/var/spool will be erased.
#
# ioChanCtl.logPrio  =              Info
procM.logPrio =                   Info
almM.logPrio =                   Info
# engine.logPrio =		    Info
# PROVSAGT.logPrio =		    Info
# OPERSAGT.logPrio =		    Info
# mmSAgt.logPrio =		    Info
# mmdb.logPrio =		    Info
 
# Specialized "autonomous" flags for debug, fault isolation
# engine.autonomous =		    true
# cfgM.autonomous =		    true
Talk2.autonomous   =                false
 
#--------------
# procM
#--------------
 
procM.minCheckHealthInterval =      10        # smallest check health interval
procM.minCheckHealthTimeout =       60        # smallest check health timeout
procM.minKillGracePeriod =          5         # smallest kill grace period
procM.almDwellInterval =            15        # seconds to wait before clearing alarm
procM.procHealthDfltAlmCat =        pmDefault # default alarm category for PM
procM.servicesDir  =                ../var         # location of PM temporary FIFOs
procM.servFmt      =                PM_%d_%d_input # format of PM temporary FIFOs
procM.recovDbFile  =                ../var/procMRecovery # PM recovery info
procM.logDBFile    =                ../var/procMLogTable # log info for recovery only
procM.runAsDaemon  =                true
 
 
#-------------
# cfgM
#-------------
 
cfgM.recovDbFile   =                ../var/cfgMRecovery  # CfgM recovery info
 
#-------------
# Engine
#-------------
 
engine.SysVirtualSwitch = 0            # 0=Nailed-Up, 1=Switched-VSC, 2=Switched-JCS
engine.SysCdrCollection = false        # set to true to generate  nonTagged old-style CDR
engine.SysPropagateChanAvail = false   # auto-blocking of C7 cics and ISDN sigPaths
engine.SysGeneratedCode = true         # false=interpreted(.mdo),true=compiled(.so) protocols
engine.SysGRSTimerInterval = 500
engine.SysGRSBlockSize = 1        
engine.SysSGCPRetryCount = 3           # max number of SGCP retry messages after failure
engine.SysSGCPRetryTimerInterval = 1000   # interval between retransmission (msec) 
engine.SysCLIval = false
engine.SysToneDetect = false
engine.SysNumTrans = false
engine.SysMinOverlap = 0
engine.SysMaxOverlap = 28
engine.SysScreeningCheck = false       # call screening using the database
#engine.LCMMdlFile = ../lib/lcm         # LSI call model
engine.LCMMdlFile = /auto/vsc-perf/90K_new/protocols/release_8T/lcm         # LSI call model
#engine.CCMdlFile =  ../lib/cc          # call context
engine.CCMdlFile =  /auto/vsc-perf/90K_new/protocols/release_8T/cc          # call context
#engine.mdoDir = ../lib/                # where .mdo files live
engine.mdoDir = /auto/vsc-perf/90K_new/protocols/release_8T/                # where .mdo files live
engine.VersionTimeoutValue = 10000     # Interval for version messages (msec)
engine.SysMdlMemoryReduction = 1    
engine.MDLANumberScreening = 0         # use calling party number for a number screening
 
#The following two lines are call based memory allocator settings. 
#set these to 0 to disable call-based memory allocator
#This setting is memory efficient, but performance suffers.
#set these to 110000 for maximum performance. Memory usage increases. 
engine.CALL_MEM_BLOCK_SIZE = 0    
engine.CALL_MEM_CHUNK_SIZE = 0    
 
# engine.SysTraceLevel = 3
 
*.LongCallTime = 21600000              # used to configure OnGoingCallTime in ms (6hrs def)
 
#
# The following overload parameter thresholds were set based on
# CPU utilization.
#
# OvlxOnsetThresh= percentage of total CPU utilization at which the overload
#level will be in effect.
# OvlxAbateThresh= percentage of total CPU utilization at which the overload
#level will no longer be in effect.  Abatement must be less than onset.
# OvlxRejectPercent= percentage of new calls that will be rejected at this
#overload
# CPUTimerInterval = refresh timer to read and compute the CPU utilization
# level. EX: 20% means 1 out of every 5 new
# calls will be rejected at this level.
#
*.Ovl1OnsetThresh = 82
*.Ovl1AbateThresh = 75
*.Ovl1RejectPercent = 25
 
*.Ovl2OnsetThresh = 90
*.Ovl2AbateThresh = 77
*.Ovl2RejectPercent = 50
 
*.Ovl3OnsetThresh = 93
*.Ovl3AbateThresh = 85
*.Ovl3RejectPercent = 100
 
#CPU Utilization sampling interval in msec.
*.CPUTimerInterval = 1000
 
 
engine.CDRencodingFormat  = ItuCDB
engine.CDRtimeStamp  = S
engine.CDRmessageTypes   = "1010,1020,1030,1040,1050,1060,1070" 
 
engine.VersionTimeoutValue = 10000
engine.StartUpAuditEnabled = false    # audit invoked at engine startup?
 
#----------------------
# CDR dumper (cdrDmpr)
#----------------------
cdrDmpr.openCDR        = true
cdrDmpr.callDetail     = /opt/CiscoMGC/local/cdbscript.sh
cdrDmpr.seqFile        = ../var/.cdr.seq
 
#------------------------------------
# Alarms/Measurements dumper (amDmpr)
#------------------------------------
 
#-------------
# ioChanMgr
#-------------
 
# Internal debug - only use this for low-level IOS debug
# This is bitmapped hex value:
#   1 - Managed Object tracing
#   2 - Simulation of streams devices from /dev to ../dev for 
#	unit testing.
ioChanMgr.trace =		    0x0
 
# These timers are in millisecs
# NOTE:  alarms are sent autonomously as they occur, alarmTimer is outdated
# and should be set to zero
ioChanMgr.alarmTimer =                  0
ioChanMgr.statTimer  =              30000
 
#Channel manager parameters for IPC flow control.
#  evtTimer(msec.) - Frequency at which the queue is scanned for Msgs.
#  hbTimer(msec.)  - Heart-beat timer, Not yet implemented.
#  statDiscardThreshold - Size of Control Queue that triggers discarding 
#                         all the queued stat events.
#  sendThreshold - Max. Number of Events from the Queue sent  at a time.
ioChanMgr.evtTimer  =                 100
ioChanMgr.hbTimer  =                 1000
ioChanMgr.statDiscardThreshold =       40
ioChanMgr.sendThreshold =              10
 
#-----------
# ioChanCtl
#-----------
ioChanCtl.DPNSSTestFrames = true 
ioChanCtl.xgcpMultiThread = true       # enable threading for the IP receive loop in MGCP
 
#-----------
# measM
#-----------
#
#  The sm_num_meas and sm_seg_size parameters are related.
#  For Elan, assume 8000 XEMeas objects fit into 8 Mb of shared memory.
#
measM.sm_num_meas = 32000    # max number of XEMeas objects than can be created (default=16000)
measM.sm_seg_size = 32       # size of shared memory in Mb (default is 32) 
measM.loadBalanceFactor = 20 # num of measmgr distribution points every 5 minutes
 
#----------
# almM
#----------
# almM.runAsDaemon =                  false
 
#-------------
# MML - since this is started and stopped by user, it
#       has the following unique requirements for logging.
#       - to alter logging levels, the logPrio parameter 
#         must be changed here, then the MML process
#         started to pick up the change.  The set-log
#         command does not affect any MML processes
#
#     - Currently MML must ALWAYS have autonomous=true
#-------------
 
MML.logPrio = Info                 # causes all MML messages to be written to the log
MML.logFileNamePrefix = mml         # causes MML messages to be diverted to mml.log
 
MML.autonomous = true
MML.runAsDaemon = false
 
MML.timeout=10000                          # in milliseconds 
#                                              (note: current XE supports 1-second resolution)
#
# individual timeout values for MML commands:
# format is:  MML.<verb> = time
# (verb all lowercase)
MML.set-sc-state = 	8500
MML.chg-cfg = 		10000
MML.startPM = 		/etc/init.d/CiscoMGC start
MML.stopPM = 		/etc/init.d/CiscoMGC stop
MML.vld-cic = 		25000
MML.snd = 		600000
 
#----------
# XE
#----------
# The next lines about ARU are here only for release 1.1
# heartbeat rate (secs): 5-255, MUST CORRESPOND TO PHYSICAL SETTING ON ARU;
# if not set, 255 will be used
XE.heartBeatRate =                  60
 
# name of the device where ARU expects to read alarm strings from; if not set,
# /dev/tty will be used
# Set this to /dev/null if an ARU is not attached 
#          or DRYCONTACT to use the Netra CMS device
XE.ARUWriteDevice =                 /dev/null
 
#systemType: NETRA-FT    means sheffield NETRA 1800FT
#systemType: NETRA       means NETRA T1100,T1120
#systemType: SPARC       means generic box without alrm LED and ARU
#systemType: SPARC-ARU   means generic  box with ARU,without alrm LED
XE.systemType =                SPARC 
 
#-----------
# foverd
#-----------
 
# NOTE: addresses below must be configured for the target system
#       - connTypes can be "socket", "serial", or "fifo"
 
# connection 1 parameters
foverd.conn1Type = socket
foverd.ipLocalPortA = 1051
foverd.ipPeerPortA = 1052
 
# connection 2 parameters
foverd.conn2Type = socket
foverd.ipLocalPortB = 1053
foverd.ipPeerPortB = 1054
 
# connection 3 parameters
foverd.conn3Type =         serial
foverd.conn3Addr =         /dev/null
 
foverd.heartbeatInterval = 4000
foverd.ackTimeout =        1000
foverd.abswitchTestInterval = 30000
foverd.graceShutTimeout =  6000
foverd.forceShutTimeout =  1000
foverd.commRetryInterval = 30000
foverd.statusRptInterval = 600000
foverd.peerCommTimeout =   10000
foverd.delayTimeout =      1000
foverd.transitionTimeout = 10000
foverd.abswitchPort =     /dev/null
 
# -----------------------------------------------------
#foverd.runAsDaemon =      false
# -----------------------------------------------------
#foverd.logPrio     =      Info
 
#-----------------
# Network Element 
#-----------------
 
product.vendor = "Cisco Systems, Inc."
product.version = "7.4(10)A"
product.time = "....."
 
#----------------------------------
# POM - Provisioning Object Manager
#----------------------------------
pom.dataSync = true                  # don't synch slave data with master
pom.port     = default                # use port 4001 when set to default
 
#----------------------------------
# Replicator
#----------------------------------
replicator.portDataChannelSend = 2968
replicator.portDataChannelRecv = 2970
replicator.portCommChannelSend = 2972
replicator.portCommChannelRecv = 2974
replicator.reconnectInterval = 15
replicator.numberReadThreads = 1       # optional thread (0=no threads,1=one thread)
 
#-----------------
# Audit properties
#-----------------
 
#engine.AuditTimerInterval = 500
#engine.MaxAuditCics = 32
#engine.AuditOverloadLvl = 25
 
#------------------
# CVT Parameters
#------------------
 
#*.OwnClli = TTTT-SS-BB-XXX
#*.OwnClli = 1-22-33-444
 
#----------------------------------
# Disk Monitor Parameters
#----------------------------------
 
diskmonitor.Limit      = 7        # Number of days to preserve
diskmonitor.Threshold  = 80       # percentage full threshold
diskmonitor.SoftLimit  = true    # set to true to allow override of preserve limit
diskmonitor.CdrRmFinished = 0     # remove "finished" cdrs after X days (0 = immediate)
diskmonitor.OptFileSys =          # list of optional filesystems to monitor (no trimming)
 
#--------------------------------
# call verification utility Parameters
#--------------------------------
callver.SaveArea = ../etc/cust_specific/toolkit
 
#------------------------------------------------------------------------------
#  End of XE Configuration Parameter File
#------------------------------------------------------------------------------

Example 3-7: Standby Host XECfgParm.dat File

# File:  XECfgParm.dat
#
# Purpose:
#
# This file contains configuration parameters that may be accessed by
# XE application programs at run-time.
#
# All lines beginning with a '#' are comments and WILL NOT BE READ BY
# PROGRAMS.  Thus application overrides of the default parameter values
# can be easily added and removed by removing/added a '#'.
#
#------------------------------------------------------------------------------
# Default parameter values have a facility name of "*" and
# will be used if no match is found on a specific facility name
#------------------------------------------------------------------------------
# Specific Facility names are as follows:
#
# logger    - Log Server
# foverd    - Failover Daemon
# MML       - MML
# procM     - Process Manager
# cdrDmpr   - CDR Dumper
# cfgM      - Configuration Manager
# engine    - call processing engine
# ioChanMgr - I/O Channel Managers
# pom       - Provisioning Object Manager
# measM     - Measurement Manager
# OPERSAGT  - Operational SNMP Agent 
# PROVSAGT  - Provisioning SNMP Agent
# mmSAgt    - Measurement Manager SNMP Agent
# almM      - Alarm Manager
# replicator- Replicator
# mmdb      - TimesTen Main Memory Data Base Process
# amDmpr    - Alarm / Measurement Dumper
# ioChanCtl - controls all channel controllers
#
#----Special Paremeter Section----
# callver     - call verification utility
# diskmonitor - disk monitor shell script
# XE          - Execution Environment
#
#------------------------------------------------------------------------------
 
*.disableMeas =	false	            # T ==> Don't accumulate meas in shared mem
*.sm_meas_baseaddr = 3400           # shared memory based address
 
*.platformId =                      1
*.transpathId =			    02      # Transpath Id for ASN
*.tempDir =                         /tmp    # temporary directory
*.dataDir =                         ../var  # volatile data directory
*.homeDirRoot =			    /opt/CiscoMGC
*.logDirectory =                    ../var/log   # NEW log directory
*.logFileNamePrefix =               platform     # NEW log prefix
*.logPrio     =                     Error
*.logMsgDrop =                      false
*.eventTrace =                      false
*.debugLevel =                      high
*.tablesFile =                      ../etc/tables.dat  # tables that can be loaded
*.autonomous   =                    false
*.runAsDaemon =                     true  
*.ownTranspathId =                  02
*.peerTranspathId =                 01
*.desiredPlatformState =            slave
*.SyscheckpointEnabled =            true
*.chkPtPort =                       2001
*.maxNumLinks =                     32
*.maxNumPRIL3Links =                504
*.maxNumMGCPLinks =                 1000
*.numberOfThreads = 2    
*.dataSourceName = 	            howdydb
*.dataCommitTime =                  10        # in millisecs
*.VSCNetworkPlacement =             0         # string values do not require quotes
*.ClearingLocation =                0         # 0 = LCM will not override this field
*.DefaultLocation =                 0         # 0 = LCM will not override this field
*.detailedCallEventCapture =        0         # detailed event capture on     
		 
*.ipAddrLocalA =                    172.24.233.225   # Should be same as *.IP_Addr1
*.ipAddrLocalB =                    10.10.11.90
*.ipAddrPeerA =                     172.24.233.67   # Failover peer's address
*.ipAddrPeerB =                     10.10.11.80
 
*.IP_Addr1 =                        172.24.233.225   # Address of interface on motherboard
*.IP_Addr2 =                        10.10.11.90
*.IP_Addr3 =                        0.0.0.0
*.IP_Addr4 =                        0.0.0.0
 
*.stPort =                          7001
 
#------------------------------------------------------------------------
# Log Server logfile locations
#------------------------------------------------------------------------
# run as daemon
logger.runAsDaemon = false 
 
# daemonAddr is socket port for logger daemon
logger.daemonAddr = ../var/lsd_addr
 
# NEW logfile rotation size max in Megabytes
logger.fileRotateSize = 100     
 
# NEW logfile rotation interval in minutes (24 hrs default)
logger.fileRotateInterval = 1440
 
# numThreads can be 0 or 1, if 1 then logger client runs in its
# own thread
logger.numThreads = 0
 
# category log files to be used with caution due to performance impact
#logger.gen = ../var/log/gen.log
#logger.env = ../var/log/env.log
#logger.tios = ../var/log/tios.log
#logger.cp = ../var/log/cp.log
#logger.prot = ../var/log/prot.log
#logger.mgmt = ../var/log/mgmt.log
#logger.mml = ../var/log/mml.log
 
#-------------------------------------------------------------------------
# Facility specific parameters
#   The remainder of this file pertains to parameters and parameter overrides
#   for individual facilitites.
#
# LogPrio and autonomous are changed for debug testing only.  Otherwise
# everyone should use the defaults above (except MML, see below.)
#-------------------------------------------------------------------------
 
# Specialized logging level for debug, fault isolation
#
# Usage of these debug parameters could cause the system to use up
# space more rapidly than normal.  If the DISK alarm is activated because
# of this activity, certain files in /opt/CiscoMGC/var/spool will be erased.
#
# ioChanCtl.logPrio  =              Info
procM.logPrio =                   Info
almM.logPrio =                   Info
# engine.logPrio =		    Info
# PROVSAGT.logPrio =		    Info
# OPERSAGT.logPrio =		    Info
# mmSAgt.logPrio =		    Info
# mmdb.logPrio =		    Info
 
# Specialized "autonomous" flags for debug, fault isolation
# engine.autonomous =		    true
# cfgM.autonomous =		    true
Talk2.autonomous   =                false
 
#--------------
# procM
#--------------
 
procM.minCheckHealthInterval =      10        # smallest check health interval
procM.minCheckHealthTimeout =       60        # smallest check health timeout
procM.minKillGracePeriod =          5         # smallest kill grace period
procM.almDwellInterval =            15        # seconds to wait before clearing alarm
procM.procHealthDfltAlmCat =        pmDefault # default alarm category for PM
procM.servicesDir  =                ../var         # location of PM temporary FIFOs
procM.servFmt      =                PM_%d_%d_input # format of PM temporary FIFOs
procM.recovDbFile  =                ../var/procMRecovery # PM recovery info
procM.logDBFile    =                ../var/procMLogTable # log info for recovery only
procM.runAsDaemon  =                true
 
 
#-------------
# cfgM
#-------------
 
cfgM.recovDbFile   =                ../var/cfgMRecovery  # CfgM recovery info
 
#-------------
# Engine
#-------------
 
engine.SysVirtualSwitch = 0            # 0=Nailed-Up, 1=Switched-VSC, 2=Switched-JCS
engine.SysCdrCollection = false        # set to true to generate  nonTagged old-style CDR
engine.SysPropagateChanAvail = false   # auto-blocking of C7 cics and ISDN sigPaths
engine.SysGeneratedCode = true         # false=interpreted(.mdo),true=compiled(.so) protocols
engine.SysGRSTimerInterval = 500
engine.SysGRSBlockSize = 1        
engine.SysSGCPRetryCount = 3           # max number of SGCP retry messages after failure
engine.SysSGCPRetryTimerInterval = 1000   # interval between retransmission (msec) 
engine.SysCLIval = false
engine.SysToneDetect = false
engine.SysNumTrans = false
engine.SysMinOverlap = 0
engine.SysMaxOverlap = 28
engine.SysScreeningCheck = false       # call screening using the database
#engine.LCMMdlFile = ../lib/lcm         # LSI call model
engine.LCMMdlFile = /auto/vsc-perf/90K_new/protocols/release_8T/lcm         # LSI call model
#engine.CCMdlFile =  ../lib/cc          # call context
engine.CCMdlFile =  /auto/vsc-perf/90K_new/protocols/release_8T/cc          # call context
#engine.mdoDir = ../lib/                # where .mdo files live
engine.mdoDir = /auto/vsc-perf/90K_new/protocols/release_8T/                # where .mdo files live
engine.VersionTimeoutValue = 10000     # Interval for version messages (msec)
engine.SysMdlMemoryReduction = 1    
engine.MDLANumberScreening = 0         # use calling party number for a number screening
 
#The following two lines are call based memory allocator settings. 
#set these to 0 to disable call-based memory allocator
#This setting is memory efficient, but performance suffers.
#set these to 110000 for maximum performance. Memory usage increases. 
engine.CALL_MEM_BLOCK_SIZE = 0    
engine.CALL_MEM_CHUNK_SIZE = 0    
 
# engine.SysTraceLevel = 3
 
*.LongCallTime = 21600000              # used to configure OnGoingCallTime in ms (6hrs def)
 
#
# The following overload parameter thresholds were set based on
# CPU utilization.
#
# OvlxOnsetThresh= percentage of total CPU utilization at which the overload
#level will be in effect.
# OvlxAbateThresh= percentage of total CPU utilization at which the overload
#level will no longer be in effect.  Abatement must be less than onset.
# OvlxRejectPercent= percentage of new calls that will be rejected at this
#overload
# CPUTimerInterval = refresh timer to read and compute the CPU utilization
# level. EX: 20% means 1 out of every 5 new
# calls will be rejected at this level.
#
*.Ovl1OnsetThresh = 82
*.Ovl1AbateThresh = 75
*.Ovl1RejectPercent = 25
 
*.Ovl2OnsetThresh = 90
*.Ovl2AbateThresh = 77
*.Ovl2RejectPercent = 50
 
*.Ovl3OnsetThresh = 93
*.Ovl3AbateThresh = 85
*.Ovl3RejectPercent = 100
 
#CPU Utilization sampling interval in msec.
*.CPUTimerInterval = 1000
 
 
engine.CDRencodingFormat  = ItuCDB
engine.CDRtimeStamp  = S
engine.CDRmessageTypes   = "1010,1020,1030,1040,1050,1060,1070" 
 
engine.VersionTimeoutValue = 10000
engine.StartUpAuditEnabled = false    # audit invoked at engine startup?
 
#----------------------
# CDR dumper (cdrDmpr)
#----------------------
cdrDmpr.openCDR        = true
cdrDmpr.callDetail     = /opt/CiscoMGC/local/cdbscript.sh
cdrDmpr.seqFile        = ../var/.cdr.seq
 
#------------------------------------
# Alarms/Measurements dumper (amDmpr)
#------------------------------------
 
#-------------
# ioChanMgr
#-------------
 
# Internal debug - only use this for low-level IOS debug
# This is bitmapped hex value:
#   1 - Managed Object tracing
#   2 - Simulation of streams devices from /dev to ../dev for 
#	unit testing.
ioChanMgr.trace =		    0x0
 
# These timers are in millisecs
# NOTE:  alarms are sent autonomously as they occur, alarmTimer is outdated
# and should be set to zero
ioChanMgr.alarmTimer =                  0
ioChanMgr.statTimer  =              30000
 
#Channel manager parameters for IPC flow control.
#  evtTimer(msec.) - Frequency at which the queue is scanned for Msgs.
#  hbTimer(msec.)  - Heart-beat timer, Not yet implemented.
#  statDiscardThreshold - Size of Control Queue that triggers discarding 
#                         all the queued stat events.
#  sendThreshold - Max. Number of Events from the Queue sent  at a time.
ioChanMgr.evtTimer  =                 100
ioChanMgr.hbTimer  =                 1000
ioChanMgr.statDiscardThreshold =       40
ioChanMgr.sendThreshold =              10
 
#-----------
# ioChanCtl
#-----------
ioChanCtl.DPNSSTestFrames = true 
ioChanCtl.xgcpMultiThread = true       # enable threading for the IP receive loop in MGCP
 
#-----------
# measM
#-----------
#
#  The sm_num_meas and sm_seg_size parameters are related.
#  For Elan, assume 8000 XEMeas objects fit into 8 Mb of shared memory.
#
measM.sm_num_meas = 32000    # max number of XEMeas objects than can be created (default=16000)
measM.sm_seg_size = 32       # size of shared memory in Mb (default is 32) 
measM.loadBalanceFactor = 20 # num of measmgr distribution points every 5 minutes
 
#----------
# almM
#----------
# almM.runAsDaemon =                  false
 
#-------------
# MML - since this is started and stopped by user, it
#       has the following unique requirements for logging.
#       - to alter logging levels, the logPrio parameter 
#         must be changed here, then the MML process
#         started to pick up the change.  The set-log
#         command does not affect any MML processes
#
#     - Currently MML must ALWAYS have autonomous=true
#-------------
 
MML.logPrio = Info                 # causes all MML messages to be written to the log
MML.logFileNamePrefix = mml         # causes MML messages to be diverted to mml.log
 
MML.autonomous = true
MML.runAsDaemon = false
 
MML.timeout=10000                          # in milliseconds 
#                                              (note: current XE supports 1-second resolution)
#
# individual timeout values for MML commands:
# format is:  MML.<verb> = time
# (verb all lowercase)
MML.set-sc-state = 	8500
MML.chg-cfg = 		10000
MML.startPM = 		/etc/init.d/CiscoMGC start
MML.stopPM = 		/etc/init.d/CiscoMGC stop
MML.vld-cic = 		25000
MML.snd = 		600000
 
#----------
# XE
#----------
# The next lines about ARU are here only for release 1.1
# heartbeat rate (secs): 5-255, MUST CORRESPOND TO PHYSICAL SETTING ON ARU;
# if not set, 255 will be used
XE.heartBeatRate =                  60
 
# name of the device where ARU expects to read alarm strings from; if not set,
# /dev/tty will be used
# Set this to /dev/null if an ARU is not attached 
#          or DRYCONTACT to use the Netra CMS device
XE.ARUWriteDevice =                 /dev/null
 
#systemType: NETRA-FT    means sheffield NETRA 1800FT
#systemType: NETRA       means NETRA T1100,T1120
#systemType: SPARC       means generic box without alrm LED and ARU
#systemType: SPARC-ARU   means generic  box with ARU,without alrm LED
XE.systemType =                SPARC 
 
#-----------
# foverd
#-----------
 
# NOTE: addresses below must be configured for the target system
#       - connTypes can be "socket", "serial", or "fifo"
 
# connection 1 parameters
foverd.conn1Type = socket
foverd.ipLocalPortA = 1052
foverd.ipPeerPortA = 1051
 
# connection 2 parameters
foverd.conn2Type = socket
foverd.ipLocalPortB = 1054
foverd.ipPeerPortB = 1053
 
# connection 3 parameters
foverd.conn3Type =         serial
foverd.conn3Addr =         /dev/null
 
foverd.heartbeatInterval = 4000
foverd.ackTimeout =        1000
foverd.abswitchTestInterval = 30000
foverd.graceShutTimeout =  6000
foverd.forceShutTimeout =  1000
foverd.commRetryInterval = 30000
foverd.statusRptInterval = 600000
foverd.peerCommTimeout =   10000
foverd.delayTimeout =      1000
foverd.transitionTimeout = 10000
foverd.abswitchPort =     /dev/null
 
# -----------------------------------------------------
#foverd.runAsDaemon =      false
# -----------------------------------------------------
#foverd.logPrio     =      Info
 
#-----------------
# Network Element 
#-----------------
 
product.vendor = "Cisco Systems, Inc."
product.version = "7.4(10)A"
product.time = "....."
 
#----------------------------------
# POM - Provisioning Object Manager
#----------------------------------
pom.dataSync = true                  # don't synch slave data with master
pom.port     = default                # use port 4001 when set to default
 
#----------------------------------
# Replicator
#----------------------------------
replicator.portDataChannelSend = 2968
replicator.portDataChannelRecv = 2970
replicator.portCommChannelSend = 2972
replicator.portCommChannelRecv = 2974
replicator.reconnectInterval = 15
replicator.numberReadThreads = 1       # optional thread (0=no threads,1=one thread)
 
#-----------------
# Audit properties
#-----------------
 
#engine.AuditTimerInterval = 500
#engine.MaxAuditCics = 32
#engine.AuditOverloadLvl = 25
 
#------------------
# CVT Parameters
#------------------
 
#*.OwnClli = TTTT-SS-BB-XXX
#*.OwnClli = 1-22-33-444
 
#----------------------------------
# Disk Monitor Parameters
#----------------------------------
 
diskmonitor.Limit      = 7        # Number of days to preserve
diskmonitor.Threshold  = 80       # percentage full threshold
diskmonitor.SoftLimit  = true    # set to true to allow override of preserve limit
diskmonitor.CdrRmFinished = 0     # remove "finished" cdrs after X days (0 = immediate)
diskmonitor.OptFileSys =          # list of optional filesystems to monitor (no trimming)
 
#--------------------------------
# call verification utility Parameters
#--------------------------------
callver.SaveArea = ../etc/cust_specific/toolkit
 
#------------------------------------------------------------------------------
#  End of XE Configuration Parameter File
#------------------------------------------------------------------------------

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. The trigger.dat file (located in /opt/CiscoMGC/etc), contains the message-sending table that contains translation values. You must manually edit the parameters in the trigger.dat file to enable SCP queries.

This section contains the following topics:

Caution 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

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.

Modifying the trigger.dat File

Note The trigger.dat file is not overwritten during software installation. Any 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 or transpathId.trigger file, after installing a new software release you need to view the trigger.template file and copy any changes in that file to your transpathId.trigger file.

To access and edit the trigger.dat file, complete the following steps:

Note If you have two Cisco MGC hosts in a switchover configuration, you must modify the trigger.dat file on each host.

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

Step 2 Copy the trigger.dat file to transpathId.trigger, where transpathId is the value in the XECfgParm.dat file on that host.

Example:
cd /opt/CiscoMGC/etc
cp trigger.dat 01.trigger

Step 3 Open the new transpathId.trigger file in your editor.

Step 4 In the transpathId.trigger file, find the $MessageSending table.

Step 5 Edit the file as follows:

a. In the $MessageSending table, select the type of translation you are using. This value is in the seventh column of the table (see Table 3-1).

# MS 1:xxxxxx LNP
# MS 2:Generic LNP
# MS 3:xxxxxxx 800
# MS 4:ANSI AIN 800 NPA
# MS 5:ANSI AIN 800 NPA-NXX
# MS 6:ANSI AIN 800 NPA-NXX-XXX
# MS 7:ANSI AIN 800 Termination information
# MS 8:ANSI PRE AIN 800
# MS 9:ANSI PRE AIN 800 Termination information

b. In the table for your translation type, change the translationType value (column F7) to the value from the Global Title Translation table you got from your STP administrator.

Step 6 Save your changes and close the editor.

Step 7 Restart the Cisco MGC software by entering the following command:

# /etc/init.d/CiscoMGC start

Table 3-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
##############
# ACTn Values
# MSG_ACTION_NONE                                := 0
# MSG_ACTION_COPY_SCCP_GT_FROM_BNUMBER           := 1
# MSG_ACTION_IS_LNP_M_BIT_CLEAR                  := 2
# MSG_ACTION_COPY_STP_SCP_INDEX_FROM_SIGNAL_DATA := 3
# MSG_ACTION_EXIT_AFTER_SENDING_MESSAGE          := 4
#
# REQuired Values
# FALSE := 0
# TRUE  := 1
#
# 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
###############
#
# transport Values
# TCAP_TRANSPORT_SCCP                              := 1
# TCAP_TRANSPORT_TCP_IP                            := 2
#
# tcapType Values
# TCAP_TYPE_ETSI_300_374_1                         := 1
# TCAP_TYPE_BELL_TR_NWT_001285                     := 2
# TCAP_TYPE_BELL_PRE_AIN                           := 3
#
# stpScpGroupIndex Values
# INTEGER to index ios dat file
#
# msg Values
# --//ITU
# BEGIN_ID                                         := 1
# CONTINUE_ID                                      := 2
# END_ID                                           := 3
# --//ANSI
# UNIDIRECTIONAL_ID                                := 5
# QUERY_WITH_PERMISSION_ID                         := 6
# QUERY_WITHOUT_PERMISSION_ID                      := 99
# RESPONSE_ID                                      := 8
# CONVERSATION_WITH_PERMISSION_ID                  := 9
# CONVERSATION_WITHOUT_PERMISSION_ID               := 100
# ABORT_ID                                         := 17
# PROTOCOL_ABORT_ID                                := 12
# USER_ABORT_ID                                    := 11
# --//GENERAL
# CONST RELEASE_ID                                 := 16
# CONST INFORMATION_ID                             := 15
#
# asn1Encoding Values
# ASN1_DEFINITE                                    := 0
# ASN1_INDEFINITE                                  := 1
#
# tcv_sk Values
# INTEGER value of Trigger Criteria Type or Service Key
# TRIG_CRITERIA_FEATURE_ACTIVATOR                  := 0,
# TRIG_CRITERIA_VERT_SERV_CODE                     := 1,
# TRIG_CRITERIA_CUSTOMIZED_ACCESS                  := 2,
# TRIG_CRITERIA_CUSTOMIZED_INTERCOM                := 3,
# TRIG_CRITERIA_NPA                                := 4,
# TRIG_CRITERIA_NPA_NXX                            := 5,
# TRIG_CRITERIA_NXX                                := 6,
# TRIG_CRITERIA_NXX_XXX                            := 7,
# TRIG_CRITERIA_NPA_NXXXXXX                        := 8,
# TRIG_CRITERIA_COUNTRY_NPA_NXXXXXX                := 9,
# TRIG_CRITERIA_CARRIER_ACCESS                     := 10,
# TRIG_CRITERIA_PREFIXES                           := 11,
# TRIG_CRITERIA_N11                                := 12,
# TRIG_CRITERIA_AFR                                := 13,
# TRIG_CRITERIA_SHARED_IO_TRUNK                    := 14,
# TRIG_CRITERIA_TERMINATION_ATTEMPT                := 15,
# TRIG_CRITERIA_OFF_HOOK_IMMEDIATE                 := 16,
# TRIG_CRITERIA_OFF_HOOK_DELAY                     := 17,
# TRIG_CRITERIA_CHANNEL_SETUP_PRI                  := 18,
# TRIG_CRITERIA_NPA_N                              := 19,
# TRIG_CRITERIA_NPA_NX                             := 20,
# TRIG_CRITERIA_NPA_NXXX                           := 21,
# TRIG_CRITERIA_NPA_NXXXX                          := 22,
# TRIG_CRITERIA_NPA_NXXXXX                         := 23,
# TRIG_CRITERIA_NETWORK_BUSY                       := 24,
# TRIG_CRITERIA_T_NO_ANSWER                        := 25,
# TRIG_CRITERIA_T_BUSY                             := 26,
# TRIG_CRITERIA_O_CALLED_PARTY_BUSY                := 27,
# TRIG_CRITERIA_SPECIFIC_FEATURE_CODE              := 28,
# TRIG_CRITERIA_O_NO_ANSWER                        := 29,
# TRIG_CRITERIA_PRI_NETWORK_SERVICES               := 30,
# TRIG_CRITERIA_O_SWITCH_HOOK_FLASH_IMMEDIATE      := 31,
# TRIG_CRITERIA_O_FEATURE_ACTIVATOR                := 32,
# TRIG_CRITERIA_O_SWITCH_HOOK_FLASH_SPECIFIED_CODE := 33,
# TRIG_CRITERIA_T_SWITCH_HOOK_FLASH_IMMEDIATE      := 34,
# TRIG_CRITERIA_T_FEATURE_ACTIVATOR                := 35,
# TRIG_CRITERIA_T_SWITCH_HOOK_FLASH_SPECIFIED_CODE := 36,
# TRIG_CRITERIA_LOCAL_NUMBER_PORTABILITY           := 37,
# TRIG_CRITERIA_ONE_PLUS                           := 38,
# TRIG_CRITERIA_SPECIFIED_CARRIER                  := 39,
# TRIG_CRITERIA_INTERNATIONAL                      := 40,
# TRIG_CRITERIA_ZERO_PLUS                          := 41,
# TRIG_CRITERIA_ZERO_MINUS                         := 42,
# TRIG_CRITERIA_LOCAL_NUMBER_PORTABILITY_PORC      := 43,
# TRIG_CRITERIA_LOCAL_NUMBER_PORTABILITY_PORC_DONER:= 44,
#
# translationType Value
# INTEGER value loaded into TcapSccpCalledAddressData translationType field
#
# tcapBodyType Values
# TCAP_BODY_SEQUENCE                               := 1
# TCAP_BODY_SET                                    := 2
#
# gtSsn Values
# GTORSSN_ROUTE_BY_GT                              := 0
# GTORSSN_ROUTE_BY_SSN                             := 1
#
# dpcPres Values
# BOOLEAN flag 0 := TRUE, 1 := FALSE
#
# ssnPres Values
# BOOLEAN flag 0 := TRUE, 1 := FALSE
#
# dpcNetwork Values
# INTEGER
#
# dpcCluster Values
# INTEGER
#
# dpcMember Values
# INTEGER
#
# ssn Values
# INTEGER
#
# 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 3-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
#################
#
# componentType Values
# TCAP_COMPONENT_UNKNOWN                           := 0  (ANSI ONLY)
# TCAP_COMPONENT_INVOKE                            := 1  (ANSI & ITU)
# TCAP_COMPONENT_RETURN_RESULT                     := 2  (ANSI & ITU)
# TCAP_COMPONENT_RETURN_ERROR                      := 3  (ANSI & ITU)
# TCAP_COMPONENT_REJECT                            := 4  (ANSI & ITU)
# TCAP_COMPONENT_RETURN_RESULT_NOT_LAST            := 5  (ANSI ONLY)
# TCAP_COMPONENT_INVOKE_LAST                       := 6  (ANSI ONLY)
# TCAP_COMPONENT_INVOKE_NOT_LAST                   := 7  (ANSI ONLY)
#
# opClass Values
# OP_CLASS_1_SUCCESS_AND_FAIL_REPORTED             := 1
# OP_CLASS_2_ONLY_FAIL_REPORTED                    := 2
# OP_CLASS_3_ONLY_SUCCESS_REPORTED                 := 3
# OP_CLASS_4_NO_REPORTING                          := 4
#
# opCodeFamily Values
# ANSI_OP_FAMILY_NONE                              := 0
# ANSI_OP_FAMILY_REQUEST                           := 100
# ANSI_OP_FAMILY_CONNECTION_CONTROL                := 101
# ANSI_OP_FAMILY_CALLER_INTERACTION                := 102
# ANSI_OP_FAMILY_STATUS_NOTIFICATION               := 103
# ANSI_OP_FAMILY_INFORMATION_REVISION              := 104
# ANSI_OP_FAMILY_NETWORK_MANAGEMENT                := 105
# ANSI_OP_FAMILY_CONNECTIVITY_CONTROL              := 106
# ANSI_OP_FAMILY_ABNORMAL_REPORT                   := 111
#
# opCodeSpecifier Values
# --//ANSI Pre AIN
# ANSI_PRE_AIN_OP_FAMILY_PARAMETER                 := 1,
# ANSI_PRE_AIN_OP_FAMILY_CHARGING                  := 2,
# ANSI_PRE_AIN_OP_FAMILY_PROVIDE_INSTRUCTIONS      := 3,
# ANSI_PRE_AIN_OP_FAMILY_CONNECTION_CONTROL        := 4,
# ANSI_PRE_AIN_OP_FAMILY_CALLET_INTERACTION        := 5,
# ANSI_PRE_AIN_OP_FAMILY_SEND_NOTIFICATION         := 6,
# ANSI_PRE_AIN_OP_FAMILY_NETWORK_MANAGEMENT        := 7,
# ANSI_PRE_AIN_OP_FAMILY_PROCEDURAL                := 8,
# ANSI_PRE_AIN_OP_FAMILY_OPERATION_CONTROL         := 9,
# ANSI_PRE_AIN_OP_FAMILY_REPORT_EVENT              := 10,
# ANSI_PRE_AIN_OP_FAMILY_MISCELLANEOUS             := 126,
#
# --//ITU Op Codes
# --//ETS 300 374-1 Page 55
# ITU_OP_SPEC_INITIAL_DP                           := 0
# ITU_OP_SPEC_ASSIST_REQUEST_INSTRUCTIONS          := 16
# ITU_OP_SPEC_ESTABLIST_TEMPORARY_CONNECTION       := 17
# ITU_OP_SPEC_DISCONECT_FORWARD_CONNECTION         := 18
# ITU_OP_SPEC_CONNECT_TO_RESOURCE                  := 19
# ITU_OP_SPEC_CONNECT                              := 20
# ITU_OP_SPEC_RELEASE_CALL                         := 22
# ITU_OP_SPEC_REQUEST_REPORT_BCSM_EVENT            := 23
# ITU_OP_SPEC_EVENT_REPORT_BCSM                    := 24
# ITU_OP_SPEC_REQUEST_NOTIFICATION_CHARGING_EVENT  := 25
# ITU_OP_SPEC_EVENT_NOTIFICATION_CHARGING          := 26
# ITU_OP_SPEC_COLLECT_INFORMATION                  := 27
# ITU_OP_SPEC_CONTINUE                             := 31
# ITU_OP_SPEC_INITIATE_CALL_ATTEMPT                := 32
# ITU_OP_SPEC_RESET_TIMER                          := 33
# ITU_OP_SPEC_FURNISH_CHARGING_INFORMATION         := 34
# ITU_OP_SPEC_APPLY_CHARGING                       := 35
# ITU_OP_SPEC_APPLY_CHARGING_REPORT                := 36
# ITU_OP_SPEC_CALL_GAP                             := 41
# ITU_OP_SPEC_ACTIVATE_SERVICE_FILTERING           := 42
# ITU_OP_SPEC_SERVICE_FILTERING_RESPONSE           := 43
# ITU_OP_SPEC_CALL_INFORMATION_REPORT              := 44
# ITU_OP_SPEC_CALL_INFORMATION_REQUEST             := 45
# ITU_OP_SPEC_SEND_CHARGING_INFORMATION            := 46
# ITU_OP_SPEC_PLAY_ANNOUNCEMENT                    := 47
# ITU_OP_SPEC_PROMPT_AND_COLLECT_USER_INFORMATION  := 48
# ITU_OP_SPEC_SPECIALIZED_RESOURCE_REPORT          := 49
# ITU_OP_SPEC_CANCEL                               := 53
# ITU_OP_SPEC_ACTIVITY_TEST                        := 55
# --//ANSI Op Codes
# --//OP_FAMILY_REQUEST
# ANSI_OP_SPEC_INFO_ANALYZED                       := 3
# ANSI_OP_SPEC_INFO_COLLECTED                      := 2
# ANSI_OP_SPEC_NETWORK_BUSY                        := 23
# ANSI_OP_SPEC_ORIGINATION_ATTEMPT                 := 24
# ANSI_OP_SPEC_TERMINATION_ATTEMPT_ATTEMPT         := 5
# --//OP_FAMILY_CONNECTION_CONTROL
# ANSI_OP_SPEC_ANALYZE_ROUTE                       := 1
# ANSI_OP_SPEC_AUTHORIZE_TERMINATION               := 2
# ANSI_OP_SPEC_CONTINUE                            := 13
# ANSI_OP_SPEC_DISCONNECT                          := 3
# --//OP_FAMILY_CALLER_INTERACTION
# ANSI_OP_SPEC_CANCEL_RESOURCE_EVENT               := 3
# ANSI_OP_SPEC_RESOURCE_CLEAR                      := 2
# ANSI_OP_SPEC_SEND_TO_RESOURCE                    := 1
# --//OP_FAMILY_STATUS_NOTIFICATION
# ANSI_OP_SPEC_MONITOR_FOR_CHANGE                  := 1
# ANSI_OP_SPEC_MONITOR_SUCCESS                     := 3
# ANSI_OP_SPEC_SEND_NOTIFICATION                   := 5
# ANSI_OP_SPEC_STATUS_REPORTED                     := 2
# ANSI_OP_SPEC_TERMINATION_NOTIFICATION            := 4
# --//OP_FAMILY_INFORMATION_REVISION
# ANSI_OP_SPEC_UPDATE_REQUEST                      := 1
# --//OP_FAMILY_NETWORK_MANAGEMENT
# ANSI_OP_SPEC_ACG                                 := 1
# --//OP_FAMILY_CONNECTIVITY_CONTROL
# ANSI_OP_SPEC_FORWARD_CALL                        := 1
# --//OP_FAMILY_ABNORMAL_REPORT
# ANSI_OP_SPEC_REPORT_ERROR                        := 1
#
# opCodeFlag Values
# OP_FLAG_NONE                                     := 0
# OP_FLAG_LOCAL                                    := 1
# OP_FLAG_GLOBAL                                   := 2
# OP_FLAG_NATIONAL                                 := 3
# OP_FLAG_PRIVATE                                  := 4
#
# correlationRequired Values
# BOOLEAN flag 0 := TRUE, 1 := FALSE
#
# 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
#################
# PAn Values
# LAST_PARAMETER                                   := 0
# ANSI_PRE_AIN_ASN1_CALLED_PARTY_NUMBER            := 001,
# ANSI_PRE_AIN_ASN1_CALLING_PARTY_NUMBER           := 002,
# ANSI_PRE_AIN_ASN1_CALLER_INTERACTION             := 003,
# ANSI_PRE_AIN_ASN1_ROUTING_NUMBER                 := 004,
# ANSI_PRE_AIN_ASN1_BILLING_NUMBER                 := 005,
# ANSI_PRE_AIN_ASN1_DESTINATION_NUMBER             := 006,
# ANSI_PRE_AIN_ASN1_LATA                           := 007,
# ANSI_PRE_AIN_ASN1_CARRIER                        := 008,
# ANSI_PRE_AIN_ASN1_LAST_CALLING_PARTY             := 009,
# ANSI_PRE_AIN_ASN1_LAST_PARTY_CALLED              := 010,
# ANSI_PRE_AIN_ASN1_CALLING_DIRECTORY_NUMBER       := 011,
# ANSI_PRE_AIN_ASN1_VMSR_IDENTIFIER                := 012,
# ANSI_PRE_AIN_ASN1_ORIGINAL_CALLED_NUMBER         := 013,
# ANSI_PRE_AIN_ASN1_REDIRECTING_NUMBER             := 014,
# ANSI_PRE_AIN_ASN1_CONNECTED_NUMBER               := 015,
# ANSI_PRE_AIN_ASN1_ORIGINATING_STATION_TYPE       := 016,
# ANSI_PRE_AIN_ASN1_SERVICE_KEY                    := 017,
# ANSI_PRE_AIN_ASN1_BILLING_INDICATORS             := 018,
# ANSI_PRE_AIN_ASN1_ACG_INDICATORS                 := 019,
# ANSI_PRE_AIN_ASN1_ECHO_DATA                      := 020,
# ANSI_PRE_AIN_ASN1_TERMINATION_INDICATORS         := 021,
# ANSI_PRE_AIN_ASN1_CONNECT_TIME                   := 022,
# ANSI_ASN1_USER_ID                                := 100
# ANSI_ASN1_BEAR_CAP                               := 101
# ANSI_ASN1_CALLED_PARTY_ID                        := 102
# ANSI_ASN1_TRIGGER_CRITERIA_TYPE                  := 103
# ANSI_ASN1_CALLING_PARTY_ID                       := 104
# ANSI_ASN1_ECHO_DATA                              := 105
# ANSI_ASN1_TERMINATION_INDICATORS                 := 106
# ANSI_ASN1_CONNECT_TIME                           := 107
# ANSI_ASN1_BUSY_CAUSE                             := 108
# ANSI_ASN1_CHARGE_NUMBER                          := 109
# ANSI_ASN1_PRIMARY_CARRIER                        := 110
# ANSI_ASN1_ORIGINAL_CALLED_NUMBER                 := 111
# ANSI_ASN1_REDIRECTING_INFORMATION                := 112
# ANSI_ASN1_CHARGE_PARTY_STATION_TYPE              := 113
# ANSI_ASN1_AMA_LINE_NUMBER                        := 114
# ANSI_ASN1_AMA_SLP_ID                             := 115
# ITU_ASN1_SERVICE_KEY                             := 200
# ITU_ASN1_CALLED_PARTY_NUMBER                     := 201
# ITU_ASN1_CALLING_PARTY_NUMBER                    := 202
# ITU_ASN1_CALLING_PARTY_BUSINESS_GROUP            := 203
# ITU_ASN1_EXTENSIONS                              := 204
# ITU_ASN1_DESTINATION_ROUTING_ADDRESS             := 205
# ITU_ASN1_ORIGINAL_CALLED_PARTY                   := 206
# ITU_ASN1_SERVICE_INDICATORS                      := 207
#
# REQuired Values
# FALSE := 0
# TRUE  := 1
#
# 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
#################
# All fields are pointers to records of other types
#
# 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
#################
# See message sending table for MSG field values
#
# OPerationReceived Values
# Pointer to OperationReceiving record
#
# REQuired Values
# FALSE := 0
# TRUE  := 1
#
# 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
###################
# See OperationSending table for field values
#
# 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
###################
# PAn Values
# LAST_PARAMETER                                   := 0
# ANSI_PRE_AIN_ASN1_CALLED_PARTY_NUMBER            := 001,
# ANSI_PRE_AIN_ASN1_CALLING_PARTY_NUMBER           := 002,
# ANSI_PRE_AIN_ASN1_CALLER_INTERACTION             := 003,
# ANSI_PRE_AIN_ASN1_ROUTING_NUMBER                 := 004,
# ANSI_PRE_AIN_ASN1_BILLING_NUMBER                 := 005,
# ANSI_PRE_AIN_ASN1_DESTINATION_NUMBER             := 006,
# ANSI_PRE_AIN_ASN1_LATA                           := 007,
# ANSI_PRE_AIN_ASN1_CARRIER                        := 008,
# ANSI_PRE_AIN_ASN1_LAST_CALLING_PARTY             := 009,
# ANSI_PRE_AIN_ASN1_LAST_PARTY_CALLED              := 010,
# ANSI_PRE_AIN_ASN1_CALLING_DIRECTORY_NUMBER       := 011,
# ANSI_PRE_AIN_ASN1_VMSR_IDENTIFIER                := 012,
# ANSI_PRE_AIN_ASN1_ORIGINAL_CALLED_NUMBER         := 013,
# ANSI_PRE_AIN_ASN1_REDIRECTING_NUMBER             := 014,
# ANSI_PRE_AIN_ASN1_CONNECTED_NUMBER               := 015,
# ANSI_PRE_AIN_ASN1_ORIGINATING_STATION_TYPE       := 016,
# ANSI_PRE_AIN_ASN1_SERVICE_KEY                    := 017,
# ANSI_PRE_AIN_ASN1_BILLING_INDICATORS             := 018,
# ANSI_PRE_AIN_ASN1_ACG_INDICATORS                 := 019,
# ANSI_PRE_AIN_ASN1_ECHO_DATA                      := 020,
# ANSI_PRE_AIN_ASN1_TERMINATION_INDICATORS         := 021,
# ANSI_PRE_AIN_ASN1_CONNECT_TIME                   := 022,
# ANSI_ASN1_USER_ID                                := 100
# ANSI_ASN1_BEAR_CAP                               := 101
# ANSI_ASN1_CALLED_PARTY_ID                        := 102
# ANSI_ASN1_TRIGGER_CRITERIA_TYPE                  := 103
# ANSI_ASN1_CALLING_PARTY_ID                       := 104
# ANSI_ASN1_ECHO_DATA                              := 105
# ANSI_ASN1_TERMINATION_INDICATORS                 := 106
# ANSI_ASN1_CONNECT_TIME                           := 107
# ANSI_ASN1_BUSY_CAUSE                             := 108
# ANSI_ASN1_CHARGE_NUMBER                          := 109
# ANSI_ASN1_PRIMARY_CARRIER                        := 110
# ANSI_ASN1_ORIGINAL_CALLED_NUMBER                 := 111
# ANSI_ASN1_REDIRECTING_INFORMATION                := 112
# ANSI_ASN1_CHARGE_PARTY_STATION_TYPE              := 113
# ANSI_ASN1_AMA_LINE_NUMBER                        := 114
# ANSI_ASN1_AMA_SLP_ID                             := 115
# ITU_ASN1_SERVICE_KEY                             := 200
# ITU_ASN1_CALLED_PARTY_NUMBER                     := 201
# ITU_ASN1_CALLING_PARTY_NUMBER                    := 202
# ITU_ASN1_CALLING_PARTY_BUSINESS_GROUP            := 203
# ITU_ASN1_EXTENSIONS                              := 204
# ITU_ASN1_DESTINATION_ROUTING_ADDRESS             := 205
# ITU_ASN1_ORIGINAL_CALLED_PARTY                   := 206
# ITU_ASN1_SERVICE_INDICATORS                      := 207
#
# REQuired Values
# FALSE := 0
# TRUE  := 1
#
# ACTn Values
# PARAM_ACTION_NONE                                := 0
# PARAM_ACTION_COPY_TO_SIGNAL_DATA                 := 1
# PARAM_ACTION_COPY_TO_CC                          := 2
# PARAM_ACTION_COPY_TO_CC_BILLED_CUST_ID           := 3
# PARAM_ACTION_SAVE_ECHO_DATA                      := 4
#
# 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
###############
# ACTn Values
# RESULT_ACTION_NONE (Last Action)                 := 0
# RESULT_ACTION_SET_LNP_M_BIT                      := 1
# RESULT_ACTION_RE_TRIGGER_VIA_LCM                 := 2
# RESULT_ACTION_RE_TRIGGER_NOW                     := 3
# RESULT_ACTION_SEND_ACTION_TO_LCM                 := 4
#
# REQuired Values
# FALSE := 0
# TRUE  := 1
#
# 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
###########
#
# PointInCallEnum from signal_defs_x.inc
# PIC_CALL_START                                   := 1
# PIC_START_CALLING                                := 2
# PIC_START_CALLING_ACK                            := 3
# PIC_CALLING                                      := 4
# PIC_CALL_PROCEEDING                              := 5
# PIC_ALERTING                                     := 6
# PIC_ANSWERED                                     := 7
# PIC_SUSPEND                                      := 8
# PIC_RESUME                                       := 9
# PIC_RELEASE_START_ORIG                           := 10
# PIC_RELEASE_START_TERM                           := 11
# PIC_RELEASE_START_LCM                            := 12
# PIC_RELEASE_CONTINUE                             := 13
# PIC_RELEASE_END                                  := 14
# PIC_CALL_END                                     := 15
#
#
# LCM Action INserviceEnum from signal_defs_x.inc
# IN_NONE                      := 0 #Sent to LCM from IN_TRIGGER if no other value is set
# IN_LNP                                           := 1
# IN_800                                           := 2
#
#
# 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 of the Preface.

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:

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 to 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 committing or deploying 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 backup and move over the data 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 "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 the example below, 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 will fail.

Example 3-8: 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 below, 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 will fail.

Example 3-9: 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 "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 below, 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 will fail.

Example 3-10: 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 the database replication is working. See "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, as follows:

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 installation. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface. If you do not need to install or remove patches or install the CMM on a separate host, continue to "Configuring the Cisco Signaling Link Terminal," for Cisco SLT configuration information.

Installing and Removing Release 7.4(x) Patches Manually

This section contains general instructions for manually installing and removing Cisco MGC software patches. Automatic installation performs patch removal and installation for you. However, should you need to perform these procedures manually, these instructions tell you how.

This section contains the following topics:

Note See Release Notes for the Cisco Media Gateway Controller Software Release 7 for specific patch information.

Installing Patches

To install a patch, complete the following steps:

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

Step 2 To stop the software, enter the following command:

# /etc/init.d/CiscoMGC stop

Step 3 Change to the directory where the patches are located:

If the patch is on a CD, insert the Cisco MGC software CD into the CD-ROM drive and change to the directory where the patches are located.
If you downloaded the patches using FTP, change to the directory where the patches are located.

Step 4 To install the package file, type the following command and press Enter:

# pkgadd -d package name

Step 5 Follow the onscreen prompts to install the applicable patches.

This completes the patch installation.

If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.

Removing Patches

Note Uninstalling a Cisco MGC software release automatically removes all patch packages. Manual removal of patches should not normally be necessary.

To remove a patch, complete the following steps:

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

Step 2 To stop the software, enter the following command:

# /etc/init.d/CiscoMGC stop

Step 3 To remove the package file, enter the following command:

# pkgrm package name

This completes the patch removal. Unless you need to perform the steps in the "Installing the Cisco Media Gateway Controller Manager Software on a Separate Host" section, continue to "Cisco Signaling Link Terminal Command Reference." If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.

Installing the Cisco Media Gateway Controller Manager Software on a Separate Host

You can install the CMM package on a different host. To install the CMM software separately from the main Cisco MGC software, perform the following steps:

Step 1 Insert the Cisco MGC software CD into a CD-ROM drive on the host.

Step 2 Navigate to the CD-ROM's drive by typing each of the following commands and pressing Enter:

cd /cdrom/cdrom0

Step 3 Type the following command and press Enter:

./install-cmm-tool.sh

The following response appears:

This script only installs the Cisco Configuration Manager (CMM) package
If you wish to install a full system please use 'install.sh' instead
 
Do you wish to proceed [y] [y,n,?,q]

Step 4 Type your response and press Enter:

The following text appears:

Processing package instance <CSCOga004> from </747c/APPLICATIONS/CSCOga004.pkg>
 
Cisco Media Gateway Controller Software Toolkit Applications
(sparc) 7.4(7)C
Cisco Systems, Inc.
 
Enter base directory path (default /opt/CMM) [?,q]

Step 5 Either type your base directory path and press Enter, or just press Enter to accept the default (recommended).

The following text appears:

:## Executing checkinstall script.
Using </opt/CMM> as the package base directory.
## Processing package information.
## Processing system information.
   2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
 
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
 
Do you want to continue with the installation of <CSCOga004> [y,n,?] y

Step 6 Type your response and press Enter:

The following message appears:

Installing Cisco Media Gateway Controller Software Toolkit Applications as
<CSC>
 
## Installing part 1 of 1.
/opt/CMM/bin/expect
/opt/CMM/bin/gunzip
/opt/CMM/mibs/measurement/measurement.my
/opt/CMM/mibs/provisioning/provisioning.my
/opt/CMM/mibs/snmpinfo.dat
/opt/CMM/mibs/tp/tp.my
[ verifying class <none> ]
Installing /opt/CMM/Packages/Packages.tar.gz
Installing /opt/CMM/bytecode/cdr/cdr.tar.gz
Installing /opt/CMM/bytecode/cmm/cmm.tar.gz
Installing /opt/CMM/bytecode/log/Viewer.tar.gz
Installing /opt/CMM/bytecode/toolbar/toolbar.tar.gz
Installing /opt/CMM/bytecode/tv/tv.tar.gz
Installing /opt/CMM/gif/gif.tar.gz
Installing /opt/CMM/mibs/common/common.tar.gz
Installing /opt/CMM/tcl/tcl.tar.gz
[ verifying class <archive> ]
Updating parameters for init.tcl
Updating parameters for start.sh
Updating parameters for version.dat
[ verifying class <relocate> ]
 
Installation of <CSCOga004> was successful.

This completes the CMM installation. If you have questions or need assistance, see the "Obtaining Technical Assistance" section of the Preface.

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

Table of Contents

Installing the Cisco Media Gateway Controller Software Release 7.4