Network Deployment (Distributed operating systems), v8.0 > Reference > Developer best practices
SIP industry standards compliance
The product implementation of SIP complies with industry standards for both a SIP container and SIP applications.
SIP container
This product complies with the following SIP standards:
This product also complies with the Internet Engineering Task Force (IETF) and Java Community Process (JCP) industry standards for SIP. The following table contains a list of the IETF and JCP standards.
WAS complies with these SIP standards.
This product complies with SIP standards as noted in the following table.
Standard Description JR116 SIP: SIP Servlet API JR289 SIP: SIP Servlet API v1.1 RFC 2543 SIP: SIP RFC 3261 SIP: SIP RFC 3262 Reliability of provisional responses in SIP RFC 3263 Locate SIP servers RFC 3265 SIP-specific event notification RFC 3311 The SIP UPDATE Method RFC 3325 Private Extensions to the SIP for asserted identity within trusted networks RFC 3326 The Reason Header field for the SIP RFC 3515 The SIP Refer method RFC 3581 The SIP Extension for Symmetric Response Routing RFC 3824 Use E.164 numbers with the SIP RFC 3891 The SIP Replace header RFC 3903 SIP Extension for event state publication RFC 3911 The SIP Join header RFC 4475 SIP torture test messages RFC 5057 Multiple dialog usages in SIP RFC 5626 Manage Client-Initiated Connections in SIP The SIP server can act as a proxy or registrar as specified in sections, 5, 6, and 7 of RFC 5626. RFC 5626 is an extension to RFC 3261. The SIP server has full support for RFC 3261. However, support for RFC 5626 comes with the following limitations:
- The SIP server can act as a User Agent, as defined in RFC 3261; however, it cannot act as a User Agent as defined in section 4 of RFC 5626.
- The SIP server does not support STUN keepalives, as specified in RFC 5626.
RFC 5658 Address Record-Route issues in SIP
SIP applications
This product complies with standards for SIP applications.
Compliance with standards for SIP applications.
This product complies with standards for SIP applications as noted in the following table.
Standard Description RFC 2848 The PINT Service Protocol: Extensions to SIP and Session Description Protocol (SDP) for IP access to telephone call services RFC 2976 The SIP INFO method RFC 3050 Common gateway interface for SIP RFC 3087 Control of service context using SIP request-URI RFC 3264 An offer and answer model with SDP RFC 3266 Support for IPv6 in SDP RFC 3312 Integration of resource management and SIP RFC 3313 Private SIP extensions for media authorization RFC 3319 Dynamic Host Configuration Protocol (DHCPv6) options for SIP servers RFC 3327 SIP Extension Header field for registering non-adjacent contacts RFC 3372 SIP for telephones (SIP-T): context and architectures RFC 3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to SIP mapping RFC 3428 SIP extension for instant messaging RFC 3455 Private Header (P-Header) extensions to the SIP for the 3rd-Generation Partnership Project (3GPP) RFC 3578 Map of Integrated Services Digital Network (ISDN) User Part (ISUP) overlap signaling to the SIP RFC 3603 Private SIP proxy-to-proxy extensions for supporting the PacketCable distributed call signaling architecture RFC 3608 SIP Extension Header field for service route discovery during registration RFC 3665 SIP basic call flow examples RFC 3666 SIP Public Switched Telephone Network (PSTN) call flows RFC 3680 A SIP event package for registrations RFC 3725 Best current practices for third-party call control (3pcc) in the SIP RFC 3840 Indicating user agent capabilities in the SIP RFC 3842 A message summary and message waiting indication event package for the SIP RFC 3856 A presence event package for the SIP RFC 3857 A watcher information event template package for the SIP RFC 3959 The early session disposition type for the SIP RFC 3960 Early media and ringing tone generation in the SIP RFC 3976 Interworking SIP and intelligent network (IN) applications RFC 4032 Update to the SIP preconditions framework RFC 4092 Usage of the SDP Alternative Network Address Types (ANAT) semantics in the SIP RFC 4117 Transcoding services invocation in the SIP using third-party call control (3pcc) RFC 4235 An invite-initiated dialog event package for the SIP RFC 4240 Basic network media services with SIP RFC 4353 A framework for conferencing with the SIP RFC 4354 A SIP event package and data format for various settings in support for the push-to-talk over cellular (PoC) service RFC 4411 Extend the SIP Reason Header for preemption events RFC 4457 The SIP P-user-database Private-Header (P-Header) RFC 4458 SIP URIs for applications such as voicemail and interactive voice response (IVR) RFC 4483 A mechanism for content indirection in SIP messages RFC 4497 Interworking between the SIP and QSIG RFC 4508 Conveying feature tags with the SIP REFER method
Browse all SIP topics
Set up SIP application composition
Develop SIP applications