Use AnswerCall to respond to a ringing line.
This action establishes the connection between the caller and Blueworx Voice Response for an incoming call. An application cannot execute actions that use the telephone line (GetData, GetKey, and so on) until this connection is established. Note that multiple AnswerCall actions do not result in the application sending multiple off-hook signals to the switch.
When Blueworx Voice Response makes an outbound call, connection is established when the called party picks up the telephone.
The AnswerCall action need not be in the same state table as the Get actions, but must have been executed before these actions in a state table that is part of the same voice application.
When you use the Incoming Call state table, you can still use the AnswerCall action in your state tables because, once a call has been answered, subsequent AnswerCall actions are ignored by Blueworx Voice Response. However, AnswerCall actions in your state tables are used by the state table debugger and may be useful.
AnswerCall supports use of the system variable SV541 to pass additional call information from a state table to SIP, and SV542 to receive information back from SIP. See Transferring information between a state table and SIP for more details . Note the following considerations that are specific to the use of the variables within AnswerCall:
Use AnswerCall to answer an incoming call notified by SIP. When Blueworx Voice Response receives an incoming call from SIP, it fills in the following system variables with information received from the network about the call:
If no application is configured to answer the call, Blueworx Voice Response automatically requests the signaling process to clear the call.
No parameters are required.
AnswerCall can have one of the following results:
Cause Code: Any.
When using an ASCII editor, code this action as the example demonstrates:
label: "Check Edges" AnswerCall() edge EDGE_AC_COMPLETED: completed edge EDGE_AC_NOT_RINGING: not_ringing ;
The edges are described above under "Possible results". For more information, see Testing a state table using the debugger.