Differences between revisions 7 and 33 (spanning 26 versions)
Revision 7 as of 2014-01-17 17:22:50
Size: 5166
Editor: DanielPocock
Comment:
Revision 33 as of 2021-06-25 01:50:42
Size: 3875
Editor: PaulWise
Comment: cleanup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
   * Please also see the [[UnifiedCommunications/DebianDevelopers/FAQ|Frequently Asked Questions]]
Line 4: Line 5:
  * SIP Proxy
  * TURN server
 * The following services are NOT available yet but are being planned or under consideration
  * --(SIP ([[http://tools.ietf.org/html/rfc3261|Session Initiation Protocol]]) Proxy, allowing to pass VoIP phone calls.)-- ([[https://alioth-lists.debian.net/pipermail/debian-rtc-team/2020-May/000194.html|decommissioned]])
  * --(TURN ([[http://tools.ietf.org/html/rfc5766|Traversal Using Relays around NAT]]) server.)-- ([[https://alioth-lists.debian.net/pipermail/debian-rtc-team/2020-May/000194.html|decommissioned]])
Line 8: Line 8:
  * Audio and/or video conference software
   * [[http://packages.debian.org/reconserver|see the reConServer package]]
   * [[https://jitsi.org/videobridge|Jitsi video bridge]] is also cool
 * You must create a real-time communications (RTC) password in [[http
://db.debian.org|the LDAP system]]
  * Do not use the same password that you use for any other Debian service. For example, you may want to cache the RTC password in a mobile device where there is a risk that it will be compromised, exposing the password.
 * The following services are NOT available yet but are being planned or under consideration
  * BOSH Support, to connect to the XMPP server over HTTPS
 * You must create a real-time communications (RTC) password in
[[https://db.debian.org|the LDAP system]]: login to update your settings, then fill the RTC password field.
  * Do not use the same password that you use for any other service. For example, you may want to cache the RTC password in a mobile device where there is a risk that it will be compromised, exposing the password.
Line 14: Line 13:
 * Your ''debian.org'' email address is also your SIP address
  * E.g. ''pocock@debian.org''
 * Your SIP software may try to use the user-part of the SIP address for authentication. It will not work.
  * In your SIP settings, look for an ''authentication username'' or ''auth user'' field. It is often blank by default.
  * Put your full SIP address, e.g. ''pocock@debian.org'' in this field
 * The same credentials are used for TURN
 * If you are lucky, your client software uses DNS NAPTR and SRV lookups to find the TURN and SIP servers, if not, you can hardcode the following values into your configuration:
  * SIP server: please use a client that finds it using SRV lookups
   * if really necessary, use the value ''vogler.debian.org'' and TLS, port 5061
  * TURN server: ''turn.debian.org'' (UDP port 3478)
  * SIP over WebSocket: ''sip-ws.debian.org'' (HTTP port 443)
 * Your ''debian.org'' email address is also your XMPP address
  * E.g. ''username@debian.org''
 
Line 29: Line 19:
 * For general discussion about how to best use SIP as a tool to achieve the wider objectives of the Debian Project, please use ''debian-devel''
 * For specific faults with the service, please contact the [[Teams/DSA|Debian System Administration (DSA)]] team

== NAT traversal ==

 * NAT and firewalls have traditionally been a problem for free RTC software
 * For SIP itself, we only use TLS
  * This is a stream connection that is more likely to get through NAT than UDP
  * It can also potentially be tunnelled through proxies using the HTTP CONNECT method (port 443)
  * Some routers try to mangle SIP packets to help them through NAT, in practice this sometimes makes the problem worse
  * By using TLS, we ensure that no intermediate device will tamper with the packets, we aim to use industry standard ICE and TURN
 * The modern approach to this problem is the use of Internet Connectivity Establishment (ICE) and, as a last resort, relaying traffic through a TURN server
 * Not all SIP clients support TURN
  * Jitsi only supports TURN with Jabber, the SIP-TURN support is coming
  * Empathy only supports TURN through Google's proprietary TURN servers, but the TURN code could use any TURN server if configuration options were available. There is a bug report for this.
  * Only one end of the connection needs a TURN server for it to work though, as long as both support ICE.
 * The [[https://rtc.debian.org|rtc.debian.org]] WebRTC service is based on [[http://jscommunicator.org|JSCommunicator]]. It supports both ICE and TURN and is pre-configured for Debian's TURN servers. Although the UI is very basic, there is a high probability that it can get through NAT in situations where the other SIP clients currently struggle.

== WebRTC status ==

Note:

 * WebRTC users can only interact with other WebRTC users
 * Jitsi and Lumicall users can interact with each other but not with WebRTC users (yet)
 * For general discussion about how to best use these technologies as a tool to achieve the wider objectives of the Debian Project, please use ''debian-devel''
 * For specific faults with the service, please contact the [[Teams/RTC|Debian Real Time Communications]] team
Line 57: Line 24:
=== Conversations.im on Android ===

See this [[UnifiedCommunications/DebianDevelopers/UserGuide/Android|step by step guide]].

=== Linphone configuration ===

 * [[DebianPackage:linphone|Linphone]] seems to work well and can receive calls from [[https://lumicall.org/|Lumicall]] users
 * See the [[UnifiedCommunications/DebianDevelopers/UserGuide/Linphone|Linphone screenshots]] for full details
Line 59: Line 35:
 * [[DebianPackage:jitsi|Jitsi]] is one of the most extensive open source communications tools, but is no longer available in Debian
Line 60: Line 37:

=== Empathy ===

 * Empathy is the default communications client in the GNOME desktop
 * See the [[UnifiedCommunications/DebianDevelopers/Empathy|Empathy screenshots]] for full details
Line 63: Line 45:
[[http://www.lumicall.org|Lumicall]] is an open source mobile SIP client for Android. It only supports audio and does not support video or messaging yet. It has good support for SDES and ZRTP encryption, uses SIP over TLS and supports ICE and TURN for NAT busting.  * [[https://lumicall.org/|Lumicall]] is an open source mobile SIP client for Android.
 * See the [[UnifiedCommunications/DebianDevelopers/UserGuide/Lumicall|Lumicall configuration page]] for full details
Line 65: Line 48:
 * Settings
  * SIP Identities (Add...)
   * SIP address/URI: username@debian.org
   * Profile enabled: Tick
   * Security mode: ZRTP
   * Gateway to PSTN: Remove tick
   * Intl. dialing prefix: 00
   * Authorization username: username@debian.org
   * Password: (your RTC password)
   * Registration: Tick
   * Use outbound proxy: Tick
   * Use STUN/TURN protocols: Tick
   * STUN server name: vogler.debian.org
   * STUN server port: 3478
   * STUN server protocol: udp
=== CSipSimple ===

 * [[WikiPedia:CSipSimple|CSipSimple]] was a project that integrated well with Android phones, and was recommended by [[https://guardianproject.info/apps/|The Guardian Project]].
 * See the [[/CSipSimple|CSipSimple configuration page]] for full details
Line 83: Line 55:
Just take it from [[https://github.com/opentelecoms-org/jscommunicator|upstream github]], use [[http://packages.debian.org/jscommunicator-web-phone|the web-phone package]] and symlink the files to your own web directory or clone an existing site:  * [[https://jscommunicator.org/|JSCommunicator]] is a browser-based WebRTC softphone using HTML5/JavaScript. It requires a modern browser.
 * See the [[UnifiedCommunications/DebianDevelopers/UserGuide/JSCommunicator|JSCommunicator configuration page]] for full details about how to put it in your own blog or web site
Line 85: Line 58:
{{{
mkdir /var/www/jscommunicator
cd /var/www/jscommunicator
wget -nH -r https://rtc.debian.org
vi config.js
}}}
=== Asterisk ===

 * [[DebianPackage:asterisk]] is a full PBX system.
 * See the [[UnifiedCommunications/DebianDevelopers/UserGuide/Asterisk|Asterisk configuration page]] for full details

=== Ekiga ===

According to [[WikiPedia:Comparison_of_VoIP_software|Wikipedia]], ekiga does not currently support TLS connections.

Key details

  • Please also see the Frequently Asked Questions

  • Debian Developers have access to the following services

  • The following services are NOT available yet but are being planned or under consideration
    • BOSH Support, to connect to the XMPP server over HTTPS
  • You must create a real-time communications (RTC) password in the LDAP system: login to update your settings, then fill the RTC password field.

    • Do not use the same password that you use for any other service. For example, you may want to cache the RTC password in a mobile device where there is a risk that it will be compromised, exposing the password.
    • Wait 30 minutes for the password to become active.
  • Your debian.org email address is also your XMPP address

Contact and support

  • For general questions about individual softphones, please contact the maintainers or upstream mailing lists
  • For general discussion about how to best use these technologies as a tool to achieve the wider objectives of the Debian Project, please use debian-devel

  • For specific faults with the service, please contact the Debian Real Time Communications team

Instructions for various client programs

Conversations.im on Android

See this step by step guide.

Linphone configuration

Jitsi configuration

  • Jitsi is one of the most extensive open source communications tools, but is no longer available in Debian

  • See the Jitsi screenshots for full details

Empathy

  • Empathy is the default communications client in the GNOME desktop
  • See the Empathy screenshots for full details

Lumicall

CSipSimple

JSCommunicator

Asterisk

Ekiga

According to Wikipedia, ekiga does not currently support TLS connections.