NewNet’s SIP

Session Initiation Protocol (SIP) is signaling protocol that is used for controlling multimedia communication including Voice and Video calls in IP networks. SIP helps establish, modify and terminate multimedia sessions or calls.

SIP stack is used in the following applications:

  • VOIP calls
  • Video Conferencing
  • Instant messaging
  • Presence information management
  • VOIP Gateways
  • IMS network nodes
  • Application Servers
  • IP Phones

NewNet Session Initiation Protocol builds on top of NewNet’s industry proven Distributed7 platform providing a highly optimized, robust and feature rich stack implementation. It is designed to make the additions of new extensions very quick. It provides high level User APIs to expedite the development of user applications. It is easily portable to any operating system but supports the most common OSs Solaris and Linux. It is designed to be highly scalable and builds on top of the D7 high availability framework. Both ipv4 and ipv6 are supported using either SCTP or TCP. Transport Layer Security (TLS) protocol is supported for improved security.

Base standard is IETF RFC3261. It is the key IP signaling protocol for 3GPP and IMS architecture.

Key RFCs supported:

  • RFC 1321: MD5: Message Digest Algorithm
  • RFC 2327: Session Description Protocol
  • RFC 2451: The ESP CBC Mode Cipher Algorithm
  • RFC 2617: HTTP Authentication
  • RFC 2778: Model for Presence and Instant Messaging
  • RFC 2779: Instant Messaging/Presence Protocol Requirements
  • RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
  • RFC 2806: URLs for Telephone Calls
  • RFC 2833: RTP Payload for DTMF & Tones
  • RFC 2915: NAPTR: Naming Authority Pointer
  • RFC 2976: SIP INFO Method
  • RFC 3204: MIME Objects for ISUP and QSIG
  • RFC 3261: SIP: Session Initiation Protocol
  • RFC 3262: SIP Reliability (PRACK)
  • RFC 3263: SIP: Locating SIP Servers
  • RFC 3264: SDP Offer/Answer
  • RFC 3265: SIP Specific Event Notification
  • RFC 3311: The SIP UPDATE method
  • RFC 3323: A Private mechanism for the Session Initiation Protocol
  • RFC 3324: Short Term Requirements for Network Asserted Identity
  • RFC 3325: Private Extensions to the SIP for Asserted Identity within Trusted Networks
  • RFC 3329: Security Mechanism for SIP
  • RFC 3428: SIP Extension for IM
  • RFC 3489: STUN: Simple Traversal UDP - NATs
  • RFC 3581: Symmetric Response Routing Ext’n
  • RFC 3665: SIP Basic Call Flow Examples
  • RFC 3711: SRTP Secure RTP
  • RFC 3856: A Presence Event Package for the SIP
  • RFC 3859: Common Profile for Presence (CPP)
  • RFC 3860: Common Profile for Instant Messaging (CPIM
  • RFC 3863: Presence Information data format (PIDF)
  • RFC 3891: SIP ‘ Replaces’ Header
  • RFC 3892: SIP Referred-By Mechanism
  • RFC 3903: SIMPLE SIP for IM and Presence
  • RFC 3966: The Tel URI for Telephone Numbers"
  • RFC 4028: Session Timers in SIP
  • RFC 4346: TLS Transport Layer Security
  • RFC 4475: SIP Torture Test Messages
  • RFC 4566: SDP Session Descrip’n Protocol/IPv6
  • SIMPLE – SIP for Instant Messaging and Presence Leveraging Extensions