Hi Alexey,
I see the "dr_enable_probing" MI command; that's great! Is there an
equivalent modparam I can add to default to 0, so that it will only probe
when we know it has the IP (when enabled by MI)?
It will be some time until I'm able to cherry-pick and test. The two
proxies are currently
Hello Liviu!
And first of all thank you for your detailed explanation.
Now I completely understand the approach was taken when developing this
feature of Clusterer.
And this looks logical to me. It gives less chances to make a human error.
What I did for now, is a clustering super-structure
Hi Jeff.
I made one solution for 2.4. You can cherry-pick
https://github.com/OpenSIPS/opensips/commit/05ca54a37d82c605e2cd6d10e5a62fb4f7c35b78
And may be this:
https://github.com/OpenSIPS/opensips/commit/94a3ede1e276984a91f93f6ece832d174b071ab8
There is documentation in commits.
-
---
Hello Team,
I have a problem with TOPOLOGY HIDING and NAT issues while using forwarding
on busy/no-answer. I fix the NATed contact and then create dialog with
topology hiding. The UPSTREAM (callee to caller) BYE relays to private IP
instead of public. All the previous requests relay after fixing
On 09.04.2020 15:03, Donat Zenichev wrote:
I have question and it's almost theoretic.
The question relates to Clusterer module and its behavior.
Will Clusterer module solve this contradiction on its own?
And if so, to which side the precedence is given?
The other way around could be to
