Notify Caller of Busy 480, 486 & 603 etc Responses

[roadwings]

Running V15, with Yealink T38, T46 & T48.

Issue: Someone dials an external number and the destination is busy, it might be a bad number, or disconnected. The callers are not notified, they hear no response in the handset and see no notice on the phone. Is this normal? How does the system notify the caller that something is wrong so that they quit redialing constantly and thinking the error is on our side?

Is this something regarding the trunk setup or phone provisioning?

 

[PhatPanda]

Excellent question, I've been wondering the same myself, mixture of Yealink and Fanvil phones here.

 

[nb]

You should get a busy tone just like we get when we call a non existing number.
Or there are prompts you can enable that are played when destination is busy - but if you do not get the busy tone, then we will not know that we have to play the prompt.

You need to check with Wireshark or the logging to see what the provider or gateways are sending.

This is a traditional issue of gateways with incorrect tonesets configured (or configured with tone sets of other countries)

Example in UK toneset for busy should be 400 Hz.
But in US it is different.
But gateway is in us configured with UK Toneset - so gateway should get 400 Hz to understand that it is busy, but this will not happen by the telco in the US - So you never get the busy signal.

Something along these lines..