• 3.8.1.  gc_OpenEx( ) with Springware Boards
• 3.8.2.  gc_OpenEx( ) with DM3 Boards

3.8.  gc_OpenEx( )

The gc_OpenEx( ) function opens voice channels, voice devices, or analog loop start interfaces. The following sections describe using gc_OpenEx( ) with Springware boards and with DM3 boards.

3.8.1.  gc_OpenEx( ) with Springware Boards

For Springware boards that host both voice devices and analog loop start interface devices, both the voice device and its associated analog loop start interface device are opened as a single channel. A single line device ID (LDID) identifies both the voice channel and the analog loop start interface.

A voice channel, voice device, or analog loop start interface device is specified by the devicename parameter using a format that includes the following information:

:P_<protocol_name>:V_<voice_channel_name>

where:

• <protocol_name> specifies the analog loop start protocol. Use the root file name of the analog protocol file (for example, na_an_io) for your country or telephone network.
• <voice_channel_name> specifies the name of the voice channel, voice device, or analog loop start interface device to be associated with the device being opened. Use the following format for the voice device:

dxxxB<virtual board number>C<channel or device number>

The prefixes (P_ and V_) in devicename are used for parsing purposes. The order of input of these parameters may be set by the application. The fields within the devicename parameter must each begin with a colon.

The following example illustrates the format for defining the devicename parameter for various voice and analog loop start interface devices when processing analog calls.

To open voice channel 2 on a D/160SC-LS board identified as virtual board 3:

:P_na_an_io:V_dxxxB3C2

Global Call automatically opens both voice device 2 and analog loop start interface device 2 on virtual board 3 and internally attaches the voice device to the analog loop start interface.

NOTE:

When using analog protocols (ANAPI or PDK), opening a board device, that is, using only the board number in the devicename parameter (for example, :V_dxxxB1) is not supported.

3.8.2.  gc_OpenEx( ) with DM3 Boards

On DM3 analog boards, the voice devices and the analog loop start devices are separate devices. When calling gc_OpenEx( ), the application can either open only the analog loop start device, or open both the analog loop start interface device and the voice device at the same time. The device(s) is specified via the devicename parameter using a format that includes the following information:

:P_<protocol_name>:N_<loop_start_device_name>:V_<voice_channel_name>

where:

• <protocol_name> can be any string. :P_ must be present, but the name of the protocol does not matter, as the protocol is embedded in the firmware and cannot be changed.
• <loop_start_device_name> specifies the name of the analog loop start device to be associated with the device being opened. Use the following format for the loop start device:

dtiB<virtual board number>T<channel or device number>

• <voice_channel_name> specifies the name of the optional voice channel to be associated with the device being opened. Use the following format for the voice channel name:

dxxxB<virtual board number>C<channel or device number>

The prefixes (P_, N_, and V_) in devicename are used for parsing purposes. The order of input of these parameters may be set by the application. The fields within the devicename parameter must each begin with a colon.

The following example illustrates the format for defining the devicename parameter for various voice and analog loop start interface devices when processing analog calls.

To open loop start device 2 on a DMV160 board identified as virtual board 1 along with voice device 1 on virtual board 2:

:P_dm3an:N_dtiB1T2:V_dxxxB2C1

Global Call automatically opens both the analog loop start interface and voice device and internally attaches the voice device to the analog loop start interface.

The voice device could be opened later using the dx_open( ) function and then attached to the Global Call device using the gc_AttachResource( ) function. The application would have to manually route the resources together. Without a voice device attached to the Global Call device, no outbound calls can be made as there will be no resources to dial digits.

Click here to contact Telecom Support Resources