[sr-dev] usrloc and db only mode

[Alex Hermann]

On Wednesday 25 February 2015, Daniel-Constantin Mierla wrote:
> 1) discovering what is the server that wrote the record

> Victor Seva on irc channel was saying that is planning to propose a
> patch for 1), relying on socket value in the location table. The use
> case presented was many servers saving and looking up the records in the
> same table, but fetch only the records written by current instance for
> sending keepalives. It makes sense not send keepalives from all
> instances, for load as well and bandwidth considerations. This could
> work relying on local socket, but I am not sure how efficient will be
> when listening on many sockets (different ips, but also different ports
> or protocols - ipv4/6, tcp, tls, udp -- all add sockets).

> The solutions that came in my mind for now:
> 
> - for 1) -- add the server_id as a new column in the location table. It
> was pointed to be that ser location had it. This will turn a query
> matching on many socket-representation strings to one expression done on
> an integer. The value for server_id can be set via the core parameter
> with the same name.


What would be the use case to share a location table between multiple 
kamailio's?

And if it is shared, why would you want to filter per server? This seems 
contradictory to sharing the table in the first place.

-- 
Greetings,

Alex Hermann