[SR-Users] Disable Dispatcher GW from DB
pwakano at gmail.com
Mon Mar 25 02:03:33 CET 2019
Hope you are all well!
I just saw a related situation regarding a disabled GW in dispatcher module.
In case I have a disabled GW the function ds_is_from_list() still matches
and returns true.
Is that expected? If so, maybe it could have an option to match only the
non-disabled GWs. Would that be reasonable?
On Wed, 6 Mar 2019 at 10:01, Patrick Wakano <pwakano at gmail.com> wrote:
> Thanks Dmitri!
> It worked like a charm!
> Patrick Wakano
> On Tue, 5 Mar. 2019, 18:42 Dmitri Savolainen, <savolainen at erinaco.ru>
>> hi Patrick
>> You may set flag=4 in "dispatcher" table for appropriate GW
>> On Tue, 5 Mar 2019 at 04:57, Patrick Wakano <pwakano at gmail.com> wrote:
>>> Hello list,
>>> Hope you are all doing well!
>>> I am looking for a way to disable a Dispatcher GW from the DB. I know I
>>> can disable it using the "kamcmd dispatcher.set_state d ..."command, but in
>>> case I do a reload or restart after that, the disabled GW will be back as
>>> Of course I could also delete the GW from DB, but for CDR purposes I
>>> want to keep the entry but mark as permanently disabled, so Kamailio won't
>>> try to use it nor ping it anymore. Does anyone how can I do that in the DB?
>>> I am looking for the exact same behavior the "kamcmd dispatcher.set_state
>>> d" does but from some change in the DB.
>>> Kind regards,
>>> Patrick Wakano
>>> Kamailio (SER) - Users Mailing List
>>> sr-users at lists.kamailio.org
>> Savolainen Dmitri
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sr-users