FreeSwitch Hangup-Cause电话挂断原因速查
Freeswitch官网太慢了,经常还打不开,把电话挂断原因大全复制一份到这里,方便日常查看
| ITU-T Q.850 Code |
SIP Equiv. | Enumeration | Cause | Description |
|---|---|---|---|---|
| 0 | UNSPECIFIED | Unspecified. No other cause codes applicable. | This is usually given by the router when none of the other codes apply. This cause usually occurs in the same type of situations as cause 1, cause 88, and cause 100. | |
| 1 | 404 | UNALLOCATED_NUMBER | Unallocated (unassigned) number [Q.850 value 1] | This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated (assigned). |
| 2 | 404 | NO_ROUTE_TRANSIT_NET | No route to specified transit network (national use) [Q.850] | This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network, which it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network, while it does exist, does not serve the equipment which is sending this cause. |
| 3 | 404 | NO_ROUTE_DESTINATION | No route to destination [Q.850] | This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network dependent basis. |
| 6 | CHANNEL_UNACCEPTABLE | channel unacceptable [Q.850] | This cause indicates that the channel most recently identified is not acceptable to the sending entity for use in this call. | |
| 7 | CALL_AWARDED_DELIVERED | call awarded, being delivered in an established channel [Q.850] | This cause indicates that the user has been awarded the incoming call, and that the incoming call is being connected to a channel already established to that user for similar calls (e.g. packet-mode x.25 virtual calls). | |
| 16 | NORMAL_CLEARING | normal call clearing [Q.850] | This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network. | |
| 17 | 486 | USER_BUSY | user busy [Q.850] | This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy it is noted that the user equipment is compatible with the call. |
| 18 | 408 | NO_USER_RESPONSE | no user responding [Q.850] | This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated. |
| 19 | 480 | NO_ANSWER | no answer from user (user alerted) [Q.850] | This cause is used when the called party has been alerted but does not respond with a connect indication within a prescribed period of time. Note - This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers. |
| 20 | 480 | SUBSCRIBER_ABSENT | subscriber absent [Q.850] | This cause value is used when a mobile station has logged off, radio contact is not obtained with a mobile station or if a personal telecommunication user is temporarily not addressable at any user-network interface. Sofia SIP will normally raise USER_NOT_REGISTERED in such situations. |
| 21 | 603 | CALL_REJECTED | call rejected [Q.850] | This cause indicates that the equipment sending this cause does not wish to accept this call, although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible. The network may also generate this cause, indicating that the call was cleared due to a supplementary service constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection. |
| 22 | 410 | NUMBER_CHANGED | number changed [Q.850] | This cause is returned to a calling party when the called party number indicated by the calling party is no longer assigned, The new called party number may optionally be included in the diagnostic field. If a network does not support this cause, cause no: 1, unallocated (unassigned) number shall be used. |
| 23 | 410 | REDIRECTION_TO_NEW_DESTINATION | This cause is used by a general ISUP protocol mechanism that can be invoked by an exchange that decides that the call should be set-up to a different called number. Such an exchange can invoke a redirection mechanism, by use of this cause value, to request a preceding exchange involved in the call to route the call to the new number. | |
| 25 | 483 | EXCHANGE_ROUTING_ERROR | This cause indicates that the destination indicated by the user cannot be reached, because an intermediate exchange has released the call due to reaching a limit in executing the hop counter procedure. This cause is generated by an intermediate node, which when decrementing the hop counter value, gives the result 0. | |
| 27 | 502 | DESTINATION_OUT_OF_ORDER | destination out of order [Q.850] | This cause indicates that the destination indicated by the user cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signal message was unable to be delivered to the remote party; e.g. a physical layer or data link layer failure at the remote party, or user equipment off-line. |
| 28 | 484 | INVALID_NUMBER_FORMAT | invalid number format (address incomplete) [Q.850] | This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete. |
| 29 | 501 | FACILITY_REJECTED | facilities rejected [Q.850] | This cause is returned when a supplementary service requested by the user cannot be provide by the network. |
| 30 | RESPONSE_TO_STATUS_ENQUIRY | response to STATUS INQUIRY [Q.850] | This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receipt of a STATUS INQUIRY. | |
| 31 | 480 | NORMAL_UNSPECIFIED | normal, unspecified [Q.850] | This cause is used to report a normal event only when no other cause in the normal class applies. |
| 34 | 503 | NORMAL_CIRCUIT_CONGESTION | no circuit/channel available [Q.850] | This cause indicates that there is no appropriate circuit/channel presently available to handle the call. |
| 38 | 502 | NETWORK_OUT_OF_ORDER | network out of order [Q.850] | This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time e.g. immediately re-attempting the call is not likely to be successful. |
| 41 | 503 | NORMAL_TEMPORARY_FAILURE | temporary failure [Q.850] | This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g. the user may wish to try another call attempt almost immediately. |
| 42 | 503 | SWITCH_CONGESTION | switching equipment congestion [Q.850] | This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic. |
| 43 | ACCESS_INFO_DISCARDED | access information discarded [Q.850] | This cause indicates that the network could not deliver access information to the remote user as requested, i.e. user-to-user information, low layer compatibility, high layer compatibility or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic. | |
| 44 | 503 | REQUESTED_CHAN_UNAVAIL | requested circuit/channel not available [Q.850] | This cause is returned when the other side of the interface cannot provide the circuit or channel indicated by the requesting entity. |
| 45 | PRE_EMPTED | |||
| 47 | resource unavailable, unspecified [Q.850] | This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies. | ||
| 50 | FACILITY_NOT_SUBSCRIBED | requested facility not subscribed [Q.850 | This cause indicates that the user has requested a supplementary service, which is available, but the user is not authorized to use. | |
| 52 | 403 | OUTGOING_CALL_BARRED | outgoing calls barred | This cause indicates that although the calling party is a member of the CUG for the outgoing CUG call, outgoing calls are not allowed for this member of the CUG. |
| 54 | 403 | INCOMING_CALL_BARRED | incoming calls barred | This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed to this member of the CUG. |
| 57 | 403 | BEARERCAPABILITY_NOTAUTH | bearer capability not authorized [Q.850] | This cause indicates that the user has requested a bearer capability that is implemented by the equipment which generated this cause but the user is not authorized to use. |
| 58 | 503 | BEARERCAPABILITY_NOTAVAIL | bearer capability not presently available [Q.850] | This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time. |
| 63 | SERVICE_UNAVAILABLE | service or option not available, unspecified [Q.850] | This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies. | |
| 65 | 488 | BEARERCAPABILITY_NOTIMPL | bearer capability not implemented [Q.850] | This cause indicates that the equipment sending this cause does not support the bearer capability requested. |
| 66 | CHAN_NOT_IMPLEMENTED | channel type not implemented [Q.850] | This cause indicates that the equipment sending this cause does not support the channel type requested | |
| 69 | 501 | FACILITY_NOT_IMPLEMENTED | requested facility not implemented [Q.850] | This cause indicates that the equipment sending this cause does not support the requested supplementary services. |
| 79 | 501 | SERVICE_NOT_IMPLEMENTED | service or option not implemented, unspecified [Q.850] | This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies. |
| 81 | INVALID_CALL_REFERENCE | invalid call reference value [Q.850] | This cause indicates that the equipment sending this cause has received a message with a call reference which is not currently in use on the user-network interface. | |
| 88 | 488 | INCOMPATIBLE_DESTINATION | incompatible destination [Q.850] | This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility, high layer compatibility or other compatibility attributes (e.g. data rate) which cannot be accommodated. |
| 95 | INVALID_MSG_UNSPECIFIED | invalid message, unspecified [Q.850] | This cause is used to report an invalid message event only when no other cause in the invalid message class applies. | |
| 96 | MANDATORY_IE_MISSING | mandatory information element is missing [Q.850] | This cause indicates that the equipment sending this cause has received a message which is missing an information element which must be present in the message before that message can be processed. | |
| 97 | MESSAGE_TYPE_NONEXIST | message type non-existent or not implemented [Q.850] | This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined of defined but not implemented by the equipment sending this cause. | |
| 98 | WRONG_MESSAGE | message not compatible with call state or message type non-existent or not implemented. [Q.850] | This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the call state, or a STATUS message was received indicating an incompatible call state. | |
| 99 | IE_NONEXIST | Information element / parameter non-existent or not implemented [Q.850] | This cause indicates that the equipment sending this cause has received a message which includes information element(s)/parameter(s) not recognized because the information element(s)/parameter name(s) are not defined or are defined but not implemented by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message. | |
| 100 | INVALID_IE_CONTENTS | Invalid information element contents [Q.850] | This cause indicates that the equipment sending this cause has received and information element which it has implemented; however, one or more fields in the I.E. are coded in such a way which has not been implemented by the equipment sending this cause. | |
| 101 | WRONG_CALL_STATE | message not compatible with call state [Q.850] | This cause indicates that a message has been received which is incompatible with the call state. | |
| 102 | 504 | RECOVERY_ON_TIMER_EXPIRE | recovery on timer expiry [Q.850] | This cause indicates that a procedure has been initiated by the expiration of a timer in association with error handling procedures. This is often associated with NAT problems. Ensure that "NAT Mapping Enable" is turned on in your ATA. If it is not NAT related it can sometimes be provider related, make sure to ensure another outbound provider does not solve the problem.
FreeSWITCH also returns this when the remote party sends a 408 for call expired. |
| 103 | MANDATORY_IE_LENGTH_ERROR | parameter non-existent or not implemented - passed on (national use) [Q.850] | This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending this cause. The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed unchanged. | |
| 111 | PROTOCOL_ERROR | protocol error, unspecified [Q.850] | This cause is used to report a protocol error event only when no other cause in the protocol error class applies. | |
| 127 | INTERWORKING | Interworking, unspecified [Q.850] | This cause indicates that an interworking call (usually a call to SW56 service) has ended. | |
| 487 | 487 | ORIGINATOR_CANCEL | ||
| 500 | CRASH | |||
| 501 | SYSTEM_SHUTDOWN | |||
| 502 | LOSE_RACE | |||
| 503 | MANAGER_REQUEST | This cause is used when you send an api command to make it hangup. For example uuid_kill <uuid> | ||
| 600 | BLIND_TRANSFER | |||
| 601 | ATTENDED_TRANSFER | |||
| 602 | ALLOTTED_TIMEOUT | This cause means that the server canceled the call because the destination channel took too long to answer. | ||
| 603 | USER_CHALLENGE | |||
| 604 | MEDIA_TIMEOUT | |||
| 605 | PICKED_OFF | This cause means the call was picked up by intercepting it from another extension (i.e. dialing **ext_number from another extension). | ||
| 606 | USER_NOT_REGISTERED | This means you tried to originate a call to a SIP user who forgot to register. | ||
| 607 | PROGRESS_TIMEOUT | See: progress_timeout | ||
| 609 | GATEWAY_DOWN | Gateway is down (not answering on OPTIONS or SUBSCRIBE) |
参考链接:https://freeswitch.org/confluence/display/FREESWITCH/Hangup+Cause+Code+Table
FreeSwitch Hangup-Cause电话挂断原因速查的更多相关文章
- Android7.0 Phone应用源码分析(四) phone挂断流程分析
电话挂断分为本地挂断和远程挂断,下面我们就针对这两种情况各做分析 先来看下本地挂断电话的时序图: 步骤1:点击通话界面的挂断按钮,会调用到CallCardPresenter的endCallClicke ...
- android 接听和挂断实现方式
参考:android 来电接听和挂断 支持目前所有版本 注意:android2.3版本及以上不支持下面的自动接听方法. (会抛异常:java.lang.SecurityException: Neith ...
- 三星S4接电话黑屏无法挂断通话
最近发现S4的通话距离感应起出了问题,接电话后直接熄屏,按什么按钮都没有反应.通话结束后只能等对方挂断才会恢复正常,再或者长按9秒电源键强制重启.极大的影响了实用体验.网上搜了下,发现这样的问题还不少 ...
- Android 对电话进行监听和挂断
1.添加权限 <!--拨打电话的权限--><uses-permission android:name="android.permission.PROCESS_OUTGOIN ...
- Android开发之通过反射获取到挂断电话的API
Android开发黑名单工具类,需要用到挂断电话的API,但是该API处于隐藏状态,需要通过反射得到该方法.. 步骤: 1.通过当前类获取到ServiceManager的字节码 Class< ? ...
- Android 电话自己主动接听和挂断具体解释
1.通过aidl及反射实现挂断电话 详细分三步: (1)ITelephony.aidl ,必须新建com.android.internal.telephony包并放入ITelephony.aidl文件 ...
- Android接听、挂断电话
新建一个名为ITelephony的aidl文件,注意包名不能改变,因为是通过反射方式来实现接听和挂断的
- iOS监听电话来电、挂断、拨号等
以下,来讲解在app内如何调用打电话功能和监听电话来电.挂断.拨号等功能. 简单的UI布局: 首先,先实现拨打电话的功能,以便于后续测试: // 拨打电话 - (IBAction)dialingBut ...
- 挂断电话demo
<!-- 结束通话和打电话的权限 --> <uses-permission android:name="android.permission.CALL_PHONE" ...
- freeswitch 挂断前执行脚本
通道变量名 api_hangup_hook 介绍在挂断时执行指定API命令 示例 <action application="set" data="api_hangu ...
随机推荐
- 细节解析 JavaScript 中 bind 函数的模拟实现
大家的阅读是我发帖的动力,本文首发于我的博客:deerblog.gu-nami.com/,欢迎大家来玩,转载请注明出处喵. 前言 bind是一个改变函数this指针指向的一个常用函数,经常用在涉及th ...
- Java---实现文件拷贝
直接上代码: package com.zjw.file; import java.io.BufferedInputStream; import java.io.BufferedOutputStream ...
- Java Annotation认知(包括框架图、详细介绍、示例说明)--转载
转载地址:https://www.cnblogs.com/skywang12345/p/3344137.html
- 代码随想录第十天 | Leecode 232. 用栈实现队列、Leecode 225. 用队列实现栈、 Leecode 20. 有效的括号、Leecode 1047. 删除字符串中的所有相邻重复项
Leecode 232. 用栈实现队列 题目链接:https://leetcode.cn/problems/implement-queue-using-stacks/submissions/ 题目描述 ...
- 代码随想录第一天 | Leecode 704 二分查找、27 移除元素、977 有序数组的平方
前言 今天是我开始刷Leecode的第一天,同时这也是开通博客园第一篇博客.我希望能在每篇博客中记录下我做出每一道题的过程,为此我想先说明一下我的博客内容的结构. 题目描述:首先说明题目的要求以及测试 ...
- 提高Flutter应用性能的最佳实践
@charset "UTF-8"; .markdown-body { line-height: 1.75; font-weight: 400; font-size: 15px; o ...
- Django踩坑之django.core.exceptions.ImproperlyConfigured mysqlclient 1.3.13 or newer is required; you have 0.9.3.
安装Django3后不想折腾mysqlclient那堆库文件,直接装了pymysql替代mysqlclient,报错:django.core.exceptions.ImproperlyConfigur ...
- 一个大对象引起的血案,GC的踩坑实录
背景: 问题: 有个渠道支付服务,负责与所有支付相关服务进行交互,包括 渠道下单支付,渠道成功通知,渠道的对账等 服务4台机,平时跑的都很稳定,通过thrift进行对外提供服务,且平时并未发现访问 ...
- python学习思维导图分享
python 本文包含了我的一些python学习的笔记和思维导图 第一部分:python基础 导图下载链接 第二部分:函数及其他文件操作 导图下载链接 第三部分:类及网络编程 导图下载链接 第四部分: ...
- Spring扩展接口-BeanFactoryPostProcessor
.markdown-body { line-height: 1.75; font-weight: 400; font-size: 16px; overflow-x: hidden; color: rg ...