VOIP_SupA_Xfer

The VOIP_SupA_Xfer state table is used as the default outbound state table for attended transfers when using DTEA, hardware. The state table attempts to perform a MakeCall and returns the success or failure to the VOIP Signaling Process using the VOIP_Call_Transfer custom server. After the results of the MakeCall have been reported, if the action was successful, the state table enters into a WaitEvent for up to 30 seconds to allow the transfer to complete. When the transfer completes, the transfer channel is hung up and the WaitEvent exited. If the call does not hang up, the WaitEvent times out and the state table finishes (this hangs up the call). If the MakeCall was not successful, the call hangs up immediately.

You can customize the application, but you must not change the basic functions. Comments in the source code show where you can insert code to perform a consultation with the third party.

Parameters

String phone_number (maximum of 40 characters)
The number to dial for the outgoing part of the transfer. This can contain a NULL string if a SIP header is passed using SV541. For more information, see the definition of phone_number in the description of the MakeCall state table action in Blueworx Voice Response for AIX: Application Development using State Tables.
String format (maximum of 50 characters)
The format string for the number to dial for the outgoing part of the transfer. For more information, see the definition of format in the description of the MakeCall state table action in Blueworx Voice Response for AIX: Application Development using State Tables.
String log_filename (maximum of 64 characters)
If this parameter is blank, no event logging is performed. If you specify a file name, event logging of the transfer calls is performed and the results are logged in the file you specify. The logging is performed by the VOIP_Xfer_Log state table.
String tags
Contains a copy of the contents of SV541 sent from the application. This can contain SIP tags such asTO_HDR (see Voice over IP tags), or user-defined tags. User defined tags are ignored by the SIP stack.