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):||27 July 2010|
|PDF File Size:||16.56 Mb|
|ePub File Size:||9.21 Mb|
|Price:||Free* [*Free Regsitration Required]|
At this stage, application may or may not ready to create an answer.
Get the current local SDP rfc 3264 or answer. If the negotiation fails, the active local and remote SDP will not change. If negotiator has initial local capability, application can specify NULL on this argument; in this case, the rfc 3264 will create answer by by negotiating remote offer with initial local capability.
Get the state string description of the specified state. This state occurs when SDP negotiation has completed, either successfully or not. Returns String description of the state. This structure contains negotiation state and several SDP session descriptors currently being rfc 3264 in the negotiation. The negotiator is capable to match and reorder local SDP according to remote offer, and create an answer that is suitable for the offer.
Create the SDP negotiator with local offer. Rfc 3264 can only call this function after negotiation has been done, or otherwise there won’t be active SDPs. To unregister the callback of specific format, just call this function with parameter rfc 3264 set to NULL.
Application calls this function when it receives SDP offer from remote.
An Offer/Answer Model with the Session Description Protocol (SDP)
Modify local session with a new SDP and treat this as a new offer. The purpose of this negotiation is to verify remote answer, and update the initial offer according to the answer. Register customized SDP format rfc 3264 callback function for the specified format.
Calling this function will not change the state of the negotiator. For example, suppose incoming call has codec order “8 0 3”, while local codec order is “3 0 8”. The declaration of customized SDP format matching callback. This rfc 3264 occurs when an offer either local or remote has been provided with answer.
If zero only a single format will 33264 returned. Match format in the SDP rfc 3264 offer and answer.
As those parameters are format specifics, rfc 3264 negotiation must be done by the format or codec implementation. If any previous negotiation process was successfull i.
If non-zero, the negotiator will respond with 3246 formats. In generating answer, rfc 3264 SDP fmtp in the rfc 3264 candidate may need to be modified by the customized SDP format matching callback to achieve flexible SDP negotiation, e. Returns Non-zero if it was remote who sent answer, otherwise zero if it was local who supplied answer.
Parameters pool Pool rfc 3264 allocate memory. Parameters neg The SDP negotiator instance. If the negotiation succeeds i. If zero, it will prefer to use the local codec order. Note that the string buffer must remain valid until the callback is unregistered.
[SIPForum-discussion] Proper RFC Hold Behavior in SDP
If application does not want send modified offer, it can just send rfc 3264 active local SDP frc the offer. Returns The negotiator state. 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, the initial offer may specify that a stream is sendrecvwhile the answer specifies that remote rfc 3264 is inactive.