Hello, dear!
Have a good day!
The topic describes meeting MS error codes.
you can find error codes in Meeting MS logs and check the error code description to find causes and solutions.
You can obtain error codes from Meeting MS logs stored in:
Windows: Installation directory\eSpaceMeetingMS\trace\Date
Linux: /home/econf/ms/trace/Date
Log file name format: Module name_Process ID_HHMMSS.log. For example:
mcmsrc_23872_083017.log: msrc log file, which is the key log file for locating conference joining faults.
mccaches_9638_105824.log: caches log file, which is the key log file for locating document sharing and transfer faults.
mcmgw_9635_095402.log: mgw log file, which is the key log file for locating call and voice faults.
mcms_9639_083017.log: ms log file, which is the key log file for locating conference and network faults.
mcsagt_9633_083017.log: mcsagt logs, which is the key log file for locating cluster faults.
Log format: <Time,tId=Process ID> Log level - [File name:Row number] [Module number] Log content
<15-11-13,10:53:56-082, tId=3661707008> INF - [mctc.cpp: 398] [TC_704684600_65601537_10.135.19.29_1] connect_response: result=IMCC_RESULT_AUTH_FAILED, nat_addr=10.135.19.29:55921
Table-1 Meeting MS error codes
Error Message | Error Code | Possible Cause |
IMCC_RESULT_NETWORK_ERROR | 2 | Network connection error. |
IMCC_RESULT_TOO_MANY_CONNECTIONS | 5 | The number of connections on the server reaches the maximum. |
IMCC_RESULT_DOMAIN_TERMINATED | 7 | The conference has ended. |
IMCC_RESULT_SERVER_UP_CONN_FAILED | 8 | Failed to connect to the upper-level server. |
IMCC_RESULT_AUTH_FAILED | 26 | Authentication fails because the conference password is incorrect. |
IMCC_RESULT_QUERY_PARENT_OR_TOP_AGENT_EXPIRED | 29 | Authentication fails because the conference password is incorrect. |
IMCC_RESULT_DOMAIN_LOCKED | 30 | The conference has been locked, and you cannot join the conference. |
IMCC_RESULT_AUTH_TIMEOUT | 31 | Conference authentication times out, and you cannot join the conference. |
IMCC_RESULT_AUTH_KEY_NOT_AVAILABLE | 32 | The authentication key is unavailable, and you cannot join the conference. |
IMCC_RESULT_TOO_MANY_CONFERENCE | 33 | The number of conferences on the server reaches the maximum, and you cannot join the conference. |
IMCC_RESULT_TOO_MANY_CONFERENCE_USER | 34 | The number of participants in the scheduled conference reaches the maximum, and you cannot join the conference. |
IMCC_RESULT_NOT_DATA_USER_LICENSE | 35 | The number of data users reaches the maximum specified by the license, and you cannot join the conference. |
IMCC_RESULT_AUTH_LINCENSE_TIMEOUT | 36 | License authentication times out, and you cannot join the conference. |
IMCC_RESULT_SVR_NOT_ALLOW | 37 | The server area is not allowed, and you cannot join the conference. |
IMCC_RESULT_USER_NOT_ALLOW | 38 | You have joined the conference and cannot join the conference again. |
Common error codes will be reported to the data conference web client. The following describes the solutions for common error codes reported to the client.
NOTE:
On the client, you must subtract 100 from an error code that is reported to find the corresponding error code in logs. For example, if error code 102 is reported to the client, the actual error code is 2 in logs.
102: Network Connection Error
Symptom
The data conference client cannot connect to the Meeting MS.
Troubleshooting
1. The mcms service is not started. You can log in to the Meeting MS and check whether the mcms service is started.
Solution: Start the mcms service.
2. The Meeting MS address used by the data conference client is incorrect. You can search for join_request in client logs and check whether the svr_addr value in the same row is correct.
Solution: Configure the correct Meeting MS address on the BMU.
3. A firewall is deployed between the data conference client and the Meeting MS. The client connects to port 1124 on the Meeting MS. Check whether port 1124 (TCP and UDP) is enabled on the firewall.
Solution: Enable port 1124 on the firewall.
4. The Meeting MS is installed on a server with dual network adapters. Check whether the listening IP address is correct in the conf.xml and cluster.xml files.
Solution: Change the local IP address in configuration files to the required listening IP address, and restart the service.
105: Number of Connections on the Server Reaches the Maximum
Symptom
The number of connections on the Meeting MS reaches the maximum.
Troubleshooting
netstat -anp|grep 1124|grep mcms
Count the number of connections. By default, the maximum number of connections is 800 for each server. This error is reported when the number of connections reaches the maximum.
Solution
Expand the capacity.
108: Failed to Connect to the Upper-Level Server
Symptom
Failed to connect to the upper-level server.
Troubleshooting
Meeting MSs with parent Meeting MSs configured fail to connect to parent Meeting MSs, or parent Meeting MSs fail to connect to the top Meeting MS. Refer to the troubleshooting procedure for error code 102.
126 and 131: Conference Authentication Failure and Timeout Error
Symptom
The data conference authentication password is incorrect or authentication times out.
Troubleshooting
1. Check whether the gateway address is correctly configured.
In data conference client logs, search for join_request and check whether the site_url value is the gateway address.
Solution: Configure the gateway address correctly on the BMU, restart the BMU and eServer, and log in to the data conference client again.
2. Check whether trunks to Meeting MSs (port number: 5092) are configured on the gateway.
Solution: Configure trunks to all Meeting MSs on the gateway.
3. Check the network connection between the gateway and the data conference authentication server.
Solution: Enable UDP port 5092 on the firewall.
4. Check whether time is consistent among the BMU, eServer, and gateway. If no, the conference may have not been scheduled.
Solution: Synchronize time among the BMU, eServer, and gateway.
5. Check whether the data conference cluster service is running properly. Verify that the mcsagt service is started and the 6jf1 cluster exists.
Solution: Verify that the local IP address is correctly configured in the conf.xml and cluster.xml files. Start the data conference cluster service.
129: Cluster Service Is Not Running Properly
Symptom
The cluster service is not running properly, and load balancing fails.
Troubleshooting
Check whether the mcsagt service is running properly, and the listening IP address is correct.
Refer to the troubleshooting procedure for error code 126.
Solution
Verify that the local IP address is correctly configured in the conf.xml and cluster.xml files. Start the data conference cluster service.
Thanks for reading!!
