Start the mobile client. On the Fault Report screen, tap Send Fault Report by Email. The mailbox receiving the log will receive a file named espace_20140410120101.zip. Before collecting the logs, ensure that the log function is enabled. If it is not enabled, enable it first, replicate the fault on the mobile client, and then send the fault report.
The following tables provide the mobile client logs. Logs in the Android operating system are slightly different from those in the iOS operating system.
Log File Name | Description | Remarks |
|---|---|---|
UILog.log | Logs UI operations of the mobile client. | You can review this log file for UI faults. |
mip.log | Logs interactions between the mobile client and the MAA during login, including:
| You can review this log file for login faults. |
tup_audio.log tup_call.log tup_mediaservice.log tup_sdp.log tup_sdpnegotiation.log tup_video.log | TUP platform logs. | You can review these log files for voice registration and call-related operations. The tup_call.log file records the SIP voice registration process of the mobile client. |
Log File Name | Description | Remarks |
|---|---|---|
eSpacelog.txt | Logs interactions between the mobile client and the MAA during login, including:
| You can review this log file for login faults. |
tup_audio.log tup_call.log tup_mediaservice.log tup_sdp.log tup_sdpnegotiation.log tup_video.log tup_offlinefile.log | TUP platform logs. | You can review these log files for voice registration and call-related operations. The tup_call.log file records the SIP voice registration process of the mobile client. |
