Australian and NZ voice and SMS for LiveKit agents: setup guide

Getting Started
1

Hi all, Harry from Atom Telecom Brisbane. We’re an Australian carriage service provider supplying in-country voice and SMS across Australia and NZ: local, 1300/1800 and mobile numbers, SIP trunking, and two-way SMS on Australian mobile numbers, all across multiple Tier 1 carriers.

We’ve seen a lot of builders in the region routing local calls and messages via overseas providers, so we’ve published a step-by-step guide for connecting an Atom number to a LiveKit Cloud agent:

:backhand_index_pointing_right: Livekit | Atom Integration

It covers:

  • Inbound: creating the LiveKit inbound trunk, a dispatch rule for your agent, and routing the Atom number to LiveKit
  • Outbound: setting Atom SIP credentials, creating the outbound trunk, and placing calls with the lk CLI
  • Verification steps and a configuration summary at the end

The guide currently covers voice on LiveKit Cloud. SMS steps are coming soon. In the meantime, if you want your agent to send and receive texts on the same Australian mobile number it answers calls on, reach out and we’ll set it up with you. Porting an existing AU/NZ number to Atom is also supported.

Happy to answer questions here, or reach me at hg@atomtel.com.

4

Thanks for posting :lk-party: :australia: :new_zealand:

5

@hg, Welcome Harry, and nice writeup. Keeping the AU/NZ PSTN leg in-country is underrated for voice agents: it trims the round-trip latency and jitter that turn detection and barge-in are most sensitive to, so a local trunk into LiveKit Cloud beats pushing calls through an overseas provider. The inbound-trunk plus dispatch-rule flow you documented is the standard setup; looking forward to the SMS steps..

6

FYI - Attached is our KBA for SMS integration in LiveKit

LiveKit | Atom - SMS Integration