3cx client drops call on busy / wrong number

[Alexandre Takacs]

Hello

Running a 15.5 SP 6 setup here with good success.

One annoyance we have is with the 3cx client (windows) when there is an exception in an outgoing call - either the destination busy or a wrong number entered.

In those cases the client "simply" drops the call immediately. No error reported, no audible signal - just gives up.

The logs show

Call or Registration to 02131****@(Ln.10002@****) has failed.
***.***.80.5 replied: 486 Busy Here [Call processing released]; from IP:***.***.80.5:5060​

or

Call or Registration to +08481*****@(Ln.10002@****) has failed.
***.***.80.5 replied: 500 INTERNAL SERVER ERROR; from IP:***.***:5060​

Are we missing something here ? Suggestions ?

 

[Markus Schröder]

I was told this should be a normal behavior. The error message will be displayed for one to two seconds. You didn't hear anything. My customers use TAPI and Jabra-Headset, the Softphone is in background and they are confused. They are really angry about that. Support told me: the Busyton should "allegedly" generated by the SIP phone, 3cx-Client does not by design. In fact, depending on which Hardware-Phone I use, the StatusCode is mostly implemented with a Busytone and display the error message. However, none of the phones waived the Busytone and a legible representation until you hang up the phone.

It coudn't be difficult to implement something like a busytone and not to autoclose the call, then you can also see the status text longer.

The absolute highlight would be if the 3CX server could play the status codes as an announcement on softphone, DECT and VOIP phone. For example "The subscriber is not available" or "This number is unknown".

The support told me that i could do a feature-request or let's see if there is not such a one and vote for it - I am still searching ;-)

.

 

[Alexandre Takacs]

Hmm... I muss say that this is rather annoying. Are we the only one bitching here ?

 

[Markus Schröder]

see: https://www.3cx.com/community/threads/play-busy-tone-when-line-is-busy.59039
or: https://www.3cx.com/community/threa...ork-when-the-phone-is-busy.58006/#post-243220

 

[Alexandre Takacs]

thanks for those pointers - it would seem that this is up to the client app to implement. I'm surprised 3cx did not bother to date to have this working - doesn't seem too hard.