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 - oren avraham (orenav)
----------
I suppose you call the fix_nated_contact on the SUBSCRIBE method, and then the NOTIFY are sent OK, but if you call the add_contact_alias on the SUBSCRIBE method, then the NOTIFY messages get to the wrong address. (this is my case...) and i think it is a normal behaviour because the handle_subscribe uses the Contact/From headers to generate the target address.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=286#comment866
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.
Hi,
a new release of Siremis is out - v4.0.0 - web management interface that
is compatible out of the box with Kamailio v4.0.x series.
More details, including link to install tutorial, are available at:
- http://siremis.asipto.com/2013/05/08/siremis-v4-0-0-released/
Regards,
Ramona
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - oren avraham (orenav)
Attached to Project - sip-router
Summary - UAC generates messages with a NULL body which failes in SANITY module check
Task Type - Bug Report
Category - Modules kamailio
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - in UAC module when generating a message without a body (i.e: when not initializing the $uac_req(body) or even when doing $uac_req(body) = "";) the generated message contains a NULL body, which fails in the SANITY module check (due to null body instead of an empty one.) - the specific check that fails is 128 (content length)
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=295
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.
Module: sip-router
Branch: master
Commit: 994155161263dab7a7f7c01105ea474702cf7fee
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9941551…
Author: Richard Fuchs <rfuchs(a)sipwise.com>
Committer: Richard Fuchs <rfuchs(a)sipwise.com>
Date: Mon May 6 11:03:07 2013 -0400
path: support SPVE in add_path*() and add second parameter
This includes a major rewrite and code cleanup of prepend_path(), which
doesn't perform any other functional changes.
---
modules/path/README | 81 ++++++++++++++---
modules/path/doc/path.xml | 7 ++
modules/path/doc/path_admin.xml | 74 +++++++++++++++-
modules/path/path.c | 184 ++++++++++++++++-----------------------
modules/path/path_mod.c | 8 ++-
5 files changed, 227 insertions(+), 127 deletions(-)
Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=994…
GIven a route[] that might be called either directly from the request route
(transaction does not exist) or asynchronously (transaction exists), a way
is needed to rationally choose between sl_send_reply and t_reply.
At the moment, I am using an intermediate async route and setting
$var(async) = 1 and then testing that when a reply needs to be sent. It
seems there could be a more elegant solution.
One thought I had is a new tm function that will choose between t_reply and
sl_send_reply depending on whether a transaction has been created.
Any other ideas? Or am I missing an obvious solution?
--
Matthew Williams
Flowroute LLC
*Important Notice: * This message is intended only for the person or entity
to which it is addressed. The information provided is confidential.
Accordingly, any review, retransmission, dissemination or other use of
this information by, or disclosure of it to, anyone other than the intended
recipient could have significant adverse effects and is prohibited.
Opinions, conclusions and other information in this message that do not
relate to official business of my company shall be understood as neither
given nor endorsed by it.