Showing posts with label jss7. Show all posts
Showing posts with label jss7. Show all posts

Wednesday, March 27, 2013

Mobicents jSS7 2.0.0.CR1 Released!

Mobicents jSS7 Team is proud to announce the first Candidate Release version 2.0.0.CR1


Mobicents jSS7 Team

Sunday, January 13, 2013

Mobicents jSS7 2.0.0.BETA4 Released!


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


What's new in this release?

This release is jam packed with new features
  1. SCCP Rule definition simplified by adding new property "originationType". Further details here Issue 142
  2. Implemented insertSubscriberData MAP message. Issue 152
  3. Implemented missing primitives for sendRoutingInfo MAP operation. Issue 172
  4. Management methods exposed for layers SCTP, SCCP and M3UA. Issue 179  
  5. Introduced new functionality - TCAP Preview mode. If TCAP stack is configured as preview, it only consumes incoming TCAP messages. Further details here Issue 181
  6. Introduced new functionality - SCCP boardcast mode. SCCP can now broadcast outgoing messages to multiple GT's. Further details here Issue 182
  7. Flexibility to change the Calling SCCP Address of outgoing message. Further details here Issue 183
  8. TCAP, MAP and CAP Dialog's now exposes remote transaction id's. Details here Issue 191
  9. TCAP allows to set the Remote and Local SCCP Address after Dialog is created. Even change values of incoming Dialogs. Details here Issue 201 

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.BETA4&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

<repository>
                          <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>
                          <releases>
                            <enabled>true</enabled>
                            <updatePolicy>never</updatePolicy>
                          </releases>
                          <snapshots>
                            <enabled>true</enabled>
                            <updatePolicy>never</updatePolicy>
                          </snapshots>
                </repository>





Binary release includes
  • ASN 2.0.1.FINAL
  • SCTP 1.1.0.FINAL 
  • SS7 2.0.0.BETA4

  

Home page for each project 



GIT Master Browse

  

GIT Tag Browse



  
 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 jSS7 Team

Tuesday, June 12, 2012

Mobicents SMSC Gateway achieves 1000 SMS/Sec rate!

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