sr-users

sr-users@lists.kamailio.org

35 participants
37509 discussions

SIPtrace store database failed
by 17603019528＠163.com 01 Apr '25

01 Apr '25

Hello, I want to store the siptrace dialog in the database，but it gives an error. Is the configuration method incorrect? Kamailio version: ``` version: kamailio 5.8.5 (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_SEND_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: compiled on 11:51:23 Mar 31 2025 with gcc 4.8.5 ``` here is the log: ####### 8(3550) DEBUG: <core> [core/udp_server.c:731]: udp_rcv_loop(): probing packet received from 172.16.80.3 7935 2(3539) DEBUG: <core> [core/udp_server.c:708]: udp_rcv_loop(): received on udp socket: (106/100/956) [[INVITE sip:1002@172.16.4.113:5460 SIP/2.0 0D 0A Via: SIP/2.0/UDP 172.16.80.3:8798;branch=z9hG4bK-d87543-4]] 2(3539) DEBUG: <core> [core/receive.c:190]: ksr_evrt_received(): event route core:msg-received not defined 2(3539) DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1 2(3539) DEBUG: <core> [core/parser/msg_parser.c:722]: parse_msg(): SIP Request: 2(3539) DEBUG: <core> [core/parser/msg_parser.c:724]: parse_msg(): method: <INVITE> 2(3539) DEBUG: <core> [core/parser/msg_parser.c:726]: parse_msg(): uri: <sip:1002@172.16.4.113:5460> 2(3539) DEBUG: <core> [core/parser/msg_parser.c:728]: parse_msg(): version: <SIP/2.0> 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Via] type 1 2(3539) DEBUG: <core> [core/parser/parse_via.c:1312]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d87543-4f7e02083f709d16-1--d87543->; state=6 2(3539) DEBUG: <core> [core/parser/parse_via.c:1312]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 2(3539) DEBUG: <core> [core/parser/parse_via.c:2663]: parse_via(): end of header reached, state=5 2(3539) DEBUG: <core> [core/parser/msg_parser.c:592]: parse_headers(): Via found, flags=2 2(3539) DEBUG: <core> [core/parser/msg_parser.c:594]: parse_headers(): this is the first via 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Contact] type 7 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [To] type 3 2(3539) DEBUG: <core> [core/parser/parse_addr_spec.c:904]: parse_addr_spec(): end of header reached, state=10 2(3539) DEBUG: <core> [core/parser/msg_parser.c:173]: get_hdr_field(): <To> [36]; uri=[sip:1002@172.16.4.113:5460] 2(3539) DEBUG: <core> [core/parser/msg_parser.c:176]: get_hdr_field(): to body (36)["1002"<sip:1002@172.16.4.113:5460> ], to tag (0)[] 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [From] type 4 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Call-ID] type 6 2(3539) DEBUG: <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [CSeq] type 5 2(3539) DEBUG: <core> [core/parser/msg_parser.c:154]: get_hdr_field(): cseq <CSeq>: <1> <INVITE> 2(3539) DEBUG: <core> [core/receive.c:397]: receive_msg(): --- received sip message - request - call-id: [NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.] - cseq: [1 INVITE] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/receive.c:263]: ksr_evrt_pre_routing(): event route core:pre-routing not defined 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/receive.c:474]: receive_msg(): preparing to run routing scripts... 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=596 a=26 n=xlog 2(3539) INFO: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <script>: 172.16.80.3:8798|172.16.4.113:5460|udp|INVITE 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=605 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=707 a=67 n=set_rpl_no_connect 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=710 a=55 n=force_rport 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=735 a=16 n=if 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Allow] type 21 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Content-Type] type 11 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [User-Agent] type 28 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=740 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=735 a=25 n=mf_process_maxfwd_header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=745 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=740 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=749 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[REQINIT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=745 a=26 n=sanity_check 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:254]: check_ruri_sip_version(): check_ruri_sip_version entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:278]: check_ruri_sip_version(): check_ruri_sip_version passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:286]: check_ruri_scheme(): check_ruri_scheme entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:305]: check_ruri_scheme(): check_ruri_scheme passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:327]: check_required_headers(): check_required_headers entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_hname2.c:316]: parse_sip_header_name(): parsed header name [Content-Length] type 12 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/msg_parser.c:187]: get_hdr_field(): content_length=417 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:350]: check_required_headers(): check_required_headers passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:358]: check_via1_header(): check via1 header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:519]: check_cseq_method(): check_cseq_method entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:553]: check_cseq_method(): check_cseq_method passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:563]: check_cseq_value(): check_cseq_value entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:591]: check_cseq_value(): check_cseq_value passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:601]: check_cl(): check_cl entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:626]: check_cl(): check_cl passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:643]: check_expires_value(): check_expires_value entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:679]: check_expires_value(): no expires header found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:776]: check_parse_uris(): check_parse_uris entered 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:780]: check_parse_uris(): parsing ruri 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:793]: check_parse_uris(): looking up From header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=122cd223 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/parser/parse_addr_spec.c:904]: parse_addr_spec(): end of header reached, state=29 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:808]: check_parse_uris(): looking up To header 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity.c:858]: check_parse_uris(): check_parse_uris passed 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| sanity [sanity_mod.c:252]: w_sanity_check(): sanity checks result: 1 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=608 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=962 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=950 a=25 n=nat_uac_test 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[NATDETECT] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=962 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=615 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=623 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=615 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=632 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=623 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=628 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=624 a=24 n=t_precheck_trans 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=628 a=24 n=t_check_trans 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:1578]: t_check_msg(): msg (0x7ff0858855f0) id=1/3539 global id=0/0 T start=0xffffffffffffffff 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:793]: t_lookup_request(): start searching: hash=30439, isACK=0 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:512]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-d87543-4f7e02083f709d16-1--d87543-] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:993]: t_lookup_request(): no transaction found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| tm [t_lookup.c:1650]: t_check_msg(): msg (0x7ff0858855f0) id=1/3539 global id=1/3539 T end=(nil) 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=632 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=757 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=753 a=24 n=has_totag 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siputils [checks.c:122]: has_totag(): no totag 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[WITHINDLG] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=753 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=637 a=5 n=route 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[AUTH] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=944 a=16 n=if 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/socket_info.c:742]: grep_sock_info(): checking if host==us: 12==12 && [172.16.4.113] == [172.16.4.113] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/socket_info.c:745]: grep_sock_info(): checking if port 5460 (advertise 0) matches port 5460 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [core/forward.c:446]: check_self(): host (0:172.16.4.113:5460) == me 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[AUTH] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=944 a=2 n=return 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=641 a=25 n=remove_hf 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=647 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=642 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=644 a=24 n=record_route 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| rr [record.c:490]: record_route(): inserted record route (r2: 1 - plen: 0) 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=645 a=24 n=dlg_manage 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:907]: internal_get_dlg(): no dialog callid='NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.' found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:975]: dlg_search(): dialog with callid='NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.' not found 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:478]: build_new_dlg(): new dialog on hash 1712 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:275]: populate_leg_info(): leg(0) route_set [], contact [sip:1003@172.16.80.3:8798], cseq [1] and bind_addr [udp:172.16.4.113:5460] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1040]: link_dlg(): linking dialog [1712:1302] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1049]: link_dlg(): ref dlg 0x7ff07ff56f10 with 1 -> 1 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:698]: get_dlg_timeout(): using default timeout 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_cb.c:227]: run_create_callbacks(): dialog=0x7ff07ff56f10 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:2128]: trace_dialog(): Spiraled dialog! 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:2150]: trace_dialog(): trace_info xavp not registered! Probably incoming E2E CANCEL! 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_profile.c:541]: set_current_dialog(): setting current dialog [1712:1302] 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:780]: dlg_lookup_mode(): ref dlg 0x7ff07ff56f10 with 1 -> 2 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:784]: dlg_lookup_mode(): dialog id=1302 found on entry 1712 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_handlers.c:1927]: dlg_manage(): dialog created before transaction 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1088]: dlg_unref_helper(): unref op on 0x7ff07ff56f10 with 1 from dlg_hash.c:1106 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| dialog [dlg_hash.c:1092]: dlg_unref_helper(): unref dlg 0x7ff07ff56f10 with 1 -> 1 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=658 a=16 n=if 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=647 a=25 n=is_method 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=648 a=25 n=sip_trace_mode 2(3539) BUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:1917]: trace_add_info_xavp(): URI should be in raw format here 2(3539) ERROR: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:1028]: sip_trace_helper(): failed to serialize siptrace info! Won't trace dialog! 2(3539) exec: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/usr/local/bin/../etc/kamailio/conf/kamailio.cfg] l=649 a=24 n=sip_trace 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| siptrace [siptrace.c:618]: sip_trace_insert_db(): storing info - no user 2(3539) DEBUG: |25-04-01 17:09:51|NWM3ODYyYWFhMDllZWYzMmI0NTMxYjZmMmI0M2Y1NjY.| <core> [db_query.c:72]: db_do_submit_query(): submitted query: insert into ###### here is my kamailio.cfg: ``` loadmodule "siptrace.so" modparam("siptrace", "db_url", DBURL) modparam("siptrace", "traced_user_avp", "$avp(user)") modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_init_mode", 0) ... route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE|REFER")) { record_route(); dlg_manage(); } if (is_method("INVITE")) { sip_trace_mode("d"); sip_trace(); } ```

1 0

New direction for Kamailio under Russian military administration
by Alex Balashov 01 Apr '25

01 Apr '25

For immediate release: BERLIN, Germany (1 April 2025)--The newly appointed executive and political head of the Russian Military Administration of Kamailio (R-MAK), General Alexander Balashov, has issued a proclamation: diversity, equity and inclusion (DEI) initiatives in the Kamailio will be fiscally de-emphasised, 'woke' modules will be removed in future releases, and realist relations with other open-source projects and commercial stakeholders will be sought, based henceforth on the 'pragmatics' of relative strength and strategic advantage, calculated from the extrapolated monetary value of Github commits. To note, the Kamailio project came into the remit of Balashov and R-MAK following the dissolution of the post-war transatlantic alliance system and the capitulation of NATO in the first quarter of 2025. These events were followed by direct negotiations between US Vice President J.D. Vance and the Government of the Russian Federation on the future course of Kamailio and SIP real-time communications, in which it was quickly concluded by both parties that Kamailio fell into the Russian sphere of influence. In an interview with Balashov, our bright and patriotic staff here at 'Krasnaya Zvezda' pressed him to further articulate and clarify the 'new thinking', as the new R-MAK initiatives have been informally dubbed around the offices of Kamailio. What follows is a selection of his remarks. Our first question to Balashov was on the tip of many journalists' tongues: what are the most woke modules in Kamailio? 'How should I know? They are everywhere, lots of people sayink it', Balashov answered, gesturing airily at the ceiling. 'Our specialists lookink on case-by-the-case basis. But sometimes is obvious, for example the JavaScript modules, like app_jsdt. This is clearly to subsidise a certain kind of morally deficient person.' What kind of person? we inquired, to be met with a characteristic frosty reply: 'You know the kind.' Our next question concerned some confusion about where, exactly, DEI initiatives are found in Kamailio today: 'From what I know this? Like swamp, this source code. How to say it, "drainink?" Yes, yes, I want to do that with swamp. Zero-based budget approach. Do you know it?' Asked to clarify, Balashov added: 'It's new idea from good friend Elon and the very efficient Dozh. Is good. We remove all module, then we look: what is broken? For example from technical viewpoint or political? What is broken? Maybe nothing.' One could be forgiven for wondering what 'broken' means in this context. We asked Balashov: does it mean CI tests no longer passing? 'No, no, no, automated tests are vegan soy-boy agenda. If you automatically test, when will you ever write correct code? I will not, I know automatic test will catch. Lazy approach. This idea, "test test test", for small minds. Do you know history of CI/CD? Propaganda is that Americans came up with it, but did not. Is invented by people from countries of later-times accession to EU, they are be-ne-fi-ci-aries of Bruxelle redistributionink policy, social cohesions grants and regional economic development equalisation initiatives, like something from socialist bloc countries or maybe Mezzogiorno, without otherwise much work prospects, until suddenly: unemployed guy with idea! "I am now Directeur of Le Cloud DevOps!" What is DevOps? It is from nothing, but suddenly hearing this in cultured places, theatres, palaces, galleries. Where it comes from? Why nobody asks? This is the old political correctness, and now we must release this suffocation with fresh and original thinking.' When our team asked for a concrete example of R-MAK's zero-based module trimming process, Balashov did not hesitate to focus on a well-known preoccupation: 'The most obvious example of very much not-needed module is TM. I Snapchat good friend Elon and I say him, "is it needed?" He says "no". But maybe I don't trust, GRU say he is always with marijuana, likewise ketamine. I make FaceTime with Milei: "¿Vos querés TM?" He says, "¡Que se vaya a la mierda y también los izquierdistas!" I phone Donald, "what do you think about this TM?" He says, "I signed a tremendous executive order to ban it this morning". I bother Orban in the middle of the night: "I am awake, asking myself, asking my wife: who needs TM?", and he answers: "no man who is civilisationally compatible with European values". Now I go to public sector union subreddits and askink same, and there is much noise and raging and I lose the karma, downvote to negative 26. I WhatsApp the leftists and they squeal. I Microsoft Teams to Bill Clinton and he says "TM is a key component of the international Kamailio order, used in 95% of configurations worldwide". Great! The answer is more clear than Lake Baikal: TM, goodbye, and I never knew you!' What else is marked for deletion?, wondered a contributing staff writer. On this point, Balashov was coy, declining to reveal the full working draft of slated cuts. However, he was not wholly unwilling to preview the direction of travel for the fate of Kamailio's 250+ modules. 'The STIR-SHAKING stuff of course gone. Now you can saying again "master-slave replication", as nature wills, without guilt, for which to be forced to this fake apologetics, "primary-secondary replication". Cannot anymore "blacklist"? What this emotionally constipated style? And likewise freedom means free to make telemarket without performative rituals of atonement for the sins.' Balashov went on to cite President Donald Trump, who had remarked: 'Robocall mitigations are money grab by failing FCC and their Trump-hating Democrat croneys. People are saying they are issuing eighth report and order, they are believing the fake liberal news. It's going to stop, and it's going to stop right now.' Balashov also intimated that he did not hold dearly in his heart the 'carrierroute' module, which he linked, in the memorable words of Fox News' Laura Ingraham, to 'the chattering vaccinated classes': 'What gigahertz your immunology system vibrates at? Mine for example clean, not 5G.' Next, we posed a question from a reader: are these changes to Kamailio simply drafting in the slipstream of global realignment, anti-free trade momentum, backlash against progressive cultural totems, as well as, in the United States specifically, the inward turn, the withdrawal from internationalism, and the return to 19th century great power realism in international relations, under the new administration of Donald Trump? 'Da, sure, of course gettink along with fraternal peoples very important, but also some important difference from Anglo-Americans. In R-MAK we are constructing "reaction with European characteristics" and the goals are too broader, coalitions bigger.' For help in understanding where R-MAK's reimagined Kamailio stakes its claim in the shifting international order and in the contested claims of popular mandates and political legitimacy, we consulted the version control history. Our GitHub research broadly supports Balashov's taxonomy of the exceptional ways in which the new thinking in Kamailio caters to a larger variety of constituencies, beyond those of its more monolithic relative, MAGA, across the Atlantic. In addition to patches from a predictable crowd of well-known Eurosceptics and critics of the post-Cold War Western security architecture, the R-MAK branch of Kamailio has many commits from supporters of renewed and muscular state-guided moral interventionism. In particular, large diffs, likely bundles of commits squashed interactive rebasing, appear to come from Catholic corporatists of southern Europe. Static code analysis also revealed a distinctive trail of gremialist design patterns and algorithms in the coding style of Jaime Guzmán. While it can be arduous to interpret this braiding of intellectual influences into bottom-line policymaking, we asked Balashov if this was the broader coalition, or the ideological imprimatur of 'reaction with European characteristics', to which he alluded. 'Sure, okay, because leadink open-source project is for what, if user is the amoral agent, captaining only the flatulent steam-ship of his hedonism? Time has ended to be saying, "do whatever you want as long as GPL-compliant", "you are free to fork if you wish", "submit the PR of your dreams". Look at yourself! This is nihilism. It is like, as Americans say, "self-licking ice cream cone", da? If you look into repository clone long enough, it in turn look back into you, and what it sees? Kamailio is not enough just for clone; it must make you better man!' Added Balashov, emphatically: 'If open-source project regime is to matter, it must be PEDAGOGICAL!' Turning to questions of relations with neighbours, Balashov rather foreseeably merged into the flow of renovated international relations realism and the spirit of great power competition once again jostling the world. We asked Balashov if the new thinking in Kamailio implies an abandonment of prior global hegemonic claims vis-a-vis OpenSIPS: 'Who is abandonink? But we must live in peace. We have no quarrels with OpenSIPS if they want Bucharest or Amsterdam. For them they are havink their interests, and we are havink our too.' Notably, and somewhat surprisingly, however, Balashov added: 'But we are going to get Yate. It is historically correct. I take away no options from the table.' Lastly, we asked Balashov to touch on the delicate subject of IMS and 6G enthusiasts increasingly migrating into the ecology of Kamailio, and whether this has a place in the current of new thinking under R-MAK. 'I not know much about them. Many people sayink they are eating dogs, eating cats, right from the street in Berlin. What to say about such people?' -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

1 0

DMQ read message too large
by Calvin E. 31 Mar '25

31 Mar '25

We are seeing errors like this when synchronizing htables over DMQ: ERROR: <core> [core/udp_server.c:677]: udp_rcv_loop(): read message too large: 60793 We have no issues with other UDP fragments caused by STIR/SHAKEN headers. Our socket buffers are sufficiently large (SO_RCVBUF is initially 26214400). Does DMQ have a receive message size limit less than what it can send? Is DMQ intended for htables under a certain total size? We tried to configure DMQ to use a TCP listener with ;transport=tcp on the notification and server address, but the DMQ traffic was still sent as UDP. The example in the documentation shows TLS, but we haven't tried that. -Calvin E.

2 3

Intermediate CDRs
by Sergio Charrua 31 Mar '25

31 Mar '25

Hi all! I have been googling, and reading documentation, but I could not find any solution. How can I implement intermediate CDRs with Kamailio ACC module (or any other module) ? For example, on long duration calls, I 'm required to save call status on a CDR, resulting in intermediate CDR lines for the call (which will result in multiple CDR lines per long duration calls). Any clue on how to implement this? Did anyone achieved that with Kamailio ACC module? Atenciosamente / Kind Regards / Cordialement / Un saludo, *Sérgio Charrua*

4 3

Multiple code modules
by David Cunningham 28 Mar '25

28 Mar '25

Hello, We have a requirement to load two code modules for use by kamailio.cfg, the reason being that we can't (won't, for business reasons) modify the first module and so need to add a second for our own code. Ideally we would load two Perl modules instead of the single module that's currently loaded like this: modparam( "app_perl", "filename", "/path/to/our/custom/Kamailio.pm" ) But I'm not sure how to load two modules like this. Otherwise, does anyone know if it's safe to load both a Perl module and a Python module? Then we could at least implement both required parts, one in Perl and one in Python. Thanks in advance for any help. -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

1 0

[ratelimit module] doubts about behavior
by juliofabian6385＠hotmail.es 26 Mar '25

26 Mar '25

I am reading https://kamailio.org/docs/modules/devel/modules/ratelimit.html and I want Kamailio, before an avalanche of calls (INVITE), to start discarding calls that exceed a threshold in 1 second, for example. So in summary I have prepared the module as follows: loadmodule "ratelimit.so" modparam("ratelimit", "timer_interval",1) modparam("ratelimit", "pipe", "1:TAILDROP:10") request_route { . . if (is_method("INVITE")) { if (!rl_check_pipe("1")) { sl_send_reply("503","Limiting"); exit; } } . . } As I understand from the documentation, this gives me a counter (one per INVITE) equal to 10, which resets after 1 second. In other words, if I receive 30 INVITES in 1 second, it will discard 20. From here, I have two questions between what I understand and what I see in the logs. FIRST QUESTION: I've made several SIPP calls in one second. I've run several tests, and the first reset of the counter always happens approximately timer_interval/2. From then on, the counter resets exactly every timer_interval. Am I doing something wrong? ########## RUNNING LOGS ########## 2025-03-26T18:59:20.509696381Z 0(1) DEBUG: <core> [core/cfg.y:2165]: yyparse(): loading module ratelimit.so 2025-03-26T18:59:20.509698675Z 0(1) DEBUG: <core> [core/sr_module.c:533]: ksr_locate_module(): found module to load </usr/lib/kamailio/modules/ratelimit.so> 2025-03-26T18:59:20.509702249Z 0(1) DEBUG: <core> [core/sr_module.c:587]: ksr_load_module(): trying to load </usr/lib/kamailio/modules/ratelimit.so> 2025-03-26T18:59:20.509704682Z 0(1) DEBUG: <core> [core/kemi.c:3463]: sr_kemi_modules_add(): adding module: ratelimit 2025-03-26T18:59:20.509707031Z 0(1) DEBUG: <core> [core/cfg.lex:2095]: pp_define(): defining id: MOD_ratelimit 2025-03-26T18:59:20.509815384Z 0(1) DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'ratelimit' matches module 'ratelimit' 2025-03-26T18:59:20.509817770Z 0(1) DEBUG: <core> [core/sr_module.c:850]: find_param_export(): found <timer_interval> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509820319Z 0(1) DEBUG: <core> [core/modparam.c:135]: set_mod_param_regex(): found <timer_interval> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509822755Z 0(1) DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'ratelimit' matches module 'ratelimit' 2025-03-26T18:59:20.509825068Z 0(1) DEBUG: <core> [core/sr_module.c:850]: find_param_export(): found <pipe> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509827468Z 0(1) DEBUG: <core> [core/modparam.c:135]: set_mod_param_regex(): found <pipe> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.509829943Z 0(1) DEBUG: ratelimit [ratelimit.c:925]: parse_pipe_params(): pipe: [1|TAILDROP|10] 2025-03-26T18:59:20.510800378Z 0(1) DEBUG: <core> [core/sr_module.c:758]: find_mod_export_record(): found export of <rl_check_pipe> in module ratelimit [/usr/lib/kamailio/modules/ratelimit.so] 2025-03-26T18:59:20.519776933Z 0(1) DEBUG: <core> [core/sr_module.c:1031]: init_mod(): ratelimit ########## LOGS WHEN APPLY RATELIMIT ########## 2025-03-26T19:01:02.095676663Z 1(7) DEBUG: {1 1 INVITE 1-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.095679040Z 1(7) DEBUG: {1 1 INVITE 1-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=1 load=0.0 network_load=0 => ACCEPT . . 2025-03-26T19:01:02.272879226Z 2(8) DEBUG: {1 1 INVITE 10-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.272881671Z 2(8) DEBUG: {1 1 INVITE 10-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=10 load=0.0 network_load=0 => ACCEPT 2025-03-26T19:01:02.292599816Z 2(8) DEBUG: {1 1 INVITE 11-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.292602425Z 2(8) DEBUG: {1 1 INVITE 11-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=11 load=0.0 network_load=0 => DROP . . 2025-03-26T19:01:02.492680874Z 1(7) DEBUG: {1 1 INVITE 21-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.492694107Z 1(7) DEBUG: {1 1 INVITE 21-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=21 load=0.0 network_load=0 => DROP 2025-03-26T19:01:02.513079779Z 2(8) DEBUG: {1 1 INVITE 22-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.513088852Z 2(8) DEBUG: {1 1 INVITE 22-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=0 counter=22 load=0.0 network_load=0 => DROP 2025-03-26T19:01:02.532804253Z 1(7) DEBUG: {1 1 INVITE 23-1(a)192.168.100.15} ratelimit [ratelimit.c:861]: w_rl_check_forced_pipe(): trying pipe 1 2025-03-26T19:01:02.532808087Z 1(7) DEBUG: {1 1 INVITE 23-1(a)192.168.100.15} ratelimit [ratelimit.c:830]: rl_check(): meth=INVITE queue=0 pipe=1 algo=2 limit=10 pkg_load=2 counter=1 load=0.1 network_load=0 => ACCEPT When the countdown restarts, it's "19:01:02.53" hours, and when it started, it was "19:01:02.09" hours. It doesn't reach the second. The drop system works well, but if my limit was 25 calls, I would have accepted the 22 I counted in the first second, plus the other 25 from the second number 2. Second question: There's a warning about a performance penalty in Kamailio when timer_interval is too small, so I've decided to set it to 2 just for practical purposes. So what should happen is that the counter would accept up to 10 calls in 2 seconds. But in the logs, what I see is the opposite: it accepts 20 calls in 2 seconds. Maybe it's supposed to work that way, and I'm misunderstanding the documentation? As optional information: Kamailio is running on a Google virtual machine, 12MB of RAM, 3 processors, 2 of which are dedicated. I'm using SIPP for load testing, and different call rates have been validated before testing the module. Sorry if my first post in this community was too long or is there more information missing :) . Thanks in advance

1 0

kamailio call redirect
by fabienbrou＠alcall.net 26 Mar '25

26 Mar '25

Hello everyone. I'm trying to redirect a call directly through kamailio by modifying the $ru variable. Just wondering if this is the right method or if there is a better way to do it. thanks

4 13

is possible empty actions?
by Sergey Safarov 26 Mar '25

26 Mar '25

I want to use contributions like route[PROXY_MEDIA] { if (is_method("BYE|CANCEL")) { # passing message for RTPengine processing } else if (!sdp_content()) { return; } # more instructions here ... rtpengine_manage(); } Now Kamailio cannot start because first if block has empty actions. How does nothing in the actions? I want to avoid not needed log messages and do not use constructions like if (!sdp_content() and ! is_method("BYE|CANCEL")) { return; }

3 2

Seeking advices on redesigning our VoIP system for scalability and manageability
by Francesco 26 Mar '25

26 Mar '25

Dear all, I hope this email finds you well. I am reaching out to gather insights and suggestions regarding a potential redesign of our VoIP system to improve scalability, ease of management, and upgradeability. *Current Setup:* - Our system is *not multi-tenant* and is based on *Kamailio and FreeSWITCH* in a distributed architecture (as example of distributed architecture, see: https://ufdcimages.uflib.ufl.edu/UF/E0/04/92/89/00001/THOMPSON_C.pdf). - Everything runs inside *LXC containers* across multiple nodes. - One of the challenges we face is *OS upgrades*, which are cumbersome and require significant manual intervention. - At the moment the code for voip is done with ansible Given these challenges, I am considering whether a *microservices-based architecture* could be a viable option. However, I have some concerns regarding: - *SIP and RTP handling with NATed containers* (e.g., Kubernetes, Docker Swarm) and potential issues with media traversal. - *Performance impact* when shifting real-time traffic handling to containerized environments. - *Upgrade and deployment strategies*—how to achieve smoother, rolling upgrades without service interruptions. - *Alternative approaches* that might be more effective, such as a hybrid model combining LXC with containerized microservices for specific functions. If anyone has experience transitioning a VoIP system to microservices or has insights on best practices for *scalable, maintainable VoIP architectures*, I would greatly appreciate your thoughts. What worked for you? What pitfalls should we be aware of?Do you have any documentation that I can check? Looking forward to learning from your experiences. Thank you. .: Francesco Colista .: Francesco Colista

3 2

TOPOS Issue with Response Handling on two different Interfaces
by Vinayak Makwana 25 Mar '25

25 Mar '25

Hello all, We are facing an issue while configuring TOPOS in Kamailio P-CSCF (running under Docker). Our objective is to strip Via, Record-Route, and Route headers for both INVITE and 180 Ringing responses. However, we observe unexpected behavior when handling the 180 Ringing/200 OK responses. Call Flow & Issue Description: Note: Public IP and Private IP mapping using the below configuration. listen=udp:Local_IP:5060 name "internal" listen=udp:Local_IP:6070 advertise Public_IP:6070 name "external" Call Flow (INVITE): A-Party --> Kamailio P-CSCF (Public IP) --> Kamailio P-CSCF (Private IP) --> Kamailio S-CSCF (Private IP) --> Kamailio P-CSCF (Private IP) --> Kamailio P-CSCF (Public IP) --> B-Party For an incoming *INVITE* (A-Party → B-Party), TOPOS successfully strips the headers when the message flows through the P-CSCF, ensuring proper privacy of routing information. *Issue* : When B-Party sends a 180 Ringing, we observe that Kamailio P-CSCF (Private IP) adds a Record-Route header before forwarding the message to A-Party. Call Flow (180 Ringing): B-Party --> Kamailio P-CSCF (Public IP) --> Kamailio P-CSCF (Private IP) --> Kamailio S-CSCF (Private IP) We need to ensure that the Record-Route and Via headers are stripped properly in both directions. Please guide us how to achieve and what we are doing wrong. TOPOS module is configured as follows: modparam("ndb_redis", "server", "name=srv1;addr=127.0.0.1;port=6379") modparam("topos_redis", "serverid", "srv1") modparam("topos", "storage", "redis") modparam("topos", "contact_mode", 1) modparam("topos", "rr_update", 1) RR module is configured as follows: modparam("rr", "enable_full_lr", 1) modparam("rr", "append_fromtag", 1) configured the below event_route: event_route[topos:msg-outgoing] { xlog("L_INFO","[topos:msg-outgoing]"); if(is_request() and $sndto(ip)=="SCSCF_PRIVATE_IP") { xlog("L_INFO","[topos:msg-outgoing] TOPOS \n"); drop; } } Thanks, Vinayak Makwana -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

1 1

← Newer
1
...
7
8
9
10
11
12
13
...
3751
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users