Please note, the question here is not how to configure Kamailio - it's already working for us. The question is, would this addition be useful to others, or is our particular configuration unlikely to be used elsewhere?
Cheers,
Charles
Hi Juha,
Yes, we could use a separate table for each registrar and replicate registrations to all of them. But we still need to add Path to ensure invites etc go via the server each client used to register (due to client NAT). And if that is local to the lookup, it still makes sense to ignore the path as it is itself.
I must admit, it would be better to compare the path IP:Port to the local ones, instead of the socket.
Cheers,
Charles
On 14 Sep 2013 05:13, "Juha Heinanen" <jh@tutpro.com> wrote:Charles Chance writes:
> We have distributed registrars with no proxies in front, so registrations
> are handled directly at the edge by any server (we then rely on DNS for
> load balancing/failover). All share the same DB/table and when a register
> is received, we add Path header manually, before saving.
question: why don't you make the system more reliable by each registrar
having its own db table?
-- juha
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev