I sometimes have users complain that their extension isn't working properly, because calls won't connect.
What's actually happened, is they're calling people whose line is engaged.
The 3CX Windows client very briefly turns the 'on hook' status area to 'busy', but blink and you'll miss it. Additionally, users are not that observant.
If you then check the call history on the client, it'll show the calls to the busy numbers, however, it doesn't give any indication that these were 'busy' - they look like successfully completed calls.
What I'd like, is to reduce calls to the helpdesk, by making it clear to users that the number they have called is busy, and that there is no fault with the system.
What's actually happened, is they're calling people whose line is engaged.
The 3CX Windows client very briefly turns the 'on hook' status area to 'busy', but blink and you'll miss it. Additionally, users are not that observant.
If you then check the call history on the client, it'll show the calls to the busy numbers, however, it doesn't give any indication that these were 'busy' - they look like successfully completed calls.
What I'd like, is to reduce calls to the helpdesk, by making it clear to users that the number they have called is busy, and that there is no fault with the system.
