Analog loop start protocols require a voice or tone resource for setting up a call. Application development considerations for using dedicated voice resources in an analog loop start environment are discussed in this chapter.
For Springware boards with on-board analog loop start devices, a voice device and an analog loop start device comprise a single channel. Although these devices can be addressed separately, all analog signaling is processed by the associated voice device; analog signaling (ring detection and loop current detection) events are not transmitted over the SCbus. For DM3 boards with on-board analog loop start devices, the voice device and the analog loop start device are separate devices.
Applications requiring voice resources during the entire call (for example, voice-mail, announcements) must have enough voice channels to dedicate one channel to each analog loop start channel. A single gc_OpenEx( ) function call can open both the analog loop start device and voice device on both Springware and DM3.
To perform activities such as routing and voice store and forward, use the gc_GetVoiceH( ) functions to obtain the voice handle associated with a line device. For example, before playing a file, you can retrieve the voice handle using the gc_GetVoiceH( ) function. If needed, you may route other resources to the analog loop start channel (for example, to send a fax) and reroute the voice channel back to the analog loop start channel before setting up or waiting for another call. You must route the same voice channel back to the associated analog loop start channel on Springware because these two resources were internally attached when opened. On DM3, no such restriction exists because the two resources are independent of each other.
The following example illustrates the function calls that apply when using dedicated voice resources.
Click here to contact Telecom Support Resources
Copyright 2003, Intel Corporation