[Kamailio-Users] Local routing

Stanisław Pitucha stanis at gradwell.net
Wed Aug 5 12:22:47 CEST 2009


2009/8/5 Martin Werne <martin.werne at googlemail.com>:
> - A total of appr. 2000 ATAs/IP Phones (today appr. 300).
> - Routing to various providers/gateways via custom made OSP-server.
> - Two Kamailio-servers on different geographic locations.
> - Load-balancing/Failover of ATA's by use of DNS-SRV.
>
> The main "problem" I see, is how local calls between ATA's registered on each of the Kamailio-servers is routed.
> How can Kamailio1 route a call to an ATA registered on Kamailio2?
>
> What is best in this scenario?
>
> 2. Let the Kamailio-servers share the same database (same location-table)?

I'd go for that one. It worked really well for me. You can add a
multi-master replication between mysql servers for example (to have a
lower access time between the openser and db). But if you're using the
standard registration time (3600s), it might be an overkill (only
0.555 registrations/s with 2000 clients).

If both proxies can reach any registered phone, you don't have to do
anything else. If you have to route through the same proxy the phone
is registered on, you can solve it with either path, or some simple
custom logic.

Watch out for ATAs and phones with broken SRV randomisation - many
will select the first entry every time. If your dns server is normal
and doesn't randomise the order, you may end up with every phone using
the same proxy all the time, or some strange split (30/70 was fairly
standard for me when using any random phones).




More information about the sr-users mailing list