AudioCodes Mediant 600 - Page 429

Version 6.4 429 March 2012
SIP User's Manual 20. Configuring the IP Media Parameters
The Application server communicates with the device using MSCML Requests (sent by the
Application server), as shown in the example below:
<?xml version="1.0" encoding="utf-8"?>
<MediaServerControl version="1.0">
<request>
... request body ...
</request>
</MediaServerControl>
The device uses MSCML Responses (i.e., sent by the device) to reply to the Application
server, as shown in the example below:
<?xml version="1.0" encoding="utf-8"?>
<MediaServerControl version="1.0">
<response>
... response body ...
</response>
</MediaServerControl>
To start an MSCML IVR call, the Application server (or any SIP user agent) sends a regular
SIP INVITE message with a SIP URI that includes the MSCML Identifier name. For
example:
INVITE sip:ivr@audiocodes.com SIP/2.0
The left part of the SIP URI includes the MSCML Identifier string ‘ivr’, which can be
configured using the ini file (parameter MSCMLID) or Web interface (see 'Configuring the
IPmedia Parameters' on page 411).
After a call is established, SIP INFO messages are used to carry MSCML requests and
responses. An INFO message that carries an MSCML body is identified by its content-type
header that is set to ‘application/mediaservercontrol+xml’.
Note that IVR requests are not queued. Therefore, if a request is received while another is
in progress, the device stops the first operation and executes the new request. The device
generates a response message for the first request and returns any data collected up to
that point. If an application is required to stop a request in progress, it issues a <Stop>
request. This request also causes the device to generate a response message.
The device supports basic IVR functions of playing announcements, collecting DTMF
digits, and voice stream recording. These services are implemented using the following
Request and Response messages:

<Play> for playing announcements

<PlayCollect> for playing announcements and collecting digits

<PlayRecord> for playing announcements and recording voice

<Stop> for stopping the playing of an announcement
The device sends a Response to each Request that is issued by the Application server.
The <Play>, <PlayCollect>, and <PlayRecord> messages are composed of two sections:
Attributes and a Prompt block (the request can contain several different Prompt blocks).
The Attributes section includes several request-specific parameters. The Prompt block
section itself is also composed of two sections: prompt-specific parameters and audio
segments (audio / variable). The (optional) prompt-specific parameters include:

locale: defines the language in which the prompt block is played (supported for local
files only). For more information on language usage, refer to the Audio Provisioning