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

							ASAI Capabilities
Issue  3  May 1998
5-21
Third Party Listen-Reconnect 
Description  
The Third Party Listen-Reconnect capability allows the client to request the server 
to reconnect a specified party (the listener) who was previously blocked from 
listening to one or more parties on a call via the Third Party Listen-Disconnect 
capability.
The server sends a C_3PSL_RECONN_ACK in response to this request. Primitive 
type C_POS_ACK indicates success; C_NEG_ACK is used if the parameters of the 
request are invalid or if it cannot reconnect to listen.
Request/Confirmation Parameters
Depending on the conditions, the request must specify the following parameters:
nListener Party Identifier — The party on the call to be listen-reconnected 
to listening.
The request may also specify:
nTalker Party Identifier — This parameter is specified to identify a specific 
party who will be listen-reconnected. If this parameter is omitted, the 
listener will be listen-reconnected to 
all other parties.
Notes
The listener party must be connected on the call and should have been previously 
listen disconnected.
Interactions with Event Reports
The capability does not affect the state of any party on a call. 
						

							ASAI Capabilities
5-22Issue  3  May 1998 
Third Party Make Call
Description
The Third Party Make Call capability allows a client to request the server to 
establish a call on behalf of two other parties, one of which must be designated as 
the calling party and the other as the called party. The capability also allows the 
server to confirm the request.
The client invokes this capability by issuing a C_3PMC_REQ to which the server 
responds with a C_3PMC_CONF (
Third Party Make Call confirmation) if the client 
has requested acknowledgement. The 
Third Party Make Call request initiates an 
Event Report (C_EN_REP).
The client retains control of the call until one of the following conditions is met:
nThe client issues a Third Party Clear Call request for the call.
nThe client issues a Third Party Relinquish Control request for the call.
nThe client receives a Third Party Call Ended capability for the call.
nThe client invokes or receives a U_ABORT capability for the call.
nThe client receives a P_ABORT capability for the association.
Note that this is not an instantaneous process; an acknowledgement from the 
server means only that the server has received and understood the request. The 
server then must attempt to fulfill the request, perhaps try several alternative 
routes. If the first route fails, the server may not be able to attempt a second route 
and call processing terminates. In this case, if the ack_flag is set on, the client 
receives an acknowledgement from the ECS. If the ack_flag is not set on, the 
client receives no response, regardless of whether the call can be made or not 
(see ‘‘C_3PMC_CONF (3ASAI)’’ on page 9-49 in Chapter 9, ‘‘Programming 
Manual Pages’’).
Request/Confirmation Parameters
nCalling Number — The party, specified by extension number, on whose 
behalf the call is being made
nCalled Number — The extension number of the third party who is being 
called
nAcknowledgement Requested — A flag that must be set on or off, 
indicating whether the server must return an acknowledgement as soon as 
it accepts the C_3PMC request
In addition, the programmer can specify any or all of the following:
nType of Facility — Trunk group, ACD split or neither (default = neither) 
						

							ASAI Capabilities
Issue  3  May 1998
5-23
nFacility Access Code — Access code of the trunk or ACD split, if one is 
specified
nPriority Call — A flag indicating that the call is a priority call
(default = no priority)
nWaiting Time — The number of rings (after the call has reached the 
alerting state) to wait for the call to be answered (default is  
ECS-dependent)
nService Circuit — A flag indicating that a call classifier is to be added to 
the call (default = no call classifier)
nDirect Agent Call — A flag indicating that the call is directed to a specific 
ACD agent (default = no agent) 
nSupervisory Assist — A flag indicating that the call has been directed by 
an ACD agent who needs assistance to an ACD supervisor 
(default = no assist)
nAlternate Destination — A flag indicating that the called number is to be 
alerted first, before the calling number (default = calling number first)
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.
nans_mach_treat —If ans_mach_treat is CO_AM_DISC, the call is 
disconnected upon answering machine detection. If the treatment is 
C_CO_AM_SWITCH, it follows the setting in the ECS administration. If the 
treatment is C_CO_AM_CONNECT, the call is connected.This parameter 
must be coded -1 if unused.
Notes
If the Service Circuit parameter is used to add a call classifier to the call and a call 
classifier is not available, the server rejects the 
Third Party Make Call request, 
terminates the call and sends the 
Third Party Call Ended capability to inform the 
client.
If the Direct Agent parameter is selected, the Type of Facility must be set to ACD 
and the Facility Access Code must be supplied. 
						

							ASAI Capabilities
5-24Issue  3  May 1998 
Interactions with Event Reports
Without the Alert Originator First option, this capability places the originating party 
in the 
active state. 
						

							ASAI Capabilities
Issue  3  May 1998
5-25
Third Party Merge
Description
The Third Party Merge capability allows a client to request the server to merge 
two existing, client-controlled calls that have a common party. The capability also 
allows the server to confirm the request. The effect of the merge is similar to a 
conference or transfer operation, depending on the value of the conference flag. If 
the conference flag is on, the common party remains connected to the call along 
with all the other parties (as in conferencing). If the conference flag is off, the 
common party is dropped from the merged call (as in transferring).
The client invokes this capability by issuing a C_3PM request to which the server 
responds with a C_3PM_CONF. The server sends positive acknowledgement when 
it has validated the parameters and merged the calls. After the acknowledgement, 
the client receives a 
Third Party Call Ended (C_3PCE) and continues to receive 
event reports for the merged call. The client can control the merged call using the 
association identifier that remains active.
Negative acknowledgement means that the request parameters were invalid or 
that the server cannot merge the two calls. In this case, the client can continue to 
control both calls.
Request/Confirmation Parameters
nCall Identifier 1 — One of the calls to be merged. 
nCall Identifier 2 — The other call. This identifier is inferred from the 
association identifier for the call.
nCommon Party Identifier — The party common to both calls.
nConference Flag — The flag that indicates whether the common party is 
to be retained on the merged call or disconnected.
n Party List — Pointer to a structure that indicates the ECS-assigned party 
identifiers after two calls are merged.
n Old Party Identifier — Pointer to a structure that indicates the old party 
identifiers before the call is merged.
Notes
The ECS chooses which call is to be Call Identifier 1 and which is to be Call 
Identifier
 2. Consult your DEFINITY ECS system administrator for specific 
information. 
						

							ASAI Capabilities
5-26Issue  3  May 1998 
Interactions with Event Reports
This capability can be issued after the common party is in the held state on the 
call for which the capability is requested and in the 
active state on the second call. 
After this capability is successfully acknowledged, the common party moves to the 
active state or to the null state, depending on the conference flag. All other parties 
to the call remain in the state they were in before the merge request. 
						

							ASAI Capabilities
Issue  3  May 1998
5-27
Third Party Reconnect
Description
The Third Party Reconnect capability allows the client to request the server to 
reconnect a specified party.
The client invokes this capability by issuing a C_3PR to which the server responds 
with a C_3PR_CONF. The client must use feedback to determine the state of the 
call with respect to each endpoint. If the server is unable to attempt the 
reconnection or if the parameters specified by the client are invalid, the 
association identifier remains valid for further control of the call and the party that 
was to have been reconnected remains in the state it was in, prior to the request.
Request/Confirmation Parameters
The following parameters are mandatory under the conditions noted; otherwise, 
they are optional:
nParty Identifier — The party to be reconnected. This parameter is 
mandatory if the association is started with a 
Third Party Make Call or Third 
Party Take Control capability. It can be inferred (and thus is optional) if the 
association is started with a 
Third Party Domain Control capability.
nCall Identifier — The call that is to be reconnected. This parameter is 
mandatory if the association is started with a 
Third Party Domain Control 
capability; if the association is started with a 
Third Party Make Call or Third 
Party Take Control capability, it can be inferred.
Notes
The party to be reconnected must be in the held state. Some servers may have to 
be directly connected to the party to be reconnected.
Interactions with Event Reports
This capability can be requested for a directly connected party when the party is in 
the 
held state. After this capability is successfully acknowledged, the party goes 
from the 
alerting state to the active state. 
						

							ASAI Capabilities
5-28Issue  3  May 1998 
Third Party Redirect Call
Description
The Third Party Redirect Call capability allows a client to request that an alerting 
call be redirected to another number. 
The client invokes this capability by issuing a C_3PREDIR request to which the 
server will respond with an acknowledgment. The server sends positive 
acknowledgment when it has validated the parameters.
The server sends a C_NEG_ACK if the parameters of the request are invalid or if it 
cannot apply the tones to the call.
Request/Confirmation Parameters
Depending on conditions, the request must specify the following parameters:
nASAI Common — The capability should be set to C_PREDIR and 
primitive_type to C_REQUEST. The sao_id (formerly known as 
cluster_id) should also be set to identify the association that controls 
the alerting call.
nCall Identifier — This parameter is required for domain control 
association, and is ignored with call control associations. Two fields, 
id_length and id_ptr are in a call id. If the id_length is zero, the 
field is omitted. If the id_length is not zero the id_ptr contains a 
binary representation for the call id.
nRedirect Number — This required parameter identifies the destination of 
the redirected call. Two fields, plan_type and s, are in a number id. The 
field s is a null-terminated string containing the destination number. The 
field plan_type is described in ‘‘Identifiers’’ on page 8-5 in Chapter 8, ‘‘ASAI 
Capability Primitives’’.
nParty Identifier — This is an optional parameter. It specifies the 
redirected-from party on the call. The length of the party identifier is 
id_length. The character array pointed to by id_ptr contains the 
party_id. If omitted, the last added party is used.
Notes
For a call to be redirected, it must be alerting at a station.
Interactions with Event Reports
A redirected call’s event reports will be the same as to call coverage. 
						

							ASAI Capabilities
Issue  3  May 1998
5-29
Third Party Relinquish Control
Description
The Third Party Relinquish Control capability allows a client to yield control of an 
existing call. All parties remain connected to the call. Once acknowledgement is 
received from the server, no further feedback is provided and the client cannot 
exert any further control over the call or domain within that association.
The client invokes this capability by issuing a C_3PRC_REQ to which the server 
responds with a C_3PRC_CONF (
Third Party Relinquish Control confirmation).  
Once positive acknowledgement has been received by the client, the association 
identifier used by the C_3PTC_REQ is terminated.
If the server sends a negative acknowledgement, the association identifier used 
by the C_3PTC_REQ is still active.
Notes
A client can issue this capability at any time, regardless of any pending or 
outstanding acknowledgements for any previously requested capability.
Interactions with Event Reports
This capability does not affect the state(s) of the parties to the call. 
						

							ASAI Capabilities
5-30Issue  3  May 1998 
Third Party Selective Drop
Description
The Third Party Selective Drop capability allows a client to request the server to 
disconnect a specified party. 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_3PSD_POS_ACK when it has disconnected the party. The 
client must use feedback to determine the state of the call with respect to each 
endpoint.
The server sends a C_3PSD_NEG_ACK if the parameters of the request are invalid 
or if it cannot disconnect the party.
Request/Confirmation Parameters
Depending on conditions, the request must specify the following parameters:
nParty Identifier — The party on the call to be disconnected. This 
parameter must be specified if the association is started with a 
Third Party 
Make Call capability; it can be inferred if the association is started with a 
Third Party Domain Control capability.
nCall Identifier — The call on which this capability operates. This 
parameter must be specified if the capability is requested over an 
association started with a 
Third Party Domain Control capability; otherwise, 
it must not be used.
nUse- 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.
Notes
There are no restrictions on this capability.