BYOC / voice infrastructure

SIP trunking for AI voice agents

Your agent platform supplies the brain. KataTelecom supplies the voice channel. Connect the agent to customers on the public phone network with international numbers, per-minute carrier rates and capacity sized to concurrent calls.

Session traceillustrative signalling sequence

An AI voice agent connects through a KataTelecom SIP trunk to the public telephone network and then to the customer.

Why BYOC

Keep the carrier layer under your control

Bundled agent minutes can include a platform markup on the voice leg. BYOC leaves prompts and conversation logic with the agent platform while your own SIP trunk carries the call at visible carrier rates.

01

Separate voice economics

Pay the agent platform for intelligence and KataTelecom for transport, with destination rates shown separately.

02

Own the number layer

Keep your DIDs and choose local campaign numbers where available. Caller ID remains subject to country rules.

03

Size for concurrent calls

Plan capacity around simultaneous sessions, destinations and the actual call profile.

Compatibility

Test the call path, then name it

Compatibility is named only after a real connection test. A platform logo never substitutes for a call that has completed in both required directions.

01SIP endpointURI, transport and reachable signalling path
02AuthenticationCredentials or approved IP address
03MediaCodec negotiation and two-way audio
04IdentityCaller ID format and country conditions
05Call flowsInbound and outbound scenarios required by the agent

Platform-specific integration guides will be published after each connection path is verified.

Carrier layer

Built for agent traffic, not a demo counter

The trunk is configured around the planned workload. Concurrency, routing and identity conditions are confirmed before production.

Capacity
Concurrent sessions
Ports and throughput are sized to expected agent load and destinations.
Media
SIP codecs
Codec and transport settings follow the tested platform path.
Numbers
120+ countries
Availability varies by market, stock and verification requirements.
Commercial
No long-term contract
Use per-minute rates and add numbers only where needed.
Catalog entry point

Start with the voice components you need

Number rental and call traffic stay separate as the agent scales.

Phone numberfrom $5/mo

Current DID catalog floor; country, stock and verification determine the final price.

Outbound voicefrom $0.002/min

Current positive catalog floor; the billed rate depends on destination and route.

Concurrent capacityby request

Sized around the planned session profile rather than a generic ceiling.

Catalog floors are reference points, not a universal quote. Setup, verification and route-specific terms may apply.

Connection path

From agent endpoint to a production call

Three steps keep platform configuration and carrier routing testable.

01 / PROFILE

Share the traffic plan

Send the endpoint, countries, call directions and expected concurrency.

02 / TEST

Connect and verify

Configure authentication, codecs and caller ID, then place test calls.

03 / ROUTE

Open production capacity

Approve the route, attach numbers and scale with agent load.

AI voice FAQ

Before the first test call

Connection details and country-specific conditions are confirmed for the actual platform and route.

01What does BYOC mean for an AI voice agent?

The platform handles the conversation; your own KataTelecom SIP trunk carries calls between it and the public phone network.

02How is AI-agent SIP traffic billed?

The carrier leg is billed per minute. Number rental and destination rates are quoted separately, without a long-term contract.

03Which phone number should the agent use?

Choose a number for the campaign market and permitted caller-ID model. Coverage spans 120+ countries, subject to stock, verification and local rules.

04Can the agent place emergency calls?

Emergency calling is not assumed in the standard setup. Availability, configuration and responsibilities must be confirmed in the service agreement before emergency traffic is routed. Keep an alternative way to reach emergency services unless explicitly agreed.

05Is the trunk compatible with my AI voice platform?

A real test confirms signalling, authentication, media, caller ID and the required inbound or outbound flows. Platform names are published only after that connection path is verified.

Request a trunk

Connect your agent to the phone network

Send the platform endpoint, target countries and expected concurrent calls. A manager will confirm the test path, number options and routing terms.