SIP client setup

Point a softphone or PBX at your trunk with the credentials your provider issued, then place a test call.

What you need

When your provider created your trunk account, they issued a SIP username and password. You configure your client to register with those. You do not register by IP address — authentication is by username.

SIP username
Your account name, issued by your provider. It is also the authentication user.
Password
Issued with the username. Keep it secret; it authorises calls billed to your account.
Server
The trunk host address your provider gave you.
Transport
SIP over UDP on port 5060.
Media (RTP)
UDP ports 10000–20000 must be open outbound for two-way audio.

Configure and register

  1. Enter the credentialsSet the SIP username, password, and server in your client. Set both the authentication user and the register user to your SIP username.
  2. Use UDP 5060Select UDP transport on port 5060. Enable symmetric RTP / rport if your client offers it — it keeps audio flowing through NAT.
  3. RegisterYour client should show registered. If it does not, re-check the username and password exactly — a wrong password returns an authentication failure, not a silent drop.
  4. Place a test callDial a permitted destination. If you hear a reorder tone or "please hang up", your account may not be permitted to dial that destination, or the account is frozen — see below.

What governs your calls

Routes and destinations
Your calls route out through the trunks your provider assigned, and only to destinations your account is permitted to dial.
Channel limit
A cap on simultaneous calls. Calls beyond it wait or are rejected until a channel frees.
Balance
Calls are rated and debited from your prepaid balance. A frozen or empty account cannot place calls.

After your first call

Your usage and call records appear in the portal within about a minute. See Call records.

If registration fails with the correct password, confirm your client sends the SIP username as the authentication user (not just the display name), and that it uses UDP 5060. Most "correct password but still rejected" cases are a client sending the wrong auth user.
← Managing DIDs Account and security →
Last updated 2026-07-10.