Destination address resolution failure Call setup timeout Internal Communication Error External communication Error Software Error Software Resources Unavailable Hardware Resources Unavailable Capability Exchange Failure QoS Error RTP/RTCP receive timer expired or bearer layer failure Signaling socket failure Gateway or signalling interface taken out of service User is denied access to this service Media Negotiation Failure due to non-existing Codec Gateway CCAPI No Memory Dynamically allocated memory on the gateway is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. No buffers Packet or buffer memory is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. CPU high Call rejected because default or configured CPU usage threshold has been exceeded. Low memory Call rejected because default or configured memory usage threshold has been exceeded. No dialpeer match No dialpeer satisfied the match criteria for accepting or handling the call. This usually indicates a dialpeer misconfiguration. No DSP resource Insufficient DSP resources to handle the call. Socket error An error occured on a socket interface. RTP Inactivity Error Media (RTP/RTCP) inactivity timer expired for the call. Invalid arguments Invalid arguments passed to a function. This usually indicates an internal software error. Invalid State Some unexpected event was received while in a state that was inappropriate for processing such an event. Timeout The software timed out waiting for some response or event to happen. Inter-process communication An internal process communication error occurred. This usually indicates some software error, but may also mean that some process was not running because of misconfiguration. Software Error An internal software error has occurred. Please report the entire IEC string, including the diagnostic code field, to customer support. Gateway or Interface OOS The Gateway is being taken out of service (forcefully or gracefully) or the signaling interfaces are being taken out of service (forcefully or gracefully). It may be possible that the signalling interface required to support the call has already been adminstratively shut down. Dial-peer connections exceeded An outbound dial-peer could not be used because the configured maximum number of connections for the dial-peer had been reached. Incompatible number type An outbound dial-peer could not be used because the configured numbering type did not match the type specified in the call. Trunk-group select fail Failed to select an available interface among the trunk group specified for use by a matching dial-peer. Caller-ID processing failure Error in processing caller ID information. Resource busy A resource needed to service the call was busy No application Could not find an application to take the incoming call. Please check your call application and dial-peer configurations. Application no longer exists The event points to a session application which does not exist any more. The event is being discarded. Incoming loop An incoming call setup indication was received, bearing the same GUID (globally unique identifier), as a call in existence. This call is being rejected because a loop is suspected. Call spike threshold An incoming call was rejected because we had exceeded configured call spike thresholds. Inbound dialpeer blocked A matched dialpeer could not be used to find an inbound application because the permission setting on it blocked its use as an inbound dialpeer. As a result, no application could be found to handle the call. Outbound dialpeer blocked A matched dialpeer could not be used to place the call because the configured permission on it contradicted its use as an outbound dialpeer. Handoff depth reached The maximum number of handoffs between applications for a single call has been exceeded. Please check your application scripts to make sure there isn't an infinite loop within the applications. Incompatible apps for handoff A call handoff attempt between applications failed because the applications were incompatible. IVR 1.0 applications are incompatible with IVR 2.0 or VXML applications. No dialpeer interface A matched dialpeer could not be used for the outbound leg because there was no appropriate interface for the dialpeer type. This may be a software or configuration error. The tag identifier for the problematic dialpeer is provided in the diagnostic field (the last component) of the 6-part IEC string. Please check your dialpeer configuration. System init error Some data structure or process that should have been created at system initialization is missing. Please report the Internal Error Code to customer support. TCL IVR No Memory Dynamically allocated memory on the gateway is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. No buffers Packet or buffer memory is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. CPU high Call rejected because default or configured CPU usage threshold has been exceeded. Low memory Call rejected because default or configured memory usage threshold has been exceeded. No dialpeer match No dialpeer satisfied the match criteria for accepting or handling the call. This usually indicates a dialpeer misconfiguration. No DSP resource Insufficient DSP resources to handle the call. Socket error An error occured on a socket interface. RTP Inactivity Error Media (RTP/RTCP) inactivity timer expired for the call. This is logged by the script when it specifies "media_inactivity_err" as the IEC to be used for the disconnect. Invalid arguments Invalid arguments passed to a function. This usually indicates an internal software error. Invalid State Some unexpected event was received while in a state that was inappropriate for processing such an event. Timeout The software timed out waiting for some response or event to happen. Inter-process communication An internal process communication error occurred. This usually indicates some software error, but may also mean that some process was not running because of misconfiguration. Software Error An internal software error has occurred. Please report the entire IEC string, including the diagnostic code field, to customer support. Gateway or Interface OOS The Gateway is being taken out of service (forcefully or gracefully) or the signaling interfaces are being taken out of service (forcefully or gracefully). It may be possible that the signalling interface required to support the call has already been adminstratively shut down. Script syntax An error was detected while parsing a tcl script. Please enable "debug voip ivr error" for more detailed information. Bad fsm event A tcl ivr script specified an unrecognized event in the definition of the fsm. Please enable "debug voip ivr error" for more detailed information Invalid args in script A tcl ivr script specified invalid arguments when invoking a tcl command procedure. Please enable "debug voip ivr error" for more detailed information Unsupported infotag A tcl script tried to access an unrecognized infotag, or it may have tried to use a recognized infotag in an unsupported mode (e.g. performing a "get" on a set-only infotag or vice-versa). Please enable "debug voip ivr error" for more detailed information. Invalid action in script A tcl script tried to execute an action or command which was invalid, or invalid given the state it was in. Please enable "debug voip ivr error" for more detailed information. Call blocked by CLI This call was rejected because it matched the profile defined for calls to be blocked. Settlement check failure An inbound call was rejected because it failed OSP settlement checking. This could have been because an OSP token was required and no valid one was found. Or it could have been because an OSP token was included in the SETUP indication when none was expected. vxmldialog failed Failed to initiate the vxml dialog. Turn on vxml debugging for more detailed information. Can't set up prompt A TCL script terminated execution on failure of the "media play" command because the prompt initialization failed. This could be due to a syntax error in the specification of prompt tokens or mis-configuration of language prompt-file locations. Please enable "debug voip ivr dynamic" and "debug voip ivr error" for more detailed information. Wrong state for media A tcl script requested a media operation (e.g. play, stop, seek) on one or more legs that were in a conferenced state, or where there was a vxml dialog active. Get infotag failed Tcl script terminated because an infotag retrieval failed. Please enable "debug voip ivr error" for more information. Set infotag failed Tcl script terminated because an infotag set operation failed. Please enable "debug voip ivr error" for more information. TCL script error An error was encountered while interpreting a TCL script. Please enable "debug voip ivr error" for more information. Bad callinfo params The application was unable to use one of the callinfo parameters for setup. Examples include the octet 3 or octet 3a fields, redirect IE, GUID, etc. Please enable "debug voip ivr error" for more information. Version mismatch The application could not run because it required an incompatible version of TCL IVR. Media request failed A TCL script terminated a call because an error status was reported by the media layer in the "ev_media_done" event. This indicates a failure in the execution of "media play" or some other media operation requested by the script. The script may choose to ignore the error, or it can opt to terminate the call, specifying this IEC ("media_done_err") as reason for the disconnect. Digit collect failed This error is logged by the TCL script when it fails to collect digits in response to a prompt and decides to terminate the call because of the failure. The failure may be normal, i.e. the caller did not enter any digits, or it may be due to an actual error in software or hardware. This IEC is logged by the script when it specifies "collectdigits_done_err" as the IEC associated with the disconnect. Accounting conn err This error code is set by the TCL script when it terminates the call because it has received an indication that the connectivity to the accounting server is lost. This IEC is logged when the script specifies "accounting_conn_err" as the IEC associated with the disconnect. Authentication err This error code is set by the TCL script when it terminates a call because of error status reported on a "ev_authenticate_done" event. The script logs this error by specifying "authenticate_done_err" as the IEC associated with the disconnect. Authorization err This error code is set by the TCL script when it terminates a call because of error status reported on a "ev_authorize_done" event. The script logs this error by specifying "authorize_done_err" as the IEC associated with the disconnect. APPLICATION FRAMEWORK No Memory Dynamically allocated memory on the gateway is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. No buffers Packet or buffer memory is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. CPU high Call rejected because default or configured CPU usage threshold has been exceeded. Low memory Call rejected because default or configured memory usage threshold has been exceeded. No dialpeer match No dialpeer satisfied the match criteria for accepting or handling the call. This usually indicates a dialpeer misconfiguration. No DSP resource Insufficient DSP resources to handle the call. Socket error An error occured on a socket interface. RTP Inactivity Error Media (RTP/RTCP) inactivity timer expired for the call. Invalid arguments Invalid arguments passed to a function. This usually indicates an internal software error. Invalid State Some unexpected event was received while in a state that was inappropriate for processing such an event. Timeout The software timed out waiting for some response or event to happen. Inter-process communication An internal process communication error occurred. This usually indicates some software error, but may also mean that some process was not running because of misconfiguration. Software Error An internal software error has occurred. Please report the entire IEC string, including the diagnostic code field, to customer support. Gateway or Interface OOS The Gateway is being taken out of service (forcefully or gracefully) or the signaling interfaces are being taken out of service (forcefully or gracefully). It may be possible that the signalling interface required to support the call has already been adminstratively shut down. Leg connections maxed The maximum number of connections for the leg has been exceeded. An attempt to bridge yet another connection on the leg failed. Handoff app not found The specified target application for a call handoff was not found on the gateway. Incompatible protocols A matched dialpeer could not be used for the outbound leg because this gateway is not capable of translating between the inbound and outbound protocols. OSP Fail OSP settlement checking failed for an outbound call. Dialpeer deleted A dialpeer that was being used for a call setup was deleted (through CLI) before the call could be initiated. Interface busy An outbound dial-peer matching this call's parameters specified an interface that was in use and unavailable. App can't handoff An application tried to place an outbound call using a dial-peer configured with an outbound application. However, the first application does not support call handoff, so cannot pass the call to the second application. Illegal "setup continue" A TCL script tried to issue a "leg setup continue" command when a previous "setup continue" was still outstanding. Call blocked by CLI This call was rejected because it matched the profile defined for calls to be blocked. SESSION APPLICATION No Memory Dynamically allocated memory on the gateway is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. No buffers Packet or buffer memory is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. CPU high Call rejected because default or configured CPU usage threshold has been exceeded. Low memory Call rejected because default or configured memory usage threshold has been exceeded. No dialpeer match No dialpeer satisfied the match criteria for accepting or handling the call. This usually indicates a dialpeer misconfiguration. No DSP resource Insufficient DSP resources to handle the call. Socket error An error occured on a socket interface. RTP Inactivity Error Media (RTP/RTCP) inactivity timer expired for the call. Invalid arguments Invalid arguments passed to a function. This usually indicates an internal software error. Invalid State Some unexpected event was received while in a state that was inappropriate for processing such an event. Timeout The software timed out waiting for some response or event to happen. Inter-process communication An internal process communication error occurred. This usually indicates some software error, but may also mean that some process was not running because of misconfiguration. Software Error An internal software error has occurred. Please report the entire IEC string, including the diagnostic code field, to customer support. Gateway or Interface OOS The Gateway is being taken out of service (forcefully or gracefully) or the signaling interfaces are being taken out of service (forcefully or gracefully). It may be possible that the signalling interface required to support the call has already been adminstratively shut down. Redirect loop detected A loop was detected while processing a redirected call. The new destination matches a previously-seen redirect address. OSP not supported Either an OSP token was detected in the SETUP message, or the dial-peer configuration specified that settlement is to be used for this call. However, the default or SESSION application configured to handle this call does not support the OSP protocol. Please check the dial-peer configuration and ensure that an OSP-capable application is defined. Call blocked by CLI This call was rejected because it matched the profile defined for incoming calls to be blocked. Interface busy An outbound dial-peer matching this call's parameters specified an interface that was in use and unavailable. No called number Either we timed out waiting for the user to enter digits for the called number, or an INFO message arrived with zero-length called number. Too many digits The user entered an excessive number of digits for the called number. Can't collect digits Digit collection is not supported on the interface or protocol that originated this call. Too many calls The number of calls serviced by this gateway has exceeded the total number permitted, as defined by the " call threshold global total-calls" CLI. Max redirects exceeded The maximum number of redirects (call forwarding) allowed for a call has been exceeded. H.323 No Memory Dynamically allocated memory on the gateway is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. No buffers Packet or buffer memory is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. CPU high Call rejected because default or configured CPU usage threshold has been exceeded. Low memory Call rejected because default or configured memory usage threshold has been exceeded. No dialpeer match No dialpeer satisfied the match criteria for accepting or handling the call. This usually indicates a dialpeer misconfiguration. No DSP resource Insufficient DSP resources to handle the call. Socket error An error occured on a socket interface. RTP Inactivity Error Media (RTP/RTCP) inactivity timer expired for the call. Invalid arguments Invalid arguments passed to a function. This usually indicates an internal software error. Invalid State Some unexpected event was received while in a state that was inappropriate for processing such an event. Timeout The software timed out waiting for some response or event to happen. Inter-process communication An internal process communication error occurred. This usually indicates some software error, but may also mean that some process was not running because of misconfiguration. Software Error An internal software error has occurred. Please report the entire IEC string, including the diagnostic code field, to customer support. Gateway or Interface OOS The Gateway is being taken out of service (forcefully or gracefully) or the signaling interfaces are being taken out of service (forcefully or gracefully). It may be possible that the signalling interface required to support the call has already been taken out. No Usr Responding, H225 timeout Timeout occurred waiting for the CallProc or Alerting messages, the calling party is given cause `No user responding', and called party is given cause code `Recovery on timer expiry' as per Q931 (section 5.2.5.4). No answer from user SETUP is sent and CallProc/Alert/Progress messages are already received and timeout occurred waiting for Connect message. H225 invalid msg The h225 message received with either an invalid CRV, parse error, mandatory IE missing, message out of sequence, wrong IE len or wrong IEC content. Setup no called no Received h225 setup message and mandatory field namely called number not present. H225 ASN error The h225 message receiver on parsing the h225 message found an ASN decode error. Setup, h225 state bad During sending of outgoing h225 setup message, found that the h225 state is wrong. Alert, h225 state bad During sending of outgoing alerting (h225) message found that the h225 state is wrong. Callproc, h225 state bad During sending of outgoing call proceeding (h225) message found that the h225 state is wrong. Progress, h225 state bad During sending of outgoing progress (h225) message found that the h225 state is wrong. Notify, h225 state bad During sending of outgoing notify (h225) message found that the h225 state is wrong. Info, h225 state bad During sending of outgoing info(h225) message found that the h225 state is wrong. UInfo, h225 state bad During sending of outgoing user info(h225) message found that the h225 state is wrong. Connect, h225 state bad During sending of outgoing setup confirm(h225) message found that the h225 state is wrong. Suspend, h225 state bad During sending of outgoing suspend(h225) message found that the h225 state is wrong. Suspend rej, state bad During sending of outgoing suspend reject(h225) message found that the h225 state is wrong. Resume, h225 state bad During sending of outgoing resume(h225) message found that the h225 state is wrong. Setup, DNS fail During originating call attempt, the DNS/Enum resolution fails. Setup no alternate During call setup attempt using an alternate endpoint it is found that there are no alternate endpoints to try. H225 chn, sock fail During h225 connection establishment, the chn connection failed due to TCP socket error. The session target in the dial-peer directly points to the remote voip endpoint. Alt h225 chn sock fail During h225 connection establishment, in a call attempt to an alternate endpoint, the chn connection failed due to TCP socket error. H225 chn, sock fail in RAS During h225 connection establishment (new connection), the chn connection failed due to TCP socket error. The dial-peer has session target of ras. H245, chn sock fail During h245 connection establishment, the chn connection failed due to TCP socket error. RSCMSM interface unavail RSCMSM CAC interface unavailable due to Resource failure. SETUP, next CRV invalid Received SETUP message at terminating endpoint, failure to get a valid unique CRV value. Setup, GW not registered If a new call is not allowed due to RAS not ready (i.e Gateway not Registered to Gatekeeper). TCS encode send Encoding and sending of terminal cap request failed. End session ack send Encoding and sending of end session ack pdu failed. End session send Encoding and sending of end session pdu failed. Userinput send Encoding and sending of user input signal pdu failed. Userinput upd send Encoding and sending of user input signal update pdu failed. Userinput alpha send Encoding and sending of user input alpha signal pdu failed. TCS ack fail In h245 capability state machine, failed to send TCS ack for the received TCS request. TCS rej send fail In h245 capability state machine, failed to send TCS reject for the received TCS request. TCS rel sent In h245 capability state machine, TCS request is received, received an internal event to send the TCS release request. TCS send fail (To be Removed) same as #46 In h245 capability state machine, failed to send the TCS request. H245 sock start fail H245 listening socket failed to start. Call entry no mem During outgoing call, resource failure for call entry data structure. Timeout h245 conn H245 connection wait timeout occcurred. MSD/MSD ACK Timeout Gateway has sent MSD request, but neither of the incoming MSD or MSD ACK message is received. MSD ACK timeout Gateway has sent MSD request, incoming MSD is received from remote and MSD ACK is sent to the remote in response. The expected MSD ACK message is not received from the remote. TCS ack wait timeout In the capability state machine, timer expiry waiting for the TCS ACK message. OLC m/c RSVP fail In olc state machine, received rsvp failure indication and minimum qos not best effort. RSVP fail treat abort Received RSVP failure and qos treatment is to abort the call. Fast QOS mismatch Received fast start Setup for QOS with remote minimum QOS as not best effort, but desired QOS is best effort. Slow QOS mismatch In H225 state machine, received a slow start h225 Setup, with no h245 address (in setup) and it is not 'sigonly' call and remote minimum QOS is not best effort. slow qos mismatch (To be removed) #65 same In h225 state machine, received h225 setup, h245 address not in setup and it is not sigonly call and min_qos!= best effort. H225, QOS release In H225 state machine, received QOS release event. fast, qos mismatch (To be Removed) Same as #64 Received fast start setup for qos and remote min_qos!=best effort and desired = best effort. The session target is RAS. Fallback chk fail In h225 state machine, fallback check failed. fback chk fail (To be Removed, same as #69) In h225 state machine, got admission confirm, fallback check failed. Fast codec mismatch In H225 state machine, received h225 fast Setup, during build of an OLC ACK found that there is no matching codec. Cap not supported In cap state machine, codec/capabilities received from the remote (in incoming TCS) are not supported. TCS rej received In cap state machine, after sending TCS request, received TCS Reject from remote. MS status indetermine In msd state machine, MSD request is received from remote, the result of Master Slave Status is indeterminate. This can happen if sent and received random numbers are same, when both the local and remote terminal types are same. MSD indetermine (To be removed) same as #74 In msd state machine, MSD request is received from remote, the result of MSDetermination is indeterminate, and max retries crossed. MSD rej received In msd state machine, MSD request is sent and MSD reject is received from the remote. The MSD requests shall be sent for fixed maximum number of retries before release. MSD rej received (To be Removed) same as #76 In msd state machine, MSD request is sent and msd reject is received from the remote. MSD rel received In msd state machine, MSD request is sent, receives MSD release release ind from the remote. MSD result disagreement In msd state machine, MSD ACK is received from remote but there is a disagreement in msd result. MSD rej received (To be removed) same as #76 In msd state machine, waiting for MSD ACK from remote, receives MSD reject from the remote. MSD rel received (To be Removed) same as #78 In msd state machine, waiting for MSD ACK from remote, receives MSD release ind from the remote. SETUP send sock failed An error occurred during SETUP PDU send operation on socket connection for H225. This can happen if remote IP is a reachable address (for ping), but it is not a valid H323 endpoint. OLC m/c, rcvd bw rej In olc state machine, bandwidth reject received. SETUP send resource fail During H225 PDU send operation, an error occurred in memory allocation or socket queue is full. ALERT send failed Encoding and sending of ALERT pdu failed. CallProc send failed Encoding and sending of Call Proceeding pdu failed. PROGRESS send failed Encoding and sending of PROGRESS pdu failed. NOTIFY send failed Encoding and sending of NOTIFY pdu failed. INFO send failed Encoding and sending of INFO pdu failed. USER INFO send failed Encoding and sending of USER INFO pdu failed. FACILITY send failed Encoding and sending of FACILITY pdu failed. SUSPEND send failed Encoding and sending of SUSPEND pdu failed. SUSPEND REJ send failed Encoding and sending of SUSPEND REJECT pdu failed. RESUME send failed Encoding and sending of RESUME pdu failed. PASSTHRU send failed Encoding and sending of PASSTHRU pdu failed. CONNECT send failed Encoding and sending of CONNECT pdu failed. H323 Interworking Error The h323 subsystem should always provide precise/exact IEC information depending upon the scenarios/place of an error. This IEC would indicate that the exact information of an error is not available. The debugs in h323 are to be looked by developer for pointing the exact issue. SIP No Memory Dynamically allocated memory on the gateway is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. No buffers Packet or buffer memory is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. CPU high Call rejected because default or configured CPU usage threshold has been exceeded. Low memory Call rejected because default or configured memory usage threshold has been exceeded. No dialpeer match No dialpeer satisfied the match criteria for accepting or handling the call. This usually indicates a dialpeer misconfiguration. No DSP resource Insufficient DSP resources to handle the call. Socket error An error occured on a socket interface. RTP Inactivity Error Media (RTP/RTCP) inactivity timer expired for the call. Invalid arguments Invalid arguments passed to a function. This usually indicates an internal software error. Invalid State Some unexpected event was received while in a state that was inappropriate for processing such an event. Timeout The software timed out waiting for some response or event to happen. Inter-process communication An internal process communication error occurred. This usually indicates some software error, but may also mean that some process was not running because of misconfiguration. Software Error An internal software error has occurred. Please report the entire IEC string, including the diagnostic code field, to customer support. Gateway or Interface OOS The Gateway is being taken out of service (forcefully or gracefully) or the signaling interfaces are being taken out of service (forcefully or gracefully). It may be possible that a signalling interface required to support the call has already been administratively shut down. 2xx, dest sdp null Sent invite, 2xx response received but destination SDP body unavailable. 2xx, dest sdp null (To be removed merged to #21) Sent invite, received 1xx, destination sdp body unavailable in the received 2xx response. ACK, dest sdp null ACK request received but destination SDP body unavailable for the delayed media call. 2xx, dest sdp null Mid call INVITE sent, 2xx response received but destination SDP body unavailable. Redirect contact null SIP Contact header missing in incoming SIP redirect (3xx) or 485 messages. refer-to header bad During call transfer with REFER, malformed or invalid Refer-To header. 18x, invalid disptype Invalid or unsupported Content-Disposition with mandatory handling received in 18x Session Progress message. Sent INVITE, bad msg Unknown SIP response message received while waiting response for INVITE. sent INVITE, bad msg (To be removed merged to #28) Unknown SIP response message received while waiting response for INVITE. Bad msg for state During outgoing resource resv state, unexpected SIP response message received for the current call state. bad msg for state (To be removed merged to #30) During outgoing resource resv allocated state, unexpected SIP response message received for the current call state. Session trgt null During outgoing call, session target found null. Session trgt parse During outgoing call, session target parse failed. Session trgt invalid During outgoing call, invalid session target type. DNS query fail For outgoing call, DNS lookup of session target failed. INVITE, dns qry fail Received failure response for the dns query (rcvd target addr null) sent for resolving the contact in the received INVITE/FQDN in SDP. INVITE, dns qry fail (To be removed merged to #36) Received failure response for the dns query (rcvd target addr null) sent for resolving the contact in the received INVITE/FQDN in SDP (after 180 ringing is sent) ACK, dns qry fail Received failure response for the dns query (rcvd target addr null) sent for resolving the contact in the received FQDN in SDP (after 200 ok is sent) MID-INVITE, dns qry fail Received failure response for the dns query (rcvd target addr null) sent for resolving the contact or SDP FQDN in the received mid INVITE request. 100, dns qry fail DNS lookup failure for the Contact header/FQDN received in SIP response message. DNS qry fail Received failure response for the dns query (rcvd target addr null) sent for resolving the contact, after QOS progress message has been sent. 3xx, redirect loop On receiving a 3xx response on an outbound call, during redirect procedure, it is found that redirect loop is encountered. 3xx, redirect max On receiving a 3xx response on an outbound call, during redirect procedure, it is found that maximum redirects are exceeded. 3xx, redirect exhaust On receiving a 3xx response on an outbound call, during redirect procedure, it is found that all contact choices are exhausted. 3xx, redirect exhaust (To be removed merged to #44) On receiving a 3xx response on an outbound call, during redirect procedure, it is found that all Contact choices are exhausted, while searching for SIP URL. Enum resolution fail Received failure response for the query sent for enum resolution. (rcvd contact list null). Contact not resolved The INVITE Contact or Record Route not resolved to an IP address & port. In the meantime either user has answered the call or loopback event is received from the session application. ACK send sock err The success response for INVITE send has been received, the socket is giving error for sending ACK. Connection to contact fail Sent INVITE and received 200 OK, TCP/UDP connection failed to the endpoint specified in the contact or record reoute. RSCMSM interface unavail RSCMSM CAC interface unavailable due to Resource failure. Socket conn refused The connection refused error occurred during send operation with error 146 Setup conn timeout Failed to receive response for the socket connection request. 1xx wait timeout If out of retries in sending invite while waiting for 1xx response, also not trying dns and there is no redirect info available. 200 wait timeout Retry exhausted for PRACK retransmission. 200 wait timeout Retry exhausted for COMET retranmission. PRACK wait timeout If out of retries in sending rel1xx messages waiting for the PRACK. PRACK wait timeout & state bad If trying to retransmit the rel1xx while waiting for PRACK message, but the state of the call is wrong. Session app rsp timeout Received INVITE request and timeout occurred while waiting for response for the sent SETUP from the session application. 1xx wait timeout If out of retries in sending mid-call INVITE waiting for 1xx response (and not trying dns). ACK wait timeout If out of retries in sending 200OK and waiting for ACK. ACK wait timeout If in active state, ACK is not received after it is out of retries for sending 200 OK for the initial INVITE. 200 wait timeout If out of retries in sending INVITE, waiting for the 200 OK. Xfer 2xx wait timeout For failed call transfer, timed-out waiting response for NOTIFY request. Send 200, rsrc fail Received INVITE request, resource error in sending 200 OK response. Send 200, rsrc fail Received PRACK message, resource error in sending 200 OK response. Send PRACK, rsrc fail Sending of PRACK message failed. Send COMET, rsrc fail Sending of COMET message fails during retransmission. Send 183, rsrc fail Sending of 183 (Progress) response message fails during transmission. Send 180, rsrc fail Sending of 180 response message fails during transmission. Rcvd 3xx, contact parse Internal error or Malformed Contact header encountered during SIP redirect (3xx) response processing. Rsrc process media Resource failure during processing of the media changes. Err launch dns Encountered a resource error in launching a DNS query. Err reinserting ccb Resource error in re-inserting the associated call control block into table. Call entry no mem During originating call resource failure in creating a call entry. Redirect info no mem Memory allocation failure for creating redirect info structure during SIP redirect (3xx) message processing. Setup, QOS mismatch During outgoing call, mismatch in QOS or invalid reliable-prov and QOS config. 1xx, QOS mismatch After 1xx Session progress receipt, QOS failure in negotiation while checking the configured req and acc QOS values with those in incoming message. RSVP failure outgoing Resource allocation failure at RSVP layer for outgoing call. QOS retries crossed Out of retries in sending QOS PROGRESS or resource reservation requests. 180, codec mismatch Media negotiation failure for incoming 180 Alerting responses. 183, codec mismatch Media negotiation failure for incoming 183 Session Progress responses. 200, codec mismatch Media negotiation failure for incoming 200 OK responses. RE-INVITE, codec mismatch A media information mismatch in the media information as received in Re-INVITE with the media information previously received in INVITE. ACK, codec mismatch During processing of the ACK message in response to 200 OK, the media negotiation failed due to codecs mismatch (in delayed media processing). 2xx, codec mismatch Sent mid invite, received 2xx response and the media negotiation failed due to codecs mismatch. INVITE, codec mismatch Media negotiation failure for incoming INVITE request. PRACK, codec mismatch Media negotiation failure for incoming PRACK message. RSVP failure incoming Resource allocation failure at RSVP layer for incoming call. INVITE, QOS mismatch During handling of INVITE, QOS failure in negotiation while checking the configured req and acc QOS values with those in incoming message. PRACK, QOS mismatch During handling of PRACK, QOS failure in negotiation while checking the configured req and acc QOS values with those in incoming message. COMET, QOS mismatch During handling of COMET, QOS failure in negotiation while checking the local QOS values with those in received a=qos:line in COMET. Fback chk fail Fallback check failed for IP network quality. This could happen either at Originating or Terminating Gateway. INVITE, invalid IE content Received INVITE with either invalid header contents, SDP or VIA params. INVITE, Preauth fail Received INVITE, pre authentication attempt failed. INVITE send fail A send operation for INVITE request failed. NOTIFY send fail A send operation for NOTIFY request failed. ACK send fail A send operation for ACK request failed. REFER send fail A send operation for REFER request failed. REFER response send fail A send operation for REFER response failed. Call Hold fail A Hold operation failed on an active call (during sending a re-invite to the peer). Connect wait timeout We received a 200 OK in response to an Invite and tried to request a UDP/TCP connection to the endpoint specified in the Contact or Record Route headers in order to send the ACK but timed out. Request, unknown method Received an incoming request message with unknown or invaild SIP method. Request, missing From/To Received an incoming request message, and it is found that mandatory fields 'From' and/or 'To' are missing or there is an error in parsing the From/To fields. Request, missing Via Received an incoming request message, and it is found that mandatory field 'Via' is missing. Request, parse Via Received an incoming request message, and encountered an error in parsing the 'Via' field. Request, missing CSeq Received an incoming request message, and it is found that mandatory field 'CSeq' is missing. Request, parse CSeq Received an incoming request message, and encountered an error in parsing the 'CSeq' field. Request, CallID unused Received an incoming request message with a CallID, which is not currently in use i.e mismatch in associating CallID with the current call control block. Request, missing Contact Received an incoming request message, and it is found that mandatory field 'Contact' is missing. Request, parse Contact Received an incoming request message, and encountered an error in parsing the 'Contact' field. Request, Version bad Received an incoming request message with a SIP version which is not supported on the User Agent. Request, Extension bad Received an incoming request message with a 'Require' header field containing an option tag with unsupported extension. Request, Record-Route bad Received an incoming request message with a 'Record-Route' header field in a malformed format. Request, Diversion bad Received an incoming request message with a Diversion header field in a malformed format. VTSP No Memory Dynamically allocated memory on the gateway is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. No buffers Packet or buffer memory is exhausted. This may indicate a temporary overload or a memory leak caused by faulty software. CPU high Call rejected because default or configured CPU usage threshold has been exceeded. Low memory Call rejected because default or configured memory usage threshold has been exceeded. No dialpeer match No dialpeer satisfied the match criteria for accepting or handling the call. This usually indicates a dialpeer misconfiguration. No DSP resource Insufficient DSP resources to handle the call. Socket error An error occured on a socket interface. RTP Inactivity Error Media (RTP/RTCP) inactivity timer expired for the call. Invalid arguments Invalid arguments passed to a function. This usually indicates an internal software error. Invalid State Some unexpected event was received while in a state that was inappropriate for processing such an event. Timeout The software timed out waiting for some response or event to happen. Inter-process communication An internal process communication error occurred. This usually indicates some software error, but may also mean that some process was not running because of misconfiguration. Software Error An internal software error has occurred. Please report the entire IEC string, including the diagnostic code field, to customer support. Gateway or Interface OOS The Gateway is being taken out of service (forcefully or gracefully) or the signaling interfaces are being taken out of service (forcefully or gracefully). It may be possible that the signalling interface required to support the call has already been adminstratively shut down. DSP mode change An attempt to change the DSP mode has been failed. DSP unknown failure An unspecified failure has happened in DSP interaction. No DSP memory available DSP could not allocate chunk memory, this may indicate a temporary overload or a memory leak caused by faulty software. No DSP resource available The call is disconnected because we are out of DSP resources. Bad DSP parameters The call has been disconnected because of some code error path. Codec incompatible The call has been failed because of the incompatible codec types. DSP alarm DSP sent an alarm which might be caused by receiving a bad packet, a wrong message or by a software problem. No voice cut through The call failed because the voice path could not be cut through. Tie line misconfiguration A tie line call has been failed because of a misconfiguration of the tie line in voice port. Please check the tie-line string. Invalid call mode An unknown call mode has been specified to setup a call. This usually indicates an internal software error. Interface deleted Failure to setup call on deleted interface. This may happen if a call comes on an interface while being hot-swapped. TDM hairpinning failed TDM hairpinning failed. This might be because of data structure allocation failure or because of actual hairpinnig failure. Set digit mode failed Attempt to set the DSP to the specific digit mode failed. This also can happen if we run out of memory. Setup indication failed This may happen if we run out of memory. DSP timeout Call failed because of time out on waiting for DSP action.