Solved Busy Tone (and hearing error codes)

[Grant Moxom]

When a user tries to call a number and the call fails for various different reasons (eg busy, or forbidden etc) the call simply ends with no prompt which means it's impossible to know if the call failed, or busy or something else.
I have a similar ticket her that was archived
https://www.3cx.com/community/threads/busy-tone-call-logs-best-practice.81865/#post-378961
I believed that using the new windows client would resolve this - anyone heard anything about this?

 

[ChrisC_3CX]

The new 3CX Desktop app is essentially the 3CX Webclient in a native Windows application so behavior is very similar if not exactly the same.

If you want, you can actually still use the 3CX Windows App (formerly known as the 3CX Phone For Windows) which will show some indication depending on the situation.

For the time being, all I can recommend is upvoting feature requests that describe this behavior such as this one: https://www.3cx.com/community/threa...codes-audio-indication-when-calls-fail.85442/


Note: As mentioned in the previous thread, the only other solution for now is to enable "Play busy Prompt" but that, as you already know, would affect call reports.

 

[Grant Moxom]

Ah gotcha thanks Chris, damn I thought that would have resolved the situation.
And yeah play busy prompt isn't an option sadly. I've upvoted, I hope enough people see that request and upvote it!