THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#319 - Possible memory leak in srdb1
User who did this - Daniel-Constantin Mierla (miconda)
----------
Doesn't look like that. The pointer to str as well as str->s are in the same memory block, not a special malloc for str->s. Can you give the path to the file and the line where the memory allocation is done for ->s?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=319#comment1025
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.
Hello,
I have a question on the use of t_check_trans for in-dialog requests.
If an in-dialog INVITE is challenged by kamailio (sending a 407
response), the ACK should be absorbed. However, the t_check_trans
function does not terminate the script. In our config, this means the
ACK gets sent to the client due to the route-set.
Should t_check_trans recognise that this transaction was rejected
locally, even though there is an onward route-set?
Hugh
--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#325 - tm doesn't relay changed 'To' header in CANCEL before dialog is established
User who did this - Daniel-Constantin Mierla (miconda)
----------
Look at modules/tm/t_cancel.c -- you have to backport the condition that enables the use of To header from uac buffer when building the cancel.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=325#comment1024
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#325 - tm doesn't relay changed 'To' header in CANCEL before dialog is established
User who did this - Trip Volpe (tvolpe)
----------
Can you point me in the direction of where that to-header change flag is used? I've been looking a bit through replace_uri() in uac, and I did find where it registers a tm callback, but that's only for TMCB_RESPONSE_IN.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=325#comment1023
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#71 - DB_DELETED flag is not checked in www_authenticate function of auth module
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Won't implement
Additional comments about closing: Function from former ser flavor.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=71
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#324 - Entity URI in NOTIFY XML body
User who did this - Daniel-Constantin Mierla (miconda)
----------
I had no time to dig in specs, I mainly applied the patch with an extra check. Could be more consistent as you describe, although not sure sip vs. sips would make a difference. Usually one party wants to subscribe to dialog states of another party, that's typically giving just sip address. sips is more about real time secure communication channel from end to end.
You can commit the enhancement you proposed as you have time/need to do it.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=324#comment1022
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#324 - Entity URI in NOTIFY XML body
User who did this - Pawel Sternal (Sternik)
----------
In my situation there is no problem because I only use "sip:" url but Alex might be right. Maybe instead compose uri with hardcoded "sip" url can be use "pres_uri" variable. Tomorow I'll try check this concept.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=324#comment1021
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#324 - Entity URI in NOTIFY XML body
User who did this - Alex Hermann (axlh)
----------
Should "sip:" really be hardcoded?
I would expect the entity to be identical to the presentity in the corresponding PUBLISH (which would equal the presentity the watchers subscribe to). That might have been a sips uri, maybe even a completely other protocol like xmpp or http.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=324#comment1020
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#241 - Incorrect outbound interface used in Via and Record-Route
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Not a bug
Additional comments about closing: It is a matter of mhomed (for bridging un-routeable networks) or config rules. Other selection criteria can be added as enhancements.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=241
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.