Difference between revisions of "Hangupcause Codes"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 100: | Line 100: | ||
<tr> | <tr> | ||
<td> 223 </td> | <td> 223 </td> | ||
<td> Providers call limit reached | <td> [[223 Providers call limit reached | Providers call limit reached]] </td> | ||
</tr> | </tr> | ||
<tr> | <tr> |
Revision as of 11:03, 28 January 2009
MOR application saves hangupcause codes to DB so it is easy to check what was the error and why call failed.
These codes can be seen in calls window (Hangup Cause column) when selected to show 'All', 'Busy', 'No Answer', 'Failed' or 'Missed' calls.
- Standard hangup codes can be found here.
- ISDN Hangup cause codes
MOR specific codes:
Code | Cause |
200 | MOR can't determine who is calling |
201 | User is blocked |
202 | Reseller is blocked |
203 | No rates for user |
204 | No suitable providers found |
205 | MOR PRO not authorized to work on this computer |
206 | server_id is not set in mor.conf file |
207 | Not clear who should receive call |
210 | Balance > 0, but not enough to make call 1s in length |
211 | Low balance for user |
212 | Too low balance for more simultaneous calls |
213 | Low balance for DID owner |
214 | Too low balance for DID owner for more simultaneous calls |
215 | Low balance for reseller |
216 | Too low balance for reseller for more simultaneous calls |
217 | Callback not initiated because device not found by ANI |
218 | Reseller does now allow loss calls |
219 | DID has reached call limit. No more calls allowed to this DID. |
220 | User call limit reached |
221 | Device call limit reached. |
222 | Resellers call limit reached. |
223 | Providers call limit reached |
224 | Provider skipped because his rate is higher then users rate. |
225 | CallerID is banned |
230 | Connection returned error code 0 instead of real code. |
231 | Provider unreachable. |