Lucent Technologies 555-230-220 User Manual
ASAI and Call Control
4-58
Issue 7 May 1998
Denial (NAK) Causes
■
Invalid association (CS0/81) — The association does not exist.
■
Invalid number (CS0/28) — Called party number is not a station or an
AWOH extension. Also sent, if the specified called number is not an
administered extension in the DEFINITY ECS.
AWOH extension. Also sent, if the specified called number is not an
administered extension in the DEFINITY ECS.
■
Mandatory IE missing (CS0/96) — A required parameter is missing in the
request.
request.
■
Invalid IE contents (CS0/100) — The call option IE value is other than
“Alert Order” or “visibility”. Also, the call_id is outside the valid range.
“Alert Order” or “visibility”. Also, the call_id is outside the valid range.
■
No user responding (CS0/18) — The station to be added does not go
off-hook within 5 seconds or cannot be forced off-hook.
off-hook within 5 seconds or cannot be forced off-hook.
■
Message not compatible with call state (CS0/98) — A Single-Step
Conference request is received with “full visibility” option when the call is in
vector processing. This also happens if the call to which a party is to be
added, is not in the proper state (for example, parked), or receiving the dial
tone. Additionally, Single-Step Conference cannot be invoked, when the
call is in the process of being classified by the ECS.
Conference request is received with “full visibility” option when the call is in
vector processing. This also happens if the call to which a party is to be
added, is not in the proper state (for example, parked), or receiving the dial
tone. Additionally, Single-Step Conference cannot be invoked, when the
call is in the process of being classified by the ECS.
■
User busy (CS0/17) — The party to be added is busy on another call, has
dial tone or is in the process of dialing a call.
dial tone or is in the process of dialing a call.
■
Reorder/Denial (CS3/42) — Maximum number of parties allowed on a call
has been reached. Also sent, if a request is made to Single-Step
Conference to add a device onto a call and the device is already on the
call.
has been reached. Also sent, if a request is made to Single-Step
Conference to add a device onto a call and the device is already on the
call.
■
COR check fail (CS3/43) — The COR checks for the call and the added
party fail.
party fail.
■
Bearer capability not available (CS0/58) — The call has conference
restrictions due to data-related features, for example, data restriction, data
privacy, and manual exclusion.
restrictions due to data-related features, for example, data restriction, data
privacy, and manual exclusion.
Protocol Error (NAK) Causes
The DEFINITY ECS issues the following cause for generating a protocol
processing error:
processing error:
■
Protocol error (CS0/111)
The Q.932 protocol has been violated, or the release is prior to Release 6,
or the capability invoked is not consistent with this association, for
example, invoking the Third Party Make Call capability on a Domain
Control association.
The Q.932 protocol has been violated, or the release is prior to Release 6,
or the capability invoked is not consistent with this association, for
example, invoking the Third Party Make Call capability on a Domain
Control association.
NOTE:
For more information regarding protocol errors and a complete list of
reason codes (cause values), see the
reason codes (cause values), see the
DEFINITY Enterprise