ASAI and Domain Control
Third Party Selective Hold
The adjunct uses this capability to place a controlled extension on hold. The effect is as if the specified party depressed the hold button on his or her terminal to locally place the call on hold. For analog sets (phones) with only one call active, selective hold places the call on conference hold (the same as if the
Information Flow
The adjunct expects a response to its request.
The ECS either:
—Places the call on hold and sends the adjunct an acknowledgement, or
—Denies the request (see causes below)
Third Party Selective Hold Parameter
call_id | [mandatory] Identifies the call to be placed on hold |
ACK (Positive Acknowledgement) Parameters
No parameters are contained in the acknowledgement for this capability.
Denial (NAK) Causes
The ECS issues one of the following reasons as the cause for ending the association:
■Invalid association (CS0/81) The association does not exist.
■Invalid number/domain (CS0/28)
The number contained in the request is an invalid call_id value.
■Invalid state (CS0/98)
The call is not in the talking state in order to be put on hold.
■Mandatory IE missing (CS0/96)
The required call_id is missing in this request.
■Invalid information element contents (CS0/100)
The party_id or call_id value of the request is invalid (for example, the party is alerting).
■User Busy (CS0/17)
The user is busy with another ASAI request.
