- sr-users - kamailio.org

Catching Register 200 OK, then using it to validate other packets.
by Richard Edmands 04 Jan '22

04 Jan '22

Hey Kamailio Users, I've written a TLS-UDP gateway. It works well, but I want to reduce the internet noise it pushes through. I have an idea on what I'd like to try. Wondering if it would be possible to catch the Register 200 OK, store it and then when receiving packets it future to then validate them against the data? I've managed to capture a 200 OK, but the save("location") function says it will return it's own 200 OK which isn't the plan since we just want to capture the location. Anyone done something similar and got some working example code? Is this a bad idea for some reason?

2 2

Re: [SR-Users] Kamailio docker image run in Kubernates
by Henning Westerholt 27 Dec '21

27 Dec '21

Hello, (please keep the list in CC) Can you pull the v2 image on the command line with the CLI commands from your repository? Do you have Maybe its some naming or access rights issue. You need to try out different things in isolating the cause, it’s difficult to guess. Have a look e.g. here for more debug options for this error https://stackoverflow.com/questions/34848422/how-can-i-debug-imagepullbacko… Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Maryam Baghdadi <maryam.baghdadi(a)gmail.com> Sent: Monday, December 27, 2021 10:15 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Kamailio docker image run in Kubernates I dedicate a service and demonset.apps in yaml file. When I assign a label to a node of k8 and then select node according to node label in yaml file for first image for example image:v1 every thing is OK and pulling done successfully . But for second time when I rebuild docker image after changing kamailio configuration for example image:v2 generated , pulling error happens… On Tue, Dec 28, 2021, 12:34 AM Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> wrote: Hello, as mentioned in the issue tracker, the error seems to be related to a failure of k8s pulling the second docker image. Have you tried to debug the second services locally, for example with docker-compose or some local k8s distribution? Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Maryam Baghdadi Sent: Monday, December 27, 2021 9:44 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: [SR-Users] Kamailio docker image run in Kubernates Hello everyone, I have a problem over running local docker images of Kamailio in Kubernate cluster.. Consider I build a local docker image from Kamailio and create a pod in one of my nodes . My process created successfully and Kamailio listen over port 5060 now I need to rebuild another docker image with new Kamailio configuration and run it as another pod with new name and listening over port 5061 but I have error "ImagePullBackOff" . I test this scenario many times but problem exists.. It is devastating for me and I need emergency help.

1 0

Kamailio docker image run in Kubernates
by Maryam Baghdadi 27 Dec '21

27 Dec '21

Hello everyone, I have a problem over running local docker images of Kamailio in Kubernate cluster.. Consider I build a local docker image from Kamailio and create a pod in one of my nodes . My process created successfully and Kamailio listen over port 5060 now I need to rebuild another docker image with new Kamailio configuration and run it as another pod with new name and listening over port 5061 but I have error "ImagePullBackOff" . I test this scenario many times but problem exists.. It is devastating for me and I need emergency help.

2 1

Kamailio Stop processing SIP traffic
by pwerspire 27 Dec '21

27 Dec '21

Hi, I have been doing some load testing with Kamailio and having some issues. I have been trying with 100 CPS and at the beginning, everything is working well but after some time (it can be 10 minutes or for example 40 minutes, is just random but normally happens more in the first 10 minutes) Kamailio stop replying to all SIP messages but still processing HTTP requests, some commands, etc. If I use "kamcmd dlg.list" no output happens and after that, all kamcmd commands just keep loading with no output. Kamailio is sharing Dialogs and htables using DMQ with other Kamailio that is the failover, if I shut down the failover one (so no DMQ replication), the test works well with the 100 CPS. Also tried with modparam("dmq", "worker_usleep", 1000) but the behavior is the same, it will stop processing traffic. This is some of configuration used: # ----------------- setting module-specific parameters --------------- modparam("dmq", "server_address", "sip:INTERNAL_INSTANCE_IP:5060") modparam("dmq", "notification_address", "DMQ_NOTIFICATION_ADDRESS") modparam("dmq", "multi_notify", 1) modparam("dmq", "ping_interval", 10) modparam("dmq", "num_workers",4) modparam("htable", "enable_dmq", 1) modparam("htable", "dmq_init_sync", 1) # ----- dialog params ----- modparam("dialog", "dlg_flag", FLD_DLG) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "db_url", DBURL_RW) modparam("dialog", "db_mode", 0) modparam("dialog", "enable_dmq", 1) modparam("dialog", "db_update_period", 10) modparam("dialog", "h_id_start", H_ID_START) modparam("dialog", "h_id_step", H_ID_STEP) Memory: Shared: 4096 Private: 512 kamailio -v version: kamailio 5.5.3 (x86_64/linux) 473cef flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, 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, 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: 473cef compiled on 09:34:57 Dec 20 2021 with gcc 10.2.1 In attach is the trap collected after the issue happens. Any more logs or configurations that can help identify or solve the issue? Thanks for the help, Regards, Tiago

6 11

How to change language in siremis web interface
by mohammad baghdadi 27 Dec '21

27 Dec '21

Hello I’m new in siremis as web interface of kamailio and I immediately need your help,I installed kamailio and siremis and login in siremis web interface,I can work with it but now I have a problem. I want to change menu language there is an option in(setting->translate->manage languages) add my desired language and click save and i see this error: Error message: #2, count(): Parameter must be an array or an object that implements Countable Script name and line number of error: [/var/www/siremis-5.3.x/siremis/modules/translation/lib/LangPackCreator.php I needed to change the language and thanks for your the help to me.

2 1

MongoDB and SIREMIS
by Tihomir Culjaga 27 Dec '21

27 Dec '21

hi, I'm running kamailio 5.4 using MongoDB as a backend database. Can I run SIREMIS on that database as well? Regards, Tihomir.

2 1

Merry Christmas and Happy Holidays 2021-2022!
by Daniel-Constantin Mierla 25 Dec '21

25 Dec '21

Another challenging year is getting close to its end, pressuring even more everyone! Let's hope things will go back to a more usual life (as it used to be) in the near future! Kamailio project continued to develop, bringing out a new major release, preparing for the next one in a few months, relying on an amazing community of developers and users. We also trust it continued to help people and companies world wide to connect with the dear ones and build a better way of living. The season holidays are ahead, time to relax, spend time with family and friends! I take again this chance to express my thanks and greetings to all the friends, developers, supporting companies and community members that made 2021 another great year for Kamailio project. Enjoy the holidays! Merry Christmas! Daniel * Santa is flying Kamailio! * -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

repository not present
by Jyoti bansal 23 Dec '21

23 Dec '21

2 1

Active/active keepalived - Kamailio includes non-local virtual IP in "myself" which breaks DMQ call routing
by Rhys Hanrahan 22 Dec '21

22 Dec '21

Hi Everyone, I have Kamailio acting as a registrar, using DMQ to replicate usrloc between nodes. I’m relaying INVITEs to the home registrar, but skipping this if (uri == myself) is true. In my lab I just setup my SBCs in an active/active mode, similar to the link below. So I have 2x VIPs and both SBCs listen on both, but the first VIP is only master on SBC01 and the second VIP is only master on SBC02. https://docs.nginx.com/nginx/admin-guide/high-availability/ha-keepalived-no… My issue is that now “myself” will always return true even if the virtual IP is actually not active on this node at the moment, so the invite is never relayed properly if it’s on another node. I guess “myself” is just blindly looking at the list of Ips that are configured with either listen= or alias= and doesn’t care if the IP actually exists on the server at the time, or not? I am thinking I may have to ditch relying on “myself” entirely and come up with some other way of checking for local requests, but I am wondering if there’s a good way of approaching this? I was thinking of perhaps triggering an add/remove of listen directives (or something) when a failover of a VIP happens, though this seems kind of heavy handed. Hoping there is a better way. Has anyone else tried doing active/active Kamailio instances like this? Thanks! Rhys Hanrahan | Chief Information Officer e: rhys(a)nexusone.com.au<mailto:rhys@nexusone.com.au> [www.nexusone.com.au]<http://www.nexusone.com.au/> [signature_132622389] <http://www.fusiontech.com.au/> NEXUS ONE | FUSION TECHNOLOGY SOLUTIONS p: 1800 NEXUS1 (1800 639 871) or 1800 565 845 | a: Suite 12.03 Level 12, 227 Elizabeth Street, Sydney NSW 2000 www.nexusone.com.au<http://www.nexusone.com.au/> | www.fusiontech.com.au<http://www.fusiontech.com.au/> The information in this email and any accompanying attachments may contain; a. Confidential information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties; b. Legally privileged information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties; and or c. Copyright material Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties. If you have received this email in error, please notify the sender immediately and delete this message. Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd does not accept any responsibility for loss or damage arising from the use or distribution of this email. Please consider the environment before printing this email.

3 6

Issue Bug in SEMS (transparent SBC profile)
by Mojtaba 21 Dec '21

21 Dec '21

Hello, Why in SEMS, some changes (in transparent SBC profile) in sip headers do not apply. For example i want to change CSeq or Contact header like this: # transparent SBC profile # defaults: transparent RURI=$r From=$f To=$t Call-ID=$ci_leg2 CSeq=$H(CSeq) Contact=$H(Contact) When I run SEMS, CSeq and Contact do not change, while other headers change. [#7fc688d7b1c0/9379] [onLoad, SBC.cpp:189] INFO: loading SBC call profiles from '/usr/local/etc/sems/etc/' [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:418] INFO: SBC: loaded SBC profile 'mo' - MD5: d6a2c29084043edde1357231f6866737 [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:423] INFO: SBC: RURI = '$r' [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:424] INFO: SBC: RURI-host = '' [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:425] INFO: SBC: From = '$f' [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:426] INFO: SBC: To = '$t' [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:431] INFO: SBC: Call-ID = '$ci_leg2222' [#7fc688d7b1c0/9379] [readFromConfiguration, SBCCallProfile.cpp:434] INFO: SBC: force outbound proxy: yes This issue caused the Asterisk could not pass the Authentication process in "match_req_to_dialog" function because the CSeq is the same as the dialogs. So the Asterisk thought this message was a LOOP message. Has anybody encountered this issue in SEMS? How did you solve this? I know there are some ways for doing this with Kamailio, But i focused on issues in SEMS With Best Regards *-- Mojtaba Esfandiari.S* *-- PhD student and Research Affiliate, * *-- Technical Manager at IP-PBX Laboratory, Ferdowsi University of Mashhad, Iran.* -- Address: IP-PBX Lab., Engineering Faculty, Ferdowsi University Main Campus, Mashhad, Iran. -- Tel: +98-51-38763635 -- Mobile: +98-915-117-6713

4 14

uac module - use htable instead of database
by Markus Bönke 20 Dec '21

20 Dec '21

Hello all, we want to use the "remote registrations feature" of the uac module to let kamailio register with other sip providers. As far as I see the module works only with a database backend. As our kamailio script should be independent from a database, a solution could be to load the configuration on startup (and refresh it periodically) from a database view into a htable and then trigger the remote registrations based on the expiration of the htable columns. Could something like this be implemented by using the uac module or by an other workaround ? Or does it require some enhancements in the uac module ? Thanks and regards Markus

2 2

Using kamcmd tm.t_uac_start to send SIP REGISTER messages in Kamailio 5.5
by Steve Sether 20 Dec '21

20 Dec '21

I'm trying to use the kamcmd tml.tc_uac_start command to send raw SIP messages in Kamailio 5.5, but I always get a error: 400 - Invalid headers. I've also tried sending OPTIONS messages with the same result. I've looked for examples of sending SIP messages via kamcmd, but can't find any. kamcmd help tm.t_uac_start specifies the following: kamcmd> help tm.t_uac_start starts a tm uac using a list of string parameters: method, ruri, dst_uri, send_sock, headers (CRLF separated) and body (optional) Essentially my problem is I don't really know how to properly encode these headers. How do I send special characters? Do I need to use double quotes, single quotes, etc around the whole header? Which characters are special? How do I encode the CRLF? I tried \r\n, but I still get this error. It says only From: and To: are required. It's a bit hard trying to make progress when all I ever get is one error message. The kamailio logs are a little more helpful, and largely point me down the road that it doesn't understand the CRLF encoding, and says my From: header includes the To: line, so it's not separating them. For example, I'm trying things like this: kamcmd -v tm.t_uac_start OPTIONS sip:200@exampleserver.com:5060 . . "From: <sip:example@192.168.0.1>;tag=d27ca05e-1789-4774-a698-dcfe91dec9b4\r\nTo: <sip:example@192.168.0.2>"\r\nExpires: 1200\r\nContent-Length: 0" Nothing seems to work, so whatever the syntax I'm using must be wrong. Just providing an example of sending SIP via kamcmd tm.t_uac_start would likely help a huge amount. Thanks! --

2 1

tcp_set_connection_lifetime(1) does not close connection
by Sebastian Damm 19 Dec '21

19 Dec '21

Hi, for having a maintenance mode, I need to implement some sort of draining functionality. All our clients register via TLS. So I thought, I just answer the next REGISTER of a client with a 503 and kill the tcp connection afterwards, so they need to open up a new connection to the loadbalancer in front and end up on a different server. This is my code: 510 if msg.is_method("REGISTER"): 1 if KSR.pv.get("$shv(MAINTENANCE_MODE)") == 1: 2 KSR.info("In maintenance mode, rejecting registration") 3 KSR.hdr.append_to_reply("Retry-After: 2\r\n") 4 KSR.sl.sl_send_reply(503, "Draining") 5 if KSR.tcpops.tcp_set_connection_lifetime(1) > 0: 6 KSR.info("Set Connection lifetime to 1") 7 return False (Side note: msg is some internal class, this is obviously KEMI with python) So now when I set the MAINTENANCE_MODE var to 1, Kamailio rejects the REGISTER requests, logs both lines and sends out a 503. Debug log tells me this: Dec 10 15:32:10 ifens5 /usr/sbin/kamailio[3851]: DEBUG: tcpops [tcpops.c:229]: tcpops_set_connection_lifetime(): new connection lifetime for conid=1: 908866403 Dec 10 15:32:21 ifens5 /usr/sbin/kamailio[3855]: DEBUG: <core> [core/tcp_main.c:4554]: tcpconn_main_timeout(): entering timer for 0x7f759cb26218 (ticks=908866499, timeout=908866499 (0 s), wr_timeout=0 (211631299 s)), write queue: 0 bytes In tcpdump I can see that the connection does not get closed immediately. Is there some timer in the tcp stack which cleans up expired connections from time to time? Can I manipulate how often this timer runs? I couldn't find anything, and clearly even though I tell Kamailio to close the connection after 1 second, it doesn't do it. Thanks for any input. Regards, Sebastian

3 3

Kamailio SIP Application server
by Weiqi Yao 17 Dec '21

17 Dec '21

Hello community, We were testing using Kmailio work as an IMS, and then turn out the phone wants to do MMTel for mobile real-time multimedia communication. We are not familiar with this topic, but anyone know Kamailio have such module or any other MMTel service can work with Kamailio? BR, Weiqi

2 2

RPC command dlg.profile_get_size with per_value response
by David VILLAUME 17 Dec '21

17 Dec '21

Hello, I would like to suggest you an implementation of the rpc command dlg.profile_get_size (on a valued profile) that would return a list of values and the number of current dialogs for any of them . Din’t know where to suggest it so I sent it there, please accept my apologies if it’s not the good place. Regards, David

2 2

SRTP/DTLS + RTP Header encryption
by Rahul mm 15 Dec '21

15 Dec '21

Hi guys, Is it possible to achieve RTP header encryption along with payload in SRTP/DTLS ? So far what I've been able to see is RTP payload encryption. I'm using kamailo 5.5.0 and rtpengine 9.2.1.6 in webRTC scenario. Many thanks. BR, Rahul

2 3

Next online devel meeting - Wed, Dec 15, 2021, 15:00UTC
by Daniel-Constantin Mierla 15 Dec '21

15 Dec '21

Hello, 2021 is almost over, time ran fast somehow this year, with a major release in the middle, which delayed the development discussion for the next one, so it's time for it! As usual, the aim is to sketch the roadmap to next major release so the developers and community members can syncronize and plan what should be done till Kamailio v5.6 will be out as well as discuss about current state of the project, look for new ideas to improve collaboration within the community, a.s.o. The meeting will be done on a matrix chat room. More details are in the wiki page of the event, available at: * https://www.kamailio.org/wiki/devel/irc-meetings/2021a Feel free to add there topics that you want to be discussed. The proposed date is next Wednesday, December 15, 2021, at 15:00UTC (15:00 London/Dublin, 16:00 most of West Europe, 10:00 New York), but other dates can be proposed if they suit for more participants. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda _______________________________________________ Kamailio (SER) - Development Mailing List sr-dev(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev

1 2

ACK is sent to wrong address when using serial forking
by Minh Phan 15 Dec '21

15 Dec '21

Dear List, As shown in the image below, Proxy 1 tries to do serial forking to Proxy 3 and then Proxy 4. Upon reception of the 480 answer ( blue frame) from Proxy 2, the Proxy 1 generated an ACK (red frame) and sent it to Proxy 1. The problem I have is that the ACK generated by Proxy 1 has a wrong RURI. I expect the ACK to be sent to the URI of the CONTACT header of the 480 message (blue frame). However, its RURI is the same as the one in the first INVITE of the dialog. Note that there is NO ROUTE header in the ACK message. As there is serial forking here, the ACK is generated by the Proxy 1 itself. Any hint would be appreciated, Best Regards, Minh Phan [image: image.png]

3 2

RTP Proxy with Local IP and Public IP
by Vijo Jose 13 Dec '21

13 Dec '21

Hai Everyone. I have configured the RTP Proxy with Kamailio SIP Proxy Server. Where I have my Kamailio is configured with private IP 10.0.0.1 and Public UP 103.XX.XX.XX and the SIP user is connecting with RTP proxy with local IP 10.0.0.1 to register. I also have a SIP Asterisk server on the public Internet with IP 90.XX.XX.XX that makes the call to sipuser@103.XX.XX.XX:5060 which is coming on the sip proxy server and the sip proxy server forwards those packets to the SIP user who is registered with local IP 10.0.0.5. Once the call is answered the RTP is started to send from the SIP server to the SIP Proxy server over the public IP from 90.XX.XX.XX to 103.XX.XX.XX which is working as expected. But from the sip user 10.0.0.5 the RTP is flowing to Proxy server public IP 103.XX.XX.XX instead of RTP Proxy server Localip 10.0.0.1. How can we configure the same? Presently I have started my RTP proxy server with command /usr/local/bin/rtpproxy -F -A 103.XX.XXXX -l 10.0.0.1 -m 10000 -M 20000 -s udp:127.0.0.1:7722 -d DBUG:LOG_LOCAL5 Thanks in advance.

3 2

Re: [SR-Users] Manipulation of request-line
by Mihovil Kolaric 12 Dec '21

12 Dec '21

Hi, unfortunately, Alex is right: manipulations ot the request-URI do not seem to re-write the whole line, the malformed line-ending (SIP/2.0<blank><CR><LF>) remains in the forwarded message.

2 2

remove rport in INVITE Via HDR and make kamailio behave asymmetric
by Nuno Miguel Reis 11 Dec '21

11 Dec '21

Hi guys. I've a scenario here where I'm receiving inbound traffic from a Mitel PBX on a LAN environment with a bunch of router hops between kamailio and the Mitel. Sometimes, not always, I get traffic from the MItel PBX where the source port is changed in transit (some kind of NAT, still don't know where exactly) from 5060 to a dynamic port different from 5060. Every INVITE comes with rport in via header as: .. Via: SIP/2.0/UDP 10.21.252.35:5060 ;branch=z9hG4bK-524287-1---d6bac01809527627*;rport* .. when this happens kamailio sends all the replies to the $si:$sp symmetrically (force_rport behavior) and I would like to force the opposite instead, making it asymmetric and sending the traffic to $si:5060 everytime. I'm having a hard time forcing the *unforce*_rport() behavior. Does anyone have a good suggestion for this? Looking forward to hear from you. Cheers, -- Nuno Miguel Reis Departamento de Engenharia Informática Faculdade de Ciências e Tecnologia Universidade de Coimbra

1 1

Unquoted values from #!defenv
by Ben Kaufman 09 Dec '21

09 Dec '21

Hello all, Looking for some clarification regarding quoting and !#defenv . I understand that the example below fails because the environmental variable HOME is not quoted, thus when used in the xlog() call it fails. How is it possible to evaluate and/or use the value of the environmental variable if defined as a preprocessor variable? Looking at the documentation the reason for this directive is "It is a simplified alternative of using #!substdef with $env(NAME) in the replacement part." But #!substdef would allow setting the value inside of a quoted string, so does it really meet that requirement? I'm aware that I could use $env(HOME) rather than a preprocessor directive of HOME. I'm just trying to understand the usage of the #!defenv feature. #!KAMAILIO ## Tested in 5.5.2 loadmodule "xlog" loadmodule "pv" loadmodule "evrexec" modparam("evrexec", "exec", "name=evrexec:timer;wait=1000;workers=1;") #!defenv HOME request_route{ forward(); } event_route[evrexec:timer] { xlog("L_N", "HOME: " + HOME + "\n"); } Ben Kaufman

3 15

wireshark decode kamailio / rtpengine ng messages
by Karsten Horsmann 08 Dec '21

08 Dec '21

Hi List, maybe someone wrote a wireshark helper (didnt know the right term) to view kamailio to rtpengine communication in human form? Some hints would be great. -- Mit freundlichen Grüßen *Karsten Horsmann*

2 1

Re: [SR-Users] wireshark decode kamailio / rtpengine ng messages
by Alex Balashov 08 Dec '21

08 Dec '21

That sounds far too niche for a helper, though, then again, Wireshark has some phenomenally exotic helpers. — Sent from mobile, with due apologies for brevity and errors. > On Dec 8, 2021, at 8:14 AM, Karsten Horsmann <khorsmann(a)gmail.com> wrote: >

1 0

Kamailio v5.3.9 Released
by Daniel-Constantin Mierla 08 Dec '21

08 Dec '21

Hello, Kamailio SIP Server v5.3.9 stable release is out. This is a maintenance release of the old stable branch, 5.3, that includes fixes since the release of v5.3.8. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.3.x. Deployments running previous v5.3.x versions are strongly recommended to be upgraded to v5.3.9 or even better to v5.4.x or 5.5.x series. For more details about version 5.3.9 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/12/kamailio-v5-3-9-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.3 is an old stable branch, v5.3.9 being the last planned release out of it, to mark the end of official maintenance. The maintained stable branches are now 5.4 and 5.5, at this time with v5.5.3 being the latest stable release. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Re: [SR-Users] Manipulation of request-line
by Alex Balashov 08 Dec '21

08 Dec '21

That will manipulate the request URI, but not the request line. — Sent from mobile, with due apologies for brevity and errors. > On Dec 7, 2021, at 4:16 PM, Karsten Horsmann <khorsmann(a)gmail.com> wrote: >

2 1

Releasing Kamailio 5.3.9 - last in 5.3.x series
by Daniel-Constantin Mierla 08 Dec '21

08 Dec '21

Hello, it is time to mark the end of official packaging for 5.3.x releases, therefore during the next days I am going to cut the v5.3.9 release from branch 5.3, likely on Wednesday, Dec 8, 2021. In other words, if no major regression is detected shortly after this release, the v5.3.9 is going to be the last one from the 5.3 branch. It is strongly recommended to move to a series that is under active maintenance, respectively 5.5.x or 5.4.x. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online Feb 21-24, 2022 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

HTTP Requests for API routing - Question on which module to use with KSR
by Emilio Panighetti 08 Dec '21

08 Dec '21

Looking into using Kamailio to route calls via an HTTP API. Basic scenario is this: INVITE comes in (no registration). And Kamailio sends an HTTP request to a server with data extracted from the INVITE. Based on the response, call KSR.setdsturi() and other actions like normalizing phone numbers, etc. (Not sure if changing Contact: headers would be a better option). For now I want to be able to make a simple call routing as a proof of concept. Planning on using Lua as a KEMI interpreter. Looking at different modules: http_client http_client_async xhttp Which module would be more appropriate? http_client_async provides a simple async method and callback, so the SIP threads can continue processing requests while the API server is preparing the response. But the call has to be parked (How is this done?) and this is also an overhead. http_client seems straightforward, but the SIP threads are tied up waiting for HTTP responses. Also looking at the KEMI documentation, the KSR function calls for HTTP_CLIENT doesn’t seem to match the config function documentation. For example, In KEMI manual: KSR.http_client.curl_connect_post() doesn’t have a corresponding in kamailio.cfg. So which would be the preferred approach? Also examples would be appreciated. Thanks in advance!

1 0

Manipulation of request-line
by Mihovil Kolaric 07 Dec '21

07 Dec '21

Hi, I have an issue with a SIP-client, that occasionally puts a blank between the version SIP/2.0 and the CRLF at the and of the request-line. (i.e. sends "ACK <uri> SIP/2.0 \r\n" instead of "ACK <uri> SIP/2.0\r\n"). Kamailio (as well as most SIP UAs) does not care about that error and successfully processes/forwards the request (also when using sanity_check()). But I also deal with a client that fails to parse that request. (Furthermore, wireshark's dissector fails to recognize such malformed messages as SIP, which makes debugging even harder). I tried to fix this issue using textops, but all functions I tried operate only on headers or message body, but do not seem to affect the request line. Is there any possibility to modify the request-line, or to replace it with a new one? Best Regards, Mihovil

2 1

Announcing public beta release of TeamsPhone - powered by Kamailio
by Sergiu Pojoga 06 Dec '21

06 Dec '21

Hello Kamailio-nians, Just to bug everyone quickly: today I'm happy to announce the public beta release of *TeamsPhone <https://teamsphone.net>*, a MS Teams <=> PBX integration solution for ITSPs, IP-PBX service providers and integrators, *powered by Kamailio*. Unlike other similar services offered as SaaS pay-per-user model, our product is oriented for ITSPs to be self-hosted and fully integrated into one's telecom network, providing an add-on service to supplement any Hosted PBX offering with seamless calling using Microsoft Teams *as-as-softphone*, or as we like to call it - TeamsPhone. Some insights about the platform: - 100% automation of MS Teams Direct Routing provisioning - multi-tenant application - API-driven - Microservices oriented architecture - RabbitMQ-powered Message Broker distribution - SIP server (you guessed it - Kamailio, of course!) Seeing how it works is worth a thousand words. A cloud *demo* instance is available at https://my.teamsphone.net for anyone to try it out, use it or abuse it. If you have questions about the product - feel free to contact me in private. Respectfully, Sergiu Pojoga Founder, teamsphone.net sergiu(a)teamsphone.net

1 0

detecting compact headers?
by Brooks Bridges 06 Dec '21

06 Dec '21

We have an internal component of our callflow that does not support compact headers (vendor says it's on the roadmap but no eta, etc) so I'm trying to find a clean way to detect if a message has compact headers and reject it. I haven't had much luck in finding a way to identify specifically if any of the headers of the message are compact however. Can anyone point me in a direction please? Thanks! Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.

3 3

ENV Values in cfg
by H Yavari 06 Dec '21

06 Dec '21

Hi to all, Is it possible to set modules parameters with env values? I know that in routes we can use $env(NAME), but what about for other parameters? for example setting DB address in K8s cluster ENV values. Regards,Hossein

2 1

DMQ Usrloc/Dialog - Experiences
by Carsten Bock 03 Dec '21

03 Dec '21

Hi, I wanted to quickly ask the group about experiences with DMQ and Usrloc/Dialog. I don't expect any issues when choosing such an approach, especially since we would have re-transmits for a message (fr_timer = 30 seconds) if we did not receive any answers or scenarios alike. So I assume, having short "outages" (less than 30 seconds) for the communication is just fine. So far I used DMQ in a non-IMS setup for synchronizing usrloc with ~15k Subscribers and it worked really well. One concern brought up (not by me) was, that synchronizing usrloc with DMQ might not be reliable at scale. I would also love to understand how to treat situations when the communication is lost for a longer period of time (e.g. if the communication between nodes is lost for 5 minutes?). Can anyone share some real-life experiences? Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock

3 5

topos xavu_field_contact_host kamailio 5.5
by Jonathan Hunter 03 Dec '21

03 Dec '21

Hi All, I was wondering if anyone can help, and advise me if I am missing something when using topos in an environment where I have more than one interface for kamailio. Essentially I would like to set the contact_host to 2 different values depending on the flow of the SIP requests, as we have a private LAN interconnect for example 10.10.10.10, and a public interconnect using 2.2.2.2 (for example). I notice there is xavu for A-side contact and B-side contact, but what about just the contact host? As I have set for example; modparam("topos", "xavu_cfg", "_tps_") modparam("topos", "xavu_field_contact_host", "contact_host") ... $xavu(_tps_=>contact_host) = "2.2.2.2"; And this works fine but obviously sets the contact_host to 8.8.8.8 across both interfaces, I ideally want it to change between 10.10.10.10 and 2.2.2.2. How can I set more than one contact_host $xavu that topos can use? As my understanding is you can only set $xavu once, so is there another way to manipulate the contact_host on requests coming in and out on different interfaces? I assume I am missing something? :) Thanks in advance Jon Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

2 1

NIST advisory
by David Villasmil 02 Dec '21

02 Dec '21

Anyone knows about this? https://nvd.nist.gov/vuln/detail/CVE-2020-28361 -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 4

Re: [SR-Users] probles with listen advertise address trying to be resolved
by Richard Robson 01 Dec '21

01 Dec '21

no the problem appear to be with the advertise this makes all listeners listen = PRIV_SOCK advertise MY_PUB_SOCK name = "ext" but listen = PRIV_SOCK_TLS advertise MY_PUB_SOCK_TLS name = "ext_tls" is failing with a look up error on MY_PUB_SOCK_TLS if I try : listen = PRIV_SOCK_TLS advertise "MY_PUB_SOCK_TLS" name = "ext_tls" it fails on a lookup for what ever the def is for that variable e.g. 1.2.3.4:5061 the defs are of the correct syntax if it replace the defs it works e.g listen = tls:10.10.10.10:5061 advertise 1.2.3.4:5061 name = "ext_tls" the two defs math the text above the problen is its working for the "global" defs without any protocl, so its making the tls listener for the wrong port as 5060 so listen = LISTEN_EXTERNAL_SOCKET advertise ADVERTISE_NAT_ADDRESS name = "ext" is working with #!substdef "!LISTEN_EXTERNAL_SOCKET!10.10.10.10:5060!g" and #!substdef "!ADVERTISE_NAT_ADDRESS!1.2.3.4:5060!g" the _TLS versions are not changing the tls port so i have tls on port 5060 when iot should be on 5061 and the name ext_tls where all other sockets are called "ext" Regards, Richard On 30/11/2021 20:03, Karsten Horsmann wrote: > Hi Richard, > > Hmmm for some reason I split my vars into parts. > > And you prefix that with tls? Like this? > > "!ADVERTISE_NAT_ADDRESS_TLS!tls:1.2.3.4:5061!g" > > Best > Karsten > > Richard Robson <richard(a)rikrobson.co.uk> schrieb am Di., 30. Nov. > 2021, 17:48: > > Hi > > > the missing = was my typo in the email and not the config. > > the probelm is only with the TLS advertise and not the non tls > advertise > > these work as expected > > listen = LISTEN_EXTERNAL_SOCKET advertise ADVERTISE_NAT_ADDRESS > name = "ext" > > #!substdef "!ADVERTISE_NAT_ADDRESS!1.2.3.4:5060!g" > > > these do not works > > #!substdef "!ADVERTISE_NAT_ADDRESS_TLS!1.2.3.4:5061!g" does not work > > listen = LISTEN_EXTERNAL_SOCKET_TLS advertise > ADVERTISE_NAT_ADDRESS_TL name = "ext-tls" > > or > > listen = LISTEN_EXTERNAL_SOCKET_TLS advertise > ADVERTISE_NAT_ADDRESS_TLS name = "ext-tls" > > > > if its not quoted then error = cannot resolve 1.2.3.4:5061 > <http://1.2.3.4:5061> of not quoted error = cannot resolve > ADVERTISE_NAT_ADDRESS_TLS > > > if i replace the def with the 1.2.3.4:5061 <http://1.2.3.4:5061> > it works > > > what is hte difference if also changed the name to > ADVERTISE_NAT_ADDRESS_SEC with the same results > > > > > On 30/11/2021 16:21, Karsten Horsmann wrote: >> Hi Richard, >> >> seems that you forgot the equal signs in the listen directive. >> Did kamailio -c -f /etc/kamailio/kamailio.cfg return something? >> http://www.kamailio.org/wiki/cookbooks/devel/core#listen >> >> I did the same with puppet. And I only manipulate my >> /etc/kamailio/kamailio-local.cfg with the configuration >> management tool. >> Small example from my templating. >> >> grep MY_PUB_IP /etc/kamailio/kamailio-local.cfg >> #!substdef "!MY_PUB_IP!1.2.3.4!g" >> .... >> egrep 'MY_HTTPS_ADDR|MY_PUB_IP|_PORT' /etc/kamailio/kamailio.cfg >> import_file "kamailio-local.cfg" >> .... >> #!substdef "!MY_HTTPS_ADDR!tls:MY_PUB_IP:MY_WSS_HTTPS!g" >> .... >> listen=udp:MY_PUB_IP:5060 >> listen=tcp:MY_PUB_IP:5060 >> listen=tls:MY_PUB_IP:5061 >> listen=MY_HTTPS_ADDR >> >> Kind regards >> Karsten >> >> Am Di., 30. Nov. 2021 um 16:57 Uhr schrieb Richard Robson >> <richard(a)rikrobson.co.uk>: >> >> I have a problem when trying to add an advertised address in >> Kamailio 5.4.2 >> >> >> we have a checf config that is populating various variable. >> some of these are for the Listeners >> >> >> >> we have this working and Im getting all protocols for the >> listeners based on the non _TLS Vars but the TLS config is >> trying to resolve ADVERTISE_NAT_ADDRESS_TLS. If I try and >> quote the variable "ADVERTISE_NAT_ADDRESS_TLS" id get an >> error saying 1.2.3.4:5061 <http://1.2.3.4:5061> is not resolvable >> >> >> therefroe I have udp,tcp and tls listeners all on the default >> ports where i need the tls on port 5061 ans not 5060 >> >> >> listen = LISTEN_EXTERNAL_SOCKET advertise >> ADVERTISE_NAT_ADDRESS name = "ext" >> >> listen = LISTEN_INTERNAL_SOCKET name = "int" >> >> listen = LISTEN_EXTERNAL_SOCKET_TLS advertise name = "ext-tls" >> >> listen = LISTEN_INTERNAL_SOCKET_TLS name = "int-tls" >> >> the Vars are defined as >> >> #!define TOPO_NAT >> >> #!substdef "!LISTEN_EXTERNAL_SOCKET!10.10.10.10:5060!g" >> >> #!substdef "!LISTEN_INTERNAL_SOCKET!10.10.10.10:5080!g" >> >> #!substdef "!ADVERTISE_NAT_ADDRESS!1.2.3.4:5060!g" >> >> #!define ENABLE_TLS >> >> #!define TLS_CONFIG_FILE "chef-managed/tls.cfg" >> >> #!substdef "!LISTEN_EXTERNAL_SOCKET_TLS!tls:10.225.73.16:5061!g" >> >> #!substdef "!LISTEN_INTERNAL_SOCKET_TLS!tls:10.225.73.16:5061!g" >> >> #!substdef "!ADVERTISE_NAT_ADDRESS_TLS!1.2.3.4:5061!g" >> >> REgards, >> >> >> Richard >> >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions >> * sr-users(a)lists.kamailio.org >> Important: keep the mailing list in the recipients, do not >> reply only to the sender! >> Edit mailing list options or unsubscribe: >> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> >> >> -- >> Mit freundlichen Grüßen >> *Karsten Horsmann* >> >> __________________________________________________________ >> Kamailio - Users Mailing List - Non Commercial Discussions >> *sr-users(a)lists.kamailio.org >> Important: keep the mailing list in the recipients, do not reply only to the sender! >> Edit mailing list options or unsubscribe: >> *https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >

2 1

Using path with DMQ to send calls to origin SBC - not sure when to modify destination URI
by Rhys Hanrahan 01 Dec '21

01 Dec '21

Hi Everyone, I am trying to add DMQ for redundancy of registrations and USRLOC, and I’m trying to send calls to the correct SBC that is the original registrar for a handset. I’ve been using the thread here where Charles gave some guidance on how to use path to store and use the original SBC: https://lists.kamailio.org/pipermail/sr-users/2018-February/100246.html and https://lists.kamailio.org/pipermail/sr-users/2013-September/079736.html I am struggling with when to decide to modify the destination URI. My testing shows this is required otherwise some handsets will ignore the invite, but right now I am doing it in a blanket form, right before SIPOUT (which is where the origin SBC handles the invite instead of LOCATION). I am sure this is being too heavy-handed though and there are some cases where I won’t want to set this, but I am not sure which? # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) { record_route(); } … xlog("Setting du according to path. Current du is $du\n"); xlog("Current route header: $(hdr(Route))\n"); xlog("Current route: $(hdr(Route){uri.host})\n"); >>> $du = $(hdr(Route){param.value,received}); #xlog("New du destination uri is: $du\n"); # dispatch requests to foreign domains route(SIPOUT); In the linked threads, Charles mentioned that only the last-hop registrar should make this change, but what’s the best way to determine if I am on the last-hop registrar? As per the snippet above, I tried using the {uri.host} transformation to extract the origin SBC’s IP from the route header. My plan is to then compare this against “myself” but I am struggling to extract the right info from the route header. And I am not even sure if this is the right general approach? The route header looks like this: <sip:ORIGIN_SBC_IP:5060;received=sip:UAC_WAN_IP:2048;lr> Any guidance or examples would be appreciated. Thanks! Rhys Hanrahan | Chief Information Officer e: rhys(a)nexusone.com.au<mailto:rhys@nexusone.com.au> [www.nexusone.com.au]<http://www.nexusone.com.au/> [signature_555064778] <http://www.fusiontech.com.au/> NEXUS ONE | FUSION TECHNOLOGY SOLUTIONS p: 1800 NEXUS1 (1800 639 871) or 1800 565 845 | a: Suite 12.03 Level 12, 227 Elizabeth Street, Sydney NSW 2000 www.nexusone.com.au<http://www.nexusone.com.au/> | www.fusiontech.com.au<http://www.fusiontech.com.au/> The information in this email and any accompanying attachments may contain; a. Confidential information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties; b. Legally privileged information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties; and or c. Copyright material Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties. If you have received this email in error, please notify the sender immediately and delete this message. Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd does not accept any responsibility for loss or damage arising from the use or distribution of this email. Please consider the environment before printing this email.

2 5

Re-writing presentity domain for DMQ
by Rhys Hanrahan 01 Dec '21

01 Dec '21

Hi Everyone, I am trying to get DMQ working for presence/dialog notifications. Presence works fine locally on the same SBC. The DMQ part itself is also working fine and I can see that the entries in presentity are being replicated between my DMQ nodes. The problem is that when the presentity records are being replicated from another SBC, the domain for that record stays as the IP of the original SBC. Then when the local_watchers is populated, the presentity_uri doesn’t match, and no NOTIFY packets are sent as a consequence. What am I missing here? I can’t see anything in the docs about how to handle this, and I can’t find any examples in the list on how to handle this either, which suggests it isn’t as common of an issue at it seems. See example of what I see in the presentity table below. In this case handset 103 is subscribed to BLFs for 103 and 104. A call came into 103 and generated an early state dialog in the presentity table. MariaDB [kamailio]> select * from presentity; +-------+-------------+--------------+--------+-- | id | username | domain | event | +-------+-------------+--------------+--------+-- 27100 | nexusone103 | x.x.x.53 | dialog | I have modified my registrations and have re-written my SUBSCRIBE and PUBLISH packet headers so that everything uses a common FQDN for both SBCs, that does DNS RR to both SBC IPs. I am also registering from the handset using this FQDN now, and yet although my active_watchers table now expects a presentity URI of XXX(a)sbc.fqdn<mailto:XXX@sbc.fqdn>, the presentity table is still using the IP addresses of the individual node that originated the dialog. MariaDB [kamailio]> select presentity_uri,watcher_username,watcher_domain,event from active_watchers; +----------------------------------------------+------------------+----------------------+-----------------+ | presentity_uri | watcher_username | watcher_domain | event | +----------------------------------------------+------------------+----------------------+-----------------+ | sip:104@sbc.fqdn | nexusone103 | sbc.fqdn | dialog | | sip:103@sbc.fqdn | nexusone103 | sbc.fqdn | dialog | +----------------------------------------------+------------------+----------------------+-----------------+ I’m out of ideas unfortunately. Any advice would be appreciated. Thanks! Rhys Hanrahan | Chief Information Officer e: rhys(a)nexusone.com.au<mailto:rhys@nexusone.com.au> [www.nexusone.com.au]<http://www.nexusone.com.au/> [signature_1328564021] <http://www.fusiontech.com.au/> NEXUS ONE | FUSION TECHNOLOGY SOLUTIONS p: 1800 NEXUS1 (1800 639 871) or 1800 565 845 | a: Suite 12.03 Level 12, 227 Elizabeth Street, Sydney NSW 2000 www.nexusone.com.au<http://www.nexusone.com.au/> | www.fusiontech.com.au<http://www.fusiontech.com.au/> The information in this email and any accompanying attachments may contain; a. Confidential information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties; b. Legally privileged information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties; and or c. Copyright material Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties. If you have received this email in error, please notify the sender immediately and delete this message. Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd does not accept any responsibility for loss or damage arising from the use or distribution of this email. Please consider the environment before printing this email.

1 0

probles with listen advertise address trying to be resolved
by Richard Robson 30 Nov '21

30 Nov '21

I have a problem when trying to add an advertised address in Kamailio 5.4.2 we have a checf config that is populating various variable. some of these are for the Listeners we have this working and Im getting all protocols for the listeners based on the non _TLS Vars but the TLS config is trying to resolve ADVERTISE_NAT_ADDRESS_TLS. If I try and quote the variable "ADVERTISE_NAT_ADDRESS_TLS" id get an error saying 1.2.3.4:5061 is not resolvable therefroe I have udp,tcp and tls listeners all on the default ports where i need the tls on port 5061 ans not 5060 listen LISTEN_EXTERNAL_SOCKET advertise ADVERTISE_NAT_ADDRESS name = "ext" listen LISTEN_INTERNAL_SOCKET name = "int" listen LISTEN_EXTERNAL_SOCKET_TLS advertise name = "ext-tls" listen LISTEN_INTERNAL_SOCKET_TLS name = "int-tls" the Vars are defined as #!define TOPO_NAT #!substdef "!LISTEN_EXTERNAL_SOCKET!10.10.10.10:5060!g" #!substdef "!LISTEN_INTERNAL_SOCKET!10.10.10.10:5080!g" #!substdef "!ADVERTISE_NAT_ADDRESS!1.2.3.4:5060!g" #!define ENABLE_TLS #!define TLS_CONFIG_FILE "chef-managed/tls.cfg" #!substdef "!LISTEN_EXTERNAL_SOCKET_TLS!tls:10.225.73.16:5061!g" #!substdef "!LISTEN_INTERNAL_SOCKET_TLS!tls:10.225.73.16:5061!g" #!substdef "!ADVERTISE_NAT_ADDRESS_TLS!1.2.3.4:5061!g" REgards, Richard

2 2

Kamailio and RTPEngine acting as SBC : wrong IP address returned
by Cyril Ramière 28 Nov '21

28 Nov '21

Hi there, I'm already using Kamailio as a simple proxy and it worked flawlessly. This time, I need to have a new setup like this: [UAC (sip phone)] <--- register & has to deal only with ----> | PUBLIC | [Kamailio + RtpEngine] | PRIVATE | <----> [Asterisk] Client = 37.100.100.100 (public) Asterisk = 172.17.200.20 (private) Kamailio/RtpEngine = 172.17.203.102 (private, advertising 3.99.99.99 public IP) Kamailio and RtpEngine will behave as a SBC/B2BUA, the client will deal only with kamailio using public access (internet), and asterisk will handle the calls but stays 100% private behind kamailio. Kamailio will handle registrations to reduce the load put on the asterisk boxes. The setup is running on AWS, my Kamailio has 1 Private IP address tied to 1 Public IP address (an Elastic public IP) so, no multi-homing, one network interface. I made a "simple" work in progress configuration, the registration is working as a PoC, and my calls are *almost* working but with some nonsense. My Main issue is that when my UAC (SIP phone) make a call, to let's say +1000, the call enters kamailio, then kamailio handle the invite, trigger rtpEngine, but the IP addresses in Record-Route and Via headers are wrong. >From Kamailio to UAC Sip Phone, it seems OK. But from Kamailio to Asterisk, the record-route/via headers are set with Kamailio Public IP when it should be the Kamailio private IP. So, when Asterisk sends a BYE, it tries to send it to the public IP of Kamailio, which is wrong. There are probably other quirks in the configuration but this one, I can't figure out what's wrong. I'm attaching a capture file, a log file and my configuration file (some informations are redacted). I am missing something and sadly I can't figure out what, a little help would be appreciated :) Regards

2 1

Problem implementing Outbound Proxy
by Christoph Russow 26 Nov '21

26 Nov '21

Hi all, im currently trying to add a Outbound Proxying to our system which right now does inbound loadbalancing for our application servers. Current: Inbound SIP Trunk -> Kamailio -> dispatcher -> ApplicationServer 1..n i now want to add the ability for our internal Application Servers to terminate their outbound calls through the kamailio system. currently i've setup a gateway in the (freeswitch) application server that has the kamailio system set as outbound-proxy. this leads to sip calls started with originate sofia/gateway/kamailio/<number>@<outbound carrier IP> to be sent to the kamailio system which then forwards it to the given carrier IP. Sadly our main carrier answers with "503 service unavailable - no bandwith available". (maybe due to the internal ip-addresses within some of the headers?) i've attached our current kamailio configuration and also a pcap of a call i tried to start with our main carrier. i tried this way as it seemed to be the easiest way so our application servers still can select the outbound carrier within their flow. maybe i'm on the wrong way here and need to solve this problem in a completely different way i don't know. TLDR: sip proxying does not work as expected. need a way to achieve outbound calls routed through kamailio from internal application servers any hint/help into the right direction is appreciated Best Regards Christoph Russow -- ________________________________________________________________ EMTEX GmbH Christoph Russow Software Engineer Bischof-Otto-Weg 9 D-91086 Aurachtal Geschäftsführer: Markus Enzinger Tel. +49 9132 7490 0 Sitz der Gesellschaft: 91086 Aurachtal Fax. +49 9132 7490 900 Amtsgericht Fürth: HRB6804 ________________________________________________________________

3 11

Call limiting with Kamailio
by Olli Attila 26 Nov '21

26 Nov '21

Hello, What choices do I have to implement a feature to Kamailio which would limit calls per customer? The environment: Two kamailio nodes sitting in different sites and they are not aware of each others sessions/dialogs and thus serving customer calls independently. Configurations on the nodes are identical excluding ip addresses. Customer call can be routed through either one of these Kam nodes. The two nodes share a common external mysql database from which all dialplan and htable entries are loaded (used in call routing for example). Customers are identified based on IP address & tel numbering and as a final result we are populating an variable which holds the customer id $var(REALM_NAME) when the identification has been done. The call limiting should be "tagged/profiled" somehow with this information if possible. Any suggestions which way to go with this? Initial ideas if one of these are worth of setting a starting point: -> Counting calls with htable and replicating with DMQ to other node (can the data survive from a restart?) -> Using the common mysql database to hold the counted calls from where both kam nodes could load data? (database load increasing?) -> Some new exciting module for this job? Cheers, Olli

4 3

cannot adopt OIDs in KAMAILIO-SIP-COMMON-MIB
by Arun Bonela 26 Nov '21

26 Nov '21

Hi we have configured snmp module on our Kamailio server following https://www.kamailio.org/dokuwiki/doku.php/utils:kamailio-and-snmp guidance. Description we could able to poll or snmpwalk most of the OIDs in KAMAILIO-REG-MIB , KAMAILIO-SIP-SERVER-MIB but having issues below from KAMAILIO-SIP-COMMON-MIB snmpd[358730]: Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatsMethod ::= { kamailioSIPMethodStatsEntry 1 } Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatsOutbounds ::= { kamailioSIPMethodStatsEntry 2 } Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatsInbounds ::= { kamailioSIPMethodStatsEntry 3 } Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatusCodeMethod ::= { kamailioSIPStatusCodesEntry 1 } Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatusCodeValue ::= { kamailioSIPStatusCodesEntry 2 } Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatusCodeIns ::= { kamailioSIPStatusCodesEntry 3 } Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatusCodeOuts ::= { kamailioSIPStatusCodesEntry 4 } Cannot adopt OID in KAMAILIO-SIP-COMMON-MIB: kamailioSIPStatusCodeRowStatus ::= { kamailioSIPStatusCodesEntry 5 } Troubleshooting root@host# snmpwalk -v2c -c public localhost .1.3.6.1.4.1.34352.3.1.1.1.4.1.1.2.0 SNMPv2-SMI::enterprises.34352.3.1.1.1.4.1.1.2.0 = No Such Object available on this agent at this OID root@host# snmpwalk -v2c -c public localhost .1.3.6.1.4.1.34352.3.1.1.1.4.1.1.2 SNMPv2-SMI::enterprises.34352.3.1.1.1.4.1.1.2 = No Such Object available on this agent at this OID Reproduction using snmpwalk or snmget to any of the above mentioned kamailioSIPStats* OIDs will do Additional Information * Kamailio Version - output of kamailio -v version: kamailio 5.5.1 (x86_64/linux) 307af8-dirty * Operating System: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Any advice, why we seeing this issue for these OIDs ? Are these decremented now ? Regards, Arun Bonela Arun Bonela UCaaS Ops – Technical Lead Tel: 0333 043 7319 Mobile: 07468 728 007 Email: Arun.Bonela(a)gamma.co.uk This is an email from Gamma Telecom Ltd, trading as “Gamma”. The contents of this email are confidential to the ordinary user of the email address to which it was addressed. This email is not intended to create any legal relationship. No one else may place any reliance upon it, or copy or forward all or any of it in any form (unless otherwise notified). If you receive this email in error, please accept our apologies, we would be obliged if you would telephone our postmaster on +44 (0) 808 178 9652 or email postmaster(a)gamma.co.uk Gamma Telecom Limited, a company incorporated in England and Wales, with limited liability, with registered number 04340834, and whose registered office is at 5 Fleet Place, London, EC4M 7RD and whose principal place of business is at Kings House, Kings Road West, Newbury, Berkshire, RG14 5BY.

2 2

Re: [SR-Users] How to not write logs to journald with kamailio
by Ginhoux, Patrick 26 Nov '21

26 Nov '21

Hi, I resend this mail because of the initial destination address was not correct. The topic was a logging problem : With the upgrade of my SIP Router proxies to RHEL 7 (and Kamailio 5.0.7) , we encounter problems where the logs are blocked to be written in the syslog. This problem is similar as the one reported in this article : [SR-Users] Kamailio logs in RHEL 7 environment <https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html> . The resolution was to increase some journald/rsyslog settings (RateLimitBurst=1000000 / $imjournalRatelimitInterval 1 $imjournalRatelimitBurst 500000). But it is somehow a workaround. Im looking to know if it should be possible for kamailio to write directly the logs to the syslog only. Thanks in advance to those can help me. Regards Patrick Ginhoux De : Ginhoux, Patrick Envoyé : lundi 22 novembre 2021 16:49 À : 'sr-users' <sr-users-bounces(a)lists.kamailio.org> Objet : How to not write logs to journald with kamailio Hi, With the upgrade of my SIP Router proxies to RHEL 7 (and Kamailio 5.0.7) , we encounter problems where the logs are blocked to be written in the syslog. This problem is similar as the one reported in this article : [SR-Users] Kamailio logs in RHEL 7 environment <https://lists.kamailio.org/pipermail/sr-users/2018-April/101065.html> . The resolution was to increase some journald/rsyslog settings (RateLimitBurst=1000000 / $imjournalRatelimitInterval 1 $imjournalRatelimitBurst 500000). But it is somehow a workaround. Im looking to know if it should be possible for kamailio to write directly the logs to the syslog only. Thanks in advance to those can help me. Regards Patrick Ginhoux

5 5

JSON Error
by Daniel W. Graham 26 Nov '21

26 Nov '21

My log is filled with this and have been unsuccessful locating additional information by increasing debug level. Any thoughts on how to quickly isolate? /usr/local/sbin/kamailio[7678]: ERROR: jansson [jansson_funcs.c:48]: janssonmod_get_helper(): json error at line 1, col 0: '[' or '{' expected near end of file /usr/local/sbin/kamailio[7677]: ERROR: jansson [jansson_funcs.c:46]: janssonmod_get_helper(): failed to parse json: /usr/local/sbin/kamailio[7677]: ERROR: jansson [jansson_funcs.c:48]: janssonmod_get_helper(): json error at line 1, col 0: '[' or '{' expected near end of file /usr/local/sbin/kamailio[7675]: ERROR: jansson [jansson_funcs.c:46]: janssonmod_get_helper(): failed to parse json: /usr/local/sbin/kamailio[7675]: ERROR: jansson [jansson_funcs.c:48]: janssonmod_get_helper(): json error at line 1, col 0: '[' or '{' expected near end of file -dan

3 5

LCR Module not loading all rules from DB
by Juha Heinanen 25 Nov '21

25 Nov '21

If your db supports DB_CAP_FETCH, lcr rules are loaded from the db 1024 rows per cycle. You could check what you get to syslog from this statement after you set log level to debug level and then execute lcr.reload: LM_DBG("loading, cycle %d with <%d> rows\n", n++, RES_ROW_N(res)); -- Juha

1 0

Problem with 302
by nathan Kirk 24 Nov '21

24 Nov '21

Hello, First time poster and I am stuck. I am using K as a mid registar to several AST boxes. The problem I am having is if AST or the END USER DEVICE sends a 302 for some reason I am getting a 500 THEN the 302 to the END USER DEVICE or AST depending which direction the call flow is. Example END USER DEVICE -> CALLS 700 -> K -> AST AST -> 302 -> K -> 500 & 302 -> END USER DEVICE What I would like to happen is when K receives the 302 it deals with it directly and it is not handed off to either end. I am using a configuration I found online with some base modifications to dip into the database real time to get the AST box IPS Any direction would be helpful. Thank you, Nathan

1 0

LCR Module not loading all rules from DB
by M Arqum CH 24 Nov '21

24 Nov '21

Hi all, lcr.reload command not loading all rules from rules table. More than 73K rules row in table, lcr.dump_rules only print 4096 rules. lcr module config : modparam("lcr", "db_url", "cluster://k1") modparam("lcr", "lcr_gw_table","lcr_gateways") modparam("lcr", "lcr_rule_table", "lcr_rules") modparam("lcr", "lcr_rule_target_table", "lcr_rule_targets") modparam("lcr", "gw_name_column", "gw_name") modparam("lcr", "ip_addr_column", "ip") modparam("lcr", "lcr_id_column", "lcr_id") modparam("lcr", "gw_uri_avp", "$avp(gw_uri_avp)") modparam("lcr", "ruri_user_avp", "$avp(ruri_user_avp)") modparam("lcr", "flags_avp", "$avp(s:cSId)") modparam("lcr", "flags_column", "cSId") modparam("lcr", "defunct_capability", 1) modparam("lcr", "lcr_id_avp", "$avp(lcr_id_avp)") modparam("lcr", "defunct_gw_avp", "$avp(defunct_gw_avp)") modparam("lcr", "lcr_rule_hash_size", 1024) modparam("lcr", "lcr_gw_count", 1024) modparam("lcr", "fetch_rows", 3000) modparam("lcr", "ping_interval", 15) # Ping every 15 seconds modparam("lcr", "ping_inactivate_threshold", 1) # Mark as inactive at first call of inactivate_gw() modparam("lcr", "ping_valid_reply_codes", "403,404,405,501") # Mark as active when 2XX or these reply codes modparam("lcr", "ping_from", "sip:lcr@mydomain.com") modparam("lcr", "lcr_count", 1) modparam("lcr", "dont_strip_or_prefix_flag", 1) modparam("lcr", "rule_id_avp", "$avp(lcr_rule_id)") modparam("lcr", "priority_ordering", 1) modparam("lcr", "ping_socket", "10.16.16.16:5060") Thanks & Regards -- Regards M Arqum

3 5

t_suspend() / t_continue() create new branches
by Sebastian Damm 24 Nov '21

24 Nov '21

Hi, I have the following weird problem. A Kamailio (5.4.x) with some asynchronous permission logic suspends outgoing INVITEs and resumes them after the answer of the permission system. Everything works as expected when the call is answered. However, when the called party rejects the call (with a 486 for example), the call doesn't get torn down immediately (it is rejected with a 408 eventually) because Kamailio logs the following: Nov 23 14:51:02 host /usr/sbin/kamailio[1569]: DEBUG: app_python [apy_kemi.c:106]: sr_kemi_config_engine_python(): execution of route type 4 with name [ksr_onreply_manage] returned 1 Nov 23 14:51:02 host /usr/sbin/kamailio[1569]: DEBUG: tm [t_reply.c:1363]: t_should_relay_response(): ->>>>>>>>> T_code=183, new_code=486 Nov 23 14:51:02 host /usr/sbin/kamailio[1569]: DEBUG: tm [t_reply.c:1448]: t_should_relay_response(): store - other branches still active Nov 23 14:51:02 host /usr/sbin/kamailio[1569]: DEBUG: tm [t_reply.c:1926]: relay_reply(): reply status=3 branch=2, save=1, relay=-1 icode=0 msg status=486 I don't do any forking, the call is just forwarded. I put the following line immediately after t_suspend() and in the beginning of the route specified in t_continue(): KSR.info("We're at branch index %d" % KSR.pv.get("$T(branch_index)")) This produces the following output: Nov 23 16:30:13 host /usr/sbin/kamailio[2745]: INFO: <core> [core/kemi.c:104]: sr_kemi_core_info(): We're at branch index 0 Nov 23 16:30:13 host /usr/sbin/kamailio[2725]: INFO: <core> [core/kemi.c:104]: sr_kemi_core_info(): We're at branch index 2 So apparently, the suspend and continue introduce new branches. (Other option: I'm doing something completely different creating those branches, but I don't have any append_branch() or similar in my code.) I assume, I just missed a configuration parameter. Can I get Kamailio somehow to behave as if there was just one branch and forward the negative reply? Thanks, Sebastian

2 3

KEMI Golang
by Eugeniu Istrati 24 Nov '21

24 Nov '21

Hello, Is there any plans to add golang into the KEMI framework? Thank you -- Eugeniu Istrati

2 1

[uac] How to force outbound registration?
by Denys Pozniak 24 Nov '21

24 Nov '21

Hello! In some cases, I need to forcibly unregister a remote SIP account through uac module, and then immediately register. To unregister I can use the command: *kamcmd uac.reg_unregister l_uuid <account>* But it's not clear how to immediately register back. For example, these commands do not give the desired effect: *kamcmd uac.reg_enable l_uuid <account>* *kamcmd uac.reg_reload* [root@kamailio]# kamailio -V version: kamailio 5.5.2 (x86_64/linux) 55e232 -- BR, Denys Pozniak

2 3

Kamailio v5.5.3 Released
by Daniel-Constantin Mierla 24 Nov '21

24 Nov '21

Hello, Kamailio SIP Server v5.5.3 stable release is out. This is a maintenance release of the latest stable branch, 5.5, that includes fixes since the release of v5.5.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.3. For more details about version 5.5.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/11/kamailio-v5-5-3-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

Releasing Kamailio v5.5.3
by Daniel-Constantin Mierla 24 Nov '21

24 Nov '21

Hello, I am considering to release Kamailio v5.5.3 sometime next week, likely on Wednesday or Thursday (Nov 24/25, 2021). This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 3

UDP packets lost - tuning Linux system configuration - Kamailio using default for SO_RCVBUF ?
by Chaigneau, Nicolas 23 Nov '21

23 Nov '21

Hello, I'm using Kamailio 5.5.2 with UDP sockets, configured with 32 children processes. During load tests, some packets seem to be dropped. I'm trying to figure out why, and how to solve (or mitigate) the issue. >From what I understand : < the SIP messages send on UDP/SCTP are received directly from the buffer in kernel one by one, each being processed once read. > (this is a message from Daniel-Constantin Mierla, posted on the mailing list back in 2014 - I assume this is still accurate) So Kamailio does not handle its own buffers for incoming messages, but simply pulls one message from the kernel queue whenever a process is available for processing. (Correct me if this is not true) Hereafter some system parameters that seem interesting to me. In particular, < net.core.rmem.default > seem very low (0,33 MB). But < net.core.rmem.max > is much higher (16 MB). Looking at the code in function probe_max_receive_buffer (src\core\udp_server.c), it seems Kamailio is trying to increase the buffer size from the default. However this does not seem to be working, seeing the following logs upon startup : 0(7602) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 349520 0(7602) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 349520 0(7602) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 349520 0(7602) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 349520 0(7602) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 349520 0(7602) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 349520 Is there something I don't understand ? could it be a bug ? One quick fix I can think of would be to increase < net.core.rmem.default >. Considering that I don't have many sockets (3 used by Kamailio), I think I could set this to 16 MB (my VMs have 8 GB of allocated RAM). What do you think ? Thanks in advance for your help. My system parameters : net.core.rmem_default = 349520 net.core.rmem_max = 16777216 # => 0,33 MB / 16 MB respectively * net.core.rmem_default, net.core.rmem_max - default and max socket receive buffer size in bytes. Each socket gets rmem_default reveive buffer size by default, and can request up to rmem_max with setsockopt<http://man7.org/linux/man-pages/man2/setsockopt.2.html> option SO_RCVBUF. net.ipv4.udp_mem = 188856 251809 377712 * net.ipv4.udp_mem = "min pressure max" - these are numbers of PAGES (4KB) available for all UDP sockets in the system. min, pressure and max controls how memory is managed, but main point is that max is maximum size in PAGES for all UDP bufers in system. These values are set on boot time (if sysctls are not explicitly set) according to available RAM size. # 377712 x 4 KB => 1475 MB net.ipv4.udp_rmem_min = 4096 * net.ipv4.udp_rmem_min, net.ipv4.udp_wmem - minimal size for receive/send buffers (in bytes), guaranteed for each socket, even if if buffer size of all UDP sockets exceeds pressure parameter in net.ipv4.udp_mem. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 2

Custom info in Contact header
by Igor Olhovskiy 23 Nov '21

23 Nov '21

Hello! On REGISTER I have a Contact header like Contact: <sip:90002@192.168.0.26:48579;transport=TLS>;some_id=90002-21080 But on calling fix_nated_register() -> save(), param some_id is lost from info, so, on INVITE to this account, some_id not appears in RURI. Is this a bug or a feature and I do need to find some workaround? -- Best regards, Igor

4 6

Help with Async transaction responses
by Michael Friesen 19 Nov '21

19 Nov '21

Hello, I am attempting to perform some asynchronous lookup upon receiving an INVITE and then reply with a 3xx response with a modified From header. My workflow now is to create a transaction when receiving the INVITE, suspend the transaction, perform the asynchronous lookup, continue the transaction upon response, and then modify the From header and reply. The ONLY problem I am having is modifying the From header! How can I modify the From header in this scenario? function ksr_request_route() if KSR.is_INVITE() then if KSR.tm.t_newtran() then cache_transaction_info() KSR.tmx.t_suspend() --perform async loookup end end return 1 end --This function called on response from async lookup. Equivalent of ONREPLY_ROUTE function ksr_reply_route() --Finds the transaction_index and transaction_label from a cache KSR.tmx.t_continue(transaction_index, transaction_label, "redirect_transaction"); KSR.x.drop() return 1 end function redirect_transaction() KSR.pv.sets("$fU", "Jenny") --Doesn't actually modify the from username for 302 response! KSR.tm.t_reply(302, "Redirecting") return 1 end Thank you much! -Michael

2 2

+ character in send_reply causes truncation of reply message?
by Benoît Panizzon 18 Nov '21

18 Nov '21

Hi send_reply("403", "+411234567 transit disallowed"); Causes the reply to be truncated after the e164 number. send_reply("403", "Forbidden +411234567 transit disallowed"); Causes the reply to be truncated after 'Forbidden'. Is there a special meaning to the + character? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

configuration dispatcher
by sondes boughdiri 17 Nov '21

17 Nov '21

Hi ALL I need to configure dispatcher call to the server asterisk i have a 21 server and i need to dispatcher call to all the server AGENT----> kamailio --->asterisk1 ---> asteisk2 ---> - ---> - ---> - ---> asterisk21 please i need your help THANK YOU

2 1

ki_jsonrpcs_dispatch(): invalid json doc
by Patrick Karton 16 Nov '21

16 Nov '21

hello , im using kamailio and rtpengine. i use rtpengine with rtp timeout as follows rtpengine --timeout=240 --silent-timeout=600 -b2b-url=http://kamailioip:5060/RPC --xmlrpc-format=2 and in kamailio modparam("jsonrpcs", "pretty_format", 1) modparam("jsonrpcs", "transport", 7) event_route[xhttp:request] { if ($hu =~ "^/RPC") { jsonrpc_dispatch(); xhttp_reply("200", "OK", "text/xml", "<methodResponse><params><param><value><string>OK</string></value></param></params></methodResponse>"); exit; } } rtpengine successfully reaches the rpc endpoint but i have an error on the jsonrpcs module 43(50) ERROR: jsonrpcs [jsonrpcs_mod.c:1275]: ki_jsonrpcs_dispatch(): invalid json doc [[<?xml version="1.0" encoding="UTF-8"?> <methodCall> <methodName>dlg.terminate_dlg</methodName> <params> <param><value><string>1-10(a)172.22.244.139</string></value></param> <param><value><string>10SIPpTag091</string></value></param> <param><value><string>8U173ymKpc1pp</string></value></param> </params> </methodCall> ]] and so the dialog module can not ends the call Kamailio 5.5.2 on debian bullseye rtpengine 10.0.1.8 on debian bullseye Thanks.

1 0

xavp functionnality in htable
by Patrick Karton 15 Nov '21

15 Nov '21

hello, do we have something like xavp in htable or a module that implements having multiple values in stack like xavp but not tied to transaction. i want data be seen by all processes but with the functionnality of xavp. Thanks.

3 3

Info: Astricon 2021 - Asterisk and LRKProxy Session
by Mojtaba 13 Nov '21

13 Nov '21

Hello, The Asterisk conference (Astricon 2021) happened last week, I had a session about extending Asterisk with the LRKProxy module in Kamailio in terms of RTP sessions. cheers, -- --Mojtaba Esfandiari.S

2 3

corex send()
by Ross McKillop 12 Nov '21

12 Nov '21

Hi All, Is there an equivalent to corex's send_tcp (https://kamailio.org/docs/modules/5.2.x/modules/corex.html#corex.f.send_tcp <https://kamailio.org/docs/modules/5.2.x/modules/corex.html#corex.f.send_tcp>) for TLS? I have a bit of an odd edge case where I can't add Via headers etc, and send_udp and send_tcp allow me to achieve what I want, but it doesn't seem to have a means of doing the same with TLS? Essentially I want to transparently proxy what is received by Kamailio on one interface to a TLS connection e.g. A = (TCP) => Kamailio = (TLS) => Remote Host (A) in this instance is already setting a Via header of the Kamailio's external IP and transport tis. I appreciate this is a non-standard way of doing it, but (A) is a black box that I can't change, what I'm essentially trying to do is have Kamailio handle the TLS but essentially (A) thinks it's at the edge. I can make it work with send_tcp for a standard TCP connection, but if I use t_relay or even forward() to send onwards by TLS then Kamailio obviously adds its own headers as you'd expect. Ross

2 2

Kamailio dropping ACKs
by Emilio Panighetti 12 Nov '21

12 Nov '21

Working on a proof of concept with Kamailio 5.5.2 (Installed via kamailio-5.5.2-0.el8.centos.x86_64 RPM from rpm.kamailio.org). Also note that this is using the LUA interface Running a simple SIPp scenario without registration. Routing is set with in Lua: KSR.dbg("EP: ksr_route_relay Check for Base Route\n"); if KSR.is_INVITE() and KSR.siputils.has_totag() < 0 then KSR.dbg("EP: ksr_route_relay Base Route\n"); --KSR.sl.send_reply("503", "OLGX Debug"); KSR.setdsturi("sip:192.168.1.14:5060"); --KSR.pv.sets("$du", "sip:192.168.1.12:5062"); end The problem is that Kamailio is dropping the ACK to the 200 OK from the UAS. Wireshark shows that the UAS is retransmitting the 200 OK and the ACK is not being forwarded from the UAC to the UAS. Within the Lua config script: -- Handle requests within SIP dialogs function ksr_route_withindlg() if KSR.siputils.has_totag() < 0 then return 1; end KSR.dbg("EP: ksr_route_withindlg has to-tag, it is within a dialog\n"); -- sequential request within a dialog should -- take the path determined by record-routing if KSR.rr.loose_route() > 0 then ksr_route_dlguri(); if KSR.is_BYE() then KSR.setflag(FLT_ACC); -- do accounting ... KSR.setflag(FLT_ACCFAILED); -- ... even if the transaction fails elseif KSR.is_ACK() then -- ACK is forwarded statelessly KSR.dbg("EP: ksr_route_withindlg Forwarding ACK\n"); ksr_route_natmanage(); elseif KSR.is_NOTIFY() then -- Add Record-Route for in-dialog NOTIFY as per RFC 6665. KSR.rr.record_route(); end KSR.dbg("EP: ksr_route_withindlg loose route calling ksr_route_relay\n"); ksr_route_relay(); KSR.dbg("EP: ksr_route_withindlg exit\n"); KSR.x.exit(); end if KSR.is_ACK() then if KSR.tm.t_check_trans() > 0 then -- no loose-route, but stateful ACK; -- must be an ACK after a 487 -- or e.g. 404 from upstream server KSR.dbg("EP: ksr_route_withindlg is ACK calling ksr_route_relay\n"); ksr_route_relay(); KSR.dbg("EP: ksr_route_withindlg exit\n"); KSR.x.exit(); else -- ACK without matching transaction ... ignore and discard KSR.dbg("EP: ksr_route_withindlg Unknown ACK exit\n"); KSR.x.exit(); end end KSR.sl.sl_send_reply(404, "Not here"); KSR.dbg("EP: ksr_route_withindlg exit after 404\n"); KSR.x.exit(); end And logs for the ACK: Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/udp_server.c:493]: udp_rcv_loop(): received on udp socket: (106/100/385) [[ACK sip:service@192.168.1.15:5060 SIP/2.0 0D 0A Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG4bK-1091869]] Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 1 (request) flags 1 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:677]: parse_msg(): SIP Request: Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:679]: parse_msg(): method: <ACK> Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:681]: parse_msg(): uri: <sip:service@192.168.1.15:5060> Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:683]: parse_msg(): version: <SIP/2.0> Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [Via] type 1 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-1091869-1-5>; state=16 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:555]: parse_headers(): Via found, flags=2 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:557]: parse_headers(): this is the first via Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [From] type 4 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [To] type 3 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=4088926SIPpTag014 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:173]: get_hdr_field(): <To> [63]; uri=[sip:service@192.168.1.15:5060] Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:176]: get_hdr_field(): to body (39)[service <sip:service@192.168.1.15:5060>], to tag (17)[4088926SIPpTag014] Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [Call-ID] type 6 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [CSeq] type 5 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/parser/msg_parser.c:154]: get_hdr_field(): cseq <CSeq>: <1> <ACK> Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: <core> [core/receive.c:387]: receive_msg(): --- received sip message - request - call-id: [1-1091869(a)192.168.1.12] - cseq: [1 ACK] Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/receive.c:259]: ksr_evrt_pre_routing(): event route core:pre-routing not defined Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/receive.c:457]: receive_msg(): preparing to run routing scripts... Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sl [sl_funcs.c:443]: sl_filter_ACK(): too late to be a local ACK! Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:489]: sr_lua_reload_script(): No need to reload [/etc/kamailio/kamailio.lua] is version 0 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:673]: app_lua_run_ex(): executing Lua function: [[ksr_request_route]] Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:675]: app_lua_run_ex(): lua top index is: 21 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [Contact] type 7 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [Max-Forwards] type 8 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [Subject] type 27 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [Content-Length] type 12 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/msg_parser.c:187]: get_hdr_field(): content_length=0 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/msg_parser.c:91]: get_hdr_field(): found end of header Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1007]: sr_kemi_lua_exec_func_ex(): param[0] for: process_maxfwd is int: 69 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1007]: sr_kemi_lua_exec_func_ex(): param[0] for: is_maxfwd_lt is int: 69 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: maxfwd [maxfwd.c:187]: ki_is_maxfwd_lt(): value = 69 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1007]: sr_kemi_lua_exec_func_ex(): param[0] for: sanity_check is int: 1511 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1007]: sr_kemi_lua_exec_func_ex(): param[1] for: sanity_check is int: 7 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:318]: check_required_headers(): check_required_headers entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:340]: check_required_headers(): check_required_headers passed Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:506]: check_cseq_method(): check_cseq_method entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:539]: check_cseq_method(): check_cseq_method passed Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:548]: check_cseq_value(): check_cseq_value entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:576]: check_cseq_value(): check_cseq_value passed Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:585]: check_cl(): check_cl entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:610]: check_cl(): check_cl passed Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:622]: check_expires_value(): check_expires_value entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:659]: check_expires_value(): no expires header found Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:759]: check_parse_uris(): check_parse_uris entered Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:763]: check_parse_uris(): parsing ruri Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:777]: check_parse_uris(): looking up From header Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:791]: check_parse_uris(): parsing From header Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1091869SIPpTag001 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:817]: check_parse_uris(): parsing From URI Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:835]: check_parse_uris(): looking up To header Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:857]: check_parse_uris(): check_parse_uris(): parsing To URI Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: sanity [sanity.c:902]: check_parse_uris(): check_parse_uris passed Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: siputils [checks.c:123]: has_totag(): totag found Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: dbg is str: EP: ksr_route_withindlg has to-tag, it is within a dialog Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/kemi.c:85]: sr_kemi_core_dbg(): EP: ksr_route_withindlg has to-tag, it is within a dialog Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: rr [loose.c:108]: find_first_route(): No Route headers found Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: rr [loose.c:1006]: loose_route_mode(): There is no Route HF Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: tm [t_lookup.c:1034]: t_check_msg(): msg (0x7fef983a2608) id=2/2414 global id=1/2414 T start=0xffffffffffffffff Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: tm [t_lookup.c:497]: t_lookup_request(): start searching: hash=12314, isACK=1 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: tm [t_lookup.c:455]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK-1091869-1-5] Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: tm [t_lookup.c:675]: t_lookup_request(): no transaction found Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: tm [t_lookup.c:1103]: t_check_msg(): msg (0x7fef983a2608) id=2/2414 global id=2/2414 T end=(ni l) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: dbg is str: EP: ksr_route_withindlg Unknown ACK exit Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/kemi.c:85]: sr_kemi_core_dbg(): EP: ksr_route_withindlg Unknown ACK exit Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1837]: sr_kemi_lua_exit(): script exit call Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:729]: app_lua_run_ex(): ksr error call from Lua: ~~ksr~exit~~ Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_mod.c:167]: sr_kemi_config_engine_lua(): execution of route type 1 with no name returned 1 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: INFO: LUA {ACK}: <core> [core/receive.c:515]: receive_msg(): request-route executed in: 364 usec Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/receive.c:606]: receive_msg(): cleaning up Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/udp_server.c:493]: udp_rcv_loop(): received on udp socket: (106/100/577) [[SIP/2.0 200 OK 0D 0A Via: SIP/2.0/UDP 192.168.1.15;branch=z9hG4bKa103.32dd17e8a1a3458280dbbe34442737e7.0,]] Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/parser/parse_fline.c:249]: parse_first_line(): first line type 2 (reply(status)) flags 1 Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/parser/msg_parser.c:687]: parse_msg(): SIP Reply (status): Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/parser/msg_parser.c:689]: parse_msg(): version: <SIP/2.0> Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/parser/msg_parser.c:691]: parse_msg(): status: <200> Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/parser/msg_parser.c:693]: parse_msg(): reason: <OK> Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/parser/parse_hname2.c:293]: parse_sip_header_name(): parsed header name [Via] type 1 Nov 11 12:24:37 ol-vm1 /usr/sbin/kamailio[2413]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKa103.3 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: tm [t_lookup.c:1103]: t_check_msg(): msg (0x7fef983a2608) id=2/2414 global id=2/2414 T end=(nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1003]: sr_kemi_lua_exec_func_ex(): param[0] for: dbg is str: EP: ksr_route_withindlg Unknown ACK exit Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/kemi.c:85]: sr_kemi_core_dbg(): EP: ksr_route_withindlg Unknown ACK exit Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:1837]: sr_kemi_lua_exit(): script exit call Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_api.c:729]: app_lua_run_ex(): ksr error call from Lua: ~~ksr~exit~~ Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: app_lua [app_lua_mod.c:167]: sr_kemi_config_engine_lua(): execution of route type 1 with no name returned 1 Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: INFO: LUA {ACK}: <core> [core/receive.c:515]: receive_msg(): request-route executed in: 364 usec Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/usr_avp.c:637]: destroy_avp_list(): destroying list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/xavp.c:541]: xavp_destroy_list(): destroying xavp list (nil) Nov 11 12:24:36 ol-vm1 /usr/sbin/kamailio[2414]: DEBUG: LUA {ACK}: <core> [core/receive.c:606]: receive_msg(): cleaning up The ACK is this: ACK sip:service@192.168.1.15:5060 SIP/2.0\r\n Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG4bK-1091869-1-5\r\n From: sipp <sip:sipp@192.168.1.12:5060>;tag=1091869SIPpTag001\r\n To: service <sip:service@192.168.1.15:5060>;tag=4088926SIPpTag014\r\n Call-ID: 1-1091869(a)192.168.1.12\r\n CSeq: 1 ACK\r\n Contact: sip:sipp@192.168.1.12:5060\r\n Max-Forwards: 70\r\n Subject: Performance Test\r\n Content-Length: 0\r\n \r\n I’ve been trying to figure this out for days and don’t know what’s wrong here. Thanks

3 4

[ndb_redis] init_without_redis issue
by Denys Pozniak 11 Nov '21

11 Nov '21

Hello! In our architecture, Kamailio uses 2 local Redis servers to get routing information. We noticed that if at the start of Kamailio the first in the modparam list is a running Redis server (name=real), and the second in the list is not running (name=fake), then Kamailio will not even try to connect to the running one. # ----- redis server params ----- modparam("ndb_redis", "init_without_redis", 1) modparam("ndb_redis", "server", "name=real;addr=127.0.0.1;port=6379;db=1") modparam("ndb_redis", "server", "name=fake;addr=127.0.0.1;port=6479;db=2") But if the servers in the list above are reversed, then everything will work as it should. Looks the initialization order affects behavior. Syslog output: Nov 11 18:00:45 kamailio /usr/sbin/kamailio[11445]: ERROR: ndb_redis [redis_client.c:224]: redisc_init(): Failed to create REDIS returned an error: Connection refused Nov 11 18:00:45 kamailio /usr/sbin/kamailio[11445]: ERROR: ndb_redis [redis_client.c:259]: redisc_init(): error communicating with redis server [fake] (127.0.0.1:6479/2): Connection refused Nov 11 18:00:45 kamailio /usr/sbin/kamailio[11445]: WARNING: ndb_redis [redis_client.c:264]: redisc_init(): failed to initialize redis connections, but initializing module anyway. There is no established connection to the real server after Kamailio starts both through redis-cli and through ss. [root@kamailio ~]# ss -anp | grep 6379 tcp LISTEN 0 128 127.0.0.1:6379 *:* users:(("redis-server",pid=10376,fd=6)) [root@kamailio ~]# kamailio -v version: kamailio 5.6.0-dev2 (x86_64/linux) 378a2d compiled on 04:12:43 Nov 11 2021 with gcc 4.8.5 [root@kamailio ~]# cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) g -- BR, Denys Pozniak

1 0

Forcing Outbound Socket
by Ross McKillop 11 Nov '21

11 Nov '21

Hi All, Try as I may I cannot force an outbound TCP request to use a non-ephemeral source port. Looking at the documentation it seems that as long as I have a line like listen=tcp:10.30.0.55:3339 I should be able to force an outbound connection to originate from that host and port, i.e. to establish a persistent connection from a specific socket to a remote host, but having tried to set it via $fs and set_send_socket() it always uses an ephemeral port. Ideally I would like kamailio to use a specific source port for contacting a specific remote host and keep the TCP socket established, and it seems like it should be simple enough to do but it's not working as expected. Best, Ross

4 6

TCP Persistent Connections
by Ross McKillop 10 Nov '21

10 Nov '21

Hopefully the collective hive mind can help with this one, as I have little experience of using TCP in this manner and neither does a friendly Kamailio expert I know personally. I'm replacing a closed box thing that accepts connections from various nodes over TCP. They send INVITEs and REGISTERs over that TCP socket and expect to receive inbound calls over the same established TCP socket. Struggling to make Kamailio behave the same way, but it should be possible. The first time it receives a message, I add the sender to the dispatcher as follows; jsonrpc_exec('{"jsonrpc": "2.0", "method": "dispatcher.add", "params": [5, "sip:$si:$sp;transport=tcp", 0, "socket=tcp:127.0.0.1:5776"], "id": 1}'); This works great, but despite setting the socket to use there, when a call later comes in and it's routed to one of the dispatcher nodes that's been added in this way it fails because Kamailio attempts to open a new connection to the IP / PORT rather than having kept the socket open from the earlier message and reusing the same connection/. Any ideas? I get the feeling I'm missing something obvious! Ross

3 3

Re: [SR-Users] htable.get issues
by Igor Olhovskiy 10 Nov '21

10 Nov '21

Yup, this is works! Thanks! Not reflected in docs, though... ср, 10 нояб. 2021 г. в 16:13, Fred Posner <fred(a)palner.com>: > > On 11/10/21 11:10 AM, Igor Olhovskiy wrote: > > Hello, > > I'm getting issues with *htable.get* rpc command > > Running > > kamctl rpc htable.get client_to_re 65825 > > What happens when you try: > > s:65825 vs 65825 > > > > Fred Posner | palner.com > Matrix: @fred:matrix.lod.com > o: +1 (212) 937-7844 > -- Best regards, Igor

1 0

htable.get issues
by Igor Olhovskiy 10 Nov '21

10 Nov '21

Hello, I'm getting issues with *htable.get* rpc command Running kamctl rpc htable.get client_to_re 65825 { "jsonrpc": "2.0", "error": { "code": 500, "message": "Not enough parameters (htable name and key name)" }, "id": 46641 } To mention, there is such name in table and if I specify wrong name - I'm getting corresponding error Kamailio 5.4.6 Running commands to *seti*, *sets* leads to same error answer Is it something to add a bug or am I missing something obvious? -- Best regards, Igor

1 0

$var assignment broken on master ?
by Chaigneau, Nicolas 09 Nov '21

09 Nov '21

Hello, I've just built Kamailio from the master. Assigning a value to a < var > doesn't seem to work anymore... This works with Kamailio 5.5.2. E.g. : $var(my_var) = "hello"; xlog("L_WARN", "var(my_var): $var(my_var)\n"); # => This shows value 0. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 4

How to determine size (number of elements) in xavp stack?
by Benoît Panizzon 09 Nov '21

09 Nov '21

Dear Community In my previous post I mentioned my problem with sql_xquery I fear I used this wrong. $dbr is probably only populated if sql_query is used. Anyway, it is always 0 in my testings, even if I clearly get a result. Now I would like to know how many results I have. How can I determine the size of an $xavp stack (or array)? Or is there another way to get the number of rows returned by a sql_xquery without looping an index through all rows? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 3

sql_xquery return 1 on 0 rows?
by Benoît Panizzon 09 Nov '21

09 Nov '21

Dear List... kamcmd> version kamailio 5.4.7 (x86_64/linux) Strange issue found. According to: https://kamailio.org/docs/modules/5.4.x/modules/sqlops.html I should get return value 2 if no rows returned: $var(query) contains a query that does not match (number is not assigned) if (sql_xquery("impkam", "$var(query)", "assignedtn") == 1) { if ($avp(debug) > 1) { xlog("L_INFO", "$cfg(route): SQL Dump Result: $var(assignedtn) ROWS: $dbr(assignedtn=>rows) \n"); } do stuff with the assigned number } else { do stuff in case that number is not assigned } Log Output: CHECK_ASSIGNED_TN: SQL Dump Result: 0 ROWS: 0 So the return value of the query was == 1 but the result contains no rows. How can that be? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

4 4

STIR/SHAKEN public key
by David Villasmil 05 Nov '21

05 Nov '21

Hello guys, I'm testing with 2 providers right now, and one of them is asking me to include my whole certificate on the *secsipid_add_identity(origTN, destTN, attest, origID, x5u, keyPath)* like: *secsipid_add_identity("$fU", "$rU", "A", "", "https://kamailio.org/stir/$rd/cert.pem <https://kamailio.org/stir/$rd/cert.pem>", "/secsipid/$rd/key.pem");* but it is stated that: *x5u is the HTTP URL referencing to the public key that should be used to verify the signature;* One provider is asking to put the cert there, the other hasn't asked that yet. So i'm a little confused, should the x5u be the actual cert (with its intermediary?) or only the public key? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 9

Suppressing part of the xlog line
by Steve Wilkins 05 Nov '21

05 Nov '21

Hello, Is there a way to suppress the printing "date & time, host, and Kamailio execution path" at the begging of each xlog line? Example current xlog line: Nov 4 16:54:52 myserver /usr/local/sbin/kamailio[7021]: INFO: <script>: => Test xlog line I would like xlog line to be: INFO: <script>: => Test xlog line Thank you,

3 2

Is this idea even feasible?
by Antony Stone 04 Nov '21

04 Nov '21

Hi. I'm looking for a solution to the following problem, and wondering whether Kamailio (with which I have very little experience so far) may be it, or whether I'm thinking in totally the wrong direction. The problem: I have a SIP client application which runs on a standard Linux system, and is extremely basic - it can REGISTER in order to receive inbound calls, and it can send INVITEs in order to place outbound calls, and that's about it. It handles media as well - in essence, it's a simple softphone. I can't change it for a more capable one, before anyone suggests that :) Specifically, this thing cannot send REINVITEs in order to put calls on hold, nor can it handle anything to do with transfers (blind or attended). I'm looking for something which does have these SIP capabilities which I could put in between this application and the SIP server through which it is placing and receiving calls, so that I can (through some sort of API) cause calls in progress to be put on hold, resumed, blind transferred, or hold-and-attended- transferred. Does that sound like something Kamailio can do? If so, can anyone point me in a helpful direction re how to go about it? If not, can anyone suggest something else which could sit in between a very basic SIP client and a PBX server, in order to inject these sorts of commands into the path and thereby give me these sorts of extra call capabilities? Thanks, Antony. -- I'm not impossible, just highly implausible. Please reply to the list; please *don't* CC me.

8 30

STIR/SHAKEN, is a number format mandatory?
by David Villasmil 04 Nov '21

04 Nov '21

Hello guys, I'm getting failed by my provider because I'm sending to them with +1 both on the headers and on the payload. My understanding is there is no mandatory format, or is there? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

4 9

UAC reg_random_delay
by Sergiu Pojoga 03 Nov '21

03 Nov '21

Hi there, May I know what exactly is supposed to be "delayed" in the UAC registration? *modparam("uac", "reg_random_delay", 20)* I have records stored in DB with *reg_delay=0*. When doing *uac.reg_dump*, I do see the value of *reg_delay* being random for various records. However, after restarting Kamailio, the registrations are all sent out *simultaneously*, there doesn't seem to be a "delay", whatever the purpose is supposed to be. Can someone clarify please? Kamailio 5.5.0 Thanks. Regards, --Sergiu

4 9

STIR/SHAKEN
by David Villasmil 02 Nov '21

02 Nov '21

Hello guys, I'm trying to test secsipid by creating an Identity header and trying to verify it with the cli utility, but it's failing: # secsipidx -sign-full -orig-tn 123456789 -dest-tn 123456789 -attest A -x5u https://pki.my.domain.com/stir-shaken-public-key.pem -k ec256-private.pem eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9wa2kudG5jcC50ZXh0bm93LmNvbS9zdGlyLXNoYWtlbi1wdWJsaWMta2V5LnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxMjM0NTY3ODkiXX0sImlhdCI6MTYzNTg4OTY3Miwib3JpZyI6eyJ0biI6IjEyMzQ1Njc4OSJ9LCJvcmlnaWQiOiJjNTE4MDI4Ny05NjJmLTRlMDItYTM1NS00YmMzY2JhYzMxNjgifQ.ei1nQY8c9EQzvuBP7pQSI03T2yIfsNg9blzSdufU7tQy0tLJwoqmM9sBAk_Uq9s2jycVxseonZ1yl1kGiSv_GA;info=< https://pki.my.domain.com/stir-shaken-public-key.pem>;alg=ES256;ppt=shaken root@sip-stir-term1:/home/admin# echo "eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9wa2kudG5jcC50ZXh0bm93LmNvbS9zdGlyLXNoYWtlbi1wdWJsaWMta2V5LnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxMjM0NTY3ODkiXX0sImlhdCI6MTYzNTg4OTY3Miwib3JpZyI6eyJ0biI6IjEyMzQ1Njc4OSJ9LCJvcmlnaWQiOiJjNTE4MDI4Ny05NjJmLTRlMDItYTM1NS00YmMzY2JhYzMxNjgifQ.ei1nQY8c9EQzvuBP7pQSI03T2yIfsNg9blzSdufU7tQy0tLJwoqmM9sBAk_Uq9s2jycVxseonZ1yl1kGiSv_GA;info=< https://pki.my.domain.com/stir-shaken-public-key.pem>;alg=ES256;ppt=shaken" > identity.txt root@sip-stir-term1:/home/admin# secsipidx -check -fidentity identity.txt -fpubkey /etc/kamailio/secsipid/ec256-private.pem -expire 3600 error message: asn1: structure error: tags don't match (16 vs {class:0 tag:2 length:1 isCompound:false}) {optional:false explicit:false application:false private:false defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} tbsCertificate @2 not-ok any ideas? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 1

how to prevent the log_prefix in syslog acc cdrs?
by Karsten Horsmann 02 Nov '21

02 Nov '21

Hi List, i thought there could be a solution to disable the log_prefix for acc module - but i didn't found it. Is there a solution to supress log_prefix for acc like acc_json did that? I use kamailio 5.5.2 with that settings: log_name="kamailio" log_facility=LOG_LOCAL4 log_prefix="{$hdr(CSeq) $ci} " the acc module then logs the "log_prefix" - plus some module/function stuff: INFO: {1 INVITE SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050} acc [acc.c:285]: acc_log_request(): ACC: transaction answered: timestamp=1635843776;utctime=2021-11-02 09:02:56;method=INVITE;from_tag=SDkk50d01-e8bc0cda;to_tag=XBr6apQ9HN4HD;call_id=SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050;code=200;reason=OK;src_user=bob;src_domain=sip100;src_ip=172.20.120.56;dst_ouser=alice;dst_user=echo;dst_domain=172.20.120.59;user_agent=;x_t_call_id=;x_routing=;x_billing= INFO: {1 ACK SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050} acc [acc.c:285]: acc_log_request(): ACC: request acknowledged: timestamp=1635843776;utctime=2021-11-02 09:02:56;method=ACK;from_tag=SDkk50d01-e8bc0cda;to_tag=XBr6apQ9HN4HD;call_id=SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050;code=200;reason=OK;src_user=bob;src_domain=sip100;src_ip=172.20.120.56;dst_ouser=alice;dst_user=alice;dst_domain=172.20.120.51;user_agent=;x_t_call_id=;x_routing=;x_billing= INFO: {2 BYE SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050} acc [acc.c:285]: acc_log_request(): ACC: transaction answered: timestamp=1635843833;utctime=2021-11-02 09:03:53;method=BYE;from_tag=SDkk50d01-e8bc0cda;to_tag=XBr6apQ9HN4HD;call_id=SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050;code=200;reason=OK;src_user=bob;src_domain=sip100;src_ip=172.20.120.56;dst_ouser=alice;dst_user=alice;dst_domain=172.20.120.51;user_agent=;x_t_call_id=;x_routing=;x_billing= The acc_json module is able to log acc without log_prefix: {"time": "2021/11/02 10:02:56", "method": "INVITE", "from_tag": "SDkk50d01-e8bc0cda", "to_tag": "XBr6apQ9HN4HD", "callid": "SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050", "sip_code": "200", "sip_reason": "OK", "src_user": "bob", "src_domain": "sip100", "src_ip": "172.20.120.56", "dst_ouser": "alice", "dst_user": "echo", "dst_domain": "172.20.120.59", "user_agent": "", "x_t_call_id": "", "x_routing": "", "x_billing": ""} {"time": "2021/11/02 10:03:53", "method": "BYE", "from_tag": "SDkk50d01-e8bc0cda", "to_tag": "XBr6apQ9HN4HD", "callid": "SDkk50d01-1f7cc956b0b908e42d284189a11b44e7-ct46om0050", "sip_code": "200", "sip_reason": "OK", "src_user": "bob", "src_domain": "sip100", "src_ip": "172.20.120.56", "dst_ouser": "alice", "dst_user": "alice", "dst_domain": "172.20.120.51", "user_agent": "", "x_t_call_id": "", "x_routing": "", "x_billing": ""} And just for the records - how to get rid off the rsyslog prefix time/date stuff: # /etc/rsyslog.d/kamailio.conf # drop :msg from rtpengine with "timer run time" - debugging only: :msg, contains, "timer run time" ~ # Template only msg: $template myFormat,"%msg%\n" # log only to local* and NOT to /var/log/messages local6.*;local6.!=info -/var/log/platform/voip/kamailio/rtpengine.log local6.* stop local5.* -/var/log/platform/voip/kamailio/rtpengine-cdr.log; myFormat local5.* stop local4.* -/var/log/platform/voip/kamailio/kamailio.log local4.* stop local2.* -/var/log/platform/voip/kamailio/kamailio-cdr.log; myFormat local2.* stop local1.* -/var/log/platform/voip/kamailio/kamailio-cdr-json.log; myFormat local1.* stop -- Mit freundlichen Grüßen *Karsten Horsmann*

1 0

kamailio didnt run with acc_json (without dialog module) - kamailio 5.5.2
by Karsten Horsmann 02 Nov '21

02 Nov '21

Hi List, i want to try out acc_json (to syslog). But if i set up "cdr_enable", 1 - it breaks the startup of kamailio with that error (dialog module is not listed as dependency). Any hints? Nov 01 13:13:59 siprouter2 kamailio[22397]: INFO: acc_json [acc_json_mod.c:135]: mod_init(): janson version : 2.10 Nov 01 13:13:59 siprouter2 kamailio[22397]: ERROR: acc_json [acc_json_mod.c:204]: mod_init(): can't load dialog API Nov 01 13:13:59 siprouter2 kamailio[22397]: ERROR: <core> [core/sr_module.c:943]: init_mod(): Error while initializing module acc_json (/usr/lib64/kamailio/modules/acc_json.so) #!ifdef WITH_DBTEXT loadmodule "db_text.so" #!endif #!ifndef WITH_DBTEXT loadmodule "db_mysql.so" #!endif loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "acc.so" loadmodule "dispatcher.so" loadmodule "permissions.so" loadmodule "avpops.so" #!ifdef WITH_ACCJSON loadmodule "acc_json.so" #!endif #!ifdef WITH_DIALPLAN loadmodule "dialplan.so" modparam("dialplan", "db_url", DBURL) modparam("dialplan", "fetch_rows", 1000) modparam("dialplan", "attrs_pvar", "$avp(s:dest)") #!endif #!ifdef WITH_JSONSTATS loadmodule "xhttp.so" loadmodule "jansson.so" loadmodule "janssonrpcc.so" #!endif #!ifdef WITH_HOMER loadmodule "siptrace.so" #!endif loadmodule "pipelimit.so" loadmodule "htable.so" .... # ----- acc params ----- modparam("acc", "log_flag", FLT_ACC) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) # ----- acc params ----- #!ifdef WITH_ACCSYSLOG modparam("acc", "log_facility", "LOG_LOCAL2") modparam("acc", "log_level", 2) #!endif /* what special events should be accounted ? */ modparam("acc", "time_mode", 4) modparam("acc", "time_attr", "utctime") modparam("acc", "time_format", "%Y-%m-%d %H:%M:%S") modparam("acc", "acc_time_column", "localtime") ## --- to syslog modparam("acc", "early_media", 1) modparam("acc", "report_ack", 1) modparam("acc", "report_cancels", 1) /* by default ww do not adjust the direct of the sequential requests. * if you enable this parameter, be sure the enable "append_fromtag" * in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;user_agent=$ua;x_t_call_id=$avp(x-t-call-id);x_routing=$avp(x_routing);x_billing=$avp(x_billing)") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) /* enhanced DB accounting */ #!ifdef WITH_ACCDB modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", DBURL) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") #!endif #!ifdef WITH_ACCJSON modparam("acc_json", "acc_missed_flag", 3) modparam("acc_json", "acc_time_mode", 1) modparam("acc_json", "cdr_output_syslog", 1) modparam("acc_json", "acc_time_format", "%Y/%m/%d %H:%M:%S") modparam("acc_json", "acc_log_facility", "LOG_LOCAL1") modparam("acc_json", "acc_log_level", 2) # Set acc_log_level to 2 (L_INFO) modparam("acc_json", "cdr_enable", 1) #!endif .... version: kamailio 5.5.2 (x86_64/linux) 55e232 flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, 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 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: 55e232 compiled on 14:20:31 Aug 25 2021 with gcc 4.8.5 -- Mit freundlichen Grüßen *Karsten Horsmann*

2 3

Strip VP8 from SDP in rtpengine
by Rahul mm 30 Oct '21

30 Oct '21

Hello, I'm facing trouble with Android 12 using webview to attempt video call. All the media is rotated from rtpengine. To workaround this problem, I wish to strip VP8 and have the calls run on VP9. For this, I added "codec-strip=VP8" but rtpengine is not able to remove it. I've even tried "codec-strip=VP8/90000" but to no avail. The video is still garbled. Am I doing anything wrong here? Thanks and Regards Rahul

4 4

Stir/Shaken Kamailio modules - stirshaken vs secsipid
by Joel Serrano 29 Oct '21

29 Oct '21

Hi everyone, As most of us, I'm starting to implement STIR/SHAKEN in our platform. I've seen there are 2 modules available in Kamailio for this: stirshaken: https://www.kamailio.org/docs/modules/5.5.x/modules/stirshaken.html secsipid: https://kamailio.org/docs/modules/5.5.x/modules/secsipid.html Suggestions on which to use? Pros/Cons of each? Do any of you have experience with any of the two? Any comments are more than welcome! Thanks, Joel.

1 0

RTPENGINE [ice] Priority collision between candidate pairs
by keffa＠alcall.net 29 Oct '21

29 Oct '21

Hello @everyone Please can you explain me how this message is errors or not ? « Oct 29 08:34:44 ip76 rtpengine[649]: WARNING: [YGiXZ1MmIA port 30104]: [ice] Priority collision between candidate pairs 9oZd7sWNVguf6cgl:e4b19f6635447b850 » thank

5 4

htable shtcn expressions
by Brooks Bridges 29 Oct '21

29 Oct '21

Referring to the expressions outlined at http://www.kamailio.org/wiki/cookbooks/5.4.x/pseudovariables#shtcn_htable_e… , is there any additional documentation or examples floating around that further explains how the right and left prefix matching works? The rest of them are pretty clear, but I'm having troubles with these and can't get them working like I would expect them to work. Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.

3 5

Configuration script behaviour with http_async_client usage
by Kris Domagalski 29 Oct '21

29 Oct '21

Hi, I'm new in Kamailio and looking for some configuration guidance. I'm using http_async_client for API requests. It's configured to use TEST2 route, which should be executed upon reception of HTTPS response. After receiving the response I would like to go back to the request_route and perform some more actions. Currently behaviour is, in the syslog I can see only entries which I push from TEST2 route (TEST 123). Cannot see the one from request route. Current syslog output: TEST123 Expected syslog output: TEST 123 TEST 789 And now my question is why kamailio is not executing remaining actions (xlog) in request_route? request_route { route(TEST1); xlog("L_INFO","TEST 789\n"); } route[TEST1] { # define API request body in JSON format jansson_set("string", "from", $fU, "$var(http_routing_query)"); # set API request parameters $http_req(all) = $null; $http_req(suspend) = 1; $http_req(timeout) = 100; $http_req(method) = "POST"; $http_req(hdr) = "Content-Type: application/json"; $http_req(body) = $var(http_routing_query); t_newtran(); # send API request http_async_query(http://local:3000/test, "TEST2"); } route[TEST2] { xlog("L_INFO","TEST 123\n"); } Thanks Kris

1 0

Re: [SR-Users] No "child_destroy" export - issue with module flatstore and flush=0
by Chaigneau, Nicolas 29 Oct '21

29 Oct '21

Hello Henning, Thanks for your reply ! For the record, I'm using Kamailio module "flatstore" with the flush deactivated. In this situation, when Kamailio is stopped, I'm losing the remaining data in files not yet flushed. So my idea was, when destroy is called, to iterate over the connection pools, and flush/close all the opened files properly. But I found out that it's not that simple :/ Do you think this is something that could be fixed in Kamailio ? Regards, Nicolas. De : Henning Westerholt <hw(a)gilawa.com> Envoyé : mardi 26 octobre 2021 20:38 À : Kamailio (SER) - Users Mailing List Cc : Chaigneau, Nicolas Objet : RE: No "child_destroy" export ? Hi Nicolas, you are right, there is no special function for children destroy. Most modules do not need it, as the data is in shared memory, processes are started over standard kamailio APIs which will be stopped from the core automatically, to give some background. Some modules do it by just iterating over an internal list of their children and then do the cleanup task. You can find an example in cdp module (destroy, diameter_peer_destroy). Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Chaigneau, Nicolas Sent: Tuesday, October 26, 2021 7:14 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] No "child_destroy" export ? Hello, I have a module, for which I need to perform some processing in the children processes when Kamailio is being stopped. I've looked at the "struct module_export", in which I see "mod_init", "child_init", "mod_destroy"... but no "child_destroy". :/ Is there a way to achieve this ? Thanks for your help. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 2

Does failure_route for redirection covers all error cases ?
by Liviu ANDRON 29 Oct '21

29 Oct '21

Hello, We are routing calls to FreeSWITCH servers. We have a failure routing mechanism in place, which looks pretty common from my research around: route[INVITE] { ... t_on_failure("REROUTE"); and failure_route[REROUTE] { if (t_is_canceled()) { exit; } // also 6xx ? if (t_check_status("5[0-9][0-9]") or (t_branch_timeout() and !t_branch_replied())) { // re-route to another available FreeSWITCH server } } The problem is that we don't capture all the failures we would like to, one such example being 480 sent by FreeSWITCH in various cases (even default in hangup_cause_to_sip, mod_sofia.c, https://github.com/signalwire/freeswitch/blob/master/src/mod/endpoints/mod_…), like a Python script crash, but also legitimate cases like "user not registered" (USER_NOT_REGISTERED). Are there other cases? Like a timeout replied (t_branch_timeout() and t_branch_replied()) which never recovers ? Shouldn't any t_branch_timeout() re-arm the failure route ? Thanks, Liviu

3 2

xhttp_pi show dr_rules buffer 2 small Error.
by Abdirahman Osman 28 Oct '21

28 Oct '21

Hello Everyone, I am using the xhttp_pi modules to see the list of rules on the browser http://172.28.253.17:5060/pi/dr_rules/show?cmd=on and am I getting Internal Server Error I checked the logs and noticed the error "ph_build_reply_footer(): buffer 2 small" 13(20) DEBUG: db_postgres [km_dbase.c:411]: db_postgres_free_query(): PQclear(0x55e2416ae9a0) result set 13(20) ERROR: xhttp_pi [xhttp_pi_fnc.c:2470]: ph_build_reply_footer(): buffer 2 small 13(20) DEBUG: xhttp_pi [xhttp_pi.c:159]: pi_send(): pi_fault(500,"Internal Server Error" 13(20) DEBUG: xhttp_pi [xhttp_pi.c:169]: pi_send(): xhttp_api.reply(0x7ffc39eb1410, 500, Internal Server Error, text/html, Internal Server Error) 13(20) DEBUG: xhttp [xhttp_mod.c:416]: xhttp_send_reply(): response with content-type: text/html 13(20) DEBUG: xhttp [xhttp_mod.c:424]: xhttp_send_reply(): response with body: Internal Server Error 13(20) DEBUG: xhttp [xhttp_mod.c:426]: xhttp_send_reply(): sending out response: 500 Internal Server Error Which buffer do I need to increase here? tried to increase sql_buffer_size but that didn't work for me. Thanks! Abdirahman A. Osman

2 2

Info: ClueCon 2021 - Sessions touching Kamailio
by Daniel-Constantin Mierla 27 Oct '21

27 Oct '21

Hello, ClueCon conference happens this week, today I will have a session about what Kamailio offers for changing SIP message content (starting in about 25 minutes) and later today Fred Posner will present about Kamailio and FreeSwitch. You can watch the even live, more details at: * https://www.cluecon.com/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

2 1

t_relay changing source IP?
by Brooks Bridges 27 Oct '21

27 Oct '21

So we have a box that's bound to all interfaces on the server, and one specific IP address (that is an HA IP), and I've run into a bit of an odd behavior that I cannot explain. For 99.9999% of our traffic, the invites come into the HA IP, and then are forwareded out the HA IP to an SBC for further processing. In a very rare instance however, I have found that there is an invite coming in the HA IP, and for some unknown reason it gets forwarded out the *interface* ip instead of the HA IP. For example: Working: 1.2.3.4 -- invite --> 9.8.7.6 (ha IP) -- invite --> 5.6.7.8 (sbc) Non working: 1.2.3.4 -- invite --> 9.8.7.6 (ha IP) *something happens here* 9.8.7.5 (interface IP) -- invite --> 5.6.7.8 (sbc) I've been through tm, tmx, and the incoming invite of a working and non working request with a fine toothed comb and I cannot for the life of me explain this behavior. Any thoughts? Confidentiality Notice: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading this e-mail is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system.

4 11

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

27 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

3 4

No "child_destroy" export ?
by Chaigneau, Nicolas 26 Oct '21

26 Oct '21

Hello, I have a module, for which I need to perform some processing in the children processes when Kamailio is being stopped. I've looked at the "struct module_export", in which I see "mod_init", "child_init", "mod_destroy"... but no "child_destroy". :/ Is there a way to achieve this ? Thanks for your help. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 1

Kamailio/Asterisk Realtime issues
by Hayden Ryan 26 Oct '21

26 Oct '21

Hi all, I have Kamailio and Asterisk set up in a realtime configuration, like this: https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb In my setup, Kamailio forwards all REGISTER requests to Asterisk, and Asterisk authenticates them. I have a single peer in sip.conf pointing towards the Kamailio server, as type=peer Each user in the Asterisk database is set to type=user, as when they are set to anything else (or blank), incoming calls from Kamailio to Asterisk display the name of the most recent extension to register. Is there something wrong with my setup here? What I am trying to do is to get MWI working. SUBSCRIBEs for MWI are forwarded to and handled by Asterisk correctly. Yet the MWI state on the handset is incorrect, as I believe it is sending the latest MWI update to the most recently registered extension. Any suggestions would be much appreciated. I assume I'm doing this the wrong way and shouldn't be forwarding any REGISTERs to Asterisk and should be handling authentication in Kamailio itself? But that seems incompatible with the realtime configuration guides I've seen. Thank you, Hayden

2 1

Please reivew the issue about diameter_request_async
by BOEINGNG 26 Oct '21

26 Oct '21

Hello! Please review the issue I mentioned here:https://github.com/kamailio/kamailio/issues/2900 <https://github.com/kamailio/kamailio/issues/2900> Could you provide some advice to me? Regrads HANG LI

1 0

Info: risk of failure by upgrading to MariaDB 10.3.31
by Daniel-Constantin Mierla 25 Oct '21

25 Oct '21

Hello, not strictly related to Kamailio, but I know a large number of its deployments run with MariaDB. Be aware of a (pretty high) risk of failure after upgrading MariaDB server to v10.3.31, which comes now on Debian 10 via the usual apt update+upgrade. I was hit on one the servers I upgraded recently, first one worked fine, the 2nd failed to start MariaDB service after upgrade - there is a bug report about it: * https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1823336.h… Downgrading MariaDB seems to be the right solution for now, specially if you didn't do a backup just before upgrade. Don't try other tricks without a fresh backup, data files can be damaged. If you have a fresh backup, there seems to be a solution by deleting database files to start with a clean set and then restore from backup with sql statements. FreeBSD has a similar bug report, so doesn't seem to be only Debian, could be other Linux distros as well. Even with fresh backups, plan for a longer maintenance time frame than usual. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online Nov 08-11, 2021 (Europe Timezone) - Nov 22-25, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 0

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] - Checking country for ($si | $T_req($si)) - END\n"); } NOTE: xlog lines added for debugging, they normally are not there. In version 5.1.4 in the logs I see: Oct 21 15:55:47 13cn3 sbc[22606]: WARNING: <script>: [DLG] - Checking country for (A.B.C.D | 186.185.186.7) - START Oct 21 15:55:47 13cn3 sbc[22606]: WARNING: <script>: [DLG] - Checking country for (A.B.C.D | 186.185.186.7) - END The same config, on v5.5.2 is returning: Oct 21 15:57:08 sbc0504 sbc[22606]: WARNING: <script>: [DLG] - Checking country for (A.B.C.D | <null>) - START Oct 21 15:57:08 sbc0504 sbc[22606]: WARNING: <script>: [DLG] - Checking country for (A.B.C.D | <null>) - END After enabling debug logs I see: WARNING: <script>: [DLG] - Checking country for (198.1.55.124 | <null>) - START *DEBUG: tmx [t_var.c:309]: pv_get_t_var_req(): used in unsupported route block - type 64*DEBUG: geoip2 [geoip2_pv.c:488]: geoip2_update_pv(): attempt to match: <null> DEBUG: geoip2 [geoip2_pv.c:491]: geoip2_update_pv(): no match for: <null> Did something change in the tmx module that could affect $T_req(pv) being accessible in the dialog:start event_route? Any alternatives to get the source IP of the request (not the reply) in the dialog:start event_route? Let me know if you prefer that I open a ticket for this in GH. Thanks, Joel.

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 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. CC (gcc) [M app_perl.so] perlfunc.o In file included from perlfunc.c:40:0: app_perl_mod.h:37:20: fatal error: EXTERN.h: No such file or directory #include <EXTERN.h> ^ compilation terminated. make[2]: *** [perlfunc.o] Error 1 make[1]: *** [modules] Error 1 make[1]: Leaving directory `/usr/src/kamailio/src' Your help would be much appreciated. Thanks, AL

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 smallerwindow in the tcp packet. Is there any settings in Kamailio that could force the window size? we are using Kamailio 5.4.2 Thanks in advance Richard

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]: WARNING: <core> [core/msg_translator.c:2861]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found Oct 5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: <core> [core/msg_translator.c:2038]: build_req_buf_from_sip_req(): could not create Via header Oct 5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: tm [t_fwd.c:479]: prepare_new_uac(): could not build request Oct 5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: tm [t_fwd.c:1759]: t_forward_nonack(): failure to add branches Oct 5 15:38:24 proxy-01 /sbin/kamailio[32087]: ERROR: sl [sl_funcs.c:414]: sl_reply_error(): stateless error reply used: No error (2/SL) How can we catch this error to avoid terminating the call prematurely? Or should we flush these TCP connections on start up? Thanks Matthew

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

2 5

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