Whitelabelling

Customizing the Phone System FQDN

This article will provide a walkthrough on customizing the phone system FQDN with a custom SSL certificate.

Looking to change the login URL?

If you're looking to change the URL that users visit in order to login to the phone system, instead check out our guide Customizing the Control Portal FQDN which covers that.

Creating the SSL

If you already have an SSL certificate, you can skip to the next section.

  1. Log into the bvoip phone system. 
  2. Go to Settings > Domains on the left-hand side.
    image-png-Jan-31-2024-10-37-48-6396-PM
  3. Scroll down to the Use Your Own Domain section.

  4. Enter your FQDN and company information, then click Ok.
  5. A download will start for key.pem and csr.pem, you may be prompted to allow for multiple downloads.
  6. Use the csr.pem file to order/generate a new SSL certificate according to your vendor's documentation.

Update FQDN for a Phone System

  1. Ensure that a CNAME is setup on the desired domain name to point to the address <phonesystem>.bvoip.net, where <phonesystem> is the system in question.
  2. Go to System > Domains again on the left-hand side.
    image-png-Jan-31-2024-10-37-48-6396-PM
  3. In the My own records section, click Add record
  4. In the Friendly domain name field, input the desired domain name.
  5. In the Certificate field, paste the generated Certificate (crt.pem) received from your SSL issuer. This should start with -----BEGIN CERTIFICATE-----.


  6. In the Certification Key field, paste the generated Private Key (key.pem) received from the CSR generator. This should start with -----BEGIN RSA PRIVATE KEY-----.


  7. Click the Ok button.

After completing these steps, expect the new domain to be working in full within 15 minutes of being set. 

Run a Health Check

If things seem to be incorrect, you can run a health check using the green check mark to the right of the domain
image-png-Jan-31-2024-11-25-34-6604-PM

Customized Domain Isn't Taking?

Reach out to our Support Team if you are seeing that the custom domain is not reflected after applying the change.