Skip to main content
Every workspace gets a Get2Dial-managed SIP domain automatically. This page covers when you’d add a custom domain of your own instead, and how to verify and place it.

​
Before you start

  • Your workspace already has a domain provisioned for you — see it, together with your WSS URI and extensions, on Workspace settings. You don’t need to do anything to use it; skip the rest of this page unless you specifically want your own domain.
  • To add a custom domain you need to own it and be able to publish DNS TXT and CNAME records for it.
  • Assigning a custom domain to edge servers requires your workspace to have its own edge servers. Most workspaces on Get2Dial’s shared platform capacity don’t have any — if Edge servers on the domain’s page has nothing to select, contact support about provisioning dedicated capacity before a custom domain can carry live traffic.

​
Steps

1

Open SIP domains

In the left navigation, select SIP domains.
2

Add your domain

Select New SIP Domain. Enter the Domain you own (for example sip.yourcompany.com), and leave WSS and TLS on unless you have a specific reason to disable either.
3

Publish the DNS TXT record

Open the domain you added. Under Verification, copy the DNS TXT record shown and publish it with your DNS provider.
4

Re-check verification

Back on the domain’s page, select Re-check now. This can take a few minutes after you publish the record, depending on DNS propagation.
5

Assign edge servers

Once verified, under Edge servers, select at least one primary server to answer for this domain. Add a failover server too if you have more than one available.
Verifying ownership and assigning edge servers is fully self-service. Issuing the TLS certificate that makes the domain actually usable requires one more DNS delegation. Get2Dial gives you the exact target for a CNAME at _acme-challenge.your-domain; add it at your DNS provider, then leave it in place for future renewals. You never share a Cloudflare token, API key, or DNS-provider sign-in. See the note on Encryption and certificates before you consider the domain finished.

​
Verify

The domain’s status shows verified, and — once the certificate step below is complete — active. Devices can then register against the domain using a subscriber’s credentials.

​
Common problems

  • Verification keeps failing. Confirm the exact TXT record was published on the exact domain shown — a record on a subdomain or the wrong host doesn’t match. DNS changes can take time to propagate; wait and re-check rather than republishing repeatedly.
  • The domain verifies but never becomes active, or shows a certificate error. Confirm the _acme-challenge CNAME is still present and matches the target Get2Dial supplied. If it is, contact support. See Encryption and certificates.
  • There’s nothing to pick under Edge servers. Your workspace has no edge servers of its own. Contact support — this is a capacity/provisioning question, not a configuration mistake on this page.

​
Next steps

Encryption and certificates

Workspace settings

Devices and registration