I have 2 nodes that i’m trying to bring up with res_corosync on asterisk 11.
The problems I’m having is that the devstate information isn’t being replicated for queue agents. So when a call comes in that lands on servers 1 and they in INUSE that state isn’t being replicated to server 2. So if a second call lands than that agent is getting a second call presented to them.
optel21*CLI> corosync show members
=============================================================
=== Cluster members =========================================
===
=== Node 1
=== --> Group: asterisk
=== --> Address 1: 172.24.220.16
=== Node 2
=== --> Group: asterisk
=== --> Address 1: 172.24.220.17
and
optel21*CLI> corosync show config
=============================================================
=== res_corosync config =====================================
===
=== ==> Publishing Event Type: mwi
=== ==> Subscribing to Event Type: mwi
=== ==> Publishing Event Type: device_state
=== ==> Subscribing to Event Type: device_state
=== ==> Publishing Event Type: ping
=== ==> Subscribing to Event Type: ping
=============================================================
here is what I have for corosync.conf
Please read the corosync.conf.5 manual page
compatibility: whitetank
totem {
version: 2
secauth: off
nodeid: 1
interface {
member {
memberaddr: 172.24.220.16
}
member {
memberaddr: 172.24.220.17
}
ringnumber: 0
bindnetaddr: 172.24.220.0
mcastport: 5405
ttl 1
heartbeat_failures_allowed=1000
}
transport: udpu
}
logging {
fileline: off
to_logfile: yes
to_syslog: yes
debug: on
logfile: /var/log/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: AMF
debug: off
}
have it i do something like a devstate change Custom:agent-Agent-name INUSE that change isn’t reflected on the second node.