Over the weekend, one of our customers in the USA suffered a mass
de-registration of handsets during the daylight saving change. After one
registration interval, they all re-registered, but inbound calls failed
for one full registration interval of each handset.
The same customer had this happen last year when they were running
OpenSIPS. At that time, it was determined by the OpenSIPS developers
that the problem was that the "expires" column in the location table
(stored in MySQL, with db_mode 3) was of type "datetime", which does not
handle daylight saving changes gracefully. They suggested changing the
db_mode, but this isn't an option because other software reads the
location table in real time to decide which SIP proxy machine the
handset is registered to. We discussed changing this column (and
last_modified which is also a datetime) to type "timestamp", but our
customer switched to Kamailio before we could make a final decision on this.
My question is therefore: can we safely do a MySQL "alter table" command
to change these two columns to timestamps so that this problem won't
happen again next year?
--
Alistair Cunningham
+1 888 468 3111
+44 20 799 39 799
http://integrics.com/
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#360 - Dialog callback on pua_dialoginfo after restart
User who did this - Kristian Høgh (kfhdk)
----------
I created a suggestion. Comments?
First I cleanup whitespace/indent mismatch (patch 01-cleanup-whitespaces.patch)
This patch changes no functionality.
Then I add callback to DLGCB_LOADED. (02-add-loaded.patch)
Created and loaded share a good part of code, so I split common parts into get_dialog_data.
At this point, existing dialogs are loaded after reboot, but we don't know who to send publish to.
The last patch (03-use-dialog-var.patch) saves pubruris_caller/pubruris_callee as dialog var when created.
On restarting kamailio pubruris_caller/pubruris_callee are restored from database.
----------
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=360#comment1153
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#341 - presence_dialoginfo -> force_single doesn't sent most relevant xml
User who did this - Daniel-Constantin Mierla (miconda)
----------
It is only devel and your patch was merged with existing code for selecting the node. So the result is different that you have locally.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=341#comment1152
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#341 - presence_dialoginfo -> force_single doesn't sent most relevant xml
User who did this - Devs Voicenter (voicenter)
----------
I think i ignored and forgot other states as i needed it for devices with led indication of call state and most have 3 states:
no calls,(same as all terminated)
rigning incoming (early)
talking (confirmed)
I'll try to add other states as well. Is it pushed to 4.0.x as well or only to devel ?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=341#comment1151
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#341 - presence_dialoginfo -> force_single doesn't sent most relevant xml
User who did this - Daniel-Constantin Mierla (miconda)
----------
I pushed a re-worked patch in git master barnch that still keeps the previous node selection mechanism if winner node is still NULL after your criteria. That should keep safe all the states. If you need to work on it, use the branch master (the patch is not backported) and create a new patch from it. Also, testing would be recommended and appreciated.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=341#comment1150
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.