THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#278 - usrloc module stops updating some records in db_mode 2
User who did this - Jordan (jordan)
----------
No, the valid record from memory is not stored in the database. Only the old expired record is in the database.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=278#comment799
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#278 - usrloc module stops updating some records in db_mode 2
User who did this - Daniel-Constantin Mierla (miconda)
----------
Got distracted a bit from this subject, caught by other tasks ...
It seems that the matching_mode 2 takes in consideration 'call-id' for database operations, but not for memory operations where it uses contact and path only. That could explain why the old record is still in database, but in memory is the new one.
Is the valid contact from memory also stored in database (the one with newer call-id)?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=278#comment798
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#270 - app_lua: add rpc reload command
User who did this - Daniel-Constantin Mierla (miconda)
----------
It doesn't seem that sr_lua_script_ver->len needs to be protected by a lock, it is set once, outside of any lock, at init. Then you read it inside a lock, but no other possibility to be updated at the same time.
Checking if there is need to reload scripts every time a function is executed seems a bit too time consuming from my point of view. Perhaps there can be added some optimization, but that can be subject to future improvements. For the beginning it would be good to have a module parameter that enables/disables the reloading. It this way one that does not need reloading does not have to be exposed to the loops executed to detect and reload scripts for each function execution.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=270#comment797
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.
Hello,
The latest commits to outbound and rr in git master should have fixed
the outbound edge proxy issues found by Olle at SIPit.
I have tested this myself with some VMs and SIPp scripts (and will be
doing some more testing over the next few days), but if anyone else has
a setup to test this with (nudge, nudge, Olle) I'd appreciate it if you
could give it a go.
Thanks,
Peter