# Setting up DCE transport capability

To implement DCE transport in Fusion, applications must perform the following tasks:

Step | Action
1 | Configure the board resources by specifying the echo_v4 module in the Resource keyword string in the appropriate CG board keyword file. The following example shows how to specify a Fusion channel with DCE transport capability in a CG board configuration resource definition string. Resource[0].Definitions = (echo_v4.ln20_apt25 & \ ((f_g723.cod_rfc2833 & f_g723.dec_rfc2833) | \ (f_g729a.cod_rfc2833 & f_g729a.dec_rfc2833) | \ (f_g711.cod_rfc2833 & f_g711.dec_rfc2833)))
2 | Start a protocol on the context associated with the voice channel, and specify appropriate mediamask parameters to enable echo cancellation, but not to detect CED and other signals within the DS0 endpoint. For more information about configuring echo cancellation appropriately for DCE over IP transport refer to Configuring the echo canceller. The following sample code shows how an application defines a flag that specifies the appropriate mediamask settings to support DCE transport. if (pCmdLineParms->bEnableDCETransport) { startparms.mediamask = NCC_CC_AUTOECHO; } else { startparms.mediamask = NCC_CC_RESVDTMF | NCC_CC_RESVSILENCE | NCC_CC_RESVCLRDWN | NCC_CC_AUTODTMF | NCC_CC_AUTOECHO; }
3 | When creating the voice channel, specify settings in the MSPP G.711 channel address and parameter structures that enable RFC 2833 capabilities. For more information about setting appropriate G.711 voice channel parameters to implement DCE over IP transport, refer to Configuring clear G.711 channels.