- Joined
- Jan 9, 2021
- Messages
- 64
- Reaction score
- 26
This is a weird one and I would like to know if anyone else has had this.
Some Background:
The most recent release of the Desktop App had a lot of problems with Jabra Headset integration in my case with the Jabra 65 Evolve and also with the 930 Pro dropping held calls on resume.
I wasn't aware of any of that and thought we had had an isolated problem with either our headsets or the latest version of Jabra Direct.
Therefore I was testing the desktop app and Jabra with various settings using my own extension.
Getting other members of staff to stop what they were doing and call me repeatedly isn't an option.
I therefore needed a way of testing my own extension and I figured I may have one. My extension has a incoming number (DID).
Used my company mobile to call the external DID directly (not the 3CX Android app on my phone as I would be trying to dial my own 3CX extension from my own 3CX Extension).
Instead of ringing and letting me pick up as expected it behaved as if I was busy or had status set as not available and went straight to voicemail.
I wasted the better part of the day thinking I had something wrong with my extension on top of the failed Headset integration.
Raised a ticket with our provider and they had no information on it.
Started looking through the forums and found others reporting Jabra problems and the solution, a beta for the Desktop App that added back the Jabra SDK integration and solved the headset problem and dropped calls too.
Doesn't solve this problem with mobile calls to a DID though.
Here is what I have found.
Mobile calls from:
Company Mobile with 3CX App installed to the external DID go straight to voicemail.
Personal mobile to the external DID are handled normally. i.e. I can pick up on the Desktop App.
Removing the mobile number from the field in my extension in 3CX makes no difference.
Removing the 3CX App from the company mobile cures the problem.
Question is why is 3CX Desktop App treating my 3CX extension as if it was busy?
The point being that according to both me and the 3CX staff I have spoken too the 3CX Android App is not involved in the outbound call from the mobile in anyway.
It shouldn't even be aware of the call so how is the 3CX server getting involved and why?
Some Background:
The most recent release of the Desktop App had a lot of problems with Jabra Headset integration in my case with the Jabra 65 Evolve and also with the 930 Pro dropping held calls on resume.
I wasn't aware of any of that and thought we had had an isolated problem with either our headsets or the latest version of Jabra Direct.
Therefore I was testing the desktop app and Jabra with various settings using my own extension.
Getting other members of staff to stop what they were doing and call me repeatedly isn't an option.
I therefore needed a way of testing my own extension and I figured I may have one. My extension has a incoming number (DID).
Used my company mobile to call the external DID directly (not the 3CX Android app on my phone as I would be trying to dial my own 3CX extension from my own 3CX Extension).
Instead of ringing and letting me pick up as expected it behaved as if I was busy or had status set as not available and went straight to voicemail.
I wasted the better part of the day thinking I had something wrong with my extension on top of the failed Headset integration.
Raised a ticket with our provider and they had no information on it.
Started looking through the forums and found others reporting Jabra problems and the solution, a beta for the Desktop App that added back the Jabra SDK integration and solved the headset problem and dropped calls too.
Doesn't solve this problem with mobile calls to a DID though.
Here is what I have found.
Mobile calls from:
Company Mobile with 3CX App installed to the external DID go straight to voicemail.
Personal mobile to the external DID are handled normally. i.e. I can pick up on the Desktop App.
Removing the mobile number from the field in my extension in 3CX makes no difference.
Removing the 3CX App from the company mobile cures the problem.
Question is why is 3CX Desktop App treating my 3CX extension as if it was busy?
The point being that according to both me and the 3CX staff I have spoken too the 3CX Android App is not involved in the outbound call from the mobile in anyway.
It shouldn't even be aware of the call so how is the 3CX server getting involved and why?