THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#285 - duplicate entry for key ruid_idx
User who did this - Juha Heinanen (jh)
Reason for closing: Fixed
Additional comments about closing: Hopefylly properly fixed by commmit 2190c572cd1bc4b57a3c2dd5241e556b834c728c
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=285
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#286 - add_contact_alias doesn't translate address when sending NOTIFY
User who did this - Sander van Grieken (accumulator)
----------
Since add_contact_alias should not be the cause, I suspect the notify sending part of the publish/subscribe mechanism..
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=286#comment827
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#286 - add_contact_alias doesn't translate address when sending NOTIFY
User who did this - Sander van Grieken (accumulator)
----------
I know add_contact_alias doesn't treat different methods differently, and that's what puzzles me. I see SUBSCRIBEs arriving, and a reply is sent back on the correctly translated address, but all NOTIFYs right after that are sent on the RFC1918 address.. I verified with xlog that the add_contact_alias IS called for SUBSCRIBE.
I also noticed in the active_watchers table, that there's no ;nat=yes added to the contact column, maybe that's of importance.
I can send you a pcap file with the exchange, preferably privately :)
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=286#comment826
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#286 - add_contact_alias doesn't translate address when sending NOTIFY
User who did this - Juha Heinanen (jh)
----------
i checked the source and add_contact_alias does not treat different methods differently. check with wireshark how the incoming and outgoing notify look like, check from which ip/port it comes from and compare to contact. finally, make sure e.g. using xlog messages that you really call add_contact_alias on the request.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=286#comment825
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 new Flyspray task has been opened. Details are below.
User who did this - Sander van Grieken (accumulator)
Attached to Project - sip-router
Summary - add_contact_alias doesn't translate address when sending NOTIFY
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - The presence functionality doesn't work when using add_contact_alias in my NATDETECT route.
It sends the NOTIFY to the internal/original IP address of the connected client (192.168.x.x).
When I use fix_nated_contact instead, the outgoing NOTIFYs are correctly translated.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=286
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 new Flyspray task has been opened. Details are below.
User who did this - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - duplicate entry for key ruid_idx
Task Type - Bug Report
Category - Module
Status - New
Assigned To -
Operating System - All
Severity - High
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - start kamailio in usrloc db_mode=1 with empty location table. give the two ul_add commands below and the second will result into duplicate entry for key ruid_idx error.
this test was done with master, but the bug may also exist in 4.0.
Apr 13 11:26:04 siika /usr/sbin/sip-proxy[12270]: INFO: Handling XMLRPC POST from <127.0.0.1> with body <<?xml version="1.0" ?><methodCall><methodName>mi</methodName><params><param><value><string>ul_add</string></value></param><param><value><string>location</string></value></param><param><value><string>jh(a)test.fi</string></value></param><param><value><string>sip:jh@as.test.fi</string></value></param><param><value><int>0</int></value></param><param><value><string>0.10</string></value></param><param><value><int>0</int></value></param><param><value><int>0</int></value></param><param><value><int>16</int></value></param><param><value><int>15</int></value></param></params></methodCall>>
Apr 13 11:26:10 siika /usr/sbin/sip-proxy[12276]: INFO: Handling XMLRPC POST from <127.0.0.1> with body <<?xml version="1.0" ?><methodCall><methodName>mi</methodName><params><param><value><string>ul_add</string></value></param><param><value><string>location</string></value></param><param><value><string>jh(a)test.fi</string></value></param><param><value><string>sip:jh@vm.test.fi</string></value></param><param><value><int>0</int></value></param><param><value><string>0.50</string></value></param><param><value><int>0</int></value></param><param><value><int>0</int></value></param><param><value><int>16</int></value></param><param><value><int>15</int></value></param></params></methodCall>>
Apr 13 11:26:10 siika /usr/sbin/sip-proxy[12276]: ERROR: db_mysql [km_dbase.c:122]: driver error on query: Duplicate entry 'ulcx-51691678-2fc1-1' for key 'ruid_idx'
Apr 13 11:26:10 siika /usr/sbin/sip-proxy[12276]: ERROR: <core> [db_query.c:235]: error while submitting query
Apr 13 11:26:10 siika /usr/sbin/sip-proxy[12276]: ERROR: usrloc [ucontact.c:615]: inserting contact in db failed
Apr 13 11:26:10 siika /usr/sbin/sip-proxy[12276]: ERROR: usrloc [urecord.c:480]: failed to insert in database
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=285
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.