Victor Seva comments

Results 105 comments of


                                            Victor Seva

Fixable/transient failures during node install require reprovisioning

In recent versions of sidero it's working as expected. @magicite time to close this one?

Failed to delete FD from epoll, errno = 1 (Operation not permitted)

Same error for me using 3.6.0 and 3.6.1 ``sipp -max_socket 5000 -t u1 -inf callee.csv -inf caller.csv -sf sipp_scenario00.xml -i 127.126.0.1 -p 51602 -nr -nd -m 1 -mp 45003 -timeout...

Failed to delete FD from epoll, errno = 1 (Operation not permitted)

Same thing ``` cat log/scenarios/invite/sipp_scenario_responder00_3799_errors.log ; sipp -v The following events occurred: 2021-01-15 15:30:46.070359 1610721046.070359: Failed to delete FD from epoll, errno = 1 (Operation not permitted) SIPp v3.7.x-SCTP-PCAP-RTPSTREAM-RTPCHECK. ```

Failed to delete FD from epoll, errno = 1 (Operation not permitted)

tested same scenario with 3.5.3, no error

Failed to delete FD from epoll, errno = 1 (Operation not permitted)

Attached strace output of 3.6.1 [sipp_strace.log](https://github.com/SIPp/sipp/files/6090062/sipp_strace.log) [sipp_strace_resp.log](https://github.com/SIPp/sipp/files/6090063/sipp_strace_resp.log) and 3.5.3 + https://github.com/lemenkov/sipp/commit/0bdf831a1bdf337bc60f54ada1c5efa3983333af + https://github.com/lemenkov/sipp/commit/37bff83a6c8083aa7b797ebb97d41f149a37af56 (needed to build it on bullseye) [sipp_3.5.3_strace.log](https://github.com/SIPp/sipp/files/6090065/sipp_3.5.3_strace.log) [sipp_3.5.3_strace_resp.log](https://github.com/SIPp/sipp/files/6090066/sipp_3.5.3_strace_resp.log)

[Bug]: frontend is without any css styling: "Could not find specified theme"

same here. Workaround worked for me too.

mismatching of library

Install the proper version built for your distribution.

Kamailio 5.6 (and 5.7) core dumps with uac_req_send() from uac module

There are dbgsym packages available in the repo

Dialog DMQ sync: Timer needs fixing, firing on wrong node!

@hb9eue did you test the proposed fix?

extented haproxy protocol support

I was thinking. Could we have something generic that abstracts the rcv parameter of the message?