ASAI and Domain Control
result_call_ | [mandatory] The call_id after the call is merged (provided by |
id | the ECS) |
party_id | [mandatory] The list of party_ids for the merged call provided |
| by the ECS |
connected | [mandatory] The list of extensions for the parties on the call |
number |
|
old party_id | A list of party ids corresponding to the calls prior to the |
| conference. This report item is used in conjunction with the |
| party_id list to map the party ids prior to the conference to |
| the party ids after the conference. |
UCID | Starting with Release 6, UCID is included only if it exists in |
(Universal | the DEFINITY ECS and the “Send UCID to ASAI”1 field is |
Call ID) | administered to ‘y’. It is a unique tag assigned to each ECS |
| call. |
1.The field “Send UCID to ASAI” is administered on the
Denial (NAK) Causes
The ECS issues one of the following reasons as the cause for ending the association:
■Invalid number/domain (CS0/28)
The controlling party has not been specified correctly.
■Message not compatible with call state (CS0/98)
The common party is not in a valid state for the operation (merge) to take place. For example, the common party does not have one call active (talking) and one call in the held state.
■Invalid information element contents (CS0/100) The party_id value of the request is invalid.
■Mandatory information element missing (CS0/96)
■Resources not available (CS3/40)
The host attempted to add a seventh party to a call with six parties active (bridging and held cases only).
■Reorder/Denial (CS3/42)
Both calls are alerting, or both calls are being service observed, or an active call is in a vector processing stage.
Protocol Error (NAK) Causes
The ECS issues the following causes for returning a protocol processing error.
