折腾:
【未解决】调试运行Android项目rcsjta的其他几个apk看看是否启动了rcs的core的service
期间,点击了
Generate RCS provisioning template
但是最后报错:

IOException occurred Unable to resolve host config.rcs.mnc009.mcc460.pub.3gppnetwork.org No address associated with hostname !
去搜:
config.rcs.mnc009.mcc460.pub.3gppnetwork.org
Official Document IR.67 – DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers
DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers
Version 10.0 24 April 2014
- ENUM
- E.164 Number Mapping
- ESP
- ENUM Service Provider
- FQDN
- Fully Qualified Domain Name
和此处相关的:
6.5 Delegation of sub-domains of “pub.3gppnetwork.org”
GSMA can delegate a sub-domain of pub.3gppnetwork.org to DNS of an MNO.
1. Identify CNAME record for the domain to be transferred.
The CNAME record shall be in format of:
- <ABC>.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org
- where
- acceptable values of <ABC> are defined in 2.3.4 (other values might be added as needed; see also NOTE 2 below)
- 1. 2.3.4 Domain names used on the Internet DNS (and owned by GSMA)
- <MNC> and <MCC> have to be replaced by respective values of the home network in decimal format, with a 2-digit MNC padded out to 3 digits by inserting a 0 at the beginning.

找到:
rcs.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org Where <MNC> and <MCC> are the MNC and MCC of the Service Provider represented in decimal (base 10) form, with any two (2) digit MNC padded out to three (3) digits by inserting a zero ("0") on the beginning for example 15 becomes 015. Used for the RCS/RCS-e service. RCS/RCS-e service may use further subdomain names depending on the RCS/RCS-e service evaluation and developments (for example config.rcs.mnc<MNC>.mcc<MCC >.pub.3gppnetwork. org). The description and the use of the subdomain names will be referenced in the RCS/RCS-e specifications where this domain can be used by all RCS/RCS-e versions. Each Service Provider is allowed to use only sub-domains consisting of MNC(s) and MCC(s) that are allocated to them by ITU-T and their local national numbering authority.


- Domain Name
- telekom.de
- Hostname
- epdg.epc.mnc001.mcc262.pub.3gppnetwork.org
- ISP
- Telekom Deutschland GmbH
- City
- Bonn, Nordrhein-Westfalen
epdg.epc.mnc001.mcc262.pub.3gppnetwork.org Subdomains * epdg.epc.mnc007.mcc425.pub * mnc010.mcc226.pub * ftcontentserver.rcs.mnc002.mcc652.pub * epc.mnc049.mcc404.pub * epdg.epc.mnc873.mcc405.pub * mnc001.mcc214.pub * config.rcs.mnc670.mcc312.pub * preprod.config.rcs.mnc001.mcc240.pub * hdn.ftcontentserver.rcs.mnc007.mcc460.pub * epdg.epc.mnc016.mcc502.pub * event.aes.mnc856.mcc405.pub * epdg.epc.mnc002.mcc238.pub * epc.mnc051.mcc440.pub * preprod.config.rcs.mnc010.mcc208.pub * mcc716.pub * 。。。 * mcc208.pub * epdg.epc.mnc450.mcc310.pub * ftcontentserver.rcs.mnc015.mcc234.pub * epdg.epc.mnc490.mcc302.pub * epdg.epc.mnc022.mcc404.pub * mcc272.pub * epdg.epc.mnc011.mcc404.pub

中国联通VoLTE-局数据规范-v0.doc
12. 169 DNS局数据设置原则... 105 12.1 *.mnc001.mcc460.pub.3gppnetwork.org解析数据.. 105 12.2 *.mnc006.mcc460.pub.3gppnetwork.org解析数据.. 106 12.3 *.mnc009.mcc460.pub.3gppnetwork.org解析数据.. 107 1.1 *.mnc009.mcc460.pub.3gppnetwork.org解析数据 对于以下域名: *.mnc009.mcc460.pub.3gppnetwork.org 权威DNS服务器上配置如下数据: 1. 业务设置代理网关XCAP 的域名: xcap. ims. mnc009.mcc460.pub.3gppnetwork.org DNS为该域名解析开启智能解析功能,配置view列表,根据发起DNS查询的源IP地址(IP地址段以北分、南方两个大区区分)不同,对于北方发起的查询将XCAP域名解析为Ut的IP地址列表,北方Ut为高优先级、南方的Ut为低优先级。对于南方省份发起的查询将XCAP域名解析为Ut的IP地址列表,南方Ut为高优先级、北方的Ut为低优先级。 1. BSF的域名:bsf. mnc009.mcc460.pub.3gppnetwork.org DNS为该域名解析开启智能解析功能,配置view列表,根据发起DNS查询的源IP地址(IP地址段以北分、南方两个大区区分)不同,对于北方发起的查询将BSF域名解析为Ut的IP地址列表,北方Ut为高优先级、南方的Ut为低优先级。对于南方省份发起的查询将BSF域名解析为Ut的IP地址列表,南方Ut为高优先级、北方的Ut为低优先级。 1. ePDG设备域名:epdg. mnc009.mcc460.pub.3gppnetwork.org DNS为该域名解析开启智能解析功能,配置view列表,根据发起DNS查询的源IP地址(IP地址段以省为单位区分)不同,将ePDG域名解析为不同的 IP地址并返回。例如:对于A省DNS发起的查询,将ePDG域名解析为A省ePDG设备的IP地址。 上述域名为新增域名,具体申请步骤需参照《中国联通互联网域名管理办法》执行。
目前不知道如何解决此错误
只不过清楚了一些细节了:
config.rcs.mnc009.mcc460.pub.3gppnetwork.org
是对应的
mnc009.mcc460.pub.3gppnetwork.org
的一个子域名
后续需要再去深究。
转载请注明:在路上 » 【未解决】rcsjta中provisioning即RCS template运行报错:IOException occurred Unable to resolve host config.rcs.mnc009.mcc460.pub.3gppnetwork.org