No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The connection is interrupted after conference start, and rebooting fail.

Publication Date:  2012-09-24 Views:  94 Downloads:  0
Issue Description
After rebooting RMCC service, first conference is normal. But at the second time, after conference scheduling, the phenomenon of conference offline is occurred. The conference is convened unsuccessful after rebooting system several times.
Alarm Information
Conference offline is showed in RMCC information window. The conference is closed after rebooting system several times.
Handling Process
Since the conference number is collided with terminal number, we can modify MCU number to avoid it. Current area number is 097, so the conference number has 8 digits. If we modify the MCU area number to 0971, the conference number has 9 digits. Then there is no collision.
After modifying MCU area number, notice the following points:
1. If MCU version is 8620, pay attention to modify MIPU board area number configuration.
2. Modify the area configuration in service area management. Add the new MCU area number, otherwise there is no MCU resource in service area.
Root Cause
Log on 8630 MCU with visor user. Open and check the debugging messages in the process of conference scheduling.
Debugging command is shown below:
debug mc open_debug
trace on
Print debugging message:
H323Call->Debugging message: register conference number:10002
F:H323call_callctrl.C,L:107
H323CALL->Debugging message: receive conference number RRJ sent by GK.
F:H323call_callctrl.C,L:7631
Conf->Register error, reason:1 register time:0!
F:h323conf_callctrl.C,L:3317
H323Call->Debugging message: register conference number:10002
F:H323call_callctrl.C,L:107
H323Call->Debugging message: register conference number:10002
F:H323call_callctrl.C,L:107
Conf->Register error, reason:1 register time:1!
F:h323conf_callctrl.C,L:3317
H323Call->Debugging message: register conference number:10002
F:H323call_callctrl.C,L:107
H323CALL->Debugging message: receive conference number RRJ sent by GK.
F:H323call_callctrl.C,L:7631
Conf->Register error, reason:1 register time:2!
F:h323conf_callctrl.C,L:3317
Conf->Register error, delete conference!
F:h323conf_callctrl.C,L:3336

We can see that the registration is fault when the conference number is 10002, for the conference number is composed by MCU area number plus 5 digits. In this case, the MCU area number is 097, so the integral conference number is 09710002. Check 09710002 in GKM and we can find a terminal registered by this number.
Suggestions
We should consider the possibility of collision between conference number and terminal number during dividing area number.

END