espace mobile failed to connect to the server

A mobile client has connected to an intranet wireless router and obtained an intranet IP address (this IP address is on the switch network where the ECS server is located). When a user uses a UC account added on the BMU to log in to the mobile client, a message is displayed, indicating that the server fails to be connected and prompting the user to check network configurations.

On the UC2.2 network, when a user attempts to log in to the mobile client, a message is displayed, indicating that the server fails to be connected and prompting the user to check network configurations. All components on the server use the Windows Server 2008 operating system and databases use the SQL Server 2008 operating system.

Possbile reason：

The MAA or BMU service file is configured incorrectly on the ECS server, causing the communication failure between the client and server.

Solution :

2. Check MAA service configurations. The MAA service file server_config.xml is configured correctly. For details about how to check the service, see section "Verifying the Basic Voice Call Service of eSpace Mobile Clients" in the eSpace UC Product Documentation.

3. Check BMU service configurations. The BMU service is configured correctly, the server ID is mobile, and the server address is MAA server IP address:7800. For details about how to check the service, see section "Verifying the Basic Voice Call Service of eSpace Mobile Clients" in the eSpace UC Product Documentation.

4. Locate the fault based on run logs of the MAA and BMU services. After comparison, the D:\Program Files\eSpace_UC\eSpace_UC_Server\Server\BMU\conf\server.xml file is configured incorrectly. The file content is as follows:

- <Context path="/appServer" docBase="appServer" debug="5" reloadable="false" crossContext="true">
  <Resource name="jdbc/mCentrex" auth="Container" type="javax.sql.DataSource" maxActive="50" maxIdle="100" maxWait="-1" username="eSpace_0713"password="8cd093434e40421a88d60fb8bd0799d3" driverClassName="oracle.jdbc.driver.OracleDriver"url="jdbc:oracle:thin10.174.3.19:1521/espace" removeAbandoned="true" removeAbandonedTimeout="600" timeBetweenEvictionRunsMillis="30000"minEvictableIdleTimeMillis="18000000" numTestsPerEvictionRun="100" />
  </Context>

In the file, the database IP address is set to the default value instead of the actual server IP address. This occurs because only the BMU is selected when the AppAgent_BMU.exe file is installed the first time, and the database fails to be connected when the AppAgent is installed the second time (users are prompted to connect to the database during BMU installation and are not prompted again during AppAgent installation).

5.Uninstall the BMU and re-install the AppAgent_BMU.exe file. During installation, select both the BMU and AppAgent components.