Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

							ASAI Capabilities
Issue  3  May 1998
5-11
Third Party Call Control Capabilities
The Third Party Call Control capability group includes a number of third party 
subgroups and two types of the abort capabilities. In addition, there are numerous 
Event Report interactions. Event reports and abort capabilities are described in 
this chapter.
Third Party Call Control allows a client to establish, control, terminate, and monitor 
calls to which the client is not a party. When invoking the Third Party capabilities, 
the client controls a call on behalf of a party to the call. For example, a client can 
request that a call be set up between Party A and Party B. At a later time, Party C 
can be conferenced into the call. The server handles the third party conference 
request as if it had been made by Party A or Party B.
Third Party Call Control that interacts with switch-classified calls is unique. In 
general, if the ECS receives any RELease COMplete message for a Third Party 
Call Control association (started by 3P_Make_Call or 3P_Take_Control), the 
ECS continues to process the call normally. 
The exception to this occurs when the ECS receives any RELease COMplete 
message for an ECS call that is in the classification state (has not yet been 
classified). In this case, on receipt of the RELease COMplete message, the ECS 
will deny a Relinquish Control request and tear down the call.
Third Party Call Control provides for the following:
nThird Party Answer Call
nThird Party Automatic Dialing
nThird Party Clear Call
nThird Party End Call
nThird Party Domain Control
nThird Party Domain Control End
nThird Party Listen Disconnect
nThird Party Listen Reconnect
nThird Party Make Call
nThird Party Merge
nThird Party Reconnect
nThird Party Redirect Call
nThird Party Relinquish Control
nThird Party Selective Drop
nThird Party Selective Hold
nThird Party Send DTMF Signals 
						

							ASAI Capabilities
5-12Issue  3  May 1998 
nThird Party Single-Step Conference
nThird Party Take Control
There are certain restrictions common to most third party calls:
nThe calling number is not permitted the service. For example, the calling 
number may not be permitted to make out-of-state calls.
nThe called number is not permitted the service. For example, the called 
number is not permitted to accept out-of-state calls.
nThe client is not permitted to request the service. 
						

							ASAI Capabilities
Issue  3  May 1998
5-13
Third Party Answer Call
Description
The Third Party Answer Call capability allows the client to request to “answer” a 
call on behalf of a station user. The call can be a ringing, bridged, or held call that 
is present at a station.
Answering a ringing, bridged or held call indicates to connect a call by forcing the 
station off-hook (if the user is on-hook) or cutting through the call to the head or 
handset (if the user is off-hook). The effect is as if the station user selected the call 
appearance of the alerting, bridged, or held call and then went off-hook.
The client invokes this capability by issuing a C_3PANS to which the server 
responds with a C_3PANS_CONF (
Third Party Answer Call confirmation). After the 
acknowledgement, the client continues to receive event reports for the answered 
call.
The 
Third Party Answer Call request is acknowledged by the server if it is able to 
connect the specified call by either forcing the station off-hook (turning the 
speakerphone on) or waiting up to five seconds for the user to become off-hook.
The server sends a C_NEG_ACK if the parameters of the request are invalid or if it 
cannot attempt the answer operation.
Request/Confirmation Parameters
nCall Identifier — Indicates the alerting, bridged, or held call to be 
connected at the controlled station.
Notes
The Third Party Answer capability can be used to answer a call present at any 
station type (that is, analog, DCP, hybrid, and BRI), as long as the station is 
domain controlled. A call which is already connected when the Third Party Answer 
request is made will result in a positive acknowledgement. 
Interactions with Event Reports
This capability can be issued after the domain-controlled station is in the alerting 
or held state on the call for which this capability is requested. After this capability 
is successfully acknowledged, the station party moves to the active state. 
						

							ASAI Capabilities
5-14Issue  3  May 1998 
Third Party Auto Dial
Description
The Third Party Auto Dial capability allows a client to request the server to 
establish a call on behalf of the controlled extension specified in a 
Third Party 
Domain Control (extension) request. The effect is that the extension places a call 
to the specified called number automatically when that extension is off-hook. The 
capability also allows the server to confirm the request.
The client issues a C_3PAD to request that the call be made and monitored.   The 
server responds with a C_3PAD_CONF if the client has requested 
acknowledgement. The 
Third Party Auto Dial confirmation indicates only that the 
request has been received and understood and that the server will try to establish 
the requested call. If the server cannot establish the call, it issues a call ended 
event report to the client. The server issues event reports only after a positive 
acknowledgement.
A negative acknowledgement is issued only if the client is not subscribed to the 
service or if the server is unable to accept the request.
Request/Confirmation Parameters
nDestination Address — The called endpoint.
nReturn Acknowledgement — Indicating that the server must return an 
acknowledgement to the client.
In addition, the following parameters are optional:
nFacility Type — Used only if the Destination Address is a trunk group.
nFacility Access Code — Required only if Facility is specified.
nPriority Calling — Provides a special ring and places call ahead of all 
other calls for that party.
nUser to-User-Data — A substructure containing user data. The structure 
contains the following fields:
—Leng field — An integer value that indicates the number of octets of 
user data included in the request. This field is set to 0 if no user-user 
data is present. Currently, the ECS will accept up to 32 bytes of data 
(leng = 32). If more than 32 bytes is specified, all data is discarded.
—Protocol field — Indicates the type of information and is restricted 
to C_UU_USER which indicates a user-specific protocol or
C_UU_IA5 which indicates IA5 or ASCII characters.
—Info field — A pointer to an ASCII string of no more that 32 
characters in length. 
						

							ASAI Capabilities
Issue  3  May 1998
5-15
Notes
There are no restrictions on this capability.
Related Event Reports
This capability does not affect the state(s) of the parties to the call. 
						

							ASAI Capabilities
5-16Issue  3  May 1998 
Third Party Call Ended
Description
The Third Party Call Ended capability is issued by the server to inform the client 
that a client-controlled call has been disconnected and the association has been 
cleared. The client can no longer control the call or use its association identifier.
The server issues a C_3PCE when the endpoints to a call have been 
disconnected or when some internal condition causes it to terminate processing 
for the call.
Request/Confirmation Parameters
Call Identifier — The call that has been terminated.
Notes
This capability may indicate that an existing call has been merged with another 
existing call. It may also be used if a call initiated by a C_3PMC_REQ cannot be 
routed by the server, thus terminating call processing.
Interactions with Event Reports
Reports that a call, identified by its call identifier, has ended and that the last party 
to the call was dropped or disconnected. A 
drop event for the last party added to 
the call is not issued in these instances; thus, this capability replaces the last 
drop 
event on a call. 
						

							ASAI Capabilities
Issue  3  May 1998
5-17
Third Party Clear Call
Description
The Third Party Clear Call capability allows a client to request that an existing call 
be disconnected and related resources be freed. All parties to the call are 
disconnected.
The client invokes this capability by issuing a C_3PCC. The server responds with a 
C_3PCC_CONF as soon as the call has been completely cleared. Until the call is 
completely cleared and all resources freed, the server continues to issue event 
reports about the call.
Notes
Control of the call to be cleared must have been initiated by a Third Party Make 
Call or a 
Third Party Take Control capability.
The client can issue this capability at any time, regardless of pending or 
outstanding acknowledgements for previously requested capabilities.
Interactions with Event Reports
After this capability is successfully acknowledged, all parties on the call return to 
the 
null state. 
						

							ASAI Capabilities
5-18Issue  3  May 1998 
Third Party Domain Control
Description
The Third Party Domain Control capability allows a client to request the server to 
begin reporting events for calls that originate and terminate at the specified 
domain. The client can also request third party call control capabilities for those 
calls. After the server accepts the request, the client receives an 
Event Report 
each time an event occurs. Clients can have several simultaneously active 
instances of 
Third Party Domain Control and a single event can be reported to 
more than one association. When this happens, the client receives separate event 
reports.
The client invokes this capability by issuing a C_3PDC_REQ to which the server 
responds with event reports. The server continues to issue event reports until one 
of the following occurs:
nThe client invokes the Third Party Relinquish Control capability
nThe server invokes the Third Party Domain Control Ended capability
nThe server receives a P_ABORT capability
nThe server receives or invokes a U_ABORT capability
Request/Confirmation Parameter
Domain — The domain over which event reports are to be provided and third 
party call control capabilities can be requested. The domain consists of:
nDomain Value (station or ACD split/skill)
Notes
The client can request control only for domains directly associated with the server.
Interactions with Event Reports
As soon as the server accepts this request, it begins to issue event reports to the 
client. 
						

							ASAI Capabilities
Issue  3  May 1998
5-19
Third Party Domain Control End
Description
The server issues the Third Party Domain Control Ended capability when it can no 
longer provide event reports or allow third party capabilities for the specified 
domain.
The server issues a C_3PDCE, after which the client no longer receives event 
reports for the domain. The server will not accept additional third party capabilities 
and the association is terminated.
Notes
Control must have been initiated with a Third Party Domain Control request.
Interactions with Event Reports
This capability does not affect the state(s) of the parties to the call. 
						

							ASAI Capabilities
5-20Issue  3  May 1998 
Third Party Listen-Disconnect
Description  
Third Party Listen-Disconnect capability allows the client to request the server to 
temporarily disconnect a specified party (the listener) from listening to 
communication from another party or parties [the talker(s)] on an active call. The 
client continues to receive feedback regarding the call and may continue to control 
the call with further Third Party capabilities.
The server sends a C_3PSL_DISC_ACK with primitive type C_POS_ACK when it 
has disconnected the listener party from listening.
The server sends a C_3PSL_DISC_ACK with primitive type C_NEG_ACK if the 
parameters of the request are invalid or if it cannot disconnect the listener party 
from listening.
Request/Confirmation Parameters
Depending on the conditions, the request must specify the following parameters:
nListener Party Identifier — The party on the call to be disconnected from 
listening.
The request may also specify:
nTalker Party Identifier — This parameter is specified to identify a specific 
party who will no longer be heard by the listener. If this parameter is 
omitted, the listener will be disconnected from listening to 
all other parties 
(that is, the listener will not hear any other party on the call).
Notes 
The listener party must be connected on the call. 
Although any voice path originating from a station or trunk on a call is blocked for 
the party which is disconnected from listening, it is possible that a disconnected 
listener will still hear faint tones or speech. This can happen in a multiparty call 
where the primary voice path is disconnected but alternate paths remain (for 
example, through a third party on the call whose voice path to listener is not 
disconnected).
Interactions with Event Reports
This capability does not affect the state of any party on a call.