Using Call Controls
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Using Call Management Controls in Script
Call Management Controls inherit from the IndexedSpeechControl class, which is the parent class of Call Management Controls that are managed by the RunSpeech object. For more information, see Management of Call Controls.
Connecting to the Default Telephony Interface Manager
Call Management Controls create a Speech Application Language Tags (SALT) smex tag that connects to the default Telephony Interface Manager on Telephony Application Services (TAS). Application authors do not need to create their own smex tag and should not try to access properties or methods of the existing smex tag directly.
Terminating a Call
In general, application authors should use the DisconnectCall control to end the phone call in a speech application after posting all necessary data to the server and closing the window. The processing of the DisconnectCall control removes the call from the TAS queue. If authors close the application page without disconnecting the call, the hardware resources used by that call remain unavailable until TAS determines that the call has timed out. The duration of this time-out is two minutes.
Handling User Disconnects
If a caller hangs up or disconnects, RunSpeech receives an error with a status of ???30. This error does not cause a postback to the server. If an application requires a postback, application authors should use the routine specified by the OnUserDisconnected property of RunSpeech to force a postback by calling the SpeechCommon.Submit() method.
For more information about the RunSpeech.OnUserDisconnected property, see RunSpeech - OnUserDisconnected Property.