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#comment… 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.