You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're building an application where iOS Voip is combined with LiveKit. We have all configured modes, categories, and options for the AudioSession depending on the type of the call: video or audio. The issue comes when the user connects to the room:
When a new call is reported and CXProvider activates an audio session, AudioSession audio routes are configured correctly:
Audio - Receiver
Video - Speaker
After connection to the room audio switches to the Speaker, but should stay Receiver as initially.
Do we have a default audio and mic configuration, where we can join the room with the required options? Example: Build-in Audio / Microphone On / Video off for video calls and Speaker Audio / Microphone On / Video on for video calls?
SDK Version
2.0.8
iOS/macOS Version
Version 14.5 (23F79)
The text was updated successfully, but these errors were encountered:
to avoid speaker, you'd need to customize the audiosession and ensure the mode is set to voiceChat. We default to videoChat, which means it'll be output to the speaker.
We're building an application where iOS Voip is combined with LiveKit. We have all configured modes, categories, and options for the AudioSession depending on the type of the call: video or audio. The issue comes when the user connects to the room:
When a new call is reported and CXProvider activates an audio session, AudioSession audio routes are configured correctly:
Audio - Receiver
Video - Speaker
After connection to the room audio switches to the Speaker, but should stay Receiver as initially.
Do we have a default audio and mic configuration, where we can join the room with the required options? Example: Build-in Audio / Microphone On / Video off for video calls and Speaker Audio / Microphone On / Video on for video calls?
SDK Version
2.0.8
iOS/macOS Version
Version 14.5 (23F79)
The text was updated successfully, but these errors were encountered: