When a login fault occurs, error information is displayed on the eSpace Mobile. You can rectify the fault based on the error information, or view the error code in eSpace Mobile logs.
Table 1 lists the error codes.
|
Error Code |
Description |
Remarks |
|---|---|---|
|
-3 |
The account is locked. |
The account is locked due to multiple failed login attempts. Contact the administrator or wait for the system to unlock the account. |
|
The account is not enabled. |
Log in to the BMU and verify that the account exists. | |
|
The user name or password is incorrect. |
The user name does not exist, or the password is incorrect. Log in to the BMU and verify that the account exists. | |
|
The account does not have the right to use terminals of the current type. |
The account does not have the right to use the eSpace Mobile. Log in to the BMU and verify that the role of the account has the right to use the eSpace Mobile. | |
|
-10 |
The account does not have the right to use the eSpace Mobile. |
Log in to the BMU and verify that the role of the account has the right to use the eSpace Mobile. |
|
408 |
The protocol stack automatically sends reply messages. |
Generally, this error is caused by network disconnection and often occurs in the scenario where users log in to the eSpace Mobile from the extranet. Verify that the eSpace Mobile can communicate with the SBC or the public port number and IP address of the SBC after mapping on the firewall. |
Start the eSpace Mobile, go to the Fault Report screen, and tap Send Fault Report by Email. The email box for receiving logs will receive a file named in the format of espace_20140410120101.zip. Before collecting logs, ensure that the log function is enabled. If the log function is not enabled, enable it, reproduce the fault on the eSpace Mobile, and send the fault report.
eSpace Mobile log information varies for the Android and iOS systems.
|
Log File |
Content Summary |
Description |
|---|---|---|
|
UILog.log |
Records UI operation logs on the eSpace Mobile. |
Check this log file for faults related to UI breakdown. |
|
mip.log |
Records interaction logs between the eSpace Mobile and the MAA during the login, including:
|
Check this log file for faults that occur during the login. |
|
tup_audio.log tup_call.log tup_mediaservice.log tup_sdp.log tup_sdpnegotiation.log tup_video.log |
Record TUP platform logs. |
Check these log files for faults related to voice registration and calling. The tup_call.log file records the SIP voice registration process of the eSpace Mobile. |
|
Log File |
Content Summary |
Description |
|---|---|---|
|
eSpacelog.txt |
Records interaction logs between the eSpace Mobile and the MAA during the login, including:
|
Check this log file for faults that occur during the login. |
|
tup_audio.log tup_call.log tup_mediaservice.log tup_sdp.log tup_sdpnegotiation.log tup_video.log tup_offlinefile.log |
Record TUP platform logs. |
Check these log files for faults related to voice registration and calling. The tup_call.log file records the SIP voice registration process of the eSpace Mobile. |
