ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
5. In cases where the request for hold is for CA2, but CA1 already has
a held call, and the call waiting is active, then the hold request is
denied.
When you set up repeated conferences from an analog set, you start with
the call on CA1, put it on hold (rule #2), and conference, the call ends up
on CA2.  The next hold request will find the call on CA2, with CA1 idle (rule
#4). Each time you complete the conference, your call remains on CA2, so
rule #4 applies repeatedly.
4-32  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Reconnectbbbbbbbb
The adjunct uses this controlling capability to reconnect an on-PBX party to a
controlled call.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch either:
Ð Reconnects the party to the call after validating the parameters, or
Ð Denies the request
Third Party Reconnect Parametersbbbbbbbbbbbbbbb
party_idIdentifies the party to be reconnected
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
The switch issues one of the following reasons as the cause for denying the
request:
Invalid association (CS0/81)
The association does not exist.
Invalid number/domain (CS0/28)
The party_id is incorrect or invalid.
Invalid Information Element contents (CS0/100)
The party_id value of the request is invalid.  For example, a Third Party
Reconnect 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.
Message not compatible with call state (CS0/98)
The party is not currently in the ``hold state so it cannot be reconnected.
The party was on-hook and did not go off-hook within five seconds after
the request was made (the call remains on hold).
Resources not available (CS3/40)
The host attempted to connect a seventh party to a six-party conference
call.
Issue 4  September 1995  
4-33 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Mandatory Information Element missing (CS0/96)
The party_id is missing in the request.
User busy (CS0/17)
The user is busy (active) on another call.
User not responding (CS0/18)
The party was on-hook when the request was made and it did not go
off-hook within five seconds (call remains on hold). |
Resources not available (CS3/43) |
The call cannot be reconnected due to too many parties already on the |
call or other switch-specific resource problems.
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
The switch 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 Communications
System CallVisor ASAI Protocol Reference
, 555-230-221.
Considerationsbbbbbbbbbbbbbbb
The adjunct uses previously received information about the party to release it
from the held state.  This party must have been placed on (hard or soft) hold
from the station set or via the adjunct.  A party may be reconnected only to the
same call from which it had been put on hold as long as there is no other active
call at the users station.  If the party is already reconnected on the specified call
when the switch receives the request, a positive ACK is returned.
If the user is on-hook (in the held state), the switch must be able to force the
station off-hook or the user must go off-hook within five seconds after requesting
a Third Party Reconnect.  If one of the above conditions is not met, the request
is denied and the party remains held.
If the user is listening to dial tone while a request for Third Party Reconnect is
received, the dial tone is dropped and the user is reconnected to the held call.
If the user is listening to any other kind of tone (for example, denial) or is busy
talking on another call, the Third Party Reconnect request is denied (CS0/17).
4-34  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Redirect Callbbbbbbbb
The adjunct uses this capability to re-route a call that is already alerting a station
extension.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch either:
Ð Redirects the call and drops the alerting party after validating the
parameters, or
Ð Denies the request and maintains the alerting party
Third Party Redirect Call Parametersbbbbbbbbbbbbbbb
redirecting
party_idIdentifies the party to be redirected from (must map to a valid
voice station extension, which includes off-premises stations
([OPS]).  If not specified, call is redirected away from ``last
added party to a call.
redirected-to-
number[mandatory] Identifies the number the call is routed to (may be
on- or off-switch).  If more than 24 digits are provided, only
the first 24 are used.
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
An acknowledgment is sent to the adjunct if the request is successfully
completed and the call stops alerting the redirecting station.
Denial (NAK) Causesbbbbbbbbbbbbbbb
The switch issues one of the following reasons as the cause for denying the
request:
Request is for release prior to G3V4 (CS0/111)
This service is only available beginning with release G3V4.
Mandatory Information Element missing (CS0/96)
The redirected-to number or other IE is missing in the request.
Invalid CRV (CS0/81)
The Call Reference Value is missing or invalid.
Invalid destination (CS3/43)
Invalid destinations include the following: empty (0 digits), unassigned
extension (invalid dial plan numbers), incomplete number of digits for
AAR/ARS pattern, or non-AAR/ARS FAC.
Issue 4  September 1995  
4-35 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Redirected-to Station Busy, or Terminating Extension Group (TEG) has
one or more members busy (CS0/17)
Miscellaneous Restrictions (CS3/42)
The redirected-to number cannot be the same as the originating
number or the redirecting number.
The call is redirecting on the first leg of a switch-classified call.
Miscellaneous Restrictions (CS3/43)
The redirected-to number is a Remote Access Extension, or the
COR check fails.
The redirecting station is origination-restricted.
Miscellaneous Restrictions (CS3/63)
The redirecting number is not a station extension, the call_id does
not exist, or the call is not in the alerting state or is redirecting while
in vector processing.
Calls that result in intercept treatment will not be allowed to redirect
even if normally such calls would be sent to an attendant.
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
The switch 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 Communications
System CallVisor ASAI Protocol Reference
, 555-230-221.
Considerationsbbbbbbbbbbbbbbb
With this service, when a call is routed to a new number, if the new number is a
station on the switch, it begins alerting (if available to receive the call) and the
originally-alerted party is dropped.  At this point, this alerting call is eligible to be
redirected again.  If the new (redirected-to) number is off-premises, the call is
routed there and the caller hears call progress tones. In this case, the call may
not be redirected again.
For both on- and off-switch redirection, the switch will not drop the redirecting
party until success is assured. It is at this point that the positive
acknowledgement is sent. If the switch cannot redirect the call, NAK is provided
and the alerting call will not be affected.
4-36  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
There is a special case where an adjunct can receive a positive
acknowledgment, but the redirect may fail.  For example, if the call is redirected
to an off-premises number and the network trunk is seized, the switch considers
this successful redirection and drops the redirecting party.  The caller may hear
any network-provided call progress tones.
Party_ids may be re-used if the call is redirected more than once.
An application using this feature should consider the timing for redirecting a call,
particularly when redirecting away from a display user. If a display station user
gets an incoming call and the application redirects it immediately, the station user
may not have enough time to read the display (the incoming call information)
before it is cleared by the application.
Since it is not possible to redirect busy calls, if possible an application should
check whether the call had resulted in a busy condition before attempting to
redirect it.  This may be done if the application receives the appropriate call
progress events from the switch (such as ``busy, ``reorder/denial, or
``connected).  ASAI Redirect Alerting Call is not disabled when trunk-to-trunk |
transfer is disabled.
The call state may change between the Alerting event and the service request for
redirection. An application should therefore expect certain NAKs and handle
them appropriately.
Issue 4  September 1995  
4-37 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Mergebbbbbbbb
The adjunct uses this controlling capability to merge (for example, conference or
transfer at a specified station) two existing controlled calls into a single call on
behalf of an on-PBX station.  A request is made over the association of the call
on hold.
NOTE:
This only works if one call is on hold while the other is active (alerting,
queued, held, or connected).
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch either:
Ð Merges the two calls after it has validated the parameters, or
Ð Denies the request if the calls and specified station are not specified or
are not in the correct state
Third Party Merge Parametersbbbbbbbbbbbbbbb
common_party_id[mandatory] Identifies the common endpoint with
regard to the held call.  This station must have a call
on hold and one active (talking) state call.
call_id[mandatory] The call_id of the active call.
conf/trans_flagThe type of merge (Conference/Transfer) is set with
this parameter.
The conf/trans_flag must be PRESENT.  If the flag is
set to TRANSFER, the calls are merged and the
common party is dropped from the call.  The transfer
operation merges the two existing calls and drops the
common party from the call.
If the conf/trans_flag is set to CONFERENCE, the
calls are merged together and the common party is
retained in the resultant call.
4-38  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
The switch replies with a call identifier for the merged call (call_id), a list of up to
six party identifiers for the parties on the call (party_id), and a list of up to six
extensions of the parties on the call.
An acknowledgement (with party/extension information) is sent to the controlling
adjunct when the conference/transfer is complete.  Included in the
acknowledgement is a list of all parties on the call (including extensions for local
parties).
The association used to request the capability is used for the acknowledgement.
Any other associations monitoring the call or Domain Controlling endpoints
receive the Call Conference/Call Transferred Event Reports.
result_call_idThe call_id after the call is merged (provided by the switch)
party_id listThe list of party_ids for the merged call (provided by the
switch)
extension listThe list of extension numbers for the parties on the merged
call.  Off-PBX parties always provide the default station
extension.  The address for queued parties is the split
extension of the queue.
Denial (NAK) Causebbbbbbbbbbbbbbb
The switch issues one of the following reasons as the cause for denying the
request:
Invalid association (CS0/81)
The association is nonexistent.
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 as required.
Resources not available (CS3/40)
The switch may have run out of resources (for example, time slots).
Issue 4  September 1995  
4-39 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Reorder/Denial (CS3/42)
Both calls are Alerting.
Both calls are being service observed.
An active call is in a vector processing stage.
The host attempted to add a seventh party to an existing six-party
conference call.
Invalid Information Element contents (CS0/100)
The party_id value of the request is invalid.
Mandatory Information Element missing (CS0/96)
The party_id or call_id is missing from the request.
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
The switch 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 Communications
System CallVisor ASAI Protocol Reference
, 555-230-221.
Considerationsbbbbbbbbbbbbbbb
Both calls must be controlled (for example, Call Control associations) for Third
Party Merge to operate successfully.
For analog sets (phones), Third Party Merge is only allowed if one call is held
and the second is active (talking).  Calls on hard hold or alerting cannot be
affected by a Third Party Merge request.
After the merge, the station is off-hook idle.
The Third Party Merge capability can be also used by the adjunct to transfer an
ACD call to a supervisor.  A sample scenario is presented below.  Note that this
sample is not the only way in which to effect the transfer to the supervisor.
An ACD agent handling may request (via data keyboard) that the call be
transferred to the supervisor.  The adjunct:
1. Places the existing call on hold.
2. Issues a Third Party Make Call request (with the supervisor-assist option)
to the supervisors extension.
4-40  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
3. When the supervisor either is alerted or answers, the adjunct may merge
the supervisor call and the previously held call using the Third Party
Merge capability.  (This capability is requested on the same association as
the held call).
Since this was a transfer request, the conf/trans_flag parameter is set to
TRANSFER and the switch drops the ACD agent from the connection after the
merge takes place.
If the ACD agent requested a supervisor conference, the same procedure would
have taken place but the conf/trans_flag would have been set to CONFERENCE;
the switch does not drop the ACD agent from the resulting connection. Thus, a
three-party call is created.
Issue 4  September 1995  
4-41