- Joined
- Jul 26, 2018
- Messages
- 45
- Reaction score
- 3
Hello everyone,
I configured a queue to ring all agents for 180 seconds, and if no answer after 180 seconds, it should send the call to VM. Everything works as expected on laptops and computers, but if I connect to the extension with 3cx on my android, then android app rings only 30 sec and stops, while laptop with the same extension continues to ring for 180 sec as configured in the queue. This extension is indeed configured to ring for 30 seconds before forwarding to voicemail, but I didn't expect 3cx app to follow extension timer when call is coming through the queue.
At first, I thought that customer is giving me false info, but I just tested it with my own phone and PC, and when call comes to the queue, PC will ring for 180 seconds, while android will ring only 30 seconds.
Does anyone have any idea how to resolve this, and if this is something implemented intentionally by 3cx?
Regards
I configured a queue to ring all agents for 180 seconds, and if no answer after 180 seconds, it should send the call to VM. Everything works as expected on laptops and computers, but if I connect to the extension with 3cx on my android, then android app rings only 30 sec and stops, while laptop with the same extension continues to ring for 180 sec as configured in the queue. This extension is indeed configured to ring for 30 seconds before forwarding to voicemail, but I didn't expect 3cx app to follow extension timer when call is coming through the queue.
At first, I thought that customer is giving me false info, but I just tested it with my own phone and PC, and when call comes to the queue, PC will ring for 180 seconds, while android will ring only 30 seconds.
Does anyone have any idea how to resolve this, and if this is something implemented intentionally by 3cx?
Regards