Thanks Daniel, I’ll give that a try.

 

 

Hello,

We have some scripts that are setting values in an htable for various things, one of which is to disable options replies to take a system “out of service”.  We discovered today upon deploying 5.8.0 that the “htable.seti” command appears to be broken.

 

[root@ip-10-52-42-102 ~]# kamcmd htable.seti system_settings option_pings_off 1

error: 500 - Not enough parameters (htable name, key name and value)

 

however if we do htable.sets it works fine (although not an integer so it’s breaking our shutdown scripts).

 

[root@ip-10-52-42-102 ~]# kamcmd htable.sets system_settings option_pings_off 1

Ok. Key set to new value.

[root@ip-10-52-42-102 ~]#

 

I’ve looked through the commit history for htable and haven’t found anything that really stands out as a possible issue, so can the gurus please take a look?

the problem should be with kamcmd+ctl, not htable, use kamctl (or kamcli) instead:

kamctl rpc htable.seti system_settings option_pings_off 1

(kamcli rpc htable.seti system_settings option_pings_off 1)

I will look into kamcmd/ctl, likely is related to conversion of values, many fields are now long instead of int and kamcmd is not much maintained, it uses a custom (undocumented) binary-rpc protocol and none of its original developers is active.

Cheers,
Daniel

-- 

Daniel-Constantin Mierla (@ asipto.com)

twitter.com/miconda -- linkedin.com/in/miconda

Kamailio Consultancy, Training and Development Services -- asipto.com

Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com