This Friday, we welcome back Adrian Georgescu (AG Projects) for a session on SylkServer that should prove to be very interesting.
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.
SylkServer was born from the need to obtain ubiquitous connectivity between SIP and XMPP protocols without having to develop a multi-stack client. End-users typically use both types of client 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:
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.
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.