Audio not working from multiple participants

External Issue #15593910

Details

Author
Michael L.
Created
Jan 24, 2018
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

Summary:

Given 3 or more participants in a WebRTC "Session", I only hear audio from the first participant that was subscribed. I can not hear audio from the second, third, etc.

Steps to reproduce:

On one computer:

On another computer with Edge:

  • Open https://meet.tokbox.com/<room_name> in Edge
  • You should see both participants
  • Try muting one at a time, ensuring to unmute the other

Observed results:

Audio from only one participant works.

Expected results:

Audio from both participants to work.

Other browsers:

  • Chrome receives audio in multi-party calls fine
  • Firefox receives audio in multi-party calls fine
  • Safari receives audio in multi-party calls fine

Note: This bug seems to only happen in the WebRTC API and not the ORTC API. When using the ORTC API it behaves as expected, and you can hear all participants. Adapter.js will fix this issue, but in our case, we have other issues caused by the ORTC API.

Tips:

Meet doesn’t always work the first time with Edge, I’ve found more success by appending p2p to the room name. So for instance, if your room name is "foobar", then “foobarp2p” will skip the media server and connect directly P2P.

Copied from Description when changed from Task to Bug

Copied from Repro Steps when changed from Bug to Task

Summary:

Given 3 or more participants in a WebRTC "Session", I only hear audio from the first participant that was subscribed. I can not hear audio from the second, third, etc.

Steps to reproduce:

On one computer:

On another computer with Edge:

  • Open https://meet.tokbox.com/<room_name> in Edge
  • You should see both participants
  • Try muting one at a time, ensuring to unmute the other

Observed results:

Audio from only one participant works.

Expected results:

Audio from both participants to work.

Other browsers:

  • Chrome receives audio in multi-party calls fine
  • Firefox receives audio in multi-party calls fine
  • Safari receives audio in multi-party calls fine

Note: This bug seems to only happen in the WebRTC API and not the ORTC API. When using the ORTC API it behaves as expected, and you can hear all participants. Adapter.js will fix this issue, but in our case, we have other issues caused by the ORTC API.

Tips:

Meet doesn’t always work the first time with Edge, I’ve found more success by appending p2p to the room name. So for instance, if your room name is "foobar", then “foobarp2p” will skip the media server and connect directly P2P.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To from “James M.” to “Gurpreet V.”

      Changed Assigned To from “Gurpreet V.” to “Angelina G.”

      Changed Steps to Reproduce

      Changed Assigned To from “Angelina G.” to “Gurpreet V.”

      Changed Status to “External”

    • Hello,

       

      Thank you for
      providing this information about the issue. We
      have confirmed the problem, and are considering a solution for a future build
      of Edge.
      We are resolving this issue as a duplicate of an existing
      feature request. We look forward to additional feedback you may have on how we
      can improve Microsoft Edge.

       

      Sincerely,

      The MS Edge Team

    • This issue has been resolved External. This means this issue may require a new feature to be implemented or other work that is more significant than a typical bug. You may be able to find more information on this issue by searching for related features on status.microsoftedge.com and uservoice.microsoftedge.com.

    You need to sign in to your Microsoft account to add a comment.

    Sign in