Section 470 - TSAPI Programmer’s Guide
4
Issued April 2000
DBS-92-470
* = Unspecified
• Grayed boxes represent devices in a call unaffected by the service or event report.
• White boxes and circles represent devices and calls affected by the service or event report.
• The parameters for the function call of the service are indicated in bold italics.
Answer Call Service
The Answer Call Service is used when an incoming call (C1) is alerting (ringing) a device
(D1) with the connection
alertingCall
(C1-D1). The effect is the same as if the answering
party answered the call via the telephone on/off button.
Function: cstaAnswerCall( ), CSTAAnswerCallConfEvent
Direction: C
→
S
Functional Description:
The Answer Call Service allows a client application to request that a call ringing at a sta-
tion be answered. Answering a ringing call means to connect a call if the user is on-hook
by forcing the station off-hook, or, if the user is off-hook, by cutting through the call to the
headset or handset. An active call may be dropped or placed on hold when the new call is
answered (depending on how the extension is programmed).
The deviceID in
alertingCall
must contain the station extension of the endpoint to be
answered on the call. A Delivered Event Report must have been received by the applica-
tion prior to this request.
The Answer Call Service can be used to answer calls presented to digital telephones only.
The Answer Call Service request is acknowledged (Ack) by the switch if the switch is able
to connect the specified call either by forcing the station off-hook (i.e., turning the speak-
erphone on) or by taking the appropriate action required to handle an existing call.
Answering a call which is already connected will result in a positive acknowledgment and
the call will remain connected.
Service Parameters:
alertingCall
[mandatory] a valid connection identifier indicates the callID
and the station extension (STATIC_ID).
Ack Parameters:
noData
None for this service.
Nak Parameter:
universalFailure
•
INVALID_CSTA_CONNECTION_IDENTIFIER (13)
An incorrect callID, or an incorrect deviceID is specified.
•
INVALID_OBJECT_STATE (22)
The specified connection at the station is not in the alerting or connected.
Summary of Contents for Selection 470
Page 1: ......
Page 8: ...viii Issued April 2000 DBS 92 470 Section 470 TSAPI Programmer s Guide ...
Page 104: ...Section 470 TSAPI Programmer s Guide 96 Issued April 2000 DBS 92 470 Call Park ...
Page 105: ...Section 470 TSAPI Programmer s Guide DBS 92 470 Issued April 2000 97 Call Pickup ...
Page 108: ...Section 470 TSAPI Programmer s Guide 100 Issued April 2000 DBS 92 470 3 Way Conference ...
Page 109: ...Section 470 TSAPI Programmer s Guide DBS 92 470 Issued April 2000 101 Hold Intercom ...
Page 112: ...Section 470 TSAPI Programmer s Guide 104 Issued April 2000 DBS 92 470 Off Hook Voice Announce ...
Page 114: ...Section 470 TSAPI Programmer s Guide 106 Issued April 2000 DBS 92 470 Transfer Supervised ...
Page 115: ...Section 470 TSAPI Programmer s Guide DBS 92 470 Issued April 2000 107 Transfer Unsupervised ...
Page 122: ...Section 470 TSAPI Programmer s Guide 114 Issued April 2000 DBS 92 470 ...
Page 126: ...iv Issued April 2000 DBS 92 470 Section 470 TSAPI Programmer s Guide ...