Android Call disconnected reason

1 Normal class

1.1 Cause No. 1 "unassigned (unallocated) number"(未分配的号码)

This cause indicates that the destination requested by the mobile station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).

1.2 Cause No. 3 "no route to destination"(目的地无路由)

This cause indicates that the called user cannot be reached because the network through which the call has been routed does not serve the destination desired.

1.3 Cause No. 6 "channel unacceptable"(信道无法接受)

This cause indicates the channel most recently identified is not acceptable to the sending entity for use in this call.

1.4 Cause No. 8 "operator determined barring"(操作者定义禁止)

This cause indicates that the MS has tried to access a service that the MS's network operator or service provider is not prepared to allow.

1.5 Cause No.16 "normal call clearing"(正常的呼叫清除)

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.

1.6 Cause No.17 "user busy"(用户忙)

This cause is used when the called user has indicated the inability to accept another call.

It is noted that the user equipment is compatible with the call.

1.7 Cause No. 18 "no user responding"(用户无响应)

This cause is used when a user does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated (defined by the expiry of either timer T303 or T310).

1.8 Cause No. 19 "user alerting, no answer"(用户振铃,无应答)

This cause is used when a user has provided an alerting indication but has not provided a connect indication within a prescribed period of time.

1.9 Cause No. 21 "call rejected"(呼叫拒绝)

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.

1.10 Cause No. 22 "number changed"(号码变换)

This cause is returned to a calling mobile station when the called party number indicated by the calling mobile station is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this capability, cause No. 1 "unassigned (unallocated) number" shall be used.

1.11 Cause No. 26 "non-selected user clearing"(未选择的用户清除)

Not supported. Treated as cause no. 31.

1.12 Cause No. 27 "destination out of order"(目的端命令超出)

This cause indicates that the destination indicated by the mobile station cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

1.13 Cause No. 28 "invalid number format (incomplete number)"(非法的号码格式(不完整的号码)

This cause indicates that the called user cannot be reached because the called party number is not a valid format or is not complete.

1.14 Cause No. 29 "facility rejected"(设备拒绝)

This cause is returned when a facility requested by user can not be provided by the network.

1.15 Cause No. 30 "response to STATUS ENQUIRY"(响应STATUS ENQUIRY)

This cause is included in STATUS messages if the message is sent in response to a STATUS ENQUIRY message. See also section 5.5.3.

1.16  Cause No. 31 "normal, unspecified"(一般,未定义)

This cause is used to report a normal event only when no other cause in the normal class applies.

2 Resource unavailable class

2.1 Cause No. 34 "no circuit/channel available"(无电路/信道可用)

This cause indicates that there is no appropriate circuit/channel presently available to handle the call.

2.2 Cause No. 38 "network out of order"(网络命令超出)

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.

2.3 Cause No. 41 "temporary failure"(临时失败)

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 mobile station may wish to try another call attempt almost immediately.

2.4 Cause No. 42 "switching equipment congestion"(交换设备拥塞)

This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.

2.5 Cause No. 43 "access information discarded"(接入信息丢弃)

This cause indicates that the network could not deliver access information to the remote user as requested; i.e., a 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.

2.6 Cause No. 44 "requested circuit/channel not available"(请求的电路/信道不可用)

This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.

2.7 Cause No. 47 "resource unavailable, unspecified"(资源不可用,未定义)

This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.

3 Service or option not available class

3.1 Cause No. 49 "quality of service unavailable"(业务质量(QOS)不可用)

This cause indicates to the mobile station that the requested quality of service, as defined in CCITT Recommendation X.213, cannot be provided.

3.2 Cause No. 50 "Requested facility not subscribed"(请求的设备未预定)

This cause indicates that the requested supplementary service could not be provided by the network because the user has no completed the necessary administrative arrangements with its supporting networks.

3.3 Cause No. 55 "Incoming calls barred within the CUG"(在CUG中来话禁止)

This cause indicates that although the called party is a member of the CUG for the incoming CUG call, incoming calls are not allowed within this CUG.

3.4 Cause No. 57 "bearer capability not authorized"(承载能力未授权)

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but the mobile station is not authorized to use.

3.5 Cause No. 58 "bearer capability not presently available"(承载能力当前不可用)

This cause indicates that the mobile station has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time.

3.6 Cause No. 63 "service or option not available, unspecified"(业务或选件不可用,未定义)

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.

3.7 Cause No. 68 "ACM equal to or greater than ACMmax"(ACM大于等于ACM最大值)

This cause is used by the mobile to indicate that call clearing is due to ACM (累计呼叫次数)being greater than or equal to ACMmax.

4 Service or option not implemented class

4.1 Cause No. 65 "bearer service not implemented"(承载业务无法实现)

This cause indicates that the equipment sending this cause does not support the bearer capability requested.

4.2 Cause No. 69 "Requested facility not implemented"(请求的设备不可执行)

This cause indicates that the equipment sending this cause does not support the requested supplementary service.

4.3 Cause No. 70 "only restricted digital information bearer capability is available"(有限的数字承载能力可用)

This cause indicates that one equipment has requested an unrestricted bearer service, but that the equipment sending this cause only supports the restricted version of the requested bearer capability.

4.4 Cause No. 79 "service or option not implemented, unspecified"(业务或选项不可执行,未定义)

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.

5 Invalid message (e.g., parameter out of range) class

5.1 Cause No. 81 "invalid transaction identifier value"(无效的传送标识符)

This cause indicates that the equipment sending this cause has received a message with a transaction identifier which is not currently in use on the MS-network interface.

5.2 Cause No. 87 "user not member of CUG"(用户非CUG成员)

This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG.

5.3 Cause No. 88 "incompatible destination"(矛盾的目的地)

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.

5.4 Cause No. 91 "invalid transit network selection"(无效的传输网络选择)

For further study. Treated as cause no. 95.

5.5 Cause No. 95 "semantically incorrect message"(语义错误消息)

This cause is used to report receipt of a message with semantically incorrect contents (see section 8.8).

6 Protocol error (e.g., unknown message) class

6.1 Cause No. 96 "invalid mandatory information"(无效的强制消息)

This cause indicates that the equipment sending this cause has received a message with a non-semantical mandatory IE error (see section 8.5).

6.2 Cause No. 97 "message type non-existent or not implemented"(消息类型不存在或不可实现)

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, or defined but not implemented by the equipment sending this cause.

6.3 Cause No. 98 "message type not compatible with protocol state"(消息类型与协议状态不一致)

This cause indicates that the equipment sending this cause has received a message not compatible with the protocol state (section 8.4).

6.4 Cause No. 99 "information element non-existent or not implemented"(消息元素不存在或不可执行)

This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. 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.

6.5 Cause No. 100 "conditional IE error"(有条件的IE错)

This cause indicates that the equipment sending this cause has received a message with conditional IE errors (see section 8.7.2).

6.6 Cause No. 101 "message not compatible with protocol state"(消息与协议状态不兼容)

This cause indicates that a message has been received which is incompatible with the protocol state or that a STATUS message has been received indicating an incompatible call state.

6.7 Cause No. 102 "recovery on timer expiry"(定时器超时恢复)

This cause indicates that a procedure has been initiated by the expiry of a timer in association with TS 04.08 error handling procedures.

6.8 Cause No. 111 "protocol error, unspecified"(协议错误,未定义)

This cause is used to report a protocol error event only when no other cause in the protocol error class applies.

7 Interworking class

7.1 Cause No. 127 "interworking, unspecified"(互联,未定义)

This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained.

©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 194,242评论 5 459
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 81,769评论 2 371
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 141,484评论 0 319
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 52,133评论 1 263
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 61,007评论 4 355
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 46,080评论 1 272
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 36,496评论 3 381
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 35,190评论 0 253
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 39,464评论 1 290
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 34,549评论 2 309
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 36,330评论 1 326
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 32,205评论 3 312
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 37,567评论 3 298
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 28,889评论 0 17
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 30,160评论 1 250
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 41,475评论 2 341
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 40,650评论 2 335

推荐阅读更多精彩内容

  • rljs by sennchi Timeline of History Part One The Cognitiv...
    sennchi阅读 7,251评论 0 10
  • 开篇第二章 1、文章的段落用 标签,文章的标题用<hx>标签,标...
    多语阅读 178评论 0 0
  • “我好像一直在寻找着什么,我好像在哪里见过你。” 一、 宫水三叶住在远离大都市的一个小山村,这是一个巫女世家出身的...
    一页欢喜阅读 2,260评论 1 12
  • 这是一本经济相关常识类书籍。读这本书,能让毫无经济触觉的人对如何用经济学原理思考、解释生活中接触到的事物,有个基本...
    璐呀璐阅读 886评论 0 1
  • 阅读的故事是《长大以后我要娶妈妈》 树袋熊塔塔每天黏着妈妈,有天他参加完别人的婚礼,也想要娶妈妈。 妈妈就让他去和...
    刘育栋mami阅读 125评论 0 0