Fault Symptom
UEs fail to perform voice service.
Fault Cause
The possible causes are as follows:
1. The user fails to register voice services.
2. A fault occurs on the service coordination mechanism (contact R&D personnel to locate the fault).
3. Disconnected with eCN.
Troubleshooting
Step 1 If the UE is connected to a eLTE3.3 eCN:
1. After receiving the service registration message, the eMDC returns 404 failure response. Check whether the UE has been registered to the eMDC.
2. After receiving the service registration message, the eMDC returns 403 failure response. Check whether a correct user password is configured on the eMDC.
Note: ubp_bcc.logs are required for the preceding troubleshooting.
Step 2 If the UE is connected to a eLTE3.4 eCN:
1. Check whether the UE has been correctly registered to the eUDC.
2. Check whether the password has been correctly configured.
3. Check whether the ipmapping is properly configured. On the Customized IP Addresses page of the eUDC, specify the IP network segment and the subnet mask.
Note:
l In eLTE3.4, RFC is used to identify whether the UE is from an external network or from an internal network. When configuring the ipmapping, set a public network address for an internal network and an enterprise network address for an external network. In the following example, an enterprise network address is used by default.
l If eXosip: osip_from_parse error sip:xxxx@:5060 is displayed, the ipmapping is configured incorrectly. Reset the ipmapping in the Customized IP Addresses page in the eUDC. Note that the network segment must be set to LAN IP.
4. On the eAPP Management system, choose System Monitoring > Service. Check whether all the processes are running.
Step 3 If is disconnected to eCN:
1. On the eAPP Management system, choose Alarm > Alarm Monitor. Check whether there is Communication Failure of SIP link alarm with eCN.
