« Previous - Version 119/177 (diff) - Next » - Current version
Adrian Georgescu, 03/13/2010 08:56 pm

= Features =

<acronym title="WikiStart, Sip*, depth=2">TOC</acronym>

''SIP SIMPLE client SDK'' is a Software Development Kit for development of Real Time Applications based on SIP and related protocols for media transport like Presence, Audio and Instant Messaging (IM). Other media types can be easily added by using an extensible high-level API.

The software has undergone in the past years several interoperability tests at [http://www.sipit.net SIPIT] and today is of industry strength quality. The SIP stack is provided by [http://www.pjsip.org PJSIP].

The library has cross platform capabilities on Linux OS, Mac OSX (Leopard and Snow Leopard) and Microsoft Windows (roadmap). The library should work with minimal changes on any platform that supports C and Python development environments.

To see ''SIP SIMPLE client SDK'' features in action you can try [http://icanblink.com Blink].

General Features * Written in Python Programming Language * Non-blocking Asynchronous Engine * High Level Middleware * Configuration Framework * TLS Security for signaling (SIP) and media (MSRP, XCAP) * Multiple SIP Accounts support * Multiple Media Types per Session (e.g. Audio + IM) * Trace capability for all underlying protocols * Failover for DNS lookups, SIP and MSRP routing * Supports re-INVITE for adding and removing media * Automatically handling if IP Address changes * Audio Conference Bridge * Wav Player and Recorder * Acoustic Echo Cancelation * Answering Machine * Wide-band Internet codecs: Speex and G722 * PSTN compatible codecs: G711, iLBC, GSM

Supported media types:

  • Audio (RTP/sRTP)
  • Instant Messaging (MSRP)
  • File Transfer (MSRP)
  • Desktop Sharing (VNC over MSRP)

All media types can be combined together in the same SIP session.

The library uses a separated from the core lookup mechanism for the next hop routing. This important feature allows the library to be used for building SIP clients that operate in combination with any SIP provider (by employing RFC 3263 DNS lookups), in a server-less LAN operation (using Bonjour protocol) or integrated into a network overlay developed by a third party (e.g. P2PSIP overlay).

Normative References

=== SIP Signaling ===

=== Location Discovery ===

=== NAT Traversal ===

=== Voice over IP ===

=== Instant Messaging ===

=== Desktop Sharing ===

=== Conferencing ===

=== Presence ===

All server-side features have been built-in and tested with [http://opensips.org OpenSIPS] Presence Agent and [http://openxcap.org OpenXCAP] server.