This section provides an overview of the Java Specification Request (JSR) 309 and describes the JSR 309 Connector features and limitations.
A brief description of terminology used in this document is provided for reference.
Servlet – A Java class which conforms to the Java Servlet Interface, by which a Java class may respond to HTTP requests. Applications using servlets may be packaged in a WAR file as a web application.
Java Specification Request (JSR) – A formal document created by members of the Java Community Process (JCP) that adds features and functionality to the Java platform.
JEE or J2EE – Java Platform, Enterprise Edition. A platform for server programming in the Java programming language.
Web Application Server – Application Server based on JEE or J2EE.
MSML – Media Server Markup Language.
OCCAS – Oracle Communications Converged Application Server.
Conference Control Leg – This terminology describes when a conference is created using a mixer component and the mixer is configured to create a conference control leg. A conference control leg requires the use of one connection resource from the Media Server.
No Conference Control Leg – This terminology describes when a conference is created using a mixer component and the mixer is configured to not create a conference control leg. In this case, the JSR 309 Connector uses the call legs to send conference configuration. Therefore, it does not require a Media Server resource.
Java Specification Request (JSR) 309 is a standard Java media server control API for multimedia application development. It provides a generic media server abstraction interface that is independent of the underlying media server control protocol. The multimedia applications, such as IVR, voice-mail, audio conferencing, and call center, are typically deployed in a SIP-based infrastructure.
The JSR 309 API provides three areas of functionality:
Network connection to establish media streams.
Media group functions such as to play, record, and control media content.
Media mixer functions to join media functions to a network connection so as to create conferences and call bridges.
For details on the JSR 309 API, see the documentation on the Java Community Process website at www.jcp.org.
For a list of JSR 309 API parameters supported by the JSR 309 Connector, see Supported Configurations.
The JSR 309 Connector is the Dialogic implementation of the JSR 309 version 1.0 final specification. This software runs on application servers such as the OCCAS and enables a multimedia application on the application server to control the PowerMedia XMS using the JSR 309 API.
The following figure illustrates the role of the JSR 309 Connector in a typical deployment.
The following components are included in this figure:
J2EE Converged Application Server – Handles SIP call control and other aspects of real-time multimedia communications using a Java EE environment with JSR 289 support.
Application – Runs on the J2EE Converged Application Server. Examples of applications: IVR, conferencing, announcements, and call centers.
JSR 309 Connector – Software connector that enables the J2EE Converged Application Server to control PowerMedia XMS through JSR 309-compliant API calls.
PowerMedia XMS – Performs the multimedia operations required to establish and maintain real-time communications while providing a high-quality user experience.
External Servers – Used for storing and streaming multimedia content.
SIP Servlet API for Call Handling – SIP stack used to communicate with SIP compliant user agents. JSR 289 is the standard API servlet used by Converged Communication Application Servers.
The JSR 309 Connector is designed to support an asynchronous programming model. Applications using the connector should be designed to interface using Listener objects for events on operation completion.