From Fedora Project Wiki
(SIP Witch offering domain and user VoIP services; secure scalable VoIP for the masses)
 
No edit summary
Line 11: Line 11:
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->


= Feature Name <!-- The name of your feature --> =
= SIP Witch Domain Telephony =


== 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. -->
 
GNU SIP Witch can be used to offer a means to create scalable and secure
VoIP services usable by everyone.  This is done by using SIP Witch as a
"domain" service for the SIP protocol, much like how Sendmail or Postfix
do so for SMTP.
 
Since SIP Witch only mitigates SIP and can media packet forward RTP for
SIP devices behind a NAT while establishing direct peer-to-peer communication between endpoints, it has little overhead, has no issues with patent encumbered codecs, and can operate directly with Social Key Verification systems such as ZRTP.  Since all users can use direct URI dialing to contact users at other locations there is no need for a central "service provider" or directory.


== 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:FASAcountName| Your Name]]
* Name: [[User:dyfet| David Sugar]]


<!-- 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: <your email address so we can contact you, invite you to meetings, etc.>
* email: dyfet@gnutelephony.org


== Current status ==
== Current status ==
* Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]  
* Targeted release: [[Releases/{{next}} | {{next}} ]]  
* Last updated: (DATE)
* Last updated: (DATE)
* Percentage of completion: XX%
* Percentage of completion: 1%


<!-- 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. -->

Revision as of 22:09, 10 October 2009

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



SIP Witch Domain Telephony

Summary

GNU SIP Witch can be used to offer a means to create scalable and secure VoIP services usable by everyone. This is done by using SIP Witch as a "domain" service for the SIP protocol, much like how Sendmail or Postfix do so for SMTP.

Since SIP Witch only mitigates SIP and can media packet forward RTP for SIP devices behind a NAT while establishing direct peer-to-peer communication between endpoints, it has little overhead, has no issues with patent encumbered codecs, and can operate directly with Social Key Verification systems such as ZRTP. Since all users can use direct URI dialing to contact users at other locations there is no need for a central "service provider" or directory.

Owner

  • email: dyfet@gnutelephony.org

Current status


Detailed Description

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion