Session Description Protocol (SDP) Simple Capability Declaration

Andreasen, Flemming

doi:10.17487/rfc3407

Cited by 9 publications

(11 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The RemoteConnectionDescriptor does not indicate support for "image/ t38" as a latent capability [RFC3407]. Consequently, the gateway will not initiate the T.38 strict fax procedure, "t38", upon detecting fax stimulus (i.e., CNG, V.21 flags, etc.).…”

Section: Localconnectionoptionsmentioning

confidence: 99%

Media Gateway Control Protocol (MGCP) Voiceband Data (VBD) Package and General-Purpose Media Descriptor Parameter Package

Stone¹,

Kumar²,

Andreasen³

2012

Self Cite

View full text Add to dashboard Cite

Section: Localconnectionoptionsmentioning

confidence: 99%

Media Gateway Control Protocol (MGCP) Voiceband Data (VBD) Package and General-Purpose Media Descriptor Parameter Package

Stone¹,

Kumar²,

Andreasen³

2012

Self Cite

View full text Add to dashboard Cite

“…It is RECOMMENDED that implementations use the attributes and procedures defined in this document instead of those defined in [RFC3407]. If capability description interoperability with legacy RFC 3407 implementations is desired, implementations MAY include both RFC 3407 capability descriptions and capabilities defined by this document.…”

Section: Sdp Capability Negotiation and Intermediariesmentioning

confidence: 99%

“…RFC 3407 [RFC3407] defined simple capability declarations, which extends SDP with a simple and limited set of capability descriptions. Grouping of media lines, which defines how media lines in SDP can have other semantics than the traditional "simultaneous media streams" semantics, was defined in RFC 5888 [RFC5888], etc.…”

mentioning

confidence: 99%

Session Description Protocol (SDP) Capability Negotiation

Andreasen¹

2010

Self Cite

View full text Add to dashboard Cite

The Session Description Protocol (SDP) was intended to describe multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. SDP was not intended to provide capability indication or capability negotiation; however, over the years, SDP has seen widespread adoption and as a result it has been gradually extended to provide limited support for these, notably in the form of the offer/answer model defined in RFC 3264. SDP does not define how to negotiate one or more alternative transport protocols (e.g., RTP profiles) or attributes. This makes it difficult to deploy new RTP profiles such as Secure RTP or RTP with RTCP-based feedback, negotiate use of different security keying mechanisms, etc. It also presents problems for some forms of media negotiation.

show abstract

“…* the relevant MIME media type, e.g., "image/t38", is included in the "m=" line in the RemoteConnectionDescriptor, or * the relevant MIME media type is included as a capability (see [RFC3407]) in the RemoteConnectionDescriptor.…”

Section: If Both Fax Localconnectionoptions and Amentioning

confidence: 99%

“…The gateway acknowledges the command and includes SDP with codec information and RFC 3407 [RFC3407] Step 3:…”

Section: Call Flow Examplesmentioning

confidence: 99%