i was wondering if anyone can help shed some light on two (thought distinct) questions/issues:
1) is there any real need to treat the FS sqlite DBs (core.db and sip_interface_1.db) as "important" (e.g. what's the worst case if they're lost / corrupted, etc.)
mc_
lumber_jack: 1) no
lumber_jack
2) for registration sync to work in kamailio -- does one need to have a shared db (e.g. mysql or similar), or is using dbtext enough? (e.g. sync is stored per kamailio server, and can be independent of a shared database)
mc_
2) registrations are stored in kazoo atm
lumber_jack
@mc_ re: #1 -- figured -- but wanted to confirm -- thanks
re: #2 - hmm ... i get this weird issue, where i have 2 kamailio servers, and a device registers to one, but later tries to originate a call to the other, but it gets denied, because it's using route-set
e.g. the kamailio configs check is the user is registered(), but apparently it's returning false ...
not sure where those registrations are stored (as least with regard to kamailio and it's registered() function)
Tica2 has quit
my understanding is that it's in some db ... by default the configs use dbtext and [i think] it's an in-memory representation (modparam("usrloc", "db_mode", 0))
but shouldn't the registration -- when occurring on one server -- notify the other kamailio server (via amqp) and the second server should be aware of it?
mc_
lumber_jack: hmm, i think its strange behaviour to register to one and call to another
but the 2nd kamailio should recv invite
and ask kazoo for authn
and auth challenge the phone
can you get the SIP trace for the INVITE?
but, i'm not overly sure there
i'm not too familiar with kamailio internals
lumber_jack
ill try and get the sip trace
the thing is, from the phone's perspective it's already registered, so it doesn't send another register.... it just sends the INVITE with a route-set ... but kamailio is rejecting anything with a route-set because it doesn't think the device is registered
mc_
lumber_jack: the phone won't send a REGISTER anyway
it should send an INVITE and get a Proxy Auth Required response
487 or whatever
then send a second invite with a Proxy-Authorization header
lumber_jack
well yes, that would be the "normal" / "expected" behavior
let me check the sip trace and see what the device is actually trying to do ...
emte1 has quit
emte joined the channel
i guess the crux of my question is: how can i keep two kamailio registration dbs in sync ... so that if a device registers with server1, server2 also "knows" about it ...
btw, as to why this is being done this way: i'm testing an active/active HA kamailio setup: low-latency DNS, announcing two IPs, they obviously get rotating when the client does a DNS lookup (post expiry), hence different servers
s/rotating/rotated
emte has quit
pramodv joined the channel
mc_
lumber_jack: not sure off hand, maybe lazedo_ can shed light if he's around
pramsky has quit
lazedo_
lumber_jack: registrations live in ecallmgr that has the reference to which kamailio the device registered, when building a bridge string to the device, we send it to kamailio appropriate kamailio server
Tica2 joined the channel
lumber_jack
@lazedo_ yup that works for calls being terminate TO the device
but coming FROM the device (e.g. device INVITE -> kamailio), the check for registered() fails