Community.Event-Amoocon2010 History

Hide minor edits - Show changes to output

September 15, 2014, at 01:53 PM by -
Added lines 46-48:

[[ | Download presentation in PDF format ]].
September 15, 2014, at 11:45 AM by -
Changed lines 5-9 from:
'''OpenSIPS''' project will present at Amoocon on June 4th - 6th, 2009 ( ).

There are 3 different topics (OpenSIPS related) presented at the conference by several people around the project:

Changed lines 18-19 from:
[[ | Download presentation in PDF format ]].
Deleted lines 32-34:

Deleted lines 46-47:
May 14, 2013, at 02:12 PM by -
Changed line 1 from:
!! Community -> Event Amoocon 2010
!!!!! Community -> [[Community.Events|Events]] -> Event Amoocon 2010
April 23, 2013, at 08:09 PM by -
Added lines 1-55:
!! Community -> Event Amoocon 2010
(:toc-float Table of Content:)

'''OpenSIPS''' project will present at Amoocon on June 4th - 6th, 2009 ( ).

There are 3 different topics (OpenSIPS related) presented at the conference by several people around the project:

!!! OpenSIPS 2.0 - a programmable framework for SIP (by Bogdan-Andrei Iancu)

The new design of OpenSIPS (2.0 design) brings a radical new approach on how a SIP server is architectured, on how you can program a SIP service, on how you can scale SIP networks.

Two most important concepts are addressed by OpenSIPS 2.0:

*'''horizontal scalability''' - having a complete separation between core (SIP engine) and the routing logic (service implementation), OpenSIPS 2.0 will natively allow clustering of multiple independent cores into a single distributed service logic.
*'''service programming''' - the routing logic (service implementation) is a separate entity that can be implemented in any high-level language (python, perl, java), enabling an easy service creation (no custom configuration) and natural integration (as application) into larger service platform.

OpenSIPS 2.0 is about efficiency, about simplicity and about integration.


!!! Integrated SIP and XMPP Services with OpenSIPS (By Anca Vamanu)

With the latest release of OpenSIPS it is possible to offer SIP and XMPP services for the same domain with complete interconnection. In a few words you can have:

* '''unique domain''' – both services: SIP and XMPP: the possibility to install a platform with a SIP server and a XMPP server sharing the same domain name and with total interconnection between the two
* an end user can create a '''single account''' and use it to log in to his SIP or XMPP client
* '''transparent interconnection''' and translation between the two protocols, an XMPP user can reach a SIP user and the other way around
* '''complete gateway''': IM, Presence and Voice, coming soon ( both the standard and libjingle version, used by Google talk)
* user can be '''reachable from both SIP and XMPP'''; a fail-over logic can be implemented so that if coming from SIP first the target user is searched in SIP and if not found, the request is translated and sent in XMPP (the same for when coming from XMPP).


!!! ICE: the ultimate way of beating NAT in SIP (by Saúl Ibarra Corretgé)

We all know NAT is one of the worst issues SIP is facing.

Interactive Connection Establishment (ICE) was born in order to fix this and help devices talk to each other traversing every type of NAT our there.

However ICE is a complex protocol and doesn’t work with the traditional NAT traversal scenarios.

The talk will go through the problem of NAT in SIP and deeply explain ICE protocol and what changes were done in OpenSIPS and MediaProxy in order to make it work.

After there will be a short live demo showing every component involved and demonstrating how and why ICE works.

Page last modified on September 15, 2014, at 01:53 PM