RFC An Offer/Answer Model with Session Description Protocol (SDP), June Canonical URL: ; File formats: . Request for Comments This RFC was published in RFC – Key words for use in RFCs to Indicate Requirement Levels · RFC SDP offer and answer model is described in RFC “An Offer/Answer Model with Session Description Protocol (SDP)”. The SDP negotiator is represented.
|Published (Last):||9 March 2007|
|PDF File Size:||16.59 Mb|
|ePub File Size:||6.72 Mb|
|Price:||Free* [*Free Regsitration Required]|
For example, the initial offer may specify that a stream is sendrecvwhile the answer specifies that remote stream rff inactive. Parameters rfc 3264 Negotiator state.
Rfc 3264 generating a new offer, in the case that a media line doesn’t match the active SDP, the new media line will be considered to replace the existing media rrfc the same position. Get the state string description of the specified state.
RFC – An Offer/Answer Model with the Session Description Protocol (SDP)
rfc 3264 Initialize the SDP negotiator with remote offer, and optionally specify the initial local capability, if known. If the negotiation fails, the active local and remote SDP will not change.
rfc 3264 To unregister the callback of specific format, just call this function with parameter cb set to NULL. In generating answer, the Rfc 3264 fmtp in the answer candidate may need to be modified by the customized SDP format matching callback to achieve flexible SDP negotiation, e. Parameters neg The negotiator.
Application calls rfc 3264 function when it receives Rfc 3264 answer from remote. If the negotiation succeeds i. The customized SDP format matching is needed when the format identification in a media stream session cannot be simply determined by encoding name and clock rate, but also involves one or more format specific parameters, which are specified in SDP fmtp attribute. If remote codec order is preferable, the selected codec will be 8, rrfc if local codec order is preferable, the selected codec will be 3.
Enumeration of customized SDP format matching option flags. In this case, the negotiator will update the stream in the local active media as inactive too. Application calls this function when it receives SDP rcf from remote.
If negotiator has initial local capability, application can specify NULL on this argument; in rfc 3264 case, the negotiator will create answer by by negotiating remote offer with initial local capability. Rfc 3264 pool The memory pool. The declaration of customized SDP format matching callback. This specifies the behavior of the SDP negotiator when responding to an offer, whether it should rather use the rfv preference as set by remote, or should it rather use the codec preference as specified by local endpoint.
Modify local session with a new SDP and treat this as a new offer. For example, an H. If negotiator doesn’t have initial local rfc 3264, application MUST specify local answer here. Create the SDP negotiator with local offer. Get SDP negotiator state. The negotiator is capable to match and reorder local SDP according to remote offer, and create an answer that is suitable for rfc 3264 offer.
If non-zero, the negotiator will use the codec rfc 3264 as specified in remote offer.
An Offer/Answer Model with the Session Description Protocol (SDP)
At this stage, application may or may not 3624 to create an answer. Allow media type rfc 3264 33264 SDP to be changed. If zero only a single format will be returned. Get the current local SDP offer or answer. As those parameters are rfc 3264 specifics, the negotiation must be done by the format or codec implementation. The format name, e. If any previous negotiation process was successfull 32264. Get the current remote SDP offer or answer. The purpose of this negotiation is to verify remote answer, and update the initial offer according to the answer.
Application normally calls this function when it receives initial offer from remote. Register customized SDP format matching callback function for the specified format.
The SDP negotiator is ready to negotiate both session descriptors. Parameters pool Pool to allocate memory. The pool’s lifetime needs to be valid for the duration of rfc 3264 negotiator. Rfc 3264 that the string buffer must remain valid until the callback is unregistered.
For example, it can have more or less media lines than the offer, or their order may be different than the offer. In this case, both active local and active remote will not be modified. Rfc 3264 the currently active local SDP.
Ken’s Unified Communications Blog: IETF RFCs Supported by Lync
Determine whether remote rfc 3264 answer as opposed to offer on the rfc 3264 negotiation. This enumeration describes SDP negotiation state.
After calling this function, application can send the SDP as offer to remote party, using signaling protocol such as SIP. If tfc, the negotiator will respond with multiple formats. Generating SDP Answer After remote offer has been set in the negotiator, application can request the SDP negotiator to generate appropriate answer based on local capability.
For example, suppose incoming call has codec order “8 32264 3”, while local codec order is “3 0 8”. Pool to rfc 3264 memory. Returns Non-zero if it was remote who sent answer, otherwise zero if it was local who supplied answer. Get the 3246 active remote SDP. If rfc 3264, it will prefer to use the local codec order.