Sun GlassFish Communications Server is a Java EE technology-based converged application server combining enterprise service-oriented architecture (SOA) and Web services capabilities with Session Initiation Protocol (SIP) servlets. Used for developing IP-based multimedia applications, Communications Server supports SIP Servletspecifics 1.0 and 1.1 and is compliant with JSR 116 and JSR 289.

Version 2.0 is the latest version, which is now available for download.

NEW FEATURES

SIP Session Replication

This feature enables persistence of SIP sessions for high availability. Companies can now provide continuous SIP application service without any service disruption/downtime using SIP Session replication.

Diameter client

Provides support for sh, Ro, Rf interfaces, enabling easier integration into IMS architecture and facilitating Authentication, Authorization, and Accounting (AAA)

Rolling upgrade

Get enhanced upgrade of a live application server with rolling upgrade, which enables seamless upgrade of SIP application server without any service disruption.

64-bit JVM support

Allows deployment of SIP application server in 64-bit mode so customers can leverage the performance enhancements of the underlying 64-bit infrastructure to meet greater quality of service levels.

Multihome support

This feature gives customers the capability to operate in a multiple NIC environment, providing redundancy within same subnet.

- Overload Protection -

This mechanism regulates SIP traffic to help avoid overload condition by regulating SIP traffic based on CPU and memory consumption.

OTHER FEATURES

Sun GlassFish Communication Server also comes with:

Multi-platform support

It can be deployed on different hardware (X86 and SPARC) and operating systems, including SUSE, Red Hat, Solaris, Windows (developer only) and Mac (developer only).

High Performance and Availability

Communication Server runs on GlassFish Enterprise Server which has set benchmark records based on SpecjAppServer. It is also tuned for low latency and high throughput, enabling the application to grow along with subscriber growth.

Open Source Development

It is based on Project SailFin, the open-source community for Java EE SIP server that includes more than 200 members including independent software vendors, network equipment providers and carriers. The availability of code and development transparency reduces risk of adoption for customers.

- SIP Orchestration -

Built-in application router provides support for simple services composition. Deployers can augment it for special needs by deploying customized routing logic. This feature facilitates development of complex multimedia applications to deliver more functional applications.

- Software Load Balancer -

A built-in converged load balancer provides continuous service availability, awareness of HTTP and SIP session association, and sticky routing of requests based on configurable policies. It supports dynamic clustering, failover, failback and configurable dynamic routing logic based on request headers and overload protection. By eliminating the need to have a hardware load balancer, the total cost of the deployments is reduced.

Simplified Development

Includes SIP annotations that enable rapid development of applications with multimedia functions. The SIP Servlet Wizard offers a simple way to get started with converged communications development through dynamic code generation. Open-source projects like eCharts.org provide other Eclipse-based development tools for developing and testing SIP applications and application routers for GlassFish Communications Server. These capabilities enable easy adoption and integration of multimedia functionality into existing and new Java EE applications.

SIP STANDARDS and RFCs SUPPORTED

Support for standards are critical to ensure interoperability and integrating. The following are supported by Communications Server:

• RFC: 2976 Description: The SIP INFO Method. For more information: http://www.faqs.org/rfcs/rfc2976.html

• RFC: 3261 Description: SIP: Session Initiation Protocol.For more information: http://www.faqs.org/rfcs/rfc3261.html

• RFC: 3262 Description: Reliability of Provisional Responses. For more information: http://www.ietf.org/rfc/rfc3262.txt

• RFC: 3265 Description: Session Initiation Protocol (SIP) - Specific Event Notification. For more information: http://www.faqs.org/rfcs/rfc3265.html

• RFC: 3311 Description: The Session Initiation Protocol (SIP) UPDATE Method. For more information: http://www.ietf.org/rfc/rfc3311.txt

• RFC: 3323 Description: A Privacy Mechanism for the Session Initiation Protocol (SIP). For more information: http://www.faqs.org/rfcs/rfc3323.html

• RFC: 3325 Description: Private Extensions to SIP for Asserted Identity within Trusted Networks. For more information: http://www.faqs.org/rfcs/rfc3325.html

• RFC: 3327 Description: Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts. For more information: http://www.faqs.org/rfcs/rfc3327.html

• RFC: 3428 Description: Session Initiation Protocol (SIP) Extension for Instant Messaging. For more information: http://www.faqs.org/rfcs/rfc3428.html

• RFC: 3515 Description: The Session Initiation Protocol (SIP) Refer Method. For more information: http://www.faqs.org/rfcs/rfc3515.html

• RFC: 3581 Description: An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing. For more information: http://www.faqs.org/rfcs/rfc3581.html

• RFC: 3761 Description: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM). For more information: http://www.faqs.org/rfcs/rfc3761.html

• RFC: 3764 Description: enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record. For more information: http://www.faqs.org/rfcs/rfc3764.html

• RFC: 3824 Description: Using E.164 numbers with the Session Initiation Protocol (SIP). For more information: http://www.faqs.org/rfcs/rfc3824.html

• RFC: 3891 Description: The Session Initiation Protocol (SIP) Replaces Header. For more information: http://www.faqs.org/rfcs/rfc3891.html

• RFC: 3903 Description: Session Initiation Protocol (SIP) Extension for Event State Publication. For more information: http://www.faqs.org/rfcs/rfc3903.html

• RFC: 3966 Description: The tel URI for Telephone Numbers. For more information: http://www.faqs.org/rfcs/rfc3966.html

• RFC: 4028 Description: Session Timers in the Session Initiation Protocol (SIP). For more information: http://www.faqs.org/rfcs/rfc4028.html

• RFC: 3588 Diameter Base Protocol. For more information: http://www.faqs.org/rfcs/rfc3588.html

• RFC: 4006 Diameter Credit-Control Application. For more information: http://www.faqs.org/rfcs/rfc3966.html

TARGET AUDIENCE

GlassFish Communications Server can be used to create a range of simple to complex interactive applications with communications capabilities. With a modular framework built on the top of GlassFish Enterprise Server, GlassFish Communications Server can be used by independent software vendors and network equipment providers looking to create value-added services like presence, IP centrex, IPTV, etc. Carriers deploying GlassFish Communications Server within their service delivery platforms will benefit from high performance and clustering support the platform provides.

More Information

Download

Sun GlassFish Communications Server Product Page

Project SailFin [...read more...]

From the latest issue:

Recent Blog Entries as of March 21, 2010, 8:17 am
Oracle Works to Assuage the Anxieties of Its Customers SysAdmin News Bites Oracle Enterprise Manager Ops Center Released Suits and Their Countersuits A More Direct Channel Model Planned for Oracle-Sun	The Importance of Information Storage and Management Sun POJO Service Engine User's Guide Sun Storage 7000 2010.Q1 Quality and Features PSA Deploys GlassFish in the Manufacture of Peugeot, Citroën Vehicles Running VirtualBox VMs as Services in Windows
Blog RSS Feed