When using the rabbitmq_publish function, there is no need to create a reply-to queue, because it will never be read. And since there is never a real consumer, the queue will never be deleted. This will eventually cloak up the RabbitMQ server with millions of generic reply queues. This bug has been fixed in master already, so this is basically a backport. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1128 -- Commit Summary -- * rabbitmq: don't create reply-to queue on publish -- File Changes -- M src/modules/rabbitmq/rabbitmq.c (35) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1128.patch https://github.com/kamailio/kamailio/pull/1128.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/1128