daniel,
thanks for your reply. i started a new thread on _GNU_SOURCE.
tcp_main.c includes io_wait.h, which in turn defines _GNU_SOURCE:
#define _GNU_SOURCE /* for POLLRDHUP on linux */
_GNU_SOURCE is also included by tls module, which can be considered to
be part of "core":
#define _GNU_SOURCE 1 /* Needed for strndup */
is it possible to get rid of these two _GNU_SOURCE dependencies?
if not, then _GNU_SOURCE version of memmem can be freely used in all
modules and we can get rid of ser_memmem.
--- juha
Hello,
(cross-posting because the results are impacting users)
recently I added a new module named evapi:
- http://www.kamailio.org/docs/modules/devel/modules/evapi.html
The purpose is to able to send custom messages to applications that
connect to kamailio via tcp on a special port (different than sip port)
as well as receive messages and react on them.
One of the first use case we look at is integration with cgrates for
real time billing. For example:
- send notification when a new call comes in and cgrates will return
allow/reject
- send notification when the call starts so cgrates can start billing
- send notification when the call ends so cgrates will close bllling
The module is now in quite good shape, sending and receiving messages.
Sending is done from config file, in the future some modules might do it
from inside. Received message is passed to config file via an
event_route and variables.
Now, the point of this discussion is to debate following points:
1) should there be a specific format used for this messages? The
examples in the README use json. The module can encapsulate them in
netstring format when sending over tcp to be easy to parse and read the
message at once. This is optional, the message can be sent as it is
2) now messages are sent to all connected applications, should be
there some subscription mechanism per event? If yes, then there has to
be a way to specify the event, so point 1) might need a specific format
3) handle response - should be there a defined api that will say
allow, reject, drop? I was thinking that the return could be some script
for an embedded interpreter (e.g., Lua) that can be executed from config
file. Or, alternative, manually scripted in the event route, so each
user defines its own api
3) other suggestions for what should be discussed?
Looking forward to opinions regarding these matters.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Bill Radis (radisb)
Attached to Project - sip-router
Summary - Setting only dlg_set_property("ka-dst") doesn't work
Task Type - Bug Report
Category - dialog
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 4.1
Due in Version - Undecided
Due Date - Undecided
Details - In dlg_hash.c, line 135:
if(!(dlg->iflags & (DLG_IFLAG_KA_SRC | DLG_IFLAG_KA_SRC)))
return 0;
should be
if(!(dlg->iflags & (DLG_IFLAG_KA_SRC | DLG_IFLAG_KA_DST)))
return 0;
It causes the keep-alives to work only if only "ka-src" attr is set or both "ka-src" and "ka-dst" are set, but not when only "ka-dst" is set.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=416
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.