Cisco Media Gateway Controller Software Installation and Configuration Guide (Releases 9.1 through 9.6)
XECfgParm.dat File Parameters
Downloads: This chapterpdf (PDF - 628.0KB) The complete bookPDF (PDF - 4.76MB) | Feedback

XECfgParm.dat File Parameters

Table Of Contents

XECfgParm.dat File Parameters

Understanding the XECfgParm.dat File Format

Cisco MGC XECfgParm.dat Files

Facility Names

Special Parameters

Cisco MGC 9.x XECfgParm.dat File Parameter Definitions


XECfgParm.dat File Parameters


This appendix describes the parameters found in the XECfgParm.dat file for the Cisco MGC software release 9.x and how they are used by the media gateway controller (MGC).

Understanding the XECfgParm.dat File Format

The XECfgParm.dat file contains system-wide as well as system tuning parameters. All fields in this file are written in the parm = value format. It supports a hash mark (#) in the first column to denote the entire line as a comment.

Parameters are prefixed with a quantifier to specify the domain of the parameter. An asterisk (*) preceding the parameter indicates that the parameter setting should be used by the entire system. A component name limits the scope to the specified component.

XECfgParm.dat parameters are arranged syntactically as follows:

facilityName.parameterName = parameterValue

Cisco MGC XECfgParm.dat Files

Facility Names

The following facility names are valid:

almM—Alarm Manager

amDmpr—Alarm / Measurement Dumper

cdrDmpr—CDR Dumper

CALL_CUTOFF_TIMER

cfgM—Configuration Manager

engine—Call processing engine

foverd—Failover Daemon

ioChanCtl—Controls all channel controllers

ioChanMgr—I/O Channel Managers

logger—Log Server

measM—Measurement Manager

mmdb—Main Memory Data Base Process

MML—MML

mmSAgt—Measurement Manager SNMP Agent

OPERSAGT—Operational SNMP Agent

pom—Provisioning Object Manager

procM—Process Manager

PROVSAGT—Provisioning SNMP Agent

replicator—Replicator

If no match is found for a facility-specific parameter, the file is searched for a match on the default facility.

Special Parameters

callver—Call verification utility

diskmonitor—Disk monitor shell script

XE—Execution environment

Cisco MGC 9.x XECfgParm.dat File Parameter Definitions

The XECfgParm.dat file configuration parameters for the Cisco MGC software release 9.x are presented alphabetically in Table A-1.


Caution This list of parameters is provided as a reference. Do not edit any parameters unless they are listed in the following table or unless you have been instructed to do so by Cisco technical support; otherwise, your system might not work as intended.

Table A-1 Cisco MGC 9.x XECfgParm.dat File Configuration Parameters 

Configuration Parameter
Definition

*.actiononchargetableaccessfailure

added in Release 9.5(2)

Allows you to specify the action to take when there is a failure to access the meter pulse tariff table.

Default: 0

Valid values: 0 (Continue Call) and 1 (Release Call).

*.AllISDNLinksFailCausesFailover

added in Release 9.5(2)

Controls the severity level of the All ISDN IP Conn Fail alarm.

Default: false

Valid values: false (alarm severity is Major) and true (alarm severity is Critical).

This property should be set to true if your Cisco MGC hosts are in separate geographic locations. You can also set this parameter to true if your system is not processing SS7 calls and you want your system to perform an automatic switchover should all of the ISDN IP connections fail.

*.AllLinksFailCausesFailover

added in Release 9.4(1)

Controls the severity level of the following alarms:

All C7IP Links Fail

All M3UA Assoc Fail

All SUA Assoc Fail

Default: false

Valid values: false (alarm severity is Major) and true (alarm severity is Critical).

This property should be set to true if your Cisco MGC hosts are in separate geographic locations. You can also set this parameter to true if your system is not processing SS7 calls and you want your system to perform an automatic switchover should all of the links fail.

*.autonomous

Enables a process, for example the engine, to be started without the system.

Default: false

Note Do not change this value.

*.chargingmode

added in Release 9.5(2)

Allows you to specify the charging mode for non-Intelligent Network (IN) calls which determines the treatment of received Metered Pulse Messages (MPMs).

Default: 1

Valid values are: 1 (AddOnCharge), 2 (ReplaceCharge), and 3 (FreeOfCharge).

*.chargingtarifftype

added in Release 9.5(2)

Allows you to specify which type of tariff table (Meter Pulse or Tariff-Rate/Scale-Factor) is to be accessed in the absence of a tariff table identifier in the charge result.

Default: 1

Valid values are: 0 (tariff-rate/scale-factor) (default) and 1 (meter pulse).

*.chkPtPort

Port number used between peer components or processes for check-pointing.

Value: Any unused port number.

Default: 2001

Leave this value as the default.

Note If you have two Cisco MGC hosts in a failover configuration, both fields in the XECfgParm.dat files should contain the same value.

*.ClearingLocation

Specifies whether to override the default location field in the call context for any call, regardless of which network device released the call. This enables you to define a default location in Release messages for any call, which can differ from the default location set in the type definition of the protocol.


Note This property has precedence over the value set in the *.DefaultLocation parameter.


Values:

0 = Normal mapping behavior, LCM will not override the Clearing Location field in Call Context.

1 = LCM will override the Clearing Location in Call Context with LOCATION_USER

2 = LCM will override the Clearing Location in Call Context with LOCATION_ PRIVATE_LOCAL

3 = LCM will override the Clearing Location in Call Context with LOCATION_ PUBLIC_LOCAL

4 = LCM will override the Clearing Location in Call Context with LOCATION_TRANSIT

5 = LCM will override the Clearing Location in Call Context with LOCATION_ PUBLIC_REMOTE

6 = LCM will override the Clearing Location in Call Context with LOCATION_ PRIVATE_REMOTE

7 = LCM will override the Clearing Location in Call Context with LOCATION_ INTERNATIONAL

8 = LCM will override the Clearing Location in Call Context with LOCATION_ INTERWORKING

9 = LCM will override the Clearing Location in Call Context with LOCATION_ LOCAL_INTERFACE

10 = LCM will override the Clearing Location in Call Context with LOCATION_ LOCAL_LOCAL

11 = LCM will override the Clearing Location in Call Context with LOCATION_ LOCAL_REMOTE

12 = LCM will override the Clearing Location in Call Context with LOCATION_ PACKET_MANAGER

13 = LCM will override the Clearing Location in Call Context with LOCATION_ UNKNOWN

Default: 0 (Normal mapping behavior)

Note Option 13 may not be valid for all solutions.

*.CPUTimerInterval

Samples the frequency of CPU utilization.

Prior to Release 9.4(1), this parameter must be set to 0 during the initial configuration of any platform with a single CPU (including Sun Netra t 100/105, Sun Netra V 120, and Sun Netra 120).

Default: 3000 msec (3 seconds)

Note During the startup of the Cisco MGC software, this parameter will be set automatically to tune the system for optimal performance.

For Release 9.4(1) and up, this parameter is set automatically when you specify a Cisco MGC type in the engine.SysVirtualSwitch parameter. Any attempt to modify this parameter is overwritten.

*.dataDir

Location of the data directory.

Default: ../var

Note Do not change this value.

*.dataSourceName

Used by the MMDB to obtain the data source name for the ODBC connection.

Default: howdydb

Note Do not change this value.

*.debugLevel

Determines level of debugging detail if debugging is initiated.

Default: high

Note Do not change this value.

*.DefaultLocation

Specifies whether to override the default location field in the call context for calls released by the Cisco MGC. This enables you to define a default location in Release messages for calls released by the Cisco MGC, which can differ from the default location set in the type definition of the protocol.


Note If the call is not released by the Cisco MGC, this property has no impact.


Values:

0 = Normal protocol-defined default value; LCM will not override the default location field in call context.

1 = LCM will override the default location in call context with LOCATION_USER

2 = LCM will override the default location in call context with LOCATION_ PRIVATE_LOCAL

3 = LCM will override the default location in call context with LOCATION_ PUBLIC_LOCAL

4 = LCM will override the default location in call context with LOCATION_TRANSIT

5 = LCM will override the default location in call context with LOCATION_ PUBLIC_REMOTE

6 = LCM will override the default location in call context with LOCATION_ PRIVATE_REMOTE

7 = LCM will override the default location in call context with LOCATION_ INTERNATIONAL

8 = LCM will override the default location in call context with LOCATION_ INTERWORKING

9 = LCM will override the default location in call context with LOCATION_ LOCAL_INTERFACE

10 = LCM will override the default location in call context with LOCATION_ LOCAL_LOCAL

11 = LCM will override the default location in call context with LOCATION_ LOCAL_REMOTE

12 = LCM will override the default location in call context with LOCATION_ PACKET_MANAGER

13 = LCM will override the default location in call context with LOCATION_ UNKNOWN

Default: 0 (Normal protocol-defined default value)

Note Option 13 may not be valid for all solutions.

*.desiredPlatformState

Determines the desired platform state.

Values:

master, if you have two (active and standby) Cisco MGC hosts

slave, if you have two (active and standby) Cisco MGC hosts

standalone, if you have a single-host system

Default: none

Note The value used is site specific. For example, use the values master and slave if you have two (active and standby) Cisco MGC hosts. Enter standalone if you have a single-host system.

*.disableMeas

Disables the collection of measurement data.

Values:

true = disables data collection

false = data is collected

Default: false

*.disablemultiplecdrs

added in Release 9.5(2)

Allows you to disable the multiple-CDRs-per-call (for example, multiple occurrences of Answer and Release CDB messages) for situations where the downstream billing system does not support this feature.

Default: 1

Valid values are: 0 (multi CDRs enabled) and 1 (multi CDRs disabled).

*.eventTrace

Used by developers only to trace events at the application level.

*.FastConnect

Allows LCM messages to pass through.

Values:

0 = Passes all signals to LCM

1 = Disables signal to LCM for "CallProceeding" received from NAS

2 = Disables signal to LCM for "CallProceeding" or "Progress" received from NAS

3 = Disables signal to LCM for "Call Proceeding", "Progress", or "Alerting" received from NAS.

*.GWClearChannelAlgorithm

Allows the use of the clear channel 64K unrestricted data transfer between gateways. Different gateways support different codecs. There is a command to see all the codecs supported on the gateway, including the clear channel codec.

For example on VISM, the command is dspcodecparams. PGW will pass any string that is defined on it. The following is what the command shows on VISM:

Codec Codec String Period (ms) Preference Type
1 - G.711u PCMU 10 8 0
2 - G.711a PCMA 10 7 8
3 - G.726-32K G726-32 10 5 2
4 - G.729a G729a 10 2 96
5 - G.729ab G729ab 10 1 96
6 - clr chan CCD 10 9 96
7 - G.726-16K G726-16 10 3 96
8 - G.726-24K G726-24 10 4 96
9 - G.726-40K G726-40 10 6 96
11 - G.723.1- G723H 30 10 96
12 - G.723.1a G723AH 30 11 96
13 - G.723.1- G723L 30 12 96
14 - G.723.1a G723AL 30 13 96

Values: null or the valid codec string

Default: null

*.homeDirRoot

Location of the home directory.

Default: /opt/CiscoMGC

Note Do not change this value.

*.ioChanMgr.IPCTimer

added in Release 9.5(2)

Specifies the frequency at which the queue is scanned for RSIP messages. When this parameter is left at its default value (0), the system uses a base parameter value. You can modify this parameter if a problem occurs.

Valid values: Any integer

Default value: 0

*.IP_Addr1

IP address of interface 1; used for signaling.

*.IP_Addr2

IP address of interface 2; used for signaling.

*.IP_Addr3

IP address of interface 3 (if installed); used for signaling.

*.IP_Addr4

IP address of interface 4 (if installed); used for signaling.

*.ipAddrLocalA

First local IP address; used for checkpointing and failover heartbeats if you have active/standby MGC hosts.

Note This is typically the same value as *.IP_Addr1.

*.ipAddrLocalB

Second local IP address; used for checkpointing and failover heartbeats if you have active/standby MGC hosts.

Note If your configuration does not use an external card, leave this setting as the default value: 0.0.0.0.

*.ipAddrPeerA

First corresponding peer IP address; used for checkpointing and failover heartbeats.

Note If you have two Cisco MGC hosts in a failover configuration, this value is the IP address of the second host.

*.ipAddrPeerB

Second corresponding peer IP address; used for checkpointing and failover heartbeats.

Note If your configuration does not use an external card, leave this setting as the default value, 0.0.0.0.

*.IP_NextHop1
*.IP_NextHop2
*.IP_NextHop3
*.IP_NextHop4
*.IP_NextHop5
*.IP_NextHop6
*.IP_NextHop7
*.IP_NextHop8

added in Release 9.4(1)

Specifies the IP addresses of up to eight next hop counters. These IP addresses are used when the next hop router IP addresses on the Cisco PGW hosts do not match.

Default: 0.0.0.0

Valid values: An IP address expressed in dotted decimal notation.

*.IUA.maxNasExtNodes

added in Release 9.4(1)

Specifies the maximum number of external nodes that can be defined with an ISDN signaling type of IUA. This number also represents the maximum number of IUA associations that can be provisioned.

Valid value: 256


Note Do not change this value.


*.IUA.maxNasPathsPerExtNode

added in Release 9.4(1)

Specifies the maximum number of NAS signaling services that can be assigned to each external node with an ISDN signaling type of IUA.

Valid value: 112


Note Do not change this value.


*.IUA.maxNasPaths

added in Release 9.4(1)

Specifies the maximum number of IUA signaling services that can be provisioned.

Valid value:1500


Note Do not change this value.


*.LISupport

added in Release 9.5(2)

Enables Cisco PGW 2200 to be used for Lawful Intercept.

Note Set this parameter to true to enable Cisco PGW 2200 support for Lawful Intercept.

Default: false

*.logDirectory

Location of the active and rotated log files.

Default: ../var/log

Note Make sure the log file has write permission for the LogServer.

*.logFileNamePrefix

Combined with the .log extension, defines the filename for log files.

Default: platform

Example: engine

Note This setting can also redirect process messages from the default log file to a specified log file. For example, engine.logFileNamePrefix = engine instructs the log server to redirect messages from the engine process to the dedicated engine.log file. This functions with or without *.logDirectory.

*.logMsgDrop

Controls whether the log server drops debug-level messages when the UNIX domain socket used for log server communication is full.

Values:

true = debug messages are dropped

false = debug messages are not dropped

Default: true


Caution If you set this parameter to false for the engine and the engine logging level is Debug, the system can fail at high call rates.

*.logPrio

Defines the initial default logging level used by logging clients when sending messages to the logging server. Use the set-log MML command to change logging levels after installation. You can specify different logging levels for each process. For example, engine.logPrio = Info

Note This setting is the only way to modify the logging level of the current MML process. The set-log command does not affect current MML process logging levels.

This parameter provides debug level LogPrio support in XECfgParm.dat for individual channel controllers. You can use the following to turn on IOCC logging:

SS7.logPrio = Debug

EISUP.logPrio = Debug

MGCP.logPrio = Debug

ISDNIP.logPrio = Debug

ISDNL3.logPrio = Debug

SIP.logPrio = Debug

TALI.logPrio = Debug

TCAP.logPrio = Debug


Caution Be sure to use the actual process name, not the MML name, of the channel controller. Note that the IOCC name is case-sensitive.

Values:

Debug—Used only for detailed debugging messages. Logging at this priority is not recommended during production because this causes a large volume of messages to be logged, which degrades system performance and can cause failover problems.

Trace—These messages capture protocol traffic. This priority is used for debugging.

Info—These messages indicate an operation that is proceeding as expected.

Warning—These messages indicate a problem exists that does not prevent the system from operating. This is the normal, default logging level for production.

Error—These messages indicate an unexpected error that is recoverable but degrades performance.

*.logPrio (continued)

Critical—These messages indicate errors so severe that a process cannot continue operating.

Default (Release 7.3 & earlier): Warning

Default (Release 7.4 & later): Error

Note Do not change this value unless you are debugging.

*.LongCallTime

Used to generate ongoing Call Data Block (CDB) 1060. CDB 1060 (on-going call event) indicates a long call in progress.

Default: 21600000 milliseconds (6 hours)

Minimum value required: 60000 milliseconds (60 seconds)

Note Typically, you should leave the value 21600000 milliseconds (6 hours) as the default. You can change it, if necessary, based on billing requirements.

If you enter a value less than the required minimum of 60000 milliseconds, it defaults to 6 hours.

*.M3UA.maxSigServices

added in Release 9.4(1)

Defines the maximum number of M3UA signaling services. It also defines the maximum number of M3UA routing keys.

Value: 1536


Note Do not change this value.


*.M3UA.maxOPCs

added in Release 9.4(1)

Defines the maximum number of M3UA OPCs.

Value: 64


Note Do not change this value.


*.M3UA.maxRoutesPerOpcDpc

added in Release 9.4(1)

Defines the maximum number of M3UA routes per OPC/DPC pair.

Value: 2


Note Do not change this value.


*.M3UA.maxSgp

added in Release 9.4(1)

Defines the maximum number of M3UA SS7 signaling gateway processes.

Value: 96


Note Do not change this value.


*.maxLinksPerSessionSet

Sets the maximum number of SS7 links contained in a session set. This is based on the maximum number of SS7 links in an SLT.

Value: 4

Default: 4

Note Do not change this value.

*.maxLocationLabels

added in Release 9.6(1)

Specifies the maximum number of location labels that can be provisioned.

Valid value: 3000

Note Do not change this value.

*.maxNumDChansPerPort

added in Release 9.5(2)

Specifies the maximum number of D-channels that can be provisioned per IP address or port.

Valid values: Any integer (1 to 2000)

Default value: 2000

*.maxnumRLMports

Used during provisioning to verify that the limit on the number of unique ports for RLM links is not exceeded.

Value: 8

Default: 8

*.MgcpBehavior

Due to MGCP gateway differences in return codes, the PGW2200 MGCPBehavior must be configured to the appropriate value in order to properly interface with the gateway.

Value range: Integer

0—No action.

Do not use this value for switched solutions.

Do not change this value for nailed solutions.

1—Value for non-IOS-based MGCP gateways such as VISM.

2—Value for IOS-based gateways such as AS5300, AS5400, and AS5350s.

Default : 0

*.numberOfThreads

Prior to Release 9.4(1), the number of threads generated by multithreaded processes such as the engine and the log master, is specified by entering one of the following values:

Values:

0 = single CPU

1 = two CPUs

2 = four CPUs

Default: 0

Note If you have a multi-CPU system (1 or 2), you must set engine.SysGeneratedCode to true.

Note During the startup of the Cisco MGC software, this parameter will be set automatically to tune the system for optimal performance.

For Release 9.4(1) and up, this parameter is set automatically when you specify a Cisco MGC type in the engine.SysVirtualSwitch parameter. Any attempt to modify this parameter is overwritten.

*.OverdecadicDigitsSupported

This parameter controls the method of loading dial plan tables and instructs the system whether to expect overdecadic (base 16) or regular decadic (base 10) digits in dial plans, routing, and other digit streams.

Correct setting of this parameter depends on local network interconnect agreements and the expected data format.

Enter true to use overdecadic digits (0-F).

*.OwnClli

Common language location identifier; used for circuit query validation when circuit queries are supported.

Value: Alphanumeric string, up to 11 characters.

Default: TTTT-SS-BB-XXX

Example: 1111-22-33-444

*.PartialCliPnoIdentity

added in Release 9.5(2)

Contains a 3-digit integer representing the PNO Identity field of the partial CLI parameter.

Valid values: 0 (default) through 999

*.PartialCliSwitchNumber

added in Release 9.5(2)

Contains a 3-digit integer representing the Switch Number field of the partial CLI parameter.

Valid values: 0 (default) through 999

*.PartialCliTypeOfSwitch

added in Release 9.5(2)

Contains a 2-digit integer representing the Type of Switch field of the partial CLI parameter.

Valid values: 0 (default) through 99

*.platformId

Enables the signaling controller to run more than one instance of the Cisco MGC software concurrently.

Default: 1

Note Do not change this value.

*.popDataSync

Specify true if master/slave mode is being used.

*.RedirectingATree

Used to control A-number screening/analysis via A-digit tree. This parameter allows the analysis system to use the A-Digit tree for mapping to the BLACKLIST function on the Redirecting CLI value. It uses the A-Digit tree to allow for black screening on the redirecting number parameter included in the IAM.

Currently, when the parameter MDLANumberScreening is set to 1 in the XECfgParm.dat file, screening is done on the redirecting number. This works when screening individual numbers but does not allow block ranges to be screened, as is the case when using DialPlan Screening in the Digit Tree functions.

Use an editor such as vi to manually add the *.RedirectingATree parameter to the XECfgParm.dat file in the following file locations and set its value:

/opt/CiscoMGC/etc/XECfgParm.dat

/opt/CiscoMGC/etc/CONFIG_LIB/new/XECfgParm.dat

Valid values:

0 = Default. Indicates the Calling Party Number (CGPN) that will be used for A-number screening/analysis via A-digit tree.

1 = Indicates that the Redirecting Number should be used for A-number screening/analysis via A-digit tree if the incoming signaling message contains both the CPN and Redirecting Number or just the Redirecting Number.

Note This property is only effective when BLACKLIST is provisioned. If Screening is data filled and this property is set to 1, then Redirecting Number is used for screening. However, if result types other than BLACKLIST/SCREENING are encountered when Redirecting Number is used during A-number Tree Analysis, an alarm RedirectingNbrFail (informational alarm) is generated.

*.SelectTermCustGrpId

Applies only to Nailed Solutions. If this parameter is not defined, it defaults to False.

If this parameter is set to True and CUSTGRPID of the Originating Leg SigPath is 0000, then you must select CUSTGRPID of the Terminating Leg SigPath.

If this parameter is set to False, you should always select CUSTGRPID of the Originating Leg SigPath.

Default: False

*.sipFailover

added in Release 9.4(1)

Specifies whether the MGC hosts, when connected with a SIP network, should perform an automatic switchover when a LAN interface fails.

Default: false

Valid values: true or false

*.sm_meas_baseaddr

Indicates the memory size of the base address.

Default: 3400

Note Do not change this value.

*.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 failover configuration, enter a different number for this value in the XECfgParm.dat file on the secondary host (for example, 7001).

Note On a new configuration, we recommend that this parameter be set to 0. This value allows the SLT port to be defined using the PEERPORT parameter of the SESSIONSET.

Note SESSIONSET reads the port value that is defined. However, if an *.stPort value other than 0 is defined in XECfgParm.dat (for example, *.stPort=7001), the SESSIONSET value gets overridden by the value in XECfgParm.dat.

*.SUA.maxSigServices

added in Release 9.4(1)

Defines the maximum number of SUA signaling services. It also defines the maximum number of SUA routing keys.

Value: 256


Note Do not change this value.


*.SUA.maxOPCs

added in Release 9.4(1)

Defines the maximum number of SUA OPCs.

Value: 64


Note Do not change this value.


*.SUA.maxRoutesPerOpcApcSsn

added in Release 9.4(1)

Defines the maximum number of SUA routes per OPC, APC, and SSN set.

Value: 2


Note Do not change this value.


*.SUA.maxSgp

added in Release 9.4(1)

Defines the maximum number of SUA SS7 signaling gateway processes.

Values: 8


Note Do not change this value.


*.SyscheckpointEnabled

Note This parameter does not apply to Release 9.3(x).

Enables or disables checkpointing.

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.

Default: false

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

*.SysConnectDataAccess

Controls whether data access is enabled or disabled (if the engine attempts to connect to the MMDB or to call screening database at startup).

Values:

true = connect to MMDB or call screening database

false = do not connect to MMDB or call screening database

Default: false

Note This parameter must be set to true in calling scenarios where Euro-LNP, A Number Screening, or other features requiring real time database access are required. Otherwise, it can remain false for an increase in the available system memory usable for call processing.

Note This parameter replaces the engine.sysScreeningCheck parameter in Cisco MGC 7.4.

*.tablesFile

Location of the database directories.

Default: ../etc/tables.dat

Note Do not change this value.

*.tempDir

Location of the temporary files.

Default: /tmp

Note Do not change this value.

*.tibcoSupport

added in Release 9.5(2)

Determines whether or not the system supports a TIBCO maintenance interface.

Default: disable

Valid values: enable or disable

*.transpathId

Identifies the local Cisco MGC host in a redundant configuration. The IDs must be unique in an active and standby pair.

Value: Any integer up to 2 digits.

Default (for the active host): 01

Note If you have two Cisco MGC hosts in a failover configuration, the number for each host must be different in the XECfgParm.dat file.

*.Virtual_IP_Addr1

added in Release 9.4(1)

Specifies a virtual IP address for a LAN interface. This IP address must be within the subset of the IP address defined for *.IP_Addr1.

Default: 0.0.0.0

Valid values: An IP address expressed in dotted decimal notation.

*.Virtual_IP_Addr2

added in Release 9.4(1)

Specifies a virtual IP address for a LAN interface. This IP address must be within the subset of the IP address defined for *.IP_Addr2.

Default: 0.0.0.0

Valid values: An IP address expressed in dotted decimal notation.

*.VSCNetworkPlacement

Determines Cisco MGC placement (AT or IXC) and bias routing accordingly.

Values:

Nanp_AT

Nanp_IXC

NULL

0

Default: NULL

Note If you do not set this property, all calls will route according to called number or some other criteria, not Carrier ID.

CALL_CUTOFF_TIMER

Provides a global system-wide timer, which is started when a call is answered and runs for the pre-configured time. When it expires the call is released in both directions and the call is cleared.

Property Valid Values: 0 to 48hours (in 1 hour intervals). A value of 0 will disable this timer.

The value set in the XECfgParm.dat file can be overridden by the value set in the first data word of the CALL_CUTOFF_TIMER result type.

Values: 0 - 48 hours (in 1 hour intervals)

0 = Disables the timer

1 through 48 = Specifies the time interval in 1hour increments.

CALL_CUTOFF_TIMER

(modified in Release 9.5(2) patch CSCOgs019)

Defines a global system-wide timer value. Timer is started after answer for every call and runs for a pre-configured time. When timer expires, the call is released in both directions and is cleared. This parameter is not dynamically reconfigurable. You must restart your system.

Valid values:

Hours: 0 (default), 1—48

Minutes: 0, 1—2880

Seconds: 0, 1—172800

CALL_CUTOFF_TIMER_UNITS (added in Release 9.5(2) patch CSCOgs019)

Defines the unit of measurement used for the global system-wide timer.

Valid values:

0 (hours) (default)

1 (minutes)

2 (seconds)

cfgM.recovDbFile

Storage location of the configuration manager recovery information.

Default: ../var/cfgMRecovery

Note Do not change this value.

diskmonitor.CdrRmFinished

Specifies the number of days to keep finished call detail record (CDR) files. The default value is 0, which means that if the Cisco BAMS is polling the Cisco MGC, CDR.bin files remain in a user-configurable directory until they are renamed by the Cisco BAMS (using format CDR_timestamp.finished) and/or the disk monitor trims the file from user-configurable directory.

Value: 0 or non-zero integer indicates days to delay before being deleted.

Default: 0

diskmonitor.CfgRmDirs

Specifies the maximum number of configurations that can be stored in the configuration library. This parameter must be manually added to the XECfgParm.dat file to activate the disk monitor enhancement shell script. This feature allows you to manipulate and disable the deletion of configuration directories through XECfgParm.dat. Old configuration directories are removed in reverse order when the indicated limit is reached.

Default: 64

If the XECfgParm.dat file is not updated, a default value of 64 is used for the number of allowable directories. If a default of 64 is used, the MGC will maintain up to 64 configurations in its /opt/CiscoMGC/etc/CONFIG_LIB directory.

Entering a value of 0 disables monitoring of the number of entries stored in the configuration library.To change the value of this parameter, you may need to add it manually to the XECfgParm.dat file.

The deletion of configuration directories can be disabled by setting the diskmonitor.CfgRmDirs parameter to a value less than or equal to 2, or greater than 64.

You can also reduce the number of allowable saved configurations by setting the parameter to a value between 3 and 64.

Note A default value in the range of 50 to 60 should be used to allow the disk monitor script to work properly when using the MML command PROV-SYNC.

diskmonitor.CoreRmDays

Specifies how many days to keep core dump files before disk monitor removes them automatically.

Default: 1

diskmonitor.Limit

Number of days to preserve before disk trimming is initiated.

Default: 7

Note Do not change this value.

diskmonitor.OptFileSys

List of optional file systems to monitor. Allows for optional user-configurable file systems to be monitored. This utility monitors the /opt file system for threshold crossing. Using this parameter, you can monitor additional file systems (disk slices) by setting parameter to the preferred directory, such as /tmp, /usr or /var. The messages associated with this parameter are sent to the platform.log file. To retrieve these messages, you must scan the platform.log file for messages using the following format: Filesystem file_system_name has exceeded num percent full. For example:

Filesystem /var has exceeded 80 percent full

These files are not trimmed by disk monitor.

Default: (blank)

diskmonitor.SoftLimit

Specifies the action to be taken once the number of days threshold set in the diskmonitor.Limit parameter is reached.

Works with diskmonitor.Threshold to prevent the disk from filling up and stopping the Cisco MGC.

If this parameter is set to true, disk monitor deletes files day by day until the utilization level drops below the threshold.

If this parameter is set to false, disk monitor closes and the system generates a DISK alarm. The files can then be deleted manually.

Default: False


Caution If this parameter is set to FALSE and the DISK alarm is raised, you must delete the non-required files to bring the disk utilization below the threshold. Otherwise, you run the risk of filling the disk and stopping the Cisco MGC.

diskmonitor.Threshold

Erases old log files to free disk space. The threshold is the percent the disk is full before trimming starts. Only var/log and var/spool are monitored by default; the diskmonitor function is local to these two directories by default.

Disk related alarms are generated only when diskmonitor is running and the disk cannot be trimmed back to the threshold level according to the parameter settings in XECfgParm.dat. If the disk is 86% full and diskmonitor successfully trims back to 80%, no alarm is generated.

Value: Any integer from 1 to 100 (% of threshold).

Default: 80

cdrDmpr.callDetail

Specifies that call detail record (CDR) files may be automatically converted from binary format to ASCII, comma-delimited format.

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

Optional: /opt/CiscoMGC/bin/converter (if binary CDR files need to be converted to ASCII)

Note The default CDR file format has changed from an ASCII format in Release 4 to a binary format in Release 7. The ASCII file has a .csv extension.

For more information on generating and viewing CDR files, see the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.

dmpr.openCDR

Specifies whether the standard data dumper should write out CDR files.

Values:

true = Standard data dumper opens a CDR file and log the call data blocks (CDB).

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

Default: true

Note The default format for CDR files has been changed since release 4 from an ASCII format to a binary format. Use the dmpr.callDetail parameter to convert the files to an ASCII format, if necessary.

engine.AuditTimerInterval

Time interval in milliseconds between two batches of audits.

Value: Any positive integer.

Default: 500

Note This is a platform-specific value and depends on your system installation. No auditing is available for nailed trunks.

engine.CallLimitingControl

(added in Release 9.6(1)

Allows enabling or disabling the call limiting capability on the MGC.

Valid values:

0 = call limiting off (default)

1 = call limiting on

engine.CALL_MEM_BLOCK_SIZE

Block of memory allocated per call.

Used by MDL.

Default:

Prior to Release 9.4(1): 0

For memory-critical configurations, use the default value.

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

Release 9.4(1) and up: set automatically based on the type of Cisco MGC selected in engine.SysVirtualSwitch. Any attempt to modify this value is overwritten.

engine.CALL_MEM_CHUNK_SIZE

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

Default:

Prior to Release 9.4(1): 0

For memory-critical configurations, use the default value.

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

Release 9.4(1) and up: set automatically based on the type of Cisco MGC selected in engine.SysVirtualSwitch. Any attempt to modify this value is overwritten.

engine.CDRencodingFormat

Specifies the call detail record (CDR) file encoding format.

Values:

AnsiCDB = North American

ItuCDB = European

CustCDB = Custom

Default: AnsiCDB

engine.CDRmessageTypes

To specify the Call Detail Blocks (CDBs are the accounting records written at various points in a call) that are generated during a call, enter one of the following sets of values (each number represents a point in a call):

1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080—These are considered the "event-based" set of values. Use this event-based list when you want to receive all CDR records at predefined points in the call. Although each of these CDBs can be specified independently, Cisco suggests that you use the event-based set as a "package" of CDBs for full accounting purposes.


Note The event-based setting is required when operating the Cisco MGC in conjunction with the BAMS adjunct.


1060, 1110—Use this value if you want end-of-call summary-type records only.

1071—Use this set of values for BAMS measurements.

Refer to the chapter "Detailed CDB Description" in the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide for details on each CDB.

engine.CDRtimeStamp

Specifies the time stamp unit in seconds or milliseconds.

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 or if you want the millisecond granularity in all of your CDR records.


Note The M setting is mandatory when operating the Cisco MGC in conjunction with the BAMS adjunct.


engine.CircuitReservation

Enables or disables the circuit reservation feature.

Values: True, False

Default: False

engine.CMMdlFile

Location of call processing libraries.

Default: ../lib/cc

Note Do not change this value.

engine.RelINAPCallsAfterSwOver

Defines the treatment of INAP calls in answer state after platform switchover. This parameter is used for calls that require INAP interaction even after the answer state. Currently, this parameter is used only for Prepaid INAP calls.

Values:

True (Release all the INAP calls after switchover)

False (Do not release INAP calls after switchover)

Default: True

Note If the value of this parameter is set to true, then PGW will release all calls immediately. If the value is set to False, PGW does not take any action for the INAP prepaid calls and these calls are treated like any normal POTS call.

engine.LCMMdlFile

Location of call processing libraries.

Default: ../lib/lcm

Note Do not change this value.

engine.MaxAuditCics

Number of circuit identification codes (CICs) that can be audited at a specified interval.

Values:

24 = North America (T1)

32 = Europe (E1)

Default: 32

Note Do not change this value.

engine.mdoDir

Location of call processing libraries.

Default: ../lib/

Note Do not change this value.

engine.SendHardwareBlock

To enable the Cisco MGC to send hardware-oriented blocking messages for any blocks that originate from the media gateways:

trueSends hardware-oriented blocking messages for any blocks that originate from the media gateways.

false—Sends only maintenance-oriented blocking messages for all blocking cases (default).

Note The functionality for this parameter is added in a patch for Release 9.3(2) and up. If your system is running Release 9.3(2) or Release 9.4(1) you must enter this parameter in the XECfgParm.dat file manually after installing the patch. If your system is running Release 9.5(2), the parameter is automatically added to the XECfgParm.dat file during the patch installation.

engine.ShortDurationCallPeriod

added in Release 9.5(2)

Allows you to specify the period used to determine a short duration call. Calls with a duration less than the specified value are recorded as a short duration call in the CDR.

Default: 0

Valid values are: 0—30. A setting of 0 indicates that this parameter is disabled. Short duration calls are not recorded in the CDR when this parameter is disabled.

engine.StartUpAuditEnabled

Audit is automatically invoked at PGW 2200 startup.

When the value is set to true the PGW 2200 automatically starts audit when it comes up as the active host. This does not apply to the standby host.

Default: false

engine.SysCdrCollection

Designates the format of call detail records (CDRs).

Values:

true = invalid for Release 7.4 and above.

false = generates binary format CDRs (default)

Default: false

Note Do not change this value. Setting this to a value of true for Release 7.4 and higher is not valid and may have deleterious effects on the system.

engine.SysCLIval

Enables or disables Calling Line Identity (CLI) validation processing on calls.

Values:

true = enables CLI validation

false = disables CLI validation

Default: false

engine.SysGeneratedCode

Determines whether compiled or interpreted code is used.

Values:

true = system uses compiled code

false = system uses interpreted code

Default: true

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.

engine.SysGSMTimerInterval

Allows group service messages (GSMs—used to advertise the state of circuits) to be sent at a periodic rate from the SS7 side of the network to the IP side of the network.

Valid values: 1000 to 30000

Default for Cisco MGC 9.2(2): 30000

Default for Cisco MGC 9.3(1): 10000

engine.SysGRSBlockSize

Used for flow control of all automatically generated GRS, CGB, and CGU messages which are generated by the Cisco MGC during run time. Typically produced due to propagation of service state changes such as MGCP endpoints changing availability. Specifies the interval, in milliseconds, between blocks of GRS parameters when the engine.SysGRSBlockSize parameter is used. The timer interval runs from the start of sending the first GRS message in each block to the first message in the next block.

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

Value: Any integer

Default: 0

Example: 1000

engine.SysMaxOverlap

Maximum number of digits required before a call is considered complete; used in overlap signaling.

Default: 28

Note Do not change this value.

engine.SysMdlMemoryReduction

Controls use of MDL memory reductions.

Prior to Release 9.4(1): values:

0 = MDL memory reductions not used (maximum performance)

1 = MDL memory reduction improvements used

Default: 0

Note For performance-critical configurations, use the default value. For memory-critical configurations, set this value to 1.

Note Setting this parameter to 1 enables the memory reduction algorithm which increases the number of concurrent (sustained) calls possible with the platform at the expense of call throughput performance.

Note During the startup of the Cisco MGC software, this parameter will be set automatically to tune the system for optimal performance.

Release 9.4(1) and up: set automatically based on the type of Cisco MGC selected in engine.SysVirtualSwitch. Any attempt to modify this value is overwritten.

engine.SysMinOverlap

Minimum number of digits required before a call is considered valid; used in overlap signaling.

Default: 0

Note Do not change this value.

engine.SysPropagateChanAvail

In a classic signaling controller configuration, propagates service messages between channels in the event of a channel failure.

Values:

true = messages propagated

false = messages not propagated (default)

Note Do not change this value.

engine.SysSGCPRetryCount

Maximum number of simple gateway control protocol (SGCP) retry messages after a failure.

Default: 3

Note Do not change this value.

engine.SysSGCPREtryTimerInterval

The interval between SGCP message transmissions, in milliseconds.

Default: 1000

Note Do not change this value.

engine.SysTraceLevel

A debugging tool that allows for different levels of engine tracing.

Default: 3

Note Do not change this value.

engine.SysVirtualSwitch

Indicates whether the Cisco MGC host functions as a signaling controller or a virtual switch controller.

Values:

0 = signaling controller (nailed trunks, no auditing is initiated)

1 = virtual switch controller (switched trunks)

Default: 0

Note During the startup of the Cisco MGC software, this parameter will be set automatically to tune the system for optimal performance.

Note For Release 9.4(1) and up, the values of the parameters listed below are automatically set based on the Cisco MGC type you select, to maximize performance for that configuration. Any attempt to change the values of these parameters is overwritten.

engine.SysMdlMemoryReduction
engine.CALL_MEM_BLOCK_SIZE
engine.CALL_MEM_CHUNK_SIZE
*.CPUTimerInterval
*.numberOfThreads

engine.VersionTimeoutValue

Defines the time out interval in number of milliseconds for version messages sent to the MGW. This delay determines how long the Cisco MGC will wait for response from the MGW during the exchange of features prior to the audit.

Value: Any integer.

Default: 10000

foverd.abswitchPort

Port used for communication with the A/B switch.

Value: /dev/term/x

Example: /dev/term/b

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

foverd.abswitchTestInterval

Time interval in milliseconds between attempts to verify that an A/B switch is present.

Default: 30000

Note This parameter only applies if your configuration uses an A/B switch.

foverd.ackTimeout

Maximum time, in milliseconds, that the failover daemon will wait for an ACK or NOACK message to be received from the peer failover daemon. For each message the failover daemon sends, the peer failover daemon sends an ACK or NOACK message to indicate that the peer is still functioning.

Default: 1000 milliseconds (1 second).

Note You can change the default value to a value more appropriate for your system installation.

foverd.commRetryInterval

Time interval in milliseconds between attempts to open a connection.

Connection types include:

Connection to the peer failover daemon

Connection to the A/B switch

Connection to the ARU

Default: 30000 milliseconds (30 seconds).

Note You can change the default value to a value more suited to your system installation.

foverd.conn1Type

Sets the connection type for connection number 1.

Values:

serial

socket

Note Typically, set this value to socket.

foverd.conn2Type

Sets the connection type for connection number 2.

Values:

serial

socket

Note Typically, set this value to socket.

foverd.conn3Addr

Specifies the address of the peer system.

Example: /dev/term/b

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 failover, you must modify the read-write permissions for the connection. For more information, see the Release Notes for the Cisco Media Gateway Controller Software Release 9.

foverd.conn3Type

Sets the connection type for connection number 3.

Values:

serial

socket

Note Typically, set this value to serial.

foverd.delayTimeout

Maximum time in milliseconds that the failover daemon can delay at startup before sending messages to its peer. This is also the delay offset that is added when the two failover daemons become too closely synchronized.

Default: 1000 milliseconds (1 second)

foverd.forceShutTimeout

Maximum time in milliseconds that the failover daemon waits before forcefully shutting down the platform.

Default: 1000 milliseconds (1 second)

foverd.graceShutTimeout

Maximum time in milliseconds that the failover daemon waits before gracefully shutting down the process manager, which shuts down the processes it controls.

Default: 6000 milliseconds (6 seconds)

foverd.heartbeatInterval

Maximum time in milliseconds between heartbeat messages from the peer failover daemon. This interval defines the frequency that the failover daemon exchanges heartbeat messages with its peer.

Default: 1000 milliseconds (1 second).

foverd.ipLocalPortA

Port number used for IP communication.

Default: 0

Note If you have two Cisco MGC hosts in a failover configuration, enter this value for the foverd.ipPeerPortA field in the XECfgParm.dat file on the secondary host.

foverd.ipLocalPortB

Port number used for IP communication.

Default: 0

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

foverd.ipPeerPortA

Port number used for IP communication.

Default: 0

Note If you have two Cisco MGC hosts in a failover configuration, enter this value for the foverd.ipLocalPortA field in the XECfgParm.dat file on the secondary host.

foverd.ipPeerPortB

Port number used for IP communication.

Default: 0

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

foverd.peerCommTimeout

Maximum time in milliseconds without communication with the remote system. At the expiration of this period, the remote system is assumed to be unavailable and failover is triggered automatically.

Default: 3000 milliseconds (3 seconds)

Note A time out value that is too small can cause a false failover, resulting in possible service interruptions.

foverd.statusRptInterval

Time interval in milliseconds that governs the frequency with which the failover daemon logs statistics on the different connections and any failures it encountered exchanging messages with its peer. Logs are created in the log directory.

Default: 600000 milliseconds (10 minutes)

foverd.transitionTimeout

Maximum time in milliseconds allowed for transitions between different states of the failover daemon. This timeout determines how long the system waits for a graceful transition to a new state before forcing the transition. If a timeout occurs, the system is restarted.

Default: 10000 milliseconds (10 seconds).

GWNetworkContinuity

For network continuity test on VISM.

Valid values:

1 means that Network Continuity is present/requested.

0 means that no Network Continuity is present/requested.

Default: 0 (Currently this property only applies to VISM GWs.)

Note This property should have value = 1 when the VISM GW property is switched on.

ioChanCtl.DPNSSTestFrames

Enables DPNSS to generate test frames.

Values:

true = if DPNSS is running, test frames are generated

false = test frames are not generated

Default: true

Note Do not change this value.

ioChanMgr.alarmTimer

This parameter is obsolete and should be set to 0.

ioChanMgr.evtTimer

Frequency, in milliseconds, at which the queue is scanned for messages.

Default: 100

Note Do not change this value.

ioChanMgr.hbTimer

This parameter is reserved for future use.

ioChanMgr.IPCsendThreshold

added in Release 9.5(2)

Specifies the maximum number of RSIPs that can be sent from the queue during a period defined by the IPCTimer XECfgParam.dat parameter. When this parameter is left at its default value (0), the system uses a base value. You can modify the value if a problem occurs.

Valid values: Any integer

Default value: 0

ioChanMgr.resumeAckTimer

Amount of time the Cisco MGC waits to get a MGMT_RESUME_ACK_RSP message from a gateway, after sending a MGMT_RESUME_REQ message fro a BSM session set.

Values are 1 to 2 seconds.

Default: 1

ioChanMgr.sendThreshold

Maximum number of events sent from the queue at one time.

Default: 10

Note Do not change this value.

ioChanMgr.sessionPauseTimer

Amount of time the Cisco MGC waits for a BSM session set to recover from failure before declaring the session set failure. Values are 1 to 10 sec.

Default: 8

ioChanMgr.statDiscardThreshold

Size of the control queue that triggers discarding of all queued stat events.

Default: 40

Note Do not change this value.

ioChanMgr.statTimer

Frequency, in milliseconds, at which measurements are collected in the Transpath input/output system (TIOS).

Default: 30000 milliseconds

Note Do not change this value.

ioChanMgr.trace

Creates unit test tracing of line and channel state machines. Generates a considerable amount of information to the log. Set to a value only when you are debugging a particular problem with line or channel service state problems.

Values:

0 x 0 = default

0 x 1 = trace

Note Do not change this value.

logger.daemonAddr

Specifies the name of the local socket used by the log server daemon. The daemon listens for connections on this address, and client programs attempt to connect to the daemon at this address.

Default: ../var/log/lsd_addr

Note If this setting is missing from the XECfgParm.dat file, the log server daemon does not run.

logger.fileRotateInterval

Triggers a file rotation based on the time elapsed since the previous rotation.

Default: 1440 minutes (24 hours)

Note This timer is reset after any rotation occurs, regardless of the cause or trigger of the rotation.

logger.fileRotateSize

Triggers a file rotation based on the size of the active file. A file rotation triggered by this parameter also resets the logger.fileRotateInterval timer.

Default: 100MB

Note The file size may grow larger than this parameter indicates due to the verbosity of the logging levels currently in effect.

logger.numThreads

Determines whether the PXE logger should run in a separate thread from the rest of the application. A value of 0 runs the logger synchronously with the application; a value of 1 runs the logger in a separate thread.

Value: 0/1 (Values less than 0 get reset to 0; values greater than 1 get reset to 1.)

Default: 0

MDLANumberScreening

Invokes the standard A-number screening on the number in the calling number parameter, regardless of whether the call is redirected or not.

Setting the MDLANumberScreening parameter to its default value 0 (zero) in the XECfgParm.dat file defaults all screening actions exclusively to the original calling party number (A-number). No screening is done on the number in the redirecting number parameter.

Default value: 0 (zero)

Note To invoke the redirecting number screening feature, set the value to 1 in the XEConfigParm.dat file during initial Cisco MGC software configuration.

MML.chg-cfg

Timeout value for the chg-cfg MML command in milliseconds; overrides MML.timeout.

Default: 10000 milliseconds

Note Do not change this value. This MML command is obsolete.

MML.snd

Timeout value for the snd MML command in milliseconds; overrides MML.timeout.

Default: 600000 milliseconds

Note Do not change this value.

MML.startPM

Timeout value for the startPM MML command in milliseconds; overrides MML.timeout.

Default: /etc/init.d/CiscoMGC start

Note Do not change this value.

MML.stopPM

Timeout value for the stopPM MML command in milliseconds; overrides MML.timeout.

Default: /etc/init.d/CiscoMGC stop

Note Do not change this value.

MML.timeout

Timeout for MML commands, in milliseconds.

Default: 10000 milliseconds

Note Do not change this value.

MML.vld-cic

Timeout value for the vld-cic MML command in milliseconds; overrides MML.timeout.

Default: 25000 milliseconds

Note Do not change this value.

pom.dataSync

Indicates that the Provisioning Object Manager (POM) should synchronize the provisioning data at startup.

Values:

true = POM is enabled, data is synchronized

false = POM is disabled, no data synchronization (default)

Note If you have two Cisco MGC hosts in a failover configuration, set this value to true. If you have a standalone Cisco MGC, set this value to false.

Note When the initial Cisco MGC configuration on the active host is deployed, you must change the pom.dataSync parameter to true in the XECfgParm.dat file on the standby host. After setting this parameter to true, you can start the Cisco MGC on the standby host. As the Cisco MGC comes up, the data on the standby host is synchronized with the data on the active host and the active host goes into the standby state.

To accommodate failover conditions where the current active host can become the standby host, you must also set the pom.dataSync parameter to true on the current active host.

Note If you are trying to maintain calls during an upgrade of a redundant system and you want to preserve your configuration, verify that the pom.dataSync parameter is set to false in /opt/CiscoMGC/etc/XECfgParm.dat.

pom.port

In a failover configuration, indicates the port number the POM uses to communicate with its peer.

Value: Any integer from 4001 to 4050

Default: 4001 or default

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

procM.almDwellInterval

Seconds that the process manager must wait before clearing an alarm.

Default: 15 seconds

Note Do not change this value.

procM.logDBFile

Specifies the location of the log level storage.

Default: ../var/procMLogTable

procM.minCheckHealthInterval

Seconds at which a process can generate heartbeats.

Default: 10 seconds

Note Do not change this value.

procM.minCheckHealthTimeout

Seconds at which a timeout can occur.

Default: 20 seconds

Note Do not change this value.

procM.minKillGracePeriod

Seconds that the process manager must wait before killing a process after a heartbeat timeout.

Default: 5 seconds

Note Do not change this value.

procM.recovDbFile

Storage location of the process manager persistent information.

Default: ../var/procMRecovery

Note Do not change this value.

procM.servFmt

Format of the process manager temporary files.

Default: PM_%d_%d_input

Note Do not change this value.

procM.servicesDir

Location of the process manager temporary files.

Default: ../var

Note Do not change this value.

procMprocHealthDfltAlmCat

This parameter is no longer used.

product.time

Software time stamp.

Note Do not change this value.

product.vendor

Software vendor name.

Note Do not change this value.

product.version

Software release version number.

Note Do not change this value.

replicator.portCommChannelRecv

Communication port for the replicator.

Default: 2974

Note Do not change this value.

replicator.portCommChannelSend

Communication port for the replicator.

Default: 2972

Note Do not change this value.

replicator.portDataChannelRecv

Communication port for the replicator.

Default: 2970

Note Do not change this value.

replicator.portDataChannelSend

Communication port for the replicator.

Default: 2968

Note Do not change this value.

replicator.reconnectInterval

Defines the reconnect interval in number of seconds for the replicator during a switchover.

Value: Any integer

Default: 15 seconds

Note Set this value to 0 for a standalone Cisco PGW.

For geographically separated Cisco PGW pairs (Geographic Separation of Active and Standby Cisco MGC Hosts), the following replicator timer values are recommended:

On one PGW, replicator.reconnectInterval = 15 seconds

On the other PGW, replicator.reconnectInterval = 20 seconds

If the timer settings are the same on both Cisco PGWs, the additional latency between the separated Cisco PGWs may cause a problem in which the replicator links are continually reconnecting and then immedately disconnecting. The timer change prevents this problem.

SipToIsupInterworkingInd

Only applicable with SIP to ISUP (or ISUP to SIP) calls.

When the Cisco PGW receives a SIP message with encapsulated ISUP (SIP-T, SIP-GTD), it sets the FCI/BCI parameter in the generated ISUP message so that all interworking-related bits have the same values as their counterparts in the encapsulated ISUP.

If usable encapsulated ISUP is not present in the SIP message, the Cisco PGW sets the Interworking Indicator bit of the FCI/BCI parameter to 'no interworking'; the ISDN User Part Indicator to 'ISUP used all the way' and the Originating Access indicator to 'Originating access non-ISDN'.

If desired, service providers can set the the Cisco PGW property 'SipToIsupInterworkingInd' to 1 which will signal in the FCI/BCI parameter in the generated ISUP message that 'interworking has been encountered' and 'ISUP is not used all the way' when encapsulated ISUP is not present in SIP message.

Values:

0 (No Interworking Encountered)

1 (Interworking Encountered)

Default Value: 0

Note If the property is absent from the XECfgParm.dat file, Cisco PGW assumes a default value of 0.

Protocol Family: Applicable to all ansi, q761 and q767 ISUP variants.