Share via

Session Negotiation

  • Article

With the RTC Client API version 1.2, the application has the choice to handle session negotiations for a session or let the RTC Client API handle the session negotiations. The client application can decide to handle negotiations for outgoing or incoming invite requests or both. The application has access to the body of the SIP INVITE request to handle session description negotiations. At any time during the session, it is also possible for the client application to renegotiate the session description. The session description can be Session Description Protocol (SDP) data, or it can be another type of session descriptor known to the application.

The RTC Client API version 1.2 also allows applications to disable the media stack. Applications may choose to negotiate the SDP for several reasons:

  • An application may decide to disable the media stack so that the support for its own media stack can be added.
  • An application may want to use only the IM feature of the product and not allow media streaming. In this case, the media stack is not loaded when the Client object is initialized.

The following topics describe the SDP protocol and the possible scenarios for negotiating session descriptions that RTC Client 1.2 supports:

  • Session Descriptions — describes the purpose of the session description in the SIP INVITE.
  • Session Negotiation Options — describes the option available to the application to create a session in which the application handles the session negotiations.