Hi!
Siptrace's default db_url is: DEFAULT_RODB_URL
Imo it does not make sense to use the read-only URL, as siptrace module
writes into the DB, no reading.
If agreed, I can change it.
regards
Klaus
Hi!
In Debian there exists package:
libmemcache-dev
and
libmemcached-dev.
The 'control' file requires 'libmemcache-dev', but I had to install
'libmemcached-dev' to build Kamailio.
Maybe someone knows the difference of memcache/memcached can fix this.
Thanks
Klaus
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#282 - Dialog bugs
User who did this - Eduardo Lejarreta (lejarreta.e)
----------
Good evening Daniel.
I've sent to you "diff -u" from: dlg_handlers.c and dlg_db_handler.c files
Please remember this:
1.- dlg->dflags |= DLG_FLAG_TOBYE; --------------->(IMPROVEMENT: DLG_FLAG_TOBYE should be also saved in any way on DB. After a "kamctl restart" we loose this contextual flag. As for us it's very important we've forced on code.)
2.- We've detected another issue we have still not corrected: the final "duration" of acc_cdr.c accounting adds the time Kamailio is "out of service" during "kamctl restart" which is usually over 6-7 seconds. The real problem is when there is a a long while between a "kamctl stop" and a "kamctl start". I'll correct this.
Regards.
Eduardo Lejarreta.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=282#comment856
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
i was again hit by the problem of non-expiring location table entries.
this time it happened without any mi commands when pjsua crashed right
after registration. 15 minutes after expiring, that registration is
still in location table, but not in memory cash.
related to this location entry, i also got to syslog:
Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: db_mysql [km_dbase.c:122]: driver error on query: Duplicate entry 'uloc-51761da3-37fb-e' for key 'ruid_idx'
Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: <core> [db_query.c:235]: error while submitting query
Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: usrloc [ucontact.c:615]: inserting contact in db failed
Apr 23 09:32:30 siika /usr/sbin/sip-proxy[14304]: ERROR: usrloc [urecord.c:363]: updating contact in db failed
that update was triggered by some timer, because it was not related to
any sip request. i haven't checked from the code what update is in
question, but unless ruid field itself is updated, i don't see how it
can result in duplicate entry.
-- juha