debian.org RTC: announcing XMPP, SIP presence and more
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Developers,
The Debian Project now has an XMPP service available to all Debian
Developers. Your Debian.org email identity can be used as your XMPP
address.
The SIP service has also been upgraded and now supports presence. SIP
and XMPP presence, rosters and messaging are not currently integrated.
The Lumicall app has been improved to enable rapid setup[1] for
Debian.org SIP users.
This announcement concludes the maintenance window on the RTC
services. All services are now running on jessie (using packages from
jessie-backports).
XMPP and SIP enable a whole new world of real-time multimedia
communications possibilities: video/webcam, VoIP, chat messaging,
desktop sharing and distributed, federated communication are the most
common use cases.
Details about how to get started and get support are explained in the
User Guide[2] in the Debian wiki. As it is a wiki, you are completely
welcome to help it evolve.
Several of the people involved in the RTC team[3] are at the Cambridge
mini-DebConf[4] this weekend (7-8 November) and would be delighted to
discuss this project with other developers in person and understand
the first experiences people have using it.
The password for all these real time communication services can be set
via the https://db.debian.org web control panel. Please note that this
password needs to be different to any of your other existing debian.org
passwords. Please use a strong password and please keep it secure.
Some of the infrastructure, like the TURN server, is shared by clients
of both SIP and XMPP. Please configure your client to use the TURN
server for audio or video streaming to work most reliably through NAT.
A key feature of both our XMPP and SIP services is that they support
federated inter-connectivity with other domains. Please try it. The
FedRTC[5] service for Fedora developers is one example of another SIP
service that supports federation. For details of how it works and how
we establish trust between domains, please see RTC Quick Start
Guide[6]. Please reach out to other communities you are involved with
and help them consider enabling SIP and XMPP federation of their own
communities/domains: as Metcalfe's law[7] suggests, each extra person
or community that embraces open standards like SIP and XMPP has far
more than just an incremental impact on the value of these standards
and makes them more pervasive.
If you are keen to support and collaborate on the wider use of Free
RTC technology, please consider joining the Free RTC mailing list[8]
sponsored by FSF Europe. There will also be a dedicated debian-rtc
list[9] for discussion of these technologies within Debian and
derivatives.
This service has been made possible by the efforts of the DSA team in
the original SIP+WebRTC project and the more recent jessie upgrades
and XMPP project. Real-time communications systems have specific
expectations for network latency, connectivity, authentication schemes
and various other things. Therefore, it is a great endorsement of the
caliber of the team and the quality of the systems they have in place
that they have been able to host this largely within their existing
framework for Debian services. Feedback from the DSA team has also
been helpful in improving the upstream software and packaging to make
them convenient for system administrators everywhere.
Special thanks to Peter Palfrader and Luca Filipozzi from the DSA
team, Matthew Wild from the Prosody[10] project, Scott Godin from the
reSIProcate[11] project, Juliana Louback for her contributions to
JSCommunicator[12] during GSoC 2014, Iain Learmonth for helping get
the RTC team up and running, Enrico Tassi, Sergei Golovan and Victor
Seva for the Prosody and prosody-modules[13] packaging and also the
Debian backports[14] team, especially Alexander Wirt, helping us
ensure that rapidly evolving packages like those used in RTC are
available on a stable Debian system.
Regards,
Daniel
1.
http://danielpocock.com/lumicall-rapid-provisioning-opus-and-other-enhancements
2.
https://wiki.debian.org/UnifiedCommunications/DebianDevelopers/UserGuide
3. https://wiki.debian.org/Teams/RTC
4.
https://wiki.debian.org/DebianEvents/gb/2015/MiniDebConfCambridge#Talks_-_Saturday_and_Sunday
5. https://fedrtc.org
6. http://rtcquickstart.org
7. http://en.wikipedia.org/wiki/Metcalfe%27s_law
8. https://lists.fsfe.org/mailman/listinfo/free-rtc
9. https://lists.debian.org/debian-rtc/
10. http://prosody.im/
11. https://www.resiprocate.org
12. http://jscommunicator.org
13. https://packages.qa.debian.org/prosody-modules
14. http://backports.debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWPej6AAoJEOm1uwJp1aqDtqkP/1L4h1WyHdL1IMCbQt1xRhH+
f9BcxkudQFIz1zIcwXNyifbPBR80IpAcCkLZf6qAhew6zsmfXMsrEjdyIDkMoppZ
5SXBzQOzXVetvGZH5FIf0LMS+1pWDQ7O+fV21PrBnRI5TN2LutslWKVjBD+yKhsA
rhktVrUbagvN2LJ8YpoQxbmJvQGY4yTZ12LNbxh5Z2ack4VNGkoSrxv2BLc9Gguy
JqtrEP9WDsizVACaqURqZAeU393hIsFar1lStphzrtWkuWZzkSfU+Ywx5DKdoPFI
Qo4ltOiHXC6NGxlKUKSfqIp5gn9izb/yxFF5W4mnpNRpo3spmeo7vs3bN2hIf6mK
LM2+5eYiQstGnnrxivdhzFul4izcEqLF8YWB6xDmliBWrM7Qzpa2K3U5GOvQeoBI
srJ9k7I9SEBNh0yPKMQ9NvU6QZ4Mqjsm41Qqa5oLDpIUKf3ljHoBAFm02D1Ew/tu
CL2fFScLOgqZ8+r1GiMqoIb78zvP3BdqD6ccpDqAFpCGaXn8xEQExzWTXehP/ffU
Mdl/h7VMZnEwKjXVbDTSDVBoMgxUjTIjdh7gRlaKXOa5JzvPRXNnmBn2spEwsjZg
XCR/elHNaWIRWXLS5EOUdXydHb0ALYRfB17ZgrC/77Ersu7L5j3Rt95rGnLJQ7JY
zcwPSL7T0VE1TrwH9qcB
=kyUb
-----END PGP SIGNATURE-----
Reply to: