Closed yashtandon113 closed 1 month ago
Hi
I worked on this issue and thought it should be done inside the SDK. What you can do is we already use In Call Manager inside the sample apps.
-> Detect device changes using Device Event Emitter with subscribing 'onAudioDeviceChanged' event. -> Route to the desired device using In Call Manager's chooseAudioRoute function. (possible parameters are BLUETOOTH, EARPIECE, SPEAKER_PHONE)
We checked the event 'onAudioDeviceChanged' listener but this is not giving us any callback when we attached the headset with our phone . Please suggest if there is any solution regarding this issue
Could you please provide any updates on this? We're stuck and eager for a resolution. Thank you!
Hi @yashtandon113,
Let's synch about this issue in one of the daily-standup.
Cheers Oguz
Hi
React Native SDK is focused on using the WebRTC library to make it work on top of the Ant Media Server's WebRTC stack. We are just using the in-call manager library for checking and managing audio devices. When I checked the issues on the original repository, I saw that it's a known issue that Bluetooth devices are not working properly right now. You can check the following issue to check the status. https://github.com/react-native-webrtc/react-native-incall-manager/issues/237
Hi @accesssolid ,
Let us know if it makes sense or you have any question
Regards Oguz
I am closing this because of inactivity.
We are currently utilizing the Ant Media React Native SDK for publishing, streaming, and conducting conference calls within our application. However, we have encountered an issue where users are experiencing difficulties with audio when using Bluetooth devices. Specifically, when users attempt to utilize Bluetooth for audio input and output during conference calls, the audio functionality does not function as expected. We have investigated potential causes internally, but we have not been able to resolve the issue thus far.