3.1. GTD Tone Considerations

NOTE:

The information in this section is applicable to Springware boards only.

Unless global tone detection (GTD) is disabled by the application by calling the gc_SetParm( ) function, if a protocol uses GTD tones for call analysis, the protocol sends tone definitions to the firmware when the gc_Attach( ) function is issued. The gc_Attach( ) function may be called directly from the application; this function is also called from within the gc_OpenEx( ) function if a voice channel is specified. The voice channel must be idle. Any pre-existing tones are deleted.

CAUTION

The application must NOT delete the default tones downloaded by the protocol or the protocol will fail.

If the application requires additional tones after the initial set of tones are loaded, they must be redefined after calling the gc_Attach( ) function. For any application that calls the gc_Attach( ) function several times on the same device (for example, when using resource sharing), the overhead associated with redundant tone deletion and definition may be avoided by calling the gc_SetParm(ldev, GCPR_LOADTONES, GCPV_DISABLE) function after the first call to the gc_Attach( ) function. Afterward, the application must reverse the effect of the gc_SetParm( ) function by issuing a gc_SetParm(ldev, GCPR_LOADTONES, GCPV_ENABLE) function when the call is complete.

NOTE:

For PDK and ICAPI protocols, the tone IDs for any additional tones that must be redefined after calling the gc_Attach( ) function cannot be in the range from 101 to 189.

Click here to contact Telecom Support Resources