Skip to main content

3.8. Interactions with Forking

3.8. Interactions with Forking​

Some call signaling systems allow various types of forking where an SDP Offer may be provided to more than one device. For example, SIP [RFC3261] defines both a "parallel search" and "sequential search". Although these are primarily signaling-level issues that are outside the scope of JSEP, they do have some impact on the configuration of the media plane that is relevant. When forking happens at the signaling layer, the JavaScript application responsible for the signaling needs to make the decisions about what media should be sent or received at any point in time, as well as which remote endpoint it should communicate with; JSEP is used to make sure the media engine can make the RTP and media perform as required by the application. The basic operations that the applications can have the media engine do are as follows:

  • Start exchanging media with a given remote peer, but keep all the resources reserved in the offer.

  • Start exchanging media with a given remote peer, and free any resources in the offer that are not being used.

Last updated on