RFC 4244 An extension to Session Initiation Protocol (SIP) for required History Information.

Direct Routing sends P-Asserted-Identity with Privacy ID headers. Private Extension to the Session Initiation Protocol for asserted identity within Trusted Networks-Sections about handling P-Asserted-Identity header.

RFC 3261 SIP: Session Initiation Protocol.

The following standards are applicable to devices that support only non-media bypass mode:

Standards applicable to devices that support non-media bypass mode The SBC connected to Direct Routing must also comply with the following RFCs (or their successors). RFC standardsĭirect Routing complies with RFC standards. This component uses SRTP and SRTCP protocols.įor more information about Direct Routing, see Phone System Direct Routing.įor more information about how Direct Routing implements the SIP protocol, see Direct Routing - SIP protocol. This is the Internet-facing component of Direct Routing that handles media traffic. This is the Internet-facing component of Direct Routing that handles SIP (TLS) connections between the SBCs and Direct Routing. The customer SBC interfaces with the following components in the Microsoft Teams backend: This article is intended for voice administrators who are responsible for configuring the connection between the on-premises Session Border Controller (SBC) and the Session Initiation Protocol (SIP) proxy service.

This article describes how Microsoft Phone System Direct Routing implements RFC standard protocols.

Dtmf rfc2833