Andreas Granig writes:
An alternative is using usrloc db-mode=3 (db-only) and
doing data
replication in the database backend (e.g. MySQL cluster or master-master
replication) for location sharing in combination with the Path extension
for NAT traversal:
http://osdir.com/ml/voip.openser.user/2006-03/msg00014.html
andreas,
usrloc readme tells about mode 3:
The mode may
be slower due the high number of DB operation. For example
NAT pinging is a killer since during each ping cycle all
nated contact are loaded from the DB; The lack of memory
caching also disable the location watcher registration (in
will not work with PA module) and disable the statistics
exports.
is that not true regarding nat pinging or do you handle nat pinging by
some other means?
-- juha