System information

Dialogic
®
HMP Software Release 3.0WIN Release Guide — December 2010 31
Dialogic Corporation
Features
Analog Front-End and CNF Audio Conference Party
A full-duplex or half-duplex connection between an audio conferencing party device
(CNF API) and a Springware front-end device on board. Requires a valid audio
conferencing party device handle obtained through the cnf_OpenParty( ) function
and a valid voice device handle obtained through the dx_open( ) function. Both
synchronous and asynchronous modes are supported. In the half-duplex connection,
either type of device can listen to the other.
Springware Voice and CNF Audio Conferencing Party
A full-duplex or half-duplex connection between an audio conferencing party device
(CNF API) and a Springware voice device on board. Requires a valid audio
conferencing party device handle obtained through the cnf_OpenParty( ) function
and a valid voice device handle obtained through the dx_open( ) function. Both
synchronous and asynchronous modes are supported. In the half-duplex connection,
either type of device can listen to the other.
Analog Front-End and HMP Voice Device
A full-duplex or half-duplex connection between a HMP voice device (Voice API) and
an analog front-end device on board. Requires a valid HMP voice device handle
obtained through the dx_open( ) function and a valid analog voice device handle
obtained through the dx_open( ) function. Both synchronous and asynchronous
modes are supported. In the half-duplex connection, either type of device can listen to
the other.
Notes:1. Do not use the dev_Connect( ) function to connect two on-board devices. One of the
device handles passed to the function must me an HMP device. If two analog device
handles are passed to dev_Connect( ), the function will return an error.
2. The dev_Connect( ) function does not support analog device connections to or from
any HMP device other than a CNF device.
3.8.2 D4PCIU Board Restrictions
The D4PCIU board does not have an onboard CT Bus. The board is capable of routing
host-based HMP resources to and from the analog front-end interface using the HMP soft
Bus. Each analog front-end interface establishes a permanent bridge connect to a unique
HMP soft Bus in the board-to-HMP soft Bus direction as returned by the
ag_getxmitslot( ) function on the associated voice device. In the HMP soft Bus-to-board
direction, an ag_listen( ) function invoked on the associated voice device is responsible
for routing from an HMP soft Bus time slot via a bridge connect. The routing can be
removed by a disconnect resulting from the ag_unlisten( ) function.
On the D4PCIU board, the ag_unlisten( ) function has a dual-purpose functionality.
Before it can create a bridge from HMP resources, it must first break the transmission of
audio from the analog front-end’s associated voice device. This is because an analog
channel can either receive audio from the HMP soft Bus bridge or the associated voice
channel. Conversely, the ag_unlisten( ) function not only breaks a previously existing
bridge from HMP resources, but it also switches back on-board audio transmission from
the analog front-end’s associated voice device. Therefore, before a new analog call can
be processed by the analog front-end interface, the ag_unlisten( ) function must be