As stated earlier, Media Server Node has a corresponding Connector in SDSE available to application scripts that uses SIP protocol with embedded MSCML messages in SIP body to communicate with Media Server Nodes. It exposes a rich set of API to applications for different Media related tasks described in Media Server Node section.


The Media Engine’s current version supports the following primitive commands and events for Media Server as specified in RFC 4722. Details can be found in the RFC document:


Configure conference

  • Creates and configures a new conference in Media Server. Even a single leg call that only has to play a pre-stored file to a user s created inside a conference container. Similarly, two way standard call between two users is also created in a conference container. This ensured general handling of one way, two way or N-way calls in a uniform manner.

Configure Conference Leg

  • Adds a new call leg to an existing conference


  • Plays a specified file to the specified call leg in a conference

Play Collect

  • Plays a specified file to the specified call leg in a conference and collects DTMF digits from the user


  • Records an incoming media stream on a call leg or conference leg into a specified file.


  • Plays a prompt and records an incoming media stream on a call leg in a specified file.


  • The <prompt> element MAY be included in the body of a <play>,<playcollect>, or <playrecord> request to specify a prompt sequence to be delivered to the caller.  The prompt sequence consists of one or more references to physical content files, spoken variables, or dynamic URLs that return a sub-sequence of files or variables.  In addition, the <prompt> element has several attributes that control playback of the included content.

Copyright All Rights Reserved 2006 to 2013 @ Media Routes Inc