You are here: CSP API Reference > 5 Response Status Values > Response Status Values
|
Hex ID |
Name |
Description as necessary |
|
00 00- |
These values differ depending on the message that returns them. |
|
|
00 10 |
Positive Acknowledgment (ACK)
|
The message was successfully processed, and any required actions were successfully completed. |
|
00 11 |
Bad Checksum
|
The message checksum does not match the checksum calculated by the system. An error must exist or a field must be missing. |
|
00 12 |
Invalid Logical Span ID
|
A field reserved for a logical span ID contains a number larger than the capacity of the switching matrix. |
|
00 13 |
Invalid Channel Number
|
A field reserved for a channel number is outside the range of 0–30 for E1 or 0–23 for T1. For E1, you can reference channel 30 only if the channel is configured for CCS, with the E1 Span Configure message. |
|
00 14 |
Message Invalid for Current Matrix State |
The CSP Matrix Series 3 Card is not in a state to accept this message. |
|
00 15 |
Negative Acknowledgment (NACK) |
Message could not be successfully processed.
The span in which a link is assigned, can have either CICs or not used at all. |
|
00 16 |
Invalid Address Range |
The address range specified in a block configuration message is |
|
00 17 |
Invalid Data Type |
Returned in response to a message with invalid data parameters. |
|
00 18 |
Invalid Channel B State
|
Channel B is in an invalid state for the action required. The More Status field indicates the state. NOTE: This does not pertain to ISDN B channels. |
|
00 19 |
Trunk Status Dead
|
One of the parties involved in a Call Processing message is associated with a dead line. |
|
00 1A |
Inseize Failure
|
Inseize could not be successfully completed |
|
00 1B |
Outseize Failure, No Acknowledgment
|
Outseize failed because acknowledgment signaling conditions were never met (for example, a channel of E&M wink start trunk did not receive a wink). |
|
00 1C |
Outseize Failure, Glare |
Outseize attempted on trunk involved in inseizure processing. |
|
00 1D |
Invalid Channel A State or Invalid PPL Event |
Channel A is in an invalid state for the action required. The Status field indicates the state of Channel A. A PPL component has received an invalid event for the current PPL state. |
|
00 1E |
Memory Allocation Failure |
Channel configuration change failed due to lack of available memory. |
|
00 1F |
Invalid Group Number |
Reserved for future use. |
|
00 20 |
Invalid Action Value |
Invalid decision parameter action value was received. |
|
00 21 |
Invalid Time |
The value entered for the time is not valid. |
|
00 22 |
First Outseize Instruction Not A Seize
|
The first instruction in an Outseize Control message must be a Seize if the channel is idle. |
|
00 23 |
Outseize "Seize" Instruction Not Allowed
|
This response is returned if one of the following occurs: An Outseize Instruction List Configure message is sent with a Seize instruction (a Seize instruction cannot be preprogrammed). An Outseize Control message with a Seize instruction is sent when one has been sent previously and the call is still active. |
|
00 24 |
Outseize Failed Due To No Answer |
Outseize failed due to no answer from the distant end. |
|
00 25 |
Invalid Encoding Format |
One of the following is invalid: the encoding format of RAN or the encoding format in a Conference Create message. |
|
00 26 |
Invalid Conference Size
|
Sent in response to a host-initiated Conference Create message, when the conference size indicated is less than 2 or greater than the maximum number of channels allowed to be conferenced together. |
|
00 27 |
DSP Not Configured for Requested Function |
No DSPs are configured for the function requested by the host (for example, configuration for service). |
|
00 28 |
DSP Resources Not Available
|
No DSP resources are currently available for the requested DSP function. Applies to DSP functions which are not managed as shared resources, for example, Conference Create. |
|
00 29 |
Invalid Conference Output Option
|
Conference output option indicated in the Conference Create message is not valid. |
|
00 2A |
Invalid Conference ID
|
Conference ID sent by the host is not associated with any conferences previously established through the Conference Create message.
or
The conference associated with this conference ID may have been marked for deletion. |
|
00 2B |
Conference Create Failure
|
Conference creation failed while the conference was establishing (for example, the MFDSP card was removed). |
|
00 2C |
Conference Establishing
|
Returned in a Delete Conference, Connect to Conference, or Connect 1-Way to Conference message if the conference associated with the conference ID is in the process of being created. |
|
00 2D |
Incompatible PCM Encoding for Conference
|
Returned in a Connect to Conference and Connect 1-Way to Conference message when the channel encoding format doesn’t match that of the conference (for example, A-law encoded channel connected to a µ-law encoded conference). |
|
00 2E |
Conference Size Exceeded
|
Returned in a Connect to Conference message when the conference size has been exceeded. |
|
00 2F |
Maximum Broadcast Number Exceeded
|
Returned in a Connect 1-Way or Connect 1-Way to Conference message when the number of 1-Way broadcasts exceeds the maximum allowed. |
|
00 30 |
DSP Resource Already Allocated
|
Returned in a Collect Digit String or DSP Service Request message if digit collection is already active on the specified channel. |
|
00 31 |
Channel Violation
|
Returned if an CSP 1000 Matrix Card card is being used in a system with more than 1,024 channels. |
|
00 32 |
Channels A and B Already Connected
|
A connect request has been sent for two channels which are already connected. |
|
00 33 |
SS7 Configuration Error |
Possible scenarios regarding virtual spans: 1. Configuring virtual CICs on remote nodes using an SS7 PQ card in the server node. 2. Configuring virtual CICs on a virtual VOCC card (type 0x80) using either an SS7 PQ card or an HP card. 3. Configuring virtual CICs beyond five virtual T-ONE cards or four virtual E-ONE cards on the server node using an SS7 PQ card. |
|
00 34 |
Ring Timeslot Inaccessible |
Remote timeslot is not accessible from this node. Check CSP hardware. |
|
00 35 |
Invalid Logical Ring ID |
|
|
00 36 |
Unassigned Ring |
|
|
00 37 |
Ring Already Assigned |
|
|
00 38 |
Invalid Ring State |
|
|
00 39 |
No Bandwidth Available |
|
|
00 3D |
Invalid ICB Data
|
An information control block has invalid length or count field, or the data within the ICB is invalid.
Invalid TLV Count Invalid TLV Length |
|
00 3E |
ISDN Congestion |
|
|
00 40 |
SRecord Invalid |
Download aborted due to invalid SRecord. |
|
00 41 |
Out of Sequence, Restart Download |
Restart download due to sequence problem. |
|
00 42 |
BRecord Invalid |
BRecord not accepted due to invalid value. |
|
00 43 |
Node Not Ready
|
A valid Logical Node ID has not been assigned (therefore, Polls cannot be requested) or the CSP is not in a valid state for the requested action (such as Download Begin during Boot State). |
|
00 44 |
No Download Begin Message Received
|
A Download SRecord or Download BRecord message was sent without a proceeding Download Begin SRecord or Download Begin BRecord message. |
|
00 45 |
Invalid Download
|
Sent in response to a Download Complete message when the download does not validate due to an incorrect checksum. |
|
00 47 |
Invalid Ring Loop Timing |
|
|
00 4B |
||
|
00 54 |
SS7 Invalid SCCP TCAP Parameter
|
An SS7 SCCP TCAP configuration attempt specified an invalid SS7 SCCP TCAP parameter. |
|
00 55 |
SS7 Invalid SCCP TCAP Configuration Parameter
|
An SS7 SCCP TCAP configuration attempt specified an invalid SS7 SCCP TCAP configuration parameter. A CSP returns this indication when a host queries for a configuration parameter using the message, SS7 SCCP/TCAP Query (0x78). |
|
00 56 |
System Busy Condition on Remote Node |
|
|
00 57 |
Conferencing Disabled |
|
|
00 58 |
Invalid Remote Timeslot for Connect 1-way Forced |
B address is not a valid remote timeslot. For SIP calls, B address is not bearer switched. |
|
00 59 |
Outseize Failure, Blocked |
|
|
00 5A |
DS3 Out of Service
|
An attempt is being made to bring one of the DS3’s spans in service but the DS3 is out of service |
|
00 5B |
DS3 Offset Out of Range |
DS3 Offset is outside the valid range 0-27 |
|
00 5C |
CIC Configure Attempted on Unconfigured Node |
CIC configuration was attempted for a node that is not configured. Possible causes: Configuring SS7 CICs on a fifth node (when using the SS7 PQ card) or the eight node (when using the SS7 Series 3 card). |
|
00 5D |
Invalid Data Value |
Invalid data or data out of range |
|
00 5E |
DS3 In Service |
An attempt is being made to loop back to a DS3, but the DS3 is in service |
|
00 5F |
Invalid Resource Attribute |
|
|
00 60 |
Outseize Failure, Guard Timing
|
Returned when the connection terminating party is in the guard state allowing for inseizures only. |
|
00 61 |
Invalid Slot |
The slot specified is not valid for the message sent. |
|
00 62 |
Invalid Span Offset
|
Field reserved for span offset is outside the valid range for the line card (0–1 for 2-span, 0–3 for 4-span, 0–7 for 8-span). |
|
00 63 |
Unassigned Span
|
The host has not yet assigned the specified Logical Span ID to a physical span. |
|
00 64 |
Unassigned Span A
|
The host has not yet assigned that span number to a hardware location. If two span/channels exist in message, the first span address is unassigned. |
|
00 65 |
Unassigned Span B
|
The host has not yet assigned that span number to a hardware location. If two span/channels exist in message, the second span address is unassigned. |
|
00 66 |
Outseize Failure, Busied Out |
Returned when connection terminating party is busied out. |
|
00 67 |
Channel B Out of Service |
Returned when connection terminating party is out of service due to a span alarm condition, is disabled, or both. Also returned if terminating party is going through error recovery or if no release of the distant end is detected. |
|
00 68 |
Channel B Not Idle
|
Returned when the connection terminating party is currently involved in call setup or teardown with another call. |
|
00 69 |
Span Already Assigned |
Span selected to be assigned is already assigned. |
|
00 6A |
Span Offset Not Available |
A span has been previously assigned to that slot and offset. |
|
00 6B |
Span Providing Loop Timing
|
Span selected to be unassigned has been selected as a loop timing source. |
|
00 6C |
Framing Error |
An incorrect framing type was specified. |
|
00 6D |
Zero Suppression Error |
An incorrect zero suppression type was specified. |
|
00 6E |
invalid Cable Length |
An invalid cable length was specified. |
|
00 6F |
Card Out of Service |
The card in the slot specified is not in service. |
|
00 70 |
Single Matrix Out of Service Attempt |
A single matrix cannot be taken out of service. |
|
00 71 |
Channel Out of Service |
One or more of the specified channels is out of service. |
|
00 72 |
Span In Service |
The span specified is in service. |
|
00 73 |
Span Out of Service |
The span specified is out of service. |
|
00 74 |
Invalid Card Type |
Incorrect card type for attempted operation. |
|
00 75 |
Invalid Entity |
The entity is out of range. |
|
00 76 |
DSP SIMM in Service |
The SIMM specified is in service. |
|
00 77 |
Invalid DSP SIMM Value |
The value specified for SIMM is invalid. |
|
00 78 |
Invalid DSP Function Type |
The type specified for SIMM is invalid. |
|
00 79 |
Invalid DSP SIMM Configuration |
The configuration specified for SIMM is invalid. |
|
00 7A |
Deletion of VRAS SIMM In Progress
|
An attempt has been made to download a recorded announcement to a SIMM while the SIMM is in the process of being deleted. |
|
00 7B |
Another Announcement Download is in Progress
|
An unsuccessful attempt has been made to download a recorded announcement while another recorded announcement download is in progress. |
|
00 7C |
No Recorded Announcement Download Initiate Message Received |
A Recorded Announcement Download message has been sent without a prior Recorded Announcement Download Initiate message sent. |
|
00 7D |
CCS Redundant I/O Card Not Available |
ISDN or SS7 card in a redundant system is missing or unavailable. |
|
00 7E |
RAN Download to Out of Service DSP
|
An attempt was made to download a recorded announcement to a DSP that is out of service. |
|
00 7F |
Software module still locked.
|
This value is returned when attempting to configure a locked module for which no product license has been downloaded. |
|
00 80 |
Partial Dial Condition |
The receive inter-digit timer has expired. |
|
00 81 |
Permanent Signal Condition |
The 1st receive digit timer has expired. |
|
00 82 |
Failure to Receive Wink 1 |
The maximum Receive Wink 1 detection timer has expired. |
|
00 83 |
Failure to Receive Wink 2 |
The maximum Receive Wink 2 detection timer has expired. |
|
00 84 |
Failure to Receive Wink 3 |
The maximum Receive Wink 3 detection timer has expired. |
|
00 85 |
Failure to Receive Wink 4 |
The maximum Receive Wink 4 detection timer has expired |
|
00 86 |
Failure to Receive Wink 5 |
The maximum Receive Wink 5 detection timer has expired. |
|
00 87 |
Failure to Receive Wink 6 |
The maximum Receive Wink 6 detection timer has expired |
|
00 88 |
Failure to Receive Wink 7 |
The maximum Receive Wink 7 detection timer has expired. |
|
00 89 |
Failure to Receive Wink 8 |
The maximum Receive Wink 8 detection timer has expired. |
|
00 8A |
No SIMM In Service For Requested Function |
There is no SIMM currently in service and configured for tone generation or VRAS. |
|
00 8B |
No Outpulsing Data Available |
Outpulse data is not available for the stage indicated. This response is also returned when connecting to an idle SS7 channel. |
|
00 8C |
No Action ICBs in Message |
An Outseize Control or Inseize Control message was sent without any action ICBs included. |
|
00 8D |
No Data ICBs in Message |
An Outseize Control message was sent without a required data ICB included. |
|
00 8E |
Wink Tolerance Exceeded |
Given incoming wink exceeded maximum allowed duration. |
|
00 8F |
Failure to Detect Off-hook |
An ANI request off-hook was not detected within the detection interval. |
|
00 90 |
Failure to Detect Dialtone |
Dialtone not detected within detection interval. |
|
00 91 |
Inpulsed Stage Not Collected |
Collection of given stage of incoming digits not indicated. |
|
00 92 |
Inpulsing Complete Timeout |
Time for complete incoming digit string collection for a given stage exceeded maximum time allowed. |
|
00 93 |
Invalid Inpulsed Source Span/Channel |
An invalid span/channel is indicated as the inpulsing channel. |
|
00 94 |
No Valid Inpulsed Data to Outpulse |
An Outpulse Stage N with Previously Inpulsed Digits instruction was initiated, however, the specified inpulsing has not occurred or has failed. |
|
00 96 |
Invalid Configuration Request for Span |
Specified configuration request for span is invalid. |
|
00 98 |
No ULC Module |
ULC module is missing. |
|
00 99 |
Invalid Configuration Request |
Configuration request is invalid. |
|
00 9A |
Invalid Command for Card Type, Span, or Channel |
Message does not apply to this card, span, or channel. |
|
00 9B |
Illegal D Channel Function |
For ISDN D channel call control administration only. |
|
00 9C |
Invalid ISDN D Channel |
ISDN PRI D channel is not valid. |
|
00 9D |
Invalid ISDN B Channel |
ISDN PRI B channel is not valid. |
|
00 9E |
Invalid ISDN Facility |
ISDN facility is invalid. |
|
00 9F |
Invalid Value for Entity |
The value specified for entity is invalid. |
|
00 A0 |
SIMM Not Present |
SIMM specified is not present. |
|
00 A1 |
D Channel Assigned |
A D channel is assigned on span ID selected. |
|
00 A2 |
Called Party Mandatory for ISDN Setup |
The called party digits are mandatory instruction elements over ISDN PRI. |
|
00 A3 |
Card Not Ready for Configuration |
The card is not in a valid state to accept configuration data. |
|
00 A4 |
ISDN D Channel Exceeds Maximum |
The ISDN card specified can not be configured for another D channel. |
|
00 A5 |
Invalid Option for Protocol |
Protocol assigned to channel in ranges does not allow for the function the host is trying to perform. |
|
00 A6 |
PPL Table Size Exceeds Max |
Size of table host wishes to download is too large. |
|
00 A7 |
PPL Table Already Exists |
Table ID already in use. |
|
00 A8 |
PPL Table Does Not Exist |
Table ID referenced does not yet exist. |
|
00 A9 |
PPL Table Does Not Validate |
The table the host has downloaded does not validate. Further information can be found in Byte and Entity fields of message responding to this error. |
|
00 AA |
Insufficient Hardware
|
The function the host is trying to perform can not be performed because the hardware needed is not present. |
|
00 AB |
PPL Table Part of Protocol
|
Error occurred trying to delete a Primitive Table or State/Event Table. The protocol that the table is associated with must be deleted first. |
|
00 AC |
Invalid Command for ISDN Facility |
The command for the ISDN facility was not valid. |
|
00 AD |
DSP Resource Inconsistency
|
Returned in a Collect Digit String or DSP Service Request message if digit collection is already active on the specified channel. Also returned when the host attempts to configure two transmitters on one card at the same time. |
|
00 AE |
Hardware Not Configured for DSP Function
|
The DSP resource management software has been requested to provide a DSP resource which does not exist. Please check DSP configurations of DSP card by sending a Card Status Query message. |
|
00 AF |
PPL Layer Forward Signal Timeout
|
Forward R2 Signal has not been detected within the maximum amount of time allowed. |
|
00 B0 |
PPL Layer Backward Signal Timeout
|
Backward R2 Signal has not been detected within the maximum amount of time allowed. |
|
00 B1 |
PPL Layer Premature Answer |
Answer was detected on an outgoing call before call setup completion. |
|
00 B2 |
PPL Layer Congestion Received |
Backward R2 Congestion Signal has been detected. |
|
00 B3 |
System Table in Use
|
System software is using the table you are trying to modify/create. Please wait a few seconds and try again. |
|
00 B4 |
Line Card Response To Matrix Timeout
|
The matrix timed-out waiting for a response from a line card. Check configuration for channel ranges that span more than two cards. |
|
00 B5 |
CPA Member Exceeds Maximum For Class
|
The maximum number of call progress analysis patterns which can be included in a class has been reached. |
|
00 B6 |
CPA Pattern Exceeds Maximum
|
The maximum amount of call progress analysis patterns supported by the system has been reached. |
|
00 B7 |
CPA Tone Group Exceeds Maximum
|
The maximum amount of call progress analysis tone groups supported by the system has been reached. |
|
00 B8 |
Invalid Pattern ID |
An invalid pattern ID has been specified for call progress analysis. |
|
00 B9 |
Invalid Interval Descriptor Count
|
An invalid interval descriptor count has been specified for call progress analysis. |
|
00 BA |
CPA Classes Exceeds Maximum
|
The maximum amount of call progress analysis classes supported by the system has been reached. |
|
00 BB |
Invalid CPA Class
|
An invalid call progress analysis class was specified in a configuration message. |
|
00 BC |
Invalid Data Found at Byte N
|
The message became invalid because of data found at byte offset N. See the LSB of the Status field of the message for the byte offset where data became invalid. |
|
00 BD |
Invalid Table Type |
The table type specified is invalid. |
|
00 BE |
Invalid Table ID |
The table ID specified is invalid. |
|
00 BF |
ISDN Response Wait Timeout
|
ISDN-initiated message timed-out; waiting for a response from the network (for example, Register with no Release Complete). |
|
00 C0 |
Action Denied |
Action request denied. |
|
00 C1 |
Action Rejected |
Action request rejected. |
|
00 C2 |
Slot Assigned As Standby |
The slot number is assigned as a standby slot. |
|
00 C3 |
Slot Not Assigned As Standby |
The slot number is not assigned as a standby slot. |
|
00 C4 |
Standby I/O Relay State Mismatch
|
The states of the relays of the I/O cards specified do not match (relays on one are enabled; relays on the other are disabled). |
|
00 C5 |
Incompatible Line Card Types |
The line cards specified are not compatible. |
|
00 C6 |
Redundant I/O Cards Not Present |
Redundant I/O cards are not present in one or more of the slots specified. |
|
00 C7 |
Line Card Switchover Already Completed |
The Line Card Switchover requested has already been completed. |
|
00 C8 |
Invalid SIMM Type |
Trying to perform VRAS functions on a non-VRAS SIMM. |
|
00 C9 |
Invalid Recorded Announcement ID
|
The recorded announcement ID is not in the allowable range or the host has requested a recorded announcement ID that does not exist in the system. Allowed Range MFDSP/DSP-ONE: 0 - 4,095 DSP Series 2: Not Applicable |
|
00 CA |
Recorded Announcement Already Exists
|
The host has attempted to download an announcement using a recorded announcement ID that is already stored in the system. |
|
00 CB |
Insufficient Memory on VRAS SIMM |
Not enough memory to store the specified recorded announcement. |
|
00 CC |
Maximum Recorded Announcement Limit Reached on VRAS SIMM |
The host has attempted to download more than the maximum allowed recorded announcements to a particular VRAS SIMM. MFDSP - 300 DSP-ONE - 2,048 DSP Series 2 - Does Not Apply |
|
00 CD |
Invalid IE Length |
The host has sent an information element (IE) in an ICB with an incorrect length. |
|
00 CE |
Invalid IE Count |
The host has sent an ICB with an incorrect IE Count value. |
|
00 CF |
Invalid Component Type |
The host has sent an ICB with an incorrect component type. |
|
00 D0 |
ISDN D Channel Switchover Timed Out |
The D channel switchover could not be completed due to timer expiration. |
|
00 D1 |
Invalid ISDN Connection Endpoint Identifier |
A valid Connection Endpoint Identifier could not be found for the addressed D channel. |
|
00 D2 |
Invalid AIB |
The address information block (AIB) is not in the proper format, or it addresses an invalid PPL state machine or channel. |
|
00 D3 |
Invalid Protocol ID |
A protocol ID specified in a PPL message is invalid. |
|
00 D5 |
Channel Already In Service |
Applies to ISDN and SS7 only. Indicates that you attempted to either assign or de-assign a protocol to a channel that is in service. |
|
00 D6 |
Invalid Command For Trunk Front End |
An invalid command was sent from the host for a trunk front end. |
|
00 D7 |
End Of PPL Audit Data
|
The end of the PPL auditing data has been reached. There are no more PPL auditing blocks in the PPL auditing logs. |
|
00 D8 |
Invalid SS7 Signaling Stack ID (0–3)
|
A signaling stack was specified that either: Was greater than the allowed values (0–3), or Did not match the signaling stack for the primary resource |
|
00 D9 |
SS7 Signaling Stack Already Configured
|
An attempt was made to configure an SS7 signaling stack that is already configured. |
|
00 DA |
Invalid SS7 Module Count
|
An attempt was made to configure an SS7 signaling stack with an invalid number of modules. The module count must be 3. |
|
00 DB |
Duplicated SS7 Module
|
An SS7 signaling stack configuration attempt specified the same SS7 model more than once. |
|
00 DC |
Unsupported SS7 Module Variant
|
An SS7 signaling stack configuration attempt specified an unsupported SS7 module variant. |
|
00 DE |
Invalid SS7 Module Type
|
An SS7 signaling stack configuration attempt specified an invalid SS7 module type. |
|
00 DF |
Invalid SS7 Signaling Stack Configuration |
An SS7 signaling stack configuration attempt could not be interpreted correctly. |
|
00 E0 |
SS7 Signaling Stack Not Configured
|
An SS7 signaling stack configuration attempt specified a signaling stack ID that is not configured. |
|
00 E1 |
Invalid SS7 Signaling Link ID
|
An invalid SS7 signaling link ID was specified that was either: Too large for the SS7 card model, or An attempt was made to de-configure a link that is not configured. |
|
00 E2 |
Invalid SS7 Signaling Link Set ID
|
An invalid SS7 signaling link set ID was specified. Valid Link Set IDs are 0 to 35. |
|
00 E3 |
SS7 Signaling Link Set Not Configured
|
An SS7 configuration attempt specified a signaling link set that is not configured. |
|
00 E4 |
SS7 Signaling Link Already Configured |
An SS7 configuration attempt expected the specified SS7 signaling link either: Was not configured, or Did not have configured SS7 signaling links |
|
00 E5 |
Invalid SS7 SLC
|
An SS7 configuration attempt specified an invalid SLC. Valid SLC codes are 0 to 15. |
|
00 E6 |
SS7 Signaling Link Set Already Configured
|
An SS7 configuration attempt expected either: The specified SS7 signaling set was not configured, or The specified SS7 signaling stack had no configured SS7 signaling link sets |
|
00 E7 |
SS7 APC Already Configured
|
An SS7 configuration attempt specified an adjacent point code (APC) that has already been associated with another link set. All links within a SS7 signaling stack that link to an adjacent signalling point must belong to a single link set. |
|
00 E8 |
Invalid SS7 Signaling Link Data Rate
|
An SS7 configuration attempt specified an invalid signaling link data rate. Valid data rates are 64 Kbps (0) and 56 Kbps (1). |
|
00 E9 |
SS7 SLC Already Configured
|
An SS7 configuration attempt specified an SLC that has already been assigned to another link within the same link set. |
|
00 EA |
|
An SS7 configuration attempt specified an invalid DCE-DTE configuration. |
|
00 EB |
SS7 Signaling Route Already Configured
|
One of the following is true: An SS7 signaling route configuration specified a route ID that already exists, or An SS7 signaling route configuration attempted to de-configure a destination for which CICs are still configured. An SS7 signaling linkset configuration attempted to de-configure a linkset for which routes are still configured. |
|
00 EC |
Invalid SS7 Signaling Route Mode Configuration
|
An SS7 Signaling Route Configure message failed due to one of the following: It specified a previously configured destination ID, but the specified stack ID or DPC did not match the previously configured destination ID. It used a destination ID that was not previously configured, but a previously configured destination ID for the signaling stack has a matching DPC. It reused the same link set to the same DPC (Route duplication)
An SS7 Signaling Route Query message failed due to one of the following: An invalid destination ID (valid IDs are 0 to 63) An invalid route ID (valid IDs are 0 to 254) Either the specified route ID or destination ID is not configured to the specified stack ID The specified destination ID and route ID are inconsistent |
|
00 ED |
No SS7 Signaling Route Entry Available
|
An SS7 Signaling Route Configure message was received and there were no unused route table entries. The CSP supports up to 20 routes per stack. |
|
00 EE |
SS7 Signaling Destination Not Configured
|
An SS7 configuration attempt specified a destination in the SS7 signaling stack that was not previously configured. |
|
00 EF |
No SS7 Signaling DPC Entry Available
|
An SS7 DPC-CIC Configure message was received specifying a DPC when no more DPC table space is available. The system allows for one DPC per span. If you try to configure more than 128 CIC groups on one system, you will get this message. |
|
00 F0 |
CCS Redundancy Already Configured
|
A CCS redundancy configuration attempt specified a primary and/or secondary slot that has previously been configured. |
|
00 F1 |
CCS Redundancy Not Configured
|
A CCS redundancy configuration or query message was received before a CCS Redundancy Configure message was received. |
|
00 F2 |
CCS Redundancy: Not A Primary Slot
|
The CCS Redundancy Configure message attempted to reference the secondary card in a CCS redundant pair. You must reference the primary card only. |
|
00 F3 |
Channel Already an SS7 CIC
|
An SS7 CIC Configure message was received that specified a CIC (or group thereof) that has been previously configured for the same channel. |
|
00 F4 |
Primary SS7 Slot Same As Secondary Slot
|
An CCS Redundancy Configure message was received specifying the same slot as the primary and secondary slot. |
|
00 F5 |
No SS7 Signaling Links Configured
|
An SS7 configuration attempt specified one of the following: An SS7 signaling link that is not configured An SS7 signaling link set that has no configured SS7 signaling links |
|
00 F6 |
No SS7 Signaling Routes Configured
|
An SS7 configuration attempt specified a destination ID or route ID that was not configured. |
|
00 F7 |
SS7 DPC-CIC Already Configured
|
An SS7 DPC-CIC Configure message was received that specified a DPC-CIC (or group thereof) that has been previously configured for the same signaling stack. |
|
00 F8 |
No SS7 Configuration Entity Available
|
An SS7 signaling route configuration attempt failed because it specified an entity (destination ID or route ID) that was not currently configured, but may have been configured previously. An SS7 DPC-CIC configuration attempt failed because no free DPC-CIC resources were available. |
|
00 F9 |
Invalid Number of SS7 ISUP Parameters
|
An SS7 ISUP Message Configure message was sent with an invalid number of parameters. |
|
00 FA |
Invalid SS7 ISUP Message Type
|
An SS7 ISUP Message Configure message was sent with an illegal Message Configuration Entry value. |
|
00 FB |
Node Already Exists
|
The Assign Logical Node ID message failed because node is already assigned. |
|
00 FC |
Invalid Node ID
|
A node ID is invalid because it met one of the following conditions: Specified node ID is greater than maximum value of 31 (0x1F). Specified node ID is greater than maximum value allowed when CSP conferencing is enabled. |
|
00 FD |
Node ID Not Configured
|
Assignment of spans failed because node is not yet assigned. When sending SS7 CIC Configure (0x6A) over CSP, this response value indicates the Ethernet is not available to the SS7 I/O card and you should check the connection. |
|
00 FE |
Maximum Number of Redundant Objects Reached |
|
|
11 11 |
Invalid Module |
Module specified is invalid (Valid range is 0x00 - 0x03) |
|
11 12 |
Module Not Present |
Module specified is not present |
|
11 13 |
Module Not Ready |
Module is not in a state to receive messages |
|
12 00 |
SIP Common Error |
|
|
12 01 |
Invalid IP Signaling Series 3 Card ID |
Invalid IP Signaling Series 3 Card ID used, or ID is out of the valid range |
|
User Not Found |
For SIP, used in Route Control and PPL Event Request messages. |
|
|
12 02 |
Invalid TLV tag |
|
|
12 03 |
MatrixInternal error |
|
|
Invalid PPL event |
For SIP, used in Route Control and PPL Event Request messages. |
|
|
12 04 |
Configuration Not Completed |
|
|
Invalid Data |
For SIP, used in Route Control and PPL Event Request messages. |
|
|
12 05 |
Invalid Query Type |
|
|
12 06 |
IP Signaling Series 3Card ID already configured |
|
|
12 07 |
Invalid Type |
|
|
12 08 |
Invalid State |
Trying to set an invalid service state or the Matrixis already in this state |
|
For SIP, used in Route Control and PPL Event Request messages. |
||
|
12 09 |
Invalid IPDC Usage option |
Trying to set an invalid IPDC usage or the option is out of range |
|
12 0A |
Invalid IP Signaling Series 3 Card interface support |
Trying to set an invalid IP Signaling Series 3 Card interface support |
|
12 0B |
Invalid Base Value |
Trying to set an invalid base value for channels and spans |
|
12 0C |
IP Signaling Series 3 Card ID not configured |
Response to Query |
|
12 0D |
IP Signaling Series 3 Card not in service |
Response to Query |
|
13 00 |
SIP Common Error |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 01 |
User Not Found |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 02 |
Invalid Call Handle |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 03 |
Invalid PPL Event |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 04 |
Invalid Data |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 05 |
Network Error |
Remote end rejected the message. For SIP, used in Route Control and PPL Event Request messages. |
|
13 06 |
Timer Expired |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 07 |
No more PPL state machines available |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 08 |
Invalid State |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 09 |
Invalid Time Slot |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 0A |
VDAC Rejected |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 0B |
Authentication Failed |
For SIP, used in Route Control and PPL Event Request messages. |
|
13 0C |
Call not in bearer free mode |
|
|
13 0D |
Invalid Action Value |
For SIP, used in Route Control and PPL Event Request messages. In PPL Event Request indicates the socket is not open so it cannot be closed. |
|
13 12 |
DNS Server Disabled (NACK)
|
All Route/Outseize Control API messages are nacked with this response if the outbound SIP call requires a DNS Server lookup and the DNS is disabled. |
|
14 01 |
Invalid Config Object Type |
|
|
14 02 |
Invalid or Out-of-Range Config Instance ID for the IP Signaling Series 3 Card |
|
|
14 03 |
Invalid Query Type |
|
|
14 04 |
Invalid TLV tag |
|
|
14 05 |
IP Signaling Series 3 Card Internal Error |
|
|
14 06 |
Invalid TLV value |
|
|
14 07 |
Invalid ICB |
|
|
14 08 |
Configuration was not completed |
|
|
14 09 |
IP Signaling Series 3 Card ID already created |
|
|
14 0A |
Invalid State
|
Trying to set an invalid service state |
|
14 0B |
CSP Matrix Series 3 Card ID already created |
|
|
14 0C |
Invalid CSP Matrix Series 3 Card ID |
|
|
14 0D |
Invalid Slot Number |
|
|
14 0E |
IP Signaling Series 3 Card is not configured |
|
|
15 01 |
Gateway mode not supported over ring |
Connecting gateway mode VoIP channel to B timeslot over ring is not supported |
|
17 01 |
Invalided DSP Number |
Used in messages Service State Configure, DSP SIMM Configure |
|
17 02 |
File ID Not Found |
Used in message DSP Cache Modify. |
|
17 03 |
No Active Playback/Record Session |
Used in messages Play File Modify, Play File Stop, Record File Modify, |
|
17 04 |
Playback/Record Session in Incorrect State |
Used in messages Play File Modify, Record File Modify |
|
17 05 |
Invalid File ID for Configuration |
Used in messages Play File Start, Record File Start |
|
17 07 |
No Resources Due to DSP Overload |
Used in messages Resource Create, Play File Start (to channel or conference), Record File Start (to channel or conference), Conference Create, DSP Service Request, Collect Digit String, Recorded Announcement Connect, Connect Tone Pattern, Outpulse Digits |
|
17 0A |
Unable to remove party from a conference |
Used in Resource Connect and Resource Disconnect messages |
|
17 0B |
Unable to add party to a conference |
Used in Resource Connect and Resource Disconnect messages. |
|
17 0C |
Channel not present in parent conference |
Used in Resource Connect message |
|
17 0D |
Channel not present in child conference |
Used in Resource Disconnect message |
|
17 0E |
Reached System Maximum Number of Conferences |
Used in Resource Create and Conference Create messages. |
|
17 11 |
Not supported in gateway mode |
Used in messages Connect to Conference, Resource Connect |
|
MSB 0x18 - Invalid B Channel State The LSB indicates the current call state. If the value is 0x1850 or above, it indicates the Layer 3 State. The Layer 3 state values depend on the signaling protocol. See the appropriate *.ppl file (CD ROM only) for Layer 3 state values, or contact Dialogic technical support.
If the value is lower than 0x1850, it indicates the Layer 4 State. The Layer 4 states are defined below. Some values are not backward-compatible with System Software versions earlier than 5.3. |
||
|
18 00 |
Out of Service |
|
|
18 01 |
Incoming Call |
|
|
18 02 |
Wait For CSA in Incoming Call State |
|
|
18 03 |
In Service Idle |
|
|
18 04 |
Incoming Call, Wait for Host Connect |
|
|
18 05 |
Outgoing Call, L3 Outseize Wait |
|
|
18 06 |
Wait For CSA in Incoming Call Wait for Host State |
|
|
18 07 |
Answered/Connected |
|
|
18 08 |
L4 Clear ACK Wait, L3 Disconnect Received |
|
|
18 09 |
L3 Clear Wait |
|
|
18 0A |
Busied out |
|
|
18 0B |
Outgoing Call Cut-thru |
|
|
18 0C |
Wait for CSA in Incoming Alerted State |
|
|
18 0D |
Wait for CSA in Incoming in Answered State |
|
|
18 0E |
Incoming Call Alerted |
|
|
18 0F |
L3 Clear Wait |
|
|
18 10 |
Wait for CSA in Outgoing Cut-thru |
|
|
18 11 |
Wait for CSA in Outgoing Alerted State |
|
|
18 12 |
L4 Clear ACK Wait, L3 Clear Received |
|
|
18 13 |
Outgoing Call Alerted |
|
|
18 14 |
L4 Clear ACK Wait, L5 Clear Received |
|
|
18 15 |
L5 Release Wait |
|
|
18 16 |
Incoming Call, L4 Clear ACK Wait (Park Processing) |
|
|
18 17 |
Incoming Call Alerted, L4 Clear ACK Wait (Park Processing) |
|
|
18 18 |
Answered, L4 Clear ACK Wait (Park Processing) |
|
|
18 19 |
Outgoing Alerted, L4 Clear ACK Wait (Park Processing) |
|
|
18 1A |
Outgoing Cut-thru, L4 Clear ACK Wait (Park Processing) |
|
|
18 1B |
Wait for CSA for Internal Routing |
|
|
MSB 0x1D - Invalid A Channel State The LSB indicates the current call state. If the value is 0x1D50 or above, it indicates the Layer 3 State. The Layer 3 state values depend on the signaling protocol. See the appropriate *.ppl file (CD ROM only) for Layer 3 state values, or contact Dialogic technical support.
If the value is lower than 0x1D50, it indicates the Layer 4 State. The Layer 4 states are defined below. Some values are not backward-compatible with System Software versions earlier than 5.3. |
||
|
1D 00 |
Out of Service |
|
|
1D 01 |
Incoming Call |
|
|
1D 02 |
Wait For CSA in Incoming Call State |
|
|
1D 03 |
In Service Idle |
|
|
1D 04 |
Incoming Call, Wait for Host Connect |
|
|
1D 05 |
Outgoing Call, Layer 3 Outseize Wait |
|
|
For PPL Event Request message (0x0044): Outseize Acknowledgment Network Wait |
||
|
1D 06 |
Wait For CSA in Incoming Call Wait for Host State |
|
|
1D 07 |
Answered/ Connected |
|
|
1D 08 |
L4 Clear ACK Wait, Layer 3 Disconnect Received |
|
|
For PPL Event Request message (0x0044): Layer 4 Release Wait |
||
|
1D 09 |
Layer 3 Clear Wait |
|
|
For PPL Event Request message (0x0044): Network Release Wait |
||
|
1D 0A |
Busied out |
|
|
1D 0B |
Outgoing Call Cut-thru |
|
|
For PPL Event Request message (0x0044): Externally Outseized |
||
|
1D 0C |
Wait for CSA in Incoming Alerted State |
|
|
For PPL Event Request message (0x0044): Hold Acknowledge Wait |
||
|
1D 0D |
Wait for CSA in Incoming in Answered State |
|
|
|
For PPL Event Request message (0x0044): Layer 3 Answer Wait |
|
|
1D 0E |
Incoming Call Alerted |
|
|
For PPL Event Request message (0x0044): Layer 4 Answer Wait |
||
|
1D 0F |
L3 Clear Wait |
|
|
1D 10 |
Wait for CSA in Outgoing Cut-thru |
|
|
For PPL Event Request message (0x0044): Layer 4 Recall Wait |
||
|
1D 11 |
Wait for CSA in Outgoing Alerted State |
|
|
For PPL Event Request message (0x0044): Purge Response Wait |
||
|
1D 12 |
L4 Clear ACK Wait, L3 Clear Received |
|
|
For PPL Event Request message (0x0044): Purge Wait |
||
|
1D 13 |
Outgoing Call Alerted |
|
|
For PPL Event Request message (0x0044): Park |
||
|
1D 14 |
L4 Clear ACK Wait, L5 Clear Received |
|
|
1D 15 |
L5 Release Wait |
|
|
1D 16 |
Incoming Call, L4 Clear ACK Wait (Park Processing) |
|
|
1D 17 |
Incoming Call Alerted, L4 Clear ACK Wait (Park Processing) |
|
|
1D 18 |
Answered, L4 Clear ACK Wait (Park Processing) |
|
|
1D 19 |
Outgoing Alerted, L4 Clear ACK Wait (Park Processing) |
|
|
1D 1A |
Outgoing Cut-thru, L4 Clear ACK Wait (Park Processing) |
|
|
1D 1B |
Wait for CSA for Internal Routing |
|
|
48 01 |
Invalid Number of TLVs |
The number of TLVs is out of range. |
|
48 02 |
Invalid Module Number |
The module number is invalid for the message sent. |
|
48 03 |
Invalid IP Address |
The IP address out of range or an invalid class. |
|
48 04 |
Invalid Subnet Mask |
The subnet mask is out of range or is invalid for the IP address. |
|
48 05 |
Duplicate IP Address |
The IP address is already assigned to another module number. |
|
48 06 |
Invalid TLV tag |
The TLV tag is out of range. |
|
48 07 |
Invalid Data Type |
The Data Type is out of range. |
|
48 08 |
Invalid TLV combination |
The combination of TLVs is invalid. |
|
48 09 |
Module Not Present |
|
|
48 11 |
Socket Incorporate Operation Error |
|
|
48 12 |
Invalid Parameter Length |
|
|
48 0A |
Invalid IMSG |
|
|
48 0B |
Motherboard IP Address Not Configured |
|
|
48 0C |
Invalid Ethernet Port |
|
|
48 0D |
Invalid TLV Value |
|
|
48 0F |
Socket bind to user error |
|
|
4D 01 |
Software key format not valid.
|
The first two bytes of the Product License field are not defined key types, or the product license contains invalid data. |
|
4D 02 |
Data decrypted not valid.
|
A serial number decrypted from a product license cannot be matched against an existing serial number on a CSP. |
|
4D 03 |
Product License - Insufficient Licensed Resources |
|
|
4D 3D |
Product License - Invalid ICB Data |
|
|
4D 74 |
Invalid Card Type. |
The line card that license was generated for does not support licensing |
|
4D AA |
Insufficient Hardware. |
Not enough room for the number of licensed spans on the chassis |
|
50 01 |
Response Timeout |
|
|
50 02 |
Null Buffer |
|
|
50 03 |
Queue Full |
|
|
50 04 |
Feature Disabled |
|
|
50 05 |
No ICBs |
|
|
50 06 |
Invalid ICB Type (Message Not Processed) |
|
|
50 07 |
Invalid ICB Type (Message Partially Processed) |
|
|
50 08 |
Invalid ICB Subtype (Message Not Processed) |
|
|
50 09 |
Invalid ICB Subtype (Message Partially Processed) |
|
|
50 0A |
Invalid Message (Message Not Processed) |
|
|
50 0B |
Invalid Message (Message Partially Processed) |
|
|
50 0C |
Unauthorized Command |
|
|
50 0D |
Incorrect ICB Data Length |
|
|
50 0E |
Host Not Connected |
|
|
50 0F |
Incorrect Host ID |
|
|
50 10 |
Reserved |
|
|
50 11 |
Maximum Number of Queries Exceeded |
|
|
50 12 |
Not used |
|
|
50 13 |
Not used |
|
|
50 14 |
Multi Host Download In Progress |
|
|
50 15 |
Multi Host Being Enabled, Wait 32 Sec |
|
|
In the SS7 CLLI Query message (0x00EB): The message could not be processed for either of the following reasons: - Stack ID and CIC Group mismatch - Internal error |
||
|
50 16 |
Odd ICB Data Count (Extended API) |
|
|
50 17 |
Non-Unique Host ID |
|
|
In the SS7 CLLI Query message (0x00EB): Invalid configuration data format, if the data format specified is not 0x01 (TLV format) |
||
|
50 18 |
Invalid ICB Subtype |
|
|
50 19 |
Host ID Assigned to Different Host |
|
|
50 1A |
Invalid ICB Data Entry |
|
|
50 47 |
Invalid Ring Loop Timing.
|
Trying to set a node to be master-configurable, but the ring timing has already been derived, or trying to set ring timing on a master node or master- configurable node, or trying to set secondary timing on the EXNET-ONE card. |
|
50 AA |
Insufficient Hardware.
|
This response status is returned when trying to initiate the Enhanced Fault Tolerance Ring Mode, but the EXNET-ONE and I/O are installed. (These EXNET® cards cannot be used in the Enhanced Fault Tolerance Ring Mode). |
|
50 C0 |
Action Denied.
|
A value of Action Denied (0xC0) is returned if the user is trying to set an EXNET-ONE card. |
|
50 75 |
Invalid TLV Tag. |
The TLV specified is not one of the 4 types allowed (Trunk Number, Local CLLI, Remote CLLI, Trunk Type) |
|
50 CD |
Invalid TLV Tag Length |
|
|
50 E0 |
SS7 Signaling Stack Not Configured |
|
|
50 F9 |
Invalid TLV Count. The TLV Count should be 0x04. |
|
|
51 00 |
ISUP Congestion |
Local or remote ISUP congestion scenario. Only priority calls will be allowed in congestion state. |
|
51 01 |
End of Route Table |
|
|
51 02 |
Retry Limit Exceeded |
|
|
51 03 |
Termination Error |
|
|
51 04 |
Purge |
|
|
51 05 |
No Destination Found |
|
|
51 06 |
Recursion |
|
|
51 07 |
ACK Wait Timer Expired |
|
|
51 08 |
No Common Resource Group Found |
|
|
51 0A |
Termination Validation Error |
|
|
51 0B |
Channel unavailable due to initialization or OOS |
|
|
51 0C |
End of Entry Data |
|
|
51 0D |
Invalid Routing Method |
|
|
51 0E |
Invalid Resource Group Table |
|
|
51 0F |
Invalid Route Table |
|
|
51 10 |
Reserved |
|
|
51 11 |
Invalid Resource Group |
|
|
51 12 |
Invalid Criteria |
|
|
51 13 |
Invalid Entry Data |
No available routes |
|
51 14 |
System Error |
|
|
51 15 |
Illegal Instruction |
|
|
51 1E |
V5 ID Invalid |
|
|
51 1F |
V5 User Port Invalid |
|
|
51 20 |
V5 User Port In Use |
|
|
51 21 |
V5 User Port Blocked |
|
|
51 22 |
V5 TS Alloc Failed |
|
|
51 23 |
V5 Timer Expiry |
|
|
51 24 |
V5 L3 Internal Error |
|
|
51 25 |
V5 Formie Invalid |
|
|
51 26 |
V5 Invalid Num of Formies |
|
|
51 28 |
V5 Unspecified |
|
|
51 29 |
V5 Access NW Fault |
|
|
51 2A |
V5 Access NW Blocked |
|
|
51 2B |
V5 Connection Present at PSTN up to a Diff V5TS |
|
|
51 2C |
V5 Connection Present at V5TS to a Diff ISDN UPTS |
|
|
51 2D |
V5 Connection Present at ISDN up to a Diff V5TS |
|
|
51 2F |
V5 Dealloc Cannot Comp Incompatiable Data |
|
|
51 30 |
V5 Dealloc Cannot Comp V5TS Data Incompatible |
|
|
51 31 |
V5 Dealloc Cannot Comp Port Data Incompatible |
|
|
51 32 |
V5 Dealloc Cannot Comp Upts Data Incompatible |
|
|
51 33 |
V5 User Port Not Provisioned |
|
|
51 34 |
V5 TS Invalid Identified |
|
|
51 35 |
V5 Link Invalid Identified |
|
|
51 37 |
V5 TS Used as Physical C Channel |
|
|
51 38 |
V5 Link Blocked |
|
|
51 8F |
Gatekeeper routed but no gatekeeper address |
|
|
51 90 |
H245 end session received |
|
|
51 91 |
RAS DRQ |
|
|
51 92 |
CALL PROCEEDING has protocol error |
|
|
51 93 |
H225 timer expired |
|
|
51 94 |
REL COMPLETE received |
|
|
51 95 |
Incoming H225 message has Q931 protocol error |
|
|
51 96 |
No Remote Alias Address or SRC IP/Port not Available |
|
|
51 97 |
H.323 Protocol Error (H.225, H.245, or RAS) |
|
|
51 98 |
H.225, H.245 Socket Open Fail |
|
|
51 99 |
Gatekeeper not Configured |
|
|
51 9A |
LRQ Failed |
|
|
51 9B |
ARQ Failed |
|
|
51 9C |
No Associated Timeslot |
|
|
51 9D |
DSP Resource Wait Timeout |
|
|
51 9E |
Invalid DSP Resource Request |
Resource already attached. |
|
51 20 |
V5 ID Invalid |
|
|
51 21 |
V5 User Port Invalid |
|
|
51 22 |
V5 User Port Blocked |
|
|
51 23 |
V5 Timer Expiry |
|
|
51 24 |
Unexpected Clearing Received |
|
|
51 25 |
Invalid V5 Formatted IEs |
|
|
51 26 |
Invalid Number of V5 Formatted IEs |
|
|
52 01 |
Signaling Route Test (SRT) failed. |
|
|
52 02 |
Signaling Route Test Acknowledgment (SRTA) has an improper pattern. |
|
|
52 03 |
The SRTA was received on the wrong SLC. (This error code not supported for DDI). |
|
|
52 04 |
Link congested |
|
|
52 05 |
Link out of service |
|
|
52 06 |
Link not equipped |
|
|
52 07 |
Request was terminated by the Host |
|
|
52 08 |
SRT is already running |
|
|
52 09 |
System error |
|
|
52 0A |
SRTC timed out |
|
|
52 0B |
Received valid SRTA in wrong Link ID (This error code not supported for DDI) |
|
|
52 0C |
Route not configured for this DPC |
|
|
52 81 |
Invalid module type for DPC/Stack/CIC combination. (Also used in the PPL Timer Configure message: 0x00CF) |
|
|
52 82 |
Message received for unassigned CIC. |
|
|
52 83 |
Only Extended API is supported for VCIC. |
|
|
If the MSB is 0x54, Error Detected in SCCP/TCAP, the LSB indicates the error as follows: |
||
|
54 00 |
Error Unknown |
|
|
54 01 |
Incorrect ICB |
The maximum number of ICBs for the TCAP primitive set is 16. |
|
54 02 |
Incorrect ICB Length or Parameter |
|
|
54 03 |
Incorrect or Missing Mandatory TCAP Parameters |
|
|
54 04 |
Incorrect or Missing Mandatory SCCP Parameter |
|
|
54 05 |
Invalid Primitive (Primitive Not Supported) |
|
|
54 06 |
Instance does not Exist |
|
|
54 07 |
Primitive Not Expected as this Time |
|
|
54 08 |
Mandatory Component Missing |
|
|
54 09 |
TCAP simultaneous active dialogue/transaction/operations reached the maximum limit. |
SS7 system busy condition (for CPU, memory or MCB). |
|
54 0A |
SSN is not Configured or not Active |
|
|
54 0B |
Maximum Length of TCAP Components for a Message Exceeded |
|
|
55 00 |
PPL Event Request: Error Unknown |
|
|
SCCPTCAP Configure: No More Status Info, or Status Unknown |
||
|
55 01 |
PPL Event Request: Invalid ICB or a Mandatory ICB is missing |
|
|
SCCPTCAP Configure: Invalid Config Type |
||
|
55 02 |
PPL Event Request: Incorrect ICB Length or Parameter |
|
|
SCCPTCAP Configure: Subsystem Configured |
||
|
55 03 |
PPL Event Request: Incorrect or Missing Mandatory TCAP Parameter |
|
|
SCCPTCAP Configure: Subsystem Not Configured |
||
|
55 04 |
PPL Event Request: Incorrect or Missing Mandatory SCCP Parameter |
|
|
SCCPTCAP Configure: Subsystem Allowed |
||
|
55 05 |
PPL Event Request: Invalid Primitive (Primitive Not Supported) |
|
|
SCCPTCAP Configure: Subsystem Not Allowed |
||
|
55 06 |
PPL Event Request: Instance does not Exist |
|
|
SCCPTCAP Configure: Invalid Option |
||
|
55 07 |
PPL Event Request: Primitive Not Expected at this Time |
|
|
SCCPTCAP Configure: Exceeds minimum number of hosts for a Subsystem |
||
|
55 08 |
PPL Event Request: Mandatory Component Missing |
|
|
SCCPTCAP Configure: Invalid Parameter |
||
|
55 09 |
PPL Event Request: Resource Limitation |
|
|
SCCPTCAP Configure: Invalid Parameter Length |
||
|
55 0A |
PPL Event Request: SSN is not Configured or not Active |
|
|
SCCPTCAP Configure: Parameter Configured |
||
|
55 0B |
PPL Event Request: Maximum Length of TCAP Components for a Message Exceeded |
|
|
SCCPTCAP Configure: Parameter Not Configured |
||
|
55 0C |
Invalid SCCP Upper Layer |
|
|
55 0D |
Maximum Active Subsystems Exceeded |
|
|
55 0E |
DPC Not Configured |
|
List