Hello José,
The issue may have been introduced by the recent multi-notify option.
To test the theory, could you try setting multi_notify to 0 and the
notification address to one of either the A or B server IP addresses?
e.g.
modparam("dmq", "notification_address", "sip:172.112.10.206:5060")
mod
Hello,
DMQ will remove nodes from its internal list if they fail to respond to its
pings - with the exception of the original notification peer specified in
config. This way, if the network connection is lost, DMQ will continue to
try the original peer indefinitely until connectivity is restored,
Hello Daniel,
The parameters that i have configured on my kamailio server are:
#!ifdef ENABLE_REG_SYNC
modparam("registrar", "sock_flag", 18)
modparam("registrar", "sock_hdr_name", "Sock-Info")
### SIP registrar replication to other nodes ##
loadmodule "dmq.so"
### distributed messa
Hello,
what are the parameters for dmq module?
Cheers,
Daniel
On 01/02/2017 11:32, José Seabra wrote:
> Hello there,
> My DMQ cluster has 4 nodes and by some reason 2 of them lost the
> network connectivity for long time(~ 4 hours), after the network of
> these 2 nodes come back they didn't ge
Hello there,
My DMQ cluster has 4 nodes and by some reason 2 of them lost the network
connectivity for long time(~ 4 hours), after the network of these 2 nodes
come back they didn't get connected on DMQ cluster automatically, i had to
restart kamailio to get them again on DMQ list.
My doubts here
