Beeping heard while making calls on Samsung S10/S20 (Wifi Only)

[jbrilliant]

We have a number of iOS and Android users, but ONLY the Samsung Galaxy S10 and S20 users have reported this issue;

The call works fine other than the beeping drives them crazy while trying to have a conversation. The other end does not hear the beeping. The users also see "Reconnecting..." on the app dial screen.

It only occiurs when making calls (to both outbound enternal numbers and internal 3CX extensions). But never when recieving calls.

It only occurs when connected to Wifi, but any wifi - e.g. home. multiple offices, client wifi. including the office with the local 3CX PBX. But is not reported to happen on 3G/4G.

It doesn't usually happen on the first call made after when joining the Wifi, but from the second call it appears about 50/50 chance of occuring.

To workaround it, they have been either turning Wifi off and back on OR close the 3CX App and re-open it before making a call, and then the next call will "usually" work without beeping, or just leaving the Wifi turned off.

Issue is not new, it's been happening for a while, so not a recent update.

The beeping is obviously being wrongly triggered in the App, but any ideas on why?

 

[KyriakosP]

Hi @jbrilliant, Please confirm the app and PBX version you are using. Also, can you please try reproducing this issue with our latest beta app and provide verbose logs?

To get a verbose log from the app while the issue occurs:
a. Go into the app's 'Settings', then 'Advanced' and enable the 'Verbose Logging' option.
b. When the issue occurs, use the 'Send Log Report', i.e. the last option in 'Settings'> 'Advanced'.
c. After you select the 'Send Log Report' option, you can now disable the 'Verbose Logging' option.

 

[jbrilliant]

Running PBX 16.0.8.9 with Auto Updates on. Android phones are all latest with Auto updates turned on.

I've asked the users to try catching it with the Verbose logging - once that's done I'll get them to run the Beta and see how it goes.

 

[KyriakosP]

That's good @jbrilliant. PM me when you have the verbose log(s) so we can start troubleshooting.