Difference between revisions of "Why call was not routed through other provider/trunk?"

From Kolmisoft Wiki
Jump to navigationJump to search
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 it 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. 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]].

Revision as of 01:30, 16 May 2010

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. 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.