 |
善于提问，勤于回答，你也是专家
|
 |
GSM 被叫 paging response后 直接转空闲
GSM 被叫 paging response后 直接转空闲 造成主叫未接通
是由于什么情况导致的？
是由于什么情况导致的？
主叫信令正常
下面是部分被叫信令
DL RR Immediate Assignment 19:36:27.826
DL RR Paging Request Type 1 19:36:27.846
DL RR System Information Type 2 19:36:27.878
DL RR Immediate Assignment 19:36:27.898
UL RR Paging Response 19:36:27.906
DL RR System Information Type 15 19:36:30.466
DL RR System Information Type 13 19:36:32.346
DL RR Paging Request Type 1 19:36:32.409
DL RR System Information Type 2ter 19:36:32.582
DL RR Paging Request Type 1 19:36:33.582
DL RR System Information Type 15 19:36:34.230
DL RR Paging Request Type 1 19:36:34.762
DL RR Paging Request Type 1 19:36:35.937
DL RR Paging Request Type 1 19:36:37.126
DL RR System Information Type 3 19:36:38.057
DL RR Paging Request Type 1 19:36:38.294
DL RR System Information Type 3 19:36:38.430
DL RR System Information Type 4 19:36:38.653
下面是部分被叫信令
DL RR Immediate Assignment 19:36:27.826
DL RR Paging Request Type 1 19:36:27.846
DL RR System Information Type 2 19:36:27.878
DL RR Immediate Assignment 19:36:27.898
UL RR Paging Response 19:36:27.906
DL RR System Information Type 15 19:36:30.466
DL RR System Information Type 13 19:36:32.346
DL RR Paging Request Type 1 19:36:32.409
DL RR System Information Type 2ter 19:36:32.582
DL RR Paging Request Type 1 19:36:33.582
DL RR System Information Type 15 19:36:34.230
DL RR Paging Request Type 1 19:36:34.762
DL RR Paging Request Type 1 19:36:35.937
DL RR Paging Request Type 1 19:36:37.126
DL RR System Information Type 3 19:36:38.057
DL RR Paging Request Type 1 19:36:38.294
DL RR System Information Type 3 19:36:38.430
DL RR System Information Type 4 19:36:38.653
我要回答
问题答案
这要看你的具体信令流程了
可能是主叫问题，突然掉话或挂机造成
也可能是被叫手机问题
还是那句话，要看整个的信令流程来分析异常点
可能是主叫问题，突然掉话或挂机造成
也可能是被叫手机问题
还是那句话，要看整个的信令流程来分析异常点
回答者：libaohong 回答时间：2011-11-24 11:38
29
26主叫信令正常
下面是部分被叫信令
DL RR Immediate Assignment 19:36:27.826
DL RR Paging Request Type 1 19:36:27.846
DL RR System Information Type 2 19:36:27.878
DL RR Immediate Assignment 19:36:27.898
UL RR Paging Response 19:36:27.906
DL RR System Information Type 15 19:36:30.466
DL RR System Information Type 13 19:36:32.346
DL RR Paging Request Type 1 19:36:32.409
DL RR System Information Type 2ter 19:36:32.582
DL RR Paging Request Type 1 19:36:33.582
DL RR System Information Type 15 19:36:34.230
DL RR Paging Request Type 1 19:36:34.762
DL RR Paging Request Type 1 19:36:35.937
DL RR Paging Request Type 1 19:36:37.126
DL RR System Information Type 3 19:36:38.057
DL RR Paging Request Type 1 19:36:38.294
DL RR System Information Type 3 19:36:38.430
DL RR System Information Type 4 19:36:38.653
下面是部分被叫信令
DL RR Immediate Assignment 19:36:27.826
DL RR Paging Request Type 1 19:36:27.846
DL RR System Information Type 2 19:36:27.878
DL RR Immediate Assignment 19:36:27.898
UL RR Paging Response 19:36:27.906
DL RR System Information Type 15 19:36:30.466
DL RR System Information Type 13 19:36:32.346
DL RR Paging Request Type 1 19:36:32.409
DL RR System Information Type 2ter 19:36:32.582
DL RR Paging Request Type 1 19:36:33.582
DL RR System Information Type 15 19:36:34.230
DL RR Paging Request Type 1 19:36:34.762
DL RR Paging Request Type 1 19:36:35.937
DL RR Paging Request Type 1 19:36:37.126
DL RR System Information Type 3 19:36:38.057
DL RR Paging Request Type 1 19:36:38.294
DL RR System Information Type 3 19:36:38.430
DL RR System Information Type 4 19:36:38.653
UL RR Paging Response 19:36:27.906
DL RR System Information Type 15 19:36:30.466
这两条信令之间间隔2秒，很诡异，怀疑被叫手机有问题，丢失信令了，具体还要靠你自己去查看手机了
DL RR System Information Type 15 19:36:30.466
这两条信令之间间隔2秒，很诡异，怀疑被叫手机有问题，丢失信令了，具体还要靠你自己去查看手机了
回答者：bentaner 回答时间：2011-11-29 08:50
我也怀疑是信令丢失，手机的问题，但是别人说要丢10秒以上才是信令丢失？！我很不理解！
寻呼响应之后应该是正常的鉴权加密过程，但你这里响应之后一直没有收到下行请求，而是继续收到寻呼，所以下行没问题，应该是上行链路差导致网络侧没有正确解码。
所以检查上行无线环境吧。
所以检查上行无线环境吧。
回答者：ftlm_lanlan 回答时间：2011-12-01 10:10
如果上行链路是正常的，会是什么造成的情况尼？
