The topos module fails to update the dialog data in the topos_d table after the processing of re-INVITEs.

I have setup a call at 11:55, and triggered a re-INVITE at 12:08. The respective topos_d table entry is not updated.

This causes the entry to expire after topos dialog_timeout value.

I would expect that the timestamp of the call in the topos_d table is updated. Is this assumption correct? If the current behavior is expected, it should documented in the module README.

No error messages from topos module in kamailio.log. Output from tables:

MariaDB [kamailio]>  select id, rectime, s_method, a_callid from topos_t; select id, rectime, s_method, a_callid from topos_d;
+-----+---------------------+----------+----------------------------------+
| id  | rectime             | s_method | a_callid                         |
+-----+---------------------+----------+----------------------------------+
| 305 | 2019-08-04 12:08:12 | INVITE   | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
| 306 | 2019-08-04 12:08:12 | ACK      | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
| 307 | 2019-08-04 12:08:14 | INVITE   | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
| 308 | 2019-08-04 12:08:14 | ACK      | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
+-----+---------------------+----------+----------------------------------+

+-----+---------------------+----------+----------------------------------+
| id  | rectime             | s_method | a_callid                         |
+-----+---------------------+----------+----------------------------------+
| 156 | 2019-08-04 11:55:22 | INVITE   | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
+-----+---------------------+----------+----------------------------------+

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.