21 Jul
2015
21 Jul
'15
5:12 p.m.
sorry, I forgot to mention, this is kamailio v4.3.1:
# kamailio -V
version: kamailio 4.3.1 (x86_64/linux) f38e67
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT,
USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST,
HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: f38e67
compiled on 18:15:23 Jul 20 2015 with gcc 4.4.7
On 21/07/2015 15:03, Asgaroth wrote:
Hi All,
I have a situation where I have 2 devices registering with the same
AOR, I have the registrar module's max_contacts parameter set to 1 and
I use the 0x04 flag on the save function.
When I use dmq_usrloc for replication, I can see 2 contacts registered
for the AOR on the "client" nodes whereas the node where the actual
registration took place only has 1 contact for the AOR.
Is this expected behaviour of the dmq_usrloc module in terms of
registration or have a come accross another bug?
Thanks