Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow more options on dispatcher.set_state #2085

Closed
duarterocha91 opened this issue Oct 1, 2019 · 1 comment
Closed

Allow more options on dispatcher.set_state #2085

duarterocha91 opened this issue Oct 1, 2019 · 1 comment
Labels
feature-request

Comments

@duarterocha91
Copy link

Greetings,

Dispatcher RPC command allows to change the runtime state of a GW using its Group ID and the IP.

In my implementation i have 2 Kamailio machines in an HA setup and, as such, i have the GW configured twice with same group_id and different sockets (Different HA adressess - one for each machine).
I would like to be able to disable on runtime GWs that are configured with an HA adress that isn't present yet on that machine. To be able do that, the combination of GroupID + IP is not enough, but Socket + IP would be enough.

Is this possible to implement ?

Best Regards
miconda added a commit that referenced this issue May 22, 2020
@miconda
dispatcher: new rpc command dispatcher.set_duid_state
b7b0f25 
- set the state of a destination by matching on duid attribute
  kamctl rpc dispatcher.set_duid_state <state> <setid> <duid>
- example: kamctl rpc dispatcher.set_duid_state i 1 xyz
- GH #2085
@miconda
Copy link
Member

miconda commented May 22, 2020

Pushed a commit (referenced abive) with a new rpc command allowing to set the state by matching on duid attribute, which is intended to be sort of unique identifier per destination record.

@miconda miconda closed this as completed May 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@miconda @henningw @duarterocha91