Mobicents Blogs

Mobicents SIP Load Balancing

Vladimir Ralev — Mon, 26 Oct 2009 12:51:00 -0700

Check out our SIP Load Balancing (SIP LB) designs and deployment scenarios.

Our goal is to support as many scenarios as possible in a simple way and maintain flexibility for future enhancements and custom load balancing. We look at the load-balancer as a platform where you can implement your own routing decision logic - distributed or standalone, stateful or stateless, layer 3/4 or layer 7, it is all up to you.

The new load balancer provides quite a few improvements on top of the old one:

Performance (>1000 cps, but depending on the algorithm)
Flexibility - pluggable algorithms and customizable algorithms
Fault Tolerance - multiple smart SIP LBs can work together and nterchangeably in case of failure when sprayed by "dumb" IP load balancers
Cooperative Load Balancing - very often, mutliple protocols and sessions are involved in a telco service. Then you need to group calls, HTTP or other protocol sessions to stick together and be failed-over together. Only your application knows the right way to group these sessions, thus sometimes it is crucial to delegate load-balancing decisions to your application. Now, you could implement your own algorithms that take hints or instructions from the applications.

For more details you can look at these slides:

Feedback is welcome!

UPDATE: Revised November 1st, 2009

Mobicents Diameter v1.1.0.GA Released!

Alexandre Mendonça — Sat, 17 Oct 2009 18:25:00 -0700

It was on Friday, 16th October 2009 that a shiny new release of Mobicents Diameter happened.

It's v1.1.0.GA and along with the usual enhancements and bug fixes, the main new features are:

JBoss AS 5 support
Stack configuration at runtime, via JMX
Educative Example for Cx/Dx application
Preview of the Mobicents Diameter User Guide

It can be downloaded from here: Mobicents Diameter v1.1.0.GA Downloads

Please note that the JBoss 5 version zip contains only the Stack and the Multiplexer, no JAIN SLEE Resource Adaptors or Examples are included. If you want to try the new Mobicents JAIN SLEE 2.x version (which runs on JBoss 5) and it's Diameter Resource Adaptors and Examples, you'll need to build them from source, which can be found in the SVN trunk.

Summing it up, you now get a more stable Diameter in 2 flavors (JBoss 4 & JBoss 5), the ability to configure the stack in realtime (add/remove realms, add/remove peers, manage timeouts, etc...), a new example of how to play with Cx/Dx (which will be the basis for the HSS prototype) plus the user guide to help you play with all of it!

A special thanks to Jared Morgan and Tom Wells for the extra effort on the documentation!

Introducing Mobicents IPBX

Vladimir Ralev — Tue, 13 Oct 2009 21:29:00 -0700

Many Mobicents community users are already familiar with IPBX, which is complete (and open-source) Media PBX with rich Web User Interface, but it's been on the background for some time due to higher priority tasks. Now with the increased community feedback, we present the new version of IPBX 1.0 CR, which is stable and covers a number of real use-cases. I cannot not mention the guys from Manaty for their help testing the IPBX and finding/solving a number of problems. But I want to thank all users who gave feedback and reported their experiences.

For those who are new to IPBX - this is a converged application (meaning it serves several protocols HTTP, SIP, Media/RTP) and as such it provides integrated experience acrosss several technologies. Let's see this short video of what the application really does:

What we see here is users authenticating against the application over HTTP and SIP protocols from Web browsers and SIP Phones respectively. They use the same credentials for both HTTP and SIP, the sessions are related to each other by the users and the state of the calls can be displayed in the Web browser of particular users. Moreover, when users call each-other they participate in the same calls, thus many users may want to see the state of the same call or conference bridge - the IPBX provides that as well.

Once you are in a call, you can invite more people in a conference, or you can remove participants. When you need to type something, use the conference chat. All participants in the conference will see the messages. The video also shows a function known as call parking, which allows you to transfer a call from one phone to another.

There are many things not shown in this video. When you are getting started you should take a look at the administrative panels (log in as admin/admin). Three important features there:

PSTN Accounts - allows you to call PSTN phones such as mobile and landline phones through a PSTN gateway service provider
PBX Settings - allows you to configure the PBX behaviour, the system announcement files, calling prefix, etc
User Administration - you can edit the user accounts from here

It is important to note that once configured, the PBX can operate without any Web User Interface. If you like you can register your phones blindly and start making calls by dialing peers or PSTN numbers (with the prefix). The SIP and Web parts of the application, although implemented by the same application logic can operate independently and still catch-up with each other if you want to log in from the Web UI.

On the technical side, this application was implemented on top of Mobicents Sip Servlets 1.0 for JBoss AS 4.2.3, Seam Telco Framework 2.2, JBoss Seam and Richfaces with JBoss Developer Studio and Mobicents Eclipse Plugins.

I really hope this project to gain more developer community interest to help us build the next features on the roadmap. Right now the following features are planned for the near future:

Recording calls
Better UI
Voicemail
Multiline calls

There are certainly a lot of other features we'd like to add, and if you have other ideas they are more than welcome.

There are few other videos, but I will just add this one for the Linux users with another set of phones:

Finally, some links:

Download - the war and the xml files must be deployed on Mobicents Sip Servlets 1.0 JBoss 4.2.3, which can be downloaded from here.
Source Code
IPBX Project Homepage
Mobicents Homepage

Enjoy!

Time to change your OS?

EDUARDO MARTINS — Wed, 07 Oct 2009 09:52:00 -0700

UNIX mixed with an easy to use UI, in a well controlled hardware environment, I must say I'm a Apple OSX fan since day 1 after change (well not quite, the Apple keyboard scheme was hard to digest)!

Now when Snow Leopard was announced with zero new features, I said to myself that an upgrade was not really a must, but since I'm fan of it how could I not do it?!?

And the upgrade was made, and with that came the "JDK6 only" world for Java, not surprising since JDK5 EOL is near. What really surprised me was the performance, simply amazing, see the screenshot below of a standalone JAIN SIP Reference Implementation application load test for a simple call setup, terminated at application side after 60s, running at 450 CPS in a 2 and half year old Macbook Pro laptop.

Wow! Is it time to change/upgrade your OS? :-)

Amazing OKI Technology

Vladimir Ralev — Mon, 05 Oct 2009 21:32:00 -0700

Last week, I visited OKI, a major japanese telecom product vendor, to help creating a better technical relationship for the telecom vertical between OKI and Red Hat JBCP team. Along with our technical meetings I got to see one of their new products in action.

It's no secret that Japan is way ahead in many IT&Telecom fields. New things are developed fast and pushed to the market quickly. As a result, the people I see on the streets are almost always "on the phone" - looking the the screen, pressing some buttons or waving the phone around. I quickly learned that the phones usually come with tons of apps and services that make you stick around such as built-in contact-less e-wallets chips, bar-code readers, TV (the Japanese TV is crazy!) and what not. I don't even mention the browsers and all the internet/IP services here. You can walk through the subway doors with the phone in your hand and the ticketing transactions occur automatically. You can scan some QR code to pick up information about items in the store, on the street or elsewhere.

Obviously, when you create a new service here, you can leverage a lot of unique infrastructure, but the Japanese market is massive and very saturated and staying on top is a real challenge.

The new product from OKI is up for the challenge. It is an advanced platform for a variety of services delivered in a unique integrated and rich user interface. Basically you call a number, it turns out the service you dialed supports streaming the enhanced user interface and your phone picks it up. Your TV, PC or other devices at home can join the service session and show you visually the current menus in the service or the results of your operations. The feedback from the system is both audio and video updated accurately in real time on all devices in the session. With your voice you can navigate through the menus or ask operations to be executed. You could use DTMF to enter a password or a code privately in case you don't want to speak out confidential information to feed the system. One of the coolest features is that if you are not at home, you could use some nearby ATM or other kiosk in Japan as a display. So, you are walking on the street and you just literally tell your phone to move the visualization to the kiosk and it's there. Additionally, kiosk and other devices may have more UI controls such as touchscreen, keyboard or a mouse. Within your service session you can use the extra controls for input. The OKI team allowed me to blog about this omitting some details and features. They put a lot of attention to details in the UI and interop interfaces, and some are really worth keeping secret :)

One of the example services implemented on top of the platform is ordering food for a family. You go through the usual steps - identifying yourself, searching for a particular type of food, selecting a restaurant, going through the menu, examine additional options, ask questions, make your order and then confirm the payment. On every step of the order the platform adds something unique to the UI that couldn't be done otherwise especially when it comes to ordering for a group of people or while on the go.

I think along with the typical customer services this platform can be useful for a number of office or enterprise applications - collaboration tools, e-meeting tools, online business workflow and so forth.

This is just one of the mind-blowing things I've seen in Japan, which is truly a very special place on Earth in every aspect. I will try to cover more "Only in Japan" stories when I catch up with my regular job.

Educating Developers about Content Authoring - The MCDUG.

jaredmorgs — Tue, 29 Sep 2009 10:53:00 -0700

In my gig as a Technical Writer for Red Hat Brisbane, I have the opportunity to work with incredibly skilled Open Source developers, and write about cutting edge technology in the Open Source software arena.

Sometimes, it is necessary to step away from the technology aspects and focus on writing content that will help a team work together more effectively. I'm talking about writing documentation that supports aspects of the open source project, not what the open source project is working on. Yes, I'm talking about a procedures guide.

The Mobicents team expressed interest in taking back ownership of the community XML documentation being maintained by Red Hat. The decision had a number of positive effects:

Developers could contribute directly to the user documentation.
The open source community had access to the community content source.
The Red Hat Content Author (me) could focus on developing the Red Hat product documentation for the project.

Because the team was going to be writing the initial content themselves using XML, I realised that the Self Managed Community Documentation (SMCD) project would fail quickly without clearly defined processes, and support with XML authoring.

I decided to take a step back from writing content for the software, and invested time in creating the Mobicents Community Documentation User Guide (MCDUG). I had to juggle urgent documentation tasks with my MCDUG writing, but the juggling act was worth it.

I have completed the first full release of the MCDUG. The guide is hosted on the JBoss.org Hudson build server, and is freely available to anyone who wishes to read it.

Much of the guide contains information that will only be relevant to Mobicents Developers, however there is some useful information about DocBook XML structure that may be useful to those new to XML Authoring.

I'm referring new Red Hat Content Authors to the structure tips contained in the MCDUG, and the information seems to be helping them get accustomed to working with XML faster.

My ultimate hope is the MCDUG will be used daily by the Mobicents developers, and will continue to evolve with the SMCD project. After all, a procedures guide is only relevant if the procedures are relevant.

Encounter with JOPR

amit.bhayani — Thu, 24 Sep 2009 12:29:00 -0700

MMS 2.X - Console comes back

baranowb — Tue, 22 Sep 2009 19:30:00 -0700

It happened. In 1.X branch we dropped console for some reasons (many discussion, outcome the same). During last MMS chat Oleg spoke words we believed noone will witnes him say: "Maybe its time for..."

Well thats the background. To make it short. We would like to announce that MMS 2.X will have management console. How it will look like? It all depends on feedback we get from users. We have general idea, but feedback and ideas are mostly welcome.
Design Wiki can be found here , public thread can be found here.

Web Presentation - JAIN SLEE 1.1 Resource Adaptor API and Migration to Mobicents JAIN SLEE 2.0

EDUARDO MARTINS — Wed, 16 Sep 2009 04:28:00 -0700

Hello there, next wednesday (23 September 2009) at 2pm UTC (Lisbon/London timezone), I will be doing a web presentation regarding the JAIN SLEE 1.1 Resource Adaptor API and the migration to Mobicents JAIN SLEE 2.0 using Elluminate. The double session target JAIN SLEE RA developers and should last 1 hour.

The guest link for the session is https://sas.elluminate.com/m.jnlp?sid=819&password=M.11157CBC38CD4E1D764384B0BACDF4

I recommend people to join 10 minutes before the session start to understand and get familiar with Elluminate features.

This is not mandatory, but if you are going to participate, please let me know by email (emmartins at gmail.com). By the way, if you are interested in the slides please requested them at same time.

See you there!

Mobicents ALL 1.2.1.GA has been released !!

Jean Deruelle — Wed, 16 Sep 2009 04:37:00 -0700

It's with intense pleasure that I forward here the news of our new aggregated release : Mobicents ALL 1.2.1.GA !

It's truly the most complete all integrated Platform out there (and it's open source !) for building next generation Telco and Convergent Applications. Nothing less nothing more. Usually vendors have one or two of the components we provide, but no one so far is able to offer all that we provide in Mobicents to your great pleasure...

Miscellaneous examples are :

Location based services : when ever friends, family is in 2kms range from you, your phone beeps
SMS based services : Vote for your Favorite Reality TV Show
IVR (Interactive Voice Response) Based Service : Check your bank account balance through the phone
Ring Back Tone
Event Notification by Phone, SMS and IM : get a phone call to set the delivery date of your order or SMS every time your order changed of status (processing, payment confirmed, shipping)
Conferencing : The Conference is integrated with your calendar and is calling you and the participants when it's time, no hassle on remembering the number to call, pin code, ... See
IT System Monitoring : every time an alert is sent by the monitoring app, your converged application send an SMS, Instant Message, tweet or calls out the IT System team to take preventive actions (Press 1 to restart the server, press 2 to redeploy the application, or whatever)
Web Integration for Convergence : Add a small widget so that the customer can be put in contact with the call center (through phone or chat) to help him get more information on the products he wants to buy.
Banking : Stock Monitoring application that sends an SMS or calls you when the stock price goes over a user defined threshold and let you press the amount of options you want to sell or buy
Customer Relationship Management : Ability to automatically answer status for support cases or record new leads, integration with leading online CRM providers
PBX : Enabling businesses to use their managed intranet to help reduce long distance expenses, enjoy the benefits of a single network for voice and data. Example : Mobicents IPBX

The Sky is the Limit !

To build all those kind of applications and more, the following components provided in the Mobicents ALL release will do the job and should cover all your needs :

Sip Servlets Container 1.0.GA : Aimed at building VoIP (SIP + Media interaction) and Converged Applications (SIP + HTTP/Java EE + Media interaction) with full HA capabilities
Media Server 1.0.3.GA : competitive, complete, best-of-breed media gateway functionality featuring highest quality with following features : Announcement, IVR, Conferencing, Packet Relay and supporting all majors audio codecs and can be controlled remotely through MGCP or in VM
JAIN SLEE Container 1.2.6.GA : Aimed at Telco and supporting multi protocols architectures in a standard and highly efficient way. Comes with following Resource Adaptors : SIP, SIP11 (JSR240 a.k.a. JAIN SLEE 1.1), Media, MGCP, JCC, XMPP, SMPP, HTTP Client, HTTP Servlet, Asterisk, Text to Speech, Rules, Diameter (Base, Cca, Rf, Ro, Sh-Client and Sh-Server), XCAP Client
Mobicents Diameter 1.0.1.GA : Provides Authentication, Authorization and Accounting capabilities
Mobicents SIP Presence Service 1.0.0.BETA5 : The Mobicents SIP Presence Service provides presence functionalities to SIP-based networks
Mobicents SIP Load Balancer 1.0.0.BETA7 : provides Load Balancing and failover SIP capabilites for Mobicents servers in a clustered environment

If you want to get started, download the binary form SourceForge and read the release notes. We are waiting for your feedback on mobicents-public google group.

Have fun !

Mobicents RTSP Stack 1.0.0.BTA1 Released!

amit.bhayani — Tue, 15 Sep 2009 13:36:00 -0700

We are happy to announce the first version 1.0.0.BETA1 of Mobicents RTSP stack. Mobicents RTSP which is built on top of Netty 3.0.1.GA uses the NIO Socket (TCP). The stack doesn't have any state machine and is neutral to be used either at RTSP Client side or RTSP Server side. The main purpose to have RTSP Stack is to provide RTSP Support for Mobicents Media Server.

As of now only TCP is supported.

Binary (including src) is available at
https://sourceforge.net/projects/mobicents/files/Mobicents%20RTSP/

SVN tag
http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/rtsp/mobicents-rtsp-1.0.0.BETA1

Look at example code

For Client Side
http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/rtsp/mobicents-rtsp-1.0.0.BETA1/src/main/java/org/mobicents/rtsp/example/Client.java

For Server Side
http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/rtsp/mobicents-rtsp-1.0.0.BETA1/src/main/java/org/mobicents/rtsp/example/Server.java

These are just for understanding on how to initialize the stack.

Any feedback please divert http://groups.google.com/group/mobicents-public/topics

Enjoy the RTSP :)

Mobicents Media Server Team.

MOBICENTS ALL 1.2.1.GA RELEASED

WhatDog — Tue, 15 Sep 2009 19:04:00 -0700

The Mobicents team is happy to announce a new release of the mobicents-all bundle, that includes an updated version of most of mobicents components. The last release, mobicents-all-1.2.0.GA, was made in February, so it was about time to update it.

There aren't many new and exciting features, these are still being developed and can be tried out in the latest beta releases of the different projects. Still, there are new diameter RAs (CCA, Rf, Ro, Sh-server) and the popular diameter-OpenIMS example is also included. The updated versions include several bug fixes and some performance improvements as well. Documentation is included and is more extent than in the previous version.

The main product versions are the following:

Mobicents JAIN-SLEE 1.2.6.GA
Mobicents SIP Servlets 1.0
Mobicents SIP Presence Service 1.0.0.BETA5
Mobicents Media Server 1.0.3.GA
Mobicents Diameter v1.0.1.GA
Mobicents SIP Load Balancer 1.0.BETA7

So go ahead, download the binary form SourceForge and read the release notes. We are waiting for your feedback on mobicents-public google group.

Have fun,

MMS - Control Protocols

baranowb — Sun, 13 Sep 2009 04:39:00 -0700

In mobicents projects we have different EE:

SLEE
MSS
. . . (maybe more)

In addition we also have Media Server. Media Server is only responsible for media part of applications. To make it short: regardless of application logic, signaling protocol utilized by application, media server role is always the same, to process media.

EE is driven by some sort of protocol chosen by development team - which has complete freedom to choose one protocol over another, restricted only by project requirements. In case of media server it is not that easy. Over time different "parties" created different control protocols for media server (media gateway).
For instance with CISCO equipment media server is controled with MGCP, in IMS environment media server is controled with H.248, in WWW it can be controled with RTSP, etc, etc.

In Mobicents Media Server 1.x.y we support only MGCP (aside of local MSC API), however we felt that this is not enough to meet demand from partners and community (more on this here).
So for MMS 2.x we have more in plans:

RTSP
H.248
MSML
VXML

During Brno we were supposed to iterate over this short list, high light use cases, differences and basic concepts. However we did not have enough time. So in order to compensate I decided to post it here.
Here we go.

Media Server Operation Model

As mentioned above media servers follow certain model of operation. See image below:

Media Server estabilishes only RTP stream exchanged between UAs. To setup streaming application makes use of some dedicated control protocol. Dedicated controler on Media Server side converts control protocol reqeusts into physical setup of underlying resources(generators,detectors, codecs, etc....). This happens regardles of signaling protocol used(on image it is SIP, but in reality it could be any suitable for application).

MSML: Media Server Markup Language

Basic inforamtion:

XML Based
It is independent of transport protocol ( SIP, HTTP, IP, ...)
Follows simple request/response model
Supports transactions
Supports semi-recovery from errors
Requires resource reservation
RTP service oriented

MSML supports something similar to transaction on Media Server side. It is not strictly defined as transaction but has very similar semantic/behaviour. Each MSML request can be seen as set of actions. Each action has arbitrary ID, set by application developer. If particular action fails, error response will contain this ID to make application aware of failure point - this is semi-recovery of error condition. MSML pinpoint exact place of failure, allowing application to free resources (yes, responsibility is pushed to application). This is required since Media Server does not reclaim them (according to MSML specs).

MSML is also RTP service oriented. Protocol does not define endpoint types as MGCP does for instance. It only defines actions that need to be undertaken to produce stream/interaction with user stream.

As protocol MSML is designed to be extensible, just as Diameter does. Functional elements are grouped into package. Each package defines set of primitives which affect Media Server. Prmitives are tags and their parameters which are intepreted by Media Server controler.
MSML allows new packages to be defined along ability to extend already defined. This is how whole language structure is defined. Definition from RFC are grouped as follows:

Core
Dialog-Core
Conf-Core
Audit-Core

Dialog-Core defines primitives to control automated actions of Media Server, it defines also subpackages to extend those capabilities:

Dialog-Base
Dialog-Transform
Dialog-Speech
.....

MSML: Base abstraction

Base MSML abstraction defines functional elements which are aligned as in image below:

conn - connection is logical unit which termiantes all RTP sessions from one UA
operator - logical unit representing DSP
dialog - set of automated actions like: play, DTMF generator/detector, etc...
conf - logical unit which mixes streams

MSML: Protocol use example

Below is use case of MSML encapsulated in SIP protocol.

MSML used inside SIP requires usually dialog to be established between application server and media server. MSML Requests/Answers are embeded in SIP INFO/INFO OK message.

In image above there is only one UA, which awaits video to be played. However for different number of UAS scheme is similar - only difference is dialog time when dialog is estabilished between app server and media server.

In example scenario app server asks Media Server to play announcement like (this is MSML Dialog): "Press one to play movie XXXXX, Press two to play movie xXXYYx" and detect DTMFs. Once UA sends DTMF, Media Server sends DTMF embeded in SIP INFO back to application server and indication that MSML Dialog has ended. Application server decodes INFO, picks file to be streamed back to UA and starts new MSML Dialog: "Play Movie Dialog".

Other protocols will follow in subsequent posts.

Red Hat developer conference Brno 2009

Pavel Slegr — Thu, 10 Sep 2009 18:32:00 -0700

This time of the year again all the developers interested in this event came to Brno to gather together to have a fun on the developer conference. The conference took place at the Masaryk University at Brno. On the following link is the full agenda including the presso for the Mobicents presentation, what I was involved at.
Developer confernce pages
The agenda was full of the very interesting topics from Jboss topics like Jopr, jboss.org, Drools, Jbpm to Fedora topics like KDE, core utils etc. Of course for me was the most interesting one the Mobicents presentation, which took place at the first day of the conference as the First one (from 9:30 am). I can honestly say, that I was a bit nervous since this was the first time I have presented in the university presentation hall. The attendance however did not exceed the expectations. Finally about 30 people were attending Mobicents presentation and some of them were the outside people , I mean non Redhatter's. What I have mainly focused on, was trying a bit evangelize about Mobicents. The basic assumption was that the target audience is not aware of Mobicents at all. So, I have generally introduced Mobicents follwoed by the other Mobicents modules overview (JAIN Slee, Sip Servlets, Media, Presence, Diameter). The presentation went quite OK and I hope that the attendees did get any idea, what we are doing in Mobicents team.

Other presentations, were also quite impressive. Especialy at the second day I would like to pick the jBPM presented by Jiri Pechanec the Red Hat QA Supervisor and the Drools presentation done by Lukas Petrovicky the Red Hat QA Associate. They both made a very interesting stuff.

Now we are in the middle of the second day and in the evening I am going to attend the Lab for the Portlet creation and then the Lab for the Jopr plugin (I hope I can easily create my own Jopr plugin as well).

After the developer conference presentations, there is going to be the pub event, which is also very expected.

Overall the developer conference is quite amazing experience for the developers to join. Is is a good time to stop a bit from the rush days, every day drill and to meet the others and see, what their projects are and what they are working on.

+1

Mobicents Brno Developer Conference 2009 - Documentation Achievements

jaredmorgs — Thu, 10 Sep 2009 09:00:00 -0700

On the 24th August 2009 at 5pm Brisbane time, I sat in the Red Hat meeting room. Normally, I would be getting on my scooter to head home, but today I was eagerly awaiting a conference call from the other side of the world. For the first time since I started at Red Hat in March, I was going to hear the voices of the entire Mobicents Open Source Software team that I have been working with.

The call I was looking forward to was from Brno, in the Czech Republic. The entire Mobicents team had flown into Brno for a week of meetings and planning sessions surrounding the Mobicents project and the JBoss Communications Platform (JBCP). The Mobicents team are truly global, with members in the United Stated, Czech Republic, France, India, Russian Federation, Poland, and Australia (me). As you can appreciate, the multiple time zones pose some challenges with communication, so having everyone in the same room was an opportunity worth seizing.

This wasn't the first time the team and I had "talked" however. At Red Hat, we use IRC extensively to communicate, but typing words into a chat window is never an absolute substitute for voice communication.

The Mobicents team kindly gave me a presenting spot so I could present my achievements with the community and product documentation over the time I was first assigned to the role. The presentation covered the following topics:

Achievements for 2009
Goals
Challenges

When I started with the team, the community and product documentation was being managed by Red Hat only. The team expressed a desire to maintain the community documentation and store the XML content on a public SVN server. I worked with the team to transfer all the XML documentation over to the Mobicents public SVN repository.

Making the community documentation source public required a total re-think of how the documentation was managed. The reality hit home that the writing effort was going from one writer, to multiple authors with varying degrees of writing experience. The team didn't have a lot of experience with XML authoring, and I found that I was repeating a lot of information about XML formatting techniques and the available authoring tools that make XML documentation less stressful.

To counter this, I created the Mobicents Community Documentation User Guide, which is basically a style, tips, and procedures guide for the project. The guide is still evolving at the time of writing, and relies heavily on the team feeding back information about the procedure and processes I've captured.

During the conversation, the team and I continued the discussion about single sourcing the Mobicents community, and JBoss Communication Platform product documentation. Using Maven and JDocBook, the team strongly believes they can produce both the project (Mobicents) and product (JBoss Communication Platform) documentation from a single XML source.

What's even more exciting about this direction, is that the product documentation source output by Maven will be fully compatible with Red Hat's Publican toolchain. Content compatibility is critical because Publican is the only way to produce Red Hat branded product documentation, which can be offered to customers in up to 22 different languages.

One common challenge for Red Hat Content Authors is getting the community documentation source to validate with Publican. Because the team and I are working together from the start of the community documentation life cycle, I'm confident that we can produce output that will meet the requirements of both the project and product documentation.

In summary, the conversation I had with the team was very productive. We finalised matters that would have taken way to many keystrokes over IRC. So thank you Mobicents team for the opportunity to present.

Mobicents/JBCP & JBoss World 2009

Jean Deruelle — Tue, 08 Sep 2009 10:24:00 -0700

I'm back from JBoss World 2009 that took place in Chicago together with the RH summit and the event was again awesome this year !
First I have to admit that the weather in Chicago was perfect and it helped raise this city as one of the best I've been so far in the US : very good public transportation, great architecture, LOTS of cultural events, plenty of parks, beaches on the lakes, ...

Tuesday was kind of pre-Jboss World day, it was mainly registration and partner pavillion opening. Me & Vladimir were tending the booth with other JBoss people and checking the partners out.
We got to meet and finally put a face on a lot of JBoss colleagues and people from our community (I won't cite any company names, but they will recognize themselves :-) ) getting at the same time great feedback on Mobicents/JBCP and evangelizing.

On the next day, we had a great keynote from our CEO, Jim Whitehurst, here is a phrase I thought I'd never hear in a CEO's keynote : "if we all had to walk around naked, we'd all spend more time at the gym" which seems to define the open-source spirit pretty well to me :-)

Wednesday, I attended Bela Ban's talk on Large clusters which was really interesting and I would recommend everyone interested in HA to check it out.I got to talk to the Jopr (JBoss ON is the corresponding product) team and we got this idea of integrating Mobicents to send text messages or call phones with DTMF recognition whenever there is some alerts in the cluster so that the IT monitoring team using Jopr can take some action whenever there is a problem. A proof of concept should be available soon :-)

Then Vladimir had it's BOF on Rapid VoIP Development Environment - SIP Servlets 1.1 (JSR-289), SEAM Telco Framework, Ruby on Rails, Eclipse VoIP Tooling
Unfortunately, we were competing against another BOF about Seam & JSR-299 containing all the JBoss Rock stars : Dan Allen, Pete Muir, Gavin King, Emmanuel Bernard, Max Rydahl Andersen and special guests; so the attendance was a bit lower than we expected but the feedback from the audience was great and had so much interesting questions that we finally got kicked out of the room :-)

Thursday, I went to see the new JBoss project GateIn that has been announced which is the ExoPlatform/JBoss Portal joint project. Definitely Interesting stuff, their booth was packed all day long and the project and UI are very slick. Those guys were definitely interested in Mobicents as well to be able to send SMS from the portal or click to dial kind of portlet, ... so a another proof of concept should see the light soon here as well.

In the afternoon, I went to see the Web Beans and HornetQ (JBoss Messaging renamed) presentations which were both of great quality.

Finally, we went to the Museum of Science and Industry party sponsored by IBM which was a lot of fun and then did a bit of pub crawling, on which I won't reveal the dirty details :-)

The last day was actually half a day and I attended to Bob's Mc Wirther presentation on TorqueBox which was the best one I attended too.

My session was among the last ones which was not very convenient because a lot of people already left the conference (1/3 to half I would say) but the attendance to the session was still pretty good (around 30 people in the room) and the presentation was very well received with a lot of feedback and exchange with the audience once again.

To wrap up on JBoss World, I would say that this was a rather good success for Mobicents/JBCP, it was very well received with a lot of people baffled by the platform and how it grew up in a year.

I uploaded my presentation here

So Thanks for coming and for coming at us, talk to us we love that, meeting the community in person and we will make sure that next year will be even better :-)

Update : For more pictures from chicago, see here : http://picasaweb.google.com/jean.deruelle/Chicago2009#

Update 2 : List of all JBoss World presentations and videos

MOBICENTS MEETING @ BRNO

WhatDog — Mon, 07 Sep 2009 09:57:00 -0700

Once every year, the mobicents team gets together to discuss the state of the mobicents nation, and in the time between, to party around. Since the previous location doesn't bring us the best memories, this year we chosed Brno in Czech Republic to be our meeting point. The decision was a little bit influenced by Pavel, with promises of great team building activities.

Unfortunately the Portuguese members of the team had trouble to get there, and missed the first day (and the first night). Once we got there we tried to compensate the time lost. Each day after the meetings all the fun begun. On Tuesday there was this football mach Portugal & Poland vs. Rest of the World where the Rest of the World team lost in the last minute with a goal scored with the hand (sorry guys). On Wednesday we went for a kart race that everybody enjoyed, not only because of the speed but also because of the crashes. We also had great dinners every day (I really appreciated the Czech cuisine) and after that we would go out in Brno's night. Surprisingly, no one got late for the meetings on the next day.

Regarding the work, we covered what we achieved last year, and the list is pretty amazing:

Jain-SLEE is certified 2.0
Sip-Servlets has reached GA
Media server 1.0 has reached GA, 2.0 is under way.
Diameter has also become GA and increased the number of supported applications
We also did great progresses on Documentation and Produtization

The road maps we discussed for the projects are also very ambitious:

Fault Tolerance and High Availability for both Jain-SLEE and Sip-Servlets
Video and SS7 support on media server
Management (cross-platform)
IMS components on top of Jain-SLEE (HSS, X-CSCF)
Improve the Jain-SIP stack

For my task inside the project, Quality Assurance, the main achievements were the releases of Mobicents-all 1.2.0 and 2 releases of JBoss Communication Platform during the last year, as well as a bunch of other GA releases for the individual projects. We also agreed on a new process to have more Mobicents-all releases with less effort. In the last month we we granted 2 new dedicated servers on QA lab that will ease the load testing of our projects. On the hudson front, the coverage now is more extent and we agreed that the developers will keep an eye on the warnings gave by the findbugs jobs.

For the near future we plan to cover the FT/HA features on the lab, first with a simple setup, and hopefully evolving to a more realistic one. We also plan to increase our coverage of media tests, as well as the coverage on protocols other than SIP. Interrupting these tasks will be a never ending stream of releases for the different projects and each one needs to get trough a final review, making sure that is not broken.

We are all looking for the next year meeting already. If you know some place where we could have lots of fun, please leave a note and we will consider it. Pictures of the good times we had this year can be found on http://picasaweb.google.pt/lbbbarreiro/MobicentsMeetingBrno.

The usual suspects: Jean, Ivelin, Amit, Luis, Bartosz, Vladimir, Alexandre, Eduardo
Our good host Pavel couldn't attend to this dinner.

Have fun,

Mobicents Meeting 2009 @ Brno

Alexandre Mendonça — Sun, 06 Sep 2009 19:23:00 -0700

It was that time of the year again when the Mobicents Team meets face-2-face to discuss the achievements made through the current year, plan the roadmaps for the upcoming year and last but not the least, party a lot!

This time it happened in Brno, the second largest city in Czech Republic, but at least for this week it was the funniest! Only possible thanks to Pavel, who led us through Brno! Thank You!

It had a quite troubled start, with the Portuguese members (me included) ending up by missing the plane due to issues with the airlines company (which suspended their operations since Sept. 1st). We made it anyway, missing the first day.

Regarding Mobicents, the 2009 achievements were quite amazing:

Mobicents SIP Servlets, Mobicents Diameter and Mobicents Media Server became GA.
Mobicents JAIN SLEE 2.x had it's first version, BETA1, which was certified for JAIN SLEE 1.1 (JSR 240), being the first besides the specs leader, and still the only open source.

Although all this being accomplished, there's still much more to work on, and a lot of new projects to stabilize. One of the hottest topics was the High-Availability across all these servers, which as you can understand is not a trivial subject and had a quite intense discussion.

On my side, I made a presentation regarding Diameter (available here), the main project where I'm involved. For the achievements of 2009, we have highlighted the following:

Integration with Mobicents SIP Servlets;
Sh-Client/Server Application support (3GPP TS 29.328 & TS 29.329);
Credit Control Application support (RFC 4006);
Ro/Rf Application support (3GPP TS 32.225 & TS 32.299);
Cx/Dx Application support (3GPP TS 29.228 & TS 29.229)

This was a great improvement for an year! But we won't stop and will evolve it even further, with the following features being the most important ones:

High-Availability;
Management Console (cross-server);
NAT (STUN/TURN/ICE) support;
WebServices support;
IMS Applications prototypes (HSS/x-CSCF)

So it's still a long road ahead of us, and now it's when the fun begins! And we are counting on the Mobicents Community for helping us out improving!

Here's a picture taken at the end of my presentation:

Left to right: Pavel, Bartosz, Amit, Jean, Vladimir, me, Ivelin, Luis and Eduardo.

And the team warming up for dinner (Pavel is missing and I'm taking the picture):

Left to right: Luis, Amit, Eduardo, Bartosz, Vladimir, Ivelin and Jean.

Cheers for Mobicents team and hope for another successful year!

JBossWorld update

Vladimir Ralev — Fri, 04 Sep 2009 23:33:00 -0700

JBossWorld is over. Overall, it was a good experience and a big step ahead in gaining mindshare, especially with Jean's efforts to deliver the Mobicents message internally and externally.

On the BOF side we ended up with a few requests about how to get started. So, this is the Rapid Telco App Development BOF Slide Deck

And the other useful links discussed:

And for the people with no experience in Telco, this is the fast-track on the theory:

SIP protocol/RTP protocol tutorial (you can also check the SIP Protocol Specification)
Sip Servlets spec
Media Server User Guide
Take some software SIP phones and play with the examples

I hope it helps and if there is anything else we'd be glad to give more info.

Slee 1.1 Classloader demystified!

baranowb — Fri, 04 Sep 2009 19:37:00 -0700

Here we go.

During our dev struggle to get v2 of Mobicents JSLEE container operational we encountered quite big problem: Class Loading scheme.
Usually class loaders are organized in classic tree structure:

one root
each leaf can have only one parent
each leaf can be a root of a subtree

This has certain limitations, as proven by our JSLEE 1.0 container. Without classloader repositories/isolation there is no way for two versions of the same ra(service/Sbb/Profile) to be deployed and enabled.
Moreover it is not possible to maintain integrity of classes loaded - consider situation:

DU1 has service using lib.jar
DU2 also has service using lib.jar
order of deply is: DU1,DU2
when DU2 is deployed, classloader finds lib.jar classes and does not load them
DU1 and DU2 services kick in, instances of lib.jar classes are created (from DU1 definition)
now DU1 is undeployed
error on class casting - vague information: can not cast XXYX.class to XXYX.class

Now regarding Mobicents JSLEE v1. JSLEE Specs did not define any way of providing dependency classes. To resolve this problem we altered a bit DU structure, each DU jar could have "library" dir with dependencies for particular DU. This proved to be enough to solve dependencies, however all above problems still apply.
Obviously JSR240 specs lead got a notion that specs lack something valuable here and in 1.1 it has been improved.
In 1.1 container "library" component has been introduced. It is not a functional component/jar - not in terms of slee, like SbbComponent or ProfileCompoment. Its only purpose is to provide standarised and versioned way to provide classes to Slee components. So no more DU/library!!
Now about classloaders. In SLEE v1.1 model has changed as well. Its a bit tricky. Consider classic model - tree, where each classloader with one parent. This is not sufficient for SLEE v1.1. New model allows multiple parent for each leaf to reflect components relation.

Classloaders are defined per component - that is not jar, but actual identifiable component(which has ComopnentID). Component class loader loads all classes from component jar "and" all classes from referenced components.
Consider case of jar file which contains definition of Sbb1, Sbb2 and Sbb3 - all sbb classes are in jar.

So:

three classloaders - Sbb1,Sbb2, Sbb3 - each "has" classes from jar
SbbX classloader has access to all referenced component classloaders

Actually component class loaders deffer queries to jar domain classloader to avoid that vague ClassCastException described above. Through references in xml descriptor classlaoder association is built(multiple parents - Sbb components usually references events, ras, other sbbs, profiles, etc...) - this is place where multiple parents are introduced. See diagram below, this should give a hint:

Welcome to a new era!

Alexandre Mendonça — Fri, 04 Sep 2009 20:32:00 -0700

That's right! It's a complete new world for me now that I've started my own blog.

First of all, let me introduce myself and the role of this blog:

I'm a Software Engineer working for JBoss R&D on the open source telco framework Mobicents. I've been using and developing services for it for almost 4 years, namely in JAIN SLEE server, and roughly 2 years ago I started to work on the core team, developing JAIN SLEE core and started from scratch along with Bartosz Baranowski the Diameter component for the project.

It's been a wonderful experience so far, I've learned a lot from all the team members, all JBoss community and from work itself!

Regarding the blog, it's been a project that I've always been delaying but I think the time has come and I hope I can keep it up! I expect to write on a regular basis, mainly with new announcements, some hints regarding my work... and whatever comes to my mind! :)

See you soon!

Mobicents Diameter - reaches 1.0.2.GA !!!

baranowb — Fri, 04 Sep 2009 06:20:00 -0700

Yes, thats true. Me and Alex managed to contribute enough time(even though he was sick and I was busy with personal erands) to make another diameter release. Still follow up will contain standalone documentation (yupieeee!!) with examples of configuration and setup.

More about release here.

Would like to make reminder about VM image we created with openIMS predeployed to make users life a bit easier, atleast for testing:

image.
readme.

Thats it for today. Cheers

3rd Annual Mobicents Metting: Brno 2009

baranowb — Fri, 04 Sep 2009 05:22:00 -0700

This august was quiet a big deal, Mobicents Team met in Brno office which was kind enough(or else) to host annual meeting. Almost all of us made it to office without any incident, however we still missed three team members which did not make it.
As usual it was tons of work and work. Since last year mobicents grew a lot (maybe not a good estimate but svn code and commits have been more than doubled, with team not expanding at all) so we had a lot of topics to go through. During las year three of our project reached GA status:

Sip Servlets
Media Server
Diameter

Two other has already got successor:

Media Server
JAIN Slee

In short last year achievements are:

JSR 289 certification (Sip Servlets 1.1)
JSR 240 certification( JSLEE 1.1, achieved by container v2.0.0.B1)
Media Server modular architecture
Diameter GA
Seam Telco Framework reaching stability

During meeting four topics reached level of "hot":

SS7 world mobicents role in IMS cloud
JSLEE 1.1 container architecture
HA
Media Server architecture

(See next post for some cool stuff that we talked about or did not talk )
Thats how we spent our time in the office - except me and Amit killing each other bond style(we were supposed to go for paintball, but eventually it has been canceled).

My main project(aside Diameter and JSLEE) is Media Server for the time beeing. Thats the one me and my co-mates were supposed to cover during this meeting.
However one of our MMS team member did not make it to Brno me and Amit were supposed to cover his topics(MMS Architecture & SS7 introduction) - in practice presentations we created were covered by Amit.
Topics that left for me were

Base HA framework - how to achieve HA for non cache replicated resources
MMS Control protocols(which I did not present, see my other posts)

Seems like very abstract topic, atleast first one. Well thats correct. Moreover its not a trivial one (HA). During my preparations for this subject I made a lot of tests and research to get a hint what lies ahead of team to achieve. Its a bit scary I must tell. It gets insanly complicated since Mobicents covers different EE - just consider case when one has different EEs, different protocols and must provide HA and FT balancer for that bunch - feeling that headache comming?
Aside my HA session we had one covered by Jean D and Vladimir R. Outcome? To make it short:

improve JSIP stack
make JSIP stack modular so it supports replication of data
finalize LB strategy
cooperate on Fault Tolertant Framework

What if FTF? Simple acronym that should in future cover some cool features(See next posts :) ).

What about fun part?
It was not bad at all, even though academic year has not started:

Before plunging into disco:
Get up early, go to work, eat late and party till morning. Here we are at eating part, good food, perfect beer, even portugal folks prefered it over wine:

And here we give a go to extreme sports part, carts made it a day, except few of us getting burns blisters from engine, it was worth chasing other team members around track:

Mobicents in Brno 2009 - annual team meeting aftermath

Ivelin — Fri, 04 Sep 2009 03:36:00 -0700

Mobicents Annual Meet at Brno Czech Republic - August 24 - 29, 2009

amit.bhayani — Fri, 04 Sep 2009 01:03:00 -0700

HELLO WORLD

WhatDog — Thu, 03 Sep 2009 19:07:00 -0700

There is no other way to start anything other than an hello, and so here am I saying hello and welcoming you to this new space that I'm creating.

The reasons why I'm creating yet another blog are several. I don't plan to post a lot, but I'll try to do it with quality, both in shape and content. I'll try to come up with interesting material, not only about my professional life and other technical issues, but also about other stuff that I may find relevant.

More about me can always be found in my personal home page, http://barreirao.pt.tc/, if you can read and understand Portuguese. WhatDog lives on.

Have fun,

Mobicents 2009 Team Meeting in Brno

Jean Deruelle — Wed, 02 Sep 2009 23:47:00 -0700

Hello fellas,

Last week was a big event for the Mobicents guys as we all got together in this beautiful city of Brno located in Czech Republic.

Everybody on the team gave an overview of what we did over the last year and the roadmaps ahead for the next year and I have to tell you that this is stunning how much has been achieved in a one year timeframe under the Red Hat :

Mobicents Sip Servlets, Media Server, Diameter reaching 1.0 GA
JAIN SLEE 1.1 Certification
Frameworks : Seam Telco Framework, JRuby Integration with TorqueBox, ECharts For Sip Servlets
Eclipse tooling with Sip Servlets and JAIN SLEE Plugins
Sip Presence Service
Initative by the Community to build IMS components on top of Mobicents

I'm really amazed to see at which pace is growing the Mobicents Platform and the community around it that is helping us out in an incredible number of ways from testing out the projects, interoperability to contributing code, ... that proves the value of open source, collaboration and sharing which are the core values of Red Hat and JBoss.

All of this to say "Thank You" to our beloved Mobicents Community.

I had 2 talks scheduled on Mobicents Sip Servlets :

First, as I said above on the achievements, challenges and goals/roadmap which you can find here
Second, on the HA plans and challenges not only for Sip Servlets but for JAIN SLEE as well so that we have a common architecture and frameworks for both our containers to ensure consistency and lower code duplication as much as possible.

As we move forward, we plan to continue investing and contributing to the NIST SIP Stack Reference Implementation of JAIN SIP Specification which is at the core of our projects (kudos to Ranga for being of great help whenever we need him). Those contributions will be mainly targeted at performance improvements, bug fixes, new features (lazy parsing, NIO, ...) and HA support.

It was great to understand what the other team members and other Mobicents projects have been up to and see their roadmaps and last but not the least, we got to have some fun to chill out a bit of the hard work of the day

so here is a part of the Mobicents team after work waiting to get into the action to go clubbing :

Silas and Eduardo showing the Mobicents Team winning the Beer Contest :

The Mobicents Team being teached by the local czech girls where the good places are in town

So Cheers guys !

JAIN-SLEE 1.1 Certification

EDUARDO MARTINS — Tue, 01 Sep 2009 13:15:00 -0700

In "blog" terms, it is officially official, Mobicents JAIN SLEE 2.0.0.BETA1 is certified for JAIN SLEE 1.1 specs, being the first one besides the specs leader, and single one which is open source.

TCK Report can be downloaded here.

August 2009, Brno Czech Republic

EDUARDO MARTINS — Tue, 01 Sep 2009 12:08:00 -0700

Last week the Red Hat Mobicents core team had a face to face meeting to review 2009 and define the plans for 2010, and uhh... have some fun also ;)

I made a few presentations related with JAIN SLEE and SIP Presence Service projects, you can look at the slides here and here. Briefly the roadmaps were updated and represent another aggressive turn, JAIN SLEE 2.x is now under heavy core optimization and cluster is the magic word, while SIP Presence finally sees a concrete plan towards a GA release.

Mobicents Platform wide, the plans for High Availability and Fault Tolerance are ambitious, with a cooperative work between JAIN SLEE and Sip Servlets teams, and there will be a strong effort by the team to also greatly improve JAIN SIP reference implementation.

Also, Mobicents Media Server team has really done a fine job into creating a great open source java media server, and the SS7 connectors roadmap for it (and also for a set of related JAIN SLEE resource adaptors) really got my attention. Cheers to all involved.

Of course, I would not finish the post without some fun time photos, after all we had soccer, karts, great dinners, awesome night parties... Look for yourself!!

Warming up for the karts, Mobicents Sip Servlets Lead Jean Deruelle and me, with awesome looking cheap fake hair

Here we go vroomm vroomm

One hell of a dinner, all the team members present at the meeting, except the great host - Pavel.
Left to right: Jean, Ivelin, Amit, Luis, Bartosz, Vladimir, Alex and me

Then calming down with a glass of Chardonnay

And the end ;)

Congratulations to the whole team for such a fantastic meeting, and to Brno city for being so kind

Mobicents team meeting in Brno 2009 & achievements in productization of jbcp

Pavel Slegr — Mon, 31 Aug 2009 22:11:00 -0700

This was the first time I had chance to meet face to face my team-mates from mobicents team. This was a great chance for me to meet others, work together and have fun together. For those of you who are not familiar with the mobicents project, please visit the following link:
www.mobicents.org
I am the one who has a part of responsibility in the turning the community project into the product, which is aimed to be supported by RedHat. https://www.redhat.com/solutions/telco/jbcp/
What were the main areas I have touched in my presentation ?
- Introduction of the achievements of productization in the past 6 moths
- Creation of the jbcp 1.2.1 release, which was following established process
- Challenges of productization

During the past 6 months I was working on the productization process for JBCP, trying more less follow the other well established products processes like EAP or SOA.
We have introduced the product branch for jbcp 1.2.x, which can be found at:
http://mobicents.googlecode.com/svn/branches/jbcp/1.2
We do have continuous integration running on the product branch and spotting for the bugs as an early notifications with plenty of unit test completing.
Tool for overseeing the API's used within the jbcp product was introduced, aiming on no populating API's with dirty code.
Tool for producing the One Off patches was introduced

With all those "little steps" we are coming closer to the ultimate goal, which is the well established process of making product of jbcp, taking Mobicents modules and turning them into good&supported product (with making sure of modules are productive ready and with stripping those they are only experimental features)

All other teams across the whole product live-cycle are doing the great job, never less there is much more space for improving the things such as communication and cooperation's with others involved.
We need to become stronger in the preparation of the plans for our product and trying to make schedules precisely.
We need to go further with the separation between the product and project in the terms of resources, support, customers.
The ultimate challenge is increasing the number of the satisfied customers, who are relying on the great support we can provide.

So, this was about the work part and I can honestly say, we did good, we worked hard and achieved all what was on the agenda.

Look how tired can it be:

Last, but not least we have had some fun of course.

We lost the game, but we did play a good soccer !

So, guys cheers then and hope we meet at some other place next time !

Maybe in...

JBoss World 2009 - Chicago September 1-4, 2009

amit.bhayani — Sun, 16 Aug 2009 02:24:00 -0700

Mobicents JAIN SLEE 2.0.0.BETA1

EDUARDO MARTINS — Fri, 07 Aug 2009 08:47:00 -0700

The loooooooooong waited first BETA version of Mobicents JAIN SLEE 2.x is out!!!! JBoss AS 5, JAIN SLEE 1.1, better performance, it all there already. See the official release announcement.

Since the container now supports JAIN SLEE 1.1, the old scheme to include library jars in deployable units is not supported, instead you should create JAIN SLEE library jars, and too make it easier we developed a new Maven2 plugin, where, putting it simple, you just configure the library id, put classes/resources in usual places, define jars to be include as default scoped dependencies. You can even define references to other libraries using dependencies with runtime scope, and the plugin will grab the library id of the referenced library automatically. Needless to say, the plugin generates the library-jar.xml XML descriptor for you and makes the jar, cool uh? :) A complete wiki page about the plugin is on the works, but you can take a look at one example here.

The maven DU plugin was also updated to 2.0.0.BETA1, defining own packaging "jainslee-du", being faster on the build process, and generating JAIN SLEE 1.1 XML descriptors. The plugin now deploys DU jars into Maven repositories, which open new possibilities for a remote DU management, kind of a SLEE online component store. See an example using new version of this plugin.

On a side note, for this BETA version of the container, people used to deploy/undeploy deployable units through file copy, what we call hard deploy, need to include a jboss-classloading.xml file in the deployable unit META-INF such as this one. This is due to some incompatibilities in class loading of the underlying JBoss AS5 Microcontainer deployers.

See you soon for some posts about JAIN SLEE 1.1 new features.

PS: Next version, BETA2, will bring Fault Tolerance and new management console, scheduled to September of this year, hooraay ;)

Mobicents JSR-309 Impl 2.0.0.BETA2 Released!

amit.bhayani — Wed, 22 Jul 2009 19:44:00 -0700

We are happy to release 2.0.0.CR2 version of Mobicents JSR309 Implementation. There are quite a few changes in JSR309 API and hence the implementation too has changed.

Specifically the Events structure have changed. Now the MediaEvent has method isSuccessful() which returns true if the event is for success, false otherwise. Hence every listener will have to have this preliminary check done and act accordingly.

Every NetworkConnection now has a SdpPortManager. The SdpPortManager is compatible with the offer/answer model. Please look at API to understand SdpPortManager. Its an important change

New features that have been added is there is an implementation for MediaConfig now. MediaConfig defines the internal structure of ResourceContainer (NetworkConnection, MediaGroup, MediaMixer etc). For predefined configurations like NetworkConnection.BASIC, MediaGroup.PLAYER, MediaGroup.PLAYER_RECORDER_SIGNALDETECTOR the implementation already has corresponding predefined MediaConfigs. The access to this predefined MediaConfigs can be achieved by calling MsControlFactory.getMediaConfig(Configuration configuration) passing one of the predefined Configuration as parameter.

The MediaConfig implementation shows the mapping between the JSR309 events/signals and corresponding MGCP events. Also it shows the endpoint name on Mobicents Media Server (MMS) that this ResourceContainer is firing signals/events on. Hence if you change the endpoint name on MMS, get the handle to existing MediaConfig impl and create a custom clone by passing new set of Parameters for example

MediaConfig playerConfig = msControlFactory.getMediaConfig(MediaGroup.PLAYER_RECORDER_SIGNALDETECTOR);
Parameters pNew = msControlFactory.createParameters();
pNew.put(ExtendedParameter.ENDPOINT_LOCAL_NAME, "/thisis/new/endpointname/1");

MediaConfigImpl clone = (MediaConfigImpl) playerConfig.createCustomizedClone(pNew);

mediaSession.createMediaGroup(clone, someParams);

In this case someParams could be null as mobicents JSR309 impl still doesn't take them into consideration.

Other way of doing this get the handle to existing MediaConfig impl and get the XML string by calling marshall()

String xml = playerConfig.marshall();

The xml will look like

<?xml version="1.0" encoding="utf-8"?>
< resource-container>
  < parameter>
    < key> ENDPOINT_LOCAL_NAME < &frasl key >
    < value > &frasl mobicents &frasl media &frasl IVR &frasl$ < &frasl value >
  < &frasl parameter >
  < player >
    < signal >
      < mgcp-event > ann < &frasl mgcp-event >
      < mgcp-package > A < &frasl mgcp-package >
      < on-endpoint > true < &frasl on-endpoint >
    < &frasl signal >
    < event >
      < mgcp-event > oc < &frasl mgcp-event >
      < mgcp-package > A < &frasl mgcp-package >
      < on-endpoint > true < &frasl on-endpoint >
      < media-event > PLAY_COMPLETED< &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > of < &frasl mgcp-event >
      < mgcp-package > A<&frasl mgcp-package >
      < on-endpoint > true < &frasl on-endpoint >
      < media-event > PLAY_COMPLETED< &frasl media-event >
    < &frasl event >
  < &frasl player >
  < recorder >
    < signal >
      < mgcp-event > aupr < &frasl mgcp-event >
      < mgcp-package > AU<&frasl mgcp-package >
      < on-endpoint > true < &frasl on-endpoint >
    < &frasl signal >
  < &frasl recorder >
  < signal-detector >
    < event >
      < mgcp-event > dtmf0< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf1< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf2< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf3< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf4< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf5< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf6< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf7< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf8< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmf9< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmfA< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmfB< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmfC< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmfD< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmfStar< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
    < event >
      < mgcp-event > dtmfHash< &frasl mgcp-event >
      < mgcp-package > D<&frasl mgcp-package >
      < on-endpoint > false < &frasl on-endpoint >
      < media-event > SIGNAL_DETECTED < &frasl media-event >
    < &frasl event >
  < &frasl signal-detector>
< &frasl resource-container>

use you favorite XML parser and replace the /mobicents/media/IVR/$ with your value for enpoint for example /thisis/new/endpointname/1 . Again get the String of this new XML and create a new MediaConfig object by calling

Reader xmlDoc = new StringReader(xml);
MediaConfig config = msControlFactory.getMediaConfig(xmlDoc);

And then get the corresponding ResourceContainer by passing this MediaConfig to mediaSession. Though this is lengthy process process, it will be useful in future to create a custom MediaConfig when JSR309Impl is mature enough to take custom MediaConfigs.

For now we have flexibility to change the MGCP vs JSR309 events and Endpoint names.

Please note that JSR309 is still under public review and not final. However unless and untill there are major change in API, mobicents JSR309 impl will not change.

Mobicents JSR309 impl version 2.0.0.BETA2 can be downloaded from https://sourceforge.net/projects/mobicents/files/

The Mobicents JSR309 home page is at http://www.mobicents.org/mms-jsr309-main.html

Follow the announcement here http://groups.google.com/group/mobicents-public/browse_thread/thread/5791bdce0143d5f9#

Please post your comments to http://groups.google.com/group/mobicents-public

Enjoy the JSr309 :)

Mobicents Media Server Team

Mobicents MGCP 2.0.0.CR4 Released

amit.bhayani — Wed, 22 Jul 2009 19:41:00 -0700

Mobicents Media Server team has released 2.0.0.CR4 version of MGCP implementation of JSR23. The focus was entirely on improving the performance both in terms of transactions per seconds and CPU consumed. We are very happy to have achieved 540 transactions per seconds at just 40 - 50% CPU load. The load test was done on my dual core, 4GB laptop.

The binary package is mobicents-mgcp-impl-2.0.0.RC4.zip and can be downloaded from http://sourceforge.net/projects/mobicents/files/

If you want to look at source code the SVN is http://mobicents.googlecode.com/svn/trunk/servers/media/jain-mgcp

The Mobicents MGCP Home Page is http://www.mobicents.org/mms-mgcp-main.html

Here is the announcement http://groups.google.com/group/mobicents-public/browse_thread/thread/37db5645d43f13be#

Please feel free to leave a comment at http://groups.google.com/group/mobicents-public

Cheers!

Mobicents Sip Servlets 1.0 released !

Jean Deruelle — Wed, 22 Jul 2009 19:11:00 -0700

We are proud to announce the Mobicents Sip Servlets 1.0, certified against Sip Servlets 1.1 specification and working on top of Tomcat 6.0.14 and JBoss AS 4.2.3.GA & 5.1.0.GA and licensed under LGPL.

Following is the list of features making it the best open source Sip Servlets 1.1 implementation out there to build powerful VoIP and Telco/Web 2.0 Converged Applications in Java and JRuby :

More than 15 Telco and Converged examples covering all imporant features to boostrap you real fast
Clustering and High Availability for scaling out
An Enterprise Monitoring and Management Console : to effectively manage and monitor the server and your applications in development or production environments
Media Support to build PBX, Announcement, Conference, IVR, Call Centers kind of applications or control Remote Media Servers and PBX
Bundled Enterprise class Mobicents Media Server
Eclipse Tooling to quickly create new Sip Servlets projects in your favorite Eclipse IDE
Development Frameworks to enhance your productivity :
- Seam Telco Framework
- JRuby Torquebox Telco Framework
- ECharts For SIP Servlets framework (E4SS) : Check out the announcement, ECharts is now officially supported !
Concurrency and Congestion Control
Diameter support and IMS Support
SIP Servlets/JAIN SLEE Interoperability

Downloads are here, online documentation is here, the roadmap is here and the Mobicents Google Group for feedback and questions is here.

Try out this new awesome release and give us your feedback !
Enjoy and Have Fun !

The Mobicents Sip Servlets Team

Enable Flash on Google Chrome Linux Dev Build

Jean Deruelle — Tue, 21 Jul 2009 03:18:00 -0700

Hey,

Looks like the google chrome dev build on linux don't come with flash enabled by default. This has been preventing you from using it on linux ? Here is a little 3 commands process that get you the google chrome plays flash on ubuntu (on most of the flash enabled site) :


sudo mkdir -p /opt/google/chrome/plugins
sudo cp /usr/lib/flashplugin-installer/libflashplayer.so /opt/google/chrome/plugins/
/opt/google/chrome/google-chrome --enable-plugins

Feel free to comment if you have more hacks to enable other plugins on google chrome linux dev builds, I'll update the post :-)

Long time uh?!

EDUARDO MARTINS — Fri, 17 Jul 2009 03:00:00 -0700

That is correct, unfortunately last months it has been difficult to find time to post something interesting, but will soon change with the release of the first beta version of Mobicents JAIN SLEE version 2, you can expect thoughts about JAIN SLEE 1.1 specs (some may be quite controversial) and other new features, such as the usage of JBoss AS5 or High Availability/ Fault Tolerance, be patient :-)

Meanwhile a new version of Mobicents SIP Presence Service is out, BETA5, which is always a little bit emotional, and mainly introduces mandatory authentication and authorization in the public XCAP interface of the XDM Server, and a better Resource List Server. More info at http://groups.google.com/group/mobicents-public/t/3b5454c49bbba13b

Mobicents JAIN SLEE was also upgraded to 1.2.6.GA, which includes serialized access to sbb entities, a better fit with the specs. See it at http://groups.google.com/group/mobicents-public/browse_thread/thread/2b1170b08c8e6ccf#

Mobicents/JBCP at JBoss World 2009

Jean Deruelle — Fri, 17 Jul 2009 03:53:00 -0700

It's this time of the year again where all of JBoss is regrouping together to present you the latest and greatest and for the first time, the event is even co-located with the Red Hat Summit for an even more incredible event since with the same pass you get access to both conferences !

For those of you that are interesting to check what Mobicents / JBoss Communications Platform is up to, we have two dedicated sessions this year :

First Valdimir Ralev will be presenting, on September 2nd at 5:45 PM, in its BOF session Rapid VoIP development - SIP Servlets 1.1, Seam Telco Framework, JRuby on Rails, Eclipse VoIP tooling, you can gather more information on his blog post as well

For my part, I'll present, on September 4th at 11:00 AM, Writing Telco 2.0 applications with JBoss Communications Platform based on Mobicents
(What's next track) which will be an overview of the main JBCP components - JSLEE 1.1 container (JSR 240), Media Server (JSR 309), SIP Servlets 1.1 container (JSR 289), Diameter Server and SIP Presence Service and will also show real world examples how telecoms leverage JBCP for innovative converged Telco 2.0 applications and blow you away with a converged Web/Telco 2.0 demo !

So make sure to regirster ASAP, the early bird registration ends today, Early bird registration extended until 17th.

Also upon user/developper demand, we could meet altogether for a Mobicents special or setup a Boot Camp there or just have a beer and talk all night so don't hesitate to ask for it !

Looking forward to meet you there !

Join us at JBossWorld 2009 in Chicago

Vladimir Ralev — Thu, 09 Jul 2009 20:40:00 -0700

Once again, someone made a terrible mistake and I will be leading the BOF session on Rapid VoIP development - SIP Servlets 1.1, Seam Telco Framework, JRuby on Rails, Eclipse VoIP tooling. They just never learn :)

The talk is on September, 2nd at 5:45 PM. It seems a bit late, but knowing the JBoss parties that occur during summits, that's actually early and a very good slot. The other good news is that I will have Jean Deruelle and some guests with me. Jean also has another talk on Telco 2.0 on Friday in the What's next track. It is worth mentioning that this year JBossWorld and Red Hat Summit take place at the same time on the same location and visitors have have access to both with their passes.

In my BOF session, we will begin with a short presentation and demos how to start developing VoIP and Converged applications with Mobicents from scratch with our telco application frameworks/platforms focusing on Seam Telco Framework and the IDEs. We will move on to some real-world examples. We will have a lot of time for questions and discussion on other Mobicents topics, VoIP technology and the current trends in the market. I hope it will be a great experience for everybody.

As always, if you are around Chicago, we can do another Mobicents user meeting somewhere.

Update: Early bird registration extended until 17th.

hSenid - officially certified JBCP partner

Ivelin — Fri, 03 Jul 2009 08:51:00 -0700

Finacial crisis ? No, the Men kind crisis

Pavel Slegr — Thu, 25 Jun 2009 22:18:00 -0700

It is a Friday, just my last day in the office before I go to vacation. I started to read a blog about the economic situation. This was very interesting article and it hit me to respond to this article and suddenly I have realise: "This is a wow topic and I want to express a little more of myself to this problem, so .. I started this article".
Whole world, the people, from everywhere are discussing the crisis, and what is much worst, a lot of them is feeling the crisis itself by loosing their jobs. The article I was reading and which hit me to write this post, was describing, how the economic theories are no valuable any more, how lots of people with the Nobel prises are discussing etc.
You know, what ? I don't think this is only about ECONOMY. What the hell, why the people think, that the whole world is about money. Do you think this is "child view". Say to me: "grow first, and you realize that whole world is about money"? Surely, you are right. But lest go a little deep and I will show you, this is not only about money.
In our global world, we are more than 30-40 years trying to catch up the bi-polarization between the "third world countries" and "good situated countries". Did wee succeed ? No I do not think so. We are rich and they are poor. Now you may think, what this has together with the crisis... a lot.
Nowadays I am quite rich guy with well situated family, good job and house for mortgage. Yes... well done. But, I do realize, that need of having 4 TV's at home is no worth a penny. I am fine with one TV, I do not need to buy the fourth one. So, in our "rich countries" there is quite a lot of people thinking the same way, I would say quite enough to get the TV developers into the trouble, that they will not sell as much as they thought.
On the other hand the people from the "poor countries", they are not going to buy the TV, because they do not have enough money to buy food.
So, where do I lead you ? I want to show, that we have reached the crisis of the people consumption and that we do not sell more TV's cars etc, if the people does not want to buy.
Today world people are used to apply for mortgage to pay up Their living and all of us, We are living on debt. Do you think we pay up the debt once ? NEVER !!! Therefore we are not producing any value, we are just promising we will pay.
It is time about to start thinking about the new ways, how to live for the future. You know the old traditionalist, they will tell you, that this is only economic recession, and that it will be over soon. NOT TRUE !
Just think about it....
Think about, what will happen when consume all the resources, what we have : oil, coil, but the worst one.. water
Do you say: "This does not affect me, and my children, hopefully not, and grand children "... who cares, we will be dead at that time.
Think about it...
About the new approach, we must find out to get out of the crisis, BUT not from the economic crisis, but the men kind crisis.

Mobicents Media Server (MMS) v2.0.0.BETA1 Released!

amit.bhayani — Thu, 18 Jun 2009 19:57:00 -0700

Here comes a new improved Mobicents Media Server 2.0.0.BETA1. The 2.x.y efforts were focused on improving performance and at same time leveraging JBoss Microcontainer to come up with component based Media Server. All the media resources (sources or sinks) are POJO based. A common theme for Mobicents Media Server 2.x.y is the breaking out of internal fixed subsystems into stand alone components implemented as POJOs and the introduction of SPIs throughout the server codebase. Those changes should not affect directly the end user but they are an important part of the Mobicents Media Server strategy for making available the various voice/video services as independent components, so that they can be wired together on demand.

Architecture

The component architecture divides the process of constructing media services into two major parts:

The implementation of components which generates or consume media data
The assembly of chains of media components to build media flow path.

The following diagrams illustrates media components wiring and "implementation” process.As depicted on the diagram above we can isolate three main groups of the media components:

components which used for generation of media content or media source;
components which consumes media or media sink;
components which itself are neither sources nor sinks but provide access to sink or source like components A and B on diagram allow to access Input which acts as a sink and Output which is a source. The component which provide access to media sink as input is known as Inlet and component getting access to output as media source is called as Outlet.

The example of Inlet is Demultiplexer that has one input (sink) and many output (source). The example is Outlet is Multiplexer which has many input's (sinks) and one output (source)

Channels and pipes

This is one of the most important fundamentals of MMS and useful if you planing to create custom media path (custom Endpoint) in MMS. Channel is not a media component but it is able to join with Media Source and Media Sink or joined with other channel. The role of channel is to construct media flow path by joining components using pipes.Channel allows to easy assembly a required media path flow. Using multiplexers and demultiplexers media stream can be merged or splited, different signaling processors may be plugged in different places to achieve more flexibility or performance.

Performance

The initial test shows that for 300 concurrent announcements there is zero Jitter (no DSP involved). This is much better compared to MMS 1.x.y. The main reason for performance improvement is number of Threads has been reduced to very few. This was achieved by making use of NIO instead of plain sockets.

Here is a comparison table between the MMS 1.x.y and MMS 2.x.y

	MMS 1.X.Y	MMS 2.X.Y
Standalone MMS Server	Not available	Available
Embedded in JBoss AS	JBoss AS 4.X.Y	JBoss AS 5.X.Y
MGCP Support	MGCP Support available via MGCP JAIN SLEE Service (SBB). Hence to use MGCP control protocol one needs to install JAIN SLEE Server, MGCP RA and mgcp-controller-sbb service	MGCP Controller is inbuilt with MMS. No SLEE required
JSR-309 Support	Not available	JSR-309 is availale which uses MGCP as MS control protocol
MSC API	Available. This is custom API developed by Mobicents Media Server.	Not available
Performance	Compared to 2.x.y, 1.x.y has very high Jitter problems due to large number of threads used. It uses plain sockets for RTP	Very less Jitter as compared to 1.x.y. It uses NIO for RTP
Basic Architecture	MMS 1.x.y is built on JMX Microkernel. No flexibility of deciding the media-path for endpoints. For example for IVR, DTMF detection will be used irrespective of application may use it or not.	MMS 2.x.y is built on top of Jboss Microcontainer. Flexibility of defining the media-path for endpoints. For example if application will never detect DTMF but only recording, the DTMF detector media component can be completely removed from IVR endpoint and hence save some processing.

You can download the MMS 2.0.0.BETA1 from here

Follow the announcement here

Your valuable feed-back is welcome

Enjoy the MMS :)

Mobicents JSR-309 Impl 2.0.0.BETA1 Released!

amit.bhayani — Thu, 18 Jun 2009 17:34:00 -0700

A brief intro on what is JSR-309

JSR-309 defines a programming model and object model for Media Server (MS) control independent of MS control protocols. JSR-309 API is not an API for a specific protocol. It will take advantage of the multiple and evolving Multimedia Server capabilities available in the industry today and also provide an abstraction for commonly used application functions like multi party conferencing, multimedia mixing and interaction dialogs.

Some of the commonly used MS control protocols are MGCP (RFC 3435), MEGACO (RFC 3525), Media Server Markup Language (MSML) (RFC 4722) and VoiceXML. The Mobicents implementation of JSR-309 API makes use of MGCP as MS control protocol.

The Mobicents JSR-309 Impl is first and only open source implementation of JSR-309 available as of today. To further understand the JSR-309 API, download specs from here.

Still the TCK for JSR-309 is not available. We are eagerly waiting for TCK to be out.

The diagram bellow shows the high-level architecture of how application can make use of JSR-309 over MGCP

The first binary release is Mobicents JSR-309 IMpl 2.0.0.BETA1. This implementation can be used not only for controlling Mobicents Media Server, but any Media Server that understands MGCP Protocol.

You can download the mobicents-jsr309-impl-2.0.0.BETA1.zip from here

The public announcement is here

Cheers!

All Mobicents IDE Tools Online

Vladimir Ralev — Thu, 11 Jun 2009 22:29:00 -0700

Some news from the past few days - all Mobicents Eclipse Plug-ins are now updated and available from the new repository. Previously, only the Sip Servlets tools were maintained, but now the EclipSLEE, the JAIN SLEE Service Creation Tool is there as well.

What's new in this latest update?

EclipSLEE 1.2.5 updated to work with Eclipse 3.4 Ganymede and with JAIN SLEE 1.1 - Many thanks to wernerdit for the patches. EclipSLEE still needs to be updated to support the new deployment mechanism. For now you can only deploy to localhost.
Sip Servlets Core Plugin 1.0.3 updated to fix a deployment issue and some glitches with Windows when loading the management console. It works with both JBoss Application Server 4.2.x and 5.1.x distros.
Sip Phone Plugin 1.0.1 updated to fix some Windows issues. There is still a flicker in the graphs in Windows, but it's reduced now. Will work on that later.

Well, with this set of tools you can create and test both Sip Servlets and JAIN SLEE applications. Note that all 3 plugins do not depend on each other and you can install them separately, but they look best together :)

This is our update site: http://mobicents.googlecode.com/svn/downloads/sip-servlets-eclipse-update-site/
(i admit, putting the update site in "sip-servlets-..." was a shortsighted idea, because we have JAIN SLEE tools there as well, but it's just a path name, it doesn't matter)

You can see the documentation about the Sip Servlets plugins here.
While the EclipSLEE documentation will remain at the old location for now.

I hope you enjoy it.

My first blog

Pavel Slegr — Thu, 11 Jun 2009 21:50:00 -0700

What, the hell ?
So long being with the IT and not blogging at all ?
Why do I hesitate to spread out my ideas around all other world ?

Simply I had never had any need talking to "dear void". While blogging started to be so popular and massive I even more hesitated to go and create my own blog.
Now is the time to break all those rules and start to share, whatever I think would be in interest of others.

Git Cheat Sheet or My Reminder against git headaches

Jean Deruelle — Tue, 02 Jun 2009 07:08:00 -0700

Ok since I'm a git noob and I'm working on the move from JBoss Rails to the new Torquebox. I need to hack the Telco part of Torquebox so that any JRuby app located in Mobicents Sip Servlets on JBoss 5 can setup and handle SIP calls. Since the torquebox repo is git based and I'm usually dealing with svn or cvs, and I messed up quite some times already with git (even after checking out the famous git svn crash course), I'll use this post to be a placeholder for the thing I usually do so that me an git get along very well.

First things first, the repo is already created on git hub so I'll just check it out using :


$ git clone git://github.com/torquebox/torquebox.git

Since Torquebox is using a notion of submodules :

I need to checkout the underlying submodules, this is achieved by doing :


$ cd torquebox
$ git submodule init
$ git submodule update

Since the master branch is locked up, I use for each module the following command to be able to push my changes to the master branch :


$ git remote add central git@github.com:torquebox/torquebox.git
$ cd torquebox-core
$ git remote add central git@github.com:torquebox/torquebox-core.git
# and so on for each submodule

Then I hack away and do my changes in the various torquebox project. When I'm ok with my changes, I use the following to commit :


$ git commit -a

If there is files or directories that needs to be added to the commit, I usually do :


$ git add 'filename'
# example : git add src/main/java/org/torquebox/ruby/enterprise/sip/sip_environment_builder.rb

This will commit things only locally, then I need to push everything to the central repo located on github, this is done by doing :


$ git push central master

Sometimes I get into a no-branch strange state (don't ask me why :-)) and I end up in no branch at all, you can check on which branch you are by doing :


$ git branch -a

The following command can be useful too :


$ git status

so when I'm on no branch, to recover, I use the following commands sequence :


# going back on master branch
$ git checkout master

# checking the lost commits on the no branch
$ git fsck --lost-found

# the previous command will out put something like
# dangling tree a628672f320e4e311a59ce4bcd879125500141ff
# dangling commit 69ade48b3183ffc7a4e09cf87a1d0e5cedaa39bc
# to merge the last commit into the master branch I just switched to
$ git merge 69ade48b3183ffc7a4e09cf87a1d0e5cedaa39bc

#then I can push to github again
$ git push central master.

I'll update this blog post once in a while on my path to non newbiness to git.
Please comment to make me understand things a bit further or advice me on some good eclipse plugin that would avoid me such pain...

Back to git now

Update : Ranga gave a link with a few more tips http://sipx-wiki.calivia.com/index.php/Mirroring_sipXecs_subversion_repository_with_git#Making_and_committing_changes

Update 2 : very nice and thorough visual tutorial http://www.ralfebert.de/blog/tools/visual_git_tutorial_1/

Time for Seam Telco Framework 2.1

Vladimir Ralev — Sun, 31 May 2009 01:19:00 -0700

The Mobicents application framework for SIP and Media on top of Seam is now officially named Seam Telco Framework (STF) and it just reached version 2.1!

There have been a number of changes and fixes since the last public version and the current 2.1 version must be stable enough to be consumed by all users.

The goal is still the same - to unify the programming model for Telco and JEE application. A somewhat new perspective for the framework is to minimize the new APIs and reuse as many standard or established APIs as possible (JSR-289, MSC or JSR-309) in order to keep a flat learning curve. You can think of it as something using the Seam infrastructure to expose these APIs to your application. For example the SIP messages and the media notification are delivered through Seam events in the context of a JSR-289 Sip Servlets Session. The Sip Servlets Session itself is backing the Seam SESSION scope context similarly to how the HTTP sessions work in Seam. Additionally, most of the framework objects are available and exposed through the Seam IoC and scoped at the right level. The STF simply plugs into Seam and reuses whatever makes sense in the SIP world. By the same logic, Seam uses that same infrastructure to expose the other APIs from the diagram (JEE, JBoss Frameworks and others) in certain roles - JSF for presentation, jBPM for flow and navigation, Drools for security and so forth.

We also want to highlight the point that most major IDEs already have support for Seam core syntax. You can use the same IDE tools to code SIP components without any extra plugins. Again, everything from STF is exposed through the Seam core infrastructure as events, components or scopes.

You should note the following changes:

The new documentation is here.
This source code of the latest stable release 2.1 is here (where the examples are stable).
The source code trunk has moved to here (including the dev examples).
The media framework is bundled.
The Connection and Link IVR helper classes are unified under a single IVRHelper class now. You can check the examples and the documentation for more information.

To have quick glance let's dive into the familiar conference IVR example:

@Scope(ScopeType.STATELESS)
public class MediaFrameworkDemo {
 @Logger Log log;
 @In MediaController mediaController;
 @In SipSession sipSession;
 @In MediaSessionStore mediaSessionStore;
 @In IVRHelper ivrHelper;
 @In MediaEventDispatcher mediaEventDispatcher;

 @In(scope=ScopeType.APPLICATION, required=false)
 @Out(scope=ScopeType.APPLICATION, required=false)

 String conferenceEndpointName;

 private final String announcement =
 "http://mobicents.googlecode.com/svn/branches/servers/media/1.x.y/examples/mms-demo/web/src/main/webapp/audio/welcome.wav";

 @Observer("INVITE")
 public void doInvite(SipServletRequest request) throws Exception {
 // Extract SDP from the SIp message
 String sdp = new String((byte[]) request.getContent());

 // Tell the other side to ring (status 180)
 request.createResponse(SipServletResponse.SC_RINGING).send();

 // Store the INVITE request in the sip session
 sipSession.setAttribute("inviteRequest", request);

 // If this is the first INVITE in the app, then we must start a new conference
 if (conferenceEndpointName == null)
 conferenceEndpointName = "media/trunk/Conference/$";

 // Create a connection between the UA and the conference endpoint
 mediaController.createConnection(conferenceEndpointName).modify("$",
 sdp); // also updates the SDP in Media Server to match capabilities of UA
 }

 @Observer("connectionOpen")
 public void doConnectionOpen(MsConnectionEvent event) throws IOException {
 // Save this connection where the framework can read it
 // mediaSessionStore.setMsConnection(event.getConnection());// This is done automatically in STF 2.0

 // The conference endpoint is now assiged after we are connected, so save it too
 conferenceEndpointName = event.getConnection().getEndpoint()
 .getLocalName();

 // Recall the INVITE request that we saved in doInvite
 SipServletRequest request = (SipServletRequest) sipSession
 .getAttribute("inviteRequest");

 // Make OK (status 200) to tell the other side that the call is established
 SipServletResponse response = request.createResponse(SipServletResponse.SC_OK);

 // Put the SDP inside the OK message to tell what codecs and so on we agree with
 response.setContent(event.getConnection().getLocalDescriptor(),
 "application/sdp");

 // Now actually send the message
 response.send();

 // And start listening for DTMF signals
 ivrHelper.detectDtmf();
 }

 @Observer("DTMF")
 public void dtmf(String button) {
 // If the other side presses the button "0" stop the playback
 if("0".equals(button)) {
 ivrHelper.endAll();
 } else {
 // otherwise play announcement
 ivrHelper.playAnnouncementWithDtmf(announcement);
 }
 // Also log the DTMF buttons pressed so far in this session
 log.info("Current DTMF Stack for the SIP Session: "
 + mediaEventDispatcher.getDtmfArchive(sipSession));
 }

 @Observer( { "BYE" })
 public void doBye(SipServletRequest request) throws Exception {
 request.createResponse(200).send();

 // And clean up the connections (not really required, because there is automatic cleanup in STF 2.1)
 MsConnection connection = mediaSessionStore.getMsConnection();
 connection.release();
 }

 @Observer("REGISTER")
 public void doRegister(SipServletRequest request) throws Exception {
 request.createResponse(200).send();
 }

}

This is how you can do conferencing and IVR just by subscribing a few methods to a few events without implementing any callback interfaces or keeping track of how the media and SIP events are related. You will notice some differences and comments. There is significant effort by STF to automatically assign and cleanup media objects when it's clear what is expected or when they should not be used any more (for example they are cleaned up when the SIP session is destroyed). Overall we just try to keep the glue code out of your application or at worst keep the glue in the metadata.

What happened with version 2.0?

Version 2.0 is was released without announcment only to solve particular problems without being fully tested. The 2.1 version has some fixes on top of 2.0 and the API changes are explained in the documentation. If you are 2.0 user all APIs are back-compatible and you should be able to switch to 2.1 without any effort.

As usual, any suggestions and feedback are welcome!

370 calls per second for 100 Million calls served on Mobicents Sip Servlets 0.9 !

Jean Deruelle — Tue, 28 Apr 2009 17:47:00 -0700

Mobicents Sip Servlets 0.9 that we just released last week has been through a load test done by Luis Barreiro, our dedicated QA engineer for the Mobicents Platform.

The load test went on for over 75 hours at a rate of 370 calls per seconds on TCP and served 100 Million Calls :-)

For more information regarding the test, hardware, reproducibility and the report, see the announcement on the Mobicents google group

Sangoma & Asterisk + SS7

amit.bhayani — Tue, 28 Apr 2009 14:55:00 -0700

Asterisk + SS7

amit.bhayani — Sun, 26 Apr 2009 04:50:00 -0700

Mobicents Sip Servlets 0.9 Released !

Jean Deruelle — Mon, 20 Apr 2009 23:29:00 -0700

Here is our new shiny Mobicents Sip Servlets 0.9 release !

The focus of this release has been to add support for converged HTTP/SIP failover with complete converged replication (both of HTTP Sessions and SIP Sessions), add Tooling support with a brand new Sip Servlets Eclipse plugin to create Sip Servlets applications and an eclipse embedded Sip Phone to be able to test those apps.

We also added support for JRuby so that you can create pure JRuby (and on Rails) VoIP applications able to start or receive calls.

Also as part of this release, the Mobicents IPBX advances to BETA1 version with the new Seam Telco Framework 2.0

Our Mobicents Sip Servlets implementation run (and is certified against the SIP Servlets 1.1 spec) on top of Apache Tomcat 6.0.14, JBoss AS 4.2.3.GA and JBoss AS 5.0.1.GA.

The other highlights of this release are :

* Java EE/EJBs/SIP converged applications are now supported for the JBoss 5 version
* Bundled User Guides for both Mobicents Sip Servlets and Mobicents Media Server
* More than 20 bug fixes

Downloads are here, online documentation is here, User Guide is here, the 0.9 changelog and roadmap is here and the Mobicents Google Group for feedback and questions is here.

Try out this new awesome release and give us your feedback !
Enjoy and Have Fun !

The Mobicents Sip Servlets Team

Official JBCP documentation available on redhat.com

Ivelin — Sun, 05 Apr 2009 09:34:00 -0700

JRuby VoIP app on JBoss 5 reloaded - Look Ma ! My pure JRuby app can now receive phone calls !

Jean Deruelle — Fri, 03 Apr 2009 10:10:00 -0700

Following on the previous blog (My JRuby-Rails app on JBoss and Mobicents can make Phone calls !), we took things a step further in the JRuby Telco integration with JBoss 5 and Mobicents Sip Servlets.

We thought this was a hassle to have to create a multi language jruby-java application for pure rubyists to be able to calls in their application, so we decided to remove the Java part altogether and allow the application to be a pure Ruby application handling VoIP to benefit from runtime modification (without having to redeploy anything) to cut development time drastically and in addition to that have all the benefits (Media support, Diameter support, STUN, advanced monitoring, clustering, failover, ...) of Mobicents Sip Servlets for free :-)

Note that this application will be bundled with our next 0.9 release that should be out very soon.

So let's go through a quick walk-through on how to do that in redoing the same application as in the previous blog post but this time pure Ruby :

The code source of the application is available here.
For the hackers that want to create it themselves here are the steps :

So let's create the application skeleton :

$ jruby -S rails pure-jruby-telco -d mysql

Go into the “pure-jruby-telco" directory, then modify the config/database.yml.
Adjust the adapter name, and instead of ‘mysql’ put ‘jdbcmysql’. You might also want to delete the lines starting with “socket:” or set it to tmp dir.

Here’s a simple example for the development environment:

development:
adapter: jdbcmysql
encoding: utf8
database: pure-jruby-telco_development
pool: 5
username: root
password:
socket: /tmp/mysqld.sock

Also edit the config/environment.rb to specify the gem dependency we have on the jdbcmysql adapter (this step is mandatory for freezing the dependencies in your app later on)


Rails::Initializer.run do |config|
...
config.gem "activerecord-jdbcmysql-adapter", :version => '0.9', :lib => 'active_record/connection_adapters/jdbcmysql_adapter'
...
end

Now, it’s time to create our database:


$ jruby -S rake db:create:all

The next step is to create some minimal scaffolding to create the complaint system

$ jruby script/generate scaffold Complaint customer_name:string company:string complaint:text sip_uri:string

$ jruby -S rake db:migrate

now, we will add the logic to make the phone call once a complaint has been created, to do that edit app/controllers/complaints_controller.rb and the create function should look like this :


def create
 @complaint = Complaint.new(params[:complaint])

 respond_to do |format|
 if @complaint.save
 # get the sip factory from the servlet context
 @sip_factory = $servlet_context.get_attribute('javax.servlet.sip.SipFactory')
 # create a new sip application session
 @app_session = request.env['java.servlet_request'].get_session().get_application_session();
 # create a new sip servlet request to start a call to the sip phone with from header equals to "sip:my_jruby_app_rocks@mobicents.org" and the to header equals to the sip_uri from the complaint
 @sip_request = @sip_factory.create_request(@app_session, 'INVITE', 'sip:my_jruby_app_rocks@mobicents.org', @complaint.sip_uri);
 # actually sending the request out to the sip phone
 @sip_request.send();

 flash[:notice] = 'Complaint was successfully created.'
 format.html { redirect_to(@complaint) }
 format.xml { render :xml => @complaint, :status => :created, :location => @complaint }
 else
 format.html { render :action => "new" }
 format.xml { render :xml => @complaint.errors, :status => :unprocessable_entity }
 end
end

Ok we are done with the web part that make phone calls, let's make the app able to handle phone calls, create a sip directory :

mkdir app/sip

This directory will contain our sip controllers to handle SIP messages, so let's create such a controller, by adding a sip_handler.rb file, to the app/sip directory, containing the following code :


# Note that the class extend a JBoss provided sip controller called JBoss::Sip::SipBaseHandler
# that mimic the Java Sip Servlet class the ruby way
class SipHandler < JBoss::Sip::SipBaseHandler
 # Handle INVITE request to setup a call by answering 200 OK
 def do_invite(request) 
 request.create_response(200).send
 end
 # Handle BYE request to tear down a call by answering 200 OK
 def do_bye(request) 
 request.create_response(200).send
 end
 # Handle REGISTER request so that a SIP Phone can register with the application by answering 200 OK
 def do_register(request) 
 request.create_response(200).send
 end
 # Handle a successful response to an application initiated INVITE to set up a call (when a new complaint is filed throught the web part) by send an acknowledgment
 def do_success_response(response)
 response.create_ack.send
 end
end

Please read the comments in the above code, they should be insightful on what's going on.
Ok that's it the app can now receive phone calls and handle the signaling part :-)

Let's prepare the application for deployment to the Mobicents Sip Servlets on top of JBoss 5 app server.

Now let's freeze the rails version and the associated gems dependencies we are using into our application so that if rails or a dependency is upgraded in the system, our application will always use the version we freezed and not the newly upgraded version of rails from the system. Note: this is highly recommended for production env and really is a best practice (google freeze rails for more information)
Note that freezing is mandatory if you wish to deploy your application to JBoss 5 with the jboss-rails plugin.

It is a 2 steps process, first freeze rails then the dependencies (in our case the jdbcmysql adapter)
Here is the command to freeze your rails application :

$ jruby -S rake rails:freeze:gems

Here is the command

$ jruby -S rake gems:unpack:dependencies

You can verify that it worked by issuing this command

$ jruby -S rake gems

That will produce the following output :


 - [F] activerecord-jdbcmysql-adapter = 0.9
 - [F] activerecord-jdbc-adapter = 0.9
 - [F] jdbc-mysql = 5.0.4

I = Installed
F = Frozen
R = Framework (loaded before rails starts)

Let's add jboss-rails-support to the application so that it can be deployed and run on JBoss 5 and even start JBoss 5 from the commandline, grab the following zip and extract it to the vendor/plugins directory of our application.

Now grab Mobicents Sip Servlets latest binary snapshot and extract it to any location that suits you and set JBOSS_HOME env variable to it.

Then in JBOSS_HOME/server/default/deploy create a file called pure-jruby-telco.yml containing :


--- 
application: 
 RAILS_ENV: development
 RAILS_ROOT: /home/deruelle/workspaces/mobicents-sip-servlets/sip-servlets-examples/pure-jruby-telco
web: 
 context: /jruby-telco
sip:
 appname: PureJRubyTelcoApplication
 rubycontroller: SipHandler

change the RAILS_ROOT in it to the location of your application.

Then let's roll and fire up the server, from the root directory of the application do

$ rake jboss:as:run

When the server has started go to the Mobicents Sip Servlets management console and for INVITE and REGISTER select PureJRubyTelcoApplication in the select box then click 'Save'. This will instruct the Mobicents Sip Servlets container to route INVITE and REGISTER requests to our JRuby application.

You're ready to test the application. Starts your favorite Sip Phone (wengo phone, linphone, ekiga, sip communicator, ...) and configure it to register to 127.0.0.1:5080 then go to http://localhost:8080/pure-jruby-telco/complaints

Create a new complaint and make sure that in the sip uri field you put the address of the sip phone as shown here

Now enjoy your first JRuby Rails Sip-Servlets application making a call to your sip phone.
Note that with some more coding and a VoIP provider such as http://www.callwithus.com, it could call real land-line phones or cell phones.

This application doesn't play any media yet so you hangup the phone whenever you like.
You can also call the application in dialing sip:pure-jruby-telco@127.0.0.1:5080 :-)

Nortel focuses on AS 5200/CS 2000. Mobicents a key component.

Ivelin — Tue, 31 Mar 2009 12:19:00 -0700

Mobicents Media Server 1.0.0.GA Released!

amit.bhayani — Mon, 30 Mar 2009 17:45:00 -0700

Here comes the first stable version of Mobicents Media Server (MMS) 1.0.0.GA that we all were waiting for!

Follow the announcement here

Download here

User Guide is here

The initial days of MMS was nothing more than JAIN SLEE Resource Adaptor (RA) on top of JMF project and was shipped with early versions of Mobicents JAIN SLEE Server. The RA was un-stable and more over JMF is project to fulfill the media needs of a desktop application. For something to truly serve the needs of telco applications we needed much more robust and scalable server. We also explored the FMJ project but that too didn't meet the requirements we had. We searched around to see if there are already existing Open Source Media Server's on top of which we can build our own or re-use it as its. But there were none and hence we decided to build our own Media Server :)

We released first Alpha version of MMS on end of Feb 2008 and took approx 13 months to come up with first stable release. Thanks to all those who has contributed, provided valuable feed-backs and big thanks to Mobicents Core Team. Last but not least a big thank you to MMS users. MMS 1.0.0.GA is the first Open Source Media Server that has passed MGCP TCK test.

MMS 1.0.0.GA has all the features from simple announcement, recording, IVR to complicated ones like Conference. MMS has support for majority of audio codecs used in industry today like PCM-U, PCM-A, G729, GSM, Speex. MMS can be easily used with JAIN SLEE Server with either MGCP Resours Abaptor or MSC Resource Adaptor or it can be integrated with Sip Servlets using the MSC API.

With release of 1.0.0.GA the life-cycle for 1.x.y comes to an end and we will be actively doing development for version 2.x.y

Going Forward....

The support for video has already begun (check out code from SVN trunk). MMS is also actively developing endpoints for SS7 support. Have a look at wiki page http://groups.google.com/group/mobicents-public/web/mobicents-ss7-roadmap. The first Alpha release of 2.0.0 will also have initial support for JSR-309. JSR-309 is protocol agnostic API for Media Server Control. The MMS implementation for JSR - 309 will be on top of MGCP.

Mobicents Google Group for feedback, queries is here

Njoy!

Mobicents Media Server Team

Google Summer of Code 2009 with Mobicents

Vladimir Ralev — Mon, 23 Mar 2009 06:56:00 -0700

This year, the Mobicents project is part of the JBoss/Red Hat/Fedora GSoC student mentoring organisation. We have collected some project ideas here, but if you have others ideas, they are welcome and you can work on them as well.

I signed up as a mentor and I am particularly interested in seeing some contributors on the PBX project or the tooling. The PBX project combines all the cutting edge Web and VoIP technologies and there are many cool tasks on the todo-list. Moreover, the project is allows you to push your own design ideas and contribute to our Seam Telco Framework.

Check the program homepage, where you can read more details, register and apply.

Any questions or comments should go to our google group.

Project ideas for Google Summer of Code 2009

amit.bhayani — Sat, 21 Mar 2009 03:41:00 -0700

My JRuby-Rails app on JBoss and Mobicents can make Phone calls !

Jean Deruelle — Wed, 11 Mar 2009 13:24:00 -0700

Following on the previous blog, I'll describe the steps to create a multi language JRuby-Rails application that utilize the power of the Sip Servlets 1.1 specification to make phone calls.

It will be bundled as a war and will be deployed on top of Mobicents Sip Servlets.

So the application will allow one to file complaints and every time a complaint is filed, a confirmation call is made to your phone saying that is has been taken into account and has been routed to a sales representative.

You can download the prebuilt application, if you're not interested in build it yourself and just want to test things out.
Note also that the source code for this app is available here
In any case, make sure you have JRuby correctly setup as explained in my previous post

Deploy the war to your favorite Mobicents Sip Servlets container. Currently only the current trunk (0.9-SNAPSHOT) is able to work correctly with a JRuby/Rails - Sip Servlets app, you can find the corresping binary snapshots of the trunk on our hudson job

Copy the war into your $JBOSS_HOME/server/default/deploy directory($JBOSS_HOME points to the location where you extracted Mobicents Sip Servlets zip) and then starts the jboss container as usual with

$ sh $JBOSS_HOME/bin/run.sh

When started, go to http://localhost:8080/sip-servlets-management and remove all configured applications in clicking on all the Delete buttons then click on Save.

You're ready to test the application. Starts your favorite Sip Phone (wengo phone, linphone, ekiga, sip communicator, ...) then go to http://localhost:8080/jruby-demo-sip-servlet-1.0-SNAPSHOT/complaints

Create a new complaint and make sure that in the sip uri field you put the address of the sip phone as shown here

Now enjoy your first JRuby Rails Sip-Servlets application making a call to your sip phone.
Note that with some hacking and a VoIP provider such as http://www.callwithus.com, it could call real land-line phones or cell phones.

The next step now is to integrate with the JBoss Rails Deployer and add to it the ability to recognize those converged telco applications, so that you don't need to recreate the war everytime you change the rails part of the app and benefit from the rails features of live modification and also of the JBoss enterprise features in your Rails application !

Also if you want to help us and contribute check our Google Summer of Code project ideas for Mobicents

For the hackers that want to create it themselves here are the steps :
(Note that the prebuilt application is integrated with Mobicents Media Server and as such has the media features of playing the audio but we will not see that below, it will just showcase the call setup.)

So let's create the application skeleton :

$ jruby -S rails jruby-sips-demo -d mysql

Go into the “jruby-sips-demo” directory, then modify the config/database.yml.
Adjust the adapter name, and instead of ‘mysql’ put ‘jdbcmysql’. You might also want to delete the lines starting with “socket:” or set it to tmp dir.

Here’s a simple example for the development environment:

development:
adapter: jdbcmysql
encoding: utf8
database: blog_development
pool: 5
username: root
password:
socket: /tmp/mysqld.sock

Also edit the config/environment.rb to specify the gem dependency we have on the jdbcmysql adapter (this step is mandatory for freezing the dependencies in your app later on)

Rails::Initializer.run do |config|
...
config.gem "activerecord-jdbcmysql-adapter", :version => '0.9', :lib => 'active_record/connection_adapters/jdbcmysql_adapter'
...
end

Now, it’s time to create our database:

$ jruby -S rake db:create:all

The next step is to create some minimal scaffolding to create the complaint system

$ jruby script/generate scaffold Complaint customer_name:string company:string complaint:text sip_uri:string

$ jruby -S rake db:migrate

now, we will add the logic to make the phone call once a complaint has been created, to do that edit app/controllers/complaints_controller.rb and the create function should look like this :


def create
 @complaint = Complaint.new(params[:complaint])

 respond_to do |format|
 if @complaint.save
 # get the sip factory from the servlet context
 @sip_factory = $servlet_context.get_attribute('javax.servlet.sip.SipFactory')
 # create a new sip application session
 @app_session = request.env['java.servlet_request'].get_session().get_application_session();
 # create a new sip servlet request to start a call to the sip phone with from header equals to "sip:my_jruby_app_rocks@mobicents.org" and the to header equals to the sip_uri from the complaint
 @sip_request = @sip_factory.create_request(@app_session, 'INVITE', 'sip:my_jruby_app_rocks@mobicents.org', @complaint.sip_uri);
 # actually sending the request out to the sip phone
 @sip_request.send();

 flash[:notice] = 'Complaint was successfully created.'
 format.html { redirect_to(@complaint) }
 format.xml { render :xml => @complaint, :status => :created, :location => @complaint }
 else
 format.html { render :action => "new" }
 format.xml { render :xml => @complaint.errors, :status => :unprocessable_entity }
 end
end

Ok we are done with the rails, let's create the war so that we can deploy it on a Java EE compliant container such as JBoss, for that we need to install Warbler :

$ jruby -S gem install -y jruby-openssl warbler

and set it up for our application with :

$ jruby -S warble config

Using jdbcmysql adapter, don't forget to uncomment this line in config/warble.rb:

config.gems += ["activerecord-jdbcmysql-adapter"]

Create the .war :

$ jruby -S warble war

Ok we are done with the rails app, now we need to create the java Sip Servlets code that will handle SIP related requests and responses and package it with the war.

So let's create the directory structure for the java classes :

$ mkdir -p src/main/java/org/mobicents/servlet/sip/demo/jruby
mkdir -p src/main/sipapp/WEB-INF

Now let's add the Sip Servlet class that will handle the SIP calls in src/main/java/org/mobicents/servlet/sip/demo/jruby :



public class JRubySipServlet extends SipServlet {

 @Override
 protected void doSuccessResponse(SipServletResponse resp) throws ServletException, IOException {
 //acknowledge that the call is accepted by the phone
 if (resp.getStatus() == SipServletResponse.SC_OK) {
 SipServletRequest ack = resp.createAck();
 ack.send();
 }
 }

 @Override
 protected void doBye(SipServletRequest request) throws ServletException, IOException {
 //respond to the hangup request
 SipServletResponse ok = request.createResponse(SipServletResponse.SC_OK);
 ok.send();
 }
}

Now let's create the sip.xml deployment descriptor in src/main/sipapp/WEB-INF :


<?xml version="1.0" encoding="utf-8"?>
<sip-app>
<app-name>org.mobicents.servlet.sip.demo.jruby.JRubySipServletApplication</app-name>
 
 <servlet>
 <servlet-name>JRubySipServlet</servlet-name>
 <display-name>JRubySipServlet</display-name>
 <description>JRuby SIP servlet</description>
 <servlet-class>
 org.mobicents.servlet.sip.demo.jruby.JRubySipServlet
 </servlet-class>
 <load-on-startup>1</load-on-startup>
 </servlet>
</sip-app>

Now let's create the web.xml deployment descriptor in src/main/sipapp/web.xml so that the application uses the development database


<web-app>
<context-param>
<param-name>rails.env</param-name>
<param-value>development</param-value>
</context-param>

<context-param>
<param-name>public.root</param-name>
<param-value>/</param-value>
</context-param>

<context-param>
<param-name>jruby.max.runtimes</param-name>
<param-value>1</param-value>
</context-param>

<filter>
<filter-name>RackFilter</filter-name>
<filter-class>org.jruby.rack.RackFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>RackFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

<listener>
<listener-class>org.jruby.rack.rails.RailsServletContextListener</listener-class>
</listener>
</web-app>

Now let's tie everything together by creating a maven pom.xml to bundle the jruby app and the sip servlets code together in a single war so create the pom.xml at the root of your project


<project xmlns="http://maven.apache.org/POM/4.0.0" xsi="http://www.w3.org/2001/XMLSchema-instance" schemalocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelversion>4.0.0</modelversion>
<parent>
<groupid>org.mobicents.servlet.sip.example</groupid>
<artifactid>sip-servlets-examples-parent</artifactid>
<version>1.2</version>
<relativepath>../pom.xml</relativepath>
</parent>
<groupid>org.mobicents.servlet.sip.example</groupid>
<artifactid>jruby-demo-sip-servlet</artifactid>
<packaging>war</packaging>
<version>1.0-SNAPSHOT</version>
<name>JRuby Sip Servlet Demo Application</name>
<url>http://www.mobicents.org/jruby-sip-servlets.html</url>

<build>
<plugins>
<plugin>
<artifactid>maven-compiler-plugin</artifactid>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
<plugin>
<artifactid>maven-war-plugin</artifactid>
<configuration>
<warsourcedirectory>
${basedir}/src/main/sipapp
</warsourcedirectory>
<webresources>
<resource>
 <directory>tmp/war</directory>
 <excludes>
 <exclude>**/web.xml</exclude>
 </excludes>
</resource>
<resource>
 <directory>log</directory>
 <!-- override the destination directory for this resource -->
 <targetpath>WEB-INF/log</targetpath>
</resource>
</webresources>
</configuration>
</plugin>
</plugins>
</build>
</project>

Create the converged jruby sip servlets war with

$ mvn clean install

Mobicents Media Server Performance better than targeted for GA release

amit.bhayani — Wed, 04 Mar 2009 01:21:00 -0800

Just few days back MMS CR6 was released with much improvements on performance. I did a quick performance test of CR6 using SipP tool for load generation, a wonderful tool called sysstat for CPU recording http://pagesperso-orange.fr/sebastien.godard/tutorial.html#section1 and our own tool for RTP Jitter recording.

The test was run for approximately 10 min with intention to measure the jitter at load of 100 ~ 110 concurrent announcements and at same time measure the CPU usage on MMS Server.

While the Jitter was under control the CPU never crossed more than 25%. The attached graph shows the idle% CPU recorded after every 5 secs.

Here are the jitter graphs taken randomly while running the test tool.

Further details here

Mobicents Media Server 1.0.0.CR6 Released!

amit.bhayani — Mon, 23 Feb 2009 18:05:00 -0800

The focus of this release has been the performance. CR6 is by far one of the best performing MMS! MMS now can easily have 200 concurrent Announcement or IVR. Details here

One of the major issue was Buffer was created too frequently and not reused which caused frequent GC. Other issue was with Inband Dtmf detection which is based on Goertzel Algorithm was consuming too much of CPU. The algorithm is modified in CR6 to have all the costly operation done at MMS start time and just use comparison's and other simple calculations at runtime.

The announcement for CR6 release is here

Download here

Cheers!

hSenid - a Mobicents Partner success story

Ivelin — Mon, 23 Feb 2009 03:06:00 -0800

Simple Steps to Deploy a JRuby Rails application on JBoss 5

Jean Deruelle — Wed, 18 Feb 2009 02:50:00 -0800

As part of the scheduled 0.9 version of Mobicents Sip Servlets, one of our tasks is to add telco features to JRuby on Rails applications so that it becomes quite easy to create click 2 dial or ipbx kind of apps in Rails.

Adhearsion, a framework written in Ruby by Jay Philips, allows Rails applications to control various functions in Asterisk servers.

Our goal here is a bit different we would like to enable current Rails application to leverage the Sip Servlets specification and be able to handle all the best parts of it. Not sure yet if we will try to integrate into JRuby-Rack or create a similar adapter for the Sip Servlets Specification... so stay tuned !

As I'm still a newbie on all the ruby world, feel free to comment to help us out or chime in with ideas on how to achieve this goal...

So since I'm a (J)Ruby-Rails-newbie, I started where all people start at the ruby home and documentation with their excellent tutorials. If you're a newbie as well please familiarize yourself with ruby before going farther. As my grandma said : "Learn to walk before you run!"

So after I felt like I grasped the basics of ruby I went on to play with the famous new kid in town that is getting all the hype these days (or is it already old fashionned and Scala, Haskell and such is getting the hype now ?) : Ruby on Rails. Same thing here, I followed their simple tutorial that gets you started and off I went with my first rails app. Then I wanted to get a bit farther and started with their blogging application tutorial.

I decided that this was enough for now and that I'll dig deeper as I go and since my objective was JRuby on Rails, I will retry to create the blogging app on JRuby.
So first download the JRuby version 1.1.6 and installed it in my home directory on my linux box under java/jruby-1.1.6. Set the JRUBY_HOME environment variable to the location where you installed it and add the JRUBY_HOME/bin directory to your PATH variable so that all commands are available from the command line. On linux this would be adding this to your ~/.bashrc file :

$ export JRUBY_HOME=/path/to/your/jruby/installation
$ export PATH=$PATH:$JRUBY_HOME/bin

You can test it out from the command line to issue the version by typing this

$ jruby -v

This will give the following output :

jruby 1.1.6 (ruby 1.8.6 patchlevel 114) (2008-12-17 rev 8388) [i386-java]

Ok let's install Rails now :

$ jruby -S gem install rails

This will produce the following output :

JRuby limited openssl loaded. gem install jruby-openssl for full support.
http://wiki.jruby.org/wiki/JRuby_Builtin_OpenSSL
Successfully installed activesupport-2.2.2
Successfully installed activerecord-2.2.2
Successfully installed actionpack-2.2.2
Successfully installed actionmailer-2.2.2
Successfully installed activeresource-2.2.2
Successfully installed rails-2.2.2
6 gems installed
Installing ri documentation for activesupport-2.2.2...
Installing ri documentation for activerecord-2.2.2...
Installing ri documentation for actionpack-2.2.2...
Installing ri documentation for actionmailer-2.2.2...
Installing ri documentation for activeresource-2.2.2...
Installing RDoc documentation for activesupport-2.2.2...
Installing RDoc documentation for activerecord-2.2.2...
Installing RDoc documentation for actionpack-2.2.2...
Installing RDoc documentation for actionmailer-2.2.2...
Installing RDoc documentation for activeresource-2.2.2...

Since JRuby doesn't support SQLite, we will use mySQL as the database (I assume it is already installed on your machine) so we install the jdbc mysql adapter for activerecord (if you don't know what activerecord, check the Rails documentation).

$ jruby -S gem install activerecord-jdbcmysql-adapter

This will produce the following output :

JRuby limited openssl loaded. gem install jruby-openssl for full support.
http://wiki.jruby.org/wiki/JRuby_Builtin_OpenSSL
Successfully installed activerecord-jdbc-adapter-0.9
Successfully installed jdbc-mysql-5.0.4
Successfully installed activerecord-jdbcmysql-adapter-0.9
3 gems installed
Installing ri documentation for activerecord-jdbc-adapter-0.9...
Installing ri documentation for jdbc-mysql-5.0.4...
Installing ri documentation for activerecord-jdbcmysql-adapter-0.9...
Installing RDoc documentation for activerecord-jdbc-adapter-0.9...
Installing RDoc documentation for jdbc-mysql-5.0.4...
Installing RDoc documentation for activerecord-jdbcmysql-adapter-0.9...

Let's create the blog application backed by mySQL now :

$ jruby -S rails blog -d mysql

Go into the “blog” directory, then modify the config/database.yml.
Adjust the adapter name, and instead of ‘mysql’ put ‘jdbcmysql’. You might also want to delete the lines starting with “socket:” or set it to tmp dir.

Here’s a simple example for the development environment:

development:
adapter: jdbcmysql
encoding: utf8
database: blog_development
pool: 5
username: root
password:
socket: /tmp/mysqld.sock

Also edit the config/environment.rb to specify the gem dependency we have on the jdbcmysql adapter (this step is mandatory for freezing the dependencies in your app later on)

Rails::Initializer.run do |config| 
...
config.gem "activerecord-jdbcmysql-adapter", :version => '0.9', :lib => 'active_record/connection_adapters/jdbcmysql_adapter'
...
end

Now, it’s time to create our database:

$ jruby -S rake db:create:all

The next step is to create some minimal scaffolding so that you could actually play with some dynamic functionality and database access:

$ jruby script/generate scaffold Post name:string title:string content:text

We need to update the database after that:

$ jruby -S rake db:migrate

Let's the application now :

$ jruby script/server

and go to http://localhost:3000/posts

Now let's freeze the rails version and the associated gems dependencies we are using into our application so that if rails or a dependency is upgraded in the system, our application will always use the version we freezed and not the newly upgraded version of rails from the system. Note: this is highly recommended for production env and really is a best practice (google freeze rails for more information)
Note that freezing is mandatory if you wish to deploy your application to JBoss 5 with the jboss-rails plugin.

It is a 2 steps process, first freeze rails then the dependencies (in our case the jdbcmysql adapter)
Here is the command to freeze your rails application :

$ jruby -S rake rails:freeze:gems

Here is the command

$ jruby -S rake gems:unpack:dependencies

You can verify that it worked by issuing this command

$ jruby -S rake gems

That will produce the following output :

 - [F] activerecord-jdbcmysql-adapter = 0.9
 - [F] activerecord-jdbc-adapter = 0.9
 - [F] jdbc-mysql = 5.0.4

I = Installed
F = Frozen
R = Framework (loaded before rails starts)

Ok now I can restart the app and play with again (nothing will have changed but if you modify your rails installation to a newer version the app will keep using the version you froze with it).

Let's deploy our application to JBoss 5 now :
First grab a JBoss AS 5.0.0.GA zip and unzip to the location of your choice then set the JBOSS_HOME env variable to it

Now let's get the jboss-rails plugin from the all too famous Bob McWhirter's github repo by issuing the following command (don't forget to move to another directory than your blog application) :

$ git clone git://github.com/bobmcwhirter/jboss-rails.git

from the newly created jboss-rails directory (note that JDK6 is needed for it to compile) :

$ mvn clean install

copy the content of the target/jboss-rails.deployer directory to JBOSS_HOME/server/default/deployers/jboss-rails.deployers.
Congratulations, We just installed the jboss-rails deployer into our jboss installation. Now let's tell the jboss deployers that we want to deploy a rails application by creating a blog-rails.yml file into JBOSS_HOME/server/default/deploy directory as explained by Bob that contain the following :

application:
 RAILS_ROOT: /home/deruelle/ruby/rails/blog
 RAILS_ENV: development
web:
 context: /blog
 host: *

ok we are all set up now, you can start your JBoss 5 application server :

$ cd JBOSS_HOME/bin
$ sh run.sh

and go to http://localhost:8080/blog/posts, there you go your JRuby-rails application working in jboss without the need to create a war and we are able to modify it at runtime, isn't that great !

Thanks Bob for you thesis, plugin and help !

Feel free to comment and let me know how well it worked for you !

Mobicents Sip Servlets 0.8 Released !

Jean Deruelle — Fri, 06 Feb 2009 05:25:00 -0800

Here is our new feature packed Mobicents Sip Servlets release !

The focus of this release has been to be able to run Mobicents Sip Servlets on top of JBoss 5, it has been better than expected since we already pass the Sip Servlets 1.1 TCK for JBoss 5.

We also wanted to be able to act as a SIP Application Server in the IMS architecture and push the limits of Seam integration and showcasing it with a Media IPBX based on the Seam Sip Servlets framework to demonstrate the technology and eventually become a real useful PBX product

We also continued to add new carrier grade features to Mobicents Sip Servlets by adding more Congestion Control mechanisms and we created a jopr plugin for Mobicents Load Balancer so that it can be more easily monitored and managed.

Our Mobicents Sip Servlets implementation run on top of Apache Tomcat 6.0.14, JBoss AS 4.2.3.GA and now on JBoss AS 5.0.0.GA and is shipped with Mobicents Media Server 1.0.0.CR5

The other highlights of this release are :

a Diameter Sh support showing integration between Mobicents Sip Servlets acting as a SIP Application Server in OpenIMS Core, using the Diameter Sh interface to receive profile updates and SIP.
Concurrency control at application level
Mobicents Sip Servlets User Guide : http://hudson.jboss.org/ hudson/job/ MobicentsDocumentation/ lastSuccessfulBuild/artifact/ html_single/index.html# chapter-Mobicents_SIP_ Servlets_Server
More SIP Extensions supported : Join - Replaces - PATH

Downloads are here, online documentation is here, User Guide is here, the 0.8 changelog and roadmap is here and the Mobicents Google Group for feedback and questions is here.

Thanks to Alex from Mobicents Diameter team, Joel Soderstrom from Telmi Communication and Alex Sova for their contributions to this release.

Enjoy !

Cheers
Mobicents Sip Servlets Team

Mobicents Media Server has new home

amit.bhayani — Fri, 06 Feb 2009 07:01:00 -0800

Mobicents MGCP implementation pases the MGCP TCK

amit.bhayani — Thu, 05 Feb 2009 17:08:00 -0800

The Mobicents MGCP stack has cleared the TCK listed on JSR 23 http://jcp.org/aboutJava/communityprocess/final/jsr023/index.html, though it wasn't one of the most challenging task we kept delaying the TCK compliance as least priority as MGCP TCK is not one of the best one can rely on. Rather we created our own test-suite for MGCP which is more reliable in terms of encoding/decoding command,testing retransmission, regression test and proper flow of command.

To understand more about TCK look at README.txt at http://code.google.com/p/mobicents/source/browse/trunk/servers/media/jain-mgcp/tck/README.txt

The test output (this may vary in your environment)

[abhayani@localhost tck]$ mvn exec:exec
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'exec'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Mobicents MGCP TCK
[INFO] task-segment: [exec:exec]
[INFO] ------------------------------------------------------------------------
[INFO] [exec:exec]
[INFO] JAIN MGCP TCK
[INFO] This instance is a Gateway.
[INFO] Using org.mobicents.mgcp.stack as the path name for JainMgcpStackImpl.
[INFO] Remote entity is 127.0.0.1:2727.
[INFO] Verbose trace selected.
[INFO]
[INFO] Testing Bandwidth parameter class.
[INFO] Testing single parameter constructor. Succeeded!
[INFO] Testing two parameter constructor. Succeeded!
[INFO]
[INFO] Testing BearerInformation parameter class. Succeeded!
[INFO]
[INFO] Testing CallIdentifier parameter class.
[INFO] Invoking constructor with valid hexadecimal string. Succeeded!
[INFO] Calling constructor with empty string (should throw exception). Succeeded!
[INFO] Calling constructor with string of more than 32 characters (should throw exception). Succeeded!
[INFO] Calling constructor with string that contains non-hexadecimal characters (should throw exception). Succeeded!
[INFO] Invoking setCallIdentifier() with valid hexadecimal string. Succeeded!
[INFO] Invoking setCallIdentifier() with empty string (should throw exception). Succeeded!
[INFO] Invoking setCallIdentifier() with string of more than 32 characters (should throw exception). Succeeded!
[INFO] Invoking setCallIdentifier() with string that contains non-hexadecimal characters (should throw exception). Succeeded!
[INFO]
[INFO] Testing ConnectionIdentifier parameter class.
[INFO] Invoking constructor with valid hexadecimal string. Succeeded!
[INFO] Calling constructor with empty string (should throw exception). Succeeded!
[INFO] Calling constructor with string of more than 32 characters (should throw exception). Succeeded!
[INFO] Calling constructor with string that contains non-hexadecimal characters (should throw exception). Succeeded!
[INFO] Invoking setConnectionIdentifier() with valid hexadecimal string. Succeeded!
[INFO] Invoking setConnectionIdentifier() with empty string (should throw exception). Succeeded!
[INFO] Invoking setConnectionIdentifier() with string of more than 32 characters (should throw exception). Succeeded!
[INFO] Invoking setConnectionIdentifier() with string that contains non-hexadecimal characters (should throw exception). Succeeded!
[INFO]
[INFO] Testing ConnectionMode parameter class. Succeeded!
[INFO]
[INFO] Testing EchoCancellation parameter class. Succeeded!
[INFO]
[INFO] Testing EventName parameter class. Succeeded!
[INFO]
[INFO] Testing ExtendedConnectionParm parameter class. Succeeded!
[INFO]
[INFO] Testing GainControl parameter class. Succeeded!
[INFO]
[INFO] Testing InfoCode parameter class. Succeeded!
[INFO]
[INFO] Testing EncryptionMethod parameter class. Succeeded!
[INFO]
[INFO] Testing PacketizationPeriod parameter class.
[INFO] Testing single parameter constructor. Succeeded!
[INFO] Testing two parameter constructor. Succeeded!
[INFO]
[INFO] Testing ResourceReservation parameter class. Succeeded!
[INFO]
[INFO] Testing SilenceSuppression parameter class. Succeeded!
[INFO]
[INFO] Testing TypeOfNetwork parameter class. Succeeded!
[INFO]
[INFO] Testing TypeOfService parameter class. Succeeded!
[INFO]
[INFO] Testing LocalOptionExtension parameter class. Succeeded!
[INFO]
[INFO] Testing NotifiedEntity parameter class. Succeeded!
[INFO]
[INFO] Testing QuarantineHandling parameter class. Succeeded!
[INFO]
[INFO] Testing ReasonCode parameter class. Succeeded!
[INFO]
[INFO] Testing RegularConnectionParm parameter class. Succeeded!
[INFO]
[INFO] Testing RequestedAction parameter class. Succeeded!
[INFO]
[INFO] Testing PackageName parameter class. Succeeded!
[INFO]
[INFO] Testing PackageName parameter class. Succeeded!
[INFO]
[INFO] Testing SupportedModes parameter class. Succeeded!
[INFO]
[INFO] Testing SupportedPackages parameter class. Succeeded!
[INFO]
[INFO] Testing LocalOptVal parameter class. Succeeded!
[INFO]
[INFO] Test of Gateway API succeeded!
[INFO]
[INFO] Continuing with messaging tests.
[INFO] Getting an instance of JainIPFactory.
[INFO] Setting path name for stack implementation to org.mobicents.mgcp.stack.
[INFO] Creating a JainMgcpStack object.
[INFO] Setting port to Gateway default port 2427
[INFO] Creating a JainMgcpProvider object
[INFO] 0 [main] INFO org.mobicents.mgcp.stack.JainMgcpStackImpl - mgcp-stack.properties read successfully!
[INFO] executorTableSize = 80
[INFO] executorQueueSize = -1
[INFO] messageReaderThreadPriority = 10
[INFO] messageDispatcherThreadPriority = 7
[INFO] messageExecutorThreadPriority = 5
[INFO] 46 [main] INFO org.mobicents.mgcp.stack.JainMgcpStackImpl - Jain Mgcp stack bound to IP 0.0.0.0/0.0.0.0 and UDP port 2427
[INFO] Jain Mgcp stack bound to IP 0.0.0.0/0.0.0.0 and UDP port 2427
[INFO] Creating a JainMgcpListener object
[INFO] Adding JainMgcpListener object to JainMgcpProvider's list
[INFO] Received AuditConnectionResponse with transaction ID 1
[INFO] Received AuditEndpointResponse with transaction ID 2
[INFO] Received CreateConnectionResponse with transaction ID 3
[INFO] Received AuditConnection with transaction ID 5
[INFO] Sent AuditConnectionResponse with transaction ID 5
[INFO] message =
[INFO] DLCX 4 local@127.0.0.1:2727 MGCP 1.0
[INFO] C:FFFF
[INFO]
[INFO] local Tx ID = 4 Remote Tx ID = 4 Sending the Command 2
[INFO] Received DeleteConnectionResponse with transaction ID 4
[INFO] Received AuditEndpoint with transaction ID 7
[INFO] Sent AuditEndpointResponse with transaction ID 7
[INFO] Received DeleteConnectionResponse with transaction ID 4
[INFO] Received EndpointConfigurationResponse with transaction ID 5
[INFO] Received CreateConnection with transaction ID 9
[INFO] Sent CreateConnectionResponse with transaction ID 9
[INFO] message =
[INFO] EPCF 8 local@127.0.0.1:2727 MGCP 1.0
[INFO] B:e:mu
[INFO]
[INFO] local Tx ID = 8 Remote Tx ID = 6 Sending the Command 2
[INFO] Received EndpointConfigurationResponse with transaction ID 6
[INFO] message =
[INFO] MDCX 10 local@127.0.0.1:2727 MGCP 1.0
[INFO] C:FFFF
[INFO] I:FFFF
[INFO]
[INFO] local Tx ID = 10 Remote Tx ID = 7 Sending the Command 2
[INFO] Received ModifyConnectionResponse with transaction ID 7
[INFO] Received EndpointConfigurationResponse with transaction ID 6
[INFO] Received ModifyConnectionResponse with transaction ID 7
[INFO] Received ModifyConnectionResponse with transaction ID 8
[INFO] Received NotificationRequestResponse with transaction ID 9
[INFO] Received DeleteConnection with transaction ID 16
[INFO] Sent DeleteConnectionResponse with transaction ID 16
[INFO] message =
[INFO] MDCX 13 local@127.0.0.1:2727 MGCP 1.0
[INFO] C:FFFF
[INFO] I:FFFF
[INFO]
[INFO] local Tx ID = 13 Remote Tx ID = 10 Sending the Command 2
[INFO] Received ModifyConnectionResponse with transaction ID 10
[INFO] message =
[INFO] RQNT 14 local@127.0.0.1:2727 MGCP 1.0
[INFO] X:FFFF
[INFO]
[INFO] local Tx ID = 14 Remote Tx ID = 11 Sending the Command 2
[INFO] Received NotificationRequestResponse with transaction ID 11
[INFO] message =
[INFO] RQNT 15 local@127.0.0.1:2727 MGCP 1.0
[INFO] X:FFFF
[INFO]
[INFO] local Tx ID = 15 Remote Tx ID = 12 Sending the Command 2
[INFO] Received NotificationRequestResponse with transaction ID 12
[INFO] message =
[INFO] NTFY 17 local@127.0.0.1:2727 MGCP 1.0
[INFO] X: FFFF
[INFO] O: */AllEvents
[INFO]
[INFO] local Tx ID = 17 Remote Tx ID = 13 Sending the Command 2
[INFO] Received NotifyResponse with transaction ID 13
[INFO] Received ModifyConnectionResponse with transaction ID 10
[INFO] Received NotificationRequestResponse with transaction ID 11
[INFO] Received EndpointConfiguration with transaction ID 24
[INFO] message =
[INFO] RQNT 18 local@127.0.0.1:2727 MGCP 1.0
[INFO] X:FFFF
[INFO]
[INFO] local Tx ID = 18 Remote Tx ID = 14 Sending the Command 2
[INFO] message =
[INFO] NTFY 19 local@127.0.0.1:2727 MGCP 1.0
[INFO] X: FFFF
[INFO] O: */AllEvents
[INFO]
[INFO] local Tx ID = 19 Remote Tx ID = 15 Sending the Command 2
[INFO] message =
[INFO] NTFY 20 local@127.0.0.1:2727 MGCP 1.0
[INFO] X: FFFF
[INFO] O: */AllEvents
[INFO]
[INFO] local Tx ID = 20 Remote Tx ID = 16 Sending the Command 2
[INFO] message =
[INFO] RSIP 21 local@127.0.0.1:2727 MGCP 1.0
[INFO] RM:disconnected
[INFO]
[INFO] local Tx ID = 21 Remote Tx ID = 17 Sending the Command 2
[INFO] Sent EndpointConfigurationResponse with transaction ID 24
[INFO] Received NotificationRequestResponse with transaction ID 14
[INFO] Received NotifyResponse with transaction ID 15
[INFO] Received NotifyResponse with transaction ID 16
[INFO] Received RestartInProgressResponse with transaction ID 17
[INFO] Test of messaging capability succeeded!

Mobicents JAIN MGCP 2.0.0.CR1 Released!

amit.bhayani — Tue, 03 Feb 2009 21:32:00 -0800

We are happy to announce the first independent binary release of Mobicents JAIN MGCP Stack implementation 2.0.0.CR1 !

Before this MGCP implementation was always part of Mobicents Media Server. However MGCP is a industry standard and can be used by applications to control Media Server's other than Mobicents Media Server. To learn more about MGCP please refere to RFC 3435 and JSR 23.

Where to download from?
The distribution can be found on SourceForge.net. The binary package is mobicents-mgcp-impl-2.0.0.RC1.

zip:
https://sourceforge.net/ project/showfiles.php?group_ id=102670&package_id=308747& release_id=658531

Source repositories:
-------------------
SVN
http://mobicents.googlecode. com/svn/trunk/servers/media/ jain-mgcp

SVN TAG
http://code.google.com/p/ mobicents/source/browse/#svn/ tags/servers/media/2.x.y/jain- mgcp/mobicents-mgcp-impl-2.0. 0.RC1

How to get started & Media Server Documentation
------------------------------ -----------------
http://groups.google.com/ group/mobicents-public/web/ user-guide - Chapter 8

Looking forward to your feedback
http://groups.google.com/group/mobicents-public/browse_thread/thread/4944fde3177f813e

Mobicents Media Server 2.x.y SVN Structure

amit.bhayani — Tue, 03 Feb 2009 18:11:00 -0800

The SVN structure for Mobicents Media Server 2.x.y Source is changed a lot as compared to version 1.x.y. The new SVN structure will now look like

media

jain-mgcp
jain-megaco
mscml
jsr-309
core

server-spi
server-impl
server-sar
server-standalone
mgcp-controller
megaco-controller

examples - All standalone examples here (not depending on SLEE or Sip Servlets)
slee

mgcp
megaco
jsr-309

examples - All SLEE examples here

converged-demo
call-controller
mgcp-demo

The protocol stacks jain-mgcp, jain-meagco, mscml and jsr-309 are independent of MMS components and depends on mobicents parent.

The core/server-spi is core api design of MMS and core/server-impl is implementation of server-spi. MMS 2.x.y can be build as standalone server (server-standalone) or service in JBoss AS 5.x (server-sar). The controllers mgcp-controller and megaco-controller will be an integration of respective stack and server-spi.

The slee is special node for JAIN SLEE. slee/ra will have all the JSLEE RA's for respective stacks and slee/examples demonstrating the usage of these RA's

Rich Telco Applications with Seam

Vladimir Ralev — Tue, 03 Feb 2009 10:45:00 -0800

UPDATE: The post was edited for clarity.

The Mobicents Seam-based Sip Servlets framework was extended with Media functions and now goes beyond SIP to unify the component models for Telco and Web applications. With this move, we are addressing the need to build quickly Media-intensive applications like PBX, conferencing, Interactive Voice Response (IVR), transaction confirmation and others.

With the help of the Seam development tools these applications can be written and tested in no time, so even if you don't want to use the Seam model in your production applications, you will find it useful for smaller "disposable" applications, or for rapid prototyping and proof-of-concept applications.

Need a conferencing application?

@Name("conference")
@Scope(ScopeType.STATELESS)
public class Conference {
 @Logger Log log;
 @In MediaController mediaController;
 @In SipSession sipSession;
 
 @In(scope=ScopeType.APPLICATION, required=false)
 @Out(scope=ScopeType.APPLICATION, required=false)
 String conferenceEndpointName;
 
 @Observer("INVITE")
 public void doInvite(SipServletRequest request) throws Exception {
 String sdp = new String((byte[]) request.getContent());
 request.createResponse(180).send();
 sipSession.setAttribute("inviteRequest", request);
 if (conferenceEndpointName == null)
 conferenceEndpointName = "media/trunk/Conference/$";
 mediaController.createConnection(conferenceEndpointName).modify("$",
 sdp);
 }

 @Observer("connectionOpen")
 public void doConnectionOpen(MsConnectionEvent event) throws IOException {
 conferenceEndpointName = event.getConnection().getEndpoint()
 .getLocalName();
 SipServletRequest request = (SipServletRequest) sipSession
 .getAttribute("inviteRequest");
 SipServletResponse response = request.createResponse(200);
 response.setContent(event.getConnection().getLocalDescriptor(),
 "application/sdp");
 response.send();
 }

 @Observer( { "BYE", "REGISTER" })
 public void sayOK(SipServletRequest request) throws Exception {
 request.createResponse(200).send();
 }

}

That's all. No cheating.

What is happening here is that when an INVITE comes (i.e. when you dial the server), we connect the call to a conference endpoint in Mobicents Media Server. If this is the first call, the conference endpoint is not assigned yet (null) and we allocate a new endpoint (with .../Conference/$) for the application. Once the connection is established, the connectionOpen event occurs, then we store the conference endpoint name at the application scope and when the subsequent calls in this application see it they will connect to the same endpoint. We can easily extend this application to work with multiple conferences or add other media functionality. All SIP and Media events occur in a SIP Session, which is basically one call from one user (or one phone). If you want to share data in the SIP session scope simply inject the SipSession as shown in the application or create a SESSION-scoped Seam component. This conference example is available here. If you want to understand Mobicents Media Server and the MSC API you should read the Mobicents Media Server Guide.

In addition to the basic media support we are aiming to simplify the most common use-cases for media applications. While developing media applications I noticed that one SIP call is always constructed like this:

or the more simple chain:

In both chains the call is terminated at some media endpoint - IVR or Conference or an Announcement endpoint (which is not shown in the diagrams). After the call is established, the user agent is connected to exactly one media endpoint at any time, either directly or through a Packet Relay endpoint. This means that we can safely store all these links and endpoints related to the call right into the SIP session and never worry again about how to pass them to another method or component. If you need to switch to another chain just keep the session data updated. That's why we are looking into reserving a special place in the SIP session for the media objects.

To understand it better let's look at another example:

@Name("mediaFrameworkDemo")
@Scope(ScopeType.STATELESS)
public class MediaFrameworkDemo {
 @Logger Log log;
 @In MediaController mediaController;
 @In SipSession sipSession;
 @In MediaSessionStore mediaSessionStore;
 @In ConnectionIVRHelper connectionIVRHelper;
 @In MediaEventDispatcher mediaEventDispatcher;
 
 @In(scope=ScopeType.APPLICATION, required=false)
 @Out(scope=ScopeType.APPLICATION, required=false)
 
 String conferenceEndpointName;
 
 private final String announcement =
 "http://mobicents.googlecode.com/svn/branches/servers/media/1.x.y/examples/" +
 "mms-demo/web/src/main/webapp/audio/welcome.wav";
 
 @Observer("INVITE")
 public void doInvite(SipServletRequest request) throws Exception {
 // Extract SDP from the SIp message
 String sdp = new String((byte[]) request.getContent());
 
 // Tell the other side to ring (status 180)
 request.createResponse(SipServletResponse.SC_RINGING).send();
 
 // Store the INVITE request in the sip session
 sipSession.setAttribute("inviteRequest", request);
 
 // If this is the first INVITE in the app, then we must start a new conference
 if (conferenceEndpointName == null)
 conferenceEndpointName = "media/trunk/Conference/$";
 
 // Create a connection between the UA and the conference endpoint
 mediaController.createConnection(conferenceEndpointName).modify("$",
 sdp); // also updates the SDP in Media Server to match capabilities of UA
 }

 @Observer("connectionOpen")
 public void doConnectionOpen(MsConnectionEvent event) throws IOException {
 // Save this connection where the framework can read it
 mediaSessionStore.setMsConnection(event.getConnection());
 
 // The conference endpoint is now assiged after we are connected, so save it too
 conferenceEndpointName = event.getConnection().getEndpoint()
 .getLocalName();
 
 // Recall the INVITE request that we saved in doInvite
 SipServletRequest request = (SipServletRequest) sipSession
 .getAttribute("inviteRequest");
 
 // Make OK (status 200) to tell the other side that the call is established
 SipServletResponse response = request.createResponse(SipServletResponse.SC_OK);
 
 // Put the SDP inside the OK message to tell what codecs and so on we agree with
 response.setContent(event.getConnection().getLocalDescriptor(),
 "application/sdp");
 
 // Now actually send the message
 response.send();
 
 // And start listening for DTMF signals
 connectionIVRHelper.detectDtmf();
 }
 
 @Observer("DTMF")
 public void dtmf(String button) {
 // If the other side presses the button "0" stop the playback
 if("0".equals(button)) {
 connectionIVRHelper.endAll();
 } else {
 // otherwise play announcement
 connectionIVRHelper.playAnnouncementWithDtmf(announcement);
 }
 // Also log the DTMF buttons pressed so far in this session
 log.info("Current DTMF Stack for the SIP Session: "
 + mediaEventDispatcher.getDtmfArchive(sipSession));
 }

 // Just say OK to these messages.
 @Observer( { "BYE", "REGISTER" })
 public void sayOK(SipServletRequest request) throws Exception {
 request.createResponse(200).send();
 
 // And clean up the connections
 MsConnection connection = mediaSessionStore.getMsConnection();
 connection.release();
 }

}

This is almost the same conference application with some IVR capabilities and some comments between the lines. The MediaSessionStore stores the call-related media objects (the MsConnection in this case) and ConnectionIVRHelper will read it from there when it is doing DTMF detection or playing announcement.

Once you are connected to the conference the application works like this - when you press a button 1-9 it will play a personal announcement (only the user who pressed the button can hear it). If the users presses "0" the announcement will be stopped. Note that MediaSessionStore, MediaEventDispatcher and ConnectionIVRHelper are not part of the framework right now, but you can copy and paste them into your own application from the media framework demo application in SVN (the discussed example). Eventually the classes from the org.mobicents.servlet.sip.seam.session.framework package will be moved into the main framework jar.

Development

If you've read the previous post about the Seam framework, you would already know that these applications can use almost all Seam features including hot-deployment and JBoss Tools-assisted development. Note that you don't need JBoss Tools, you can use your own IDE or no IDE with Ant or Maven or whatever you want.

Here is what you need to get started with JBoss Tools:

Mobicents Sip Servlets 0.7.2 with JBoss AS 4.2.3 or Mobicents Sip Servlets 0.8 with JBoss AS 4.2.3 (please do not use it with JBoss AS 5.0 for now, since the Media support there is still in technology preview stage)
Install the latest nightly build of JBoss Tools in Eclipse 3.4 (this is the update site) - you need JBoss Seam, JBoss AS Tools and Richfaces plug-ins as minimum. You must use the nightly builds for Seam 2.1 support. Soon, a new JBoss Developer Studio will be released with official Seam 2.1 support.
Get Seam 2.1.1.GA and configure it as Seam runtime in JBoss Tools when asked.

Once you create a Seam 2.1 project you can extend it with the Telco framework by following these steps:

Get the sip-servlet-seam-entrypoint.jar and put in the Web App lib folder (under WebContent/WEB-INF/lib)
Put this sip.xml in WebContent/WEB-INF/ :

<?xml version="1.0" encoding="utf-8"?>

<sip-app>

 <app-name>PUT_SOME_APPLICATION_NAME_HERE</app-name>
 <display-name>SeamEntryPointApplication</display-name>
 <description>SeamEntryPointApplication</description>
 
 <main-servlet>
 SeamEntryPointServlet
 </main-servlet>

 <servlet>
 <servlet-name>SeamEntryPointServlet</servlet-name>
 <display-name>SeamEntryPointServlet</display-name>
 <description>Seam Entry Point Servlet</description>
 <servlet-class>
 org.mobicents.servlet.sip.seam.entrypoint.SeamEntryPointServlet
 </servlet-class>
 <load-on-startup>1</load-on-startup>
 </servlet>

 <listener>
 <listener-class>
 org.mobicents.servlet.sip.seam.entrypoint.SeamEntryPointServlet
 </listener-class>
 </listener>

</sip-app>

Now you are done. Just start adding Seam components.

Another way to get started is to checkout one of the examples mentioned above and play with them without IDE support (but it requires Maven).

Some guidelines

Do not subscribe methods to SIP and media events in Seam components with SESSION or CONVERSATION scopes! The reason is that each of these SESSION or CONVERSATION scoped components is likely to have multiple instances (depending on the number of the sessions) and they all will be called, which is probably not what you want.
Always subscribe public methods to SIP and media events. Any other access modifier will cause you method not to be called.
When dealing with JPA, always use your own EntityManager. Either EVENT or METHOD scoped or manage it manually through the EntityManagerFactory. The default CONVERSATION-scoped entityManager might produce "EntityManager closed" errors.
When initiating a SIP request from a Web session, do it in another thread! Seam uses thread-local storage and the Web contexts will collide with the SIP contexts. We are working on solving this issue and will probably be addressed in the future.
Keep in mind that outjection occurs at the end of a method call. If you attempt to use an outjected variable from a nested method call, it will fail.

Any feedback or contributions are welcome!

Red Hat, Mobicents at GSMA, Barcelona, Feb 16-19, 2009

Ivelin — Mon, 02 Feb 2009 07:51:00 -0800

Mobicents Media Server 1.0.0.CR5 a step closer to GA (Stable) release

amit.bhayani — Thu, 29 Jan 2009 11:34:00 -0800

Mobicents Sip Servlets 0.7.2 Released !

Jean Deruelle — Mon, 26 Jan 2009 04:52:00 -0800

This release is primarly a bug fix release where a handful of bug fixes have been fixed (see below), please note that Issue 519 can potentially break your existing apps (make sure the main-servlet element in your sip.xml is enclosed by servlet-selection element) and The JBoss version has also been updated with the latest Mobicents Media Server release (1.0.0.CR5).

Issue 482 Sip Servlet Listeners can not load classes from WEB-INF/lib
Issue 489 Problem with Subsequent Requests in MSS
Issue 494 Duplicating of URI parameters in SipURIImpl
Issue 497 Address.toString() doesn't contain any Address parameters
Issue 504 Route to Load Balancer not added in ha proxy case
Issue 505 PRACK can not be proxied properly and generate 500 response
Issue 507 URI encoded by SipApplicationSession is rejected by mobicents load balancer
Issue 514 Proxying subsequest INVITE overrides CSeq
Issue 519 Tomcat/JBoss 4 parsing not compliant with the xsd
Issue 523 java.lang.IllegalStateException: "invalidate": Session already invalidated

Downloads are here, online documentation is here, User Guide is here and the Mobicents Google Group for feedback and questions is here.

Hacking the JBoss 5 deployers to load Sip Servlets Applications

Jean Deruelle — Fri, 23 Jan 2009 03:36:00 -0800

After a great Christmas break, I came fully restored and since JBoss 5.0.0.GA was released on the fifth of December 2008, so out for about a month. Since the JBoss 5 features a great new shiny architecture :

Check Ales' introduction to JBoss MicroContainer, the component framework that transparently binds AS modules.
Also See Dimitris discussing the overhaul done to make AS agnostic to any particular component model.
A great real-world use case is Bob's work over at http://oddthesis.org, where he details the steps he took to add Rails support to AS and get all sorts of enterprise features (eg. clustering) for free in the process.

So I decided it was a really good time to make Mobicents Sip Servlets able to work on JBoss 5. So I took a look at a very good blog post from Bob McWhirter to get a first understanding of how the JBoss 5 deployers worked together to deploy a .war archive and came up with a similar design to extend the existing deployers so that JBoss 5 is now able to deploy Sip Servlets and Converged HTTP/Sip Servlets applications :

So I hacked away and about a week later, Mobicents Sip Servlets was passing the Sip Servlets 1.1 TCK on top of JBoss 5, in addition to Tomcat 6.0.14 and JBoss 4.2.3 !
You can get the nightly snapshots binaries on our hudson job if you want to try it out and give us some feedback on mobicents-public google groups

It allowed us to refactor a bit Mobicents Sip Servlets to be more modular on plugging to various containers (such as Tomcat and JBoss) so it is just a matter of maven profiles now to build Mobicents Sip Servlets on top of Tomcat or various major versions of JBoss. With even more refactoring, I'm sure we could succeed to run Mobicents Sip Servlets on top of Jetty or why not Glassfish, but that's another story ;-)

This gives us a very great foundation to experiment on top of JBoss 5, such as Building converged telco applications integrated with JRuby by example so stay tuned for more in the coming months ! :-)

You can find more details here on what currently happens in the design diagram above when loading a sip servlets application :

Note : I copied most of the content of Bob McWhirter's blog post and adapted it to show how the sip.xml and annotations are parsed and injected and combined with the other existing MetaData :

"JBoss MicroContainer look in WEB-INF/ for meta-data descriptors, such as sip.xml, web.xml and jboss-web.xml. This is where true deployment of components starts. Deployment runs through a series of stages, with deployers setup to match particular files and stages, doing the right things at the right time.

One of the earliest stages is the PARSE stage. A deployer can be bound to this stage to be given an early chance to match, parse, and act upon any meta-data file. For normal WAR deployment, the WebAppParsingDeployer does exactly that. There’s a nice hierarchy of classes to make parsing XML descriptors such as web.xml super simple.

For our Sip Servlets case we are using SipAppParsingDeployer to parse the sip.xml descriptor and create the corresponding hierarchy of JAXB classes and reusing some of the existing web.xml ones when it is possible (ie when the sip_app.xsd reuses some javaee types from the web_app_2_5.xsd). It is indeed super simple :-)

The WebAppParsingDeployer is the bridge from a web.xml file sitting on the filesystem or in an archive to the MetaData deployment bits. The parser reads web.xml, and produces a WebMetaData object associated with the deployment. The WebMetaData is simply a nice object-tree representing anything you can denote in web.xml.

Same thing here in our case, we use a SipAppParsingDeployer. The parser reads sip.xml, and produces a SipMetaData object associated with the deployment. The SipMetaData is simply a nice object-tree representing anything you can denote in sip.xml.

We also might have a jboss-web.xml meta-data in our WAR, and that is parsed (during the PARSE stage) in our case by the JBossConvergedSipAppParsingDeployer (instead of JBossWebAppParsingDeployer). This deployer, like the previous, reads the jboss-web XML file and creates, in this case, a JBossConvergedSipMetaData (instead of JBossWebMetaData) object. It is also gathering the previous MetaData (SipMetaData and WebMetaData) and merged them with itself.

Once we’ve parsed these .xml files, the container has enough information to build up the classpath for the component. Some of these deployers have also thrown off or modified some ClassLoadingMetaData, which describe paths that should be added to the classpath.

As the container enters the CLASSLOADER stage of deployment, other magic occurs to actually set up the classpath.

After that, There is annotations parsing through ConvergedSipAnnotationMetaDataDeployer that produces SipMetaData and WebMetaData also but based on the annotations instead of the xml descriptors this time

In the end, it’s the JBossConvergedSipMetaData (instead of JBossWebMetaData) that drives the ultimate deployment, but what if we don’t have a jboss-web.xml? That’s where the MergedJBossConvergedMetaDataDeployer (instead of MergedJBossWebMetaDataDeployer) comes in. It looks for SipMetadata (parsed from the sip.xml and the annotation based one), WebMetaData(parsed from the web.xml and the annotation based one), and a JBossWebMetaData if one has been parsed, and merges everything into a singular JbossConvergedSipMetaData (instead of JBossWebMetaData).

I’m a little fuzzy on the ins and outs of the CLASSLOADER stage at this point, but magic occurs there.

And our app still isn’t deployed yet. But we’re getting there.

Finally, we enter the REAL stage of deployment, which fittingly-enough, is where the actual deployment occurs. Hooray!

Our TomcatConvergedDeployer (instead of TomcatDeployer) that is sip servlets aware is hanging out there, waiting for JBossWebMetaData objects to appear. When it sees one, it checks if the application is a sip servlets application (by checking if a sip.xml descriptor or Sip Servlets annotations are present), if it is not it deploy as a standard web app otheriwse it goes to work setting up information for our extended Tomcat (that is sip servlets aware) to deploy a sip-app. It configures everything in Tomcat from the information other deployers figured out from sip.xml, web.xml, jboss-web.xml and annotations and embodied in the MetaData by creating a TomcatConvergedDeployment (instead of TomcatDeployment for a standard webapp).

This TomcatConvergedDeployment also sets up the private jndi for the webapp and binds the needed objects to it (like SipFactory, TimerService and SipSessionsUtils). It also set the InjectionContainer, TomcatConvergedSipInjectionContainer(instead of TomcatInjectionContainer) so that needed objects can be injected into annotated attributes of the archive.

It jams it into Tomcat, hits the big red “go” button, and port 5080 is serving you sip-app (and port 8080 also if this is a HTTP/SipServlets converged application).

Finally. :-)

Jean

Media Gateway Control Protocol Stack Performance improved

amit.bhayani — Mon, 22 Dec 2008 01:41:00 -0800

Mobicents at Devoxx

Vladimir Ralev — Sat, 06 Dec 2008 06:33:00 -0800

UPDATE: Making the slides available in PDF and google documents.

And if you want to view in your browser here is the quickie and this is the BOF (some formatting is lost).

Devoxx (a.k.a. JavaPolis) is starting tomorrow. Ed and I have a converged applications BOF on Day 2, where we will be covering the Mobicents platform and you can ask questions about any Mobicents technology - JAIN SLEE, Sip Servlets, Media Server, etc. Also, there will be another talk on Mobicents Sip Servlets about what's new and cool there. Among other things, I will be demoing the Seam integration, how to code&deploy SIP applications quickly with JBoss Developer Studio and possibly some ways to make active Web UI with AJAX and Reverse AJAX.

If you are up for a meeting ping me on vladimir.ralev at gmail.com.

Looking forward..

100 Million calls served for Mobicents Sip Servlets 0.7.1

Jean Deruelle — Tue, 02 Dec 2008 18:19:00 -0800

Mobicents Sip Servlets 0.7.1 that we just released yesterday has been through a load test done by Luis Barreiro, our dedicated QA engineer for the Mobicents Platform.

The load test went on for 80 hours at a rate of 350 calls per seconds and served about 100 Million Calls :-)

For more information regarding the test, hardware, reproducibility and the report, see the announcement on the Mobicents google group

Mobicents Sip Servlets 0.7.1 Released !

Jean Deruelle — Mon, 01 Dec 2008 22:01:00 -0800

This version is primarily a bug fix release over version 0.7 where Issue 481 reported against 0.7 has been fixed and the default concurrency control mode was updated from "SipSession" to "None" to cope with the Issue 480.

Downloads are here, online documentation is here, User Guide is here and the Mobicents Google Group for feedback and questions is here.

Mobicents Sip Servlets 0.7 Released !

Jean Deruelle — Sun, 23 Nov 2008 21:14:00 -0800

Here is our new release since we got Sip Servlets 1.1 certified about a month and a half ago which made us the first open source Sip Servlets 1.1 (JSR 289) container to be certified and as of now still the only open source one to be certified :-)

The focus of this release has been to get more production carrier grade features integrated into Mobicents Sip Servlets such as :

Concurrency and Congestion Control,
Mid Call Failover and Clustering Support for all kind of pure SIP Applications (Proxy, B2BUA, UAC, UAS),
Seamless integration into JOPR and Embedded JOPR (JBoss Administration console), the JBoss Enterprise management solution
Diameter support for charging in Technology Preview.

We also started to utilize the JBoss Seam framework so that it can now be used to enhance your sip servlets application and development experience : http://www.mobicents.org/mss- seam.html

Our Mobicents Sip Servlets implementation run on top of Apache Tomcat 6.0.14 and now on JBoss AS 4.2.3.GA and is shipped with Mobicents Media Server 1.0.0.CR3

The other highlights of this release are :

Two new shiny examples :

a conference media server demo application built on GWT with server-push updates, see http://www.mobicents.org/ conference-demo.html and vlad's blog post about it at http://vladimirralev.blogspot. com/2008/10/conference-demo- for-sip-servlets.html

a Diameter Event Charging service based on Location Service that performs call charging at a fixed-rate (event charging).

Mobicents Sip Servlets User Guide : http://hudson.jboss.org/ hudson/job/ MobicentsDocumentation/ lastSuccessfulBuild/artifact/ html_single/index.html# chapter-Mobicents_SIP_ Servlets_Server

More SIP Extensions supported

Move to JBoss AS 4.2.3.GA

Downloads are here, online documentation is here, User Guide is here, the 0.7 changelog and roadmap is here and the Mobicents Google Group for feedback and questions is here.

Thanks to Alex and Hauke Dämpfling for their contributions to this release.

Enjoy !

Cheers
Mobicents Sip Servlets Team

One year @ JBoss : Mobicents Sip Servlets 0.7 released !!!

Jean Deruelle — Mon, 24 Nov 2008 02:11:00 -0800

It's been now one year since I joined JBoss, a division of Red Hat and about a month and a half since our last release that made Mobicents Sip Servlets the first Open Source container to become Sip Servlets 1.1 (JSR 289) certified.

So it was due time for another release and we wanted it to be feature packed so here goes the review of the latest and greatest of Mobicents Sip Servlets that you can download here

First, Concurrency Control. It defines here how a sip servlets application can be accessed concurrently and what would its expected behavior in this case. Although the JSR 289 Expert Group couldn't agree on a concurrency control mechanism for JSR 289 and that feature has been postponed to the next version of the spec, we believe this feature can greatly simplify the life of the Sip Servlets developers. Also in getting more experience on that front and feedback from the community we would like to start to draft a proposal for inclusion in the next revision of the specification.
So Mobicents Sip Servlets supports not one but three concurrency control modes :

None - is the one defined (or not defined...) by the specification and the developer is reponsible for synchronizing access to shared resources such as SipSession or SipApplicationSession attributes or objects held by those sessions.
SipSession : This mode guarantees that two or more messages from the same SipSession will never be processed simultaneously. They will be serialized on the SipSession meaning that they will be processed sequentially by the sip servlet in the order of their arrival so you can access SipSession attributes in a safe way.
SipApplicationSession : This mode guarantees that two or more messages from the same SipApplicationSession will never be processed simultaneously so you can access SipApplicationSession attributes and the SipSession attributes in a safe way.

Those different concurrency modes for now only take into account SIP messages for serializing access to either the SipSession or SipApplicationSession which means that you have to be careful if you are accessing shared resources in an unmanaged way, for example if you access a SipSession attribute from an unmanaged thread or from EJB this access will not be synchronized. But we are working on it :-)

Congestion Control : All the messages that arrives in the Mobicents Sip Servlets container will go, after some initial processing, in a queue to wait for, depending on the chosen concurrency control mode, a free thread or the lock on the session to be released. If this queue gets full the container will start rejecting any new SIP requests (except ACK) with SIP error code 503 until the server catches up. Note that only SIP requests will be rejected, the SIP responses that arrive at a full queue will be stored and processed sooner or later. In the future we will be adding more congestion control mechanisms like memory threshold, CPU threshold, choose between sending 503 or just dropping any new message coming in depending on the load threshold... so stay tuned !

Enterprise Monitoring and Management Console through Seamless integration into JOPR and Embedded JOPR (JBoss Administration console), the JBoss Enterprise management solution : I just blogged about it 3 days ago so for more details see my blog post.

Mid Call Failover Support : We completed our HA capabilities for pure SIP applications so you can now failover to any node in the cluster in the middle of a call for all kind of pure SIP Applications (Proxy, B2BUA, UAC, UAS) ! We will now be working on failover for converged applications and add performance and stability automated test based on smartfrog so that it becomes final.

We also have been working on two great new features and wish some community feedback on them so we first introduce them as Technlogy Preview into this 0.7 release :
JBoss Seam framework is now able to enhance your sip servlets application : As Vladimir is currently working on a cool PBX application, he was feeling that this was not enough :-) so he started to dig and hack on how the JBoss Seam framework could be utilized to simplify the Sip Servlets application development and has been very successful, See his blog post about it and the public discussion. As we were discussing together the implications of this, we decided to start a subproject dedicated to it to rock the sip servlets world and continue our unification task (between Sip Servlets and Http or Sip Servlets and JSLEE) the same way Seam has been rocking the http servlets world. So check it out and see how it can improve your Time to Market and development experience all together and don't forget to give us your feedback and what you would like to see improved or implemented.

Diameter support : For users of Mobicents Sip Servlets, we wanted them to be able to charge calls that are going through their applications so Alexandre Mendonça who is leading the Diameter project for the Mobicents platform, has tremendously helped us in getting us Diameter support and hacked a Sip Servlets Diameter Event Charging application based on the Location Service example that performs call charging at a fixed-rate (event charging), so check it out and give us your feedback. Alex is now planning on getting more of the Diameter protocol implemented and as he go, he will hack Sip Servlets applications that showcase the different possible call flows to help you do Authentication, Authorization and Accounting on top of Mobicents Sip Servlets.

Also we got 2 new shiny examples, the Diameter Event Charging one that we just discussed and the Conference Media Server application built on GWT with server-push updates to provide desktop-like experience for the user interface. This application is in response to the high demand of the community for Media Conferencing on top Mobicents Sip Servlets and this example will be later integrated into the PBX application that Vlad is builing.

Also with all those new features, we moved to the latest version of JBoss AS 4.2.3.GA and also comes the usual round of bug fixes and enhancements comprised of an updated Management Console, more SIP Extensions (PRACK, OPTIONS, INFO), and more.

Check out our roadmap to see what's coming next !

Feel free to give us your feedback on the Mobicents Google Group
Thanks for using Mobicents Sip Servlets !

Mobicents Sip Servlets gets a shiny new Administration console !

Jean Deruelle — Fri, 21 Nov 2008 07:07:00 -0800

As some of you might be aware, earlier this year JBoss released Jopr, an enterprise management solution for JBoss middleware projects and other application technologies based on RHQ, and Embedded Jopr, which will become the new JBoss Administration console and is based on Jopr.

Since the project does provide great extensibility and thanks to the good documentation of the project and its plugin architecture (see http://pilhuhn.blogspot.com/2008/05/writing-rhq-plugin-part-1.html and http://support.rhq-project.org/display/RHQ/RHQ+Plugin+Community) we decided that it was time for Mobicents Sip Servlets to be seamlessly integrated into those great projects and finally have a way to being administrable into large scale enterprise deployments.

So we hacked our own plugin. We decided to start simple with http://support.rhq-project.org/display/RHQ/Writing+Custom+Plugins#WritingCustomPlugins-GettingStartedQuickly and provide accessibility to the SipApplicationDispatcher, which is a central piece in the Mobicents Sip Servlets Architecture since it has the responsibility of dispatching the SIP requests and responses (that is gets from the underlying jain-sip stack) to the deployed Sip Servlets applications.
So you can control the concurrency and congestion control of the server through it. This was really a piece of cake and was done and working in an afternoon.

Excited by the easiness to integrate into jopr, we decided to provide metrics for Sip Sessions and Sip Applications Session available into standard pure SIP Servlets applications or converged Java EE/SIP applications about the same way it is currently done in Jopr for HTTP Sessions. Same thing, it was done real quick and with a result showing seamless integration into jopr. See our Mobicents Sip Servlets jopr plugin that works for both Jopr and Embedded Jopr.

It took us about 2 days to complete the task 1 day of coding and discovering and one day of polishing and documenting... To try it out just download the latest release of Mobicents Sip Servlets and drop the embedded jopr war that contains our plugin in the server/default/deploy directory and hit http://localhost:8080/embedded-jopr

I have only one thing to say, thanks to the JBoss Operations Team for providing such a good project that saved us quite a bit of time to have a full blown enterprise management solution for our project. Keep up the good work, guys !

Performance of Mobicents Media Server 1.0.0.CR3

amit.bhayani — Fri, 21 Nov 2008 04:24:00 -0800

JBoss Seam enhances Sip Servlets

Vladimir Ralev — Thu, 20 Nov 2008 08:33:00 -0800

Seam-managed SIP components. How about that? Seam components can now handle real SipServletRequests while taking advantage of the Seam perks - bijection, scoping, transaction management, interceptors and everything else.

Your SIP and HTTP Servlets are running in the same servlet context and they share the same application-scoped components, while the session-scoped components are mapped to the respective SIP and HTTP sessions*. You can work with both EJBs and POJOs, interact with your web-layer, and still build very loosely coupled telco components working on the same messages without being aware of each-other. Seam provides synchronous and asynchronous light-weight message passing through the @Observer-annotated methods, which covers most of the communication needs in converged applications.

How it works?

The Seam 2 core is now mostly independent of HTTP Servlets and JSF. Basically we hooked a controller Sip Servlet and session listeners to the Seam lifecycle to control the context assignment for incoming SIP messages. When a SIP message arrives, we raise Seam events to notify the Seam components subscribed to receive the SIP events. We had to use a small Java reflection hack to reach some protected Seam contexts, but I believe it is safe. We will try to make it more clean.

The setup is straightforward - just add the controller servlet to your Seam application in a Sip Servlets container and it's ready to go. For now you can start with the sample application.

Theoretically this technique can work on any JSR289-compliant container that supports JBoss Seam, but I have only tested it on Mobicents Sip Servlets 0.6/0.7 with JBoss Application Server 4.2.3 and Seam 2.1.0.SP1.

One example

This is simple SIP service which responds to an INVITE and counts the number of messages per session. There is a session-scoped counter, which is incremented on every message. Note how you can subscribe methods to SIP events. You can subscribe as many methods as you like in any Seam component, they all will be notified.


@Name("simpleSeamSipService")
@Scope(ScopeType.STATELESS)
@Transactional
public class SimpleSeamSipService {
 @Logger Log log;
 @In SessionMessageCounter sessionMessageCounter;

 public void incrementMessageCounter() {
 sessionMessageCounter.increment();
 log.info("Processed SIP messages "
 + sessionMessageCounter.getMessages());
 }

 @Observer("INVITE")
 public void doInvite(SipServletRequest request)
 throws Exception {
 incrementMessageCounter();
 request.createResponse(180).send();
 Thread.sleep(100);
 request.createResponse(200).send();
 }

 @Observer("ACK")
 public void doAck(SipServletRequest request)
 throws Exception {
 incrementMessageCounter();
 }

 @Observer({"REGISTER","BYE"})
 public void sayOK(SipServletRequest request)
 throws Exception {
 incrementMessageCounter();
 request.createResponse(200).send();
 }

 @Observer({"RESPONSE"})
 public void sayOK(SipServletResponse response)
 throws Exception {
 incrementMessageCounter();
 }
}

You should keep in mind that the Seam events are application-wide. If you need cross-application messaging use JMS (which accidentally is also effortless with Seam).

And here is the SIP-session scoped component:


@Name("sessionMessageCounter")
@Startup
@Scope(ScopeType.SESSION)
public class SessionMessageCounter {
 private int messages;
 
 public int getMessages() {
 return messages;
 }
 
 public void increment() {
 messages++;
 }
}

Actually, this component is created and stored in every Seam session, no matter if it's SIP or HTTP. This is a bit inefficient, but has some advantages. Ultimately we would want to have a separate SipSession and SipApplicationSession scopes in Seam and we will probably get there with the user-defined scopes in Web Beans (JSR 299) or a newer version of Seam.

Why use it?

All the Seam goodness.
Development will be easier, because you can take advantage of the Seam WEB-INF/dev classloader to deploy Seam components faster. Otherwise you have to redeploy the whole war/ear (10-20 secs vs 1-2 secs). This feature is not perfect yet.
Testing - Seam provides a great framework for testing based on dependency injection and mocking.
Programming model is practically the same as the one you use for Web apps with Seam and similar to the future Web Beans.
Potential to integrate with jBPM and JBoss Rules through Seam. (contributors?)

Why not to use it?

It is not standards-based.
Performance is suffering a bit with Seam.

You can find the sample application in SVN:
http://mobicents.googlecode.com/svn/trunk/servers/sip-servlets/sip-servlets-seam

We will soon provide a kit for integrating this capability in your applications. Until then, use the sample application.

*(We currently have no use for conversation scope in SIP.)

A week at MTN, Nigeria

amit.bhayani — Sat, 15 Nov 2008 04:02:00 -0800

A Conference Demo for Sip Servlets

Vladimir Ralev — Fri, 24 Oct 2008 17:44:00 -0700

UPDATE: Now the Media Server has been released and the application doesn't need any tweaks to work. All dependencies come from the maven repository.

There is a new example application for Sip Servlets - a conference demo. Conferencing has been important for many of our users and this is a good way to get them started and show them how easy it is. In fact I spent more time fighting with Maven than actually writing the code for this example (and I know this is not really an achievement).

The features demonstrated by this applications are the following:

Mobicents Media Server 1.0.0.CR2 - the latest version of Media Server with the latest MSC API. This Medis Server is not released yet, so you will need to build it from the trunk.
Sip Servlets Conference API Preview - this API will help Sip Servets users to create and manage conferences in Media Server and will be part of the future Mobicents Sip Servlets PBX.
Server Push updates with GWT - providing instant updates in the browser about the conference status without polling and enabling desktop-like experience. JSR 315 (HTTP Servlets 3.0) will have support for delayed request/response handling, so this is definitely becoming part of the asynchronous web applications in Java, which is particularly useful for real-time interaction with telco applications.
Completely annotated Sip Servlets application - minimum glue code and XML.

The application still has some bugs, but I am working on it.

The example is available in SVN from here.

Jain Sip is working on top of android

Jean Deruelle — Wed, 22 Oct 2008 11:36:00 -0700

I had a bit of free time yesterday night and I noticed the first google android powered phone hit the market in USA so I said to myself, what if I tried to port jain sip stack to android...
Not so much work should be needed since android supports a lot of the JDK 1.5 packages natively. So I tried and believe it or not, no work was actually required to make the jain sip stack work on android, it just runs :-)
Again kudos to Ranga for such a great stack :-) and to Google for having a nice OS where you can really reuse most of your Java applications (pending a rewrite of the UI)

So here is my proof of concept :
I ported the well known Shootist and Shootme examples from the sip stack to android and uploaded a zip here that you can play with.

The zip contains shootist and shootme standard examples and shootist and shootme android examples. Unzip in a location that we will call

So first you need to have the android SDK installed and have the android tools on your path (see the Android installation instructions for that)

Then you can start the android emulator with the following command:

$ emulator

from , do the following :

$ cd shootme-android/bin/

and then

$ adb install shootme-android.apk

this install the shootme android example application into the emulator
go back to and do the following :

$ cd shootist-android/bin/

and then

$ adb install shootist-android.apk

this install the shootist android example application into the emulator

You can see the applications installed in the emulator by clicking on the gray arrow at the bottom of the android phone screen :

Ok so much for the installation of the applications into android. Now let's get real and have some fun. Let's try the shootme android application first.

on the emulator, go to the menu and select the application called shootme.
It says that the jain sip stack has started on 10.0.2.15 (localhost's emulator ip address of android)

Since the emulator has its own ip address system we need to setup a UDP redirection from our host's localhost:5070 to the emulated system's localhost:5070 so that teh shootme android application can be pinged from our shootist standard application with the following command

$ adb emu redir add udp:5070:5070

let's start the standard shootist example so that it calls shootme and that a SIP call flow (INVITE-OK-ACK and then BYE-OK) is done between them.
go back to and do the following :

$ cd shootist/dist

and then

$ java -jar shootist.jar

you should now see the messages being exchanged between the shootme android application and the shootist standard application.

if the emulator sip messages are not enough, more log is available through the command

$ adb logcat

now kill the shootist app with Ctrl+C and close the emulator

You can also do the reversed example and start first the shootme:

Since the emulator has its own ip address system we need to setup a UDP redirection from our host's localhost:5060 to the emulated system's localhost:5060 so that the shootist example application can be pinged back from our shootme standard application with the following command

$ adb emu redir add udp:5060:5060

let's start the standard shootme example so that it waits to be called by the shootist android applicationand that a SIP call flow (INVITE-OK-ACK and then BYE-OK) is done between them.
go back to and do the following :

$ cd shootme/dist

and then

$ java -jar shootme.jar

on the emulator, go to the menu and select the application called shootist.

You should now see the messages being exchanged between the shootme android application and the shootist standard application.

if the emulator sip messages are not enough, more log is available through the command

$ adb logcat

Please post comments if you have problems running the examples or if you want to give me some feedback...

Mobicents Metamorphosis

amit.bhayani — Fri, 03 Oct 2008 13:13:00 -0700

Mobicents JAIN-SLEE Server 1.2.0.GA released!

EDUARDO MARTINS — Thu, 02 Oct 2008 20:02:00 -0700

Hooray, the long-waited stable 1.2 release of Mobicents JAIN-SLEE Server is finally available. Check out the details of this fine release here.

Custom XCAP Application Usages on Mobicents XDMS

EDUARDO MARTINS — Wed, 01 Oct 2008 04:43:00 -0700

In case you want to learn about XCAP Application Usages and how those are implemented in Mobicents XDM Server, so you can add a custom one, or contribute with a standard one not available (such as poc), please have a look at this slides.

The Mobicents team met in Munich, Germany to plan…

EDUARDO MARTINS — Wed, 01 Oct 2008 04:35:00 -0700

The Mobicents team met in Munich, Germany to plan 2009 and have some fun. You can download the presentations I made, regarding the features & development plan for Mobicents JAIN SLEE Server 2.x and an introduction to the SIP Presence Service, which explains why you should go for it. Additional presentations can be found here.

Me and Jean Deruelle, Mobicents JAIN SLEE & SIP Servlets Interoperability in late meeting!

Using Mobicents with Legacy Network Elements (PSTN, SS7)

Ivelin — Tue, 30 Sep 2008 13:31:00 -0700

Mobicents becomes the First Open Source Certified SIP Servlets 1.1 (JSR 289) container

Ivelin — Tue, 30 Sep 2008 12:48:00 -0700

Mobicents Sip Servlets 0.6 achieves JSR-289 compliance!

Vladimir Ralev — Tue, 30 Sep 2008 05:52:00 -0700

The freshly released Mobicents Sip Servlets 0.6 is now the first open-source JSR-289 compatible server. Or more precisely two servers, since we have both JBoss and Tomcat versions.

Pick your distro from here.

Read more in Jean Deruelle's blog, the official announcement and the project homepage.

If you enjoy watching successful TCK results:

Jean is the man!

Mobicents Sip Servlets is Sip Servlets 1.1 ( JSR 289) certified !!!!

Jean Deruelle — Tue, 30 Sep 2008 14:15:00 -0700

Mobicents is the First Open Source Certified Server - Again.
After being the first JSLEE 1.0 certified open source server (To my great delight, I hacked on that part too about 5 years ago and had the pleasure to pass this TCK too), now Mobicents is the first Open Source SIP Servlets 1.1 server as well....
which makes JBoss the first vendor to certify even among commercial vendors, not counting the company who wrote the TCK....
In other words, we were the latest to enter the game of the SIP Servlets vendors, we built our server from scratch in about a year and now are the first to be certified, isn't that great :-) ?
Not only that but we also features capabilities that are outside the scope of the specification such as :

We are also driving towards a converged model between SIP Servlets and JSLEE and the first logical step : interoperability has been made possible on the Mobicents Platform since JBoss is the only vendor to implement both specifications so that you can benefit from the best of both worlds.
The IEEE paper that has been published related to this work will be made available soon.

I would like to personally thank all the people that worked with me in making this dream (actually it was a hell of a work :-)) come true :

* M. Ranganathan that mentored me in the open source world from my early days of work (I always remember my first assignment hacking with you on the jain sip applet phone hearing our voices fast forwarding in the NIST premises :-) ) that started this project and put all of us in it :-), for your help working with us to design and hack together during the first versions of the project and later on in giving your gold advices to keep us on track, for your work on jain sip and the nist sip stack (jsip rocks and rolls !!!) that we use as the underlying sip connector and for having the passion of the true digital monkey hacker. My inner bonobo is jumping around :-)

* Valdimir Ralev for working like hell on the project during the beginning until the fun of the last month while passing the TCK and the joy of today :-) and for the fun we had in our virtual garage :-). Thanks so much for the great work.

* Bartosz Baranowski for your help working with us to design and hack together during the first versions of the project.

* Ivelin Ivanov for making me part of the JBoss dream, that made the Mobicents Open Source Platform possible and what it is now and mentoring me along the way and for all the fun during the wild trips abroad... You're a hell of a guy, wild at heart :-)

* Our fellows at Tomcat and JBoss that build the containers on which this work has been made possible.

* Mihir Kulkarni from Oracle for its timely replies about the TCK tests.

* The JSR 289 expert group members for their commitment and hard work
on the specification. (it was good to see you guys in LA)

It feels so good... I love this job !

Note : See Ivelin's post and Vlad's post about it also.

Mobicents team visits the Red Hat office in Munich

Vladimir Ralev — Thu, 25 Sep 2008 07:06:00 -0700

We started with an inventory inspection. Turned out there is enough beer in the office to host the entire Oktoberfest. As a moral obligation we had to reduce the amount of alcohol to the lawful limit. Then we moved on to the real Oktoberfest (managers know it as an important telecom conference). After this, everything is blurry.

In the few flashbacks I have from time to time there are some slides about Mobicents, german bars and "forty dollar". Later, a summary of the meetings surfaced here. Check it out if you are interested in the Mobicents roadmaps and current status. I see some exciting things there :)

On the flight back to home (trying to impress the girl next to me) I mixed wine, beer, coffee and apple juice. It rocks.

Munich, sorry for the mess.

Mobicents 2008 core team meeting

Ivelin — Thu, 25 Sep 2008 05:41:00 -0700

Mobicents Webinar recording now available !

Jean Deruelle — Wed, 10 Sep 2008 03:04:00 -0700

There is an online recording available of the Mobicents Webinar recently hosted by me where you can see most of the products that are composing the Mobicents Communications Platform as well as a demo showcasing a converged application built on top of Seam, Mobicents SIP Servlets and Mobicents Media Server deployed on Jboss AS.
If you missed the live session, make sure to take the time to watch this update on the latest and greatest from Mobicents. You will also learn where we are headed in the future.

Please post feedback about the webinar to this thread.

Have fun !

Mobicents JAIN-SLEE Server 1.2.0.CR2 released!
EDUARDO MARTINS — Fri, 29 Aug 2008 11:24:00 -0700
Mobicents JAIN-SLEE Server 1.2.0.CR2 released!

This release improves 1.2.0.CR1 stability with a few fixes on the JAIN
SLEE core and examples. Here is the list of issues fixed.

This release also provides a new version of an old but useful example,
the SIP Wake Up Service.

What is included:
-------------------------------------------------------------------------------
* Core JAIN SLEE Server
* Management Console
* Resource adaptors: SIP RA, SIP11 RA (complaint with JAIN SLEE 1.1
specs), JCC RA, XMPP RA, SMPP RA, HTTP Client RA, HTTP Servlet RA,
Asterisk RA, Text to Speech RA, Rules RA, Diameter Base RA
* Educational examples: Google Talk Bot, SIP Services, SIP Wake Up
* Sources zip for debug purposes

Where to download from?
-------------------------------------------------------------------------------
The distribution can be found on SourceForge.

More info here.

Mobicents Sip Servlets is now HA grade !

Jean Deruelle — Thu, 21 Aug 2008 07:12:00 -0700

As you may have noticed, we released our 0.5 version of Mobicents Sip Servlets about a week ago now following our release early, release often moto and fresh back from my vacations, I wanted to go into more details with you on the great new feature of this version : You can now start to cluster your UAS type of SIP servlets applications and you'll have built-in mid-call failover support for it !

What do this mean to me you may say ? Read on...

By using our Mobicents SIP Load Balancer and the new shiny Mobicents SIP Servlets Clustering with let's say 2 nodes A and B, you'll be able to execute the following call flow :

Start a call that goes through the Load Balancer and is handled by node A (the sip session and sip application session as well as their Serializable attributes are going to be replicated on node B)
kill node B and wait that it is completely stopped
Hangup the call, the tear down of the call will be handled correctly by node B with all the session attributes that were present on node A available on node B.

If you want to try it out, you'll need to use our Mobicents Sip Servlets JBoss release and use the pre-configured cluster-enabled server (the all profile configuration) that comes bundled with it.

You can follow the step by step examples described in the Mobicents Sip Servlets Failover Documentation

Please note that this feature is still limited to UAS type of applications and that support is coming for Proxy, B2BUA and Converged type of applications in the following releases.

Feel free to post you feedback and to contact us if you'd like to contribute.
We like to hear from you.

Mobicents SIP Presence Service 1.0.0.BETA2 has…

EDUARDO MARTINS — Wed, 13 Aug 2008 17:57:00 -0700

Mobicents SIP Presence Service 1.0.0.BETA2 has been released. This release is the first binary publicly available! More info here. Enjoy!

Mobicents JAIN SLEE Server 1.2.0.CR1 has been…

EDUARDO MARTINS — Wed, 13 Aug 2008 09:41:00 -0700

Mobicents JAIN SLEE Server 1.2.0.CR1 has been released. This release is the first candidate for the 1.2.0 GA and hopefully will be the last. More info here.

Tested my SIP enabled mobile phone with Mobicents Server

amit.bhayani — Wed, 09 Jul 2008 10:32:00 -0700

Mobicents Sip Servlets 0.4 Released !

Jean Deruelle — Wed, 25 Jun 2008 03:18:00 -0700

Yesterday we just released the 0.4 version of Mobicents Sip Servlets with some interesting hot new features.
It is shipped with :

Management Console
Educational converged example : Click To Call
Mobicents Media Server 1.0.0-BETA2-SNAPSHOT (JBoss only)

To download this release and try it out, follow the following link :

Mobicents Sip Servlet 0.4 downloads

This is our latest release working on top of both containers Tomcat 6.0.14 or JBoss AS 4.2.2.GA providing some new features, bug fixes, enhancements and so on. Let's review what's new.

Load Balancing & Failover support : Load Balancing and Failover is a hot new feature that has just been added. The feature is still in its basic stage meaning that you can load balance on any number of nodes that are registered with the sip load balancer. The Sip load balancer uses a round-robin algorithm to cycle through a list of Mobicents sip Servlets nodes in order. Some other load balancing algorithms will be added such as algorithms where the health status of the servers are taken in account to avoid overloading a server already full by example.
Currently any Mobicents Sip Servlets node can act as a backup node. So if one node fails, all new calls will be redirected only on the still alive remaining nodes.
Mid-call failover where another node of the cluster could recover a dialog from a failed node is not supported yet but should be added pretty soon.

Performance improvement/Performance apps : We worked on providing some automated SIPp tests and scripts to measure, and improve over time, the performance of Mobicents Sip Servlets on Tomcat and JBoss. Here is what we achieved Tomcat 6.0.14, JDK 1.5 : Call rate was 100 calls/sec for 24h, for a total of 8.640.000 calls on a standard server with 2x AMD 2220 SE processors and 8GB of RAM. Performance on JBoss is being measured but since the core logic (just the wiring is different) is the same we should have the same kind of results on both containers.

JSLEE/SIPS interop application : As JBoss is the only vendor to implement both
specifications, JSLEE and Sip Servlets, through its Mobicents Communication Platform, this makes it a natural fit to build converged and interoperable JSLEE/SIP Servlets applications that are able to comply with standards in a portable manner. This application is a proof of concept of integration and interoperability between JSLEE and Sip servlets and has been shown at JavaOne 2008 in San Francisco (see my previous post and posts from other Mobicents team members Vladimir Ralev and Ivelin Ivanov). As we're acquiring experience with Java EE, JSLEE and SIP Servlets, this is a first step towards the process of driving a unified programming model, so stay tuned !

Facebook click to call application : This example shows how SIP Servlets can be used along with HTTP servlets to create a Facebook plugin that allows users to call real phones through a SIP-PSTN gateway provider. See Vladimir Ralev's post for more information on this killer app !

More Extensions : SUBSCRIBE/NOTIFY is now supported

We aligned on the JSR 289 Proposed Final Draft API

We merged SIP Session Management with HTTP Session Management : Our Sip Session Manager was previously completely separated from the http session management mechanism, we just moved the Sip Session Management where it should be, with the http session management. This would help us to provide more integrated Session Management and reuse some of the work done on http session clustering in JBoss for Sip session clustering.

and the usual round of various enhancements and bug fixes :
Derived Sip Sessions
Servlet-mapping still supported in 1.1
New Cancel methods on Proxy feature
Move adding of Via header to send() instead of B2buaHelper.createRequest
Routing to external application server
Application Redeployment Bug Fixed
Escaped characters not supported in SIP URI
Fix for the creation of subsequent requests for a given sip session.

See Mobicents Sip Servlets for more information.

You can also check our Mobicents Sip Servlets Roadmap to see what's coming next.

Mobicents looking for A+ Product Manager

Ivelin — Sat, 14 Jun 2008 13:40:00 -0700

A JAIN SLEE beginner's tutorial? That's a…

EDUARDO MARTINS — Tue, 10 Jun 2008 07:16:00 -0700

A JAIN SLEE beginner's tutorial? That's a question I see frequently in Mobicents forums, and so I decided to write one that examples how to use Mobicents JAIN-SLEE Server and the last tools we made around Apache Maven2. You can call it "Developing a Hello World JAIN SLEE service in 30 minutes or less".

Of course, before we need a working environment, so you need to install Mobicents JAIN SLEE server binary (don't forget to add an environment variable JBOSS_HOME pointing to the jboss-4.2.2.GA directory of the Mobicents install), and for this tutorial you will also need the Eclipse IDE and Apache Maven2. Additionally you will need to setup Mobicents JAIN SLEE Maven Archetypes. Click on the links for instructions on how to do that.

Ready to rumble? Lets start by creating the Maven2 project using Mobicents JAIN SLEE Maven Archetypes.

Part 1 - Creating the Maven2 project

Open a bash/terminal/command line in the Eclipse workspace directory and type

mvn archetype:generate -DarchetypeCatalog=local

The Maven2 Archetype plugin will ask you what archetype you want to use, introduce the number for jain-slee-basic-service. Second it will ask you the values for some properties:

groupId - introduce org.mobicents.slee.example
artifactId - introduce hello-world
version - just press enter to accept default value
package - introduce org.mobicents.slee.example again

After defining those properties the plugin will ask you to confirm it, introduce y.

The process will finally build the project, which will be a directory named hello-world.

Part 2 - Create the Eclipse project and import it in the Eclipse workspace

Ensure Eclipse is closed, and in the bash/terminal/command line (Eclipse's workspace directory) do

mvn -Declipse.workspace=. eclipse:add-maven-repo

Maven will add a variable M2_REPO to Eclipse pointing to Maven2 local repository. Now change to hello-world directory and do

mvn mobicents:eclipse

Maven will create the Eclipse project files. Finally open Eclipse, in the File menu select Import, then "General->Existing Projects into Workspace", next and finally browse to the hello-world directory and Eclipse should find a project named ... hello-world, select it and press Finish.

Part 3 - JAIN SLEE coding

Lets start with a short overview of JAIN SLEE. A SLEE is an application server, a container for software components. JAIN SLEE is designed and optimized for event driven applications, also known as asynchronous applications.

A JAIN SLEE event represents an occurrence that requires application processing. Each event has a specified event type (name,vendor and version), and all applications define the event types they want to handle, on the application Xml descriptors. For each event type of interest an event handler method must be provided in the application.

Events occur in a resource, inside or outside of the container. We call "event firing" to the action of posting of an event into the container, and when this happens the container will route the event to all applications interested on it, that is, all application instances (entities) attached to the context of that event, in JAIN SLEE this context is named activity. This attachment can be explicit (lets leave that for another article) or implicit, when the application defines the event type of the event being routed as an initial event. This means that if an application defines an event type as "initial", then all events of that type will be handled by the application.

So JAIN SLEE applications, also known as Services, are pure logic, which is executed by the container when events are fired in the container, which means they don’t have any active resources. In that sense, a JAIN SLEE service is no different than a web page script executed by the browser.

Going deeper, a JAIN SLEE Service is a tree of Service Building Blocks (Sbb), containing one root Sbb which then can declare others as child Sbbs, which then can have their own childs, and so on. Each Sbb is a Java abstract class, and includes the following logic:

implementation of the event handler methods
implementation of the interface to be used by other Sbbs who declare it as a child
implementation of an entity/instance life-cyle
implementation of methods to manage persistence of instance data

A well designed JAIN SLEE application only has one initial event, since each event of that type creates a new logical and independent instance of the application.

Ok, now what we want for our service is that when it is activated a message "Hello World" will be printed on the console. The Maven archetype we used already made most of the job:

it created a Service, which is nothing more than a Xml descriptor, that you can find in du/src/main/resources/services/service.xml, that just defines it's id (name,vendor,version) and its root sbb:


<service-name>hello-world SLEE Service</service-name>
<service-vendor>org.mobicents.slee.example</service-vendor>
<service-version>1.0-SNAPSHOT</service-version>
<root-sbb>
<description>
 <sbb-name>hello-world SBB</sbb-name>
 <sbb-vendor>org.mobicents.slee.example</sbb-vendor>
 <sbb-version>1.0-SNAPSHOT</sbb-version>
</description>
</root-sbb>
...

it created a Sbb that handles an internal event, ServiceStartedEvent, that is fired whenever a service is activated. How is this done you may ask, each Sbb class is packed in jar with a Xml descriptor (you can open it in eclipse please? sbb/src/main/resources/META-INF/sbb-jar.xml), this descriptor defines the Sbb id (name,vendor,version), its Java class and the events it handles, in this case ServiceStartedEvent:


<sbb-name>hello-world SBB</sbb-name>
<sbb-vendor>org.mobicents.slee.example</sbb-vendor>
<sbb-version>1.0-SNAPSHOT</sbb-version>

<sbb-classes>
 <sbb-abstract-class reentrant="False"> 
 <sbb-abstract-class-name>
 org.mobicents.slee.example.RootSbb
 </sbb-abstract-class-name> 
 </sbb-abstract-class> 
</sbb-classes> 

 <event direction="Receive" event="True">
 <event-name>ServiceStartedEvent</event-name>
 <event-type-ref>
 <event-type-name>
 javax.slee.serviceactivity.ServiceStartedEvent
 </event-type-name>
 <event-type-vendor>javax.slee</event-type-vendor>
 <event-type-version>1.0</event-type-version>
 </event-type-ref>
 <initial-event-select variable="ActivityContext" />
</event>

The Sbb class itself you can open it in the source package of the eclipse project, with the name RootSbb, which includes the ServiceStartedEvent event handler:

public void onServiceStartedEvent(
 javax.slee.serviceactivity.ServiceStartedEvent event,
 ActivityContextInterface aci) {
 
 try {
 Context myEnv = (Context) new InitialContext().lookup("java:comp/env");
 ServiceActivity sa = ((ServiceActivityFactory) myEnv
 .lookup("slee/serviceactivity/factory")).getActivity();
 if (sa.equals(aci.getActivity())) {
 // it's this service that is starting
 logger.info("service activated...");
 } 
 // don't want to receive further events on this activity
 aci.detach(this.sbbContext.getSbbLocalObject());
 
 } catch (Exception e) {
 logger.error("Can't handle service started event.", e);
 }
}

The logic in this event handler looks ugly but it's simple, it retrieves the ServiceActivity of the service from it's JNDI environment, and compares it with the ServiceActivity where the event was fired. If matches it means it's our service that is being activated. Great, now we just need to print the message in the console and in fact it's already printing something, "service activated", so all you need to do is change that code to

logger.info("hello world!!!");

Part 4 - Run the service

The end is close, let's start Mobicents JAIN SLEE Server, doing run.sh/run in server/bin folder of the Mobicents directory. Use another bash/terminal/command line window please.

Once it stops go to the window in the hello-world example directory and do

mvn install

Voila, Maven builds the Service's Deployable Unit jar on it's own, copies it to the Mobicents server deploy dir, and you should see the service being deployed on the window where Mobicents is running. In the end you should see

03:04:44,697 INFO [RootSbb] hello world!!!

That's it, have fun with JAIN SLEE specification document (the best knowledge source for sure) and don't forget to leave your feedback here.

JAIN SLEE / SIP Servlet becoming obvious choice

amit.bhayani — Tue, 20 May 2008 08:19:00 -0700

Mobicents Sip Servlets Management Console

Vladimir Ralev — Mon, 12 May 2008 07:38:00 -0700

One of the things that got shipped with Mobicents 1.2.0.BETA1, but didn't receive enough attention is the Sip Servlets Management Console and hopefully this post will reach the users.

The managment console is a web application available at http://localhost:8080/sip-servlets-management/ for those who have the latest Mobicents.

Currently it allows configuring the application router in the Sip Servlets container by dragging the blocks or the columns of the applications associated with certain SIP method and we plan to enhance it with application management and monitoring module, stun, media and other configuration options.

You can see it in action here.

In the future we plan to add wildcard and rules matching to the Application Router configuration tool, so stay tuned.

JavaOne 2008 Materials

Vladimir Ralev — Mon, 12 May 2008 06:28:00 -0700

JavaOne 2008 was interesting. The Mobicents team held short sessions on the Mobicents Platform. In my presentation I tried to cover the basics of VoIP, show some real world examples and applications, explain the components and the features in Mobicents. I also had a few slides on the new programming model that we are developing now. At the end I made a quick demo of a Facebook click-to-call application that calls two different phones and links them (web-initiated 3pcc).

Unfortunately, it didn't go as planned. It was supposed to be 15 mins presentation and 45 mins demos, and it was 45 mins of presentation and just a few minutes of demo. And I sucked. They shouldn't let me talk to people :)

Anyway, it seems the Mobicents sessions attracted a lot of people interested to learn about converged and VoIP applications. There are a few requests to post the presentations and demos, so here they are:

Building Converged Applications with Mobicents by me
Mobicents Communications Platform - Java EE, JAIN-SLEE, SIP Servlets, Media Server by Jean Deruelle

The demos can be found here:

Facebook Click2Call Demo (source code)

The Facebook demo basically asks for two phone numbers, then you can click Dial and the phones should start ringing. Once you pick up both phones the call is established and both parties can hear each other.

JSLEE and Sip Servlets Interop Demo (source code)

This demo shows is a web store where once the user has checked out with some items in the basket, he receives a call on his phone and must confirm the payment by pressing 1. It is similar to the original JAIN SLEE Converged demo (Shopping demo) and the Sip Servlets Shopping Demo but it uses both JAIN SLEE and Sip Servlets.

First post

Vladimir Ralev — Mon, 12 May 2008 04:07:00 -0700

Testing

Mobicents at JavaOne 2008

Ivelin — Wed, 07 May 2008 03:20:00 -0700

Mobicents Platform showcased @ JavaOne 2008 in San Francisco

Jean Deruelle — Mon, 28 Apr 2008 10:14:00 -0700

On my last post, I presented a nice application demonstrating interoperability betwen Sip Servlets and JAIN SLEE, and this would be the demo of my talk at JavaOne 2008.

Here is the abstract of the talk I'll give :

"Mobicents Converged Application Server: JSLEE, SIP Servlets, Java EE"

"The Mobicents Communication Platform is the best architecture to create, deploy and manage services and applications integrating voice, video and data across a range of IP and communications networks. It drives convergence in leveraging the three following core capabilities :

Mobicents JAIN-SLEE which provides a highly scalable event-driven application server capable of bridging multiple IP and legacy protocols.
Mobicents Sip Servlets which delivers a consistent, open platform on which to develop and deploy portable and distributable SIP and Converged JEE services.
Mobicents Media Server which delivers competitive, complete, best-of-breed media gateway functionality featuring highest quality."

So if you're somewhat interested in telecommunications, next generation applications, SIP or simply in the power of the Mobicents Platform :-) as a whole or in jboss products, please come and see us in action at Booth #734 or Join us for the JBoss Speakeasy Party next door to the Moscone Center at Jillian's inside the Metreon from 5:30-8:30 p.m. Thursday, May 8.

Don't forget to register and I may be able to bring you some of the beers you ordered through the JAIN SLEE/Sip Servlets Interop application we will demo :-)

For more information on what Jboss will present or for more insight on the other talks please click on the following link http://www.jboss.org/files/events/javaone2008events.htm

I hope to see and chat with with you there !

Update : You can find my presentation here : http://www.jboss.org/presentations/JavaOne2008_MobicentsPlatform.odp

Sip-Servlets and JAIN-SLEE : working hand in hand, is the war over ?

Jean Deruelle — Mon, 28 Apr 2008 09:40:00 -0700

As you might know, there is a constant war raging between Sip Servlets and JAIN-SLEE and most see them as competing specifications/products and try to choose between one or the other.

My take is that they don't need to compete since they complete each other very well and it has been one of the leitmotiv behind building Mobicents Sip Servlets.

JAIN SLEE is a more complex specification than SIP Servlets, and it has been know as heavyweight and with a steep learning curve. However JAIN SLEE has standardized a high performing event driven application server, an execution environment with a a good concurrency model and powerful protocol agnostic capabilities thus covering a variety of telco protocols.
SIP Servlets on the other is way much simple and easier to get started with. Its focus is currently on SIP + HTTP/JEE only and is more of a programming model while JAIN SLEE is more of an application environment, a platform.
The fact that Sip Servlets is focused on SIP+JEE makes it a natural fit to build JEE converged applications and way much simpler than JAIN SLEE. To me it feels like JAIN SLEE and Sip Servlets target different audiences, different needs.

It's been a long time since I wanted to leverage the power of both and make them work hand in hand to leverage standards all the way for an application. It is now possible since the Mobicents Platform provides both JAIN SLEE and Sip Servlets implementation within the same VM.

So I hacked away, helped by my Mobicents fellows and here it is the JAIN-SLEE/Sip Servlets Interoperability Demo.

This converged application leverages the power of the Mobicents Platform and shows how JAIN-SLEE and Sip Servlets can be used together to leverage standards for protocols outside of the scope of JSR 289 specification in using JAIN-SLEE.

In this example, Mobicents Sip Servlets is used to handle the SIP protocol for which it is a natural fit, JEE is used as a gateway to communicate between Sip Servlets and JAIN SLEE worlds, Mobicents JAIN-SLEE is used to control Media through Media and Text to Speech Resource Adaptors and Mobicents Media Server is used to handle Media and DTMF signals.

Media has been used here as a proof of concept of a typical need for sip servlets applications that is outside of the Sip servlets Spec and support for it is really up to vendors thus the application, if built using only Sip Servlets, would be non portable between vendors and application servers.
The same kind of application could be built for accessing other standards (such as Diameter offered by most vendors in the same proprietary way) or legacy protocols through JAIN-SLEE in a PORTABLE way without to resort to vendor proprietary extensions.

One of the logical next steps Mobicents is already taking is to drive and create a unified model that leverages the simplicity and tight JEE integration of Sip Servlets with the power of concurrency control and protocols abstraction of JAIN-SLEE. Feel free to join us if you're interested in it !

Mobicents Sip Servlets has a new home

Jean Deruelle — Mon, 28 Apr 2008 09:30:00 -0700

The Mobicents Sip Servlets project that started off at java.net to implement the SIP Servlet v1.1 (JSR 289) work in progress specification on top of Tomcat & Jboss and to develop interoperability standards between Sip Servlets and JAIN-SLEE has now moved away to join its family, the Mobicents Platform.

The project will leverage the same communications channel as the Mobicents platform :
User Forum
Contributor Forum
Mobicents google group

The source code is now accessible at http://code.google.com/p /mobicents/source/browse/trunk /servers/sip-servlets for browsing or at https://mobicents.googlecode .com/svn/trunk/servers/sip -servlets for
checkout.

Issues are available at http://code.google.com/p/mobicents/issues/list?q=label%3Acomponent%20label%3Asip-servlets&can=2

sip-servlets.dev.java.net will stay as it is for historical purposes but won't be updated anymore.

Stay tuned !

Mobicents is now maven'ized

amit.bhayani — Sun, 20 Apr 2008 07:59:00 -0700

Review of book 'Internet Multimedia Communications Using SIP'

amit.bhayani — Mon, 24 Mar 2008 04:12:00 -0700

Presentations on Mobicents and JAIN SLEE

amit.bhayani — Fri, 29 Feb 2008 09:36:00 -0800

JBoss World 2008 - Orlando, Florida

amit.bhayani — Sun, 24 Feb 2008 12:27:00 -0800

Last week I attended JBoss World 2008 at Orlando,…

EDUARDO MARTINS — Mon, 18 Feb 2008 07:18:00 -0800

Last week I attended JBoss World 2008 at Orlando, the biggest JBoss event ever, with around 750 attendees not working for JBoss/Red Hat.

One of the most interesting things I noticed, is that there is huge market of J2EE developers that can really make a difference with JBoss solutions, by leveraging Mobicents projects into their web applications.

We made a demo of a converged web 2.0 application using JBoss Seam and Mobicents (and much more actually) for a furniture store, that would call site users and admins according to order details, for order auth, confirmation, etc and the reaction was a big big "wow". Attendees left the room with the idea something must be changing.

It's a new world for them, using more than a browser to interact with users, and it's a new world for us, who have been targeting primarily the telco market.

The only not so good thing was the size of the audience for this demo, but the presentation title was somehow misleading and it was at 10h am after JBoss World party! Anyway, we will evolve this demo and for sure present it in more J2EE big events along the year.

Photo of the Mobicents team members present at JBW, left to right: Alexandre Mendonça (R&D), Vladimir Ralev (R&D), Bartosz Baranowski (R&D), Luis Barreiro (QA), me (R&D), Amit Bhayani (R&D), Jean Deruelle (R&D)

Mobicents JSLEE or Mobicents SIP Serlvets: Which one is better?

Ivelin — Thu, 17 Jan 2008 02:07:00 -0800

JBCP training class at Nortel

Ivelin — Tue, 11 Dec 2007 10:48:00 -0800

Japanese telcos still on the cutting edge

Ivelin — Mon, 10 Dec 2007 01:24:00 -0800

Telco 2.0 Executive Summit, October 2007

Ivelin — Mon, 10 Dec 2007 01:03:00 -0800

Who knows, someday I may write something…

EDUARDO MARTINS — Wed, 31 Oct 2007 10:07:00 -0700

Who knows, someday I may write something here...

JBoss Communication Platform creates buzz in India and Indian sub continents

amit.bhayani — Tue, 30 Oct 2007 15:33:00 -0700

HTTP Client Review

amit.bhayani — Sun, 29 Jul 2007 08:35:00 -0700

Telco 2.0 and Disposable Apps

Ivelin — Sun, 08 Jul 2007 08:10:00 -0700

Red Hat launches Communications Platform

Ivelin — Mon, 18 Jun 2007 17:12:00 -0700

SIP integrated with SOA answer to Intelligent JEE Application

amit.bhayani — Wed, 16 May 2007 14:36:00 -0700

Test

amit.bhayani — Wed, 09 May 2007 16:18:00 -0700

Motorola invests in JSLEE

Ivelin — Sat, 13 Jan 2007 09:06:00 -0800

Some notes from Oredev

Ivelin — Sat, 02 Dec 2006 01:55:00 -0800

IT Vendors vs. NEPs - Round 2.0

Ivelin — Wed, 27 Sep 2006 07:37:00 -0700

Another good day for Open Source and IMS

Ivelin — Wed, 07 Jun 2006 13:35:00 -0700

Standardization out of the box

Ivelin — Tue, 23 May 2006 12:50:00 -0700

Gartner starts serious coverage of event driven architectures

Ivelin — Sat, 18 Mar 2006 08:24:00 -0800

See you at VON Spring 2006

Ivelin — Fri, 24 Feb 2006 11:02:00 -0800

Gizmo Project and Google Talk are Now Connected!

Ivelin — Wed, 15 Feb 2006 06:28:00 -0800