> Thanks for the pull request. Just inventing a new patch category is not the
> right approach, sorry.
Changed to core.
> Please just use "core" for the core part and the other module parts as
> individual commits per module with the respective module name as prefix.
Done.
Kind regards,
Seb
Have you looked at
https://kamailio.org/docs/modules/stable/modules/rabbitmq.html ?
--
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/2895#issuecomment-949930320_
### Description
I am using kazoo-module for connecting Kamailio to RabbitMQ and publishing
messages to several consumers.
Now I´d like to extend my setup to a more sophisticated routing based on a
consistent hash-exchange
(https://github.com/rabbitmq/rabbitmq-consistent-hash-exchange), while
r
> Thanks for the pull request. Just inventing a new patch category is
> not the right approach, sorry.
>
> Please just use "core" for the core part and the other module parts as
> individual commits per module with the respective module name as
> prefix.
No problem, will do.
> One small question
Thanks for the pull request. Just inventing a new patch category is not the
right approach, sorry.
Please just use "core" for the core part and the other module parts as
individual commits per module with the respective module name as prefix.
One small question, why do you add this additional
libcs are implementing changes to fix the year 2038 issue on 32 bit
platforms (see [1]). musl libc already went ahead and implemented it,
starting with musl-1.2.0 (see [2]).
This commit adds a new definition to src/core/dprint.h:
TIME_T_INT_FMT
If __USE_TIME_BITS64 is defined (by a time64 libc,
Closed #2803.
--
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/2803#event-5506018958___
Kamailio (SER) - Development Mailing List
sr-dev@l
@grumvalski: if it does not work without it, then you can backport - you have
commit access.
--
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/2888#issuecomment-949650352__
@NGSegovia commented on this pull request.
> @@ -169,12 +169,16 @@ int msrp_relay(msrp_frame_t *mf)
wsev.len = p - reqbuf;
wsev.id = con->id;
evp.data = (void *)&wsev;
+ tcpconn_put(con);
@NGSegovia pushed 1 commit.
bf371ccbfa1c89fefcd9d9322ae75189d97fc862 msrp: fix some tcpconn where memory
was never cleaned up
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/kamailio/kamailio/pull/2890/files/19714ebaa0f653f65d83025e2d
Module: kamailio
Branch: 5.3
Commit: 67f40d2f7e59820e8527cd8457e70741caf0c2da
URL:
https://github.com/kamailio/kamailio/commit/67f40d2f7e59820e8527cd8457e70741caf0c2da
Author: Kamailio Dev
Committer: Kamailio Dev
Date: 2021-10-22T14:32:49+02:00
modules: readme files regenerated - modules ... [
- URL:
https://github.com/kamailio/kamailio/commit/3bcbc75ffd69818ca6ce2491fc7aa7f7fb242927
Author: Theo
Date: 2021-10-22T08:48:48Z
tm: 200 OK not processed correctly by Proxy after final non-2xx
Description:
Problem:
Forwarding of 200 OK while sent 488 waits for ACK, destroys the U
Hello @henningw,
I checked usage of cscf_get_ue_via function. And I saw ims_ipsec_pcscf,
ims_qos, ims_registrar_pcscf module are using this function.
All of them are pcscf modules.
ims_usrloc_pcscf keeps a hashtable to keep the pcscf contacts. And hash code
is calculated with UE's IP address
Thanks for merging Henning. Should we backport it also to stable branches?
--
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/2888#issuecomment-949314462_
14 matches
Mail list logo
