System configuration: 1MCU+15 terminals, E1 transmission
When convene conference, sound of main meeting place can send to sub meeting place, but can’t hear the sound of sub meeting place, sub meeting place line is connected correctly, and local terminal doesn’t mute. Observe the port state corresponding to MCU, it doesn’t long distance mute. Find out that we have to mute first then turn on the sound to make dialog from main meeting place to sub meeting place. After convening all meeting place into conference in second debugging, find out that the state is opposite. The sound of sub meeting place can be sent to main meeting place, but sub meeting place can’t hear the sound of other meeting place.
Check MCU corresponding parameters, find out the meeting is operated permanently, once the terminal start, it will join the conference immediately. See from the theory of our company’s TV system, each time the terminal quit the conference equals to drops off the conference. When terminal rejoins the conference, MCU will still keep the state of long distance mute of sound off.
1. Quit conference and rejoin, system is normal when all the meeting place don’t long distance mute or sound off.
2. After meeting place A long distance mute, A quit and rejoin the conference, still keeps the state of long distance mute, but MCU port shows it’s not long distance mute.
3. After meeting place A long distance sound off, A quit and rejoin the conference, still keeps the state of long distance sound off, but MCU port shows it’s not long distance sound off.
When terminal quits the conference and rejoins, MCU will not keep the state of long distance mute and sound off. Operate platform keeps on displaying that the terminal’s corresponding port long distance mute and sound off. Notice R&D, modify software and malfunction disappeared.