Dear all, Daniel
we have been testing this module with the following setup
kamailio 5.3.2
evapi params
modparam("evapi", "workers", 4)
modparam("evapi", "netstring_format", 0)
modparam("evapi", "bind_addr", "127.0.0.1:8448")
modparam("evapi", "max_clients", 32)
then in the configuration we do
hello Daniel
thanks, finally i could do that, i was struggling with this because in
kamailio 5.4 there was not being created a socket on the bindaddr param
when starting kamailio. (that's why i even tried to start to listen on a
regular tcp socket to connect there an application)
But in 5.5 and
Hello,
you must have a different socket in modparam("evapi", "bind_addr",
"...") than the core listen parameter for sip tcp traffic. The connect
with your evapi app to the socket specified in modparam.
Cheers,
Daniel
On 15.09.20 09:29, David Escartin wrote:
> hello Daniel
>
> i have tried the
hello Daniel
i have tried the directive
listen=127.0.0.1:8448 and listen=tcp:127.0.0.1:8448
and i tried now for example to connect with a tcp client from port 48583
(randomly selected when i made the tcp connect i guess)
tcp0 0 127.0.0.1:8448 127.0.0.1:48583
ESTABLISHED
Hello,
to what port do you connect for evapi?
The logs indicate connection to sip tcp port.
Cheers,
Daniel
On 14.09.20 18:06, David Escartin wrote:
> Dear all
>
> We are trying to use the evapi module to send some data to an external
> application but I'm having problems getting the clients
Dear all
We are trying to use the evapi module to send some data to an external
application but I'm having problems getting the clients connected.
I have the kamailio (version 5.3) running with a tcp socket 127.0.0.1:8228,
and the evapi params are just
modparam("evapi", "workers", 4)
