I already read some of the articles from the links you provided, but answer
is still not straight forward. The relevant part states that "The new
dialog clustering support in OpenSIPS 2.4 is a complete one as it not only
takes care of dialog replication/sharing, but also of dialog handling in
terms of properly triggering dialog-specific actions."
But there is no information on how or "if" the module will  do call
representing / re-homing or restoring.


Hi Konrad!

Clustering OpenSIPS is some mix of:
- N OpenSIPS nodes
- N RTPEngine instances (I think you can use one, standalone,
on a different host than OpenSIPSes)
- at least 1 Redis, in case of >=2 RTPEngines, to share
RTP sessions
- some VRRP realisation, e.g. Keepalived or Pacemaker/Corosync.

OpenSIPSes share cluster-related critical data through BIN interface [1],
along with cluster-related options in some modules like usrloc [2],
dialog [3], tm [4]. Please find 'cluster' word on the documentation pages,
I hope this will give you answers on your questions.


Another kind of clustering is for horizontal scaling,
not redundancy/high-availability.
A good example is registrar server

And some more 

On Tue, Mar 5, 2019 at 11:38 PM Konrad Malewski <> wrote:

> Hello,
> We ware trying out clusterer module with opensips. We are having problems
> understanding what is the purpose of clustering when it comes to calls, so
> if anyone has some insights we would appreciate:
>     - if in active-backup mode active fails how backup is going to recover
> the call (with one of our tries nothing happened) ? Does clusterer module
> handles it ?
>     - does the behavior differ when it comes to tcp/udp ?
>     - how does opensips support call representing / re-homing or restoring
> ?
> thanks for any hint,
>    Konrad
Users mailing list

Reply via email to