Integrations
Kamailio contact center integration
Kamailio ties several Asterisk servers into one phone system, and our connector links each of them to the platform. A call arrives at Kamailio and goes to the right or least busy server, while agents, queues, and reports in the platform stay shared – as if there were one switch. You need this setup when call volume is high, you have several sites, or you need a backup server.
1carriers and offices send callsSIP2Kamailio picks a server by rulesroute3Asterisk handles the call, menu, and queueon call4CONTACT.WORK shows the call to the agentrecordCapabilities
What you get with Kamailio
Examples
Three ways Kamailio, Asterisk, and the platform work together
Kamailio sits first in the call path, with your Asterisk servers and the connector behind it. We design the setup around your network.
Several Asterisk servers, one phone system in the platform
Calls arrive at Kamailio and are spread across Asterisk servers. Each server is connected to the platform, so agents see one shared queue and managers see one set of reports.
- One shared queue for agents
- Add a server without reconfiguring
- One set of reports across servers
asterisk-1312 calls, 64% loadnormalasterisk-2298 calls, 61% loadnormalasterisk-3305 calls, 63% loadnormalPlatformone queue and one report – 915 callscombinedAsterisk servers by city, one contact center
Each city has its own Asterisk, and Kamailio decides where to send the call: by number, time of day, or load. The platform brings the cities together: a night shift in one city takes calls from the whole country.
- The call goes to the right site
- One night shift for the whole country
- All cities in one set of reports
8 800call from Chicago – Asterisk in New Yorkby numberNightfrom 9:00 PM all calls – Asterisk in Denverby timePeakNew York busy – some calls go to Denverby loadPlatformboth cities in one queue and one reportcombinedA backup Asterisk, no downtime
If an Asterisk server stops responding, Kamailio sends new calls to the backup. The platform keeps working with it like the primary: agents, queues, and recordings stay in place.
- Failover to the backup server
- Agents keep working
- No gaps in recordings and reports
14:02primary Asterisk stopped respondingfailure14:02new calls go to the standby Asteriskfailover14:03agents in CONTACT.WORK take calls, queues intactworking14:05recordings and reports with no gapsnormalIn every setup, Asterisk handles the calls, the IVR, and the call queue, while agents work in the platform.
How it works
How Kamailio fits into the platform's telephony
Entry point
Kamailio in front of Asterisk
Carriers and offices send calls to Kamailio. It checks the call, applies routing rules, and picks the Asterisk server that will take the call.
- Carrier trunks
- Your own routing rules
- Screening suspicious calls
CarrierSIP trunk, call taken by KamailioansweredRulesupport line, New York siteselectedasterisk-1load 92%, call not sentbusyasterisk-2load 41%, call routedsentServers
Asterisk behind the load balancer
Kamailio can front many Asterisk servers in one or several cities. A new server joins the setup without stopping the running ones.
- Servers in different cities
- Add servers without downtime
- Maintenance one server at a time
asterisk-1New York · 186 callsrunningasterisk-2New York · 141 callsrunningasterisk-3Denver · 97 callsrunningasterisk-4Denver · down for maintenancefailoverPlatform
All servers as one system
The CONTACT.WORK connector is connected to every Asterisk server behind Kamailio. Monitoring, reports, agent statuses, and the customer record work as if there were one server.
- A connector on every server
- One monitoring view
- One customer history
Queue“Support” – 9 waitingsharedAgents34 on the line, any servercombinedReport4,812 calls today from all serverscombinedCRMsummaries and recordings – in the customer recordas usualSetup
How we deploy Kamailio
- 01SizingWe estimate call volume, sites, and how many Asterisk servers you need.
- 02DesignWe design routes, failover, and entry points for carriers.
- 03ServersWe deploy Kamailio and the Asterisk servers and set up security.
- 04ConnectorWe connect all Asterisk servers to the platform through the connector.
- 05TestingWe take nodes offline one at a time and see how the system handles a failure.
- 06Go-liveWe move carrier traffic to Kamailio and monitor the load.
Requirements
What Kamailio requires
- Load
- Usually from several hundred concurrent calls
- Servers
- A dedicated server for Kamailio and two or more Asterisk servers
- Network
- Connectivity between sites and carrier access
- Carriers
- SIP trunks that terminate on Kamailio
- Hosting
- The CONTACT.WORK cloud, your own servers, or both
- Cost
- Sizing and setup billed in development hours, ongoing support under your plan
Preparation
What to prepare for a Kamailio implementation
Q&A
Frequently asked questions
Do we need Kamailio if we have one Asterisk server?
Usually not. Kamailio pays off when you have several servers or sites, or when call volume calls for load balancing and failover.
How many Asterisk servers can connect to the platform through Kamailio?
As many as your load requires: a new Asterisk server goes behind Kamailio and gets its own connector, and the platform immediately sees its calls in shared queues and reports.
Can we add Kamailio to an Asterisk we already run?
You can: Kamailio goes in front of your Asterisk, carriers switch over to it, and the connector and platform settings stay the same. New servers are added alongside later.
How does Kamailio connect to the CRM?
Not directly: the call passes through Kamailio to Asterisk, then the platform finds the customer and writes the outcome to your CRM. Your CRM doesn't care which server handled the call.
How much does Kamailio cost?
Kamailio itself is free. You pay for the project – sizing, setup, and ongoing support – in development and support hours under your plan. Contact us for pricing.
Glossary
Terms on this page
- Connector
- A prebuilt module that links the platform with telephony, a CRM, or another system. Learn more →
- Backup
- Data is regularly copied to a separate place so it can be restored if something goes wrong. Learn more →
- CRM – customer relationship management
- Where a company keeps its customers, deals, and full communication history. Learn more →
- Customer record
- The screen of customer data an agent sees during a conversation. Learn more →
- Cloud deployment (cloud)
- The platform runs on the vendor's servers, and agents connect over the internet. Learn more →
- Call routing
- Rules the system uses to decide who gets a call. Learn more →
- IVR (interactive voice response)
- A phone menu: the caller hears a greeting and picks the right department. Learn more →
- Call queue – callers waiting to be answered
- Callers waiting for an available agent. Learn more →
- SIP trunk
- A phone line from the carrier over the internet instead of a wire. Learn more →
- SIP (Session Initiation Protocol)
- The protocol that sets up calls in IP telephony. Learn more →
- Hosting
- You rent a server from a provider instead of buying one. Learn more →
- On-premises deployment
- The system runs on the company's own servers, not in the vendor's cloud. Learn more →
Updated: