- Added 2 new flags, disable_caller_publish_flag and disable_callee_publish_flag
- Wrapped each call to dialog_publish_multi to first check if the flag is set
This is actually quite a strange usecase. It's useful when calls do not route internally on Kamailio but are always forced out through a B2BUA which routes back to Kamailio for eventual delivery to the phone. In this case, you can disable callee (recipient) notifications for the outbound call leg from Phone->Kamailio->B2BUA and caller (initiator) notifications for the inbound leg from B2BUA->Kamailio->Phone.
In this case, you don't get notifications for 2 dialogs for each party on the call - rather 1 dialog per party. For a BLF phone, this doesn't really change anything however when BLF notifications are used to trigger events in other systems, it can be helpful to de-duplicate the messages.
I can't imagine there will be a queue of people wanting to use this... but it's implemented in such a way that behavior won't change unless the flags are defined and implemented.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/979
-- Commit Summary --
* pua_dialoginfo: Add flags to disable caller and/or callee PUBLISH when required
* pua_dialoginfo: Docs for disable_caller_publish_flag and disable_callee_publish_flag
-- File Changes --
M src/modules/pua_dialoginfo/doc/pua_dialoginfo_admin.xml (38)
M src/modules/pua_dialoginfo/pua_dialoginfo.c (165)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/979.patchhttps://github.com/kamailio/kamailio/pull/979.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/979
Instead of using the time2str routines that go through timezone
conversion in kamailio, let MySQL do it. This helps with the
sipcapture module in case the system time is CET but the database
is operated in UTC. In these cases the micro_ts and date columns
would be offseted by the timezone difference and look-ups fail
to work.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/957
-- Commit Summary --
* db_mysql: Let the database convert the timestamp
-- File Changes --
M src/modules/db_mysql/km_val.c (18)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/957.patchhttps://github.com/kamailio/kamailio/pull/957.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/957
The nsq module creates several processes for consumer workers.
The ranks for all this process are incremented one by one, starting with value 1.
Value 1 is defined as PROC_SIPINIT and has a special meaning for most of the regular modules.
One side effect of this is that the registration records are loaded from the db twice!
One simple fix would be to fork all the workers with a PROC_NOCHLDINIT ranking.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/975
We need a new label for “5.0” in the github issue tracker.
I resisted creating an issue for this since there was no label for 5.0 issues. Recursive bug :-)
Cheers,
/O