Restcomm

We've just released a new spin for Mobicents Diameter, v1.1.2.GA.It happened on 21st of February and along with the usual bug fixing and improvements, there's a great addition to the suite: The Mobicents Diameter Jopr Plugin.Jopr is an enterprise ... [More] management solution which provides administration, monitoring, alerting, operational control and configuration in an enterprise setting with fine-grained security and an advanced extension model.The Mobicents Diameter Jopr Plugin provides the following functionalities:Stack configuration and managementProvides means of changing stack parameters, such as various timeout values, duplicate protection, accept undefined peers, thread pools size, etc.;Start/Stop stack, Enable/Disable validationLocal peer configuration and statisticsAllows change of local peer IP Address and URI, Realm name, supported Application-Ids, etc.;Real time statistics regarding memory usageNetwork Peers management and statisticsProvides ability to add and remove Network Peers;Statistics regarding requests/answer sent and/or received (total and per minute), Average time for message processing, Number of messages waiting on queue, number of messages failed to send/receive, etc.Realms configuration and managementAllow runtime realm configuration, ie, change realm name, Peers list, Application Ids, etc.;Add and remove RealmsAll these functionalities plus the added value by Jopr, which provides availability for each component (Stack, Local Peer, Network Peers and Realms), alert configuration, intuitive graphs and some more cool and intuitive features makes this a great companion for the Diameter suite!Regarding installation and configuration of Jopr and the plugin, while we are working at the documentation for it, you can follow JAIN SLEE Jopr Plugin User Guide (Installing Jopr and Mobicents JAIN SLEE Plugin chapter) since it's the exact same procedure.Here are some screenshots of the plugin in action:   Enjoy! [Less]

The RTSP stack that was developed and maintained by mobicents is now merged with Netty main stream! RTSP is extension of HTTP Protocol. Netty already have very good support for HTTP; adding RTSP was just an extension.A big thanks goes to Trustin for ... [More] merging Mobicents RTSP Code and providing support.Release version Netty 3.2.0.ALPHA4 already has the RTSP included. However there are no examples available. If you want to understand how to use the RTSP stack have a look at RtspServerStackImpl in Mobicents Media Server, which represents the Server side for RTSP. Classes in Package org.mobicents.media.server.ctrl.rtsp (here) shows how to maintain the state.Though Mobicents Media Server is not using RtspClientStackImpl, I have just added this to show how RTSP can be used at Client side also.Once I find some time I will add RTSP examples directly in RTSP Trunk.Download your 3.2.0.ALPHA4 version of Netty from here .Enjoy! [Less]

Wow, this was a great year !I can not remember from my past experience any of the year, which has fleet away so fast as this one. There has been many of the things happening and most of them I have really enjoyed. Few couple months from beginning ... [More] were quite hard. Time to settle down everything and find out how the things are working took quite long, but I enjoyed! It is good to remember here, the Productization meeting at Newcastle, which helped me a lot. To meet the guys, working on the same things for various platforms/projects was inspiring. We have established a process for the regular incremental patches of our Mobicents/ JBCP platform and even going through difficulties, we have delivered our distributions. Meeting of the other team-mates in August was great time to enjoy the fact, that although I am here alone in Brno, there are other guys worldwide playing the same game as I do.Cheers guys ! :)Great experience for me was as well a RedHat developer conference here in Brno, where I had a chance to introduce Mobicents during my presentation.Looking forward to next year, I am sure will be great :) [Less]

Here is our new shiny Mobicents Sip Servlets 1.2 release, certified against the Sip Servlets 1.1 specification and working on top of Tomcat 6.0.20 and JBoss AS 4.2.3.GA & 5.1.0.GA and licensed under LGPL.This release is the last community version ... [More] that will propose Mobicents Sip Servlets on top of JBoss 4.2.x series. If you need still need support for it, we recommend you to either upgrade to the JBoss 5.x series or buy a JBCP subscriptionAs such our latest release's focus was essentially on the JBoss 5.x version and has a mixed focus :More management metrics/control :More Congestion Controls : Sip Session/ Sip App Session Creation per sec; and Alerts and value or percentage for back to normalMore Monitoring Stats : Number of responses received per Status code, Number of requests received per Request MethodMore Monitoring Stats for the Mobicents Load Balancer : Number of responses received per Status code, Number of requests received per Request MethodAdd JMX capabilities to the Mobicents JAIN SIP StackClustering and High Availability where many bugs were fixed and SipApplicationSession Fault Tolerant Timers have been implemented (only on JBoss 5.x version)The other highlights of this release are :Port Seam Telco Framework to JB5Move To Mobicents Media Server 2.0 BETA3Move To Apache Tomcat 6.0.20More than 20 bug fixesDownloads are here, online documentation is here, User Guide is here, the 1.2 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 [Less]

For a very long time we have been using mobicents spreadsheetI was searching for any consistent, up-to-date roadmap information for various modules of Slee, Sip Servlets, Diameter. I do not want argue, how bad, or good this was, but I think we can ... [More] agree on the fact, this approach was not bringing us a big value.It is the time to introduce, how we deal with roadmap management for Mobicents now. First of all have a look at SipServlets roadmap and JainSLEE roadmap and check the roadmap's yourself.Current roadmap management we use, bring us consistent, up-to-date and what is most important flexible way, how to handle roadmap. There is no need to remember, when You, as developers, deal with any of the issues, update some sheets or any extra place, to keep roadmap consistent. Only need is to manage gcode issue and roadmap is every day automatically generated and updated accordingly with the most recent changes and updates.We can follow (observe) such roadmap every day progress or weekly progress, as you like, to check, whether the issue has been started updated or not.When you are interested in more details, how this works you can check documentation for automated roadmap tool. (This documentation is being updated, so you may expect some progress on it).Currently, we do have Slee and Sip Servlets modules and Diameter with Media server modules are coming soon.check for yourself ! [Less]

Sometime ago Eduardo spent some time to create basic maven archetypes for JSLEE. Since 2.x CR1 of JSLEE is going out and there was a lot of google group traffic regarding setting up basic project, I dedicated some time to create similar package for ... [More] JSLEE 1.1.Here is wiki page which describes how to use archetypes (iirc). I will update it once I get spare 5 minutes.Sources can be found here. [Less]

We are happy to announce the binary release of Mobicents JSR-309 implementation 2.0.0.BETA3 !This is just intermediary release and still uses the JSR309 draft API before we start implementing the JSR309 Final Spec.Announcement is here Download from ... [More] hereMobicents JSR-309 Impl page http://www.mobicents.org/mms-jsr309-main.htmlLooking forward to your feedback [email protected] Media Server Team [Less]

It took some time to reach this point. But ... its out. Another 2.x.y media server from mobicents has been born yesterday.Details can be found in media server blog. In short, what does it bring?Video support for ISO files RTSP support - this includes ... [More] mobicents RTSP stack and MMS ControllerSS7 support previewYes, SS7. At the moment its still not full, but allows to do some cool stuff.Currently SS7 guide is short and can be found here. However next release will incorporate it in regular guide.Roadmap can be found here.So what those goodies allow?Video is self explanatory. RTSP adds live streaming capability(its a bit like showcast radios on winamp with, but bit cooler since it allows operations like: pause, rewind - VCR style).Finally SS7. We tested with real MSC on operators side. Tests performed:link setup and stability(long term IN_SERVICE)streamingMU validation(it takes time to learn how to read those bits)SCCP,TCAP and CAMEL testing. CAMEL test has been performed by JSLEE 1.x.y application with JCC RA( it can be found in svn, code is very simple )Here is what Media Server Team planned for MMS:stabilize core for CR1add other SS7 protocols as independent stacks(that can be used without MMS)B/D channels endpoints SS7 RAs for JSLEE 2.x and similar resource for MSSIf everything goes smootly next release will allow JSLEE and MSS to connect to legacy network and provide means of replacing Asterisk.Big thanks to Vladimir for hand on HDLC part for MTP layers. [Less]

We are proud to announce the release of Mobicents Media Server (MMS) v2.0.0.BETA3The major focus of this release has been making MMS Video capableRTSP EnabledSS7 SupportVideoTo make Video possible, MMS has its own parser to parse ISO Based Media ... [More] files. Any request for playing ISO Based Media files is first parsed and then depending on the Tracks (audio/video or both) supported, the Player streams the individual tracks separately. Bellow diagram shows abstract of how MMS takes care of video internally.RTSPRTSP is a separate Controller module in MMS 2.0.0.BETA3. Now MMS can either be controlled using the MGCP or RTSP Requests. While both have different requirements and may not be needed in same MMS instance at same time. With modular structure of MMS its very easy to remove either of controller modules from MMS by deleting /deploy/mgcp-conf.xml or /deploy/rtsp-conf.xml depending on needs. By default RTSP starts at port 554. Linux users either have to start as root or change this port as in Linux, and other UNIX-like systems, you have to be root (have superuser privileges) in order to listen to TCP or UDP ports below 1024 (the well-known ports). The default media directory is /media and every RTSP request to play a media file searches for file in this directoey. By default it comes with sample_50kbit.3gp, sample_100kbit.mov and sample_100kbit.mp4 ISO based media files. As of now there are known issues with parsing for sample_100kbit.mov. Nevertheless you can stream the media to your favriote player by opening the url rtsp:// :554/sample_100kbit.mp4. Add your own media files here and stream them on the fly - no need to restart the server.The bellow diagram shows how components fit in RTSP.SS7This is one of the biggest achievement of MMS. With SS7 support the Mobicents truly becomes Telco solution provider ranging from legacy protocols like SS7 to next generation networks like SIP used extensively in IMS. The SS7 support in MMS is provided by using the SS7 cards available in market and hence for the first time MMS uses the external hardware. These SS7 cards must be Zaptel compatible (Digum / Sangoma cards). For SS7 support, the MMS only takes care of lower layers MTP2/MTP3 for signalling. MMS is also responsible for circuit media. The higher protocols like ISUP, SCCP etc is external to MMS. We are developing the higher layer (layer 4 and above of SS7) as individual stacks (for example ISUP Stack, SCCP stack etc). These higher layer stacks can be used by respective Resource Adaptor in Mobicents JAIN SLEE Server or can be consumed by Sip Servlets and hence make Sip Servlets SS7 capable! While the MTP2/MTP3 is ready in MMS 2.0.0.BETA3, considerable efforts are spent in developing higher layers stacks. Look at MMS SS7 Roadmap for further details. The public page also explains how Dialogic cards can be directly used with native Dialogic drivers taking care of lower SS7 layers.Bellow diagram shows how components fit in MMS - SS7 ArchitectureFor configuration regarding the Zaptel Card visit http://groups.google.com/group/mobicents-public/web/mms-ss7-supportYou can download the MMS 2.0.0.BETA3 Binary from http://sourceforge.net/projects/mobicents/files/Mobicents%20Media%20Server/Browse the SVN at http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.BETA3Checkout the source code for 2.0.0.BETA3 from link http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.BETA3/The public announcement is here http://groups.google.com/group/mobicents-public/browse_thread/thread/fc334a5ef1ff79ff#Enjoy the Video! and develop real Converged Application :)CheersMobicents Media Server Team. [Less]