mamo
Forum User
- Joined
- Aug 22, 2016
- Messages
- 39
- Reaction score
- 2
Hi,
I have noticed a very strange and annoying Problem on the Android app.
The problem occurs reproduceable when I am in a call on my smartphone (just plain standard Android call via my mobile carrier, no 3CX, no other SIP or whatsoever). If now someone calls me at my landline number, firstly the softphone on my Windows PC starts ringing. A second later push reaches my Android phone. I hear an unpleasant beep and at the same time the person who is calling me gets kicked out of the line with the error message "the person you are calling is not available presently".
Easiest way to reproduce the issue is to just call yourself via your smartphone (use mobile carrier and dial SIP number that gets routed to the same smartphone via 3CX). It will ring once, beep once and play the error message thereafter.
My phone is an LG G5 with all available updates (currently running Android 6.0.1).
3CX and the Android app are also up to date (just newly installed the whole system last week and now running some tests the uncovered the problem I am describing here).
I have noticed a very strange and annoying Problem on the Android app.
The problem occurs reproduceable when I am in a call on my smartphone (just plain standard Android call via my mobile carrier, no 3CX, no other SIP or whatsoever). If now someone calls me at my landline number, firstly the softphone on my Windows PC starts ringing. A second later push reaches my Android phone. I hear an unpleasant beep and at the same time the person who is calling me gets kicked out of the line with the error message "the person you are calling is not available presently".
Easiest way to reproduce the issue is to just call yourself via your smartphone (use mobile carrier and dial SIP number that gets routed to the same smartphone via 3CX). It will ring once, beep once and play the error message thereafter.
My phone is an LG G5 with all available updates (currently running Android 6.0.1).
3CX and the Android app are also up to date (just newly installed the whole system last week and now running some tests the uncovered the problem I am describing here).