Hello,
uac_replace_to and uac_replace_from functions can receive two arguments,
display and uri.
In current implementation two double quotes are automatically added to
display during fixup.
Would it be a better behavior not to add any quotes? If the user wants
some quotes he should add them by himself.
E.g:
right now, if I get a display "Vicente" from an invite and store it in
$fn variable, if I call
uac_replace_from($fn, uri_foo) it produces ""Vicente"" in the
display which kamailio complaints about.
If we would avoid quotes, uac_replace_from function could accept:
uac_replace_from("Bob", uri) display = Bob
uac_replace_from("\"Bob\"", uri) display = "Bob"
standard supports quoted strings, not quoted tokens, spaces before and
after quotes, etc.
Attached patch should avoid quotes in uac_replace functons.
What are your opinions about this?
Kind regards,
Vicente.
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 - tm:branch-failure event_route is not executed on all branch failures
Task Type - Bug Report
Category - tm
Status - New
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - when t_relay() fails due to unreachable tcp destination, [t_fwd.c:1520] generates error message
LOG(L_ERR, "ERROR: t_send_branch: sending request on branch %d "
"failed\n", branch);
and immediately sends back SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) response.
tm:branch-failure event_route is not executed although it has been activated for the branch. instead, this makes is difficult to act on the failing branch in the config script, for example, by unregistering the unresponsive contact.
currently tm:branch-failure event_route is executed only from t_reply.c when reply is processed. one possibility to fix this might be generating a fake reply from t_fwd.c so that t_reply.c could do its job. another one might be calling the activated tm:branch-failure event_route directly from t_fwd.c.
i would appreciate if someone who is familiar with internals of tm module could fix this bug.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=296
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.
if t_relay() fails, for example, when tcp connection to destination is
dead, no transaction is created and therefore tm:branch-failure
event_route thus is not executed. this greatly complicates config
script writing, for example, when trying to unregister unresponsive
contacts.
is there any possibility to enhance the current t_relay implementation
so that even if transaction is not created, tm:branch-failure would
still be executed for each branch of the failing t_relay?
-- juha
Hi all,
I've proposed an RTC track (maybe half-day event) for DebConf13 in August
All the practical details are here, (talk proposals welcome!):
http://debconf13.debconf.org/
and it is a good idea for people to register ASAP, even if not attending
for the whole week. The exact day for the RTC track should be confirmed
later. If just interested in RTC, please do let me know by email after
you register.
DebConf13 is probably where some of the groundwork will be done for
Debian 8's RTC strategy. Debian 7 was just released and there will be
about 12-18 months development before the next freeze begins. In that
time, it is really crucial for Debian to take a leadership position in
making RTC interoperable in a way that involves no more effort than the
scary alternatives.
And it will be Debian's 20th birthday... that doesn't happen often in a
free software project.
Please feel free to email me privately or ask general questions on
debconf-discuss or #debconf IRC
Regards,
Daniel