THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - David Kovarik (kovik)
Attached to Project - sip-router
Summary - bad sotket after re-register in location table
Task Type - Bug Report
Category - usrloc (k)
Status - Assigned
Assigned To - Daniel-Constantin Mierla
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - This happened after re-register
mysql query log: socket='udp:81.31.45.57\0\0060' in table udp:81.31.45.57060 instead of udp:81.31.45.57:5060
Query update location set expires='2011-12-14 15:00:47',q=-1.00 ,cseq=4,flags=0,cflags=192,user_agent='Well T20 hw7.0.0.54 fw9.60.9.5 00:15:65:15:ae:b2',received='sip:85.135.106.202:4078',path=NULL,socket='udp:81.31.45.57\0\0060',methods=16383,last_modified='2011-12-14 14:58:47' where username='300169' AND contact='sip:300169@192.168.2.101:5062' AND callid='1248885213(a)192.168.2.101'
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=191
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.
A user has added themself to the list of users assigned to this task.
FS#191 - bad sotket after re-register in location table
User who did this - David Kovarik (kovik)
http://sip-router.org/tracker/index.php?do=details&task_id=191
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#185 - textopsx:msg_apply_changes() can corrupt incoming TCP message buffer
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Backported to branch 3.2 as well.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=185
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#183 - tls module error on initialization when used together with the dialog module
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Commit done to master branch.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=183
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#183 - tls module error on initialization when used together with the dialog module
User who did this - Daniel-Constantin Mierla (miconda)
----------
I committed the patch with some safety checks for shutdown at init time (when there is an error during startup). If you can give a try to tls and postgres together in such deployments and let me know if works, then I can backport to 3.2 sooner, I expect it will take me time to do it, since I am not using postgres I need to setup some new test environment.
Anyhow, I am closing this item, reopen if issues appear.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=183#comment462
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.
I am having problems with the db_fetch_next routine and Postgres.
I can’t see any problem with my code that calls it, and as far as I can tell the problem appears to be in the db_postgres_fetch_result routine.
On the first invocation of db_postgres_fetch_result it allocates a result structure and gives me the first 5 rows of the 198 that match my query after calling db_postgres_convert_rows.
On the 2nd invocation it fails to retrieve the next 5 rows because CON_RESULT(_con) is NULL !
Anyone got any suggestions?
Paul Pankhurst
Engineering Director
Crocodile RCS Ltd
Tel: 01489 668620
DDI: 01489 668622
www.crocodile-rcs.com