IPneo :: Reach . Share . Enrich

VoIP SDK

VoIP SDK:

IPneo provides a highly optimized SIP based VoIP SDK that combines high performance, modularity, minimum footprint as well as cost-effectiveness. Providing access to a full fledged set of APIs, IPneo’s VoIP SDK is the key building block for various VoIP solutions. The VoIP SDK is also ideal for single VoIP chip and can be seamlessly integrated within any audio embedded system.

The set of optimized SIP and RTP stacks that are fully compliant to the IETF specifications, and the support of different codecs like AMR-NB, AMR-WB, G.711, G.729, iLBC among others, grant IPneo’s VoIP SDK a high level of reliability and interoperability within any VoIP-based ecosystem.

IPneo’s VoIP SDK is portable on a number of operating systems such as Android, iOS, Symbian, Linux, MAC and more.

Features:

  • Fully compliant to IETF RFCs
  • Basic SIP messages and SIP extensions
  • Full SDP support
  • TCP and UDP support
  • IPv6 support
  • NAT Traversal support
  • DNS support
  • Event packages subscriptions
  • Well-defined API's for full access to the stack functionality
  • Extensively tested and interoperable with third party protocol stacks
  • OS independent ANSI C source code granting seamless portability
  • Fits in both VoIP and IMS solutions

Supported RFCs:

Basic SIP
  • RFC 3261 (June 2002): SIP: Session Initiation Protocol
  • RFC 3262 (June 2002): Reliability of provisional responses in Session Initiation Protocol (SIP)
  • RFC 3263 (June 2002): Session Initiation Protocol (SIP): Locating SIP Servers
  • RFC 3311 (September 2002): The Session Initiation Protocol (SIP) UPDATE method
  • RFC 3515 (April 2003): The Session Initiation Protocol (SIP) REFER method
  • RFC 4028  ( April 2005): Session Timers in the Session Initiation Protocol (SIP)
  • RFC 3892 (September 2004): The Session Initiation Protocol (SIP) Referred-By Mechanism
  • RFC 3891 (September 2004): The Session Initiation Protocol (SIP) "Replaces" Header
  • RFC 3840 (August 2004): Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
  • RFC 3986: URI Generic Syntax

Authentication
  • RFC 3329 (January 2003): Security Mechanism Agreement for the Session Initiation Protocol (SIP)
  • RFC 2617:HTTP Authentication: Basic and Digest Access Authentication
  • RFC 3310: Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)

Extensions
  • RFC 3313 (January 2003): Private Session Initiation Protocol (SIP) Extensions for Media Authorization
  • RFC 3323 (November 2002): A Privacy Mechanism for the Session Initiation Protocol (SIP)
  • RFC 3325 (November 2002):Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks
  • RFC 3327 (December 2002): Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts
  • RFC 3608 (October 2003): Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration
  • RFC 3428 (December 2002): Session Initiation Protocol (SIP) Extension for Instant Messaging
  • RFC 3455 (January 2003): Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)
  • RFC 3581 (August 2003): An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
  • RFC 3841 (August 2004): Caller Preferences for the Session Initiation Protocol (SIP)
  • RFC 3420 (November 2002): Internet Media Type message/sipfrag

Event Packages
  • RFC 3265 (June 2002): Session Initiation Protocol (SIP) Specific Event Notification
  • RFC 3680 (March 2004): A Session Initiation Protocol (SIP) Event Package for Registrations
  • RFC 3903 (October 2004): An Event State Publication Extension to the Session Initiation Protocol (SIP)
  • RFC 4575 - SIP Event Package for Conference State
  • RFC 3842: A Message Summary and Message Waiting Indication Event Package for  the Session Initiation Protocol (SIP)
  • RFC 3856: A Presence Event Package for the Session Initiation Protocol
  • RFC 3857 : A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)

Media Handling
  • RFC 2327: SDP: Session Description Protocol
  • RFC 3264 (June 2002): An Offer/Answer Model with Session Description Protocol (SDP)
  • RFC 3312 (October 2002): Integration of resource management and Session Initiation Protocol (SIP)
  • RFC 3388 (December 2002): Grouping of Media Lines in Session Description Protocol
  • RFC 3556 (July 2003): Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth
  • RFC 4566 SDP: Session Description Protocol

Signaling Compression
  • RFC 3320 (March 2002): Signaling Compression (SigComp)
  • RFC 3321: Signaling Compression (SigComp) - Extended Operations
  • RFC 3485 (February 2003): The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) static dictionary for Signaling Compression (SigComp)
  • RFC 3486 (February 2003): Compressing the Session Initiation Protocol (SIP)
  • RFC 4077: A Negative Acknowledgement Mechanism for Signaling Compression

Networking
  • RFC 3489 STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators
  • RFC 2916 E.164 number and DNS


.