Can 3CX display SIP response info?

[jakorsme]

In the log I see that our dropped outbound calls are returning a SIP POP response code of 404 (Disconnected/not in service) or 500 level errors like Busy.
But in the web client, the connection just drops after maybe 15 seconds of silence. No indication of why in the web client.

Id there some 3CX configuration I need to add or change so the SIP response codes or better yet, a description is displayed to the caller, so they know why their call failed?

If I call on my cell phone for instance I get a recording saying "this number has been disconnected or is no longer in service"

 

[Evolute IT]

In the log I see that our dropped outbound calls are returning a SIP POP response code of 404 (Disconnected/not in service) or 500 level errors like Busy.
But in the web client, the connection just drops after maybe 15 seconds of silence. No indication of why in the web client.

Id there some 3CX configuration I need to add or change so the SIP response codes or better yet, a description is displayed to the caller, so they know why their call failed?

If I call on my cell phone for instance I get a recording saying "this number has been disconnected or is no longer in service"

The message played would be from your provider. Some, however, sends a 404 and the PBX just drops the call. A deskphone would show it, so do the logs and event logs.

That being said, the Webclient doesn't show the error message as far as I know. Mobile apps will if the message is one of the common ones like 404, 406 and such.

 

[jakorsme]

That's what I was afraid of. Seems like a pretty glaring omission from the webapp. A sales rep not being able to distinguish between a busy phone and a phone number no longer in service. I hope 3CX fixes that.