Click here for more information about Supervised Transfer.
Development
Environment Technical Information
|
|||||||||||||||||||||||||||||||||||||||||||||||
Requirements |
|||||||||||||||||||||||||||||||||||||||||||||||
Configuring
a Dialogic Card PBX Strings |
|||||||||||||||||||||||||||||||||||||||||||||||
Using This Sample Program |
|||||||||||||||||||||||||||||||||||||||||||||||
To create a three way call click the ThreeWay button instead of the Complete button. Some telephony devices require you to create a three way call in order to create a conference. You will notice that the TeleTools etLine control will indicate that a conference has been created in those situations. Once the primary call is on hold and the consultation call is connected you may click the SwapHold button. This will cause the consultation call to be placed on hold and the primary call the be taken off hold. Most telephony devices require the primary call to be on hold before completing the transfer or creating a three way call. Some telephony devices do not support this feature. Read the device documentation to determine their capability. Also see the “etLine.Transfer Methods” topic in the ExceleTel TeleTools help file. For demonstration purposes, this sample program requires the primary call to be dialed. A typical application could perform the transfer for either an outbound or an inbound call. Most telephony devices (and their associated TAPI TSP) do not care if the primary call was inbound or outbound.
|
|||||||||||||||||||||||||||||||||||||||||||||||
Download this Sample Program |
|||||||||||||||||||||||||||||||||||||||||||||||
For Use With TeleTools v3.7
|
|||||||||||||||||||||||||||||||||||||||||||||||
How this Sample Program Works |
|||||||||||||||||||||||||||||||||||||||||||||||
|
When the program starts the Form_Load event handler routine fires. The etLine control is enabled which allows the list of devices to be used to fill the Device combo box. The etLine.TeleScope.Visible property is set to True causing the etLine TeleScope to be displayed. When the user selects a device from the list box the etLine.Device.Active property is set to False and the Active check box is unchecked. When the Active check box is checked the etLine1.AddressCapabilitiesCallFeatures property is checked to see if the selected device supports supervised transfers. This is done by checking the bit flag at the position defined by the constant LINECALLFEATURE_SETUPTRANSFER. If the device does not support this feature then an error dialog box is displayed. Finally the etLine.Device.Active property is set to True, activating the TAPI line device. Pressing the Dial button causes the etLine.Call.PhoneNumber property to be filled with the phone number in the edit box adjacent to the button. If the associated Address edit box has a numeric value other than zero then the etLine.Call.Paramaters.Defaults property is set to False and the etLine1.Call.Parameters.AddressID is set. This is useful with telephony devices that support multiple addresses for the selected line device. Finally the etLine.Call.Dial method is called. Pressing the TransferDial button causes the etLine.Transfer.PhoneNumber property to be filled with the phone number in the edit box adjacent to the button. If the associated Address edit box has a numeric value other than zero then the etLine.Transfer.Paramaters.Defaults property is set to False and the etLine1.Transfer.Parameters.AddressID is set. This is useful with telephony devices that support multiple addresses for the selected line device. Finally the etLine.Transfer.Dial method is called. Clicking the SwapHold button causes the etLine1.Transfer.SwapHold method to be called. Clicking the SwapHold button causes the etLine1.TransferComplete method to be called. Clicking the SwapHold button causes the etLine1.TransferThreeWay method to be called.
|
|||||||||||||||||||||||||||||||||||||||||||||||
Release Notes |
|||||||||||||||||||||||||||||||||||||||||||||||
April 9, 2003Published |