Lucent Technologies Definity Enterprise Communications Server 555-230-220 ユーザーズマニュアル
ASAI and Call Control
4-44
Issue 7 May 1998
■
Invalid Information Element contents (CS0/100)
The party_id value of the request is invalid. For example, a Third Party
Selective Hold is sent for the destination of a ringing call (the call is ringing
and not yet answered at that endpoint). The party_id specified in the
party_id Information Element has not passed through the connected stage
and is therefore invalid.
The party_id value of the request is invalid. For example, a Third Party
Selective Hold is sent for the destination of a ringing call (the call is ringing
and not yet answered at that endpoint). The party_id specified in the
party_id Information Element has not passed through the connected stage
and is therefore invalid.
■
User busy (CS0/17)
The user is busy with another ASAI request.
The user is busy with another ASAI request.
■
Invalid call type (CS3/43)
The call cannot be held due to the type of call (for example, emergency,
wake-up, or service observed).
The call cannot be held due to the type of call (for example, emergency,
wake-up, or service observed).
Protocol Error (NAK) Cause
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.
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
reason codes (cause values), see the
DEFINITY Enterprise
Communications Server CallVisor ASAI Protocol Reference
,
555-230-221.
Considerations
The adjunct must know the party_id before placing the party on hold. A party may
only be put on hold if it is in on the call.
only be put on hold if it is in on the call.
After a party is placed on hold through a Third Party Hold request, the user does
not receive dial tone (regardless of the type of phone [set]). Thus, subsequent
calls must be placed by selecting an idle call appearance or through the Third
Party Make Call Request.
not receive dial tone (regardless of the type of phone [set]). Thus, subsequent
calls must be placed by selecting an idle call appearance or through the Third
Party Make Call Request.
Only station extensions support this capability; any requests containing party_ids
corresponding to a trunk will be denied.
corresponding to a trunk will be denied.
If the party is already on hold on the specified call when the ECS receives the
request, a positive ACK is returned.
request, a positive ACK is returned.
NOTE:
An analog set can be looked at as having two call appearances, CA1 and
CA2.
CA2.