Hi,
I have a Kamailio cluster with multiple nodes sharing information over DMQ.
My DMQ configuration:
- `notification_address` points to a DNS name that resolves to all cluster
nodes
- `multi_notify` is set to 1
**Problem:**
When I add a new node to the cluster, I update the DNS record to include
the new node's IP. However, DMQ only resolves the `notification_address` at
startup, so existing nodes don't discover the new peer.
**What I've tried:**
1. Looking for a DMQ reload command (like `dmq.reload`) - doesn't exist
2. `kamcmd cfg.reload` - doesn't re-resolve DMQ notification_address
**Question:**
How can I force DMQ to re-fetch/re-resolve the peer list without restarting
Kamailio?
Restarting is not an option as it would disrupt active TCP/WebSocket
connections and ongoing calls.
**Environment:**
- Kamailio version: 6.0.1
- DMQ configuration:
```
modparam("dmq", "server_address",MY_DMQ_SERVER_ADDR)
modparam("dmq", "notification_address", MY_DMQ_NOTIFICATION_ADDR)
modparam("dmq", "multi_notify", 1)
modparam("dmq", "num_workers", 4)
modparam("dmq_usrloc", "enable", 1)
modparam("dmq", "ping_interval", DMQ_PING_INTERVAL)
```
Any suggestions for dynamic peer discovery without restarts?
Regards
Rajneesh
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions --
[email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
