- sr-users - kamailio.org

UAC parameter for enabling and disabling remote registration
by Ahmed Fouad 14 Apr '22

14 Apr '22

Hi, I was wondering if this patch was ever merged to the current release(s) https://github.com/kamailio/kamailio/commit/49f354276df3cfc2cdb0f85b5a1839f… I'd like to start Kamailio with all remote registration disabled then enable based on the code logic Thanks in advance,

2 9

Roadmap to the next major release - v5.6.0
by Daniel-Constantin Mierla 14 Apr '22

14 Apr '22

Hello, it is the time to plan a bit the road to the next major release, to be versioned 5.6.0. The 5.5.0 was release about one year ago, therefore it is time to set the milestones for getting 5.6.0 out. I would propose to freeze the development on Thursday, April 14, 2020, test till mid of May or so, then release v5.6.0. There is a lot of development to existing components and a couple of new modules. If anyone wants a different time line towards 5.6.0, let's discuss and choose the one that suits most of the developers. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 3

kamailio fail to load sip-router.cfg
by bayu p 14 Apr '22

14 Apr '22

Dear Sir, Could you please help me, please to share how to load sip-router.cfg file inside running kamailio ? the file is necessary to be load during rerouting kamailio gateway. I have 2 platform kamailio , both of them are failed to load sip-router.cfg file. They are apt kamailio installation source and the second is tar.gz kamailio installation source, which reload / restart kamailio process (and installation) were failed to load sip-router.cfg file. Best Regards,

2 5

Re: [SR-Users] Kamailio IMS heavy load
by Henning Westerholt 12 Apr '22

12 Apr '22

Hello, checking CPU/I/O performance of the database during the load test would be a start. You can also monitor database access e.g. with a network debugging tools. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Евгений Мастратов <dgeka25594(a)gmail.com> Sent: Tuesday, April 12, 2022 10:03 AM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Kamailio IMS heavy load Hey Henning! Thanks for the advice, I understand about logging, I will make edits and re-check. And how can I check the fact that what are the gaps when reading / writing the database? I am using MySQL. вт, 12 апр. 2022 г. в 10:52, Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>>: Hello, as mentioned, I would start by monitoring my dependencies, in particular related to I/O, like database or monitoring. Just to be sure, you are not running the tests with enabled debug log level? This would certainly cause problems. 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 ??????? ????????? Sent: Monday, April 11, 2022 5:23 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] Kamailio IMS heavy load Hi! Previously, I created a ticket on github https://github.com/kamailio/kamailio/issues/3071 and tried to deal with the problem there, but they sent me here for advice. I set up Kamailio IMS , in the end everything turned out great, calls are made, and I decided to check how Kamailio copes with the load. I am creating a load using the sipp application. There is no problem with a low call generation rate, but if you raise the call generation to more than 20 calls per second, some of the calls fail. I compared the calls and saw that the ICSCF does not send a 180 Ringing message towards the S-CSCF [..] As I found out further and suggested, the problem is that some calls are cut on the S-CSCF and this is probably due to some kind of timer, but I could not figure out which one. Full logs and dump are attached to the issue on github, below is a log sample by bad dialog 0x7fc133ce61d8 ``` Apr 5 08:24:33 ims-core /usr/local/sbin/kamailio[26061]: DEBUG: ims_dialog [dlg_handlers.c:284]: dlg_iuid_sfree(): freeing dlg iuid [465:10905] (0x7fc133ce61d8) Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1025]: link_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_cb.c:251]: run_create_callbacks(): dialog=0x7fc133ce61d8 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_handlers.c:789]: dlg_onreq(): dialog [0x7fc133ce61d8] added to tm callbacks Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26059]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26059]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1293]: next_state_dlg(): dialog 0x7fc133ce61d8 changed from state 1 to state 6, due event 4 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_handlers.c:1489]: dlg_onreply(): dialog 0x7fc133ce61d8 failed (negative reply) Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_cb.c:277]: run_dlg_callbacks(): dialog=0x7fc133ce61d8, type=4 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 0 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): ref <=0 for dialog 0x7fc133ce61d8 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:196]: destroy_dlg(): destroying dialog 0x7fc133ce61d8 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:207]: destroy_dlg(): removed timer for dlg 0x7fc133ce61d8 [3791:1419] with clid '43-3057631(a)10.2.16.63<mailto:43-3057631@10.2.16.63>' and tags '78885556600' Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_cb.c:277]: run_dlg_callbacks(): dialog=0x7fc133ce61d8, type=8192 ``` What could be the reasons for this behavior and how to diagnose them? I did not observe problems with MEM or CPU during the tests. I will be grateful for any advice.

1 0

Kamailio IMS heavy load
by Евгений Мастратов 12 Apr '22

12 Apr '22

Hi! Previously, I created a ticket on github https://github.com/kamailio/kamailio/issues/3071 and tried to deal with the problem there, but they sent me here for advice. I set up Kamailio IMS , in the end everything turned out great, calls are made, and I decided to check how Kamailio copes with the load. I am creating a load using the sipp application. There is no problem with a low call generation rate, but if you raise the call generation to more than 20 calls per second, some of the calls fail. I compared the calls and saw that the ICSCF does not send a 180 Ringing message towards the S-CSCF [image: image.png] [image: image.png] As I found out further and suggested, the problem is that some calls are cut on the S-CSCF and this is probably due to some kind of timer, but I could not figure out which one. Full logs and dump are attached to the issue on github, below is a log sample by bad dialog 0x7fc133ce61d8 ``` Apr 5 08:24:33 ims-core /usr/local/sbin/kamailio[26061]: DEBUG: ims_dialog [dlg_handlers.c:284]: dlg_iuid_sfree(): freeing dlg iuid [465:10905] (0x7fc133ce61d8) Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1025]: link_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_cb.c:251]: run_create_callbacks(): dialog=0x7fc133ce61d8 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_handlers.c:789]: dlg_onreq(): dialog [0x7fc133ce61d8] added to tm callbacks Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26059]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:35 ims-core /usr/local/sbin/kamailio[26059]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fc133ce61d8 with 1 -> 2 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1293]: next_state_dlg(): dialog 0x7fc133ce61d8 changed from state 1 to state 6, due event 4 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_handlers.c:1489]: dlg_onreply(): dialog 0x7fc133ce61d8 failed (negative reply) Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_cb.c:277]: run_dlg_callbacks(): dialog=0x7fc133ce61d8, type=4 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 1 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fc133ce61d8 with 1 -> 0 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): ref <=0 for dialog 0x7fc133ce61d8 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:196]: destroy_dlg(): destroying dialog 0x7fc133ce61d8 Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_hash.c:207]: destroy_dlg(): removed timer for dlg 0x7fc133ce61d8 [3791:1419] with clid '43-3057631(a)10.2.16.63' and tags '78885556600' Apr 5 08:24:38 ims-core /usr/local/sbin/kamailio[26056]: DEBUG: ims_dialog [dlg_cb.c:277]: run_dlg_callbacks(): dialog=0x7fc133ce61d8, type=8192 ``` What could be the reasons for this behavior and how to diagnose them? I did not observe problems with MEM or CPU during the tests. I will be grateful for any advice.

2 1

How to submit updates for core documentation?
by Ben Kaufman 11 Apr '22

11 Apr '22

Hello, I had a small patch merged for 5.6 to add preprocessor macros #!trydefenv and #!trydefenvs. (https://github.com/kamailio/kamailio/issues/2967), but they need documentation. I believe that they should ultimately end up on this page: https://www.kamailio.org/wiki/cookbooks/devel/core. I don't see this in the /doc section of the repo. What's the process for me to submit this documentation? Ben Kaufman Sr. VoIP Engineer - BCM One +1.612.735.9309 bkaufman(a)bcmone.com<mailto:bkaufman@bcmone.com> 24 hour client support: +1.855.639.6300 [https://www.bcmone.com/files/bcmone-logo.png]<https://www.bcmone.com/> [https://www.bcmone.com/files/twitter-icon-circle.png] <https://www.facebook.com/bcmonenyc/> [https://www.bcmone.com/files/twitter-icon-circle.png] <https://twitter.com/bcm_one/> [https://www.bcmone.com/files/linkedin-icon-circle.png] <https://www.linkedin.com/company/business-communications-management/> NOTE: This e-mail and any attachments are from BCM One, Inc. and are intended solely for the use and review of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail (and any attachments) from your computer and do not copy or disclose it to anyone else.

2 4

reply sent
by Daniel Paape 11 Apr '22

11 Apr '22

Hello, Is there a function that can be called from a module that will return the last response code sent, regardless of whether it was a local or relayed reply? thanks, Daniel

2 1

LCR from_gw function
by Antoine DEBARRE 11 Apr '22

11 Apr '22

Hi, Kamailio 5.5.4 from deb packages I tried to use the lcr function from_gw(lcr_id[, ip_addr, proto]) I've declared several gws with different lcr_id Unfortunately from_gw doesn't work with lcr_id > 1 For example : if (from_gw(2,$si,1)) { .... } ... error message => ki_from_gw(): invalid lcr_id parameter value 2 Thanks in advance ! -- <https://app.livestorm.co/comdata-group/metaverse-what-will-cx-look-like-in-…>

2 1

Kamailio + Asterisk + Voip SIP Trunk = Incorrect IP on ACK
by Luciano Motti 09 Apr '22

09 Apr '22

Hello! I have the following architecture: - Kamailio with RTPEngine (with public access on IP *YY.YY.42.207*) - Asterisk (with no public access, internal IP *172.31.69.198*) I am using a Voip SIP (with public access on IP *54.XXX.XXX.44*) configured as a Trunk on Kamailio using UAC Module. The issue I am facing is that the SIP messages replies I get from the VOIP provider are being destined to Kamailio's public IP (YY.YY.42.207) instead of Asterisk's IP (as sent on the message). For example, this is the 200 message I sent to the VOIP provider (I clearly state that the contact is Asterisk sip:172.31.69.198:5080): 2022/04/07 14:17:19.260864 172.31.32.7:5060 -> 54.XXX.XXX.44:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 54.XXX.XXX.44:5060;rport=5060;branch=z9hG4bK90b6.f7a6b0a4.0 Record-Route: <sip:YY.YY.42.207;lr;ftag=p0BjH21gpa3rc> Call-ID: 464f21c3-3120-123b-91b2-026ef2fede4c From: "419XXXXX998" <sip:38XXXX02@172.31.32.169>;tag=p0BjH21gpa3rc To: <sip:38XXXX02@54.XXX.XXX.44>;tag=8c3bb09e-a909-4cb4-99a7-3c57aa8f946e CSeq: 50116727 INVITE Server: Asterisk PBX 18.11.0 *Contact: <sip:172.31.69.198:5080 <http://172.31.69.198:5080>>* Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER Supported: 100rel, timer, replaces, norefersub Content-Type: application/sdp Content-Length: 239 v=0 o=- 1649321756 1649321759 IN IP4 172.31.69.198 s=Asterisk c=IN IP4 172.31.69.198 t=0 0 m=audio 10010 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=maxptime:150 a=sendrecv But the ACK I get from them is destined to Kamailio instead of Asterisk: 2022/04/07 14:17:19.263469 54.XXX.XXX.44:5060 -> 172.31.32.7:5060 *ACK sip:YY.YY.42.207:5060 SIP/2.0* Route: <sip:YY.YY.42.207;lr;ftag=p0BjH21gpa3rc> Via: SIP/2.0/UDP 54.XXX.XXX.44:5060;branch=z9hG4bK90b6.f7a6b0a4.2 Max-Forwards: 69 From: "419XXXXX998" <sip:38XXXX02@172.31.32.169>;tag=p0BjH21gpa3rc To: <sip:38XXXX02@54.XXX.XXX.44>;tag=8c3bb09e-a909-4cb4-99a7-3c57aa8f946e Call-ID: 464f21c3-3120-123b-91b2-026ef2fede4c CSeq: 50116727 ACK Contact: <sip:voip.voip-sbc.6792.fab37901@54.XXX.XXX.44:5060> Content-Length: 0 This causes Kamailio to not know where to forward the message to... Asterisk never gets the reply. This is happening to one of the SIP Trunks I am using, with the other, everything is fine. Is there anything I can do to work around it (other than contacting the provider to fix on their end)? Thanks! ps: I have attached the full SIP messages trail to help.

2 1

Htable reload
by David Villasmil 07 Apr '22

07 Apr '22

Hello all, I’ve been trying to figure out how htable reloads happen. Does it replaces the existing one or creates a new one, populates it from the db and then renames it? The latter would be (I think) ideal, even if it uses more resources. Thanks! David -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

4 6

Kamailio 5.5.4 lcr command disabled
by bayu p 07 Apr '22

07 Apr '22

Hello Expert, We faces problem in utilizing lcr command line in "kamctl lcr show_gws", whereas kamailio version is 5.5.4 which are new kamailio release, "kamctl lcr show_gws" shown result "command disabled". in this case, LCR module is already been uploaded and the systemd has been running well active kamailio. Could you share, what probably wrong in my kamailio configuration? Best Regards,

2 4

Kamailio 5.5.4 lcr command disabled
by bayu p 07 Apr '22

07 Apr '22

Hello Expert, I have problem in utilizing lcr command line in "kamctl lcr show_gws", whereas my kamailio version is 5.5.4 which are new kamailio release, "kamctl lcr show_gws" shown result "command disabled". in this case, LCR module is already been uploaded and the systemd has been running active kamailio. Here detailed screenshot : [image: image.png] Could you share, what probably wrong in my kamailio configuration? Best Regards,

1 1

Kamailio 5.5.4 lcr command disabled
by bayu p 07 Apr '22

07 Apr '22

problem in "kamctl lcr show_gws" resulting "command disabled". Kamailio uses LCR module uploaded and running active kamailio. what probably wrong in kamailio? [image: image.png]

1 0

Kamailio 5.5.4 lcr command disabled
by bayu p 07 Apr '22

07 Apr '22

problem in "kamctl lcr show_gws" (kamailio version 5.5.4 / new release) resulting "command disabled". LCR module had been uploaded on running well active kamailio. Could you share, what probably wrong in my kamailio configuration? [image: image.png] Best regards

1 0

Kamailio 5.5.4 lcr command disabled
by bayu p 07 Apr '22

07 Apr '22

Hello Expert, I have problem in utilize lcr command line "kamctl lcr show_gws", whereas kamailio version is 5.5.4 (new kamailio release), those resulting "command disabled". In this case, LCR module is already been uploaded and the systemd has been running active kamailio. Could you share, what probably wrong in my kamailio configuration? [image: image.png] Best regards

1 0

kamailio 5.5.4 source not found file pcre.h file
by bayu p 07 Apr '22

07 Apr '22

Dear Developer, would you please share which pcre.h file ? due to my compiling source kamailio 5.5.4 found error as captured below. In file included from dialplan.c:59: dialplan.h:33:10: fatal error: pcre.h: No such file or directory 33 | #include <pcre.h> | ^~~~~~~~ compilation terminated. Kind Regards,

2 2

Kamailio preprocessor to get hostname
by David VILLAUME 06 Apr '22

06 Apr '22

Hello all , Do you know any way to get the hostname of my server at kamailio runtime ? The simple idea behind this would be ton import a specific environment file base on hostname. Regards, David

2 1

parse XML nested name-spaces
by Artur Hovsepyan 06 Apr '22

06 Apr '22

good evening everyone, can you please help how to parse following XML body and get the "<gml:pos>31.204359 -44.512358</gml:pos>" in a variable? <?xml version="1.0"?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:con="urn:ietf:params:xml:ns:geopriv:conf" entity="sip:+6478897789@ims.mnc0xx.mccxxx.3gppnetwork.org"> <dm:device id="Wifi"> <gp:geopriv> <gp:location-info> <gs:Circle srsName="urn:ogc:def:crs:EPSG::5524"> <gml:pos>31.204359 -44.512358</gml:pos> <gs:radius uom="urn:ogc:def:uom:EPSG::8190">10.578000</gs:radius> </gs:Circle> <con:confidence pdf="normal">92</con:confidence> </gp:location-info> <gp:method>DBH_HELO</gp:method> <gp:usage-rules/> </gp:geopriv> <dm:timestamp>2022-04-05T19:16:34Z</dm:timestamp> </dm:device> </presence> i tried few variants: xinfo("GML_LOC: $xml(x=>xpath:/pidf:presence/pidf:dm:device/pidf:gp:geopriv/pidf:gp:location-info/pidf:gs:Circle/pidf:gml:pos)\n") xinfo("GML_LOC: $xml(x=>xpath:/pidf:presence/pidf:dm\:device/pidf:gp\:geopriv/pidf:gp\:location-info/pidf:gs\:Circle/pidf:gml\:pos)\n"); xinfo("GML_LOC: $xml(x=>xpath:/pidf:presence/pidf:dm:device/pidf:gp:geopriv/pidf:gp:location-info/pidf:gs:Circle/pidf:gml:pos)\n"); xinfo("GML_LOC: $xml(x=>xpath:/pidf:presence/dm:device/gp:geopriv/gp:location-info/gs:Circle/gml:pos)\n"); and end up with error "unable to evaluate xpath expression": ERROR: xmlops [pv_xml.c:308]: pv_get_xml(): unable to evaluate xpath expression [/pidf:presence/dm:device/gp:geopriv/gp:location-info/gs:Circle/gml:pos/70] thanks in advance,Art

2 2

least cost routing module activation error
by bayu p 06 Apr '22

06 Apr '22

Dear Kamailio Expert, I already add module lcr, but found error when searching pvar "ddn" inside source code core/pvapi.c at line 923, as shown error log captured below : Apr 6 10:26:50 kamal /usr/sbin/kamailio[180954]: ERROR: <core> [core/pvapi.c:923]: pv_parse_spec2(): error searching pvar "ddn" Apr 6 10:26:50 kamal /usr/sbin/kamailio[180954]: ERROR: <core> [core/pvapi.c:1126]: pv_parse_spec2(): wrong char [n/110] in [$ddn] at [3 (0)] Apr 6 10:26:50 kamal /usr/sbin/kamailio[180954]: ERROR: xlog [xlog.c:511]: xdbg_fixup_helper(): wrong format[Domain of destination: $ddn] Apr 6 10:26:50 kamal /usr/sbin/kamailio[180954]: ERROR: <core> [core/route.c:1166]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:901 Apr 6 10:26:50 kamal /usr/sbin/kamailio[180954]: ERROR: <core> [core/route.c:1166]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:903 Apr 6 10:26:50 kamal /usr/sbin/kamailio[180954]: ERROR: <core> [core/route.c:1166]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:918 The question are, how to define correct "INVITE" methode (or correct format) inside route[LCR] which is already defined inside kamailio.cfg: route[LCR] { if (status=="200") { xlog("LCR: Inside the LCR routen"); } if(method=="INVITE") { xlog("We got an invite"); if(!load_gws(1, $rU, $var(caller_uri))) { xlog("Couldn't load gateways"); sl_send_reply("500", "Server Internal Error - Cannot load gateways"); exit; } else { xlog("GW Selected '$avp(i:709)'n"); xlog("Domain of destination: $ddn"); xlog("To URI: $tun"); } if(!next_gw()) { xlog("Couldn't proceed to next gateway"); sl_send_reply("503", "Service not available, no gateways found"); exit; } else { xlog("Calling the first matched gatewayn"); xlog("ruri_user_avp: '$avp(i:500)'n"); xlog("To URI after next_gw: $tun"); xlog("Request URI: $rUn"); } } } Kind Regards

1 0

escape firt two lines from get_body_part to get xml only part
by Artur Hovsepyan 06 Apr '22

06 Apr '22

hello everyone, i am trying to parse the xml from the message body: get_body_part("application/pidf+xml", "$var(pbody)"); and i am getting the following in my pbody var: Content-Disposition: render;handling=optionalContent-ID: <sip:+6478897789@ims.mnc0xx.mccxxx.3gppnetwork.org><?xml version="1.0"?><presence xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:con="urn:ietf:params:xml:ns:geopriv:conf" entity="sip:+6478897789@ims.mnc0xx.mccxxx.3gppnetwork.org"><dm:device id="Wifi"><gp:geopriv><gp:location-info><gs:Circle srsName="urn:ogc:def:crs:EPSG::5524"><gml:pos>31.204359 -44.512358</gml:pos><gs:radius uom="urn:ogc:def:uom:EPSG::8190">10.578000</gs:radius></gs:Circle><con:confidence pdf="normal">92</con:confidence></gp:location-info><gp:method>DBH_HELO</gp:method><gp:usage-rules/></gp:geopriv><dm:timestamp>2022-04-05T19:16:34Z</dm:timestamp></dm:device></presence> how can i escape the first two lines in order to get the xml part of the content? thanks in advance,Art

2 6

Jansson question
by Barry Flanagan 06 Apr '22

06 Apr '22

Hi I am trying to use the jannson_get function to pull field "secret" from the below json: {"3":{"options":{"secret":"mybigsecret"}}} This works is I use jansson_get("3.options.secret"..... However, I need to know the value of "3" in order to use it. I have tried all the variations on path I can find, but none apart from using the actual root value work for me. How can I either: 1. Construct a PATH which will pick this up, or 2. Obtain this root value ("3" in my example) I have tried testing using https://jsonpath.com/ and a path of "$..secret" and "$..options.secret" works there, but not in jansson kamailio module. Any assistance much appreciated. Thanks -- -Barry

2 1

escape firt two lines from get_body_part to get xml only part
by Does it really matter? 06 Apr '22

06 Apr '22

1 0

Manual usage and example kamailio kamctl
by bayu p 06 Apr '22

06 Apr '22

Dear Expert Kamailio, I use this tutorial kamctl to make kamailio and other sip server communicated https://manpages.ubuntu.com/manpages/xenial/man8/kamctl.8.html but, i cannot found further tutorial how use kamctl. Could you please share, the detail/further tutorial and example of kamctl usage.. Since i always found error/failure during execute some command from the link, here captured: (1). # kamctl cr dump -e \E[37;31mERROR: Error opening Kamailio's FIFO /var/run/kamailio/kamailio_rpc.fifo -e \E[37;31mERROR: Make sure you have loaded the jsonrpcs module and set FIFO transport parameters (2). # kamctl lcr show_gws -e \E[37;31mERROR: command disabled (3). # kamctl lcr reload -e \E[37;31mERROR: command disabled (4). # kamctl ping 192.168.31.50 { "jsonrpc": "2.0", "error": { "code": 400, "message": "Invalid request uri \"192.168.31.50\"" }, "id": 76608 } (5). # kamctl cr reload { "jsonrpc": "2.0", "error": { "code": 500, "message": "Method Not Found" }, "id": 76659 } Warm Regards, >

5 16

Kamailio stop processing SIP in high call load with dlg replication via DMQ
by José Seabra 05 Apr '22

05 Apr '22

Hi there, I've two kamailio servers sharing dlg vars between them and I've noticed that during high call load (~50-70 CPS) the kamailio that is processing all the calls and sharing the dialogs with the other kamailio, stops processing SIP. If I set the parameter enable_dmq to 0 I cannot replicate the issue so I assume that it's related to dialog replication through DMQ. *Kamailio version: *5.4.7 - I've tested with recent versions but the issue remains *Configurations of Kamailio_1:* # ----- dialog params ----- modparam("dialog", "dlg_flag", FLD_DLG) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "enable_dmq", 1) modparam("dialog", "h_id_start", 1000) modparam("dialog", "h_id_step", 6000) # ----- dmq params ----- 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) *Configurations of Kamailio_2:* # ----- dialog params ----- modparam("dialog", "dlg_flag", FLD_DLG) modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "enable_dmq", 1) modparam("dialog", "h_id_start", 5000) modparam("dialog", "h_id_step", 6000) # ----- dmq params ----- 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) In this link you can find the kamctl trap <https://textbin.net/quykw71nyl>output after kamailio stop processing SIP. Thank you Best Regards -- Cumprimentos José Seabra

1 0

Auth_ephemeral Module > username_format not accepted
by Luciano Motti 05 Apr '22

05 Apr '22

Hi! I was able to successfully use the auth_ephemeral module on my environment: Kamailio > Asterisk > ARI I ran into a problem with ARI, where Asterisk wouldn't send the complete from URI to ARI program, just the first part (timestamp), and the most important part (the username) isn't forwarded. For example: Kamailio username: 1649106119:1001 Asterisk only forwards 1649106119 to ARI, which makes it impossible for me to track the user. So I planned on using the deprecated username_format from Auth Ephemeral module: https://kamailio.org/docs/modules/4.1.x/modules/auth_ephemeral.html#auth_ep… By switching the timestamp with the username, my problems would be fixed. After setting the variable, and trying to register on Kamailio with username 1001:1649106119, I get an error message: SIP/2.0 400 Bad From URI Am I doing something wrong? Thanks!

2 2

Re: [SR-Users] More than TCP 800 concurrent calls, slows Kamailio (LUA FILE API REQUESTS)
by Henning Westerholt 05 Apr '22

05 Apr '22

Hello, please keep the list in CC, that others can comment as well. Beside from the obvious (improving the performance of the lua API call), you could use indeed asynchronous processing. If you just use the lua code to emit the REST request, using a native http client module would be probably also faster as doing it over lua. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Giovanni Jose <gio.jose(a)gmail.com> Sent: Wednesday, March 30, 2022 5:17 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] More than TCP 800 concurrent calls, slows Kamailio (LUA FILE API REQUESTS) Hello Henning, Thanks so much for the fast response I just commented the loop and I was hitting the backend and it's slow anyway maybe it's because, for this type of implementation when the destination of the call is decided by the API backend, I need to use the http_async_client module? I am noticing that for high volume calls kamailio slows the traffic and shows errors because there's a delay that is been added when the backend responds for every call. On Tue, Mar 29, 2022 at 11:53 PM Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> wrote: Hello, why are you sleeping for 1s in the loop? This will cause Kamailio to block processing. I also do not see any stop condition on the loop, so it will loop until the limit. 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 Giovanni Jose Sent: Tuesday, March 29, 2022 9:46 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] More than TCP 800 concurrent calls, slows Kamailio (LUA FILE API REQUESTS) Hello Guys I am having this issue where kamailio is receiving requests from SIPp (we are currently testing the platform and doing QA) but if we do more than 800 concurrent calls kamailio starts failing and slowing the requests, The scenario is the following: I am sending 5000 calls at 100 CPS on TCP and I am having this route in the configuration file: # Handle the calls to api route[CALL_API] { xlog("L_NOTICE"," Call request $var(call_request) method: $rm \n"); $var(loop_true)=1; while ($var(loop_true)) { if(!lua_run("call_request","$var(call_request)","$sht(token=>new_token)")) { xlog("L_NOTICE", "SCRIPT: failed to execute lua function!\n"); } if ($var(loop_true)){ sleep("1"); } } xlog("L_NOTICE", "SCRIPT: Sucess to execute lua function!\n"); } So I am executing a LUA script for the requests and the API response will tell the destination of the call. At 800 concurrent calls, I can notice SLOWLINESS in the SIPp testing tool, and then I will start receiving 408 timeouts. This sounds like a load issue or something because I believe there's a time that it's been added every time we hit the backend and wait for the response. any help will be appreciated Regards Gio

2 1

Jansson question
by Barry Flanagan 05 Apr '22

05 Apr '22

Hi I am trying to use the jannson_get function to pull field "secret" from the below json: {"3":{"options":{"secret":"mybigsecret"}}} This works is I use jansson_get("3.options.secret"..... However, I need to know the value of "3" in order to use it. I have tried all the variations on path I can find, but none apart from using the actual root value work for me. How can I either: 1. Construct a PATH which will pick this up, or 2. Obtain this root value ("3" in my example) I have tried testing using https://jsonpath.com/ and a path of "$..secret" and "$..options.secret" works there, but not in jansson kamailio module. Any assistance much appreciated. Thanks -- -Barry

1 0

rpm.kamailio.org is down
by Riccardo Villa 05 Apr '22

05 Apr '22

Host is up and responding to ping but not to http requests. Riccardo -- -- NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.

2 1

Asterisk, unable to find dialog for ACK with route param and call-id
by Trevor Peirce 05 Apr '22

05 Apr '22

Hello, I'm having some trouble with what I think is the dialog module. I've got Kamailio 5.5.4 running well for some time. Recently I added Asterisk to the mix and have come across an issue. Call to Kamailio. Kamailio sends it to Asterisk. Asterisk may decide to "forward" the call. To do this it will place a new outbound call through Kamailio. From the user perspective, this works absolutely fine (invite, ringing, ok, bye). The acc module handles it fine also. However dialog does not, and the events for ok and bye do not fire on the original call. They do fire for the forwarded call. I've added some logging output to try to isolate the problem, but I'm no further ahead. Here's what I have. Any suggestions? ** Call initiated ** INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=100 ru=<null> tu=sip:destination@endpoint DLG_status=<null> dlg-h-id=3360 INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=100 ru=<null> tu=sip:fwddest@0.0.0.1:5060 DLG_status=<null> dlg-h-id=12036 INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=183 ru=<null> tu=sip:fwddest@0.0.0.1:5060 DLG_status=<null> dlg-h-id=12036 INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=183 ru=<null> tu=sip:destination@endpoint DLG_status=<null> dlg-h-id=3360 INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=200 ru=<null> tu=sip:fwddest@0.0.0.1:5060 DLG_status=<null> dlg-h-id=12036 CRITICAL: dialog [dlg_timer.c:200]: update_dlg_timer(): Trying to update a bogus dlg tl=0x7fa0494006e8 tl->next=(nil) tl->prev=(nil) ERROR: dialog [dlg_hash.c:1329]: update_dlg_timeout(): failed to update dialog lifetime CRITICAL: dialog [dlg_timer.c:200]: update_dlg_timer(): Trying to update a bogus dlg tl=0x7fa0494006e8 tl->next=(nil) tl->prev=(nil) ERROR: dialog [dlg_hash.c:1329]: update_dlg_timeout(): failed to update dialog lifetime ERROR: dialog [dlg_profile.c:1028]: dlg_set_timeout_by_profile(): Unable to set timeout on 3306:12036 NOTICE: acc [acc.c:270]: acc_log_request(): ACC: transaction answered: timestamp=1648611824;time_unix=1648611824.346;method=INVITE;from_tag=as292200a1;to_tag=as75834dc4;call_id=7cef233547dca0ac7882ce5249b3b54c;code=200;reason=OK INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=200 ru=<null> tu=sip:destination@endpoint DLG_status=<null> dlg-h-id=<null> NOTICE: acc [acc.c:270]: acc_log_request(): ACC: transaction answered: timestamp=1648611824;time_unix=1648611824.354;method=INVITE;from_tag=as730369e7;to_tag=as3b06b3e2;call_id=53bad4f0034b61a5745163d82daef402;code=200;reason=OK INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=200 ru=<null> tu=sip:destination@endpoint DLG_status=<null> dlg-h-id=<null> WARNING: dialog [dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK with route param '161.02d' [353:3360] and call-id '53bad4f0034b61a5745163d82daef402' WARNING: dialog [dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK with route param '161.02d' [353:3360] and call-id '53bad4f0034b61a5745163d82daef402' ** The call is answered and endpoints can talk to each other ** ** Now the original caller hangs up ** WARNING: dialog [dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for BYE with route param '161.02d' [353:3360] and call-id '53bad4f0034b61a5745163d82daef402' NOTICE: acc [acc.c:270]: acc_log_request(): ACC: transaction answered: timestamp=1648611831;time_unix=1648611831.933;method=BYE;from_tag=as730369e7;to_tag=as3b06b3e2;call_id=53bad4f0034b61a5745163d82daef402;code=200;reason=OK INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=100 ru=<null> tu=sip:fwddest@0.0.0.1:5060 DLG_status=<null> dlg-h-id=12036 INFO: <script>: onreply_route[MANAGE_REPLY] branch [0] rm=INVITE rs=200 ru=<null> tu=sip:fwddest@0.0.0.1:5060 DLG_status=<null> dlg-h-id=12036 ERROR: <script>: got result for bye = Bye!; DLG_lifetime = 8 NOTICE: acc [acc.c:270]: acc_log_request(): ACC: transaction answered: timestamp=1648611832;time_unix=1648611832.115;method=BYE;from_tag=as292200a1;to_tag=as75834dc4;call_id=7cef233547dca0ac7882ce5249b3b54c;code=200;reason=OK ERROR: dialog [dlg_handlers.c:363]: dlg_terminated_confirmed(): failed to get dialog from params! ** Everything ends cleanly on the other SIP endpoints ** What can I do from here to try to isolate this further? Thanks, -- Trevor Peirce AcroVoice Solutions Inc

2 4

Kamailio as a SBC
by Nileshwar Goswami 05 Apr '22

05 Apr '22

Hi There, I'm looking out for an SBC and came across your platform. Can Kamailio work as a SBC and provide all the functionalities of a SBC ? A quick reply will be appreciated. Best Regards, Nileshwar Goswami

2 1

RTPENGINE : Kamailio - Get status if max sessions reached
by Youssef Boujraf 01 Apr '22

01 Apr '22

Dear, QUESTION : Through kamailio,We are using rtpengine_manage and the return value is true or false but don"t know for which reason. * How to be informed if rtpengine reach the maximum of sessions and will not accept any rtp routing ? * We have seen if rtpengine reached the max-session; The call is accept by kamailio and finally no audio because SDP not processed- kamailio.log Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: ALERT: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} <script>: [NATMANAGE] branch_id:0 ruri: sip:9919993@public:32617;transport=UDP;rinstance=f5d124565504bdb6, method:INVITE, status:<null>, extra_id: z9hG4bK-524287-1---290944f5547c740a0, rtpengine_manage: replace-origin replace-session-connection via-branch=extraMar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine_funcs.c:144]: check_content_type(): type <application/sdp> found validMar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:1834]: build_rtpp_socks(): same rtpengines list version: 1 (1648562844)Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3276]: select_rtpp_node_old(): rtpengine hash table lookup failed to find node for calllen=24 callid=nIdGvZZNiFnt3_r0xSIKpQ.. viabranch=z9hG4bK-524287-1---290944f5547c740a0Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3167]: select_rtpp_node_new(): sum is = 27Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2691]: rtpp_function_call(): proxy reply: d6:result10:load limit7:message30:Parallel session limit reachedeMar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: INFO: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2715]: rtpp_function_call(): proxy udp:192.168.1.33:2223 has reached its load limit (Parallel session limit reached) - trying next oneMar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:1834]: build_rtpp_socks(): same rtpengines list version: 1 (1648562844) Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3276]: select_rtpp_node_old(): rtpengine hash table lookup failed to find node for calllen=24 callid=nIdGvZZNiFnt3_r0xSIKpQ.. viabranch=z9hG4bK-524287-1---290944f5547c740a0 Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3167]: select_rtpp_node_new(): sum is = 27 Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2691]: rtpp_function_call(): proxy reply: d6:result10:load limit7:message30:Parallel session limit reachede Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: INFO: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2715]: rtpp_function_call(): proxy udp:127.0.0.1:2223 has reached its load limit (Parallel session limit reached) - trying next one Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:1834]: build_rtpp_socks(): same rtpengines list version: 1 (1648562844) Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3276]: select_rtpp_node_old(): rtpengine hash table lookup failed to find node for calllen=24 callid=nIdGvZZNiFnt3_r0xSIKpQ.. viabranch=z9hG4bK-524287-1---290944f5547c740a0 Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3167]: select_rtpp_node_new(): sum is = 27 Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: INFO: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2900]: rtpp_test(): rtpengine instance <udp:127.0.0.1:2223> found, support for it enabled Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: INFO: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2900]: rtpp_test(): rtpengine instance <udp:192.168.1.33:2223> found, support for it enabled Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3167]: select_rtpp_node_new(): sum is = 27 Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: ERROR: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3330]: select_rtpp_node(): rtpengine failed to select new for calllen=24 callid=nIdGvZZNiFnt3_r0xSIKpQ.. Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21065]: ERROR: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2678]: rtpp_function_call(): no available proxies Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21070]: ALERT: {2 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} <script>: [NATMANAGE] branch_id:0 ruri: <null>, method:INVITE, status:100, extra_id: z9hG4bK-524287-1---290944f5547c740a0, rtpengine_manage: replace-origin replace-session-connection trust-address via-branch=extra Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21069]: ALERT: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} <script>: [NATMANAGE] branch_id:1 ruri: sip:9919993@public:32617;transport=UDP;rinstance=f5d124565504bdb6, method:INVITE, status:<null>, extra_id: z9hG4bK-524287-1---290944f5547c740a0, rtpengine_manage: replace-origin replace-session-connection Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21069]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:1834]: build_rtpp_socks(): same rtpengines list version: 1 (1648562844) Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21069]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3276]: select_rtpp_node_old(): rtpengine hash table lookup failed to find node for calllen=24 callid=nIdGvZZNiFnt3_r0xSIKpQ.. viabranch= Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21069]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:3167]: select_rtpp_node_new(): sum is = 27 Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21069]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2691]: rtpp_function_call(): proxy reply: d7:warning38:Call-ID not found or tags didn't match6:result2:oke Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21069]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2784]: rtpp_function_call(): rtpengine hash table insert node=udp:192.168.1.33:2223 for calllen=24 callid=nIdGvZZNiFnt3_r0xSIKpQ.. viabranch= Mar 29 16:08:14 kamailio /usr/sbin/kamailio[21069]: DEBUG: {1 2 INVITE nIdGvZZNiFnt3_r0xSIKpQ..} rtpengine [rtpengine.c:2801]: rtpp_function_call(): rtpengine hash table remove entry for callen=24 callid=nIdGvZZNiFnt3_r0xSIKpQ.. viabranch= - rtpengine.log : Mar 29 16:08:14 rtp01srv rtpengine[3921]: INFO: [nIdGvZZNiFnt3_r0xSIKpQ..]: [control] Received command 'offer' from 192.168.1.41:42822 Mar 29 16:08:14 rtp01srv rtpengine[3921]: DEBUG: [nIdGvZZNiFnt3_r0xSIKpQ..]: [control] Dump for 'offer' from 192.168.1.41:42822: { "supports": [ "load limit" ], "sdp": "v=0 Mar 29 16:08:14 rtp01srv rtpengine[3921]: o=Zoiper 141319690 1 IN IP4 192.168.30.216 Mar 29 16:08:14 rtp01srv rtpengine[3921]: s=Z Mar 29 16:08:14 rtp01srv rtpengine[3921]: c=IN IP4 192.168.30.216 Mar 29 16:08:14 rtp01srv rtpengine[3921]: t=0 0 Mar 29 16:08:14 rtp01srv rtpengine[3921]: m=audio 8000 RTP/AVP 0 101 8 3 97 Mar 29 16:08:14 rtp01srv rtpengine[3921]: a=rtpmap:101 telephone-event/8000 Mar 29 16:08:14 rtp01srv rtpengine[3921]: a=fmtp:101 0-16 Mar 29 16:08:14 rtp01srv rtpengine[3921]: a=rtpmap:97 iLBC/8000 Mar 29 16:08:14 rtp01srv rtpengine[3921]: a=fmtp:97 mode=30 Mar 29 16:08:14 rtp01srv rtpengine[3921]: a=sendrecv Mar 29 16:08:14 rtp01srv rtpengine[3921]: ", "replace": [ "origin", "session-connection" ], "call-id": "nIdGvZZNiFnt3_r0xSIKpQ..", "via-branch": "z9hG4bK-524287-1---290944f5547c740a0", "received-from": [ "IP4", "public" ], "from-tag": "75983054", "command": "offer" } Mar 29 16:08:14 rtp01srv rtpengine[3921]: ERR: [nIdGvZZNiFnt3_r0xSIKpQ..]: [core] Parallel session limit reached (2) Mar 29 16:08:14 rtp01srv rtpengine[3921]: INFO: [nIdGvZZNiFnt3_r0xSIKpQ..]: [control] Replying to 'offer' from 192.168.1.41:42822 (elapsed time 0.000058 sec) Mar 29 16:08:14 rtp01srv rtpengine[3921]: DEBUG: [nIdGvZZNiFnt3_r0xSIKpQ..]: [control] Response dump for 'offer' to 192.168.1.41:42822: { "result": "load limit", "message": "Parallel session limit reached" } Mar 29 16:08:14 rtp01srv rtpengine[3921]: INFO: [control] Received command 'ping' from 192.168.1.41:42822 Mar 29 16:08:14 rtp01srv rtpengine[3921]: DEBUG: [control] Dump for 'ping' from 192.168.1.41:42822: { "command": "ping" } Mar 29 16:08:14 rtp01srv rtpengine[3921]: INFO: [control] Replying to 'ping' from 192.168.1.41:42822 (elapsed time 0.000001 sec) Mar 29 16:08:14 rtp01srv rtpengine[3921]: DEBUG: [control] Response dump for 'ping' to 192.168.1.41:42822: { "result": "pong" } How to get this information then we could cancel the call or send sip message that the number of max call is reached ? -- Youssef

3 7

Kamailio PCSCF route logic
by Weiqi Yao 30 Mar '22

30 Mar '22

Hello community, We made some modifications to Kamailio PCSCF sample cfg file, so when PCSCF receiving an tcp SUBSCRIBE message it add ;transport=tcp to the end of Contact URI. Below is what we added the route block right after if (is_method("INVITE|SUBSCRIBE")) logic if (is_method("SUBSCRIBE") && proto=='tcp') { $var(original_contact_header) = $ct; $var(new_contact_header) = $(var(original_contact_header){re.subst,/(.*:.*)(>);/\1;transport=tcp>/g}); remove_hf("Contact"); append_hf("Contact: $var(new_contact_header)\r\n"); msg_apply_changes(); } We did see the ;transport=tcp been added but we also seeing a bad line ;alias=[...] is added before the To: line [cid:image001.png@01D84375.8D109B20] Does anyone know what function might cause this ;alias been added before To: line? BR, Weiqi

2 2

Parallel forking call drop scenario
by Koray Vatansever 30 Mar '22

30 Mar '22

Hi everyone, I'm facing the following situation. Clients are connected over TLS. Therefore there is no retransmission in Kamailio. How can I prevent this call drop? +---+ +-----------+ +-----+ +-----+ | A | | Kamailio | | B1 | | B2 | +---+ +-----------+ +-----+ +-----+ | | | | | INVITE | | | |------------------------------------>| | | | | -------------------\ | | | |-| Parallel forking | | | | | |------------------| | | | | | | | | INVITE | | | |---------------------->| | | | | | | | INVITE | | | |--------------------------------------------------->| | | | | | | 180 Ringing | | | |<----------------------| | | | | | | | | 180 Ringing | | |<---------------------------------------------------| | | | ------------------------\ | | | |-| User answers the call | | | | | |-----------------------| | | | | | | | 200 OK | | | |<----------------------| | | | | | | 200 OK | | | |<------------------------------------| | | | | | | | ACK | | | |------------------------------------>| | | | | | | | | ACK | | | |---------------------->| | | ------------------------------\ | | | |-| Session established with B1 | | | | | |-----------------------------| | | | | | | | ----------------------------\ | | | |-| Client changes network | | | | | | LTE to Wifi or vice versa | | | | | | Temporary connection lost | | | CANCEL | | |---------------------------| | |----------------------------------------------X | | | | | -------------------------------------------------\ | | | |-| Reconnected with different IP | | | | | | CANCEL is missed and client continues ringing. | | | | | | User answers the call. | | | | 200 OK | |------------------------------------------------| | |<---------------------------------------------------| | | | | | 200 OK | | | |<------------------------------------| | | | | | | | | | BYE | | |<---------------------------------------------------| | | | | | BYE | | | |<------------------------------------| | | | ---------------------------\ | | | |-| Session terminated by B2 | | | | | | Call Drop | | | | | |--------------------------| | | |

2 2

More than TCP 800 concurrent calls, slows Kamailio (LUA FILE API REQUESTS)
by Giovanni Jose 30 Mar '22

30 Mar '22

Hello Guys I am having this issue where kamailio is receiving requests from SIPp (we are currently testing the platform and doing QA) but if we do more than 800 concurrent calls kamailio starts failing and slowing the requests, The scenario is the following: I am sending 5000 calls at 100 CPS on TCP and I am having this route in the configuration file: # Handle the calls to api route[CALL_API] { xlog("L_NOTICE"," Call request $var(call_request) method: $rm \n"); $var(loop_true)=1; while ($var(loop_true)) { if(!lua_run("call_request","$var(call_request)","$sht(token=>new_token)")) { xlog("L_NOTICE", "SCRIPT: failed to execute lua function!\n"); } if ($var(loop_true)){ sleep("1"); } } xlog("L_NOTICE", "SCRIPT: Sucess to execute lua function!\n"); } So I am executing a LUA script for the requests and the API response will tell the destination of the call. At 800 concurrent calls, I can notice SLOWLINESS in the SIPp testing tool, and then I will start receiving 408 timeouts. This sounds like a load issue or something because I believe there's a time that it's been added every time we hit the backend and wait for the response. any help will be appreciated Regards Gio

2 1

dispatcher socket attrs binding
by David Villasmil 29 Mar '22

29 Mar '22

Hello guys, Im starting kamailio with listen=0.0.0.0:5060 and in my dispatcher list i have in the attrs something like: socket=udp:172.17.0.2:5060 That IP address belongs to kamailio's host and it is binging to it. Is it right i can't set a specific IP in the socket attribute if listen is 0.0.0.0? maybe i should be able to? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 4

kamailio - mariadb hosted on remote server - issue
by Youssef Boujraf 29 Mar '22

29 Mar '22

Dear all, I don't belive to connect Kamailio to a remote Mariadb will take too much time. STEP 1 : KAMAILIO : -------------------------------- $ sudo kamailio -v version: kamailio 5.5.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 10.2.1 STEP 2 : Set the kamctlrc config ------------------------------------------------ KAMAILIO IP : 192.168.1.41 MARIADB IP : 192.168.1.39 - /etc/kamailio/kamctlrc SIP_DOMAIN=example.be DBENGINE=MYSQL DBHOST=192.168.1.39 // where the mariadb is installed DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="XX" DBROUSER="kamailioro" DBROPW="XX" DBACCESSHOST=192.168.1.41 // where kamctl is launched (here kamailio srv) DBROOTUSER="root" DBROOTPW="kamailio" CHARSET="latin1" STEP 3 : MARIADB : hosted on different srv than kamailio -------------------------------------------------------------------------------------- IP : 192.168.1.39 - /etc/mysql/mariadb.conf.d/50-server.cnf # this is only for the mysqld standalone daemon [mysqld] # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. #bind-address = 127.0.0.1 bind-address = 0.0.0.0 STEP 4 : TEST : Reote connection with the DB ---------------------------------------------------------------------- REMOTE IP : 192.168.1.41 DB IP : 192.168.1.39 $ sudo mysql -u root -h 192.168.1.39 -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 298 Server version: 10.5.15-MariaDB-1:10.5.15+maria~bullseye mariadb.org binary distribution Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]>The connection is established with success. STEP 5 : KAMAILIO DB : creation ---------------------------------------------------- $ sudo kamdbctl create -e \E[37;33mINFO: creating database kamailio ... -e \E[37;33mINFO: granting privileges to database kamailio ... -e \E[37;33mINFO: creating standard tables into kamailio ... -e \E[37;33mINFO: Core Kamailio tables successfully created. Create the presence related tables? (y/n): y -e \E[37;33mINFO: creating presence tables into kamailio ... -e \E[37;33mINFO: Presence tables successfully created. Create the tables for imc cpl siptrace domainpolicy carrierroute drouting userblocklist htable purple uac pipelimit mtree sca mohqueue rtpproxy rtpengine secfilter? (y/n): y -e \E[37;33mINFO: creating extra tables into kamailio ... -e \E[37;33mINFO: Extra tables successfully created. Create the tables for uid_auth_db uid_avp_db uid_domain uid_gflags uid_uri_db? (y/n): y -e \E[37;33mINFO: creating uid tables into kamailio ... -e \E[37;33mINFO: UID tables successfully created. STEP 6 : DB : verify the users creation and rights -------------------------------------------------------------------------- MariaDB [(none)]> select user, host from mysql.user; +-------------+--------------+ | User | Host | +-------------+--------------+ | kamailio | 192.168.1.39 | | kamailioro | 192.168.1.39 | | kamailio | 192.168.1.41 | | kamailioro | 192.168.1.41 | | root | 192.168.1.41 | | kamailio | localhost | | kamailioro | localhost | | mariadb.sys | localhost | | mysql | localhost | | root | localhost | +-------------+--------------+ 10 rows in set (0.001 sec) MariaDB [(none)]> SHOW GRANTS FOR kamailio(a)192.168.1.41; +--------------------------------------------------------------------------------------------------------------------+ | Grants for kamailio(a)192.168.1.41 | +--------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO `kamailio`(a)`192.168.1.41` IDENTIFIED BY PASSWORD '*157PASSWORD' | | GRANT ALL PRIVILEGES ON `kamailio`.* TO `kamailio`(a)`192.168.1.41` | +--------------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.000 sec) MariaDB [(none)]> SHOW GRANTS FOR kamailio(a)192.168.1.39; +--------------------------------------------------------------------------------------------------------------------+ | Grants for kamailio(a)192.168.1.39 | +--------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO `kamailio`(a)`192.168.1.39` IDENTIFIED BY PASSWORD '*157PASSWORD' | | GRANT ALL PRIVILEGES ON `kamailio`.* TO `kamailio`(a)`192.168.1.39` | +--------------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.000 sec) MariaDB [(none)]> SHOW GRANTS FOR kamailio@localhost; +-----------------------------------------------------------------------------------------------------------------+ | Grants for kamailio@localhost | +-----------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO `kamailio`@`localhost` IDENTIFIED BY PASSWORD '*157PASSWORD' | | GRANT ALL PRIVILEGES ON `kamailio`.* TO `kamailio`@`localhost` | +-----------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.000 sec)STEP 7 : ADDRESS TABLE : add new ip address$ sudo systemctl restart kamailio sipsecure@kamailio:/etc$ sudo kamctl address add 0 192.168.1.26 32 0 HP -e \E[37;33mINFO: execute '/sbin/kamctl address reload' to synchronize cache and database STEP 8 : DB : verify if the new ip address is created ? Yes MariaDB [(none)]> select * from kamailio.address; +----+-----+--------------+------+------+------+ | id | grp | ip_addr | mask | port | tag | +----+-----+--------------+------+------+------+ | 1 | 0 | 192.168.1.26 | 32 | 0 | HP | +----+-----+--------------+------+------+------+ 1 row in set (0.000 sec) STEP 9 : Reload the content of the DB into kamailio. It failed ---------------------------------------------------------------------------------------- The host: '192.168.1.41' is kamailio (remote client)$ sudo kamctl address reload { "jsonrpc": "2.0", "error": { "code": 500, "message": "Reload failed." }, "id": 12397 } In /var/log/daemon.log Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 281 [Warning] Aborted connection 281 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 273 [Warning] Aborted connection 273 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 295 [Warning] Aborted connection 295 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Mar 28 17:09:49 db04srv mariadbd[2430]: 2022-03-28 17:09:49 264 [Warning] Aborted connection 264 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Now, if I am trying to restart "kamailio" service, I got an error : Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: DEBUG: <core> [core/sr_module.c:940]: init_mod(): permissions Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: DEBUG: permissions [address.c:179]: reload_address_db_table(): Number of rows in address table: 1 Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: DEBUG: permissions [address.c:191]: reload_address_db_table(): failure during checks of database value 1 (group) in address table Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: ERROR: permissions [address.c:233]: reload_address_db_table(): database problem - invalid record Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: CRITICAL: permissions [address.c:536]: init_addresses(): reload of address table failed Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: ERROR: permissions [permissions.c:657]: mod_init(): failed to initialize the allow_address function Mar 28 17:36:30 kamailio /usr/sbin/kamailio[14196]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module permissions (/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so) Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/cfg.y:1860]: yyparse(): loading module permissions.so Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:513]: ksr_locate_module(): found module to load </usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so> Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:563]: load_module(): trying to load </usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so> Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/kemi.c:3090]: sr_kemi_modules_add(): adding module: permissions Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/cfg.lex:1963]: pp_define(): defining id: MOD_permissions Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'permissions' matches module 'permissions' Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:811]: find_param_export(): found <db_url> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:128]: set_mod_param_regex(): found <db_url> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:112]: set_mod_param_regex(): 'permissions' matches module 'permissions' Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/sr_module.c:811]: find_param_export(): found <load_backends> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:30 kamailio kamailio: DEBUG: <core> [core/modparam.c:128]: set_mod_param_regex(): found <load_backends> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:31 kamailio kamailio: DEBUG: <core> [core/sr_module.c:719]: find_mod_export_record(): found export of <allow_source_address> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so] Mar 28 17:36:31 kamailio kamailio: DEBUG: <core> [core/sr_module.c:719]: find_mod_export_record(): found export of <allow_source_address_group> in module permissions [/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.soIf I remove the record from the database manually, I can restart kamailio but no way to add any address. Thanks if someone could highlight my path. Best Regards, -- Youssef

2 4

avps on regexps?
by David Villasmil 28 Mar '22

28 Mar '22

Hello guys, Is it possible to use apvs on regexps like: $avp(myvar)=$(re{uri.user}{re.subst,/^\+$avp(some_var)/$avp(some_var)/}); doesn't seem possible Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 3

proxy and forward
by jaflong jaflong 28 Mar '22

28 Mar '22

2 1

nathelper OPTIONS ping
by Xuo Guoto 28 Mar '22

28 Mar '22

Hello all, I am trying to periodically send SIP OPTIONS to all connected WebRTC clients from Kamailio. The functionality is similar to qualify=yes of Asterisk. Following are the configuration changes I have made to get this working. #!define FLB_NATSIPPING 7 <snip/> loadmodule "nathelper.so" <snip/> # ----- nathelper params ----- modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) modparam("nathelper", "natping_interval", 20) modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") <snip/> # Handle SIP registrations route[REGISTRAR] { if (is_method("REGISTER")) { xlog("L_INFO", "Processing REGISTER in route[REGISTRAR]\n"); if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); # do SIP NAT pinging xlog("L_INFO", "Setting FLB_NATSIPPING\n"); setbflag(FLB_NATSIPPING); } if (!save("location")) { sl_reply_error(); } xlog("L_INFO", "Successfully processed REGISTER in route[REGISTRAR]\n"); exit; } } When the WebRTC client registers, I can see the log: Setting FLB_NATSIPPING, but SIP OPTIONS packets are not seen. I am checking it using the Chrome console, at client side as well as sipdump module in server side. Do I have to do any additional configuration? I am not posting the full config file here so that its easy to focus on the relevant parts, but can do that if needed. Thanks and regards, X.

2 1

Re: [SR-Users] Kamailio : kamctl address reload with HAProxy
by Henning Westerholt 28 Mar '22

28 Mar '22

Hello, please keep the list in CC – that others can comment as well. Can you actually connect from the kamailio system e.g. with mysql client? If yes, as I said – I would try to debug the issue further with network analysis tools. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Paclinio <thomas.leutscher(a)gmail.com> Sent: Monday, March 28, 2022 1:11 PM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: [SR-Users] Kamailio : kamctl address reload with HAProxy Hello, KAMCTL : I've resolved the problem with kamctl that now can communicate with my remote Cluster by adding this line in kamctlrc. // HAPROXY = 192.168.1.37 DBHOST=192.168.1.37 DBACCESSHOST=192.168.1.37 I can now add and reload new addresses with success. KAMAILIO + HAPROXY: But now, I've this issue when restarting kamailio. Mar 28 10:54:39 kamailio /usr/sbin/kamailio[8416]: ERROR: permissions [address.c:233]: reload_address_db_table(): database problem - invalid record Mar 28 10:54:39 kamailio /usr/sbin/kamailio[8416]: ERROR: permissions [permissions.c:657]: mod_init(): failed to initialize the allow_address function Mar 28 10:54:39 kamailio /usr/sbin/kamailio[8416]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module permissions (/usr/lib/x86_64-linux-gnu/kamailio/modules/permissions.so) My DBURL is #!substdef "!DB_USER!kamailio!g" #!substdef "!DB_PASS!XXXXX!g" #!substdef "!DB_HOST!192.168.1.37!g" // HA PROXY #!substdef "!DB_PORT!MY_PORT_DB!g" #!substdef "!DB_NAME!kamailio!g" #!define DBURL "mysql://DB_USER:DB_PASS@DB_HOST/DB_NAME" KAMAILIO + REMOTE DB : Even I using a remote database I'm getting the same issue. I've discovered the connection between kamailio and remote database is aborded instantly after restarting kamailio. Mar 28 11:47:30 db03srv mariadbd[874]: 2022-03-28 11:47:30 44076 [Warning] Aborted connection 44076 to db: 'kamailio' user: 'kamailio' host: '192.168.1.41' (Got an error reading communication packets) Thank you [Das Bild wurde vom Absender entfernt.]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Le dim. 27 mars 2022 à 22:52, Henning Westerholt <hw(a)gilawa.com<mailto:hw@gilawa.com>> a écrit : Hello, it seems the data that gets delivered to the Kamailio is corrupted. Analyse it further e.g. with a network trace, wireshark etc.. 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 Paclinio Sent: Friday, March 25, 2022 5:22 PM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] Kamailio : kamctl address reload with HAProxy Dear colleagues, I've installed a Galera cluster with a HAProxy that kamailio interacts with. Kamailio's DBURL is linked to the proxy that will contact the databases. Kamailio works fine except when I need to reload something from the database (Using kamctl). When cache and database are the same I receive sudo kamctl address reload { "jsonrpc": "2.0", "result": "Reload OK", "id": 13111 } Now when I have something using kamctl, it still works and is replaced on all my databases. sipsecure@kamailio:~$ sudo kamctl address add 0 192.168.48.15 32 0 Test -e \E[37;33mINFO: execute '/sbin/kamctl address reload' to synchronize cache and database Then when i try to reload i receive sipsecure@kamailio:~$ sudo kamctl address reload { "jsonrpc": "2.0", "error": { "code": 500, "message": "Reload failed." }, "id": 13504 } And when I'm going to read my logs to see a error, I only see that little sentence Mar 25 17:14:40 kamailio /usr/sbin/kamailio[13343]: ERROR: permissions [address.c:233]: reload_address_db_table(): database problem - invalid record Could I have some explanation ? Thank you. [Das Bild wurde vom Absender entfernt.]<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>

2 2

t_suspend / t_continue & insert_hf
by Fuad Trle 28 Mar '22

28 Mar '22

Hello, I'm inserting some headers after getting value from http_async_query. If a call is relayed, I see them. But If I t_suspend and t_continue call (before time out), I do not see added headers. Here is flow: route(START) t_newtran(); #.. prep for query http_async_query("url","HTTP"); route(HTTP) #.. collect and using data from query insert_hf("$var(key): $var(value)\r\n"); t_store(); if (registered("location") { route(RELAY); } else { t_suspend(); exit; } route(AWAKE) t_continue(); I see that the branch index ($T_branch_idx) is 0 at start. 1 after http query, +1 if there is forking or location. +1 after t_suspend. It looks like t_continue uses a branch with index after t_suspend. I tried with t_save_lumps() to carry over changes. Any idea how to do this?

3 3

What is the status of nat_traversal.so
by hanxiaofang 28 Mar '22

28 Mar '22

Hello Kamailio community, What is the status of nat_traversal.so? https://www.kamailio.org/wiki/alphaindexes/devel/modfunctions Could not find any functions for this module here. Regards hanxiaofang

2 1

Kamailio : kamctl address reload with HAProxy
by Paclinio 27 Mar '22

27 Mar '22

Dear colleagues, I've installed a Galera cluster with a HAProxy that kamailio interacts with. Kamailio's DBURL is linked to the proxy that will contact the databases. Kamailio works fine except when I need to reload something from the database (Using kamctl). When cache and database are the same I receive sudo kamctl address reload > { > "jsonrpc": "2.0", > "result": "Reload OK", > "id": 13111 > } Now when I have something using kamctl, it still works and is replaced on all my databases. sipsecure@kamailio:~$ sudo kamctl address add 0 192.168.48.15 32 0 Test > -e \E[37;33mINFO: execute '/sbin/kamctl address reload' to synchronize > cache and database Then when i try to reload i receive sipsecure@kamailio:~$ sudo kamctl address reload > { > "jsonrpc": "2.0", > "error": { > "code": 500, > "message": "Reload failed." > }, > "id": 13504 > } And when I'm going to read my logs to see a error, I only see that little sentence Mar 25 17:14:40 kamailio /usr/sbin/kamailio[13343]: ERROR: permissions > [address.c:233]: reload_address_db_table(): database problem - invalid > record Could I have some explanation ? Thank you. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 1

Using DNS log in
by Steve 26 Mar '22

26 Mar '22

Hello, I have a very basic Kamailio 5.4 configuration on Debian 11 with RTPProxy 2.2 behind a firewall. It works fine with the sip client logging into the server public ip address. However, the sip client is not able to log in when using a dns domain name directed to that public ip address. Is there a specific setting in the Kamailio and/or RTPProxy config files for using a dns domain name instead of a numeric ip address? Also, is there a Kamailio module that allows use of encrypted keys instead of passwords when logging in? Thanks for any info, Steve

2 2

Forward and proxy
by jaflong 26 Mar '22

26 Mar '22

Hi Kamailio community Any advise on how to archive this sip.mydomain.com sip.mypbx.com sip_phone =======sip/tls=======> KAMAILIO =========sip/udp=======>PBX sip_phone should register to Kamilio with tls Kamailio should proxy register to PBX with udp sip_phone invites should be proxied to PBX in sip_client setting he will point to sip.mydomain.com as his server Regards

2 1

(no subject)
by jaflong jaflong 26 Mar '22

26 Mar '22

2 1

t_suspend / t_continue & insert_hf
by Fuad Trle 25 Mar '22

25 Mar '22

Hello, I'm inserting some headers after getting value from http_async_query. If a call is relayed, I see them. But If I t_suspend and t_continue call (before time out), I do not see added headers. Here is flow: route(START) t_newtran(); #.. prep for query http_async_query("url","HTTP"); route(HTTP) #.. collect and using data from query insert_hf("$var(key): $var(value)\r\n"); t_store(); if (registered("location") { route(RELAY); } else { t_suspend(); exit; } route(AWAKE) t_continue(); I see that the branch index ($T_branch_idx) is 0 at start. 1 after http query, +1 if there is forking or location. +1 after t_suspend. It looks like t_continue uses a branch with index after t_suspend. I tried with t_save_lumps() to carry over changes. Any idea how to do this?

1 0

Kamailio SCSCF forward SIP INVITE over TCP
by Weiqi Yao 24 Mar '22

24 Mar '22

Hello community, We currently have some issues with Kamailio SCSCF forwarding a large SIP UDP INVITE packet(size around 3000bytes), it got dropped somewhere in the ethernet. I tried increase the MTU size on both sides' interface and even define it on the switch port, but still no luck. So I am thinking to force SCSCF to send this INVITE over TCP, I followed this link: https://andersbrownworth.com/cms/264/, enabled naptr in SCSCF config and configured NAPTR and SRV DNS record, but the SCSCF still stop even forward it out. I think I did the DNS part right cause when I switch the NAPTR record to point to UDP it worked. Anyone have some experience with configure SCSCF forwarding SIP through TCP? BR, Weiqi

1 0

JsSIP:UA Request-URI does not point to us
by Xuo Guoto 24 Mar '22

24 Mar '22

Hello all, I am facing an issue with JsSIP not recognizing replies from Kamailio. the call sequence goes as follows: INVITE -----------------------------> <-------------------------------SIP/2.0 100 Trying <-------------------------------SIP/2.0 180 Ringing <-------------------------------SIP/2.0 200 OK ACK --------------------------------> <-------------------------------SIP/2.0 200 OK ACK --------------------------------> <-------------------------------SIP/2.0 200 OK ACK --------------------------------> <-------------------------------SIP/2.0 200 OK ACK --------------------------------> <-------------------------------SIP/2.0 200 OK ACK --------------------------------> <-------------------------------SIP/2.0 200 OK ACK --------------------------------> <-------------------------------SIP/2.0 200 OK ACK --------------------------------> <-------------------------------BYE 404 Not Found ----------------------> When JsSIP receives ACK it prints an error: JsSIP:UA Request-URI does not point to us From another thread with similar issue at https://groups.google.com/g/sip_js/c/uiaXS_qc2n8 it could be that JsSIP is not recognizing the GRUU is pointing towards it. In the INVITE message I can see a line "Record-Route: > <mailto:sip:Stg-CQD0r2-10020005@erx-staging-q01.mydomain.com> <mailto:sip:Stg-CQD0r2-10020005@erx-staging-q01.mydomain.com> < <mailto:sip:Stg-CQD0r2-10020005@erx-staging-q01.mydomain.com> <mailto:sip:Stg-CQD0r2-10020005@erx-staging-q01.mydomain.com> mailto:;expires=600;received=mailto:;gr=urn:uuid:b8a691ff-f678-4866-8cf0-780d670e7e33 < <mailto:sip:9747815015@erx-staging-q01.mydomain.com> <mailto:sip:Stg-CQD0r2-10020005@10.10.1.9> > <mailto:sip:Stg-CQD0r2-10020005@10.10.1.9> <mailto:sip:9747815015@erx-staging-q01.mydomain.com> > <mailto:sip:Stg-CQD0r2-10020005@10.10.1.9> <mailto:sip:9747815015@erx-staging-q01.mydomain.com> <mailto:sip:stg-cqd0r2-10020005@erx-staging-q01.mydomain.com> > <mailto:sip:Stg-CQD0r2-10020005@10.10.1.9> <mailto:sip:9747815015@erx-staging-q01.mydomain.com> <mailto:sip:stg-cqd0r2-10020005@erx-staging-q01.mydomain.com> < mailto:sip:stg-cqd0r2-10020005@erx-staging-q01.mydomain.com <mailto:sip:9747815015@erx-staging-q01.mydomain.com> <mailto:sip:Stg-CQD0r2-10020005@10.10.1.9> < mailto:sip:stg-cqd0r2-10020005@erx-staging-q01.mydomain.com <mailto:sip:9747815015@erx-staging-q01.mydomain.com> <mailto:sip:Stg-CQD0r2-10020005@10.10.1.9> > <mailto:sip:Stg-CQD0r2-10020005@10.10.1.9> <mailto:sip:9747815015@erx-staging-q01.mydomain.com>

2 4

Re: [SR-Users] sr-users Digest, Vol 202, Issue 25
by 韩小仿 24 Mar '22

24 Mar '22

Hi, Henning Westerholt Pls close case1 Thanks! hanxiaofang From: sr-users-request Date: 2022-03-24 19:00 To: sr-users Subject: sr-users Digest, Vol 202, Issue 25 Send sr-users mailing list submissions to sr-users(a)lists.kamailio.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users or, via email, send a message with subject or body 'help' to sr-users-request(a)lists.kamailio.org You can reach the person managing the list at sr-users-owner(a)lists.kamailio.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sr-users digest..." Today's Topics: 1. Re: {param.in, name[, delimiter]} error when delimiter is comma (Henning Westerholt) 2. TOPOH is generating new Call-ID for BYE (Marrold) 3. Re: SIPS Errors on Kamailio (Christopher Vincent) 4. bug in tm module? (Daniel Paape) 5. Re: bug in tm module? (Henning Westerholt) 6. carrierroute with non-numeric characters (Arek ?azarczyk) 7. Re: carrierroute with non-numeric characters (Henning Westerholt) 8. Re: carrierroute with non-numeric characters (Arek ?azarczyk) 9. Re: carrierroute with non-numeric characters (Henning Westerholt) ---------------------------------------------------------------------- Message: 1 Date: Wed, 23 Mar 2022 12:49:40 +0000 From: Henning Westerholt <hw(a)gilawa.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Cc: ??? <13715209697(a)139.com> Subject: Re: [SR-Users] {param.in, name[, delimiter]} error when delimiter is comma Message-ID: <PAXPR05MB855899124FF2FD96E43C7E7FBF189(a)PAXPR05MB8558.eurprd05.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hello, Please have a look to the documentation, the issue is described there, and a workaround also suggested. http://www.kamailio.org/wiki/cookbooks/devel/transformations#parameters_lis… 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> On Behalf Of ??? Sent: Wednesday, March 23, 2022 11:12 AM To: sr-users <sr-users(a)lists.kamailio.org> Subject: [SR-Users] {param.in, name[, delimiter]} error when delimiter is comma Hi, all Kamailio5.5.4 $var(s) = "a=1;b=2;c=3"; $var(s1) = $(var(s){param.value,b}); // work well $var(s) = "a=1|b=2|c=3"; $var(s1) = $(var(s){param.value,b,|}); // work well // but $var(s) = "a=1,b=2,c=3"; $var(s1) = $(var(s){param.value,b,,}); ERROR: <core> [core/pvapi.c:1131]: pv_parse_spec2(): invalid parsing in [$(var(s){param.value,b,,})] at (4) CRITICAL: <core> [core/cfg.y:3683]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 366, column 13-38: Can't get from cache: $(var(s){param.value,b,,}) how to fix this? Thanks! ________________________________ hanxiaofang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20220323/836492af/…> ------------------------------ Message: 2 Date: Wed, 23 Mar 2022 15:05:58 +0000 From: Marrold <kamailio(a)marrold.co.uk> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: [SR-Users] TOPOH is generating new Call-ID for BYE Message-ID: <CAC-Lcd8H5H=V4ua7y7Fv-t=LFoC=JZC9FZaKH5JtO+K1QJNxcw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I have enabled the TOPOH module with mask_callid enabled, but it's generating a new Call-ID for a BYE which gets rejected with a 481 downstream. If I disable the TOPOH module it works as expected. Does anyone know where I should start looking? SIP-wise the initial BYE seems compliant. This is Kamailio 5.5.3 on Debian 11 Thanks Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20220323/be811b10/…> ------------------------------ Message: 3 Date: Wed, 23 Mar 2022 18:13:54 +0000 From: Christopher Vincent <CDV(a)redwoodtech.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] SIPS Errors on Kamailio Message-ID: <3C0E2FDC7BD2334492F46C0DA6E07428014E8D1BD0(a)RTG-Exchange01.Redwood.com> Content-Type: text/plain; charset="utf-8" Recompiled Kamailio from source kamailio -v version: kamailio 5.5.4 (x86_64/linux) 4c8938 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: 4c8938 compiled on 14:21:51 Mar 23 2022 with gcc 4.8.5 Compiled a newer version of OpenSSL openssl version OpenSSL 1.1.1m 14 Dec 2021 Then followed through this http://www.kamailio.org/wiki/tutorials/tls/howto-openssl-1-0 Errors changed slightly, but issue still persists kamailio -c loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(3878) ERROR: <core> [core/sr_module.c:570]: load_module(): could not open module </usr/local/lib64/kamailio/modules/tls.so>: /usr/local/lib64/kamailio/modules/tls.so: undefined symbol: OPENSSL_sk_num 0(3878) CRITICAL: <core> [core/cfg.y:3684]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 106, column 12-19: failed to load module 0(3878) INFO: pv [pv_shv.c:60]: shvar_init_locks(): locks array size 16 0(3878) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(3878) CRITICAL: <core> [core/cfg.y:3687]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 253, column 72: Can't set module parameter 0(3878) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(3878) CRITICAL: <core> [core/cfg.y:3687]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 254, column 72: Can't set module parameter 0(3878) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(3878) CRITICAL: <core> [core/cfg.y:3687]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 255, column 68: Can't set module parameter 0(3878) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(3878) CRITICAL: <core> [core/cfg.y:3687]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 260, column 39: Can't set module parameter ERROR: bad config file (5 errors) (parsing code: 0) 0(3878) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized sed /usr/local/etc/kamailio/kamailio.cfg -n -e 106p -e 253p -e 254p -e 255p -e 260p loadmodule "tls.so" modparam("tls", "private_key", "/etc/kamailio/star.redwoodtest.com.pem") modparam("tls", "certificate", "/etc/kamailio/star.redwoodtest.com.pem") modparam("tls", "ca_list", "/etc/kamailio/star.redwoodtest.com.pem") modparam("tls", "tls_method", "TLSv1+") Thanks, Chris From: Christopher Vincent Sent: 21 March 2022 09:41 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Cc: Christopher Vincent <CDV(a)redwoodtech.com> Subject: RE: [SR-Users] SIPS Errors on Kamailio Hi Karsten, Sergey, Thank you for your responses. Kamailio module appears to be installed rpm -ql kamailio-tls /usr/lib64/kamailio/modules/auth_identity.so /usr/lib64/kamailio/modules/tls.so /usr/lib64/kamailio/openssl_mutex_shared /usr/lib64/kamailio/openssl_mutex_shared/openssl_mutex_shared.so /usr/share/doc/kamailio/modules/README.auth_identity /usr/share/doc/kamailio/modules/README.tl Kamailio was installed from the repository using yum / dnf https://rpm.kamailio.org/centos/kamailio.repo Load module order has been corrected to as below loadmodule "sl.so" loadmodule "tls.so" loadmodule "jsonrpcs.so" loadmodule "db_mysql.so" loadmodule "kex.so" ... Kamailio ?c still showed the same errors Thanks, Chris From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Safarov Sent: 19 March 2022 07:38 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: Re: [SR-Users] SIPS Errors on Kamailio SECURITY WARNING: This email is from an external source - do not open or click any attachments if you suspect the email is suspicious. Please report any suspicious emails to Information Security (InformationSecurity(a)redwoodtech.com<mailto:InformationSecurity@redwoodtech.com>) In your config "tls" module after "sl" module. loadmodule "sl.so" loadmodule "tls.so" you need load tls module before "jsonrpcs" module. On Fri, Mar 18, 2022 at 9:59 PM Karsten Horsmann <khorsmann(a)gmail.com<mailto:khorsmann@gmail.com>> wrote: Hi, are you sure the Kamailio tls module is on your system? Check the module path for tls.so like this or if you have build it from source? rpm -ql kamailio-tls /usr/lib64/kamailio/modules/auth_identity.so /usr/lib64/kamailio/modules/tls.so /usr/lib64/kamailio/openssl_mutex_shared /usr/lib64/kamailio/openssl_mutex_shared/openssl_mutex_shared.so /usr/share/doc/kamailio/modules/README.auth_identity /usr/share/doc/kamailio/modules/README.tls Christopher Vincent <CDV(a)redwoodtech.com<mailto:CDV@redwoodtech.com>> schrieb am Fr., 18. M?rz 2022, 12:37: Hi, Kamailio / RTPEngine was set up on CentOS 8 running SIP to SIPS and RTP to SDES SRTP conversion. This worked as expected Attempted to duplicate the setup on RHEL but errors were seen. These errors were present on both RHEL 7 / RHEL 8. The errors seen were as below kamailio -c loading modules under config path: /usr/lib64/kamailio/modules/ 0(9165) ERROR: tls [tls_init.c:611]: tls_pre_init(): Unable to set the memory allocation functions 0(9165) ERROR: tls [tls_init.c:613]: tls_pre_init(): libssl current mem functions - m: 0x7f7a77c367a0 r: 0x7f7a77c367f0 f: 0x7f7a77c36770 0(9165) ERROR: tls [tls_init.c:615]: tls_pre_init(): module mem functions - m: 0x7f7a72db7653 r: 0x7f7a72db769f f: 0x7f7a72db76fc 0(9165) ERROR: tls [tls_init.c:617]: tls_pre_init(): Be sure tls module is loaded before any other module using libssl (can be loaded first to be safe) 0(9165) ERROR: <core> [core/sr_module.c:590]: load_module(): /usr/lib64/kamailio/modules/tls.so: mod_register failed 0(9165) CRITICAL: <core> [core/cfg.y:3683]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 137, column 12-19: failed to load module 0(9165) INFO: pv [pv_shv.c:60]: shvar_init_locks(): locks array size 16 0(9165) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(9165) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 249, column 72: Can't set module parameter 0(9165) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(9165) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 250, column 72: Can't set module parameter 0(9165) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(9165) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 251, column 68: Can't set module parameter 0(9165) ERROR: <core> [core/modparam.c:181]: set_mod_param_regex(): No module matching <tls> found 0(9165) CRITICAL: <core> [core/cfg.y:3686]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 256, column 39: Can't set module parameter ERROR: bad config file (5 errors) (parsing code: 0) 0(9165) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized The kamailio config was exactly the same as on the CentOS systems and started as below /* Server ports: */ #!substdef "!SIP_PORT!5060!g" #!substdef "!SIPS_PORT!5061!g" /* Listen addresses */ #!substdef "!UDP_LOCAL_ADDR!udp:SERVER_IP_ADDR:SIP_PORT!g" #!substdef "!TCP_LOCAL_ADDR!tcp:SERVER_IP_ADDR:SIPS_PORT!g" /* Server connections: */ #!ifndef MAX_CONNECTIONS #!define MAX_CONNECTIONS 8192 #!endif ##!define WITH_DEBUG /* Transaction and branch flags: FLT_ - per transaction (message) flags FLB_ - per branch flags */ #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_NATS 5 #!define FLT_OUT 8 #!define FLB_NATB 6 #!define FLB_NATSIPPING 7 #!define KAMAILIODBURL1 "mysql://kamailio:kamailiorw@localhost/kamailio" #!define WITH_TLS enable_tls=1 listen=tls:<ipaddr>:5062 ####### Global Parameters ######### ### LOG Levels: ALERT=-5, BUG=-4, CRIT=-3, ERR=-1, WARN=0, NOTICE=1, INFO=2, DBG=3 #!ifdef WITH_DEBUG debug=4 log_stderror=no #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 /* display memory usage on exit */ mem_summary=15 /* join free memory fragments */ mem_join=1 /* proxy will fork and run in daemon mode */ /* one process will be created for each network interface the proxy listens to and for each protocol (TCP/UDP), multiplied with the value of 'children' parameter */ fork=yes children=8 listen=TCP_LOCAL_ADDR listen=UDP_LOCAL_ADDR /* life time of TCP connection when there is no traffic - a bit higher than registration expires to cope with UA behind NAT */ tcp_connection_lifetime=3605 /* sip over websockets may not specify a content length header */ tcp_accept_no_cl=yes /* buffer size used for tcp reads, limits the maximum message size (SIP, HTTP) that can be received over tcp */ tcp_rd_buf_size=65536 /* max number of tcp connections */ tcp_max_connections=MAX_CONNECTIONS ####### Modules Section ######## # set paths to location of modules mpath="/usr/lib64/kamailio/modules/" loadmodule "jsonrpcs.so" loadmodule "db_mysql.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.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 "cfgutils.so" loadmodule "textopsx.so" loadmodule "nathelper.so" loadmodule "uac.so" loadmodule "ipops.so" loadmodule "debugger.so" loadmodule "exec.so" loadmodule "avpops.so" loadmodule "sqlops.so" loadmodule "rtpengine.so" loadmodule "sl.so" loadmodule "tls.so" # ----------------- setting module-specific parameters --------------- # ----- usrloc params ----- # store contacts in memory only modparam("usrloc", "db_mode", 0) # hash size of 16,384 modparam("usrloc", "hash_size", 14) # removes contact if ws disconnects modparam("usrloc", "handle_lost_tcp", 1) modparam("tm|usrloc", "xavp_contact", "ulattrs") # ----- jsonrpcs params ----- modparam("jsonrpcs", "fifo_name", "/tmp/kamailio_jsonrpc.fifo") modparam("jsonrpcs", "dgram_socket", "/tmp/kamailio_rpc.sock") # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) #default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 0) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 0) # ----- uac params ----- modparam("uac", "restore_mode", "none") # ----- registrar params ----- modparam("registrar", "method_filtering", 1) modparam("registrar", "max_contacts", 1) # max value for expires of registrations modparam("registrar", "max_expires", 3600) # disable GRUU modparam("registrar", "gruu_enabled", 0) # ----- acc params ----- /* what special events should be accounted? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) /* by default ww do not adjust the direction 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") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) # ----- dispatcher params ----- modparam("dispatcher", "db_url", KAMAILIODBURL1) modparam("dispatcher", "flags", 2) modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_from", "sip:<address>.com<sip:%3caddress%3e.com>") modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "ds_probing_threshold", 1) modparam("dispatcher", "ds_inactive_threshold", 1) modparam("dispatcher", "ds_probing_mode", 3) # ----- pv params ----- modparam("pv", "shvset", "maintenance=i:0") modparam("pv", "shvset", "virtualIP1=i:0") modparam("pv", "shvset", "virtualIP2=i:0") # ----- nathelper params ----- modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") # Note: leaving NAT pings turned off here as nathelper is only being used for # WebSocket connections. NAT pings are not needed as WebSockets have # their own keep-alives. # ----- rtpengine params ----- modparam("rtpengine", "rtpengine_sock", "udp:localhost:2223") modparam("rtpengine", "rtpengine_sock", "udp:localhost:2223") #modparam("rtpengine", "write_sdp_pv", "$avp(sdp)") #modparam("rtpengine", "force_send_interface", SERVER_IP_ADDR) #modparam("rtpengine", "setid_default", -1) #modparam("rtpengine", "rtp_inst_pvar", "$avp(RTPENGINE)") #modparam("rtpengine", "rtpengine_retr", 5) #modparam("rtpengine", "queried_nodes_limit", 5) #modparam("rtpengine", "rtpengine_allow_op", 1) #modparam("rtpengine", "hash_table_size", MAX_CONNECTIONS) #modparam("rtpengine", "hash_table_tout", 7200) modparam("tls", "private_key", "<cert path>") modparam("tls", "certificate", "<cert path>") modparam("tls", "ca_list", "<cert path>") # modparam("tls", "ca_list", "<cert path>") modparam("tls", "tls_method", "TLSv1+") ####### Routing Logic ######## If load module lines for TLS are move to near the top of the config file, config will parse and non-SIPS calls will work loadmodule "sl.so" loadmodule "tls.so" But logs will show WARNING: <core> [main.c:2985]: main(): tls support enabled, but no tls engine available (forgot to load the tls module?) WARNING: <core> [main.c:2987]: main(): disabling tls... Presumably loading the module before configuring it just gives it default values so the latter config is ignored Any advice on the matter would be appreciated Thanks in advance, Chris __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users(a)lists.kamailio.org<mailto:sr-users@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 __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users(a)lists.kamailio.org<mailto:sr-users@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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20220323/4d2d15a7/…> ------------------------------ Message: 4 Date: Wed, 23 Mar 2022 20:16:03 +0000 From: Daniel Paape <dpaape(a)amtelco.com> To: "sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> Subject: [SR-Users] bug in tm module? Message-ID: <CO6PR13MB5321D941E99DE2BA6702E24BC9189(a)CO6PR13MB5321.namprd13.prod.outlook.com> Content-Type: text/plain; charset="iso-8859-1" Hello I'm running K5.5.3 and have checked the 'issues' link in github and saw nothing regarding what I am seeing. I think that there is a bug in the tm module with respect to the "tm:local-response" event route. In the "t_reply.c" file, there is a static variable called '_tm_local_response_set_lookup'. This variable is initialized at load time to zero. It is checked in the '_reply_light()' routine and will initiate a local callback from the config script if "armed". The problem as I see it is that if the callback is readied, the variable is set to one. But it is never reset. So the practical outworking is as follows. A register is received and the request_route arms the callback. The register requires an authorization (local database sqlite). After the 401 is sent back, the callback via the module event route is called as expected. All good except that the module event route script fragment is never executed again after the first call. I'm no expert on the tm module but I would think that somewhere in there, the variable should be reset to zero so that subsequent transactions can initiate the event route again. thanks for any help, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20220323/a0311764/…> ------------------------------ Message: 5 Date: Wed, 23 Mar 2022 20:21:26 +0000 From: Henning Westerholt <hw(a)gilawa.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] bug in tm module? Message-ID: <PAXPR05MB8558B125061A99B7E6A3D352BF189(a)PAXPR05MB8558.eurprd05.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hello, If you think there is a bug in the tm module, you could create an issue in our tracker here: https://github.com/kamailio/kamailio/issues/new?assignees=&labels=&template… Please also add some description of the wrong behaviour that you are seeing in the server to it. Thanks, Henning From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Daniel Paape Sent: Wednesday, March 23, 2022 9:16 PM To: sr-users(a)lists.kamailio.org Subject: [SR-Users] bug in tm module? Hello I'm running K5.5.3 and have checked the 'issues' link in github and saw nothing regarding what I am seeing. I think that there is a bug in the tm module with respect to the "tm:local-response" event route. In the "t_reply.c" file, there is a static variable called '_tm_local_response_set_lookup'. This variable is initialized at load time to zero. It is checked in the '_reply_light()' routine and will initiate a local callback from the config script if "armed". The problem as I see it is that if the callback is readied, the variable is set to one. But it is never reset. So the practical outworking is as follows. A register is received and the request_route arms the callback. The register requires an authorization (local database sqlite). After the 401 is sent back, the callback via the module event route is called as expected. All good except that the module event route script fragment is never executed again after the first call. I'm no expert on the tm module but I would think that somewhere in there, the variable should be reset to zero so that subsequent transactions can initiate the event route again. thanks for any help, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20220323/61051c0f/…> ------------------------------ Message: 6 Date: Thu, 24 Mar 2022 07:39:26 +0100 From: Arek ?azarczyk <arek(a)lazarczyk.org.pl> To: sr-users(a)lists.kamailio.org Subject: [SR-Users] carrierroute with non-numeric characters Message-ID: <a20892cf-fa42-eefe-2bea-b75a74e3196d(a)lazarczyk.org.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Hi, I'm in a process of long overdue update of kamailio from 4.3 to 5.5, after update i can not start kamailio casue: Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: INFO: carrierroute [cr_data.c:456]: add_route(): adding prefix TR, prob 1.000000 Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: INFO: carrierroute [cr_data.c:469]: add_route(): found carrier and domain, now adding route Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: carrierroute [cr_domain.c:166]: add_route_to_tree(): cannot insert route flags into d-trie Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: <core> [dtrie.c:138]: dtrie_insert(): cannot insert non-numerical character Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: carrierroute [cr_data.c:179]: reload_route_data(): could not load routing data Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: carrierroute [carrierroute.c:240]: mod_init(): could not prepare route data I know that string TR is non-numeric data ;) but i have thoes routes deep in my infrastructure logic so i just can not change them to some numbers, is there any way i can resolve this without changeing routes in my whole infrastrucure (almost 50 servers)? Please help :) -- Arek ?azarczyk ------------------------------ Message: 7 Date: Thu, 24 Mar 2022 07:07:35 +0000 From: Henning Westerholt <hw(a)gilawa.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] carrierroute with non-numeric characters Message-ID: <PAXPR05MB8558847862B2480F6CC9E2EABF199(a)PAXPR05MB8558.eurprd05.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Hello, give this parameter a try: https://kamailio.org/docs/modules/5.5.x/modules/carrierroute.html#idm173 If it also not works with this parameter set to 128 and its used to work on 4.3, its probably a code regression. Please open an issue on our GitHub tracker about it then. Cheers, Henning -- Henning Westerholt ? https://skalatan.de/blog/ Kamailio services ? https://gilawa.com -----Original Message----- From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Arek Lazarczyk Sent: Thursday, March 24, 2022 7:39 AM To: sr-users(a)lists.kamailio.org Subject: [SR-Users] carrierroute with non-numeric characters Hi, I'm in a process of long overdue update of kamailio from 4.3 to 5.5, after update i can not start kamailio casue: Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: INFO: carrierroute [cr_data.c:456]: add_route(): adding prefix TR, prob 1.000000 Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: INFO: carrierroute [cr_data.c:469]: add_route(): found carrier and domain, now adding route Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: carrierroute [cr_domain.c:166]: add_route_to_tree(): cannot insert route flags into d-trie Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: <core> [dtrie.c:138]: dtrie_insert(): cannot insert non-numerical character Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: carrierroute [cr_data.c:179]: reload_route_data(): could not load routing data Mar 24 07:30:13 DEV-SBC-FE1 /usr/sbin/kamailio[22768]: ERROR: carrierroute [carrierroute.c:240]: mod_init(): could not prepare route data I know that string TR is non-numeric data ;) but i have thoes routes deep in my infrastructure logic so i just can not change them to some numbers, is there any way i can resolve this without changeing routes in my whole infrastrucure (almost 50 servers)? Please help :) -- Arek ?azarczyk __________________________________________________________ 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 ------------------------------ Message: 8 Date: Thu, 24 Mar 2022 08:42:20 +0100 From: Arek ?azarczyk <arek(a)lazarczyk.org.pl> To: Henning Westerholt <hw(a)gilawa.com>, "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] carrierroute with non-numeric characters Message-ID: <97be0b82-e083-673b-1e2b-f11a62692f34(a)lazarczyk.org.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Thanks, that worked :) , i've must missed that parameter during initial config. BR, A?. W dniu 24.03.2022 o?08:07, Henning Westerholt pisze: > Hello, > > give this parameter a try: > > https://kamailio.org/docs/modules/5.5.x/modules/carrierroute.html#idm173 > > If it also not works with this parameter set to 128 and its used to work on 4.3, its probably a code regression. Please open an issue on our GitHub tracker about it then. > > Cheers, > > Henning > -- Arek ?azarczyk ------------------------------ Message: 9 Date: Thu, 24 Mar 2022 07:58:10 +0000 From: Henning Westerholt <hw(a)gilawa.com> To: Arek ?azarczyk <arek(a)lazarczyk.org.pl>, "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] carrierroute with non-numeric characters Message-ID: <PAXPR05MB8558EA2CE9C0F379042C9DBABF199(a)PAXPR05MB8558.eurprd05.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Great, thanks for the feedback. Henning -----Original Message----- From: Arek ?azarczyk <arek(a)lazarczyk.org.pl> Sent: Thursday, March 24, 2022 8:42 AM To: Henning Westerholt <hw(a)gilawa.com>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] carrierroute with non-numeric characters Thanks, that worked :) , i've must missed that parameter during initial config. BR, A?. W dniu 24.03.2022 o?08:07, Henning Westerholt pisze: > Hello, > > give this parameter a try: > > https://kamailio.org/docs/modules/5.5.x/modules/carrierroute.html#idm1 > 73 > > If it also not works with this parameter set to 128 and its used to work on 4.3, its probably a code regression. Please open an issue on our GitHub tracker about it then. > > Cheers, > > Henning > -- Arek ?azarczyk ------------------------------ Subject: Digest Footer _______________________________________________ sr-users mailing list sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users ------------------------------ End of sr-users Digest, Vol 202, Issue 25 *****************************************

1 0

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