GSM未接通原因值事件代码

合集下载

GSM未接通、掉话及切换失败

未接通、掉话及切换失败分析一、未接通分析正常呼叫主叫起呼和被叫接入过程：主叫起呼信令流程图被叫接入信令流程图由主叫起呼信令流程图可以看出，主叫首先发出channel request report-→immediate assignment-→CM service request-→setup-→call proceeding-→assignment command-→assignment complete-→alerting-→connect-→完成一次起呼。

在主叫assignment complete 完成后2－3秒左右被叫开始信道请求流程Channel request report→immediate assignment-→setup→call confirmed→assignment command→assignment complete-→alerting→connect-→完成一次被叫接入。

1、未接通原因分析（1）RACH冲突或者AGCH拥塞建议：查看与RACH相关的参数――最大重发次数和发送分布时隙数以及与AGCH相关的参数――接入准许保留块数（2）SDCCH拥塞建议：检查SDCCH配置，查看相关小区SDCCH话务量（3）SDCCH掉话或者TCH拥塞建议：查看是否启用SDCCH信道上的切换，查看相关小区话务量和TCH配置，在排除无线方面原因后，应跟踪Abis接口、A接口信令从交换侧寻找问题原因（4）位置更新引起未接通建议：查看位置更新定时器和位置区设置（5）小区重选过程引起未接通建议：查看相关小区的小区重选参数2、未接通实例分析（1）SDCCH拥塞导致未接通在主叫完成起呼（assignment complete ）后2秒左右，此时被叫发起信道请求channel request report,由于SDCCH拥塞溢出，被叫手机无法获得SDCCH，重复2次发送信道请求后仍然无法获得SDCCH信道消息的回复，导致未接通的发生。

GSM网络cause value值的详细解释

处理过程2004-11-24 0:01:27 刘业标以下是我知道的常见Disconnect / Release Cause :Cause Value Reason==============================================================31 BSS or MSC problem34(beforeAssignmentCommand) TCH Blocking34(after Assignment Complete) MSC Blocking41(after Assignment Command) BSS problem, especially DRI problem41(after Assignment Complete) MSC problem42 MSC Congestion44 BSS problem, especially the CIC blocking111 BSS or MSC problem2004-11-26 14:55:38 罗怀瑾以下为已知的CAUSE VALUE 集合1 Unassiagned number(未分配的号码（空号）)3 No route to destination(无至目的地的路由)6 Channel unacceptable(不可接受的信道)16 Normal clearing(正常清除)17 User busy(用户忙)18 No user responding(无用户响应)19 User alerting,no answer(已有用户提醒，但无应答)21 Call rejected(呼叫拒绝)22 Number changed(号码改变)26 Non selected user clearing(清除未选择的用户)27 Destination out of order(终点故障)28 Incomplete number(无效号码格式（不完全的号码）)29 Facility rejected(设施被拒绝)30 Response to status enquiry(对状态询问的响应)31 Normal,unspecified(正常，未规定)34 No circuit/channel available(无电路/信道可用)38 Network out of order(网络故障)41 Temporary failure(临时故障)42 Switching equipment congestion(交换设备拥塞)43 Access information discarded(接入信息被丢弃)44 Requested circuit/channel not available(请求的电路/信道不可用)47 Resources unavailable,unspecified(资源不可用，未规定)49 Quality of service unavailable(服务质量不可用)50 Requested facility not subscribed(未预订所请求的设施)55 Incoming calls barred within the CUG57 Bearer capability not authorized(承载能力未认可)58 Bearer capability not presently available(承载能力目前不可用)63 Service or option not available,unspecified(无适用的业务或任选项目，未规定)65 Bearer service not implemented(承载业务不能实现)MS2：始终处于空闲状态问题分析：CM Service被拒绝，原因是位置更新失败，或跨LAC以后手机未进行位置更新，或者交换机问题。

手机常见错误码GSM错误代码表

手机常见错误码GSM错误代码表GSM错误代码表GSM device:AT+CMEE=1AT&WCME ERROR's (GSM Equipment related codes)Error DescriptionCME ERROR: 0 Phone failureCME ERROR: 1 No connection to phoneCME ERROR: 2 Phone adapter link reservedCME ERROR: 3 Operation not allowedCME ERROR: 4 Operation not supportedCME ERROR: 5 PH_SIM PIN requiredCME ERROR: 6 PH_FSIM PIN requiredCME ERROR: 7 PH_FSIM PUK requiredCME ERROR: 10SIM not insertedCME ERROR: 11SIM PIN requiredCME ERROR: 12SIM PUK requiredCME ERROR: 13SIM failureCME ERROR: 14SIM busyCME ERROR: 15SIM wrongCME ERROR: 16Incorrect passwordCME ERROR: 17SIM PIN2 requiredCME ERROR: 18SIM PUK2 requiredCME ERROR: 20Memory fullCME ERROR: 21Invalid indexCME ERROR: 22Not foundCME ERROR: 23Memory failureCME ERROR: 24Text string too longCME ERROR: 25Invalid characters in text stringCME ERROR: 26Dial string too longCME ERROR: 27Invalid characters in dial stringCME ERROR: 30No network serviceCME ERROR: 31Network timeoutCME ERROR: 32Network not allowed, emergency calls onlyCME ERROR: 40Network personalization PIN requiredCME ERROR: 41Network personalization PUK requiredCME ERROR: 42Network subset personalization PIN required CME ERROR: 43Network subset personalization PUK required CME ERROR: 44Service provider personalization PIN required CME ERROR: 45Service provider personalization PUK required CME ERROR: 46Corporate personalization PIN requiredCME ERROR: 47Corporate personalization PUK requiredCME ERROR: 48PH-SIM PUK requiredCME ERROR: 100Unknown errorCME ERROR: 103Illegal MSCME ERROR: 106Illegal MECME ERROR: 107GPRS services not allowedCME ERROR: 111PLMN not allowedCME ERROR: 112Location area not allowedCME ERROR: 113Roaming not allowed in this location area CME ERROR: 126Operation temporary not allowedCME ERROR: 132Service operation not supportedCME ERROR: 133Requested service option not subscribed CME ERROR: 134Service option temporary out of orderCME ERROR: 148Unspecified GPRS errorCME ERROR: 149PDP authentication failureCME ERROR: 150Invalid mobile classCME ERROR: 256Operation temporarily not allowedCME ERROR: 257Call barredCME ERROR: 258Phone is busyCME ERROR: 259User abortCME ERROR: 260Invalid dial stringCME ERROR: 261SS not executedCME ERROR: 262SIM BlockedCME ERROR: 263Invalid blockCME ERROR: 772SIM powered downCMSERROR's (GSM Network related codes)Error DescriptionCMSERROR: 1 Unassigned numberCMSERROR: 8 Operator determined barringCMSERROR: 10 Call baredCMSERROR: 21 Short message transfer rejectedCMSERROR: 27 Destination out of serviceCMSERROR: 28 Unindentified subscriberCMSERROR: 29 Facility rejectedCMSERROR: 30 Unknown subscriberCMSERROR: 38 Network out of orderCMSERROR: 41 Temporary failureCMSERROR: 42 CongestionCMSERROR: 47 Recources unavailableCMSERROR: 50 Requested facility not subscribedCMSERROR: 69 Requested facility not implemented CMSERROR: 81 Invalid short message transfer reference value CMSERROR: 95 Invalid message unspecifiedCMSERROR: 96 Invalid mandatory informationCMSERROR: 97 Message type non existent or not implemented CMSERROR: 98 Message not compatible with short message protocol CMSERROR: 99 Information element non-existent or not implemente CMSERROR: 111Protocol error, unspecifiedCMSERROR: 127Internetworking , unspecifiedCMSERROR: 128Telematic internetworking not supportedCMSERROR: 129Short message type 0 not supportedCMSERROR: 130Cannot replace short messageCMSERROR: 143Unspecified TP-PID errorCMSERROR: 144Data code scheme not supportedCMSERROR: 145Message class not supportedCMSERROR: 159Unspecified TP-DCS errorCMSERROR: 160Command cannot be actionedCMSERROR: 161Command unsupportedCMSERROR: 175Unspecified TP-Command errorCMSERROR: 176TPDU not supportedCMSERROR: 192SC busyCMSERROR: 193No SC subscriptionCMSERROR: 194SC System failureCMSERROR: 195Invalid SME addressCMSERROR: 196Destination SME barredCMSERROR: 197SM Rejected-Duplicate SMCMSERROR: 198TP-VPF not supported CMSERROR: 199TP-VP not supported CMSERROR: 208D0 SIM SMS Storage full CMSERROR: 209No SMS Storage capability in SIM CMSERROR: 210Errorin MSCMSERROR: 211Memory capacity exceeded CMSERROR: 212Sim application toolkit busy CMSERROR: 213SIM data download error CMSERROR: 255Unspecified errorcause CMSERROR: 300ME FailureCMSERROR: 301SMS service of ME reserved CMSERROR: 302Operation not allowed CMSERROR: 303Operation not supported CMSERROR: 304Invalid PDU mode parameter CMSERROR: 305Invalid Text mode parameter CMSERROR: 310SIM not inserted CMSERROR: 311SIM PIN required CMSERROR: 312PH-SIM PIN required CMSERROR: 313SIM failureCMSERROR: 314SIM busyCMSERROR: 315SIM wrongCMSERROR: 316SIM PUK required CMSERROR: 317SIM PIN2 required CMSERROR: 318SIM PUK2 required CMSERROR: 320Memory failureCMSERROR: 321Invalid memory index CMSERROR: 322Memory fullCMSERROR: 330SMSC address unknown CMSERROR: 331No network service CMSERROR: 332Network timeout CMSERROR: 340No +CNMA expected。

GSM网络cause_value值的详细解释

各种未接通信令汇

ISUP消息中rel原因值G3.1正常类别原因NO.1：未分配的（未确定的）号码"unassigned (unallocaled) number"该原因表示不能到达主叫用户所请求的终点，因为虽然号码格式有效，但该号码目前尚未分配（未确定）。

原因NO.2：无路由到达规定的转换网络（国内使用）"no route to specified transit network(nationaluse)"unallocaled(unassigned) number该原因表示发送该原因的设备已经收到一个通过特定未被识别的转接网络迂回呼叫的请求。

发送该原因的设备不能识别该转接网络是因为该转接网络不存在或当它存在时并没有未该设备提供服务。

是否支持该原因由网络决定。

原因NO.3无路由到达终点"no route to destination"该原因表示不能到达被叫用户，因为呼叫所经过的网络不为所希望的终点提供服务。

是否支持该原因由网络决定。

原因NO.4发送特殊的信息音"send special information tone"该原因表示不能达到被叫用户的原因在于应向主叫用户返回特殊信息音。

原因NO.5转接前缀拨号错误（国内使用）"misdialled trunk prefix(national use)"该原因表示被叫方号码的转接前缀错误内含。

原因NO.6：不可接受的通路"chnnel unacceptable"该原因表示发送实体在呼叫中不接受使用最新标识的通路。

原因NO.7：呼叫已给出并正在已建立的通路上递交"call awarded and being delivered in an established channel"该原因表示已给予用户来呼叫，并表示这一来呼叫在已建立的通路上与类似的呼叫一起正在被连接到该用户。

GSM异常事件原因值总结

SccpRRRR cause value (octet 2)Bits8 7 6 5 4 3 2 10 0 0 0 0 0 0 0 Normal event0 0 0 0 0 0 0 1 Abnormal release, unspecified0 0 0 0 0 0 1 0 Abnormal release, channel unacceptable0 0 0 0 0 0 1 1 Abnormal release, timer expired0 0 0 0 0 1 0 0 Abnormal release, no activity on the radio path0 0 0 0 0 1 0 1 Preemptive release0 0 0 0 0 1 1 0 UTRAN configuration unknown0 0 0 0 1 0 0 0 Handover impossible, timing advance out of range 0 0 0 0 1 0 0 1 Channel mode unacceptable0 0 0 0 1 0 1 0 Frequency not implemented0 0 0 0 1 0 1 1 Originator or talker leaving group call area0 0 0 0 1 1 0 0 Lower layer failure0 1 0 0 0 0 0 1 Call already cleared0 1 0 1 1 1 1 1 Semantically incorrect message0 1 1 0 0 0 0 0 Invalid mandatory information0 1 1 0 0 0 0 1 Message type non-existent or not implemented0 1 1 0 0 0 1 0 Message type not compatible with protocol state0 1 1 0 0 1 0 0 Conditional IE error0 1 1 0 0 1 0 1 No cell allocation available0 1 1 0 1 1 1 1 Protocol error unspecifiedAll other cause values shall be treated as 0000 0000, 'normal event' The listed RR cause values are defined in Annex F.Table 10.5.123/3GPP TS 24.008 (concluded): Cause information element valuesBss3.2.2.5 CauseThe cause element is used to indicate the reason for a particular event to have occurred and is coded as shown below.The cause value is a single octet element if the extension bit (bit 8) is set to 0. If it is set to 1 then the cause value is a 2octet field. If the value of the first octet of the cause field is 1XXX 0000 thenoctet 1octet 2octet 3(octet 4)The length indicator is a binary representation of the length of the following element.Cause Value:Class (000): Normal eventClass (001): Normal eventClass (010): Resource unavailableClass (011): Service or option not available, but implementedClass (100): Service or option not implemented or currently disabled, i.e. not supportedClass (101): invalid message (eg parameter out of range)Class (110): protocol errorClass (111): interworkingIn the following table, "reserved for international use" means that this codepoint should not be used until a meaning has been assigned to it following the process of international standardisation. "Reserved for national use" indicates codepoints that may be used by operatorsassigment fail包含 rr cause 和BSS causeCP8.1.4.2 CP-Cause elementThis element is included in the CP-ERROR message, the layout is given in figure 8.3/3GPP TS 24.011. The error causes are listed in table 8.2/3GPP TS 24.011.876543211 octet1 octetFigure 8.3/3GPP TS 24.011: CP-Cause element layoutTable 8.2/3GPP TS 24.011: Content and coding of CP-CauseRp8.2.5.4 RP-Cause elementThis element is a variable length element always included in the RP-ERROR message, conveying a negative result of a RP-DATA message transfer attempt or RP-SMMA notification attempt. The element contains a cause value and optionally a diagnostic field giving further details of the error cause.The coding of the cause value is given in table 8.4/3GPP TS 24.011. The mapping between error causes in 3GPP TS24.011 and 3GPP TS 29.002 (MAP) is specified in 3GPP TS 23.040. Parameters included in the return error from MAP (e.g. System Failure) are mapped directly into the diagnostic field.876543211 octet1 octet1 octet1 octet *Figure 8.8/3GPP TS 24.011: RP-Cause element layoutmessagein a mobile originating SM-transfer attemptmessage in a mobile terminating SM-transfer attemptmessage in a memory available notification attemptHANDOVER FAILURE同assgmnet failHANDOVER REQUIRED REJECTThis message is sent from the MSC to the BSS via the relevant SCCP connection. It indicates to the。

GSM未接通代码

GSM未接通代码GSM未接通代码解释1 Normal class1.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 themobile station cannot be reachedbecause 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 u ser; 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 class2.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 functioningcorrectly 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 class3.1 Cause No. 49 "quality of service unavailable"（业务质量（QOS）不可用）This cause indicates to the mobile station that the requested quality of service, as defined inCCITT 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"（在ＣＵＧ中来话禁止）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 othercause in the service or option not available class applies.3.7 Cause No. 68 "ACM equal to or greater than ACMmax"（ＡＣＭ大于等于ＡＣＭ最大值）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 class4.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) class5.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 notcurrently in use on the MS-network interface.5.2 Cause No. 87 "user not member of 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) class6.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 this6.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 class7.1 Cause No. 127 "interworking, unspecified"（互联，未定义）This cause indicates that there has been interworking with a network which does not providecauses for actions it takes; thus, the precise cause for a message which is being sent cannot be ascertained.。

GSM未接通原因

1.第2步：是否存在Immediate assignment reject ，若有，则说明存在SDCCH阻塞。

如果有大量的SDCCH阻塞，若没有“Immediate assignment ”，信号弱或干扰，导致系统无法收到“ channel request”或MS无法解码下行消息。

2.第4步：是否存在CM service reject ，若有，可能是欠费、漫游到没有权限的地区或者割接后小区交换没有做数据，还有可能是VLR，HLR有问题
3.是否存在第7步，若没有而直接收到系统下发disconnect消息，可能是存在TCH拥塞。

4.第8步，手机直接响应Assignment fail ，存在干扰、信号弱或硬件故障导致TCH分配失败
5.到第3、4步或到第8步MS直接转到寻呼信道，则是SD或TCH信道上掉话，主要原因有信号弱、话音差或硬件故障导致。

到第8或9步，直接收到系统下发disconnect消息（释放信道原因见下表），则查看被叫问题（原因有以上几种）。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

该原因表示呼叫正在被预先占有。

原因NO.9：先占电路留作重新使用"preemption-circuit reserved for reuse"该原因表示呼叫正在被预先占有，电路留作先点交换的重新使用。

原因NO.16：正常的呼叫清除"normal call clearing"该原因表示呼叫正在被清除，这是因为呼叫所涉及的用户之一已经请求清除呼叫。

在正常情况下，网络不发送这一原因。

原因NO.17：用户忙"user busy"当被叫用户指示不能接受另一个呼叫时使用这一原因。

原因NO.18：无用户响应"no user responding"当被叫用户在规定的时间周期内不用提醒或连接指示响应呼叫建立消息时使用这一原因。

原因NO.19：无用户应答（用户已提醒）"no answer from user(user alerted)"当用户在规定的时间周期内提供提醒指示但未提供连接指示时使用这一原因。

注－该原因不一定由Q.931程序产生，而可能由内部网络定时器产生。

原因NO.20：用户缺席"subscriber absent"该原因用作移动应用，本规范暂不使用。

原因NO.21：呼叫拒绝"call rejected"该原因表示发送这一原因的设备不希望接收呼叫，虽然它可以接受呼叫，因为发送该原因的设备既不忙，也兼容。

该原因可以由网络产生，表示由于补充业务的限制而清除了呼叫。

诊断字段可能包含有关补充业务的附加信息和拒绝原因。

原因NO.22：号码变更"number changed"当主叫用户所指示的被叫用户号码不再被分配时，该原因被返回到主叫用户。

新的被叫用户号码可以作为任选项目包含在诊断字段中。

如果网络不支持这种能力，将使用原因NO.1未分配的（未确定）的号码。

原因NO.26：清除未选择的用户"non-selected user clearing"该原因表示未给予用户来呼叫。

原因NO.27：终点故障"destination out of order"该原因表示不能到达用户所指示的收端，因为收端的接口工作不正常。

术语"工作不正常"表示信令消息不能递交到远端用户；例如，远端用户的物理层或数据层故障，用户设备脱机等。

原因NO.28：无效的号码格式（不完整号码）"invalid number format(incomplete number)"该原因表示不能到达被叫用户因为被叫用户号码的格式无效或被叫用户号码不完整。

原因NO.29：性能被拒绝"facility rejected"当网络不能提供用户所请求的性能时则返回这一原则。

原因NO.30：对STATUS ENQUIRY的响应"response to STATUS ENQUIRY"当产生STATUS消息的原因是先接收到一条STATUS ENQUIRY消息时，该原因被包含在STATUS消息中。

原因NO.31：正常，未规定"normal,unspecified"仅在正常原因类别中无其它原因适用时，使用该原因报告一个正常事件。

G3.2无可用的资源类别原因NO.34：无可用的电路/通路"no circuit'channel available"该原因表示目前尚无适当的电路/通路可用来处理呼叫。

原因NO.38：网络失序"network out of order"该原因表示网络运行不正确，并且条件可能会持续相当长的时间；例如，立刻重新发起呼叫可能不会成功。

原因NO.39：永久帧方式连接未开放业务"permanent frame mode connection out-of -service"原因包含在STATUS消息表示一个永久建立帧方式连接未开放业务（例如，由于设备或部分故障）。

注－该原因在本标准中暂不使用。

原因NO.40：永久帧方式连接可运营"permanent frame mode connection operational"该原因包含在STATUS消息表示一个永久建立帧方式连接是可运营的，并且可以传递用户信息。

注－该原因在本标准中暂不使用。

原因NO.41：临时故障"temporary failure"该原因表示网络工作不正常，并且这一状态不可能持续很长时间，例如，用户几乎可能立即希望进行另一次试呼。

原因NO.42：交换设备拥塞"switching equipment congestion"该原因表示产生这一原因的交换设备正在历经高业务量周期。

原因NO.43：接入信息被丢弃"access information discarded"该原因表示网络不能向远端用户按要求递交接入信息：即，如诊断中所指示的用户－用户信息，低层兼容性，高层兼容性或子地址。

应用注意所丢弃的某种接入信息作为任选项目被包含在诊断中。

原因NO.44：请求的电路/通路不可用"requested circuit/channel not available"当另一侧接口不能提供请求实体所指示的电路或通路时，返回这一原因。

原因NO.46：优先呼叫阻塞"precedence call blocked"该原因表示没有优先电路，或者被叫用户忙，并且其呼叫由相同或更高的优先级。

原因NO.47：资源不可用，未规定"resource unavailable,unspecified"该原因仅在没有任何其它的资源不可用类型使用时报告一个资源不可用的事件。

G3.3无适用的业务或任选项目类别原因NO.49：业务质量不可用"quality of service not available"该原因用来报告所申请的建议X.213中定义的业务质量不能提供（例如，不能支持吞吐量或转接延迟）。

原因NO.50：未预订所请求的性能"requested facility not subscribed"该原因表示网络不能提供所请求的补充业务，因为用户没有完成支持业务的网络所必要的管理手续。

原因NO.53：CUG内呼出呼叫阻塞"outgoing calls barred within CUG"该原因表示虽然主叫方是可以呼出CUG呼叫的CUG成员，但CUG的该成员不允许呼出呼叫。

原因NO.55：CUG内呼入呼叫阻塞"incoming calls barred within CUG"该原因表示虽然被叫方是可以接收呼入CUG呼叫的CUG成员，但CUG的该成员不允许接收呼入呼叫。

原因NO.57：承载能力未认可"bearer capability not authorised"该原因表示，虽然产生该原因的设备已实施了用户请求的承载能力，但用户未被认可使用。

原因NO.58：目前尚无可用的承载能力"bearer capability not presently available"该原因表示，虽然产生该原因的设备已实施了用户请求的承载能力，但此时无可用的承载能力。

原因NO.62：分配的呼出接入信息与用户级别不一致"inconsistency in designated outgoing access information and subscriber class"该原因表示在分配的呼出接入信息与用户级别之间存在不一致。

原因NO.63：无适用的业务或任选项目，未规定"service or option not available, unspecified"仅在无适用的业务或任选项目类别中无其它原因使用时，使用该原因报告无适用的业务或任选项目事件。

G3.4业务或任选项目未实施类别原因NO.65：承载能力未实施"bearer capability not implemented"该原因表示发送这一原因的设备不支持所请求的承载能力。

原因NO.66：通路类型未实施"channel type not implemented"该原因表示发送这一原因的设备不支持所请求的类型。

原因NO.69：请求的性能未实施"requested facility not implemented"该原因表示发送这一原因的设备不支持所请求的补充业务。

原因NO.70：只有受限的数字信息承载可用（国内使用）"only restricted digital information bearer capability is available(national use)"该原因表示主叫方已申请了一个不受限的承载业务，但是发送该原因的设备仅支持所请求的承载能力中受限形式。

原因NO.79：业务或任选未实施，未规定"service or option not implementaed,unspecified"该原因用作仅当业务或任选未实施类别中无其它原因使用时报告一个业务或任选未实施事件。

G3.5无效的消息（例如，参数超出范围）类别原因NO.81：无效的呼叫参考值"invlalid call reference value"该原因表示发送这一原因的设备所收到的消息带有不是在用户－网络接口现行使用的呼叫参考。

原因NO.82：所标识的通路不存在"identfied channel does not exist"原因表示发送这一原因的设备接收到一个呼叫请求，请求使用在接口处未被激活的通路。

例如，如果用户预订了一次群接口的第1到12条通路，而用户设备或网络企图使用第13至23条通路，则产生这一原因。

原因NO.83：存在暂停的呼叫，但无所用的呼叫身份"a suspended call exists,but this call identity does not"该原因表示呼叫试图恢复时使用的呼叫身份与现行呼叫暂停时使用的呼叫身份不相同。

原因NO.84：呼叫身份在使用"call identity in use"该原因表示网络已接收到一个呼叫暂停的请求，这一呼叫暂停请求包含在有可能恢复呼叫的接口范围内一个暂停呼叫已经使用的呼叫身份（包括无呼叫身份）。