Unwanted behavior on outgoing calls

Once I make an outgoing call, the destination is ringing and the recipient doesn’t want to answer my call (pushes me to dnd), my pbx uses my next available trunk to continue the ongoing call. The recipient has to drop the call a second time.
This is a unwanted behavior of my pbx. Once a call is rejected, it should get a reject/dnd and give up instead of trying to continue the call via the next trunk.
Where can I change this setting? In extension settings or outbound-route settings?

Which channel technology are you using? If SIP (either chan_pjsip, or chan_pjsip), what is the SIP status code, and any status code returned in the rejection?

Whilst I think Asterisk is weak in handling “busy everywhere” responses, if you have fallback trunks, it can only go by the response it receives, and, if it cannot distinguish between that being due to a network problem, and an end user rejection, it will not be able to both provide alternative trunks, and provider your requested behaviour. Therefore, we need to know whether there is enough information to distinguish the two cases, before we even try to think how to handle the busy everywhere case.

It’s pjsip only. See also manipulated screenshot of the CDR. An yes, I can see the problem. Once a trunk is not available or his max number of lines are occupied, the next available trunk should be used. Trunks in screenshot are called ‘AnlagenA’ and ‘Telekom200’.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.