Only the Chinese version of this page is provided currently. The English version will be provided soon.
Help & Documentation>腾讯会议>会议室连接器相关问题

Issues with Meeting Room Connector

Last updated: 2026-04-28 19:04:52

Issues with H.323/SIP Device Call

How to handle when Cisco Terminal H.323 cannot join the meeting?

The H.323 switch on the Cisco Terminal is turned on, but it cannot dial into Tencent Meeting via the H.323 protocol. Solution:
1. Log in to the Web management interface of the Cisco Terminal, click setup > configuration > H323.
2. Change the CallSetup Mode option to Direct. If using an H.323 account to call, select Gatekeeper.




How to handle a black screen upon joining the meeting with a Cisco H.323 Terminal?

When using the Cisco Terminal to dial into Tencent Meeting via the H.323 protocol, the Tencent Meeting side sees a black screen from the Cisco Terminal. Solution:
1. Enter the Web management interface of the Cisco Terminal to modify the configuration, click setup > configuration > conference.
2. Change VideoBandwidth Mode from Dynamic to Static.




How to handle when the Cisco Terminal can't receive screen sharing?

When the Cisco Terminal dials into Tencent Meeting via the SIP protocol, it cannot receive the auxiliary stream sent by Tencent Meeting. Solution:
1. Enter the Web management interface of the Cisco Terminal to modify the configuration, click setup > configuration > sip.
2. Change the mode in ICE to off.




How to handle when Huawei Terminal SIP cannot join the meeting?

Huawei Terminal using the SIP protocol is unable to join Tencent Meeting. Solution:
1. Using terminal administrator privileges, log in to the terminal's Web Interface, modify the configuration, click Network > Firewall.
2. Change the SIP call port, local SIP listening port, and SIP server listening port to 5060.




Issues related to H.323/SIP device registration

How to resolve if H.323/SIP device registration fails?

Possible causes and solutions for registration failure are as follows:
Reason
Measure
Terminal cannot access the public network
Switch to a different network to ensure the device can access the public network.
Enterprise network firewall port restrictions.
Modify the enterprise network firewall settings, open the corresponding ports according to the firewall port configuration requirements of the meeting room connector, and refer to:
Incorrect terminal registration parameter settings.
Check the configured short number, username, password, and gatekeeper address according to the operation configuration guide to ensure they are correct.
Account already registered by another terminal.
An H.323 account or SIP account can only be registered on one device. If the account is already registered, replace the H.323 account or SIP account.
Service unreachable due to DNS configuration restrictions.
Configure the gatekeeper/GK address as an IP address, and refer to: Meeting Room Connector Access Address.

After H.323 device registration, how to resolve the issue of successful content sharing display but the remote end not receiving the shared screen during a meeting?

When multiple H.323 devices share auxiliary streams simultaneously in the same meeting, an individual device may occasionally encounter a situation where the auxiliary stream is shown as sent successfully, but the remote end does not receive the shared screen. In this case, the party sharing the auxiliary stream can first stop sharing and then restart sharing the auxiliary stream.

How to resolve when the device fails H.323 authentication during H.323 registration?

If the device does not support entering the username and password for H.323 authentication, H.323 registration verification will fail. In this case, you can switch to using a SIP account for registration.

After successful H.323 device registration, inviting the device registration number to join the meeting but the terminal fails to respond, how to solve it?

If an H.323 device shows successful registration, but the terminal cannot answer when the device is invited to join a meeting by dialing its registered short number, the issue may be due to incomplete compatibility of the outbound call protocol. In this case, you can join the meeting by directly dialing the Tencent Meeting number from the registered device, or switch to using SIP for registration and outbound calls.

After successful H.323 device registration, inviting the device registration number to join the meeting but the call fails, how to solve it?

If an H.323 device shows successful registration, but the invitation to join a meeting fails when the registered short number is dialed, the registered device may not be supported by the cross-firewall outbound call protocol. In this case, you can join the meeting by directly dialing the Tencent Meeting number from the registered device, or switch to using SIP for registration and outbound calls.

Why Can't I Add New H.323/SIP Registration Accounts? Is There a Limit on the Number of H.323/SIP Registration Accounts per Enterprise Account?

If you cannot add a new H.323/SIP registration account, it may be because the number of currently created registration accounts has reached the upper limit. The maximum number of H.323/SIP registration accounts that can be created is three times the number of MRA licenses purchased by the enterprise.