Difference between revisions of "Hangupcause Codes"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 187: | Line 187: | ||
<tr> | <tr> | ||
<td> 239 </td> | <td> 239 </td> | ||
<td> [[239 | <td> [[239 Device used its daily call time limit| Device used its daily call time limit]] </td> | ||
</tr> | |||
<tr> | |||
<td> 240 </td> | |||
<td> [[240 Provider belongs to the User which makes call| Provider belongs to the User which makes call]] </td> | |||
</tr> | </tr> | ||
</table> | </table> |
Revision as of 18:19, 8 May 2012
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.
- ISDN Hangup cause codes
Standard codes
Code | Cause |
34 | no circuit/channel available |
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 |