• 12.3.1. gc_Open( ) and gc_OpenEx( ) Restrictions (Fixed Routing)
• 12.3.2. Associating Network and Voice Devices (Fixed Routing)
• 12.3.3. ISDN Direct Layer 2 Access (Fixed Routing)

12.3. Using the GlobalCall API in an R4 on DM3 Fixed Routing Configuration

12.3.1. gc_Open( ) and gc_OpenEx( ) Restrictions (Fixed Routing)

In R4 applications that use a DM3 fixed routing configuration, it is not possible to specify the protocol and voice device in the ASCII string pointed to by the devicename parameter in gc_Open( ) and gc_OpenEx( ) commands.

The devicename can be as simple as:

    :N_dtiB1T1

where:

• N_ denotes a network timeslot device, in this example, dtiB1T1

The following restrictions apply:

• The network timeslot device field (N_) is required.
• The protocol identifier field (P_), if specified, is ignored. The protocol name is unnecessary here because it is selected when using Dialogic Configuration Manager for PCD/FCD file selection. Also, for R4 on DM3 products, all protocols are bi-directional. You do not need to dynamically open and close devices to change the direction of the protocol. For R4 on earlier-generation devices, most protocols are unidirectional.
• The voice channel device field (V_), if set to a value other than the voice device automatically assigned during download, causes the gc_Open( ) command to fail. Voice devices are automatically associated with network devices as part of the cluster configuration during firmware download.

12.3.2. Associating Network and Voice Devices (Fixed Routing)

For R4 applications that use earlier-generation boards, it is possible to open a line device using the gc_Open( ) function, open a voice device using the dx_open( ) function, then use the gc_Attach( ) function to associate the voice device with the line device, using the line device ID and the voice device handle.

For R4 applications that use DM3 fixed routing configurations, this is neither necessary nor possible. A voice device is automatically associated with a line device as part of a DM3 cluster configuration during DM3 initialization. Therefore, the gc_Attach( ) and gc_Detach( ) functions are not supported.

NOTE:

Including a voice device name that is different than the voice device automatically associated with the line device, in the devicename parameter of the gc_Open( ) function returns an error.

12.3.3. ISDN Direct Layer 2 Access (Fixed Routing)

For R4 applications that use a DM3 fixed routing configuration, the gc_GetFrame( ) and gc_SndFrame( ) functions are supported. The DM3 firmware supports direct layer 2 access in DM3 fixed routing configurations.

Click here to contact Dialogic Customer Engineering