From Fedora Project Wiki
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 will be used to operate SIP in a manner analogous to what sendmail does for SMTP to allow anyone to connect to both local SIP user agents and devices managed as local extensions, and remote users through SIP URI's over the public Internet. Because SIP Witch does no media processing and supports direct peer to peer interconnect, true secure protocols such as ZRTP may be used in conjunction to offer Internet scalable secure VoIP & video services without the need for a central directory or service provider (such as Skype requires).

Owner

  • email: dyfet@gnutelephony.org

Current status

  • Targeted release: Fedora13
  • Last updated: 2009-10-10
  • Percentage of completion: 1%


Detailed Description

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.

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion