You can now define a mcast parameter before a listen parameter that
contains a multicast address. After each listen parameter mcast gets
reset. mcast must contain the name of an interface, eg `eth1`.
Issue GH#813
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/815
-- Commit Summary --
* core: added mcast to select interface for multicast
-- File Changes --
M cfg.lex (3)
M cfg.y (16)
M globals.h (1)
M ip_addr.h (3)
M main.c (1)
M socket_info.c (8)
M udp_server.c (24)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/815.patchhttps://github.com/kamailio/kamailio/pull/815.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/815
If you configure kamailio to listen on a multicast address (eg. `224.0.1.75`) it _auto_ selects the interface that joins the multicast group. The selection happens on what the kernel thinks the multicast IP address is active on. This is decided by the kernel route table since you cannot configure a multicast address on your interface. In the default scenario this would mean the default route interface will be selected to join the multicast group. In case you want to select another interface this is possible by altering the route for that particular multicast address to the interface you desire. This is a workable solution but it has the following downsides:
- need to add route manually to specify interface
- multicast for 1 specific address only possible on 1 interface
I would like to propose a solution by adding a config parameter to kamailio (eg. `mcast_interface`) which could then be defined before each `listen` directive that is a multicast address. This would allow for selecting an interface per listen socket in the same way as you can specify the amount of workers for an interface. In this scenario there is no need for manually adding a route to specify the interface.
Please let me know if this is a feature that is of interest to kamailio. If so I'd be willing to work on this myself, but somebody else can also do it.
If something isn't clear or needs more explanation don't hesitate to ask.
--
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/813
- check dialog_id is not NULL before call delete_presentity_if_dialog_id_exists
sometimes after check_if_dialog(str body, int *is_dialog, char **dialog_id) it is possible
is_dialog==1
dialog_id==NULL
#0 __strcmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp.S:260
#1 0x00007feb2e446603 in delete_presentity_if_dialog_id_exists (presentity=0x7feb545c8ca8, dialog_id=0x0) at presentity.c:419
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/817
-- Commit Summary --
* presence: fix crush if dialog id is NULL
-- File Changes --
M modules/presence/presentity.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/817.patchhttps://github.com/kamailio/kamailio/pull/817.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/817
Add new rabbitmq module.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/786
-- Commit Summary --
* rabbitmq: Add new module
-- File Changes --
A modules/rabbitmq/Makefile (14)
A modules/rabbitmq/README (244)
A modules/rabbitmq/doc/Makefile (4)
A modules/rabbitmq/doc/rabbitmq.xml (39)
A modules/rabbitmq/doc/rabbitmq_admin.xml (338)
A modules/rabbitmq/rabbitmq.c (579)
A modules/rabbitmq/rabbitmq.h (15)
A modules/rabbitmq/utils.c (192)
A modules/rabbitmq/utils.h (50)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/786.patchhttps://github.com/kamailio/kamailio/pull/786.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/786
When I'm using a htable in Kamailio, I can get the htable:expired:<htable> route to be executed if I include in my htable name a _ character (meaning my_htable does not work whereas myHable works).
Is it a known restriction or limitation the htable module or of Kamailio or is it a bug?
I'm using Kamailio on Ubuntu.
--
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/811