Abnormal behavior of speaker button on system provided call screen

Question

We write VoIP application using CallKit and PortSIP and here is a problem is reproduced only on iOS 11.2.x. When user taps speaker button on CallKit provided screen system enables speaker but icon remains in disabled state. If user taps again system also turns speaker on and forgets about button. To disable speaker user should tap button twice. Has anybody met this bug? And what was your solution? (:

Thanks.

Do you have solution for this or fixed this issue any alternate? Thanks, — Madhu, Feb 09 '18 at 04:21
@Madhu, nope. I've reported this bug to apple but they only ask me to send them sysdiagnose… again and again ): — Alex Zaikin, Feb 14 '18 at 13:33
I raised a bug for WebRTC with this bug: https://bugs.chromium.org/p/webrtc/issues/detail?id=9307#c1. Apps that don't use WebRTC (Like WhatsApp) are not having this issue. — YYamil, Jun 04 '18 at 15:38
I am also facing same issue. CallKit with WebRTC. Anyone found any alternate solution? — Kiran Patel, Nov 09 '18 at 23:49
You may check my answer here https://stackoverflow.com/a/55413256/6064953 For me it works as expected. — Igor Rutmb, Mar 29 '19 at 08:34

score 13 · Answer 1 · answered Feb 15 '18 at 11:34

13

    RTCDispatcher.dispatchAsync(on: RTCDispatcherQueueType.typeAudioSession) {
        let audioSession = RTCAudioSession.sharedInstance()
        audioSession.lockForConfiguration()
        let configuration = RTCAudioSessionConfiguration.webRTC()
        configuration.categoryOptions = [AVAudioSessionCategoryOptions.allowBluetoothA2DP,AVAudioSessionCategoryOptions.duckOthers,
                                         AVAudioSessionCategoryOptions.allowBluetooth]
        try? audioSession.setConfiguration(configuration)
        audioSession.unlockForConfiguration()
    }

It helps me for CallKit. Speaker button works as expected.

answered Feb 15 '18 at 11:34

Алексей Смольский

141
7

1

`func provider(_ provider: CXProvider, perform action: CXAnswerCallAction) { }` – Алексей Смольский Apr 27 '18 at 07:23
I did it, and though it is not working. How Did you manage to do this? – Abhishek Mitra Apr 27 '18 at 10:46
Worked for me and I have no idea why. Thanks. – clawoo May 23 '18 at 15:02
It works! And this should be the accepted answer despite not being an official workaround. – cmacera May 14 '19 at 10:35
I'm using twilio-webrtc along with call-keep to handle video calling and callkit. It works fine so far but creates an issue while phone is locked and unable to handle event at that time. Any idea how to handle that scenario? – Jaydeep Patel Sep 19 '19 at 06:54
I tried this solution, though it's not working. Any suggestions to fix this issue ?? – Balaji Ramakrishnan Feb 17 '20 at 08:14
1

```try? AVAudioSession.sharedInstance().setCategory( AVAudioSession.Category.playAndRecord, mode: AVAudioSession.Mode.voiceChat, options: [.duckOthers, .allowBluetoothA2DP, .allowBluetooth] )``` I use it in all my projects. Maybe someone changes AVAudioSession after that – Алексей Смольский Feb 18 '20 at 09:03
I've fixed my issue using this solution. Thanks @АлексейСмольский – Balaji Ramakrishnan Feb 19 '20 at 06:37
Worked for me on CallKit and WebRTC combination. Thank you @АлексейСмольский – Alexander Aug 10 '20 at 07:59
Worked for me! Thank you. – Ankur Lahiry Mar 21 '21 at 04:43

score -1 · Accepted Answer · answered Dec 31 '17 at 08:59

-1

The same issue has been experienced in the previous versions as well. So this is not the new issue happening on the call kit.

This issue has to be resolved from iOS. We don't have any control over this.

answered Dec 31 '17 at 08:59

RJV Kumar

2,283
16
28

Abnormal behavior of speaker button on system provided call screen

2 Answers2

Linked