Cisco PGW 2200 Softswitch Release 9 Messages Reference
Log Messages
Downloads: This chapterpdf (PDF - 1.02MB) The complete bookPDF (PDF - 5.01MB) | Feedback

Log Messages

Table Of Contents

Log Messages

Log Messages Overview

MGCP Return Codes

End User Log Messages

Obsolete End User Log Messages

TAC Log Messages

MGCP Gateway Error Message for TAC


Log Messages


Revised: August 4, 2010, OL-1117-11

This chapter provides an overview of the Cisco PGW 2200 Softswitch software log message system, describes the messages and parameters that may be displayed, and lists the MGCP return codes that may be included in a log message.

Within this chapter, the log messages have been divided into two categories: those that provide information useful for end-users and those that provide troubleshooting information useful only to the Cisco TAC.

The following sections are included in this chapter:

Log Messages Overview

MGCP Return Codes

End User Log Messages

Obsolete End User Log Messages

TAC Log Messages

MGCP Gateway Error Message for TAC

For further information about configuring and using system logs, see the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide and the Cisco PGW 2200 Softswitch Release 9 MML Command Reference Guide.

Log Messages Overview

The Cisco PGW 2200 Softswitch creates system log messages and stores them in log files in either the /opt/CiscoMGC/var/log directory or a directory determined during the client initialization period or specified in the XE configuration parameter file. System log messages provide vital information that you can use in monitoring your system and troubleshooting problems. However, you should observe the following caution:


Caution Debug level logging provides extremely verbose output and, if misused, can cause serious system performance degradation.

The logging subsystem takes messages initiated by various software processes within the Cisco PGW 2200 Softswitch software, formats the messages, and writes them to the appropriate log files. The logging subsystem also adds a time stamp, a process identifier (for the UNIX process), and a log message severity. See the "SET-LOG" section of the Cisco PGW 2200 Softswitch Release 9 MML Command Reference Guide for a description of log levels.

Log messages take the following form:

Date/time-stamp, Timezone, Process Name, Process ID, <log level>, LogID:<text of the 
message>. (This text can take multiple lines but normally is only a single line.)

Example:
Fri Jan 14 08:46:53:700 EST 2000 | ProcessManager (PID 19593) <Info>
GEN_INFO_PSTART: Starting process PROVSAGT.

Note The time displayed in log messages is in system time.


The log files are stored in a directory indicated by the *.logDirectory XE configuration parameter and are given a name indicated by the *.logFileNamePrefix XE Configuration parameter. By default, all messages are written to the platform.log file in the $BASEDIR/var/log directory.

Additional XE configuration parameters can be set to direct various log messages to log files other than platform.log. To direct all log messages from a given process to a dedicated log file, use the *.logFileNamePrefix parameter to override the default. To direct log messages by category, set the various logger.category XE configuration parameters to the desired file name.

The Viewer Toolkit includes a log viewer that you can use to view the contents of the system logs. Various filter criteria are provided to reduce the volume of data included for you to review when searching the logs.

MGCP Return Codes

All MGCP commands are acknowledged by the system. The acknowledgment carries a return code indicating the status of the command. A number of log messages also include the MGCP return codes. A return code is an integer, for which the following three ranges of values have been defined:

Values between 200 and 299 indicate a successful completion.

Values between 400 and 499 indicate a transient error.

Values between 500 and 599 indicate a permanent error.

The values currently defined are listed in Table 2-1.

Table 2-1 MGCP Return Codes 


Return Code
Description

000

Response acknowledgement.

100

Transaction is being executed. Completion response will follow.

101

Transaction has been queued.

200

Transaction was executed normally.

250

Connection was already deleted.

400

Transaction not executed, transient error.

401

Phone is already off hook.

402

Phone is already on-hook.

403

Endpoint does not have sufficient resources.

404

Insufficient Bandwidth.

405

Endpoint is restarting.

406

Transaction timeout.

407

Transaction aborted.

409

Internal overload.

410

Endpoint not available.

500

Endpoint unknown.

501

Endpoint is not ready.

502

Endpoint does not have sufficient resources.

503

All of wildcard is too complicated.

504

Unknown or unsupported command.

505

Unknown remote connection descriptor.

506

Unable to satisfy both local connection option and remote connection descriptor.

507

Unsupported functionality.

508

Unknown quarantine handling.

509

SDP Error.

510

Protocol error.

511

Unrecognized extension.

512

Gateway not equipped to detect events.

513

Gateway not equipped to generate signal.

514

Transaction could not be executed because the gateway cannot send the specified announcement.

515

Invalid connection ID.

516

Unknown Call ID.

517

Unsupported/Invalid mode.

518

Unsupported/Invalid package.

519

Endpoint does not have a digit map.

520

Endpoint restarting.

521

Endpoint redirected to another call agent.

522

No such signal or event.

523

Unknown action or illegal combination of actions.

524

Internal inconsistency in LocalConnectionOptions (LCO).

525

Unknown extension in LCO.

526

Insufficient bandwidth.

527

Missing RemoteConnectionDescriptor.

528

Incompatible protocol version.

529

Hardware failure.

530

CAS signaling protocol error.

531

Failure of a grouping of trunks (facility error).

532

Unsupported values in LCO.

533

Insufficient bandwidth. Response too large.

534

Codec negotiation failure.

535

Packetization period not supported.

536

Unsupported RestartMethod.

537

Unknown or unsupported digit map extension, since the gateway does not have the digit map.

538

Event/Signal parameter error.

540

Per endpoint connection limit was exceeded.

596

VISM-specific return code indicating VCC failure or VCC could not be set up.

597

VISM-specific return code indicating the glare is detected

598

Media connection failure.

599

VISM-specific return code indicating media connection loss.


End User Log Messages

Log messages that provide information useful for end-users are presented in this section. The documentation of these messages is still incomplete. Messages that are for informational purposes only, in which the second part of the message name is "_INFO_", may lack descriptions.

MESSAGE:

CP_ERR_ABNORMAL_TRACE: <class::method>: <abnormal trace error>

DESCRIPTION:

Displays the error messages for abnormal trace. The possible messages are:

Abnormal trace is already active

Signaling path already exists

Abnormal trace request failed

Cisco PGW 2200 Softswitch abnormal trace request is not valid

Signaling path not found

Failed to allocate timer

No period given so not starting one

Map insert failed

Signaling path level failed


MESSAGE:

cmgPackInitializeCdr::execute: no interface

DESCRIPTION:

This message appears when the Cisco PGW 2200 Softswitch rejects an LI interface for licensing reasons.

MESSAGE:

CP_ERR_BC_INSV: <either class::method: or class::method: call <callid>> Bear channel is not in service

DESCRIPTION:

The bearer channel is not in the in-service state.


MESSAGE:

CP_ERR_BLK_CICS: < class::method>: failed to block <number of cics> cics

DESCRIPTION:

The action to block the CIC failed because the CIC number is larger than the maximum number of provisioned CICs.


MESSAGE:

CP_ERR_CHAN_NOT_ACQ: <class::method: | class::method: call <callid>> the channel is not acquired

DESCRIPTION:

This message is logged when a property value for a CIC (that is not available for call setup) cannot be read. A message is logged for each property that cannot be read. This error is logged when the channels are defined on the far-end [SS7] but not on the Cisco PGW 2200 Softswitch and when there is a mismatch between the channels on both sides of the call data path.


MESSAGE:

CP_ERR_FIND_COMPTYPE: <class::method>: failed to find compType table entry <component type>

DESCRIPTION:

The component type is not found in the component table.


MESSAGE:

CP_ERR_FIND_CUST: <class::method>: failed to find customer <customer ID>

DESCRIPTION:

The specified customer is not found.


MESSAGE:

CP_ERR_FIND_OBJECT: <class::method>: could not find < object type - e.g. Protocol Adapter or SigPath> for <XE Component ID>

DESCRIPTION:

Failed to find the object for the specified component ID.


MESSAGE:

CP_ERR_FIND_PTCODE: < class::method: <call<callid>>>: cannot find pointCode <point code>

DESCRIPTION:

The point code cannot be found.


MESSAGE:

CP_ERR_FIND_SIGPATH_COMP: <class method>: failed to find sigPath < sigPath Id> in component table

DESCRIPTION:

The signaling path cannot be found in the component table.


MESSAGE:

CP_ERR_FIND_SPAN: <class::method> failed to find span < sigPath>/<span>

DESCRIPTION:

The SPAN cannot be found in the span table.


MESSAGE:

CP_ERR_FIND_TRUNK: <class::method>: failed to find trunk <trunkGroup>/<trunk>

DESCRIPTION:

The trunk cannot be found in the trunk table.


MESSAGE:

CP_ERR_FIND_TRUNKGRP: <class::method>: failed to find trunkGroup <trunkGroup ID>

DESCRIPTION:

The trunk group cannot be found in the component table.


MESSAGE:

CP_ERR_FIND_VSF: <class::method>: failed to find VSF <VSF ID>

DESCRIPTION:

The virtual switching fiber cannot be found.


MESSAGE:

CP_ERR_FIND_VSF_BOX: <class::method>: failed to find VSF with boxnum <VSF box number>

DESCRIPTION:

The virtual switching fibers with the specified box number cannot be found.


MESSAGE:

CP_ERR_FIND_VSF_CXNSP: <class::method>: failed to find VSF with cxnSigPath <sigPath ID>

DESCRIPTION:

The virtual switching fiber with the connection signaling path cannot be found.


MESSAGE:

CP_ERR_HW_BC_BLK: <either class::method: or class::method: call <callid>> Bear channel is hardware blocked

DESCRIPTION:

The bearer channel is in the hardware blocking state.


MESSAGE:

CP_ERR_INV_USER: <class::method>: invalid user/network for sigPath <sigPath ID>, default=user

DESCRIPTION:

The user or network for the signaling paths is invalid; the default has been changed.


MESSAGE:

CP_ERR_LOAD_COT: <class::method>: failed to load <COT percentage name>, must be 0-100

DESCRIPTION:

The action to load continuity test percentage failed. The percentage must be in the range of 0 to 100.


MESSAGE:

CP_ERR_MAN_BC_BLK: <either class::method: or class::method: call <callid>> Bear channel is manual blocked

DESCRIPTION:

The bearer channel is manually blocked.


MESSAGE:

CP_ERR_NO_AVAIL_BC: <either class::method: or class::method: call <callid>> No available bear channel

DESCRIPTION:

There is no available bearer channel to be acquired for new calls.

The Cisco PGW 2200 Softswitch logs an error message in platform.log CP_ERR_CHAN_NOT_ACQ when a call is rejected due to no available channel. You can use this log to determine which bearers are failing and analyze them for one of the following three conditions.

1. Glare Condition: For example, for Cisco PGW 2200 Softswitch PRI backhaul for incoming call, if you can configure PBX to set exclusive bit to "preferred" in channel Id, the Cisco PGW 2200 Softswitch will select another available channel in case of glare. Alternatively you can also configure PBX to re-route the call if it fails.

2. Bearer is not in service: Using MML command, you can find out the cause of bearer failure.

3. Stuck endpoint: If there is stuck cic, and repeated error message: CP_ERR_CHAN_NOT_ACQ on the same channel in platform.log, use the print-call command on a stuck cic and then use kill-call to clear the channel.


MESSAGE:

CP_ERR_PROCESS_ALREADY_EXIST: < class::method>: <process> process already exists for call <call id>

DESCRIPTION:

The originating or terminating process for the specified call ID already exists.


MESSAGE:

CP_ERR_RESET_ACT: < class::method>: failed to reset, grp reset already active on <pointCode>/<cic>

DESCRIPTION:

The reset action failed because the group reset action was already active on the point code.


MESSAGE:

CP_ERR_RESET_BC: <class::method>: failed to reset bearChan, no call on <pointCode>/ <cic>

DESCRIPTION:

The action to reset the bearer channel failed because there is no call on the channel.


MESSAGE:

CP_ERR_RESET_CICS: <class::method>: failed to reset > <max number of cics> cics

DESCRIPTION:

The action to reset the CIC failed because the CIC number is larger than the maximum CIC number provisioned.


MESSAGE:

CP_ERR_SP_IS_CONG: <either class::method: or class::method: call <callid>>: SigPath is congested

DESCRIPTION:

The signal path is in congestion. New call setup may be affected.


MESSAGE:

CP_ERR_START_AUDIT: <either class::method: or class::method: call <callid>>: Cannot start audit

DESCRIPTION:

Unable to start NAS Audit because the audit timer cannot be started.


MESSAGE:

CP_ERR_START_GWAY_AUDIT: <either class::method: or class::method: call <callid>> Failed to start GWAY audit

DESCRIPTION:

Produced during startup and at failover (standby to active) to indicate that a gateway audit has not been performed, typically because XECfgParm.dat parameter engine.StarUpAuditEnabled=false. This message has been changed to CP_WARN_START_GW_AUDIT in software Release 8.0 and later. This message generally does not indicate a problem with the system.


MESSAGE:

CP_ERR_STOP_GWAY_AUDIT: <either class::method: or class::method: call <callid>> Failed to stop GWAY audit during platform state change

DESCRIPTION:

The action to stop the gateway audit failed because the platform state change is processing.


MESSAGE:

CP_INFO_ABNORMAL_TRACE: <class::method>: <info message>

DESCRIPTION:

Displays abnormal trace information. The possible information messages are:

Cisco PGW 2200 Softswitch trace has already stopped.

Signaling path abnormal trace is already in progress.

There is no abnormal trace request to delete on the signaling path timer expiration.


MESSAGE:

CP_INFO_DELETE_ROUTEKEY: <class::method>: Send route key delete request for sigPath <sigPath Id>, cic range - <CIC Range>

DESCRIPTION:

Deleting route key for the specified signaling path and CIC range.


MESSAGE:

CP_INFO_HW_ADDR: <class::method> - host <host name of system> has ethernet address <ethernet address>

DESCRIPTION:

Displays the network name of the system and the hardware address associated with the system's primary Ethernet adapter.


MESSAGE:

CP_INFO_INIT_ROUTEKEY: <class::method>: Begin initialization of route keys for sigPath <sigPath Id>

DESCRIPTION:

Process of registering signaling gateway route keys has started.


MESSAGE:

CP_INFO_LOAD_DIALPLAN_FAIL: failed to load dial plan tbls for customer <customer ID>


MESSAGE:

CP_INFO_LOAD_DIALPLAN_OK: loaded dial plan tbls for customer < customer ID>


MESSAGE:

CP_INFO_MDL_MEM_REDUCTION: <class::method>: SysMdlMemoryReduction level = <SysMdlMemoryReduction parm value>

DESCRIPTION:

Displays the value of the SysMdlMemoryReduction parameter.


MESSAGE:

CP_INFO_REGISTER_ROUTEKEY: <class::method>: Send route key registration request for sigPath <sigPath Id>, cic range - <CIC Range>

DESCRIPTION:

Registering the route key for the specified signaling path and CIC range.


MESSAGE:

CP_INFO_ROUTEKEY_RESPONSE: <class::method and response status (see description)> for sigPath <sigPath Id>, cic range starting at <route key start CIC>

DESCRIPTION:

Received an acknowledgement for a signaling gateway key registration/de-registration request. There are several possible response status values. The valid ones are:

route key registered

route key registration failed

route key de-registered

route key deleted

route key delete failed


MESSAGE:

CP_INFO_UNKNOWN_CALLID: <class::method>: received < event type> with unknown call id < call id>

DESCRIPTION:

Received event with unknown call ID.


MESSAGE:

CP_INFO_VSF_SSC: <class::method>: service state affecting event received; <message string containing details for the event>

DESCRIPTION:

Received event relating to a service state change for a gateway or virtual switching fiber.


MESSAGE:

CP_WARN_CALL_FAIL: <class::method> <compID of either orig or term sigPath> <Span and CIC information>

DESCRIPTION:

This message is produced any time a call object cannot be fully instantiated due to the mated B channel(s) being unavailable for one of the following reasons (as shown in the log message):

Blocked, out of service (OOS), unequipped

Originating or terminating protocol instance not available


Note This message does not always indicate a problem. For example, maintenance actions such as service state propagation (blocking/unblocking) typically generate these messages because they are manipulating the service state of one or more B channels. However, seeing this message immediately after receiving an IAM or SETUP from the line generally indicates a problem.



MESSAGE:

CP_WARN_CONFIG_ERRS: <class::method>: <number of errors> config errors

DESCRIPTION:

Either the signaling path does not exist, or the signaling path has no bearer channels. Number of errors indicates the number configuration violations detected.


MESSAGE:

CP_WARN_DUP_CHPT_MSG: < class::method>: Duplicate checkpoint answer message for call <call id>

DESCRIPTION:

During an attempt to create a standby call, it was noted that the checkpoint answer message already exists. The duplicate call is not created.


MESSAGE:

CP_WARN_GET_HW_ADDR: <class::method>: could not determine system hardware address: <reason for failure>

DESCRIPTION:

The specified class::method was unsuccessful in its attempt to retrieve the system's hardware address. The message also provides a detailed reason for the failure. In place of the actual address, a randomly generated value will be used in its place.


MESSAGE:

CP_WARN_INV_CONFIG: <class::method>: invalid config, only <num bearChans> bearChans

DESCRIPTION:

The configuration command is invalid because the bearer channel number is less than 2.


MESSAGE:

CP_WARN_PRINT_CALL: <class::method>: <info message>

DESCRIPTION:

Displays the reasons why the system failed to respond to a print call command. The possible reasons are:

Originating CCP is not valid.

Filestream is not valid.

Tracereq is not valid.

Signaling path is not valid.

Terminating CCP is not valid.

Printing is not done.


MESSAGE:

CP_WARN_PTCODE_SEND_BLK1: bearChan: <pointCode>/<cic> failed to send un/block msgs, pointCode not IS or initialized

DESCRIPTION:

Failed to send BLOCK/UNBLOCK messages; the point code is not in the in-service state or is not initialized.


MESSAGE:

CP_WARN_PTCODE_SEND_BLK2: failed to send un/block msgs, pointCode <pointCode ID> not IS

DESCRIPTION:

Failed to send BLOCK/UNBLOCK messages; the point code is not in the in-service state.


MESSAGE:

CP_WARN_UCIC: < class method>: received unequipped cic <cic> for point code < point code>

DESCRIPTION:

Configuration error. Bearer channel for the originating call not found.


MESSAGE:

ENV_CRIT_PROC_ERR: Unexpected return from <One of 'Pre-init', 'init', 'Post-init', 'Run', 'Pre-finalize',> stage, status = <XE Status code - reason for the failure> (<Status code converted to an error message string>)

DESCRIPTION:

Process initialization failure message in the XEProcShell. 'Finalize' or 'Post-finalize.'


MESSAGE:

ENV_ERR_CONFIG_PARM_LOOKUP_FAIL: Configuration parameter lookup failed for <Execution Environment Configuration Parameter name>

DESCRIPTION:

Process failed to locate given parameter in the XECfgParm.dat file. Process will exit.


MESSAGE:

ENV_ERR_DEFLT_CHDIR: Change to default data dir ' <Default data directory>' failed: <Error code> ( <Error code converted to a string>)

DESCRIPTION:

Data directory is missing or the user does not have permission to access it.


MESSAGE:

ENV_ERR_DNS_BIND: failed to bind to a port for processing DNS queries: <bind() Error code>

DESCRIPTION:

The SIP IOCC failed to bind to any of specified DNS ports. The ports could be currently being used by other applications.


MESSAGE:

ENV_ERR_GETHOSTBYNAME: Failed to find hostname for IPC <Pathname> status < Error code>

DESCRIPTION:

The host in question does not exist or is currently not connected to the network.


MESSAGE:

ENV_ERR_PLATFORM_ID: Invalid value for PlatformId = < Bad platform id string from config parameter file>. Check configuration parameters.

DESCRIPTION:

Invalid information in the configuration file for the PlatformId.


MESSAGE:

ENV_ERR_PROCESSOR_INFO: Failed to get processor info - Status: <Error code>

DESCRIPTION:

System will not attempt to bind engine threads to specific CPUs. The system will run, but performance may suffer if the CPU binding is required for this configuration to run at peak efficiency.


MESSAGE:

ENV_INFO_BIND_PROCESSOR_OK: Bind to processor <Processor number> successful


MESSAGE:

ENV_INFO_BIND_PSET: Attempt to bind to processor set <Processor set>


MESSAGE:

ENV_INFO_BIND_PSET_OK: Bind to processor set <Processor set> successful


MESSAGE:

ENV_INFO_BIND_THREAD: Bind Component %C to Thread - Poolname = <Thread identifier in SW_Layout table>


MESSAGE:

ENV_INFO_CLR_ALARM: COMPID <Component Id>: Clear alarm - Category <Category Id> Desc: <Alarm Description>

DESCRIPTION:

Clear a specific alarm.


MESSAGE:

ENV_INFO_CPU: Physical System: <Host name>\n\t# CPU = <Number of CPUs>\n\tClock Speed = <CPU Clock Speed>


MESSAGE:

ENV_INFO_IPC_OPEN: Opened FIFO <Name of the FIFO> (fd = <File Descriptor>)


MESSAGE:

ENV_INFO_NO_COMP_ENTRY: Failed to find component entry for <Component id> - Err = <Error code from findObj routine>


MESSAGE:

ENV_INFO_SET_ALARM: COMPID Component Id: Set alarm - Category Alarm Category Desc: Alarm Description

DESCRIPTION:

Set the specified alarm.


MESSAGE:

ENV_INFO_SET_PROCESS_PRIORITY: Attempt to set process priority to <New process priority>


MESSAGE:

ENV_INFO_SET_SCHED_PARMS: Scheduling parameters set successfully


MESSAGE:

ENV_WARN_CONFIG_PARM_LOAD_FAIL: <Handler trying to load a parameter>: Config param load failed for <Parameter name>, using default value (<Default value (may be empty string)>)

DESCRIPTION:

Attempted to load a configuration parameter from the configuration file and failed. System will use the default value for this parameter.


MESSAGE:

ENV_WARN_GET_SCHED_PARMS_FAIL: Can't get scheduling parameters - Errno = <Unix Error code>

DESCRIPTION:

Unable to get scheduling parameters.


MESSAGE:

ENV_WARN_LOAD_TBL: Failed to load component table with data mgr (<Error return from load routine>)

DESCRIPTION:

Failed to load a data table.


MESSAGE:

ENV_WARN_MEAS_LOCKFAIL: XEMeas(<Component Id>, <Category Id>): Failed to lock shared mem - Error code=<Error code>

DESCRIPTION:

Trying to update a shared memory measurement and failed to acquire the lock. See /usr/include/sys/errno.h file for an interpretation of the error code.


MESSAGE:

ENV_WARN_SET_SCHED_PARMS_FAIL: Can't set scheduling parameters - Errno = <Unix Error code>

DESCRIPTION:

Failed to set scheduling parameters.


MESSAGE:

GEN_CRIT_AB_SWITCH_INIT_FAIL: <Classmethod> Error initializing A/B switch, switchover failed - will retry every <period in seconds, after which a retry will be attempted> seconds

DESCRIPTION:

While attempting failover, the system was unable initialize the A/B switch. Re-attempts to initialize the A/B switch will be made periodically based upon the value of the foverd.commRetryInterval (milliseconds) parameter in XECfgParm.dat file.


MESSAGE:

GEN_CRIT_DYN_RCONFIG_BK_FAIL: Back-out of dynamic re-config failed < further info or an empty string>

DESCRIPTION:

After failure of dynamic reconfiguration, a roll-back to the previous configuration was attempted. This roll-back failed. The Cisco PGW 2200 Softswitch will continue to use the available configuration information.


MESSAGE:

GEN_CRIT_FOD_REQ_PARMS: Required parms <loaded/missing> : <info on the params or null string>

DESCRIPTION:

Unable to load required parameters from the XECfgParm.dat file.


MESSAGE:

GEN_CRIT_OBJ_LNK_ERR: Error re-linking object model <further info or an empty string>

DESCRIPTION:

Dynamic reconfiguration has failed. Roll-back to the original configuration will be attempted.


MESSAGE:

GEN_CRIT_PINIT: <class::method>: Process <process name> initialization failed. <specific reason for failure>

DESCRIPTION:

Unable to initialize the specified process. The reason for the failure is given in the message.


MESSAGE:

GEN_ERR_AB_SWITCH_MODE_SET_FAIL: Cannot set <name of the mode> mode (errno: <error no>), will retry every <period in seconds, after which a retry will be attempted> seconds

DESCRIPTION:

Failover daemon was unable to set the mode of the A/B Switch while initializing the A/B Switch (during switchover). Re-attempt to set the mode periodically based upon the value of the foverd.commRetryInterval (milliseconds) parameter in the XECfgParm.dat file.


MESSAGE:

GEN_ERR_AB_SWITCH_OPEN_FAIL: Cannot open <name of the device (path) to which the AB Switch is connected> (errno: <error no>), will retry every <period in seconds, after which a retry will be attempted> seconds

DESCRIPTION:

While attempting to fail over, unable open a port on the A/B switch. Re-attempts to open a port will be made periodically based upon the value of the foverd.commRetryInterval (milliseconds) parameter in the XECfgParm.dat file.


MESSAGE:

GEN_ERR_AB_SWITCH_SIG_FAIL: Could not set <<signal name> (RTS,DTR etc.)> on <name of the device (path) to which the AB Switch is connected>(errno: <errno>)

DESCRIPTION:

While attempting to fail over, unable to send a sequence of pulses controlling the A/B switch. Re-attempts to send the sequences of pulses will be made periodically based upon the value of the foverd.commRetryInterval (milliseconds) parameter in the XECfgParm.dat file.


MESSAGE:

GEN_ERR_CONFIG_FAIL: compId <component id>: <process and action> Configuration failure <reason>

DESCRIPTION:

An attribute of the specified component was configured with an invalid value.


MESSAGE:

GEN_ERR_DIROPEN: <class::method>: Error opening directory <name of directory which could not be opened>, status = <status of open operation>

DESCRIPTION:

Unable to create to the specified directory. Possible status meanings are:

1 = Not super-user

2 = No such file or directory

9 = Bad file number

20 = Not a directory

23 = File table overflow

24 = Too many open files

25 = Inappropriate ioctl for device

28 = No space left on device


MESSAGE:

GEN_ERR_FCOPY: Error copying file <name of file being copied> to < name of file being copied to>, status = <status of copy>

DESCRIPTION:

Unable to copy the specified file. Possible status meanings are:

1 = Not super-user

2 = No such file or directory

9 = Bad file number

20 = Not a directory

23 = File table overflow

24 = Too many open files

25 = Inappropriate ioctl for device

26 = Text file busy

27 = File too large

28 = No space left on device


MESSAGE:

GEN_ERR_FLINK: Error creating link between <top level directory> - <active directory path>, status = <System error code>

DESCRIPTION:

Unable to create an active link between directories. Possible status meanings are:

1 = Not super-user

2 = No such file or directory

9 = Bad file number

20 = Not a directory

25 = Inappropriate ioctl for device

26 = Text file busy

29 = Illegal seek

30 = Read only file system

31 = Too many links

32 = Broken pipe


MESSAGE:

GEN_ERR_FNOTFOUND: Could not find file <file which could not be found>.

DESCRIPTION:

Unable to find the specified file. Possible status meanings are:

2 = No such file or directory

9 = Bad file number

20 = Not a directory


MESSAGE:

GEN_ERR_FOD_CXN_INIT_FAIL: Cannot initialize connection <connection Id> (errno: < error no>) will retry every <period in seconds, after which a retry will be attempted> seconds

DESCRIPTION:

Unable to open the serial connection between the peer failover daemons. The Cisco PGW 2200 Softswitch will re-attempt to open this connection periodically based upon the value of the forverd.commRetryInterval (in milliseconds) parameter in the XECfgParm.dat file. The default retry interval in XECfgParm.dat is 30 seconds.


MESSAGE:

GEN_ERR_FOPEN: Error opening file <name of file/fifo>, status = <status of open operation>

DESCRIPTION:

Unable to create or write to the specified file. Possible status meanings are:

1 = Not super-user

2 = No such file or directory

9 = Bad file number

20 = Not a directory

23 = File table overflow

24 = Too many open files

25 = Inappropriate ioctl for device

26 = Text file busy

27 = File too large

28 = No space left on device


MESSAGE:

GEN_ERR_FREAD: Error reading file <name of file/fifo>, status = <status of read operation>

DESCRIPTION:

Unable to read the specified file. Possible status meanings are:

#define EPERM 1: Not super-user

#define ENOENT 2: No such file or directory

#define ESRCH 3: No such process

#define EINTR 4: interrupted system call

#define EIO 5: I/O error

#define ENXIO 6: No such device or address

#define E2BIG 7: Arg list too long

#define ENOEXEC 8: Exec format error

#define EBADF 9: Bad file number

#define ECHILD 10: No children

#define EAGAIN 11: Resource temporarily unavailable

#define ENOMEM 12: Not enough core

#define EACCES 13: Permission denied

#define EFAULT 14: Bad address

#define ENOTBLK 15: Block device required

#define EBUSY 16: Mount device busy

#define EEXIST 17: File exists

#define EXDEV 18: Cross-device link

#define ENODEV 19: No such device

#define ENOTDIR 20: Not a directory

#define EISDIR 21: Is a directory

#define EINVAL 22: Invalid argument

#define ENFILE 23: File table overflow

#define EMFILE 24: Too many open files

#define ENOTTY 25: Inappropriate ioctl for device

#define ETXTBSY 26: Text file busy

#define EFBIG 27: File too large

#define ENOSPC 28: No space left on device

#define ESPIPE 29: Illegal seek

#define EROFS 30: Read only file system

#define EMLINK 31: Too many links

#define EPIPE 32: Broken pipe

#define EDOM 33: Math arg out of domain of func

#define ERANGE 34: Math result not representable

#define ENOMSG 35: No message of desired type

#define EIDRM 36: Identifier removed

#define ECHRNG 37: Channel number out of range

#define EL2NSYNC 38: Level 2 not synchronized

#define EL3HLT 39: Level 3 halted

#define EL3RST 40: Level 3 reset

#define ELNRNG 41: Link number out of range

#define EUNATCH 42: Protocol driver not attached

#define ENOCSI 43: No CSI structure available

#define EL2HLT 44: Level 2 halted

#define EDEADLK 45: Deadlock condition.

#define ENOLCK 46: No record locks available.

#define ECANCELED 47: Operation canceled

#define ENOTSUP 48: Operation not supported

Filesystem Quotas

#define EDQUOT 49: Disc quota exceeded

Convergent Error Returns

#define EBADE 50: invalid exchange

#define EBADR 51: invalid request descriptor

#define EXFULL 52: exchange full

#define ENOANO 53: no anode

#define EBADRQC 54: invalid request code

#define EBADSLT 55: invalid slot

#define EDEADLOCK 56: file locking deadlock error

#define EBFONT 57: bad font file fmt

Interprocess Robust Locks

#define EOWNERDEAD 58: process died with the lock

#define ENOTRECOVERABLE 59: lock is not recoverable

Stream problems

#define ENOSTR 60: Device not a stream

#define ENODATA 61: no data (for no delay io)

#define ETIME 62: timer expired

#define ENOSR 63: out of streams resources

#define ENONET 64: Machine is not on the network

#define ENOPKG 65: Package not installed

#define EREMOTE 66: The object is remote

#define ENOLINK 67: the link has been severed

#define EADV 68: advertise error

#define ESRMNT 69: srmount error

#define ECOMM 70: Communication error on send

#define EPROTO 71: Protocol error

Interprocess Robust Locks

#define ELOCKUNMAPPED 72: locked lock was unmapped

#define ENOTACTIVE 73: Facility is not active

#define EMULTIHOP 74: multihop attempted

#define EBADMSG 77: trying to read unreadable message

#define ENAMETOOLONG 78: path name is too long

#define EOVERFLOW 79: value too large to be stored in data type

#define ENOTUNIQ 80: given log. name not unique

#define EBADFD 81: f.d. invalid for this operation

#define EREMCHG 82: Remote address changed

Shared library problems

#define ELIBACC 83: Can't access a needed shared lib.

#define ELIBBAD 84: Accessing a corrupted shared lib.

#define ELIBSCN 85: .lib section in a.out corrupted.

#define ELIBMAX 86: Attempting to link in too many libs.

#define ELIBEXEC 87: Attempting to exec a shared library.

#define EILSEQ 88: Illegal byte sequence.

#define ENOSYS 89: Unsupported file system operation

#define ELOOP 90: Symbolic link loop

#define ERESTART 91: Restartable system call

#define ESTRPIPE 92: if pipe/FIFO, don't sleep in stream head

#define ENOTEMPTY 93: directory not empty

#define EUSERS 94: Too many users (for UFS)

BSD Networking Software Argument errors

#define ENOTSOCK 95: Socket operation on non-socket

#define EDESTADDRREQ 96: Destination address required

#define EMSGSIZE 97: Message too long

#define EPROTOTYPE 98: Protocol wrong type for socket

#define ENOPROTOOPT 99: Protocol not available

#define EPROTONOSUPPORT 120: Protocol not supported

#define ESOCKTNOSUPPORT 121: Socket type not supported

#define EOPNOTSUPP 122: Operation not supported on socket

#define EPFNOSUPPORT 123: Protocol family not supported

#define EAFNOSUPPORT 124: Address family not supported by protocol family

#define EADDRINUSE 125: Address already in use

#define EADDRNOTAVAIL 126: Can't assign requested address

Operational errors

#define ENETDOWN 127: Network is down

#define ENETUNREACH 128: Network is unreachable

#define ENETRESET 129: Network dropped connection because of reset

#define ECONNABORTED 130: Software caused connection abort

#define ECONNRESET 131: Connection reset by peer

#define ENOBUFS 132: No buffer space available

#define EISCONN 133: Socket is already connected

#define ENOTCONN 134: Socket is not connected

XENIX has 135 - 142

#define ESHUTDOWN 143: Can't send after socket shutdown

#define ETOOMANYREFS 144: Too many references: can't splice

#define ETIMEDOUT 145: Connection timed out

#define ECONNREFUSED 146: Connection refused

#define EHOSTDOWN 147: Host is down

#define EHOSTUNREACH 148: No route to host

#define EWOULDBLOCK EAGAIN

#define EALREADY 149: operation already in progress

#define EINPROGRESS 150: operation now in progress

SUN Network File System

#define ESTALE 151: Stale NFS file handle


MESSAGE:

GEN_ERR_FREMOVE: Error removing file <file name>, status = <status>

DESCRIPTION:

Unable to delete the specified file. Possible status meanings are:

1 = Not super-user

2 = No such file or directory

9 = Bad file number

20 = Not a directory

26 = Text file busy


MESSAGE:

GEN_ERR_FRENAME: Error renaming file <current file name> to be <new file name>, status = <status>

DESCRIPTION:

Unable to rename the specified file. Possible status meanings are:

1 = Not super-user

2 = No such file or directory

9 = Bad file number

20 = Not a directory

25 = Inappropriate ioctl for device

26 = Text file busy


MESSAGE:

GEN_ERR_FWRITE: Error writing file <name of file>, status = <status>

DESCRIPTION:

Unable to create or write to the specified file. Possible status meanings are:

1 = Not super-user

2 = No such file or directory

9 = Bad file number

20 = Not a directory

23 = File table overflow

24 = Too many open files

25 = Inappropriate ioctl for device

26 = Text file busy

27 = File too large

28 = No space left on device


MESSAGE:

GEN_ERR_GETCFGPARM: <class::method>: Failed to get <name of configuration parameter> for facility <name of the facility>

DESCRIPTION:

Could not obtain the desired parameter from the XECfgParm.dat file.


MESSAGE:

GEN_ERR_HA_MSO: Cannot comply with Manual Switch Over request. Reason <reason string>

DESCRIPTION:

Generated by the process manager (procM) when a request for manual switchover is received.


MESSAGE:

GEN_ERR_HLTH_ALM_CAT_FAIL: Health alarm category <name of the health alarm category> not found in table <table name>

DESCRIPTION:

The specified alarm category was not found in the appropriate configuration table.


MESSAGE:

GEN_ERR_LINK_DOWN: Link to <Remote location> is down

DESCRIPTION:

Communication path is unavailable


MESSAGE:

GEN_ERR_MISMATCH: protocol mismatch with <name of the module, compID of link, compID of channel controller>

DESCRIPTION:

Protocol family for the link does not match that of the assigned channel controller.


MESSAGE:

GEN_ERR_MISSING: <What is missing - for example, in XEAlmCat.cpp it is 'SNMP Trap #> is missing for <Name of object that is missing information>

DESCRIPTION:

A parameter or object is missing configuration or update information.


MESSAGE:

GEN_ERR_MKDIR: Failed to create directory: <Pathname>

DESCRIPTION:

Failed to create a directory; the path may be invalid or the user may not have permission to create a directory.


MESSAGE:

GEN_ERR_NOROUTE: compId <Component Id>: No Route found for <name (example: channel controller)>

DESCRIPTION:

For the specified SS7 channel controller, unable to get the SS7 route information from the Data Dictionary.


MESSAGE:

GEN_ERR_PG_NOT_FOUND: Process group name <process group name> not found in table <table name>

DESCRIPTION:

Did not find specified the process group in components.dat file.


MESSAGE:

GEN_ERR_PROC_INPUT: Bad input stream while initializing process <process name>

DESCRIPTION:

Data Dictionary file processes.dat is either missing or corrupted, or the specified process is not described in the processes.dat file.


MESSAGE:

GEN_ERR_PROC_KILL_FAIL: <name of process> Failed to kill process <reason>

DESCRIPTION:

Failed to kill the specified process. The reason is a system error code.


MESSAGE:

GEN_ERR_PROC_NOT_FOUND: Process name <process name> not found in table <table name>

DESCRIPTION:

Did not find specified process in the components.dat file.


MESSAGE:

GEN_ERR_PSTOP: <class::method>: Failed to stop process <name of process>. <reason>

DESCRIPTION:

Unable to stop the specified process. The reason is a system error code.


MESSAGE:

GEN_ERR_SERVICE: <class::method>: Could not find service <name of the service>

DESCRIPTION:

Data Manager was unable to find the specified service in the services.dat file.


MESSAGE:

GEN_ERR_SERV_NOT_AVA: <service name> service is not available

DESCRIPTION:

Service is not available.


MESSAGE:

GEN_ERR_TIMEOUT: < class::method name>: <timer name or other description of timer> timeout


MESSAGE:

GEN_ERR_TIMEOUT_PROC: <classmethod name> <timer name or other description of timer> timeout for <process name> process

DESCRIPTION:

Response expected from the specified process did not occur within the time period set by specified timer.


MESSAGE:

GEN_ERR_UNKNOWN_MSG: <component ID>: Unrecognized or unknown message <Method name> <Content of the buffer>

DESCRIPTION:

Unable to process a message from either the engine or the gateway.


MESSAGE:

GEN_ERR_XFER_FILE: <class::method>: file transfer failed for <name of file being transferred>, status = <status>

DESCRIPTION:

Unable to move a file from one directory to another. Status is an XE event code.

See the following URLfor a detailed description of the status code:

http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/products_tech_note09186a008010ff0a.shtml.


MESSAGE:

GEN_INFO_ADDPATH_REQ: compId <component id> :Request to add path

MESSAGE:

GEN_INFO_CHKSUM: CheckSum on File < Filename> = <String containing the checksum value>


MESSAGE:

GEN_INFO_COMP_MON_STOP: Stopping monitoring for component <component name>


MESSAGE:

GEN_INFO_COMP_MON_STRT: Starting monitoring for component <component name>


MESSAGE:

GEN_INFO_COMP_MON_STRT_ACT: Graceful startup for monitoring of component <component name> pending active dependencies <description of active dependencies>


MESSAGE:

GEN_INFO_COMP_MON_STRT_INACT: Graceful startup for monitoring of component <component name> pending inactive dependencies <description of inactive dependencies>


MESSAGE:

GEN_INFO_DYN_RCONFIG_BK_OK: Back-out of dynamic re-config successful


MESSAGE:

GEN_INFO_DYN_RCONFIG_COMP: Dynamic re-configuration completed


MESSAGE:

GEN_INFO_DYRFG_STRT: Beginning dynamic re-configuration


MESSAGE:

GEN_INFO_EVTEXIT: Exiting event handler <name of event handler>


MESSAGE:

GEN_INFO_EVTHDNL_NOT_RQD: <Eventhandler name> Need not handle event of type <event type> <further info or an empty string>


MESSAGE:

GEN_INFO_EVTINIT: Initializing event handler <name of event handler>


MESSAGE:

GEN_INFO_EVT_CRT: Creating event <name of the event>


MESSAGE:

GEN_INFO_FACSTRT: Request to start <Facility name> completed with status <Return status or further info or an empty string>


MESSAGE:

GEN_INFO_FCREATE: Creating file <name of the file>


MESSAGE:

GEN_INFO_FOD_RQ_RCV: Failover daemon received <type of request received <shutdown, OOS,IS etc)> request <current state of local system> <current state of remote system>


MESSAGE:

GEN_INFO_FOVERD: <info string>

DESCRIPTION:

This log message is generated by foverd to reflect the pertinent fault tolerant information.


MESSAGE:

GEN_INFO_FREAD: Reading file <name of the file>


MESSAGE:

GEN_INFO_GETCFGPARM: Getting Configuration Parameter <the value of cfg. parameter.> of <the name of the parameter.>, Facility <the name of the facility>


MESSAGE:

GEN_INFO_HA_ACTION: <name of the process>: handling HA command <HA command <Standby/OOS/FSO/CSO>> <node for which this command is intended <local/remote>>

DESCRIPTION:

This message is used by processes that receive a high availability (HA) command from the process manager. When the process manager propagates HA commands to transition the platform to a certain active or standby state, these commands are received by different processes such as the alarm manager, engine, replicator, IOCM, etc., which use the message to handle the commands.


MESSAGE:

GEN_INFO_HA_ALL_READY: FT all ready


MESSAGE:

GEN_INFO_HA_ID: FTHA ownId=compId <component id>: peerid=<component id of peer>


MESSAGE:

GEN_INFO_HA_MSO_ENT: Entertaining a request for Manual Switch Over


MESSAGE:

GEN_INFO_HA_READY: <IOCC id of relevant IO Channel Controller>: FT Ready


MESSAGE:

GEN_INFO_HA_REG: <IOCC id of relevant IO Channel Controller>: FT Registered


MESSAGE:

GEN_INFO_INVALID_CONFIG: Unexpected configuration


MESSAGE:

GEN_INFO_LOG_LVL_CHGFAIL: < name of handler> Request for log level change, Component ID <ComponentId> failed < further info or an empty string>


MESSAGE:

GEN_INFO_MAXLINES: compId <Component Id>: Max <example: SRCP> number of lines exceeded


Note GEN_INFO_MAXLINES: is no longer supported as of Release 9.6(1).



MESSAGE:

GEN_INFO_MONP_VERSION_CRT: Version <version> of monitoring process <process name> created


MESSAGE:

GEN_INFO_MON_PROC_CRT: Created monitoring process <process name>


MESSAGE:

GEN_INFO_MON_PROC_DEL: Monitoring process <process name> deleted


MESSAGE:

GEN_INFO_MON_PROC_SRSTRT: Monitoring process < process name> stop detected, with signal number <signal no.>, killing and restarting


MESSAGE:

GEN_INFO_MON_PROC_TRSTRT: Monitoring process <process name> termination detected, with signal number <signal no.>, restarting


MESSAGE:

GEN_INFO_MON_PROC_VERSION_SUP: Version <version> of monitoring process <process name> superseded


MESSAGE:

GEN_INFO_OLD_MON_PROC_COMP_KILL: Killed old monitoring process for component <component name>


MESSAGE:

GEN_INFO_OLD_MON_PROC_KILL: Killed old monitoring process for component <process name>


MESSAGE:

GEN_INFO_PCREAT: Created process <process name> with PID <process ID>


MESSAGE:

GEN_INFO_PDEL: Process <process name> deleted


MESSAGE:

GEN_INFO_PEXIT: Process <process which is exiting>exiting

DESCRIPTION:

This message is used by the process that is exiting.


MESSAGE:

GEN_INFO_PG_ACTION: <Activity indication <startup/shutdown>> for process group <process group name> pending < description of the pending dependents <active/inactive>> dependents


MESSAGE:

GEN_INFO_PG_BEGIN: Beginning graceful <state indication <Startup/Shutdown>> for process group <process group name>


MESSAGE:

GEN_INFO_PG_DELETED: Process group <process group name> deleted


MESSAGE:

GEN_INFO_PG_FEXIT: Force exiting process group <process group name>


MESSAGE:

GEN_INFO_PG_SDL_START: Scheduling startup for process group <process group name> in < seconds before startup> seconds


MESSAGE:

GEN_INFO_PG_SHUTDOWN: Shutting down process group < process group name>


MESSAGE:

GEN_INFO_PG_START: Starting process group <process group name>


MESSAGE:

GEN_INFO_PG_SUPERSEDED: Process group <process group name> superseded


MESSAGE:

GEN_INFO_PINIT: Process < process name> initialization complete

DESCRIPTION:

Initialization is complete.


MESSAGE:

GEN_INFO_PLATFORM_STATE: Setting current platform state to <state>

DESCRIPTION:

This message is displayed to indicate the current platform state when updated by the process manager. Possible states are:

OOS—Platform is currently out of service and cannot perform as active or standby Cisco PGW 2200 Softswitch until commanded to do so.

Standby—Platform is not in active status but can become active if necessary.

Active—Platform has completed initialization and has assumed the role of the active node in a failover or standalone Cisco PGW 2200 Softswitch configuration.


MESSAGE:

GEN_INFO_PRG_OBSLT_DAT: Purging obsolete data from memory


MESSAGE:

GEN_INFO_PROC_NOTACTIVE: Process < process name> NOT Active


MESSAGE:

GEN_INFO_PROC_PND_SHUT_INACT: Shutdown for process <process name> pending active dependencies < description of active dependencies>


MESSAGE:

GEN_INFO_PROC_PND_START_INACT: Startup for process <process name> pending inactive dependencies <description of inactive dependencies>


MESSAGE:

GEN_INFO_PROC_RESTRT_DENY: Process <process name> has exceeded its restart limit of <maxRestarts> within <interval> seconds and will not be scheduled for restart


MESSAGE:

GEN_INFO_PROC_RESTRT_INIT: Restart initiated for process <process name>


MESSAGE:

GEN_INFO_PROC_RESTRT_STAT: Process <process name> restart <info on restart - already scheduled to restart, will not be scheduled to restart>


MESSAGE:

GEN_INFO_PROC_SDL_RESTRT: Scheduling startup for process <process name> in <time interval in seconds within which startup is scheduled> seconds


MESSAGE:

GEN_INFO_PROC_SDL_START: Scheduling startup for process <process name> in <seconds before startup> seconds


MESSAGE:

GEN_INFO_PROC_STAT_REQ_FAIL: <name of handler> Request for process status, Component ID <ComponentId> failed <further info or an empty string>


MESSAGE:

GEN_INFO_PROC_STOP_DETECTED: Process <process name> stop detected, with <additional info ('exit status' or 'signal no')> <value of exit status or signal no>


MESSAGE:

GEN_INFO_PSHUT: Shutting down process <Process name> <further info or an empty string>


MESSAGE:

GEN_INFO_PSTART: Starting process <Name of process that was started>

DESCRIPTION:

This message is used by a process that starts another process.


MESSAGE:

GEN_INFO_PVERSION_CRT: Version <version> of process <process name> created


MESSAGE:

GEN_INFO_PVERSION_SUP: Version <version> of process <process name> superseded


MESSAGE:

GEN_INFO_RECOV_COMP: Recovery for platform <PlatformId> completed < further info or an empty string>


MESSAGE:

GEN_INFO_RECOV_INIT: Initiating recovery sequence for platform <PlatformId> <further info or an empty string>


MESSAGE:

GEN_INFO_SHUT_COMP: Shutdown for platform <PlatformId> completed <further info or an empty string>


MESSAGE:

GEN_INFO_STANDALONE: Detected Standalone flag. Declaring the platform to be Active


MESSAGE:

GEN_INFO_STRT_INIT: Initiating start-up sequence for platform <PlatformId> <further info or an empty string>


MESSAGE:

GEN_INFO_TIMEOUT: <Name of the timer>timeout. <further info or an empty string>


MESSAGE:

GEN_TRACE_EVTREC: <name of the event handler> Received message with event type/subtype <event type>/<event subtype>


MESSAGE:

GEN_TRACE_FREAD: Reading <FIFO name> status = <status of read operation>, size = < number of bytes read>

DESCRIPTION:

This message is used to show the status of reading a FIFO.


MESSAGE:

GEN_TRACE_FWRITE: Writing <FIFO name> status = <status of read operation>, size = < number of bytes written>

DESCRIPTION:

This message is used to show the status of writing a FIFO.


MESSAGE:

GEN_TRACE_IPCREAD: <class::method name>: Reading IPC <IPC name or service name>, size = < size of the data read from this IPC>


MESSAGE:

GEN_TRACE_POLLEVTREC: <class::method name>: received polling event <event type>


MESSAGE:

GEN_WARN_DEL: compId <component id> :Deleting component

DESCRIPTION:

Deleting a specified link from the channel controller.


MESSAGE:

GEN_WARN_FOD_PARM_INV: Invalid <parameter name> using default: <default value>

DESCRIPTION:

Did not obtain a meaningful value for this parameter from the XECfgParm.dat file. Using the default parameter. Default parameters are:

foverd.heartbeatInterval = 4000

foverd.ackTimeout = 2000

foverd.abswitchTestInterval = 12000

foverd.graceShutTimeout = 10000

foverd.forceShutTimeout = 4000

foverd.commRetryInterval = 10000

foverd.statusRptInterval = 3600000

foverd.peerCommTimeout = 9000

foverd.transitionTimeout = 20000


MESSAGE:

GEN_WARN_FOD_REM_STATE_CHG: Remote system <current/failover> state change: <current state> --> <next state>

DESCRIPTION:

Failover daemon unable to change the state (to either current or failover) of the remote system.


MESSAGE:

GEN_WARN_FOVERD: < Information>

DESCRIPTION:

Generated by the failover process to reflect the pertinent fault tolerant warning information.


MESSAGE:

GEN_WARN_HA_MODE_NONHA: FT: non-fault tolerance mode going active

DESCRIPTION:

Unable to handle the platform state change. The non-fault tolerance mode is activated.


MESSAGE:

GEN_WARN_MON_PROC_TERM_TO: Monitoring process for component <component name> has not terminated within the expected health timeout interval of <timeout value> seconds, suspending monitoring until it terminates

DESCRIPTION:

Monitoring process for the specified component did not terminate within the expected health timeout interval; suspending monitoring until the monitoring process terminates.


MESSAGE:

GEN_WARN_PATH_NOT_CREATED: compId <component id> :Path could not be created

DESCRIPTION:

SS7 route could not be created for the specified component.


MESSAGE:

GEN_WARN_PHEALTH_CHK: Process < process name> failed health check

DESCRIPTION:

Specified process failed to respond to the heartbeat and is apparently not alive.


MESSAGE:

GEN_WARN_PROC_NOT_ALIVE: Process with PID <PID> is not alive, but is still listed in active process table

DESCRIPTION:

During periodic cleanup by the process manager, it was discovered that the process with the specified PID is no longer alive.


MESSAGE:

GEN_WARN_PROC_TERM_DETECTED: Process <process name> termination detected, with < additional info ('exit status' or 'signal no')> <value of exit status or signal no>

DESCRIPTION:

Termination of the specified process has been detected. The value of the exit status is a system wait code (see the UNIX man page for the wait<pid> command for more information).


MESSAGE:

GEN_WARN_PSHUT: Shutting down process <Process name> <further info or an empty string>

DESCRIPTION:

Indicates that a graceful shutdown of the specified process is occurring.


MESSAGE:

GEN_WARN_PSTARTED: Process <name of process that was started> started

DESCRIPTION:

This message is used by a process that was started by another process.


MESSAGE:

GEN_WARN_PSTOP: Stopping process <process stopped>

DESCRIPTION:

Process manager is stopping the specified process.


MESSAGE:

GEN_WARN_SIG: Received signal <Signal name> <further info or an empty string>

DESCRIPTION:

The process manager received the specified signal.


MESSAGE:

handleEngReq(), counted license has been changed due to license server unreachable for a long period of time

DESCRIPTION:

This message indicates that the number of counted licenses is less because the license server has been unreachable for a long period of time.

MESSAGE:

handlePeriodTimerEvent(), counted license has been changed due to license server unreachable for a long period of time

DESCRIPTION:

This message indicates that the number of counted licenses is less because the license server has been unreachable for a long period of time.

MESSAGE:

IC_NO_CIRCUIT_AVAILABLE (value 29)

DESCRIPTION:

When the UCM module receives the RSLT_NO_AVAILABLE_TRKS message, it sets the internal cause code to this message.


MESSAGE:

LMDataMgr::handlePeriodTimerEvent(), No valid base license, inform procM to shutdown PGW

DESCRIPTION:

This message indicates that there is no base license.

MESSAGE:

LMDataMgr::handleProcMReq(), gethostid() function been crashed, inform procM to shutdown PGW

DESCRIPTION:

This message indicates that the gethostid() function has crashed. The Cisco PGW 2200 Softswitch shuts down.

MESSAGE:

LMDataMgr::handleProcMReq(), No valid base license, inform procM to shutdown PGW

DESCRIPTION:

This message indicates that there is no base license.

MESSAGE:

LMDataMgr::initialize(), gethostid() function been crashed, inform procM to shutdown PGW

DESCRIPTION:

This message indicates that the gethostid() functionhas crashed. The Cisco PGW 2200 Softswitch shuts down.

MESSAGE:

LMDataMgr::initialize(), No valid base license, inform procM to shutdown PGW

DESCRIPTION:

This message indicates that there is no base license.

MESSAGE:

locLabelNotFound

DESCRIPTION:

A-number label xxxx (label component id) is not found

or

B-number label xxxx (label component id) is not found

or

origSide label xxxx (label component id) is not found

or

termSide label xxxx (label component id) is not found

MESSAGE:

locTableAccessFail

DESCRIPTION:

Failed to access the location label table

MESSAGE:

MGMT_ERR_POM_DEPLOY: <class::method>: deploy failed, status = <status>

DESCRIPTION:

Unable to deploy the provisioned configuration. Roll back to original configuration. Status is an XE event code.


MESSAGE:

MGMT_ERR_POM_POSTPROV: <class::method name>: Error in post provisioning processing <Provisioning error message returned>

DESCRIPTION:

Post-processing in POL (creation of channel controllers, customer specific files) failed.


MESSAGE:

MGMT_ERR_POM_PROVVALID: <class::method name>: Error validating configuration data for <number of tables rejected> tables

DESCRIPTION:

Validation of the provisioned configuration resulted in errors. Roll back to the original configuration. The number of validation rejections is provided


MESSAGE:

MGMT_ERR_SETALMSEV: Failed to set Alarm Severity < alarm severity level <almMinor/almMajor/almCritical>> by command <command sent to device by IOCTL (TSIOCALCTL/U4FTIOCALCTL)>, status = < status>

DESCRIPTION:

Unable to set the alarm severity for the specified alarm. The status code is a system code identified in the errno.h file.


MESSAGE:

MGMT_ERR_UPDOBJ: < class::method name>: Failed to update < name of object>, status = <Provisioning Object Library (POL) error code>

DESCRIPTION:

Unable to update (edit) a component in the Data Dictionary.


MESSAGE:

MGMT_INFO_ALMACKED: Alarm (category ID <category ID>, component ID < component ID>) is set and acked


MESSAGE:

MGMT_INFO_ALMLOG: ALARM Originator :< Service id>, Category <alarm category ID>, State <alarm state>


MESSAGE:

MGMT_INFO_CHANGE_LOG_LVL: Changing logging level to <new logging level (DEBUG, INFO, etc)>


MESSAGE:

MGMT_INFO_GOT_EVENTYPE: GOT EVENT TYPE < event type>


MESSAGE:

MGMT_INFO_MMDBGREW: Database grew by <growth in kbytes> KBytes (<portion in use> of <total usable> in use)


MESSAGE:

MGMT_INFO_MMDBSHRA: Database shrank by <shrinkage in Kbytes> KBytes (<portion in use> of < total usable> in use)


MESSAGE:

MGMT_INFO_MMDBTRM1: <request>: termination request received


MESSAGE:

MGMT_INFO_MMDBTRM2: <request>: termination begins


MESSAGE:

MGMT_INFO_POM_COMMIT: Successfully committed provisioning data


MESSAGE:

MGMT_INFO_POM_DEPLOY: Successfully deployed provisioning data


MESSAGE:

MGMT_INFO_POM_EMPTYLINK: The provisioning link path is empty, maintaining existing link


MESSAGE:

MGMT_INFO_POM_NOTFINDSESS: Could not find session < session id> for <usage of find session <cancel/stop>>


MESSAGE:

MGMT_INFO_POM_SESS: POM session by < user id> for version < destination version> restored


MESSAGE:

MGMT_INFO_POM_SESSBUSY: Session is used by <session ID>, starting session rejected


MESSAGE:

MGMT_INFO_POM_SESSTIMEOUT: Session inactive. <result of the session timeout>


MESSAGE:

MGMT_INFO_POM_STARTSESS: Session started by <session id>


MESSAGE:

MGMT_INFO_POM_STOPSESS: Session stopped by <session id>


MESSAGE:

MGMT_INFO_STARTDYNCFG: Dynamic reconfiguration starting for table <name of table>


MESSAGE:

MGMT_INFO_STOPDYNCFG: Dynamic reconfiguration for table <name of table> complete


MESSAGE:

MGMT_WARN_MMDBTRM3: <request>: termination complete

DESCRIPTION:

Completed the disconnect from the TimesTen database.


MESSAGE:

MGMT_WARN_UNKN_INTERVAL: <name of receiver> received unknown bucket interval <bucket interval> for bucket <name of bucket>

DESCRIPTION:

Unsupported interval specified for this bucket. Defaulting to 24-hour interval.


MESSAGE:

MGMT_WARN_UPOBJ: Updating Object <name of object> compId <component id>

DESCRIPTION:

Updating (as part of dynamic reconfiguration) the specified component.


MESSAGE:

MML_INFO_COMMAND: MML Command <name of MML command entered>


MESSAGE:

PROT_ERR_AVM_RSP_AFTER_TO: compId < component id>: Response has come after timeout < type of (conn/audit/entity/socket) response>

DESCRIPTION:

Used when the response comes from the AVM after a timeout occurs.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_ERR_BSM_ACTI_GRP: Failed to activate session grp %i set %i with err %x

DESCRIPTION:

This message is applicable only if the Cisco PGW 2200 Softswitch is configured in fault tolerant mode. Valid values of 'err' are:

0x17—The set index is out of bounds

0x0c—Incompatible arguments


MESSAGE:

PROT_ERR_MTP3: MTP3 Error Message from compId <component Id>: <general error string>

DESCRIPTION:

The general error string 'CP DiscInd reason xx' indicates failure of SS7 link identified by the 'compId' in the message. xx indicates the reasons for the failure. The following are the valid reasons:

00 - Request from the layer management

01 - SURM failure

02 - Excessive length of align period

03 - T7 timer expiration

04 - Physical interface failure

05 - 2 out of 3 invalid BSNs

06 - 2 out of 3 invalid FIBs

07 - LSSU condition

08 - Excessive MTP2 congestion

19 - SIOS received in LSC

20 - T2 expired waiting for SIO

22 - SIOS received in IAC

23 - Proving failure

24 - T1 expired waiting for FISU

25 - SIN received while in service

32 - CTS lost

37 - No resources


MESSAGE:

PROT_ERR_MTP3_LNK_CNTL: Link <destination point code> change of state to <state into which the link has transitioned>, cause <cause of state change>

DESCRIPTION:

Indicates why a link has an error.


MESSAGE:

PROT_ERR_MTP3_LSET_CNTL: Linkset <destination point code> state change to <state link has transitioned to>, cause <cause of state change>

DESCRIPTION:

Indicates why a link set has encountered an error.


MESSAGE:

PROT_ERR_MTP3_PC_CNTL: Point code <destination point code> change of state to <point code state transition>, cause <cause of state change>

DESCRIPTION:

Indicates why the point code has experienced an error.


MESSAGE:

PROT_ERR_MTP3: MTP3 Error Message from compId <component Id>:CP Error sending Mgmt Statistics Req

DESCRIPTION:

The error string "CP Error sending Mgmt Statistics Req" indicates failure of the SS7 link (identified by the "compId" in the message) to send information.


MESSAGE:

PROT_ERR_MTP3_RTE_CNTL: Route <destination point code> change of state to <new state>, cause <cause for state change>

DESCRIPTION:

Indicates why the route is experiencing an error.


MESSAGE:

PROT_ERR_NOT_CONFIG: compId <component id> :Route cannot be configured - cause <failure cause>

DESCRIPTION:

Unable to configure the route.


MESSAGE:

PROT_ERR_RLM_DATA_RCV: No data received for RLM link <component id of RLM link>

DESCRIPTION:

No data was received on the RLM link. As a result the Cisco PGW 2200 Softswitch takes the RLM OOS. Please check the communication with the NAS.


MESSAGE:

PROT_ERR_SRCP_BLD_PARMTYPE: compId <component id>: Unknown or unsupported SRCP parameter type <encoded value of the event parameter type>

DESCRIPTION:

Indicates that the SRCP message cannot be built because the event parameter type is unknown or unsupported.


Note PROT_ERR_SRCP_BLD_PARMTYPE: is no longer supported as of Release 9.6(1).



MESSAGE:

PROT_ERR_SRCP_PARSE_MAJVER: compId <component id>: SRCP major version mismatch < major version number>

DESCRIPTION:

Indicates that the major version number in the SRCP message does not match what this version of software supports.


Note PROT_ERR_SRCP_PARSE_MAJVER: is no longer supported as of Release 9.6(1).



MESSAGE:

PROT_ERR_SRCP_PARSE_MINVER: compId <component id>: SRCP minor version mismatch < minor version number>

DESCRIPTION:

Indicates that the minor version number in the SRCP message does not match what this version of software supports.


Note PROT_ERR_SRCP_PARSE_MINVER: is no longer supported as of Release 9.6(1).



MESSAGE:

PROT_ERR_SRCP_PARSE_PROT: compId <component id>: Protocol <protocol> not SRCP

DESCRIPTION:

Indicates that the SRCP message cannot be parsed because the protocol field in the command line is not SRCP.


Note PROT_ERR_SRCP_PARSE_PROT: is no longer supported as of Release 9.6(1).



MESSAGE:

PROT_ERR_UNREGSTR: unregistered SIO from Engine <component id>

DESCRIPTION:

Indicates that SS7 IOCC has received a message from the engine with an invalid SIO.


MESSAGE:

PROT_ERR_VSI_ENG_SERVICE: compId <Component Id>: Failed to add <indicates whether it is 'Engine write' or 'IDU read'> service; <is the requested IDU service or the Engine service.> not defined

DESCRIPTION:

Used when adding engine write or IDU read service for the VSI.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_ERR_VSI_RESYNC_CKSUMBLK_NOTFOUND:Checksum block <Checksum block> does not exist for slave id <slave id>

DESCRIPTION:

Used when a Checksum block could not be found during a resync procedure.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_ERR_VSI_RESYNC_PENDLIST_EMPTY: < is class::method name.>: Empty pending List

DESCRIPTION:

Used when the pending list is empty.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_ERR_XGCP_BLD_EPID: compId <component id>: XGCP endpoint string error <endpoint id>

DESCRIPTION:

Indicates that the xgcp message cannot be built because the end point is either not specified or not able to process.


MESSAGE:

PROT_ERR_XGCP_BLD_RESP_CODE: compId <component id>: XGCP endpoint string error %s

DESCRIPTION:

Indicates that the xgcp message cannot be built because the response code is invalid.


MESSAGE:

PROT_ERR_XGCP_PARSE_LINE: compId < component id>: Cannot parse <message line>

DESCRIPTION:

Indicates that an entire line in the SGCP/MGCP message cannot be parsed.


MESSAGE:

PROT_ERR_XGCP_PARSE_MINVER: compId < component id>: SGCP/MGCP minor version mismatch :< minor version number>

DESCRIPTION:

Indicates the minor version number in the SGCP or MGCP message does not match what this version of software supports.


MESSAGE:

PROT_ERR_XGCP_PARSE_PROT: compId <component id>: Protocol < protocol> not SGCP/MGCP

DESCRIPTION:

Indicates that the SGCP or MGCP message cannot be parsed because the protocol field in the command line is not SGCP or MGCP.


MESSAGE:

PROT_INFO_ADD_PTCODE: compId <Component Id> :Unable to add <is the type of point code> Pt Code


MESSAGE:

PROT_INFO_AVM_SIG_CHAN: AVM Sig Chan <component id>, state changed to <current state>, cause <cause for the state transition>

DESCRIPTION:

Indicates the status change on an AVM signaling channel.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_INFO_AVM_SIG_PATH: AVM Sig Path < component id>, state changed to <current state>, cause < cause for the state transition>

DESCRIPTION:

Used to indicate the status change on a AVM signaling channel.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_INFO_BAD_STAT: compId <component id> :cfgTrilliumLinkset linkset - bad state


MESSAGE:

PROT_INFO_BAD_TRANS: bad '<SSC>' transition <component id>


MESSAGE:

PROT_INFO_BSM_LINK_DOWN: Receive IO_DATA_LINK_DOWN for set :<set Id> grp <group Id> sess <session Id>

DESCRIPTION:

BSM link is down.


MESSAGE:

PROT_INFO_BSM_LINK_RESET: Receive IO_DATA_LINK_RESET for set <set Id> grp <group Id> sess <session Id>

DESCRIPTION:

BSM link is reset.


MESSAGE:

PROT_INFO_BSM_LINK_UP: Receive IO_DATA_LINK_UP for set <set Id> grp <group Id> sess <session Id>

DESCRIPTION:

BSM link is up.


MESSAGE:

PROT_INFO_BSM_SESS_EXIST: Session <session Id> already exists in group <group Id>

DESCRIPTION:

Invalid session encountered in the specified group.


MESSAGE:

PROT_INFO_BSM_STBY_GRP: Standby session grp <group Id> set <set Id>

DESCRIPTION:

BSM standby group.


MESSAGE:

PROT_INFO_CHANGE_LOG_LVL: Changing logging level to <new logging level (DEBUG, INFO, etc)>


MESSAGE:

PROT_INFO_CHNA_DEL_REQ: Received SSC request for deleted channel <component id of deleted channel>


MESSAGE:

PROT_INFO_CRT_SESS_MNGR: Created Session Manager


MESSAGE:

PROT_INFO_DPC_NOT_CONFIG: compId <component id of Destination Point Code> :Destination Pt code not configured properly


MESSAGE:

PROT_INFO_DPNSS: Info message from DPNSS: <Text of the message>


MESSAGE:

PROT_INFO_DPNSS_BEAR_CNTL: DPNSS channel %lx state change %s channel %s


MESSAGE:

PROT_INFO_DPNSS_LNK_CNTL: DPNSS channel %lx state change %s cause %s


MESSAGE:

PROT_INFO_IDU_TOO_BIG: <component id>: PDU size (<size of PDU>) exceeds max <maximum size> size

DESCRIPTION:

IDU is too big.


MESSAGE:

PROT_INFO_IOCC_INIT: Initializing IOCC: <component id of channel controller>


MESSAGE:

PROT_INFO_IOCC_KILL: killing Channel Controller


MESSAGE:

PROT_INFO_IP: Info message from IP: <Text of the message>


MESSAGE:

PROT_INFO_IP_LNK_CNTL: IP channel %lx state change %s cause %s


MESSAGE:

PROT_INFO_ISDN: Info message from ISDN: <general information string>


MESSAGE:

PROT_INFO_KILL_SESS_MNGR: Terminating Session Manager


MESSAGE:

PROT_INFO_MSG_UNKNLINK: compId <component id> :RLM message for unknown link


MESSAGE:

PROT_INFO_MTP3: compId <component id> <error message>

DESCRIPTION:

Indicates an error for the specified component. Valid error codes are:

Error Code                Description

ESN049                    Route configuration failed due to invalid combined linkset ID for the route.

ESN057                    Status request for particular route failed due to invalid DPC value.

ESN069                    Control request failed as an invalid control request for MTP3.

ESN257                    Signaling link test procedure already started for the link available at MTP2. The                                   re-confirmation indication for the link by MTP2 has been discarded.


MESSAGE:

PROT_INFO_MTP3_DPC_SWAP_LOOPBACK: <is enabled or disabled.> DPC SWAP loopback


MESSAGE:

PROT_INFO_MTP3_LNK_CNTL: Link <component Id> state change <transition state> cause <cause request>

DESCRIPTION:

MTP3 link control information.


MESSAGE:

PROT_INFO_MTP3_LOOPBACK: <is enabled or disabled.>MTP3 loopback


MESSAGE:

PROT_INFO_MTP3_RTE_CNTL: Route <destination point code> change of state to <route state transition>, cause <cause of state change>

DESCRIPTION:

Provides the tracking information needed to determine why a route list state change occurred.


MESSAGE:

PROT_INFO_NOT_CONFIG: compId <Component Id> : Unable to configure <The type of point code i.e user, MTP3> for pt code <Component Id of the point code>


MESSAGE:

PROT_INFO_PATH_PC_SSC: Path %08lx: PC SSC - trans %i


MESSAGE:

PROT_INFO_PATH_SSC: Path %08lx: SSC - trans %i cause %i


MESSAGE:

PROT_INFO_PLAT_ABORT: Platform state abort


MESSAGE:

PROT_INFO_PLAT_ACTIVE: Setting platform active


MESSAGE:

PROT_INFO_PLAT_CNTRL_SWITCH: Setting platform controlled switchover


MESSAGE:

PROT_INFO_PLAT_FRCD_SWITCH: Setting platform forced switchover


MESSAGE:

PROT_INFO_PLAT_OUT_OF_SRV: Setting platform out-of-service


MESSAGE:

PROT_INFO_PLAT_STANDBY: Setting platform standby


MESSAGE:

PROT_INFO_PRIOCNTL_REALTIME: Priocntl <channel controller name> now Real Time!!!


MESSAGE:

PROT_INFO_PROC_CTRL_REQ: < component id>: procCtrlReq(), status:< state transition>


MESSAGE:

PROT_INFO_RCVD_FROM_ICOM: Received <SSC name> from IOCM


MESSAGE:

PROT_INFO_RCVD_SSC: <class name>, received ssc msg from IOCM


MESSAGE:

PROT_INFO_RCV_SSC_REQ: Received SSC request <name of SSC request> for RLM link <component id>


MESSAGE:

PROT_INFO_RCV_UNSUP_SSC_REQ: Received unsupported SSC request for channel <component id>


MESSAGE:

PROT_INFO_REINIT_TCP: compId <component id of TCP channel> :Re-initializing TCP channel


MESSAGE:

PROT_INFO_REM_SIGCHAN: <component id of SigChan>: removeSigChan


MESSAGE:

PROT_INFO_REQ_CHAN_DEL: Received SSC request for deleted channel <component id of channel>


MESSAGE:

PROT_INFO_RESUM_RLM_PROC: Resuming RLM processing for group <group ID>


MESSAGE:

PROT_INFO_RLM_NOTENA: Rlm enabled: port %i


MESSAGE:

PROT_INFO_SENDFAIL: Unable to send link statistics to IOCM


MESSAGE:

PROT_INFO_SEND_IDU: <component id of channel which is sending IDU>: Send IDU to Eng


MESSAGE:

PROT_INFO_SERV_STAT_CHG: <component id>: procSSCMsgToChanMgr(), status:<status> - incorrect


MESSAGE:

PROT_INFO_SESS_ADD: < component id of session>: Session added successfully


MESSAGE:

PROT_INFO_SS7_CFG_MSG: Received SS7 <is the name of Module> cfg msg from IOCM


MESSAGE:

PROT_INFO_SSC_TO_CHANMGR: <component id>C: SSC Msg to ioChanMgr, status:<status>


MESSAGE:

PROT_INFO_TCP_LNK_CNTL: TCP channel %lx state change %s cause %s


MESSAGE:

PROT_INFO_TIMER_NOTAVA: Unable to allocate < is the name of timer> timer


MESSAGE:

PROT_INFO_UDP_LNK_CNTL: UDP channel %lx state change %s cause %s


MESSAGE:

PROT_INFO_UNEX_MSG: compId <component id> :<message type> message to unexpected component


MESSAGE:

PROT_INFO_UNSUP_REQ_CHAN: Received unsupported SSC request for channel <component id>


MESSAGE:

PROT_INFO_UNXP_CODE_STAT: Unexpected Pt code status < status> for <component id>


MESSAGE:

PROT_INFO_VSI_CFG_MSG: compId <component id of SigChan>: Received sig chan config msg from channel manager

DESCRIPTION:

Indicate the receipt of the configuration message from the channel manager.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_INFO_VSI_MASTER: compId <Component Id>: VSI Master log <info log from Master>

DESCRIPTION:

Displays information level messages from the VSI master API.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_INFO_VSI_RESP_RCV: <is class::method>: received <is ACK or NAK> response

DESCRIPTION:

Highlights an ACK/NAK response from the slave.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_INFO_VSI_SIG_CHAN: VSI Sig Can <component id>, state changed to <current state>, cause <cause for the state transition>

DESCRIPTION:

Indicates a status change on a VSI signaling channel.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_INFO_VSI_SIG_PATH: VSI Sig Path <component id>, state changed to <current state>, cause <cause for state transition>

DESCRIPTION:

Indicates the status change on a VSI signaling path.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_INFO_WAIT_NET_STABLE: RLM group <RLM group id>: waiting for network to stabilize


MESSAGE:

PROT_TRACE_ATM_AAL5_CLOSE: compId < componentId>: Deleting Stream < info on DSL number and File descriptor>

DESCRIPTION:

Indicates the closing of an AAL5 interface.


MESSAGE:

PROT_TRACE_ATM_AAL5_OPEN: compId <componentId>: IO stream AAL5 Open interface <name of the interface>

DESCRIPTION:

Indicates the opening of an AAL5 interface.


MESSAGE:

PROT_TRACE_ATM_SEND: SEND TO >>>> <component Id of the port on which message is sent> <: <VPCI to which message was sent>

DESCRIPTION:

Indicates that an ATM message was sent.


MESSAGE:

PROT_TRACE_AVM_PDU: Hex dump of AVM messages <component id> <from or to Media Gateway Controller (0 FROM, 1 TO)> <hex dump of PDU>

DESCRIPTION:

Used to dump the AVM PDU information.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_TRACE_MGCP_FROM_GW: compId: < the component ID>, MGCP msg from gateway, ip: < the gateway's ip address>, msg: <the message>

DESCRIPTION:

This message captures an MGCP message from the gateway.


MESSAGE:

PROT_TRACE_MGCP_TO_GW: compId: <the component ID>, MGCP msg to gateway, ip: <the gateway's ip address>, msg: < the message>

DESCRIPTION:

This message captures an MGCP message to the gateway.


MESSAGE:

PROT_TRACE_SIP_FROM_GW: compId: < the component ID>, SIP msg from gateway, ip: <the gateway's ip address>, msg: < the message>

DESCRIPTION:

This message captures an SIP message from the gateway.


MESSAGE:

PROT_TRACE_SIP_TO_GW: compId: < the component ID>, SIP msg to gateway, ip: <the gateway's ip address>, msg: < the message>

DESCRIPTION:

This message captures an SIP message to the gateway.


MESSAGE:

PROT_TRACE_SRCP_FROM_GW: compId: < the component ID>, SRCP msg from gateway, ip: < the gateway's ip address>, msg: <the message>

DESCRIPTION:

This message captures an SRCP message from the gateway.


Note PROT_TRACE_SRCP_FROM_GW: is no longer supported as of Release 9.6(1).



MESSAGE:

PROT_TRACE_SRCP_TO_GW: compId: <the component ID>, SRCP msg to gateway, ip: <the gateway's ip address>, msg: < the message>

DESCRIPTION:

This message captures an SRCP message to the gateway.


Note PROT_TRACE_SRCP_TO_GW: is no longer supported as of Release 9.6(1).



MESSAGE:

PROT_TRACE_TCAP_PDU_RX: Hex dump of TCAP message received, SSN=<Subsystem number in the message.>, LEN=<Length of the trace data.>,<Hex dump of TCAP PDU>


MESSAGE:

PROT_TRACE_TCAP_PDU_TX: Hex dump of TCAP message transmitted, SSN=<Subsystem number in the message.>, LEN=<Length of the trace data.>,<Hex dump of TCAP PDU>


MESSAGE:

PROT_TRACE_VSI_MASTER_MSG_SEND: Sending message to client. Message type <message type being sent>

DESCRIPTION:

Used when the master is sending a message to a client.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_TRACE_VSI_PDU: Hex dump of VSI messages <component id> <from or to Media Gateway Controller (0 FROM, 1 TO)> <Hex dump of PDU>

DESCRIPTION:

Used to dump the VSI PDU info when VSI messages are sent or received.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_TRACE_VSI_PROCCTRLREQ: compId <Component Id>: procCtrlReq - status <is current status>

DESCRIPTION:

Used when a ProcCtrlReq message is received from the channel manager.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_WARN_AVM_CONFIG_FAIL: compId <is the component id to which this sigchan is downloaded>: could not be created

DESCRIPTION:

Used by IOCC-AVM to indicate that the particular signaling channel is downloaded already and cannot be created.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

PROT_WARN_ENG_FULL: Engine IPC is full: pending incoming IDUs

DESCRIPTION:

Indicates that an IOCC is not able to send the messages received from the network to the engine. Verify whether the engine is processing the calls.


MESSAGE:

PROT_WARN_XGCP_PARSE_LONGCOMM: compId <component id>: Long SGCP/MGCP comment truncated <comment>

DESCRIPTION:

Indicates that the SGCP or MGCP message contains a long comment, and only a truncated copy will be passed to the upper layer.


MESSAGE:

RSLT_NO_AVAILABLE_TRKS

DESCRIPTION:

When percentage overflow is switched off, there is no percentage routing data sampled during routing analysis. When all the trunk groups and routes are checked, generic analysis returns this message to the UCM module.


MESSAGE:

SEND_STATE_TMR_EXPIRY

DESCRIPTION:

The message is send depending on active or standby state. The send_state_tmr_expiry functions is called when the state-TMR of a group expires. It reads the current platform and sends either a BSM_ACTIVE or BSM_STANDBY message.

The message is sent when two platforms are active and then later one of them restarts as standby. If the remaining active platform was not the last one to send BSM_ACTIVE message to the peer, the peer considers both platforms inactive.

ACTION:

Check the state of the EISUP backhaul sessions on both the Active and Standby Cisco PGW 2200 Softswitches to ensure that they are in the proper state. If they are not, collect the EISUP IOCC debug logs to forward to TAC to analyze.


MESSAGE:

SM_WRITESESSION:<component Id> is OOS, PDU Dropped.

DESCRIPTION:

The specified component is out of service, and data was lost.


MESSAGE:

TIOS_ERR_CDNG_INV: physLineIf: <component id of physical line> - coding %s is invalid for CEPT carrier

DESCRIPTION:

Indicates that the line coding type has been configured incorrectly for the given physical interface. Check the configuration for the specified physical interface.


MESSAGE:

TIOS_ERR_INVALID_RC

DESCRIPTION:

Indicates a mismatch in the configuration of the routing context between the Cisco PGW 2200 Softswitch and the Signaling Gateway.


MESSAGE:

TIOS_ERR_INVALIDCARD: Invalid Cardtype < cardtype> for line <component id of line>

DESCRIPTION:

Indicates a configuration error for the line.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

TIOS_ERR_INV_CARD: %08lx - invalid card %s or line %s

DESCRIPTION:

Indicates a configuration error for the physical interface.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

TIOS_ERR_INV_CARRIER: %s %C - invalid carrier %s

DESCRIPTION:

Indicates a configuration error in the physical interface.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

TIOS_ERR_INV_PROT: invalid Transport protocol= %s in stp.dat

DESCRIPTION:

Indicates a configuration error in the SS7subsystem.


MESSAGE:

TIOS_ERR_IN_STATE: in State <the name of the current state>

DESCRIPTION:

This message is informational and displays the current state.


MESSAGE:

TIOS_ERR_IP_RTE_CONF_FAIL: IP Route for <component ID of signal channel> Configuration Failure, Cause <reason for failure>

DESCRIPTION:

IP route for the specified signaling channel failed due to a configuration problem.


MESSAGE:

TIOS_ERR_IP_RTE_FAIL: IP Route for <component ID of signal channel> Failed, Cause <reason for failure>

DESCRIPTION:

IP route for the specified signaling channel failed due to the cause specified in the message.


MESSAGE:

TIOS_ERR_IPINTF_FAIL: IP Interface <provisioning name of interface, such as IP_ADDR1> has failed, OS name is <operating system name of interface, such as hme0>

DESCRIPTION:

The Ethernet interface used by a provisioned object is not operating.


MESSAGE:

TIOS_ERR_LINKFAIL: compId < component id of link>: No link with prio=1

DESCRIPTION:

Indicates a configuration error. No SS7 link with priority 1 is configured in the linkset indicated by the component ID.


MESSAGE:

TIOS_ERR_NOCARDCOMP: < component id of card>: No containing card component

DESCRIPTION:

Indicates data inconsistency in the sigChanDev.dat file. An entry in sigChanDev.dat file uses a card that is not provisioned.


MESSAGE:

TIOS_ERR_NOLINE: <component id of line>: No line entry

DESCRIPTION:

Indicates a data inconsistency between the phyLineIf.dat file and the sigChanDev.dat file. An entry in the sigChanDev.dat file is referring to a nonexistent entry in the physLineIf.dat file.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

TIOS_ERR_NOLINECOMP: <component id of line component>: No containing line component

DESCRIPTION:

Indicates a data inconsistency between the sigChanDev.dat file and the physLineIf.dat file. An entry in the sigChanDev.dat file is referring to a non existent entry in the physLineIf.dat file.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

TIOS_ERR_NOTDEF: OPC <component id of OPC> or APC < component id of APC>: not defined for route compId < component id of route>

DESCRIPTION:

Indicates a configuration error for an APC; either parameter 1 or parameter 2 in the error message is not defined in the dpc.dat file.


MESSAGE:

TIOS_ERR_NO_ENTRY: FAILURE: <component id of sigChan> No sigChanDev or sigChanDevIp Entry

DESCRIPTION:

Indicates a configuration error where the parameter in the log message is not defined in either the sigChanDev.dat or the sigChanDevIp.dat file.


MESSAGE:

TIOS_ERR_PROC_EXIST: <component id of process> component does not exist in process

DESCRIPTION:

The specified internal component does not exist in the process reporting the error. The question marks indicate that there is no MML mapping to the component ID, meaning there is no component entry.


MESSAGE:

TIOS_ERR_PROTNOFOUND: Signaling Terminal Port Number not found

DESCRIPTION:

Indicates a configuration error in the XECfgParm.dat file. The "stPort" parameter must be defined for the SS7 channel controllers to function properly.


MESSAGE:

TIOS_ERR_RECONFIG_FAIL:<component ID of component being reconfigured> reconfigure failed, <component ID of component in wrong state> must not be IS

DESCRIPTION:

Indicates that the DPC specified in the first parameter must be taken out of service to reconfigure the component specified in the second parameter.


MESSAGE:

TIOS_ERR_SCCP_MEAS: Error in SCCP measurement collection

DESCRIPTION:

Indicates an error in retrieving the SCCP measurements from the trillium SCCP stack. As a result, the measurement counters for SCCP will not show the correct values.


MESSAGE:

TIOS_ERR_SOCKET_ICMP: <class::method> failed to open a raw socket for ICMP msg processing:<socket() return code>

DESCRIPTION:

Error occurs when a raw socket is being created. The socket can only be opened by a UNIX superuser.


MESSAGE:

TIOS_ERR_TCAPMSG: Error in processing TCAP message. Invalid/missing <Name of the parameter associated with the error>, param =< Parameter1 value>,param2=< Parameter2 value>

DESCRIPTION:

Indicates that a TCAP message could not be processed in the trillium TCAP stack because of invalid or missing parameters. The following invalid or missing parameters are reported:

invokeId—Duplicate/unrecognized invoke ID.

mandatory element—A mandatory element is missing.

message—An unexpected/unrecognized message is received.

compEvent—Invalid component event in compReq primitive.


MESSAGE:

TIOS_ERR_TCAPSTACK: Error from TCAP stack. FAILURE: <Error type.>. param1=<Parameter associated with the error>,param2=<Parameter associated with the error>

DESCRIPTION:

The dynamic reconfiguration might have failed as a result of this error.


MESSAGE:

TIOS_ERR_UNKNOWN_IPADDR: Unknown IP address <peer or local>

DESCRIPTION:

Indicates a configuration error in the XECfgParm.dat file. IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4 parameters are possibly not defined in this file.


MESSAGE:

TIOS_ERR_UNKN_CKPT: Unknown < name of the checkPt port> checkpoint port

DESCRIPTION:

The chkPtPort parameter is not defined in the XECfgParm.dat file.


MESSAGE:

TIOS_ERR_UNKN_COMPTP: Component type <name of the comp type> is not defined in compTypes.dat

DESCRIPTION:

The component type is not defined in the compTypes.dat file.


MESSAGE:

TIOS_ERR_UNKN_MGC: Unknown Media Gateway Controller: <Media Gateway Controller name>

DESCRIPTION:

The ownTranspathId and/or peerTranspathId parameters are not defined in the XECfgParm.dat file.


MESSAGE:

TIOS_ERR_UNKN_MSG: Unknown meas for <component id>, measNm <measurement name>

DESCRIPTION:

The measNm parameter is not defined in the measCats.dat file.


MESSAGE:

TIOS_ERR_UNKN_PLTST: Parameter 'desiredPlatformState' is not defined in XECfgParm.dat

DESCRIPTION:

The desiredPlatformState parameter is not defined in the XECfgParm.dat file.


MESSAGE:

TIOS_ERR_UNKN_PROPERTY: Property <Property prefix>.< Property name> is not defined in properties.dat. Info = <Additional informational parameter>

DESCRIPTION:

The property identified by the parameters in the message is not defined in the properties.dat file.


MESSAGE:

TIOS_ERR_UNKN_STRING_PROPERTY: String property <Property prefix> - <Property name> not defined in properties.dat. Info= <Additional informational parameter>

DESCRIPTION:

The property identified the parameters in the message is not defined in the properties.dat file.


MESSAGE:

TIOS_ERR_UNKN_TIOS_FAM: <data file name for which the error is detected.> unknown proto family<protocol family name that is not recognized.>for sigpath <Component name>

DESCRIPTION:

The sigPath.dat file contains a record with an unknown protocol family name.


MESSAGE:

TIOS_ERR_UNREC_CARD: <class name>: unrecognized card type < card type>

DESCRIPTION:

Indicates an error in one of the records in the sigChanDev.dat file.


MESSAGE:

TIOS_INFO_CRSER: ioCardABC compId <component id of service>: createService


MESSAGE:

TIOS_INFO_DELOBJ: Deleting object <component id of object being deleted>


MESSAGE:

TIOS_INFO_DLD: compId <component id of module being downloaded>: Downloaded <name of module being downloaded>

DESCRIPTION:

Displays MGCP signaling path information.


MESSAGE:

TIOS_INFO_DNS_DOWN: local SIP DNS state changed to DOWN

DESCRIPTION:

The SIP has changed the local DNS state to DOWN.


MESSAGE:

TIOS_INFO_DNS_UP: local SIP DNS state changed to UP

DESCRIPTION:

The SIP has changed the local DNS state to UP.


MESSAGE:

TIOS_INFO_FIND_IOCC_FAIL: Cannot find ioCC <component id of channel controller not found>: Creating <component id of new channel controller being created>


MESSAGE:

TIOS_INFO_GETALA: ioCardABC compId <component id of card>: trying to get alarms


MESSAGE:

TIOS_INFO_INIT_ACTV: INIT: Active Mode


MESSAGE:

TIOS_INFO_INIT_STBY: INIT: Standby Mode


MESSAGE:

TIOS_INFO_IP_RTE_CRT: Creating IP Route for <component ID of signal channel> via nexthop <gateway address string in dot decimal notation (i.e. 1.2.3.4)> using netmask <subnet mask string in dot decimal notation (i.e. 255.255.255.240)>

DESCRIPTION:

Creating IP route for the specified signaling channel with the specified gateway and subnet parameters.


MESSAGE:

TIOS_INFO_IP_RTE_DEL: Deleting IP Route for <component ID of signal channel> via nexthop <gateway address string in dot decimal notation (for example, 1.2.3.4)> using netmask <subnet mask string in dot decimal notation (for example, 255.255.255.240)>

DESCRIPTION:

Deleting IP route for the specified signaling channel with the specified gateway and subnet parameters.


MESSAGE:

TIOS_INFO_IP_RTE_IN_USE: IP Route for <compID> via next hop <gateway address string in dot decimal notation (for example, 1.2.3.4)> using netmask <mask string in dot decimal notation (for example, 255.255.255.240)>

DESCRIPTION:

Indicates the next hop address and netmask for a specified signaling channel.


MESSAGE:

TIOS_INFO_IPINTF_RECOV: IP Interface <provisioning name of interface, such as IP_ADDR1> has recovered, OS name is <operating system name of interface, such as hme0>

DESCRIPTION:

An alarm has been cleared for the Ethernet interface used by a provisioned object.


MESSAGE:

TIOS_INFO_NOT_IMPL: <component id>: NOT IMPL fault=<fault id> state=<state id>


MESSAGE:

TIOS_INFO_PORTFOUND: Found Signaling Terminal Port Number <port number>


MESSAGE:

TIOS_INFO_RCMSG: ioCardABC compId <component id>: rcv XERawMsg


MESSAGE:

TIOS_INFO_RCVERRMSG: ioCardABC compId <component id>: rcv ioCardIpcErrorMsg


MESSAGE:

TIOS_INFO_RECON: <component id>: RECON state=<SVC state>


MESSAGE:

TIOS_INFO_SCCP_USER_IS: SCCP User IS: Switch=< Indicates protocol type (ANSI/ITU)>,suId=<SCCP Service user Id>


MESSAGE:

TIOS_INFO_SCCP_USER_OOS: SCCP User OOS: Switch=<Indicates protocol type (ANSI/ITU)>,suId=<SCCP Service user Id>


MESSAGE:

TIOS_INFO_SSN_STATE: SSN State change for SSN = <Subsystem number.>, DPC=<DPC>: new state = <new state>


MESSAGE:

TIOS_WARN_AUDIT_CMPLT: <component id>: Gateway AUDIT already retrieved and complete (command = <command>)

DESCRIPTION:

Gateway audit is complete.


MESSAGE:

TIOS_WARN_AUDIT_RESP: Gateway Audit Response string = <contents of the audit response>

DESCRIPTION:

Gateway audit response is received.


MESSAGE:

TIOS_WARN_AUDIT_RNNG: <component id>: Gateway audit in progress - request <command> ignored

DESCRIPTION:

Gateway audit is in progress.

Request translation table:

0—Undefined

1—GW_START

2—LINE_START

3—GW_RESPONSE

4—LINE RESPONSE

5—GW-RTRV

6—LINE-RTRV


MESSAGE:

TIOS_WARN_AVM_SSC_XMIT: compId <component id>: Transmit AVM SP-SSC=<SSC state>, CAUSE =<cause of SSC>

DESCRIPTION:

Indicates that an SSC was transmitted by AVM.


Note This message is obsolete starting with the Cisco PGW 2200 Softswitch software release 9.4(1).



MESSAGE:

TIOS_WARN_CKPT_SSC: compId <Component Id>: CHKPT SSC trans=<Transition id>, cause=<Error number>

DESCRIPTION:

This log message should appear only on the standby host and indicates receipt of checkpointing event for a signaling channel. The value of cause is always 0 and can be ignored.


MESSAGE:

TIOS_WARN_DIST_INV: distance <Value of distVal parameter which is wrong.> is not valid for CEPT carrier

DESCRIPTION:

The distVal parameter for one of the records in the physLineIf.dat file is wrong. A distVal value of 75 is assumed.


MESSAGE:

TIOS_WARN_DNS_QUERYFAIL: failed to send DNS query msg: < the IP address>

DESCRIPTION:

SIP IOCC has sent a DNS query to the network.


MESSAGE:

TIOS_WARN_FAS_SSC_XMIT:<component id>: Transmitted FAS IP Service State Change=<new service state>, Cause=<cause for change to new service state>

DESCRIPTION:

A service state change (SSC) event has been sent.

Cause code translation:

0 = CAUSE_UNKNOWN

1 = CAUSE_NA

2 = CONFIG_FAIL

3 = LINE_FAIL

4 = LINKSET_FAIL

5 = LINK_FAIL

6 = ENGINE_RESET

7 = CAUSE_COMMANDED_OOS

8 = CAUSE_COMMANDED_IS

9 = SUPPORTING_ENTITY

10 = OOS_PENDING

11 = IS_PENDING

12 = TRAFFIC_PATH

13 = C7_SignalErr

14 = C7_BSNR_FIBR

15 = C7_LinkCongestion

16 = C7_AckDelay

17 = C7_LocalInhibit

18 = C7_RemoteInhibit

19 = C7_LocalBlocked

20 = C7_RemoteBlocked

21 = C7_LocalUninhibit

22 = C7_RemoteUninhibit

23 = C7_LocalUnblocked

24 = C7_RemoteUnblocked

25 = C7_LocalInhibitDeny

26 = CongLocal

27 = CongRemote

28 = CAUSE_ACTIVE

29 = CAUSE_STBY

30 = MGCP_HEARTBEAT_FAILED

31 = SRCP_HEARTBEAT_FAILED

32 = SRCP_AUDIT_GW_TYPE_FAILED

33 = SRCP_AUDIT_GW_SLOT_NUM_FAILED

34 = SRCP_AUDIT_GW_NUM_OF_LINES_FAILED

35 = SRCP_AUDIT_GW_BACKHAUL_PROTOCOL_FAILED

36 = SRCP_AUDIT_GW_CONTROL_PROTOCOL_FAILED

37 = SRCP_AUDIT_GW_COORD_PROTOCOL_FAILED

38 = SRCP_AUDIT_GW_NUM_OF_BACKHAUL_SESSIONS_FAILED

39 = SRCP_AUDIT_GW_CU_IP_ADDR_FAILED

40 = SRCP_AUDIT_GW_CU_IP_PORT_FAILED

41 = SRCP_AUDIT_GW_SU_IP_ADDR_FAILED

42 = SRCP_AUDIT_GW_SU_IP_PORT_FAILED

43 = SRCP_AUDIT_LINE_SIG_PROTOCOL_FAILED

44 = SRCP_AUDIT_LINE_CODING_FAILED

45 = SRCP_AUDIT_LINE_STATE_FAILED

46 = SRCP_AUDIT_LINE_LOOPBACK_FAILED

47 = C7_Prohibit

48 = C7_Restrict

49 = C7_SRT_PASSED

50 = C7_SRT_FAILED

SSC translation:

0 = UNDEFINED_TRANS

1 = CREATE

2 = DELETE

3 = COMMANDED_IS

4 = COMMANDED_OOS

5 = FAILED

6 = RESTORED

7 = RESET

8 = CONGESTION

9 = FORCED_OOS

10 = COMMANDED_INH

11 = COMMANDED_UNINH

12 = COMMANDED_EMRG_ALIGN

13 = ENG_IS

14 = ENG_OOS

15 = RESTART_DCHANS


MESSAGE:

TIOS_WARN_FAULT: <component id>: FAULT=<fault id> <active or clear>

DESCRIPTION:

Indicates a change in an alarm state for the component specified in the message.


MESSAGE:

TIOS_WARN_SC_SSC_RCV: <component id>: Received Signal Channel Service State Change=<new service state>, Cause=<cause for change to new service state>

DESCRIPTION:

A service state change (SSC) event has been received.

Cause code translation:

0 = CAUSE_UNKNOWN

1 = CAUSE_NA

2 = CONFIG_FAIL

3 = LINE_FAIL

4 = LINKSET_FAIL

5 = LINK_FAIL

6 = ENGINE_RESET

7 = CAUSE_COMMANDED_OOS

8 = CAUSE_COMMANDED_IS

9 = SUPPORTING_ENTITY

10 = OOS_PENDING

11 = IS_PENDING

12 = TRAFFIC_PATH

13 = C7_SignalErr

14 = C7_BSNR_FIBR

15 = C7_LinkCongestion

16 = C7_AckDelay

17 = C7_LocalInhibit

18 = C7_RemoteInhibit

19 = C7_LocalBlocked

20 = C7_RemoteBlocked

21 = C7_LocalUninhibit

22 = C7_RemoteUninhibit

23 = C7_LocalUnblocked

24 = C7_RemoteUnblocked

25 = C7_LocalInhibitDeny

26 = CongLocal

27 = CongRemote

28 = CAUSE_ACTIVE

29 = CAUSE_STBY

30 = MGCP_HEARTBEAT_FAILED

31 = SRCP_HEARTBEAT_FAILED

32 = SRCP_AUDIT_GW_TYPE_FAILED

33 = SRCP_AUDIT_GW_SLOT_NUM_FAILED

34 = SRCP_AUDIT_GW_NUM_OF_LINES_FAILED

35 = SRCP_AUDIT_GW_BACKHAUL_PROTOCOL_FAILED

36 = SRCP_AUDIT_GW_CONTROL_PROTOCOL_FAILED

37 = SRCP_AUDIT_GW_COORD_PROTOCOL_FAILED

38 = SRCP_AUDIT_GW_NUM_OF_BACKHAUL_SESSIONS_FAILED

39 = SRCP_AUDIT_GW_CU_IP_ADDR_FAILED

40 = SRCP_AUDIT_GW_CU_IP_PORT_FAILED

41 = SRCP_AUDIT_GW_SU_IP_ADDR_FAILED

42 = SRCP_AUDIT_GW_SU_IP_PORT_FAILED

43 = SRCP_AUDIT_LINE_SIG_PROTOCOL_FAILED

44 = SRCP_AUDIT_LINE_CODING_FAILED

45 = SRCP_AUDIT_LINE_STATE_FAILED

46 = SRCP_AUDIT_LINE_LOOPBACK_FAILED

47 = C7_Prohibit

48 = C7_Restrict

49 = C7_SRT_PASSED

50 = C7_SRT_FAILED

SSC translation:

0 = UNDEFINED_TRANS

1 = CREATE

2 = DELETE

3 = COMMANDED_IS

4 = COMMANDED_OOS

5 = FAILED

6 = RESTORED

7 = RESET

8 = CONGESTION

9 = FORCED_OOS

10 = COMMANDED_INH

11 = COMMANDED_UNINH

12 = COMMANDED_EMRG_ALIGN

13 = ENG_IS

14 = ENG_OOS

15 = RESTART_DCHANS


MESSAGE:

TIOS_WARN_SC_SSC_XMIT: <component id>: Transmitted Signal Channel Service State Change=<new service state>, Cause=<cause for change to new service state>

DESCRIPTION:

A service state change (SSC) event has been sent.

Cause code translation:

0 = CAUSE_UNKNOWN

1 = CAUSE_NA

2 = CONFIG_FAIL

3 = LINE_FAIL

4 = LINKSET_FAIL

5 = LINK_FAIL

6 = ENGINE_RESET

7 = CAUSE_COMMANDED_OOS

8 = CAUSE_COMMANDED_IS

9 = SUPPORTING_ENTITY

10 = OOS_PENDING

11 = IS_PENDING

12 = TRAFFIC_PATH

13 = C7_SignalErr

14 = C7_BSNR_FIBR

15 = C7_LinkCongestion

16 = C7_AckDelay

17 = C7_LocalInhibit

18 = C7_RemoteInhibit

19 = C7_LocalBlocked

20 = C7_RemoteBlocked

21 = C7_LocalUninhibit

22 = C7_RemoteUninhibit

23 = C7_LocalUnblocked

24 = C7_RemoteUnblocked

25 = C7_LocalInhibitDeny

26 = CongLocal

27 = CongRemote

28 = CAUSE_ACTIVE

29 = CAUSE_STBY

30 = MGCP_HEARTBEAT_FAILED

31 = SRCP_HEARTBEAT_FAILED

32 = SRCP_AUDIT_GW_TYPE_FAILED

33 = SRCP_AUDIT_GW_SLOT_NUM_FAILED

34 = SRCP_AUDIT_GW_NUM_OF_LINES_FAILED

35 = SRCP_AUDIT_GW_BACKHAUL_PROTOCOL_FAILED

36 = SRCP_AUDIT_GW_CONTROL_PROTOCOL_FAILED

37 = SRCP_AUDIT_GW_COORD_PROTOCOL_FAILED

38 = SRCP_AUDIT_GW_NUM_OF_BACKHAUL_SESSIONS_FAILED

39 = SRCP_AUDIT_GW_CU_IP_ADDR_FAILED

40 = SRCP_AUDIT_GW_CU_IP_PORT_FAILED

41 = SRCP_AUDIT_GW_SU_IP_ADDR_FAILED

42 = SRCP_AUDIT_GW_SU_IP_PORT_FAILED

43 = SRCP_AUDIT_LINE_SIG_PROTOCOL_FAILED

44 = SRCP_AUDIT_LINE_CODING_FAILED

45 = SRCP_AUDIT_LINE_STATE_FAILED

46 = SRCP_AUDIT_LINE_LOOPBACK_FAILED

47 = C7_Prohibit

48 = C7_Restrict

49 = C7_SRT_PASSED

50 = C7_SRT_FAILED

SSC translation:

0 = UNDEFINED_TRANS

1 = CREATE

2 = DELETE

3 = COMMANDED_IS

4 = COMMANDED_OOS

5 = FAILED

6 = RESTORED

7 = RESET

8 = CONGESTION

9 = FORCED_OOS

10 = COMMANDED_INH

11 = COMMANDED_UNINH

12 = COMMANDED_EMRG_ALIGN

13 = ENG_IS

14 = ENG_OOS

15 = RESTART_DCHANS


MESSAGE:

TIOS_WARN_UNKN_LF: line <field name> type <value that is not recognize> is not recognized

DESCRIPTION:

The value specified in the field identified by the first parameter in one of the records in the physLineIf.dat file is not recognized.


MESSAGE:

TIOS_WARN_XMIT_AUDIT: <Message id>: XMIT AUDIT command <Command in the message>

DESCRIPTION:

Generated when a gateway audit message is sent.


MESSAGE:

UMC: CCodeModeFailed, Outgoing_Format_B, Country Code prefix addition failed, B Number = XXXXXXXX"

DESCRIPTION:

Call processing failed because of missing required country code digits.


Obsolete End User Log Messages

These end user log messages were deleted with the Cisco PGW 2200 Softswitch software release 9.4(1). Additional obsolete log messages are identified under the individual messages in the "End User Log Messages" section.

CP_CRIT_ASP_TYPE

CP_ERR_CRT_ASP

CP_INFO_RMG_INIT

PROT_ERR_AVM

PROT_ERR_VSI

PROT_ERR_VSI_MASTER

PROT_ERR_VSI_RESYNC_BADCKSUMBLK_EXCEEDED

PROT_ERR_VSI_RESYNC_CONNID_CMTSTATUSFAIL

PROT_ERR_VSI_RESYNC_CONNID_DELETEFAIL

PROT_ERR_VSI_RESYNC_CONNID_NOTFOUND

PROT_ERR_VSI_RESYNC_PENDLIST_ADDFAIL

PROT_ERR_VSI_RESYNC_PHYSIF_NOTFOUND

PROT_ERR_VSI_STATUSRESP_SENDFAIL

PROT_ERR_VSI_UNKN_MSGTYPE

PROT_WARN_VSI

PROT_WARN_WRITE_EVT

TIOS_ERR_ASP_MSG

TIOS_ERR_CARD_INIT

TIOS_ERR_COLL_ERR

TIOS_WARN_ASP_RESET

TIOS_WARN_ASP_SSC_RCV

TIOS_WARN_UNREC_ENUM

TIOS_WARN_XMIT_AVM

TAC Log Messages

The following log messages are intended to assist the Cisco Technical Assistance Center (TAC) in troubleshooting customer problems. Use of these messages frequently requires knowledge of the programming code used in the Cisco PGW 2200 Softswitch software. Therefore, these messages have not been described for the end user; they are listed here, in alphabetical order, for reference purposes only.

If you receive one of the following messages, contact the Cisco TAC for assistance. See the Preface for information about contacting the Cisco TAC.


Note These messages are intended for the Cisco TAC only.


CP_CRIT_ADD_CHGHNDLR: <class::method>: failed to add change handler

CP_CRIT_ADD_PROPTBL: <class::method>: failed to add engine properties table

CP_CRIT_ASP_TYPE: <class::method>: type for ASP is not specified in comType.dat table

CP_CRIT_CFG_EVTHNDLR: <class::method:<call<callid>>>:failed to install CFG event handler <event handler name>

CP_CRIT_CHPT_EVTHNDLR: <class::method: <call<callid>>>: failed to install CHPT event handler <event handler name>

CP_CRIT_CRT_MGRS: <class::method>: failed to create data mgr or call mgr

CP_CRIT_EVTHNDLR: <class::method: <call<callid>>>: failed to instantiate all event handlers

CP_CRIT_EXT_EVTHNDLR: <class::method: <call<callid>>> failed to install external event handler <event handler name>

CP_CRIT_FIND_CC_PARM: <class::method>: failed to find call-context file parm <parameter not found>, <reason>

CP_CRIT_FIND_MDL_PARM: <class::method>: failed to find MDL file parm <parameter not found>, <reason>

CP_CRIT_INIT_IMPEXP: <class::method>: failed to init MDL import/export parms

CP_CRIT_INIT_SIGS: <class::method>: failed to init signals

CP_CRIT_INT_EVTHNDLR: <class::method: <call<callid>>>: failed to install internal event handler <status string>

CP_CRIT_IOS_EVTHNDLR: <class::method: <call<callid>>>: failed to install IOS event handler <status string>

CP_CRIT_LOAD: <class::method>: failed to load <LCM or CC> from <fileName>

CP_CRIT_MML_EVTHNDLR: <class::method: <call<callid>>>: failed to install mml event handler <status string>

CP_CRIT_PROC_EVTHNDLR: <class::method: <call<callid>>>: failed to install PROC event handler <status string>

CP_CRIT_REGSERVICE: <class method>: failed to register <service name> service

CP_CRIT_REG_MDLFUNC: <class method>: failed to register mdl function <function name>

CP_CRIT_TALK2_EVTHNDLR: <class::method: <call<callid>>>: failed to install Talk2 event handler <status string>

CP_CRIT_TRC_HDR: <class::method>: failed to create trace header file (/tmp permissions?)

CP_ERR_ADD_CHGHNDLR: <class::method: <call<callid>>>: failed to add change handler

CP_ERR_ADD_CLIENT: <class method>: failed to add client

CP_ERR_ADD_MDLSIGNAL: <class method>: failed to add MDL signal <mdl signal Id> to engine-mdl signal table

CP_ERR_ADD_MEAS: <class method>: failed to add meas failed for <dest>

CP_ERR_ALLOC_MDL_TIMERS: <class::method: | class::method: call <callid>> Failed to allocate MDL timers for process <MDL process name> process id <MDL process id>

CP_ERR_ALLOC_MEM: <class::method: | class::method: call <callid>> Failed to alloc memory for class <class name>

CP_ERR_ASGN_BC: <class::method>: failed to assign, bearChan <bearChan ID> has no VSF

CP_ERR_AUDIT_CONGST: <class::method>: auditLoop application is congested

CP_ERR_AUDIT_SCHEDULE: <class::method>: auditLoop application is scheduled again

CP_ERR_AUEP: <class::method>: failed to audit the end point

CP_ERR_BAD_CALLSIDE: <class::method: <call<callid>>>: bad callside <callside>

If the callside value is 1, the failure occurred on the origination sigpath side.

If the callside value is 2, the failure occurred on the termination sigpath side.

CP_ERR_BAD_CKSUM: <class::method: <call<callid>>>: bad checksum for <file name>

CP_ERR_BAD_STREAM: <class::method: <call<callid>>>: bad stream

CP_ERR_BC_NOT_FOUND: <class::method: | class::method: call <callid>> Failed to find bear channel

CP_ERR_BOXNUM: <class::method>: failed to get boxnum: none <= <max boxnum>

CP_ERR_BUILD_MDL_MSG: <class::method: | class::method: call <callid>> Failed to build MDL message

CP_ERR_CALL_SCHEDULED_TWICE: <class::method: | class::method: call <callid>> Call got scheduled twice

CP_ERR_CALL_TERM_ABNORMALLY: <class::method: | class::method: call <callid>> Call has terminated abnormally <terminating cause>

CP_ERR_CHAN_MAP_IE_NOT_SUPPORTED: <either class::method: | class::method: call <callid>> Channel Map IEs not supported

CP_ERR_CREATE_CALL_FAILED: <class::method>:Could not create a new call

CP_ERR_CREATE_STBY_CALL_INSTANCE: <class::method: | class::method: call <callid>> Failed to create standby call instance

CP_ERR_CRT_ASP: <class::method>: failed to create auxSigPath

CP_ERR_CRT_BC_EXISTS: <class::method>: failed to create bearChan <bearChan ID>, already exists

CP_ERR_CRT_BC_VSF: <class::method>: failed to create bearChan <bearChan ID>, no VSF

CP_ERR_CRT_CALL: <class::method>: failed to create call on <pointCode>/<bearChan>

CP_ERR_CRT_MEAS: <class::method>: failed to create meas

CP_ERR_CRT_SIGPATH: <class::method>: failed to create sigPath <sigPath ID>

CP_ERR_CRT_SPAN: <class::method>: failed to create span <span ID>, sigPath <sigPath ID>

CP_ERR_CXN_EXIST: <class::method: <call<callid>>>: <type of connection> connection already exists

CP_ERR_DD_RETRV: <class::method: <call<callid>>>: failed to retrieve a record of record type <record type> key <key> from dynamic data store

CP_ERR_DEL_CHGHNDLR: <class::method>: failed to delete change handler

CP_ERR_DE_REG_WRITE_SERVICE: <class::method: | class::method: call <callid>> Failed to de-register write service

CP_ERR_DUP_ENDPOINT: <class::method>: duplicate endpoint <existing bearChan>, <bearChan with dup endpoint>

Configuration error message that indicates that the specified bearer channel has the same endpoint as a previously specified one.

CP_ERR_ENABLE_ACCESS: <class::method>: cannot enable engine system connection data access

CP_ERR_ENQUEUE_FAILED_IN_CALL: <class::method>: Failed to queue a command into <queue name> queue of call <call id>

CP_ERR_FILL_EXIST: <class::method: <call<callid>>>: handleStartTrace(Abnormal) file exists

CP_ERR_FIND_BC: <class::method: <call<callid>>>: cannot find bearChan <bearChan ID>

CP_ERR_FIND_BC_CALL: <class::method>: Call <call id> associated with the bearer channel <bearer channel identifier(sigpath id/span id/cic)> cannot be found in the call map.

CP_ERR_FIND_CALL: <class::method>: failed to find call on <pointCode>/<bearChan>

CP_ERR_FIND_CALL_FOR_CALLID: <class::method: <call<callid>>>: cannot find call for call id <call id>

CP_ERR_FIND_CALL_PROCESS: <class::method>: Could not obtain process <mdl process id> in call <signal name>.

CP_ERR_FIND_CLIENT: <class method>: failed to find client

CP_ERR_FIND_ENUM_ID: <class::method>: failed to find enum id <enum id>

CP_ERR_FIND_MASTER_DATA: <class::method>: No master data saved in call <call ID> for the signal <signal name>; hence not requeuing the signal

CP_ERR_FIND_MEAS: <either class::method: | class::method: call <callid>> Failed to find measurement <measurement name>

CP_ERR_FIND_MGCP_PARM: <class::method and add'l info>: Failed to find MGCP parameter <MGCP parameter name> in <MGCP message name> message

Indicates that the specified MGCP parameter is not found in the MGCP message.

CP_ERR_FIND_RANGE: <class::method>: failed to find range for <bearChan ID>

CP_ERR_FIND_SIGPATH: <class method>: failed to find the sigPth <sigPath Id> in usepool as it should be

CP_ERR_FIND_VC: <class::method>: failed to find virtChan <sigPath>/<virtChan>

CP_ERR_GET_CALL_PROC: <class method>: failed to find call control process <call side> in call <call Id>

CP_ERR_GET_CDR_MGR: <class::method: <call<callid>>>: failed to get CDR manager

CP_ERR_GET_CHPT_CONN_DATA: <class::method: | class::method: call <callid>> Failed to populate Ans connection data

CP_ERR_GET_EXTDATA: <class::method: <call<callid>>: failed to get external function data

CP_ERR_GET_MDL_DIR: <class::method>: failed to get MDL protocol dir <facility> <reason>

CP_ERR_GET_MDL_PROC_FROM_CALL: <class::method: | class::method: call <callid>> Failed to get MDL process id <MDL process id = mdlProcIdTP> from cmgCall object

CP_ERR_GET_NEW_CALL: <class::method: | class::method: call <call id>> Failed to get new call

CP_ERR_GET_OCC: <class::method: <call<callid>>>: cannot get originating call control process

CP_ERR_GET_OVLD: <class::method: <call<callid>>>: failed to get overload condition

CP_ERR_GET_PA: <class::method>: failed to get protocol adapter for sigPath <sigPath ID>

CP_ERR_GET_PARM: <class::method: <call<callid>>>: failed to get parameter id

CP_ERR_GET_PROC: <class::method>: failed to get orig process for call <call ID>

CP_ERR_GET_PROP: <class::method>: failed to get property value

Depending on which version or patch you are running, in some cases, this error message includes the missing propName property. The message description line "failed to get property value" that appears on the propName line gives more details, which may not be the same for some other versions or older patches.

Check the Cisco PGW 2200 Softswitch Release Notes on which version you are running, and if there is a patch available for that release, you can obtain more details on the properties message.

Example: CP_ERR_GET_PROP: cmgPropFunc::execute: UCID=0000037e, OSigPath=00150001, OTG=*NA*, OSPAN=*NA*, OTS/CIC=101, TSigPath=00140002, TTG=*NA*, TSPAN=o, TTS/CIC=1, propName=PostConnectToneDuration propEnum=62 side=1 location=1 failed to get property value

Call Side value - 0 = Orig, 1 = Term

For [Side =1], the parameter PostConnectToneDuration in properties.dat was missing. You can also run a unix difference command on the active or standby file properties.dat to check the difference. You can also verify from TAC to check the missing parameters in the property.dat file.

[Side =0] means that MDL is requesting to read the property values from the terminationg side of the call, but the call has not selected a TCC. When MDL wants to access this property, it sends the enum value to the engine and then from the start-up list, the engine identifies the property name and looks for it in the property.dat file.


Note The property names are case-sensitive.


CP_ERR_GET_SIGPATH: <class::method> failed to get sigPath for call <call ID>

CP_ERR_GET_SIGPATH_FOR_CALLSIDE: <class::method: <call<callid>>>: failed to get sigPath for callside <callside>

If the callside value is 1, the failure occurred on the origination sigpath side.

If the callside value is 2, the failure occurred on the termination sigpath side.

CP_ERR_GET_TCC: <class::method: <call<callid>>>: cannot get terminating call control process

CP_ERR_IE_NOT_FOUND: <class::method: | class::method: call <callid>> CALL_STATE information element is not found

CP_ERR_INCON_SLAVES: <class::method>: inconsistent slave values: <number of cics> cics > <number of bits> bits

CP_ERR_INIT: <class method>: failed to initialize <class name>

CP_ERR_INIT_CHPT_STBY_CALL_LEG: <class::method: or class::method: call <callid>> Failed to init <ORIG or TERM call side> call leg

The Cisco PGW 2200 Softswitch copies every incoming call data to the standby machine, so that in case of a failover, the standby has the data for current active calls and call states. To determine if the replicator is working properly on the standby system, use the command: rtrv-tc:all on both systems at approximately the same time.
If calls marked IN or OUT on the active system are all marked IDLE on the standby, there might be a problem.

Example: CP_ERR_INIT_CHPT_STBY_CALL_LEG: engChptMgr::handleStandbyAnswerChpt:call 155808 1 Failed to init ORIG call leg

CP_ERR_INIT_MDL_INF: <class::method: <call<callid>>>: failed to initialize mdl informer

CP_ERR_INIT_MDL_PROC: <class::method: | class::method: call <callid>> Failed to initialize MDL for process <process name>

CP_ERR_INIT_MDO: <class::method>: failed to init conversion def <protocol name> from MDO file <protocol file>

CP_ERR_INSERT_OBJ_IN_MAP: <class::method: | class::method: call <callid>> Failed to insert key <MAP key> in MAP <MAP table name>

CP_ERR_INSERT_PROC: <class::method>: Failed to insert cmgCallRefId into processedProcs, size = <proc size>

CP_ERR_INV_ARG: <class::method>: invalid args

CP_ERR_INV_ARG_FOR_TAG: <class::method>: invalid args for tagId <tag ID>

CP_ERR_INV_BC_IE: <class::method: | class::method: call <callid>> Bear Chan IE has invalid length

CP_ERR_INV_CALL_DIR: <class::method: | class::method: call <callid>> Invalid call direction

CP_ERR_INV_COMM: <application identifier> Invalid command <command type> for target <target type>

CP_ERR_INV_DATA_LEN: <class::method: | class::method: call <callid>> Invalid MDL data length <MDL data len>

CP_ERR_INV_ENUM_TYPE: <class::method: | class::method: call <callid>> Invalid enum type <MDL data len>

CP_ERR_INV_GWY: <application identifier> invalid gateway <gateway compid>

CP_ERR_INV_IDU_PARM: <class method>: <parameter name> <error reason>

CP_ERR_INV_LCM: <class::method>: invalid LCM checksum (CC version)

CP_ERR_INV_LEGID: <class::method>: incorrect LegId value

CP_ERR_INV_MDL_FUNC_GROUP: <class::method: | class::method: call <callid>> invalid MDL function group <MDL function group id>

CP_ERR_INV_MDL_PROC: <class::method: | class::method: call <callid> Invalid MDL process id process id

CP_ERR_INV_MGCP_VER: <class::method and add'l information>: MGCP version is not supported

Indicates that the MGCP version specified during provisioning is not supported.

CP_ERR_INV_MSG_LEN: <class::method: | class::method: call <callid> Invalid message length <message length in bytes>

CP_ERR_INV_NULL_SIGPATH: <class::method>: invalid null sigPath <sigPath ID>

CP_ERR_INV_PARM: <class::method: <call<callid>>>: invalid parameter <parameter> <cause>

CP_ERR_INV_PARMS: <class::method: | class::method: call <callid> Invalid parameter <parameter id>

CP_ERR_INV_PARM_COUNT: <class::method: | class::method: call <callid>> Invalid number of parameter <number of parameter>

CP_ERR_INV_PDUTP: <class::method: <call<callid>>>: invalid PDU type from sigPath <sigPath>

CP_ERR_INV_PROP: <class::method>: invalid property value <property value> for <sigPath ID>

CP_ERR_INV_RESTART_IND_IE: <class::method>: restart indicator IE has invalid length

CP_ERR_INV_SERVICE_STATE: <class::method: <call<callid>>>: invalid service state <channel service state>

CP_ERR_INV_SIGPATH: <application identifier> Invalid sigPath

CP_ERR_INV_SLAVE: <class::method>: invalid slave <cic> not in this group reset (<slave range>)

CP_ERR_INV_SPAN_ID: <application identifier> Invalid spanid <spanid>

CP_ERR_INV_STOP_COMMAND: <application identifier> bad status at event type = <event type>, event sub type = <event sub type>

CP_ERR_INV_TARGET: <application identifier> Invalid target <target type> for command <command type>

CP_ERR_IN_MGCP_MSG: <class::method and add'l info>: Incoming MGCP Message: <break down of incoming MGCP message content display>

Displays incoming MGCP message content upon failure of the transaction.

CP_ERR_LINK_MDL_PROC_TO_CALL: <class::method: | class::method: call <callid>> Failed to link MDL process to <ORIG or TERM call side> call context

CP_ERR_LOAD_MDL: <class::method: <call<callid>>>: failed to load MDL module <process name> from <protocol file name>

CP_ERR_LOAD_TBL: <class::method>: failed to load <table name> from <file name>

CP_ERR_MARKED_FOR_DEL_CALL: <class::method: | class::method: call <callid>> Call is marked for delete

CP_ERR_MDL_MSG: <group ID, message ID and error status>: Invalid MDL message <groupID (defined in MDL Engine Interface)>

CP_ERR_MDL_MSG_PARSE: <class::method>: message parse failed, call ID <call ID>

Indicates that the engine cannot parse a message from MDL.

CP_ERR_MDL_OBJ_PTR_IS_NULL: <class::method: | class::method: call <callid>> object ptr <cmgLcmProcCxt.m_lcmDef> is NULL for process <MDL process name>

CP_ERR_MISMATCH_SIGPATH: <application identifier> Mismatch sigpath data are <sigpath compid> and <sigpath compid>

CP_ERR_MSG_TOO_LONG: <class::method: | class::method: call <callid>> Message is too long

This error is linked to writing the given message buffer to a line. Part of the IOCC/PDU (network) message is sent out to a line. In this case, you need to run an MDL trace to find the reason for the error, or forward the details to TAC.

Example:

CP_ERR_MSG_TOO_LONG: cmgProtocolAdapter::outputNetEvent: UCID=000441ce, OSigPath=0014000e, OTG=*NA*, OSPAN=0, OTS/CIC=11, TSigPath=0015000e, TTG=*NA*, TTS/CIC=11, Meassge is too long.

CP_ERR_NO_ASCID: <class::method: <call<callid>>>: Remote ASC ID not set

CP_ERR_NO_MATE: <class::method>: failed to set call using, <bearChan ID> has no mate

CP_ERR_NO_TRK_IN_GRP: <class::method>:There is no trunk in trunk group <trunk group Id>

CP_ERR_NULL_CALLOBJ: <class::method: <call<callid>>>: null call object

CP_ERR_NULL_CALL_PROC: <class method>: null process found in the map for call reference <call reference id>

CP_ERR_NULL_PDU: <class::method: <call<callid>>>: null PDU

CP_ERR_OBJ_NOT_FOUND_IN_MAP: <class::method: | class::method: call <callid>> Failed to find key <MAP key> in MAP <MAP table name>

Part of a global call ID identifies the call to be deleted, which moves the call from a map of active calls to a map of deleted calls. This can happen in case of calls that had no connection ID as a result of hung conne4ctions on GW or GLARE, or the calls were cleared the first time on GW, but subsequent calls failed because variables in the MDL were not reset. In this situation the call status on the GW and the Cisco PGW 2200 Softswitch are out of sync.

Example:

CP_ERR_OBJ_NOT_FOUND_IN_MAP: engChptMgr::handleStandbyReleaseChpt: call 1854980 Failed to find key 1854980 in MAP engChptMgr.m chptCallIdMap

Action: Check call status on the gateway by using the command: show mgcp connection and on the Cisco PGW 2200 Softswitch by using the MML command: rtrv-tc: all

CP_ERR_OBJ_PTR_IS_NULL: <class::method: | class::method: call <callid>> object ptr <cmgLcmProcCxt.m_lcmDef> is NULL

This error is generated on calls which are routed across the EISUP link. Gateway properties are normally accessed through a bearChan, but no bearChan is available if the call is using an EISUP link. In such cases, the property should be obtained from the opposite call leg.

For example, an MGCP sigpath configured GWDefaultCodecString to construct the Local Connection Option to be used in CRCX. The engine is to get the Gateway properties from the terminating side, but if the engine state is not in the connect state, it will generate this error.

Action: Run an MDL trace in combination with Cisco snooper.

Example: CP_ERR_OBJ_PTR_IS_NULL: cmgPropFunc::execute: UCID=0002a331, OSigPath=00190004, OTG=*NA, OSPAN=*NA*, OTS/CIC=0, TSigPath=00190005, TTG=*NA*, TSPAN=0, TTS/CIC=0, object ptr rmgBearChan is NULL

CP_ERR_OPEN_FILE: <class::method: <call<callid>>>: failed to open file, errno <errno>

CP_ERR_OUT_MGCP_MSG: <class::method and add'l info>: Outgoing MGCP Message: <break down of outgoing MGCP message content display>

Displays outgoing MGCP message content in hex format upon failure of the transaction.

For example, if a Cisco PGW 2200 Softswitch doesn't receive the acknowledgement to the request it sends out before the mgcpRetxTimer (MGCP sigpath property) expires, it resends the request. The MGCP sigpath property mgcpRetxCount defines the maximum times of resending. After the Cisco PGW 2200 Softswitch performs the maximum times of resending, it removes the transaction of that request. If the acknowledgement to the request comes after the transaction of that quest is removed, the Cisco PGW 2200 Softswitch generates the CP_ERR_OUT_MGCP_MSG. Check the log information on routers and gateways to see if they hold back the acknowledgements to the requests that the Cisco PGW 2200 Softswitch sends out.

CP_ERR_PAIR: <class method>: <pair state> for sigpath <sigPathId>

CP_ERR_PDUMSG: <class::method: <call<callid>>>: Error PDU message sent to <sigPath>

CP_ERR_POPULATE_ANS_CHPT_CALL_LEG: <class::method: | class::method: call <callid>> Failed to populate <ORIG or TERM call side> ans checkpoint call leg

CP_ERR_POPULATE_ANS_CHPT_DATA: <class::method: | class::method: call <callid>> Failed to populate ans call chpt msg

CP_ERR_PRINT_CALL: <either class::method: | class::method: call <callid>>: failed to print call <callId>

CP_ERR_PRINT_MDL_MSG: <class::method: | class::method: call <callid>>: failed to print MDL message: groupID <groupID (defined in MDL Engine Interface)>, msgID <messageID (defined in MDL Engine Interface)>

CP_ERR_QUERY: <class::method>: data access query failed: <returned error message from the query>

CP_ERR_READ_PARM: <class::method>: failed to read parameter from extData

CP_ERR_REG_EVT: <class method>: failed to register events

CP_ERR_REG_PIPE_EVT: <class::method: | class::method: call <callid>> Failed to register communication event <communication event id>

CP_ERR_REG_READ_SERVICE: <class::method: | class::method: call <callid>> Failed to register read service

CP_ERR_REG_SVC: <class::method>: failed to register <object> for service <service name>

CP_ERR_REG_TBL: <class::method>: failed to register for <table name> table

CP_ERR_REG_WRITE_SERVICE: <class::method: | class::method: call <callid>> Failed to register write service

CP_ERR_RTRV_HDL_DBS: <class::method>: failed to retrieve handle to engDatabase

CP_ERR_RTRV_HDL_MDL_INF: <class::method>: failed to retrieve handle to rmgMDL_Informer

CP_ERR_RTRV_HDL_MDL_PROC: <class::method>: failed to retrieve handle to cmgMDLProcCxt

CP_ERR_SAVE_TCC: <class::method>: failed to save TCC info for call <call ID>

CP_ERR_SEND_ANS_MSG_TO_REP: <class::method: | class::method: call <callid>> Failed to send ans chpt msg to replicator

CP_ERR_SEND_CALLEVT: <class method>: failed to send message into call pointCode=<pointCode>, cic=<cic>

CP_ERR_SEND_MSG: <class::method: <call<callid>>>: failed to send message into call for <sigPath>

CP_ERR_SEND_MSG_TO_MDL_PROC: <class::method: | class::method: call <callid>> Failed to send message to MDL process

CP_ERR_SEND_MSG_TO_PROC: <class::method: <call<callid>>>: failed to send message into mdl process <process id> of call <call id>

CP_ERR_SEND_MSG_TO_REP: <class::method: | class::method: call <callid>> Failed to send Evt <XE Event id> and EvtSubType <XE Event Sub Type id> to replicator

CP_ERR_SET_ARG: <class::method: <call<callid>>>: failed to set args

CP_ERR_SET_INUSE: <class::method>: failed to set call using, <bearChan ID> in use by call <call ID>

CP_ERR_SET_MATED: <class::method>: failed to set call using, <bearChan ID> already mated

CP_ERR_SET_PROP: <class::method>: failed to set property value

CP_ERR_SIGNAL_MISMATCH: <class::method>:Discrepancy in the signals (<signals that are not matching>) stored in the master data and the signal command; hence not requeuing the signal

CP_ERR_SIGPATH_NOTAVAIL: <class::method> sigpath <sigpath component id> not available

CP_ERR_SIG_CALL: <class::method>: failed to signal call <call ID>

CP_ERR_START_MDL_PROC: <class::method: | class::method: call <callid>> Failed to start MDL process <MDL process name> process id <MDL process id>

CP_ERR_STREAM: <class method>: stream error

CP_ERR_UNEX_MSG: <class::method>: unexpected msg type <msg type>

CP_ERR_UNEX_TRAN: <class::method>: unexpected transition <state transition>

CP_ERR_UNKN_BLKTP: <class::method: <call<callid>>>: unknown block type <blocktype>

Example:

CP_ERR_UNKN_BLKTP: cmgMastertCallExtFuncData:: getData: UCID=01255bf8, OSigPath=00150002, OTG=00200004, OSPAN=*NA*, OTS/CIC=963, TSigPath=003e0001, TTG=*NA*, TSPAN=0, TTS?CIC=2001, unknown block type 258

Block Type = Decimal 258

= Hex 102 (0x102)

= 0x100 | 0x2

= (MML_BLK_BIT) | (BLK_MANUAL_LOCAL)

= Local Manual Block from MML

This is a valid value on a blocking type.

BLK_NONE = 0

BLK_AUTO_LOCAL = 0x0001 // HW fail - local

BLK_MANUAL_LOCAL = 0x0002 // Manual - local

BLK_AUTO_REMOTE = 0x0004 // HW fail - remote

BLK_MANUAL_REMOTE = 0x0008 // Manual - remote

L_BLK_BIT = 0x0100

PROPAGATION_BLK_BIT = 0x0200 // Local block due to MATE_UNAVAILABLE

UNSOLICITED_BLK_BIT = 0x0400

CP_ERR_UNKN_CMD1: <class::method>: unknown cmd <command>

CP_ERR_UNKN_COMPTYP: <class::method>: unknown compType in cxnSigPath <cxnSigPath ID>

CP_ERR_UNKN_MEAS: <class::method>: unknown meas <measurement> for sigPath <sigPath ID>

CP_ERR_UNKN_MSGTYPE: <class method>: unknown message type <message Type> received

CP_ERR_UNKN_MSG_MDL: <class::method>: unknown MDL message group <message group>, message type <message type>

CP_ERR_UNKN_PROTO_FAM: <class::method>: unknown protocol family for <protocol name>

CP_ERR_UNKN_PROTO_SIGPATH: <class::method>: unknown protocol <proto name> for sigPath <sigPath ID>

CP_ERR_UNKN_QUERY: <class::method>: unknown data access query <access query name>

CP_ERR_UNKN_REQTP: <class::method: <call<callid>>>: unknown request type <request type>

CP_ERR_UNKN_SEL_ALGO: <class::method>: unknown select algorithm <algorithm> for trunkGrp <trunkGroup ID>

CP_ERR_UNKN_TRUNKGRP: <class::method>: unknown trunkGrp type <trunkGroup type> for sigPath <sigPath ID>

CP_ERR_UNKNOWN: <class::method and add'l info>: Unknown software error

Unknown software problem. Indicates that design constraints have been violated.

CP_ERR_UNSPEC_PARM: <class method>: unspecified config parameter <parameter name>, status <status>

CP_ERR_UN_MATCHING_PA: <class::method: | class::method: call <callid>> Un-matching protocol adapter

CP_ERR_UPD_TBL: <class::method>: failed to update table <table name>

CP_ERR_UPD_TBL_PURGE: <class::method>: failed to update tables, purge failed

CP_ERR_VAL_BC: <class::method>: failed to validate bearChan <bearChan ID>

CP_ERR_VAL_DPC: <class::method>: failed to validate DPC <DPC ID>

CP_ERR_VAL_SIGPATH: <class::method>: failed to validate sigPath <sigPath ID>

CP_ERR_VIRTCHAN_NONDPNSS: <class method>: virtual chan for non-DPNSS sigpath <sigpath Id>

CP_ERR_VNET_GT_SIGPATH: < > vnet < > > max length 4 for sigpath <sigpath>

CP_ERR_VNET_TBL_INDEX: < > vnet tbl index < >, max 9999 for sigpath <sigpath>

CP_ERR_WRITE_SIGPATH: <class::method>: failed to write event to sigPath <sigPath ID>

CP_INFO_ABORT_CMD: Aborting the following command <string for command>

CP_INFO_AUDIT_IN_PROGRESS: <class::method>: audit already in progress

CP_INFO_CHAN_STATE: Mismatch in channel state, <channel state in Media Gateway and media gateway controller>, span <spanID>, channel <channel number>

CP_INFO_CLEAR_MISMATCH: <class::method and add'l information>: Clear mismatches between the Cisco PGW 2200 Softswitch and Gateway

MGCP audit endpoint has detected and resolved a mismatch. The mismatch can be due to hung resources in either the Cisco PGW 2200 Softswitch or the gateway.

CP_INFO_CRT_BCS: created <number of bearChans> bearChans

CP_INFO_CRT_BC_PAIRS: created <number of bearChan pairs> bearChan pairs

CP_INFO_CRT_BC_SIGPATH: created <num bearChans> bearChans for sigPath <sigPath ID>

CP_INFO_CRT_SIGPATH: created <number of sigPaths> sigPaths

CP_INFO_CRT_TRUNKGRP: created <number of trunk groups> trunkGroups

CP_INFO_DUMP_DATA: <data string>

CP_INFO_FIND_EXTFUNC: <class::method>:could not find extfunc data entry for <external function id> in call <call id>

CP_INFO_GRPSERV_COUNT: <class::method>: reached max count for checking group service complete

CP_INFO_INIT_CMD: command initialized <info string>

CP_INFO_INIT_HDLR: <class method> initialized

CP_INFO_LOAD_PROTO: loaded <protocol name> from file <filename>

CP_INFO_MDLSIGNAL_TBL: Build engine-mdl table: <number of signals> ASC signals

CP_INFO_MDL_ENABLE: <class::method and add'l info>: MDL enable interface

Indicates that MDL instructed the engine to enable endpoint interface.

CP_INFO_MDL_PERM_DISABLE_: <class::method and add'l info>: MDL permanently disable interface

MDL instructed the engine to permanently disable endpoint interface.

CP_INFO_MDL_TEMP_DISABLE: <class::method and add'l info>: MDL temporary disable interface

Indicates that MDL instructed the engine to temporarily disable endpoint interface.

CP_INFO_PROCESS_NOT_EXIST: <class::method>:Process <Process> in call <callId> no longer exists, so trashing the timer expiration event

CP_INFO_RESYNC_RESP: <class::method>: RESYNC RESP does not match previous RESYNC REQ sig path <sigPathID>, span <spanID>, discard message

CP_INFO_RMG_INIT: resource mgr init OK, local ASP ID = <ASP ID>

CP_INFO_RUNMODE: running in <SWITCHED or NAILED-UP> mode

CP_INFO_SET_ALARM: Alarm set: sigPath=<component name of the SigPath>, <span, bearer channel, and alarmIndex of alarm>

Indicates the scope of the alarm generated for the signaling path specified in the message.

span=<span>, bc=<bearer channel>, alarmIndex=nnn

CP_INFO_SSC_EVENT: <application log identifier> SSC FROM sigState <current sigpath state> TO sigTransState <transition sigpath state>

CP_INFO_START_AUDIT: Audit started

CP_INFO_START_TRACE: Start trace: trace log file <trace directory><trace filename>

CP_INFO_STOP_AUDIT: Audit stopped

CP_INFO_STOP_TRACE: Stop trace: sigPath <sigPathId>

CP_INFO_TEMP_LOGMSG: <temporary placeholder string for future defined message>

CP_INFO_UNSPEC_PARM: unspecified config param <parameter name>, will default

CP_TRACE_PRO_HEX_MSG: <protocol message in hex format>

CP_TRACE_STOP_COMMAND: <application identifier> event type = <event type>, event sub type = <event sub type>

CP_WARN_BAD_ENUM_VALUE: <class::method>: enum value is out of bound: enum tag =<enum tag>, enum value= <enum value>

CP_WARN_BC_NOT_CONFG: The bearChan for SigPath <sigPathID>, span <spanID>, cic <circuitID> is not configured

CP_WARN_CANT_CHG_AUD_STATE: <class::method> cannot change audit state from <old state> to <new state>

CP_WARN_CONGEST: <congestion info string>

CP_WARN_FIND_BC: cannot find bearChan <beachChan Id>

CP_WARN_FIND_CALL: <class::method> cannot find call obj with callId <callId>

CP_WARN_FIND_PROP: <class::method> could not find property <propName> for resource <compName>

CP_WARN_FIND_PROTO_ADAPTER: <class::method>: <Originating/Terminating side> protocol adapter corresponding sig path id <SigPathId> is zero. So, the check point data is being ignored. May be the engine is initialized with no data and is not yet synched with the master.

CP_WARN_FIND_SPAN: failed to find span <sigPath>/<span>

CP_WARN_GET_ALARM_CAT: <class::method>: failed to get alarm category: <alarm category>

CP_WARN_GET_PROT_ADAPTER: failed to get protocol adapter for sigPath <class::method>

CP_WARN_INSUFF_PA_ENTRIES: <class::method: | class::method: call <callid>> Insufficient protocol adapter entries

CP_WARN_INV_PARMS: <class::method: | class::method: call <callid>> Invalid parameter <parameter id>

CP_WARN_NO_BC_INIT: no bearChans (re)initialized

CP_WARN_PROT_ADP_DEL: <class::method> The last protocol adapter for sigPath <SigPath Id> was deleted, entering into special logic

CP_WARN_QUEUE_SIGN: <class::method: | class::method: call <callid>> [Thread:<XEThread>] This signal cannot be queued

CP_WARN_REG_READ_SERVICE: failed to register read service <service name>

CP_WARN_REG_WRITE_SERVICE: failed to register write service <service name>

CP_WARN_RESYNC: Audit:: resync response not received for sp <sigPathID>, span <spanID>

CP_WARN_SYNC: <class::method>: unable to send RESYNC REQ message for sigPath <sigpath Id>

CP_WARN_TEMP_LOGMSG: <temporary placeholder string for future defined message>

CP_WARN_UNSPEC_PROP_PTCODE: unspecified <property name> for pointCode <pointCode ID>, default=<default value>

CP_WARN_UNSPEC_PROP_SIGPATH: unspecified <property name> for sigPath <sigPath ID>, default=<default value>

CP_WARN_UNSPEC_PROP_TRUNKGRP: unspecified <property name> for trunkGroup <trunkGroup ID>, default=<default value>

CP_WARN_WRITE_MSG: <class::method>: can not write message to destination: Sigpath Id: <sigPath ID>

CP_WARN_WRITE_SIGPATH: <class::method>: cannot write to <sigPath ID>, state <sigPath state>

Indicates that this connection signal path is not in service.

ENV_CRIT_LOGSRVR_REREAD_REQUEST: Logger requested to reread component.dat

The LogServer has been notified that it should reread the components file in order to pick up any updates that might have been applied so that the component ID translation to MML name is accurate. THIS MESSAGE IS RESERVED FOR USE BY THE LOG SERVER ONLY.

ENV_ERR_ADD_ALM_FAIL: compId <MMLname[Component Id]>: Failed to add/register alarm id <Alarm Id>, category <Category>

ENV_ERR_ADD_CHG_HDLR: Component Chg Hdlr Add failed - status = <Error code>

ENV_ERR_ALM_CAT_FAIL: Alarm Cat <Alarm category> not found - Cannot <'set' or 'clear'> Alarm for comp <Component name>

ENV_ERR_ALM_COMP_FAIL: Component <Component name> not found - Cannot <'set' or 'clear'> Alarm Cat <Alarm category>

ENV_ERR_BIND: bind() failed for UDP IPC <Pathname>, status <Error code>

ENV_ERR_CONNECT: bind() failed for UDP IPC <Pathname>, status <Error code>

Indicates that a process has failed to open an IPC channel to another process in the system.

ENV_ERR_CRT_MUTEX: Failed to create XEMutex <Name of the mutex>

ENV_ERR_CRT_SHARED_MEM_KEY: Error creating shared memory key <Key string>, status <Error code>

ENV_ERR_CRT_SOCKET: Failed to create socket for IPC (<Pathname>), status <Error code>

Indicates that the application failed to create an IPC socket. The application will exit.

ENV_ERR_DATA_MGR: Data manager init failed - <Error code> (<Error code converted to a string>)

ENV_ERR_EVT_DISPATCH: Event dispatcher init failed - status = <Error code>

ENV_ERR_EVT_SIZE: Event size <Size of the event> different from buffer size <Size of the incoming buffer>

ENV_ERR_FIFO_READ: Bad return from FIFO read: Status <Error code>

ENV_ERR_INTERNAL: Internal error: <Error description string> - <Translation of XE Error code>

ENV_ERR_IPC_CANT_PUT: IPC Open failed - Error code = <Error code converted to string (strerr(errno))> Path <The FIFO that can't be accessed>

ENV_ERR_IPC_FLAG: Failed to <Set or Clear> <Description of the flag> for IPC fd <IPC File Descriptor>

ENV_ERR_IPC_MODE: Failed to <Set or Clear + <what was not set/cleared>> for <IPC pathname>, status <Error code>

ENV_ERR_IPC_NULL_SVC: IPC Open failed - Null Service

ENV_ERR_IPC_OPEN: IPC Open failed - Error code = <Error code converted to string (strerr(errno))> Bad Path <The FIFO that can't be accessed>

ENV_ERR_IPC_READ: IPC Read failed - Error code = <Error code converted to string (strerr(errno))> Bad Path <The FIFO that can't be accessed>

ENV_ERR_IPC_STAT: IPC Stat failed - Error code = <Error code converted to string (strerr(errno))> Bad Path <The FIFO that can't be accessed>

ENV_ERR_LICENSE: License could not be obtained - status = <Error code>

ENV_ERR_LOAD_SW_TBL: Failed to load SW Layout table - Status: <Error code>

ENV_ERR_LOAD_TBL: Error loading objects from file to <Table name> - Status <Error code> (<Error code, converted to a string>)

ENV_ERR_MAIN_LOOP: regAppMainLoop() called more than once

Indicates that the application has called this routine more than once. That should never happen.

ENV_ERR_POLL: Bad return from poll() - status = <Value of errno>

Indicates that the system call failed. Check the value of the status parameter to see what occurred.

ENV_ERR_REG_SW_TBL: Failed to register SW Layout table - Status: <Error code>

ENV_ERR_REOPEN_SERVICE: Can't reopen default service <Default service name>

ENV_ERR_SIGACTION: Sigaction error for sig num <Signal number>, status = <Value of errno>

ENV_ERR_STREAMS: Formatted Streams not supported - service: <Service name>

ENV_ERR_STREAM_GETMSG: Getmsg failed on fd <File descriptor>: Status <Error code> (<Error code, converted to a string>)

ENV_ERR_STREAM_INV_MODULE: <Name of the streams module> not a valid module - no modules pushed

ENV_ERR_STREAM_IOCTL: IOCTL (NREAD) failed on fd <File descriptor>: Status <Error code> (<Error code, converted to a string>)

ENV_ERR_STREAM_OPEN: STREAMS open failed: <Pathname that was being opened>: <Reason for failure>

Indicates that the system failed to open a stream object. The reason for the failure is displayed in the message.

ENV_ERR_STREAM_PUSH: Error pushing a Streams (<Pathname that was being opened>) module: <Name of the streams module>

ENV_ERR_THREAD_SPAWN: Failed to spawn thread: Detailed error info: <Description of error (attr_init_failed, set_stacksize)>

ENV_ERR_UNKN_SERVICE: Unknown service type '<Service description>' in configuration

ENV_ERR_UNSUPPORTED_IPC: Unsupported IPC mechanism (<IPC type>) - service: <Service name>

ENV_TRACE_IPC_OPEN: Opened buffered FIFO <Name of the FIFO> (fd = <File Descriptor>)

ENV_WARN_ACCESS_PSET_FAIL: Can't access processor set <Processor set>: Errno = <Unix Error code>

ENV_WARN_BIND_PROCESSOR_FAIL: Failed to bind <Process/thread name (from SW_Layout.cfg table)> to processor <Physical CPU number> - Status: <Error code>

ENV_WARN_BIND_PSET_FAIL: Can't bind to processor set <Processor set>: Errno = <Unix Error code>

ENV_WARN_EXTRA_FIELDS: Extra fields in service.dat ignored: <List of information from service.dat>

Indicates that the service.dat file is configured incorrectly.

ENV_WARN_NO_SW_LAYOUT_REC: Failed to find first SW_Layout record

ENV_WARN_REG_TBL: Failed to register component table with data mgr (<Error return from regTable routine>)

GEN_CRIT_ADD_SERVICE: Error adding <name of the service> service.

GEN_CRIT_ALLOCMEMFAIL: <class::method>: Failed to allocate memory for <type of object>

GEN_CRIT_EVTHDLCRT: <name of class::method>: Error creating event Handler <name of event handler>

GEN_CRIT_SERVICE_NOT_DEF: <undefined service> service not defined

GEN_ERR_ADD_ROUTE: <name of class/method> Unable to add route (<MMLname[component id]>)

GEN_ERR_ALLOC_EVT_FAIL: <Classmethod>: Could not allocate <name of event> <reason for failure or supplementary string>

GEN_ERR_ALM_CAT_FAIL: Alarm Cat <Alarm category> not found - Cannot <'set' or 'clear'> Alarm for comp <Component name>

GEN_ERR_ALM_CAT_NOT_FOUND: alarm category <name of the alarm category> not found in table <table name>

GEN_ERR_ALM_PRXY_PROC_FAIL: Cannot create <alarm name> XEAlarmProxy for process <process name>

GEN_ERR_BUFFOV: <name of the buffer> buffer overflow

Indicates an error has occurred due to overflow of an internal buffer.

GEN_ERR_CKSUM: <Facility name> CheckSum error on <Filename or connection name on which checksum error occurred> = <String containing the checksum value or further info on the error>

GEN_ERR_CORRUPT_INP: Corrupted input for <Name of component with corrupted input>

Indicates that internal creation of an alarm failed.

GEN_ERR_CPROCEXIT: <class::method name>: Child Process <process id> terminated with status = < >

GEN_ERR_DEPNT_GRP: <classmethod> <name of dependent> cannot be a dependent group - group does not exist.

GEN_ERR_DEPNT_PROC: <classmethod> <name of dependent> cannot be a dependent process - process does not exist.

GEN_ERR_DEP_CIRCLR: Dependency between <name of component> and <name of component> appears circular and will be ignored

GEN_ERR_DEP_GRP: <classmethod> Dependency <name of dependency> cannot be placed on group - group does not exist.

GEN_ERR_DEP_INV: Dependency between <name of component> and <name of component> invalid <further error info or a null string>

GEN_ERR_DEP_PROC: <classmethod> Dependency <name of dependency> cannot be placed on process - process does not exist.

GEN_ERR_DREG_SERVICE: Error De-Registering Service compId <component id of service>

GEN_ERR_EVTCRT: <Class::method>: Error creating event handler <name of event handler>

GEN_ERR_EVTHDLIDFIND: <class::method>: Could not find event handler with ID = <id of event handler>

GEN_ERR_EVTHDLNAMEFIND: <class::method>: Could not find event handler <name of the event handler>

GEN_ERR_EVTHNDL: <Classmethodeventhandler name> Cannot handle event of type <event type> <further info or an empty string>

GEN_ERR_EVTINIT: <class::method name>: Error initializing event handler <event handler name>

GEN_ERR_EVTINSTALL: <Class::method>: Could not install <name of event handler> event handler.

GEN_ERR_EVTNOTFND: <event handler> Cannot find originating event <further info or an empty string>

GEN_ERR_EVTREAD: <class::method>: Error reading message, Service ID=<name of service>, status=<status>

GEN_ERR_EVTWRITE: <name of class/method name>: Error sending message with event type <event type>, status = <status>

GEN_ERR_FIND: compId <Component Id>: Could not find <Name>

GEN_ERR_FOD_CXN_INV_STATE: <Facility name> Invalid state on read (<connection name>): '<supplementary info or a null string>'

GEN_ERR_FOD_SIGACT: Sigaction returned error for signal number <signal number>, errno: <error no>

GEN_ERR_FOVERD: <error string>

Generated by foverd to reflect the pertinent fault tolerant error information.

GEN_ERR_FREADSIZE: Error reading <name of file/fifo> with <bytes read> bytes, expected <bytes expected> bytes

GEN_ERR_GETFAIL: Could not get name of the object> id

Used only for VSI signaling channels.

GEN_ERR_HA_UNKNCMD: FT: Unknown command <command number> to local node

GEN_ERR_HLTH_ALM_PROC_FAIL: Failed to <'set' or 'clear'> health alarm for process <process name> <further info on error or null string>

GEN_ERR_IFINIT_FAIL: Could not initialize <interface name>: <format string used for logging a symbolic status code>

Indicates failure to initialize an interface such as the alarm manager.

GEN_ERR_IPCCREATE: <class::method>: Error creating <type of IPC <READ/WRITE/READWRITE> IPC for <:name of the service>

GEN_ERR_IPCOPEN: <class::method>: Error opening <type of IPC <READ/WRITE/READWRITE>> IPC for <name of the service>.

GEN_ERR_IPCPOLL: <class::method name>: Error polling IPC <IPC name or service name>, status=<status >

GEN_ERR_IPCREAD: <class::method name>: Error reading IPC <IPC name or service name>, status= <status >

GEN_ERR_IPCREADSIZE: Error reading IPC <IPC name> with <number of bytes read from IPC> bytes, <number of bytes expected> bytes expected

GEN_ERR_IPCWRITE: <class::method name>: Error writing IPC <IPC name or service name>, error: = <error no>

GEN_ERR_IPC_INIT: <class name> Error initializing <IPC name> IPC stat=<errorno>

GEN_ERR_LIBCFAIL: C Library call <name of the C Library function> failure <error code>

Indicates that an error was returned by a C library function.

GEN_ERR_MON_PROC_CRT: Attempt to create monitoring process <process name> failed, monitoring suspended.

GEN_ERR_MOOS_ALM_PROC_FAIL: Failed to <'set' or 'clear'> MOOS alarm for process <process name> <further info on error or null string>

GEN_ERR_OBJCRT_FAIL: compId <Component Id>: Instantiation of <name of the object being instantiated> failed in <is class::method name>

Used when object instantiation fails.

GEN_ERR_PCREAT: Cannot create process <process name> <format string used for logging a symbolic status code>.

Indicates that the process manager (ProcM) failed to start one of its processes.

GEN_ERR_PEVT_WRITE: Failed to write event to process <process name> <format string used for logging a symbolic status code>:

GEN_ERR_PEXEC: <class::method>: Failed to run process <name of process>, status = <value of errno>

GEN_ERR_PFORK: <Class::method name>: Failed to fork process <process name>, status = <value of errno>

GEN_ERR_PG_INV: Process group <process group name> invalid <further error info or a null string>

GEN_ERR_PG_RX_TIMER_NOTSUPP: Process group <process group name> received unsupported timer event

GEN_ERR_POLL: <class::method>: <name of timer or any name to indicate the error> polling error, status = <status>

GEN_ERR_PROC_CRASH_WITH_CORE: Process <process name> has crashed, Core file = <core file name>

Indicates core dump of a process and the name of the core file.

GEN_ERR_PROC_INV: Process <process name> invalid <further error info or a null string>

GEN_ERR_PTXN_PATH: Unable to build transition path for process <process name> <further info or an empty string>.

GEN_ERR_REC_DBASE: <classmethod> Recovery database error <further info on the error or a null string>

GEN_ERR_REC_DBASE_COMP: <classmethod> Recovery database error <further info on the error or a null string> for component <name of component>

GEN_ERR_REGSERVICE: <class::method name>: Could not register service <service name>, status = <status>

GEN_ERR_REGWR_SERVICE_PROC: <classmethod name> Error registering write service for process <process name> <format string used for logging a symbolic status code>

GEN_ERR_REM_OBJ: <classmethod> Error removing <further info or the type of the object> objects.

GEN_ERR_SERV_NOT_DEF: <service name> service not defined

GEN_ERR_SOCKET_FAIL: <name of socket that failed> socket call failed, <error string explaining why it failed>

Indicates that the call to the UNIX socket routine failed; displays the string equivalent of errno via a call to the strerror() function.

GEN_ERR_TIMERINIT: <class::method>: Failed to initialize <timer name> timers

GEN_ERR_TIMERSTART: <class::method>: Failed to start <name of timer> timer. <further information or an empty string>

GEN_ERR_TMDOUT_TXN: <event handler> Timed-out transaction <further info or an empty string>

GEN_ERR_TXN_DSTR: Error destroying transaction, tid <transaction ID> <further info or an empty string> <format string used for logging a symbolic status code>.

GEN_ERR_TXN_FIND: Failed to find transaction, tid <transaction ID>, for <facility name> <format string used for logging a symbolic status code>.

GEN_ERR_TXN_ORG_EVT: Failed to find orig event for <facility name> <format string used for logging a symbolic status code>.

GEN_ERR_UNKNEVT: <class::method>: received unknown event type:subtype <event type> :<event subtype>

GEN_ERR_UNKNPROT: compId <component id>: unknown Protocol Family, <protocol family number>

GEN_ERR_UNKN_ALARM: compId <component id>: Unknown Alarm <alarm name>

GEN_ERR_UNKN_COMPID: compId <component id of the component that generates the message>: unknown component Id <component id which is invalid>

GEN_INFO_ADD_LINK: compId <component id> :Unable to add link <line name / type (e.g. MTP3)>

GEN_INFO_ADD_LINKSET: compId <component id> :Unable to add linkset <name / type of linkset>

GEN_INFO_CLOSE_FD: Closed <File Descriptor for file or FIFO that was closed>

GEN_WARN_EVTCRT: Error creating event handler <name of event handler>

GEN_WARN_UNKN_ALARM: Unknown Alarm <name of unknown alarm>

GEN_WARN_UNKN_TIMER_EVT: <class:method name>: received unknown timer event type/subtype <event type>/<event subtype>

GEN_WARN_UNKWNEVT: <class::method | name of event handler>: received unknown event type:subtype <event type> : <event subtype>

MGMT_CRIT_ADDFAIL: Error adding <name of service> service

MGMT_CRIT_SRVC_UNDEF: <name of the service> service is not defined

Indicates that the channel manager service is not defined in the services.dat file.

MGMT_ERR_ADDOBJ: <class::method name>: Failed to add <name of the object>, status = <XE status>

MGMT_ERR_ARUINIT: <class::method name>: Failed to initialize ARU

MGMT_ERR_DMGR_NOTAVAIL: XEDataMgr not available

MGMT_ERR_DMNOTAVAIL: <class::method name>: Data Manager is not available

MGMT_ERR_EDITALM: Failed to <action <Add/Delete/Update>> alarm: compId <Component Id>, category <category>

MGMT_ERR_EDITCLT: Failed to <action <Add/Delete/Update>> a client of service ID <service id>

MGMT_ERR_EDITTBL: <class::method>: Failed to <action <PURGE/LOAD/REGISTER/DEREGISTER/RELOAD/UPDATE>> table <table name>

MGMT_ERR_FINDALMCAT: <class::method name>: Failed to find alarm category ID <alarm category ID>

MGMT_ERR_FINDOBJ: <class::method name>: Failed to find object <name of object> from table <name of the table>

MGMT_ERR_GETALMCLTLIST: <class::method>: Failed to get client list

MGMT_ERR_GETALMREGLIST: <class::method name> Failed to get alarm registration list

MGMT_ERR_INITDMPR: <class::method>: Failed to initialize <name of the dumper (could be measurement report or alarm dumper)>, status = <status>

MGMT_ERR_INVLD_PARAM: invalid parms: fd <fd number>, buf <contents of buffer>

MGMT_ERR_MMDBDETL: ODBC Error <ODBC error string>, TimesTen error <x10 error code>, ODBC rc <ODBC return code>

MGMT_ERR_MMDBSUM: Database error while '<action being performed>' (filename <filename>, line <line number>)

MGMT_ERR_MSG_TOOLARGE: message is too large (<size of message>)

MGMT_ERR_NOTAVAIL: < > not available < >

MGMT_ERR_OPEN_SERVICE: Failed to open <service name> service (<service id>)

MGMT_ERR_POM_COMMIT: <class::method>: commit failed, status = <status>

MGMT_ERR_POM_INVALID_RST_INDEX: <class::method name>: POM received invalid result index <index value>

MGMT_ERR_POM_PEERPROV: <class::method name>: Error <deploying/synchronizing> provisioning data by peer, status = <status of provisioning request>

MGMT_ERR_REGALM: Failed to <action of Add/Delete/Update> alarm registration, compId <component id>, alarm category <alarm category>

MGMT_ERR_RESETALMRELAY: <class::method name>: Failed to reset alarm state (<class::method name>) relay

MGMT_ERR_SENDALM: <class::method name>: Failed to send alarm event <type of alarm event> to client of service ID <service ID of the client>

MGMT_ERR_SETALMRELAY: <class::method>: Failed to set alarm state (<state <INFO/MINOR/MAJOR/CRITICAL>>) relay

MGMT_ERR_SNMP_MKTRAPVARBIND: <class::method name>: Failed to make trap varbind for <trap name>

MGMT_ERR_SNMP_REGALM: <class::method name>: Failed to register for receiving alarm report

MGMT_ERR_SRVC_NOTAVAIL: <name of service> service is not available in <name of module>

MGMT_ERR_TBLNAME: <class::method>: Invalid table name <name of table>

MGMT_INFO_MMDBALRT: MMDB ALERT: <alert string>

MGMT_WARN_FINDALM: Failed to find alarm, compId <component Id>, cat. Id <category Id>, service Id <service Id>

MGMT_WARN_FINDALMREG: <class::method name> Failed to find alarm registration of service ID <service id> and category ID <category id>

MGMT_WARN_FINDOBJ: Failed to find object <object name> from table <table name>

MGMT_WARN_MMDBDLCK: Database deadlocks occurred (<number of locks> detected)

MGMT_WARN_MMDBTIMO: Database lock timeouts occurred (<number of timeouts> detected)

MGMT_WARN_READ_EVNT: read event: < > retrnd < > bytes: < > expected

MGMT_WARN_WRITE_EVT: compId <component id>: write failed (<service name>) for <is the type of event> Event

MML_ERR_BLK_STATE_UNKN: compId <component id>: Unknown block state=<unknown block state>, cic=<cic>

PROT_CRIT_ADDFAIL: Error adding <name of service> service

PROT_CRIT_ALLOC_WRITE: Error allocating <is name of the area> area

PROT_CRIT_COMP_UNDEF: compId <component id>: component is not defined

PROT_CRIT_CREATE_THREAD_FAIL: Failed to create de-mux thread

PROT_CRIT_DPNSS: critical message from DPNSS: <text of critical message from DPNSS>

PROT_CRIT_ISDN: Fatal/Critical message from ISDN: <Text of the message>

PROT_CRIT_SRVC_UNDEF: <name of the service> service is not defined

Indicates an error in the services.dat file.

PROT_ERR_ADDFAIL: Error adding <name of the service> service

PROT_ERR_ADD_SESS: <component id>: Error adding session <name of session>

PROT_ERR_ALLOC_MSG: <class:method name>: Cannot allocate message area

PROT_ERR_ALLOC_SEND: Error allocating SSC to send to <component id> over IP

PROT_ERR_ALLOC_WRITE: Error allocating <string indicating where pdu was sent>

PROT_ERR_ATM_ADDPOLLDEV_FAIL: compId <componentId>: Error adding poll device <name of the interface>

Indicates the failure to add poll device.

PROT_ERR_ATM_ADDVPCI_FAIL: Add VPCI failed: <Error code converted to string (strerr(errno))>

Indicates the failure of a VPCI addition; the message is preceded by the file descriptor and VPCI value.

PROT_ERR_ATM_ADDVPCI_NOTINSERVICE: compId <componentId>: add vpci to a stream not in-service: <function name in which this call was made>

PROT_ERR_ATM_ATTACH_FAIL: ATM Attach failed: <Error code converted to string (strerr(errno))>

PROT_ERR_ATM_BWALLOC_FAIL: Bandwidth Alloc failed: <Error code converted to string (strerr(errno))>

Indicates the failure of ATM BandWidth allocation; preceded by the interface number.

PROT_ERR_ATM_DSL_NOTFOUND: compId <componentId>: no DSL was found: <function name in which this call was made>

PROT_ERR_ATM_FD_READ_FAIL: FD <File Descriptor> error reading data: <Error code converted to string (strerr(errno))>

PROT_ERR_ATM_INTF_OPEN_FAIL: ATM interface open failed: <Error code converted to string (strerr(errno))>

Indicates an ATM interface open failure; the message is preceded by the interface name.

PROT_ERR_ATM_NO_LOCAL_DSL: compId <componentId>: No local DSL available: <function name in which this call was made>

Indicates the nonavailability of local DSL.

PROT_ERR_ATM_SEND_FAIL: compId <componentId>: ioStreamSend error: <Error code converted to string (strerr(errno))>

PROT_ERR_ATM_SETRAW_FAIL: ATM Set RAW failed: <Error code converted to string (strerr(errno))>

Indicates the failure of ATM Set RAW; the message is preceded by the interface number.

PROT_ERR_ATM_STREAM_INUSE: compId <componentId>: stream already in use: <function name in which this call was made>

PROT_ERR_ATM_UNEXPECTED_POLL: <function name in which this call was made>: Unexpected polling event

PROT_ERR_AVM: AVM Error Message <general error string>

PROT_ERR_BAD_CMND: bad <name of the command> command

PROT_ERR_BSM_ADD_SESS: Failed to add session to group <group ID> with err <return code from adding session code.>

PROT_ERR_BSM_ADD_SESS_RET: Failed to add session with err < >

PROT_ERR_BSM_CRT_FAIL: Error creating Bsm object for session set < >

PROT_ERR_BSM_CRT_MISC: Failed to <error text> for <component id> with err <return code fog get session set id>

PROT_ERR_BSM_DEL_GRP: Failed to delete group <group ID> from set <set ID> with err <return code.>

PROT_ERR_BSM_DEL_SESS: Failed to delete session <session ID> from group <group ID> with err <return code.>

PROT_ERR_BSM_DEL_SET: Failed to delete set <set ID> with err <return code>

PROT_ERR_BSM_GRP_CONF: Session <session Id> already exists in group <group Id> which conflict with group <group Id>

PROT_ERR_BSM_PLAT_INIT: bsm platform_init failed <failure code from initialization of platform.>

PROT_ERR_BSM_RUDP_CONFIG: Failed to configure rudpParms for group <groupd Id> with err <error code>

PROT_ERR_BSM_SET_EXIST: Session set <set Id> already exists for <component Id>

PROT_ERR_BSM_SET_REG: Failed to register <component name> for session set <set Id> with err <error code>

PROT_ERR_BSM_STBY_GRP: Failed to standby session grp <group Id> set <set Id> with err <error code>

PROT_ERR_CCTC_NOT_ACTIVE: < >:CCTC not active

PROT_ERR_CCTC_NOT_STANBY: < >:CCTC not Standby

PROT_ERR_CRT_SESS_MNGR_FAIL: Failed to create Session Manager <error code>

PROT_ERR_DISCRD_TCP: <component id>: Discarding TCP DATA size =<size of packet>

PROT_ERR_DMGR_NOTAVAIL: XEDataMgr not available

PROT_ERR_DPNSS: Error message from DPNSS: <Text of the message>

PROT_ERR_ENG_PDU_TOO_BIG: Engine PDU (<component id>) for channel <channel> too large (<size of packet>)

PROT_ERR_ILLEGAL_STAT: Illegal SigChan status type

PROT_ERR_INIT: Cannot instantiate <Name of module it cannot instantiate.>

PROT_ERR_INVALID_MSGLEN: Invalid messageLength <message length> in KEEPALIVE, IPChan=<component id>

PROT_ERR_INVAL_STAT: Invalid State for <The device name. i.e Link> Ctrl request

PROT_ERR_INV_STAT: <component id> :procCtrlReq(), invalid status

PROT_ERR_INV_SWITCH: Switch type (<switch type number>) for <component id> is invalid

PROT_ERR_IP: IP Error Message <general error string>

PROT_ERR_ISDN: Error message from ISDN: <general error string>

PROT_ERR_KILL_SESS_MNGR: Error terminating Session Manager <error code>

Error codes:

0x51—Session does not exist

0x01—General failure

PROT_ERR_LX_FAIL: <class::method> for <component id> failed

PROT_ERR_MAKE_REASON: FT Make < >: reason < >

PROT_ERR_MSG_SEND_FAIL: <component id>: <name of the module>, failed to send msg

PROT_ERR_MTP: MTP Error Message MTP3 <general error string>

Error Code: SnUiSntUDatReq invalid ssf value 133 code 6: indicates a mismatch in the Service Indicator byte (which is an octet in the SS7 MTP2 message). This Service Indicator octet is mapped in the srvInfo variable in Cisco PGW 2200 Softswitch.

PROT_ERR_OPC_FIND: Can not find OPC <component id of IPC>

133 in binary is 10000101. The upper two bits that indicate national or international are set to 01, which means Spare, i.e., for international use. This error does not strictly mean that something wrong was sent on the wrire, but it can also come from an incongruence between the main Cisco PGW 2200 Softswitch engine and one of the SS7 IOCC (the processes that handle the SS7 input and output).

PROT_ERR_OPEN_SERVICE: Failed to open <service name> service (<service id>)

PROT_ERR_PATH_MAP_INSERT: Failed to add path <component id of path> to path map

PROT_ERR_POOL_MEM: Cannot get memory pool

PROT_ERR_PRIOCNTL_FAIL: PRIOCTL failed <error> start procM as root

PROT_ERR_PROC_IDU: <component id of sigpath>: procEngineIDU msg buf, sigPath OOS (<sigpath status>)

PROT_ERR_Q921: Q921 Error Message <general error string>

PROT_ERR_RCV_SSC_NON_ACTV: Received SSC in non-active state <component id>

PROT_ERR_RUDP_INIT_FAIL: Failed to initialize RUDP, return code=<return code>

PROT_ERR_SCHEDINFO: Schedinfo lid <lid id> rid <rid id>

PROT_ERR_SCHEDINFO_FAIL: Schedinfo failed for <is RT chmod +s Chan Ctrl>

PROT_ERR_SESS_MAP_INSERT: Failed to add chan <component id> to session map <return code>

PROT_ERR_SOCKETINIT: compId <component id> :Socket-init failed

PROT_ERR_SRCP_BLD_ACTION: compId <component id>: Cannot specify action with SRCP signals <encoded value of the signal>

Indicates that the SRCP message cannot be built because actions are not allowed with SRCP signals.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_BLD_CVID: compId <component id>: Unrecognized control vector <control vector id>

An unknown parameter, encoded in binary data stream format as a control vector, is present in the message received from the upper layer. An attempt will be made to skip over the unrecognized control vector, but the resulting message will probably be incomplete.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_BLD_CVLEN: compId <component id>: Incorrect length of control vector <control vector id>

Indicates that there is an inconsistency in the message (encoded in binary data stream format) received from upper layer, specifically the size of a particular parameter (control vector), and that building of the message has been aborted.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_BLD_EVT: compId <component id>: SRCP event <encoded value of the event> out of range

Indicates that the SRCP message cannot be built because the event specified is not in the associated package.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_BLD_REQEVT: compId <component id>: SRCP event <encoded value of the event> cannot be requested

Indicates that the SRCP message cannot be built because the requested event parameter specifies a non-requestable SRCP event.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_BLD_REQINFO: compId <component id>: Invalid SRCP requested info <encoded value of the requested info>

Indicates that the SRCP message cannot be built because the requested information parameter is invalid.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_BLD_SIGEVT: compId <component id>: SRCP event <encoded value of the event> cannot be signalled


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_PARSE_EPID: compId <component id>: Cannot parse SRCP endpoint id in <endpoint id>

Indicates that the SRCP message cannot be parsed because the endpoint ID is invalid (see RFC 821).


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_PARSE_EVTPARM: compId <component id>: Cannot parse SRCP parameter for <package>/<event which carries the parameter>

Indicates that the SRCP message cannot be parsed because it contains an event that carries an invalid or extraneous parameter.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_PARSE_LINE: compId <component id>: Cannot parse <message line>

Indicates that an entire line in the SRCP message cannot be parsed.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_PARSE_MSGTYPE: compId <component id>: Unknown or unexpected message type <message type>

Indicates that the SRCP message cannot be parsed because the message type is unknown or unexpected (for call agent).


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SRCP_RANGE_TXNID: compId <component id>: SRCP transaction ID <transaction id> out of range

Used by components that handle SRCP messages. It indicates an error due to an out of range transaction ID. SRCP transaction ID ranges from 1 to 999999999.


Note PROT_ERR_SRCP_ messages are no longer supported as of Release 9.6(1).


PROT_ERR_SWITCH_TYPE: compId <component id> :Switch type (<switch type>) is invalid

PROT_ERR_VSI: VSI : VSI Error Message <general error string>

PROT_ERR_VSI_MASTER: compId <Component Id>: VSI Master Error log <error log from Master>

Used to display information level messages from VSI master API.

PROT_ERR_VSI_RESYNC_BADCKSUMBLK_EXCEEDED: Bad Check sum blocks count <the number of bad checksum blocks>, exceeds Maximum number of checksum blocks <the maximum number of checksum blocks.>

Used when the bad checksum block count exceeds the maximum checksum block count.

PROT_ERR_VSI_RESYNC_CONNID_CMTSTATUSFAIL: Could not update Connection Id <connection ID> to CommitStatus <Commit status>

Used when the commit status of the specified connection ID could not be updated.

PROT_ERR_VSI_RESYNC_CONNID_DELETEFAIL: <is class::method name>: Could not delete connId <connection Id> from <the list (response list/resync data array)>

Used when the specified Connection ID could not be deleted from the specified list, that is, response list, resyncDataarray.

PROT_ERR_VSI_RESYNC_CONNID_NOTFOUND: <class::method name> Connection Id <Connection Id> not found in <the list (resyncDataArray or pending list or response list)>

PROT_ERR_VSI_RESYNC_PENDLIST_ADDFAIL: <is class::method name.>: Could not add request to pending list

Used when a request could not be added to the pending list.

PROT_ERR_VSI_RESYNC_PHYSIF_NOTFOUND: Could not find Physical Id for logical I/F Id <is the logical Interface ID.>

PROT_ERR_VSI_STATUSRESP_SENDFAIL: compId <component id>: Failed to send status response to IOCM

Used when the status response from the VSI fails to be sent.

PROT_ERR_VSI_UNKN_MSGTYPE: <class::method name>: Unknown message type <message ID received> received

Used when an unknown message type is received by the given object in the IOCC-VSI subsystem.

PROT_ERR_WRITE_FAIL: Write failed (<system error number (errno)>) for <name of the failing unit> Event (path: <component Id>).

PROT_ERR_WRT_BUFF: <component id>: procEngineIDU msg buf, error writing buffer (<size of buffer>)

PROT_ERR_XGCP_BLD_CVID: compId <component id>: Unrecognized control vector <control vector id>

Indicates that there is an unknown parameter (encoded in binary data stream format as a control vector) in the message received from upper layer. An attempt will be made to skip over the unrecognized control vector but the message built will probably be incomplete.

PROT_ERR_XGCP_BLD_MODE: compId <component id>: Invalid SGCP/MGCP mode <encoded value of the mode>

Indicates that the SGCP or MGCP message cannot be built because the mode parameter is invalid.

PROT_ERR_XGCP_BLD_MSGTYPE: compId <component id>: Invalid SGCP/MGCP message type <encoded value of the message type>

Indicates that the SGCP or MGCP message cannot be built because the message type specified is invalid.

PROT_ERR_XGCP_BLD_OFFLIMIT: compId <component id>: Traversing pass end of GDS

Indicates an inconsistency in the message (encoded in binary data stream) received from upper layer, specifically the length of the data stream; building of the message is aborted.

PROT_ERR_XGCP_PARSE_EPID: compId <component id>: Cannot parse SGCP/MGCP endpoint id in <endpoint id>

Indicates that the SGCP or MGCP message cannot be parsed because the endpoint ID is invalid (see RFC 821).

PROT_ERR_XGCP_PARSE_MAJVER: compId <component id>: SGCP/MGCP major version mismatch <major version number>

Indicates that the major version number in the SGCP or MGCP message does not match what this version of software supports.

PROT_ERR_XGCP_PARSE_MSGTYPE: compId <component id>: Unknown or unexpected message type <message type>

Indicates that the SGCP or MGCP message cannot be parsed because the message type is unknown or unexpected (for call agent).

PROT_ERR_XGCP_RANGE_TXNID: compId <component id>: SGCP/MGCP transaction ID <transaction id> out of range

Used by components that handle SGCP or MGCP messages. It indicates an error due to an out of range transaction ID. SGCP or MGCP transaction ID ranges from 1 to 999999999.

PROT_INFO_BSM_ACTI_GRP: Activate session grp <group Id> set <set Id>

PROT_INFO_MTP3_LSET_CNTL: Linkset <component Id> state change <transition state> cause <cause request>

PROT_INFO_MTP3_PC_CNTL: Point code <component Id> state change <transition state> cause <cause request>

PROT_INFO_Q921_LNK_CNTL: Q921 channel <component Id> state change <transition state> cause <cause request>

CP_INFO_SEND_MSG_TO_GW: <class::method and add'l info>: Failed to send MGCP message to Gateway

Indicates that the MGCP message was not sent to the gateway because either the connection signaling path is out of service (OOS) or the OLC/TLC is disabled.

PROT_TRACE_ASN_PDU: Hex dump of ASN messages <component Id> <from or to location> <the dump of the message>

PROT_TRACE_DPNSS_PDU: Hex dump of DPNSS messages <component Id> <from or to location> <the dump of the message>

PROT_TRACE_MTP3_PDU: Hex dump of MTP3 and UP messages <component Id> <from or to location> <the dump of the message>

PROT_TRACE_Q921_PDU: Hex dump of Q921 messages <component Id> <from or to location> <the dump of the message>

PROT_TRACE_RLM_PDU: Hex dump of RLM messages <component Id> <from or to location> <the dump of the message>

PROT_TRACE_SM_PDU: Hex dump of SM messages <component Id> <from or to location> <the dump of the message>

PROT_TRACE_UDP_PDU: Hex dump of UDP messages <component Id> <from or to location> <the dump of the message>

PROT_WARN_CHAN_NOT_CREATED: channel not created <component id>

PROT_WARN_CONFLIC_CONFIG: compId <component Id of channel>: Conflicting IP configurations w/ channels <component id of channel whose config is conflicting with the other channel>

PROT_WARN_DPNSS: DPNSS Warning Message <general error string>

PROT_WARN_IP: Warning message from IP: <Text of the message>

PROT_WARN_ISDN: Warning message from ISDN: < >

PROT_WARN_MTP3: MTP3 Warning Message <general error string>

PROT_WARN_NOPOLLIN: Received a message from a file descriptor that is not being polled.

PROT_WARN_POLLERR: POLLERR file descriptor <file descriptor number>

Indicates that the IOCC encountered an error while polling a file descriptor and has stopped polling that file descriptor.

PROT_WARN_PROC_CTRL_REQ: <component id> :procCtrlReq() <contents of buffer>

Received a message from the channel manager from channels that are not in service.

PROT_WARN_READFAIL: read failed (<system error number (errno)>) <internal component name> event (<event type>)

PROT_WARN_READ_EVNT: read event: <event type> retrnd <received message length> bytes: <expected message length> expected

PROT_WARN_RLM: compId <component id>: RLM should not be here

PROT_WARN_SERV_STAT_CHG: <component id>:procSSCMsgToChanMgr(), invalid status <status>

PROT_WARN_SRCP_PARSE_LONGCOMM: compId <component id>: Long SRCP comment truncated <comment>

Indicates that the SRCP message contains a long comment and only a truncated copy will be passed to the upper layer.


Note PROT_WARN_SRCP_PARSE_LONGCOMM: is no longer supported as of Release 9.6(1).


PROT_WARN_VSI: VSI Warning Message <general error string>

PROT_WARN_WRITE_EVT: compId <component id>: write failed (<service name>) for <is the type of event> Event

TIOS_CRIT_MSG_WRT_FAIL: msg write failed = <error code>

TIOS_CRIT_STPSCP_INDEX: STPSCP index = <STPSCP index value from STP.dat> is assigned to SSN = <SSN values in STP.dat associated with the STPSCP index> and SSN = <SSN values in STP.dat associated with the STPSCP index> in STP.DAT

TIOS_CRIT_TCAPSTACK: TCAP stack interface error. <Name of the stack function that returned an Error> failed. SSN =<Subsystem number>

TIOS_ERR_ADD: Failure adding component id of object attempted to be added>

TIOS_ERR_ADDOBJ: <compID>: Adding <the name of the object added>

TIOS_ERR_ASP_MSG: compId <component id>: Sending SSC with an unknown transition because signal=<component id of signal>

TIOS_ERR_BAD_SIDE: <component name> bad <DPNSS> side for sigpath <component Id>

TIOS_ERR_BUF_TOO_SMALL: <method name> - buffer size exceeded

TIOS_ERR_CARD_INIT: <name of the card> Card Instantiation

TIOS_ERR_COLL_ERR: ITK IO Card Statistics Gather Failure on card <card number>

TIOS_ERR_CREATELINE: Line create error compId <component id of the line>

TIOS_ERR_CRT_FAIL: <component id of channel controller>: Cannot create ioCC

TIOS_ERR_DATA_TABLE: Failed to load data table <Data table name>

TIOS_ERR_EVT_FAIL: Failed to write <event type (ex: control)> event on SVC <name of the svc>

TIOS_ERR_FIND: <component name> <auxiliary name> component type not found

TIOS_ERR_FORMT_INV: physLineIf: <component Id> - format <format in error> is invalid for CEPT carrier

TIOS_ERR_INTRNL_ERR: INTERNAL: <name of the internal object name> errors

TIOS_ERR_INV_IDU: <class::method> IDU message Error: <error reason>

TIOS_ERR_IPC_ERR: Received IPC Error from <indicates where error is coming from (ie. line card)> compId <component id of that component>

TIOS_ERR_MAP_FAM_FAIL: <component id of the pointcode>: FAILURE pc cannot map family <Point code family type that can not be mapped.>

TIOS_ERR_MEAS_ADD: Failed to add a measurement for <Component Id>, unknown measurement <Measurement name>

TIOS_ERR_MLTPL_PROT_ENTRS: (<component id of sigPath>) Multiple control protocol entries found to same GW in .dat files

TIOS_ERR_NO_TYPE_PC: <component id of point code>: Point code with no type

Indicates that the point code type of the parameter is unknown. Examples of point code types are ANSI, ETSI, NTT, and CHINA.

TIOS_ERR_NULL_PTR: <class::method name> - NULL GDS message pointer

TIOS_ERR_OPEN: channel compId <component id>: Failure opening Svc <buffer> <name of the svc>

TIOS_ERR_RUDP_ADD_DEL: <pointer to connection record>, rudpAddDeleteFd failed

TIOS_ERR_RUDP_ADD_FD: rudpAddDeleteFd, exceeded number of fds adding fd <file descriptor>

TIOS_ERR_RUDP_ALLOC_CONN: rudp_accept, connection failed to open

TIOS_ERR_RUDP_ALLOC_CREC: rudp_accept, failed to create new connection record

TIOS_ERR_RUDP_ARR_INVAL_STATE: rudpSegArrival, connection <pointer to connection record> invalid state <current state>

TIOS_ERR_RUDP_BUF_EMPTY: Send buffer empty in rudp_send()

TIOS_ERR_RUDP_BUF_FREE: rudpBufFree, failed buffer <pointer to connection record>

TIOS_ERR_RUDP_BUF_FREE_TWICE: rudpBufFree, buffer freed twice

TIOS_ERR_RUDP_BUF_GETSZ: rudpBufGetSz, failed buffer <pointer to buffer>

TIOS_ERR_RUDP_BUF_SETSZ: rudpBufSetSz, failed buffer <pointer to buffer>

TIOS_ERR_RUDP_BUF_TOO_LARGE: Buffer too large in rudp_send(). Received <number of bytes received>, max_allowed <maximum buffer size>

TIOS_ERR_RUDP_CLOSE: Cannot close server connection record, there are active clients

TIOS_ERR_RUDP_CLOSE_DATA: rudp_close, rudpWaitData failed

TIOS_ERR_RUDP_CLOSE_WAIT: Error - connection already being closed

TIOS_ERR_RUDP_CREC: Trying to remove connection, from <pointer to connection record (parent)>, which has no children

TIOS_ERR_RUDP_CREC2: Trying to remove connection <pointer to connection record>, from <pointer to connection record>, which is not a parent

TIOS_ERR_RUDP_CREC3: Trying to remove connection <pointer to connection record>, from <pointer to connection record>, list empty

TIOS_ERR_RUDP_CREC4: Trying to remove connection <pointer to connection record>, from <pointer to connection record>, not in list

TIOS_ERR_RUDP_DEL_FD: rudpAddDeleteFd, failed to delete fd <file descriptor>

TIOS_ERR_RUDP_INVAL_CONNID: Invalid Connection ID

TIOS_ERR_RUDP_INVAL_CONNTYPE: rudpAddDeleteFd, invalid connection type (<connection type>) adding fd <file descriptor>

TIOS_ERR_RUDP_INVAL_STATE: Error - invalid state

TIOS_ERR_RUDP_LISTEN_CREC: rudp_listen, cannot find connection record, error <error code>

TIOS_ERR_RUDP_LISTEN_INVAL_CREC: rudp_listen, invalid connection record, <pointer to connection record>

TIOS_ERR_RUDP_MAX_FD: Exceeded max number of file descriptors (RUDP)

TIOS_ERR_RUDP_MAX_RESYN: Connection <pointer to connection record>, maximum number (<number of soft resets>) of soft resets exceeded

TIOS_ERR_RUDP_MAX_RETRANS: Connection <pointer to connection record>, maximum number (<maximum number of retransmissions>) of retransmission exceeded

TIOS_ERR_RUDP_NEXT_CREC: rudp_next, cannot find connection record, fd <file descriptor>

TIOS_ERR_RUDP_NO_MORE_CREC: rudpConnAdd, no more connection records

TIOS_ERR_RUDP_OOS_QUEUE_EMPTY: rudpRemoveSentSegment, conn <pointer to connection record>out-of-sequence empty

TIOS_ERR_RUDP_QUEUE_EMPTY: rudpFront, connection <pointer to connection record> input queue is empty

TIOS_ERR_RUDP_SEM_WAIT: rudpFront, connection <pointer to connection record> sem_wait failed, rc = <return code>

TIOS_ERR_RUDP_TIMER: rudp_timer, NULL rudpFirstConn

TIOS_ERR_RUDP_WAIT_DATA: rudpWaitDat, connection <pointer to connection record> sem_wait failed, rc <return code>

TIOS_ERR_SCCP_CONFIG_FAIL: SCCP Config failed. Element=<Type of configuration that failed>,Instance=<Instance number>, reason=<reason.>

TIOS_ERR_SCCP_INVALID_EVT:Invalid event in SCCP prim <Event Id> spId <SCCP service provider ID> cause <Cause>

TIOS_ERR_SCCP_INVALID_MTP3_EVT:Invalid event in SCCP from MTP3 prim <Event Id> spId <SCCP service provider ID> cause <Cause>

TIOS_ERR_SCCP_INVALID_TCAP_EVT:Invalid event in SCCP from TCAP prim <Event Id> spId <SCCP service provider ID> cause <Cause>

TIOS_ERR_SCCP_ROUTING_ERR: SCCP ROUTING ERROR. UNKNOWN ROUTE.

TIOS_ERR_SCCP_SYNTAX_ERR: Syntax error in SCCP switch <Protocol variant> suId = <SCCP service user ID>

TIOS_ERR_SC_SSC_UNKWN: compId <component id>: Unknown <name of the SSC> SSC transition <state transition>

Indicates that the channel manager could not handle the SSC message from the channel controller.

TIOS_ERR_SIGPATH: sigpath create error compId <component id of SigPath>

TIOS_ERR_SIZE_NOT_MATCH: <Name of the method logging this error message> - buffer size does not match GDS length

TIOS_ERR_SSCTRANS: <location SSC origin> SSC transition Cause <the cause> default <default value>

TIOS_ERR_STACK_SWERR: Software error: FILE=<File name in which the error was detected>, LINE=<Line number>, ERRVAL = <Error Value>

TIOS_ERR_STREAM: <name of the class> stream error

TIOS_ERR_TCAPCONFIG: TCAP %s config not OK, Param = <Parameter associated with the error>

TIOS_ERR_TCAP_ENGINE: TCAP-ENGINE interface error. Bad or missing <Name of the parameter associated with the error>. msgType=<Message type>. param=<Parameter value>

Possible values for msgTypes are:

1 = CONST BEGIN_ID

2 = CONST CONTINUE_ID

3 = CONST END_ID

4 = CONST UNIDIRECTIONAL_ID

5 = CONST QUERY_WITH_PERMISSION_ID

6 = CONST QUERY_WITHOUT_PERMISSION_ID

7 = CONST RESPONSE_ID

8 = CONST CONVERSATION_WITH_PERMISSION_ID

9 = CONST CONVERSATION_WITHOUT_PERMISSION_ID

10 = CONST ABORT_ID

11 = CONST PROTOCOL_ABORT_ID

12 = CONST USER_ABORT_ID

13 = CONST RELEASE_ID

14 = CONST INFORMATION_ID

TIOS_ERR_TCAP_GEN_FAIL: <Name of the method> failed in <class::method>. Param =<Parameter>

TIOS_ERR_UNKNOUTPUT: compId <component id>: Unknown output < >

TIOS_ERR_UNKN_TRANS: Unknown <i.e CheckPt or UI> Transition <Transition id>

TIOS_ERR_UNKN_TYPE: <internal object name> - Unknown <internal component name> message type <message type>

TIOS_ERR_UNKN_VCTR_TYPE: <internal object name> - Unknown Control Vector type <control vector type>

TIOS_INFO_ADDOBJ: <is component ID>: Added

TIOS_INFO_FIND_IOCC_FAIL_CRT: <component id of channel controller not found>: Cannot find ioCC: <component id of new channel controller being created> - Creating

TIOS_WARN_ADDOBJ: Adding Object <name of the object> compId <component id of object>:

TIOS_WARN_ADD_DEVICE: Adding <component id of object> on device <name of the object>

TIOS_WARN_ADD_SIGPATH: Adding Lisup SigPath <component id of sigpath>

TIOS_WARN_ASP_RESET: <component id of ASP channel controller>: Receive Reset from ASP CC

Because ASP IOCC is no longer used, this message should never appear in the log file.

TIOS_WARN_ASP_SSC_RCV: < > : Received ASP SSC=< > CAUSE=< >

Because ASP IOCC is no longer used, this message should never appear in the log file.

TIOS_WARN_ATTACH_ROUTE: <component id of route>: Attaching Route to linkset=<component id of linkset>

TIOS_WARN_BAD_SIDE: <component name> bad <DPNSS> side for sigpath <component Id>

TIOS_WARN_CANT_WRT_EVT: Failed to write <event type> on SVC <name of the service>—must requeue

TIOS_WARN_DELOBJ: Deleting object <Component Id>

TIOS_WARN_DLD: IOCC <component id of channel controller being downloaded> is not downloaded.

TIOS_WARN_DONE_ADD_SIGPATH: Done adding Lisup SigPath <component id of SigPath>

TIOS_WARN_DPC_CONG:DPC Congstion for SigSrvc <SigSrvc component ID>

TIOS_WARN_EVT_FAIL: Failed Unknown <Event name> Event subtype=<subtype number>

TIOS_WARN_EVT_NOT_IMPL: <component Id>: FAILURE Event <message type> not implemented

TIOS_WARN_EVT_RCV: Received an unknown <Event name>. Event subtype=<subtype number>

TIOS_WARN_FIND: <component id> cannot find component name

TIOS_WARN_GEN_UNSIGNAL: <component id>: Generated unknown signal <sigid>

Indicates that the state machine for the component cannot handle the output signal.

TIOS_WARN_MAXCONFIG: Configured limit for <Name of the configured parameter> has reached. Limit=<Maximum configured value>

TIOS_WARN_MGMT_EVT_NOT_IMPL: <component id>: FAILURE mgmt event subtype=<subevent type> not implemented

TIOS_WARN_OBJNOTFND_MIB: compId <Component id of the object that was not found in the MIB.>: Entry not found in the MIB.

TIOS_WARN_PC_SSC_RCV: <component id for which SSC is received>: Received SC-SSC TRANSITION = <new state> CAUSE=<cause for the transition>

TIOS_WARN_PC_SSC_XMIT: <Component for which the SSC is transmitted>: Transmitted SC-SSC TRANSITION = <Requested transition> CAUSE=<Cause>

TIOS_WARN_RELOAD: Dynamic reconfig: Entering update handler for <name of data file>

Indicates that the update handler for the data file is invoked during dynamic reconfiguration.

TIOS_WARN_SP_SSC_XMIT: <component id>: Transmit SP-SSC TRANSITION= <Requested state transition>, CAUSE =<cause>

TIOS_WARN_SSC_TRANS: compId <Component Id>: XMIT SSC transition <Transition ID>

TIOS_WARN_STP_CONG:STP Congestion for SigSrvc <SigSrvc component Id>

TIOS_WARN_TCAP_GEN_DEL: Deleting <Object name being deleted>. Param = <Parameter>

TIOS_WARN_TIMER_EVT_NOBUF: Received timer event with no buffer

TIOS_WARN_UNKN_LCD_TP: line coding type < > is not recognized

This message is no longer used by the TIOS subsystem.

TIOS_WARN_UNREC: < > not recognized

This message is no longer used by the TIOS subsystem.

TIOS_WARN_UNREC_ENUM: < > enum < > is not recognized

Indicates that the cardtype parameter in one of the records in the physLineIf.dat file is not recognized.

TIOS_WARN_UNREC_INVRTR: Inverted HDLC type < > is not recognized

Indicates that there is a configuration error in the physLineIf.dat file.

TIOS_WARN_UNREC_LINE: line <parameter> type <value that is not recognized> is not recognized

Indicates that there is a configuration error in the physLineIf.dat file.

TIOS_WARN_UNSIGNAL: <component id>: unknown signal <signal>

TIOS_WARN_UNXP_TYPE: unexpected <name of the event> type <type of the event>

Indicates that there is a configuration error in the physLineIf.dat file.

TIOS_WARN_UPDOBJ: Failed to update %s, compId <component id of object>

TIOS_WARN_UPD_DEST: Update Destination <component id of destination>

Indicates that the destination is being upgraded during dynamic reconfiguration.

TIOS_WARN_XMIT_AVM: <Transaction number>: XMIT AVM SC-SSC trans < >

This message is no longer used by the TIOS subsystem.

MGCP Gateway Error Message for TAC

Cisco PGW 2200 Softswitch would flag a call as mute during Delete Connection (DLCX) if all the following conditions become true:

1. Cisco PGW 2200 Softswitch is configured in Fault Tolerance mode. (There is no need to have a Standby box. The XECfgParm.dat parameter *.desiredPlatformState should be set to either master or slave.)

2. The call was answered (i.e., the call was successfully cut-through).

3. Code 250 OK message was received with (P:) in response to DLCX.

4. Either PS=0 or PR=0 in (P:) (PS:package sent, PR:package received).

5. The call duration was more than 1 second.

Below is an example of an error log:

Tue Dec 31 11:29:22:322 2002 EST | engine (PID 10753) <Error>

Possible mute call detected--gateway error:callId (C:= 1), call duration = 2 sec

Other leg information:

Terminating Leg:GatewayName = mgcp200

connection Id (I:= AA075)

This leg information:callId (C:= 1)

GatewayName = mgcp200 on Orignating Leg groupId = 2

msgId = deleteConnectionAckMsg msgLenInBytes = 89

sigPath = ss7svc1 spanId = ffff cic/bc = 12

connection Id (I:= AA074) agent = SS7-ITU

connectionParameters = PS=102, OS=16320, PR=0, OR=24320, PL=0, JI=0, LA=0

returnCode = 250

transactionId = 194

ackComment = OK