When the SMC2.0+ViewPoint 8650 initiates a conference by calling site IP addresses, all sites fail to join the conference, returning an error saying that the destination is unreachable.
ViewPoint 8650: V100R008C03SPC500
Traversal between public and private networks is not configured for the SMC2.0. A conference can be successfully initiated using the VP9650 and the sample conference template.
Network configuration: The SMC2.0 and MCU are on the same switch and belong to the same network segment. The terminal is in another network segment. The MCU can directly ping the IP address of each terminal.
1. The SMC2.0 fails to initiate a conference, with an error saying that the destination is unreachable. However, a conference can be successfully initiated using the VP9650 and the sample conference template. Check the network configuration of the ViewPoint 8650 and VP9650 MCU. No special configuration is found. They are in the same network segment.
2. Check on the SMC2.0 and find that no area is configured for the SC. Both the VP9650 and ViewPoint 8650 are registered with the embedded SC. All terminals are not registered and are called by their IP addresses.
3. Capture signaling packets from the SMC2.0, MCU, and terminals.
The signaling sent by the ViewPoint 8650 MCU is not directly sent to the terminals but is sent to the SC, which then forwards the signaling to the terminals.
Take one terminal as an example:
However, no signaling is received on the terminal. This indicates that the network between the SC and the terminal is abnormal.
4. According to analysis on this networking scenario, a conference can be successfully initiated through the following methods, without changing the network from the SMC2.0 to the terminals.
Method 1: Log in to the MCU web interface, and disable GK and SIP for the ViewPoint 8650. (The prerequisite is that a terminal will be directly called by its IP address.)
Method 2: On the SMC2.0, choose device > SC to change the SC setting by modifying the signaling routing policy from automatic to not routed.
Either of these methods can solve the problem.
The MCU signaling cannot be transferred from the SC to the terminals due to network issues between the SC and the terminals.
Disable GK and SIP for the MCU and disable the signaling routing policy for the SC.