2. Empowering SIP Applications with J2EE Technology Marcelo Oliveira & Sudhrity Mondal Principal Architects, BEA Systems
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16. VoIP using J2EE IVR/Speech Voicemail Quality Monitoring ACD CTI IP Network Customer Data Mart Applications Order Mgmt Trouble Ticketing SIP (JSR 116) J2EE Platform Network Resources not standalone apps JSP IIOP JMS JTS JNDI JAAS EJB JCA JDBC JMX PSTN Mobile 2G/3G Phone Fixed Phone Web Application CRM Billing Soft Phone CSR CSR Desktop IP IP Media Gateway Management Console
17.
18.
19. J2EE SIP Application Enablement J2EE Enablement User Agent User Agent User Agent User Agent Web Browser Web Browser Web Browser Web Browser SIP SIP HTTP HTTP Media Processor Media Processor Media Processor Media Processor Media Processor Generic Load Balancer Generic Load Balancer SIP Conferencing Application Conferencing Application Conferencing Application MGCP / MEGACO User Agent User Agent User Agent User Agent Web Browser Web Browser Web Browser Web Browser SIP SIP HTTP HTTP Proprietary SIP / HTTP Load Balancer SIP / HTTP Load Balancer Web Server Web Server Web Server Multipoint Controller Multipoint Controller Multipoint Controller Media Processor Media Processor Media Processor Media Processor Media Processor
20.
21.
22. SOA for VoIP Services Enterprise Service Bus IT Network Core Network J2EE Application Server Billing Web Service Access Service Creation & Orch. EAI Broker BPM J2EE Application Servers Portal Content Personal SIP SIP Servlets HTTP Servlets HTTP Network Adapters Telephony Messaging Video Policy OA&M Access Control Partner Management EJB’s
Extremely Thorough and Complex Architecture Managed by 3GPP and 3GPP2 Hundreds of documents Entirely packet based, using SIP as the signaling protocol Defines a whole new set of servers and applications Driver for Fixed / Mobile / IP convergence Opportunity to increase ARPU New cutting edge services Telephony applications and services look more like HTTP applications
Voice over IP applications can be separated into two distinct planes: Signaling and Media
- Used by the signaling plane to communicate and act over the elements on the media plane - MGCP and MEGACO [H.248] have dominated the telecom market as the protocols of choice for media gateway control - Media server are pushing for alternative XML based media server control protocols to simplify the development of media reach VoIP applications. Some examples are: MSCML MSML/MOML In this presentation we will focus on MSCML
- Used by the signaling plane to communicate and act over the elements on the media plane - MGCP and MEGACO [H.248] have dominated the telecom market as the protocols of choice for media gateway control - Media server are pushing for alternative XML based media server control protocols to simplify the development of media reach VoIP applications. Some examples are: MSCML MSML/MOML In this presentation we will focus on MSCML
VoIP enables an extensive new set of applications and revolutionizes some of the traditional ones
As most of the traditional development in this area is done in C/C++, an initial decision on what HW/SW platforms will be supported has to be made
User & Management Interfaces High efforts required for proper integration with application Application Scalability Defining a scalable architecture is time consuming Testing all possible deployment scenarios Application Fault Tolerance A lot of time is spent on defining and validating a fault tolerant architecture Disconnection between Web Tier and Application Complex redundancy strategies for high availability Limited failover capabilities Mostly relying on expensive platforms
Integration with other applications The technology used for creating the applications can be a major obstacle for integrating with other systems or applications like: Databases Web Services Enterprise Information Systems Reusability Many companies do not have the resources to spend on creating reusable components for their applications Normally every new application faces the same challenges
The SIP Servlet API Specification – JSR 116 defines a high-level extension API for SIP servers. It enables SIP applications to be deployed and managed based on the J2EE servlet model.
Transparent state sharing between SIP and HTTP sessions Simplified Media Gateway Control Transparent Server Redundancy for high availability Transparent fail-over capabilities No need for a SIP aware load balancer.