tag:blogger.com,1999:blog-89869053763243378872024-02-20T09:28:17.949-08:00Mobicents Media Serveramit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.comBlogger19125tag:blogger.com,1999:blog-8986905376324337887.post-80217985631838988602010-11-19T06:41:00.000-08:002010-11-19T06:58:27.244-08:00Mobicents Media Server (MMS) v2.1.0.BETA1 Released!!!<div>We are happy to announce the release of <b>Mobicents Media Server (MMS) v2.1.0.BETA1</b></div><div><br /></div><div><br /></div><div>The biggest feature added in this release is RTCP capability. </div><div>Also the timer precision within MMS is now accurate to nano seconds. This greatly improves the voice quality. </div><div><br /></div><div>The MMS 2.x.y can be controlled using MGCP Protocol </div><div><br /></div><div>To understand how to use JSR-309 Impl with Sip Servlet look at <a href="http://www.mobicents.org/mss-jsr309-demo.html">JSR 309 Demo</a> example available with latest Mobicents Sip Servlets Server release. </div><div><br /></div><div>To understand how to use Mobicents Media Server with JAIN SLEE Server look at <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/mgcp-demo">mgcp-demo</a>, <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/echo">echo</a> and <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/packet-relay-demo">packet-relay-demo</a> examples. </div><div><br /></div><div><b>Mobicents Media Server Home Page:</b></div><div><a href="http://www.mobicents.org/mms/mms-main.html">http://www.mobicents.org/mms/mms-main.html </a></div><div><br /></div><div><b>MMS Guide page:</b></div><div><a href="http://www.mobicents.org/mms/mms-docs.html">http://www.mobicents.org/mms/mms-docs.html </a></div><div><br /></div><div>To know the details of issues fixed in this release follow </div><div><a href="http://code.google.com/p/mobicents/issues/list?can=1&q=label:Component-Media-Server%20label:Version-2.1.0%20label:Release%20label:Release-Type-Beta%20status:Fixed">http://code.google.com/p/mobicents/issues/list?can=1&q=label:Component-Media-Server%20label:Version-2.1.0%20label:Release%20label:Release-Type-Beta%20status:Fixed</a></div><div><br /></div><div><b>Where to download from?</b></div><div>----------------------- </div><div>The distribution can be found on SourceForge.net. The binary package for </div><div>standalone is mms-standalone-2.1.0.BETA1.zip </div><div>Download from </div><div><a href="http://sourceforge.net/projects/mobicents/files/Mobicents%20Media%20Server/2.1.0.BETA1/mms-standalone-2.1.0.BETA1.zip/download">http://sourceforge.net/projects/mobicents/files/Mobicents%20Media%20Server/2.1.0.BETA1/mms-standalone-2.1.0.BETA1.zip/download</a></div><div><br /></div><div><b>Source repositories:</b></div><div>------------------- </div><div>SVN checkout </div><div><a href="http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1/">http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1/</a></div><div><br /></div><div>SVN Browsing </div><div><a href="http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1">http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.1.0.BETA1</a></div><div><br /></div><div><b>Looking forward to your feedback: </b></div><div>--------------------------------- </div><div>http://groups.google.com/group/mobicents-public </div><div><br /></div><div><b>Mobicents Media Server Team</b></div>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-3505965160453931732010-09-22T04:35:00.000-07:002010-09-22T04:36:57.047-07:00Mobicents SMPP Stack!<div>We are happy to announce addition of new Project SMPP in Mobicents Incubator!</div><div><br /></div><div>The <b>Mobicents SMPP</b> stack is implementation of SMPP Version 5.0 Specifications. The initial code is forked from Java SMPP API Project. A big thanks goes to Oran Kelly, founder of Java SMPP Project for awesome work!</div><div><br /></div><div>The main reason to fork the code is to optimize the stack as much as possible specific to Mobicents JSLEE SMPP5 Resource Adaptor. </div><div><br /></div><div>We have released the first version of stack 1.0.0.BETA1 which will be included in next release of Mobicents JSLEE SMPP5 Resource Adaptor.</div><div><br /></div><div><b>Mobicents SMPP Home Page:</b></div><div><a href="http://www.mobicents.org/incubator/smpp/intro.html">http://www.mobicents.org/incubator/smpp/intro.html</a></div><div><br /></div><div><br /></div><div><br /></div><div><b>Where to download from?</b></div><div>----------------------- </div><div>The distribution can be found on SourceForge.net. The binary package is <b>smpp-impl-1.0.0.BETA1.jar </b></div><div>Download from </div><div><a href="https://sourceforge.net/projects/mobicents/files/Mobicents%20SMPP/1.0.0.BETA1/">https://sourceforge.net/projects/mobicents/files/Mobicents%20SMPP/1.0.0.BETA1/</a></div><div><br /></div><div><br /></div><div><br /></div><div><b>Source repositories:</b></div><div>------------------- </div><div><br /></div><div>SVN checkout </div><div><a href="https://mobicents.googlecode.com/svn/trunk/servers/jain-slee/resources">https://mobicents.googlecode.com/svn/trunk/servers/jain-slee/resources</a></div><div><br /></div><div>SVN Browsing </div><div><a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/protocols/smpp">http://code.google.com/p/mobicents/source/browse/#svn/trunk/protocols/smpp</a></div><div><br /></div><div><br /></div><div><br /></div><div><b>Looking forward to your feedback:</b></div><div>--------------------------------- </div><div><a href="http://groups.google.com/group/mobicents-public">http://groups.google.com/group/mobicents-public </a></div><div><br /></div><div><br /></div><div>Thanks,</div><div>Mobicents Team.</div>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-3701193611213002572010-08-17T05:19:00.000-07:002010-08-17T05:23:44.285-07:00We are very happy to announce the release of <span style="font-weight: bold;">Mobicents Media Server (MMS) v2.0.0.GA</span><br />This is by far the most stable release of Mobicents Media Server!!<br /><br />There are no new features added in this release, but few bug fixes from <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/86b7cf22708ed8bd#">MMS v2.0.0.CR3</a>.<br /><br />The MMS 2.x.y can be controlled using <a href="http://www.mobicents.org/mms/mms-mgcp-main.html">MGCP</a> Protocol<br /><br />To understand how to use JSR-309 Impl with Sip Servlet look at <a href="http://www.mobicents.org/mss-jsr309-demo.html">JSR 309 Demo</a> example available with latest Mobicents Sip Servlets Server release.<br /><br />To understand how to use Mobicents Media Server with JAIN SLEE Server look at <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/mgcp-demo">mgcp-demo</a>, <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/echo">echo</a> and <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/packet-relay-demo">packet-relay-demo</a> examples.<br /><br /><span style="font-weight: bold;">Mobicents Media Server Home Page:</span><br /><a href="http://www.mobicents.org/mms/mms-main.html">http://www.mobicents.org/mms/mms-main.html</a><br /><br /><span style="font-weight: bold;">MMS Guide page:</span><br /><a href="http://www.mobicents.org/mms/mms-docs.html">http://www.mobicents.org/mms/mms-docs.html</a><br /><br /><span style="font-weight: bold;">Where to download from?</span><br />-----------------------<br />The distribution can be found on SourceForge.net. The binary package for standalone is mms-standalone-2.0.0.GA.zip<br />Download from<br /><a href="http://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.0.0.GA/">http://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.0.0.GA/</a><br /><br /><span style="font-weight: bold;">Source repositories:</span><br />-------------------<br /><br />SVN checkout<br /><a href="http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.GA/">http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.GA/</a><br /><br />SVN Browsing<br /><a href="http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.GA">http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.GA</a><br /><br /><span style="font-weight: bold;">Looking forward to your feedback:</span><br />---------------------------------<br /><a href="http://groups.google.com/group/mobicents-public">http://groups.google.com/group/mobicents-public</a><br /><br /><span style="font-weight: bold;">Mobicents Media Server Team</span>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-56195742033228197152010-07-30T12:49:00.000-07:002010-07-30T12:54:32.367-07:00Mobicents Media Server (MMS) v2.0.0.CR3 Released!We are happy to announce the release of <span style="font-weight: bold;">Mobicents Media Server (MMS) v2.0.0.CR3</span><br /><br />There are couple of new feature added as well as performance improvements<br /><br /><ol><li>The issue with MBROLA TTS fixed and by default 3 voices are available. For details look at <a href="http://code.google.com/p/mobicents/issues/detail?id=1476">http://code.google.com/p/mobicents/issues/detail?id=1476</a></li><li>New mixers are added for Conference Endpoint <a href="http://code.google.com/p/mobicents/issues/detail?id=1599">http://code.google.com/p/mobicents/issues/detail?id=1599</a></li><li>Connection can now be audited to know the statistics at real-time. Details at <a href="http://code.google.com/p/mobicents/issues/detail?id=1598">http://code.google.com/p/mobicents/issues/detail?id=1598</a></li><li>For more details look at <a href="http://code.google.com/p/mobicents/issues/list?cursor=1604&q=label%3AComponent-Media-Server%20label%3ARelease-Type-Candidate-3%20label%3AVersion-2.0.00&updated=1604&ts=1280517894&can=1">http://code.google.com/p/mobicents/issues/list?cursor=1604&q=label%3AComponent-Media-Server%20label%3ARelease-Type-Candidate-3%20label%3AVersion-2.0.00&updated=1604&ts=1280517894&can=1</a></li><li>The majority of effort was to integrate the SS7 lower layers MTP2/MTP3 on MMS side such that MMS can be used as Media Gateway once B Channel Endpoint is done. For SS7 related announcement look at<a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/e9d5a29020612e1c"> http://groups.google.com/group/mobicents-public/browse_thread/thread/e9d5a29020612e1c</a></li></ol><br />The MMS 2.x.y can be controlled using <a href="http://www.mobicents.org/mms/mms-mgcp-main.html">MGCP Protocol</a><br /><br />To understand how to use JSR-309 Impl with Sip Servlet look at <a href="http://www.mobicents.org/shopping-demo-jsr309.html">JSR 309 Demo</a> example available with latest Mobicents Sip Servlets Server release.<br /><br />To understand how to use Mobicents Media Server with JAIN SLEE Server look at <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/mgcp-demo">mgcp-demo</a>, <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/echo">echo</a> and <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/jain-slee/examples/packet-relay-demo">packet-relay-demo</a> examples.<br /><br /><span style="font-weight: bold;">Mobicents Media Server Home Page:</span><br /><a href="http://www.mobicents.org/mms/mms-main.html">http://www.mobicents.org/mms/mms-main.html</a><br /><br /><span style="font-weight: bold;">MMS Guide page:</span><br /><a href="http://www.mobicents.org/mms/mms-docs.html">http://www.mobicents.org/mms/mms-docs.html</a><br /><br /><span style="font-weight: bold;">Where to download from?</span><br />-----------------------<br />The distribution can be found on SourceForge.net. The binary package for standalone is mms-standalone-2.0.0.CR3.zip<br /><br />Download from<br /><br /><a href="https://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.0.0.CR3/">https://sourceforge.net/downloads/mobicents/Mobicents%20Media%20Server/2.0.0.CR3/</a><br /><br />Source repositories:<br />-------------------<br /><br />SVN checkout<br /><a href="http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.CR3/">http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.CR3/</a><br /><br />SVN Browsing<br /><a href="http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.CR3">http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.CR3</a><br /><br />Looking forward to your feedback:<br />---------------------------------<br /><a href="http://groups.google.com/group/mobicents-public">http://groups.google.com/group/mobicents-public</a><br /><br /><span style="font-weight: bold;">Mobicents Media Server Team</span>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-35710244308380890922010-05-06T22:17:00.000-07:002010-05-06T22:21:05.762-07:00Mobicents MGCP Impl Stack goes GA!Mobicents Media Server team released the second stable version of MGCP Impl stack. The main focus was to improve the performance to a level where MGCP signaling doesn't hamper the media quality. We are very happy to take MGCP Stack to a level where it can easily achieve 1000 CPS rate, where 1 CPS is round-trip of CRCX, RQNT and DLCX request/response.<br /><br />One of the major changes incorporated is entire stack is now single threaded. This is very important for predictable behavior and to make sure that thread context switching doesn't go beyond control, where media processing cannot be started and executed in stipulated time.<br /><br />The distribution can be found on SourceForge.net. The binary package is<br />mobicents-mgcp-impl-2.0.0.GA.jar:<br /><a href="https://sourceforge.net/project/admin/explorer.php?group_id=102670">https://sourceforge.net/project/admin/explorer.php?group_id=102670</a><br /><br />SVN Trunk Checkout <a href="http://mobicents.googlecode.com/svn/trunk/protocols/jain-mgcp">http://mobicents.googlecode.com/svn/trunk/protocols/jain-mgcp</a><br /><br />SVN Trunk Browse <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/protocols/jain-mgcp">http://code.google.com/p/mobicents/source/browse/#svn/trunk/protocols/jain-mgcp</a><br /><br />SVN Tag Checkout <a href="http://mobicents.googlecode.com/svn/tags/protocols/jain-mgcp/mobicents-mgcp-impl-2.0.0.GA/">http://mobicents.googlecode.com/svn/tags/protocols/jain-mgcp/mobicents-mgcp-impl-2.0.0.GA/</a><br /><br />SVN Tag Browse <a href="http://code.google.com/p/mobicents/source/browse/#svn/tags/protocols/jain-mgcp/mobicents-mgcp-impl-2.0.0.GA">http://code.google.com/p/mobicents/source/browse/#svn/tags/protocols/jain-mgcp/mobicents-mgcp-impl-2.0.0.GA</a><br /><br /><a href="http://www.mobicents.org/mms/mms-mgcp-main.html">Mobicents MGCP Home Page</a><br /><br />Looking for your <a href="http://groups.google.com/group/mobicents-public/topics">feed back</a><br /><br />Enjoy the most powerful MGCP Stack :)amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com1tag:blogger.com,1999:blog-8986905376324337887.post-49273477524034227402010-02-06T07:48:00.000-08:002010-02-06T19:11:38.418-08:00RTSP supported by JBoss Netty!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.<br /><br />A big thanks goes to <a href="http://gleamynode.net/">Trustin</a> for merging Mobicents RTSP Code and providing support.<br /><br />Release version <span style="font-weight: bold;">Netty 3.2.0.ALPHA4</span> 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 <a href="http://code.google.com/p/mobicents/source/browse/trunk/servers/media/core/controllers/rtsp/src/main/java/org/mobicents/media/server/ctrl/rtsp/stack/RtspServerStackImpl.java">RtspServerStackImpl</a> in Mobicents Media Server, which represents the Server side for RTSP. Classes in Package org.mobicents.media.server.ctrl.rtsp (<a href="http://code.google.com/p/mobicents/source/browse/trunk/servers/#servers/media/core/controllers/rtsp/src/main/java/org/mobicents/media/server/ctrl/rtsp%3Fstate%3Dclosed">here</a>) shows how to maintain the state.<br /><br />Though Mobicents Media Server is not using <a href="http://code.google.com/p/mobicents/source/browse/trunk/servers/media/core/controllers/rtsp/src/main/java/org/mobicents/media/server/ctrl/rtsp/stack/RtspClientStackImpl.java">RtspClientStackImpl</a>, I have just added this to show how RTSP can be used at Client side also.<br /><br />Once I find some time I will add RTSP examples directly in RTSP Trunk.<br /><br />Download your 3.2.0.ALPHA4 version of Netty from <a href="http://www.jboss.org/netty/downloads.html">here</a> .<br /><br />Enjoy!amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com1tag:blogger.com,1999:blog-8986905376324337887.post-63422533080392676792010-01-23T03:34:00.000-08:002010-01-23T03:36:35.085-08:00Mobicents JSR-309 Impl 2.0.0.BETA3 Released!We are happy to announce the binary release of <span style="font-weight: bold;">Mobicents JSR-309 implementation 2.0.0.BETA3 !</span><br /><br />This is just intermediary release and still uses the JSR309 draft API before we start implementing the JSR309 Final Spec.<br /><br />Announcement is <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/958f731d5b12ed29">here </a><br /><br />Download from <a href="https://sourceforge.net/projects/mobicents/files/Mobicents%20JSR-309%20Impl/">here</a><br /><br />Mobicents JSR-309 Impl page <a href="http://www.mobicents.org/mms-jsr309-main.html">http://www.mobicents.org/mms-jsr309-main.html</a><br /><br />Looking forward to your feedback mobicents-public@googlegroups.com<br /><br /><br /><span style="font-weight: bold;">Mobicents Media Server Team </span>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com1tag:blogger.com,1999:blog-8986905376324337887.post-63040441701028036022010-01-14T21:03:00.000-08:002010-01-14T21:18:35.971-08:00Mobicents Media Server (MMS) v2.0.0.BETA3 Released!<div style="text-align: left;">We are proud to announce the release of <b>Mobicents Media Server (MMS) v2.0.0.BETA3</b></div><div style="text-align: left;"><b><br /></b></div><div style="text-align: left;">The major focus of this release has been making MMS </div><div style="text-align: left;"><ol><li>Video capable</li><li>RTSP Enabled</li><li>SS7 Support</li></ol></div><div style="text-align: center;"><br /></div><div style="text-align: left;"><b>Video</b></div><div style="text-align: left;"><b><br /></b></div><div style="text-align: left;">To make Video possible, MMS has its own parser to parse <a href="http://en.wikipedia.org/wiki/ISO_base_media_file_format">ISO Based Media files</a>. 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.</div><div style="text-align: left;"><br /></div><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEixyzJd1TjmFHZ7tkgchL35kUg246fg1QKCCNs0zltEbpvOrh8HtglVVlUMFpRJG_Bx60fybK7GTvMSnS5OuSFiTs1wjBLDco9A_Ih4LNDpciS7i_HetuD6EHkylxOyTGnJWTYfgOUl9g/s320/MMSbeta3Blog-SS7-Video.jpg" style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 248px;" border="0" alt="" id="BLOGGER_PHOTO_ID_5426828126128345106" /><b>RTSP</b><div><b><br /></b><div><b><div><span class="Apple-style-span" style="font-weight: normal;"><a href="http://en.wikipedia.org/wiki/RTSP">RTSP</a> 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://<ip>:554/sample_100kbit.mp4. Add your own media files here and stream them on the fly - no need to restart the server.</span></div><div><span class="Apple-style-span" style="font-weight: normal;"><br /></span></div><div><span class="Apple-style-span" style="font-weight: normal;">The bellow diagram shows how components fit in RTSP.</span></div></b><div><div style="text-align: center;"><br /></div><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTQc6_7jplMoebbOWdDXYgfV6ZDyVahp7Cps_PAH9Xhzdquzi5o_4lWeOD8lr2u0uxXLvfP997RjD2gqvATnTyMq4LmUBA3dlm8bleWDuD2g-CNMbDuo5o8LEoaFzpIDHYetBwvc_RfQ/s320/MMSbeta3Blog-RTSP.jpg" style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 234px;" border="0" alt="" id="BLOGGER_PHOTO_ID_5426828231465106594" /><b>SS7</b><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEho0-51QT3ZASM7hPX-6YSeenbeop7hvOEJ0xGVO1V8dVf_DJ7XDbAAlHXRyvb9GlB9-KQ3AVmr8ZV7X1lWKNjf3_6tYxXQdlc9eHMRgUFwHk2QxQiuGQn_sRq3BQKA7e4LL4kRYc4mow/s1600-h/MMSbeta3Blog-SS7.jpg"></a></div><div><b><br /></b></div><div><b><div><span class="Apple-style-span" style="font-weight: normal;">This 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 <a href="http://groups.google.com/group/mobicents-public/web/mobicents-ss7-roadmap">MMS SS7 Roadmap</a> 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.</span></div><div><span class="Apple-style-span" style="font-weight: normal;"><br /></span></div><div><span class="Apple-style-span" style="font-weight: normal;">Bellow diagram shows how components fit in MMS - SS7 Architecture</span></div></b></div><div><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEho0-51QT3ZASM7hPX-6YSeenbeop7hvOEJ0xGVO1V8dVf_DJ7XDbAAlHXRyvb9GlB9-KQ3AVmr8ZV7X1lWKNjf3_6tYxXQdlc9eHMRgUFwHk2QxQiuGQn_sRq3BQKA7e4LL4kRYc4mow/s1600-h/MMSbeta3Blog-SS7.jpg" style="text-decoration: none;"><img style="text-align: left;display: block; margin-top: 0px; margin-right: auto; margin-bottom: 10px; margin-left: auto; cursor: pointer; width: 287px; height: 320px; " src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEho0-51QT3ZASM7hPX-6YSeenbeop7hvOEJ0xGVO1V8dVf_DJ7XDbAAlHXRyvb9GlB9-KQ3AVmr8ZV7X1lWKNjf3_6tYxXQdlc9eHMRgUFwHk2QxQiuGQn_sRq3BQKA7e4LL4kRYc4mow/s320/MMSbeta3Blog-SS7.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5426828496300597730" /></a><br /><br /><div style="text-align: left;">For configuration regarding the Zaptel Card visit <span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 12px; "><a href="http://groups.google.com/group/mobicents-public/web/mms-ss7-support">http://groups.google.com/group/mobicents-public/web/mms-ss7-support</a></span></div><div><br /></div><div><br /></div><div>You can download the MMS 2.0.0.BETA3 Binary from <a href="http://sourceforge.net/projects/mobicents/files/Mobicents%20Media%20Server/">http://sourceforge.net/projects/mobicents/files/Mobicents%20Media%20Server/</a></div><div><br /></div><div>Browse the SVN at <a href="http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.BETA3">http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.BETA3</a></div><div><br /></div><div>Checkout the source code for 2.0.0.BETA3 from link <a href="http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.BETA3/">http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/core/mms-core-2.0.0.BETA3/</a></div><div><br /></div><div>The public announcement is here </div><div><a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/fc334a5ef1ff79ff#">http://groups.google.com/group/mobicents-public/browse_thread/thread/fc334a5ef1ff79ff#</a></div><div><br /></div><div>Enjoy the Video! and develop real Converged Application :)</div><div><br /></div><div>Cheers</div><div><b>Mobicents Media Server Team.</b></div></div></div></div>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-52523056967599659532009-09-15T20:36:00.000-07:002009-09-15T20:43:46.400-07:00Mobicents RTSP Stack 1.0.0.BTA1 Released!We are happy to announce the first version <span style="font-weight: bold;">1.0.0.BETA1</span> of <span style="font-weight: bold;">Mobicents RTSP</span> 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.<br /><br />As of now only TCP is supported.<br /><br />Binary (including src) is available at<br /><a href="https://sourceforge.net/projects/mobicents/files/Mobicents%20RTSP/">https://sourceforge.net/projects/mobicents/files/Mobicents%20RTSP/</a><br /><br />SVN tag<br /><a href="http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/rtsp/mobicents-rtsp-1.0.0.BETA1">http://mobicents.googlecode.com/svn/tags/servers/media/2.x.y/rtsp/mobicents-rtsp-1.0.0.BETA1</a><br /><br /><br />Look at example code<br /><br />For Client Side<br /><a href="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">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</a><br /><br />For Server Side<br /><a href="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">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</a><br /><br />These are just for understanding on how to initialize the stack.<br /><br />Any feedback please divert <a href="http://groups.google.com/group/mobicents-public/topics">http://groups.google.com/group/mobicents-public/topics</a><br /><br />Enjoy the RTSP :)<br /><br />Mobicents Media Server Team.amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-59935282290698872272009-07-23T02:44:00.000-07:002009-07-23T04:11:26.087-07:00Mobicents JSR-309 Impl 2.0.0.BETA2 Released!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.<br /><br />Specifically the Events structure have changed. Now the <span style="font-style: italic;">MediaEvent</span> has method <span style="font-style: italic;">isSuccessful()</span> 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.<br /><br /><br />Every<span style="font-style: italic;"> NetworkConnection</span> now has a <span style="font-style: italic;">SdpPortManager</span>. The <span style="font-style: italic;">SdpPortManager</span> is compatible with the offer/answer model. Please look at API to understand <span style="font-style: italic;">SdpPortManager</span>. Its an important change<br /><br /><br />New features that have been added is there is an implementation for <span style="font-style: italic;">MediaConfig</span> now. <span style="font-style: italic;">MediaConfig</span> defines the internal structure of <span style="font-style: italic;">ResourceContainer</span> (<span style="font-style: italic;">NetworkConnection</span>, <span style="font-style: italic;">MediaGroup</span>, <span style="font-style: italic;">MediaMixer</span> etc). For predefined configurations like <span style="font-style: italic;">NetworkConnection.BASIC</span>, <span style="font-style: italic;">MediaGroup.PLAYER</span>, <span style="font-style: italic;">MediaGroup.PLAYER_RECORDER_SIGNALDETECTOR</span> the implementation already has corresponding predefined MediaConfigs. The access to this predefined MediaConfigs can be achieved by calling <span style="font-style: italic;">MsControlFactory.getMediaConfig(Configuration configuration)</span> passing one of the predefined <span style="font-style: italic;">Configuration</span> as parameter.<br /><br />The <span style="font-style: italic;">MediaConfig</span> 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 <span style="font-style: italic;">ResourceContainer</span> is firing signals/events on. Hence if you change the endpoint name on MMS, get the handle to existing <span style="font-style: italic;">MediaConfig</span> impl and create a custom clone by passing new set of <span style="font-style: italic;">Parameters</span> for example<br /><br /><br /><span style="font-style: italic;">MediaConfig playerConfig = msControlFactory.getMediaConfig(MediaGroup.PLAYER_RECORDER_SIGNALDETECTOR);</span><br /><span style="font-style: italic;">Parameters pNew = msControlFactory.createParameters();</span><br /><span style="font-style: italic;">pNew.put(ExtendedParameter.ENDPOINT_LOCAL_NAME, "/thisis/new/endpointname/1");</span><br /><br /><span style="font-style: italic;">MediaConfigImpl clone = (MediaConfigImpl) playerConfig.createCustomizedClone(pNew);</span><br /><br /><span style="font-style: italic;">mediaSession.createMediaGroup(clone, someParams);</span><br /><br />In this case someParams could be null as mobicents JSR309 impl still doesn't take them into consideration.<br /><br />Other way of doing this get the handle to existing MediaConfig impl and get the XML string by calling marshall()<br /><br /><span style="font-style: italic;">String xml = playerConfig.marshall();</span><br /><br />The xml will look like<br /><br /><?xml version="1.0" encoding="UTF-8"?><br />< resource-container><br /> < parameter><br /> < key> ENDPOINT_LOCAL_NAME < &frasl key ><br /> < value > &frasl mobicents &frasl media &frasl IVR &frasl$ < &frasl value ><br /> < &frasl parameter ><br /> < player ><br /> < signal ><br /> < mgcp-event > ann < &frasl mgcp-event ><br /> < mgcp-package > A < &frasl mgcp-package ><br /> < on-endpoint > true < &frasl on-endpoint ><br /> < &frasl signal ><br /> < event ><br /> < mgcp-event > oc < &frasl mgcp-event ><br /> < mgcp-package > A < &frasl mgcp-package ><br /> < on-endpoint > true < &frasl on-endpoint ><br /> < media-event > PLAY_COMPLETED< &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > of < &frasl mgcp-event ><br /> < mgcp-package > A<&frasl mgcp-package ><br /> < on-endpoint > true < &frasl on-endpoint ><br /> < media-event > PLAY_COMPLETED< &frasl media-event ><br /> < &frasl event ><br /> < &frasl player ><br /> < recorder ><br /> < signal ><br /> < mgcp-event > aupr < &frasl mgcp-event ><br /> < mgcp-package > AU<&frasl mgcp-package ><br /> < on-endpoint > true < &frasl on-endpoint ><br /> < &frasl signal ><br /> < &frasl recorder ><br /> < signal-detector ><br /> < event ><br /> < mgcp-event > dtmf0< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf1< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf2< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf3< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf4< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf5< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf6< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf7< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf8< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmf9< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmfA< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmfB< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmfC< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmfD< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmfStar< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < event ><br /> < mgcp-event > dtmfHash< &frasl mgcp-event ><br /> < mgcp-package > D<&frasl mgcp-package ><br /> < on-endpoint > false < &frasl on-endpoint ><br /> < media-event > SIGNAL_DETECTED < &frasl media-event ><br /> < &frasl event ><br /> < &frasl signal-detector><br />< &frasl resource-container><br /><br />use you favorite XML parser and replace the <value>/mobicents/media/IVR/$</value> with your value for enpoint for example <value>/thisis/new/endpointname/1</value>. Again get the String of this new XML and create a new MediaConfig object by calling<br /><br /> <span style="font-style:italic;">Reader xmlDoc = new StringReader(xml);<br /> MediaConfig config = msControlFactory.getMediaConfig(xmlDoc);<br /></span><br />And then get the corresponding <span style="font-style:italic;">ResourceContainer</span> by passing this <span style="font-style:italic;">MediaConfig</span> 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.<br /><br />For now we have flexibility to change the MGCP vs JSR309 events and Endpoint names.<br /><br />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.<br /><br />Mobicents JSR309 impl version 2.0.0.BETA2 can be downloaded from <a href="https://sourceforge.net/projects/mobicents/files/">https://sourceforge.net/projects/mobicents/files/</a><br /><br />The Mobicents JSR309 home page is at <a href="http://www.mobicents.org/mms-jsr309-main.html">http://www.mobicents.org/mms-jsr309-main.html</a><br /><br />Follow the announcement here <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/5791bdce0143d5f9#">http://groups.google.com/group/mobicents-public/browse_thread/thread/5791bdce0143d5f9#</a><br /><br />Please post your comments to <a href="http://groups.google.com/group/mobicents-public">http://groups.google.com/group/mobicents-public</a><br /><br /><br />Enjoy the JSr309 :)<br /><br /><span style="font-weight:bold;">Mobicents Media Server Team</span>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com1tag:blogger.com,1999:blog-8986905376324337887.post-85776742604124982682009-07-23T02:41:00.000-07:002009-07-23T02:44:33.961-07:00Mobicents MGCP 2.0.0.CR4 ReleasedMobicents 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. <br /><br />The binary package is mobicents-mgcp-impl-2.0.0.RC4.zip and can be downloaded from <a href="http://sourceforge.net/projects/mobicents/files/">http://sourceforge.net/projects/mobicents/files/</a><br /><br />If you want to look at source code the SVN is <a href="http://mobicents.googlecode.com/svn/trunk/servers/media/jain-mgcp">http://mobicents.googlecode.com/svn/trunk/servers/media/jain-mgcp</a><br /><br />The Mobicents MGCP Home Page is <a href="http://www.mobicents.org/mms-mgcp-main.html">http://www.mobicents.org/mms-mgcp-main.html</a><br /><br />Here is the announcement http://groups.google.com/group/mobicents-public/browse_thread/thread/37db5645d43f13be#<br /><br />Please feel free to leave a comment at <a href="http://groups.google.com/group/mobicents-public">http://groups.google.com/group/mobicents-public</a><br /><br />Cheers!amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-12626786630396017792009-06-19T02:57:00.000-07:002009-06-19T03:15:21.866-07:00Mobicents Media Server (MMS) v2.0.0.BETA1 Released!Here comes a new improved <span style="font-weight: bold;">Mobicents Media Server 2.0.0.BETA1</span>. 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.<br /><br /><span style="font-weight: bold;">Architecture</span><br /><br />The component architecture divides the process of constructing media services into two major parts:<br /><br /><ol><li>The implementation of components which generates or consume media data</li><li>The assembly of chains of media components to build media flow path.</li></ol><br />The following diagrams illustrates media components wiring and "implementation” process.<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-M5KtxivU4NSwxIQc-LNux-Cn_xSS_2fxLovCGE44oceqVeJ0moXh4bNGU6wOOuiSrHOPctG7NWqQehx3naM9d0cKOFEPpZj8qAQ4ldYVOSq1OkPyHoPAziNPosBwqqObNW1j7QU70g/s1600-h/MMSBlogMediaFlowPath.png"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 198px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-M5KtxivU4NSwxIQc-LNux-Cn_xSS_2fxLovCGE44oceqVeJ0moXh4bNGU6wOOuiSrHOPctG7NWqQehx3naM9d0cKOFEPpZj8qAQ4ldYVOSq1OkPyHoPAziNPosBwqqObNW1j7QU70g/s320/MMSBlogMediaFlowPath.png" alt="" id="BLOGGER_PHOTO_ID_5348976907655617218" border="0" /></a>As depicted on the diagram above we can isolate three main groups of the media components:<br /><br /><ul><li>components which used for generation of media content or media source;</li><li>components which consumes media or media sink;</li><li>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.</li></ul><br />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)<br /><br /><br /><span style="font-weight: bold;">Channels and pipes</span><br /><br />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.<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPaA55Qdt37Fyw585gs5_5GkEAGUt1ilE4MLI2gBkpAHQ7YVxCpSMeMqB6M0zhO0Vi34Fru91YF3LMAJtHwsWe44y_8S8DYbEtwrNX__AAoe1nWM-WeFDidHm1WTdYzOTBDZGH6fKBOg/s1600-h/MMSBlogChannel.png"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 198px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPaA55Qdt37Fyw585gs5_5GkEAGUt1ilE4MLI2gBkpAHQ7YVxCpSMeMqB6M0zhO0Vi34Fru91YF3LMAJtHwsWe44y_8S8DYbEtwrNX__AAoe1nWM-WeFDidHm1WTdYzOTBDZGH6fKBOg/s320/MMSBlogChannel.png" alt="" id="BLOGGER_PHOTO_ID_5348977692723325218" border="0" /></a>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.<br /><br /><br /><span style="font-weight: bold;">Performance</span><br /><br />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.<br /><br />Here is a comparison table between the MMS 1.x.y and MMS 2.x.y<br /><table rules="none" border="0" cellspacing="0" cols="3" frame="void"> <br /> <tbody><br /> <tr><br /> <td style="border: 1px solid rgb(0, 0, 0);" width="198" align="left" bgcolor="#c0c0c0" height="19"><b><br /></b></td><br /> <td style="border: 1px solid rgb(0, 0, 0);" width="406" align="left" bgcolor="#c0c0c0"><b>MMS 1.X.Y</b></td><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" width="322" align="left" bgcolor="#c0c0c0"><b>MMS 2.X.Y</b></td><br /> </tr><br /><br /> <tr><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left" height="19">Standalone MMS Server</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">Not available</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">Available</td><br /> </tr><br /><br /> <tr><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left" height="19">Embedded in JBoss AS</td><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">JBoss AS 4.X.Y</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">JBoss AS 5.X.Y</td><br /> </tr><br /> <tr><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left" height="53">MGCP Support</td><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">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</td><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">MGCP Controller is inbuilt with MMS. No SLEE required</td><br /> </tr><br /> <tr><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left" height="36">JSR-309 Support</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">Not available</td><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">JSR-309 is availale which uses MGCP as MS control protocol</td><br /><br /> </tr><br /> <tr><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left" height="36">MSC API</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">Available. This is custom API developed by Mobicents Media Server.</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">Not available</td><br /> </tr><br /><br /> <tr><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left" height="36">Performance</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">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</td><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">Very less Jitter as compared to 1.x.y. It uses NIO for RTP</td><br /> </tr><br /> <tr><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left" height="103">Basic Architecture</td><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">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.</td><br /><br /> <td style="border: 1px solid rgb(0, 0, 0);" align="left">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.</td><br /><br /> </tr><br /> </tbody><br /></table><br /><br /><br /><br />You can download the MMS 2.0.0.BETA1 from <a href="http://www.mobicents.org/mms-downloads.html">here</a><br /><br />Follow the announcement <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/9e878daac2e86a72">here</a><br /><br />Your valuable feed-back is welcome<br /><br /><br />Enjoy the MMS :)amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-21696266863670163982009-06-19T00:34:00.000-07:002009-06-19T03:16:22.066-07:00Mobicents JSR-309 Impl 2.0.0.BETA1 Released!<span style="font-weight: bold;">A brief intro on what is JSR-309</span><br /><br />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.<br /><br />Some of the commonly used MS control protocols are <a href="http://www.mobicents.org/mms-mgcp-main.html">MGCP (RFC 3435)</a>, 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.<br /><br />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 <a href="http://jcp.org/en/jsr/detail?id=309">here</a>.<br /><br />Still the TCK for JSR-309 is not available. We are eagerly waiting for TCK to be out.<br /><br /><br />The diagram bellow shows the high-level architecture of how application can make use of JSR-309 over MGCP<br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-WjPkwVTA60DDBAKciZxqrfHOwFQDbIbNfsjAScO3pRl-nUckZvZhP8vjYWdbwoY8_s-N64ZMbrD1ohlPtfyiw4sofy3N2VZa7pQGE5frG7UAfdtbATeYXhlTxNYTilE6v54CiC7ASg/s1600-h/SipJSR309.jpeg"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 237px; height: 320px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh-WjPkwVTA60DDBAKciZxqrfHOwFQDbIbNfsjAScO3pRl-nUckZvZhP8vjYWdbwoY8_s-N64ZMbrD1ohlPtfyiw4sofy3N2VZa7pQGE5frG7UAfdtbATeYXhlTxNYTilE6v54CiC7ASg/s320/SipJSR309.jpeg" alt="" id="BLOGGER_PHOTO_ID_5348939674355895234" border="0" /></a>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.<br /><br />You can download the mobicents-jsr309-impl-2.0.0.BETA1.zip from <a href="http://www.mobicents.org/mms-jsr309-downloads.html">here</a><br /><br />The public announcement is <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/f0f1803749a49069">here </a><br /><br />Cheers!amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-57953440179390017552009-03-31T00:45:00.000-07:002009-03-31T01:22:56.411-07:00Mobicents Media Server 1.0.0.GA Released!Here comes the first stable version of <span style="font-weight: bold;">Mobicents Media Server (MMS) 1.0.0.GA</span> that we all were waiting for!<br /><br />Follow the announcement <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/73f3dfaec3bfba1e">here</a><br /><br />Download <a href="https://sourceforge.net/project/showfiles.php?group_id=102670&package_id=263989&release_id=672288">here</a><br /><br />User Guide is <a href="http://hudson.jboss.org/hudson/job/MobicentsBooks/lastSuccessfulBuild/artifact/media/index.html">here</a><br /><br />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 :)<br /><br />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.<br /><br />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.<br /><br />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<br /><br /><span style="font-weight: bold;">Going Forward</span>....<br /><br />The support for video has already begun (check out code from <a href="http://code.google.com/p/mobicents/source/browse/#svn/trunk/servers/media">SVN trunk</a>). MMS is also actively developing endpoints for SS7 support. Have a look at wiki page <a href="http://groups.google.com/group/mobicents-public/web/mobicents-ss7-roadmap">http://groups.google.com/group/mobicents-public/web/mobicents-ss7-roadmap</a>. 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.<br /><br />Mobicents Google Group for feedback, queries is <a href="http://groups.google.com/group/mobicents-public">here</a><br /><br />Njoy!<br /><br /><span style="font-weight: bold;">Mobicents Media Server Team</span>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com1tag:blogger.com,1999:blog-8986905376324337887.post-87171362214849264302009-03-04T09:21:00.000-08:002009-03-04T10:53:19.519-08:00Mobicents Media Server Performance better than targeted for GA releaseJust few days back <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/324afa5f43848663">MMS CR6</a> was released with much improvements on performance. I did a quick performance test of CR6 using <a href="http://sipp.sourceforge.net/">SipP</a> tool for load generation, a wonderful tool called sysstat for CPU recording <a href="http://pagesperso-orange.fr/sebastien.godard/tutorial.html#section1">http://pagesperso-orange.fr/sebastien.godard/tutorial.html#section1</a> and our own <a href="http://code.google.com/p/mobicents/issues/detail?id=501">tool</a> for RTP Jitter recording.<br /><br />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.<br /><br />While the Jitter was under control the CPU never crossed more than 25%. The <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/27719cec805d05af">attached</a> graph shows the idle% CPU recorded after every 5 secs.<br /><br /><a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/27719cec805d05af#">Here</a> are the jitter graphs taken randomly while running the test tool.<br /><br />Further details <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/27719cec805d05af#">here</a>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-24797180384946829392009-02-24T02:05:00.000-08:002009-02-24T18:35:04.852-08:00Mobicents Media Server 1.0.0.CR6 Released!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 <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/a8114d9f8e156a8e#">here</a><br /><br />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 <a href="http://en.wikipedia.org/wiki/Goertzel_algorithm">Goertzel Algorithm</a> 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.<br /><br />The announcement for CR6 release is <a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/324afa5f43848663#">here</a><br /><br />Download <a href="https://sourceforge.net/project/showfiles.php?group_id=102670&package_id=263989&release_id=663597">here</a><br /><br />Cheers!amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-66070787488369175212009-02-06T01:08:00.000-08:002009-02-06T01:30:25.850-08:00Mobicents MGCP implementation pases the MGCP TCKThe Mobicents MGCP stack has cleared the TCK listed on JSR 23 <a href="http://jcp.org/aboutJava/communityprocess/final/jsr023/index.html">http://jcp.org/aboutJava/communityprocess/final/jsr023/index.html</a>, 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.<br /><br />To understand more about TCK look at README.txt at <a href="http://code.google.com/p/mobicents/source/browse/trunk/servers/media/jain-mgcp/tck/README.txt">http://code.google.com/p/mobicents/source/browse/trunk/servers/media/jain-mgcp/tck/README.txt</a><br /><br />The test output (this may vary in your environment)<br /><br /><p style=""><br /><span style="font-family: courier new;">[abhayani@localhost tck]$ mvn exec:exec</span><br /><span style="font-family: courier new;">[INFO] Scanning for projects...</span><br /><span style="font-family: courier new;">[INFO] Searching repository for plugin with prefix: 'exec'.</span><br /><span style="font-family: courier new;">[INFO] ------------------------------------------------------------------------</span><br /><span style="font-family: courier new;">[INFO] Building Mobicents MGCP TCK</span><br /><span style="font-family: courier new;">[INFO] task-segment: [exec:exec]</span><br /><span style="font-family: courier new;">[INFO] ------------------------------------------------------------------------</span><br /><span style="font-family: courier new;">[INFO] [exec:exec]</span><br /><span style="font-family: courier new;">[INFO] JAIN MGCP TCK</span><br /><span style="font-family: courier new;">[INFO] This instance is a Gateway.</span><br /><span style="font-family: courier new;">[INFO] Using org.mobicents.mgcp.stack as the path name for JainMgcpStackImpl.</span><br /><span style="font-family: courier new;">[INFO] Remote entity is 127.0.0.1:2727.</span><br /><span style="font-family: courier new;">[INFO] Verbose trace selected.</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing Bandwidth parameter class.</span><br /><span style="font-family: courier new;">[INFO] Testing single parameter constructor. Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Testing two parameter constructor. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing BearerInformation parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing CallIdentifier parameter class.</span><br /><span style="font-family: courier new;">[INFO] Invoking constructor with valid hexadecimal string. Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Calling constructor with empty string (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Calling constructor with string of more than 32 characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Calling constructor with string that contains non-hexadecimal characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setCallIdentifier() with valid hexadecimal string. Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setCallIdentifier() with empty string (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setCallIdentifier() with string of more than 32 characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setCallIdentifier() with string that contains non-hexadecimal characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing ConnectionIdentifier parameter class.</span><br /><span style="font-family: courier new;">[INFO] Invoking constructor with valid hexadecimal string. Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Calling constructor with empty string (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Calling constructor with string of more than 32 characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Calling constructor with string that contains non-hexadecimal characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setConnectionIdentifier() with valid hexadecimal string. Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setConnectionIdentifier() with empty string (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setConnectionIdentifier() with string of more than 32 characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Invoking setConnectionIdentifier() with string that contains non-hexadecimal characters (should throw exception). Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing ConnectionMode parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing EchoCancellation parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing EventName parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing ExtendedConnectionParm parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing GainControl parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing InfoCode parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing EncryptionMethod parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing PacketizationPeriod parameter class.</span><br /><span style="font-family: courier new;">[INFO] Testing single parameter constructor. Succeeded!</span><br /><span style="font-family: courier new;">[INFO] Testing two parameter constructor. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing ResourceReservation parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing SilenceSuppression parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing TypeOfNetwork parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing TypeOfService parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing LocalOptionExtension parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing NotifiedEntity parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing QuarantineHandling parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing ReasonCode parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing RegularConnectionParm parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing RequestedAction parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing PackageName parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing PackageName parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing SupportedModes parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing SupportedPackages parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Testing LocalOptVal parameter class. Succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Test of Gateway API succeeded!</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] Continuing with messaging tests.</span><br /><span style="font-family: courier new;">[INFO] Getting an instance of JainIPFactory.</span><br /><span style="font-family: courier new;">[INFO] Setting path name for stack implementation to org.mobicents.mgcp.stack.</span><br /><span style="font-family: courier new;">[INFO] Creating a JainMgcpStack object.</span><br /><span style="font-family: courier new;">[INFO] Setting port to Gateway default port 2427</span><br /><span style="font-family: courier new;">[INFO] Creating a JainMgcpProvider object</span><br /><span style="font-family: courier new;">[INFO] 0 [main] INFO org.mobicents.mgcp.stack.JainMgcpStackImpl - mgcp-stack.properties read successfully!</span><br /><span style="font-family: courier new;">[INFO] executorTableSize = 80</span><br /><span style="font-family: courier new;">[INFO] executorQueueSize = -1</span><br /><span style="font-family: courier new;">[INFO] messageReaderThreadPriority = 10</span><br /><span style="font-family: courier new;">[INFO] messageDispatcherThreadPriority = 7</span><br /><span style="font-family: courier new;">[INFO] messageExecutorThreadPriority = 5</span><br /><span style="font-family: courier new;">[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</span><br /><span style="font-family: courier new;">[INFO] Jain Mgcp stack bound to IP 0.0.0.0/0.0.0.0 and UDP port 2427</span><br /><span style="font-family: courier new;">[INFO] Creating a JainMgcpListener object</span><br /><span style="font-family: courier new;">[INFO] Adding JainMgcpListener object to JainMgcpProvider's list</span><br /><span style="font-family: courier new;">[INFO] Received AuditConnectionResponse with transaction ID 1</span><br /><span style="font-family: courier new;">[INFO] Received AuditEndpointResponse with transaction ID 2</span><br /><span style="font-family: courier new;">[INFO] Received CreateConnectionResponse with transaction ID 3</span><br /><span style="font-family: courier new;">[INFO] Received AuditConnection with transaction ID 5</span><br /><span style="font-family: courier new;">[INFO] Sent AuditConnectionResponse with transaction ID 5</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] DLCX 4 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] C:FFFF</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 4 Remote Tx ID = 4 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Received DeleteConnectionResponse with transaction ID 4</span><br /><span style="font-family: courier new;">[INFO] Received AuditEndpoint with transaction ID 7</span><br /><span style="font-family: courier new;">[INFO] Sent AuditEndpointResponse with transaction ID 7</span><br /><span style="font-family: courier new;">[INFO] Received DeleteConnectionResponse with transaction ID 4</span><br /><span style="font-family: courier new;">[INFO] Received EndpointConfigurationResponse with transaction ID 5</span><br /><span style="font-family: courier new;">[INFO] Received CreateConnection with transaction ID 9</span><br /><span style="font-family: courier new;">[INFO] Sent CreateConnectionResponse with transaction ID 9</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] EPCF 8 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] B:e:mu</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 8 Remote Tx ID = 6 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Received EndpointConfigurationResponse with transaction ID 6</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] MDCX 10 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] C:FFFF</span><br /><span style="font-family: courier new;">[INFO] I:FFFF</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 10 Remote Tx ID = 7 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Received ModifyConnectionResponse with transaction ID 7</span><br /><span style="font-family: courier new;">[INFO] Received EndpointConfigurationResponse with transaction ID 6</span><br /><span style="font-family: courier new;">[INFO] Received ModifyConnectionResponse with transaction ID 7</span><br /><span style="font-family: courier new;">[INFO] Received ModifyConnectionResponse with transaction ID 8</span><br /><span style="font-family: courier new;">[INFO] Received NotificationRequestResponse with transaction ID 9</span><br /><span style="font-family: courier new;">[INFO] Received DeleteConnection with transaction ID 16</span><br /><span style="font-family: courier new;">[INFO] Sent DeleteConnectionResponse with transaction ID 16</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] MDCX 13 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] C:FFFF</span><br /><span style="font-family: courier new;">[INFO] I:FFFF</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 13 Remote Tx ID = 10 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Received ModifyConnectionResponse with transaction ID 10</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] RQNT 14 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] X:FFFF</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 14 Remote Tx ID = 11 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Received NotificationRequestResponse with transaction ID 11</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] RQNT 15 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] X:FFFF</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 15 Remote Tx ID = 12 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Received NotificationRequestResponse with transaction ID 12</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] NTFY 17 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] X: FFFF</span><br /><span style="font-family: courier new;">[INFO] O: */AllEvents</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 17 Remote Tx ID = 13 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Received NotifyResponse with transaction ID 13</span><br /><span style="font-family: courier new;">[INFO] Received ModifyConnectionResponse with transaction ID 10</span><br /><span style="font-family: courier new;">[INFO] Received NotificationRequestResponse with transaction ID 11</span><br /><span style="font-family: courier new;">[INFO] Received EndpointConfiguration with transaction ID 24</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] RQNT 18 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] X:FFFF</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 18 Remote Tx ID = 14 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] NTFY 19 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] X: FFFF</span><br /><span style="font-family: courier new;">[INFO] O: */AllEvents</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 19 Remote Tx ID = 15 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] NTFY 20 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] X: FFFF</span><br /><span style="font-family: courier new;">[INFO] O: */AllEvents</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 20 Remote Tx ID = 16 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] message =</span><br /><span style="font-family: courier new;">[INFO] RSIP 21 local@127.0.0.1:2727 MGCP 1.0</span><br /><span style="font-family: courier new;">[INFO] RM:disconnected</span><br /><span style="font-family: courier new;">[INFO]</span><br /><span style="font-family: courier new;">[INFO] local Tx ID = 21 Remote Tx ID = 17 Sending the Command 2</span><br /><span style="font-family: courier new;">[INFO] Sent EndpointConfigurationResponse with transaction ID 24</span><br /><span style="font-family: courier new;">[INFO] Received NotificationRequestResponse with transaction ID 14</span><br /><span style="font-family: courier new;">[INFO] Received NotifyResponse with transaction ID 15</span><br /><span style="font-family: courier new;">[INFO] Received NotifyResponse with transaction ID 16</span><br /><span style="font-family: courier new;">[INFO] Received RestartInProgressResponse with transaction ID 17</span><br /><span style="font-family: courier new;">[INFO] Test of messaging capability succeeded!</span><br /></p>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com1tag:blogger.com,1999:blog-8986905376324337887.post-35158391055605441532009-02-04T05:32:00.000-08:002009-02-04T05:36:01.013-08:00Mobicents JAIN MGCP 2.0.0.CR1 Released!<span style="font-size:100%;">We are happy to announce the first independent binary release of Mobicents JAIN MGCP Stack implementation 2.0.0.CR1 !<br /><br />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.<br /><br /><b>Where to download from?</b><br />The distribution can be found on SourceForge.net. The binary package is mobicents-mgcp-impl-2.0.0.RC1.</span> <div id=":1qn" class="ArwC7c ckChnd"><wbr><span style="font-size:100%;">zip:<br /><a href="https://sourceforge.net/project/showfiles.php?group_id=102670&package_id=308747&release_id=658531" target="_blank">https://sourceforge.net/<wbr>project/showfiles.php?group_<wbr>id=102670&package_id=308747&<wbr>release_id=658531</a><br /><b><br />Source repositories:</b><br />-------------------<br />SVN<br /><a href="http://mobicents.googlecode.com/svn/trunk/servers/media/jain-mgcp" target="_blank">http://mobicents.googlecode.<wbr>com/svn/trunk/servers/media/<wbr>jain-mgcp</a><br /><br />SVN TAG<br /><a href="http://code.google.com/p/mobicents/source/browse/#svn/tags/servers/media/2.x.y/jain-mgcp/mobicents-mgcp-impl-2.0.0.RC1" target="_blank">http://code.google.com/p/<wbr>mobicents/source/browse/#svn/<wbr>tags/servers/media/2.x.y/jain-<wbr>mgcp/mobicents-mgcp-impl-2.0.<wbr>0.RC1</a><br /><b><br />How to get started & Media Server Documentation</b><br />------------------------------ </span> <wbr><span style="font-size:100%;">-----------------<br /><a href="http://groups.google.com/group/mobicents-public/web/user-guide" target="_blank">http://groups.google.com/<wbr>group/mobicents-public/web/<wbr>user-guide</a> - Chapter 8<br /><br />Looking forward to your feedback<br /><a href="http://groups.google.com/group/mobicents-public/browse_thread/thread/4944fde3177f813e">http://groups.google.com/group/mobicents-public/browse_thread/thread/4944fde3177f813e</a><b><br /></b></span> </div>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com0tag:blogger.com,1999:blog-8986905376324337887.post-3276349386646452502009-02-04T02:11:00.000-08:002009-02-04T02:36:53.841-08:00Mobicents Media Server 2.x.y SVN Structure<span style="font-size:100%;"><span style="font-family:arial;">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</span><br /><br /></span><ul style="font-family:arial;"><li><span style="font-size:100%;">media</span></li><ul><li><span style="font-size:100%;">jain-mgcp</span></li><li><span style="font-size:100%;">jain-megaco</span></li><li><span style="font-size:100%;">mscml</span></li><li><span style="font-size:100%;">jsr-309</span></li><li><span style="font-size:100%;">core</span></li><ul><li><span style="font-size:100%;">server-spi</span></li><li><span style="font-size:100%;">server-impl</span></li><li><span style="font-size:100%;">server-sar</span></li><li><span style="font-size:100%;">server-standalone</span></li><li><span style="font-size:100%;">mgcp-controller</span></li><li><span style="font-size:100%;">megaco-controller</span></li></ul><li><span style="font-size:100%;">examples - All standalone examples here (not depending on SLEE or Sip Servlets)<br /></span></li><li><span style="font-size:100%;">slee</span></li><ul><li><span style="font-size:100%;">ra</span></li><ul><li><span style="font-size:100%;">mgcp</span></li><li><span style="font-size:100%;">megaco</span></li><li><span style="font-size:100%;">jsr-309</span></li></ul><li><span style="font-size:100%;">examples - All SLEE examples here</span></li><ul><li><span style="font-size:100%;">converged-demo</span></li><li><span style="font-size:100%;">call-controller</span></li><li><span style="font-size:100%;">mgcp-demo</span></li></ul></ul></ul></ul><span style="font-size:100%;"><span style="font-family:arial;"><br />The protocol stacks jain-mgcp, jain-meagco, mscml and jsr-309 are independent of MMS components and depends on mobicents parent.<br /></span><br /><span style="font-family:arial;">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.</span><br /><br /><span style="font-family:arial;">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</span><br /></span>amit.bhayanihttp://www.blogger.com/profile/03443922141120254113noreply@blogger.com1