[OpenSIPS-Users] Introducing OpenSIPS 2.3

[Nabeel]

Hi,

I run an ejabberd server for xmpp as well as OpenSIPS for SIP and was
wondering if these two could be integrated in any way in the future. These
servers run concurrently but they are completely independent of each other,
although for the same user base.

Nabeel

On 12 Jan 2017 4:48 p.m., "Bogdan-Andrei Iancu" <bogdan at opensips.org> wrote:

> A new year has arrived, so it is the time for a new OpenSIPS major
> release – for OpenSIPS version 2.3 .
>
> For this version, the main focus on development is the *“integration”*,
> the integration of OpenSIPS with various external entities. Why is
> integration so important to end up being the main tag of a major release?
> Well, everybody in the VoIP world is operating VoIP platforms/systems – and
> these are more than SIP Engines (as OpenSIPS is). Indeed, the SIP Engine
> is the core and most important part of the platform, but to build something
> usable and useful, you need additional components into your platform like
> CDR/billing engines, monitoring and tracing tools, data backends, non-SIP
> trunking or more specialized SIP engines. Shortly you need your SIP Engine (
> OpenSIPS, of course) to be able to easily integrate with all these
> components.
>
> OpenSIPS 2.3  brings some new and exciting integration capabilities, that
> will definitely boost the value of your SIP platform:
>
>    - extended Homer/SIPCapture <http://sipcapture.org/> integration to
>    allow capturing of non-SIP data (transport level data, Management Interface
>    commands, REST queries and more);
>    - SIP-I support both in terms of passing-through and in terms of
>    converting SIP-I to SIP and vice-versa ;
>    - CGRates <http://cgrates.org/> integration for powerful
>    rating/billing – everything in a simple and automatic way (via a dedicated
>    module);
>    - FreeSWITCH <https://freeswitch.org/> flavored Load-Balancing for a
>    more realistic and accurate traffic balancing over FreeSWITCH clusters (as
>    the load information is fetched in realtime from FreeSWITCH);
>    - the Event Engine
>    <https://en.wikipedia.org/wiki/Event-driven_programming> to provide
>    support for scenarios based on Subscribe/Notify model, where the script
>    execution may subscribe and resume later according to certain events (like
>    a dynamic implementation of the Push Notification mechanism);
>    - extended RabbitMQ <https://www.rabbitmq.com/> support for custom and
>    flexible data injection directly from OpenSIPS script;
>    - extended Asynchronous support for more complex async scenarios (like
>    launch with no wait);
>    - more end-device integration (special SIP extensions).
>
> The timeline for OpenSIPS 2.3 is:
>
>    - Beta Release – 13-17 March 2017
>    - Stable Release – 24-28 April 2017
>    - General Availability – 2nd of May 2017, during OpenSIPS Summit
>    <https://blog.opensips.org/2016/12/08/opensips-summit-2017-amsterdam/>
>
> To talk more about the features of this new release, a public audio
> conference <https://www.uberconference.com/opensips> will be available on 19th
> of January 2017, 4 pm GMT
> <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Introducing+OpenSIPS+2.3&iso=20170119T18&p1=49&ah=1>, thanks to
> the kind sponsorship of UberConference <https://www.uberconference.com/>.
> Anyone is welcome to join to find out more details or to ask questions about
> OpenSIPS 2.3 .
>
> This is a public and open conference, so no registration is needed, but if
> you want to announce your intention to participate, please let us know via the
> form on the blog post
> <https://blog.opensips.org/2017/01/12/introducing-opensips-2-3/>.
>
> Best regards,
>
> --
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170116/356076ce/attachment-0001.html>