sr-users January 2026

sr-users@lists.kamailio.org

19 participants
31 discussions

Releasing v5.8.7
by Daniel-Constantin Mierla 14 Jan '26

14 Jan '26

Hello, I am considering to release Kamailio v5.8.7 (out of branch 5.8) on Wednesday, Jan 14, 2026. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. The most of the commits planned for this release are backported, should any be found missing, reply to sr-dev mailing list. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com

1 1

Development for v6.1.x is frozen
by Daniel-Constantin Mierla 09 Jan '26

09 Jan '26

Hello, the formal notification that the development for the next major version 6.1.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 6.1 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, new pull requests can still be done, but they will be merged after branching 6.1. Can still be done commits with documentation improvements, enhancements to related tools (e.g., kamctl, kamcmd), merging exiting pull requests at this moment, exporting missing KEMI functions and completing the functionality of the new modules/components added for 6.1. Once the branch 6.1 is created, new features can be pushed again to master branch as usual. From that moment, the v6.1.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 6.1 is going to be built at: * https://www.kamailio.org/wikidocs/features/new-in-6.1.x/ Upgrade guidelines will be collected at: * https://www.kamailio.org/wikidocs/install/upgrade/6.0.x-to-6.1.0/ Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v6.0.x to 6.1.x. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com

1 0

Production IMS with kamailio 6
by James Browne 08 Jan '26

08 Jan '26

Hi Has any of us ever successfully (or know someone who has) set up an IMS with kamailio in production that scales to thousands of users? I'm working on an POC and I might be able to use some help. James

3 3

Kamailio v6.0.5 Released
by Daniel-Constantin Mierla 08 Jan '26

08 Jan '26

Hello, Kamailio SIP Server v6.0.5 stable release is out! This is a maintenance release of the latest stable branch, 6.0, that includes fixes since the release of v6.0.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v6.0.x. Deployments running previous v6.0.x versions are strongly recommended to be upgraded to v6.0.5. For more details about version 6.0.5 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2026/01/kamailio-v6-0-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com

1 0

Planning to next major release series Kamailio v6.1.x
by Daniel-Constantin Mierla 08 Jan '26

08 Jan '26

Hello, last week several developers went to Dusseldorf for the Kamailio Devel Meeting for two fruitful days working on merging some of the pull request, address many reported issues, building a new deb packaging infrastructure, as well as add new features. Among achievements: reviewing/merging a couple of PRs, including merging a new module; pull request to use stdatomic; completing the building of debs with cmake; start of creating the new platform for deb building; proper support for async sql queries with no connection available at start up; more modules not destroying structures at shut down to avoid races; archiving a few modules ... During a video conference with other main developers, it was also discussed about the roadmap to the next major release series, respectively Kamailio v6.1.x, agreeing more or less to continue the development for about 2-3 weeks to allow people to still contribute new features, then enter the testing phase. Based on that, I would propose: - freeze the development at the beginning of January 7, 2027 (to be after the winter/season holidays, before many devs might be offline) - testing phase as needed for 4 to 6 weeks - release likely to be by mid of February or slightly later The new features have to be pushed to the git repository or made pull requests by freeze date. Should anyone want to suggest alternatives, just propose them to sr-dev mailing list to be discussed further with the developers. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com

1 2

Releasing v6.0.5
by Daniel-Constantin Mierla 08 Jan '26

08 Jan '26

Hello, I am considering to release Kamailio v6.0.5 (out of branch 6.0) on Thursday, Jan 8, 2026. If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com

1 1

Topos and stun
by Servan Kroes 06 Jan '26

06 Jan '26

Hi, We have implemented topos successfully. Only now we get an error in the log by receiving stun messages: Jan 5 10:12:14 VC-POC-SERVAN kamailio@vcare_edgeudp[4163314]: 5(4163314) DEBUG: <core> [core/udp_server.c:741]: udp_rcv_loop(): probing packet received from 192.168.22.127 9601 Jan 5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]: 6(4163315) DEBUG: <core> [core/stun.c:42]: stun_process_msg(): STUN Message: [[>>> Jan 5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]: <<<]] Jan 5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]: 6(4163315) INFO: <core> [core/parser/parse_fline.c:145]: parse_first_line(): method not followed by SP Jan 5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]: 6(4163315) ERROR: <core> [core/parser/parse_fline.c:274]: parse_first_line(): parse_first_line: bad message (offset: 0) Jan 5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]: 6(4163315) DEBUG: <core> [core/parser/msg_parser.c:721]: parse_msg(): invalid message Jan 5 10:12:15 vm-kamailio kamailio[4163315]: 6(4163315) ERROR: <core> [core/parser/msg_parser.c:794]: parse_msg(): ERROR: parse_msg: message=<#001#001> Jan 5 10:12:15 vm-kamailio kamailio[4163315]: 6(4163315) DEBUG: topos [topos_mod.c:446]: tps_prepare_msg(): outbuf buffer parsing failed! Jan 5 10:12:15 vm-kamailio kamailio[4163316]: 7(4163316) DEBUG: <core> [core/udp_server.c:718]: udp_rcv_loop(): received on udp socket: (94/28/28) [[ 00 01 00 08 02 A6 P_ 97 1A D8 , AE CF C8 c 06 u E6 7 00 03 00 04 00 00 00 04 ]] Jan 5 10:12:15 vm-kamailio kamailio[4163316]: 7(4163316) DEBUG: <core> [core/stun.c:42]: stun_process_msg(): STUN Message: [[>>> Jan 5 10:12:15 vm-kamailio kamailio[4163316]: <<<]] Jan 5 10:12:15 vm-kamailio kamailio[4163316]: 7(4163316) INFO: <core> [core/parser/parse_fline.c:145]: parse_first_line(): method not followed by SP Jan 5 10:12:15 vm-kamailio kamailio[4163316]: 7(4163316) ERROR: <core> [core/parser/parse_fline.c:274]: parse_first_line(): parse_first_line: bad message (offset: 0) Jan 5 10:12:15 vm-kamailio kamailio[4163316]: 7(4163316) DEBUG: <core> [core/parser/msg_parser.c:721]: parse_msg(): invalid message Jan 5 10:12:15 vm-kamailio kamailio[4163316]: 7(4163316) ERROR: <core> [core/parser/msg_parser.c:794]: parse_msg(): ERROR: parse_msg: message=<#001#001> Jan 5 10:12:15 vm-kamailio kamailio[4163316]: 7(4163316) DEBUG: topos [topos_mod.c:446]: tps_prepare_msg(): outbuf buffer parsing failed! Jan 5 10:12:15 vm-kamailio kamailio[4163317]: 8(4163317) DEBUG: <core> [core/udp_server.c:718]: udp_rcv_loop(): received on udp socket: (91/28/28) [[ 00 01 00 08 03 E0 EB N E6 A`Q C8 3 89 ~ D0 C9 E9 v 00 03 00 04 00 00 00 02 ]] Jan 5 10:12:15 vm-kamailio kamailio[4163317]: 8(4163317) DEBUG: <core> [core/stun.c:42]: stun_process_msg(): STUN Message: [[>>> Jan 5 10:12:15 vm-kamailio kamailio[4163317]: <<<]] Jan 5 10:12:15 vm-kamailio kamailio[4163317]: 8(4163317) INFO: <core> [core/parser/parse_fline.c:145]: parse_first_line(): method not followed by SP Jan 5 10:12:15 vm-kamailio kamailio[4163317]: 8(4163317) ERROR: <core> [core/parser/parse_fline.c:274]: parse_first_line(): parse_first_line: bad message (offset: 0) Jan 5 10:12:15 vm-kamailio kamailio[4163317]: 8(4163317) DEBUG: <core> [core/parser/msg_parser.c:721]: parse_msg(): invalid message Jan 5 10:12:15 vm-kamailio kamailio[4163317]: 8(4163317) ERROR: <core> [core/parser/msg_parser.c:794]: parse_msg(): ERROR: parse_msg: message=<#001#001> Jan 5 10:12:15 vm-kamailio kamailio[4163317]: 8(4163317) DEBUG: topos [topos_mod.c:446]: tps_prepare_msg(): outbuf buffer parsing failed! If we disable topos, we don't get these messages. Is this an bug? Or is there a setting in topos or stun that I can check? Kind regards, Servan Kroes

4 5

Intermittent SCSCF → HSS Diameter Connection Failure - CER Not Sent After TCP Connect
by Qasim Loay 05 Jan '26

05 Jan '26

Hello Kamailio Community, *This issue is being re-submitted with CDP debug logs for further analysis.* We are experiencing a *critical issue* with Kamailio where the *SCSCF randomly stops sending CER messages to the HSS* in some cases, even after TCP connections are successfully established. This results in *complete authentication failures*. Please find the (IMS containers + HSS) logs with and the diameter config through the following link: https://www.filemail.com/d/vhdnkujjnernogn *Environment* - *Kamailio Version:* kamailio 6.0.2 (x86_64/linux) d4dc5d - *Deployment:* SCSCF and HSS as a container on same physical machine using macvlan networking *Components:* - SCSCF: 172.22.1.20 - HSS: 172.22.1.3 - ICSCF: 172.22.1.19 *Problem Description* The issue occurs *randomly*. The system works normally for a period of time, then suddenly the Diameter connection between the SCSCF and HSS fails and enters what appears to be a *reconnection loop*. *Here's the cycle we're observing:* *1. *ERROR: ims_auth [cxdx_mar.c:132]: async_cdp_callback(): Transaction timeout - did not get MAA *2. *SCSCF: WARNING: cdp [peermanager.c:337]: peer_timer(): Inactivity on peer [hss.epc.mnc092.mcc418.3gppnetwork.org] and no DWA, Closing peer... *3. State Timeout (~40 seconds later):* S-CSCF: ERROR: cdp [peerstatemachine.c:164]: sm_process(): in state Closed timeout event Timeout *4. Reconnection Attempt (~30 seconds later):* SCSCF: INFO: cdp [peerstatemachine.c:551]: I_Snd_Conn_Req(): Peer hss.epc.mnc092.mcc418.3gppnetwork.org SCSCF: INFO: cdp [receiver.c:991]: peer_connect(): Trying to connect to 172.22.1.3 port 3870 SCSCF: INFO: cdp [receiver.c:1090]: peer_connect(): Peer hss.epc.mnc092.mcc418.3gppnetwork.org:3870 connected *5. HSS Side (waiting indefinitely):*HSS: [hss:0.19.37] 2025/12/25 04:46:39.060208 [INF] [scscf>hss:0][waiting for CER from 172.22.1.20:33284] *Cascading Effects:* *ICSCF accumulates branches:* ICSCF: ERROR: tm [t_fwd.c:792]: add_uac(): maximum number of branches exceeded ICSCF: ERROR: tm [t_fwd.c:1771]: t_forward_nonack(): failure to add branches As a result, *UEs are unable to register to IMS*, leading to a *VoLTE service outage for all UEs*. Thank you and I look forwarding to hearing from you

1 0

Kamailio 6.0 failed to start on Alpine
by Cindy Leung 05 Jan '26

05 Jan '26

Hello, We have recently upgraded our Alpine base image (3.23) along with Kamailio (6.0.4) and we are getting segfault at startup. Our custom config was working in Alpine 3.22 with Kamailio 5.8.4. We are not building Kamailio from source. We're getting it from apk. We were able to locate the problem with TLS. We tested with the default config that shipped with the package - segfault. Our self-signed cert is generated by this: openssl req -newkey rsa:2048 -x509 -keyout private.key -out cert.pem -days 3650 -nodes -subj "/C=US/ST=/L=/O=/OU=/CN=" We tried to build it from source - segfault Then we tried the same exercise with Ubuntu - apt install kamailio kamailio-tls-modules Using the same certificate, using the default config in the package, no segfault. I wish you all Happy Holidays!! TIA. Here're the logs from the alpine startup: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.2:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.2:5060 tls: 127.0.0.1:5061 tls: 172.17.0.2:5061 Aliases: tls: ef79bc4947ca:5061 tls: localhost:5061 tcp: ef79bc4947ca:5060 tcp: localhost:5060 udp: ef79bc4947ca:5060 udp: localhost:5060 0(45) INFO: <core> [core/tcp_main.c:5252]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(45) INFO: <core> [main.c:3322]: main(): current open file limits [soft/hard]: [1048576/1048576] Segmentation fault (core dumped) /usr/sbin/kamailio -E -f /etc/kamailio/kamailio.cfg -DD (gdb) bt full #0 0x0000ffffbe397df4 in __pthread_getspecific (k=k@entry=0) at src/thread/pthread_getspecific.c:8 self = <optimized out> #1 0x0000ffffbe2c2300 in mod_init () at tls_mod.c:406 method = <optimized out> verify_client = <optimized out> rand_buf = "\210\000\001\000\001\000\000\000\200\004\360\330\377\377\000\000\024\3518\276\377\377\000\000\275@ =\276\377\377\000" k = 0 __func__ = "mod_init" __llevel = <optimized out> __kld = <optimized out> #2 0x0000aaaad4e659b8 in init_mod (m=0xffffbdb86660) at core/sr_module.c:1037 ret = <optimized out> __func__ = "init_mod" #3 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb89bb0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #4 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8a110) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #5 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8aac0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #6 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8b840) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #7 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8dad0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #8 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8eab0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #9 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb8f2c0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #10 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb90220) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #11 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9a740) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #12 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9ac60) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #13 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9b0b0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #14 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9bad0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #15 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9ceb0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #16 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9dc70) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #17 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9eba0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #18 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9f410) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #19 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9f8c0) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #20 0x0000aaaad4e658c4 in init_mod (m=0xffffbdb9ff70) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #21 0x0000aaaad4e658c4 in init_mod (m=0xffffbdba1b60) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #22 0x0000aaaad4e658c4 in init_mod (m=0xffffbdba2060) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #23 0x0000aaaad4e658c4 in init_mod (m=0xffffbdba3040) at core/sr_module.c:1032 ret = <optimized out> __func__ = "init_mod" #24 0x0000aaaad4e6a34c in init_modules () at core/sr_module.c:1068 t = <optimized out> i = <optimized out> __func__ = "init_modules" #25 0x0000aaaad4c349b4 in main (argc=<optimized out>, argv=<optimized out>) at main.c:3353 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0xffffbe3f7ba0 <ldso> "" tmp_len = 0 port = 5060 proto = 0 aproto = 0 ahost = 0x0 socket_name = 0x0 aport = 0 listen_field_count = <optimized out> listen_fields = {0x18 <error: Cannot access memory at address 0x18>, 0x99ba <error: Cannot access memory at address 0x99ba>, 0x18 <error: Cannot access memory at address 0x18>} options = 0xaaaad4f178ee ":f:cm:M:dVIhEeb:B:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1938757098 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> n_lst = <optimized out> p = <optimized out> tbuf = 0xffffd8f01ab0 "!" tbuf_tmp = <optimized out> st = {st_dev = 63, st_ino = 48481, st_mode = 16877, st_nlink = 1, st_uid = 100, st_gid = 0, st_rdev = 0, __pad = 0, st_size = 4096, st_blksize = 4096, __pad2 = 0, st_blocks = 8, st_atim = {tv_sec = 1766082557, tv_nsec = 947394010}, st_mtim = {tv_sec = 1766093215, tv_nsec = 591712013}, st_ctim = {tv_sec = 1766093215, tv_nsec = 591712013}, __unused = {0, 0}} l1 = <optimized out> lim = {rlim_cur = 1048576, rlim_max = 1048576} option_index = 0 long_options = {{name = 0xaaaad4f18d0a "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0xaaaad4f2682c "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0xaaaad4f3197d "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0xaaaad4f18d0f "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0xaaaad4f18d15 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0xaaaad4f18d1e "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0xaaaad4f18d28 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0xaaaad4f18d32 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0xaaaad4f18d3d "modparam", has_arg = 1, flag = 0x0, val = 1030}, { name = 0xaaaad4f18d46 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0xaaaad4f26949 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0xaaaad4f18d51 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0xaaaad4f18d5b "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0xaaaad4f18d62 "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" Cindy

4 7

Re: topos-redis kamailio 6.x
by Angel Elena 04 Jan '26

04 Jan '26

Yes Daniel; I'm currently reviewing the routing logic to eliminate the errors. Thank you. --------------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://diablo.craem.net _(___V @craem_ www.linkedin.com/in/angel-elena-medina --------------------------------------- Kopano Webapp. -----Original message----- > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > Sent: Friday 2nd January 2026 11:58 > To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> > Cc: Angel Elena <craem(a)craem.net> > Subject: Re: [SR-Users] topos-redis kamailio 6.x > > Hello, > do you have the SIP messages with a lot of/large > routing headers (e.g., record-/route, via, ...)? > Cheers, > Daniel > On 26.12.25 22:49, Angel Elena via > sr-users wrote: > hi, good afternoon. > I'm testing Kamailio 6.0 on Debian 13 and I need to hide the network topology > for a specific provider and keeping the contact header simple (topos.so style). > My topos.so config > loadmodule "topos_redis.so" > loadmodule "topos.so" > loadmodule "ndb_redis.so" > modparam("topos", "storage", "redis") > modparam("ndb_redis", "server", "name=srv1;addr=127.0.0.1;port=6379;db=0") > modparam("topos_redis", "serverid", "srv1") > modparam("topos", "sanity_checks", 1) > modparam("topos", "branch_expire", 3600) > modparam("topos", "dialog_expire", 14400) > with this config in kamailio.log appears this issue (it's a migrated config > from 5.4 version): > Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61635]: ERROR: topos > [tps_storage.c:663]: tps_storage_record(): failed to store (dlg: 0 dir: 0 > metid: 512) > Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61636]: ERROR: topos_redis > [topos_redis_storage.c:934]: tps_redis_load_branch(): not enough space for > a_contact > Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61634]: ERROR: topos_redis > [topos_redis_storage.c:934]: tps_redis_load_branch(): not enough space for > a_contact > Dec 26 22:42:54 kamailio-sbc /usr/local/sbin/kamailio[61633]: ERROR: topos_redis > [topos_redis_storage.c:934]: tps_redis_load_branch(): not enough space for > a_contact > I'm reading the documentation, but I don't see how to increase these values > to avoid these errors. > Thank you and happy holidays > --------------------------------------- > Ángel Elena Medina _o) > craem(a)craem.net <mailto:craem@craem.net> / \\ > http://diablo.craem.net <http://diablo.craem.net> _(___V > @craem_ > www.linkedin.com/in/angel-elena-medina <http://www.linkedin.com/in/angel-elena-medina> > --------------------------------------- > Kopano Webapp. > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- sr-users(a)lists.kamailio.org > <mailto:sr-users@lists.kamailio.org> > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org <mailto:sr-users-leave@lists.kamailio.org> > Important: keep the mailing list in the recipients, do not reply only to the > sender! > -- > Daniel-Constantin Mierla (@ asipto.com) > twitter.com/miconda -- linkedin.com/in/miconda > Kamailio Consultancy, Training and Development Services -- asipto.com > Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com > > -- > > This message has been scanned for viruses and > > dangerous content by > MailScanner <http://www.mailscanner.info/>, and is > > believed to be clean.

1 0

2026

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