Difference between revisions of "Why call was not routed through other provider/trunk?"
From Kolmisoft Wiki
Jump to navigationJump to search
m |
m |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
1. Check '''[[Call Tracing]]''' – it is possible that other Providers can't handle the call (no rates, not configured properly, not assigned to LCR, etc). | 1. Check '''[[Call Tracing]]''' – it is possible that other Providers can't handle the call (no rates, not configured properly, not assigned to LCR, etc). | ||
2. Check '''STATISTICS –> Calls –> Last Calls''' – check '''Hangup Cause''' for your failed call. If the Hangup Cause is NO ANSWER or BUSY, then MOR does not route the call to the next provider. More details [[NO ANSWER/BUSY interpretation for providers | here]]. | 2. Call hangup cause is not FAILED. (Next provider is used ONLY when call hangup cause is FAILED). Check '''STATISTICS –> Calls –> Last Calls''' – check '''Hangup Cause''' for your failed call. If the Hangup Cause is NO ANSWER or BUSY, then MOR does not route the call to the next provider. More details [[NO ANSWER/BUSY interpretation for providers | here]]. | ||
<br><br> | <br><br> | ||
<br><br> | |||
= See also = | |||
* [[I have a problem with Calls]] | |||
* [[I HAVE A PROBLEM]] | |||
Latest revision as of 03:23, 4 September 2013
If you see that a call was not routed through the second (third/fourth/...) Provider/Trunk, take the following steps:
1. Check Call Tracing – it is possible that other Providers can't handle the call (no rates, not configured properly, not assigned to LCR, etc).
2. Call hangup cause is not FAILED. (Next provider is used ONLY when call hangup cause is FAILED). Check STATISTICS –> Calls –> Last Calls – check Hangup Cause for your failed call. If the Hangup Cause is NO ANSWER or BUSY, then MOR does not route the call to the next provider. More details here.
