Difference between revisions of "Hangupcause Codes"
From Kolmisoft Wiki
Jump to navigationJump to search
(8 intermediate revisions by 2 users not shown) | |||
Line 15: | Line 15: | ||
<td> <b>Code</b> </td> | <td> <b>Code</b> </td> | ||
<td> <b>Cause</b> </td> | <td> <b>Cause</b> </td> | ||
</tr> | |||
<tr> | |||
<td> 18 </td> | |||
<td> [[Cause No. 18 - no user responding | no user responding]]</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 23: | Line 27: | ||
<td> 34 </td> | <td> 34 </td> | ||
<td> [[34 no circuit/channel available | no circuit/channel available]]</td> | <td> [[34 no circuit/channel available | no circuit/channel available]]</td> | ||
</tr> | |||
<tr> | |||
<td> 41 </td> | |||
<td> [[41 temporary failure | temporary failure]]</td> | |||
</tr> | |||
<tr> | |||
<td> 58 </td> | |||
<td> [[58 - Bearer capability not presently available | Bearer capability not presently available]]</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 95: | Line 107: | ||
<tr> | <tr> | ||
<td> 211 </td> | <td> 211 </td> | ||
<td> [[211 Low balance for user | Low balance for user]] | <td> [[211 Low balance for user | Low balance for user]]</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
Line 401: | Line 413: | ||
<td> 287</td> | <td> 287</td> | ||
<td> [[287 Low balance for Device | Low balance for Device]] </td> | <td> [[287 Low balance for Device | Low balance for Device]] </td> | ||
</tr> | |||
<tr> | |||
<td> 288</td> | |||
<td> [[288 Reseller inbound call limit reached | Reseller inbound call limit reached]] </td> | |||
</tr> | |||
<tr> | |||
<td> 289</td> | |||
<td> [[289 Provider's rate is higher than max allowed rate in Flat-Rates | Provider's rate is higher than max allowed rate in Flat-Rates]] </td> | |||
</tr> | |||
<tr> | |||
<td> 290</td> | |||
<td> [[290 Daily Balance Limit reached | Daily Balance Limit reached]] </td> | |||
</tr> | </tr> | ||
</table> | </table> |
Latest revision as of 07:00, 8 July 2024
MOR application saves hangupcause codes (HGC in MOR terminology) to the database, so it is easy to check what the error was and why the call failed.
These codes can be seen in the Calls window (Hangup Cause column) when selected to show 'All', 'Busy', 'No Answer', 'Failed' or 'Missed' calls.
- Standard hangup codes can be found here.
- ITU-T Q.850 Codes Link2 Link3
- SIP Response Codes
Standard codes
Code | Cause |
18 | no user responding |
20 | subscriber absent |
34 | no circuit/channel available |
41 | temporary failure |
58 | Bearer capability not presently available |
102 | Recovery on timer expiry |
SIP Response Codes
Code | Cause |
487 | Request Terminated by bye or cancel |
MOR specific codes
Relation between MOR hangupcause codes and Standard codes
This table describes which standard ISDN code is MOR giving when one or another hangupcause is given.
MOR code | ISDN code | SIP code |
208 | 34 | 503 Service unavailable |
210 | 34 | 503 Service unavailable |
211 | 34 | 503 Service unavailable |
212 | 34 | 503 Service unavailable |
213 | 34 | 503 Service unavailable |
214 | 34 | 503 Service unavailable |
215 | 34 | 503 Service unavailable |
216 | 34 | 503 Service unavailable |
219 | 34 | 503 Service unavailable |
220 | 34 | 503 Service unavailable |
221 | 34 | 503 Service unavailable |
222 | 34 | 503 Service unavailable |
223 | 34 | 503 Service unavailable |
226 | 1 | 404 Not found |
229 | 1 | 404 Not found |
233 | 66 | 500 Internal server error |
All others not listed above and greater than 199 ( >=200 ) | 21 | 403 Forbidden |
Starting from MOR 12, it is possible to change relation between MOR code and ISDN code. Relation can be defined in mor.conf.