在VOLTE和VONR通话中一个关键的网元就是IMS，而SIP消息会话地址之间存在着一定的相关性；如果这些相关性没能正确匹配，可能得到的只有错误消息“404 not found”；
IMS/SIP消息中的地址选取，取决于其规范类型 (RFC、3gpp、承载规范等) 及在相同规范的不同版本。本文旨在为您提供一些指南，并帮助您缩小搜索范围，做为查找这些问题中“寻址“工具；
1.注册和邀请（Register&Invite）地址结构
1.1 注册（Register）消息内容
根据TS.34 229-1 V10.2.0 (2013-07) A.1,终端在IMS中注册包括以下内容：
Header/param | Value/remark | Ref |
Request-URI | SIP URI formed from home domain name as stored in EFDOMAIN (when using ISIM) or SIP URI formed from home domain name derived from the IMSI (when no ISIM available on the UICC) | RFC 3261 |
From | any IMPU within the set of IMPUs on ISIM (when using ISIM) or public user identity derived from px_IMSI (when no ISIM available on the UICC) same public user identity as in initial REGISTER public user identity derived from px_IMSI px_EmergencyPublicUserIdentity (if the UE is already registered to IMS or if the UE is using ISIM) or public user identity derived from px_IMSI (when UE is using USIM and UE is not yet registered to IMS) | RFC 3261 |
To | any IMPU within the set of IMPUs on ISIM (when using ISIM) or public user identity derived from px_IMSI (when no ISIM available on the UICC) same public user identity as in initial REGISTER public user identity derived from px_IMSI px_EmergencyPublicUserIdentity (if the UE is already registered to IMS or if the UE is using ISIM) or public user identity derived from px_IMSI (when UE is using USIM and UE is not yet registered to IMS) | RFC 3261 |
Contact Feature Param | SIP URI with IP address or FQDN and indicating either an unprotected port selected by the UE or no port at all. When A7 the SIP URI shall contain the sos URI parameter. SIP URI with IP address or FQDN and protected server port of UE. When A7 the SIP URI shall contain the sos URI parameter. +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gppservice.ims.icsi.mmtel" +g.3gpp.smsip video +sip.instance media feature tag with the instance ID of the UE |
|
1.2 邀请（Invite）消息内容
根据TS 34 229-1 V10.2.0 (2013-07) A.2.9,终端在IMS中邀请时包括以下内容：
Header/param | Value/remark | Ref |
Request-URI | UE"s registered contact address in SIP URI form, as provided in the Contact header of the REGISTER message UE"s contact address in SIP URI form, as provided in the Contact header within any response or request within the dialog | RFC 3261 |
From | an SIP URI of the SS representing the calling UE SIP URI of SS (i.e. the remote UE) as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in To header within requests sent by the UE and in From header within requests sent by the SS) | RFC 3261 |
To | SIP or TEL URI of the UE SIP URI of the UE as used in any previous request in the same dialog (In the earlier requests within the same dialog this URI appears in From header within requests sent by the UE and in To header within requests sent by the SS) | RFC 3261 |
Contact | SIP URI with IP address or FQDN and protected server port of the calling UE, for example 'sip:caller@3gpp.org:6543'. SIP URI with IP address or FQDN and unprotected server port of the calling UE. |
|
2.用户及通知（SUBSCRIBE / NOTIFY）消息地址结构
3.（被叫）邀请和再见（INVITE / BYE)中地址结构
4.起始到目地（From / To for whole VoLTE Sequence）VOLTE通话地址结构
原文来自：http://www.sharetechnote.com/
整理：kangguoying20200923
"5G(NR)网络中MIB消息及案例”已在微信公众号"跟着老康学5G"中推出，敬请关注！
扫码关注5G通信官方公众号,免费领取以下5G精品资料
1、回复“LTBPS”免费领取《《中国联通5G终端白皮书》》
2、回复“ZGDX”免费领取《中国电信5G NTN技术白皮书》
3、回复“TXSB”免费领取《通信设备安装工程施工工艺图解》
4、回复“YDSL”免费领取《中国移动算力并网白皮书》
5、回复“5GX3”免费领取《 R16 23501-g60 5G的系统架构1》
6、回复“iot6”免费领取《【8月30号登载】物联网创新技术与产业应用蓝皮书——物联网感知技术及系统应用》
7、回复“6G31”免费领取《基于云网融合的6G关键技术白皮书》
8、回复“IM6G”免费领取《6G典型场景和关键能力白皮书》
关注楼主