Thanks a lot once again, that was the issue (flags=seed), here is the
output of the command now:
# opensipsctl fifo clusterer_list_cap
Cluster:: 1
Capability:: usrloc-contact-repl State=Ok
Dominic
On Thu, Aug 9, 2018 at 5:13 AM, John Quick
wrote:
> Hi Dominic,
>
> I have a similar setup
Hi Dominic,
The state listed by 'clusterer_list_cap' refers to the startup
synchronization mechanism. When you register a sip device on an
instance, that event is replicated on the spot to the other instances in
the cluster, but older registrations are only pulled from other nodes at
Hi Dominic,
I have a similar setup in a test rig. For comparison, here is the output I
get for the same fifo commands:
opensipsctl fifo clusterer_list
Cluster:: 1
Node:: 1 DB_ID=1 URL=bin:192.168.0.118:5678 Enabled=1 Link_state=Up
Next_hop=1 Description=vSvr2
opensipsctl fifo
There's something I'm not getting though, I defined my cluster with 2
opensips instances:
# opensipsctl fifo clusterer_list
Cluster:: 1
Node:: 2 DB_ID=-1 URL=bin:10.0.20.163:5566 Enabled=1 Link_state=Up
Next_hop=2 Description=none
# opensipsctl fifo clusterer_list_topology
Cluster:: 1
On Wed, Aug 8, 2018 at 4:52 AM, Bogdan-Andrei Iancu
wrote:
> Hi Dominic,
>
> Please see inline.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
> http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On
Hi Dominic,
Please see inline.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
http://opensips.org/training/OpenSIPS_Bootcamp_2018/
On 08/07/2018 10:36 PM, Dominic wrote:
Hi all, just to make sure I'm one the right
Hi all, just to make sure I'm one the right track here I'd like to share a
few thoughts of where I'm currently going with my architecture, any
feedback is really appreciated specially if it can help me avoid any
pitfalls in the future. Here is what I'm trying to do:
I currently have a a few
