Selected Cases for IMS Troubleshooting: http://support.huawei.com/carrier/docview?nid=SCL1000000486

 

--------------------------------------------------------------------------------------------------------------------------------------------------------

Symptom

When calls are made using the SIP terminal and software client, the Request-URIs sent by the SIP terminal and software client are in different formats.

Problem Analysis

Currently, the common SIP software clients that are put to test are X-Lite, MC, and eyeBeam. When these software clients are used to initiate calls, the Request-URI is a SIP URI. However, when the SIP terminal is used to initiate calls, the Request-URI is a tel URI.

Handling Procedure

To enable the SIP software client to set the Request-URI to a tel URI for outgoing calls, use either of the following methods:

• Set Domain to ims.lkhnlab.cox.net;user=phone on the SIP software client. When the SIP software client is used to initiate a call, the Request-URI is sip:12148885555@ims.lkhnlab.cox.net;user=phone, which is equivalent to a tel URI. Figure 1 shows how to set the SIP software client.

  Set the following parameters on the SIP software client: User name, Password, Authorization name, Domain, and Sip proxy. When the SIP software client is used to initiate calls, Domain is mainly used for setting the Request-URI. Typically, Domain is set to ims.huawei.com. After this setting, when the SIP software client is used to initiate a call, the Request-URI is set to a SIP URI, for example, sip:123456@ims.huawei.com.

  Figure 1 Setting Domain on the SIP software client
  mk:@MSITStore:\\hwrnd-fs\szx01\CNP_info_F\08-项目文件夹\01-IMS资料部\00-IMS资料项目部\21-资料满意度\01-推送材料\07-2014年IMS期刊\故障案例\第三期\Troublesh_case_en.chm::/Troublesh_Case/figure/eyeBeam.png

  
  

• On the SIP software client, dial a number in "tel+number" format.

  For example, when tel:123456 is dialed on the SIP software client, the Request-URI in an outgoing message is tel:123456.

Suggestion and Summary

None.

 

Specific and workable which can help people efficiently locate network faults.

This document is very well done