sr-users January 2021

sr-users@lists.kamailio.org

58 participants
67 discussions

failover on SIP servers
by AL RSM 02 Feb '21

02 Feb '21

Hi, I was wondering what is the recommended approach to implement a failover on several destination SIP servers: 1) using DNS SRV records 2) using dispatcher list 3) combination of both. Thanks, AL

3 2

Acc module unable to insert cdr in mysql server
by M Arqum CH 01 Feb '21

01 Feb '21

Hello Members, Kamailio acc module is not inserting cdr into MySQL DB, sometimes it works and sometimes didn't, the number of parameters/values are similar in failed as well success scenario. I also check with tcpdump for MySQL requests, unfortunately, Kamailio didn't issue insert query toward DB server, so it is clear to me that the MySQL server is nothing to do with failed queries. Please guide me on what I should do to find and fix the issue. Kamailio Installed version : kamailio -v version: kamailio 5.4.1 (x86_64/linux) 2ca223 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_BLACKLIST, 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: 2ca223 compiled on 12:51:24 Sep 21 2020 with gcc 6.3.0 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_logic.c:691]: tmcb_func(): acc callback called for t(0x7fe29b2a7870) event type 512, reply code 200 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_logic.c:413]: should_acc_reply(): probing acc state - code: 200 flags: 0x6 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_logic.c:446]: should_acc_reply(): acc is on Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 0 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 1 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 2 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 4 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 5 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 6 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 7 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 8 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 9 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 10 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 11 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 12 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 13 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 16 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 17 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 19 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 20 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 22 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 26 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 28 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 29 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 32 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 6, index i 33 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: tm [t_hooks.c:256]: run_trans_callbacks_internal(): DBG: trans=0x7fe29b2a7870, callback type 512, id 0 entered Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 0 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 1 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 2 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 3 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 4 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 5 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 8 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 9 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 11 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 12 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 14 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 18 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 20 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 21 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 24 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 25 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: ERROR: acc [acc_cdr.c:267]: db_write_cdr(): failed to insert into database Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 0 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 1 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 2 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 3 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 4 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 5 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 8 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 9 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 11 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 12 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 14 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 18 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 20 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 21 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 24 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: acc [acc_extra.h:63]: free_strar_mem(): Freeing memory, type is 2, message_index 3, index i 25 Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: ERROR: acc [acc_cdr.c:682]: cdr_on_end_confirmed(): failed to write cdr! Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103637]: DEBUG: tm [t_reply.c:1758]: cleanup_uac_timers(): RETR/FR timers reset Jan 28 13:38:29 /root/mykamailio/sbin/kamailio[103682]: DEBUG: tm [timer.c:634]: wait_handler(): finished transaction: 0x7fe29727ba88 (p:0x7fe294d27288/n:0x7fe294d27288) -- Regards M Arqum

2 2

UACREG to many Asterisk
by Javier Valencia 01 Feb '21

01 Feb '21

Hi there! Go ahead I apologize for my English. I have a Kamailio 5.4 with the DISPATCHER module and UAC enabled (for remote REGISTER), the DISPATCHER has several SETIDs, and they have one or more Asterisk balanced behind it. In Kamalio script, when an endpoint does REGISTER, I enable the REGISTER of the UAC module. And when it expires or expires=0 I disable the REGISTER in the UAC module. In the UACREG table in the database, L_UUID (unique key), L_USERNAME, R_USERNAME, and AUTH_USERNAME have the same value. For example CST100EXT100. Knowing that the DISPATCHER and UAC modules have no relationship, but that when a SETID has several balanced Asterisks, how can I make the UAC module send the REGISTER to all the Asterisks of a SETID? Clarifications; 1.- I cannot update the Asterisk, which are currently in version 11. They do not support PATH. 2.- I can modify the content of the UACREG table so that l_uuid has a suffix '_X'. 3.- Call jsonrpc_exec several times to enable the REGISTER in the UAC module. (diff emulated) < jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": "uac.reg_enable", "params": ["l_uuid", "s: $ au"]}') ; > jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": "uac.reg_enable", "params": ["l_uuid", "s: $ au_1"]}') ; > jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": "uac.reg_enable", "params": ["l_uuid", "s: $ au_2"]}') ; > jsonrpc_exec ('{"id": 1, "jsonrpc": "2.0", "method": "uac.reg_enable", "params": ["l_uuid", "s: $ au_3"]}') ; But I want to know if there is any more elegant way to do this. Cheers, JV -- Logo <http://www.voiper.es/> Javier Valencia | CTO Centro de Negocios Martín Buendía Camino de las Cañadas, nº 1C, Portal 1, 2ºG 29649 Mijas (Málaga) # 951562080 (T) <tel:951562080> | 687486759 (M) <tel:687486759> # www.voiper.es <http://www.voiper.es/> ------------------------------------------------------------------------ AVISO LEGAL ----------- Este mensaje contiene información confidencial destinada para ser leída exclusivamente por el destinatario. Queda prohibida la reproducción, publicación, divulgación, total o parcial del mensaje así como el uso no autorizados por el emisor. En caso de recibir el mensaje por error, se ruega su comunicación al remitente lo antes posible. Por favor, indique inmediatamente si usted o su empresa no aceptan comunicaciones de este tipo por Internet. Las opiniones, conclusiones y demás información incluida en este mensaje que no esté relacionada con asuntos profesionales de SMART RECARGAS, S.L, se entenderá que nunca se ha dado, ni está respaldado por el mismo. Responsable del Tratamiento de Datos ------------------------------------ SMART RECARGAS , SL Camino de las Cañadas, 1C PORTAL 1 2º G 29651 MIJAS COSTA (MALAGA)

3 2

externally triggered message sending to specific clients
by Syed Shahryar 01 Feb '21

01 Feb '21

Is it possible to send arbitrary text messages triggered by an external application (evapi/http) to registered SIP clients via websocket? The following doesn't seem to do anything. KSR.corex.send_data("sip:user@example.com", "Message at $Ts"); -- -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of email transmission. If verification is required, please request a hard-copy version.

2 1

logging error events to database
by Sergiu Pojoga 30 Jan '21

30 Jan '21

Hi there, I was wondering if there's a way to log various core error events in some DB. For example, below error occurred Jan 29 11:43:56 kamailio[11076]: {1 11440 INVITE 28b653bd-8f62-4085-a5ef-f2a4ac0f393d } ERROR: <core> [core/parser/sdp/sdp_helpr_funcs.c:499]: extract_mediaip(): no `IP[4|6]' address in `c=' field Jan 29 11:43:56 kamailio[11076]: {1 11440 INVITE 28b653bd-8f62-4085-a5ef-f2a4ac0f393d } ERROR: <core> [core/parser/sdp/sdp.c:430]: parse_sdp_session(): can't extract common media IP from the message Thanks in advance. Regards, --Sergiu

4 5

Establish connection between MsTeams and Kamailio.
by Willy Valles Rios 30 Jan '21

30 Jan '21

Hello community, Please your support, I tell you that I am integrating Kamailio with MsTeams, after some time reviewing this, I finally achieved the connection from my Kamailio server to MsTeams and I can validate that the connection to MsTeams is in AP. [root @ kamailio-server kamailio] # kamcmd dispatcher.list | egrep "URI | FLAGS" URI: sip: sip.pstnhub.microsoft.com; transport = tls FLAGS: AP However, from the admin panel of MsTeams (Direct Routing) I see that the connection to my sbc "sbc.netvoiceperu.com" is with TLS connectivity status in "Active" but the SIP options status is in "Warning". I have made calls from MsTeams thinking that the SIP options status would change to "active" but it is still in "Warning" state. On the other hand, I have enabled a siptrace in Kamailio and verify that the SIP OPTIONS from kamailio are being sent in the following format to MsTeams. OPTIONS sip: sip.pstnhub.microsoft.com; transport = tls SIP / 2.0 Via: SIP / 2.0 / TLS 161.35.44.66:5061 ;branch=z9hG4bKea07.52224687000000000000000000000000.0 To: <sip: sip.pstnhub.microsoft.com; transport = tls> From: <sip: sbc.netvoiceperu.com>; tag = d3569c818b500aeb8c373426e76c2884-81763c71 CSeq: 10 OPTIONS Call-ID: 13ea237a751e0c48-9148(a)161.35.44.66 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.4.0 (x86_64 / linux)) As you can see, the SIP OPTIONS sent from Kamailio to MsTeams does not contain the "Contact" field, which in theory said "Contact" field should have been added by Kamailio according to the configuration added in kamailio.cfg event_route [tm: local-request] { sip_trace (); if (is_method ("OPTIONS") && $ ru = ~ "pstnhub.microsoft.com") { append_hf ("Contact: <sip: sbc.netvoiceperu.com: 5061; transport = tls> \ r \ n"); } xlog ("L_INFO", "Sent out tm request: $ mb \ n"); } As additional information, I inform you that I also managed to observe the SIP OPTIONS that MsTeams sends to Kamailio. OPTIONS sip: sbc.netvoiceperu.com: 5061; transport = tls SIP / 2.0 FROM: <sip: sip-du-a-eu.pstnhub.microsoft.com: 5061>; tag = f1bdeb5f-662f-4544-a436-e9aa9ad78da4 TO: <sip: sbc.netvoiceperu.com> CSEQ: 1 OPTIONS CALL-ID: c47e2782-16c3-49cb-8931-24e9709d260a MAX-FORWARDS: 70 VIA: SIP / 2.0 / TLS 52.114.75.24:5061;branch=z9hG4bK48b0e6be CONTACT: <sip: sip-du-a-eu.pstnhub.microsoft.com: 5061> CONTENT-LENGTH: 0 USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2021.1.15.7 i.EUWE.10 ALLOW: INVITE, ACK, OPTIONS, CANCEL, BYE, NOTIFY However I don't see the 200 OK SIP responses from Kamailio to MsTeams. I think this may be the reason why I see the SIP OPTIONS status in "Warning" from the MsTeams panel. Maybe the contact field is not being added in the SIP OPTIONS messages that Kamailio sends to MsTeams and for that reason I don't see 200OK responses from MsTeams. Could you help me solve this please. Cheers Saludos Cordiales -- *Willy Valles Rios* *Unified Communications Specialist* phone: +51955747343 em@il: willyvalles17(a)gmail.com

2 1

registering gsm gateway by siremis
by shashank shekhar 29 Jan '21

29 Jan '21

Hi, I want to register a gsm gateway on my kamailio server with siremis ...kindly guide me on this Thankyou Regards Shashank shekhar 9162735161

2 1

Kamailio as inbound and outbound proxy
by Michael Friesen 29 Jan '21

29 Jan '21

Hello, I am trying to configure Kamailio as both an inbound and outbound proxy. Inbound requests flow Sip Trunk -> Kamailio -> Asterisk. Outbound requests flow Asterisk -> Kamailio -> Sip Trunk. Inbound traffic is sent to port 5060 on kamailio which listens on the PRIVATE_IP:5060 and advertises PUBLIC_IP:5060. How can we ensure that when messages are sent to the Sip Trunk they have Record-Route headers with the PUBLIC_IP and when messages are sent to asterisk they have Record-Route headers with the PRIVATE_IP?

2 1

kamailio 5.4.3 ubuntu 20.04 tls - http_async_client
by Filippo Graziola 28 Jan '21

28 Jan '21

Hi all, I have an issue related (my guess) to tls and http_async_client module that result in a segmentation fault and a not correct handle of tls connections. First with only tls module loaded, not forked: 0(1021) INFO: <core> [core/tcp_main.c:4983]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1021) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1021) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1021) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support! 0(1021) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman 0(1021) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 4718592 and 2359296 bytes 0(1021) INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold1 has been changed to 4718592 0(1021) INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 2359296 0(1021) INFO: <core> [main.c:2833]: main(): processes (at least): 9 - shm size: 67108864 - pkg size: 67108864 0(1021) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1021) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSs<default>: tls_method=12 0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSs<default>: certificate='/etc/kamailio/fullchain.pem' 0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSs<default>: ca_list='(null)' 0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSs<default>: crl='(null)' 0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): TLSs<default>: require_certificate=0 0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSs<default>: cipher_list='(null)' 0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSs<default>: private_key='/etc/kamailio/privkey.pem' 0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): TLSs<default>: verify_certificate=0 0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSs<default>: verify_depth=9 0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSs<default>: verify_client=0 0(1021) NOTICE: tls [tls_domain.c:1105]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... 0(1021) INFO: tls [tls_domain.c:711]: set_verification(): TLSs<default>: No client certificate required and no checks performed 0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSc<default>: tls_method=20 0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSc<default>: certificate='(null)' 0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSc<default>: ca_list='(null)' 0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSc<default>: crl='(null)' 0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): TLSc<default>: require_certificate=0 0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSc<default>: cipher_list='(null)' 0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSc<default>: private_key='(null)' 0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): TLSc<default>: verify_certificate=0 0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSc<default>: verify_depth=9 0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSc<default>: verify_client=0 0(1021) INFO: tls [tls_domain.c:714]: set_verification(): TLSc<default>: Server MAY present invalid certificate 6(1027) ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error 6(1027) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:141FC044:SSL routines:tls_setup_handshake:internal error 6(1027) ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP: XXXXXXXXXXXXXXX 6(1027) ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination IP: XXXXXXXXXX 6(1027) ERROR: <core> [core/tcp_read.c:1498]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f2cbc1b3948 r: 0x7f2cbc1b3a70 (-1) so no segmentation fault but error in handling. Second one also with http_async_client loaded: 0(1059) INFO: <core> [core/tcp_main.c:4983]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1061) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1061) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1061) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support! 0(1061) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman 0(1061) INFO: http_async_client [http_async_client_mod.c:222]: mod_init(): Initializing Http Async module 0(1061) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 5242880 and 2621440 bytes 0(1061) INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold1 has been changed to 5242880 0(1061) INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 2621440 0(1061) INFO: <core> [main.c:2833]: main(): processes (at least): 10 - shm size: 67108864 - pkg size: 67108864 0(1061) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1061) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1061) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSs<default>: tls_method=12 0(1061) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSs<default>: certificate='/etc/kamailio/fullchain.pem' 0(1061) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSs<default>: ca_list='(null)' 0(1061) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSs<default>: crl='(null)' 0(1061) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): TLSs<default>: require_certificate=0 0(1061) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSs<default>: cipher_list='(null)' 0(1061) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSs<default>: private_key='/etc/kamailio/privkey.pem' 0(1061) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): TLSs<default>: verify_certificate=0 0(1061) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSs<default>: verify_depth=9 0(1061) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSs<default>: verify_client=0 0(1061) NOTICE: tls [tls_domain.c:1105]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... 0(1061) INFO: tls [tls_domain.c:711]: set_verification(): TLSs<default>: No client certificate required and no checks performed 0(1061) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSc<default>: tls_method=20 0(1061) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSc<default>: certificate='(null)' 0(1061) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSc<default>: ca_list='(null)' 0(1061) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSc<default>: crl='(null)' 0(1061) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): TLSc<default>: require_certificate=0 0(1061) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSc<default>: cipher_list='(null)' 0(1061) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSc<default>: private_key='(null)' 0(1061) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): TLSc<default>: verify_certificate=0 0(1061) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSc<default>: verify_depth=9 0(1061) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSc<default>: verify_client=0 0(1061) INFO: tls [tls_domain.c:714]: set_verification(): TLSc<default>: Server MAY present invalid certificate 0(1061) INFO: http_async_client [async_http.c:101]: async_http_init_sockets(): inter-process event notification sockets initialized 0(1061) INFO: http_async_client [async_http.c:84]: async_http_init_worker(): started worker process: 1 0(1059) CRITICAL: <core> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer 0x1 (out of memory block!) called from tls: tls_init.c: ser_free(323) - ignoring Segmentation fault this time, there is a segmentation fault. The above is a result of this minimal configuration: #!KAMAILIO ####### Global Parameters ######### /* LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR, ... */ debug=2 log_stderror=no memdbg=5 memlog=5 log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " children=2 tcp_children=2 auto_aliases=no alias="XXXXXXXXXXXXX" listen=udp:eth0 server_signature=no tcp_connection_lifetime=3605 tcp_max_connections=40960 tcp_accept_no_cl=yes enable_tls=yes listen=tls:XXXXXXXXXX:5061 advertise XXXXXXXXXXXX:5061 tls_max_connections=40000 enable_sctp=no ####### Modules Section ######## loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "tls.so" loadmodule "http_async_client.so" #----------------- setting module-specific parameters --------------- #----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") #----- http client ---- modparam("http_async_client", "workers", 1) ####### Routing Logic ######## request_route { exit; } I used the above configuration to take out as much as possible my mistakes in the configuration, but with my full kamailio configuration, tls connections give the above errors but everything else works just fine (also http_async_client module functions which are used on INVITES) and calls are going properly (unfortunately tls is required). I found a couple of issues that are similar https://github.com/kamailio/kamailio/issues/2560 and https://github.com/kamailio/kamailio/issues/2466# but as far as I understood the issue 2466 is closed because fixes are already included. I tried in any case to compile from source a few older releases with the same result, changed also the certificate and private key (letsencrypt), moreover I have another kamailio (v5.3.4) running on ubuntu 18.04 (same configuration) without any issues. I saw that there is a different version of openssl version 1.0.. in ubuntu 18.04, version 1.1 in ubuntu 20.04, but the segmentation fault seems to happen after an error on free some memory. Have you some ideas? tell me if you need more info from me. Thanks Filippo

4 7

Problems establishing SIP signaling between MsTeams and Kamailio
by Willy Valles Rios 28 Jan '21

28 Jan '21

Hello community, I am having trouble establishing SIP signaling between MsTeams and Kamailio. I currently have this configuration in my tls.cfg file [server: default] method = TLSv1.2 + verify_certificate = yes require_certificate = yes private_key = /etc/kamailio/certificates/private-key.pem certificate = /etc/kamailio/certificates/certificate.pem [client: default] method = TLSv1.2 + verify_certificate = yes require_certificate = yes private_key = /etc/kamailio/certificates/private-key.pem certificate = /etc/kamailio/certificates/certificate.pem My domain was certified with ssl through an authoritative certifier (GoDaddy), however I see these errors in the / var / log / messages of the Kamailio server. Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support! Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_init.c:722]: tls_h_mod_init_f(): compiled with openssl version "OpenSSL 1.0.2k-fips 26 Jan 2017" (0x100020bf), kerberos support: on, compression: on Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_init.c:730]: tls_h_mod_init_f(): installed openssl library version "OpenSSL 1.0.2k-fips 26 Jan 2017" (0x100020bf), kerberos support: on, zlib compression: on#012 compiler: gcc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: WARNING: tls [tls_init.c:787]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 13107200 and 6553600 bytes Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: [core/cfg/cfg_ctx.c:598]: cfg_set_now(): tls.low_mem_threshold1 has been changed to 13107200 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: [core/cfg/cfg_ctx.c:598]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 6553600 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: [main.c:2834]: main(): processes (at least): 25 - shm size: 67108864 - pkg size: 4194304 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSs: tls_method=22 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSs: certificate='/etc/kamailio/certificados/certificate.pem' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSs: ca_list='(null)' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSs: crl='(null)' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:335]: ksr_tls_fill_missing(): TLSs: require_certificate=1 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSs: cipher_list='(null)' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSs: private_key='/etc/kamailio/certificados/private-key.pem' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:353]: ksr_tls_fill_missing(): TLSs: verify_certificate=1 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSs: verify_depth=9 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSs: verify_client=0 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: NOTICE: tls [tls_domain.c:1107]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='' ... Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:697]: set_verification(): TLSs: Client MUST present valid certificate Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSc: tls_method=22 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSc: certificate='/etc/kamailio/certificados/certificate.pem' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSc: ca_list='(null)' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSc: crl='(null)' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:335]: ksr_tls_fill_missing(): TLSc: require_certificate=1 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSc: cipher_list='(null)' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSc: private_key='/etc/kamailio/certificados/private-key.pem' Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:353]: ksr_tls_fill_missing(): TLSc: verify_certificate=1 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSc: verify_depth=9 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSc: verify_client=0 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:697]: set_verification(): TLSc: Server MUST present valid certificate Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32422]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/32422 Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32424]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32425]: ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32425]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS write:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32425]: ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP: 52.114.75.24 Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32425]: ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination IP: 161.35.44.66 Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32425]: ERROR: [core/tcp_read.c:1493]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f45242be028 r: 0x7f45242be150 (-1) Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32426]: ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32426]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS write:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32426]: ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP: 52.114.132.46 Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32426]: ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination IP: 161.35.44.66 Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32426]: ERROR: [core/tcp_read.c:1493]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f45242d9278 r: 0x7f45242d93a0 (-1) Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32427]: ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32427]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS write:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32427]: ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP: 52.114.14.70 Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32427]: ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination IP: 161.35.44.66 Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32427]: ERROR: [core/tcp_read.c:1493]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f45242be028 r: 0x7f45242be150 (-1) Could you help me identify the problem please. Cheers Saludos Cordiales -- *Willy Valles Rios* *Unified Communications Specialist* phone: +51955747343 em@il: willyvalles17(a)gmail.com

9 18

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 2021