Skip to content
Linq
Outbound Calling

Authenticate outbound calls

How your voice platform proves to Linq that it may place calls from your numbers.

Early access

Outbound calling is in early access. Contact Linq to turn it on for your numbers.

Linq authenticates every outbound call with a SIP username and password (SIP digest authentication). These credentials are for outbound calls only. They’re separate from your API key, and from your SIP profiles, which set where Linq sends your inbound calls.

When Linq turns on outbound calling for your account, Linq gives you a SIP username and password over a secure channel. Store the password in your platform’s secret store. To replace it, ask Linq for a new password.

  1. Your platform sends the INVITE.
  2. Linq replies 407 Proxy Authentication Required, with a challenge.
  3. Your platform sends the INVITE again, with a Proxy-Authorization header built from your username and password.
  4. Linq checks the credentials, then the caller ID and the rest of the call (Caller ID).

Most SIP servers and hosted voice-agent platforms do steps 2 and 3 for you once you enter the username and password in their outbound trunk settings.

  • Send your calls over TLS; see Transport and encryption.
  • Don’t register: Linq doesn’t use SIP registration and refuses REGISTER.

Restrict your credentials to your IP addresses (optional)

Section titled “Restrict your credentials to your IP addresses (optional)”

If your platform sends calls from fixed IP addresses, Linq can also accept your credentials only from those addresses. Contact Linq to set this up.

Anyone with your SIP username and password can place calls from your numbers.

  • Keep them in your platform’s secret store, never in client code or in a repository.
  • Enter the password only in your trunk’s authentication fields. Never put it in a SIP URI (user:password@host) or a dial string, and don’t log full SIP messages that carry it.
  • Rotate the password when someone with access to it leaves, and after any suspected leak. Ask Linq for a new password.
  • If you think they’ve leaked, contact your Linq representative at once. Linq can turn off outbound calling for your account and give you new credentials.
What you see Cause What to do
407, then 403 after you send credentials. No call event. The username or password is wrong. Check the credentials in your trunk settings. If they’re right, ask Linq for a new password.
Your platform can’t connect, or gets no reply. Your platform sent the call without TLS. Use TLS on port 5061 (Where to send calls).

If Linq accepts your credentials but refuses the call, for example because of the caller ID, see When a call is refused.