Inbound calls
Every number points to a SIP target, the agent connection. We send each inbound call there. You set the target in the dashboard under Rufnummern (numbers) or with the CLI:
trunkbeam numbers connect 12 --sip-uri "sip:agent@voice.example;transport=tls"
trunkbeam numbers connect 12 --elevenlabs # ElevenLabs in one step
If your agent does not answer, for example during an outage at the provider, a regular German phone number can ring instead, such as your office. Set how long the agent has to pick up with --after (5 to 30 seconds, default 8):
trunkbeam numbers fallback 12 "07422 123456" --after 10
The SIP INVITE carries the caller’s number in the From header and the dialed number in the To header and additionally in the X-TrunkBeam-Called header. So your agent can behave differently per number.
Outbound calls
For calls from your agent to the outside and for transfers, set up an access in the dashboard under SIP-Zugang (SIP access). You get a username and password, which you enter at your voice platform together with these values:
Host: sip.trunkbeam.com
Port: 5061
Transport: TLS
Username: (from the dashboard)
Password: (shown once)
Only numbers from your account are allowed as caller ID. We reject anything else, so nobody can place calls from numbers they do not own.
Setup at your platform
Voice platforms usually call this “Bring your own SIP trunk”, “Custom telephony” or “SIP trunk”. The flow is similar everywhere:
- Create a SIP trunk at the platform with host
sip.trunkbeam.comand the credentials above. - Add your number at the platform and assign it to your agent.
- Set the SIP address the platform gives you for inbound calls as the target with us.
trunkbeam guide <provider> --number <id> shows you these steps with your real values.
For the exact fields at ElevenLabs, LiveKit, Vapi, Retell, Ultravox and OpenAI, see the platform guides.
HD voice with G.722
TrunkBeam supports HD voice with the G.722 wideband codec, which carries a wider speech frequency range than traditional narrowband telephony.
HD quality requires your device, voice platform and the entire call path to support wideband audio. The systems on the SIP connection must negotiate a suitable codec. An HD-capable phone alone is not enough if another leg carries only narrowband audio, such as G.711. Converting that audio to G.722 later does not restore the lost frequencies.
This also applies to transfers: HD quality on the new connection depends on the destination device and call path.
Technical background: ITU-T G.722 and SDP codec negotiation in RFC 3264.
Technical details
| Signaling | SIP over TLS (port 5061) |
| Media | SRTP and RTP |
| Codecs | G.722, G.711 A-law (PCMA), G.711 µ-law (PCMU) |
| DTMF | RFC 2833 (telephone-event) |
| Number format | E.164, for example +493023125417 |
We will publish the IP ranges for firewall rules at launch.