Gotcha. I have a similar scenario. I use SQLops to set a gw status to 4
where it’s ATTRS is “whatever” and reload ds_reload()
That might work for you as well.
On Wed, 28 Aug 2019 at 16:36, Duarte Rocha wrote:
> > Why not just calling dispatcher.set_state directly to the kamailio? That
> would
> Why not just calling dispatcher.set_state directly to the kamailio? That
would only set the state in memory. Unless you do a reload.
Set_state works with gw uri and group as argument. In this scenario both
gws have the same uri and group and i only want to disable the one that has
a socket that
Why not just calling dispatcher.set_state directly to the kamailio? That
would only set the state in memory. Unless you do a reload.
On Wed, 28 Aug 2019 at 13:21, Duarte Rocha wrote:
> Yes, i only want to disable it on one Kamailio.
>
> A quarta, 28/08/2019, 11:32, Duarte Rocha
> escreveu:
>
>>
Yes, i only want to disable it on one Kamailio.
A quarta, 28/08/2019, 11:32, Duarte Rocha
escreveu:
> Greetings,
>
> I have two Kamailio's working on a HA scenario. Both Kamailio's have DB
> replication and each machine has one HA IP. In order to set this up, i have
> every GW on the DB duplicat
You want to disable it on only one kamailio, correct?
On Wed, 28 Aug 2019 at 12:34, Duarte Rocha wrote:
> Greetings,
>
> I have two Kamailio's working on a HA scenario. Both Kamailio's have DB
> replication and each machine has one HA IP. In order to set this up, i have
> every GW on the DB dupl
Greetings,
I have two Kamailio's working on a HA scenario. Both Kamailio's have DB
replication and each machine has one HA IP. In order to set this up, i have
every GW on the DB duplicated, one with Socket IPA and another with socket
IPB.
I have both GWs in a active state configurated in the repl
