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.
What’s live and what’s coming
Section titled “What’s live and what’s coming”- Inbound calls to your SIP endpoint.
- TLS-encrypted SIP signalling using either
sips:orsip:…;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.
- Outbound calling: your voice platform places calls from your Linq numbers through Linq. Contact Linq to turn it on for your numbers.
- A Linq dashboard screen for setup.
For what Linq decides on a call and what you decide, read How calls work for your agent.
How a call reaches you
Section titled “How a call reaches you”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.
If your primary doesn't answer
Busy or declined (486, 600, 603) does not fail over.
Step by step:
- The caller dials your Linq number. The phone network sends an INVITE to Linq.
- Linq sends an INVITE to your endpoint, for example
INVITE sips:[email protected]:5061. - If your endpoint replies
180 Ringingor183, Linq passes it back and sendscall_voice.ringingto your webhook URL. - Your endpoint answers with
200 OK. Linq passes it back and sendscall_voice.answered. - The
ACKreaches your endpoint through Linq. - Audio flows directly between the phone network and your endpoint, using RTP
or SRTP as negotiated in SDP.
sips:andsip:…;transport=tlsencrypt SIP signalling. - The caller hangs up with a
BYE, which goes through Linq. Linq sendscall_voice.ended.
If your primary doesn’t answer, Linq tries your backup URI once; see How calls work for your agent.
Your call, your platform
Section titled “Your call, your platform”Any SIP endpoint can take your calls if it:
- accepts INVITEs on a public IPv4 address: over TLS with a
sips:URI or asip:…;transport=tlsURI (recommended), or over UDP with asip: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
401or407 - 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.
Audio quality (HD)
Section titled “Audio quality (HD)”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.
Events and call records
Section titled “Events and call records”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.