Skip to content
Linq
Introduction

Voice

Answer calls on your Linq phone numbers with your own SIP endpoint or voice agent.

Send the inbound calls on your Linq phone numbers to a SIP endpoint you run, or to your voice-agent platform’s SIP address. This works for any number on your account that can be set up for voice, including numbers you message from.

You set it up through the API. There’s no dashboard screen for it yet.

Voice is available on Pro and Enterprise plans. Your Linq representative can help with pricing.

Live
  • Inbound calls to your SIP endpoint.
  • TLS-encrypted SIP signalling using either sips: or sip:…;transport=tls.
  • HD audio with G.722, AMR-WB or Opus.
  • Custom SIP headers on every INVITE.
  • A backup endpoint, with automatic failover when your primary doesn’t answer.
  • Call webhooks: when a call rings, when it’s answered, and when it ends.
Early access
  • Outbound calling: your voice platform places calls from your Linq numbers through Linq. Contact Linq to turn it on for your numbers.
Coming
  • A Linq dashboard screen for setup.

For what Linq decides on a call and what you decide, read How calls work for your agent.

When someone calls your Linq number, the phone network sends the call to Linq. Linq looks up the SIP profile assigned to that number and sends an INVITE to the profile’s primary URI. The URI has no user part (the part before @); Linq sets it to the number that was called, in E.164: sips:[email protected]:5061.

Linq stays in the signalling path for the whole call. The audio doesn’t: it flows directly between the phone network and your endpoint. Linq doesn’t change the SDP (the part of the INVITE that describes the audio), so the codec is negotiated end to end.

The caller is in the From header. The caller’s carrier sets the call’s attestation (the STIR/SHAKEN rating of how sure the carrier is that the caller may use that number), and Linq passes it to you unchanged. Caller ID can be spoofed. Don’t use the caller’s number alone to identify or authenticate a caller.

How an inbound call reaches your SIP endpoint Ladder diagram. The caller dials your Linq number. The phone network sends an INVITE to Linq, and Linq sends an INVITE to your SIP endpoint with the called number as the user part. Your endpoint's 180 Ringing and 200 OK go back through Linq, which posts call_voice.ringing and call_voice.answered to your webhook URL. The ACK comes through Linq. Audio (RTP) flows directly between the phone network and your endpoint and does not pass through Linq. The caller's BYE comes through Linq, and Linq posts call_voice.ended to your webhook URL.

If your primary doesn't answer

Failover to your backup URI Linq sends the INVITE to your primary URI. If the primary doesn't reply within 3 seconds, replies with a 5xx, or doesn't answer within 30 seconds, Linq sends the INVITE to your backup URI.

Busy or declined (486, 600, 603) does not fail over.

Linq relays the SIP signalling for the whole call and posts call events to your webhook URL. The audio goes straight between the phone network and your endpoint.

Step by step:

  1. The caller dials your Linq number. The phone network sends an INVITE to Linq.
  2. Linq sends an INVITE to your endpoint, for example INVITE sips:[email protected]:5061.
  3. If your endpoint replies 180 Ringing or 183, Linq passes it back and sends call_voice.ringing to your webhook URL.
  4. Your endpoint answers with 200 OK. Linq passes it back and sends call_voice.answered.
  5. The ACK reaches your endpoint through Linq.
  6. Audio flows directly between the phone network and your endpoint, using RTP or SRTP as negotiated in SDP. sips: and sip:…;transport=tls encrypt SIP signalling.
  7. The caller hangs up with a BYE, which goes through Linq. Linq sends call_voice.ended.

If your primary doesn’t answer, Linq tries your backup URI once; see How calls work for your agent.

Any SIP endpoint can take your calls if it:

  • accepts INVITEs on a public IPv4 address: over TLS with a sips: URI or a sip:…;transport=tls URI (recommended), or over UDP with a sip: URI that has no ;transport=
  • accepts audio from the phone network’s media addresses, and advertises a public address in its SDP
  • shares a codec with the call: PCMU, PCMA, G.722, AMR-WB or Opus
  • replies to the INVITE within 3 seconds
  • doesn’t challenge Linq’s INVITE with 401 or 407
  • knows the called number: on a hosted voice-agent platform, add your Linq number there first

Linq relays the caller’s BYE to your endpoint.

Linq’s signalling addresses are shared by every Linq customer, so allowing them doesn’t prove a call is for your numbers; read Protect your endpoint before you take calls.

Linq supports PCMU, PCMA, G.722, AMR-WB and Opus. G.722, AMR-WB and Opus are HD (wideband). The best codec that both sides support is used.

A call is HD only when every leg negotiates a wideband codec, so HD is supported but not guaranteed. If your endpoint and the call share no codec, the call fails with 488. If your platform uses a wideband codec not on this list, contact Linq.

Linq sends a webhook when a call rings, when it’s answered, and when it ends. Each event carries the call’s id. You can fetch the call record with the same id.

Connect your SIP endpoint shows how to subscribe and find a call. Call events use the same delivery, signatures and retries as message events; see the Webhooks guide.