Skip to main content
This guide uses a Huawei CloudLink endpoint as the example. Other brands use different menu names, but you fill in the same information. Before you start, read the Room Connector overview to decide between “endpoint registration” and “direct IP”. Have this information ready:
The endpoint registers to the device gateway with an account, so the platform can see whether it’s online and dialing needs only the meeting ID.

​
1. Create an account in the admin console

Open Device management in the admin console, choose the SIP (or H323) tab → Endpoint registration → Add account: Add a SIP account The H.323 dialog has the same fields: Add an H.323 account

​
2. Enter the registration details on the endpoint

SIP endpoint: find the SIP server (registrar) settings, enable registration, and enter: Huawei endpoint SIP registration settings H.323 endpoint: find the gatekeeper (GK) settings, enable registration, and enter: Huawei endpoint H.323 registration settings

​
3. Confirm it’s online

The endpoint usually shows “Registered”. Back in the admin console, when the account status changes to Online, registration has succeeded: Endpoint registration list Can’t register? See the FAQ.

​
Option 2: Direct IP

Use this when the endpoint doesn’t support registration or has a fixed IP. The platform must be able to reach the endpoint’s IP directly. Go to Device management → SIP (or H323) → Direct IP → Add device: Add a direct IP device Direct IP devices have no online status, so -- in the list is normal.

​
Bring the endpoint into the meeting

​
The endpoint dials in

On the endpoint’s call screen, enter the number and call it like a phone call: Registered endpoints: dial only the meeting ID. Registered endpoint dialing the meeting ID Unregistered endpoints: dial meetingID@deviceGatewayAddress. Unregistered endpoint dialing meetingID@gatewayAddress Once the call connects, the endpoint enters the meeting directly and sees the composite video of the whole meeting.
The device gateway can enable an incoming-call IP allowlist; when it’s on, only endpoints on the list can dial in. It’s configured at deployment as needed. If dial-in is rejected, first ask the deployment team whether the allowlist is on.

​
The platform invites the endpoint

The endpoint receives an incoming call and enters the meeting when answered (or directly, if the endpoint is set to auto-answer). There are three entry points: Admin console: Meeting management → open the meeting details → Invite → Invite device → Conferencing endpoints, select the endpoints, and confirm. Inviting a device from the admin console Meeting client: during the meeting, the host clicks Invite → Invite device, selects the endpoints, and sends the invitation. Inviting a device from the meeting client Business system via API: call Invite devices to the channel; see the Device integration guide for how. The host side of the conferencing SDK also has a corresponding method (such as adminInviteAgent on Web).

​
During the meeting

  • The endpoint is a member of the meeting, named by its “Display name”
  • The endpoint sees the whole meeting composited by the MCU and hears the mixed audio of the whole meeting
  • The host can turn the endpoint’s microphone and camera on or off and remove the endpoint from the meeting from the meeting client or the console; removing it hangs up the endpoint
  • If the endpoint hangs up, it exits the meeting

​
Registering endpoints to a third-party platform

If the customer already has its own SIP server or H.323 gatekeeper, the device gateway can also register to it as an endpoint and call devices there. This must be configured at deployment; contact us.