Mobicents Blogs

GIT Master Browse

http://code.google.com/p/jasn/source/browse/?name=release-2.0.1.FINAL

GIT Tag Browse

http://code.google.com/p/sctp/source/browse/?name=release-1.1.0.FINAL

http://code.google.com/p/jss7/source/browse/?name=release-2.0.0.BETA4

How to Use it?

Please refer to documentation in /ss7 module for detailed explanation.

More Information

For more detailed information, please visit the following sites:

Mobicents Google Group, for posting questions (http://groups.google.com/ group/mobicents-public)
Mobicents Homepage (http://www.mobicents.org)

Mobicents jSS7 Team

Build your own Mobicents Dashboard in 15 Minutes!

Alexandre Mendonça — Mon, 17 Dec 2012 12:03:00 +0000

The Mobicents suite is growing everyday, from the early days of the initial JAIN SLEE container project, a lot of new fronts have been going on, such as SIP Servlets, Diameter Stack, Media Server, SS7 Stack, Restcomm, etc.

With such a vaste suite of projects, the need for common management and monitoring tools is a major concern we have been facing, as each project having it's own set of tools is not a optimal solution. At least a common framework/interface is desired.

JMX is a standard for monitoring and managing JVMs, but it's connector uses RMI, which is not the sexiest protocol these days. In that sense, we have searched for a JMX <=> HTTP bridge to use a REST-like protocol as a frontend to the JMX server. This brought us to Jolokia. With such bridge, we can easily extend our choices of management frameworks outside Java. Plus, it brings many other goodies, such as being firewall friendly (HTTP is allowed anywhere), security (filter what is accessible), support for bulk requests, etc.

Installing Jolokia

Jolokia is very simple to install in the JBoss AS container:

Download Jolokia from here. Select the binary package.
Extract the zip file.
Copy the jolokia.war from the agents sub-directory to your JBoss AS deploy directory.
If the JBoss AS is not running already, start it.

You should now be able to issue HTTP requests to Jolokia agent. Using curl (or pointing your browser to the URL), you can do:

$ curl http://localhost:8080/jolokia/read/java.lang:type=Memory/HeapMemoryUsage/used

{"timestamp":1355453720,"status":200,"request":{"mbean":"java.lang:type=Memory","path":"used",
"attribute":"HeapMemoryUsage","type":"read"},"value":310667560}

This is how we read a value, returned in a JSON format, using Jolokia REST API. The format used is the following: <base-url>/read/<mbean name>/<attribute name>/<inner path>. You can learn more reading the Jolokia Reference Manual.

So, now that we have this working, lets make some good use of it. Graphs are the best way to show this data over time. Looking for a good JavaScript graphs library, there are several options such as Google Chart Tools, HighCharts, jqPlot, YUI Charts, etc. For this demo we will be using HighCharts. It is not completely free, but it is a very good and feature rich chart library, plus there's this great article by Tomasz Nurkiewicz to help us getting started.

So, let's start to build our dashboard. Create an HTML file in your favorite editor and, here we go:


<html>
 <body>
  <div id="chart" />

  <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.js"></script>
  <script src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.9.2/jquery-ui.js"></script>
  <script src="http://jolokia.org/dist/1.0.6/js/jolokia.js"></script>
  <script src="http://jolokia.org/dist/1.0.6/js/jolokia-simple.js"></script>
  <script src="http://code.highcharts.com/highcharts.src.js"></script>

  <script id="source" language="javascript" type="text/javascript">
   $(document).ready(function() {
    var jolokia = new Jolokia("http://localhost:8080/jolokia");

    var chart = new Highcharts.Chart({
     chart: {
      renderTo: 'chart',
      defaultSeriesType: 'spline',
      events: {
       load: function() {
        var series = this.series[0];
        setInterval(function() {
         var x = (new Date()).getTime();
         var memoryUsed = jolokia.getAttribute("java.lang:type=Memory", "HeapMemoryUsage", "used");
         series.addPoint({
          x: new Date().getTime(),
          y: parseInt(memoryUsed)
         }, true, series.data.length >= 50);
        }, 1000);
       }
      }
     },
     title: {
      text: 'HeapMemoryUsage'
     },
     xAxis: {
      type: 'datetime'
     },
     yAxis: {
      title: { text: 'HeapMemoryUsage' }
     },
     series: [{
      data: [],
      name: 'Used Memory'
     }]
    });
   });
  </script>
 </body>
</html>

These 50 lines of HTML/JavaScript code already produce a very nice chart:

This is as easy as it gets! We may now add a lot of other extras, make it more generic to handle several charts, several data sources per chart, make use of jQuery UI Sortable to make a portlet-like dashboard, where it is possible to group and arrange those charts as desired, etc. Ready? Let's go!


<html>
 <head>
  <link rel="stylesheet" type="text/css" href="http://ajax.googleapis.com/ajax/libs/jqueryui/1.9.2/themes/black-tie/jquery-ui.css"/>
  <style>
   .column { width: 400px; float: left; padding-bottom: 10px; }
   .portlet { margin: 0 1em 1em 0; }
   .portlet-header { margin: 0.3em; padding-bottom: 4px; padding-left: 0.2em; }
   .portlet-header .ui-icon { float: right; }
   .portlet-content { padding: 0.4em; }
   .ui-sortable-placeholder { border: 1px dotted black; visibility: visible !important; height: 238px !important; }
   .ui-sortable-placeholder * { visibility: hidden; }
  </style>
 </head>

 <body style="background-color: #EEE; font-family: Verdana; font-size: small;">
  <!-- The template to be used for new portlets -->
  <div style="display: none;">
   <div class="portlet ui-widget-content ui-helper-clearfix ui-corner-all" id="portlet-template" style="">
    <div class="portlet-header ui-widget-header ui-corner-all">
     <span class='ui-icon ui-icon-minusthick'></span>
     <span class="title"> </span>
    </div>
    <div class="portlet-content"></div>
   </div>
  </div>

  <div><h2 style="text-align: center;">.:[ MOBICENTS DASHBOARD ]:.</h2></div>
  <hr />
  <div id="charts" class="column" /></div>

  <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.js"></script>
  <script src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.9.2/jquery-ui.js"></script>
  <script src="http://jolokia.org/dist/1.0.6/js/jolokia.js"></script>
  <script src="http://jolokia.org/dist/1.0.6/js/jolokia-simple.js"></script>
  <script src="http://code.highcharts.com/highcharts.src.js"></script>

  <script id="source" language="javascript" type="text/javascript">
  $(document).ready(function() {
   jolokia = new Jolokia({url: "http://localhost:8080/jolokia", fetchInterval: 1000});

   var factory = new JmxChartsFactory();
    factory.create([
     {
      type: 'read',
      name: 'org.mobicents.slee:name=EventRouterStatistics',
      attribute: 'AverageEventRoutingTime'
     }
    ]);
    factory.create([
     {
      type: 'read',
      name: 'org.mobicents.slee:name=EventRouterStatistics',
      attribute: 'ActivitiesMapped'
     }
    ]);
    executors = []
    numExecutors = jolokia.getAttribute("org.mobicents.slee:name=EventRouterConfiguration","EventRouterThreads");
    for (var i = 0; i < numExecutors; i++) {
     executors[i] = {
      type: 'exec',
      name: 'org.mobicents.slee:name=EventRouterStatistics',
      operation: 'getAverageEventRoutingTime(int)',
      args: [i]
     }
    }
    factory.create(executors);
    factory.create([
     {
      type: 'read',
      name: 'java.lang:type=Memory',
      attribute: 'HeapMemoryUsage',
      path: 'committed'
     },
     {
      type: 'read',
      name: 'java.lang:type=Memory',
      attribute: 'HeapMemoryUsage',
      path: 'used'
     }
    ]);
    factory.create(
     {
      type: 'read',
      name: 'java.lang:type=OperatingSystem',
      attribute: 'SystemLoadAverage'
     }
    );
    factory.create(
     {
      type:  'read',
      name:  'java.lang:type=Threading',
      attribute: 'ThreadCount'
     }
    );
   });

   function JmxChartsFactory(keepHistorySec, pollInterval, columnsCount) {
    var series = [];
    var monitoredMbeans = [];
    var chartsCount = 0;

    // if not given a value for number of columns, use what fits.
    columnsCount = columnsCount || Math.floor($(window).width()/$(".column").width());
    // poll interval, defaults to 1000ms
    pollInterval = pollInterval || 1000;
    // how many data points to show in the graphs, defaults to 30
    var keepPoints = (keepHistorySec || 30) / (pollInterval / 1000);

    setupPortletsContainer(columnsCount);

    setInterval(function() {
     pollAndUpdateCharts();
    }, pollInterval);

    this.create = function(mbeans) {
     mbeans = $.makeArray(mbeans);
     series = series.concat(createChart(mbeans).series);
     monitoredMbeans = monitoredMbeans.concat(mbeans);
    };

    function pollAndUpdateCharts() {
     var requests = prepareBatchRequest();
     var responses = jolokia.request(requests);
     updateCharts(responses);
    }

    function createNewPortlet(name) {
     return $('#portlet-template')
       .clone(true)
       .appendTo($('.column')[chartsCount++ % columnsCount])
       .removeAttr('id')
       .find('.title').text((name.length > 50 ? '...' : '') + name.substring(name.length - 50, name.length)).end()
       .find('.portlet-content')[0];
    }

    function setupPortletsContainer() {
     var column = $('.column');
     for(var i = 1; i < columnsCount; ++i){
      column.clone().appendTo(column.parent());
     }
     $(".column").sortable({
      connectWith: ".column"
     });

     $(".portlet-header .ui-icon").click(function() {
      $(this).toggleClass("ui-icon-minusthick").toggleClass("ui-icon-plusthick");
      $(this).parents(".portlet:first").find(".portlet-content").toggle();
     });
     $(".column").disableSelection();
    }

    function prepareBatchRequest() {
     return $.map(monitoredMbeans, function(mbean) {
      switch(mbean.type) {
       case 'read':
        return {
         type: mbean.type,
         opts: mbean.args,
         mbean: mbean.name,
         attribute: mbean.attribute,
         path: mbean.path
        };
        break;
       case 'exec':
        return {
         type: mbean.type,
         arguments: mbean.args,
         mbean: mbean.name,
         operation: mbean.operation,
         path: mbean.path
        };
        break;
      }
     });
    }

    function updateCharts(responses) {
     var curChart = 0;
     $.each(responses, function() {
      var point = {
       x: this.timestamp * 1000,
       y: parseFloat(this.value)
      };
      var curSeries = series[curChart++];
      curSeries.addPoint(point, true, curSeries.data.length >= keepPoints);
     });
    }

    function createChart(mbeans) {
     return new Highcharts.Chart({
      chart: {
       renderTo: createNewPortlet(mbeans[0].name),
       height: 200,
       defaultSeriesType: 'spline',
      },
      title: { text: null },
      xAxis: { type: 'datetime' },
      yAxis: { title: { text: mbeans[0].attribute || mbeans[0].operation } },
      legend: {
       enabled: true,
       borderWidth: 0
      },
      credits: {enabled: false},
      series: $.map(mbeans, function(mbean) {
       return {
        data: [],
        name: mbean.path || mbean.attribute || mbean.args
       }
      })
     })
    }
   }
  </script>
 </body>
</html>

A bit more of code than previously, but with this we added 6 different graphs, some with more than one data series, we added portlet behavior... in my opinion, it is still quite simple for the output we get of it:

Is it cool or what? And all of this in a single static html file. Personally, I love it.

And this is the way we are heading with Mobicents Monitoring and Management... adding some extras such as thresholds with some kind of alarms/notifications, more customization like easily adding/removing charts at runtime through web interface, add some persistence to remember history and preferences, and many more to make this a solid tool to keep your Mobicents suite under control!

Mobicents jSS7 v2.0.0.BETA3 released!

amit.bhayani — Tue, 20 Nov 2012 10:16:00 +0000

We are happy to announce a new Mobicents jSS7 release, v2.0.0.BETA3!

Download from http://code.google.com/p/jss7/wiki/Downloads?tm=2

What's new in this release?

This release consist of following new features

M3UA load balancing is taken care. Depending on configuration, most significant bit or least significant bit of SLS is used for load balancing between AS and remaining bits are used for load balancing between ASP's
At SCCP layer the load balancing between primary and backup address is now configurable for bits 0,1,2,3 and 4 of SLS
Added management event listeners for SCTP, M3UA and SCCP layers for external management and monitoring
New MAP messages cancelLocation, provideRoamingNumber, sendRoutingInfo, insertSubscriberData implemented
Implemented GEO Primitives in MAP
M3UA number of ASP that should be active for loadbalancing can now be configured at AS creation time
Added support for UCS2 and Urdu GSM7 Bit encoding for USSD

In addition many bugs fixed and some performance improvements. Complete list of issues covered in this release are listed here http://code.google.com/p/jss7/issues/list?can=1&q=Version%3D2.0.0.BETA3&sort=priority+version&groupby=version&colspec=Summary+Type+Status+ID&cells=tiles

WARNING :

If you are upgrading to jSS7 2.0.0.BETA3 from older version, make sure you delete the SccpStack_sccpresource.xml and SccpStack_sccprouter.xml from persist directory. These are the files where SCCP persists configurations. You will have to execute the SCCP commands again from CLI. This is because there are changes in XML tags of persist directory and instead of using fully qualified calss names, it now uses the nouns which is in line with how its done in M3UA and SCTP. See the issue http://code.google.com/p/jss7/issues/detail?id=146

Please note that archives are now uploaded to https://oss.sonatype.org/ content/groups/public. Please point to sonatype repository in your applications pom.xml

<id>mobicents-public- repository-group</id>

<name>Mobicens Public Maven Repository Group</name>

<url>https://oss.sonatype.org/ content/groups/public</url>

<layout>default</layout>

<updatePolicy>never</ updatePolicy>

</releases>

<updatePolicy>never</ updatePolicy>

</snapshots>

</repository>

Daily build is configured at https://mobicents.ci. cloudbees.com/job/Mobicents- jSS7-2.x/

Binary release includes

ASN 2.0.1.FINAL
SCTP 1.0.0.FINAL
SS7 2.0.0.BETA3

Home page for each project

GIT Master Browse

http://code.google.com/p/jasn/source/browse/?name=release-2.0.1.FINAL

GIT Tag Browse

http://code.google.com/p/sctp/source/browse/?name=release-1.0.0.FINAL

http://code.google.com/p/jss7/source/browse/?name=release-2.0.0.BETA3

How to Use it?

Please refer to documentation in /ss7 module for detailed explanation.

More Information

For more detailed information, please visit the following sites:

Mobicents Google Group, for posting questions (http://groups.google.com/ group/mobicents-public)
Mobicents Homepage (http://www.mobicents.org)

Mobicents jSS7 Team

How to bulk update deals in Highrise HQ

Ivelin — Mon, 22 Oct 2012 12:08:00 +0000

Mobicents jSS7 2.0.0.BETA2 Released!

amit.bhayani — Sun, 09 Sep 2012 13:36:00 +0000

We are happy to announce a new Mobicents jSS7 release, v2.0.0.BETA2!

What's new in this release?

This release is jam packed with new features

The client side command line interface provides tab completion and help for every command. Look at Issue 2
CAP V2 circuit switched call fully implemented (Issue 10)
New MAP messages CheckIMEI (Issue 76) implemented
All the unimplemented MAP/CAP messages have API interfaces already defined (Issue 104, Issue 105, Issue 106, Issue 107, Issue 108)
M3UA ASP ID can now be configured at ASP creation time (Issue 15)
SCTP layer supports configuring server that accepts connection from anonymous ip:port
Added support for ANSI Point Code format (both 5bit and 8bit SLS) (Issue 3)
Support for WinOS native drivers for Dialogic
Enhanced SS7 simulator to act as SMS Center for testing (Issue 73)

In addition many bugs fixed and some performance improvements. Complete list of issues covered in this release are listed here http://code.google.com/p/jss7/issues/list?can=1&q=Version%3D2.0.0.BETA2&sort=priority+version&groupby=version&colspec=Summary+Type+Status+ID&cells=tiles

Other features implemented but not included in this binary is completion of TCAP RA and CAP RA which will be bundled with next release of JAIN SLEE Server

Please note that archives are now uploaded to https://oss.sonatype.org/ content/groups/public. Please point to sonatype repository in your applications pom.xml

<id>mobicents-public- repository-group</id>

<name>Mobicens Public Maven Repository Group</name>

<url>https://oss.sonatype.org/ content/groups/public</url>

<layout>default</layout>

<updatePolicy>never</ updatePolicy>

</releases>

<updatePolicy>never</ updatePolicy>

</snapshots>

</repository>

Download

Download 2.0.0.BETA2 from http://code.google.com/p/jss7/wiki/Downloads?tm=2

Daily build is configured at https://mobicents.ci. cloudbees.com/job/Mobicents- jSS7-2.x/

Binary release includes

ASN 2.0.1.FINAL
SCTP 1.0.0.CR4
SS7 2.0.0.BETA2

Home page for each project

GIT Master Browse

http://code.google.com/p/jasn/source/browse/?name=release-2.0.1.FINAL

GIT Tag Browse

http://code.google.com/p/sctp/source/browse/?name=release-1.0.0.CR4

http://code.google.com/p/jss7/source/browse/?name=release-2.0.0.BETA2

How to Use it?

Please refer to documentation in /ss7 module for detailed explanation.

More Information

For more detailed information, please visit the following sites:

Mobicents Google Group, for posting questions (http://groups.google.com/ group/mobicents-public)
Mobicents Homepage (http://www.mobicents.org)

Mobicents jSS7 Team

Mac OSX / Terminal Tip : Naming your terminal windows and tabs

Alexandre Mendonça — Sat, 18 Aug 2012 01:55:00 +0000

I'm a huge fan for those little tips that can save you some time and frustration.

Recently working with several terminal windows and tabs, I've been finding myself wandering around them to find the right terminal where I wanted to land on. All added up, it was a significant penalty in my "performance" and, even worse, made me mad!

I was already using different color schemes for the different terminal windows, by contexts, so I could quickly identify what was in each terminal once I see it. But since having 6+ terminal windows and colors is not practical, I group some in the same window, again, by context.

I've decided to look for a way to name the terminal window and/or tabs so I can quickly get to the one I needed. It's actually quite simple, just type (in the desired terminal tab):

echo -n -e "\033]0;Your Title Goes Here\007"

et voilà! Precious time saved!

Mobicents SIP Servlets on JBoss AS7 passes the JSR 289 TCK !

Jean Deruelle — Thu, 16 Aug 2012 22:29:00 +0000

Following on today's news that TeleStax, Inc is now a member of the JCP and part of the JSR 359 Expert Group, we are also pleased to announce that latest snapshot version of Mobicents SIP Servlets (MSS) on JBoss AS7 is now passing the JSR 289 which means it is the first SIP Servlets container to integrate with HTTP Servlets 3.0, Java EE 6 and benefits from all the JBoss AS7 goodnesses (it now starts as fast as Tomcat and integrates with JBoss AS7 CLI for monitoring and management)

You can see the test results from our Cloudbees Jenkins Continuous Integration Job (Thanks to the Cloudbees FOSS Program)

Roadmap

We still have a couple of items left to complete before calling it a release, namely the Documentation.

As such we decided to bump the next release version number to 2.0.0.FINAL and updated the roadmap accordingly

Special Thanks

I would like to thank the usual suspects that work on this ie :

myself for helping here and there at the end and mostly in the beginning by refactoring MSS on being independent of any containers, ie MSS could plug into other containers such as Jetty, Resin, Glassfish (if there is enough interest or contributors ready to contribute either container integration)
Vladimir Ralev who did the initial chunk of work for integrating into 7.0.2 and having a proof of concept
But most importantly a HUGE Thanks to Jose Maria Recio, Co-Founder of Solaiemes whose products help carriers to keep their role relevant, allowing them to build alternatives to over-the-top offers using enablers as Joyn / RCS-e and RCS as a Platform. He highly earned his stripes to be on the Mobicents Hall of Fame along with other companies like Twilio, Cisco, Avaya, OKI, Free Mobile and many others...

New Hat

Eduardo Martins — Tue, 10 Jul 2012 10:09:00 +0000

I'm now officially a member of the JBoss Application Server core development team, my blog will now become more personal, and switch focus to the matters of my main activity. I created a new blog for the Mobicents SLEE project, please follow it ;-)

Mobicents Diameter has a new home.. powered by git!

Alexandre Mendonça — Wed, 04 Jul 2012 01:12:00 +0000

Due to the increasingly number and complexity of sub-projects, Mobicents has been splitting it's projects under independent project homes.

We are now at a transition stage, where each project lead will migrate his project at the appropriate time. For Diameter, after our major release (1.4.0.FINAL), it seemed the best time to do this migration.

The new home of the Mobicents Diameter project is located at http://code.google.com/p/jdiameter/. Feel free to visit us!

With this change, we have also taken the chance to move to a "better" and more powerful version control system, so we have changed from SVN to Git. We hope this will ease the contributions, which have been happening more often, thanks to out thriving community!

Despite being a allegedly better VCS, Git also has it's own shortcomings, such as not being able to checkout a single folder. The lack of this feature has impacted our structure, since it makes it impossible to independently release sub-components in the same Git repository.

While digging for a solution, I've came across the "sparse checkout" feature. While this may work for checking out only some folder(s), it is not supported by maven release plugin, thus not fixing the main problem. Another possible (and probably more correct) solution would be to use the "sub-repository" approach, where we'd split the components into different sub-repositories.

We actually did this on a first phase, but after realizing the big changes it would imply and being aware that google code messes with the automatic revision links (http://code.google.com/p/support/issues/detail?id=3245) we have decided to revert back to the single repository approach and abdicate from the release independency for each component. We have barely used it, anyway. The only exception is for the ~~Jopr~~ RHQ Plugin, so it got it's own sub-repository.

As a reference for someone going through the same process of moving from a [googlecode] SVN repository to a [googlecode] git repository, I'll leave a summary of the commands used for the move (please keep in mind that I'm totally new to git, so these may not be the optimal way, feel free to comment):

0. (optional) Since SVN only lists the username and git uses the email as well, the migration will cause weird authors such as "brainslog <brainslog@bf0df8d0-2c1f-0410-b170-bd30377b63dc>" it may be good to sanitize the authors. For that I've used the following script in the SVN repository:
svn log -q | awk -F '|' '/^r/ {sub("^ ", "", $2); sub(" $", "", $2); print $2" = "$2" <"$2">"}' | sort -u > authors.txt

And then I've fixed the outcome in authors.txt to the correct: username = Full Name .

1. Clone the new (and probably empty) repository
git clone https://@code.google.com/p/jdiameter/ git-jdiameter

2. Clone from SVN (with authors fixed) to the cloned git repository, with full history, tags and branches
git svn clone -A authors.txt -Ttrunk/servers/diameter -ttags/servers/diameter -bbranches/servers/diameter https://mobicents.googlecode.com/svn git-jdiameter

Where -A points to the authors file, -T to the trunk of the SVN repository, -t to the tags and -b to the branches. Use only what you need, I didn't needed the branches part as we don't have any.

3. Enter the local git repository
cd git-jdiameter

4. Push!
git push --all

5. Create the git tags from SVN tags (I know this can be automatized but I needed to make some customizations to existing tags, as not all were correct)
git tag "1.0.0.BETA1" "refs/remotes/tags/jdiameter-1.0.0.BETA1"
...
git tag "1.0.0.FINAL" "refs/remotes/tags/1.0.0.FINAL"

6. Push.. again!
git push --tags

These are the 7 magical steps! In case that you don't care about history, simply do a "svn export --force http://mobicents.googlecode.com/svn/trunk/servers/diameter/ git-jdiameter" and push it, nothing else. Also, as mentioned, I did not had branches but I suppose they'd make it in the #4 push.

Mobicents Diameter users working with ~~trunk~~ master, must now switch to this new repository as the SVN will not be updated anymore! Do a "git clone https://code.google.com/p/jdiameter/" and hack away!

Say hello to RAY

Eduardo Martins — Tue, 19 Jun 2012 08:42:00 +0000

Mobicents SLEE 2.7.0.FINAL, codenamed RAY, is now available for download, check the release announcement, as usual there are lots of goodies included :-)

Mobicents SMSC Gateway achieves 1000 SMS/Sec rate!

amit.bhayani — Tue, 12 Jun 2012 01:36:00 +0000

Mobicents SMSC is first and only open source SMSC Gateway completely on Java. Last week SMSC Gateway was put under stress in production environment at one of the Tier-1 operators.

We are glad to announce that Mobicents SMSC Gateway achieved 1000 SMS/Sec rate and successfully delivered 1 billion SMS's per day per SMSC instance. With Cluster of 4 SMSC instances doing load balance, it easily reaches 3.8 Billion SMS per day.

The test environment was based on "Bulk SMS" application where ESME would submit the SMS's to SMSC and SMSC in-turn would do MAP SRI for MSISDN and then ForwardSM. Since this was real life scenario, there were Components Error like user not available and other MAP error conditions which SMSC handled gracefully.

The Bulk SMS Application used is developed and contributed by TeleStax partners Convergence

Mobicents SMSC Gateway is deployed on Quad Core Dual Processor Servers - Intel Xeon X5570. The OS is CentOS 5.8. JVM minimum(-Xms) and maximum(-Xmx) memory set is 3GB.

Below is the wireshark screenshot showing the throughput from ESME

For each SMS on an average there were 4 MAP messages getting exchanged; the throughput in terms of MAP is more than 4000 MAP messages/sec. Below is the wireshark analysis of MAP messages

Mobicents jSS7 2.0.0.BETA1 Released!

amit.bhayani — Thu, 07 Jun 2012 01:23:00 +0000

We are happy to announce a new Mobicents jSS7 release, v2.0.0.BETA1!

What's new in this release?

This release is jam packed with new features

CAP Protocol included in the binary for first time. Only version 1 and 2 of CAP are supported. Look at Issue 1 and Issue 10
New MAP messages AnyTimeInterrogation (Issue 9), UpdateLocation (Issue 57) and SendAuthenticationInfo (Issue 58) included
Support for dahdi based cards, Digum and Sangoma (Issue 29) brought back
New GUI based SS7 Simulator introduced (Issue 17). This tool allows users to test SS7 stack conveniently with click of button!
SCCP pointcode loadbalancing taken care (Issue 13)

In addition many bugs fixed and some performance improvements. Complete list of issues covered in this release are listed here http://code.google.com/p/ jss7/issues/list?can=1&q= Version%3D2.0.0.BETA1&sort= priority+version&groupby= version&colspec=Summary+Type+ Status+ID&cells=tiles

Please note that archives are now uploaded to https://oss.sonatype.org/ content/groups/public. Please point to sonatype repository in your applications pom.xml

<id>mobicents-public- repository-group</id>

<name>Mobicens Public Maven Repository Group</name>

<url>https://oss.sonatype.org/ content/groups/public</url>

<layout>default</layout>

<updatePolicy>never</ updatePolicy>

</releases>

<updatePolicy>never</ updatePolicy>

</snapshots>

</repository>

Daily build is configured at https://mobicents.ci. cloudbees.com/job/Mobicents- jSS7-2.x/

Binary release includes

ASN 2.0.0.FINAL
SCTP 1.0.0.CR3
SS7 2.0.0.BETA1

Where to download from?

https://sourceforge.net/ projects/mobicents/files/ Mobicents%20Protocols%20Suite/ 2.0.0.BETA1/?

Home page for each project

GIT Master Browse