From Fedora Project Wiki
< Features
mNo edit summary |
No edit summary |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
Make it easier for the deployment of federated SIP and XMPP (Jabber) networks, | Make it easier for the deployment of federated SIP and XMPP (Jabber) networks, functioning much like federated SMTP email. | ||
functioning much like federated SMTP email. | |||
== Owner == | == Owner == | ||
<!--This should link to your home wiki page so we know who you are--> | <!--This should link to your home wiki page so we know who you are--> | ||
* Name: [[User:Pocock|Daniel Pocock]] | * Name: [[User:Pocock|Daniel Pocock]] | ||
* Home page: http://danielpocock.com | |||
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved--> | <!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved--> | ||
* Email: daniel@pocock.com.au | * Email: daniel@pocock.com.au | ||
| Line 17: | Line 16: | ||
* Targeted release: [[Releases/19 | Fedora 19 ]] | * Targeted release: [[Releases/19 | Fedora 19 ]] | ||
* Last updated: 2013-01-28 | * Last updated: 2013-01-28 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
| Line 34: | Line 34: | ||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
Packaging reSIProcate, which introduces the following: | [https://bugzilla.redhat.com/show_bug.cgi?id=892625 Packaging reSIProcate], which introduces the following: | ||
* repro SIP proxy (with federated TLS support) | * repro SIP proxy (with federated TLS support) | ||
* reTurnServer, a TURN server for easy NAT traversal (supports both SIP and XMPP/Jabber users) | * reTurnServer, a TURN server for easy NAT traversal (supports both SIP and XMPP/Jabber users) | ||
and maybe also [http://www.opentelecoms.org/dlz-ldap-enum dlz-ldap-enum], a bind9 module for ENUM lookups backed by an existing LDAP infrastructure. | |||
== How To Test == | == How To Test == | ||
| Line 62: | Line 63: | ||
== User Experience == | == User Experience == | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
Sysadmins can quickly install a SIP proxy and TURN server and get federated using the instructions in the [http://www. | Sysadmins can quickly install a SIP proxy and TURN server and get federated using the instructions in the [http://www.rtcquickstart.org/ Federated VoIP quick start howto] guide | ||
== Dependencies == | == Dependencies == | ||
| Line 75: | Line 76: | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
* http://www.rtcquickstart.org | |||
* http://www.resiprocate.org | * http://www.resiprocate.org | ||
* http://www.opentelecoms.org | * http://www.opentelecoms.org | ||
| Line 89: | Line 91: | ||
* See [[Talk:Features/FederatedVoIP]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | * See [[Talk:Features/FederatedVoIP]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||
[[Category: | [[Category:FeatureAcceptedF19]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 09:45, 29 May 2013
Federated VoIP
Summary
Make it easier for the deployment of federated SIP and XMPP (Jabber) networks, functioning much like federated SMTP email.
Owner
- Name: Daniel Pocock
- Home page: http://danielpocock.com
- 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):
- Calling to/from users of Lumicall on Android using sip:number@sip5060.net addresses
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
- http://www.rtcquickstart.org
- http://www.resiprocate.org
- http://www.opentelecoms.org
- http://packages.debian.org/sid/repro (also in Debian and Ubuntu)
- http://en.wikipedia.org/wiki/Federated_VoIP
- http://wiki.debian.org/UnifiedCommunications (a similar initiative is ongoing within Debian)
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