sr-dev June 2024

sr-dev@lists.kamailio.org

14 participants
225 discussions

[kamailio/kamailio] extented haproxy protocol support (PR #3731)
by sergey-safarov 12 Jul '24

12 Jul '24

#### Pre-Submission Checklist - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] Each component has a single commit (if not, squash them into one commit) - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist: - [ ] PR should be backported to stable branches - [x] Tested changes locally - [x] Related to issue #3667 #### Description Allow creating Record-Route and Via header using destination address and port in the haproxy protocol header. PR created behalf @ivanuschak You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3731 -- Commit Summary -- * core: extented haproxy protocol parser * rr: extented haproxy protocol suppport * path: extented haproxy protocol suppport * websocket: extented haproxy protocol suppport * siptrace: extented haproxy protocol suppport -- File Changes -- M src/core/forward.h (4) M src/core/msg_translator.c (137) M src/core/parser/msg_parser.h (1) M src/core/receive.c (6) M src/core/receive.h (3) M src/core/tcp_conn.h (1) M src/core/tcp_main.c (22) M src/core/tcp_read.c (20) M src/modules/path/path.c (2) M src/modules/rr/loose.c (4) M src/modules/rr/record.c (6) M src/modules/siptrace/siptrace.c (89) M src/modules/websocket/ws_frame.c (9) M src/modules/websocket/ws_handshake.c (3) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3731.patch https://github.com/kamailio/kamailio/pull/3731.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3731 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3731(a)github.com>

6 22

[kamailio/kamailio] WIP pkg: RPM packaging add kamailio-tls_wolfssl subpackage (PR #3592)
by space88man 09 Jul '24

09 Jul '24

5 27

[kamailio/kamailio] ims_registrar_pcscf,ims_qos: added a parameter for trusting the bottom Via header on requests (PR #3891)
by Dragos Vingarzan 08 Jul '24

08 Jul '24

#### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - Not yet - first let's see if the work is valid, then I'll recompose the whole work to satisfy this. Otherwise... if I need to fix something, it's too hard to work like this... - [ ] Each component has a single commit (if not, squash them into one commit) - ditto - [x] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Normally, the IMS P-CSCF should identify the clients (UEs) by the received IP address and ports on Rx. The current code is using a mix of that, plus using Contact and Via headers, with arguable potential security issues. This patch adds a new parameter to `ims_registrar_pcscf` and `ims_qos` modules, allowing for an optional outsource of the IPsec functionality to another element, which is also in charge of checking/enforcing correct UE Via header. The existing code is allowed to work as before, with the default value of the flag being towards that. List of functional changes: - `ims_qos` - added `trust_bottom_via` parameter - List of indirect changes: - default I-CSCF config example contained a questionable line which adds a `+` as a prefix in Request-URI. After way too much time wasted to figure out why the Diameter LIR has bogus SIP or TEL URI values in UserName AVP, I have discovered this. Seems like someone had just tel-URIs in their network, but otherwise the blind addition of this prefix makes no sense to me. - added a `str2ushort()` macro, since code was using some dangerous casting and macros with a larger type - List of non-functional fixes: - spelling in comments - comments at the end of line moved above the line they refer to; with just 80 columns code-formatting, commenting on the same line provides for some super weird and hard to read code, so IMHO should not be allowed (or ... much harder now... increase to 120 columns) - You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3891 -- Commit Summary -- * squashed work -- File Changes -- M misc/examples/ims/icscf/kamailio.cfg (4) M src/core/ut.h (36) M src/lib/ims/ims_getters.c (2) M src/modules/ims_icscf/location.c (10) M src/modules/ims_qos/ims_qos_mod.c (27) M src/modules/ims_qos/ims_qos_mod.h (1) M src/modules/ims_qos/rx_aar.h (4) M src/modules/ims_qos/rx_authdata.h (2) M src/modules/ims_qos/rx_avp.c (2) M src/modules/ims_qos/rx_avp.h (1) M src/modules/ims_registrar_pcscf/doc/ims_registrar_pcscf_admin.xml (39) M src/modules/ims_registrar_pcscf/ims_registrar_pcscf_mod.c (18) M src/modules/ims_registrar_pcscf/notify.c (2) M src/modules/ims_registrar_pcscf/save.c (78) M src/modules/ims_registrar_pcscf/service_routes.c (125) M src/modules/ims_registrar_pcscf/subscribe.c (75) M src/modules/ims_registrar_pcscf/subscribe.h (4) M src/modules/ims_usrloc_pcscf/udomain.c (4) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3891.patch https://github.com/kamailio/kamailio/pull/3891.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3891 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3891(a)github.com>

2 20

[kamailio/kamailio] performance regression related to new TCP connection tracking feature with a high number of connections (Issue #3759)
by Henning Westerholt 05 Jul '24

05 Jul '24

### Description On systems with a high number of TCP sessions there can be a significant performance regression observed, probably related to the newly added TCP connection tracking feature. ### Troubleshooting #### Reproduction No special configuration is necessary, just install the latest 5.7.x release, e.g. 5.7.3 on a production system with a lot of clients connected over TCP or TLS. You need to have a large number of clients connected to be able to observe the regression. For a high number of connections (e.g. more then 20.000 up to 30.000 connections) the Kamailio servers uses about 30% to 50% more CPU as with the old version. #### Debugging Data Two graphs were attached to this issue. The first shows the CPU load before (less load) and after the upgrade (increased load). The second is a flamegraph that shows that over 80% of the CPU time is spent in the newly added function tcp_connection_limit_srcip(). <img width="372" alt="cpu-load-before-after" src="https://github.com/kamailio/kamailio/assets/6481937/ec92c41b-25e2-4847-a4bc…"> ![flamegraph](https://github.com/kamailio/kamailio/assets/6481937/5c2e3982-2d5b-4acd-a774-bad8fa64bd0a) Most of the CPU time is spend in the TCP main process, as expected. #### Log Messages No special log messages could be observed. #### SIP Traffic ### Possible Solutions The TCP limit feature should probably be optimized to not cause such a large performance regression. It should be also possible to deactivate it completly and therefore getting a comparable performance as before the feature addition. ### Additional Information Kamailio 5.7.3 and probably also git master version. * **Operating System**: Debian 11, Debian 12 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3759 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3759(a)github.com>

2 6

[kamailio/kamailio] tcpops module event_route[tcp:closed] route block $conid is null (Issue #3767)
by liangbaolin 05 Jul '24

05 Jul '24

### Description During the process of using version 5.7.4 of Kamailio, I found that the $conid cannot be correctly obtained in the TCP: closed routing block of the TCP module event_route. I am certain that it is normal in version 5.4.8. ### Troubleshooting ``` pv [pv_core.c:2725]: pv_get_tcpconn_id() ``` #### Reproduction The test scenario initiated a register registration process for me, and after completing the disconnection of the TCP connection, triggered this event. #### Log Messages  ``` 2024-02-26T01:35:55.902002512Z 52(98) DEBUG: <core> [core/receive.c:635]: receive_msg(): cleaning up 2024-02-26T01:35:55.902034482Z 52(98) DEBUG: <core> [core/tcp_read.c:280]: tcp_read_data(): EOF on connection 0x7f99a1546a80 (state: 0, flags: c018) - FD 24, bytes 0, rd-flags 10000 ([12.0.1.6]:15821 -> [12.0.1.6]:5060)52(98) DEBUG: <core> [core/tcp_read.c:343]: tcp_read(): read 0 bytes: 2024-02-26T01:35:55.902051542Z 2024-02-26T01:35:55.902058282Z 52(98) DEBUG: <core> [core/tcp_read.c:1532]: tcp_read_req(): read= 0 bytes, parsed=0, state=0, error=1 2024-02-26T01:35:55.902063282Z 52(98) DEBUG: <core> [core/tcp_read.c:1534]: tcp_read_req(): last char=0x00, parsed msg= 2024-02-26T01:35:55.902069402Z 2024-02-26T01:35:55.902074032Z 52(98) DEBUG: <core> [core/tcp_read.c:1544]: tcp_read_req(): EOF 2024-02-26T01:35:55.902101372Z 52(98) DEBUG: <core> [core/io_wait.h:598]: io_watch_del(): DBG: io_watch_del (0x559e8a029740, 24, -1, 0x10) fd_no=2 called 2024-02-26T01:35:55.902153162Z 52(98) DEBUG: <core> [core/tcp_read.c:1927]: handle_io(): removing from list 0x7f99a1546a80 id 2 fd 24, state 2, flags c018, main fd 134, refcnt 2 ([12.0.1.6]:15821 -> [12.0.1.6]:5060) 2024-02-26T01:35:55.902168112Z 52(98) DEBUG: <core> [core/tcp_read.c:1702]: release_tcpconn(): releasing con 0x7f99a1546a80, state -1, fd=24, id=2 ([12.0.1.6]:15821 -> [12.0.1.6]:5060) 2024-02-26T01:35:55.902173372Z 52(98) DEBUG: <core> [core/tcp_read.c:1705]: release_tcpconn(): extra_data (nil) 2024-02-26T01:35:55.902208402Z 83(129) DEBUG: <core> [core/tcp_main.c:3747]: handle_tcp_child(): reader response= 7f99a1546a80, -1 from 1 2024-02-26T01:35:55.902224742Z 83(129) DEBUG: <core> [core/tcp_main.c:3904]: handle_tcp_child(): case CONN_EOF tcp_emit_closed_event before 5 2024-02-26T01:35:55.902229802Z 83(129) DEBUG: <core> [core/tcp_main.c:3671]: tcp_emit_closed_event(): TCP closed event creation triggered (reason: 0) 2024-02-26T01:35:55.902318572Z 83(129) DEBUG: tcpops [tcpops.c:311]: tcpops_handle_tcp_closed(): received TCP closed event 2024-02-26T01:35:55.902331352Z 83(129) DEBUG: tcpops [tcpops.c:261]: tcpops_tcp_closed_run_route(): event reason id: 0 rt: 1 2024-02-26T01:35:55.902335132Z 83(129) ERROR: tcpops [tcpops.c:278]: tcpops_tcp_closed_run_route(): run_top_route() before tev->id: 2 2024-02-26T01:35:55.902480972Z 83(129) DEBUG: <core> [core/tcp_main.c:1713]: _tcpconn_find(): 2 port 0 2024-02-26T01:35:55.902493872Z 83(129) DEBUG: pv [pv_core.c:2725]: pv_get_tcpconn_id(): no conid 2024-02-26T01:35:55.902498762Z 83(129) DEBUG: pv [pv_core.c:2726]: pv_get_tcpconn_id(): msg->rcv.proto_reserved1: 2 2024-02-26T01:35:55.902503592Z 83(129) DEBUG: <core> [core/tcp_main.c:1713]: _tcpconn_find(): 2 port 0 2024-02-26T01:35:55.902508262Z 83(129) DEBUG: <core> [core/pvapi.c:1418]: pv_printf_mode(): final buffer length 111 2024-02-26T01:35:55.902513422Z 83(129) ERROR: <script>: tcp connection closed conid: (<null>), tcp(conid): <null>, Ri: 12.0.1.185, Rp: 5060 , si: 12.0.1.6 , sp: 15821 2024-02-26T01:35:55.902607692Z 83(129) DEBUG: <core> [core/tcp_main.c:1713]: _tcpconn_find(): 2 port 0 2024-02-26T01:35:55.902625622Z 83(129) DEBUG: pv [pv_core.c:2725]: pv_get_tcpconn_id(): no conid 2024-02-26T01:35:55.902630672Z 83(129) DEBUG: pv [pv_core.c:2726]: pv_get_tcpconn_id(): msg->rcv.proto_reserved1: 2 2024-02-26T01:35:55.902635822Z 83(129) ERROR: tcpops [tcpops.c:280]: tcpops_tcp_closed_run_route(): run_top_route() after tev->id: 2 2024-02-26T01:35:58.777642759Z 41(87) DEBUG: ims_dialog [dlg_handlers.c:2026]: print_all_dlgs(): ********************41(87) DEBUG: ims_dialog [dlg_handlers.c:2027]: print_all_dlgs(): printing 65536 dialogs ``` #### SIP Traffic  ``` my test script block event_route[tcp:closed] { xlog("L_ERR", "$proto connection closed conid: ($conid), tcp(conid): $tcp(conid), Ri: $Ri, Rp: $Rp , si: $si , sp: $sp\n"); } file: src/modules/pv/pv_core.c int pv_get_tcpconn_id(struct sip_msg *msg, pv_param_t *param, pv_value_t *res) { ... if((con = tcpconn_get(msg->rcv.proto_reserved1, 0, 0, 0, 0)) == NULL) // return false { LM_DBG("no conid\n"); //additional custom log LM_DBG("msg->rcv.proto_reserved1: %d\n",msg->rcv.proto_reserved1); return pv_get_null(msg, param, res); } .... } file: src/core/tcp_main.c struct tcp_connection *tcpconn_lookup(int id, struct ip_addr *ip, int port, union sockaddr_union *local_addr, int try_local_port, ticks_t timeout) { ... if(unlikely(c == NULL)) { c = _tcpconn_find(id, ip, port, &local_ip, local_port); // retrun c == null } ... } struct tcp_connection *_tcpconn_find( int id, struct ip_addr *ip, int port, struct ip_addr *l_ip, int l_port) { ... if(likely(id)) { hash = tcp_id_hash(id); for(c = tcpconn_id_hash[hash]; c; c = c->id_next) { //tcpconn_id_hash find c is null #ifdef EXTRA_DEBUG LM_DBG("c=%p, c->id=%d, port=%d\n", c, c->id, c->rcv.src_port); print_ip("ip=", &c->rcv.src_ip, "\n"); #endif .... } inline static int tcpconn_try_unhash(struct tcp_connection *tcpconn) { ... _tcpconn_detach(tcpconn); //executed ... lock_release(&tcpconn->write_lock); ... } static inline void _tcpconn_detach(struct tcp_connection *c) { ... tcpconn_listrm(tcpconn_id_hash[c->id_hash], c, id_next, id_prev); //remove c ... } ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.7.4 (x86_64/linux) 9920d9-dirty flags: , EXTRA_DEBUGUSE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 9920d9 -dirty compiled on 09:59:52 Feb 26 2024 with gcc 7.5.0 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3767 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3767(a)github.com>

5 8

[kamailio/kamailio] secsipid method to only validate signature without checking the rest of the header (Issue #3784)
by Ben Kaufman 05 Jul '24

05 Jul '24

### Description Currently secsipid has a method to sign arbitrary (json) data (`secsipid_sign`), however it has no converse method to check the signature. Currently, an attempt to check a `div` signature for example will yield a `-303` error (`SIPHdrInfo`). Rather than trying to have full parsing for every possible type of Identity header (which are likely to increase in variety), it would be good to simply check "is this signature valid by trusted key", possibly validating the `iat` timestamp as well, but without any other opinions on the header values. ### Expected behavior A feature to check only the signature of an identity header. #### Actual observed behavior Currently the `secsipid_check_` family of functions fails for non- `shaken` passport types. #### Debugging Data The following DIV identity header was generated by secsipid's `secsipid_sign()` function, so it should be possible to reverse this to validate the signature: ``` Identity: eyJhbGciOiJFUzI1NiIsInBwdCI6ImRpdiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9kLm10c2VjLm1lL2QzYTkvQmZUeGJVTlozS1FMLnBlbSJ9.eyJkZXN0Ijp7InRuIjpbIjE2MTI1NTU0MzIxIl19LCJpYXQiOiIxNzEwMTY5MzQ1Iiwib3JpZyI6eyJ0biI6IjE1NTU3MzU5MzA5In0sImRpdiI6eyJ0biI6IjE5NTI1NTU5ODc2In19.-0QF6-u6zgAQNoAhdiETuhAu7FuRDzxmFch_cTdhcbeWvUZ60NQXxdPM-JucpOtFaEdn9wnFreAZ_6vZoc_Phg;info=<https://d.mtsec.me/d3a9/BfTxbUNZ3KQL.pem>;alg=ES256;ppt=div ``` ### Possible Solutions Because it's fairly straight forward to investigate the JWT, it's not necessary to try to account for every possible passport type, etc. The act of validating the signature is the complicated part, so a function that does only that would be convenient. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.7.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 12.2.0 ``` * **Operating System**: Currently alpine linux 3.19 in a docker container, but it should be pretty reproducible everywhere. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3784 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3784(a)github.com>

3 12

Initial Support for CMake in Kamailio - Feedback Needed!
by Xenofon Karamanos 04 Jul '24

04 Jul '24

Hello all, I've started working on integrating CMake as a build system for the Kamailio. This is an initial step towards potentially offering CMake as an alternative to the current build system across the entire Kamailio project. Right now, the CMake configuration is quite basic and covers only the core module. It offers limited options described in Makefile.defs that are required to build the core module. Some notes regarding the definitions can be found also in the CMakelists.notes<https://github.com/kamailio/kamailio/compare/master...cmake#diff-4e8ba0f2d5…> that made the build failed and maybe it's good to remove from current Makefiles as well, if i am not wrong. Before we consider extending it to other modules and components, i would like some feedback whether you find it useful at all. You can find the initial CMake files in the cmake branch. Please take a look and feel free to share any feedback or suggestions. Your input will be much appreciated and nessecary if we want CMake as a build system. For anyone wanting to try and compile using cmake, here are some basic instructions on how to get you started. Checkout the cmake branch of kamailio repo. Create a new folder, let's call it build. mkdir build && cd build Then run CMake for the configuration cmake .. (you can also then use ccmake . for a visual of the offered options) Build and install using make make -j4 make install OR Build and install using cmake cmake --build . cmake --install . You can of course use the CMake variable CMAKE_INSTALL_PREFIX to change the installation paths as follows and of course other preprocessor defintions: cmake -DCMAKE_INSTALL_PREFIX=./kamailio-cmake -DUSE_TCP=0 .. This will install it in the build/kamailio-cmake folder but fails to build because USE_TCP is required for kamailio to build (Check CMakelists.notes). Thank you all for your continuous contributions and support. Looking forward to hearing your thoughts and insights. Best regards, Xenofon https://github.com/kamailio/kamailio/tree/cmake [https://repository-images.githubusercontent.com/15101579/2d895000-e695-11e9…]<https://github.com/kamailio/kamailio/tree/cmake> GitHub - kamailio/kamailio at cmake<https://github.com/kamailio/kamailio/tree/cmake> Kamailio - The Open Source SIP Server for large VoIP and real-time communication platforms - - GitHub - kamailio/kamailio at cmake github.com

2 7

[kamailio/kamailio] usrloc: refactor some db queries using global usrloc_columns variable (PR #3888)
by Lucian Balaceanu 04 Jul '24

04 Jul '24

2 3

[kamailio/kamailio] Kamailio core dum v5.6 (Issue #3859)
by itpanda2024 04 Jul '24

04 Jul '24

we use Kamailio v5.6 and run cncxx module but when run cncxx function , it restart kamailio service and infor core dump -Log ; ay 28 10:08:30 KAM02 kamailio[45289]: 35(45289) ERROR: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: check : 2 35(45289) INFO: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: CDR Recording May 28 10:08:30 KAM02 kamailio[45289]: 35(45289) INFO: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: check source and dest : 0 va 0 May 28 10:08:30 KAM02 kamailio[45289]: 35(45289) INFO: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: thông tin nmp : May 28 10:08:30 KAM02 kamailio[45289]: 35(45289) INFO: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: vao 20 May 28 10:08:30 KAM02 kamailio[45289]: 35(45289) INFO: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: vao 3 May 28 10:08:30 KAM02 kamailio[45289]: 35(45289) ERROR: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: huong goi t1 giong t2 \n35(45289) ERROR: {1 83879051 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: cap nhạt update fail route May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: check : 1 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: telco id 1: 1 \n 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: payment_method: 1 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: IP telco 1: 1 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: credit_money : 10.000000 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: customer_id : htc May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: start_cost : 0.000 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: cps : 0 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: initial_p : 0 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: final_p : 0 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) INFO: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} app_perl [kamailioxs.xs:489]: XS_Kamailio_log(): >>> input: 10.000000, 0, <= May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) INFO: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} app_perl [kamailioxs.xs:489]: XS_Kamailio_log(): >>> return -1 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: check credit : -1 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: check cuoc realtime May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: IP telco 2: 1 May 28 10:08:30 KAM02 kamailio[45257]: 3(45257) ERROR: {1 83965494 INVITE 592b5ff7-9742-123d-7eb8-00505697ee23} <script>: cap nhạt update fail route May 28 10:08:35 KAM02 kamailio[45262]: 8(45262) ERROR: {1 83965494 ACK 592b5ff7-9742-123d-7eb8-00505697ee23} uac [replace.c:660]: restore_uri(): new URI [] shorter than old URI [sip:0868233455@125.212.210.235:65000] May 28 10:08:36 KAM02 kernel: traps: kamailio[45361] trap divide error ip:7f0ebbc39ec7 sp:7fffe1365020 error:0 in cnxcc.so[7f0ebbc39000+3c000] May 28 10:08:36 KAM02 systemd[1]: Started Process Core Dump (PID 46616/UID 0). May 28 10:08:37 KAM02 systemd-coredump[46617]: Process 45361 (kamailio) of user 982 dumped core.#012#012Stack trace of thread 45361:#012#0 0x00007f0ebbc39ec7 check_calls_by_money (cnxcc.so + 0x3ec7)#012#1 0x00000000006c5f2a fork_basic_timer (kamailio + 0x2c5f2a)#012#2 0x00007f0ebbc41a2c __child_init (cnxcc.so + 0xba2c)#012#3 0x0000000000636f94 init_mod_child (kamailio + 0x236f94)#012#4 0x0000000000636bde init_mod_child (kamailio + 0x236bde)#012#5 0x000000000063778f init_child (kamailio + 0x23778f)#012#6 0x000000000042f78d main_loop (kamailio + 0x2f78d)#012#7 0x000000000043995c main (kamailio + 0x3995c)#012#8 0x00007f0ec2629590 __libc_start_call_main (libc.so.6 + 0x29590)#012#9 0x00007f0ec2629640 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x29640)#012#10 0x000000000041dc35 _start (kamailio + 0x1dc35)#012ELF object binary architecture: AMD x86-64 May 28 10:08:37 KAM02 systemd[1]: systemd-coredump(a)4-46616-0.service: Deactivated successfully. May 28 10:08:37 KAM02 kamailio[45363]: 109(45363) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 115 May 28 10:08:37 KAM02 kamailio[45254]: 0(45254) ALERT: <core> [main.c:783]: handle_sigs(): child process 45361 exited by a signal 8 May 28 10:08:37 KAM02 kamailio[45254]: 0(45254) ALERT: <core> [main.c:787]: handle_sigs(): core was generated May 28 10:08:37 KAM02 kamailio[45254]: 0(45254) INFO: <core> [main.c:810]: handle_sigs(): terminating due to SIGCHLD May 28 10:08:37 KAM02 kamailio[45256]: 2(45256) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45259]: 5(45259) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45359]: 105(45359) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45260]: 6(45260) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45262]: 8(45262) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45264]: 10(45264) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45267]: 13(45267) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45357]: 103(45357) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45271]: 17(45271) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45273]: 19(45273) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45265]: 11(45265) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45263]: 9(45263) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45276]: 22(45276) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45353]: 99(45353) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45278]: 24(45278) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45281]: 27(45281) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45283]: 29(45283) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45269]: 15(45269) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45268]: 14(45268) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45362]: 108(45362) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45285]: 31(45285) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45288]: 34(45288) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45274]: 20(45274) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45272]: 18(45272) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45280]: 26(45280) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45275]: 21(45275) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45286]: 32(45286) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45352]: 98(45352) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45290]: 36(45290) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45294]: 40(45294) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45277]: 23(45277) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45296]: 42(45296) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45279]: 25(45279) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45299]: 45(45299) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45304]: 50(45304) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45257]: 3(45257) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45306]: 52(45306) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45282]: 28(45282) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45308]: 54(45308) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45300]: 46(45300) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45284]: 30(45284) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45302]: 48(45302) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45255]: 1(45255) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45287]: 33(45287) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45310]: 56(45310) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45315]: 61(45315) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45295]: 41(45295) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45258]: 4(45258) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45297]: 43(45297) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45301]: 47(45301) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45312]: 58(45312) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45314]: 60(45314) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45292]: 38(45292) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45303]: 49(45303) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45317]: 63(45317) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45305]: 51(45305) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45261]: 7(45261) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45360]: 106(45360) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45319]: 65(45319) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45321]: 67(45321) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45307]: 53(45307) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45323]: 69(45323) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45309]: 55(45309) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45289]: 35(45289) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45311]: 57(45311) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45348]: 94(45348) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45340]: 86(45340) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45313]: 59(45313) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45291]: 37(45291) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45316]: 62(45316) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45318]: 64(45318) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45293]: 39(45293) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45324]: 70(45324) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45270]: 16(45270) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45320]: 66(45320) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45266]: 12(45266) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45332]: 78(45332) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45326]: 72(45326) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45322]: 68(45322) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45356]: 102(45356) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45328]: 74(45328) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45330]: 76(45330) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45325]: 71(45325) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45327]: 73(45327) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45334]: 80(45334) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45329]: 75(45329) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45331]: 77(45331) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45336]: 82(45336) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45333]: 79(45333) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45335]: 81(45335) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45338]: 84(45338) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45342]: 88(45342) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45344]: 90(45344) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45346]: 92(45346) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45354]: 100(45354) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45339]: 85(45339) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45337]: 83(45337) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45351]: 97(45351) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45349]: 95(45349) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45341]: 87(45341) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45355]: 101(45355) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45343]: 89(45343) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45358]: 104(45358) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45350]: 96(45350) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45345]: 91(45345) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45347]: 93(45347) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45298]: 44(45298) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45363]: 109(45363) INFO: <core> [main.c:866]: sig_usr(): signal 15 received May 28 10:08:37 KAM02 kamailio[45254]: 0(45254) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized May 28 10:08:37 KAM02 systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILURE May 28 10:08:37 KAM02 systemd[1]: kamailio.service: Failed with result 'exit-code'. May 28 10:08:37 KAM02 systemd[1]: kamailio.service: Consumed 1.023s CPU time. May 28 10:08:37 KAM02 systemd[1]: kamailio.service: Scheduled restart job, restart counter is at 2. May 28 10:08:37 KAM02 systemd[1]: Stopped kamailio - the Open Source SIP Server. May 28 10:08:37 KAM02 systemd[1]: kamailio.service: Consumed 1.023s CPU time. May 28 10:08:37 KAM02 systemd[1]: Started kamailio - the Open Source SIP Server. May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: rtimer [rtimer_mod.c:299]: stm_t_param(): created rtimer name=cdr interval=300 mode=1 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [core/tcp_main.c:5105]: init_tcp(): using epoll_lt as the io watch method (auto detected) May 28 10:08:37 KAM02 kamailio[46624]: Listening on May 28 10:08:37 KAM02 kamailio[46624]: udp: 125.212.210.235:65000 May 28 10:08:37 KAM02 kamailio[46624]: udp: 172.16.172.245:65000 May 28 10:08:37 KAM02 kamailio[46624]: udp: 172.16.172.246:65000 May 28 10:08:37 KAM02 kamailio[46624]: Aliases: May 28 10:08:37 KAM02 kamailio[46624]: udp: KAM02:65000 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: http_client [http_client.c:316]: mod_init(): HTTP proxy port set to 0. Disabling HTTP proxy May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: regex [regex_mod.c:375]: load_pcres(): num groups = 4 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: regex [regex_mod.c:377]: load_pcres(): <group[0]>((^09[03]\d{7}$#015)|(^089\d{7}$#015)|(^07\d{8}$#015))</group[0]> (size = 45) May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: regex [regex_mod.c:377]: load_pcres(): <group[1]>((^09[6-8]\d{7}$#015)|(^086\d{7}$#015)|(^03\d{8}$#015))</group[1]> (size = 46) May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: regex [regex_mod.c:377]: load_pcres(): <group[2]>((^09[14]\d{7}$#015)|(^08[1-58]\d{7}$#015))</group[2]> (size = 37) May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: regex [regex_mod.c:377]: load_pcres(): <group[3]>((^02[48]\d{8}$#015)|(^842[48]\d{8}$))</group[3]> (size = 35) May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) WARNING: outbound [outbound_mod.c:117]: mod_init(): "stun" module is not loaded. STUN is required to use outbound with UDP. May 28 10:08:37 KAM02 kamailio[46624]: WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. May 28 10:08:37 KAM02 kamailio[46624]: WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. May 28 10:08:37 KAM02 kamailio[46624]: WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. May 28 10:08:37 KAM02 kamailio[46624]: WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: pike [pike.c:93]: pike_init(): PIKE - initializing May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: pike [ip_tree.c:79]: init_lock_set(): probing 256 set size May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: app_perl [app_perl_mod.c:210]: parser_init(): setting lib path: '/usr/local/lib64/kamailio/perl/' May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: app_perl [app_perl_mod.c:242]: parser_init(): successfully loaded perl file "/usr/local/etc/plugin/realtime-payment/scripts/aaa-script.pl" May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: app_perl [app_perl_mod.c:345]: mod_init(): perl interpreter has been initialized (1716865717.772062 => 1716865717.813451) May 28 10:08:37 KAM02 kamailio[46624]: WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: dispatcher [dispatch.c:407]: pack_dest(): uri without sip scheme - fixing it: 125.212.210.236:65000 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: dispatcher [dispatch.c:407]: pack_dest(): uri without sip scheme - fixing it: 125.212.210.237:65000 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: dispatcher [dispatch.c:407]: pack_dest(): uri without sip scheme - fixing it: 125.212.210.238:65000 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: dispatcher [dispatch.c:407]: pack_dest(): uri without sip scheme - fixing it: 172.16.172.244:65000 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: dispatcher [dispatch.c:407]: pack_dest(): uri without sip scheme - fixing it: 172.16.172.243:65000 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: dispatcher [dispatch.c:407]: pack_dest(): uri without sip scheme - fixing it: 172.16.172.242:65000 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: dispatcher [dispatch.c:407]: pack_dest(): uri without sip scheme - fixing it: 101.99.1.36:5060 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: cnxcc [cnxcc_mod.c:246]: __mod_init(): Loading cnxcc module May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: drouting [drouting.c:279]: dr_init(): DRouting - initializing May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [main.c:3150]: main(): processes (at least): 110 - shm size: 67108864 - pkg size: 8388608 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) WARNING: tm [tm.c:527]: fixup_routes(): t_on_failure("OUT_FAILURE"): empty/non existing route May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) WARNING: tm [tm.c:527]: fixup_routes(): t_on_failure("OUT_FAILURE"): empty/non existing route May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) WARNING: tm [tm.c:527]: fixup_routes(): t_on_failure("MS_IN_FAILURE"): empty/non existing route May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) WARNING: tm [tm.c:527]: fixup_routes(): t_on_failure("MS_IN_FAILURE"): empty/non existing route May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) WARNING: tm [tm.c:527]: fixup_routes(): t_on_failure("MS_IN_FAILURE"): empty/non existing route May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) WARNING: tm [tm.c:527]: fixup_routes(): t_on_failure("MS_OUT_FAILURE"): empty/non existing route May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 for fd 8 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 on fd 8 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 for fd 9 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 on fd 9 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [core/udp_server.c:163]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 for fd 10 May 28 10:08:37 KAM02 kamailio[46624]: 0(46624) INFO: <core> [core/udp_server.c:233]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 on fd 10 May 28 10:08:37 KAM02 kamailio[46625]: WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a f -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3859 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3859(a)github.com>

3 15

[kamailio/kamailio] db_redis: change logs on delete (PR #3892)
by Stefan Mititelu 03 Jul '24

03 Jul '24

3 8

← Newer
1
2
3
4
5
6
7
...
23
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2024