Good day, everyone!
This post will introduce you how to deal with the issue of a scheduled meeting probability failure. Please find more details on the topic as you read further down this post.
[Diagnostic]
Trying to schedule a high-definition conference on the userportal page, which fails probabilistically. When the failure occurs, the system prompts that the server is busy.
MediaX version: V300R008C60SPC100
[Analysis]
1. Analyzing the messages
Viewed the HTTP message tracking. No matter if the scheduled meeting succeeds or fails, the request to create the meeting will be sent to MediaX, which will exclude the problems on the portal. Whenever the scheduled meeting fails, the system prompts an internal error of the server.
2. Log analysis
The running log indicates that there is ’no valid MCU to use‘ in the response message received from the MRFC. It is speculated that MCU is not registered.
Ran the DSP MRS command and discovered that an MCU is configured, but why is there a probabilistic failure?
3. Analyzing the status of MCU
Ran the DSP MCU command on the MRFC and found that the MCU status was unstable. It is both the registration and unregistered statuses for a while.
Therefore, it can be confirmed that the scheduled conference failure is due to the fact that MCU is not registered on MRFC.
Confirmed with R&D, it may be the issue of MCU's SIP registration time. Logged in to the MCU's web page and checked the registration time, which was 50 and 300, which does not meet the configuration under IMS networking.
[Root cause]
MCU's re-registration interval and refresh interval are too long, resulting in the unstable MCU state on MRFC.
[Solution]
Modify MCU's re-registration interval and refresh interval to 5 and 10.
