Gang,
We have some new functionality for the nathelper planned that would need
to know final destination URI for the message to work properly.
Currently this means that we have to require script writer to invoke
this function only after all URI transformations have been applied,
which might quite significantly complicate script logic. Moreover it
might be even impossible in some cases to do so, for example when using
t_relay() function, which uses transaction state to determine message
destination.
Therefore, I see the need for a callback mechanism in core, allowing
callback functions to be registered on per-message basis and then to be
executed in some well-defined points of message processing. The
mechanism could be sufficiently generic to allow different uses. One of
the other use that I have in mind is destructor callback, which is to be
called when the message structure is being freed, so that modules would
be able to release any resources allocated (memory, connections,
descriptors, etc).
Any comments and suggestions are welcome.
Regards,
--
Maksym Sobolyev
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
T/F: +1-646-651-1110
Web: http://www.sippysoft.com
MSN: sales(a)sippysoft.com
Skype: SippySoft
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#60 - kamailio 3.0.x: segfault in carrierroute
User who did this - marius zbihlei (marius.zbihlei)
Reason for closing: Fixed
Additional comments about closing: Bug Fixed by patch 5604e51eb8fd6502495a37c26f9c549bcd63ca8a
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=60
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 new Flyspray task has been opened. Details are below.
User who did this - Ovidiu Sas (osas)
Attached to Project - sip-router
Summary - kamailio: updated module_exports for RPC functionality
Task Type - Improvement
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Hello all,
Adding RPC functionality to the k modules requires a new field in the module_exports for the k interface.
Attached is a small patch that updates the k module_exports.
I was playing with it while adding some RPC functionality to the k ratelimit module.
Before going more into this path, I would like to have this patch reviewed and integrated into the source tree.
Maybe we should also think about unifying the s and k module exports.
Regards,
Ovidiu Sas
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=62
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#62 - kamailio: updated module_exports for RPC functionality
User who did this - Ovidiu Sas (osas)
http://sip-router.org/tracker/index.php?do=details&task_id=62
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,
the process of merging users(a)list.kamailio.org and
sr-users(a)lists.sip-router.org is completed, offering a single place for
community discussions via email related to stable versions and generic
topics, also removing confusion for new comers which to use for best
feedback.
Because sr-users was a rather new mailing list, I imported the archive
from users. It will help to continue the topics and have the entire
knowledge base built over years in the same place, for web searches.
The old Users mailing list archive still exists separately, link at:
http://lists.kamailio.org/pipermail/users/
No new posts will get there, subscription is disabled, messages to users
list are directed to sr-users (therefore replying to existing threads on
either of the mailing lists work just fine).
No matter you were a Users or SR-Users subscriber, updates to your
profile can be done at:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
I case your password is no longer valid, you can retrieve it via
password reminder at:
http://lists.sip-router.org/cgi-bin/mailman/options/sr-users
Thanks,
Daniel
PS.
Some of you may have received an unintentional "unsubscribed from
sr-users-new mailing list" message, just ignore it - happened when I
simulated synchronization of members on temporary name sr-users-new, no
unsubscribe action was actually done -- sorry for inconvenience.
--
Daniel-Constantin Mierla
Hi, compiling with "make deb" makes usage of the config.h in which I
can set the PKG memory. This valua can also be set (in a more
fashioned way) in Makefile.vars along with other parameters as MEMDBG.
However "make deb" doesn't read Makefile.vars so memory debugging is
not compiled. Perhaps I should add "-DDBG_QM_MALLOC" somewhere in the
debian rules file?
But more important, is it possible to share an unique "custom
parameters" file readable when using "make deb" or whatever "make
xxxxx"?
Thanks.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
Hello,
I renamed kamailio-docs(a)lists.kamailio.org to
sr-docs(a)lists.sip-router.org. Info about it at:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-docs
Lately, several discussions touched the documentation aspects, in a need
for a better structuring and updates for the new context of sip router
project. The old mailing list was active for a while, but with the start
of sip router project was ignored because of more focus on integration work.
I hope some of you will join, help to build new documentation and spot
mistakes in existing versions. Volunteers that want to lead various
documentation efforts are more than welcome! Just say what you need...
Thanks,
Daniel
--
Daniel-Constantin Mierla * http://www.asipto.com/ *
http://twitter.com/miconda *
http://www.linkedin.com/in/danielconstantinmierla