Is this a 3CX Message? “Your call cannot be completed as dialed. Please check the number and dial again. Message 0143”

[ITAdmin]

Sometimes, when a caller is calling in, they are hearing the following: “Your call cannot be completed as dialed. Please check the number and dial again. Message 0143”. More times than not, if the caller will call back in, they will get through to our system and someone will answer the call.

Is this a message being generated by 3CX?

My environment:

• 3CX Version: 16.0.493
• Server OS, Windows 10 Pro
• Is the 3CX Server Hosted and where? No
• IP Phone Make/Model/Firmware: Grandstream GXP2135, 1.0.11.3
• Provisioning Method: Local
• Trunk Provider or Gateway Make/Model: DIDLogic
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: YES

Thanks for your help

 

[leejor]

That sounds like a provider message. The tag...0143, should help identify the origination. May be your provider (less likely) , or the originators, or the PSTN network the call is passing through.

 

[ITAdmin]

Thanks. Do you have any idea how I can do that? I have contacted both of the providers involved ( AT&T and DIDLogic ). So far, no one will acknowledge it is their message.

But it does sound like the message is not coming from 3CX, so that's good.

 

[leejor]

Make note of when this happens. Check the Activity log to be certain that you did not receive a call, that was rejected. Then check with your provider to see if they have any record of the failed calls, if it even made it to them.
Is there any pattern in the originations?

 

[ITAdmin]

Not that I can tell. I have been running Wireshark and looking at the Call Logs, but I can not seem to find anything. I don't think the call is making it to us, but I am still working on it.

 

[YiannisH_3CX]

Hello @ITAdmin

This is not a 3CX generated prompt which most probably means that the call is not hitting 3CX. I would recommend gathering some information about the providers the callers are using when making the calls since this might be coming from them. Try to see if the issue revolves around a specific origination provider.

 

[ITAdmin]

Thanks for confirming. We are currently in the process of doing that. This thread can be closed.