NO ANSWER/BUSY interpretation for providers

By default NO ANSWER or BUSY call end disposition is counted as call end after which there is no meaning to try to dial same destination again because destination is not answering (NO ANSWER) or is currently busy (BUSY).

And if we have several Providers in our LCR - call ends after we receive NO ANSWER or BUSY from some Provider and our routing ends.

This is ok for ideal world where all Providers follow standards and sends correct call end codes, e.g.:

• NO ANSWER when calls is not answered after some period (timeout),
• BUSY when recipient is busy (talking with somebody else)
• ANSWERED when call was answered and ended
• FAILED when some error happened

Sometimes Providers cheat. For example they can't deliver call to some destination due to some problem in their network or similar. Then they send NO ANSWER or BUSY signal for FAILED call. And then our routing breaks. If we have several more Providers in our LCR - our LCR will not try to send call over remaining Providers and will and the call.

This often happens for GREY (illegal) routes. For more details see: False ANSWER

To partly solve this problem MOR provides workaround as "NO ANSWER/BUSY interpretation for providers".

It lets to set NO ANSWER or/and BUSY interpretation as FAILED.

That means - if Provider reports NO ANSWER or/and BUSY - MOR treats this as FAILED and next Provider in LCR (if there is/are more) is tried to send call.

These options can be set in Providers Settings: