System information

30 Dialogic
®
HMP Software Release 3.0WIN Release Guide — December 2010
Dialogic Corporation
Features
media streaming between their four analog interfaces and HMP; however, they have no
CT Bus connectivity.
Note: The Dialogic
®
D/4PCIU board will not function with any other board in the system, and
must be the only board in the system. This is a permanent, stand-alone restriction.
The Dialogic
®
D/80PCIE-LS Media Board is a full-length PCI Express form factor, eight-
port, full-featured JCT board. In addition, it provides media streaming between HMP and
its eight analog interfaces and eight on-board voice devices.
The following sections provide information specific to using these Springware products
with HMP software.
3.8.1 Bridge Device
The analog devices, like other Dialogic
®
HMP interface boards, have a bridge device that
enables media streaming between HMP and the board. The boards have their bridges
enabled by default.
With the Dialogic
®
D/80PCIE-LS board, both the board’s analog interfaces and on-board
voice devices are connected to the CT Bus. The CT Bus provides the fabric for intra-board
connectivity or, in the case of other CT Bus boards in the system, for inter-board
connectivity. In addition, the bridge device can be used to stream media to and from HMP.
Traditional CT Bus routing and HMP streaming are accomplished using the standard run-
time routing APIs. On-board voice and analog interface half-duplex streaming connections
from HMP media and IP media devices are performed using the Voice API TDM Routing
functions. HMP half-duplex streaming connections from on-board voice and analog
interface devices are performed using the traditional TDM Routing APIs for their
respective technologies.
Alternatively, half- or full-duplex bridging connections between HMP and bridge-capable,
on-board devices on these analog-interface boards can be accomplished using the
Dialogic
®
Device Management API function dev_Connect( ). On analog boards, the SRL
device handle has the dual purpose of acting on either the proper voice device, or the
analog-interface device. In order to differentiate analog voice devices from analog front-
ends, a new connection type value, DM_ANALOG_INTF, is added to the dev_Connect( )
function’s connType parameter. This value specifies that the Springware voice device
handle passed as either devHandle1 or devHandle2 is treated as an analog front-end.
For example, DM_ANALOG_INTF needs to be ORed with either DM_FULLDUP or
DM_HALFDUP for the application to consider the analog voice device passed to
dev_Connect( ) as an analog front-end. If DM_ANALOG_INTF is not ORed, then the
analog voice device will be considered a voice device.
Note: The dev_Disconnect( ) function must be called to break a connection made using the
dev_Connect( ) function before a new connection can be established.
The following connections are supported: