Find JSRs
Submit this Search

Ad Banner

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 79: JAINTM MEGACO API Specification

Stage Access Start Finish
Final Release Download page 06 Dec, 2004  
Final Approval Ballot View results 17 Feb, 2004 01 Mar, 2004
Proposed Final Draft Download page 27 May, 2003  
Public Review Download page 24 Oct, 2002 23 Nov, 2002
Community Draft Ballot View results 03 Sep, 2002 09 Sep, 2002
Community Review Login page 02 Aug, 2002 09 Sep, 2002
Expert Group Formation   12 Sep, 2000 06 Jun, 2001
JSR Review Ballot View results 29 Aug, 2000 11 Sep, 2000
Status: Final
JCP version in use: 2.1
Java Specification Participation Agreement version in use: 1.0

This work will specify the JAINTM API through which access to protocol stacks that support the MEGACO/H.248 protocol may be achieved.

Please direct comments on this JSR to the Spec Lead(s)

Specification Leads
  Vikas Bajaj Hughes Software Systems
Expert Group
  Hughes Software Systems Nokia Corporation Sun Microsystems, Inc.

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Hughes Software Systems Ltd.

Name of Contact Person: Vikas Bajaj

E-Mail Address:

Telephone Number: +91-124-6346666 (x2804)

Fax Number: +91-124-6346530

Specification Lead: Vikas Bajaj

E-Mail Address:

Telephone Number: +91-124-6346666 (x2804)

Fax Number: +91-124-6346530

Initial Expert Group Membership:

AePONA, Ericsson, Radvision, Sun Microsystems, Inc., Nortel Networks

Section 2: Request

2.1 Please describe the proposed Specification:

This JSR is to develop the JAIN APIs for the MEGACO protocol.
It will describe the Java API for call control in the Telecommunications
and Internet industry.

The MEGACO/H.248 is a new protocol belonging to the Gateway Control
class of Protocols. It is a protocol proposed jointly by IETF and ITU-T that
specifies the syntax and semantics of messages that are used by the
Call Agent (alternately called as the Media Gateway Controller in the
Decomposed VoIP Gateway architecture terminology) to control
and thereby establish media connections in a Gateway (alternately
referred to as the Media Gateway in the Decomposed VoIP Gateway
Architecture terminology). The protocol defines a model for the Gateway
comprising objects called as Contexts and Terminations and defines APIs
by which the Call Agent can manipulate these objects within the Gateway.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

The JAIN MEGACO Specification is targeted towards Telephony over Internet
Protocol (IP) networks.Therefore, the platforms on which the APIs are expected to be used may
be desktops, servers or embedded cards.

2.3 What need of the Java community will be addressed by the proposed specification?

The JAIN MEGACO Specification defines an API which allows for the rapid
creation and deployment of dynamic telephony services into a Java telephony
platform. Standard Telephony applications require costly resources to
develop, test, and deploy. A JAIN MEGACO component can be rapidly
developed, tested, and integrated on a variety of platforms with access to
numerous tools and utilities. A JAIN cross-platform solution gives the
Carriers, Service Providers, and Network Equipment Providers a consistent,
open environment where they can develop and deploy portable telephony

2.4 Why isn't this need met by existing specifications?

The MEGACO/H.248 protocol is a new protocol that has come into formal
existence very recently. The protocol is unique in the type of functionality that it
addresses and does not have an overlap with any other protocol. There does not
currently exist any Java specification that addresses this protocol.

2.5 Please give a short description of the underlying technology or technologies:

The JAIN MEGACO Specification is based on underlying MEGACO/H.248 protocol
stacks supplied by the JAIN JSPA members and on other third-party MEGACO
protocol stack implementations. The purpose is to provide a ubiquitous, standard
interface into MEGACO protocol stacks.

A JAIN MEGACO application can be written as a program, applet, servlet, or
bean. The JAIN MEGACO API encapsulates the functions of the MEGACO
protocol and abstracts the protocol with a standardized Java interface, so that
call-processing applications can readily communicate with Voice over IP gateways.

While no dependency on Java visual tools for constructing JAIN MEGACO
components is assumed, the use of a Java Bean Manager and/or visual Java
bean builder can be a significant aid in the development, integration, testing,
and deployment of a voice-over-IP network that employs JAIN MEGACO

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

Package names being considered are:
This package contains the main interfaces, classes, and exceptions
required to send and receive MEGACO messages.
This package contains the interfaces, classes, and exceptions
representing the Session Description Protocol (SDP), as specified in
RFC 2327, used by MEGACO. It needs to be explored how this
package has been used by the JAIN MGCP & SIP APIs and if
a consistent scheme can be evolved for the use of this package.

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

No, The proposed specification does not have any dependencies on specific operating systems,
CPUs, or I/O devices.

2.8 Are there any security issues that cannot be addressed by the current security model?

None. JAIN SIP expects to utilize standard JDK security.

2.9 Are there any internationalization or localization issues?

Because JAIN SIP is based on IETF specifications, the API can be readily adapted to all markets.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

None of the existing specifications are expected to get affected by these specifications.

2.11 Please describe the anticipated schedule for the development of this specification.

The anticipated elapsed time for the development of this specification is about nine months after
approval of JSR.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

The specification document for MEGACO/H.248 on which these APIs will be based is the
IETF draft draft-ietf-megaco-merged-01.txt. This is draft obtained by the merger of
draft-ietf-megaco-protocol-08.txtand draft-ietf-megaco-errata-03.txt.All these drafts are available
on the IETF site A related site where MEGACO related information is available

3.2 Explanation of how these items might be used as a starting point for the work.

Since the JAIN MEGACO APIs shall be based on the MEGACO protocol standard, the above listed documents will form the starting point for the work.