Description » History » Revision 58
Revision 57 (Adrian Georgescu, 09/01/2013 01:02 PM) → Revision 58/60 (Adrian Georgescu, 03/30/2014 01:53 AM)
This wiki page is meant for providing technical documentation and access to the version control source code repository.
SylkServer official web site is http://sylkserver.com
h2. Description
SylkServer allows creation and delivery of rich multimedia applications accessed by SIP User Agents and XMPP endpoints. The server supports SIP and XMPP signaling, RTP and MSRP media planes, has built in capabilities for creating ad-hoc multimedia conferences with HD Audio, IM and File Transfer and can be easily extended with other applications by using Python language.
h2. Background
SylkServer was born from the need of realizing ubiquitous connectivity between SIP and XMPP protocols without having to develop a multi-stack client. End-users typically use both type of clients for their best features. SIP and XMPP protocols have in common the same addressing scheme user@domain email style addresses. Using SylkServer, the best client of either protocol can be used to reach clients using the other protocol without having to configure anything in the network or clients. We call this function SIP/XMPP gateway, which is standardized by the XMPP foundation.
A complete description of the SIP/XMPP gateway standards and SylkServer design and implementation can be found here:
http://sylkserver.ag-projects.com/projects/sylkserver/wiki/DesignXMPP
Going beyond simple translation of media, SylkServer is able to create multiparty conferences with clients from both worlds. Using SylkServer ad-hoc multiparty conferencing capabilities, both SIP and XMPP client can connect to the same address and exchange the participants list, have text chat and wide-band audio. Again, there is no need to configure anything to realize such complex task.
h2. Deployment
SylkServer is an application server that behaves like a SIP end-point and therefore must be deployed behind a SIP Proxy/Registrar server for registration, proxy, presence agent, accounting and authorization functions. The SIP Proxy must be configured to route certain flows to SylkServer and handle incoming requests from it as necessary.
h2. Support forum
Go to "SIP beyond VoIP":http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip mailing list
!>{width: 500px}sylk-server-diagram.png!
h2. Features
For the complete feature list look on the [[features]] page
h3. SIP Signaling
* TLS, TCP and UDP transports
* INVITE and REFER methods
* SUBSCRIBE/NOTIFY
* DNS and Bonjour discovery
h3. Voice over IP
* Wideband (Opus, G722, Speex)
* Narrowband (G711, GSM, iLBC)
* Encryption (sRTP)
h3. Instant Messaging
* Chat Sessions (MSRP)
* Composing Indication
* Delivery reports
h3. Conferencing
* Wideband audio
* IM and File Transfers
* Screen-sharing
* Participants Info
h3. XMPP Gateway
* Presence and IM
* Multi-party conferencing (MUC)
* Jingle wide-band audio (RTP)
"XMPP gateway design":http://sylkserver.ag-projects.com/projects/sylkserver/wiki/DesginXMPP