# Manually Register an Htek IP Phone with Cloud Voice If you prefer to set up an Htek desk phone by hand rather than through auto provisioning, you can enter the extension's SIP (Session Initiation Protocol) credentials directly in the phone's web interface. SIP is the signaling standard that lets the phone register with, and place calls through, Cloud Voice. This walkthrough uses an Htek UC921G running firmware 2.0.4.8.18 as its example, but the same steps apply to any Htek phone that supports SIP. The task has two halves: first you collect the extension's registration details from Cloud Voice, then you type those details into the phone. :::note Manual registration is best for a one-off phone or for troubleshooting. If you are deploying several phones, auto provisioning is faster and less error-prone because it pushes the settings to each phone automatically. ::: ## Supported devices Any Htek IP phone that supports the SIP standard. ## Step 1. Collect the registration details from Cloud Voice Sign in to the Cloud Voice web portal and record the values below. You will type them into the phone in Step 2. Cloud Voice acts as your PBX (Private Branch Exchange), the phone system that registers extensions and routes calls. **Extension credentials** Go to **Extension and Trunk > Extension**, click the edit icon ![edit](/images/pbx/edit.png) next to the extension, then open **User > Extension Information** and note down: - Extension Number - Registration Name - Registration Password ![Extension Information panel listing the extension number, registration name, and registration password](/images/pbx/extension-information.png) :::note These three values are separate. The Registration Name and Registration Password are the SIP credentials the phone uses to authenticate, and they are usually not the same as the Extension Number. Copy each one exactly, including capitalization. ::: **Transport protocol** Go to **Extension and Trunk > Extension**, click the edit icon, then open **Advanced > VoIP Settings** (VoIP stands for Voice over Internet Protocol) and note the value in the **Transport** field. This tells you how SIP signaling travels between the phone and Cloud Voice. The options are UDP (User Datagram Protocol), TCP (Transmission Control Protocol), and TLS (Transport Layer Security). This example uses UDP. ![Cloud Voice, VoIP Settings showing the extension's transport protocol set to UDP](/images/pbx/extension-transport-protocol.png) :::caution The transport protocol you set on the phone must match the extension's transport on Cloud Voice, and that protocol must be enabled on the PBX, or registration will fail: - For **TCP**, confirm the SIP TCP port is turned on under **PBX Settings > SIP Settings > General > Basic**. ![PBX Basic SIP settings with the TCP port enabled](/images/pbx/ext-reg-open-tcp.png) - For **TLS**, confirm TLS is turned on under **PBX Settings > SIP Settings > TLS**. ![PBX SIP settings with TLS enabled](/images/pbx/ext-reg-open-tls.png) ::: :::tip TLS encrypts SIP signaling, so it is the most secure choice. If security matters for this deployment, set the extension to TLS on Cloud Voice first, then select TLS on the phone in Step 2 so both ends agree. ::: **PBX domain name** The domain name your Cloud Voice system is reached at. This example uses `pbx.example.com`. **SIP registration port** The default SIP registration port is `5060`. ## Step 2. Register the extension on the Htek phone 1. Sign in to the phone's web interface. ![Htek phone web login page](/images/pbx/log-into-htek.png) a. In your browser's address bar, enter the phone's IP address. b. Enter the username `admin` and its password. On a factory-default phone the password is also `admin`. c. Click **Sign in**. :::caution Leaving the default `admin` / `admin` login in place lets anyone on the network reconfigure the phone, which is a toll-fraud and eavesdropping risk. Change the admin password to a strong, unique value once registration is confirmed. ::: 2. Go to **Profile > Basic** and edit a profile for registration. A profile holds the shared connection settings (server and transport) that one or more accounts can reuse. a. Set the following, then note which profile you edited so you can select it later: ![Htek profile settings with the primary SIP server and transport configured](/images/pbx/htek-registration-pce.png) - **Primary SIP Server**: Enter the PBX domain name. - **SIP Transport**: Select the extension's transport protocol. In this example, select **UDP**. b. At the bottom of the page, click **SaveSet**. 3. Go to **Account > Basic** and complete the account settings. ![Htek account settings with the SIP user ID, authenticate ID, and password filled in](/images/pbx/htek-reg-setting.png) a. From the **Account** drop-down, select an available account. b. Set **Account Active** to **Yes** to enable the account. c. From the **Profile** drop-down, select the profile you edited in Step 2. d. Enter the extension credentials: - **Label**: A display name for the account, shown on the phone screen. - **SIP User ID**: The extension number. - **Authenticate ID**: The extension's registration name. - **Authenticate Password**: The extension's registration password. - **Local SIP Port**: The SIP registration port. :::note The Htek field names differ from the Cloud Voice labels you collected in Step 1. Map them like this: **SIP User ID** takes the Extension Number, **Authenticate ID** takes the Registration Name, and **Authenticate Password** takes the Registration Password. Mixing these up is the most common reason a manual registration fails. ::: e. At the bottom of the page, click **SaveSet**. ## Result The extension registers with Cloud Voice. Confirm success by checking the **Account Status** field. ![Cloud Voice, Htek account list showing the extension registered successfully](/images/pbx/htek-extension-registered-pce.png)