THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#197 - pua_dialoginfo: set PUBLISH R-URIs via AVPs
User who did this - Jasmin Schnatterbeck (jasmin)
----------
That's also possible, but I think it's a question of the underlying concept - e.g.: normally, a request consists of 3 URIs (from/to/req) and those requests, whose to-Uri==req-Uri are a special kind of request. The idea is to natively represent the information content of the "most regular" request with the structure, but with having the ability to store "special" requests (req uri==to uri) in an efficient way.
So, when sending the requests, the r-uris are obtained using pubruris_caller/callee. The part of code that generates the request (dlg cb) does not have to care about to choose between variables for to-uri and req-uri for each request that is being sent - that is, indeed, not necessary.
But the structure of the memory blocks, the shm pointers reference to, are different depending on whether using the feature or not. In the first case, it is "struct str_list + uristring", in the last case it is "struct str_list" only - and this str_list is not really necessary (in the last case), but makes it possible to have a unique format for the publish-information... and therefore it helps to separate the tasks "collect/decide about request information" and "send requests".
Right, if the feature is enabled (via module parameter) it's responsibility (and freedom) of the script writer to choose appropriate PUBLISH request URIs, that includes the case to not send any PUBLISH request to anyone.
jasmin
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=197#comment491
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#196 - rtpproxy timeout functionality via dlg_terminate_dlg mi command
User who did this - Daniel-Constantin Mierla (miconda)
----------
I see the patch to rtpproxy.c of kamailio's module is rather small, sending the timeout socket address for U command, not based on to_tag. Is it?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=196#comment490
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#197 - pua_dialoginfo: set PUBLISH R-URIs via AVPs
User who did this - Daniel-Constantin Mierla (miconda)
----------
Isn't better to not allocate shm pointers for dlginfo->pubruris_caller and dlginfo->pubruris_callee when the avps are not used/set? They are used just to point inside the structure to from/to_uri. There can be some if conditions instead to set the address to be used.
Also, get_str_list(...) can return null if the avps are not set. If I understood right, nothing is generated in this case, not even using from/to_uri.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=197#comment489
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#176 - server crash while running "tm.t_uac_wait" via sercmd
User who did this - Ovidiu Sas (osas)
----------
I wasn't able to reproduce this :(
AFAIR, the issue was related to the fact that in fifo_server.c:fifo_rpc_init() the func_param.capabilities member is left NULL.
My understanding was that "capabilities" MUST be provided and it should return 0 if async commands are not available (this is how I restricted async commands in xhttp_rpc).
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=176#comment488
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#198 - uac_replace_to and backup via AVPs
User who did this - Daniel-Constantin Mierla (miconda)
----------
Can you make the patch for master branch? It does not apply clean and breaks some additions done in devel version.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=198#comment487
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#196 - rtpproxy timeout functionality via dlg_terminate_dlg mi command
User who did this - Nick Altmann (nikbyte)
----------
Sorry, browser bugs. :-)
----------
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=196#comment486
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#196 - rtpproxy timeout functionality via dlg_terminate_dlg mi command
User who did this - Daniel-Constantin Mierla (miconda)
http://sip-router.org/tracker/index.php?do=details&task_id=196
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.