RFC support

Last Updated : Dec 16, 2020 |

The following table lists how Avaya SBC complies with supported Request for Comment (RFC) specifications.

RFC

Support

RFC 2046 (MIME, obsoletes 1590)

Complies

RFC 2246 (TLS v1)

Complies

RFC 2833 (DTMF in RTP payload)

Complies

RFC 2976 (SIP INFO method)

Complies

RFC 3261 (SIP, obsoletes 2543)

Complies

RFC 3262 (SIP provisional responses)

Complies

RFC 3263 (SIP resource location)

Complies

RFC 3264 (SDP offer / answer model)

Complies

RFC 3265 (SIP event notification)

Complies

RFC 3311 (SIP UPDATE method)

Complies

RFC 3323 (SIP privacy)

Partially complies – no service disruption

RFC 3325 (SIP privacy extensions)

Partially complies – no service disruption

RFC 3327 (SIP header extension)

Does not comply

RFC 3515 (SIP REFER method)

Complies

RFC 3581 (SIP symmetric response)

Complies

RFC 3605 (SDP with RTCP)

Complies

RFC 3665 (SIP Basic Call Flow)

Complies

RFC 3680 (SIP registration events)

Complies – relayed

RFC 3711 (SRTP)

Complies

RFC 3842 (SIP message waiting)

Complies – relayed

RFC 3856 (SIP presence)

Complies – relayed

RFC 3857 (SIP watcher mechanism)

Complies – relayed

RFC 3891 (SIP replaces header)

Complies

RFC 3892 (SIP referred-by mechanism)

Complies – relayed

RFC 3911 (SIP join header)

Complies – relayed

RFC 3951 (Internet Low Bit Codec)

Complies – relayed

RFC 4028 (SIP session timers)

Complies

RFC 4103 (Real-time text)

Complies

RFC 4122 (UUID to support GSID tracing)

Complies

RFC 4235 (SIP event dialogs)

Complies

RFC 4346 (TLS 1.1)

Complies

RFC 4566 (SDP, obsoletes 2327, 3266)

Complies

RFC 4568 (SDP security with SRTP)

Complies

RFC 4573 (Far End Camera Control)

Complies – relayed

RFC 4575 (SDP conference events)

Complies – relayed

RFC 4582 (Binary Floor Control Protocol)

Complies – relayed

RFC 4662 (SIP resource list events)

Complies – relayed

RFC 4730 (SIP key press events)

Complies – relayed

RFC 5031 (SIP URN for Emergency and other services)

Complies

RFC 5245 (Interactive Connectivity Establishment)

Complies

RFC 5246 (TLS 1.2)

Complies

RFC 5389 (TURN/STUN for WebRTC)

Complies

RFC 5806 (Diversion Indication in SIP

Complies

RFC 5853 (Requirements for Enterprise SBC Deployments)

Complies

RFC 5905 (Network Time Protocol V4)

Complies

RFC 5923 (Connection Reuse for SIP)

Complies

RFC 6062 (TURN on TCP)

Complies

RFC 7064 (Session Traversal Utilities for NAT – STUN)

Complies

RFC 7065 (Traversal Using relays around NAT) – TURN)

Complies

RFC 7245 (An Architecture for Media Recording Using the SIP)

Complies

RFC 7865 (SIPRec Metadata)

Complies

RFC 7866 (SIPRec Protocol)

Complies