15 Jul
2024
15 Jul
'24
4:13 p.m.
Hey @sergey-safarov,
As this PR is concerned, each new kamailio instance creates it's own set of these 3
files/sockets in `/run/kamailio-{name}`, ie `/run/kamailio-dev/` has these 3 files.
Then one can issue rpc command with
`kamcmd -s /run/kamailio-dev/kamailio_ctl corex.debug 3`.
Also, modparams control this in each `kamailio-{name}.cfg` (unless I am misunderstanding
the params) such as
```
/* set the path to RPC fifo control file */
# modparam("jsonrpcs", "fifo_name",
"/run/kamailio/kamailio_rpc.fifo")
/* set the path to RPC unix socket control file */
# modparam("jsonrpcs", "dgram_socket",
"/run/kamailio/kamailio_rpc.sock")
# ----- ctl params -----
/* set the path to RPC unix socket control file */
# modparam("ctl", "binrpc",
"unix:/run/kamailio/kamailio_ctl")
```
`kamctl` and `kamctlrc` have some variables regarding these files/sockets like
```
## control engine: RPCFIFO
## - default RPCFIFO
# CTLENGINE="RPCFIFO"
## path to FIFO file for engine RPCFIFO
# RPCFIFOPATH="/run/kamailio/kamailio_rpc.fifo"
```
but not sure how to handle this for the template as kamctl can't take arguments I
think and we can't create a second `kamctlrc-dev` to pass it on.
Does this make sense in any way for your question?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3904#issuecomment-2228607281
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3904/c2228607281(a)github.com>