关键字搜索:
siptx-io
volte_auto_testing
AT命令:
CIREGU
CGACT
volte基本流程场景:
参考博客:http://www.cnblogs.com/gnuhpc/archive/2012/12/10/2812095.html
sip hold:
http://blog.csdn.net/blade2001/article/details/9163205
sip协议详解:
https://wenku.baidu.com/view/9069e37569eae009581bec9d.html
https://wenku.baidu.com/view/d2e34ad484254b35eefd34f7.html?re=view
一、SDP/Bearer match失败
tft packet filter这块24.008 10.5.6.12 Traffic Flow Template有讲到,UE的资源预留在RFC 3313有提到,具体行为可能并没有细说,是通过平常看log和workshop所知的。关于此类问题首先看到VoLTE_Auto_Testing: [0][call] event/recv/0/2/bw_cnf/0这一块能判断是资源预留失败,接着可以通过查看tft的行为来进一步判断
在call进行的过程中手机会跟网络进行SDP/Bearer match,如果匹配失败,IMCB向call UA发送bw_cnf=0,这样会导致UA发cancel来断cal,常常会有网络问题导致的bearer匹配失败
K4添加通话失败是因为BW Reserve Failure导致UA发Cancel断call
02-17 15:02:24.236500 1849 1880 I VoLTE_Auto_Testing: [0][call] event/recv/0/2/bw_cnf/0
02-17 15:02:24.240988 1848 1861 D VoLTE SIPTX: [SIPTX-IO] Send SIP (2409:8019:8630:1900:8::: 9900 )[131073:1638420] ==> { CANCEL tel:668189;phone-context=ims.mnc002.mcc460.3gppnetwork.org SIP/2.0 }
02-17 15:02:24.242998 1849 1880 I VoLTE_Auto_Testing: [0][call] state_change/0/2/DISC_IND
k4呼出失败是因为之前所说的BW Reserve Failure导致UA发Cancel断call,而failure是因为在第二通cal建立的过程中网络错误的删除了pf=2的上行RTP packet filter,这样导致了后续qos和tft都match failed,而对比机log则不存在这样的情况,因为网络没有错误删除任何pf,这是网络问题造成的,请您知悉!
Type Index Time Local Time Module Message Comment Time Different
OTA 610411 491332 17:27:57:305 ESM [NW->MS] ESM_MSG_MODIFY_EPS_BEARER_CONTEXT_REQUEST (PTI:0, EBI:7) //消息体中可以看到pf
101. .... = TFT operation code: Delete packet filters from existing TFT (5)
.... 0001 = Packet filter identifier: 2 (1)
03-04 17:27:58.151558 4436 4436 I VoLTE IMCB: tft_mod (1) qos_mod(1) imcb_bearer_msg_media_add_req_chk (vendor/mediatek/proprietary/frameworks/opt/volte/volte_imcb/sub_imcb/bearer/src/imcb_bearer_media_chk.c, 211)
03-04 17:28:04.082754 4434 4470 I VoLTE_Auto_Testing: [0][call] event/recv/0/2/bw_cnf/0
03-04 17:28:04.088060 4433 4453 D VoLTE SIPTX: [SIPTX-IO] Send SIP (2409:8019:8630:1900:8::: 9900 )[524292:2228254] ==> { CANCEL tel:664253;phone-context=ims.mnc002.mcc460.3gppnetwork.org SIP/2.0 }
二、呼叫转移的问题(待确认)
分析从log中看UE这边收到181之后就有收到网络很快下发的487从而通话只能被断开,这个是网络行为决定的,由于贵司是用联通卡设置了呼叫转移,怀疑的跨运营商之间网络还是有问题,之前其他客户也有碰到类似的问题,还请贵司用相同的卡在相同地点多对比测试,请知悉!
16569: 02-23 14:06:19.919106 1762 1782 D VoLTE SIPTX: [SIPTX-IO] Recv SIP (2409:8019:8630:1900:8::: 9900 )[131073:262147] <== { SIP/2.0 181 Call Is Being Forwarded }
16652: 02-23 14:06:19.922044 1763 3097 I VoLTE_Auto_Testing: [0][call] msg/recv/resp/0/-1/181
16682: 02-23 14:06:19.923350 1763 3097 I VoLTE_Auto_Testing: [0][call] event/send/0/1/ecpi/2/0/0/3/0
16689: 02-23 14:06:19.923617 1763 3097 I VoLTE_Auto_Testing: [0][call] event/send/0/1/notify/2
17943: 02-23 14:06:21.459108 1762 1782 D VoLTE SIPTX: [SIPTX-IO] Recv SIP (2409:8019:8630:1900:8::: 9900 )[131073:262147] <== { SIP/2.0 487 Request Terminated }
18018: 02-23 14:06:21.489841 1763 3097 I VoLTE_Auto_Testing: [0][call] msg/recv/resp/0/-1/487
18035: 02-23 14:06:21.490466 1763 3097 I VoLTE_Auto_Testing: [0][call] event/send/0/1/bw_rel
18043: 02-23 14:06:21.490808 1763 3097 I VoLTE_Auto_Testing: [0][call] event/send/0/1/ecpi/133/0/0/3/31
三、4G连接断开导致volte通话中断
主叫端在收到SIP/2.0 180 Ringing由于信号比较弱 rsrp[-486] rsrq[-60] ,导致网络下发了ERRC_RRCConnectionRelease
Type Index Time Local Time Module Message Comment Time Different
SYS 290269 160840 14:51:13:400 NIL [AT_I p20, s10]ATD664253;
OTA 293869 160888 14:51:13:600 ESM [NW->MS] ESM_MSG_ACTIVATE_DEDICATED_EPS_BEARER_CONTEXT_REQUEST (PTI:0, EBI:7)
OTA 294085 160888 14:51:13:600 ESM [MS->NW] ESM_MSG_ACTIVATE_DEDICATED_EPS_BEARER_CONTEXT_ACCEPT (PTI:0, EBI:7)
SIP 0 14:51:13:788 [MS->NW]INVITE tel:664253;phone-context=ims.mnc007.mcc460.3gppnetwork.org SIP/2.0
SIP 1 14:51:13:922 [NW->MS]SIP/2.0 100 Trying
OTA 307739 161099 14:51:14:800 ESM [NW->MS] ESM_MSG_MODIFY_EPS_BEARER_CONTEXT_REQUEST (PTI:0, EBI:7)
OTA 307951 161099 14:51:14:800 ESM [MS->NW] ESM_MSG_MODIFY_EPS_BEARER_CONTEXT_ACCEPT (PTI:0, EBI:7)
SIP 2 14:51:15:017 [NW->MS]SIP/2.0 183 Session Progress
SIP 3 14:51:15:052 [MS->NW]PRACK sip:[2409:8019:8630:2100:0008:0000:0000:0000]:9900;Hpt=8f32_16;CxtId=3;TRC=ffffffff-ffffffff SIP/2.0 <