Cisco ICM custom server error messages

This section lists the Cisco ICM custom server error messages and their possible causes.

Table 1 shows the possible error messages that can be produced by the Cisco ICM custom server. It also describes some of the conditions or causes that might produce these messages. These messages are logged in the Blueworx Voice Response errorlog.

Table 1. Cisco ICM custom server error messages
Error number	Severity of alarm	Brief description	Detailed description	Possible causes
20504	Red	ERROR: <service definition file> has been deleted.	Indicates that the service definition file has been removed.	A user has moved or deleted the service definition file.
20504	Red	Cisco ICM custom server ended.	Indicates that the custom server has ended.	The custom server might have been ended manually or abnormally. The custom server must be restarted.
20504	Red	Waited <number> seconds for connection to ICR	The custom server is awaiting connection from ICM.	Ensure that ICM is fully functioning and configured correctly for this IVR.
20504	Red	ERROR: Reading Sockets Process Queue - return code <return code>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Contact IBM Support for assistance in resolving.
20504	Red	ERROR: ICR Close Request received - Status <status number>, Text ><text string><.	ICM has requested that the connection be closed	ICM is shutting down.
20504	Red	ERROR: Unable to get number of available channels.	The custom server failed in an attempt to retrieve channel status information from Blueworx Voice Response.	The communication with Blueworx Voice Response has been broken. Possibly Blueworx Voice Response terminated unexpectedly. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Unable to get state of channels	The custom server failed in an attempt to retrieve channel status information from Blueworx Voice Response.	The communication between Blueworx Voice Response has been broken. Possibly Blueworx Voice Response terminated unexpectedly. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: No entry in Trunk Status Table for CallID <Call ID number>	A CallID cannot be associated with the requested function or message.	Ensure application flow is correct such that call ids are associated with a call prior to messages being exchanged with ICM.
20504	Red	ERROR: Invalid Service Definition file. See Yellow Warnings	The service definition file is invalid.	Correct the syntax errors within the service definition file.
20504	Red	ERROR: Unable to determine status of channels.	The custom server failed in an attempt to retrieve channel status information from Blueworx Voice Response.	The communication between Blueworx Voice Response has been broken. Possibly Blueworx Voice Response terminated unexpectedly. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Reading VRU Monitor Process Queue - return code <return code>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	ERROR: Creating socket, errno <error number>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Getting Host address for <hostname>.	An AIX error occurred while trying to resolve the hostname.	Ensure that the host name can be correctly resolved on the command line and retry. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Getting Port number for Service <service name>	An error occurred attaching to a port for the specified service.	Ensure that the port is not in use by another process and retry.
20504	Red	ERROR: Binding to socket. <Error string> errno X.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Waited <number> seconds for Socket connection to complete.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Listening to socket, errno <error number>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	Failed to accept socket after <number> attempts, errno <error number>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Contact IBM Support for assistance in resolving. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Writing to socket. <socket name>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	Attempting to read <number> bytes from socket, maximum temporary buffer <number>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Reading from socket. <socket name>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	Message too long: length asked for <number>, length received <number>, maximum length <number>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: CA_Execute_State _Table failed-rc <return code>, CA_errno <error number>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Failed to create Queue <number> using <path name>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Failed to flush Queue <number>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Queue Key is invalid for Queue <queue name>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Contact IBM Support for assistance in resolving.
20504	Red	ERROR: Failed to get access to Queue <number> using <queue name>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Enqueuing a message - rc <return code>, errno <error number>.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Flush Queue failed.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Poll was interrupted: CA_errno=<error number> ;errno=<error number.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	ERROR: In CA_Poll, CA_errno=<error number>;errno=<error number>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Contact IBM Support for assistance in resolving.
20504	Red	ERROR: Unable to allocate memory for service data, errno = <error number>.	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Only <number> entries allowed in Service Definition table.	The service definition file is invalid.	The service definition file is invalid and should be modified appropriately.
20504	Red	ERROR: errno <error number> in stat for <service definition file>.	The service definition file has been deleted, locked or corrupted.	Ensure that a valid service definition file exists and retry.
20504	Red	ERROR: closing Service Definition File rc=<return code>	The service definition file has been deleted, locked or corrupted.	Ensure that a valid service definition file exists and retry.
20504	Red	ERROR: Invalid MessageType (SCI) of <message type>.	A message has been received which cannot be handled by the custom server. The message will be discarded.	Verify the application design on both the IVR and ICM. If the problem continues, contact IBM support for assistance in resolving.
20504	Red	ERROR: Invalid MessageType of <message type>.	A message has been received which cannot be handled by the custom server. The message will be discarded.	Verify the application design on both the IVR and ICM. If the problem continues, contact IBM support for assistance in resolving.
20504	Red	Unable to Unlock shared memory, reason: <error string>	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	Lock semaphore non-zero!!	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	Unable to Lock shared memory, reason: <error string>	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	Lock semaphore >1!!	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Cannot open shared resource file - <resource file>	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: creating global shared memory segment	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	Multiple instances were configured, but no parameter definition file was specified.	The custom server parameters are incorrect.	Ensure that the custom server parameters are configured correctly.
20504	Red	ERROR: Must select at least one: -K (EDFI) or -U (SCI).	The custom server parameters are incorrect.	Ensure that the custom server parameters are configured correctly.
20504	Red	ERROR: Failed to create queues with rc = <return code>, path = <path name>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Unable to attach to DirectTalk, CA_errno=<error number>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Ensure WVR is running. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Failed to attach shared memory.	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Failed to create semaphore with rc = <return code>.	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Failed to allocate shared memory with rc = <return code>. Queue_Path [<queue name>]	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	No pipe to custom server process for instance number <instance number>	An internal inter-process communication error has occurred.	Ensure that the custom server parameters are correct. If running in a multi-instance environment ensure that the Set_Instance_Number function has been correctly invoked. If application error is ruled out then it is possible that an internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	Write() for instance number <instance number>failed, errno <error number>(<error string>)	An internal inter-process communication error has occurred.	Ensure that the custom server parameters are correct. If running in a multi-instance environment ensure that the Set_Instance_Number function has been correctly invoked. If application error is ruled out then it is possible that an internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	Write() for instance number <instance number> failed .	An internal inter-process communication error has occurred.	Ensure that the custom server parameters are correct. If running in a multi-instance environment ensure that the Set_Instance_Number function has been correctly invoked. If application error is ruled out then it is possible that an internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	ECC Tag array database full	An internal memory error has occurred.	An internal memory handle has become corrupt, a process has terminated or an AIX error has occurred. Contact IBM Support for assistance in resolving.
20504	Red	ERROR: No entry in Call Table for CallID <Callid>.	A CallID cannot be associated with the requested function or message.	Ensure application flow is correct such that call ids are associated with a call prior to messages being exchanged with ICM.
20504	Red	ERROR: Unknown Message(<message id>) read by Call Process	A message has been received which cannot be handled by the custom server. The message will be discarded.	Verify the application design on both the IVR and ICM. If the problem continues, contact IBM support for assistance in resolving.
20504	Red	ERROR: Reading Call Process Queue - return code <return code>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20504	Red	ERROR: Processing Message - return code <return code>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	ERROR: Call Process terminating - Operational Status = <return code>	Either the custom server is terminating or an internal inter-process communication error has occurred.	An internal communication handle may have become corrupt, a process has terminated or an AIX error has occurred. Contact IBM Support for assistance in resolving.
20504	Red	ERROR: Poll was interrupted: errno=<error number>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	ERROR: In poll, errno=<error number>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20504	Red	Activity was detected, but could not be allocated to a process. Contact IBM Support for further information.	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Contact IBM Support for assistance in resolving.
20504	Red	read() failed, errno <error number>(<error string>) - closing child process for link_id <link id>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading System restart at the end of this table.
20503	Yellow	ERROR: Unknown Function ID - <function id>. The message will be discarded.	A message was received from a state table for a function id which cannot be processed by the custom server.	Verify the application design. If the problem continues, contact IBM support for assistance in resolving.
20503	Yellow	An invalid number of instances was specified, defaulting to 1	The custom server parameters are incorrect.	Ensure that the custom server parameters are configured correctly.
20503	Yellow	ERROR: Invalid parameter(s) - Child instance <instance number> terminating	The custom server parameters are incorrect.	Ensure that the custom server parameters are configured correctly.
20503	Yellow	WARNING: -B parameter was not specified. Defaulting Dialogue ID to <number>	The custom server parameters are incorrect.	Ensure that the custom server parameters are configured correctly.
20503	Yellow	WARNING: -B<start integer> was not in the required range. Defaulting Dialogue ID to <number>	The custom server parameters are incorrect.	Ensure that the custom server parameters are configured correctly.
20503	Yellow	ERROR: CallID <call id number> on TrunkGp <trunk group number>Trunk <trunk number> not cleared.	Indicates that a CallID associated with a particular trunk group and trunk was not release when the call ended.	The state table has failed to identify a call event that caused the call to end. The state table must be changed to ensure that its error handling capabilities handle this call condition. This error is not critical to applications.
20503	Yellow	Service Name '<service name>' is a duplicate.	Indicates that two service names in the service definition file are identical.	A user has modified the service definition file incorrectly while the custom server was running.
20503	Yellow	ERROR: From poll in test_socket, errno = <error number>	An internal inter-process communication error has occurred.	An internal communication handle has become corrupt, a process has terminated or an AIX error has occurred. Follow the instructions under the heading Custom server restart at the end of this table.
20503	Yellow	ERROR: No service is available.	Indicates that no services are available in the service definition file.	A user has modified the service definition file to indicate that no services are available on this VRU.
20503	Yellow	ERROR: The latest version of the service definition file has not been loaded.	Indicates that the service definition file is not valid and will not be uploaded to the ICM.	A user has modified the service definition file incorrectly while custom server was running.
20503	Yellow	Service ID “<number>” is a duplicate.	Indicates that two ServiceIDs in the service definition file are identical.	A user has modified the service definition file incorrectly while the custom server was running.
20503	Yellow	State table “<state table name>” is a duplicate.	Indicates that two state table names in the service definition file are identical.	A user has modified the service definition file incorrectly while the custom server was running.
20503	Yellow	Cisco ICM custom server: No channels are in service.	Indicates that no channels on the VRU are in service.	The Blueworx Voice Response system has just initialized with no channels in service, or a user has quiesced or disabled the channels.
20503	Yellow	ERROR: CallID <CallID> on TrunkGp <TrunkGp> Trunk <Trunk> not cleared by previous call instance.	Indicates that a CallID associated with a particular trunk group and trunk was not release when the call ended.	The state table has failed to identify a call event that caused the call to end. The state table must be changed to ensure that its error handling capabilities handle this call condition. This error is not critical to applications.
20502	Green	INFO: ICR re-connection #<connection number> completed.	Connection with ICM has been reestablished after an outage.
20502	Green	Cisco ICM custom server: No channels are in service, problem has CLEARED.	Indicates that the above error condition has cleared.	n/a
20502	Green	Cisco ICM custom server: Loaded and Initializing ICM/PG Session.	Indicates that the custom server has initialized.	n/a
System restart: Restart Blueworx Voice Response. If this fails to resolve the problem, proceed to step 2. Restart the pSeries computer. If this fails to resolve the problem, contact IBM support for assistance Custom server restart: Restart the Cisco ICM custom server. If this fails to resolve the problem, contact IBM support for assistance