Razvan,
I am curious about this. I can see how you can use the ratelimit module to
reject calls based on calls per second, or any configured window, but Mehdi was
asking about reporting it as a statistic. I can't see any way to get the value
out of the ratelimit module for use elsewhere; it
Hi Vlad,
Thanks for the clarification.
OK - that makes sense.
I suppose this processed_dialogs value incrementing on the standby node is
a good indicator that clustering and dialog syncing is working as expected.
Thank you.
On Mon, 21 Oct 2019 at 13:30, Vlad Patrascu wrote:
> The term
The term "processed" should be read more generically in this context to
include to act of receiving the replicated dialog and preparing it to
become active at any time.
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com
On 10/21/2019 02:57 PM, solarmon wrote:
Hi Vlad,
That
Hi Vlad,
That was my understanding too, but why would processed_dialogs be
incrementing on the standby (State=0) node?
On Mon, 21 Oct 2019 at 12:51, Vlad Patrascu wrote:
> Hi solarmon,
>
> 'failed_dialogs' and 'processed_dialogs' represent the total number of
> failed/processed dialogs on
Hi solarmon,
'failed_dialogs' and 'processed_dialogs' represent the total number of
failed/processed dialogs on that OpenSIPS instance since startup. If one
of the nodes has been running and handling traffic for a longer time,
it's normal for the stats to be different. On the other hand
Alexey,
Sorry, I'm a bit confused with your answer, and why you are using this
thread to ask another question!
I'm just trying to understand whether these statistics figures should be
synced or not, and why they would be different between the two clustered
openSIPS servers (clustered using
Hi, solarmon
no, there’s no need to sync dialogs. It’s another type of cluster.
As for now, the main purpose is just to have a common
user location dataset, when OpenSIPS nodes will know
the location of each registered device. If it’s connected locally,
it will serve the call locally. If the
Hi,
Are dialogs stats meant to be totally synced between to openSIPS nodes in a
cluster - i.e. when using clusterer?
I am monitoring/graphing the active_dialogs, failed_dialogs and
processed_dialogs for each node, using 'opensipsctl fifo get_statistics'
and they are not fully synced:
*Node 1:*
Hi list
I’m trying to find the best solution for setting
federated user location cluster.
Key notes:
- geographically distributed OpenSIPS nodes
- the same numbering plan for all devices (no strict
ranges for Europe/Asia and so on)
- ability to be in service (at least inside of each node)
in
