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

From Kolmisoft Wiki
Jump to navigationJump to search
(New page: If you see that call was not routed through second (third/fourth/...) Provider/Trunk then do following steps: 1. Check '''Call Tracing''' - it is possible that other Providers can't handl...)
 
Line 1: Line 1:
If you see that call was not routed through second (third/fourth/...) Provider/Trunk then do following steps:
If you see that call was not routed through second (third/fourth/...) Provider/Trunk then do 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)
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 you failed call. If it is NO ANSWER or BUSY then MOR does not route call to next Provider. More details [[NO ANSWER/BUSY interpretation for providers | here]].
2. Check '''STATISTICS - Calls - Last Calls''' - check '''Hangup Cause''' for you failed call. If it is NO ANSWER or BUSY then MOR does not route call to next Provider. More details [[NO ANSWER/BUSY interpretation for providers | here]].

Revision as of 09:47, 29 September 2009

If you see that call was not routed through second (third/fourth/...) Provider/Trunk then do 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 you failed call. If it is NO ANSWER or BUSY then MOR does not route call to next Provider. More details here.