BelledonneCommunications / linphone-sdk

Mirror for linphone-sdk (https://gitlab.linphone.org/BC/public/linphone-sdk.git)
GNU Affero General Public License v3.0
104 stars 80 forks source link

Initiator of Call conference cannot participate in conversation (no incomming (speaker) and no outgoing (microphone) sound) #331

Open BijleveldT opened 1 year ago

BijleveldT commented 1 year ago

Hi there,

While testing with Linphone in combination with SIP and conference calls, I ran into the following issue where the initiator of the conference call can not participate in the conversation.

  1. Describe the bug (mandatory)

Three phones start a conference call via SIP (all three are logged-in/registered with SIP accounts to a central SIP/PBX server). A calls B, then B calls C. Finally, B converts the calls to a conference. From this moment on, B is no longer able to speak/hear the ongoing conference. A and C remain 'active'.

I was able to reproduce this with the (latest?) beta version of Linphone from the PlayStore beta track. Linphone Version 5.1.0-beta.92+91554f99f (release/5.1,releasewitHCrasshlytics) Linphone SDK 5.2.95-pre.1+4938179ac (release/5.2, release)

  1. To Reproduce (mandatory)

Have three mobiles (A, B, and C) with Linphone using SIP A calls B B calls C B initiates a Conference call with A and C Conference call starts with all three participants A and C have "normal" conference capabilities (e.g. When A makes sound. C can hear this and vice-versa) However, B cannot hear A and C, nor can A and C hear B.

  1. Expected behavior (mandatory)

When a conference call is initiated all attendees should be able to speak (and be heard) and be able to hear the other participants speaking.

  1. Please complete the following information (mandatory)

A (left device in the attached video) Samsung Galaxy XCover 5 - SM-G525F (Android 13) B (center device in the attached video) Samsung Galaxy XCover 4s - SM-G398FN (Android 11) C (right device in the attached video) Ascom Myco 3 Cellular Wi-Fi EU (Android 9)

All 3 device run the (latest?) beta release of Linphone from the PlayStore Linphone Android 5.1.0-beta.92+91554f99f (release/5.1,releaseWithCrashlytics) Linphone SDK 5.2.95-pre.1+4938179ac (release/5.2,release)

  1. SDK logs (mandatory)

XCover 5 (A13) (Phone on the left in the attached video) https://www.linphone.org:444//tmp/64d5ff7af0c1d_9d93458e5cd785794de2.gz

XCover 4s (A11) (Phone at the center in the attached video) https://www.linphone.org:444//tmp/64d5ffac0679a_f6d7b97a1bde8a3c01ed.gz

Ascom Myco 3 (A9) (Phone on the right of attached video) https://www.linphone.org:444//tmp/64d5ffd4a7cf1_ef77db31d71703cdcbb2.gz

  1. Adb logcat logs (mandatory if native crash)

n.a.

  1. Screenshots (optional)

See attached video https://github.com/BelledonneCommunications/linphone-android/assets/141026307/bb212203-d9a5-47ad-afdb-0b0ea3322fc3

  1. Additional context (optional)

In the video it can be seen the other microphones are muted and set to speaker mode (for easy testing). When noise is made at Phone B, nothing is heard on the other 2 phones.

Likewise, when phone B is set to speaker and muted mic and the mic of any of the other two phones is (re)enabled. Nothing can be heard at phone B, when noise is made close to any of the other phones.

If there is any extra info you need to reproduce/fix this issue, don't hesitate to ask. I will try to provide as much info as possible. Thanks for the great support and your effort for this product.

Kind regards, Thijs

zeejaydev commented 1 year ago

Did you try to go back to the conference view and tap on the conference icon again? that should force add Phone B to the conference again but you might face this other issue https://github.com/BelledonneCommunications/linphone-sdk/issues/329

BijleveldT commented 1 year ago

Dear Zaid,

I tried your work-around, but then I ran into other unwanted behaviour. So it is a way to work around the initial problem, but the problem that follows is not acceptable in a ‘work environment’.

When clicking the conference button again (like you suggested), phone B was added to the conference. But… The “mute microphone” is not working correctly anymore. When I press ‘mute’ on phone B, the icon on phone B indicates that the mic should be muted, but phone A and C can still hear what is being said at B.

Pressing the “mute” button multiple times at “B” does not resolve the issue. i.e. UI state toggles, but the microphone actually remains functional. (For extra context, phone B is running Android 11. I don’t know if that is important, but just to give as much info as possible)

With the few short/quick tests I did, luckily I did not encounter BelledonneCommunications/linphone-sdk#329.

Kind regards, Thijs

Van: Zaid Jamil @.> Verzonden: vrijdag 11 augustus 2023 20:27 Aan: BelledonneCommunications/linphone-android @.> CC: Thijs Bijleveld @.>; Author @.> Onderwerp: Re: [BelledonneCommunications/linphone-android] Initiator of Call conference cannot participate in conversation (no incomming (speaker) and no outgoing (microphone) sound) (Issue BelledonneCommunications/linphone-sdk#331)

Did you try to go back to the conference view and tap on the conference icon again? that should force add Phone B to the conference again but you might face this other issue might BelledonneCommunications/linphone-sdk#329https://github.com/BelledonneCommunications/linphone-sdk/issues/329

— Reply to this email directly, view it on GitHubhttps://github.com/BelledonneCommunications/linphone-sdk/issues/331, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BBT6IA33EL3QCVFXFUL2P5DXUZ2PHANCNFSM6AAAAAA3MYZDI4. You are receiving this because you authored the thread.Message ID: @.**@.>>

mvdhorst commented 1 year ago

I've got the same issue, is there already any sight whether the issue can be resolved

BijleveldT commented 9 months ago

Hello,

It has been a while, so I thought I'd try to reproduce/check this issue with the latest Linphone from the Google Play store. Unfortunately, this issue is still present.

Is there any info on when (or even if) this issue will be addressed?

Kind regards, Thijs