
ASAI and Domain Control
Denial (NAK) Causes
■Invalid association (CS0/81) — The association does not exist.
■Invalid number (CS0/28) — The specified call_id is within the allowable range but currently not active in the ECS.
■Mandatory IE missing (CS0/96) — A required parameter is missing in the request.
■Invalid IE contents (CS0/100) — The call_id is outside the allowable range for the DEFINITY ECS or the call option IE value is other than ‘Alert Order’ or ‘visibility’.
■No user responding (CS0/18) — The station to be added does not go
■Message not compatible with call state (CS0/98) — A
■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.
■Reorder/Denial (CS3/42). Maximum number of parties allowed on a call has been reached. Also sent, if a request is made to
■COR check fail (CS3/43) — The COR checks for the call and the added party fail.
■Bearer capability not available (CS0/58) — The call has conference restrictions due to
Protocol Error (NAK)Causes
The ECS issues the following cause for generating a protocol processing error:
■Protocol error (CS0/111)
The Q.932 protocol has been violated 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 DEFINITY Enterprise Communications Server CallVisor ASAI Protocol Reference,