<div dir="ltr"><div>Dear Kamilio Community,<br><br>After doing several reads to our Kamailio configuration, the dispatcher list is in AP:<br><br>URI: sip: <a href="http://sip.pstnhub.microsoft.com">sip.pstnhub.microsoft.com</a>; transport = tls<br> FLAGS: AP<br>URI: sip: <a href="http://sip2.pstnhub.microsoft.com">sip2.pstnhub.microsoft.com</a>; transport = tls<br> FLAGS: AP<br>URI: sip: <a href="http://sip3.pstnhub.microsoft.com">sip3.pstnhub.microsoft.com</a>; transport = tls<br> FLAGS: AP<br><br>But in the MS Teams dashboard the SIP OPTIONS STATUS column is WARNING.<br><br>In the LOGs sent to OPTIONS, it gives us to understand that with sent to MS TEAMS:<br></div><div><br></div><div>Jan 8 19:01:40 Kamailio-Server /usr/sbin/kamailio[1444]: INFO: <script>: Sent out tm request: OPTIONS sip:<a href="http://sip.pstnhub.microsoft.com">sip.pstnhub.microsoft.com</a>;transport=tls SIP/2.0#015#012Via: SIP/2.0/TLS 161.35.44.66:5061;branch=z9hG4bKd25f.2835f676000000000000000000000000.0#015#012To: <sip:<a href="http://sip.pstnhub.microsoft.com">sip.pstnhub.microsoft.com</a>;transport=tls>#015#012From: <sip:<a href="http://sbc.netvoiceperu.com">sbc.netvoiceperu.com</a>>;tag=69ae0da9200ed8d142f2e4a69f531080-213e3c71#015#012CSeq: 10 OPTIONS#015#012Call-ID: <a href="http://07561978687e60d0-1444@10.131.245.99#015#012Max-Forwards">07561978687e60d0-1444@10.131.245.99#015#012Max-Forwards</a>: 70#015#012Content-Length: 0#015#012User-Agent: kamailio (5.4.0 (x86_64/linux))<br>Jan 8 19:01:40 Kamailio-Server /usr/sbin/kamailio[1444]: INFO: <script>: Sent out tm request: OPTIONS sip:<a href="http://sip2.pstnhub.microsoft.com">sip2.pstnhub.microsoft.com</a>;transport=tls SIP/2.0#015#012Via: SIP/2.0/TLS 161.35.44.66:5061;branch=z9hG4bKe25f.b14dc514000000000000000000000000.0#015#012To: <sip:<a href="http://sip2.pstnhub.microsoft.com">sip2.pstnhub.microsoft.com</a>;transport=tls>#015#012From: <sip:<a href="http://sbc.netvoiceperu.com">sbc.netvoiceperu.com</a>>;tag=69ae0da9200ed8d142f2e4a69f531080-44c3af70#015#012CSeq: 10 OPTIONS#015#012Call-ID: <a href="http://07561978687e60d1-1444@10.131.245.99#015#012Max-Forwards">07561978687e60d1-1444@10.131.245.99#015#012Max-Forwards</a>: 70#015#012Content-Length: 0#015#012User-Agent: kamailio (5.4.0 (x86_64/linux))<br>Jan 8 19:01:40 Kamailio-Server /usr/sbin/kamailio[1444]: INFO: <script>: Sent out tm request: OPTIONS sip:<a href="http://sip3.pstnhub.microsoft.com">sip3.pstnhub.microsoft.com</a>;transport=tls SIP/2.0#015#012Via: SIP/2.0/TLS 161.35.44.66:5061;branch=z9hG4bKb25f.8442f914000000000000000000000000.0#015#012To: <sip:<a href="http://sip3.pstnhub.microsoft.com">sip3.pstnhub.microsoft.com</a>;transport=tls>#015#012From: <sip:<a href="http://sbc.netvoiceperu.com">sbc.netvoiceperu.com</a>>;tag=69ae0da9200ed8d142f2e4a69f531080-fa555adb#015#012CSeq: 10 OPTIONS#015#012Call-ID: <a href="http://07561978687e60d2-1444@10.131.245.99#015#012Max-Forwards">07561978687e60d2-1444@10.131.245.99#015#012Max-Forwards</a>: 70#015#012Content-Length: 0#015#012User-Agent: kamailio (5.4.0 (x86_64/linux))<br>Jan 8 19:01:42 Kamailio-Server journal: Suppressed 103 messages from /system.slice/kamailio.service<br></div><div><br></div><div>In the kamailio.cfg configuration it is declared:<br><br> listen=tls:<a href="http://161.35.44.66:5061">161.35.44.66:5061</a><br> listen=tcp:<a href="http://10.131.245.99:5061">10.131.245.99:5061</a><br><br>modparam ("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")<br>modparam ("dispatcher", "ds_probing_mode", 1)<br>modparam ("dispatcher", "ds_ping_interval", 60)<br><br>And this fragment was also added:<br><br>event_route [tm: local-request] {<br><br> if (is_method ("OPTIONS") && $ ru = ~ "<a href="http://pstnhub.microsoft.com">pstnhub.microsoft.com</a>") {<br> append_hf ("Contact: <sip: <a href="http://sbc.netvoiceperu.com">sbc.netvoiceperu.com</a>: 5061; transport = tls> \ r \ n");<br> }<br> xlog ("L_INFO", "Sent out tm request: $ mb \ n");<br>}<br></div><div><br></div><div>There is something additional that has to be declared so that in the MS Teams panel the SIP OPTIONS STATUS column is shown as ACTIVE and not as WARNNING, in the MS TEAMS documentation it is a possible problem related to OPTIONS events.<br></div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Atentamente<b><br><br>Adalberto Carlos Mestanza T.</b><br><br></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El jue, 7 ene 2021 a las 21:54, Ovidiu Sas (<<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">That certificate should already be present under the OS's trusted<br>
certificates directory (debian and ubuntu certs are stored under<br>
/etc/ssl/certs), maybe under a different name, and is required for<br>
remote endpoint's certificate validation.<br>
One can load a particular certificate or a list of certificates.<br>
Multiple certificates can be concatenated into one single file as<br>
stated in the documentation:<br>
<a href="https://kamailio.org/docs/modules/devel/modules/tls.html#tls.p.ca_list" rel="noreferrer" target="_blank">https://kamailio.org/docs/modules/devel/modules/tls.html#tls.p.ca_list</a><br>
Hope this helps a little bit in understanding of the ca_list param.<br>
<br>
Regards,<br>
Ovidiu Sas<br>
<br>
On Thu, Jan 7, 2021 at 8:10 AM <<a href="mailto:rob.van.den.bulk@gmail.com" target="_blank">rob.van.den.bulk@gmail.com</a>> wrote:<br>
><br>
> I Used this tls.cfg<br>
><br>
><br>
><br>
> Use bc2025.pem as extra, Microsoft needs this…<br>
><br>
><br>
><br>
> And works fine on different Kamailio-msteams sbcs<br>
><br>
><br>
><br>
><br>
><br>
> [server:default]<br>
><br>
> method = TLSv1.2+<br>
><br>
> verify_certificate = yes<br>
><br>
> require_certificate = yes<br>
><br>
> private_key = /etc/letsencrypt/live/sbc.combivoipdom.nl-0001/privkey.pem<br>
><br>
> certificate = /etc/letsencrypt/live/sbc.combivoipdom.nl-0001/fullchain.pem<br>
><br>
> ca_list = /etc/letsencrypt/live/sbc.combivoipdom.nl-0001/bc2025.pem<br>
><br>
> server_name = <a href="http://sbc.combivoipdom.nl" rel="noreferrer" target="_blank">sbc.combivoipdom.nl</a><br>
><br>
><br>
><br>
> [client:default]<br>
><br>
> method = TLSv1.2+<br>
><br>
> verify_certificate = yes<br>
><br>
> require_certificate = yes<br>
><br>
> private_key = /etc/letsencrypt/live/sbc.combivoipdom.nl-0001/privkey.pem<br>
><br>
> certificate = /etc/letsencrypt/live/sbc.combivoipdom.nl-0001/fullchain.pem<br>
><br>
> ca_list = /etc/letsencrypt/live/sbc.combivoipdom.nl-0001/bc2025.pem<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Cheers Rob<br>
><br>
><br>
><br>
> Van: sr-users <<a href="mailto:sr-users-bounces@lists.kamailio.org" target="_blank">sr-users-bounces@lists.kamailio.org</a>> Namens Daniel-Constantin Mierla<br>
> Verzonden: donderdag 7 januari 2021 08:53<br>
> Aan: Kamailio (SER) - Users Mailing List <<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a>>; Willy Valles Rios <<a href="mailto:willyvalles17@gmail.com" target="_blank">willyvalles17@gmail.com</a>><br>
> CC: Carlos Mestanza T. <<a href="mailto:mestacart@gmail.com" target="_blank">mestacart@gmail.com</a>><br>
> Onderwerp: Re: [SR-Users] Problems establishing SIP signaling between MsTeams and Kamailio<br>
><br>
><br>
><br>
> Does this happen when Kamailio connects to MS Teams? The logs indicate the received TLS certificate is not trusted:<br>
><br>
> 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<br>
><br>
><br>
><br>
> You can set debug=3 in kamailio.cfg and see if the DEBUG messages provide more hints. For me it worked fine with Letsencrypt certs in Kamailio and accepting what ever MS sent back. I used Debian 10 and libssl 1.1.<br>
><br>
><br>
><br>
> Cheers,<br>
> Daniel<br>
><br>
><br>
><br>
> On 06.01.21 21:47, Willy Valles Rios wrote:<br>
><br>
> Hello community,<br>
><br>
><br>
><br>
> I am having trouble establishing SIP signaling between MsTeams and Kamailio. I currently have this configuration in my tls.cfg file<br>
><br>
><br>
><br>
> [server: default]<br>
><br>
> method = TLSv1.2 +<br>
><br>
> verify_certificate = yes<br>
><br>
> require_certificate = yes<br>
><br>
> private_key = /etc/kamailio/certificates/private-key.pem<br>
><br>
> certificate = /etc/kamailio/certificates/certificate.pem<br>
><br>
><br>
><br>
> [client: default]<br>
><br>
> method = TLSv1.2 +<br>
><br>
> verify_certificate = yes<br>
><br>
> require_certificate = yes<br>
><br>
> private_key = /etc/kamailio/certificates/private-key.pem<br>
><br>
> certificate = /etc/kamailio/certificates/certificate.pem<br>
><br>
><br>
><br>
> 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.<br>
><br>
><br>
><br>
> Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support!<br>
><br>
> Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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'<br>
><br>
> 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)'<br>
><br>
> Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSs: crl='(null)'<br>
><br>
> 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<br>
><br>
> 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)'<br>
><br>
> 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'<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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='' ...<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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'<br>
><br>
> 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)'<br>
><br>
> Jan 6 15:13:45 Kamailio-Server /usr/sbin/kamailio[32409]: INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSc: crl='(null)'<br>
><br>
> 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<br>
><br>
> 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)'<br>
><br>
> 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'<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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)<br>
><br>
> Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32425]: ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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)<br>
><br>
> Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32426]: ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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)<br>
><br>
> Jan 6 15:13:55 Kamailio-Server /usr/sbin/kamailio[32427]: ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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<br>
><br>
> 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)<br>
><br>
><br>
><br>
> Could you help me identify the problem please.<br>
><br>
><br>
><br>
> Cheers<br>
><br>
><br>
><br>
> Saludos Cordiales<br>
><br>
> --<br>
><br>
> Willy Valles Rios<br>
><br>
> Unified Communications Specialist<br>
><br>
><br>
><br>
> phone: +51955747343<br>
><br>
> em@il: <a href="mailto:willyvalles17@gmail.com" target="_blank">willyvalles17@gmail.com</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
><br>
> Kamailio (SER) - Users Mailing List<br>
><br>
> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
><br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
> --<br>
><br>
> Daniel-Constantin Mierla -- <a href="http://www.asipto.com" rel="noreferrer" target="_blank">www.asipto.com</a><br>
><br>
> <a href="http://www.twitter.com/miconda" rel="noreferrer" target="_blank">www.twitter.com/miconda</a> -- <a href="http://www.linkedin.com/in/miconda" rel="noreferrer" target="_blank">www.linkedin.com/in/miconda</a><br>
><br>
> Funding: <a href="https://www.paypal.me/dcmierla" rel="noreferrer" target="_blank">https://www.paypal.me/dcmierla</a><br>
><br>
> _______________________________________________<br>
> Kamailio (SER) - Users Mailing List<br>
> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
<br>
<br>
-- <br>
VoIP Embedded, Inc.<br>
<a href="http://www.voipembedded.com" rel="noreferrer" target="_blank">http://www.voipembedded.com</a><br>
</blockquote></div>