Guest

Cisco Unified MeetingPlace

MeetingPlace Server Alarm Reference

Cisco - MeetingPlace Server Alarm Reference

Document ID: 50866

Updated: Jan 31, 2006

   Print

Contents

Introduction

This document provides a list of Cisco MeetingPlace server major, minor, warning, and info alarms. This document also includes alarm descriptions.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco MeetingPlace server software (all versions).

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Major Alarms

0x10014 Mutex unlock failed, errno=1, mutex id 4404060, attr 647

Definition

This alarm occurs when the Network Server is restarted and the CSes are not restarted. In this situation, the server tries to write the outdial statistics but it cannot because the Network Server was restarted. The outdial report is off. The musocket warnings are timeouts in the socket receive code.

Resolution

This does not affect anything and the errors go away.

0x10017 Invalid message size; size=1948, minimum=40, class=26, code=30

Definition

This message sees which module (=class) currently has trouble. class 26 = GWSIM agent. Each particular class has defined message codes. For GWSIMAGENT codes, 30 = PROCOUTPUT 50 = querygateway.

0x1001e Unable to obtain file lock on mailbox, errno=0

Definition

Scenario 1: An attempt was made to issue the command-line interface (CLI) potester command on a Cisco MeetingPlace 4.13 server. It is a known issue that the potester command does not work correctly in version 4.1.3, and there is a fix for it. However, it is not service-affecting or caused by customers. Only a Cisco technician or the system manager has access to this command.

Note: POTester is a Post Office box tester that can create and resolve Cisco MeetingPlace e-mail notification issues.

Scenario 2: An attempt was made to issue the potester command to clear the mailbox, but forgot to log in as superuser (su). You must be logged in as su in order to issue the potester command. However, the command is terminated if you let it sit for approximately three seconds. After you receive the terminated prompt, alarms 01001e and 101007c are generated.

Resolution

Solution for Scenario 2: You may have a hung POTester process. Kill the POTester process (CLI command), then rerun POTester to clean the mailbox.

0x1001f Message queue full

Definition

This error indicates that a lower priority task (such as constant monitoring) does not get cycle. This can cause server restarts.

0x10035 Trace Log error I/O error 28

Resolution

Complete these steps:

  1. Down the system.

  2. Log in as superuser (su).

  3. Issue the cd /usr/adm command.

  4. Issue the rm *trace.log command.

  5. Answer y to the prompt for deleting each trace file.

  6. Issue the restart enable command.

0x10036 Trace log: error returned by awrite(); error = 1450

Definition

Error Codes:

  • 1450 = Insufficient system resources exist to complete the requested service.

    33 = the file was locked when the operation was trying to occur

0x10044 Mutex destroy failed, errno=%d, mutex id %d, attr %d

Definition

This alarm is caused when the Network Server restarts without the restart of the CSes. In this situation, the server tries to write the outdial statistics but it cannot because the Network Server was restarted. Therefore, the outdial report is off. The musocket warnings are timeouts in the socket receive code.

0x10050 Disk key does not match database entry

Definition

A disk drive does not have a valid license key. This can indicate the drive was not initialized in manufacturing, that contents of the drive are damaged, or that someone has made an attempt to use a drive that is not from Cisco.

Resolution

Issue the hwconfig command in order to identify the bad drive, which you need to replace.

0x10051 Device[5] Unit[0] Slot[1] Port[0] I/O error reading or writing a disk drive

Definition

This error indicates a problem reading or writing to disk. Usually the next alarm describes the exact nature of problem encountered, such as minor alarm 0xa0015, "Fail to read all bytes, req=0, read=200".

0x10088 Invalid or conflicting server record for unit #xx

Definition

Unit xx is attached to a Cisco MeetingPlace server. Unit xx is not removed with the proper procedure, and then the hostname or IP address of the Windows NT gateway is changed. When the Windows NT gateway tries to connect to the Cisco MeetingPlace server, the Ethernet address matches, but the hostname or the IP address does not.

Resolution

Complete these steps.

  1. On the Cisco MeetingPlace server, issue the net command in order to deactivate unit 11.

  2. On the Windows NT gateway, stop all Cisco MeetingPlace services. In the gateway system integrity manager (GWSIM) administrator user interface (UI), click Delete Unit.

  3. After the unit is removed from server database, the Delete Unit button changes to Add Unit. Click the Add Unit button in order to reattach the gateway to the server.

0x20003 Gen DB Free Lock Failed. Status = 1

Definition

This indicates that the server has been unable to free a database mutex within the Conference Scheduler (CS). If the mutex is truly broken, there are Raima errors in the log.

Resolution

If this happens while the system comes up or goes down, ignore it. If there are other Raima errors, escalate.

0x2001e Cannot log into the SIM

Definition

The Conference Scheduler (CS) attempts to come up, but it is not allowed to log into the system integrity manager (SIM).

Resolution

Usually when this happens, a duplicate CS is manually started. If this is the case, then ignore the alarm. If the CS comes up and this happens, make sure that the other modules are correctly started. Also, make sure there is no other CS that runs in the background (issue the ps ax command and look for ConfSchd in the output). If another CS runs, stop it. Also, make sure the SIM is up and running. If not, start the SIM before you start the CS.

0x2004a Cannot open the MSC for conferences Err = aa

Definition

This alarm means that the Conference Scheduler (CS) cannot see the Master Switch Controller (MSC) card when it comes up.

Resolution

Make sure the MSC card is there and functional. Make sure that the device driver for the MSC is loaded successfully when the system came up. If you cannot get it, issue the vt msc command in order to access the card, and then reboot and try again. (These steps must be done on either the stand-alone server or the conference server). If the problem persists, then the card is either bad or is not seated correctly on the PCI bus.

0x20064 Init conf failed. Err = 170

Definition

On startup, the Conference Scheduler (CS) is unable to initialize everything it needs in order to start. The most likely scenario is that it cannot initialize the Master Switch Controller (MSC).

Resolution

If this alarm appears after the alarm 0x2004a, it means that the conference scheduler will not come up. If a different alarm precedes this alarm, that alarm explains the problem.

0x20078 The CS is behind X seconds. Conf Y, Next Event Z

Definition

The Conference Scheduler has to perform some action for a conference (unique ID, decimal format Y) x seconds ago. For some reason, it was unable to do so, and now it re-executes those scheduled actions and realizes that it is x seconds past the activity completion time.

The event codes are:

 2: generic start conference
 3: send out a reminder for a conference.
 4: page people at the start of a conference (alpha numeric .. not yet supported)
 5: call people (blast outdial) at the start of the conference (includes numeric pagers)
 6: call other servers at the start of the call
10: alarm to say that the VUI cannot start the conference like it has been told.
11: end the conference because no one showed up
12: retry calling people because they have not answered the first time
16: Give the warning prompt
17: Tell people that they have extra time.
18: See if you can extend the conference. Tell people one way or another.
19: Free resources at the end of the conference.
21: Purge the conference from any voice
22: Delete the existence of the conference.

Resolution

  • Ignore if this happens once in awhile for a short period of time.

  • Ignore if the system was down for awhile and has just been brought online.

  • Ignore if an old database was restored onto the system.

  • Escalate if this happens in the normal course of the day for an extended period of time.

The exact event that was late is described based on the event. A known case is when ConfSchd fails to allocate conferences, which causes system restarts. In order to verify this, kill the ConfSchd process in order to force a core dump. (Issue the kill -7 xx command, where xx is the ConfSchd process id from the ps -ax command output.) Retrieve the core for analysis.

0x3003c Trouble with the sim... Err = XXX

Definition

The Voice User Interface (VUI) is unable to log into the system integrity manager (SIM).

Resolution

Usually when this happens, it is because a duplicate VUI is manually started. If this is the case, then ignore the alarm. If the VUI comes up and this happens, make sure that the other modules are started correctly. Also, make sure there is no other VUI that runs in the background (issue the ps ax command and look for VUI in the output). If another one is running, stop it. Also, make sure the SIM is up and running. If not, start the SIM before you start the VUI.

0x30093 Bad NW Hangup. Port XXX, VUI Port YYYY, Session ZZZZ

Definition

The Voice User Interface (VUI) receives a hang up from the public switched telephone network (PSTN) for a call that it does not know about. This can happen at startup when there are calls that come in before the VUI is ready. It can also happen on a heavily loaded system on which many people hang up at once and the system cannot handle the instantaneous influx of messages.

Resolution

If this happens on startup, ignore it. If this happens once in awhile when the system has been up for awhile, ignore it. If there are many of these messages, especially on the same port, then the port is probably hung and you need to escalate the problem.

0x30095 No cp msg pending. Port XXX, State 0, OutMsg 524288

Definition

A cpserver message arrives for the Voice User Interface (VUI), but the VUI does not care. At one time it did care, but now it has decided to give up on the message and move on. The cpmessages are:

CP_ANSWER = 0x01, CP_CLOSEFILE = 0x02,
CP_DELETEFILE = 0x04, CP_DISCONNECT = 0x08,
CP_DUPFILE = 0x10, CP_OPENFILE = 0x20,
CP_OUTPULSEDIGITS = 0x40, CP_PAUSEPLAY = 0x80,
CP_PAUSERECORD = 0x100, CP_PLACECALL = 0x200,
CP_TRANSFER = 0x400, CP_PLAYFILE = 0x800,
CP_PLAYFILELIST = 0x1000, CP_RECORD = 0x2000,
CP_RESERVEFILE = 0x4000, CP_RESUMEPLAY = 0x8000,
CP_RESUMERECORD = 0x10000, CP_SEEKFILE = 0x20000,
CP_STOPPLAY =    0x40000, CP_SETCONFMODE =  0x80000,
CP_STOPRECORD = 0x100000, CP_CHECKIFDIAL = 0x200000,

This usually happens because the VUI times out while it waits for the cpserver. This can happen when a message gets dropped by the system under heavy load. Look for major and minor messages in the alt log during this period of time.

For each of these occurrences, one port is affected. In order to see if a user is affected, check the message type. If it is a play file, then it is probably affected; if it is a disconnect, then it probably is not affected.

Resolution

If a T-span goes down or numerous people hang up at once (such as at the end of a conference), ignore the alarm. If you see this alarm on a PCI system, take note and write up a case. This should only be seen on old 486 Extended Industry-Standard Architecture (EISA) systems.

0x3009d Session Number 151 too big

Definition

The Voice User Interface (VUI) is overwhelmed with requests. On a 120-port system, the VUI has 150 sessions from which it can handle incoming and outgoing calls. If there are back-to-back conferences that require outdials in order to start the meetings, this error is likely to occur.

Resolution

The next conference should eventually start because most systems are configured to retry failed outdial attempts. If the overbook parameter is not set to high in order to force the first set of conferences to end so that room is made for the starting set, then all is well. If the second set of conferences cannot eventually start because the first set never goes away, then the overbook is probably too high on their system.

0x52400 Raima error xxx (-xxx) errno xxx

Definition

This code generically indicates that the low-level database functions have detected a fault. In many cases this is a warning about corruption in the database structures. In other cases, it indicates defects which may or may not be severe.

These are the Raima error codes (included for information only):

/* -------------------status codes-------------------- */
/* user errors */
#define S_USER_FIRST -1       /* first user err */
#define S_DBOPEN    -1        /* database not opened */
#define S_INVSET    -2        /* invalid set */
#define S_INVREC    -3        /* invalid record */
#define S_INVDB     -4        /* invalid database */
#define S_INVFLD    -5        /* invalid field name */
#define S_INVADDR   -6        /* invalid db_address */
#define S_NOCR      -7        /* no current record */
#define S_NOCO      -8        /* set has no current owner */
#define S_NOCM      -9        /* set has no current member */
#define S_KEYREQD   -10       /* key value required */
#define S_BADTYPE   -11       /* invalid lock type */
#define S_HASMEM    -12       /* record is owner of non-empty set(s) */
#define S_ISMEM     -13       /* record is member of set(s) */
#define S_ISOWNED   -14       /* member already owned */
#define S_ISCOMKEY  -15       /* field is a compound key */
#define S_NOTCON    -16       /* record not connected to set */
#define S_NOTKEY    -17       /* field is not a valid key */
#define S_INVOWN    -18       /* record not legal owner of set */
#define S_INVMEM    -19       /* record not legal member of set */
#define S_SETPAGES  -20       /* error in d_setpages (database open or bad param) */
#define S_INCOMPAT  -21       /* incompatible dictionary file */
#define S_DELSYS    -22       /* illegal attempt to delete system record */
#define S_NOTFREE   -23       /* attempt to lock previously locked rec or set */

#define S_NOTLOCKED -24       /* attempt to access unlocked record or set */
additional details:  The system was trying to access a record and expected it to be 
locked and it was not locked. One way this can happen is when reports are running and 
another module try to access the database.  This is nothing to be concerned about 
unless it happens repeatedly

#define S_TRANSID   -25       /* transaction id not be supplied */
#define S_TRACTIVE  -26       /* transaction already active */
#define S_TRNOTACT  -27       /* transaction not currently active */
/* -28 */
#define S_TRFREE    -29       /* attempt to free a lock inside a transaction */
/* -30 */
#define S_NOTRANS   -31       /* attempted update outside of transaction */
#define S_EXCLUSIVE -32       /* functions requires exclusive db access */
#define S_STATIC    -33       /* Attempted to write lock a static file */
#define S_USERID    -34       /* No user id exists */
#define S_NAMELEN   -35       /* database file/path name too long */
#define S_RENAME    -36       /* invalid file number passed to d_renfile */
#define S_NOTOPTKEY -37       /* field is not an optional key */
#define S_BADFIELD  -38       /* field not defined in current record type */
#define S_COMKEY    -39       /* record/field has/in a compound key */
#define S_INVNUM    -40       /* invalid record or set number */
#define S_TIMESTAMP -41       /* record or set not timestamped */
#define S_BADUSERID -42       /* invalid user id - not alphanumeric */
#define S_NONETBIOS -43       /* NetBIOS is not installed on machine */
/* -44 */
/* -45 */
#define S_NOTYPE    -46       /* No current record type */
#define S_INVSORT   -47       /* Invalid country table sort string */
#define S_DBCLOSE   -48       /* database not closed */
#define S_INVPTR    -49       /* invalid pointer */
#define S_INVID     -50       /* invalid internal ID */
#define S_INVLOCK   -51       /* invalid lockmgr communication type */
#define S_INVTASK   -52			/* invalid task id */
#define S_NOLOCKCOMM -53      /* must call d_lockcomm() before d_open() */
#define S_NOTIMPLEMENTED -54  
#define S_USER_LAST -54       /* last user error */

/* system errors */
#define S_SYSTEM_FIRST -900   /* first system error */
#define S_NOSPACE   -900      /* no more space on file */
#define S_SYSERR    -901      /* system error */
#define S_FAULT     -902      /* page fault -- too many locked pages */
#define S_NOWORK    -903      /* no working file set in dio */
#define S_NOMEMORY  -904      /* unable to allocate sufficient memory */
#define S_NOFILE    -905      /* unable to locate a file */
#define S_DBLACCESS -906      /* unable to access db lock file */
#define S_DBLERR    -907      /* db lock file open/access error */
#define S_BADLOCKS  -908      /* inconsistent database locks */
#define S_RECLIMIT  -909      /* file record limit reached */
#define S_KEYERR    -910      /* key file inconsistency detected */
/* -911 */
#define S_FSEEK     -912      /* Bad seek on database file */
/* -913 */
#define S_READ      -914      /* Bad read on database/overflow file */
#define S_NETSYNC   -915      /* Network synchronization error */
#define S_DEBUG     -916      /* Debugging check interrupt */
#define S_NETERR    -917      /* Network communications error */
#define S_RECOVERY  -918      /* Auto-recovery is about to occur */
#define S_WRITE     -919      /* Bad write on database/overflow file */
#define S_NOLOCKMGR -920      /* Unable to open lockmgr session */
#define S_DUPUSERID -921      /* DBUSERID is already used by someone else */
#define S_LMBUSY    -922      /* The lock manager is busy */
#define S_DISCARDED -923      /* attempt to lock discarded memory */
#define S_SEM       -924      /* unable to open semaphore */
#define S_LMCERROR  -925      /* New Network layer error code */

Resolution

Raima 905—Some (one or more) key files are missing or corrupted. Issue the cmdbcheck and cmdbfix commands. Contact Cisco Technical Support. Compare a /lat/db directory listing against a good Conference Server (CS) to see what is missing, if anything. The problem can also be caused by a corruption inside a file, in which case nothing shows externally. The causes of the problem are many and include filesystem/disk glitch, power glitches and any other outages before the server was properly downed. Reboot the system or kill the system integrity manager (SIM) when a system appears to have trouble when it comes up.

Raima 910—Schedule down time at the earliest opportunity and issue the cmdbfix command. For other errors, if the problem frequently occurs, restart the system. In all cases, you need to report the problem to engineering since it indicates a defect. These errors can also appear when the root or database file systems have been corrupted. The fsck command may be able to diagnose and repair the disk in these situations.

0x52424 DB main exited by quit with error code 65570

Definition

The database server detects an unrecoverable error and exis. One possibility is that the database lock files are corrupt.

Versions affected: This error was discovered in Cisco MeetingPlace version 4.2.x, but the same code exists in the current 5.1.1 and 5.2.0 versions.

Resolution

If you encounter this alarm in combination with a 0x10022 (Open failed, errno=6) information log, as illustrated here, and the system restarts multiple times and is unable to bring up all Cisco MeetingPlace modules, down the system (important), delete the files in the /tmp/dbtasklocks directory, and restart the system.

04/12 20:14:58 INFO 0x10022  3/15, "libdbtask.cc", 294 (0x6, 0, 0, 0)
                    Open failed, errno=6
04/12 20:14:58 MAJ  0x52424  3/15, "db.cc", 362 (0x10022, 0, 0, 0)
                    DB main exited by quit with error code 65570

0x5242c DB server reroute (send) failed code %d

Definition

See error 0x52441 and the fail code list.

0x52440 DB api SendMsg failed code 160 msgseq 6 msgcode 118 and 0x52441 DB api GetMsg failed code 155

Definition

A module has trouble when it communicates with the database server. Code 160 indicates “busy.” Code 155 indicates a timeout, which is usually an indication that communication has been lost with the Conference Server.

Codes:

11 = this typically indicates network connection com failure between
 the network server and other MP servers
150 = out of memory
151 = internal error
152 = bad session
153 = bad client
154 = bad message
155 = timeout
156 = no message
157 = not found
158 = server not active
159 = no handle
160 = busy
161 = duplicate

Msgcode:
1	=	Find User Unique ID
3	=	Find User Name
4 	=	Find User VUNAME (cannot find the recorded VUI name for the user)
7	=	goto User
10	=	Option Check
11	=	Find Group Unique ID
16	=	goto Group
19	=	goto SystemCofig
27	=	Find Timezone ID
51	=	goto SWConfig
91	=	goto CS Outdial
100	=	API login
101	=	API logout
115	=	Find SCSI
118	=	Find Unit
121	=	Find Site
137	=	goto Userlist
142	=	goto UserListMem
156	=	goto CNMTGCATEGORYBODY
218	=	goto Remote Server

Resolution

This alarm is not serious by itself. Look for other indications of trouble at and around the time of this alarm.

0x52442 DB api message size was 267, expected 266 (code 118)

Definition

The database server received a malformed message from a client module or Cisco MeetingTime. This indicates a product defect. It most likely associated with the use of an old client version.

Resolution

If the problem is associated with the use of an older client version, consider an upgrade. Report all unexplained problems of this type as defects.

0x52444 DB api communication initialization failed (code 65)

Definition

A module failed to establish communication with the database server.

Resolution

Look for other indications of trouble.

0x5244f DB server too many tasks (167772160) requested (1221 allowed) conn 1211 ws –1820523042

Definition

A gateway logs in and did not already log out.

Resolution

Stop the Cisco MeetingPlace gateway system integrity manager (GWSIM) service, wait a few minutes, and then restart the service.

0x5245b DB server could not open query file errno 2, sessio

Definition

A query file could not be opened by the report generator. This can indicate a protocol error between the report generator and Cisco MeetingTime. This is associated with running reports and can be caused when you cancel a report.

Resolution

Attempt to create a repeatable scenario and report back to Cisco Technical Support. This is most likely not a critical error.

0x52465 DB server error 2 refreshing object type 6, msg code 0

Definition

This alarm is generated if a system administrator uses Cisco MeetingTime 5.0 to create a new profile on a Cisco MeetingPlace 5.1.1 system, but the profile ID already exists.

Resolution

There is no harm caused by this scenario. However, this will be fixed in a future server build so that no alarms are generated. In order to prevent alarms from being generated, you can also update Cisco MeetingTime to match the version that runs on the Cisco MeetingPlace server (Cisco MeetingTime 5.1).

0x6183c WS router wrong session 524293, (expected 0), code

Definition

This is a protocol error between Cisco MeetingTime and Cisco MeetingPlace. It is not serious.

Resolution

Report as a defect if you find it in the latest software release; otherwise, ignore it.

0x6183d WS router imc_rte initialization failed code 524293

Definition

This is an indication that the workstation server module was unable to initialize access to the system integrity manager at startup, and is symptomatic of a larger problem.

Resolution

Look for other indications of trouble.

0x61840 WS router unable to check option count for workstat

Definition

See 0x6183d.

0x6185f MeetingPlace Client 5, Session d0e23009 Reports Err

Definition

The MAPI gateway has trouble communicating with the mail server. This usually means that one address within the mail message is not deliverable.

0x7001e Software fault: module #23, signal=14, pc=237947

Definition

This indicates a software module has faulted.

Resolution

Refer all errors of this type to engineering.

0x70034 Temperature out of range

Definition

This alarm indicates that the temperature inside the Cisco MeetingPlace server has exceeded 104 degrees. This can indicate a fan assembly failure or an air conditioning failure.

Resolution

Check the temperature inside the room that houses the Cisco MeetingPlace server and verify that the fans in the fan assembly are spinning.

0x70035 Hardware watchdog timeout

Definition

The system has restarted itself. The low-level software did not respond to the hardware watchdog timer. In general, the hardware watchdog timer restarts the system if the low-level software does not respond within four to eight minutes.

Resolution

Contact Cisco Technical Support for further investigation.

0x70036 Power supply voltage out of tolerance

Definition

The power supply voltages are reported as either too high or too low. This can ultimately cause data loss on the disks or other hardware component failures.

Resolution

The power supply will likely have to be replaced. Contact Cisco Technical Support for further investigation.

0x70041 Restarting due to software module failure, module =

Definition

The system has initiated a system restart because one of the software modules stopped communicating with the system integrity manager (SIM).

Resolution

Contact Cisco Technical Support for further investigation.

0x70049 System crashed: power fail, reset, or watchdog time

Definition

The system has initiated a system restart for of one of these reasons:

  1. The power supply had a severe failure, someone cycled power (possibly by a hard reboot), or the power cord was disconnected.

  2. There was a power outage at the customer site, which causes the Cisco MeetingPlace server to lose power and trigger a restart once power is restored.

  3. The software halted (“froze”) due to a severe bug.

  4. A hardware fault, such as a bad disk, which causes the Cisco MeetingPlace server to boot up very slowly (see alarm 0xa003d).

  5. Failure to read and write to DAT tape due to bad DAT tape, DAT drive, or possibly SCSI driver failure.

Resolution

Check with the customer for any possible explanation for the power interruption. Contact Cisco Technical Support for further investigation.

Ignore this alarm if it occurs only once. Replace hardware (either CPU or hard disk, based on isolation results from Cisco Technical Support) if this alarm occurs more than once within a short period of time (such as one month).

0x70050 Error sending to a socket; ret = , errno = , size =

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x7005e Server socket startup failed, ex=0x70050

Definition

This is similar to a network hiccup. Both workstation server (Cisco MeetingTime or an old gateway) and the system integrity manager (SIM) complain about a socket error. The MAJ is a gateway unit that attempts a reconnect. The SIM responds to the reconnect request, but then is unable to detect the gateway unit. The reason SIM (on the Cisco MeetingPlace server) is unable to detect the gateway is because gateway SIM (GWSIM) (on the gateway) was in the process of restarting itself. When GWSIM come back up, if it still cannot connect to the network, it restarts itself after 30 seconds. This cycle continues until GWSIM can connect and communicate with the SIM.

Resolution

This is self-healing in that once the network problem goes away, this alarm goes away as well. If the alarm happens frequently, you may have some network connectivity problem. Contact Cisco Technical Support for assistance. If you are not running GWSIM version 4.2.0.33 or later, upgrade your GWSIM.

0x70071 NMI reported; TS register = 0x41

Definition

This information usually follows a system crash, and provides information about the possible causes (for example, watchdog timeout, power supply failures, or memory parity errors) and the number of total occurrences.

Resolution

Correlate this information with the prior system crash, and contact Cisco Technical Support for further investigation.

0x70073 Memory parity error

Definition

The CPU card has reported a memory parity error. This indicates a bad memory component.

Resolution

Monitor the system to see if there is more than one occurrence per month. If this alarm occurs more than once a month, replace the CPU card. If it occurs less than once a month, no action is necessary.

0x7007a Severe congestion! Message dst=0x7f1a5195,src=0x7f

Definition

This indicates a severe internal message queue overload on a networked conference server. This probably causes the server to restart. This problem would be associated with extraordinary traffic, possibly associated with network problems such as a broadcast storm or connectivity failure.

Resolution

Determine what was going on at the time of the failure. Look for network problems or some unusual activity.

0x7007e Ohnoo

Definition

Module failure causes this server crash. The Ohnoo.out dump file is generated.

0x70081 Unit 1 is down

Definition

Indicates that a Conference Server is down.

Resolution

Indicates that a Conference Server is down.

0x7008c Unit 1 is down

Definition

This alarm indicates a suspected SCSI subsystem hang, In other words, a disk hang.

Resolution

Look for other messages to indicate the cause.

0x70091 Network server lost charter; shutting down

Definition

The network server lost communication with the network.

Resolution

Determine why the network server was unable to connect to the conference server. Once the issue is resolved, take the steps necessary to switch the shadow server back to being a shadow server and bring the network server back online. It is also possible to convert the primary to a shadow and attach it back to the network.

0x7009a Communication lost with conference server 1

Definition

The network server unexpectedly lost communication with a conference server. This can indicate a physical network problem or a server crash.

Resolution

Look for other messages to indicate the cause.

0x7009b Communication lost with shadow server

Definition

The network server unexpectedly lost communication with a shadow server. This can indicate a physical network problem or a server crash.

Resolution

Look for other messages to indicate the cause.

0x7009c Communication lost with gateway unit #

Definition

The Cisco MeetingPlace gateway system integrity manager (GWSIM) is an integral part of every Cisco gateway product. GWSIM resides on the Windows NT server and constantly monitors network connection between the Windows NT server and the Cisco MeetingPlace system. This alarm is generated when the Network Server loses communication with the Windows NT gateway server.

Resolution

Make sure the gateway server is up. Look for a cause. Some possible causes are:

  1. The Windows NT server restarts. From the time the Windows NT server begins to shut down to the time that it completely comes back up, communication between the Windows NT server and the Cisco MeetingPlace server is broken.

  2. Check network hardware, such as router, NIC, cables and UPS. Was there any work being performed on the network infrastructure when the alarm was generated?

  3. Are there reports of other corporate servers going down at the same time? This can point to a network problem.

  4. Check the port configuration on your switch. The switch ports needs to be set to auto-negotiate.

  5. Load network monitoring software, such as SnifferPro, to monitor the traffic.

  6. Issue the ping command continuously. Make sure to log pipe output into a file, to see if there are periods of high network congestion or transmission delays.

  7. For Cisco MeetingPlace Server versions earlier than 4.3.1, run the broadcast storm test (contact Cisco Technical Support for the Tech Note). For Cisco MeetingPlace Server versions 4.3.1 and later, issue the chkbcast command-line interface (CLI) command from the superuser (su) level.

  8. Find out from Cisco Technical Support whether the particular version of GWSIM you are running has connectivity-related coding defects. If it does, upgrade to a more recent GWSIM version

    A code defect was discovered in GWSIM 4.1.0.27 that causes GWSIM to continually generate alarms and restarting itself. Three characteristic alarms resulting from this code defect are listed here:

    MAJ 07009c SW MODULE=2 Communication lost with gateway unit 10
    MAJ 120f02 SW MODULE=25 Gateway SIM Agent (Unit 10) Not Responding
    MAJ 70041 SW MODULE=26 Restarting due to software module 
    failure, module = 26

0x700a4 System crashed: restarted by the integrity manager

Definition

This indicates the system integrity manager (SIM) restarted a system.

Resolution

Look for signs of a broadcast storm or some other unusual activity. Escalate to Cisco Technical Support if the cause is not obvious.

0x700b2 Module polling mechanism is frozen

Definition

Some threads that run at lower priority (compared to other activities) fail to get CPU time or disk access. An example is if you issue the viewexlog command continuously, which requires both CPU time and disk write access.

Resolution

Priority increased in Cisco MeetingPlace 4.2.1a to prevent this occurrence.

0x700b7 Low priority infinite loop detected

Definition

Cisco MeetingPlace tasks are assigned different priority levels based on how critical they are to the functionality of Cisco MeetingPlace. Immediate response to a request to schedule a meeting is required, so that is high priority. Other tasks, such as a remote Telnet session or a Cisco MeetingTime report being run, are low-priority tasks. This alarm means that some low-priority task has misbehaved, and the failed task is taking up all low-priority cycles.

If you are unable to make a Telnet connection to the Cisco MeetingPlace server, you can see this alarm. This alarm means that an earlier Telnet session got into an infinite loop. Some possible causes are a module sent by FTP was corrupted during transmission and someone tried to uncompress it, or someone ran the uncompress command without specifying bin. Since you cannot make a Telnet connection, it is suspected that the uncompress went into an infinite loop taking up all low priority cycles, so no one can make a Telnet connection.

Resolution

If you attempt to transfer the module by FTP to the MeetingPlace server, try to transfer a fresh copy of the module by FTP. The uncompress should be successful after you replace the bad copy of the module on the server.

0x700ce file system access, perm=%o, expected=%o

Definition

The "ohnoo" background check process has detected that the permissions on the MeetingPlace root partition have changed. The "ohnoo" background check does this check every minute and logs this error if the permissions change. The "ohnoo" check then fixes the permissions so that "perm" equals the value indicated by "expected". This major alarm is logged when the error is detected. This exact alarm is logged again, but as an info, after the partition permissions are repaired (which happens within a few milliseconds). When this major alarm is logged, the permissions shown by "perm" and "expected" reflect the pre-repair state of the problem partition (they should be different).

Resolution

There is no resolution except to determine what can be happening to cause this. Who was logged in at the time of this error? Did someone or some program change the permissions?

0x90002 Bad port number (internal error) port = 100

Definition

This alarm occurs when the access license count is configured to be less then the number of configured ports.

Resolution

Either fix the access license count or reset the port configuration to use fewer ports than the license count.

0x90006 Unknown request code, code=38

Definition

A disconnect is generated by a client before the cpserver is ready for it.

Resolution

Ignore this if it happens on startup. Otherwise, you need to escalate.

0x90078 (EvtAreadComplete)Block read is invalid, port=0, er

Definition

Cannot play a block that does not belong to the file. The cause is a corruption in the file system.

Resolution

Use the file system check utility to fix the internal file system data structures on the disk.

0x90087 (EX_ML_SEND_FAIL) "()Fail to notify VUI, port=%x,err=%x"

Definition

This indicates that operating system resources are unavailable for the cpserver to notify the Voice User Interface (VUI) about an incoming call. This can happen at peak times on very busy systems with older, slower CPU cards on Extended Industry-Standard Architecture (EISA) systems. Although this can result in some calls not being answered (in other words, ring-no-answer), this problem corrects itself when the congestion disappears within a minute or two.

Resolution

If these are relatively rare and the customer has not reported any problems, then no action is necessary. If the customer is aware of the problem and desires a resolution, then upgrade the customer to a PCI system in order to fix the problem.

0x9009e (EX_SEND_EVENT_FAIL) "(EvtHangup)Fail send incoming event to client, port=%x, err=%x"

Definition

This is identical to alarm 0x90087, except that this alarm is caused by incoming hangups. When the incoming hangup is lost, the next call on that port is not answered (that is, ring-no-answer). As explained in the entry for alarm 0x90087, the congestion disappears within a minute or two.

Resolution

If these are relatively rare and the customer has not reported any problems, then no action is necessary. If the customer is aware of the problem and desires a resolution, then upgrade the customer to a PCI system to fix the problem.

0x90133 (LogEvent)Test entry, user specified parameters

Definition

This is a test message generated by a technician.

Resolution

Ignore this message. This is used to test the event logging and notification (alarm subsystems).

0x90134 (LogEvent)Test entry, user specified parameters

Definition

This is a test message generated by a technician.

Resolution

Ignore this message. This is used to test the event logging and notification (alarm subsystems).

0x90172 Failed to create a socket, err=0 Failed to create a socket, err=0

Definition

The system call to create a socket failed. This is caused by a system error. Check the error value to determine the specific cause for the failure.

Resolution

You must reboot the system and verify that the socket is successfully created. If it is not, escalate the problem to Cisco Technical Support.

0xa0002 No Disks Configured, num=0

Definition

There are no disks configured in the database for the file system. This is caused by an incomplete or incorrect configuration.

Resolution

You must reconfigure the system and configure at least one disk for the file system.

0xa0005 Invalid dir number=%x, DiskNum=%x

Definition

This alarm indicates that the directory number is out of range. The valid range is from 0 to CM_NDIRS_PER_DISK_MAX.

Resolution

The Cisco MeetingPlace server has to get a correct number before the operation can be completed.

0xa0006 Invalid disk number=%x, dir=%x

Definition

This alarm indicates that the disk number is out of range. The valid range is from 0 to CM_NDISKS_MAX.

Resolution

You need to get a correct number before the operation can be completed.

0xa0007 Not all data read,should=%x,read=%x, Disk=%x

Definition

Unable to read the static configuration file from disk. Both copies of the file were unreadable. You might need to delete and recreate it. The file may have been deleted or corrupted.

Resolution

Execute the Fix File System utility and re-create the static configuration file. Care must be taken to make sure that the number of H, I, B and the number of valid directories is the correct one. They can be obtained from the Dynamic Configuration file.

0xa000a Disk not configured, disk=%x

Definition

Even though the disk specified is within the valid range, that disk has no shared memory allocated.

Resolution

Configure the disk. Escalate the problem to Cisco Technical Support, because this is an internal inconsistency in the software.

0xa003d "HWFAULT", No such disk

Definition

The disk configured in the database for the file system cannot be found, or the disk is broken or going bad.

Resolution

Issue the diskoptions command to reconfigure the disk system if necessary. Replace with a spare disk if one is available. A bad voice disk can cause the Cisco MeetingPlace server to boot very slowly.

0xa005d Fail init StatConfig, err=%x,disk=%x

Definition

The system failed to read the static configuration file for a configured disk. This means that the disk is unusable. You cannot retrieve existing messages, nor record new ones. The error parameter may have caused the failure to read the file, or it may be an internal software error.

Resolution

Here are three possible resolution methods:

  • Reset the system and see if it comes up correctly the next time.

  • Make sure that the drive is correctly installed.

  • Escalate the problem to Cisco Technical Support for further analysis.

0xb0001 Activate DTI card 0, not there

Definition

The system attempted to activate a Digital Trunk Interface (DTI) card because it is in the database, but the card does not appear to be in the system.

Resolution

Check the address DIP switches on each of the cards to confirm that the IDs are set properly. If they are all correct, then swap in a new card for the problem card to see if it can be recognized. If there is still a problem, there can be a backplane or chassis problem. Contact Cisco Technical Support for further investigation.

0xb0008 Need more PRC(s) (at least 1) for trunks, trunk typ

Definition

The system is configured for more ports than the number of Port Resource Cards (PRCs) that are recognized in the software.

Resolution

Verify that the proper number of PRCs are present in the system. If they are physically there, then restart the system with a terminal connected to the front panel. As the system initializes, the drivers attempt to detect the Master Switch Controller (MSC) and PRCs and display what they detect (such as MSC #0, PRC #0, PRC #1, and so on). If the system does not recognize each of the PRCs, then at least one of the cards is not recognized. Capture the information from the terminal and contact Cisco Technical Support for further investigation.

0xb0025 PRC Driver DOWNLOAD_FPGA error, id = 0, errno = 237

Definition

The Port Resource Card (PRC) could not be configured. The PRC is probably bad.

Resolution

Replace the PRC with a new card at the latest revision level.

0xb0027 FPGA not programmed successfully, id = 10

Definition

The Port Resource Card (PRC) could not be configured. The PRC is probably bad.

Resolution

Replace the PRC with a new card at the latest revision level.

0xb0029 PRC Driver SET_SHARED_MEM error, id = 2, errno = 5

Definition

The Port Resource Card (PRC) failed in having its shared memory set up. There are likely other errors for this PRC, and it is likely bad.

Resolution

Replace the PRC with a new card at the latest revision level.

0xb0049 PRC Driver SET_PRC_TRK_SIG error, errno = 13

Definition

The Port Resource Card (PRC) failed during trunk signaling. There are likely other errors for this PRC. The PRC is likely bad.

Resolution

Replace the PRC with a new card at the latest revision level.

0xb0052 MSC Driver DOWNLOAD_FPGA error, id = 0, errno = 237

Definition

The Master Switch Controller (MSC) could not be configured. The MSC is likely bad.

Resolution

Replace the MSC with a new card at the latest revision level.

0xb005c MSC Driver SEND_COMMAND error, id = 0, command = 22

Definition

Commands could not be sent down to the Master Switch Controller (MSC). This happens if the system is shut down before it has completely come up.

Resolution

None. In general, it is better to wait for the system to come up completely before you shut it down.

0xb0063 PRC command queue overflow ([11], card 0, slot 5, [

Definition

The Port Resource Card (PRC) is unable to access its command queue. There are probably other related errors and alarms. The PRC may be bad.

Resolution

If this is the first occurrence, document the failures and monitor the system for repeat occurrences. If it happens again, replace the PRC with a new card at the latest revision level.

0xb0064 PRC event queue overflow ([11], card 0, slot 6, [-1

Definition

The Port Resource Card (PRC) does not respond to commands. There can be other related errors and alarms. The PRC might be bad.

Resolution

If this is the first occurrence, document the failures and monitor the system for repeat occurrences. Otherwise, escalate the problem.

0xb0065 PRC is not responding ([11], card 0, slot 5, [-1])

Definition

The Port Resource Card (PRC) does not respond to commands. There can be other related errors and alarms. The PRC might be bad.

Resolution

If this is the first occurrence, document the failures, restart the system, and monitor the system for repeat occurrences. If it happens again, replace the PRC with a new card at the latest revision level.

0xb0068 MSC is not responding ([10], card 0, slot 4, [-1])

Definition

The Master Switch Controller (MSC) does not respond to commands. There are possibly other related errors and alarms. The MSC is possibly bad.

Resolution

If this is the first occurrence, document the failures, restart the system, and monitor the system for repeat occurrences. If it happens again, replace the MSC with a new card at the latest revision level.

0xb0078 Red Alarm detected on this T1 span

Definition

The T1 span is detected as down.

T1 spans can be detected as down for two reasons:

  1. Loss Of Signal (LOS)—The T1 receiver sees either no signal or a signal that is so weak that it seems to be 0 volts (no signal). For alternate mark inversion (AMI)-encoded T1, a long sequence of 0 bits can appear to the receiver as an LOS. Binary 8-zero substitution (B8ZS) encoding eliminates this situation.

  2. Out Of Frame (OOF)—The T1 receiver sees pulses, which indicate a signal in T1. However, the basic framing (bit) pattern expected in the 193rd bit is not correct.

Red Alarms can result from:

  1. Incorrect span configuration (for example, Extended Superframe [ESF] instead of Superframe [SF], binary 8-zero substitution [B8ZS] instead of jammed bit).

  2. The T1 cable being unplugged from the back of the Cisco MeetingPlace system.

  3. Faulty wiring at the punch-down block (a loose wire in the connector).

  4. A failure at the Channel Service Unit (CSU), or the CSU in a remote loop-back.

  5. A failure of the T1 interface card in the Cisco MeetingPlace server.

  6. A problem at the telephone company (Telco) (for example, private branch exchange [PBX] or central office [CO]).

  7. A cable that is too long. Generally, the cable between the Cisco MeetingPlace server and the local far-end (PBX, CSU, or central office Network Interface Unit [CO NIU]) should not exceed 600 feet.

  8. The use of an incorrect wire type. Category (CAT) 5 wire needs to be used rather than CAT 3 or any other wire type. Also, only four wires in the eight-wire CAT 5 cable should be used (Rcv Tip and Ring, Xmt Tip and Ring). Attempts to route two T1 circuits through the eight available wires can cause cross-talk and intermittent T1 outages.

Resolution

Issue the spanstat command to verify the current state of the span. If the span is up, and there is a reasonable explanation for the prior failure, then no action is necessary. If the span is still down, verify the span configuration and the connection to the Cisco MeetingPlace server. With assistance from the customer, PBX tech or public switched telephone network (PSTN), verify the wiring and the CSU. Swap the span with a known good span and see whether the problem follows the span (this implies a customer wiring or PBX/CO configuration problem) or whether the problem stays with our Digital Trunk Interface (DTI) hardware interface (this implies a Cisco MeetingPlace server hardware or configuration problem). If it looks like a DTI problem, gather the appropriate logs (spanstat -s, spanstat -all, hwconfig, alarm, and errorlog command output) and contact Cisco Technical Support for further investigation. Also issue the dcard, span, and port commands to check that the configuration matches the PBX/PSTN.

0xb0082 Timed out during evtpoll, errno = 11, last event 10

Definition

This alarm occurs when the Cisco MeetingPlace server times out while it waits for a Port Resource Card (PRC) event.

Resolution

This alarm does not indicate a serious problem, if it occurs infrequently. If it occurs frequently, contact Cisco Technical Support.

0xb0094 PRC DSP never came up, ports lost ([11], card 0, sl

Definition

One or more of the DSPs on the Port Resource Card (PRC) cannot be initialized. This results in severe audio failure (either loud noise or silence) for the group of ports associated with that DSP. On an Extended Industry-Standard Architecture (EISA) system, each DSP failure affects four ports. On a PCI system, each DSP failure affects twelve ports.

Resolution

Replace the PRC with a new card at the latest revision level.

0xb0097 MSC Driver SET_PROMPT error, id = 0, errno = 9

Definition

Cached prompts could not be sent down to the Master Switch Controller (MSC). This can happen if the system is shut down before it has completely come up.

Resolution

None. In general, it is better to wait for the system to come up completely before you shut it down.

0xb00a0 Bad port number received from PRC 0, port number 25

Definition

The Port Resource Card (PRC) has generated an event that might contain some garbage. The PRC may be bad.

Resolution

Contact Cisco Technical Support for further investigation.

0xb00a6 Unexpected READY event from PRC 0, state 3, diag =

Definition

The Port Resource Card (PRC) has unexpectedly restarted its firmware. The PRC may be bad.

Resolution

If this is the first occurrence, document the failures, restart the system, and monitor the system for repeat occurrences. If it happens again, replace the PRC with a new card at the latest revision level.

0xb00a7 Unexpected READY event from MSC 0, state 3, diag =

Definition

The Master Switch Controller (MSC) has unexpectedly restarted its firmware. The MSC is possibly bad.

Resolution

If this is the first occurrence, document the failures, restart the system, and monitor the system for repeat occurrences. If it happens again, replace the MSC with a new card at the latest revision level.

0xb00bc ETI handle 8103 not found, event = 400

Definition

This alarm occurs when the software gets a disconnect from a port that it has already disconnected.

Resolution

There is no resolution.

0xb00db DTI Driver no interrupts from card, id = 0

Definition

The Digital Trunk Interface (DTI) driver does not detect any interrupts from any of the DTI cards. This can sometimes happen if there are no active T1 spans physically plugged in to the Cisco MeetingPlace server or if there is a DTI hardware problem.

Resolution

If there are active T1 spans plugged in, then the DTI hardware needs to be examined. Verify that on each of the cards, the interrupt selection and interrupt termination jumpers are set properly. That is, each of then DTIs needs to use the same interrupt, but only DTI 0 should have the interrupt termination jumper installed. If the problem still exists, contact Cisco Technical Support for further investigation.

0xb00e2 IRC find database record failed, id = 0, raima erc = 150

Definition

Either there is no Internet Resource Card (IRC) is installed, or database initialization failed.

Resolution

This alarm occurs on 4.2.0 server software, but is fixed in version 4.2.1a.

0xb0137 ISDN D-Channel is down on this E1 span

Definition

The E1 PRI span is not able to support ISDN operations.

The Data Channel (D-channel) of the E1 PRI span is not operational. E1 PRI (ISDN) circuits exchange messages on the sixteenth E1 channel. A specific exchange of messages must be received before the D-channel entity can be considered operational. Specifically, each end sends a Set Asynchronous Balanced Mode Enabled (SABME) message (also called "frame") to the other end. In return, the other end must reply with an Unnumbered Acknowledgement (UA) frame. If the UA frame is not seen by one side, that side considers the D-channel to be down and ISDN signaling operations (the making and breaking of calls) cannot occur.

A downed D-channel can result from:

  1. Non-zero TEI and/or SAPI (T1 PRI only)—The T1 PRI Cisco MeetingPlace implementation supports only an ISDN Terminal Endpoint Identifier (TEI) of 0 and a Service Access Point Identifier (SAPI) of 0. Any other values sent in a SABME frame cause the server to ignore the frame and not respond with a UA frame. Essentially, the D-channel and the rest of the ISDN link do not ever come up.

  2. Far-end is not ISDN—If this happens during initialization, check to make sure the far-end E1 equipment supports and is configured for ISDN.

  3. High bit error rate—If many bit errors occur, the messages needed to establish a D-channel get corrupted and D-channel establishment does not occur.

  4. Transient while span goes down—If the entire span goes down due to framing or loss of signal problems, a downed D-channel indication can occur at the same time. In this case, ignore the D-channel message if a lost frame or signal error is also present.

Resolution

Issue the spanstat command to verify the current state of the span. If the span is up, and there is a reasonable explanation for the prior failure, then no action is necessary. If the span is still down, verify the span configuration and the connection into the Cisco MeetingPlace server. Also, verify that more basic errors, such as lost frame or lost signal, are not present. If these other errors are present, address them first to see if the D-channel problem goes away.

0xb014f Lost Signal detected on this T1/PRI span

Definition

The T1 span does not see an electrical signal.

A Loss Of Signal (LOS) condition occurs if the T1 receiver sees either no signal or a signal that is so weak that it appears to be 0 volts (no signal). For alternate mark inversion (AMI)-encoded T1, a long sequence of 0 bits can appear to the receiver as an LOS. Binary 8-zero substitution (B8ZS) encoding eliminates this situation.

Definition

LOS can result from:

  1. Incorrect span configuration, such as AMI instead of B8ZS.

  2. The T1 cable being unplugged from the back of the Cisco MeetingPlace server.

  3. Faulty wiring at the punch-down block (a loose wire in the connector).

  4. A failure at the Channel Service Unit (CSU), or CSU in remote loop-back.

  5. A failure of T1 interface card in the Cisco MeetingPlace server.

  6. A problem at the telephone company (Telco) (for example, PBX or CO).

  7. A cable that is too long. Generally, the cable between the Cisco MeetingPlace server and the local far-end (PBX, CSU, or central office Network Interface Unit [CO NIU]) should not exceed 600 feet.

  8. The incorrect wire type. You need to use a CAT 5 wire rather than CAT 3 or any other wire type. Also, only four wires in the 8 wire CAT 5 cable should be used (Rcv Tip & Ring, Xmt Tip & Ring). Attempts to route two T1 circuits through the eight available wires can cause cross-talk and intermittent T1 outages.

Resolution

Issue the spanstat command to verify the current state of the span. If the span is up, and there is a reasonable explanation for the failure, then no action is necessary. If the span is still down, verify the span configuration and the connection into MeetingPlace. With assistance from the customer, PBX tech or PSTN, verify the wiring and the CSU. Swap the span with a known good span and see whether the problem follows the span (implies a customer wiring or PBX/CO configuration problem) or whether the problem stays with our Digital Trunk Interface (DTI) hardware interface (this implies a MeetingPlace hardware or configuration problem). If it looks like a DTI problem, gather the appropriate logs (such as spanstat -s, spanstat -all, hwconfig, alarm, and errorlog) and contact the Support Center for further investigation. You also need to check that the configuration matches PBX/PSTN with the use of the dcard, span, and port commands.

0xb0150 Lost Frame detected on this T1/PRI span

Definition

The T1 span does not see a valid framing pattern.

An Out-Of-Frame (OOF) condition indicates that the T1 receiver sees pulses (which indicate a signal in T1), but the basic framing (bit) pattern expected in the 193rd bit is not correct.

Red Alarms can result from:

  1. An incorrect span configuration, such as Extended Superframe (ESF) instead of Superframe (SF) or B8ZS instead of jammed bit.

  2. Faulty wiring at the punch-down block (a loose wire in the connector).

  3. A failure at the Channel Service Unit (CSU), or CSU in remote loop-back.

  4. A failure of the T1 interface card in the Cisco MeetingPlace server.

  5. A problem at the telephone company (Telco). For example, at the private branch exchange (PBX) or central office (CO).

  6. A cable somewhere in the system is too long. Generally, the cable between the Cisco MeetingPlace server and the local far-end (PBX, CSU, or central office Network Interface Unit [CO NIU]) should not exceed 600 feet. Excessively long cables can cause bit errors, which in turn can corrupt framing patterns.

  7. A wire of the wrong type. You need to use a Category (CAT) 5 wire rather than CAT 3 or any other wire type. Also, only four wires in the eight-wire CAT 5 cable should be used (Rcv Tip and Ring, Xmt Tip and Ring). Attempts to route two T1 circuits through the eight available wires can cause cross-talk and intermittent T1 outages.

Resolution

Issue the spanstat command to verify the current state of the span. If the span is up, and there is a reasonable explanation for the failure, then no action is necessary. If the span is still down, verify the span configuration and the connection to the Cisco MeetingPlace server. With assistance from the customer or PBX tech or PSTN, verify the wiring and the CSU. Swap the span with a known good span and see whether the problem follows the span (implies a customer wiring or PBX/CO configuration problem) or whether the problem stays with our Digital Trunk Interface (DTI) hardware interface (this implies a Cisco MeetingPlace server hardware or configuration problem). If it looks like a DTI problem, gather the appropriate logs (spanstat -s, spanstat -all, hwconfig, alarm, and errorlog command output) and contact the Support Center for further investigation. You should also issue the dcard, span, and port commands to check that the configuration matches that of the PBX/PSTN.

0xb0154 ISDN D-Channel is down on this T1/PRI span

Definition

The T1 PRI span is not able to support ISDN operations.

The Data Channel (D-channel) of the T1 PRI span is not operational. T1 PRI (ISDN) circuits exchange messages on the D-channel, which is the 24th T1 channel. A specific exchange of messages must be received before the D-channel entity can be considered operational. Specifically, each end sends a Set Asynchronous Balanced Mode Enabled (SABME) message (also called "frame") to the other end. In return, the other end must reply with an Unnumbered Acknowledgement (UA) frame. If the UA frame is not seen by one side, that side considers the D-channel to be down and ISDN signaling operations (the making and breaking of calls) does not occur.

A downed D-channel can result from:

  1. Non-zero Terminal Endpoint Identifier (TEI) or Service Access Point Identifier (SAPI) (T1 PRI only)—The T1 PRI Cisco MeetingPlace implementation only supports an ISDN TEI of 0 and SAPI of 0. Any other values sent to it in a SABME frame cause it to ignore the frame and not respond with a UA frame. Essentially, the D-channel and the rest of the ISDN link then never come up.

  2. Far-end is not ISDN—If this happens during initialization, check to make sure the far-end T1 equipment is configured for and supports ISDN.

  3. High bit error rate—If numerous bit errors occur, the messages needed to establish a D-channel becomes corrupted and D-channel establishment does not occur.

  4. Transient while span goes down—If the entire span goes down due to framing or Loss Of Signal (LOS) problems, a downed D-channel indication can occur at the same time. In this case, ignore the D-channel message if a lost frame or signal error is also present.

Resolution

Issue the spanstat command to verify the current state of the span. If the span is up, and there is a reasonable explanation for the failure, then no action is necessary. If the span is still down, verify the span configuration and the connection into the Cisco MeetingPlace server. Also, verify that more basic errors, such as lost frame or lost signal, are not present. If these other errors are present, fix them first to see if the D-channel problem goes away.

0xb0156 IP Global Configuration find database record failed, raima erc = %d

Definition

The TVAPI could not find the IP Global Configuration record. On new systems, this record should always be created while the tvdbinit utility runs. If not, it indicates that the system was not initialized properly when it was manufactured. On upgrades, this record should be created by the upgradetcnfg utility. If not, it indicates that the upgrade encountered some serious errors.

Resolution

This error should never happen. But if it does, the best way to fix this problem is to run tvdbinit again, and then redo the entire trunk configuration.

0xb015a ACTI %d, physical link %d is down (IP)

Definition

One of the modules on an Audiocodes board has lost its Ethernet carrier. The module is configured for Voice over IP (VoIP) operations.

Resolution

The Ethernet network is down or the cable to the board is unplugged. Determine the reason for the downed network or reconnect the cable.

0xc0001 Cannot open MSC device, id = 0, errno = 19

Definition

The software thinks that there is no Master Switch Controller (MSC) in the system.

Resolution

Verify that there really is an MSC in the system. If there is, restart the system with a terminal connected to the front panel. As the system initializes, the drivers attempt to detect the MSC and Port Resource Cards (PRCs) and display what is detected (such as MSC #0, PRC #0, PRC #1, and so on.). If the system does not recognize the MSC, capture the information from the terminal and contact Cisco Technical Support for further investigation.

0xc0002 MSC Driver SEND_COMMAND error, id = 0, command = 22

Definition

Commands could not be sent down to the Master Switch Controller (MSC). This can happen if the system is shut down before it has completely come up.

Resolution

None. In general, it is better to wait for the system to come up completely before you shut it down.

0xf000b Failed to initialize SIM interface, ex=458764

Definition

This alarm indicates a problem with Module 18, which is the Post Office server. The potester command was issued incorrectly. The command issued, which does not exist, was poserver.

Resolution

There is no harm done to the server.

0xf0087 There are too many msgs queued in the PO

Definition

This alarm indicates an overflow of the Post Office server queue.

Resolution

Make sure the mail system (Microsoft Exchange, Domino, or other mail software) still actively accepts and sends messages. If the mail system is OK, try to restart the Cisco MeetingPlace notification gateways.

0x110001 DBAPI Initialization Failed or 0x11000A Failed to open database; ex = 0x0

Definition

These errors are generated by the shadow network server when it has trouble accessing the database, either locally on its own server or remotely on the network server. It is caused by problems communicating with the network server. Other log entries indicate the source of the problem.

Resolution

Make sure there is communication with the network server. Verify that the database local to the shadow server is up.

0x110003 Failed to log into network server DBS; erc = 0x9b

Definition

Indicates that the shadow network server does not communicate properly with the network server. This can indicate that the network server is down or out of communication.

erc 9b=timeout erc 97=internal error

Resolution

Make sure the network server communicates properly with the shadow server.

0x110012 Shadow server is 279894 hours behind

Definition

Verify that there are no other shadow server minor alarms. If there are no others, this means the shadow server database has finally synched up with the network server database. It becomes an issue if the same type of alarm is generated, but the number of hours is greater than 279,894. This means the shadow server cannot update its database because it cannot connect to the network server.

Resolution

Monitor and escalate with Cisco Technical Support if this problem reoccurs.

0x120402 Outlook Gateway (Unit #) Not Responding

Resolution

Complete these steps

  1. Check to see if there was a network interruption.

  2. Check the gateway system integrity manager (GWSIM) eventlog for Cisco MeetingPlace for Outlook events.

  3. Check the Windows NT Application Eventlog.

    Note: In the Windows NT Application Eventlog log, look for this error (this alarm can be caused by the Microsoft Outlook account password on the Exchange server being expired:

    Note:  Error The description for Event ID (2) in Source (MPOutlook) could not be found. It contains the following insertion string(s): "Error: 0x80070532 Message: Logon failure: the specified account password has expired. "

0x120403 Outlook Gateway (Unit #) Failed

Definition

This indicates that the Microsoft Outlook service terminated unexpectedly for some reason. If the Cisco MeetingPlace server does not receive a shutdown message from the service, then the next time it checks for it and receives no response it assumes the service has failed and logs this error.

Resolution

Complete these steps.

  1. The problem can be with the network. If there are other Cisco MeetingPlace services on the machine, determine whether or not they have trouble communicating with the MeetingPlace server.

  2. Look in the Service Manager on the Outlook Gateway Windows machine. Is the service running? Look in the gateway system integrity manager (GWWSIM) log. Look at the Windows Task Manager under processes and see if there are multiple mpoutlook.exe processes that run.

  3. Stop and restart the service and monitor. If the problem persists, escalate the problem with Cisco Technical Support.

0x120404 Outlook Gateway (Unit #) Shutdown

Definition

The service was manually shut down.

Resolution

Restart the service.

0x120702 VoIP CCAgent (Unit 10) Not Responding

Definition

The Cisco MeetingPlace IP gateway service might be down.

Resolution

Check to see if the service runs. The IP address of the Cisco MeetingPlace server or the IP gateway might be incorrect in the MeetingPlace server configuration.

0x140008 Gateway SIM: Handler Queue Full

Definition

If the network connection is slow between the server and gateway unit, the gwsim handler queue can often become backed up. You may see this warning message along with the Handler Queue Full alarm:

WARN 0x700b5 Overflow of update queue for unit #

"Overflow of update queue" means the server tries to send information out to the gateway unit, but the gateway unit accepts the message very slowly. This is different from a total network outage, in which case the server drops and reinitiates the connection.

Resolution

Check if there are communication errors or socket errors prior to or when the alarm occurred, review cm_alt log on the gateway server side and the viewexlog on the MeetingPlace server side to identify the root cause.

0x170001 (EX_AC_BD_INVAL_HANDLE) Inval bd hndl = ???, bd # = ???, bd type = ???

Definition

An operation is being requested of ACTI where an invalid board handle has been passed to it by TVAPI. Alternately, there is internal table corruption in ACTI and invalid board information is read. The board number listed, if valid, is most likely no longer able to send or receive calls.

Resolution

The only solution is to restart the system. If there is enough capacity with other Audiocodes boards, this restart can be held off until a time convenient for the customer. Otherwise, the restart needs to be as soon as possible. If the board number or board type are garbage (valid board types are 14-TP1610 and 13-TP610), issue the blade command to reinstall the Audiocodes boards.

Minor Alarms

0x1003e Error reading the peg table from disk, errno=2

Definition

This alarm indicates a file is missing.

Resolution

The peg database file may need to be reinitialized. Refer to Cisco Technical Support.

0x10062 Tape write failed during backup, tar code 3

Definition

The backup failed because of a physical drive problem.

Resolution

Make sure a tape is in the drive. Replace the tape. Clean the drive heads. Replace the drive.

0x10075 Non-null message: class=0x3, ptr=0x4f5b58, code=61

Definition

Alarm class and code definitions:

class 3=cpserver, code 61=stop record problem with telephony cards class 5=CS module, code 91=FINISHRETRIEVECONFATT

If the unit that caused this alarm is a gateway unit (that is, one of the units from Unit 10 through 15), this alarm means that when a gateway shuts down (or possibly just logs out) and it finds a message left over in its message queue, the message is thrown away.

Resolution

This alarm can be ignored unless it is repeated frequently or constantly.

0x10078 Internal error: erc=0x97, location=0, max=45

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x1007c Client receive failed, ex=0x9

Definition

See 0x1001e.

0x11000 Failed to open database; ex = 0x110003

Definition

The shadow server failed to open a database.

Resolution

Check communication with the network server. Look for other indications that the local database is corrupted.

0x1700a (EX_AC_CH_TDM_XC_TO_ERR) Chan PSTN to H.110 xcon err = ???, sysport = ???, H.110 st:ts = ???:???

Definition

During initialization, channels are mapped to specific H.110 streams and timeslots. If these mappings cannot be done, calls can be established, but users experience dead air. Users are unable to either talk or listen to conferences.

Resolution

The only solution is to restart the system. The restart needs to be as soon as possible, because calls that are established give the illusion that everything is functional.

0x2005b Msg Checksum does not agree. Sum 0, Expected Size 98, Code 64, Size 98

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x2005d Act conf. Allocation failed: Err =

Definition

This alarm is given when the system detects an error while it attempts to allocate internal resources to support a conference. The user might not be able to attend or schedule a meeting when this error occurs.

The user gets a "meeting ID not recognized" message when trying to attend meetings, or the user gets an "internal error" message when trying to schedule a meeting through Cisco MeetingTime or the web.

Resolution

If your Cisco MeetingPlace server software version is earlier than 4.2.1d, upgrade the software to 4.2.1d (or a later version that also contains a fix for this error).

If you encounter this problem in a newer version (later than 4.2.1d), contact Cisco Technical Support.

0x20071 Cannot read the options. Err = 155

Definition

Err=155=time out

Err 524293=0x80005 OM option code mismatch

Resolution

Contact Cisco Technical Support for further investigation.

0x20083 Bad msg size received from client. Code 34, Expected 58, Received 86, Ver 1

Definition

The Conference Server (CS) receives an inter-module communication message of unexpected size.

Alarm code and version definitions:

code 34=get list of meetings version 1=Cisco MeetingTime version 8=Cisco MeetingPlace Web

Resolution

If this alarm does not accompany a major alarm, it does not indicate a serious problem. It can be ignored.

0x200a5 No Not Event Queue Entries Available

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x200c0 Too many conference ports. Wanted 48, Licensed 24

Definition

The number of conference ports in the Cisco MeetingTime configuration is greater than the number of conference port licenses purchased.

Resolution

Reduce the conference ports setting to a number equal to or less than the total conference ports licenses option key.

0x200c1 Conference Port Problem Resolved!

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x200fe Reserve All Ports maintenance mtg still in effect. End mtg to free ports.

Definition

An attempt to schedule meetings is made on a system with all ports in maintenance mode.

Resolution

End the "Reserve All Ports" meeting to allow normal meetings to be scheduled and to return Cisco MeetingPlace to normal operation.

0x30001 Bad stack. Act = 206, port = 99, substate = 1, App

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x30004 Invalid Digit, Digit = 2

Definition

The Voice User Interface (VUI) module attempts to spell out a two-digit string, the second character of which is a 2 (not a character "2", but the value 2). The VUI does not understand it, and so it complains.

Resolution

This error does not affect service and you can ignore it. However, if this error is continually generated, open a service request with Cisco Technical Support.

0x30005 Invalid Month = X

Definition

An unrecognized two-digit month was entered by a user from the Voice User Interface (VUI) when prompted to enter a two-digit month by Cisco MeetingPlace.

Resolution

This alarm is harmless. Train users accordingly on entering a two-digit month when they schedule or review notes from the VUI.

0x3000a More segments than allowed. Seg Num Received 65536,

Definition

None.

Contact Cisco Technical Support for further investigation.

0x3000e VUI and CS having trouble communicating. Err = 102

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x30010 Incomplete Application! App No = 21, Dest State = 1

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x3001b No VUI Conference Object...Internal State Construct

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x30020 (BAD) Seq of msg fffff672, Seq of VUI fffff772, Offending Server 5, code of Msg 39

Definition

See 0x52440 and 0x52441 for the msgcode list.

0x30026 Knock Lock failure. Erc = 0, Conf Num = 1515870810

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x3003b Bad event

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x30091 Cannot add key for user. Err 8193, Port 62, Digit 1

Definition

A user presses the dual tone multifrequency (DTMF) keys too fast and this causes Cisco MeetingPlace to drop some of the digits

Resolution

Cisco MeetingPlace indicates an error caused when a user presses keys too quickly. No software defects are indicated.

0x300af Desired Response has not yet arrived

Definition

This alarm occurs after a recording is paused, while it waits for a restart of the recording or for the meeting to end. When neither event occurs within a certain period of time, this error is generated. This error is found in Cisco Meeting Place server build 5.00af.

Resolution

This alarm does not affect service.

0x300b0 Desired operation is not available in this state

Definition

None

Resolution

Contact Cisco Technical Support for further investigation.

0x300b5 Cannot read System Configuration

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x300ba Trying to play a number that is too big. Num = 2132

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x300bd CP Msg left after timeout. Seq: 0, In Mask 0, Out Mask 512

Definition

This alarm is a direct result of alarm 0x300c8 (port timeout). After a port times out, the Voice User Interface (VUI) module performs a cleanup process for that port. This alarm indicates that there are one or more unprocessed messages for that port, which are disregarded.

Resolution

  1. Has there been a recent T1 issue? If the private branch exchange (PBX) or telephone company (Telco) does not send the proper signal to Cisco MeetingPlace to disconnect calls, port timeouts result. In some cases the port is left in a hung state.

  2. If this is a Cisco MeetingPlace networked system, have there been any network issues between the conference servers and the network server? If a port tries to access information that is on the network server and there is an abrupt network problem, this can also lead to a port timeout and this alarm.

0x300c0 Trying to bring a uInt below 0 error

Definition

This alarm indicates that an unsigned integer decrements to a value below zero related to participants that depart a reservationless meeting. Instances of this alarm are found not to affect service. Service is not affected whether this alarm is logged because a meeting initiator or other participant departs a reservationless meeting. This output shows an example of this alarm:

12/20 08:28:55 MIN 0x300c0 0/8, "vuiconfssn.cc", 632 (0x1fe61, 0, 0, 0) Trying to bring a uInt below 0 error. 12/20 08:26:59 MIN 0x300c0 0/8, "vuiconfssn.cc", 632 (0x1fe61, 0, 0, 0) Trying to bring a uInt below 0 error. 12/20 08:16:12 MIN 0x300c0 0/8, "vuiconfssn.cc", 632 (0x1fe61, 0, 0, 0) Trying to bring a uInt below 0 error.

Resolution

None.

0x300c5 SW MODULE=8 Bad Session Num

Definition

Possible causes are a race condition (someone tried to place a call while another call is in the process of terminating), a line disrupted during a session, or trunks swapped while meetings were in progress. These problems can cause the Voice User Interface (VUI) to be unable to synch up with Conference Server (CS)/Network Server (NS) modules.

0x300c7 Invalid Key

Definition

A user presses the wrong dual tone multifrequency (DTMF) keys and Cisco MeetingPlace does not understand some of the keys pressed.

Resolution

Cisco Meeting Place indicates an error based on an incorrect operation by a user, who presses the wrong keys. If this alarm does not happen a lot, ignore it. If this alarm does occur on a frequent basis and it always happens to the same port, the same span, or the same Port Resource Card (PRC) card, you need to troubleshoot further.

0x300c8 Port Timeout. Reason = 159:31, Port = 1900548, Tag

Definition

This alarm is related to communication losses or a busy database. When the network server is busy and cannot send all the meeting information about a call to the conference server, this alarm results. There is no impact to service.

Resolution

Even though this alarm does not affect service, it can show that there is another problem (possibly a serious one, such as communication losses or a busy database). Contact Cisco Technical Support.

0x300df Request for conf. bank with no conf. attached.u 190

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x300e6 Too many attempts to log into profile (10556) 37323

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x300f1 Too many Access Ports Configured compared to License

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x30101 Cannot load flexmenu application. Err 8226 App 100

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x30107 Possible message lost from the cpserver

Definition

See alarm 0x30095.

0x3010e Too many errors while connecting to MP. Errs 4 Port

Definition

None

Resolution

Contact Cisco Technical Support for further investigation.

0x30110 Port 40 timeout waiting to receive Data of type 19 State 187

Definition

Alarm type and state:

Type 19=SNATRANSFER State 187=StMP2MP_SNASLAVEGETID

If Single Number Access (SNA) is implemented and a call comes in on (for example, Conference Server 1 [CS1]), but the meeting is actually on Conference Server 2 (CS2), the Cisco MeetingPlace server initiates a MeetingPlace to MeetingPlace (MP2MP) call transfer. This alarm happens because CS2 expects to receive the data from another CS1. The failure of the function is responsible for receipt of a frame of information across the publish switched telephone network (PSTN) from another Cisco MeetingPlace server using dual tone multifrequency (DTMF) digits. The action receives all incoming dual-tone multifrequency (DTMF) digits. Somehow CS2 did not receive any data and times out, the system just terminates the session (ends the call).

Resolution

If the port times out and is then free, there is no need to worry. If the port is hung, contact Cisco Technical Support.

0x3012f RSNA remote server lookup error, erc=%d, ID=%d

Definition

A remote server lookup fails in an unexpected manner. There is a database problem or a failure to communicate with the database.

Resolution

Look for other error indications.

0x30130 RSNA transfer loop? UserID=%d MtgOwner=%d

Definition

There is a Reservationless Single Number Access (RSNA) transfer loop. This alarm indicates an inter-server configuration conflict or a user-database synchronization problem.

Resolution

Recheck the configuration for RSNA for both servers involved.

0x30134 RSNA user unknown, user=%08x%08x%08x%08x

Definition

A user identified in a Reservationless Single Number Access (RSNA) transfer is unknown. This error indicates a user database inter-server synchronization problem.

Resolution

Recheck the configuration for RSNA for both servers involved.

0x30135 RSNA: Unexpected error looking up user (ret=%d)

Definition

An unexpected error occurs when you look up a user profile. There is a database problem or a failure to communicate with the database.

Resolution

Look for other error indications.

0x30136 RSNA: Guest user lookup failed (ret=%d)

Definition

This error indicates that you are unable to access the guest profile record. There is a database problem or a failure to communicate with the database.

Resolution

Look for other error indications.

0x30137 RSNA: Password mismatch, user=%08x%08x%08x%08x

Definition

The password provided in the transfer information block does not match the password of the local user. This error indicates an inter-server database synchronization problem.

Resolution

Look for other error indications.

0x30138 RSNA: Info block verification failed, ex=%#x

Definition

Corrupted information block received from the transferring server. Indicates the information was corrupted in transmission, a software version mismatch, clock skew, or an attempt at forgery.

Resolution

Look up the secondary exception code (ex=) for more specifics.

0x30142 StartPlay outstanding

Definition

Within the Voice User Interface (VUI), a prompt unexpectedly continues to play on a port. This error can indicate a VUI state machine problem where a prompt playing was initiated and then forgotten. Problems can happen when the cpserver returns a response which the VUI does not expect.

Resolution

Issue the viewexlog and cptrace commands around the time that this error is reported and completely capture the output. Verify that the port works correctly and that successful calls follow the report of this error. In the worst case, if the port is stuck in a strange state and callers hear ring no answer (RNA) or silence, a restart can be necessary to free it up. Alternately, on a public switched telephone network (PSTN), the associated telephony span may be disconnected to prevent incoming calls on this port. Escalate the problem to Cisco Technical Support in any case.

0x5244e DB server connected task not current code 0

Definition

This alarm began to surface after M3 rollout. The cause is due to a database access mechanism during database backup. This alarm does not impact database integrity. Databases are backed up on an hourly basis. You see hourly cycles with these log entries:

07/03 14:16:41 INFO 0x10000e 0/0, "exlog.cc", 40 (0x1, 0, 0, 0) DB disk backup: completed OK 07/03 14:15:53 MIN 0x5244e 0/9, "dbtasks.cc", 606 (0, 0, 0, 0) DB server connected task not current code 0 07/03 14:15:53 INFO 0x52455 0/9, "dbcurr.cc", 175 (0x5, 0, 0x18, 0) DB server unable to put currency, status 5, dbn 0

Resolution

If you run Cisco MeetingPlace versions 5.0.0, 5.0.2q, or 5.1.0x, temporarily discontinue all tape backup activities in order to minimize any disruption of service.

Alarm (MIN 0x5244e) has been downgraded to a warning, as there has been no user or system impact noted. The fix will be available in next M3 hotfix build (5.0.2v and 5.1.0aa).

0x6185c WS closing connection 5 on fd -1878073338, user id

Definition

The workstation server closes a Cisco MeetingTime connection.

Resolution

This is not an error indication. It is not generated by Cisco MeetingPlace 4.0 and later systems.

0x6185f MeetingPlace Client 5, Session d67e6007 Reports Err

Definition

The workstation server reports a gateway error.

Resolution

Look up the gateway error code supplied.

0x7006d 0/2, "muserver.cc", 323 (0x3, 0x6, 0x29de, 0xe4a7) Client unit not found in database (ex=0x3)

Definition

A gateway system integrity manager (GWSIM) attempts to connect, but its unit has been removed from the server.

Resolution

Once you find it, the GWSIM service should be disabled or uninstalled. You can identify it by the Ethernet address 00-06-29-DE-E4-A7.

0x70087 The shadow network server is not running

Definition

The shadow network server is configured in the system but does not run. Check to see if network server and shadow server switchover occurs, so that the old shadow server is now your network server, and your old network server is down, in which case, you do not have a active shadow server. When the diskcopy command is issued on the shadow server, this alarm is also generated.

Resolution

If you do not want a shadow server, then set Shadow Server Attached? in the Usage Parameters toNO.

0x70088 Stopping exception log due to flooding

Definition

The system integrity manager (SIM) is flooded with too many exception log entries. Logging stops until the rate drops to a level that can be handled.

Resolution

If this happens during normal system operation, report to Cisco Technical Support as a defect. Otherwise, ignore it.

0x7008b AC power failure indication

Definition

The system restarts due to an alternating current (AC) power interruption. This can be because the power supply failed, someone cycled power, or the power cord was disconnected.

Resolution

Check with the customer for any possible explanation for the power interruption. Contact Cisco Technical Support for further investigation.

0x700c6 Power supply fan “n” cooling failure

Definition

The power supply fan does not cool down the unit.

Resolution

Check to see if the power supply “n” filter needs to be replaced. If the filter is clean or the problem is not corrected after the filter is changed, the power supply unit might need to be replaced.

0x700bb Power supply fan “n” is failing

Definition

There is a problem with the power supply fan.

Resolution

Check to see if the power supply “n” filter needs to be replaced. If the filter is clean or the problem is not corrected after the filter is changed, the power supply unit might need to be replaced.

0x700cb A power supply is failing

Definition

In the Cisco MeetingPlace Audio Server 8112, one of the two power supplies fails.

Resolution

Have service personnel schedule downtime on the server to replace the bad power supply as soon as possible.

0x90017 Bad event code, code=42

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x90019 (EX_NO_ERROR) "Information event, param1=%x, par2=%x, par3=%x, par4%x"

Definition

This is not an error. It is used to log an information message. Each place that logs this messages can put different values for each of the parameters.

Resolution

This is not an error and no fix is required.

0x9001a (EX_CACHE_FAIL_PROMPT_NUM_TOO_LARGE) "(FileCached)Invalid recnum=%x, Dir=%x, Disk=%x"

Definition

A file ID that was already cached was being added to the lookup tables of cached prompts, but the record number for the prompt was too large. The file ID has a record number that is greater than the maximum number of prompts in the system. It is an invalid record number, because the prompt associated with the file ID does not exist.

Resolution

There is an inconsistency between the ID that was cached and the one being added. This is an internal software inconsistency. Escalate the problem to Cisco Technical Support.

0x9001b (EX_FILEID_CACHE_FULL) "(FileCached)File array full, index=%x"

Definition

An attempt to add a file ID that was already cached to the lookup tables of cached files failed because the table was full. More files are cached than originally planned. The file is played from the file system instead of from the cached location. This does not impact system operation unless the system is very heavily loaded.

Resolution

Notify Cisco Technical Support so that the array can be increased.

0x9001c (EX_UNCACHE_FILEID_NOT_FOUND) "(UnCacheId) File id was not cached, rec=%x, disk=%x, dir=%x"

Definition

An attempt to uncache a file ID from the lookup tables failed because the file was not already cached. If an inconsistency exists, the incorrect file ID in a prompt may be played. This is caused when an invalid file ID is passed or when the file was already uncached.

Resolution

Notify Cisco Technical Support so that problem can be analyzed. Look for inconsistent prompts being played.

0x9001d (EX_UNCACHE_FAIL_PROMPT_NUM_TOO_LARGE) "(UnCacheId)Prompt id invalid, rec=%x, disk=%x"

Definition

An attempt to uncache a prompt from the lookup tables failed because the record number of the prompt was too large. This is caused when an invalid file ID is passed. The prompt does not exist.

Resolution

Notify Cisco Technical Support so that problem can be analyzed.

0x9001e (EX_INVALID_RESOURCE_FOR_PROC) "(EvtPortReq)Only Port/Conf ID excepted, resc=%x"

Definition

In the EvtPortReq routine, a client request was received to perform an operation on a port or conference, but the ID Resource type was not either type. An invalid ID Resource type means that we cannot identify the port to where we should perform the request. The cause is that an invalid file ID was passed. The client may have confused a PortId or ConferenceId with another type of ID.

Resolution

Notify Cisco Technical Support so that problem can be analyzed.

0x9001f (EX_PORT_EVENT_PROC_FAILED) "(MidLevel)Failed event processing, erc=%x, Req=%x, evt=%x"

Definition

This alarm indicates a failure to process an event request for a port.

Resolution

Analyze the related error in the event log to determine the cause, as well as the primary error code. If you cannot determine the cause, notify Cisco Technical Support so that the problem can be analyzed.

0x90020 (EX_CONF_NUM_TOO_BIG) "(ValidatePortID)Conference num in req too big, num=%x"

Definition

Changes made on a conference had a conference number in the file ID that is bigger than the maximum allowed. Cannot attempt to perform request. This error occurs because the client request is invalid. A conference ID could have been mixed with a file ID.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90021 (EX_RESOURCE_INVALID_FOR_PORT) "(ValidatePort)Resource type invalid for port, type=%x"

Definition

The Resource Type of the ID is not the correct one for a port. The ID does not specify a port, but some other type of resource.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90022 (EX_SUBRESOURCE_INVALID_FOR_PORT) "(ValidatePort)SubResource type invalid for port, type=%x"

Definition

The SubResource Type of the ID is not the correct one for a port. The ID does not specify a port. Instead, the ID specifies some other type of resource.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90023 (EX_PORT_NUM_TOO_BIG) "(ValidatePort) Port num is too big, num=%x"

Definition

The ID has a port number that is bigger than the maximum allowed. The operating system cannot attempt to perform the request. The ID may not be a portID but some other type of ID.

Resolution

Notify Cisco Technical Support so that problem can be analyzed.

0x90024 (EX_PORTID_TRAILER_INVALID) "(ValidatePortID)Trailer in ID is invalid, trailer=%x"

Definition

The ID has a trailer value that is invalid for an ID. The operating system cannot attempt to perform the request because other data in the ID may also be corrupted. The client may have sent an invalid ID, or the ID may have been overwritten.

Resolution

Notify Cisco Technical Support so that problem can be analyzed.

0x90025 (EX_RESOURCE_INVALID_FOR_CONF ) "(ValidateConf)Resource type invalid for conf, type=%x"

Definition

The Resource Type of the ID is not the one for a conference. The ID does not specify a conference port, but some other type of resource.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90026 (EX_SUBRESOURCE_INVALID_FOR_CONF) "(ValidateConf)SubResource type invalid for conf, type=%x"

Definition

The SubResource Type of the ID is not the one for a conference. The ID does not specify a conference, but some other type of resource.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90027 (EX_CONFID_TRAILER_INVALID) "(ValidateConfID)Trailer in ID is invalid, trailer=%x"

Definition

The ID has a trailer value invalid for an ID. Cannot attempt to perform the request because other data in the ID may also be corrupted. The client may have sent an invalid ID, or the ID may have been overwritten.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90028 (EX_INVALID_PORT_ID) "(EvtPortReq)Invalid Port ID, erc=%x"

Definition

The ID is not that of a port. Cannot service a request on an invalid port. The client may have sent an invalid ID, or the ID may have been overwritten.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90029 (EX_INVALID_CONF_ID) "(EvtPortReq)Invalid Conference ID, erc=%x"

Definition

The ID is not that of a conference. Cannot service a request on an invalid conference. The client may have sent an invalid ID, or the ID may have been overwritten.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x9002a (EX_MIDLEVEL_FAIL_ADD_SET) "(MidLevel)fail to add an event to the set,evt=%x, err=%x"

Definition

The operating system (OS) system call evtaddset fails to add an event to the list of events the thread waits for. This issue can be a serious operating system (OS) problem.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x9002b (EX_EVTPOLL_FAIL) "(MidLevel)System call evtpoll failed, err=%x"

Definition

The system call evtpoll fails while it waits for an event. This can be a serious operating system (OS) problem.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x9002c (EX_MIDLEVEL_TIMEOUT) "(MidLevel)Evtpoll timed out"

Definition

Cisco MeetingPlace timed out while it waited for an event.

Resolution

This message is for information only. It is not an error.

0x9002d (EX_MIDLEVEL_RECEIVED_EVENT) "(MidLevel)Evtpoll received an event, evt=%x, data=%x"

Definition

The thread received an event which will begin to process. This occurs when another thread notifies this thread of an event.

Resolution

This is an information message only. It is not an error.

0x9002e (EX_STARTPLAYLIST_INVALID_ID) "(StartPlayFileList)Invalid Resource Type in ID, type=%x"

Definition

The Resource type in the ID on which the file list was requested to play is invalid. The system can only play to a Port Resource Card (PRC) port or to a Master Switch Controller (MSC) port. This error occurs because an invalid ID was passed by the client. The ID may have been overwritten.

Resolution

The client must make requests with a valid ID.

0x9002f (EX_STARTPLAYLIST_INVALID_STATE) "(StartPlayFileList)Invalid state, status=%x"

Definition

The port should not already be playing a playlist command when a new playlist command is received from a client. This alarm can result when a client sends a new command before the previous one was completed.

Resolution

Make sure the client does not queue requests.

0x90030 (EX_STARTPLAYLIST_INVALID_NUM_FILES) "(StartPlayFileList)Invalid num files in request=%x"

Definition

The number of files in the playlist request is invalid. There are either too many files to play or none at all. The request is not processed and an error is sent back to the client.

Resolution

Make sure the client sends a correct request.

0x90031 (EX_STARTPLAYLIST_INVALID_NUM_GROUPS) "(StartPlayFileList)Invalid num groups in request=%x"

Definition

The number of groups in the playlist request is invalid. There are either too many groups to play or none at all. The request is not processed and an error is sent back to the client.

Resolution

Make sure the client sends a correct request.

0x90032 (EX_STARTPLAYLIST_OP_IN_PROGRESS) "()Currently performing an operation=%x"

Definition

A client request to play a file or list of files was received, but the port is in the middle of a performance of another file operation on the port.. The ability to queue at this level is not implemented.

Resolution

Make sure the client does not send a new request until the previous one is completed and acknowledged.

0x90033 (EX_NUM_IDS_IN_GROUP1_NULL) "(StartPlayFileList)No ids specified in first group=%x"

Definition

There were no IDs specified in the first group in the playlist client request. There must be at least one ID in the first group. Only the last group can have a count of zero IDs.

Resolution

Make sure the client does not send an invalid request.

0x90034 (EX_PLAYLIST_SM_OVERFLOW) "(PlayFileListSM)Overflow the OpStatus array, head=%x, tail=%x"

Definition

There were no IDs specified in the first group in the playlist client request. There must be at least one ID in the first group. Only the last group can have a count of zero IDs.

Resolution

Make sure the client does not send an invalid request.

0x90035 (EX_PL_SM_OPENFILE_FAIL) "(PlayFileListStateMachine)open file fail, err=%x"

Definition

A request to the file system to open a file failed. The file cannot be played and play of the entire file list is aborted. The client is notified of the failure and the ID that caused the error is returned. This occurs when the client sends an invalid file ID or the file system is corrupted.

Resolution

Make sure the ID is invalid. If it is valid, you must fix the file system.

0x90036 (EX_LOG_ID_1) "(Any)Log an ID: Resc=%x,Subr=%x, Idx=%x, Seq=%x"

Definition

This alarm is used to log an ID in the event log. You can examine the previous entries in the log to determine why the ID was logged. The alarm logs the Resource, Subresource, index (record number) and the SequenceNumber.

Resolution

Check the previous entries in the log.

0x90037 (EX_LOG_ID_2) "(Any)Log an ID: (Dir,Disk) App1=%x,Reserv=%x, Trailer=%x"

Definition

This alarm is used to log an ID in the event log. You can examine the previous entries in the log to determine why the ID was logged. The alarm logs the App1 specific value (Dir and Disk), a reserved field, and the Trailer.

Resolution

Check the previous entries in the log.

0x90038 Received a PLayListCompleted evt, rcvd=%x

Definition

An unexpected playlist was received and the event completed. The list of outstanding queued requests can be corrupted, or an event may have been lost.

Resolution

This is an internal software inconsistency problem. This is a harmless race condition and is demoted to Warning as of Cisco MeetingPlace Server version 5.2.1.4.

0x90039 (EX_EVT_ENTRY_TOO_BIG) "(Free/ClearEntry)Entry number out of bounds, max=%x, entry=%x"

Definition

The entry into the TV events table is out of bounds (it is too large).

Resolution

This is an internal software inconsistency problem. Escalate the problem to Cisco Technical Support.

0x9003a (EX_EVT_ENTRY_NOT_FREE) "(ClearEntry)Cannot clear an entry that is not free, entry=%x"

Definition

There was an attempt to clear an entry that is not free into the TV event table. The entry cannot be cleared unless it is free.

Resolution

This is caused by an internal software inconsistency problem. Escalate the problem to Cisco Technical Support.

0x9003b (EX_EVT_TABLE_FULL) "(GetFreeEntry)table is full, scan=%x"

Definition

Failed to find a free entry in the table.

Resolution

This is caused by an internal software inconsistency problem. Escalate the problem to Cisco Technical Support so that the table size can be increased.

0x9003c (EX_EVT_NO_FREE_ENTRY) "(TVAPIHandler)Failed to get a free entry for event,err=%x"

Definition

Failed to get a free entry in the event table for the next TV event. The system may be under heavy load, so it cannot process all events in a timely manner. There may be an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support so that the table size can be increased and the problem can be analyzed.

0x9003d (EX_TV_GET_EVENT_FAIL) "(TVAPIHandler)Failed to get a TVAPI event,err=%x"

Definition

Failed to get an event from the TVAPI. There may be a problem with the TVAPI.

Resolution

Check the event log for related entries that may indicate how to fix the problem.

0x9003e (EX_TV_EVT_CODE_INVALID) "(TVAPIHandler)Received an event with an invalid code=%x"

Definition

The event received from the TVAPI has an invalid code. There may be a problem with the TVAPI. Check the event log for related error entries. It may be a new code that is not yet accepted by the Call Processing (CP) module. There is corruption in the event message received.

Resolution

Check the event log for entries that can indicate how to fix the problem. Escalate the problem to Cisco Technical Support for further analysis.

0x9003f (EX_EKILL_FAILED) "()Failed to send an event=%x, err=%x, ptid=%x, evtdata=%x"

Definition

The ekill operating system (OS) system call failed. This can be caused by an OS problem. Check the other parameters. The value for err should give the reason the OS failed.

Resolution

Check the event log for entries that can indicate how to fix the problem. Escalate the problem to Cisco Technical Support for further analysis.

0x90040 (EX_TV_ENTRY_ALREADY_FREE) "(TVFreeEntry)Entry already free, err=%x, entry=%x"

Definition

An attempt was made to free an entry in the event table that was already free. This can occur when a variable is overwritten, when there is a stack overflow, or as a result of an internal software inconsistency

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90041 (EX_TV_INVALID_PORT_TYPE) "(TVHandler)Not Port or Conference type=%x"

Definition

The TV event received, playlist done, contains a type that is neither a T1 port nor a conference port. The type must be one of those two types. The TVAPI may have sent a corrupted message, or the TV event table may have been corrupted or overwritten. The problem is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90042 (EX_TV_HEAD_TAIL_DIFFERENT) "(PlayListSM)Head and tail not equal, head=%x, tail=%x"

Definition

An event that a file has completed play is received. In this state, the state machine needs to have only one file queued, so the head and the tail pointers are equal. This alarm occurs when the state machine is out of synch. It may have lost some TVAPI events.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90043 Num open files should be 1, num=%x

Definition

An event that a file has completed play was received. In this state, the state machine needs to have only one file queued, so that the current number of open files is equal to 1. However, this is not the case. This alarm occurs when the state machine is out of synch.. It may have lost some TVAPI events. A hard disk that fails and causes read/write errors can also trigger this alarm.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90044 (EX_CLOSEFILE_FAIL) "()Close file fail, err=%x, fh=%x, Status=%x, DTMFmap=%x"

Definition

A request to the file system to close a file fails. The client is notified of the failure, and the ID that caused the error is returned. This error occurs when the file system is corrupted after the file plays.

Resolution

Make sure the ID is invalid. If it is valid, you must fix the file system.

0x90045 (EX_PL_SM_FILE_NOT_OPEN) "(PlayFileListSM)File should have been opened, stat=%x"

Definition

The system is in the PL_PLA_FILE state, and the file to be played should had been previously opened, but it was not. The error is logged and the play operation is aborted.

Resolution

This error is caused by an internal software inconsistency. Report the error to Cisco Technical Support so that it can be further analyzed.

0x90047 (EX_NOT_A_PORT_ID) "(CPGetIDPortNum)Cannot get the port num from a non-portID=%x"

Definition

The system attempts to get the port number from an ID that is not a port ID. The ID is for another type of resource.

Resolution

Make sure that a port ID is passed, and not an ID of a different resource.

0x90048 (EX_NOT_A_CONF_ID) "(CPGetIDConfNum)Cannot get the conference num from a non-confID=%x"

Definition

The system attempts to get the conference number from an ID that is not a conference ID. The ID is for another type of resource.

Resolution

Make sure that a conference ID is passed, and not an ID of a different resource.

0x90049 (EX_NOT_A_VFILE_ID) "(CPGetIDDiskDirNum)Cannot get the disk/dir num from a non-VfileID=%x"

Definition

The system attempts to get the disk/dir number from an ID that is not a voice file ID. The ID is for another type of resource.

Resolution

Make sure that a voice file ID is passed, and not an ID of a different resource.

0x9004a (EX_MORE_Q_THAN_EXPECTED) "(PlayFListSM)Was not expecting more files queue, tail=%x, head=%x"

Definition

While in the PL_WAIT_FILE_2 state, the system receives an event that informs it that the file at the head of the queue completes play. It needs to be able to begin to play the file list, which should be the only element queue. This is not the case. This problem occurs because of an inconsistency in the state machine.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9004b (PlayFListSM)Invalid state for the state machine

Definition

The state is invalid for the PlayListStateMachine. There is an inconsistency in the state machine.

Resolution

This is an internal software inconsistency. Escalate this problem to Cisco Technical Support so that the problem can be analyzed.

0x9004c (EX_FILE_NOT_CACHED) "(BuildTVAPIList)File not cached, Port=%x,fConf=%x,idIndex=%x"

Definition

The file ID is not cached. Cisco MeetingPlace cannot try to build a list of cached file IDs with a file ID that is not cached.

Resolution

This is an internal software inconsistency. Escalate the problem to Cisco Technical Support so that the problem can be analyzed.

0x9004d (EX_FILEID_NOT_CACHED) "(GetCachedPtr)The file id is not cached, cannot get the ptr"

Definition

An attempt to get the pointer of the location where the prompt is cached in the Port Resource Card (PRC) or Master Switch Controller (MSC) card is made for a prompt that is not cached.

Resolution

Escalate the problem to Cisco Technical Support so that the problem can be solved.

0x9004e (EX_RT_EVT_PORT_TOO_BIG) "()Received a TV Event with invalid port num=%x, evt=%x"

Definition

The port number in an event from the TVAPI is out of range (too large). The message is discarded because it cannot be processed. This occurs because there is a problem with the operation of the TVAPI, or the event is corrupted in the queue.

Resolution

Escalate the problem to Cisco Technical Support so that the problem can be solved.

0x9004f (EX_EVT_CONF_TOO_BIG) "()Received a TV Event with invalid conf num=%x, evt=%x"

Definition

The conference number in an event from the TVAPI is out of range (too large). The message is discarded because it cannot be processed.

Resolution

Check the exception log for related entries to determine the cause of the failure. Escalate the problem to Cisco Technical Support so that the problem can be solved.

0x90050 (EX_PC_PLACE_CALL_FAIL) "(PlaceCallMainLoop)Fail to place call, err=%x"

Definition

Fails to process a request from a client to place a call. There is a problem with the operation of the TVAPI, or the event is corrupted in the queue.

Resolution

Follow the suggestions for related errors, such as 90051 and 90052.

0x90051 (EX_PC_INVALID_EVENT) "(PlaceCallMainLoop)Received invalid event, evt=%x"

Definition

The thread receives an invalid event, which it cannot process.

Resolution

This is an internal software inconsistency. Escalate the problem to Cisco Technical Support so that the problem can be solved.

0x90052 (EX_REALTIME_FAIL_ADD_SET) "(RealTime)fail to add an event to the set,evt=%x, err=%x"

Definition

The operating system (OS) system call evtaddset fails to add an event to the list of events the thread waits for. This can be a serious operating system (OS) problem.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90053 (EX_REALTIME_TIMEOUT) "(RealTime)Evtpoll timed out"

Definition

Cisco MeetingPlace times out while it waits for an event.

Resolution

This is an informational message only, not an error.

0x90054 (EX_REALTIME_EVTPOLL_FAIL) "(RealTime)System call evtpoll failed, err=%x"

Definition

The system call evtpoll fails while the system waits for an event. This can be a serious operating system (OS) problem.

Resolution

Notify Cisco Technical Support so that the problem can be analyzed.

0x90055 (EX_REALTIME_RECEIVED_EVENT) "(RealTime)Evtpoll received an event, evt=%x, data=%x"

Definition

The thread was notified by another thread of an event to be processed.

Resolution

This is an informational message only, not an error.

0x90056 (EX_REALTIME_INVALID_EVENT) "(RealTime)Evtpoll rcv invalid event, evt=%x, data=%x"

Definition

The thread received an event that is not one of the expected ones. This occurs when one thread sends incorrect events to another, wrong thread.

Resolution

This is a software inconsistency. Notify Cisco Technical Support so that the problem can be further analyzed.

0x90057 (EX_REALTIME_CONF_OP_FAILED) "(RealTime)Op conf port fail, evt=%x, data=%x, port=%x"

Definition

The operation requested on the conference fails. For a more complete description of the error, see the related entries in the event log.

Resolution

See related entries in the event log for a recommended action.

0x90058 (EX_REALTIME_PORT_OP_FAILED) "(RealTime)Op in port fail, evt=%x, data=%x, port=%x"

Definition

The operation requested on the conference fails. For a more complete description of the error, see the related entries in the event log.

Resolution

See the related entries in the event log for a recommended action.

0x90059 (EX_REALTIME_CONF_AREAD_FAIL) "(RealTime)Conf aread fail,err=%x,evt=%x,evtdata=%x,conf=%x"

Definition

There was an error while processing the event that an asynchronous read on a conference port completed.

Resolution

See related entries in the event log for a recommended action.

0x9005a (EX_REALTIME_PORT_AREAD_FAIL) "(RealTime)Port aread fail,err=%x,evt=%x,evtdata=%x,conf=%x"

Definition

There was an error while processing the event that an asynchronous read on a port completed.

Resolution

See the related entries in the event log for a recommended action.

0x9005b (EX_REALTIME_CONF_AWRITE_FAIL) "(RealTime)Conf awrite fail,err=%x,evt=%x,evtdata=%x,conf=%x"

Definition

There was an error while processing the event that an asynchronous write on a conference port completed.

Resolution

See the related entries in the event log for a recommended action.

0x9005c (EX_REALTIME_PORT_AWRITE_FAIL) "(RealTime)Port awrite fail,err=%x,evt=%x,evtdata=%x,conf=%x"

Definition

There was an error while processing the event that an asynchronous write on a port completed.

Resolution

See the related entries in the event log for a recommended action.

0x9005d (EX_EVT_PORT_TOO_BIG) "()Port invalid,port=%x,evt=%x,offset=%x, buffer=%x"

Definition

The port number received in a TVAPI event is too big. The maximum port number allowed is CM_MAX_ACCESS_PORTS. This can occur when the TVAPI has a stack or data overflow and the message in the Event table is corrupt.

Resolution

See the related entries in the event log for more information. Escalate the problem to Cisco Technical Support.

0x9005e (EX_RT_EVT_CONF_TOO_BIG) "(RealTime)Conf port invalid,port=%x,evt=%x,offset=%x, buffer=%x"

Definition

The conference port number received in a TVAPI event is too big. The maximum conference port number allowed is CM_MAX_CONF_RSRC_PORTS. This can occur when the TVAPI has a stack or data overflow and the message in the Event table has been corrupted.

Resolution

See the related entries in the event log for more information. Escalate the problem to Cisco Technical Support.

0x9005f (EX_RT_TV_INVALID_PORT_TYPE) "(RealTimeML)Not Port or Conference type=%x"

Definition

The TV event received, Play buffer done, contains a type that is neither a port nor a conference port. It is required to be one of those two types. The TVAPI could have sent a corrupted message, or the TV Event table could have been corrupted or overwritten. This is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90060 (EX_RT_TV_INVALID_EVT_CODE_TYPE) "(RealTimeML)Invalid Evt code type=%x, evt=%x"

Definition

The TV event received, Play buffer done, contains a message code that is not an expected type. It must be a Done Buffer Event. The TVAPI could have sent a corrupted message, or the TV Event table could have been corrupted or overwritten. This is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90061 (EX_ML_DEACTIVATE_PORT_FAIL) "(EvtPortReq)Failed to deactivate EvtData=%x, err=%x"

Definition

Fails to deactivate the port as specified in the request from the client.

Resolution

Search the event log for related entries to determine the cause of the failure.

0x90062 (EX_ML_ANSWER_CALL_FAIL) "(EvtPortReq)Failed to answer call, port=%x, err=%x"

Definition

Fails to answer a call in the port as specified in the request from the client.

Resolution

Search the event log for related entries to determine the cause of the failure.

0x90063 (EX_ML_DISCONNECT_CALL_FAIL) "(EvtPortReq)Failed to disconnect call, port=%x, err=%x"

Definition

Fails to disconnect a call in the port as specified in the request from the client.

Resolution

Search the event log for related entries to determine the cause of the failure.

0x90064 (EX_ML_PAUSE_PLAY_FAIL) "(EvtPortReq)Failed to pause play, port=%x, err=%x"

Definition

Fails to pause play in the port as specified in the request from the client.

Resolution

Search the event log for related entries to determine the cause of the failure.

0x90065 (EX_ML_PAUSE_RECORD_FAIL) "(EvtPortReq)Failed to pause record, port=%x, err=%x"

Definition

Fails to pause record in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x90066 (EX_ML_PLAY_FILE_FAIL) "(EvtPortReq)Failed to play file, port=%x, err=%x, port type=%x"

Definition

Fails to play the file in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x90067 (EX_ML_PLAY_LIST_FAIL) "(EvtPortReq)Failed to play list, port=%x, err=%x, port type=%x"

Definition

Fails to play the list in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x90068 (EX_ML_RECORD_FAIL) "(EvtPortReq)Failed to record, port=%x, err=%x"

Definition

Fails to record in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x90069 (EX_ML_RESUME_PLAY_FAIL) "(EvtPortReq)Failed to resume play, port=%x, err=%x"

Definition

Failed to resume play in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x9006a (EX_ML_RESUME_RECORD_FAIL) "(EvtPortReq)Failed to resume record, port=%x, err=%x"

Definition

Failed to resume record in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x9006b (EX_ML_STOP_PLAY_FAIL) "(EvtPortReq)Failed to stop play, port=%x, err=%x"

Definition

Failed to stop play in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x9006c (EX_ML_STOP_RECORD_FAIL) "(EvtPortReq)Failed to stop record, port=%x, err=%x"

Definition

Failed to stop record in the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x9006d (EX_ML_GET_RQ_FAIL) "()GetRequest fail, evt=%x, err=%x, evtdata=%x"

Definition

Failed to create an object with the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x9006e (EX_ML_GET_RQ_TEXT_FAIL) "()GetRequest Text fail, evt=%x, err=%x, evtdata=%x"

Definition

Failed to get a pointer to the text of the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x9006f (EX_ML_ACTIVATE_PORT_FAIL) "(EvtPortReq)Failed to activate port=%x, err=%x"

Definition

Failed to activate the port as specified in the request from the client.

Resolution

Search the event log for other related entries to determine the reason for the failure.

0x90070 (EX_PORT_RQ_STACK_FULL) "()Stack is full, cannot q req, ptr=%x, port=%x"

Definition

Received a client request to perform, but cannot add another request because the stack of outstanding operations is full.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90071 (EX_PREV_OP_NOT_IDLE) "()Prev op was not idle, ptr=%x, port=%x, status=%x"

Definition

Received a client request to perform a PlayFileList, but the stack had a previous operations that was not paused. Cannot perform an operation on a port if the previous operation is not paused. This problem can occur when too many requests are incomplete, and the client sends an operation request and does not wait for the previous one to complete.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90072 (EX_PLSM_NO_TV_EVENT) "(PlayListSM)Did not receive a TVAPI event, state=%x, port=%x"

Definition

This state should be processed with a TVAPI event, but none was received. Either an invalid event was received, or something other than a TVAPI event was received.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90073 (EX_CANNOT_PLAY_INVALID_PORTID) "()The PortID in the request is diff than in array, port=%x"

Definition

The client sent a request to make an operation on a port, but the PortID included in the message is different than the PortID in the array. The wrong key is used by the client, and it cannot perform the operation. The client may have an old PortID (with an old key). The PortStatus table may be corrupted.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90074 (EX_RT_START_PORT_OP) "(EvtStartPortOp)Req op is not play/record, port=%x, op=%x"

Definition

The real-time threads can only service requests to play or record a file. The requested operation is neither one. This occurs when invalid data is sent to the real-time thread. There can be corruption on the midlevel routines, or in the Port or Conference status array.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90075 (EX_RT_BUF_NOT_IDLE) "(EvtStartPortOp)The A/B bufs were not idle, port=%x, stat=%x"

Definition

The status of the A and B buffers was not idle before the messages began to play. The status must be idle, otherwise buffers still played by the Port Resource Card (PRC)/Master Switch Controller (MSC) are overwritten. The buffers can be genuinely idle, but the flag may not have been updated accordingly. The buffers are still played, and this operation should not have been scheduled so early.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90076 (EX_RT_BUF_NUM_INVALID) "(EvtAreadComplete)The buffer number is too large, port=%x, buf=%x"

Definition

The routine received a notification that a buffer was filled from the file system, but the buffer number is out of bounds. This is caused by a corruption in the event received from the file system. The initial values send in the aread command were invalid.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90077 (EX_RT_BUF_STATE_INVALID) "(EvtAreadComplete)Buffer state not readfromdisk, port=%x, buf=%x"

Definition

Cisco MeetingPlace received an event that states that data has been read from the file system into the buffer, but that the buffer was in an unexpected state. This can occur due to a corruption of the internal data structures for the port or conference port in the event received from the file system.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90078 (EX_RT_INVALID_BLOCK) "(EvtAreadComplete)Block read is invalid, port=%x, err=%x"

Definition

The block read from the file system does not belong to the file that is played. Cisco MeetingPlace cannot play a block that does not belong to the file. This is caused by a file system corruption.

Resolution

Execute the file system check utility to fix the internal file system data structures on the disk.

0x90079 (EX_RT_FAIL_TV_PLAY_BUF) "(EvtAreadComplete)TVAPI fail to play a buffer, port=%x, err=%x, buf=%x"

Definition

A command to the TVAPI to play a buffer failed. The buffer is part of a file that is played. Either there is a problem in the TVAPI or the states in Call Processing (CP) do not match the TVAPI states.

Resolution

This is an internal software inconsistency. Escalate this problem to Cisco Technical Support.

0x9007a (EX_RT_FAIL_FS_PLAY_BUF) "()File System fail to play, port=%x, err=%x, buf=%x"

Definition

A command to the file system to play a block from a file failed.

Resolution

Check other errors related to the file system for suggestions on how to solve the problem.

0x9007b (EX_RT_EVT_DONE_BUF_ENTRY) "(RealTime)Invalid entry, TV evt buf done, err=%x, buf=%x"

Definition

Received an event from the TVAPI that states that the buffer has completed play, but the entry into the array of received TV events did not allow to free the received event. This error is caused by a software inconsistency in the TV event received table.

Resolution

Escalate this problem to Cisco Technical Support so that the problem can be analyzed.

0x9007c (EX_RT_INVALID_BUF_STATE) "(DoneTVBuffer)Buffer"(DoneTVBuffer)Buffer state invalid, is=%x, should=%x, port=%x, conf=%x"

Definition

While a file is played, Cisco MeetingPlace receives an event from the TVAPI that states that the buffer completed play, but the state of the buffer in the port data structure showed that the buffer was not playing. This problem is caused by a software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support so that the problem can be analyzed.

0x9007d (EX_RT_NEXT_BUF_IDLE) "(EvtTVBufDone)Buffer idle, buf=%x, port=%x, conf=%x"

Definition

Cisco MeetingPlace detected the next buffer to be in the idle state, even though it should be reading from the disk. This problem is caused by a software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support so that the problem can be analyzed.

0x9007e (EX_ML_EVT_PORT_OP_RESP_FAIL) "(MidLevelML)Evt port op resp failed, err=%x, evtdata=%x"

Definition

Cisco MeetingPlace received an event from the real-time thread, a port operation response, but an error occur while the response was processed. Check in the event log for related entries that can help you identify the problem.

Resolution

Check the description of related entries for suggestions on an action to take.

0x9007f (EX_ML_EVT_CLIENT_REQ_ERROR) "(EvtClientReq)Error processing request req=%x,err=%x,EvtData=%x"

Definition

Cisco MeetingPlace detected an error while it processed a request from a client.

Resolution

Check the description of related entries for a suggestion on an action.

0x90080 (EX_RT_REQ_TO_STOP) "()The MidLevel thread requested to stop, or error."

Definition

The real-time thread received a command to stop play or recording of a file. Must start to clear the operations. This alarm is not an error. It can happen under normal circumstances.

Resolution

Unless you detect abnormal conditions, ignore this alarm.

0x90081 (EX_RT_EVT_BUF_DONE_FAIL) "(RealTimeMainLoop)Process of TV buf done failed, err=%x"

Definition

Failed to process the buffer-process completion event received from the TVAPI.

Resolution

Check the fix description for other related errors to determine an appropriate course of action.

0x90082 (EX_ML_TV_EVT_FAIL) "(MidLevelMainLoop)Fail to process event, err=%x,evt=%x,port=%x"

Definition

Failed to process the event received from the TVAPI that informs about the completion of an operation or of an unsolicited event.

Resolution

Check the description for other related errors to determine a course of action.

0x90083 (EX_ML_INCALL_NUM_TONES) "(EvtIncomimgCall)Too many tones received=%x,max=%x,port=%x"

Definition

The number of tones that receive an incoming call event from the TVAPI is out of range (too large). The TVAPI is confused and the port sent too many tones. The table that stores the TVAPI may have been overwritten.

Resolution

Check the physical port to make sure that it works properly. If port is functional, escalate the problem to Cisco Technical Support for further analysis.

0x90084 (EX_ML_ANSWER_CALL_ID) "(EvtClientReq)The ID send to answer call is invalid, port=%x"

Definition

The Call Processing (CP) client sent a request to answer an incoming call, but the ID in the client request is not identical to the one that is in the array. The client is confused and sends the wrong port ID. The port array has been corrupted and the port ID overwritten.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90085 (EX_ML_TV_ANSWER_CALL) "(AnswerCall)Failed to go offhook in the port, port=%x,err=%x"

Definition

Failed to go off hook for (answer) a new incoming call. The TVAPI is confused and the Call Processing (CP) module is out of synch with it. The port array may have overflowed.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90086 (EX_GET_SESSION_ID_FAIL) "(EvtIncomingCall)Fail to get a SI session#, port=%x,err=%x"

Definition

Cisco MeetingPlace failed to make a request to the system integrity manager (SIM) to create a new session ID. This error is caused by a malfunction of the SI module.

Resolution

Check the event log for related entries to discover the cause of the problem. Escalate the problem to Cisco Technical Support for further analysis.

0x90087 (EX_ML_SEND_FAIL) "()Fail to notify VUI, port=%x,err=%x"

Definition

Failed to send an event to the client. This problem is caused by problems with the IMC. The Voice User Interface (VUI) may have crashed.

Resolution

You may need to restart the system if there is more than one entry in the log and it is not possible to access the system.

0x90088 (EX_ML_IC_CALL_BAD_STATE) "(AnswerCall)Invalid state, AnswerCall cmd, port=%x,state=%x"

Definition

The port is not in the appropriate state to process an incoming call, so it cannot accept an answer call command from the client. This problem occurs because the Call Processing (CP) module and the client are out of synch.

Resolution

Hang up on the port so that both modules synchronize. Escalate this problem to Cisco Technical Support for further investigation.

0x90089 (EX_ML_PL_BAD_STATE) "(StartPlay)Invalid state,PlayFile cmd, port=%x, state=%x"

Definition

The port is not in a valid state while it processes a client request to play a file. This problem occurs because the Call Processing (CP) module and the client are out of synch.

Resolution

Hang up on the port so that both modules synchronize. Escalate this problem to Cisco Technical Support for further investigation.

0x9008a (EX_ML_IN_CALL_PORT_DEAC) "(EvtIncomingCall)Port is deactive, port=%x"

Definition

Cisco MeetingPlace received an incoming call event in a port that was in the deactive state. It cannot accept a call in a port in that state. This problem occurs because the Call Processing (CP) module and the TVAPI are out of synch.

Resolution

Hang up on the port so that both modules synchronize. Escalate this problem to Cisco Technical Support for further investigation.

0x9008b (EX_ML_IN_CALL_PORT_BUSY) "(EvtIncomingCall)Port is busy, port=%x"

Definition

Cisco MeetingPlace received an incoming call event in a port that was busy (in use). It cannot accept a call in a port in that state. This problem occurs because the Call Processing (CP) module and the TVAPI are out of synch.

Resolution

Hang up on the port so that both modules synchronize. Escalate this problem to Cisco Technical Support for further investigation.

0x9008c (EX_CP_GENERAL_ERROR) "()General error in the Call Processing module,%x,%x,%x,%x"

Definition

This is a general error used for several different conditions that should not typically occur.

Resolution

Escalate this problem to Cisco Technical Support for further investigation.

0x9008d (EX_FS_FAIL_ADD_SET) "(FSMainLoop)Fail add event to set, err=%x, evt=%x"

Definition

Cisco MeetingPlace failed to add an event to the set in the FileSystem main loop. This problem is caused by an operating system failure.

Resolution

Escalate this problem to Cisco Technical Support for further investigation.

0x9008e (EX_FS_EVTPOLL_FAIL) "(FSMainLoop)Fail evtpoll call, err=%x, evt=%x"

Definition

Cisco MeetingPlace failed to get an event in the FileSystem main loop. This problem is caused by an operating system failure.

Resolution

Escalate this problem to Cisco Technical Support for further investigation.

0x9008f (EX_FS_RECEIVED_EVENT) "(FSMainLoop)Rcv request for FS, evt=%x, evtdata=%x"

Definition

Cisco MeetingPlace received an event for a file system request.

Resolution

This alarm is only an informational message and it does not indicate an error.

0x90090 (EX_FS_INVALID_EVENT) "(FSMainLoop)Rcv invalid event, evt=%x, evtdata=%x"

Definition

Cisco MeetingPlace received an unexpected event. This problem is caused by an operating system problem.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90091 (EX_FS_GET_RQ_FAIL) "(FSEvtClientReq)Failed to get request, evt=%x, err=%x"

Definition

Cisco MeetingPlace failed to get the request sent by the client. This error is caused by an operating system problem.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90092 (EX_FS_GET_RQ_TEXT_FAIL) "(FSEvtClientReq)Failed to get request text, evt=%x, err=%x"

Definition

Cisco MeetingPlace failed to get the request text sent by the client. This error is caused by an operating system problem.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90093 (EX_FS_CLOSE_FILE_FAIL) "(FSEvtClientReq)Fail to close file, evt=%x, err=%x, handle=%x"

Definition

Cisco MeetingPlace failed to close a file in the file system.

Resolution

Search the event log for other, related entries to discover the cause of the alarm and possible solutions.

0x90094 (EX_FS_DELETE_FILE_FAIL) "(FSEvtClientReq)Fail to delete file, evt=%x, err=%x"

Definition

Cisco MeetingPlace failed to delete a file in the file system.

Resolution

Check for a fix suggestion from related entries in the event log.

0x90096 (EX_FS_OPEN_FILE_FAIL) "(FSEvtClientReq)Fail to open file, evt=%x, err=%x"

Definition

Failed to open a file in the file system.

Resolution

Check related entries in the event log to determine the cause of the problem and find fix suggestions.

0x90097 (EX_FS_SEEK_FILE_FAIL) "(FSEvtClientReq)Fail to seek in a file, evt=%x, err=%x"

Definition

Cisco MeetingPlace failed to seek a file in the file system.

Resolution

Check related entries in the event log to determine the cause of the problem and find fix suggestions.

0x90098 (EX_ML_FAIL_PLAY_FILE) "()Error detected while playing file, err=%x"

Definition

An error is detected, probably by the file system, while a file plays.

Resolution

Check related entries in the event log to determine the cause of the problem and find fix suggestions.

0x90099 (EX_ML_EVT_DONE_TONE) "(EvtDoneTone)Event rcvd not the one expected, err=%x"

Definition

Cisco MeetingPlace received from the TVAPI the invalid event Done Playing DTMF Tones on a port, but that was not the current event for the port. This problem is caused by an internal software inconsistency, out of sequence. The invalid event is sent by the TVAPI.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9009a (EX_ML_INVALID_STATE_DISC) "(Disconnect)Invalid state for disconnect, port=%x, MainStatus=%x"

Definition

Cisco MeetingPlace received a client request to disconnect a port, but the state of the port is not one where a disconnect can be sent to the TVAPI. This problem is caused by an internal software inconsistency, out of sequence. An invalid request was sent by the client.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9009b (EX_ML_HANGUP_FAIL) "(Disconnect)TV API failed to hang up port, port=%x, err=%x"

Definition

The request sent to the TVAPI to hang up the port failed. This error is caused by an internal TVAPI problem. An invalid request was sent by the client. The request sets an invalid state for the port, in which it cannot hang up

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9009c (EX_INVALID_DEACT_LEVEL) "(DeactivatePort)Deact level invalid=%x, port=%x, Conf=%x, evtdata=%x"

Definition

The deactivation level received in the client request is invalid. The messages were corrupted in transmit to the Call Processing (CP) module.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9009d (EX_RQ_Q_NOT_EMPTY) "()Req q is not empty, port=%x, fConf, RqPtr=%x, Req=%x"

Definition

Cisco MeetingPlace received a request that requires the request queue to be empty before it can be serviced. The queue is not empty, so the request cannot be serviced. For example, to set a port in the conference mode so that it can attend a conference, there cannot be a play request currently on the port. This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis. Hang up the call to clear the state of the port, so that the new call starts clean.

0x9009e (EX_SEND_EVENT_FAIL) "(EvtHangup)Fail send incoming event to client, port=%x, err=%x"

Definition

Cisco MeetingPlace failed to send a notification to a client of an incoming event. Search for related entries in the event log to help determine the source of the problem.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9009f (EX_ML_IN_TONES_NUM_TONES) "(EvtIncomingTones)Invalid num of tones=%x, max=%x, port=%x"

Definition

The number of tones received on a port is greater than expected. The messages were corrupted and the number of tones is invalid. The TVAPI sent more than the allowed number of dual-tone multifrequency (DTMF) tones.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900a0 (EX_ML_TONES_BAD_STATE) "(EvtIncomingTones)Invalid State for digits=%x,max=%x,port=%x"

Definition

The number of tones received on a port is greater than expected. The messages were corrupted and the number of tones is invalid. The TVAPI sent more than the allowed number of dual-tone multifrequency (DTMF) tones.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900a1 (EX_FAIL_GET_AB_ADDR) "(TVActivPorts)Fail get A/B buf addr,erc=%x,port=%x,@A=%x,@B=%x"

Definition

Cisco MeetingPlace failed to get the address of the A and B buffers for the specified port. This information is obtained after port initialization, but the port failed to initialize because it was not configured or the Port Resource Card (PRC) was never correctly activated.

Resolution

Run hardware diagnostics on the card. There may be faulty hardware or firmware.

0x900a2 Invalid event rcvd,state=%x,port=%x,conf=%x,code=%x

Definition

This alarm occurs when someone joins a meeting by phone at the same time that the Cisco MeetingPlace server plays the "Now attending..." message. Someone initiates the recording (clicks the recording button in Meeting Console or presses #61, for example). By design, a broadcast message (such as "Now attending...") is not recorded into the meeting. In other words, recording code momentarily stops recording when a message is broadcast to all participants. However, because someone tries to initiate the recording, a conflict occurs that causes this alarm to be generated.

Here is an example of this alarm:

(PLStateM)Invalid event rcvd,state=f8,port=10,conf=0,code=0

Resolution

This alarm is not a problem and can easily be reproduced. No resolution is needed.

0x900a3 (EX_PLSM_BUILDCARD_FAIL) "(PLStateM)BuildCardList failed, err=%x,port=%x,conf=%x,PLState=%x"

Definition

Cisco MeetingPlace failed to build a list of cached prompts to be sent to the Port Resource Card (PRC) or Master Switch Controller (MSC) card to play. Check for related entries in the log to determine the cause of the problem.

Resolution

Follow the instructions for related error entries.

0x900a4 (EX_RT_FAIL_TV_RECORD_BUF) "(EvtStartPortOp)TVAPI fail record,err=%x,port=%x,conf=%x,Buf#=%x"

Definition

The TVAPI failed to record a buffer into the Port Resource Card (PRC) or Master Switch Controller (MSC) buffer. Check for related entries in the log to determine the cause of the problem. The value for the entry err contains the reason the TVAPI failed.

Resolution

Follow the instructions for related error entries.

0x900a5 (EX_RT_INVALID_RQ) "(EvtTVBufDone)Invalid request type=%x,port=%x,conf=%x,Buf#=%x"

Definition

The request type is invalid. Only record and play are accepted in this state. This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x900a6 (EX_RT_FAIL_FS_RECORD_BUF) "()File System fail to record, port=%x, err=%x, buf=%x"

Definition

A command to the file system to record a block to a file failed. Check other errors related to the file system to identify the cause of the problem.

Resolution

Check other errors for a suggestion on how to solve the problem.

0x900a7 (EX_OUTPULSE_TVAPI_FAIL) "(Outpulse)TVAPI fail to outpulse, err=%x, port=%x, fConf=%x"

Definition

A command to the TVAPI to outpulse a string of dual-tone multifrequency (DTMF) tones failed. Analyze the error code with field err for the cause of the TVAPI failure.

Resolution

Check other errors for a suggestion on how to solve the problem.

0x900a8 (EX_ACTIVATE_TVAPI_FAIL) "(ActivatePort)TVAPI fail to activate port=%x, fConf=%x, err=%x"

Definition

A command to the TVAPI to activate a port failed. Analyze the error code with field err for the cause of the TVAPI failure.

Resolution

Check other errors for a suggestion on how to solve the problem.

0x900a9 (EX_CURR_PORTID_INVALID) "()PortID in Req is invalid, port=%x, fConf=%x"

Definition

A request for a port or conference has been received, but the port ID in the request is different than the current port ID of the port. The client does not have the correct port ID. The ID may have been overwritten, or it may be old. It is also possible that the Call Processing (CP) module may have deleted the current port ID and may be invalid.

Resolution

Check other errors for a suggestion on how to solve the problem. Escalate the problem to Cisco Technical Support for further analysis.

0x900aa (EX_PAUSE_PLAY_INVALID_STATE) "(PausePlay)Invalid state for pauseplay,port=%x,RqPtr=%x,State=%x"

Definition

A command to pause play of a file or a list of files cannot be accepted in the current state of the port. Several state values are checked. There must be a play request in the queue of outstanding requests, the main status of the port must be connected, and there must be no requests in the queue. This problem occurs when there is loss of synchronization between the client Voice User Interface (VUI) and the Call Processing (CP) module. The VUI believes that the state of the port is different than the state of the port in the CP module.

Resolution

Hang up in the port; this should resynchronize the VUI and the CP module. Escalate the error log to Cisco Technical Support for further analysis.

0x900ab (EX_PAUSE_PLAY_TVAPI_FAIL) "(PausePlay)TVAPI pause fail,port=%x, fConf=%x,err=%x"

Definition

The command sent to the TVAPI to pause play of a file or list of files failed. Check the value of the error returned by the TVAPI, which is one of the parameters displayed in the message.

Resolution

Check for related errors and for a fix description of the error returned by the TVAPI.

0x900ac (EX_PAUSE_RECORD_INVALID_STATE) "(PauseRecord)Invalid state for pauserecord,port=%x,RqPtr=%x,State=%x"

Definition

A command to pause recording of a file cannot be accepted in the current state of the port. Several state values are checked. There must be a record request in the queue of outstanding requests, the main status of the port must be connected, and there must be requests in the queue. This problem occurs when there is loss of synchronization between the client Voice User Interface (VUI) and the Call Processing (CP) module. The VUI believes that the state of the port is different than the state of the port in the CP module.

Resolution

Hang up in the port to resynchronize the VUI and the CP module. Escalate the error log to Cisco Technical Support for further analysis.

0x900ad (EX_PAUSE_RECORD_TVAPI_FAIL) "(PauseRecord)TVAPI pause fail,port=%x,fConf=%x,err=%x"

Definition

The command sent to the TVAPI to pause recording a file failed. Check the value of the error returned by the TVAPI, which is one of the parameters displayed in the message.

Resolution

Check for related errors and for a fix description of the error returned by the TVAPI.

0x900ae (EX_CANNOT_RECORD_INVALID_PORTID) "(StartRec)PortID, Rq diff than current,port=%x, fConf=%c"

Definition

The client sent a request to make an operation on a port, but the port ID included in the message is different than the port ID in the array. The client supplies the wrong key, and the operation cannot be performed. This problem can occur because the client has an old port ID (with an old key) or the PortStatus table is corrupted.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900af (EX_RESUME_PLAY_INVALID_STATE) "(ResumePlay)Invalid state for ResumPlay,port=%x,p2=%x,p3=%x,p4=%x"

Definition

A command to resume play of a file cannot be accepted in the current state of the port. Several state values are checked. There must be a play request in the queue of outstanding requests, the main status of the port must be connected, and there must be requests in the queue. This problem occurs when there is loss of synchronization between the client Voice User Interface (VUI) and the Call Processing (CP) module. The VUI believes that the state of the port is different than the state of the port in the CP module.

Resolution

Hang up in the port to resynchronize the VUI and the CP module. Escalate the error log to Cisco Technical Support for further analysis.

0x900b0 (EX_CURR_FH_INVALID) "()The fh in Req is diff than current,port=%x,fConf=%x,Rqfh=%x,Currfh=%x"

Definition

The request received has a file handle that is different than the file handle for the current operation. Either the client has overwritten its data area and passed the incorrect file handle to the Call Processing (CP) module, or the CP module has done something similar.

Resolution

Hang up in the port and start a new call, which should start with a clean copy of all the variables. Escalate the problem to Cisco Technical Support for further analysis.

0x900b1 (EX_RESUME_PLAY_TVAPI_FAIL) "(ResumePlay)TVAPI resume play fail, port=%x, fConf=%x, err=%x"

Definition

The command to the TVAPI to resume playing a file failed. Look at the parameter err in the event log to find the reason the TVAPI failed.

Resolution

Follow the fix recommendation for the TVAPI error number from the alarm.

0x900b2 (EX_ABORT_OPERATION) "()Abort all queued requests, port=%x, fConf=%x, Rq=%x"

Definition

All the client requests queued for this port are aborted. The port is in the process of disconnection, so it needs to respond to all that was queued. The Voice User Interface (VUI) and the Call Processing (CP) modules are out of synch, and the port is in the process of disconnection (the connection is closed). All outstanding requests must be cleared so that the next call starts from a known clean initial state.

Resolution

Hang up the call to clear the problem. Escalate to Cisco Technical Support for further analysis.

0x900b3 (EX_INVALID_STATE_FOR_RESUME) "(ResumePlay)Invalid op status, port=%x, fConf=%x, Rq=%x"

Definition

All the client requests that were queued for this port are being aborted. The port is in the process of disconnection, so you need to respond to all that was queued. The Voice User Interface (VUI) and the Call Processing (CP) modules are out of synch, and the port is in the process of disconnection (the connection is being closed). All outstanding requests must be cleared so that the next call starts from a known clean initial state.

Resolution

Hang up the call to clear the problem. Escalate to Cisco Technical Support for further analysis.

0x900b4 (EX_RESUME_RECORD_INVALID_STATE) "(ResumeRecord)Invalid state,port=%x,p2=%x,p3=%x,p4=%x"

Definition

A command to resume recording a file cannot be accepted in the current state of the port. Several state values are checked. There must be a record request in the queue of outstanding requests, the main status of the port must be connected, and there must be requests in the queue. This error occurs when there is loss of synchronization between the client Voice User Interface (VUI) and the Call Processing (CP) module. The VUI believes that the state of the port is different than the state of the port in the CP module.

Resolution

Hang up in the port to resynchronize the VUI and the CP module. Escalate the error log to Cisco Technical Support for further analysis.

0x900b5 (EX_RESUME_RECORD_TVAPI_FAIL) "(ResumeRecord)TVAPI resumeRec fail, port=%x, fConf=%x, err=%x"

Definition

The command to the TVAPI to resume recording a file failed. Look at the parameter err in the event log to find the reason the TVAPI failed.

Resolution

Follow the fix recommendation for the TVAPI error number from the alarm.

0x900b6 (EX_ABORT_RECORD_TVAPI_FAIL) "(StopRecord)TVAPI StopRec fail, port=%x, fConf=%x, err=%x"

Definition

The command to the TVAPI to stop recording a file failed. Look at the parameter err in the event log to find the reason the TVAPI failed.

Resolution

Follow the fix recommendation for the TVAPI error.

0x900b7 (EX_INVALID_STATE_STOP_RECORD) "(StopRecord)Invalid state StopRec,port=%x,fConf=%x,Stat=%x"

Definition

The state of the port for the request before the Stop Record request is invalid. This error may have one of several possible causes. There may be an internal software inconsistency. The Voice User Interface (VUI) may be out of synch with the VUI module and think that a file is being recorded even though it is not. Cisco MeetingPlace may have already stopped play of the file a millisecond before the VUI sent the stop record request, so there is no error, just a timing difference (in which case, the alarm can be ignored).

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900b8 (EX_STOP_PLAY_INVALID_STATE) "(StopPlay)Invalid stat StopPlay,port=%x,fConf=%x,Stat=%x"

Definition

The port was in an invalid state when the Stop Play request was received. This is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900b9 (EX_ABORT_PLAY_TVAPI_FAIL) "(StopPlay)TVAPI StopPlay fail, port=%x, fConf=%x, err=%x"

Definition

The command to the TVAPI to stop play of a file failed. Look at the parameter err in the event log to find the reason the TVAPI failed.

Resolution

Follow the fix recommendation for the TVAPI error.

0x900ba (EX_INVALID_STATE_FOR_STOP_PLAY) "(StopPlay)Invalid state for port, port=%x, fConf=%x, Stat=%x"

Definition

The port state is an invalid one to process a Stop Play request. This error occurs because there is a loss of synchronization between the Voice User Interface (VUI) and the Call Processing (CP) modules.

Resolution

Escalate the problem to Cisco Technical Support for further analysis. Hang up the call to clear the state of the port, so that the new call starts clean.

0x900bb (EX_RQ_Q_ERROR) "(PortOpResp)Request Q is invalid, port=%x, fConf=%x, RqPtr=%x, Req=%x"

Definition

The requests queued in the request queue are not the ones expected. There is an inconsistency in the requests, so Cisco MeetingPlace cannot respond to the expected requests. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis. Hang up the call to clear the state of the port, so that the new call starts clean.

0x900bc (EX_SET_CONF_MODE_TVAPI_FAIL) "(SetConfMode)TVAPI SetConfMode fail,port=%x,fConf=%x,err=%x"

Definition

The command sent to the TVAPI to set the conference mode failed. In order to find the cause of the problem, check the value of the error returned by the TVAPI.

Resolution

Check for related errors and for a fix description of the error returned by the TVAPI.

0x900bd (EX_RT_ERROR_PLAYING) "(EvtAReadComplete)Error while playing,port=%x,fConf=%x,err=%x,buf=%x"

Definition

While an asynchronous read operation completed, it was detected that an error had already occurred. The play operation is aborted. Check the parameter err in the error log for the reason play was aborted.

Resolution

Check the fix description for the parameter err, and follow that suggestion.

0x900be (EX_RT_ERROR_RECORDING) "(EvtAWriteComp)Error while recording,port=%x,fConf=%x,err=%x,buf=%x"

Definition

While an asynchronous write operation completed, it was detected that an error had already occurred. The recording operation is aborted. Check the parameter err in the error log for the reason recording was aborted.

Resolution

Check the fix description for the parameter err, and follow that suggestion.

0x900bf (EX_PREV_OP_NOT_PAUSED) "()Prev op was not paused, ptr=%x, port=%x, status=%x"

Definition

Cisco MeetingPlace received a client request to play a file list, but a previous operation that was not paused was on the stack. Cisco MeetingPlace cannot perform an operation on a port if the previous operation is not paused. This error occurs when there are too many incomplete requests and the client sends another operation request before the previous one is completed.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900c0 (EX_STOP_PLAY_LIST) "(StopPlaylist)State is not playing list, port=%x,fConf=%x,status=%x"

Definition

The last request Cisco MeetingPlace operated on before it received the Stop Play List request was not a play list request. Because of this, MeetingPlace cannot stop anything but a play list. This error occurs because the Call Processing (CP) and Voice User Interface (VUI) modules are out of synch.

Resolution

Hang up on the port to synchronize all the modules. Escalate the problem to Cisco Technical Support for further analysis.

0x900c1 (EX_ABORT_PLAY_LIST_TVAPI_FAIL) "(StopPlayList)TVAPI fail, port=%x, fConf=%x, err=%x"

Definition

The command to the TVAPI to stop play of a list of files failed. Look at the parameter err in the event log to find the reason the TVAPI failed.

Resolution

Follow the fix recommendation for the TVAPI error.

0x900c2 (EX_SEEK_PAUSED_FILE_FAIL) "(PlayListSM)FS Seek fail,port=%x,fConf=%x,err=%x, fh=%x"

Definition

A seek operation on the file that has just been paused has failed. Look at the parameter err in the event log to find the reason the file system seek failed.

Resolution

Follow the fix recommendation for the file system error.

0x900c3 (NewCall)Place Call table full

Definition

This alarm indicates an issue with outdialing. In order to be more specific, the outgoing call could not be placed. This can be caused by one of these two issues:

  1. Improper call disconnections from the private branch exchange (PBX) or telephone company (Telco).

  2. Too many outgoing calls dialed at the same time.

If the alarm is infrequent, it can be ignored. See the Workaround and Resolution if the alarm is frequent.

Workaround

If the alarm is frequent, it is very likely that the outgoing call queue is jammed. Entries in the outgoing call queue are not freed once the calls are placed. In this case, the outdialing feature ceases to function until the Cisco MeetingPlace server is restarted.

Resolution

This issue has been addressed in MeetingPlace server PCI release 4.3.1a (and later) and MeetingPlace server M3 release 5.0.2q (and later).

0x900c4 (EX_PC_GET_RQ_FAIL) "(NewOutgoingCall)Failed to get request, evt=%x, err=%x"

Definition

The system failed to get the request sent by the client. This error is caused by an operating system problem.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900c5 (EX_PC_GET_RQ_TEXT_FAIL) "(NewOutgoingCall)Failed to get request text, evt=%x, err=%x"

Definition

The system failed to get the request text sent by the client. This error is caused by an operating system problem.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900c6 (EX_TG_INVALID_PORT_INDEX) "(GetPort)Reached end of port table, PortGrp=%x, Index=%x, MaxIndex=%x"

Definition

The system failed to get the next port in the port group because the index given to begin to scan for the next port was too large. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900c7 (EX_TG_INVALID_PORT_GRP_NUM) "(GetNxtPort)PortGrpNum invalid,PortGrp=%x,Index=%x,MaxIndex=%x"

Definition

The system failed to get the next port in the port group because the index given to begin to scan for the next port was too large. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900c8 (EX_PC_XLAT_TABLE_EXAUSTED) "(NewOutCall)Xlat Table exhausted,err=%x,Index=%x,PortGrp=%x"

Definition

There are no more entries in the translation table that match the phone number specified. It can be because there is no match. This alarm may not indicate a problem if all of the ports are busy. If the ports are idle and an attempt to place a call still fails, there is a problem.

Resolution

Check the translation table and verify that the configured translations are correct.

0x900c9 (EX_PC_NUM_BLOCKED) "(NewOutCall)Dialed number is blocked,Index=%x,PortGrp=%x"

Definition

The number that was requested to dial is a blocked number. The translation table translates the number into a null string, which cannot be dialed.

Resolution

This issue is not an error; it results from the way the digit translation has been configured. If the number should not be blocked, the digit translation table must be changed.

0x900ca (EX_TIMEOUT_INVALID_STATE) "(TimeoutResp)Invalid state,port=%x,fConf=%x,Stat=%x"

Definition

The port is in an invalid state when the timeout expired. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900cb (EX_PC_PORT_NOT_IDLE) "(PlaceCall)Port not Idle, port=%x, fConf=%x, State=%x"

Definition

The mid-lLevel thread received a request to place an outgoing call on a port that is not idle. Outgoing calls are only allowed on idle ports. This issue occurs when the port status changes by the time the request is received by the mid-level thread and Place Call checks the port.

Resolution

This alarm is not an error. The Place Call thread attempts to place the outgoing call on another port, so there is no error or problem.

0x900cc (EX_PCSM_INVALID_STATE) "(OutDialSM)Invalid state for state machine, port=%x,fConf=%x,state=%x"

Definition

The state is invalid for the Place Call state machine. This error occurs because of an inconsistency in the state machine or an internal software inconsistency.

Resolution

Escalate to Cisco Technical Support so that the problem can be analyzed.

0x900cd (EX_FLASH_TVAPI_FAIL) "(OutDialSM)TVAPI failed to Flash, port=%x,fConf=%x,err=%x,state=%x"

Definition

The TVAPI failed to send a flash on the requested port. Look at the err parameter for the reason the flash failed.

Resolution

Follow the fix suggestion given by the err parameter.

0x900ce (EX_BAD_DIGIT) "(OutDialSM)Unexpected digit to dial, port=%x, fConf=%x, digit=%x"

Definition

There is an unexpected digit in the string of digits to be dialed. Corruptions of the data is assumed and the place call operation is aborted. This error occurs because the translated string to be dialed is corrupted or the digit translation tables for outdialing are incorrect, and include incorrect characters.

Resolution

Check the translation tables for outgoing calls. If no apparent cause is found and the problem persists, escalate the problem to Cisco Technical Support.

0x900cf (EX_CALL_TVAPI_FAIL) "(OutDialSM)Failed to tvapi Call, port=%x,fConf=%x, err=%x"

Definition

A call to the TVAPI to call on a port (go offhook and dial a string of digits) failed. Check the error description for the err parameter to determine the cause of the failure.

Resolution

Follow the fix description included under the err parameter.

0x900d0 (EX_PLAY_TVAPI_FAIL) "(OutDialSM)Failed Play tvapi call, port=%x,fConf=%x, err=%x"

Definition

A call to the TVAPI to play on a port (dial a string of digits) failed. Check the error description for the err parameter to determine the cause of the failure.

Resolution

Follow the fix description included under the err parameter.

0x900d1 (EX_OD_INVALID_EVT) "(OutDialSM)Evt rcvd not one expected, port=%x,fConf=%x, expt=%x, rcv=%x"

Definition

The event received from the TVAPI was not the event the Out Dial state machine expected. The TVAPI either sent the incorrect event or the Out Dial state machine is confused and expected the wrong event.

Resolution

This issue does not cause a problem, because the Place Call thread attempts to place the call on a different port. There can be a very short delay before the call is placed. If the call was a transfer, the caller can be disconnected. Escalate the problem to Cisco Technical Support for further analysis.

0x900d2 (EX_TONE_EVT_NO_DIGIT) "(PCallSM)Tone Evt rcvd with 0 digits,port=%x,Conf=%x,num=%x,digit=%x"

Definition

Received a tone event from the TVAPI, but there were no tones in the event. Tone events must have at least one tone to be valid. This problem occurs when the TVAPI sends an invalid event or when the TVAPI sends a valid event, but the data in the Call Processing (CP) module is corrupted.

Resolution

Hang up the call and try again. This should clear the problem. Escalate the problem to Cisco Technical Support for further analysis.

0x900d3 (EX_EVT_NOT_TIMEOUT) "(PCallSM)Evt rcvd is not timeout,port=%x,Conf=%x,evt=%x"

Definition

While a port placed a call, the port waited for a timeout event (which causes a delay while dialing), but the event received was not the timeout. This error is caused by an internal software inconsistency. The TVAPI sent an unexpected event while a call was placed.

Resolution

The system hangs up on the port and tries again on another port. There is only a brief delay before the call is placed. Escalate the problem to Cisco Technical Support for further analysis.

0x900d4 (EX_UNEXPECTED_EVT) "(PCallSM)Unexpected Evt rcvd, port=%x, Conf=%x, evt=%x"

Definition

While a port placed a call, the port waited for a set of events, but the event received does not belong to the set. This error is caused by an internal software inconsistency. The TVAPI sent an unexpected event while a call was placed.

Resolution

The system hangs up on the port and tries again on another port. There is only a brief delay before the call is placed. Escalate the problem to Cisco Technical Support for further analysis.

0x900d5 (EX_INVALID_PARAMS) "(PCallSM)Invalid parameters for call, port=%x, Conf=%x, evt=%x"

Definition

The routine OutDial state machine has been called with incorrect parameters. It cannot receive an event and a timeout at the same time. This error is caused by an internal software inconsistency.

Resolution

The system hangs up on the port and tries again on another port. There is only a brief delay before a call is placed. Escalate to Cisco Technical Support for further analysis.

0x900d6 (EX_UNEXPECTED_TONE) "(PCallSM)Rcvd unexpected tone,port=%x,Conf=%x,tonercv=%x,expect=%x"

Definition

Received a Tone event from the TVAPI, as expected. But the tone in the event was not the expected one. This error is caused by an internal software inconsistency. Either he TVAPI sent the incorrect tone or the Call Processing (CP) module corrupted its data.

Resolution

The system hangs up on the port and tries again on another port. There is only a brief delay before a call is placed. Escalate the problem to Cisco Technical Support for further analysis.

0x900d7 (EX_PC_GLARE) "()Rcvd a glare event, port=%x, Conf=%x"

Definition

Received a glare event from the TVAPI. This is not an error, just a notification of an incoming call at the same time an outgoing call was placed.

Resolution

There is no problem. The outgoing call is cancelled and the incoming call is allowed to proceed. The outgoing call is placed on another port.

0x900d8 (EX_TRANSFER_INVALID_STATE) "(XferState)Invalid state,port=%x,Conf=%x,RqPtr=%x,MainSt=%x"

Definition

A command to transfer the port cannot be accepted in the current state of the port. The port must be connected and no other requests queued. This error occurs when there is loss of synchronization between the client Voice User Interface (VUI) and the Call Processing (CP) module. The VUI believes that the state of the port is different than the state of the port in the CP module.

Resolution

Hang up in the port to resynchronize the VUI and the CP module. Escalate the error log to Cisco Technical Support for further analysis.

0x900d9 (EX_PHONE_NUM_LEN_INVALID) "(XferPort)PhoneNum len invalid,port=%x,Conf=%x,Len=%x, max=%x"

Definition

The phone number to which this port is transferred is of invalid length (either zero or too long). This error occurs because the Voice User Interface (VUI) sent an invalid number, or the data in the messages sent by the VUI and received by the Call Processing (CP) module were corrupted.

Resolution

Hang up on the port and try again. This problem is probably transient and should disappear. Escalate the error log to Cisco Technical Support for further analysis.

0x900da (EX_NO_PORTGRP_FOR_PORT) "(GetPortGrpNum)Port not in a PortGrp,port=%x,Conf=%x,Len=%x, max=%x"

Definition

The port does not belong to a port group, probably because it is an invalid port number (a port that has not been configured).

Resolution

Verify that the port is configured. Check all of the port parameters and the Class of Service (CoS).

0x900db (EX_NO_XLAT_FOR_PORTGRP) "(XlatPhNumForPortGrp)No transl for PortGrp,port=%x,Conf=%x,Len=%x, max=%x"

Definition

Unable to perform digit translation for the phone number and the specified port group number. This problem occurs when the port group number is invalid or the digit translation table does not contain such an entry.

Resolution

Verify that the port group number is valid. Verify that the phone number to be translated is a valid one. Check the consistency of the digit translation tables.

0x900dc (EX_GET_PORTGRP_FAIL) "(TransferPort)Failed to get PortGrpNum,port=%x,Len=%x, max=%x"

Definition

Unable to perform digit translation for the phone number and the specified port group number. This occurs when the port group number is invalid or the digit translation table does not contain such an entry.

Resolution

Verify that the port group number is valid. Verify that the phone number to be translated is valid. Check the consistency of the digit translation tables.

0x900dd (EX_PORT_NO_ASSIST) "(TransferPort)No assistance in port, port=%x"

Definition

This port is configured to not provide assistance. This is not an error, only a configuration option.

Resolution

This is not an error condition, only a configuration option. Change the configuration if assistance for this port is desired.

0x900de (EX_PORT_NO_FLASH) "(TransferPort)No flash in port, port=%x"

Definition

This port is configured to not provide Flash capabilities. This is not an error, only a configuration option.

Resolution

This is not an error condition, only a configuration option. Change the hardware and software configuration if Flash capabilities are desired for this port.

0x900df (EX_XLATLOAD) "(CPdbInit)No flash in port, port=%x"

Definition

An attempt to add a pattern to the digit translation table failed. The table may be full or some of the parameters may be invalid.

Resolution

Make sure that the digit translation table is not full. Escalate the problem to Cisco Technical Support for further analysis.

0x900e0 (EX_NULLID_IN_PLAY_LIST) "(PlayListSM)Null ID in play file list, port=%x, fConf=%x"

Definition

A null file ID was included in the list of file IDs requested to be played. A null file ID is not a valid ID and therefore cannot be played.

Resolution

Make sure that the database is initialized with the prompts, so that there is no null file ID. Escalate the problem to Cisco Technical Support for further analysis.

0x900e1 (EX_DBCFOPEN) "Unable to initialize the config database, ex=%#x"

Definition

This is routine: A request to initialize the database failed. This is caused by a database problem. The database has not been created.

Resolution

Escalate the problem to Cisco Technical Support.

0x900e2 (EX_FAIL_TV_DEACTIVATE) "(Disconnect)TVAPI Failed to deactivate a port=%x,fConf=%x,err=%x"

Definition

A command to the TVAPI to deactivate a port failed. The port does not exist, is not configured, or is in some other way not available to be deactivated.

Resolution

Look at the parameter err to find the reason the TVAPI failed to deactivate the port.

0x900e3 ()Index out of bounds=ddee

Definition

This alarm is caused by a bad outdial. It does not indicate a serious problem.

Resolution

This alarm does not indicate a serious problem and no resolution is needed.

0x900e4 (PlaceCallResp)Entry is free=

Definition

When the system outdials or makes a Flash transfer and the remote destination fails to answer or the call cannot be completed, the Cisco MeetingPlace system continues the attempt a certain number of times. How many times the system retries is set in Cisco MeetingTime. At the end of the retry counter, this alarm is generated.

Resolution

The cause of this alarm can be an incorrect termination of a system outdial, such as a port timeout. Reasons for a port timeout include an incorrectly-dialed number or failure to respond by a remote user. Check for reasons the outdial was not successful.

0x900e5 (TransferCall)Failed to Xlat phonenum, err=30

Definition

The server is unable to use the translation table that is assigned. For example, the translation table (xtable.current-0) says to translate the number dialed to port group 0. The problem is that port group 0 is set Outdial=N, and port group 1 is set Outdial=Y.

Resolution

Set the translation table from Group=0 to Group=ANYGROUP, or to the port group number that does allow outdials. A restart is not needed for the changes in the translation tables to take effect, but you do need to be at the csc prompt.

0x900e6 (EX_RT_INVALID_OP) "(EvtTVBufDone)Op requested is invalid, port=%x, op=%x"

Definition

The operation requested from the mid-level thread to the real-time thread is not one supported by the real-time thread. This occurs when the mid-level thread has overwritten some of its variables.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x900e7 (EX_TVAPI_CONTROL_FAIL) "(SVNotif)TVAPI speed-vol ctrl fail,Port=%x,fConf,err=%x,upd=%x"

Definition

A command to the TVAPI to control the speed and the volume on a port failed. Check the description of the parameter err for the cause of the failure.

Resolution

Follow the fix description for parameter err.

0x900e8 (EX_NO_RQ_IN_Q) "(EvtDoneTone)No request is queued, Port=%x, fConf=%x, RqPtr=%x"

Definition

There are no requests queued for this port, and a response to a request was received. This can mean that there is an internal inconsistency in the software. The cause of the problem can be that the cpserver data structures for the port are corrupted or that the TVAPI sent an event for a port that is not connected.

Resolution

Escalate this problem to Cisco Technical Support for further analysis. Disconnect the port in order to clear the problem.

0x900e9 (EX_TONE_INVALID_STATE) "(EvtDoneTone)Invalid state for DoneTone, port=%x, fConf=%x, State=%x"

Definition

The port is in an invalid state when the Done Tone event is received. This occurs when there is an internal software inconsistency or when the TVAPI sends the wrong event or the event to the wrong port.

Resolution

Hang up in the port to clear the problem. Escalate the error log to Cisco Technical Support for further analysis.

0x900ea (EX_INVALID_TONE_LIST) "(ConvertAtoTT)Invalid string to be converted"

Definition

The list to convert from ASCII to Touch tones accepted by the TVAPI has an invalid length, so it is not converted. The list remains unchanged. If the error occurs while an outgoing call is placed, check the digit translation tables for inconsistencies. Otherwise, there can be an internal software inconsistency.

Resolution

Check the digit translation tables. Escalate the problem to Cisco Technical Support for further analysis.

0x900eb (EX_RESP_OUTSTANDING) "(StartPlayFile)Response still outstanding, Port=%x, fConf=%x"

Definition

A request to begin to play a file is received while the response from the previous request to the real-time thread is still expected. A new request to play a file can only be processed once the real-time thread completely processes the previous play or record request. This problem occurs due to an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900ec File should had been closed, Port=%x, fConf=%x, fh=%x

Definition

While the system was cleaning up after a list of files was played, a file was still open (the file handles something other than zero). This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x900ed (EX_UNEXPECTED_EVENT_RCVD) "(PlayListSM)Rcvd unexpected event, Port=%x, fConf=%x, fh=%x"

Definition

While a list of files plays, Cisco MeetingPlace receives an unexpected event completion, rather than the expected play cached list event completion.. This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x900ee (EX_TVAPI_OPEN_FAIL) "(CPInit)Failed to init (open) the TVAPI, err=%x"

Definition

Failed to open the TVAPI. Check the err parameter to find the reason for the failure.

Resolution

Check the description for the err parameter.

0x900ef (EX_TVAPI_CLOSE_FAIL) "(CPInit)Failed to close the TVAPI, err=%x"

Definition

Failed to close the TVAPI. Check the err parameter to find the reason for the failure.

Resolution

Check the description for the err parameter.

0x900f0 (EX_NEW_CALL_IN_Q) "(EvtHangUp)Already queued a new incoming call, port=%x"

Definition

Failed to close the TVAPI. Check the err parameter to find the reason for the failure.

Resolution

Check the description for the err parameter.

0x900f1 (EX_BUF_OP_FAILED) "(EvtTVBufDone)Buf operation failed,port=%x,req=%x"

Definition

An operation requested on a buffer failed. The TVAPI (Port Resource Card [PRC]/Master Switch Controller [MSC]) is unable to process the request. If the PRC port hangs up and the cpserver has not yet processed the hangup, it continues to request play/recording on a buffer.

Resolution

This issue is not necessarily a problem, but rather a timing issue. If the port is hung, hang up on the port to clear the state. Escalate the problem to Cisco Technical Support for further analysis.

0x900f2 (EX_PLAY_LIST_OP_FAILED) "(PlayListSM)Failed to play a cached list, port=%x, req=%x"

Definition

An operation requested to play a list of cached prompts failed. The TVAPI (Port Resource Card [PRC]/Master Switch Controller [MSC]) was unable to process the request. If the PRC port has hung up and the cpserver has not yet processed the hangup, it continues to request play/recording on a buffer.

Resolution

If the port is hung, hang up on the port to clear the state. Escalate the problem to Cisco Technical Support for further analysis.

0x900f3 (OutDialSM)Failed tvapi operation, port=a, fConf=0, wait=a, op=5

Definition

A TVAPI operation request failed. The TVAPI (Port Resource Card [PRC]/Master Switch Controller [MSC]) was unable to process the request. The PRC/MSC was in a state in which the request was not expected.

Resolution

Hang up on the port to clear the state if the port is hung. Escalate to Cisco Technical Support for further analysis. For Cisco MeetingPlace version 4.1.3 systems, a fix is implemented in the 4.1.3k Voice User Interface (VUI) module. For Cisco MeetingPlace version 4.2.0 systems, a fix is implemented in the 4.2.1a VUI module.

0x900f4 (EX_BUF_WAS_IDLE) "(RealTimeThread)Event received an idle buffer, port=%x, conf=%x, buf=%x"

Definition

An event is received for a buffer that is marked as idle. There is an inconsistency between the state of the buffer and an asynchronous operation that was performed on the buffer. This issue occurs because of an internal software inconsistency.

Resolution

This issue is not a problem. The port should recover in the next play or record operation, or once the port is hung. Escalate the problem to Cisco Technical Support so that the problem can be analyzed.

0x900f5 (EX_NOT_IMPLEMENTED) "()Feature, Cmd or Event not implemented, port=%x, conf=%x, buf=%x"

Definition

This feature is not implemented. It should never be called or executed. This issue is due to an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support so that the problem can be analyzed.

0x900f6 (EX_INVALID_OPTION) "()Option in command line invalid, arg count=%x"

Definition

One of the options in the command line when the cpserver command is issued is invalid. It is ignored by cpserver. This problem occurs due to an incorrectly spelled option or an unsupported feature.

Resolution

Issue the cpserver command again with the correct command line argument.

0x900f7 (EX_TVAPI_ACTIVATE_FAIL) "(TVACTIVPort)Failed to activate port,port=%x,fConf=%x,Err=%x"

Definition

The request to the TVAPI to activate a port failed. Check the err parameter to determine the reason why the TVAPI failed to activate the port.

Resolution

Follow the fix description for the err parameter.

0x900f8 (EX_WAITFOREVENT_TVAPI_FAIL) "(OutDialSM)Fail WaitForEvt tvapi, port=%x,fConf=%x,err=%x"

Definition

A call to the TVAPI to WaitForEvent on a port (dial a string of digits) failed. Check the parameter err to find the reason the call failed.

Resolution

Follow the fix description included under the err parameter.

0x900f9 (EX_CP_NOT_SUPPORTED) "()Request is not supported by the cpserver, %x, %x,%x, %x"

Definition

The request for a feature or action in the cpserver is not yet supported.

Resolution

This is not an error, so there is no resolution. The next release may support the feature.

0x900fa (EX_SEIZE_TVAPI_FAIL) "(OutDialSM)Fail Seize tvapi, port=%x,fConf=%x,err=%x"

Definition

A call to the TVAPI to seize on a port failed. Check the error description for the parameter err to determine the cause of the failure.

Resolution

Follow the fix description included under the err parameter.

0x900fb (EX_TIMER_GETREQUEST_FAIL) "()Failed timer GetRequest, port=%x,fConf=%x,err=%x"

Definition

A call to the timer thread to get a timer request that had expired failed. Check the error description for the parameter err to determine the cause of the failure.

Resolution

Follow the fix description included under the err parameter.

0x900fc Failed timer AddRequest, port= ,fConf= ,err=

Definition

This alarm means that the server performed an outdial to a phone number, but encountered a problem along the way.

Resolution

This problem is corrected in the Cisco MeetingPlace version 4.3.0u cpserver module.

0x900fd (EX_INVALID_VIRTUAL_FUNC) "()Virtual function called, port=%x,fConf=%x"

Definition

A virtual function for the TVAPI was called, even though virtual functions should never be called. This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x900fe (EX_THREAD_ID) "()The thread ID expected was different, port=%x,fConf=%x"

Definition

This message is expected to be processed by a different thread ID. This problem is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x900ff (EX_OUTDIAL_TOO_MANY_ERRORS) "(PCResp)Too many errors while outdialing,cnt=%x"

Definition

The number of ports that failed to outdial the requested call is over the limit. Reject the place call request and inform the client that the request failed.

Resolution

This problem is probably due to an incorrect port configuration. Verify that all ports are correctly configured and that all of the parameters are valid.

0x90100 (EX_PORT_STAT_BAD_NUM_PORTS) "(EvtPStat)Invalid Num ports=%x, max=%x"

Definition

The Port Status event received from the TVAPI contains an invalid number of ports. This problem occurs because the message was overwritten or the TVAPI incorrectly formatted the message.

Resolution

This problem is caused by an internal software inconsistency. Escalate the problem to Cisco Technical Support for further analysis.

0x90101 (EX_PORT_STAT_INVALID_STATUS) "(EvtPStat)Invalid port status, Stat port event=%x"

Definition

The Port Status event received from the TVAPI contains an invalid status. This problem occurs because the message was overwritten or the TVAPI incorrectly formatted the message.

Resolution

This problem is caused by an internal software inconsistency. Escalate the problem to Cisco Technical Support for further analysis.

0x90102 (EX_EVT_PORT_STAT_FAIL) "(EvtPStat)Failed to set port status, port=%x, err=%x"

Definition

Failed to set the status of a port. An event received from the TVAPI is the initiator of this action. Check the value of the parameter err to determine the cause for the error.

Resolution

Check the fix description for the parameter err.

0x90103 (EX_EVT_PORT_BAD_PORT_NUM) "(EvtPStat)PortNum invalid=%x"

Definition

The port number obtained from the Port Status Event is out of range. This error is caused by an internal software inconsistency. The TVAPI sent an incorrect port number, or the messages got corrupted by the cpserver.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90104 (EX_NO_SPEECH_INVALID_STATE) "(EvtNoSpeech)Invalid State for Port=%x, state=%x"

Definition

A no-speech event is received for a port that is not in the connected state, which does not make sense. This error occurs when the Port Resource Card (PRC) firmware and the cpserver are out of synch.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90105 (EX_PORT_OUT_OF_SERVICE) "(EvtPortStat)Port is out of service,Port=%x, state=%x"

Definition

Received an event from the TVAPI that the port is out of service. This error is caused by Telephony problems on the port or the Port Resource Card (PRC) firmware.

Resolution

Check the ports that are reported out of service.

0x90106 (EX_TV_EVT_FW_ERROR) "(TVAPIHndlr)TVAPI FW Error, CardType=%x,Card=%x,Port=%x,type=%x"

Definition

An event from the TVAPI is received that indicates there is a firmware error on a port.

Resolution

This alarm can be ignored as long as it happens infrequently.

0x90107 (EX_TV_EVT_HW_ERROR) "(TVAPIHndlr)TVAPI HW Error,CardType=%x,Card=%x,Port=%x,type=%x"

Definition

An event from the TVAPI is received that indicates there is a hardware error on a port.

Resolution

This alarm can be ignored as long as it happens infrequently.

0x90108 (EX_TV_EVT_PRC_READY) "(TVAPIHndlr)TVAPI PRC READY, Code=%x"

Definition

An event is received from the TVAPI that indicates that the Port Resource Card (PRC) is up.

Resolution

This alarm is an informational message, not an error.

0x90109 (EX_BUF_PATTERN_INVALID) "(EvtAReadComplete)Buffer not written,Port=%x,fConf=%x,buf=%x"

Definition

The Port Resource Card (PRC)/Master Switch Controller (MSC) buffer was not overwritten by the play request to the file system. It means that an event arrived that states that the asynchronous I/O request to read from disk to Port Resource Card (PRC)/MSC memory was completed, but the special pattern was not overwritten. This problem occurs because the asynchronous I/O did not complete successfully.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9010a (EX_RESP_TO_REQ_FAIL) "()Failed to send response to req,err=%x,par1=%x,par2=%x"

Definition

Failed to send a response to a request. Most of the client requests to the the cpserver are responded to with this alarm. This error is severe and can hang ports. It is caused by an inconsistency in the structure that holds the requests.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9010b (EX_CACHED_RECEIVED_EVENT) "(CachedPrompts)Evtpoll received an event, evt=%x, data=%x"

Definition

The thread received an event that it will begin to process.

Resolution

This alarm is an informational message only, not an error.

0x9010c (EX_CACHED_GET_RQ_FAIL) "(EvtCachedClientReq)Failed to get request, evt=%x, err=%x"

Definition

Failed to get the request sent by the client. This error is caused by an operating system problem.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9010d (EX_CACHED_GET_RQ_TEXT_FAIL) "(EvtCachClntRq)Fail get request text,evt=%x,err=%x"

Definition

Failed to get the request text sent by the client. This error is caused by an operating system problem.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9010e (EX_CACHE_EVT_CLIENT_REQ_ERROR) "(EvtCachClntRq)Err proc request rq=%x,err=%x,EvtD=%x"

Definition

While a request from a client is processed, an error is detected by the cached prmt thread. Check the event log for related entries that can help you to identify the source of the problem.

Resolution

Check the description of related entries for a suggestion on an action.

0x9010f (EX_FAIL_CACHE_ID) "(EvtCachClntRq)Failed to cache ID,err=%x,EvtData=%x"

Definition

A request to cache a file ID fails. Check the cause for the err parameter to determine the reason for the failure.

Resolution

Check the description of the parameter err for a suggestion on an action to take.

0x90110 (EX_FAIL_UNCACHE_ID) "(EvtCachClntRq)Failed to uncache ID,err=%x,EvtData=%x"

Definition

A request to uncache a file ID fails. Check the cause for the err parameter to determine the reason for the failure.

Resolution

Check the description of the parameter err for a suggestion on an action to take.

0x90111 (EX_FAIL_UPDATE_FILE_CACHE) "(EvtCachClntRq)Failed to update file cache,err=%x,EvtData=%x"

Definition

A request to update the file cache fails. Check the cause for the err parameter to determine the reason for the failure.

Resolution

Check the description of the parameter err for a suggestion on an action to take.

0x90112 (EX_CACHED_ID_ALREADY_THERE) "(CacheFileID)ID already cached,rec=%x,dir=%x,disk=%x,loc=%x"

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x90113 (EX_PRC_CACHE_FULL) "(CacheFileID)The PRC cache is full,rec=%x,dir=%x,disk=%x"

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x90114 (EX_MSC_CACHE_FULL) "(CacheFileID)The MSC cache is full,rec=%x,dir=%x,disk=%x"

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x90115 (EX_CACHE_TABLE_FULL) "(CacheFileID)The cache table or lookup is full,rec=%x,dir=%x,disk=%x"

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x90116 (EX_UNSUPPORTED_CACHE_LOC) "(CacheFileID)Cache location not supported,loc=%x"

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x90117 (EX_FAIL_LOAD_CACHED_PROMPTS) "(EvtCachClntRq)Failed to load cached prompts,err=%x,EvtData=%x"

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x90118 (EX_FS_INVALID_REQ) "(FSEvtClientReq)Invalid request for File System=%x"

Definition

The file system cpserver thread receives a request that it cannot fulfill. The file system thread can only fulfill some of the cpserver requests. This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90119 (EX_LOW_PRIO_INVALID_REQ) "(LowPrioClientRq)Invalid request for Low Priority Thread=%x"

Definition

The Low Priority thread, which handles all cpserver requests that are not real-time sensitive, receives a request that is not yet implemented. This problem occurs because of an internal software inconsistency or because the client has requested a service that is not yet implemented.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9011a (EX_ALREADY_PLAYING_CACHED_LIST) "(PlayFileSM)Already playing a cached List, port=%x,fConf=%x"

Definition

This port or conference already plays a list of cached prompts, so it should not attempt to play a second list. Even though the PlayFileListSM machine supports several queue levels, the Cisco MeetingPlace server does not play two lists of cached prompts one after the other, because a complete list can handle all the file IDs in a Voice User Interface (VUI) play list request. This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9011b (EX_SERVICE_NOT_AVAIL) "()This service is not currently available=%x"

Definition

The service or request requested by the client is not currently available. It could be that it is not yet implemented or that the resources required for that service are not available at the time. Cisco MeetingPlace may try to repeat the request later, or after the system is restarted.

Resolution

Restart the system. Escalate the problem to Cisco Technical Support for further analysis.

0x9011c (EX_FILE_ID_NOT_CACHED) "(GetFileIDCachedLocation)This file ID is not cached anywhere"

Definition

A request to find out if a voice file ID is cached was negative. The ID is either not cached or caching is disabled.

Resolution

This is only an informational message, not an error. Nothing needs to be fixed.

0x9011d (EX_DONT_CACHE_NULL_ID) "(CacheToHW)Null file IDs cannot be cached"

Definition

A request to cache a null file ID was received. Null file IDs are not cached, because they are invalid IDs. This issue is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9011e (EX_INVALID_CACHE_KIND) "()Cannot hash that type of cache kind=%x"

Definition

Not all voice file types are hashed. A request to hash an invalid type is received. This issue is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x9011f (EX_DYN_CACHING_NOT_ALLOWED) "(CacheID)Cannot do dynamic caching"

Definition

The dynamic caching requested for the list of voice file IDs is not currently possible. Static caching must be completed before dynamic caching can start. This issue is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90120 (EX_BUFF_DONE_OFFSET_INVALID) "(EvtTVBufDone)BufDone offset invalid=%x, max=%x"

Definition

A buffer was interrupted while it was played, and the offset into the buffer returned by the TVAPI is not within the length of the buffer. The offset must be less than the length of the buffer (minus the block heading). This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90121 (EX_CACHE_INVALID_REQ) "(EvtCachedClientReq)Invalid request for Cache Prompts Thread=%x"

Definition

The Cache Prompts thread received a request that is not yet implemented. This issue is either caused by an internal software inconsistency or by a request from the client for a service that is not yet implemented.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90122 (EX_INVALID_TIMEOUT_TYPE) "(OutDialSM)Invalid timeout type,port=%x,fConf=%x,type=%x,sec=%x"

Definition

A timeout is received while a call is placed (outdialed), but it is of an unexpected type. This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90123 (EX_ML_REQ_NOT_IMPLEMENTED) "(EvtClientReq)Req not implemented=%x"

Definition

The request received by the Mid Level thread is not yet implemented. There may be incompatibility between the cpserver and the clients, or the request received may have been corrupted.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90124 (EX_MISSED_HANGUP_EVT) "(EvtIncomingCall)Hangup event not recieved, port=%x, fConf=%x"

Definition

A hangup event was not received between two incoming call events on the same port. This issue is caused either by a firmware error or by a loss of a hangup event by the cpserver.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90125 (EX_TIMER_DEL_REQUEST_FAIL) "()Failed timer DeleteRequest, port=%x,fConf=%x,err=%x"

Definition

A call to the Timer thread to delete a timer request failed. Check the error description for the parameter err to determine the cause of the failure.

Resolution

Follow the fix description included under the err parameter.

0x90126 (EX_PC_PLACE_NEXT_FAIL) "(PlaceCallNext)Fail to place next call, err=%x"

Definition

Failed to process a client request to place the next call. Check the parameter err to find the reason for the failure.

Resolution

Follow the suggestions for any related errors received along with this one.

0x90127 (EX_PC_NOT_DIALING) "(PlaceCallNext)Entry not dialing, port=%x"

Definition

The place call thread received a notification from the mid-level thread that an outdial request has successfully dialed and that a new one can start if still under the limit. However, the identifier of the request that completed is not valid because the state of the request was not dialing. There was an invalid pointer to the entry, caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90128 (EX_RNA_TIMEOUT) "(OutDialSM)RingNoAnswer timeout,port=%x,fConf=%x"

Definition

The far end did not answer in the allocated time (one minute).

Resolution

This is only an informational message, not an error.

0x90129 (EX_OUTDIAL_BUSY) "(OutDialSM)Busy tone while outdialing,port=%x,fConf=%x"

Definition

Received a busy tone from the far end while outdialing.

Resolution

This is only an informational message, not an error.

0x9012a (EX_SEIZE_TVAPI_NAK) "(OutDialSM)Seize tvapi nacked, port=%x,fConf=%x,err=%x"

Definition

The response to a seize command to the TVAPI is nacked. Check the error description for the parameter err to determine the cause of the failure.

Resolution

Follow the fix description included under the err parameter.

0x9012b (EX_WAIT_FOR_SILENCE_TIMEOUT) "(OutDialSM)Wait for silence timeout,port=%x,fConf=%x"

Definition

Cisco MeetingPlace did not get a silence tone in the allocated amount of time.

Resolution

This is only an informational message, not an error (unless it happens very often).

0x9012c (EX_WAIT_FOR_BONG_TIMEOUT) "(OutDialSM)Wait for bong timeout,port=%x,fConf=%x"

Definition

Cisco MeetingPlace did not get the tone in the allocated amount of time.

Resolution

This is only an informational message, not an error (unless it happens very often).

0x9012d (EX_WAIT_FOR_DIALTONE_TIMEOUT) "(OutDialSM)Wait for dialtone timeout,port=%x,fConf=%x"

Definition

Cisco MeetingPlace did not get a dialtone in the allocated amount of time.

Resolution

This is only an informational message, not an error (unless it happens very often).

0x9012e (EX_WAIT_FOR_TONE_TIMEOUT) "(OutDialSM)Wait for tone timeout,port=%x,fConf=%x"

Definition

Cisco MeetingPlace did not get a tone in the allocated amount of time.

Resolution

This is only an informational message, not an error (unless it happens very often).

0x9012f (EX_FS_SET_RECORDING_LIMITS) "(FSSetRecordingLimits)Fail to set Conf limit=%x"

Definition

The file system cpserver thread received a request to set the recording limits, but it failed to set them. The limits requested may have been invalid. For example, a request to set a conference recording limit greater than the total amount of recording space available.

Resolution

Check the total amount of recording space and the value of the limit. If there is still a problem, escalate the problem to Cisco Technical Support for further analysis.

0x90130 (EX_RAS_INVALID_REQ) "(RASClientRq)Invalid request for RAS Thread=%x"

Definition

The Remote Access Server (RAS) thread made a request that is not yet implemented. Either there is an internal software inconsistency or the client has requested a service that is not yet implemented.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90131 (EX_RAS_EVT_CLIENT_REQ_ERROR) "(RASClientReq)Error processing request req=%x,err=%x,EvtData=%x"

Definition

The Remote Access Server (RAS) thread detected an error while a client request was processed. Check the event log for related entries that can help you identify the problem.

Resolution

Check the description of related entries for a suggestion on an action to take.

0x90132 (EX_DEXIM_INVALID_REQ) "(DeximClientRq)Invalid request for Dexim main Thread=%x"

Definition

The Remote Access Server (RAS) thread made a request for a service that is not yet implemented. Either there is an internal software inconsistency or the client requested a service that is not yet implemented.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90133 (EX_DEXIM_EVT_CLIENT_REQ_ERROR) "(DeximClientReq)Error processing request req=%x,err=%x,EvtData=%x"

Definition

The Dexim Main thread detected an error while a client request was processed. Check the event log for related entries that can help you identify the problem.

Resolution

Check the description of related entries for a suggestion on an action.

0x90134 (EX_LOGEVENT) "(LogEvent)Test entry, user specified parameters"

Definition

This alarm indicates that this entry was created by the user for test purposes.

Resolution

No resolution is required.

0x90135 (EX_NO_PREV_OP) "(PlayFileListSM)No prev operation"

Definition

This state assumes that there is an outstanding operation for the port, but no operations are queued. This problem is caused by an internal software error.

Resolution

Escalate this problem to Cisco Technical Support.

0x90136 (EX_DX_INVALID_Q_INDEX) "()Index out of bounds index=%x,max=%x"

Definition

The index to the list of queued requests is out of bounds. This issue is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support.

0x90137 (EX_DX_Q_NOT_INITIALIZED) "()Request Q not initialized"

Definition

The list of queued requests is not initialized. Cannot perform any operation on this list. This problem is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support.

0x90138 (EX_DX_Q_NO_MORE_FREE) "(GetFreeEntry)No more free Q entries available"

Definition

A request to get another free entry cannot be fulfilled because there are no more free entries in the free list. Either there are too many current service requests, or there is an internal software inconsistency.

Resolution

Perform the request when the system is not under such heavy use and escalate to Cisco Technical Support.

0x90139 (EX_DX_Q_INTERNAL_INCONSISTENCY) "()Internal Inconsistency in the queued requests"

Definition

An internal inconsistency was detected in the DEXIM data structures. The cpserver export and import capability is disabled.

Resolution

Escalate the problem to Cisco Technical Support. In order to reenable export and import capabilities, you must restart the system.

0x9013a (EX_DX_FAIL_Q_REQUEST) "(QueueRequest)Fail to Q request, err=%x"

Definition

A request to queue a client request failed. It was not possible to queue the request to be processed later. Check the error parameter for the cause of the failure.

Resolution

Escalate the problem to Cisco Technical Support. This can be a temporary problem. Verify that the next request can either be immediately processed, or be queued to be processed later.

0x9013b (EX_DX_Q_EMPTY) "(UnQueueRequest)Queue is empty, no more requests waiting."

Definition

All the queued requests have been processed, and are either active or have been completed. This is not an error condition.

Resolution

This alarm is an informational message only, not an error.

0x9013c (EX_DX_THREAD_NOT_READY) "(DEXIMInit)Thread failed to be active on time."

Definition

A thread did not activate in the ten seconds allocated to it. This error is very unusual and could be an operating system (OS) or configuration problem. The consequences are that the export and import capabilities in the cpserver are disabled.

Resolution

Restart the system to attempt to correctly initialize the export and import capabilities in the cpserver.

0x9013d (EX_DX_INVALID_RQ_INDEX) "()Index out of bounds, index=%x,max=%x"

Definition

The index to the request table is out of bounds. This error is caused by an internal software inconsistency.

Resolution

Escalate this problem to Cisco Technical Support.

0x9013e (EX_DX_RQ_TABLE_NOT_INIT) "()Request Q not initialized"

Definition

The object has not been initialized. Cannot perform a search on an uninitialized object. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x9013f (EX_DX_RQ_NO_MORE_FREE) "(FindFreeEntry)No more table free entries available"

Definition

The table where all the requests are saved is full. Unable to find an empty entry. Either there are too many requests currently being serviced, or there is an internal software inconsistency.

Resolution

Perform the request when the system is not being as heavily used, and escalate to Cisco Technical Support.

0x90140 (EX_DX_GET_RQ_FAIL) "()Failed to get request, evt=%x, err=%x"

Definition

Failed to get the request received from the client. There is an internal inconsistency or an operating system problem.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90141 (EX_DX_GET_RQ_TEXT_FAIL) "()Fail get request text,evt=%x,err=%x"

Definition

Failed to get the request text received from the client. There is an internal inconsistency or an operating system problem.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90142 (EX_DX_NO_FREE_ENTRY) "()No free entry to process request."

Definition

Failed to get a free entry in the table where all the client requests are stored. The request is being rejected. Either there is an internal inconsistency, or the system is busy processing too many export and import requests.

Resolution

Wait until the system becomes less busy, and escalate the problem to Cisco Technical Support for further analysis.

0x90143 (EX_DX_INVALID_IMPORT_RQ) "()Import Rq data invalid."

Definition

The data received for an import request failed to be validated. The request is rejected. This occurs because the client data is invalid. There can be an internal data inconsistency. The client must send valid data.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90144 (EX_DX_INVALID_EXPORT_RQ) "()Export Rq data invalid."

Definition

The data received for an export request failed to be validated. The request is rejected. This occurs because the client data is invalid. There can be an internal data inconsistency. The client must send valid data.

Resolution

Escalate this problem to Cisco Technical Support for further analysis.

0x90145 (EX_DX_INVALID_RQ) "()Unexpected Rq received, rq=%x."

Definition

The request received was an unexpected one. The request is rejected. Either the client request is not accepted, or there is an internal data inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90146 (EX_DX_RQ_IN_Q_NOT_FOUND) "()Rq not found in the list of queued rq,rq=%x."

Definition

Failed to find a queued request in the list of queued requests. There is an internal data inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90147 (EX_DX_FAIL_Q_NEW_RQ) "()Failed to queue new Rq,rq=%x, err=%x."

Definition

Failed to queue a new request. Check the err parameter for the cause of the failure.

Resolution

Follow the recommendations for the err parameter and escalate the problem to Cisco Technical Support for further analysis.

0x90148 (EX_DX_RQ_INDEX_INVALID) "()Index out of bounds idx=%x, max=%x."

Definition

The index into the request table is out of bounds. Cannot access the requested entry. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90149 (EX_DX_RQ_INVALID_HANDLE) "()Invalid Handle, hd=%x."

Definition

The handle used to access the request table is invalid. The handle for that entry is different than the one in the entry itself. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9014a (EX_DX_EXPORT_NULLID) "()Cannot export a Null FileID"

Definition

Cannot export a null file ID from the Linear File System (LFS). The client data is invalid. It does not point to a valid file.

Resolution

The client must specify a valid file from the LFS to be exported. Escalate the problem to Cisco Technical Support for further analysis.

0x9014b (EX_DX_INVALID_DATA_TYPE) "()Type of data requested is invalid, type=%x, fExport=%x"

Definition

Cannot export nor import the type of data requested. The client request is invalid.

Resolution

The client must specify a valid data type. Escalate the problem to Cisco Technical Support for further analysis.

0x9014c (EX_DX_INVALID_DEVICE_TYPE) "()Type of device requested is invalid, type=%x"

Definition

Cannot export nor import to the device type specified. The client request is invalid.

Resolution

The client must specify a valid data type. Escalate the problem to Cisco Technical Support for further analysis.

0x9014d (EX_DX_FILE_SIZE_INVALID) "()File sizes are invalid, real=%x, compress=%x"

Definition

The compressed and uncompressed sizes of the file are not valid. The client request is invalid.

Resolution

The client must specify valid file sizes. Escalate the problem to Cisco Technical Support for further analysis.

0x9014e (EX_DX_TEXT_SIZE_INVALID) "()Text string length is invalid, len=%x"

Definition

The length of the text string is invalid. There is a fixed-length field where the string should be stored. The client request is invalid.

Resolution

The client must specify a valid string length. Escalate the problem to Cisco Technical Support for further analysis.

0x9014f (EX_DX_FAIL_GET_BUF) "()Activation failed, no buffers avail, err=%x"

Definition

Cisco MeetingPlace failed to activate a request because it was unable to get a buffer for this request. Buffers are needed for all data transfers. This error is caused by an internal software inconsistency.

Resolution

Try again later. Escalate the problem to Cisco Technical Support for further analysis.

0x90150 (EX_DX_FAIL_FREE_BUF) "()Failed to free a buffer, err=%x"

Definition

Failed to free a buffer. Check the err parameter for the reason for the failure. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90151 (EX_DX_FAIL_OPENFILE) "()Failed to open the file, err=%x"

Definition

Failed to open the file. Check the err parameter in order to determine the cause of the failure. The file may not exist, there may not be enough recording space available, or there may be an internal software inconsistency.

Resolution

If there is an internal error, escalate the problem to Cisco Technical Support for further analysis.

0x90152 (EX_DX_BUF_INVALID_HANDLE) "()Invalid Handle, hd=%x."

Definition

The handle used to access the request table is invalid. The handle for that entry is different than the one in the entry itself. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90153 (EX_DX_BUF_USE_COUNT) "()Invalid Use Count for a buffer, BufHd=%x, Usecnt=%x."

Definition

While Cisco MeetingPlace tried to free a buffer, it found that the use count was invalid. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90154 (EX_DX_ACTIVE_LIMIT) "()Max active rq number reached, num active=%x."

Definition

The maximum number of active requests has been reached.

Resolution

This is not an error, it is just a normal condition of operation.

0x90155 (EX_DX_NOT_EXPORT) "(GetData)Getting data, but not exporting, handle=%x."

Definition

This request to get data is processed for an entry that is not exported. This issue is caused by an internal software inconsistency.

Resolution

Abort the operation and try again, and escalate the problem to Cisco Technical Support.

0x90156 (EX_MISSING_THREADS) "(cpmain)Not all threads initialized (rt, mid)."

Definition

Not all of the real-time and mid-level threads are created within a reasonable amount of time. Some ports may not be correctly activated. This error is caused by an internal software inconsistency or an operating system problem.

Resolution

Restart the system and escalate to Cisco Technical Support.

0x90157 (EX_DX_INVALID_BUF_CONTROL_STATE) "()The state for the Control Buffer is invalid=%x."

Definition

The state of the control buffer is invalid. There is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90158 (EX_DX_BUF_NOT_QUEUED) "(ActivateRq)Cannot Activate non-queued buffer, state=%x."

Definition

Can activate only requests that are queued. The buffer has an invalid state. This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90159 (EX_DX_COPY_TO_RESP_FAIL) "(GetData-Buf)Failed to copy from buf to resp msg, err=%x"

Definition

Failed to copy the requested data from the buffer to the client response message. This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x9015a (EX_DX_NOT_IMPORT) "(PutData)Putting data, but not importing, handle=%x"

Definition

This request to add data is processed for an entry that does not import. This issue is caused by an internal software inconsistency.

Resolution

Abort the operation and try again. Escalate the problem to Cisco Technical Support.

0x9015b (EX_DX_INVALID_NUM_BYTES_HEADER) "(PutData-buf)Not enough bytes for header rec=%x"

Definition

The number of bytes received for this put data request, which is of the type that needs to update the header record, is not enough to fill the header record. This request should be the first put Data request, and it needs to contain at least the same number of bytes as the header record. Either the client did not send a correct put data request, or there is an internal software inconsistency.

Resolution

Check the request from the client, abort the operation and try again, and escalate the problem to Cisco Technical Support.

0x9015c (EX_DX_INVALID_BUF_HD) "(Valid-Rq)The Buf Handle for Rq is invalid=%x,should be=%x"

Definition

The request specified has a buffer handle different that the one passed as a parameter. This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x9015d (EX_DX_NOT_ACTIVE) "(DeximClientRq)Data Export and Import Not Active."

Definition

The cpserver export and import feature is not currently active. All requests receive an error in response. Either a user disabled the feature, or there is an internal software inconsistency.

Resolution

Try again later or escalate the problem to Cisco Technical Support.

0x9015e (EX_DX_INVALID_STATE_FOR_ACTIVATE) "(ActivateRq)Invalid state=%x"

Definition

This is an invalid state for a request to go to the active state. This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x9015f (EX_OD_FAILED_TO_WAIT_FOR_EVT) "(OutDialSM)Failed to receive expected event"

Definition

While a port waits for an event while it places a call, it fails to receive the expected event in the allocated amount of time. The outdial attempt is aborted and the normal retry mechanisms are followed. There can be signaling in the port, an unexpected tone received over the port, or an internal software inconsistency.

Resolution

Retry the outdial and escalate the problem to Cisco Technical Support.

0x90160 (EX_SI_INVALID_INDEX) "(ClearEntry)Index out of bounds=%x, max=%x"

Definition

The index into the Session Interest table is too big. There is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90161 (EX_SI_NO_FREE_ENTRY) "(Interest:GetFreeEntry)No more free entries"

Definition

There were no more free entries in the Session Interest table. Either there is an internal software inconsistency, or too many clients have made requests for service.

Resolution

Wait for a time with less traffic, and escalate the problem to Cisco Technical Support.

0x90162 (EX_SI_SESSIONID_NOT_FOUND) "(Interest:FindSessionID)Session ID not found"

Definition

The session ID was not found in the Session Interest table. Either the session ID was already processed, or there is an internal software inconsistency.

Resolution

This condition is probably not a problem. If other errors occur, escalate the problem to Cisco Technical Support.

0x90163 (EX_SI_INTEREST_NOT_INIT) "(Interest)Not initialized"

Definition

The Session Interest object was not correctly initialized, probably because the shared memory was not allocated. This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90164 (EX_SI_INTEREST_NOT_FOUND) "(RemoveInterest)Session not being tracked=%x"

Definition

This session ID is not tracked, and there is no knowledge of it. It can be that no client has requested to keep track of this session or connection ID, that connection has terminated, or that there is an internal software inconsistency.

Resolution

If an action fails, try it again. If it fails again, escalate the problem to Cisco Technical Support.

0x90165 (EX_SI_SUBS_NO_INTEREST) "(RemoveInterest)Subsystem has no interest"

Definition

The subsystem has no interest in the session ID. No interest removed. This issue is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90166 (EX_DX_CONN_NOT_FOUND) "(FindSessionID)Session not found, session=%x"

Definition

The session was not found in the request table. Either the session is not currently used in an export or import, or there is an internal software inconsistency.

Resolution

If an action fails, retry it, and escalate the problem to Cisco Technical Support.

0x90167 (EX_DX_ABORT_SESSION) "(Abort)Export Import Session aborted=%x"

Definition

The session is aborted. Cisco MeetingPlace received a notification that the client session is no longer valid, or there is an internal software inconsistency.

Resolution

Repeat the export or import request. If problem happens more than ten times a day, escalate the problem to Cisco Technical Support.

0x90168 (EX_DX_RQ_TIMEOUT) "(CheckConsistency)Dexim, timeout waiting for request, session=%x"

Definition

Cisco MeetingPlace times out while it waits for a request for an export or import session. Clients must make requests within a specified maximum time (usually 60 seconds). If no request is received within that time, it is assumed that the client had a problem. The session is cancelled and all requests from the client for the cancelled session are rejected. Either the client went away, or the client was too slow and took too much time between requests.

Resolution

If the client was overloaded, wait until the load is reduced and try again.

0x90169 (EX_DX_INVALID_RESOURCEID) "(ValidateImport)Invalid ResID, handle=%x, type=%x"

Definition

The resource ID specified by the client for the import request is not supported. The client specified an invalid resource ID type.

Resolution

Make the client change the resource ID type and try again. If the resource ID is the correct type, or if the failure continues, escalate the problem to Cisco Technical Support.

0x9016a (EX_DX_INVALID_SUB_RESOURCEID) "(ValidImp)Invalid SubResID, handle=%x, type=%x"

Definition

The subresource ID specified by the client for the import request is not supported. The client specified an invalid subresource ID type.

Resolution

Make the client change the subresource ID type and try again. If the subresource ID is the correct type, or if it continues to fail, escalate the problem to Cisco Technical Support.

0x9016b (EX_INVALID_XLAT_TABLE_NUM) "Invalid Translation table num=%d, max=%d"

Definition

The translation table that the client has requested to use is invalid. The request is rejected. The client specified an invalid translation table number.

Resolution

Make the client change the translation table number and try again. Escalate the problem to Cisco Technical Support.

0x9016c (EX_TVAPI_INVALID_PORT_GRP_NUM) "(InitPortGrp)PortGrpNum invalid,PortGrp=%x,Port=%x"

Definition

The port group number obtained from the TVAPI for the given port is invalid. The valid range for the port groups for all ports is from 0 to CM_MAX_NUM_PORT_GROUPS (32). Either there is an internal software inconsistency, or a database inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis. The system uses a default value of zero for the group number of the port. The system must be correctly configured, with a valid range set for the port group number, and then the system must be restarted so that the new values are activated.

0x9016d (EX_PORT_GRP_INVALID_PORT_NUM) "(GetPortGroupNum)PortNum invalid=%x"

Definition

Cisco MeetingPlace attempted to get the port group number that a port belongs to, but the port number is invalid. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9016e (EX_DX_REQUEST_NOT_QED) "(DXDeleteRequest)Handle is not queued, handle=%x"

Definition

Failed to find the handle in the queue for waiting requests. Either there is an internal inconsistency, or the client made an invalid request.

Resolution

Try not to make the client send invalid requests. Escalate the problem to Cisco Technical Support.

0x9016f (EX_INVALID_XLAT_NUM_LIST) "Invalid Number of phone# to check if dialable num=%d, max=%d"

Definition

The client has requested to check if dialable an invalid number of phone numbers. A default value of 1 is used, so only the first number in the list is checked.

Resolution

Make the client change the number of phones to list and try again. Escalate the problem to Cisco Technical Support.

0x90170 (EX_INVALID_DEXIM_TCP_NUM_DIST) "Invalid Number units to distribute LFS file, num=%d, max=%d"

Definition

The client has requested the Linear File System (LFS) file be distributed to an invalid number of Voice Processing (VP) units or IP addresses.

Resolution

Make the client change the number of VP units the LFS file should be distributed to, and escalate the problem to Cisco Technical Support.

0x90171 (EX_DEXIM_DATA_TYPE_NOT_SUPPORTED) "Data Type to Ex/Import, not currently supported=%d"

Definition

The data type that the client has requested to export is not supported in this type of device.

Resolution

Make the client request a supported data type for the device. Escalate the problem to Cisco Technical Support.

0x90172 (EX_SOCK_CREATE) "Failed to create a socket, err=%x"

Definition

The system call to create a socket failed due to a system error. Check the error value to determine the cause of the failure.

Resolution

Reboot the system and verify that this time the socket is successfully created. Escalate the problem to Cisco Technical Support.

0x90173 (EX_SOCK_IOCTL) "Failed to ioctl-nonblocking socket, err=%x"

Definition

The system call to set a socket as non-blocking failed due to a system error. Check the error value to determine the cause of the failure.

Resolution

Reboot the system and verify that this time the socket is successfully set to non-blocking. Escalate the problem to Cisco Technical Support.

0x90174 (EX_SOCK_SET_OPT) "Failed to set option for a socket, err=%x, socket=%x, option=%x"

Definition

The system call to set an option for a socket (setsockopt) failed due to a system error. Check the error value to determine the cause of the failure.

Resolution

Reboot the system and verify that next time the option is set successfully. Escalate the problem to Cisco Technical Support.

0x90175 (EX_SOCK_BIND) "Failed to bind a socket, err=%x, socket=%x"

Definition

The system call to bind a socket (bind) failed due to a system error. Check the error value to determine the cause of the failure.

Resolution

Reboot the system and verify that next time the socket can bind successfully. Escalate the problem to Cisco Technical Support.

0x90176 (EX_SOCK_LISTEN) "Failed to listen on a socket, err=%x, socket=%x"

Definition

The system call to listen on a socket (bind) failed due to a system error. Check the error value to determine the cause of the failure.

Resolution

Reboot the system and verify that next time the socket can listen. Escalate the problem to Cisco Technical Support.

0x90177 (EX_GETHOSTNAME) "Failed to get this unit host name, err=%x"

Definition

The system call to get this node host name failed due to a system error. Check the error value to determine the cause of the failure.

Resolution

Reboot the system and verify that next time Cisco MeetingPlace can get the host name. Log in as a superuser and at the csc prompt, issue the more /etc/hosts command. The host name displays. Escalate the problem to Cisco Technical Support.

0x90178 (EX_GET_UNITS_DB_FAIL) "Failed to get the configured units from the DB, err=%x"

Definition

Failed to get all of the configured units from the database. All requests to distribute a Linear File System (LFS) file to other units in the system fail until the system is rebooted and the database problem fixed. This issue is the result of a system error. Check the error value to determine the cause of the failure.

Resolution

Reboot the system and verify that next time Cisco MeetingPlace can get the configured units from the database.

0x90179 (EX_DIST_FILE_FAIL) "Failed to distribute a LFS file to all units, err=%x"

Definition

Failed to distribute a Linear File System (LFS) file to all the requested units. The cause of the failure can be found in the error code.

Resolution

Check the description under the err value.

0x9017a (EX_SELECT_FAIL) "Failed OS call select, err=%x"

Definition

System call select failed. This is a low-level error condition. When more than five consecutive errors of this nature are detected, the cpserver restarts. Check the err value to find the cause of the error.

Resolution

Check the description under the err value.

0x9017b (EX_SOCK_ACCEPT_FAIL) "Failed to accept a Socket connection, err=%x"

Definition

Cisco MeetingPlace failed to accept a new socket connection request. Check the err value to find the cause of the error.

Resolution

Check the description under the err value.

0x9017c (EX_DX_DIST_UNIT_NUM) "(DeximDistFiles)Invalid Unit number, unit=%x"

Definition

The unit number that the message is sent to is not our unit number, so Cisco MeetingPlace should never have received this message request.

Resolution

The client should send a request with valid data. Escalate the problem to Cisco Technical Support.

0x9017d (EX_DX_DIST_STR_LEN) "(DeximDistFiles)Invalid String Length for LFS, len=%x"

Definition

The length of the string that the client supplied to be written in the header record in the Linear File System (LFS) is invalid.

Resolution

The client should send a request with valid data. Escalate the problem to Cisco Technical Support.

0x9017e (EX_DX_CPAPI_INIT) "(TCPClientInit)Failed to Init all CPAPIs"

Definition

Failed to initialize all of the Call Processing (CP) application programming interfaces (APIs) for all the units. Check for previous entries in the error log in order to determine the cause.

Resolution

Escalate the problem to Cisco Technical Support.

0x9017f (EX_DX_UNIT_NUM) "(TCPClient)Unit number is invalid, unit=%x, max=%x"

Definition

The unit number is invalid. It can be too large (greater than MAX_UNITS_PER_SYSTEM), or it can be unconfigured. The parameter in the error string indicates the unit number. The client may have sent an invalid unit number or there may be an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90180 (EX_DX_CP_LOGIN) "(TCPClient)Failed to login to a remote cpserver, unit=%x, err=%x"

Definition

Cisco MeetingPlace failed to log in to a remote cpserver. Check the other parameters logged to find the reason for the failure and the unit number that you failed to log into. This error occurs because the client sent an invalid unit number, because the unit is down or has not been configured, or because of an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90181 (EX_DX_DIST_NULLID) "()Cannot distribute a Null FileID"

Definition

Cannot distribute a null file ID to other units. The client data does not point to a valid file.

Resolution

The client must specify a valid file from the Linear File System (LFS) to be exported. Escalate the problem to Cisco Technical Support for further analysis.

0x90182 (EX_DX_DIST_IMPORT_RQ) "(DFARUImportMsgRq)All Import rq failed"

Definition

All the import requests sent to other units failed. The node requested to be distributed to the Linear File System (LFS) file may be down, not configured, or have other problems.

Resolution

The client should try the request later, when the units are up. Escalate the problem to Cisco Technical Support for further analysis.

0x90183 (EX_DX_DIST_UNIT_BUSY) "(DFARUImportMsgRq)Unit too busy, import rq queued, unit=%x"

Definition

The unit is too busy (has more than ten active requests), so it has queued an import request. In order not to overload the unit or delay other units, Cisco MeetingPlace does not deliver to this unit at this time. For this file to be delivered, the requestor must send another request later.

Resolution

The client should try the request later, when the unit is less busy. Escalate the problem to Cisco Technical Support for further analysis.

0x90184 (EX_DX_DIST_SOCK) "(DFARUSocketConn)Failed socket setup, err=%x, unit=%x"

Definition

Failed to complete all of the socket creation and setup tasks for a unit. Check the parameter err to find the reason for the failure.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90185 (EX_DX_DIST_TCP_DONE_RQ) "(DFARUTcpDone)All Import rq failed"

Definition

All of the TCP Done requests sent to other units failed. The node requested to be distributed to the Linear File System (LFS) file are down, not configured, or have other problems.

Resolution

The client should try the request later, when the units are up. Escalate the problem to Cisco Technical Support for further analysis.

0x90186 (EX_DX_DIST_GET_DATA) "(DFARUWrtHdAndData)Fail to get more data from LFS,err=%x"

Definition

While Cisco MeetingPlace distributes a file to all requested units, it fails to get more data from the Linear File System (LFS) so that it can continue to export the file. This issue is caused by an internal LFS error.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90187 (EX_DX_DIST_WRITE_HD) "(DFARUWrtHd)Fail to write all Hd"

Definition

Failed to write the Remote RqHd to all the units requested. Units may be down or TCP may have problems.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90188 (EX_DX_DIST_NFDS) "(Init)Not enough File descriptors,max=%x"

Definition

The maximum number of file descriptors that Cisco MeetingPlace can get from Lynx is too small for the normal operation of the cpserver distribution of files. The operating system may have begun to run out of resources. Non-critical applications are disabled in order to avoid a more serious effect on the system.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90189 (EX_DX_DIST_SELECT) "()Select sys call failed, errno=%x"

Definition

The select system call failed. The operating system may have begun to run out of resources, so the request is aborted.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9018a (EX_DX_NO_UNIT_FOR_FD) "(GetUnitFromFd)The socket Fd not used by any unit,Fd=%x"

Definition

The File descriptor (Fd) is not used by any of the sockets that are connected to the other units. It is an invalid Fd. This error is caused by an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9018b (EX_DX_DIST_UNDERFLOW) "(DFARUWriteData)Underflow of data,Fd=%x"

Definition

The number of bytes written is larger than the number of bytes left. This error is caused by an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9018c (EX_DX_EVT_LOST) "(DeximTCPWrite)Missed event"

Definition

The eventpoll timed out, but there was a socket ready for it to write to. This fact indicates that an event somehow got lost. This error is due to an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9018d (EX_DX_TIMEOUT) "(DeximTCPWrite)Timeout waiting for a ready socket."

Definition

The eventpoll timed out and there is nothing to do. This error is due to an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9018e (EX_DX_ACCEPT) "(DoForEverTCPMainLoop)Accept sys call failed, err=%x"

Definition

When it receives a connect request from a socket, ans responds with an accept, but the system call fails. Check the value of the error parameter in order to determine the cause for the error. The error may be due to an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x9018f (EX_DX_INVALID_SOCK_STATE) "(DoFrEvrTCPMainLp)Invalid State for socket=%x"

Definition

The state of the socket is unexpected. When Cisco MeetingPlace receives a new connect request for a socket, it should have the socket as not active in its internal data structures. This is not the case. Still, the new connect request is accepted and the old resources are released. This error is caused by an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90190 (EX_DX_INVALID_SOCK) "(Abort)Invalid socket File descriptor,Fd=%x"

Definition

The file descriptor for a socket is invalid. This error is due to an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90191 (EX_DX_SOCK_WRITE) "()Write to socket failed, err=%x,Fd=%x"

Definition

Failed to write to the socket. Check the err parameter value to find the cause of the problem. The issue can be due to an internal inconsistency.

Resolution

Escalate the problem to Cisco Technical Support for further analysis.

0x90192 (EX_DX_INVALID_NUM_BYTES) "()Invalid num bytes requested, num=%x, max-min=%x"

Definition

The number of bytes requested to be read or written is invalid. The number is either 0 or greater than the maximum allowed. Either the client did not send the correct number of bytes, or there is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90193 (EX_DX_FD_NOT_SET) "()The Socket File Descriptor was not set, fd=%x"

Definition

The File descriptor (Fd) for the socket was not set in the Fd set. In order to reach this point, the Fd should have been set. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90194 (EX_DX_FD_SET) "()The Socket File Descriptor was set, fd=%x"

Definition

The File descriptor (Fd) for the socket was set in the Fd set. In order to reach this point, it should not have been set. This error is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90195 (EX_DX_NUM_BYTES) "()Data Exp-Imp Number of bytes invalid, num=%x"

Definition

The number of bytes that have been received for an import or the number of bytes that are being sent by an export is invalid. This problem is caused by an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x90196 (EX_DX_NOT_DISTLFSFILE) "Request is not to DistLFS File, rq=%x"

Definition

This request should be the one that distributes an Linear File System (LFS) file to other units, but it was not that type. This issue is caused by an internal software inconsistency.

Resolution

Abort the operation and try it again. Escalate the problem to Cisco Technical Support.

0x90197 (EX_INVALID_REQUEST) "Request is a valid one for this state, rq=%x"

Definition

Either the request that the port is in is not valid for the state of the port, or the request is not a valid request. This issue is caused by an internal software inconsistency.

Resolution

Abort the operation and try it again Escalate the problem to Cisco Technical Support.

0x90198 (EX_DX_INVALID_SERVER_MSG) "Socket Msg from server invalid,was=%x,should=%x"

Definition

The message sent by the cpserver to a client (in this case, the cpserver itself, which acts as a client while it distributes a Linear File System [LFS] file) did not receive all the expected data. This issue is caused by either a communication problem by the server or an internal software inconsistency.

Resolution

Ignore this alarm if it occurs only once. Escalate the problem to Cisco Technical Support if it occurs frequently.

0x90199 (EX_DX_INVALID_RQ_CODE) "The request code is invalid, req=%x"

Definition

The request code is invalid for this operation, so it cannot be performed. This error is due to an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support.

0x9019a (EX_DX_TCP_DONE_BEFORE_DATA) "Import-Rcvd TCPDone before all the data,hd=%x"

Definition

This alarm is not an error. It means that the TCP Done request is received before all the data is received over the socket. This situation is very unusual, because it means that information arrived over a message queue faster than over a direct socket.

Resolution

This is not an error and no resolution is required.

0x9019b (EX_DX_CLIENT_CANCEL) "Client cancelled operation"

Definition

This alarm is not an error. The client has decided to cancel the export or import operation for some reason. This alarm often means that the client decides not to continue with the upload or download of an attachment.

Resolution

This is not an error and no resolution is required.

0x9019c (EX_PORT_MAYBE_HANG) "Port may be in a hang state, p=%x"

Definition

Cisco MeetingPlace has just received a hangup on a port that cannot be processed because MeetingPlace still thinks that it is busy. Cisco MeetingPlace gave the caller ring no answer (RNA). But it should have released all port resources by this time, and it should also have received the Voice User Interface (VUI) disconnect request. Because it has not, it assumes that something is wrong and begins to free things. This problem occurs because Cisco MeetingPlace is out of synch with the VUI and the TVAPI. The cause is not clear, but the final state is.

Resolution

This problem should clear itself for the next call. If it does not, contact Cisco Technical Support.

0x9019d (EX_SIGPIPE) "Socket generated SIGPIPE, signal=%x"

Definition

Cisco MeetingPlace received a signal SIGPIPE, which has interrupted whatever activity MeetingPlace was performing at the time. This is because Cisco MeetingPlace was doing things with sockets, which sometimes get closed at inconvenient times.

Resolution

No resolution is required. MeetingPlace should be able to recover and continue.

0x9019e (EX_TOO_LONG_TO_DISC) "VUI took too long to disconnect, port=%x, time sec=%x"

Definition

If it takes the Voice User Interface (VUI) too long (usually more than one minute) to send a disconnect request, a warning is logged. Either there is too much network (LAN) traffic on a networked system, or the VUI is confused.

Resolution

No resolution is required. MeetingPlace is able to recover and continue.

0x9019f (EX_PORT_CONFIG) "Access ports: %d max; %d licensed; %d TVAPI"

Definition

This alarm shows the number of ports in the server (unit) record, the number licensed, the default for no license, and the number reported by the TVAPI.

0x901a0 TVAPI MSC FW Error, Card= , Port= , type=

Definition

This alarm is demoted from Minor to Warning in server version 4.2.1b and later. The customer should no longer see this error.

The card number and port number indicate the card number and port number in which this alarm is generated.

Explanations for common TYPEs are:

  • Type 17—This is usually harmless. However, in some instances a port can get into a state on the MSC whereby if a user calls in on that port, they experience dead air.

  • Type 25—This error occurs when some unknown sequence of events causes high level software to ask the firmware to do something (add third party to a two-party outdial conference) and the firmware logs a complaint that this is "illegal".

  • Type 26—This is when a party action is not appropriate for the conference specified. For example, the high level software tries to delete a party from a conference that either does not exist or does not contain the party. The high level software is confused.

  • Type 28—This is when a party action is not appropriate for the current party state. This is often related to the type 25 error. For example, if the high level software tries to add the third party to a two-party conference, you see the type 25 error. Then when the high level software tries to delete the party, you see the type 28 error because the firmware never added it because of the earlier error.

For all of these, it is unlikely that users are affected. However, if users complain about dead air, or a failed transfer to attendant, or not being able to attend a conference, it can be useful to correlate the complaints to any of these MSC errors.

0x901a1 TVAPI PRC FW Error, Card= , Port= , type=

Definition

The Card=# and Port=# variables indicate the card number and port number in which this alarm generates.

  • Type 2c—This type indicates excess port delay. This indicates that the firmware is very busy, and some operations can be slightly delayed by a few hundred milliseconds. This type of delay is never noticed by an end user, so this is logged for information purposes only.

0x901a2 (EX_TV_EVT_MSCHW_ERROR) "(TVAPIHndlr)TVAPI MSC HW Error,Card=%x,Port=%x,type=%x"

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x901a3 (TVAPIHndlr)TVAPI PRC HW Error, Card=0, Port=3, Type=3

Definition

The Port Resource Card (PRC) reports a possible hardware related problem. Type definitions (in hexadecimal) are listed here:

  • 01: queue became empty too soon

    02: too many elements in command

    03: event queue is full

    04: port number in command is out of range

    05: port state invalid for current command

    06: prior port command not processed when a new command received

    07: invalid command

    08: invalid event code

    09: 4ms interrupts are not occurring

    0A: invalid buffer descriptor action

    0B: invalid action or action/buffer combo

    0C: timer expired in missed tick

    0D: error flag set by interrupt processing

    0E: DSP reported error

    0F: voice buffer op already in progress

    10: action table error

    11: port has entered the error state

    12: seize for outgoing was unsuccessful

    13: tone buffer has too many tones

    14: invalid buffer number

    15: no voice buffer ready when should be

    16: invalid buffer size-less than 1 sample

    17: no record buffer ready when needed

    18: already have tones in buffer when given more

    19: DSP dual port memory test failure

    1A: DSP boot loader detected error

    1B: invalid configuration parameter

    1C: DSP reported leading edge, but tone > DTMF

    1D: error logged already

    1E: timeout unexpected in state

    1F: unexpected tone received in state

    20: invalid tone number to output

    21: conf number in command is out of range

    22: party number in command is out of range

    23: error in play/record buffer

    24: no parties in conference

    25: too many parties added to conference

    26: party not in specified conference

    27: conference state invalid

    28: party state invalid

    29: no resource port allowed for special 2 party conf

    2A: update_conf attempt to switch resource ports

    2B: stack calls exceeded stack depth

    2C: port event handling delayed too much

    2D: i960 generated a Card Fault

    2E: record buffer overflow

    2F: ECM command queue overflow

    30: bad ECM checksum

    31: ECM error report

    32: ECM memory test failure

    33: debug report

    34: bad DSP number in HPI access

    35: bad ECM queue pointers

    36: expected DSP is missing

    37: ECM not responding to checksum command

    38: PRM BSPs out of sync

    39: PRM not handshaking on command

    40: number of errors

Resolution

Type 3—This means that the PRC firmware reports events to the cpserver, but the queue gets full. Either the cpserver is dead (rare) or the PRC driver is confused (even rarer). Issue the vt command on that PRC. Once in vt, issue the perr and idb commands and report results to Cisco Technical Support.

Types 38 and 39—The PRM_NOT_RESPONDING (0x39) and PRM_OUT_OF_SYNC errors (0x38) are very serious, and result in completely unacceptable service on this card. Most likely, these errors are caused by bad hardware. Replace this card immediately.

Types 35 and 37—ECM_BAD_QUEUE (0x35) and ECM_NOT_RESPONDING (0x37). Issue the VT commands on the PRC and Master Switch Controller (MSC) (perr and cerr). Restart the server. When the server has come back up, issue the VT commands again. If the errors return after the restart, it is time to replace the hardware.

0x901a4 (EX_PROMPT_NUM_TOO_LARGE) "(GetFromWhere)Invalid recnum=%x, Dir=%x, Disk=%x"

Definition

The file ID has a record number that is greater than the maximum number of prompts in the system. It is an invalid record number the prompt does not exist.

Resolution

This problem is caused by inconsistency between the prompts and the software. Escalate the problem to Cisco Technical Support.

0x901a5 (EX_ML_OUTPULSE_FAIL) "(EvtPortReq)Failed to outpulse, port=%x, err=%x"

Definition

Failure to outpulse (dial) in the port as specified in the request from the client. Search the event log for related entries to determine the reason for the failure.

Resolution

Check the event log for reasons for the failure.

0x901bb IP Gateway not responding, IP addr %08x

Definition

Cisco MeetingPlace is not longer able to detect the Voice over IP (VoIP) gateway. VoIP calls are not possible until VoIP gateway communication is restored.

Resolution

Restart the VoIP gateway. If that does not work, restart Cisco MeetingPlace. Also, check to see whether an Ethernet cable is disconnected or the network is down (or partially down).

0x901bc Gateway monitor thread start error: %x

Definition

The IP gateway monitoring thread has failed to start.

Resolution

Escalate the problem to Cisco Technical Support.

0xa000a Disk not configured, disk=%x

Definition

Even though the disk specified is within the valid range, that disk has no shared memory allocated.

Resolution

Configure the disk. Escalate the problem to Cisco Technical Support, because this is an internal inconsistency in the software.

0xa000b Recnum too big=e6d,DiskNum=2,DirNum=0,WhichBitMap

Definition

The record number is out of range. Either it is bigger than the maximum allowed or a file is created with 0 records. This problem is caused by an overwritten variable or stack, or an incorrect disk, directory, or bitmap.

Resolution

Make sure that the correct disk, directory, or bitmap is accessed. Report the error to Cisco Technical Support.

0xa0012 Invalid rectype=%x

Definition

The valid record types are Header (0), Index (1) and VBlock (2). All other values are not yet valid. This problem is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support. You can also attempt to reset the system and try again.

0xa0013 Fail to write all bytes, req=%x, written=%x

Definition

The operating system (OS) fails to write the correct number of bytes to disk for a header, index, or block record. This is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support. You can attempt to reset the system and try again.

0xa0014 OFA Invalid handle=184c00c1, OFA=0

Definition

The specified file to read/write is not opened. The file handle is invalid. This is an internal software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support. You can attempt to reset the system and try again.

0xa0015 Fail to read all bytes, req=b240106, read=

Definition

Failure to read the correct number of bytes to disk for a header, index, or block record. This is an internal Software inconsistency.

Resolution

Escalate the problem to Cisco Technical Support. You can attempt to reset the system and try again.

0xa0016 failed, Dyn Config not loaded, disk=%x, dir=%x

Definition

The system fails to open a directory. Check the error log for more details of why the attempt to open fails. Check other codes in the event log for more details.

Resolution

Check the error log and event log for more details.

0xa0017 FS Dir not mounted, Disk=%x, Dir=%x

Definition

The directory is not mounted, so operations cannot be requested on that directory. Make sure that the directory and the disk are configured. If not, configure them before you continue. Otherwise, make sure that the static and dynamic configuration files in the disk are correct.

Resolution

Reconfigure the directory and disk in the database. Recreate the static and dynamic files and make sure that the directory and disk specified are valid.

0xa001c Invalid index to OFA array=186

Definition

The index to the array is too large. This error is caused by an overwritten stack or variable, stack overflow, and similar problems.

Resolution

This is an internal software inconsistency. Escalate the problem to Cisco Technical Support.

0xa001e OpenFile array (OFA) full

Definition

The array that holds the list of all open files is full. There is too much traffic in the Conference Manager system. Too many ports play, delete, and record messages at the same time.

Resolution

Configure some ports to not take calls if the problem continues to occur. If it does not happen again, take no further action. This is an internal software problem. Notify Cisco Technical Support so that the size of the array can be increased.

0xa0023 Id does not match HRec id,id=%x, Hid=%x

Definition

The file ID used to open the file does not match the ID in the header record.

The file ID used to open the file is an old one, and the file has already been deleted. This is a security mechanism that the file system has to prevent unauthorized access to files. It may also be an internal software inconsistency.

Resolution

Escalate the error to Cisco Technical Support.

0xa0024 Index FileID diff than HRecID, IRecNum=%x

Definition

The file ID used to open the file does not match the ID in the index record.

The file ID used to open the file is an old one, and the file has already been deleted. This is a security mechanism that the file system has to prevent unauthorized access to files. It may also be an internal software inconsistency.

Resolution

Escalate the error to Cisco Technical Support.

0xa0025 Block FileID diff than HRecID, BRecNum=%x

Definition

The file ID used to open the file does not match the ID in the block, or the file ID in one of the blocks does not match the main file ID.

The file ID used to open the file is an old one, and the file has already been deleted. This is a security mechanism that the file system has to prevent unauthorized access to files. It can also be an internal software inconsistency or an inconsistency in the file system.

Resolution

Escalate the error to Cisco Technical Support. You may have to execute a utility in order to check the file system internal inconsistency.

0xa0030 H/I signature invalid,rec#=%x, signature%x%x

Definition

The signature in the record read from the disk is invalid. This implies that the data in it cannot be trusted because it can be corrupt. Data on the disk is corrupted (a disk problem), or the previous time that the record was written to disk, the data was already corrupt.

Resolution

The record is unusable. Delete the recording session. Escalate the problem to Cisco Technical Support.

0xa003a Next Index still valid, fh=3d050078

Definition

The background thread that reads the next index receives a request to read one for an opened file handle, but the next index is still valid. It cannot continue reading it because it would overwrite the next index with a new one. This is an internal software inconsistency problem.

Resolution

Escalate the problem to Cisco Technical Support.

0xa003b Still reading next I, fh=40cd00e6

Definition

The background thread that reads the next index receives a request to read one for an opened file handle, but the flag that indicates that the action is performed is not set correctly. This is an internal software inconsistency problem.

Resolution

Escalate the problem to Cisco Technical Support.

0xa0042 Bad license record for number of access ports

Definition

The number of access ports configured in Cisco MeetingTime does not match the number of licenses purchased for the access port option.

0xa0046 AIO Read failed, err=%x, SeekPos=%x, nBytes=%x, Filehandle=%x

Definition

The asynchronous read request failed. The information indicated by the parameter err shows the reason for the failure.

Resolution

Check the description for the parameter err.

0xa0047 AIO Write failed, err=%x, SeekPos=%x, nBytes=%x, Filehandle=%x

Definition

The asynchronous write request failed. The information indicated by the parameter err shows the reason for the failure.

Resolution

Check the description for the parameter err.

0xa0071 Dec count too big=%x

Definition

This alarm indicates that there is a voice file with errors. The error is probably caused by the deletion of a voice file or attachment. When this happens, the file system does not really delete the file, but decrements its use count. As a result, the file system is confused because the number of usecounts it believes there are does not match with the number the application thinks there are.

In the error log, you should see some logs from fsdynconfig.cc around each of the times this alarm occurs.

Resolution

If the alarm does not occur frequently, it can be ignored. If not, shut down the Cisco MeetingPlace server, and then issue the vfptrfix –f command. This utility takes a long time, so run it over night. This method should recover a small percentage of the space.

0xa0072 Recording exceed limit=%x, %x

Definition

The number of used blocks in the system that are reserved for this type of recording has been exceeded. Too many recordings exist in the system.

Resolution

This issue is not really a problem, although if the system runs out of recording space, it may be time to start purging conference recordings.

0xa0073 Recording limits,tot=%x,Conf=%x,NonConf=%x,Def=%x

Definition

The operating system sets the recording limits for conference and non-conference recording types. It receives a request to set the recording limits, or it sets them as default while it comes up.

Resolution

This is an informational message and there is nothing to fix.

0xb0065 PRC is not responding ([11], card 2, slot 7, [-1])

Definition

The Port Resource Card (PRC) does not respond to commands. There may be other, related errors and alarms. The PRC may be bad.

Resolution

If this is the first occurrence, document the failures, restart the system, and monitor the system for repeat occurrences. If it happens again, replace the PRC with a new card at the latest revision level.

0xb0068 MSC is not responding ([10], card 0, slot 4, [-1])

Definition

The Master Switch Controller (MSC) does not respond to commands. There may be other, related errors and alarms. The MSC may be bad.

Resolution

If this is the first occurrence, document the failures, restart the system, and monitor the system for repeat occurrences. If it happens again, replace the MSC with a new card at the latest revision level.

0xb0079 Yellow Alarm detected on this T1 span ([14], card 1

Definition

The T1 span is detected as reporting a yellow alarm from the far end. This can result from:

  1. Incorrect span configuration (for example, Extended Superframe [ESF] instead of Superframe [SF], binary 8-zero substitution [B8ZS] instead of jammed bit).

  2. Faulty wiring at the punchdown block (a loose wire in the connector).

  3. A failure at the Channel Service Unit (CSU).

  4. A problem at the private branch exchange (PBX) or central office (CO).

Resolution

Issue the spanstat command in order to verify the current state of the span. If the span is up, and there is a reasonable explanation for the prior failure, then no action is necessary. If the span is still down, verify the span configuration and the connection into the Cisco MeetingPlace server. With assistance from the customer or PBX tech, verify the wiring and the CSU. Swap the span with a known good span and see whether the problem follows the span (this implies a customer wiring or PBX/CO configuration problem) or whether the problem stays with the Domestic Trunk Interface ((DTI) hardware interface (this implies a Cisco MeetingPlace server hardware or configuration problem). If it looks like a DTI problem, issue the spanstat -s, spanstat -all, hwconfig, alarm, and errorlog commands in order to gather the appropriate logs and contact Cisco Technical Support for further investigation. Also issue the dcard, span, and port commands in order to check that the configuration matches that of the PBX/PSTN.

0xb0095 Unexpected evtpoll event 3f, evtData b898, evtTag b

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0xb009b Unsupported PRC hardware revision 5 in slot 2

Definition

The Port Resource Card (PRC) detected is newer than the software expects.

Resolution

The software applies the latest firmware to the newer hardware and attempts to activate the card. If Cisco MeetingPlace works correctly, ignore the error. Otherwise, contact Cisco Technical Support for further investigation.

0xb009c Unsupported MSC hardware revision 5 in slot 0

Definition

The Master Switch Controller (MSC) detected is newer than the software expects.

Resolution

The software applies the latest firmware to the newer hardware and attempts to activate the card. If Cisco MeetingPlace works correctly, ignore the error. Otherwise, contact Cisco Technical Support for further investigation.

0xb009d PRC hardware not most recent, revision 0, slot 0

Definition

The Port Resource Card (PRC) detected is older than the software expects. This can result in system failures.

Resolution

You might need to replace the PRC. Contact Cisco Technical Support for further investigation.

0xb009e MSC hardware not most recent, revision 0, slot 0

Definition

The Master Switch Controller (MSC) detected is older than the software expects. This can result in system failures.

Resolution

You might need to replace the MSC. Contact Cisco Technical Support for further investigation.

0x100009 Shadow database copy aborted: database locked

Definition

You must remove the file /tmp/shadow.lock from the shadow server.

Resolution

Make a Telnet connection to the Cisco MeetingPlace server and issue these commands to login, locate the file, and delete it:

rlogin vp9 cd /tmp rm shadow.lock exit

0x100011 DB disk backup is disabled. Run 'save' to enable

Definition

This minor alarm is generated during system startup if the internal disk-to-disk database backup is disabled. It is disabled automatically by several maintenance procedures, notably any software upgrade.

Resolution

In order to prevent this alarm condition, a technician should issue the save command, which makes the upgrade permanent. The purpose of the alarm is to remind the technician to issue the save command.

0x100019 Server still has factory default password for 'admin' login name

Definition

The default User ID/password that MeetingPlace was shipped with "admin/cisco" has not been changed.

Resolution

Log in as "admin" with the "cisco" password. Run the command line utility passwd in order to change the password for admin. Make sure to save your password in a safe place or you will not be able to log in to MeetingPlace as "admin" in the future.

0x120102 WebPub Data Service (Unit #) Not Responding or 0x120103 WebPub Data Service (Unit #) Failed

Definition

The Cisco MeetingPlace Web Replication Service has failed on the specified unit. Replication Service used to be called “Data Service” in older versions of Cisco MeetingPlace Web.

Resolution

Check the status of the Windows NT services in the service manager, and restart the Cisco MeetingPlace Replication Service and check to see if web publishing is up.

Check for any Dr. Watson errors. If there are any such errors, get the Dr. Watson log and application and system event viewer log.

Check the application event viewer log to see any error messages that may be logged at the time the alarm was generated.

0x120104 WebPub Data Service (Unit #) Shutdown

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x120142 WebPub Agent (Unit #) Not Responding

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x120143 WebPub Agent (Unit #) Failed

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x120144 WebPub Agent (Unit #) Shutdown

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x120182 WebPub Audio Service (Unit XX) Not Responding

Definition

The Web Publisher service fails on the specified unit.

Resolution

Issue the gwstatus command to check the status of the service on Cisco MeetingPlace. If this also shows it does not respond, issue the gwstart command in order to restart the service. Check the status again to see that the service is functional.

0x120b02 MPBackup (Unit %d) Not Responding

Definition

The Cisco MeetingPlace backup operation for unit "%d" started, but now no longer indicates that it is alive.

Resolution

Restart the backup operation.

0x120b03 MPBackup (Unit %d) Failed

Definition

The Cisco MeetingPlace backup operation for unit "%d" started, but did not finish correctly.

Resolution

Restart the backup operation.

0x120f02 Gateway SIM Agent (Unit #) Not Responding or 0x120f03 Gateway SIM Agent (Unit #) Failed

Definition

The gateway system integrity manager (GWSIM) agent on the specified unit has failed. This is usually associated with other alarms, such as MAJ 0x7009c.

Resolution

The cause of loss of communications between the Cisco MeetingPlace server and the Windows NT gateway server needs to be determined. Follow the steps to troubleshoot outlined in the entry for alarm 0x7009c. A quick workaround to help GWSIM reestablish a connection to the Cisco MeetingPlace server is to manually stop and restart the Cisco MeetingPlace Gateway SIM Service on the Windows NT server.

0x120f04 Gateway SIM Agent (Unit #) Shutdown

Definition

None.

Resolution

Contact Cisco Technical Support for further investigation.

0x140011 Gateway SIM Manager: no client handler for this request

Definition

A handler for a gateway system integrity manager (GWSIM) request has timed out in the Gateway SIM Manager.

Resolution

Retry the request.

0x150022 Gateway SIM Agent: message send error: %lx

Definition

SIM Agent (on the Windows NT server side) sent a message to the SIM Manager (on the Cisco MeetingPlace server side), but experienced an error.

0x170001 (EX_AC_BD_INVAL_HANDLE) Inval bd hndl = ???, bd # = ???, bd type = ???

Definition

An operation is requested of ACTI where an invalid board handle is passed to it by TVAPI. Alternately, there is internal table corruption in ACTI and invalid board information is read. The board number listed, if valid, most likely cannot send or receive calls.

Resolution

The only solution is to restart the system. If there is enough capacity with other Audiocodes boards, this restart can be held off until a time convenient for the customer. Otherwise, the restart needs to be as soon as possible. If the board number or board type are garbage (valid board types are 14-TP1610 and 13-TP610), issue the blade command in order to reinstall the Audiocodes boards.

0x170003 (EX_AC_BD_HNDL_XLAT_ERR) Bd hndl xlate err = ???, bd # = ???, bd type = ???, bd hndl = ???

Definition

TVAPI has no knowledge of the fact that each TP1610 board is really two sub-boards called “modules.” TVAPI therefore provides the handle of module 0 on a TP1610. ACTI then looks at the span number provided with the handle and determines whether the handle really maps to module 1. This error means that the board handle to module translation failed. Generally, the error number is either 45 (ACTI_STATUS_ERROR_SPAN_NUM_OUT_OF_RANGE ) or 44 (ACTI_STATUS_ERROR_NO_MATCHING_HANDLE). If the error number is 45, TVAPI most likely has a problem because it is sending down an illegal span number. Otherwise, something is internally wrong in the ACTI handle translation table. In either case, the TVAPI operation fails, which often results in lost calls.

Resolution

The only solution is to restart the system. If there is enough capacity with other Audiocodes boards, this restart can be held off until a time convenient for the customer. Otherwise, the restart needs to be as soon as possible. If the board number or board type are garbage (valid board types are 14-TP1610 and 13-TP610), issue the blade command in order to reinstall the Audiocodes boards.

0x170008 (EX_AC_GET_CH_DEF_ERR) Get chan def err = ???, bd type = ???

Definition

As the system initializes, channels are set up with a default template configuration that is customized based on what TVAPI requests. If this initial template cannot be set up, all channels for the board type in question are useless for making and receiving calls.

Resolution

The only solution is to restart the system. The restart needs to be as soon as possible. If the board type is garbage (valid board types are 14-TP1610 and 13-TP610), issue the blade command in order to reinstall the Audiocodes boards.

0x170009 (EX_AC_CH_OPEN_ERR) Chan open err = ???, bd # = ???, sysport = ???

Definition

As the system initializes, channels are opened to allow them to make and receive calls. If a channel cannot be set up, it has no identity that TVAPI can use for outcalls on the channel. In this case, another channel can be used, because the unopened channel indicates an error. However, for incalls, the private branch exchange (PBX) or central office (CO) receives an immediate “RELEASE COMPLETE” message, and incalls to Cisco MeetingPlace can be lost.

Resolution

The only solution is to restart the system. The restart needs to be as soon as possible. If the board number is garbage (board numbers should range from 0 to 2), issue the blade command to reinstall the Audiocodes boards. The sysport number needs to range from 0 to 735 for T1 PRI or 0 to 959 for E1 PRI. If the sysport is out of range, also issue the blade command in order to reinstall the Audiocodes boards.

0x17000a (EX_AC_CH_TDM_XC_TO_ERR) Chan PSTN to H.110 xcon err = ???, sysport = ???, H.110 st:ts = ???:???

Definition

During initialization, channels are mapped to specific H.110 streams and timeslots. If these mappings cannot be done, calls can be established but users experience "dead air". Users are not able to either talk or listen regarding conferences.

Resolution

The only solution is to restart the system to fix this problem. The restart needs to be as soon as possible because calls that are established give the illusion that everything is OK.

0x17000b (EX_AC_CH_TDM_XC_FR_ERR) Chan PSTN from H.110 xcon err = ???, sysport = ???, H.110 st:ts = ???:???

Definition

As the system initializes, channels are mapped to specific H.110 streams and timeslots. If these mappings cannot be done, calls can be established, but users experience dead air. Users are unable to either talk or listen to conferences.

Resolution

The only solution is to restart the system. The restart needs to be as soon as possible. This is because calls that are established give the illusion that everything is functional.

0x17000c (EX_AC_CH_RFG_ERR) Chan PSTN from H.110 xcon err = ???, sysport = ???, H.110 st:ts = ???:???

Definition

During normal operation, TVAPI tries to reconfigure a channel “on the fly,” but the attempt fails. “On the fly” channel reconfiguration is currently not supported, so this message should never be seen. However, if this feature is added, this failure indicates that the channel is probably unusable.

Resolution

The only solution is to restart the system.

0x170022 (EX_AC_GET_SPAN_DEF_ERR) Get span def err = ???, bd type = ???, phy mod # = ???

Definition

As the system initializes, spans (trunks) are set up with a default template configuration that is customized in accordance with what TVAPI requests. If this initial template cannot be set up, all spans for the board type in question are useless for making and receiving calls.

Resolution

The only solution is to restart the system. The restart needs to be as soon as possible. If the board type is garbage (valid board types are 14-TP1610 and 13-TP610), issue the blade command in order to reinstall the Audiocodes boards. Also, the physical module number ("phy mod") should range from 0 to 1. Any other value indicates internal corruption, which also warrants a restart as soon as possible.

0x170024 (EX_AC_BD_OPEN_ERR) Bd open err: bd # = ???, bd type = ???, bd rel # = ???

Definition

ACTI attempted to open an Audiocodes module (either one-half of an MA-16 or a single MA-4). The board handle received back from the firmware download and open attempt was bad. (Any board handle returned with value -1 (0xFFFFFFFF) or less is bad). "bd #" is the number of the 0-relative board number of the Audiocodes board within all Audiocodes boards installed. "bd type" is 14 for a TP1610 (regular or lite). "bd type" is 13 for a TP610 (which is no longer used). "bd rel #" is the 0-relative board number of the Audiocodes board within that type of board. Since TP1610 regular and lite boards have the same board ID, "bd rel #" and "bd #" is always the same.

Resolution

This can indicate bad configuration in the blade command or a bad board. Try to get more information on the problem. Enable stderr tracing to /tmp/cpserver/stderr by ACTI. In order to turn this on, as CSC:

  1. cd/ tmp/cpserver

  2. touch acti_stderr_trace.txt

  3. Restart the system.

If the error occurs again, look in /tmp/cpserver/stderr for various errors near the top of the file.

0x170025 (EX_AC_BD_OPEN_ERR2) Bd open err2: phy mod 1 hndl = ???, phy module hndl 0 = ???

Definition

This is extra information from the 0x170024 "Bd open err" error. See error 0x170024 for more information. Under this follow-on information. However, "phy mod 1 hndl" is the bad handle received back if physical module 1 (logical module 0) is opened. This is probably a -1. The handle "phy mod 0 hndl" is the bad handle received back if physical module 0 (logical module 1) is opened. This is also probably a -1. For an MA-4 board, only physical module 0 (logical module 1) exists for download.

Resolution

See the resolution suggestions for alarm 0x170024.

0x170026 (EX_AC_BD_ACCESS_ERR) Bd access err (bus # is -1): bd # = ???, bd type = ???, bd rel # = ???

Definition

This error indicates that the driver cannot find the board when it initially queries the board for existence.

Resolution

Issue the blade command in order to reinstall the Audiocodes boards. Restart the system.

0x170028 (EX_AC_SPN_ENB_DSBL_ERR) Span enable/disable error = ???, span = ???, enable(1)? = ???, bd id = ???

Definition

For some reason, the system is unable to change the clocking status of a span. The span could not be disabled or enabled as the system master clock synchronization source. The result is that the master Master Switch Controller (MSC) clock provider takes over with its internal crystal. This produces slips. The slips might produce noise. However, calls are usually not dropped unless the slip rate is extremely high.

Resolution

Unplug and replug the span in question; if that does not correct the problem, restart the system.

Warnings

0x200fd Scheduler %d not found in invitee list for conf %ld

Definition

The list of people to be part of an Audio conference needs to include the person who calls the meeting. However, for some reason, the person who calls the meeting is not in that list.

Resolution

If the person who calls the meeting cannot get into their own meeting, delete the meeting and create a new one that they can attend. If this continues to be a problem, escalate this issue to Engineering.

0x200ff Lock held for %d seconds

Definition

A MeetingPlace thread has obtained and kept an internal resource for an excessive amount of time.

Resolution

Escalate this problem to Engineering.

0x3012d Prompt language %d may not be installed correctly

Definition

Language # "%d" probably does not play correctly (or at all) because of installation problems.

Resolution

When this error code occurs it means that a voice prompt language is not installed correctly and it needs to be reinstalled. It is possible that "upgradeprompt" needs to be run. It is possible that the language needs to be reinstalled from tape/CD (or ftp).

0x30131 RSNA transfer service not available (erc=%d)

Definition

The RSNA transfer fails for an unexpected reason (indicates software defect).

Resolution

Contact CSC about software updates and a list of known problems with RSNA.

0x30132 RSNA transfer failed, erc=%d

Definition

The RSNA transfer fails because there is either a configuration problem, environmental problem, or an end-point that does not support the transfer protocol.

Resolution

Re-check the RSNA configuration of both MeetingPlace systems. Make sure that end-point supports the transfer protocol.

0x30133 RSNA not active

Definition

Receives an incoming RSNA call but RSNA is not active on this server.

Resolution

Activate RSNA on the server if RSNA functionality is desired.

0x30139 RSNA: Info block had bad signature

Definition

Invalid signature on the information block is received from the transferring server. Indicates a defect or transmission error.

Resolution

Attempt the RSNA action again and see if the error persists. If so, contact CSC about possible RSNA updates. Also, check the network to see if its error rate is low and that the network is configured properly.

0x3013a RSNA: Info block version mismatch, got=%d, expected=%d

Definition

Unsupported information block version number. Indicates that the information provided by the transferring server is unusable. Corrupted in transmission or server version incompatibility.

Resolution

Make sure that the two MeetingPlace servers have the same software revision. Also, check the network to see if its error rate is low and that the network is configured properly.

0x3013b RSNA: Info block bad size, got=%d, expected=%d

Definition

Invalid size is reported for the transfer information block. Corrupted in transmission or defect.

Resolution

Attempt the RSNA action again and see if the error persists. If so, contact CSC about possible RSNA updates. Also, check the network to see if its error rate is low and that the network is configured properly.

0x3013c RSNA: Info block has bad key code, got=%d, expected=%d

Definition

The key code for the transfer information block is unrecognized. This can be due to a corruption in transmission, software version incompatibility, or defect.

Resolution

Attempt the RSNA action again and see if the error persists. If so, contact CSC about possible RSNA updates. Also, check the network to see if its error rate is low and that the network is configured properly.

0x3013d RSNA: Info block has bad checksum

Definition

The checksum on the transfer information block is invalid. Corrupted in transmission or attempt at forgery.

Resolution

Check the network to see if its error rate is low and that the network is configured properly. Also, consider whether there is a security issue.

0x3013e RSNA: Info block has bad time stamp, got=%d, now=%d

Definition

The time stamp on the transfer information block is invalid. This can be because it was corrupted in transmission, delayed in transmission, clock skew between servers, or an attempt at forgery.

Resolution

Attempt the RSNA action again and see if the error persists. If so, contact CSC about possible RSNA updates. Also, check the network to see if its error rate is low and that the network is configured properly. Also, check the time on the two MeetingPlace servers to see if clock skew is present and, if so, correct this. Lastly, consider whether there is a security issue.

0x3013f RSNA: No user password provided

Definition

The transferring MeetingPlace server does not provide a password for the user who is transferred.

Resolution

Set the password for the user on both MeetingPlace servers to be the same. Then reattempt the operation to verify that the problem is fixed.

0x30140 RSNA: Password mismatch

Definition

The password provided in the transfer information block does not match the local user password. This indicates an inter-server database synchronization problem.

Resolution

Reconfigure the password for the user on both MeetingPlace servers to be the same. Then reattempt the operation to verify that the problem is fixed.

0x30141 RSNA: Database insert failed, status=%d

Definition

Failure to add the RSNA application record to the database. Indicates a database problem or failure to communicate with the database.

Resolution

Look for other error indications.

0x3014d Number of language licenses (%d) exceeds max allowed (%d)

Definition

The server can support from one to four languages. More than four language licenses are installed.

Resolution

Uninstall enough language licenses until there are no more than four.

0x700cc (EX_C3_FANOUT) One or multiple fans are failing

Definition

In the C3 box, one or more of the cooling fans fails.

Resolution

Have service personnel schedule downtime on the C3 as soon as possible in order to replace the bad fan(s). Alternately, there can be a possibility that only the fan filters need to be cleaned.

0x700cd Error querying STAT register, errno=%d

Definition

Fails to read the STAT register on CPU card.

Resolution

This can be a hardware problem. Run hwconfig to see if it has the same complaint. If yes, replace the CPU card.

Note: The hwconfig command probably does not complain if this is a transient problem. However, still replace the CPU card if this error is found in exlog from time to time.

0x100013 File system block capacity reached or exceeded (fs %d,util %d,cap %d)

Definition

The Lynx file system exceeds the space it needs for normal MeetingPlace operation.

Resolution

Search and remove unwanted file(s), especially large files such as infocap.

0x100014 File system inode capacity reached or exceeded (fs %d,util %d,cap %d)

Definition

The Lynx file system has exceeded the number of file identifiers it needs for normal MeetingPlace operation.

Resolution

Search and remove unwanted file(s). Run out of inode can be because of many small files.

0x100016 DB backup to gateway failed (code %d)

Definition

The database is not successfully backed up to the BackupGateway even though a BackupGateway is found.

Resolution

Verify that the backup gateway is operational and configured correctly. Verify that there is sufficient disk space available to the backup gateway. If backups are being copied to a network drive, change the backup drives to be a local drive on the backup gateway.

0x100017 DB backup to gateway failed: no backup gateway found

Definition

The database is not successfully backed up because no BackupGateway is found.

Resolution

Verify that the backup gateway is operational and configured correctly. If the backup feature is not in use, disable backups from MeetingTime.

0x100018 DB backup to gateway failed: timeout copying files

Definition

The database is not successfully backed up because the file copy takes an excessively long time.

Resolution

Verify that the backup gateway is operational and configured correctly. Verify that there is sufficient disk space available to the backup gateway. If backups are copied to a network drive, change the backup drives to be a local drive on the backup gateway.

0x170002 (EX_AC_BD_CLOSE_ERR) Bd close err = %d, bd # = %d, phy mod # = %d, bd type = %d

Definition

When the system shuts down, the ACAPI library reports that it is not able to close a board. Since the system is already shutting down, service is not affected.

Resolution

Nothing needs to be done. However, Engineering needs to be notified in case this problem indicates greater problems in the ACTI software.

0x170004 (EX_AC_WIDE_ERR) ACTI wide error = %d, err type = %d, bd hndl = %d, chan hndl = %d

Definition

A specific message from a board has been sent up to ACTI. There are many possible errors. Generally most of these are recoverable.

Resolution

Nothing needs to be done. However, Engineering needs to be notified in case this problem indicates greater problems in the ACTI software or Audiocodes boards.

0x170005 (EX_AC_BD_GET_INFO_ERR) Bd get info err: bd rel # = %d, bd type = %d, PCI bus = %d

Definition

ACTI attempts to get information about the Audiocodes boards in the system and fails.

Resolution

Nothing needs to be done. If this is harmless, no other errors or warnings are reported. Otherwise, take action based on the other warnings/errors.

0x170006 (EX_AC_SH_RAM_STORE_ERR) Sh RAM store err: bd # = %d, bus = %d, old/new slot = %d/%d

Definition

ACTI attempts to store information about the Audiocode boards into its Shared RAM but fails. This can be because Shared RAM cannot be created properly. The general result is that some off-line utilities like spanstat do not report information properly.

Resolution

Nothing needs to be done unless the various span and port utilities need to be run. If they need to be run, restart the system in order to fix this problem.

0x170007 (EX_AC_SPN_TRACE_SET_ERR) Span trace set err = %d, bd # = %d, span = %d, trace level = %d

Definition

ACTI attempts to set the tracing settings for a span but fails. If the tracing level is about to increase, the additional trace information expected by the user is not gathered. If the tracing level is about to decrease, the current level continues. In this case, some extra system load is present because of the unwanted tracing.

Resolution

Nothing needs to be done as this does not affect service. However, this problem probably indicates a lack of system integrity. This can include problems with ACTI Shared RAM. Restart the system in order to clear the problem.

0x17000d (EX_AC_CH_CLOSE_ERR) Chan close err = %d, sysport = %d, ch hndl = %d

Definition

When the system shuts down, the ACAPI library reports that it is not able to close a channel. Since the system is already shutting down, service is not affected.

Resolution

Nothing needs to be done. However, Engineering needs to be notified in case this problem indicates greater problems in the ACTI software.

0x17000f (EX_AC_SPN_NREF_DSBL_ERR) Span netref dsbl err = %d, span = %d, bd id = %d, phy mod # = %d

Definition

For some reason, the system is not able to get a TP1610 module to stop driving H.110 NetRef. The result of this is that the NetRef produced is probably bad or absent. The master MSC clock provider takes over with its internal crystal. This produces slips. The slips probably produce noise. However, calls are probably not dropped unless the slip rate is extremely high.

Resolution

Restart the system.

0x170011 (EX_AC_BD_SET_INFRA_ERR) Bd netref set infrastruct err = %d, bd id = %d, bd hndl = %d

Definition:

In order to change NREF clocking, ACTI has to execute a special "SetInfrastructure" routine. This message indicates that the routine does not execute properly. The result is that the clock sync related command does not complete. This probably means that the system is synced to a bad clock but the master clocking MSC takes over. Since the master clocking MSC uses its internal crystal, there are slips and some voice degradation. There can even be unexpected call disconnects if the slips are very bad.

Resolution

Restart the system.

0x170012 (EX_AC_BD_UPD_CLK_CFG) Bd update clk config err = %d, bd id = %d, bd hndl = %d

Definition

This is the same as warning 0x170011.

Resolution

Restart the system.

0x170013 (EX_AC_SPN_NREF_CHG_ERR) Span netref chg err = %d, span = %d, enable(1)? = %d, bd id = %d

Definition

This is the same as warning 0x170011.

Resolution:

Restart the system.

0x170014 (EX_AC_PORT_SND_CALL_PROC_ERR) Port send call proc err = %d, sysport = %d, call hndl = %d

Definition

ACTI attempts to send a Call Proceeding message for an incall and fails. The incall is probably lost.

Resolution

If this happens only on rare occasions, there can be a load problem or race condition. In this case, nothing needs to be done. If this happens often, the Audiocodes board or ACAPI library software are probably corrupted. Restart the system to fix this.

0x170015 (EX_AC_PORT_SND_ALERTING_ERR) Port send alerting err = %d, sysport = %d, call hndl = %d

Definition

ACTI attempts to send an Alerting message for an incall and fails. The incall is probably lost.

Resolution

If this happens only on rare occasions, there can be a load problem or race condition. In this case, nothing needs to be done. If this happens often, the Audiocodes board or ACAPI library software are probably corrupted. Restart the system in order to fix this.

0x170016 (EX_AC_PORT_SND_ANS_CALL_ERR) Port send answer call err = %d, sysport = %d, call hndl = %d

Definition

ACTI attempts to send an Answer Call (CONNECT) message for an incall and fails. The incall is probably lost.

Resolution

If this happens only on rare occasions, there can be a load problem or race condition. In this case, nothing needs to be done. If this happens often, the Audiocodes board or ACAPI library software are probably corrupted. Restart the system in order to fix this.

0x170017 (EX_AC_PORT_SND_DISC_CALL_ERR) Port send disc call err = %d, sysport = %d, call hndl = %d

Definition

ACTI attempts to disconnect a call and fails. The call probably disconnects within 60 seconds anyway.

Resolution

If this happens only on rare occasions, there can be a load problem or race condition. In this case, nothing needs to be done. If this happens often, the Audiocodes board or ACAPI library software are probably corrupted. Restart the system in order to fix this.

0x170018 (EX_AC_PORT_SND_REL_CALL_ERR) Port send release err = %d, sysport = %d, call hndl = %d

Definition

ACTI attempts to release a call originally disconnected by the far-end. The call is probably released by the far-end within 60 seconds anyway.

Resolution

If this happens only on rare occasions, there can be a load problem or race condition. In this case, nothing needs to be done. If this happens often, the Audiocodes board or ACAPI library software are probably corrupted. Restart the system in order to fix this.

0x170019 (EX_AC_PORT_SND_REJ_CALL_ERR) Port send reject call err = %d, sysport = %d, call hndl = %d

Definition

ACTI attempts to reject an incall. The call is probably cleared down by the far-end within 60 seconds anyway.

Resolution

If this happens only on rare occasions, there can be a load problem or race condition. In this case, nothing needs to be done. If this happens often, the Audiocodes board or ACAPI library software are probably corrupted. Restart the system in order to fix this.

0x17001a (EX_AC_PORT_OUTCALL_ERR) Port outcall err = %d, sysport = %d, bd hndl = %d, spn:ts = %d

Definition

ACTI attempts to make an outcall and fails. This can be because of glare. The higher level software of MeetingPlace probably retries the outcall on a different channel.

Resolution

If this happens only on rare occasions, there can be a load problem or race condition. In this case, nothing needs to be done. If this happens often, the Audiocodes board or ACAPI library software are probably corrupted. Restart the system in order to fix this.

0x17001b (EX_AC_NO_BOARDS_IN_SYSTEM) No boards in system

Definition

When MeetingPlace comes up, ACTI is called by TVAPI and reports no Audiocodes boards in the system. If the system is still configured or not configured for Audiocodes boards, this is not a problem. If the system is expected to be fully operational and have Audiocodes boards, then Telephony access is not available.

Resolution

If there needs to be Audiocodes boards in the system, make sure that these boards are physically present in the Chassis. They need to be present starting in Slot 1 and optionally Slot 2 (if two boards). If they are present, run blade in order to reconfigure the system and restart.

0x17001c (EX_AC_SHARED_RAM_MAP_ERR) Map ACTI shared RAM error

Definition

ACTI is not able to map its Shared RAM for use by spanstat and other utilities. Spanstat, acsetrace, and other utilities are not able to run.

Resolution

If the utilities mentioned do not need to run, nothing needs to be done. Otherwise, restart the system in order to fix the problem.

0x17001d (EX_AC_SHARED_RAM_UNMAP_ERR) Unmap ACTI shared RAM error

Definition

ACTI is not able to unmap its Shared RAM at the time of shutdown. Since the system shuts down anyway, no harm is done.

Resolution

Since this occurs at the time of shutdown, you can ignore this warning.

0x17001e (EX_AC_SHARED_RAM_INIT_UNMAP_ERR) Initial unmap ACTI shared RAM error

Definition

ACTI is not able to unmap its Shared RAM at the time of initialization (to unmap any old Shared RAM first). Spanstat, acsetrace, and other utilities are not able to run.

Resolution

If the utilities mentioned do not need to run, nothing needs to be done. Otherwise, restart the system in order to fix the problem.

0x17001f (EX_AC_SHARED_RAM_CREATE_ERR) Create ACTI shared RAM error

Definition

ACTI is not able to create its Shared RAM at the time of initialization. Spanstat, acsetrace, and other utilities are not able to run.

Resolution

If the utilities mentioned do not need to run, nothing needs to be done. Otherwise, restart the system in order to fix the problem.

0x170020 (EX_AC_SHARED_RAM_TRUNCATE_ERR) Truncate ACTI shared RAM error

Definition

ACTI is not able to "size" its Shared RAM at the time of initialization. Spanstat, acsetrace, and other utilities are not able to run.

Resolution

If the utilities mentioned do not need to run, nothing needs to be done. Otherwise, restart the system in order to fix the problem.

0x170021 (EX_AC_BD_TYPE_ERR) Bd type error = %d, type = %d, num found = %d

Definition

ACTI tries to get specifics about a particular board type and fails (the number of that board that currently exists). Since this is required before Audiocodes boards can be initialized, Audiocodes boards are available for use if needed. Telephony access is not available in MeetingPlace if provided by the Audiocodes boards.

Resolution

If the Audiocodes boards are not in use, this error can be ignored. Otherwise, reinstall the boards using blade and restart the system.

0x170023 (EX_AC_BD_ALREADY_OPEN) Bd already opened: bd # = %d, bd type = %d

Definition

ACTI is asked more than once by TVAPI to open a board. The board is already successfully opened. The request should not have been made again. It causes no harm. However, this can indicate an error in TVAPI or higher.

Resolution

Nothing needs to be done. If other errors/warnings occur in conjunction with this, do what the other errors/warnings indicate.

0x170038 Port get statistics error: sysport # = %d

Definition

An attempt is made to get port statistics from ACTI (probably by spanstat or tvportstat) for port "%d". However, the statistics are never delivered as per the ACTI Shared RAM handshake protocol.

Resolution

Try to request the statistics again. If this fails, there can be a problem with ACTI Shared RAM. If this is so, a restart of the system is required to clear it.

0x170039 Port clear statistics error: sysport # = %d

Definition

An attempt is made to get port statistics from ACTI (probably by spanstat or tvportstat) for port "%d". However, the statistics are never delivered as per the ACTI Shared RAM handshake protocol.

Resolution

Try to request the statistics again. If this fails, there can be a problem with ACTI Shared RAM. If this is, a restart of the system is required in order to clear it.

0x17003a Fatal ACTI wide error = %d, bd hndl = %d, chan hndl = %d

Definition

One of the installed Audiocodes boards (also called "Multi-Access blade") has a major problem described by the leftmost "%d" error code.

Resolution

Check PSTN or VoIP call activity on the affected board with spanstat or tvportstat. If normal activity continues, note the incident for later in case of problems. If call activity stops or spanstat/tvportstat cannot access ACTI, a system restart is needed. The specific "%d" error code that describes the error can be decoded by Product Development engineers or Audiocodes.

0x17003b Recoverable ACTI wide error = %d, bd hndl = %d, chan hndl = %d

Definition

One of the installed Audiocodes boards (also called "Multi-Access blade") has a recoverable problem described by the leftmost "%d" error code.

Resolution

Check PSTN or VoIP call activity on the affected board with spanstat or tvportstat. If normal activity continues, note the incident for later in case of problems. If call activity stops or spanstat/tvportstat cannot access ACTI, a system restart is needed. The specific "%d" error code that describes the error can be decoded by Product Development engineers or Audiocodes.

0x17003c Info ACTI wide error = %d, bd hndl = %d, chan hndl = %d

Definition

One of the installed Audiocodes boards (also called "Multi-Access blade") indicates special information described by the leftmost "%d" code.

Resolution

Nothing needs to be done unless these information entries flood the log. If the log is flooded, restart the system and also inform Cisco Technical Support.

0x17003d Debug ACTI wide error = %d, bd hndl = %d, chan hndl = %d

Definition

One of the installed Audiocodes boards (also called "Multi-Access blade") indicates special debug information described by the leftmost "%d" code.

Resolution

Nothing needs to be done unless these debug entries flood the log. If the log is flooded, restart the system and also inform Cisco Technical Support.

0x17003f Broken RTP stream, bd/mod = (%d/%d), chan hndl = %d, sysport = %d

Definition

The VoIP RTP stream connected to the indicated sysport (system absolute port number) has broken. If this condition persists for more than a few seconds, this ends the VoIP call in progress on that port. For additional background information, the bd (Multi-Access board number), mod (module on board), and chan hndl (channel handle relative to the board module) are also provided.

Resolution

If the call is eventually lost, reattempt the call to see if only a temporary network anomaly has occurred. If calls can be connected successfully, monitor your network for lost packets. Otherwise, look further to determine the reason for lost connectivity.

  • Does this occur on all sysports? In this case, possible causes are a broken/unplugged Ethernet cable, bad network switching equipment, or even a MeetingPlace problem that requires a system restart.

  • Does this occur only for certain groups of phone numbers? It is likely a problem with switching equipment further back in the network or with a particular Telephony provider.

  • Does this happen only for a certain number? There can be a problem that exists with the far-end phone or cable connected to that phone.

0x170041 (EX_AC_BD_UNKNOWN_TYPE_ERR) Bd unknown type of %d, bd # = %d, phy mod # = %d

Definition

When ACTI opens a board, the board type it is asked to open is not one it knows how to configure.

Resolution

If all the installed Audiocodes boards come up okay, nothing needs to be done other than report this warning. Otherwise, see what boards are present through blade, reconfigure the system, and restart it.

0x170042 (EX_AC_BD_TOO_MANY_CAS_PROT_ERR) Bd too many CAS protocols of %d, bd # = %d, bd type = %d, phy mod # = %d

Definition

There are too many CAS protocol files that are received by ACTI from TVAPI. Since ACTI does not support CAS protocols, something is probably wrong in the database, in TVAPI, or higher.

Resolution

If all the installed Audiocodes boards come up okay, nothing needs to be done other than report this warning. Otherwise, reconfigure the system through blade and restart.

0x170043 (EX_AC_SPN_LINE_INFO_REQ_ERR) Span line info request err = %d, span # = %d, bd hndl = %d, rel span # = %d

Definition

The spanstat command requests ACTI to go get span statistics. ACTI tries and fails. Statistics from the single spanstat request is not available.

Resolution

If this happens once, this can be load related and no harm is done. Request statistics again. Otherwise, something is probably wrong in ACTI or lower. Restart the system to fix this.

0x170044 (EX_AC_SPN_PSTN_ERR_DBG_EVENT) Span err/dbg evt = ???, bd id # = ???, phy mod # = ???, span # = ???

Definition

ACTI receives a span related error or debug event from an Audiocodes board. Generally, these events occur at the time of initialization or soon after.

Resolution

Most of these events are warnings that can be ignored. If this happens only initially and not very often, nothing needs to be done. Otherwise, something is probably wrong in one or more of the Audiocodes boards which can affect traffic. Restart the system in this case.

0x170045 (EX_AC_SPN_PSTN_ERR_DBG_EVENT2) Span err/dbg evt2: err code = %d, timeslot = %d, origin = %d, line in file = %d

Definition

This is follow-on information for error 0x170044. Any span error/debug warning generates two Exlog entries.

Resolution

This is the same resolution as 0x170044.

0x170046 (EX_AC_BD_ERR_DBG_EVENT) Bd err/dbg evt = %d, bd id # = %d, phy mod id = %d

Definition

ACTI receives a board (actually module) related error or debug event from an Audiocodes board. Generally, these events occur at the time of initialization or soon after.

Resolution

Most of these events are warnings that can be ignored. If this happens only initially and not very often, nothing needs to be done. Otherwise, something is probably wrong in one or more of the Audiocodes boards which can affect traffic. Restart the system in this case.

0x170047 (EX_AC_BD_ERR_DBG_EVENT2) Bd err/dbg evt2: err code = %d, origin = %d, line in file = %d

Definition

This is follow-on information for error 0x170046. Any board error/debug warning generates two Exlog entries.

Resolution

This is the same resolution as for 0x170044.

0x170048 (EX_AC_SPN_UNSUPPORTED_COMMAND) Span unsupported command: span # = %d

Definition

This indicates that TVAPI requests ACTI to execute an API routine that is not supported. This should never happen. If it does happen, this can be because the TVAPI software is not built properly with ACTI software.

Resolution

Check if this happens right after a software upgrade. If so, contact engineering. If not, the system software is probably corrupted. Restart the system in order to fix this.

0x170049 (EX_AC_SPN_GET_ALM_STATUS_ERR) Span get alarm status error: span # = %d

Definition

The spanstat command requests ACTI to go get span alarm status. ACTI tries and fails. Alarm status from the single spanstat request is not available.

Resolution

If this happens once, this can be load related and no harm is done. Request alarm information again. Otherwise, something is probably wrong in ACTI or lower. Restart the system in order to fix this.

0x170050 (EX_AC_SPN_GET_STATISTICS_ERR) Span get statistics error: span # = %d

Definition

Spanstat requests ACTI to go get span statistics. ACTI tries and fails. Statistics from the single spanstat request are not available. (Note that statistics are requested in two places to get the entire picture. That is why two versions of this warning exist).

Resolution

If this happens once, this can be load related and no harm is done. Request statistics again. Otherwise, something is probably wrong in ACTI or lower. Restart the system in order to fix this.

0x170051 (EX_AC_NSF_IE_CIC_VALUE_ERR) NSF IE CIC value error. sysport = %d, NSF IE # = %d, char# = %d, value = %d

Definition

The NSF code CIC value received by ACTI from TVAPI is not "well formed". The CIC needs to be a sequence of three or four ASCII characters from '0' to '9'. ACTI finds these characters to be out of range. The NSF code is not sent in the Setup message that goes out. This can cause the outcall to fail if the NSF code is needed. Otherwise, the outcall can cost the customer a lot more to make.

Resolution

The CIC in the database is probably faulty. Re-input all the NSF data and restart the system.

0x170052 (EX_AC_NSF_IE_CIC_TYPE_ERR) NSF IE CIC type error. sysport = %d, NSF IE # = %d, type = %d

Definition

The NSF code CIC type received by ACTI from TVAPI is outside the legal range. The NSF code is not sent in the Setup message that goes out. This can cause the outcall to fail if the NSF code is needed. Otherwise, the outcall can cost the customer a lot more to make.

Resolution

The CIC in the database is probably faulty. Re-input all the NSF data and restart the system.

0x170053 (EX_AC_NSF_IE_BFCV_RANGE_ERR) NSF IE BFCV range error. sysport = %d, NSF IE # = %d, BFCV value = %d

Definition

The NSF code BFCV value received by ACTI from TVAPI is outside the legal range. The NSF code is not sent in the Setup message that goes out. This can cause the outcall to fail if the NSF code is needed. Otherwise, the outcall can cost the customer a lot more to make.

Resolution

The CIC in the database is probably faulty. Re-input all the NSF data and restart the system.

0x170054 (EX_AC_NSF_IE_BFCV_TYPE_ERR) NSF IE BFCV type error. sysport = %d, NSF IE # = %d, BFCV type = %d

Definition

The NSF code BFCV type received by ACTI from TVAPI is outside the legal range. The NSF code is not sent in the Setup message that goes out. This can cause the outcall to fail if the NSF code is needed. Otherwise, the outcall can cost the customer a lot more to make.

Resolution

The CIC in the database is probably messed up. Re-input all the NSF data and restart the system.

0x170055 (EX_AC_NSF_IE_INSERT_ERR) NSF IE insert error. sysport = ???, ret_code = ???

Definition

ACTI tries to insert the NSF IE (Information Element) into an outgoing setup message but fails. The NSF code is not sent in the Setup message that goes out. This can cause the outcall to fail if the NSF code is needed. Otherwise, the outcall can cost the customer a lot more to make.

Resolution

The ACTI software or lower is probably corrupted. Restart the system in order to fix this.

Info

0x3012e User note on port %d. Conf %d subconf %d. Keys %d

Definition

A user pressed the keycode 1379 nnnn where nnnn is indicated by "Keys %d". The port and conference number of the user is also noted in the message.

Resolution

This is used as a way for users (properly trained) to indicate that they experience trouble while they use MeetingPlace. Talk to the user to find out why they pressed this keycode.

0xb0135 ACTI %d, module %d is up (PSTN)

Definition

One of the modules on an Audiocodes board has come up. The module has been configured for PSTN operations. There are up to two of these messages for a TP1610 (two modules per board) and one of these messages for a TP1610-ultralite.

Resolution

There is nothing that needs to be done. However, if a system is configured to have a certain Audiocodes board perform PSTN operations and this message is not received, there is a system configuration problem. In this case, contact Cisco Technical Support for how to resolve this issue.

0xb0155 ACTI %d, physical link %d is up (IP)

Definition

One of the modules on an Audiocodes board detects Ethernet carrier. The module has been configured for VoIP operations. There are up to two of these messages for a TP1610 (two modules per board) and one of these messages for a TP1610-ultralite.

Resolution

There is nothing that needs to be done. However, if a system is configured to have a certain Audiocodes board perform VoIP operations and this message is not received, there is either a system configuration problem or the Ethernet is down. In this case, contact Cisco Technical Support for how to resolve this issue.

0xb0157 ACTI card %d present, but not used

Definition

There is an Audiocodes board present in the system (and powered up) that is not used for anything.

Resolution

There is nothing to do if the board is supposed to be installed but not otherwise used. However, if the system is configured to use this board, check the blade command for a misconfiguration.

0xb0158 Courtesy downing MSC %d

Definition

A user has downed an MSC device so that it no longer supports conferencing.

Resolution

This is generally done on purpose by a technician in preparation for a hotswap replacement of the SmartBlade that contains the MSC. This is perfectly normal if it is done intentionally by the technician. Otherwise, this can indicate that the MSC is downed by mistake. In this case the technician needs to bring the MSC back up.

0xb0159 Courtesy downing PRC %d

Definition

A user has downed a PRC device so that it no longer supports individual phone calls.

Resolution

This is generally done on purpose by a technician in preparation for a hotswap replacement of the SmartBlade that contains the PRC. This is perfectly normal if it is done intentionally by the technician. Otherwise, this can indicate that the PRC is downed by mistake. In this case the technician needs to bring the PRC back up.

0x100012 File system capacities are OK

Definition

The Lynx file system has enough free space for normal MeetingPlace operation.

Resolution

There is nothing that needs to be done.

0x100015 DB backup to gateway completed OK to unit %d

Definition

The database is backed up to the BackupGateway OK.

Resolution

There is nothing that needs to be done.

0x120b00 MPBackup (Unit %d) OK

Definition

The MeetingPlace backup operation is completed OK.

Resolution

There is nothing that needs to be done.

0x120b01 MPBackup (Unit %d) Starting

Definition

The MeetingPlace backup operation starts.

Resolution

There is nothing that needs to be done.

0x120b04 MPBackup (Unit %d) Shutdown

Definition

This unit is shutdown.

Resolution

Verify that the unit operates. If necessary, restart the unit. If the unit is shutdown intentionally, ignore this error.

0x120b05 MPBackup (Unit %d) Status is Unknown

Definition

A backup gateway is configured but currently it does not run. This can happen if the backup gateway PC is shutdown or disconnected.

Resolution

Verify that the unit operates. If necessary, restart the unit. If the unit has been shutdown intentionally ignore this error.

0x17000e (EX_AC_SPN_NETREF_CHG) Span netref change: span = %d, enable(1)? = %d, bd id = %d"

Definition

To be determined.

Resolution:

None.

0x170040 RTP stream re-established, bd/mod = (%d/%d), chan hndl = %d, sysport = %d

Definition

The VoIP RTP stream connected to the indicated sysport (system absolute port number) that was lost has been restored. See Warning 0x17003F for more information. For additional background information, the bd (Multi-Access board number), mod (module on board), and chan hndl (channel handle relative to the board module) are also provided.

Resolution

There is nothing that needs to be done. However, constant RTP stream loses and restores indicate an intermittent problem in the network that is on in MeetingPlace that needs to be addressed.

0x170041 RTP stream re-established on sysport %d after %d seconds

Definition

See Info 0x170040. This to inform the user on the duration of the RTP stream outage.

Resolution:

There is nothing that needs to be done. However, as mentioned for Info 0x170040, constant RTP stream loses and restores indicate an intermittent problem in the network that is on in MeetingPlace that needs to be addressed.

Related Information

Updated: Jan 31, 2006
Document ID: 50866