A solution for your needs
Connect an existing bot or discuss launching a new one.
One call flow
Connect your phone number, bot, and team.
Clear pricing
Know the cost of connection, calling, and the agent in advance.
Telephony for your bot
Receive calls.
Bring in your team.
A SIP trunk connects the telephone network to a voice agent. A customer calls your company number, and the bot receives the call and responds using the configured call flow.
- Connect an existing bot or launch a new project.
- Inbound and outbound calls to agreed destinations.
- Transfers to a staff member when human assistance is needed.
Architecture without unnecessary complexity
How a call works
For an inbound call, the number receives a call from the telephone network and forwards it to the agreed SIP address.
01
Phone number
The customer dials your familiar company number.
02
Stream Telecom
The call is directed to the agreed SIP route.
03
Your AI agent
The platform recognizes speech, generates a response, and speaks it aloud.
04
Staff member
When needed, the call is transferred according to the configured call flow.
For outbound calls, the direction is reversed: AI platform → SIP trunk → customer’s phone. Outbound calling availability and the displayed number are agreed separately.
What matters before launch
What the connection includes
Inbound and outbound calls
We will define call destinations, number formats, and permitted Caller ID.
Capacity for your workload
We will agree on the number of concurrent conversations and the rate of new call attempts — CPS.
Two-way audio
We will check compatible codecs and media flow so both parties can hear each other.
Transfer to a human agent
We will choose a transfer mechanism: SIP REFER or a connection through a PBX, if supported by the setup.
Connection security
We will agree on authentication, IP-based access, and TLS/SRTP availability on the required segments.
Fallback scenario
We will define what happens when the destination is busy, times out, or is unavailable over SIP.

Failover and transfers
Who will answer the customer
if the bot is unavailable
We will discuss a fallback destination: a staff member, a PBX queue, or another available handler. Trigger conditions are checked using test calls.
Stream Telecom voice agents
We will connect your existing bot or help launch a new one
We will select a telephone connection, call flows, and the integrations your business needs.
New project
Launching a voice agent
We will define which questions the agent answers, what data it needs, and when it transfers a call to a staff member. We will agree on the scope of work and pricing.
Already have a bot
SIP connection
We will check your bot’s interface and connect it to the telephone network. We will configure numbers, call destinations, and routes.
Working with your team
Connection to your PBX
We will agree on transfers to staff and queues. If needed, we will configure CRM data exchange separately.
What we check together
What we check before launch
| Routes | Inbound and outbound calls, the correct destination number, and Caller ID. |
|---|---|
| Audio | Voice in both directions, agreed codecs, NAT, and RTP. |
| Load | Concurrent conversations and the rate of new calls within the agreed limits. |
| Transfers | The call reaches a staff member; busy and no-answer behavior is clearly defined. |
| Failure | Disconnecting the primary destination triggers the expected fallback scenario. |
What the price includes
- Setup and recurring fees for a number, if required.
- SIP connection parameters and agreed capacity.
- Calls to selected destinations.
- Additional routing and integration work — as agreed.
Voice agent, call flow, and integration costs are listed separately from the number and calls. We will agree on the solution scope and final quote before connection.
Answers before you connect
