ASAI and Call Control
■Outgoing calls barred (CS0/52)
The requested Third Party Make Call is being attempted over a trunk that has been restricted from use by the originator.
■Invalid Information Element contents (CS0/100)
The call_id specified by the Third Party Take Control capability is beyond the maximum allowable call_id value. For example, you could get this cause value if the ECS received a User to User Information (UUI) Information Element longer than 32 bytes in an ASAI message or one that did not include the header.
■Message not compatible with call state (CS0/98) The message is not compatible with the CRV state.
■Service or option not subscribed/provisioned (CS0/50)
If an adjunct includes
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 is inconsistent.
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,
Considerations
The ECS allows only one adjunct to control a call. Additional requests to control a call by other adjuncts are denied by the ECS.
When a multifunction station user is receiving a dial tone on a call appearance and the adjunct invokes a Third Party Make Call for that station, the ECS selects the same call appearance and call_id to establish the call.
The sum of the dest_addr and dest_route_select parameters can equal 32 digits.
