Technical data

The Combined Board is named M-Board in the web interface.

• With the Internal Call Transfer, an application can forward a call to another application. It is possible for

application manufacturers and developers to detect the characteristic of a call (Fax, Voice, Modem, etc)

and forward the call to another, compatible application. This is required if a solution is splitted into

multiple single applications. This feature is especially relevant for application developers. For further

documentation, contact the Dialogic Support team.

• With the Call Transfer Emulation (ECT Emulation), an application can initiate a Call Transfer at a high

level call control API (e.g., CAPI, Dialogic

Diva

SDK, TAPI, etc.). The M-Board can emulate a regular

Call Transfer behavior at the upper interface (Call Transfer result and disconnect towards the application)

while the Diva Media Board bridges the two channels together, also known as tromboning. This helps if

the switch does not support Call Transfer or if it is required to bridge a gap between the Call Transfer

start and completion (board stays connected until the switch completes a Call Transfer). This feature can

be configured in the Board Configuration page under ECT Emulation.

Note: Line Interconnect is not supported for Diva Media Boards grouped in an M-Board.

• Support for advanced call routing

• Support for Dialogic

DSI SS7 APIs

• Support for the Dialogic

Diva

Software Development Kit (SDK)

• Support for high efficient parallel Dialogic

Diva

Media Board loading procedure

• Support for running TAR archives in embedded systems without using the package manager

• The Dialogic

Diva

TTY driver is available as open source

• Support for 64-bit systems (A 64-bit system is recommended, if various Diva Media Boards should be

operated in one system.)

Note: The Dialogic

Diva

softIP for SIP software is only supported on 32-bit systems.