THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#364 - Crash in TCP Read on Kamailio 4.0.1
User who did this - Josh (JoshE)
----------
I think we may have hijacked my original issue here. My 4.0.1 - 4.0.4 were crashing on what appeared to be some combination of XMLRPC and outbound cURL / HTTP requests.
It certainly isn't 100% reproducible, but with a handful of fairly active servers, I am able show the issue occurs every few weeks.
I am updating everything to 4.1 and will give you guys an update on the behavior there.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=364#comment1210
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#374 - Database location table not updated correctly?
User who did this - Daniel-Constantin Mierla (miconda)
----------
You have to upgrade to at least latest 4.0 (or 4.1) and set ruid based db operations:
- http://kamailio.org/docs/modules/4.0.x/modules/usrloc.html#usrloc.p.db_ops_…
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=374#comment1209
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#374 - Database location table not updated correctly?
User who did this - Morten Tryfoss (mtryfoss)
----------
I think unregister/expire works as long as callid matches between db and memory.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=374#comment1208
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.
Good morning,
I've tried building debian packages for squeeze and noticed that the sipt
module isn't getting packaged. How is it decided what modules get
included into the deb packages?
Regards,
Torrey
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#374 - Database location table not updated correctly?
User who did this - Hugh Waite (hugh.waite)
----------
I made some changes recently (to master and 4.1) so that if a sip.instance was present and the callid is different to what is in memory/DB, all previous entries are deleted.
It was tracked as FS#368 and commited to the registrar module on 22 Novemebr.
Is this an additional problem that it doesn't work for unregister/expire? Does it need backporting to other branches?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=374#comment1207
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#374 - Database location table not updated correctly?
User who did this - Morten Tryfoss (mtryfoss)
----------
In these cases it seems like sip.instance is always used. It's a mobile client using pjsip which switches between different networks several times during the day.
I'll try to explain:
1) at register, contact is inserted.
2) at re-register, contact is updated using instance and req_id.
3) may switch between different networks. still ok.
4) callid changes (could be a crash/restart of the sip client). "kamctl ul show" is updated correctly, but not the database table. instance and req_id is still being used, so all other fields except callid is updated correctly.
5) client looses network and the registration expires. kamailio tries to delete this using username + contact + callid. affected rows is zero, because there is a mismatch in the callid field between kamailios internal database and the location. table.
6) client restores network and registers again, still with the same instance id. now there are two rows in the location table and one in kamailios internal database.
7) at re-register both rows are updated using instance + req_id. all fields except callid is updated on both rows.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=374#comment1206
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.