Setting up a Connect call via MS Teams or Zoom
This is a temporary solution to enable multiple participants to be able to observe the view shared by a Mira Prism headset during a Connect call. Native multi-party participant calling is coming to Mira Connect.
- The person due to make or receive the Connect call with the Headset User (known as the "Remote Expert") should first log into their Organization's Mira Enterprise suite on their workstation with their support web browser (latest version of Chrome or Edge), and leave as an open tab. This will ready the Remote Expert to be able to share their screen on the Zoom or MS Teams call with the Remote Participants (other persons invited to the Zoom or MS Teams call).
- Start the meeting with Zoom or MS Teams, including the further remote participants.
- Ensure the Headset user is logged into the Mira Prism app on their headset so they are able to receive or make a Connect call (The user will appear on the Mira Connect contact list with a green dot if logged in and connectivity available).
- Initiate Zoom or MS Team screen sharing, and ensure “Include System Audio” (MS Teams) or "Include Computer Audio" (Zoom) is selected as appropriate.
- Select "Screen share" within the Zoom or MS Teams call, and share the browser tab logged into the Mira web suite.
- From within the Mira web suite, you can now start a Mira Connect call.
- You will now be using MS Teams or Zoom to broadcast the headset user's POV in the Mira Connect call to other remote participants on the MS Teams or Zoom call.
NOTE: Only the headset user and Remote Expert (the participant on the Zoom or MS Teams call logged into the Mira web suite on the other end of the Connect call, and sharing their screen) will have continuous bi-directional communication. This means other remote participants on the Zoom or MS Teams call will be able to hear the headset wearer, but will not be able to speak with the headset user directly.
- The result is the Remote Expert must act as the moderator/go-between during the call, which removes direct cross-talk back and forth with the headset user and remote participants.
General Best Practices
- Test in advance on the exact systems that will be used during a demo or live trial, in order to get familiar with the configurations, and minimize any surprises.
- Manage Expectations: Remote participants will experience slightly increased lag. They are viewing a video call within a video call.
- Use bluetooth headphones on the headset side to eliminate risks of feedback noise on the call. Learn more about bluetooth headphone recommendations for Mira Prism.
- If you are demonstrating a Connect call taking place the Prism headset via a Zoom or MS Teams call (ie the headset is near your work station laptop or desktop conducting the Zoom call to display the headset user via the webcam), you will experience audio feedback between the headset phone mic and speakers, and the work station mic and speakers. To resolve this, ensure the microphone on the MS Teams or Zoom call is muted on the work station near the headset).
- Ensure audio sharing is enabled on MS Teams or Zoom. This permits the audio from the Mira Connect session to be shared with other participants.
- Note: Audio shared with "Share System Audio" enabled is supported in one direction, the remote participant(s) will be able to hear the headset user. Two-way audio to the headset user is restricted to the Remote Expert only. This enables the Remote Expert to administer the call and minimize distractions to the headset user from remote participant cross-talk.
- The remote expert is running both Mira’s Connect App in the Web Portal as well as the Teams or Zoom App
- The headset user is wearing the headset.
- The participants that call into the MS Teams or Zoom call