[OpenSIPS-Users] Help with my OpenSips architecture
vladp at opensips.org
Thu Aug 9 05:29:37 EDT 2018
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
startup. You probably did not set the "seed" flag for any of the nodes,
so the syncing process is unable to bootstrap correctly.
On 08/08/2018 09:55 PM, Dominic wrote:
> 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
> <http://10.0.20.163:5566> Enabled=1 Link_state=Up Next_hop=2
> # opensipsctl fifo clusterer_list_topology
> Cluster:: 1
> Node:: 1 Neighbours=2
> Node:: 2 Neighbours=1
> However it seems usrloc is not synced as seen in the state below:
> # opensipsctl fifo clusterer_list_cap
> Cluster:: 1
> Capability:: usrloc-contact-repl State=not synced
> However if I register 1 sip device on instance 1, I can see the device
> on both instances if I run "opensipsctl ul show". So it looks as
> though the usrloc is replicated properly so I wonder why "opensipsctl
> fifo clusterer_list_cap" has the "not synced" state.
> On Wed, Aug 8, 2018 at 8:00 AM, Dominic <wallnut.monkeys at gmail.com
> <mailto:wallnut.monkeys at gmail.com>> wrote:
> On Wed, Aug 8, 2018 at 4:52 AM, Bogdan-Andrei Iancu
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
> Hi Dominic,
> Please see inline.
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> OpenSIPS Bootcamp 2018
> On 08/07/2018 10:36 PM, Dominic wrote:
>> 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 asterisk servers directly facing the
>> public internet, with sip devices registering directly with a
>> specific asterisk.
>> So my first goal was to have the sip devices register
>> directly with OpenSips so I used the mid_registrar module for
>> that, and forward the registers to the right asterisk. This
>> seems to work very well so far.
>> Secondly, I setup rtp proxy, on the same box as opensips,
>> this also seems to work great so far. At this point I should
>> be able to not have the asterisk facing public internet.
> Do you intend to move the * boxes to a private network ? or to
> keep them with public IP, but behind a firewall ?
> Yes I indend to move them to a private network behind a firewall
> with no public IP.
>> The third thing I now want to do, and this is where I am
>> currently stuck is to figure out what my options are in terms
>> of high availability of the opensips. I figured I would go
>> with a VIP setup with 2 identical opensips box. So in this
>> type of setup i would have to replicate usrloc and dialogs
>> between the 2 opensips instances right? Am I forgetting anything?
> yes, you are on the right tracks - use the dialog replication
> (with a sharing tag) and usrloc full sharing mode - this will
> give you the HA you are looking for (in combination with a VIP)
> Perfect, I'll give that a shot
>> Am I on the right track with this type of setup or am I
>> missing something big here? It's also worth mentioning that I
>> am using OpenSIPS 2.4
>> Any advice/links with info on similar setup/code examples are
>> very welcome
> For the HA, see
>> Users mailing list
>> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
> Thanks a lot for the replies, the help is really appreciated
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users