THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Kevin Scott Adams (TheGrandWazoo)
Attached to Project - sip-router
Summary - SCA - Primary line appearance hangs when secondary is picked up.
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Medium
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - Using Polycom 650's with SIP Firmware 3.3.5 or 4.0.4 and Kamailio 4.0.2 the following happens..
If you have two line appearances with 1 call each and you select the 2nd appearance the 1st appearance on both phones will illuminate. When you hangup the second appearance the first will stay in a 'seized' state on both phones.
Using the kamcmd sca.release_appearance will clear 'seized' line.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=329
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.
Hi Peter,
In thread:
http://lists.kamailio.org/pipermail/sr-dev/2013-January/018347.html
you mentioned transaction support that you have added to PostgreSQL driver.
Unfortunately I do need to use mysql as our HA solution is based on mysql
cluster.
Hence I have implemented the required new functions e.g start_transaction.
However mysql only has one table locking mode (unlike PostgreSQL) and if
you lock a table within a transaction, you can't read other tables without
also obtaining locks for them as well. As there are places where
active_watchers table is locked but the code tries to query the watchers
table, this is an issue. I have simply disabled the table locking for the
time being.
It is possible that the implicit transaction locking that mysql is enough
to solve the issues you were trying to solve. To determine this, can you
tell me or point to a thread that explains what race conditions were trying
to be mitigated in process_notifier mode.
Cheers and thanks
Shane
--
Imagination NZ Ltd
Level 6
92 Queens Drive
P0 Box 30449
Lower Hutt 5040
+64 4 5703870 Extn 875
+64 21 608919 (mobile)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#327 - bugs in uac_redirect module
User who did this - Federico Cabiddu (lester)
----------
Imho the fact that the pool_id stores it's not so strange. While the other db modules implement the interface with the engine, db_flatstore implement the interface and the engine.
The dir part of the connection is actually the db_url, while the pools are an "internal" mechanism to optimize file write/read, without opening/closing the file for each request.
About the pkg_malloc question: I cannot answer but I can dig in the code to try to understand if there are some drawbacks.
Thank you for looking at it.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=327#comment1039
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#327 - bugs in uac_redirect module
User who did this - Daniel-Constantin Mierla (miconda)
----------
I applied the first patch for acc module.
For the second one I wanted to ask first if the new pkg malloc is safe for runtime, not to result in a leak. I hadn't have the time to look at the code in more details. I saw it has a part of freeing the table name, just don't know if both of the functions are executed together.
Also, seems a bit strange for me that the table name is part of the database id. Only the db_url should be taken in consideration. But I haven't used flatstore in ages to know its insights by heart.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=327#comment1038
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 is now closed:
FS#328 - Parser doesn't eliminate linebreaks when logging bad packets, breaks syslog
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Not a bug
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=328
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.