Difference between revisions of "NO ANSWER/BUSY interpretation for providers"

From Kolmisoft Wiki
Jump to navigationJump to search
m
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
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).
This option is applied to the call LegB.


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.
By default, the '''NO ANSWER''' or '''BUSY''' call end disposition is counted as the end of a call. After this, it is pointless to try to dial the same destination again, because the destination is not answering (NO ANSWER) or is currently busy (BUSY).


This is ok for ideal world where all Providers follow standards and sends correct call end codes, e.g.:
If we have several providers in our LCR, the call ends after we receive NO ANSWER or BUSY from a provider, and our routing ends.


* NO ANSWER when calls is not answered after some period (timeout),  
This is okay for an ideal world in which all providers follow standards and send the correct call end codes, e.g.:
* 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.
* NO ANSWER when calls are not answered after a certain period (timeout).
* BUSY when a recipient is busy (talking with somebody else).
* ANSWERED when a call has been answered and ends.
* FAILED when an error occurs.
 
However, providers sometimes cheat (or do not have the technical skills to make this correctly). For example, if they can't deliver a call to a destination because of some problem in their network or something similar, they may send the NO ANSWER or BUSY signal for a FAILED call. And then our routing breaks. If we have several more providers in our LCR, our LCR will not try to send calls over to the remaining providers and will end the call.


This often happens for GREY (illegal) routes.  
This often happens for GREY (illegal) routes.  


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


It lets to set NO ANSWER or/and BUSY interpretation as FAILED.
This makes it possible to set a NO ANSWER and/or 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.
That means, if a provider reports NO ANSWER and/or BUSY, MOR treats this as FAILED and the next provider in LCR (if there are further providers) is tried to send the call.


These options can be set in Providers Settings:
These options can be set in Providers Settings:
Line 24: Line 26:
[[Image:noanswer_busy_interpretation.png]]
[[Image:noanswer_busy_interpretation.png]]


'''It is advised to use these settings ONLY and ONLY on confirmed cheating Providers. That means - these settings should be 'NO' for most of the time.'''
'''It is advised to use these settings ONLY and ONLY on confirmed cheating/misconfigured providers. That is, these settings should usually be 'NO'.'''
 


----


Related pages:
<br><br>
=See also=


* [[Why call was not routed through other provider/trunk?]]
* [[Why call was not routed through other provider/trunk?|Why was a call not routed through another provider/trunk?]]
* [[* button does not work]]

Latest revision as of 14:10, 14 October 2021

This option is applied to the call LegB.

By default, the NO ANSWER or BUSY call end disposition is counted as the end of a call. After this, it is pointless to try to dial the same destination again, because the destination is not answering (NO ANSWER) or is currently busy (BUSY).

If we have several providers in our LCR, the call ends after we receive NO ANSWER or BUSY from a provider, and our routing ends.

This is okay for an ideal world in which all providers follow standards and send the correct call end codes, e.g.:

  • NO ANSWER when calls are not answered after a certain period (timeout).
  • BUSY when a recipient is busy (talking with somebody else).
  • ANSWERED when a call has been answered and ends.
  • FAILED when an error occurs.

However, providers sometimes cheat (or do not have the technical skills to make this correctly). For example, if they can't deliver a call to a destination because of some problem in their network or something similar, they may send the NO ANSWER or BUSY signal for a FAILED call. And then our routing breaks. If we have several more providers in our LCR, our LCR will not try to send calls over to the remaining providers and will end the call.

This often happens for GREY (illegal) routes.

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

This makes it possible to set a NO ANSWER and/or BUSY interpretation as FAILED.

That means, if a provider reports NO ANSWER and/or BUSY, MOR treats this as FAILED and the next provider in LCR (if there are further providers) is tried to send the call.

These options can be set in Providers Settings:

Noanswer busy interpretation.png

It is advised to use these settings ONLY and ONLY on confirmed cheating/misconfigured providers. That is, these settings should usually be 'NO'.




See also

Retrieved from "https://wiki.kolmisoft.com/index.php?title=NO_ANSWER/BUSY_interpretation_for_providers&oldid=26801"