Features/FederatedVoIP

From FedoraProject

< Features
Revision as of 16:45, 9 May 2013 by Pocock (Talk | contribs)

Jump to: navigation, search

Contents

Federated VoIP

Summary

Make it easier for the deployment of federated SIP and XMPP (Jabber) networks, functioning much like federated SMTP email.

Owner

  • Email: daniel@pocock.com.au

Current status

  • Targeted release: Fedora 19
  • Last updated: 2013-01-28
  • Percentage of completion: 100%


Detailed Description

Many VoIP installations still operate on a standalone basis, often with a single SIP proxy or soft PBX trunking all calls to an external provider. Ideally, VoIP should be fully federated, with no central provider other than perhaps the DNS. This feature aims to bring that vision closer to reality, by making it easier to start a SIP proxy in federated mode, using TLS by default for security/identity of external peers and benefiting from ENUM for legacy phone numbers.

Benefit to Fedora

Fedora users can call each other and users of other platforms like Debian and Ubuntu, just using a user@domain address with the same convenience as email.

Scope

Packaging reSIProcate, which introduces the following:

  • repro SIP proxy (with federated TLS support)
  • reTurnServer, a TURN server for easy NAT traversal (supports both SIP and XMPP/Jabber users)

and maybe also dlz-ldap-enum, a bind9 module for ENUM lookups backed by an existing LDAP infrastructure.

How To Test

Using the following SIP user agents:

  • Empathy (with the telepathy-rakia module), the default softphone in the Gnome desktop
  • Jitsi, the most popular and most advanced cross-platform
  • Lumicall, the secure mobile SIP client for Android (based on Sipdroid)

and testing against various open SIP networks (please add some more):

User Experience

Sysadmins can quickly install a SIP proxy and TURN server and get federated using the instructions in the Federated VoIP quick start howto guide

Dependencies

These are new packages that won't impact existing packages. Some other new packages in the future may choose to use reSIProcate as their SIP stack, given it is the most advanced and liberally licensed SIP stack implementation.

Contingency Plan

These are new packages and have no impact on unrelated packages or the system as a whole if they are not ready on time.

Documentation

Release Notes

  • Better support for truly federated VoIP, with the reSIProcate (repro) SIP proxy and reTurnServer, an ICE/STUN/TURN server for both SIP and XMPP (Jabber) networks

Comments and Discussion