If you can move the IP between rtpengine hosts, you can use Redis to publish/subscribe state between them. Take a look here: https://kamailio.org/events/2020-KamailioWorldOnline/KW2020-YufeiTao-HAForKa...

You may want to consider a separate pool for rtpengine, as it may scale much differently. This would allow you to inform all of the Kamailio nodes of incoming and outgoing rtpengine hosts. Using a fixed config, you can selectively enable/disable nodes via RPC commands/kamcmd. If you need something more dynamic, the Kamailio module supports loading/reloading nodes from a database table. Take a look at rtpengine_allow_op and db_url.

On Tue, Nov 5, 2024 at 9:31 PM Evgenii Buchnev via sr-users sr-users@lists.kamailio.org wrote:

Hi Dear Community,

Would appreciate your input into where to look further to explore my options and would be good to learn your experience with the following.

There are many active-active kamailio nodes behind tcp load balancer. On the same VM with each Kamailio there is an instance of RTPEngine to manage Media/Transcoding/Etc for that Kamailio. This scales UP easily - new nodes just added behind tcp load balancer. To be able to scale down and/or update node configuration - I'd like to be able to drain sessions/calls properly and pass any active calls from current Kamailio and RTPEngine to other nodes.

DMQ is not yet in place, although it's planned.

What would be proper ways of migrating RTP sessions to other RTPEngines? Caveats?

Also wonder how properly a tcp/tls based SIP session can be passed to another Kamailio?

Thank you in advance for your input.

Evgenii Buchnev __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: