Difference between revisions of "Hangupcause Codes"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 200: | Line 200: | ||
<td> 242 </td> | <td> 242 </td> | ||
<td> [[242 No Rates for Reseller|No Rates for Reseller]] </td> | <td> [[242 No Rates for Reseller|No Rates for Reseller]] </td> | ||
</tr> | |||
<tr> | |||
<td> 243 </td> | |||
<td> [[243 Provaider skipped because of CPS limitation]] </td> | |||
</tr> | |||
<tr> | |||
<td> 244 </td> | |||
<td> [[244 Device call aborted because of CPS limitation]] </td> | |||
</tr> | </tr> | ||
</table> | </table> |
Revision as of 11:01, 1 February 2013
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 |
Starting from MOR 12, it is possible to change relation between MOR code and ISDN code. Relation can be defined in mor.conf.