jdiameter

Here comes new release of Mobicents SS7 version 1.0.0 Beta8!We are glad to announce that M3UA implementation now leverages SCTP replacing TCP. Another milestone achieved is Mobicents SS7 stack works end-to-end with Dialogic boards. Native library to ... [More] invoke Dialogic board is included in the binary. The native code is compiled only for linux but you can compile source for any Operating System you are using. In addition the M3UA implements the Pending Queue for AS and algorithm to route the traffic to correct AS. The routing can be leveraged for load-balancing. As usual other fixes.-----------------------------------------------Release includes:-----------------------------------------------ASN libraryss7 protocols including the lowest layer MTP2/MTP3 to higher layer ISUP, SCCP, TCAP and MAPMobicents SCCP ServiceStandalone Mobicents Signaling GatewayShell ManagementFor details on stack creation and configuration please refer to docs available online http://www.mobicents.org/ss7/docs.htmlThe examples are not part of release. Please refer to JSLEE 2.1+ GA or subsequent MSS release.Note that this release is a BETA. Modules are under development and some parts MAY change.Where to download from? https://sourceforge.net/projects/mobicents/files/Mobicents%20Protocols%20Suite/1.0.0.B8/------------------Release Contents------------------* ASN v1.0.0.BETA3* SS7 v1.0.0.BETA8------------------SVN Trunk Checkout------------------http://mobicents.googlecode.com/svn/trunk/protocols/asnhttp://mobicents.googlecode.com/svn/trunk/protocols/ss7------------------SVN Trunk Browse------------------http://code.google.com/p/mobicents/source/browse/#svn%2Ftrunk%2Fprotocols%2Fss7http://code.google.com/p/mobicents/source/browse/#svn%2Ftrunk%2Fprotocols%2Fasn------------------SVN Tag Checkout------------------http://code.google.com/p/mobicents/source/browse/#svn%2Ftags%2Fprotocols%2Fasn%2Fasn-1.0.0.BETA3http://code.google.com/p/mobicents/source/browse/tags/protocols/ss7/#ss7%2Fmobicents-ss7-1.0.0.BETA8----------------How to Use it?----------------Please refer to online documentation.------------------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 SS7 Team [Less]

This year I will have the pleasure to copresent at JUDCon 2011 (May 2-3, 2011 in Boston) this talk Tuning and development with SIP Servlet on Mobicents/JBoss Communications Platform with Naoki Nishihara (which I'm eager to meet for the first time) ... [More] , who has been contributing to Mobicents since 2009 and is now part of the core team. He works at Oki Electric Industry Co., Ltd and is leading the Spring Sip Servlets Framework effort on the Mobicents community. I will stay around for JBoss World as well so if you're attending either event or will be in the area get in touch with us via Twitter, IRC (on Freenode channel #mobicents), or email (jean dot deruelle at gmail dot com) and I'll buy you a beer while you tell me about what you are doing on top of Mobicents and the new  features you want in the next version of Mobicents ;-) I hope to see you there Jean [Less]

Sometimes you need to deploy complex applications which touch different standards/platform, for instance a SLEE application which interacts with a Java EE component, and in such case it is important that each part of the system deploys (and ... [More] undeploys) in correct order. In JBoss AS5 and 6 it is possible to setup a custom deploy order by using some specific meta data, and I just create an article on how to do it, check it out. [Less]

Mobicents JAIN SLEE 2.4.0.CR1, codenamed SAKURA, the first LGPL release of the popular open source container, is now available for download. Check the announcement at http://goo.gl/lfE9S.

We are happy to announce release of Mobicents SS7 1.0.0.BETA7-----------------------------------------------Release includes:-----------------------------------------------ASN library ss7 protocols including the lowest layer MTP2/MTP3 to higher layer ... [More] ISUP, SCCP, TCAP and MAP Mobicents ServiceStandalone Mobicents Signaling GatewayShell ManagementThe most notable changes in this release are as follows: Standalone Mobicents Signaling Gateway (SG) is a signaling agent that receives/sends Switched Circuit Network (SCN) native signaling at the edge of the IP network.Small bug fixes and enchancements For details on stack creation and configuration please refer to docs available online http://www.mobicents.org/ss7/docs.htmlThe examples are not part of release. Please refer to JSLEE 2.1+ GA or subsequent MSS release.Note that this release is a BETA. Modules are under development and some parts MAY change.Let us know if you have any issues.Where to download from? https://sourceforge.net/projects/mobicents/files/Mobicents%20Protocols%20Suite/1.0.0.B7/------------------Release Contents------------------ * ASN v1.0.0.BETA3* SS7 v1.0.0.BETA7------------------SVN Trunk Checkout------------------http://mobicents.googlecode.com/svn/trunk/protocols/asnhttp://mobicents.googlecode.com/svn/trunk/protocols/ss7------------------SVN Trunk Browse------------------http://code.google.com/p/mobicents/source/browse/#svn%2Ftrunk%2Fprotocols%2Fss7http://code.google.com/p/mobicents/source/browse/#svn%2Ftrunk%2Fprotocols%2Fasn------------------SVN Tag Checkout------------------http://code.google.com/p/mobicents/source/browse/#svn%2Ftags%2Fprotocols%2Fasn%2Fasn-1.0.0.BETA3http://code.google.com/p/mobicents/source/browse/tags/protocols/ss7/#ss7%2Fmobicents-ss7-1.0.0.BETA7----------------How to Use it?---------------- Please refer to online documentation.------------------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 SS7 Team [Less]

Just a quick post about trying to bridge SIP video phones to RTSP video content providers. The goal is to enable SIP phones to display audio and video from regular RTSP providers such as YouTube. Even though SIP and RTSP have nothing to do with each ... [More] other, they carry SDP inside the messages, so it shouldn't be too hard to make them talk to each other.App overviewTo achieve the goal here we will need a SIP stack, RTSP stack and potentially an RTP stack. For SIP we'll use Mobicents Sip Servlets, for RTSP we can use JBoss Netty where the RTSP codecs were contributed by Mobicents Media Server team. RTP is really optional, because we should be able to wire the client and the RTSP server to talk directly with each-other RTP and there is no need the app server to understand what's going on.Basically a Sip Servlets application will initiate RTSP play sequence for each INVITE transaction and it will tear down the RTSP session when the client disconnects with a BYE.Simple enough. Let's see the code we need: protected void doInvite(SipServletRequest request) throws ServletException, IOException { RTSPStack rtsp = new RTSPStack(); // Try to take RTSP URI from the SIP request "To" header String rtspParameter = request.getTo().getURI().getParameter("rtsp"); if(rtspParameter == null) { rtspParameter = request.getRequestURI().getParameter("rtsp"); } if(rtspParameter != null) { rtsp.uri = "rtsp://" + rtspParameter; } .. SDP pre-processing.. rtsp.init(); // start the OPTIONS, DESCRIBE, SETUP, PLAY sequence .. SDP post-processing .. sipServletResponse = request.createResponse(SipServletResponse.SC_OK); sipServletResponse.setContent(rtsp.sdp, "application/sdp"); sipServletResponse.send(); }Negotiating the SDPThe SDP used by normal SIP phones is slightly different from the SDP used by most RTSP servers, but it is close enough. If your phones and RSTP servers know exactly the same codecs and payload types, the integration would be effort-less. For YouTube it requires a few pre- and post-processing steps on both sides:Extract the audio and video RTP socket port numbers from the client SDP advertised in the INVITETranslate the SDP the the RTSP server returns. The Wireshark screenshot on the right shows the captures RSTP SDP (note the track information and the way ports are shown in the RTSP response).One big challenge for all this to work is to have a phone that understands the standard RTSP codecs used by many RTSP providers. Most commonly those are AMR/G722.2 for audio and H263-2000 for video advertised with the following RTP map:a=rtpmap:99 AMR/8000/1a=rtpmap:98 H263-2000/90000Unfortunately, neither of these codecs is supported by any free SIP phone making it very difficult to build a one-for-all solution and test it without transcoding through a media server. Transcoding should be avoided, because it adds great computational complexity and difficulties with the project scalability.Matching the RTP/SDP payload typeEven without transcoding, apparently, very often you will have to deal with RTP payload number incompatibility. IANA assigns the standard RTP payload types over here. RTSP from YouTube uses the dynamic payload type range (96-127) where the numbers don't correspond strictly to particular codec and it is up to the phones to interpret it correctly with codec name string matching or some other method. This can also be be compensated for in the SIP server side. If you have phones that understand exactly the same payload types as the RTSP server, then great - no extra work is needed. If not, you will want to convert the types.To allow payload type modification we will need to bring the app server back in the RTP traffic to translate the RTP. We don't need a media server for this, just a very light-weight stack to pass-thru the RTP traffic. I added the RTPPacketForwarder class to the project which can be managed by the RTSPStack. Basically it binds sockets on both interfaces on the server and forwards the RTP packets unchanged except for the payload type which can optionally be overwritten to match the payload number required by the phone. Note that, when payload number modification is required the SDP must also be adapted in the Sip Servlets app to advise both the phone and the RTSP server to talk to the ports owned by the RTPPackerForwarder.NAT/firewall problemsSIP already has means for NAT traversal but for RTP it's a different story. There are two cases here - a firewall between the client and MSS or a firewall between MSS and the RTSP server. In the first case it would be responsibility of the SIP client to work around it. In the second case this means our server will have to implement at least a dumb RTP stack to pass packets from one side of the firewall to the other - a modification to the RTPPacketForwarder would enabled this. The stun4j module is added to the project to allow STUN lookup of the addresses if needed. That would once again require extra SDP modification to change the port numbers and addresses. The good news is that this is not required in many cases, because a good number of firewalls will do application layer gateway-ing or simply forward certain port ranges to the computer behind the firewall automatically or after asking the router to do it.CodeThe example is available in the Mobicents SVN, you will probably need to customize it for particular SIP phone and RTSP provider depending on the supported codecs and network topology. By default it is configured for YouTube.svn co http://mobicents.googlecode.com/svn/trunk/servers/sip-servlets/sip-servlets-examples/sip-rtsp-gateway [Less]

After several discussions and shared thoughts between the Mobicents team and the community, it has been decided to align the Mobicents license with the remaining JBoss projects, changing to the LGPL 2.1 Open Source license!Mobicents SIP Servlets was ... [More] already using such license, but now it is applied to ALL Mobicents Projects (Diameter, JAIN SLEE, Media Server, SS7, etc), effective March 1, 2011.We hope the community enjoys the change! [Less]

That's right, Red Hat decided to change the licenses of all Mobicents projects, including JAIN SLEE and SIP Presence, to LGPL. I believe this will allow the community to grow even more, and hopefully, increase 3rd party code contributions.

New versions of the Maven plugins for Mobicents JAIN SLEE can be found on JBoss Maven repository, which are compatible with Maven 2.x and 3.x:Maven DU Plugin 2.0.0.CR1 - a plugin which creates JAIN SLEE deployable unitsMaven Library Plugin 1.0.0.CR1 ... [More] - a plugin which creates JAIN SLEE Library jarsA couple of articles were added to the new Mobicents wiki at jboss.org, explaining how the plugins may be used.UPDATE 1: CR1 versions of both plugins had an issue with the plugins descriptor, both are fixed in new versions:Maven DU Plugin 2.0.0.CR2Maven Library Plugin 1.0.0.CR2UPDATE 2: A couple more issues were found with DU Plugin CR2, with respect to bundling services, a new fixed version is already available:Maven DU Plugin 2.0.0.CR3Also, all the RA, Enabler and Example projects of components bundled with the Mobicents JAIN SLEE release now use the newest plugin versions. A few examples:Diameter Base RA LibraryDiameter Sh Client RA Library (refers the one above)SIP UAS Example DU [Less]