October 2021 - sr-users

T_req(pv) not accessible in dialog event route in v5.5.2
by Joel Serrano 23 Oct '21

23 Oct '21

Hello, I'm in the process of updating some servers that are running Kam v5.1.4 to v5.5.2. After the upgrade I've noticed that I've lost some custom metrics that we have defined via config-script. Snippet of the relevant config: event_route[dialog:start] { # Gather metrics regarding source IP xlog("L_WARN", "[DLG] - Checking country for ($si | $T_req($si)) - START\n"); if (geoip2_match("$T_req($si)", "src")) { # Country found ... } xlog("L_WARN", "[DLG] - … [View More]

2 3

"EXTERN.h: No such file or directory" error when compiling Kamailio 5.5 on Centos 7
by AL RSM 22 Oct '21

22 Oct '21

Hi, While trying to install Kamailio 5.5 on Centos 7 I am getting the following error. Perl is already installed. I verified "EXTERN.h" does not exist on the VM. # make include_modules="tm app_perl" cfg # make prefix=/ all .... .... Can't locate ExtUtils/Embed.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .). BEGIN failed--compilation aborted. Can't locate … [View More]

2 1

tls connections
by Richard Robson 20 Oct '21

20 Oct '21

I'm trying in vain to get a tls connection to a carrier. ~Without too much detail we are exchanging certificates and they are saying we are triggering a reset of the connection because we are requesting to chage the tcp window size. there are requiring us to have a window size of 65535. there we are sending a smaller window size. as far as I understand this should be OK. I have tried to force out linux install to set the window size to 65535 but we are still sing the … [View More]

2 2

Catching websocket / TCP errors
by Marrold 20 Oct '21

20 Oct '21

Hi, We're currently implementing WebRTC (SIP over a websocket) on our Kamailio proxies and we're experiencing a minor issue after a restart. We write all USRLOC entries to a shared database to implement HA. These are then loaded on a restart, which leaves us with entries with TCP connections that no longer exist. When a call attempt is made the proxy can't find the connection ID and immediately rejects the call with a "500 No error (2/SL)" - Oct 5 15:38:24 proxy-01 /sbin/kamailio[32087]: … [View More]

2 5

Use constants in attrs column of the dispatcher module
by Markus Bönke 19 Oct '21

19 Oct '21

Hello all, I’ve a question regarding the dispatcher module. So far we use on every server a separate database table, where the attribute column is set to the local internal or external socket like "socket=udp:192.168.1.70:5060“ or socket=udp:80.239.xxx.xxx:5060. Is there a way to use constants here like socket=udp:IPADDR_INTERN:5060 or socket=udp:IPADDR_EXTERN:5060 which are replaced when the data is loaded from the DB? Thanks and regards Markus

1 0

Kamailio on AWS Kubernetes with NLB
by Cedric Thiebault 18 Oct '21

18 Oct '21

Hello, I'm trying to deploy Kamailio on Kubernetes (AWS EKS with Network Load Balancer) but I'm not able to register using TCP. I'm using official Docker image 5.5.0-buster. I did some tests with Docker Compose and it worked fine, but on K8S it does not :-( Here are my logs: Listening on udp: 127.0.0.1:5060 udp: 172.31.4.29:5060 udp: 172.31.0.221:5060 tcp: 127.0.0.1:5060 tcp: 172.31.4.29:5060 tcp: 172.31.0.221:5060 … [View More]Aliases: tcp: ip-172-31-0-221.eu-central-1.compute.internal:5060 tcp: 172-31-4-29.kube-prometheus-stack-prometheus-node-exporter.infra-prometheus.svc.cluster.local:5060 tcp: localhost4.localdomain4:5060 tcp: localhost4:5060 tcp: localhost.localdomain:5060 tcp: localhost:5060 udp: ip-172-31-0-221.eu-central-1.compute.internal:5060 udp: 172-31-4-29.kube-prometheus-stack-kubelet.kube-system.svc.cluster.local:5060 udp: localhost4.localdomain4:5060 udp: localhost4:5060 udp: localhost.localdomain:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4983]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:188]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:3030]: main(): processes (at least): 41 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 29(35) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/35 31(37) INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 35(41) INFO: <core> [core/parser/parse_fline.c:147]: parse_first_line(): method not followed by SP 35(41) ERROR: <core> [core/parser/parse_fline.c:271]: parse_first_line(): parse_first_line: bad message (offset: 0) 35(41) ERROR: <core> [core/parser/msg_parser.c:747]: parse_msg(): ERROR: parse_msg: message=<> 35(41) ERROR: <core> [core/receive.c:374]: receive_msg(): core parsing of SIP message failed (194.230.146.66:9055/2) And my service: apiVersion: v1 kind: Service metadata: name: kamailio-tcp annotations: service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: '*' service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing service.beta.kubernetes.io/aws-load-balancer-target-group-attributes: preserve_client_ip.enabled=true service.beta.kubernetes.io/aws-load-balancer-type: external labels: app.kubernetes.io/instance: test-sip app.kubernetes.io/name: kamailio-tcp app.kubernetes.io/version: 5.5.0-buster spec: type: LoadBalancer externalTrafficPolicy: Local ports: - name: sip-tcp nodePort: 30567 port: 5060 protocol: TCP targetPort: 5060 selector: app.kubernetes.io/instance: test-sip app.kubernetes.io/name: kamailio I have a Netwok Load Balancer create with a listener for TCP 5060 but when I try to connect with Zoiper or Linphone, it does not work :-( I used tcpdump on my pod and it received well some SIP commands. Any ideas of what could be wrong here? Thanks in advance! Cedric [View Less]

2 5

Routing dialogs (INVITE) from Lua
by Emilio Panighetti 18 Oct '21

18 Oct '21

Hello, Based on kamailio-basic-kemi.cfg and kamailio-basic-kemi-lua.lua, I’m trying to get a simple test to go through using SIPp built-in UAC and UAS scenarios, using LUA config: Commented out all the registration blocks and trying to run a simple proxy for now, but I can’t seem able to change the URI. SIPp UAC: 192.168.1.12:5060 SIPp UAS: 192.168.1.12:5062 Kamailio 5.5.2: 192.168.15.:5060 Part of the Kamailio.lua config: -- wrapper around tm relay function function ksr_route_relay() -… [View More]- enable additional event routes for forwarded requests -- - serial forking, RTP relaying handling, a.s.o. if KSR.is_method_in("IBSU") then if KSR.tm.t_is_set("branch_route")<0 then KSR.dbg("EP: ksr_route_relay Set for branch_route\n"); KSR.tm.t_on_branch("ksr_branch_manage"); end end if KSR.is_method_in("ISU") then if KSR.tm.t_is_set("onreply_route")<0 then KSR.dbg("EP: ksr_route_relay Set for onreply_route\n"); KSR.tm.t_on_reply("ksr_onreply_manage"); end end if KSR.is_INVITE() then if KSR.tm.t_is_set("failure_route")<0 then KSR.dbg("EP: ksr_route_relay Set for failure\n"); KSR.tm.t_on_failure("ksr_failure_manage"); end end if KSR.tm.t_relay()<0 then KSR.dbg("EP: ksr_route_relay Set for reply_error\n"); KSR.sl.sl_reply_error(); end -- EP: Base route KSR.dbg("EP: ksr_route_relay Check for Base Route\n"); if KSR.is_INVITE() then KSR.dbg("EP: ksr_route_relay Base Route (DU)\n"); --KSR.sl.send_reply("503", "Debug"); KSR.setdsturi("sip:192.168.1.12:5062"); KSR.pv.sets("$du", "sip:192.168.1.12:5062"); end KSR.dbg("EP: ksr_route_relay exit\n"); KSR.x.exit(); end What’s happening here is that instead of forwarding the INVITE to the SIPp UAC, it creates a loop. Tried KSR.setdsturi() only (KSR.pv.sets commented out) and it’s still the same. If I comment out the 503 reply, then that’s what the UAC gets back. Here’s the log when calling ksr_route_relay: Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/msg_translator.c:162]: check_via_address(): (192.168.1.12, 192.168.1.12, 0) Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:489]: sr_lua_reload_script(): No need to reload [/etc/kamailio/kamaili o.lua] is version 0 Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:673]: app_lua_run_ex(): executing Lua function: [[ksr_onsend_route]] Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:675]: app_lua_run_ex(): lua top index is: 0 Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: tm [t_funcs.c:376]: t_relay_to(): new transaction forwarded Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: dbg is str: EP: ksr_r oute_relay Check for Base Route Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/kemi.c:85]: sr_kemi_core_dbg(): EP: ksr_route_relay Check for Base Route Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: dbg is str: EP: ksr_r oute_relay Base Route (DU) Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/kemi.c:85]: sr_kemi_core_dbg(): EP: ksr_route_relay Base Route (DU) Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: setdsturi is str: sip :192.168.1.12:5062 Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: sets is str: $du Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[1] for: sets is str: sip:192. 168.1.12:5062 Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/kemi.c:2906]: sr_kemi_pv_sets(): pv set: $du Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/pvapi.c:371]: pv_cache_add(): pvar [$du] added in cache Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: dbg is str: EP: ksr_r oute_relay exit Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/kemi.c:85]: sr_kemi_core_dbg(): EP: ksr_route_relay exit Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:1837]: sr_kemi_lua_exit(): script exit call Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_api.c:729]: app_lua_run_ex(): ksr error call from Lua: ~~ksr~exit~~ Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: app_lua [app_lua_mod.c:167]: sr_kemi_config_engine_lua(): execution of route type 1 with no n ame returned 1 Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) INFO: LUA {INVITE}: <core> [core/receive.c:515]: receive_msg(): request-route executed in: 1335 usec Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: LUA {INVITE}: <core> [core/receive.c:606]: receive_msg(): cleaning up Oct 17 23:42:48 ol-vm1 kamailio[2416]: 3(2419) DEBUG: <core> [core/udp_server.c:493]: udp_rcv_loop(): received on udp socket: (112/100/661) [[INVITE sip:service@ 192.168.1.15:5060 SIP/2.0 0D 0A Record-Route: <sip:192.168.1.15;lr=on> 0D 0A Via: SIP/2.0/U]] Any idea how we can route this message? Thanks! [View Less]

2 1

dmq_usrloc writes to database on other nodes too
by Maarten Ureel 17 Oct '21

17 Oct '21

I have the idea that if you enable dmq_usrloc, the other nodes that receive the usrloc info, also try to write to database. We see this by a lot of errors indicating the index violation on postgres. What is the easiest way to tell Kamailio that it does not need to store the usrloc in database if the data came through a DMQ message? Currently I have in my config: # DMQ processing if(is_method("KDMQ") && $Rp == 5090) { dmq_handle_message(); } I have understood that … [View More]

2 4

kamailio SipTrace Module
by Андрей Зюзенков 17 Oct '21

17 Oct '21

Good afternoon, I apologize for disturbing you. I have a question that I cannot find in the documentation https://www.kamailio.org/docs/modules/devel/modules/siptrace.html#siptrace.… 3.3. trace_flag parameter has some values. And what values can be and what do they mean pls, help

2 1

http_async_client "route_name" is considered a failure route?
by Brooks Bridges 16 Oct '21

16 Oct '21

So I've been working on this for a while, and I cannot seem to find a way around this. When using the http_async_client to request data from an external API, the returned data in the "route_name" target is being treated as a failure route, so most of the subsequent processing and messaging that I want to do is not working, either because the function can't be used in a failure route, or because I have to create a transaction prior to doing the request, which then throws an error by immediately … [View More]

2 1

Call to MS Teams
by Володимир Іванець 15 Oct '21

15 Oct '21

Hello all! I'm trying to make a call from the system with Kamailio to a MS Teams. I can answer in the Teams client, system will receive response 200 OK and audio streams will be started. The problem I have is that after a short period of time Teams sends BYE with the reason "An acknowledgement was not received for the call acceptance in the allotted time". If I try to hangup from the system side, Teams will receive BYE and respond with "481 Call Leg/Transaction Does Not Exist" - "Call leg … [View More]

1 1

unable to receive UDP
by dem＠htsweb.com 13 Oct '21

13 Oct '21

After 4 (long) days of trying to receive any UDP SIP, I'm hoping someone can point out what I'm doing wrong. I've looked at the kamailio code. I'm beginning to think it's the 'polling' code, but it looks fine. It could be Centos or a Dell network driver, but not seeing any errors anywhere. - stock build/compile... Version: kamailio 5.5.2 (x86_64/linux) 0d53d9 Compile flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP,… [View More] PKG_MALLOC, 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 MAX_RECV_BUFFER_SIZE=262144 MAX_URI_SIZE=1024 BUF_SIZE=65535 DEFAULT PKG_SIZE=8MB DEFAULT SHM_SIZE=64MB ADAPTIVE_WAIT_LOOPS=1024 TCP poll methods: poll, epoll_lt, epoll_et, sigio_rt, select Source code revision ID: 0d53d9 Compiled with: gcc 4.8.5 Compiled architecture: x86_64 Compiled on: 08:44:19 Oct 11 2021 Running Centos 7 all updated. Dell R630. # sestatus SELinux status: disabled # firewall-cmd --list-all ports: 5666/tcp 873/tcp 873/udp 80/tcp 443/tcp 5060/tcp 5060/udp 5061/tcp 5061/udp - Just trying to send SIP INVITE from trunk provider to R630 kamailio... (SIP trunk) UDP 172.200.200.202:5060 -> (firewall) UDP 172.250.250.162:5060 -> 1:1 NAT -> (R630) UDP 10.102.88.81:5060 - I can 'see' the packet hit the em3 network... # tcpdump -i em3 -e -vv -n port 5060 11:53:33.260892 99:99:ef:3e:69:c1 > 99:99:1c:48:4e:e3, ethertype IPv4 (0x0800), length 1366: (tos 0x0, ttl 54, id 20430, offset 0, flags [none], proto UDP (17), length 1352) 172.200.200.202.sip > 10.102.88.81.sip: [udp sum ok] SIP, length: 1324 INVITE sip:+18005551234@172.250.250.162:5060 SIP/2.0 ... At this point, I just need to see a SIP INVITE received. Then I can go back to working on a real config. I've tried with TCP on/off, listening on all networks, alias on/off, strace and everything else I could think of.Truly appreciate any guidance. Tried every sample config possible, but I just need to test receiving the SIP UDP packet, so this 'should' be minimum config... #!KAMAILIO debug=9 log_stderror=no log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " children=2 disable_tcp=yes udp4_raw=on auto_aliases=no alias="sbc01.mysite.com" listen=udp:10.102.88.81:5060 loadmodule "debugger.so" loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" modparam("debugger", "cfgtrace", 1) request_route { xlog("SIP received xxxxxxxxxxxxxxxxxxx\n"); } # kamcmd ps 11578 main process - attendant 11579 udp receiver child=0 sock=10.102.88.81:5060 11580 udp receiver child=1 sock=10.102.88.81:5060 11581 slow timer 11583 timer 11584 secondary timer 11585 JSONRPCS FIFO 11586 JSONRPCS DATAGRAM 11587 ctl handler - I get plenty of logging, but the logging just waits here... Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10060]: INFO: ctl [io_listener.c:210]: io_listen_loop(): io_listen_loop: using epoll_lt as the io watch method (auto detected) Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10060]: DEBUG: <core> [core/mem/q_malloc.c:374]: qm_malloc(): qm_malloc(0x7fd2a8bae010, 4800) called from core: core/io_wait.c: init_io_wait(469) Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10059]: DEBUG: <core> [core/mem/q_malloc.c:419]: qm_malloc(): qm_malloc(0x7fd2a8bae010, 65456) returns address 0x7fd2a8c652d8 frag. 0x7fd2a8c652a0 (size=65456) on 1 -th hit Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10060]: DEBUG: <core> [core/mem/q_malloc.c:419]: qm_malloc(): qm_malloc(0x7fd2a8bae010, 4800) returns address 0x7fd2a8c652d8 frag. 0x7fd2a8c652a0 (size=4800) on 1 -th hit Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10060]: DEBUG: <core> [core/mem/q_malloc.c:374]: qm_malloc(): qm_malloc(0x7fd2a8bae010, 2400) called from core: core/io_wait.c: init_io_wait(516) Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10060]: DEBUG: <core> [core/mem/q_malloc.c:419]: qm_malloc(): qm_malloc(0x7fd2a8bae010, 2400) returns address 0x7fd2a8c66600 frag. 0x7fd2a8c665c8 (size=2400) on 1 -th hit Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10060]: DEBUG: ctl [io_listener.c:246]: io_listen_loop(): io_listen_loop: adding socket 8, type 2, transport 3 (/var/run/kamailio//kamailio_ctl) Oct 12 11:38:04 sbc01 /usr/local/sbin/kamailio[10060]: DEBUG: ctl [../../core/io_wait.h:375]: io_watch_add(): DBG: io_watch_add(0x7fd2a70a5360, 8, 2, 0x2439960), fd_no=0 - The only other thing that I see is transport 3. Isn't that a UNIXS_SOCK? [View Less]

5 9

Kamailio Inbound proxy to Asterisk - ACL Filtering
by Mihai Cezar 13 Oct '21

13 Oct '21

Hello, I have an issue with filtering on the asterisk side, my requests are: UsersPhones(bria) -> Kamailio -> Asterisk -> Sip Trunk Out. The goal is to manage a new layer of protection ( IP filtering / Whitelisting ). When I try to compile a list of Whitelisted IP in sip.conf I get this error: NOTICE[205]: acl.c:748 ast_apply_acl: SIP contact ACL: Rejecting '145.72.23.45' due to a failure to pass ACL '(BASELINE)' WARNING[205]: chan_sip.c:17061 parse_register_contact: Domain '5.12.16.… [View More]

4 7

Compile kamailio-5.4 against openssl1.1.1
by Antony Russell 13 Oct '21

13 Oct '21

Hello I see that support for compiling kamailio against openssl1.1.1 was recently added (https://github.com/kamailio/kamailio/pull/2779) and I see that this can be done in kamailio-5.5.2. Will this ability be made available in kamilio-5.4? I see it is not in the most recent 5.4 release (5.4.7) -- *Antony Russell* Chief Technical Officer Tel 087 820 8113 antony.russell(a)telviva.co.za www.telviva.co.za *Telviva (Pty) Ltd - formerly Connection Telecom (Pty) Ltd* -- https://www.telviva.… [View More]

1 0

Fail Call from Webrct to PSTN SIP Trunk
by Abdul Rahman Reza 11 Oct '21

11 Oct '21

Hi Everyone There some log kamailio Warning: 399 03077.08860.B.005.422.228.0.15.01039.00000000.00000 "SDP body length beyond limit" how to increase maximum length sdp in kamailio, because i don't see any configuration related to sizing max length SDP on kamailio documentation please help me Thank you very much

3 3

Let's Encrypt DST Root CA X3 cert CA expiration 30th/Sept - Any issues?
by Joel Serrano 11 Oct '21

11 Oct '21

Hello, I'm wondering if anyone had any issues yesterday with the expiration of the DST Root CA X3 cert? Out of all the servers I manage, only a couple were affected (debian 8). They were production servers so we replaced the cert with a different one to solve the issue while we find the root cause. Anyone out there had any issues yesterday because of this? I'm just curious! Joel.

10 12

upgrade kamailio 4.4.x-to-5.0.0 - PostgreSQL migrations
by Giovanni Tommasini - timenet srl 11 Oct '21

11 Oct '21

Hi Dears, I'm working on upgrading Kamailio from 4.4.6 to 5.4.0 in an installation where I use PostgreSQL I understand that I have to upgrade in steps by following these links: - http://www.kamailio.org/wiki/install/upgrade/4.4.x-to-5.0.0 - http://www.kamailio.org/wiki/install/upgrade/5.0.x-to-5.1.0 - https://www.kamailio.org/wiki/install/upgrade/5.1.x-to-5.2.0 - https://www.kamailio.org/wiki/install/upgrade/5.2.x-to-5.3.0 - https://www.kamailio.org/wiki/install/upgrade/5.3.x-to-5.4.0 in … [View More]

3 5

Critical log when $mbu pseudovariable is accessed
by Alberto Izquierdo 11 Oct '21

11 Oct '21

Hi, I'm getting some CRITICAL logs when accessing the content of the $mbu pseudovariable in a "onsend_route" function. The log lines look like this: ``` CRITICAL core 35847:core/msg_translator.c:493 null send socket CRITICAL core 35847:core/msg_translator.c:893 FIXME: null send_sock CRITICAL core 35847:core/msg_translator.c:493 null send socket CRITICAL core 35847:core/msg_translator.c:493 null send socket CRITICAL core 35847:core/msg_translator.c:493 null send socket CRITICAL … [View More]

2 7

rtpengine module dependencies
by Juha Heinanen 10 Oct '21

10 Oct '21

rtpengine module README tells this about module dependencies: 3.1. Kamailio Modules The following modules must be loaded before this module: tm module - (optional) if you want to have rtpengine_manage() fully functional Looks like this is not correct. If Kamailio connects to rtpengine over websocket protocol, then there is dependency on lwsc module. I haven't checked if lwsc module works without tls module when wss is used. -- Juha

1 0

Kamailio Inbound proxy to Asterisk - ACL Filtering
by Mihai 09 Oct '21

09 Oct '21

Hello, I have an issue with filtering on the asterisk side, my requests are: UsersPhones(bria) -> Kamailio -> Asterisk -> Sip Trunk Out. The goal is to manage a new layer of protection ( IP filtering / Whitelisting ). When I try to compile a list of Whitelisted IP in sip.conf I get this error: NOTICE[205]: acl.c:748 ast_apply_acl: SIP contact ACL: Rejecting '145.72.23.45' due to a failure to pass ACL '(BASELINE)' WARNING[205]: chan_sip.c:17061 parse_register_contact: Domain '5.12.16.… [View More]

1 0

Nagios NRPE Plugin for Kamailio 5.x
by Angelo Sipper 08 Oct '21

08 Oct '21

Hi, I would like to monitor kamailio via our nagios. Is there any working plugin available for nagios nrpe to monitor shared memory and some other config variables for kamailio 5.x that someone has used and could suggest? Kind regards, Angelo

2 1

update max_while_loops in config
by Juha Heinanen 08 Oct '21

08 Oct '21

It is possible to update value of max_while_loops dynamically in config file? For example, there could be a need to increase the max in some while loop, but after the loop is done, decrease it again for other loops. There exists an rpc command to do that, but I haven't found how to do it in config file. I tried @cfg_seti.core.max_while_loops = 200; but got syntax error. -- Juha

3 6

Suspend INVITE between ip4 and ip6 users
by Péter Barabás 08 Oct '21

08 Oct '21

Hi, I try to modify the kamailio configuration to work between ipv4 and ipv6 clients. Clients are mobile sofphones, so they are mostly in background without registration. 1. When an INVITE arrives from IPV4 address, transaction is suspended and a push notification is sent to callee. 2. Callee gets push notification and registers to kamailio. 3. INVITE transaction continues. My kamailio config is based on this article: https://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 using … [View More]

1 0

Missing line in line.count transformation
by Daniel Donoghue 08 Oct '21

08 Oct '21

I think I’ve found an edge case with the string transformations for line.count: In pv_trans.c, the following code does not appear to consider the last line if there are multiple lines and the last one is not terminated with \n. case TR_LINE_COUNT: n=0; for(i=0; i<val->rs.len; i++) if(val->rs.s[i]=='\n') n++; if(n==0 && val->rs.len>0) n = 1; val->flags = PV_TYPE_INT|PV_VAL_INT|PV_VAL_STR; val->ri = n; val->rs.s … [View More]

4 5

Parsing Error in Timer Module of kamailio
by Surabhi Garg 07 Oct '21

07 Oct '21

Hi Team, Greetings! I am trying to use Timer Module of Kamailio to keep calling particular route at particular time interval. Here is the snippet of my config: loadmodule "timer.so" modparam("timer", "declare_timer", "MYTIMER=SHUTDOWN,5000,slow,enable"); route[SHUTDOWN] { xlog("system shutdown: $sht(graceful_shutdown=>shutdown)\n"); } But after restarting the Kamailio, I keep on getting parsing errors in every 5 sec and my route "SHUTDOWN" never get called. Which … [View More]

2 2

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 October 2021