- Joined
- Jun 24, 2020
- Messages
- 3
- Reaction score
- 0
Device Info
-------------------------------------------------------
Phone Model: Samsung Galaxy S9+
App Version: 16.3.1.93
Additional details
-------------------------------------------------------
Connection: 4G LTE
Server OS: Raspbian Debian
Hello,
When in my local network using the Android soft phone client on my phone the status icon in the top right of the app shows green and I am able to manipulate it, along with in call mute, transfer, conference etc. If I turn off my WiFi on my phone, and use 4G LTE only the app still says ready for calls. I am able to place and receive calls (sometimes it doesn't ring through if the app isn't open, but that's pretty uncommon), however the status icon in the top right is grey and does nothing when i click it. Also the in call controls such as mute, transfer, conference etc are grayed out and unusable. I updated to the latest beta release (16.3.1.93) of the app to see if this changes, but the behavior seems to be persistent. Is this the expected behavior, or should those features/capabilities work when outside the local network as well?
Thanks,
Eric
-------------------------------------------------------
Phone Model: Samsung Galaxy S9+
App Version: 16.3.1.93
Additional details
-------------------------------------------------------
Connection: 4G LTE
Server OS: Raspbian Debian
Hello,
When in my local network using the Android soft phone client on my phone the status icon in the top right of the app shows green and I am able to manipulate it, along with in call mute, transfer, conference etc. If I turn off my WiFi on my phone, and use 4G LTE only the app still says ready for calls. I am able to place and receive calls (sometimes it doesn't ring through if the app isn't open, but that's pretty uncommon), however the status icon in the top right is grey and does nothing when i click it. Also the in call controls such as mute, transfer, conference etc are grayed out and unusable. I updated to the latest beta release (16.3.1.93) of the app to see if this changes, but the behavior seems to be persistent. Is this the expected behavior, or should those features/capabilities work when outside the local network as well?
Thanks,
Eric