User`s manual

Version 5.4 485 May 2008
SIP User's Manual 10. Media Server Capabilities
The following figure illustrates standard MSCML application architecture:
Figure 10-7: MSCML Architecture
The architecture comprises the following components:
 device: Operating independently, the device controls and allocates its processing
resources to match each application’s requirements. Its primary role is to handle
requests from the Application server for playing announcements and collecting digits.
 Application Server: An application platform that controls the call signaling. It
interfaces with the device using MSCML. It instructs the media server to play
announcements, collect digits and record voice streams.
 Audio Provisioning Server (APS): The APS provides the device with a flexible audio
package that enables users to easily import audio files, define audio sequences, and
include different languages for variable announcement playing.
 Remote Storage: An HTTP server that contains less-frequently used voice prompts
for playback and to which voice stream recording is performed.
 IP Phones / MediaPack: Client applications.
10.2.2.1 Operation
On startup, the device sends a heartbeat packet (a proprietary UDP Ping packet) to the
APS. The IP address of the APS to which the device sends the heartbeat packet is defined
by the parameter HeartBeatDestIP. After receiving the heartbeat packet, the APS scans its
internal database for the IP address (node) of the device (a provision set that includes all
necessary audio data is defined for each node). Once found, the APS sends (over HTTP)
the provision set to the device. The provision set includes two files: the audio package as a
VP.dat file, and an XML file (segments.xml) that contains indices to the announcements
stored on the VP.dat file. The two files are stored on the device RAM and are used for
playing announcements.