RFC 5370: The Session Initiation Protocol (SIP) Conference Bridge Transcoding Model

This document describes how to invoke transcoding services using the conference bridge model. This way of invocation meets the requirements for SIP regarding…

Read RFC 5370 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3261: SIP: Session Initiation Protocol
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 4474: Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)
Normative reference — RFC 3325: Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
Normative reference — RFC 3323: A Privacy Mechanism for the Session Initiation Protocol (SIP)
Normative reference — RFC 3850: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling
Normative reference — RFC 4244: An Extension to the Session Initiation Protocol (SIP) for Request History Information
Normative reference — RFC 4117: Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)
Normative reference — RFC 5363: Framework and Security Considerations for Session Initiation Protocol (SIP) URI-List Services
Normative reference — RFC 5366: Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)
Normative reference — RFC 5369: Framework for Transcoding with the Session Initiation Protocol (SIP)
Informative reference — RFC 4566: SDP: Session Description Protocol
Informative reference — RFC 4575: A Session Initiation Protocol (SIP) Event Package for Conference State
Informative reference — RFC 5360: A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)