Hello,
some information is still cached for some processing in presence
modules. Not sure to what extent you can rely on sharing everything via
database, maybe t_replicate will help for the rest of the cases.
I think posgress is the db that has the most features needed by presence
modules for sha
Hello,
there was not change in record route parsing or processing between 4.3.1
and 4.3.2.
Do you get this all the time? Or it happens only sporadically? Can you
capture the sip traffic for such situation (e.g., using: ngrep -d any
-qt -W byline port 5060)?
Cheers,
Daniel
On 19/09/15 09:41, Cha
Hi Thibault,
there is no need for special decline handling when using tsilo, so the
default basic should work with the modifications you've done.
I tested your scenario with this config and I haven't been able to get the
crash. Could you please perform a test with debug level 3 and send me the
whol
Thanks for the reply Daniel.
But is that possible to use the same Presence DB with multiple Kamailio's ?
If i'll use same postgres DB with multiple Kamailio's - it'll cause DB
locks and other issues ?
What is the best way to do SUBSCRIBE presence replications - maybe via
SIP (to replicate eve
I just upgraded from kamailio-4.3.1-1.1.x86_64 to kamailio-4.3.2-2.1.x86_64 and now when I hang up the called party the
calling party line stays open and I get this in the log:
ERROR: rr [loose.c:106]: find_first_route(): failed to parse Route HF
On the back end asterisk server the call stays ac
