THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Michel de Weerd (mweerd)
Attached to Project - sip-router
Summary - Notify has incorrect information when q=0.5 in the Contact header
Task Type - Bug Report
Category - Modules kamailio
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - When the …
[View More]ims_registar_scscf module sends a Notify after a deregistration and the contact has q= parameter, the XML contains state terminated for the AOR, and for the contact the state is active.
<?xml version="1.0"?>
<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" version="1" state="partial">
<registration aor="sip:+351915639755@nl.intinfra.com" id="0x2aeaf52ebb80" state="terminated">
<contact id="0x2aeaf52ebdd0" state="active" event="registered" expires="3558" q="0.500">
<uri>sip:+351915639755@192.168.230.47:5060;ep=192.168.137.206:49856;transport=udp</uri>
</contact>
</registration>
</reginfo>
When q= parameter is not added in the contact field, the XML in the notify contains the following information after deregistration, AOR is terminated and also contact id in the state terminated.
<?xml version="1.0"?>
<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" version="1" state="partial">
<registration aor="sip:+31652526347@nl.intinfra.com" id="0x2b3396aecd60" state="terminated">
<contact id="0x2b3396af1e60" state="terminated" event="unregistered" expires="0">
<uri>sip:+31652526347@10.38.102.75:49844;transport=tcp</uri>
</contact>
</registration>
</reginfo>
The contact in the XML of the notify seems to be incorrectly constructed when q=.. used in the contact header.
Attached a patch which creates the correct contact info when the subscriber deregisters
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=342
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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Devs Voicenter (voicenter)
Attached to Project - sip-router
Summary - presence_dialoginfo -> force_single doesn't sent most relevant xml
Task Type - Improvement
Category - Modules kamailio
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - …
[View More]When single xml mode is turned on(some phones do not support/treat right multiple xmls). Not always most relevant xml is sent.
The order should be according to priority: early/confirmed/terminated. And it shouldn't be allocated due time. Other option is to make it optional. Here is the sample of patch:
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=341
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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Devs Voicenter (voicenter)
Attached to Project - sip-router
Summary - module pua_reginfo, function reginfo_handle_notify
Task Type - Bug Report
Category - Modules kamailio
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - According to the …
[View More]documentation (http://www.kamailio.org/docs/modules/4.0.x/modules/pua_reginfo.html) function reginfo_handle_notify () doesn't accept any parameters, though the code says different:
{"reginfo_handle_notify", (cmd_function)reginfo_handle_notify, 1, domain_fixup, 0, REQUEST_ROUTE}
the quick fix would be:
- {"reginfo_handle_notify", (cmd_function)reginfo_handle_notify, 1, domain_fixup, 0, REQUEST_ROUTE},
+ {"reginfo_handle_notify", (cmd_function)reginfo_handle_notify, 0, domain_fixup, 0, REQUEST_ROUTE},
but not sure if it's the right one
AFAIK it's in all 4.0.0 (maybe not including -pre release)
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=340
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.
[View Less]
Hi,
For the above, does it make sense to add new modules - dmq_dialog,
dmq_presence, etc? Or just to add to existing code?
Cheers,
Charles
--
www.sipcentric.com
Follow us on twitter @sipcentric <http://twitter.com/sipcentric>
Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered
office: Unit 10 iBIC, Birmingham Science Park, Holt Court South, Birmingham
B7 4EJ.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#339 - pua_reginfo: Fails to insert the contact into the location table
User who did this - Wonbin Cho (wbcho)
----------
That will be really appreciated.
:)
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=339#comment1080
You are receiving this message because you have requested it from the Flyspray bugtracking system. If …
[View More]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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#339 - pua_reginfo: Fails to insert the contact into the location table
User who did this - Daniel-Constantin Mierla (miconda)
----------
OK. I'm not the developer of the module, I just commented by looking at the patch. If the developer doesn't get to it soon, I will apply the patches to fix the issue and he can jump in later for tunings.
----------
More information can be found at the following URL:
…
[View More]http://sip-router.org/tracker/index.php?do=details&task_id=339#comment1079
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.
[View Less]
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#339 - pua_reginfo: Fails to insert the contact into the location table
User who did this - Wonbin Cho (wbcho)
----------
Hi,
In fact, I left a comment on FS#338 about that.
The code gets there not because of the length of aor but because the first loop in the while statement hits following lines:
/* Only process registration sub-items */
if (xmlStrcasecmp(registrations->name, BAD_CAST "registration"…
[View More]) != 0)
goto next_registration;
It seems that the first "registration" item of "reginfo" XML node is not properly loaded.
The first loop hits "goto next_registration" (as quoted above) and 'ul.unlock_udomain' function is called there.
But it seems that aor is initialized by 'ul.lock_domain' function which is not called in the first loop.
This causes the segfault I reported in FS#338.
So I added if (aor.len > 0) condition to avoid it.
I think that is not a real solution that causes the problem. It's only my humble workaround so please feel free to change as you fit.
Thanks!
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=339#comment1078
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.
[View Less]