Overview

Media Routes Cloud Communications Infrastructure (CCI) is a comprehensive development, execution and policy enforcement framework for a variety of Communications Applications ranging from enterprise to consumer markets.

 

CCI enables Service Providers and Enterprises to acquire a complete, working infra-structure for Enterprise Communications, hosted on premises or in the Cloud. CCI thus supports public, private and hybrid Cloud models.

 

CCI has been designed from the ground-up to provide the well-known best practices of a Cloud based infrastructure in other domains like Compute, Web-services hosting and Application Hosting. It is dynamically scalable on the fly by adding computation resources to communications applications.

 

CCI Architecture and Components

CCI is comprised of two Media Routes products:

  • SOFTWARE DEFINED SERVICE ENGINE
  • Session Border Controller
    • Access Session Border Control
    • Peering Session Border Control

 

SOFTWARE DEFINED SERVICE ENGINE (SDSE)

This is the core execution environment that runs communications applications. It is internally composed of multiple components. It is scalable by merely adding software processes in a seamless manner.
SDSE consists of the following components:

 

Application node (AN)

These are software processes that run communications applications written in the form of scripts. Media Routes provides a variety of full working and tested enterprise applications with an associated data model and database schema. Applications running on AN are programmed in one of the two scripting languages:

  • The universally well-known JavaScript
  • CCXML (a W3c standardized language) in combination with JavaScript

Service API

SDSE exposes a rich set of API (Application Programming Interfaces) for script-based application developers. These are primitive operations for different tasks that a typical application may require. Examples include creating and receiving telephony calls, playing and recording media files, creating conferences, Authentication Authorization and Accounting, database access, web-services access etc.

 

Protocol Connectors

SDSE consists of several protocol stacks. These stacks are called “Connectors” since they connect the system to external client and server applications on these protocols. Each Connector exposes its own service API to script-based applications in the form of primitive operations described above. Conversely, each service API is owned and provided by one Connector. The list of Connectors is ever-growing as more protocols are added to SDSE on a regular basis according to Media Routes roadmap. The currently supported connectors include:

    • SIP
    • HTTP (with RESTFUL API support)
    • RADIUS (as a client)
    • DIAMETER (as a client)
    • Database access (supports Stored Procedure calling for both MySQL and Oracle)
    • XML over socket
    • Media Handling (MSCML over SIP)

Media server Node (MN)

These are software processes that run the server application that handles media. Media Server has a corresponding Connector in the SDSE available to Application scripts that exposes its own set of service APIs for media handling. Media Connector communicates with Media server Node using standard SIP protocol with a standardized XML based language called MSCML (Media Server Control Markup Language) embedded in the body of SIP INFO messages. As a result of separate Media serving nodes, Media handling, which is typically more CPU intensive can be scaled and distributed across multiple CPU cores, multiple physical servers, and even geographically distributed servers in isolation from the other parts of SDSE such as Applications nodes.
Media handling involves all media related tasks such as:

  • Media Relaying and Proxy
  • Media Trans-Coding
  • Multi-party Conference handling
  • Media Recording
  • Collection of user entered digits during multi-media sessions as DTMF
  • Playing of Pre-stored Media files for use cases such as:
    • Ring-back tones and Dial tones
    • Announcements
    • IVR prompts and menus
  • Handling of incoming Fax
  • Video Relaying

Session Border Controller (SBC)

This is the core infrastructure enabler that handles all concerns of the Enterprise or Service Provider’s domain border. SBC provides many unique features and services. Some of the key features of SBC include:

  • Load Balancing across Application Servers
  • Access Network side Policy Enforcement
  • Peering Network side Policies and Routing
  • SIP Registrations and Registrations Pass-through
  • Capability to Monetize several Infrastructure properties
  • Programmability on the fly through scripting to enhance its functionality and implement new policies and features

More information on SBC can be found at:
http://www.mediaroutes.com/Session-Border-Controller.html

  


Copyright All Rights Reserved 2006 to 2013 @ Media Routes Inc