Mobile Client Login Faults

• ios: Open the mip.log file using a text editor and search for keywords "retval<return>". The value of retval<return> is the error code, and the information displayed is similar to the following. According to the error code, check the fault cause and solution.

  2015-05-26_14:35:09.488+0800[ECS][DEBUG]{msg.recv}decodeMsg() RECV msg = CC_Login.MT_ACK#32771 
      @LoginAckProcessor{
          [1]retval<return> : 0
          [2]desc : "success"
          [3]name : "*****"
          [4]mobile : ""
          [5]callno : "*****"
          [6]sex : "*"
          [7]headaddress : ""
          [8]mailaddress : ""
          [9]funcid : "1101101001000010010001001100000001000010011000000010010110001000"
          [10]imuserver : ""
          [11]imuport : ""
          [12]maxconfnum : 16
          [13]maxsmsnum : 30
          [14]voipunm : "81005"
          [15]voippin : "********[9]"
          [16]serverip : "200.75.206.21"
          [17]serverport : "5060"
          ...

• Android phone: Open the eSpacelog.txt file using a text editor and search for keyword "retval". The value of retval is the error code, and the information displayed is similar to the following. According to the error code, check the fault cause and solution.

  2015-04-18_11:00:14.615+0800[ECS][DEBUG(3)]msg.recv{650} XmlMsg.decodeBuf(XmlMsg.java:257) RECV msg = 
      @com.huawei.ecs.mip.msg.LoginAck {
          [sno] = -32681
          retval = 0
          desc = "success"
          name = "****"
          mobile = ""
          callno = "********[8]"
          sex = "*"
          headaddress = "3"
          mailaddress = ""
          funcid = "1101101001010000010001001100000001000010011000000010100110001101"
          imuserver = ""
          imuport = ""
          maxconfnum = 16
          maxsmsnum = 30
          voipunm = "01008600"
          voippin = "********[8]"
          serverip = "10.174.7.155"
          serverport = "5060"
          countrycode = ""
          useragent = "HUAWEI SoftCoPCA"
          ...

Use a text editor to open the mip.log or eSpacelog.txt file and check whether the following messages exist. If yes, the mobile client has sent messages. Then, review the log of the MAA.

• CheckVersion
• CheckVersionAck
• KeyExchange
• KeyExchangeAck
• Login
• LoginAck

• Server failure: Check whether the MAA service is started.
• Network problems: Run the ping command to check the network connectivity, check the firewall configuration, and check whether the port is enabled.