VoLTE Log分析与主要SIP消息
高通在IMS产品介绍会上明确说明将VoLTE代码封装在Modem里，故VoLTE的Log主要是在Modem里；在Main Log 和 Radio Log里的信息量较少或压根没有输出；Net Log里是SIP消息相关的，主要是看SIP消息的流程、配置有没有问题。
一、Log分析
分析问题时，整体方向是：先用Wireshark看下有没有SIP消息，SIP消息有没有异常，再看Modem Log里的空中接口相关的Log，最后看详细的Modem Log。 如果定位不到问题，或看Modem Log有困难，找网络适应性组的帮忙分析(早期是张平平在跟VoLTE)，他们经验比较丰富，对空口消息比较熟悉，从Modem侧定位问题比较快速。如果网络适应性组的同事也定位不到问题，或忙不过来，需要提Case给高通，请高通的技术支持协助分析。
检查点：
1. NV参数
NV 01896 ipv6_enabled 1 (1:开启IPv6地址类型)
NV 67261 IMSParamSrc 2 (2:从卡里读注册参数；0:从NV 67258读) NV 67264 ---> RegPCOEnable/RegPreConfigEnabled 1) 注网时通过PCO发P-CSCF请求获取P-CSCF地址 RegPCOEnable = 1, RegPreConfigEnabled = 0
AT$QCPDPIMSCFGE=1,1,0,0 (Set PCO for profile 1)
2) 从ISIM卡读取P-CSCF域名 RegPCOEnable = 0, RegPreConfigEnabled = 1
Set regManagerPreConfigServerBase to empty
3) 从NV里读取P-CSCF地址
RegPCOEnable = 0, RegPreConfigEnabled = 1
Set regManagerPreConfigServerBase = “P-CSCF IP address”:SIP Port
NV 71527 ---> iISIMPriority/iNVPriority/iPCOPriority
P-CSCF地址获取方式的优先级，0为禁用，值越小优先级越高(正数值) A.P-CSCF from PCO and IMS parameters from Card: ISIM=2, NV=3, PCO=1 B.P-CSCF from NV and all others from Card: ISIM=1, NV=2, PCO=0 C.All IMS parameters from NV: ISIM=0, NV=1, PCO=0
2. SIM卡
USIM/ISIM，只有这两种SIM卡可以注册IMS，USIM根据IMSI构造，ISIM读卡里的IMPI和IMPU。
IMS用户标识：每个用户分配1个私有用户标识（IMPI）和多个公有用户标识（IMPU） （IMPI：IM Private Identity，私有用户标识，IMPU：IM Public Identity，公有用户标识）。
IMPI用于注册、授权、管理、计费等目的。IMPU用于用户之间进行通讯，采用SIP URI格式或者TEL URI格式，包含1个E.164的TEL URI和2个SIP URI。其中TEL URI用户可见，用于业务发起与终结业务。SIP URI用户不可见，用于融合通信域内的管理与路由。在融合通信系统中，一个用户的所有IMPU构成一个隐式注册集。
所有码号由网络配置，通过终端配置服务下发到终端。不允许用户申请自定义的SIP URI。
具体用户标识如下：
TEL URI：采用E.164编号，使用用户的手机号码，具体格式如： tel:+8613901011111
SIP URI：采用E.164编号+域名方式，具体格式如：sip：+8613901011111@<省份>.ims.mnc
高通文档对SIM卡要求的描述如下：
The UICC card needs to have an ISIM application along with the proper credentials for IMS registration. The credentials include: From the USIM
Mobile Subscriber Integrated Services Digital Network Number (MSISDN) – Generally the phone number of the device
From the ISIM
IMS Private Identity (IMPI) IMS Public Identity (IMPU)
Domain – Domain of the home network
Security Key – Subscriber key for security authentication OP – Operator algorithm configuration value
AuthScheme parameters – Algorithms for security authentication
3. 网络
要注册到支持VoLTE的LTE网络，并且数据网络开关要打开，Default APN要设置好，Default APN 和 IMS APN的IP地址类型要设置好（如：IPV4V6）。 有些卡虽然支持IMS，但是可能会被Modem端的一些配置文件屏蔽掉（carrier_policy.xml），导致只能注册GSM网 -- 调试时碰到PLMN为46005的白卡被屏蔽的案例。
IMS的注册和退注册，完全由Modem端控制，上层不可见。注册网络时，如果发起连接的PDN的APN类型里有IMS（如APN类型配为：default,ia,ims），基站激活默认承载（手机上网用的那个PDN），会下发P-CSCF的地址，手机随后向该地址发起IMS注册；
如果手机在默认承载里没有P-CSCF地址，手机会发起IMS的PDN请求；
如果在Default PDN 和 IMS PDN 两个承载里都没有发现P-CSCF地址，则不会发起IMS注册。 高通文档描述：
When the UE powers up, it will initially attach to the IMS PDN, then the IMS app on the modem side will automatically connect to the IMS PDN for IMS registration. As soon as attach is complete, Android will use the default profile to trigger an additional PDN connect to the internet PDN.
We usually create two Profiles for the VoLTE by QMICM, the first one is for the Internet APN
and the second is for the IMS APN. The MTP will attach to the Internet APN and then initiate the PDN Connect request to the IMS APN. After the successfully IMS APN connection and QCI = 5 bear activation, the MTP will be able to send IMS SIP Register Message to the P-CSCF.
4. 通路检查
SIM卡，射频功率，和Modem侧检查 Contents： Camping Issues SIB Decode Failure RACH Failures Radio Link Failures Low DL Throughput Issues Low UL Throughput Issues Data Sanity for Throughput Issues F3 Keywords
《80-NE962-1_A_LTE_AS_Typical_Field_Scenarios_Checklists.pdf》
二、SIP消息：
会话初始化协议SIP(Session Initiation Protocol)是一个在IP网络上进行多媒体通信的应用层控制协议,它被用来创建,修改,和终结一个或多个参加者参加的会话进程。
SIP Body 里的SDP(会话描述)部分，请阅读SDP协议。
SIP的请求方法：INVITE，ACK，BYE，CANCEL，OPTIONS，REGISTER，PRACK，SUBSCRIBE，NOTIFY，PUBLISH，INFO，REFER，MESSAGE，UPDATE。详细内容请阅读SIP协议。
中移动在IMS用的SIP，有部分扩展，详细内容请阅读《中国移动CM-IMS(SIP)技术规范》的第2部分《中国移动CM-IMS(SIP)技术规范_第2部分：SIP的消息V1.0.0.doc》，该文档描述了CM-IMS所用的SIP的格式，信息头名称简写也可以查到。
详细的SIP消息流程，请阅读《中国移动CM-IMS(SIP)技术规范》的第3部
分《中国移动CM-IMS(SIP)技术规范_第3部分：SIP的基本流程.doc》。 中移动对SIP消息、头域以及信令流程提出的定制化需求，请阅读《中国移动CM-IMS(SIP)技术规范》的第4部分《中国移动CM-IMS(SIP)技术规范_第4部分：CM-IMS业务对SIP的要求V1.0.0.doc》。
这里只列出IMS注册、主叫、被叫、eSRVCC、PS上收发SMS，退注册的SIP消息和空中接口消息，其他的SIP消息请阅读《41-融合通信接口规范（终端-平台接口分册）v1.0.0（技术参考版）.pdf》、《41-融合通信接口规范（终端-平台接口分
册）v1.0.0（技术参考版）20140716.docx》(两个文档内容一样，word格式易于搜索)，其他
的空中接口消息请阅读《VoLTE终端测试规范——通信功能和性能分册V1.0.0（报批稿）.pdf》。
1. IMS注册
SIP消息：
Request: REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org (1 binding) Status: 401 Unauthorized
Request: REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org (1 binding) Status: 200 OK (1 binding)
说明：
[MS --> NW] 手机向网络(PLMN为00101)请求IMS注册
[NW --> MS] 网络回复401 Unauthorized，消息里携带鉴权需要用到的信息 [MS --> NW] 手机再次请求IMS注册，消息里携带鉴权应答信息
[NW --> MS] 网络回复200 OK，消息里携带VoLTE能力信息
空口消息如下：
UL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL UL DL UL DL UL UL
RRC CONNECTION REQUEST //RRC请求 RRC CONNECTION SETUP COMPLETE //RRC请求建立 EMM: AUTHENTICATION REQUEST //鉴权请求 EMM: AUTHENTICATION RESPONSE //鉴权应答 EMM: SECURITY MODE COMMAND //安全模式命令(信令完整性保护) EMM: SECURITY MODE COMPLETE //安全模式完成 SECURITY MODE COMMAND
SECURITY MODE COMPLETE
ESM: ESM INFORMATION REQUEST //ESM信息请求 ESM: ESM INFORMATION RESPONSE //ESM信息应答 EMM: IDENTITY REQUEST //身份请求(IMSI) EMM: IDENTITY RESPONSE //身份应答 UE CAPABILITY ENQUIRY //UE能力查询 UE CAPABILITY INFORMATION //UE能力应答 RRC CONNECTION RECONFIGURATION //RRC连接重配 RRC CONNECTION RECONFIGURATION COMPLETE //RRC连接重配完成 EMM: ATTACH COMPLETE / ESM: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT EMM: EMM INFORMATION
ESM: PDN CONNECTIVITY REQUEST //PDN连接请求 RRC CONNECTION RECONFIGURATION //RRC连接重配 RRC CONNECTION RECONFIGURATION COMPLETE //RRC连接重配完成 ESM: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT //默认承载建立
具体的SIP消息：
REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org SIP/2.0
f:
i: 559862608_185027992@192.168.1.1
v: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1775912190 Max-Forwards: 70
m:
Route:
P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 l: 0
Authorization: Digest uri=\6789@ims.mnc001.mcc001.3gppnetwork.org\
twork.org\Expires: 7200 k: path
Allow: INVITE,BYE,CANCEL,ACK,NOTIFY,UPDATE,REFER,PRACK,INFO,MESSAGE,OPTIONS
SIP/2.0 401 Unauthorized Max-Forwards: 70
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1775912190
From:
Allow: INVITE, ACK, CANCEL, BYE, PRACK, MESSAGE
WWW-Authenticate: digest realm=\ko6JtopNRZQTM1qu1w9soAAoN8UzWq73D0=\604283c04d\Content-Length: 0
REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org SIP/2.0
f:
i: 559862608_185027992@192.168.1.1
v: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3758589676 Max-Forwards: 70
m:
P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 l: 0
Authorization: Digest username=\ealm=\op=auth,nonce=\e=%ue=\Expires: 7200 k: path
Allow: INVITE,BYE,CANCEL,ACK,NOTIFY,UPDATE,REFER,PRACK,INFO,MESSAGE,OPTIONS
SIP/2.0 200 OK Max-Forwards: 70
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3758589676
From:
Call-ID: 559862608_185027992@192.168.1.1 CSeq: 559862608 REGISTER
Allow: INVITE, ACK, CANCEL, BYE, PRACK, MESSAGE Date: Sat, 15 Nov 2014 16:24:51 GMT
P-Associated-URI:
Contact:
2. 主叫流程
融融融融APP融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融融APP1融融融融融APP融融融融融INVITE融融融融Request-uri融融TEL融融2融融融融融融融3融融融融融融融融融融4融融融融融5融融融融融融融TEL URI6融融融融融融融SIP URI7融融融融融URI融融融融融融融融8融融融融融融融融融9融融融融融融融融融融融融融融融融融融融融融融融融融10融融融融融融融融融融APP11融融融APP融融180融融融融融融融融融融融融融12融融融融融13融融融融融14融融融180融融融融融融15融融融融融16融融融融融17融融融180融融18融融融180融融
SIP消息：
Request: INVITE sip:0123456789;phone-context=ims.gd.chinamobile.com@ims.gd.chinamobile. com;user=phone Status: 100 Trying Status: 180 Ringing
Request: PRACK sip:0123456789@192.168.1.2:55379;transport=udp
Status: 200 OK Status: 200 OK
Request: ACK sip:0123456789@192.168.1.2:55379;transport=udp Request: BYE sip:0123456789@192.168.1.2:55379;transport=udp Status: 200 OK
说明：
[MS --> NW] 手机语音呼叫用户0123456789 [NW --> MS] 网络回复100 Trying，开始寻呼
[NW --> MS] 网络回复180 Ringing，找到被叫，响铃振铃
[MS --> NW] 手机用PRACK回复100rel，通知网络已收到振铃消息 [NW --> MS] 网络回复200 OK (PRACK)
[NW --> MS] 网络回复200 OK (INVITE)，被叫应答 [MS --> NW] 主叫回复ACK，呼叫建立
……………………. ……………………. 通话中 ……………………. ……………………. [MS --> NW] 主叫发BYE挂机
[NW --> MS] 网络回复200 OK，挂断电话
空口消息如下：
DL UL UL DL UL UL
RRC CONNECTION RECONFIGURATION
RRC CONNECTION RECONFIGURATION COMPLETE
ESM: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT RRC CONNECTION RECONFIGURATION
RRC CONNECTION RECONFIGURATION COMPLETE ESM: DEACTIVATE EPS BEARER CONTEXT ACCEPT
//专用承载建立
//恢复默认承载
具体的SIP消息：
INVITE sip:0123456789;phone-context=ims.gd.chinamobile.com@ims.gd.chinamobile.com;user=phone SIP/2.0
f: \
t:
CSeq: 561128295 INVITE
i: 561128295_185090136@192.168.1.1
v: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3624637363 Max-Forwards: 70
m:
Route:
P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 P-Preferred-Identity:
Accept: application/sdp,application/3gpp-ims+xml
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
a: *;+g.3gpp.icsi-ref=\k: 100rel,replaces,from-change P-Early-Media: supported l: 435 v=0
o=root 5000 1000 IN IP4 192.168.1.1 s=QC VOIP
c=IN IP4 192.168.1.1 t=0 0
m=audio 50010 RTP/AVP 104 102 105 100 b=AS:41 b=RS:0 b=RR:0
a=rtpmap:104 AMR-WB/16000
a=fmtp:104 mode-change-capability=2;max-red=0 a=rtpmap:102 AMR/8000
a=fmtp:102 mode-change-capability=2;max-red=0 a=rtpmap:105 telephone-event/16000 a=fmtp:105 0-15
a=rtpmap:100 telephone-event/8000 a=fmtp:100 0-15 a=sendrecv
a=maxptime:240 a=ptime:20
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3624637363 Max-Forwards: 70
From: \
To: hone> Call-ID: 561128295_185090136@192.168.1.1 CSeq: 561128295 INVITE Content-Length: 0 SIP/2.0 180 Ringing Max-Forwards: 70 Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3624637363 From: \ To: Call-ID: 561128295_185090136@192.168.1.1 CSeq: 561128295 INVITE Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE Record-Route: Supported: precondition Supported: 100rel RSeq: 1 Privacy: none User-Agent: Anritsu-VirtualUA/4596 Content-Length: 0 Contact: P-Asserted-Identity: PRACK sip:0123456789@192.168.1.2:55379;transport=udp SIP/2.0 Max-Forwards: 70 From: \ To: Call-ID: 561128295_185090136@192.168.1.1 CSeq: 561128296 PRACK User-Agent: Anritsu-VirtualUA/4596 Content-Length: 0 v: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK4129161699 P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 RAck: 1 561128295 INVITE Route: SIP/2.0 200 OK Max-Forwards: 70 Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK4129161699 From: \ To: Call-ID: 561128295_185090136@192.168.1.1 CSeq: 561128296 PRACK Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE Record-Route: User-Agent: Anritsu-VirtualUA/4596 Content-Length: 0 Contact: SIP/2.0 200 OK Max-Forwards: 70 Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3624637363 From: \ To: Call-ID: 561128295_185090136@192.168.1.1 CSeq: 561128295 INVITE Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE Record-Route: Contact: o=anritsu 853 671855 IN IP4 192.168.1.2 s=- i=A VOIP Session c=IN IP4 192.168.1.2 t=0 0 m=audio 60000 RTP/AVP 104 102 105 100 b=AS:41 b=RS:0 b=RR:0 a=rtpmap:104 AMR-WB/16000 a=fmtp:104 mode-change-capability=2;max-red=0 a=rtpmap:102 AMR/8000 a=fmtp:102 mode-change-capability=2;max-red=0 a=rtpmap:105 telephone-event/16000 a=fmtp:105 0-15 a=rtpmap:100 telephone-event/8000 a=fmtp:100 0-15 a=sendrecv a=maxptime:240 a=ptime:20 a=rtcp:60001 ACK sip:0123456789@192.168.1.2:55379;transport=udp SIP/2.0 Max-Forwards: 70 Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK901577778 From: \ To: Call-ID: 561128295_185090136@192.168.1.1 CSeq: 561128295 ACK Content-Length: 0 Route: BYE sip:0123456789@192.168.1.2:55379;transport=udp SIP/2.0 t: f: \ i: 561128295_185090136@192.168.1.1 CSeq: 561128297 BYE v: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3262761237 Max-Forwards: 70 P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 l: 0 Route: P-Preferred-Identity: SIP/2.0 200 OK Max-Forwards: 70 Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK3262761237 From: \ To: Call-ID: 561128295_185090136@192.168.1.1 CSeq: 561128297 BYE Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE Record-Route: User-Agent: Anritsu-VirtualUA/4596 Content-Length: 0 Contact: P-Asserted-Identity: 3. 被叫流程 SIP消息： Request:INVITE sip:001010123456789@192.168.1.1:5060 Status:100 Trying Status:SIP/2.0 180 Ringing Status:SIP/2.0 200 OK Request: BYE sip:001010123456789@192.168.1.1:5060 Status: SIP/2.0 200 OK 说明： [NW --> MS] 网络寻呼sip:001010123456789@ims.mnc001.mcc001.3gppnetwork.org [MS --> NW] 手机回复100 Trying [MS --> NW] 手机回复180 Ringing，振铃 [MS --> NW] 手机回复200 OK，应答，被叫建立 ……………………. ……………………. 通话中 ……………………. ……………………. [NW --> MS] 网络发BYE挂机 [MS --> NW] 手机回复200 OK，挂断电话 空口消息如下： DL UL UL DL UL UL RRC CONNECTION RECONFIGURATION RRC CONNECTION RECONFIGURATION COMPLETE ESM: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT RRC CONNECTION RECONFIGURATION RRC CONNECTION RECONFIGURATION COMPLETE ESM: DEACTIVATE EPS BEARER CONTEXT ACCEPT //专用承载建立 //恢复默认承载 具体的SIP消息： INVITE sip:001010123456789@192.168.1.1:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2:60124;branch=z9hG4bKe9f77cafd88b452dab9752198ad5e94f28;rport;transport=udp Via: SIP/2.0/UDP 192.168.1.2:60115;branch=z9hG4bKf3b6a856a57d467e9437f54d214995ea21dbba51 Max-Forwards: 69 Call-ID: c64488da3d6644409c0b6324e3cd911c CSeq: 9001 INVITE To: From: Supported: precondition Accept-Contact: *;+g.3gpp.icsi-ref=\it User-Agent: Anritsu-VirtualUA/4596 Content-Type: application/sdp Content-Length: 569 Contact: P-Asserted-Identity: o=anritsu 9 457009 IN IP4 192.168.1.2 s=- i=A VOIP Session c=IN IP4 192.168.1.2 t=0 0 m=audio 60000 RTP/AVP 107 97 8 0 101 b=AS:64 b=RS:800 b=RR:2400 a=ptime:20 a=maxptime:20 a=rtpmap:107 AMR-WB/16000 a=fmtp:107 octet-align=1; mode-set=2 a=rtpmap:97 AMR/8000 a=fmtp:97 octet-align=1; mode-set=7 a=rtpmap:8 PCMA/8000/1 a=rtpmap:0 PCMU/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=mid:0 a=sendrecv a=rtcp:60001 a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos optiSIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.1.2:60124;branch=z9hG4bKe9f77cafd88b452dab9752198ad5e94f28;rport;transport=udp,SIP/2.0/UDP 192.168.1.2:60115;branch=z9hG4bKf3b6a856a57d467e9437f54d214995ea21dbba51 Call-ID: c64488da3d6644409c0b6324e3cd911c CSeq: 9001 INVITE To: From: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 192.168.1.2:60124;branch=z9hG4bKe9f77cafd88b452dab9752198ad5e94f28;rport;transport=udp,SIP/2.0/UDP 192.168.1.2:60115;branch=z9hG4bKf3b6a856a57d467e9437f54d214995ea21dbba51 Call-ID: c64488da3d6644409c0b6324e3cd911c CSeq: 9001 INVITE To: Contact: P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 Allow: INVITE,ACK,CANCEL,BYE,UPDATE,PRACK,MESSAGE,REFER,NOTIFY,INFO SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.2:60124;branch=z9hG4bKe9f77cafd88b452dab9752198ad5e94f28;rport;transport=udp,SIP/2.0/UDP 192.168.1.2:60115;branch=z9hG4bKf3b6a856a57d467e9437f54d214995ea21dbba51 Call-ID: c64488da3d6644409c0b6324e3cd911c CSeq: 9001 INVITE To: Contact: ervice.ims.icsi.mmtel\Record-Route: P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 k: 100rel,from-change Allow: INVITE,ACK,CANCEL,BYE,UPDATE,PRACK,MESSAGE,REFER,NOTIFY,INFO v=0 o=root 5000 1000 IN IP4 192.168.1.1 s=QC VOIP c=IN IP4 192.168.1.1 t=0 0 m=audio 50010 RTP/AVP 107 101 b=AS:30 b=RS:0 b=RR:0 a=rtpmap:107 AMR-WB/16000 a=fmtp:107 octet-align=1;mode-set=2;mode-change-capability=2;max-red=0 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:20 a=ptime:20 BYE sip:001010123456789@192.168.1.1:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.2:60126;branch=z9hG4bKe9f77cafd88b452dab9752198ad5e94f2c;rport;transport=udp Via: SIP/2.0/UDP 192.168.1.2:60115;branch=z9hG4bKf3b6a856a57d467e9437f54d214995eaae85bb3f Max-Forwards: 69 Call-ID: c64488da3d6644409c0b6324e3cd911c CSeq: 9002 BYE To: P-Asserted-Identity: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.2:60126;branch=z9hG4bKe9f77cafd88b452dab9752198ad5e94f2c;rport;transport=udp,SIP/2.0/UDP 192.168.1.2:60115;branch=z9hG4bKf3b6a856a57d467e9437f54d214995eaae85bb3f Call-ID: c64488da3d6644409c0b6324e3cd911c CSeq: 9002 BYE To: Record-Route: P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 4. eSRVCC (LTE --> GSM) SIP消息： None 说明： None 空口消息如下： No. Progress Time BTS 1 09:16.8 LTE1 2 09:16.9 LTE1 3 09:17.1 LTE1 4 09:17.2 LTE1 5 09:17.2 LTE1 6 09:17.2 LTE1 7 09:17.2 LTE1 8 09:17.2 LTE1 9 09:17.3 LTE1 10 09:17.3 LTE1 11 09:17.6 LTE1 12 09:17.7 LTE1 13 09:36.4 LTE1 14 09:36.6 GSM/GPRS2 15 09:36.6 GSM/GPRS2 16 09:36.6 GSM/GPRS2 17 09:36.6 GSM/GPRS2 18 09:36.6 GSM/GPRS2 19 09:36.6 GSM/GPRS2 20 09:36.6 GSM/GPRS2 21 09:36.6 GSM/GPRS2 Direction UL UL DL UL DL UL DL UL DL UL DL UL DL UL UL UL UL UL UL UL UL Message RRC CONNECTION REQUEST RRC CONNECTION SETUP COMPLETE EMM: AUTHENTICATION REQUEST EMM: AUTHENTICATION RESPONSE EMM: SECURITY MODE COMMAND EMM: SECURITY MODE COMPLETE SECURITY MODE COMMAND SECURITY MODE COMPLETE UE CAPABILITY ENQUIRY UE CAPABILITY INFORMATION RRC CONNECTION RECONFIGURATION RRC CONNECTION RECONFIGURATION COMPLETE MOBILITY FROM EUTRA COMMAND RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS 22 23 24 25 26 27 28 29 30 09:36.6 09:36.6 09:36.6 09:36.6 09:36.6 09:36.6 09:36.6 09:36.6 09:36.7 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 UL UL UL UL UL UL UL UL UL RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS RR: CHANNEL REQUEST / HANDOVER ACCESS 31 09:36.7 32 09:36.7 33 09:36.7 34 09:36.7 35 09:36.7 36 09:36.9 37 09:37.0 38 09:47.9 39 09:48.1 40 09:48.2 41 09:48.2 42 09:50.4 43 09:50.5 44 09:50.6 45 09:50.6 46 09:50.9 47 09:52.1 48 09:52.1 49 09:52.5 50 09:52.5 51 09:53.2 52 09:53.3 53 09:53.9 54 09:53.9 55 09:53.9 56 09:56.5 57 09:56.7 58 10:01.7 59 10:01.8 60 10:01.8 61 10:02.7 62 10:02.8 63 10:27.7 64 10:27.7 65 10:28.2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 GSM/GPRS2 LTE1 LTE1 LTE1 LTE1 LTE1 UL RR: CHANNEL REQUEST / HANDOVER ACCESS UL RR: CHANNEL REQUEST / HANDOVER ACCESS UL RR: CHANNEL REQUEST / HANDOVER ACCESS UL RR: CHANNEL REQUEST / HANDOVER ACCESS UL RR: CHANNEL REQUEST / HANDOVER ACCESS UL RR: HANDOVER COMPLETE UL RR: GPRS SUSPENSION REQUEST DL CC: DISCONNECT UL CC: RELEASE DL CC: RELEASE COMPLETE DL RR: CHANNEL RELEASE UL RR: CHANNEL REQUEST / HANDOVER ACCESS DL RR: IMMEDIATE ASSIGNMENT UL MM: LOCATION UPDATING REQUEST DL MM: AUTHENTICATION REQUEST UL RR: GPRS SUSPENSION REQUEST UL MM: AUTHENTICATION RESPONSE DL RR: CIPHERING MODE COMMAND UL RR: CIPHERING MODE COMPLETE DL MM: IDENTITY REQUEST UL MM: IDENTITY RESPONSE DL MM: LOCATION UPDATING ACCEPT UL MM: TMSI REALLOCATION COMPLETE DL MM: MM INFORMATION DL RR: CHANNEL RELEASE UL RR: CHANNEL REQUEST / HANDOVER ACCESS UL GPRS MM: Routing area update request UL RR: CHANNEL REQUEST / HANDOVER ACCESS UL GPRS MM: Routing area update request DL GPRS MM: Authentication & ciphering req UL RRC CONNECTION REQUEST UL RRC CONNECTION SETUP COMPLETE UL RRC CONNECTION REQUEST UL RRC CONNECTION SETUP COMPLETE DL EMM: AUTHENTICATION REQUEST 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 10:28.3 10:28.4 10:28.4 10:28.4 10:28.5 10:28.5 10:28.5 10:28.5 10:37.1 10:37.1 10:37.3 10:37.4 10:37.4 10:37.4 10:37.5 10:37.5 10:37.5 10:37.5 10:37.8 10:37.9 10:37.9 10:38.7 10:38.8 10:38.8 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 LTE1 UL DL UL DL UL UL DL DL UL UL DL UL DL UL DL UL DL UL DL UL UL DL UL UL EMM: AUTHENTICATION RESPONSE EMM: SECURITY MODE COMMAND EMM: SECURITY MODE COMPLETE EMM: TRACKING AREA UPDATE ACCEPT EMM: TRACKING AREA UPDATE COMPLETE ESM: BEARER RESOURCE MODIFICATION REQUEST EMM: EMM INFORMATION RRC CONNECTION RELEASE RRC CONNECTION REQUEST RRC CONNECTION SETUP COMPLETE EMM: AUTHENTICATION REQUEST EMM: AUTHENTICATION RESPONSE EMM: SECURITY MODE COMMAND EMM: SECURITY MODE COMPLETE SECURITY MODE COMMAND SECURITY MODE COMPLETE UE CAPABILITY ENQUIRY UE CAPABILITY INFORMATION RRC CONNECTION RECONFIGURATION RRC CONNECTION RECONFIGURATION COMPLETE ESM: BEARER RESOURCE MODIFICATION REQUEST RRC CONNECTION RECONFIGURATION RRC CONNECTION RECONFIGURATION COMPLETE ESM: DEACTIVATE EPS BEARER CONTEXT ACCEPT 具体的SIP消息： None 4. SMS over PS (Receive) SIP消息(安立MD8475A是通过4G发送的，无SIP消息)： None 说明： None 空口消息如下： No. Progress Time BTS Direction Message 1 2 3 4 04:54.3 04:54.3 04:54.3 04:54.3 LTE1 LTE1 LTE1 LTE1 DL UL UL DL EMM: DOWNLINK NAS TRANSPORT EMM: UPLINK NAS TRANSPORT EMM: UPLINK NAS TRANSPORT EMM: DOWNLINK NAS TRANSPORT 具体的SIP消息： None 5. SMS over PS (Send) SIP消息(安立MD8475A是通过4G发送的，无SIP消息)： None 说明： None 空口消息如下： No. 1 2 3 4 Progress Time 07:12.8 07:13.0 07:13.0 07:13.0 BTS LTE1 LTE1 LTE1 LTE1 Direction UL DL DL UL Message EMM: UPLINK NAS TRANSPORT EMM: DOWNLINK NAS TRANSPORT EMM: DOWNLINK NAS TRANSPORT EMM: UPLINK NAS TRANSPORT 具体的SIP消息： None 6. Deregister SIP消息： Request: REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org (remove 1 binding) Status: 200 OK (removed 1 binding) 说明： [MS --> NW] 手机断网 [NW --> MS] 网络回复200 OK 空口消息如下： No. 1 2 Progress Time BTS 35:39.5 LTE1 35:39.5 LTE1 Direction Message UL EMM: DETACH REQUEST DL RRC CONNECTION RELEASE 具体的SIP消息： REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org SIP/2.0 f: i: 561118703_185011576@192.168.1.1 v: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK2663585505 Max-Forwards: 70 m: P-Access-Network-Info: 3GPP-E-UTRAN-TDD; utran-cell-id-3gpp=0010100010000000 Expires: 0 l: 0 Authorization: Digest username=\ealm=\op=auth,nonce=\1118695\c6d55553a25424297fe4c604283c04d\k: path Allow: INVITE,BYE,CANCEL,ACK,NOTIFY,UPDATE,REFER,PRACK,INFO,MESSAGE,OPTIONS SIP/2.0 200 OK Max-Forwards: 70 Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK2663585505 From: Allow: INVITE, ACK, CANCEL, BYE, PRACK, MESSAGE Date: Sat, 15 Nov 2014 16:52:20 GMT P-Associated-URI: Contact: 三、参考文档 1.SIP消息 《41-融合通信接口规范（终端-平台接口分册）v1.0.0（技术参考版）.pdf》 《41-融合通信接口规范（终端-平台接口分册）v1.0.0（技术参考版）20140716.docx》 (两个文档内容一样，word格式易于搜索) 本标准规定了融合通信终端与平台之间交互所涉及的通信接口，是融合通信终端及平台网元设备需要遵从的技术文件，供中国移动内部使用，为融合通信平台业务的开发、建设、维护，以及融合通信终端的设计提供技术依据。 《IMS：IP多媒体子系统概念与服务》 (原书第3版) -- 纸质书籍 不仅描述了IMS关键概念、体系结构、主要过程和典型业务，而且针对IMS多媒体电话、IMS语音呼叫连续性、IMS转接、IMS本地号码、紧急会话、IMS中的通信服务标识、支持固网接入的新的认证模型、NAT穿越和全球可路由用户 代理URI等新内容进行了深入浅出的剖析。《IMS:IP多媒体子系统概念与服务(原书第3版)》内容远远超越了简单的协议介绍，通过翔实而生动的典型流程和举例深入地揭示了IMS系统设计背后的思想和理念。《IMS:IP多媒体子系统概念与服务(原书第3版)》共分3部分，有13章，详细地分析了IMS注册、IMS多媒体电话以及语音呼叫连续性的例子，对每个实体上的过程进行详细介绍。 2. 空中接口消息 《VoLTE终端测试规范——通信功能和性能分册V1.0.0（报批稿）.pdf》 本标准规定了中国移动VoLTE终端通信功能和性能测试方法以及相关测试用例，包括IMS基本过程、补充业务、短消息能力、移动性以及性能测试，供中国移动内部和厂商共同使用；适用于中国移动VoLTE终端，是中国移动通信集团公司及省公司内部进行的VoLTE终端功能和性能测试时的技术依据。 3. 高通的文档 《80-NF124-1_D.pdf》 网络结构，注册、呼叫流程介绍，较详细 《80-NE962-1_A_LTE_AS_Typical_Field_Scenarios_Checklists.pdf》 check list & log keyword 《80-N9839-1_G_IMS_Config_Overview.pdf》 对IMS涉及的NV参数的详细说明 《AU80-NJ394-1_A_IMS_VT_Overview.pdf》 视频电话流程 《80-NP815-1_A_E911_Call_Flows_Log_Analysis_Overview.pdf》 紧急呼叫流程 《80-NP686-1_B_Configuring_UE_Using_Binary_Modem_Configuration.pdf》 二进制Modem配置(CMCC测试相关) 《80-NP425-1_C_CMCC_Device_Config_Testing_Information.pdf》 CMCC测试配置手机