<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p>do not reply to mailing list digest messages, they have no
relation to the message you want to continue the discussion.</p>
<p>If you want to engage in an active discussion, disable the digest
option and follow up by replying to specific messages.<br>
</p>
<p>Or just create a new message, and if you want to refer to an
existing discussion, then paste the link to the thread discussion
on mailing list web archive.</p>
<p>Cheers,<br>
DAniel<br>
</p>
<div class="moz-cite-prefix">On 26.01.21 17:54, Willy Valles Rios
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOtNiqQ3oreGDWpeB6bXCOUPYN71xrwC5uEFMZ4GfNx_H3KX9g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">Hello community,<br>
<br>
After a while, I finally got the connection from my Kamailio
server to MsTeams and I can validate that the connection to
MsTeams is in AP.<br>
<br>
[root @ kamailio-server kamailio] # kamcmd dispatcher.list |
egrep "URI | FLAGS"<br>
URI: sip: <a
href="http://sip.pstnhub.microsoft.com"
moz-do-not-send="true">sip.pstnhub.microsoft.com</a>;
transport = tls<br>
FLAGS: AP<br>
<br>
However, from the admin panel of MsTeams (Direct Routing) I
see that the connection to my sbc "<a
href="http://sbc.netvoiceperu.com" moz-do-not-send="true">sbc.netvoiceperu.com</a>"
is with TLS connectivity status in "Active" but the SIP
options status is in "Warning".<br>
<br>
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.<br>
<br>
OPTIONS sip: <a href="http://sip.pstnhub.microsoft.com"
moz-do-not-send="true">sip.pstnhub.microsoft.com</a>;
transport = tls SIP / 2.0<br>
Via: SIP / 2.0 / TLS
161.35.44.66:5061;branch=z9hG4bKea07.52224687000000000000000000000000.0<br>
To: <sip: <a href="http://sip.pstnhub.microsoft.com"
moz-do-not-send="true">sip.pstnhub.microsoft.com</a>;
transport = tls><br>
From: <sip: <a href="http://sbc.netvoiceperu.com"
moz-do-not-send="true">sbc.netvoiceperu.com</a>>; tag =
d3569c818b500aeb8c373426e76c2884-81763c71<br>
CSeq: 10 OPTIONS<br>
Call-ID: <a href="mailto:13ea237a751e0c48-9148@161.35.44.66"
moz-do-not-send="true">13ea237a751e0c48-9148@161.35.44.66</a><br>
Max-Forwards: 70<br>
Content-Length: 0<br>
User-Agent: kamailio (5.4.0 (x86_64 / linux))<br>
<br>
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<br>
<br>
event_route [tm: local-request] {<br>
sip_trace ();<br>
if (is_method ("OPTIONS") && $ ru = ~ "<a
href="http://pstnhub.microsoft.com" moz-do-not-send="true">pstnhub.microsoft.com</a>")
{<br>
append_hf ("Contact: <sip: <a
href="http://sbc.netvoiceperu.com" moz-do-not-send="true">sbc.netvoiceperu.com</a>:
5061; transport = tls> \ r \ n");<br>
}<br>
xlog ("L_INFO", "Sent out tm request: $ mb \ n");<br>
}<br>
<br>
As additional information, I inform you that I also managed to
observe the SIP OPTIONS that MsTeams sends to Kamailio.<br>
<br>
OPTIONS sip: <a href="http://sbc.netvoiceperu.com"
moz-do-not-send="true">sbc.netvoiceperu.com</a>: 5061;
transport = tls SIP / 2.0<br>
FROM: <sip: <a
href="http://sip-du-a-eu.pstnhub.microsoft.com"
moz-do-not-send="true">sip-du-a-eu.pstnhub.microsoft.com</a>:
5061>; tag = f1bdeb5f-662f-4544-a436-e9aa9ad78da4<br>
TO: <sip: <a href="http://sbc.netvoiceperu.com"
moz-do-not-send="true">sbc.netvoiceperu.com</a>><br>
CSEQ: 1 OPTIONS<br>
CALL-ID: c47e2782-16c3-49cb-8931-24e9709d260a<br>
MAX-FORWARDS: 70<br>
VIA: SIP / 2.0 / TLS 52.114.75.24:5061;branch=z9hG4bK48b0e6be<br>
CONTACT: <sip: <a
href="http://sip-du-a-eu.pstnhub.microsoft.com"
moz-do-not-send="true">sip-du-a-eu.pstnhub.microsoft.com</a>:
5061><br>
CONTENT-LENGTH: 0<br>
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2021.1.15.7 i.EUWE.10<br>
ALLOW: INVITE, ACK, OPTIONS, CANCEL, BYE, NOTIFY<br>
<br>
However I don't see the 200 OK SIP responses from Kamailio to
MsTeams.<br>
<br>
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.<br>
<br>
Could you help me solve this please.<br>
<br>
Cheers<br clear="all">
</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div><br>
</div>
<div><font face="verdana,
sans-serif">Saludos Cordiales</font></div>
<div><span
style="color:rgb(136,136,136);font-family:"Times
New
Roman";font-size:13.3333px;background-color:rgb(253,253,253)">--</span><span
style="color:rgb(136,136,136);font-family:"Times New
Roman";font-size:13.3333px;background-color:rgb(253,253,253)"> </span><br>
</div>
<div
style="background-color:rgb(253,253,253)">
<div dir="ltr"><font
style="color:rgb(136,136,136);font-family:"Times
New Roman"" size="2"
face="trebuchet ms,
sans-serif"><u>Willy Valles
Rios</u></font>
<div>
<div><font face="trebuchet
ms, sans-serif"
color="#bf9000"><b>Unified
Communications
Specialist</b></font></div>
<div
style="color:rgb(136,136,136);font-family:"Times
New
Roman";font-size:13.3333px"><b><font
face="trebuchet ms,
sans-serif"
color="#bf9000"><br>
</font></b></div>
<div
style="color:rgb(136,136,136);font-family:"Times
New
Roman";font-size:13.3333px"><font
face="trebuchet ms,
sans-serif">phone:
+51955747343</font></div>
<div
style="color:rgb(136,136,136);font-family:"Times
New
Roman";font-size:13.3333px"><font
face="trebuchet ms,
sans-serif">em@il: <span
style="color:rgb(51,102,153)"><a href="mailto:willyvalles17@gmail.com"
target="_blank"
moz-do-not-send="true">willyvalles17@gmail.com</a></span></font></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">El dom, 10 ene 2021 a las
6:03, <<a href="mailto:sr-users-request@lists.kamailio.org"
moz-do-not-send="true">sr-users-request@lists.kamailio.org</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">Send
sr-users mailing list submissions to<br>
<a href="mailto:sr-users@lists.kamailio.org"
target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sr-users-request@lists.kamailio.org"
target="_blank" moz-do-not-send="true">sr-users-request@lists.kamailio.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:sr-users-owner@lists.kamailio.org"
target="_blank" moz-do-not-send="true">sr-users-owner@lists.kamailio.org</a><br>
<br>
When replying, please edit your Subject line so it is more
specific<br>
than "Re: Contents of sr-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Problems establishing SIP signaling between MsTeams
and<br>
Kamailio (Carlos Mestanza T.)<br>
2. Re: Problems establishing SIP signaling between MsTeams
and<br>
Kamailio (Rob van den Bulk)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 8 Jan 2021 19:16:30 -0500<br>
From: "Carlos Mestanza T." <<a
href="mailto:mestacart@gmail.com" target="_blank"
moz-do-not-send="true">mestacart@gmail.com</a>><br>
To: Ovidiu Sas <<a href="mailto:osas@voipembedded.com"
target="_blank" moz-do-not-send="true">osas@voipembedded.com</a>><br>
Cc: "Kamailio (SER) - Users Mailing List"<br>
<<a href="mailto:sr-users@lists.kamailio.org"
target="_blank" moz-do-not-send="true">sr-users@lists.kamailio.org</a>>,
"Daniel Constantin Mierla (asipto)"<br>
<<a href="mailto:miconda@gmail.com" target="_blank"
moz-do-not-send="true">miconda@gmail.com</a>><br>
Subject: Re: [SR-Users] Problems establishing SIP signaling
between<br>
MsTeams and Kamailio<br>
Message-ID:<br>
<<a
href="mailto:CAHcXM7PN0zuJC9jONTERZdfur3b%2BucwnCC712Ss1OBxCiMctUg@mail.gmail.com"
target="_blank" moz-do-not-send="true">CAHcXM7PN0zuJC9jONTERZdfur3b+ucwnCC712Ss1OBxCiMctUg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Dear Kamilio Community,<br>
<br>
After doing several reads to our Kamailio configuration, the
dispatcher<br>
list is in AP:<br>
<br>
URI: sip: <a href="http://sip.pstnhub.microsoft.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">sip.pstnhub.microsoft.com</a>;
transport = tls<br>
FLAGS: AP<br>
URI: sip: <a href="http://sip2.pstnhub.microsoft.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">sip2.pstnhub.microsoft.com</a>;
transport = tls<br>
FLAGS: AP<br>
URI: sip: <a href="http://sip3.pstnhub.microsoft.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">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<br>
TEAMS:<br>
<br>
Jan 8 19:01:40 Kamailio-Server /usr/sbin/kamailio[1444]:
INFO: <script>:<br>
Sent out tm request: OPTIONS sip:<a
href="http://sip.pstnhub.microsoft.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">sip.pstnhub.microsoft.com</a>;transport=tls<br>
SIP/2.0#015#012Via: SIP/2.0/TLS<br>
161.35.44.66:5061;branch=z9hG4bKd25f.2835f676000000000000000000000000.0#015#012To:<br>
<sip:<a href="http://sip.pstnhub.microsoft.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">sip.pstnhub.microsoft.com</a>;transport=tls>#015#012From:
<sip:<br>
<a href="http://sbc.netvoiceperu.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">sbc.netvoiceperu.com</a>>;tag=69ae0da9200ed8d142f2e4a69f531080-213e3c71#015#012CSeq:<br>
10 OPTIONS#015#012Call-ID:<br>
<a
href="http://07561978687e60d0-1444@10.131.245.99#015%23012Max-Forwards"
rel="noreferrer" target="_blank" moz-do-not-send="true">07561978687e60d0-1444@10.131.245.99#015#012Max-Forwards</a>:<br>
70#015#012Content-Length: 0#015#012User-Agent: kamailio (5.4.0<br>
(x86_64/linux))<br>
Jan 8 19:01:40 Kamailio-Server /usr/sbin/kamailio[1444]:
INFO: <script>:<br>
Sent out tm request: OPTIONS sip:<a
href="http://sip2.pstnhub.microsoft.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">sip2.pstnhub.microsoft.com</a>;transport=tls<br>
SIP/2.0#015#012Via: SIP/2.0/TLS<br>
161.35.44.66:5061;branch=z9hG4bKe25f.b14dc514000000000000000000000000.0#015#012To:<br>
<sip:<a href="http://sip2.pstnhub.microsoft.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">sip2.pstnhub.microsoft.com</a>;transport=tls>#015#012From:
<sip:<br>
<a href="http://sbc.netvoiceperu.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">sbc.netvoiceperu.com</a>>;tag=69ae0da9200ed8d142f2e4a69f531080-44c3af70#015#012CSeq:<br>
10 OPTIONS#015#012Call-ID:<br>
<a
href="http://07561978687e60d1-1444@10.131.245.99#015%23012Max-Forwards"
rel="noreferrer" target="_blank" moz-do-not-send="true">07561978687e60d1-1444@10.131.245.99#015#012Max-Forwards</a>:<br>
70#015#012Content-Length: 0#015#012User-Agent: kamailio (5.4.0<br>
(x86_64/linux))<br>
Jan 8 19:01:40 Kamailio-Server /usr/sbin/kamailio[1444]:
INFO: <script>:<br>
Sent out tm request: OPTIONS sip:<a
href="http://sip3.pstnhub.microsoft.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">sip3.pstnhub.microsoft.com</a>;transport=tls<br>
SIP/2.0#015#012Via: SIP/2.0/TLS<br>
161.35.44.66:5061;branch=z9hG4bKb25f.8442f914000000000000000000000000.0#015#012To:<br>
<sip:<a href="http://sip3.pstnhub.microsoft.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">sip3.pstnhub.microsoft.com</a>;transport=tls>#015#012From:
<sip:<br>
<a href="http://sbc.netvoiceperu.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">sbc.netvoiceperu.com</a>>;tag=69ae0da9200ed8d142f2e4a69f531080-fa555adb#015#012CSeq:<br>
10 OPTIONS#015#012Call-ID:<br>
<a
href="http://07561978687e60d2-1444@10.131.245.99#015%23012Max-Forwards"
rel="noreferrer" target="_blank" moz-do-not-send="true">07561978687e60d2-1444@10.131.245.99#015#012Max-Forwards</a>:<br>
70#015#012Content-Length: 0#015#012User-Agent: kamailio (5.4.0<br>
(x86_64/linux))<br>
Jan 8 19:01:42 Kamailio-Server journal: Suppressed 103
messages from<br>
/system.slice/kamailio.service<br>
<br>
In the kamailio.cfg configuration it is declared:<br>
<br>
listen=tls:<a href="http://161.35.44.66:5061"
rel="noreferrer" target="_blank" moz-do-not-send="true">161.35.44.66:5061</a><br>
listen=tcp:<a href="http://10.131.245.99:5061"
rel="noreferrer" target="_blank" moz-do-not-send="true">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" rel="noreferrer"
target="_blank" moz-do-not-send="true">pstnhub.microsoft.com</a>")
{<br>
append_hf ("Contact: <sip: <a
href="http://sbc.netvoiceperu.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">sbc.netvoiceperu.com</a>:
5061;<br>
transport = tls> \ r \ n");<br>
}<br>
xlog ("L_INFO", "Sent out tm request: $ mb \ n");<br>
}<br>
<br>
There is something additional that has to be declared so that
in the MS<br>
Teams panel the SIP OPTIONS STATUS column is shown as ACTIVE
and not as<br>
WARNNING, in the MS TEAMS documentation it is a possible
problem related to<br>
OPTIONS events.<br>
<br>
Atentamente<br>
<br>
*Adalberto Carlos Mestanza T.*<br>
<br>
<br>
<br>
El jue, 7 ene 2021 a las 21:54, Ovidiu Sas (<<a
href="mailto:osas@voipembedded.com" target="_blank"
moz-do-not-send="true">osas@voipembedded.com</a>>)<br>
escribi?:<br>
<br>
> 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" moz-do-not-send="true">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"
moz-do-not-send="true">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 =<br>
>
/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" moz-do-not-send="true">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 =<br>
>
/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" moz-do-not-send="true">sr-users-bounces@lists.kamailio.org</a>>
Namens<br>
> 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"
moz-do-not-send="true">sr-users@lists.kamailio.org</a>>;<br>
> Willy Valles Rios <<a
href="mailto:willyvalles17@gmail.com" target="_blank"
moz-do-not-send="true">willyvalles17@gmail.com</a>><br>
> > CC: Carlos Mestanza T. <<a
href="mailto:mestacart@gmail.com" target="_blank"
moz-do-not-send="true">mestacart@gmail.com</a>><br>
> > Onderwerp: Re: [SR-Users] Problems establishing SIP
signaling between<br>
> MsTeams and Kamailio<br>
> ><br>
> ><br>
> ><br>
> > Does this happen when Kamailio connects to MS Teams?
The logs indicate<br>
> the received TLS certificate is not trusted:<br>
> ><br>
> > Jan 6 15:13:55 Kamailio-Server
/usr/sbin/kamailio[32425]: ERROR: tls<br>
> [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL<br>
> 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<br>
> provide more hints. For me it worked fine with
Letsencrypt certs in<br>
> Kamailio and accepting what ever MS sent back. I used
Debian 10 and libssl<br>
> 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<br>
> 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<br>
> (GoDaddy), however I see these errors in the / var / log
/ messages of the<br>
> Kamailio server.<br>
> ><br>
> ><br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [tls_mod.c:389]: mod_init(): With ECDH-Support!<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [tls_mod.c:392]: mod_init(): With Diffie Hellman<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [tls_init.c:722]: tls_h_mod_init_f(): compiled with
openssl version<br>
> "OpenSSL 1.0.2k-fips 26 Jan 2017" (0x100020bf), kerberos
support: on,<br>
> compression: on<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [tls_init.c:730]: tls_h_mod_init_f(): installed openssl
library version<br>
> "OpenSSL 1.0.2k-fips 26 Jan 2017" (0x100020bf), kerberos
support: on, zlib<br>
> compression: on#012 compiler: gcc -I. -I.. -I../include
-fPIC -DOPENSSL_PIC<br>
> -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
-DHAVE_DLFCN_H -DKRB5_MIT<br>
> -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2<br>
> -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4<br>
> -grecord-gcc-switches -m64 -mtune=generic
-Wa,--noexecstack -DPURIFY<br>
> -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT
-DOPENSSL_BN_ASM_MONT5<br>
> -DOPENSSL_BN_ASM_GF2m -DRC4_ASM -DSHA1_ASM -DSHA256_ASM
-DSHA512_ASM<br>
> -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM
-DWHIRLPOOL_ASM -DGHASH_ASM<br>
> -DECP_NISTZ256_ASM<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: WARNING: tls<br>
> [tls_init.c:787]: tls_h_mod_init_f(): openssl bug #1491
(crash/mem leaks on<br>
> low memory) workaround enabled (on low memory tls
operations will fail<br>
> preemptively) with free memory thresholds 13107200 and
6553600 bytes<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO:<br>
> [core/cfg/cfg_ctx.c:598]: cfg_set_now():
tls.low_mem_threshold1 has been<br>
> changed to 13107200<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO:<br>
> [core/cfg/cfg_ctx.c:598]: cfg_set_now():
tls.low_mem_threshold2 has been<br>
> changed to 6553600<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO:<br>
> [main.c:2834]: main(): processes (at least): 25 - shm
size: 67108864 - pkg<br>
> size: 4194304<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO:<br>
> [core/udp_server.c:154]: probe_max_receive_buffer():
SO_RCVBUF is initially<br>
> 212992<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO:<br>
> [core/udp_server.c:206]: probe_max_receive_buffer():
SO_RCVBUF is finally<br>
> 425984<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [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<br>
> [tls_domain.c:317]: ksr_tls_fill_missing(): TLSs:<br>
> certificate='/etc/kamailio/certificados/certificate.pem'<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [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<br>
> [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<br>
> [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<br>
> [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<br>
> [tls_domain.c:349]: ksr_tls_fill_missing(): TLSs:<br>
> private_key='/etc/kamailio/certificados/private-key.pem'<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [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<br>
> [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<br>
> [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<br>
> [tls_domain.c:1107]: ksr_tls_fix_domain(): registered
server_name callback<br>
> handler for socket [:0], server_name='' ...<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [tls_domain.c:697]: set_verification(): TLSs: Client MUST
present valid<br>
> certificate<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [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<br>
> [tls_domain.c:317]: ksr_tls_fill_missing(): TLSc:<br>
> certificate='/etc/kamailio/certificados/certificate.pem'<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [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<br>
> [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<br>
> [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<br>
> [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<br>
> [tls_domain.c:349]: ksr_tls_fill_missing(): TLSc:<br>
> private_key='/etc/kamailio/certificados/private-key.pem'<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32409]: INFO: tls<br>
> [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<br>
> [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<br>
> [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<br>
> [tls_domain.c:697]: set_verification(): TLSc: Server MUST
present valid<br>
> certificate<br>
> ><br>
> > Jan 6 15:13:45 Kamailio-Server
/usr/sbin/kamailio[32422]: INFO: jsonrpcs<br>
> [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<br>
> [io_listener.c:214]: io_listen_loop(): io_listen_loop:
using epoll_lt io<br>
> watch method (config)<br>
> ><br>
> > Jan 6 15:13:55 Kamailio-Server
/usr/sbin/kamailio[32425]: ERROR: tls<br>
> [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<br>
> [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL<br>
> routines:ssl3_get_server_certificate:certificate verify
failed<br>
> ><br>
> > Jan 6 15:13:55 Kamailio-Server
/usr/sbin/kamailio[32425]: ERROR: tls<br>
> [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<br>
> [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:<br>
> [core/tcp_read.c:1493]: tcp_read_req(): ERROR:
tcp_read_req: error reading<br>
> - c: 0x7f45242be028 r: 0x7f45242be150 (-1)<br>
> ><br>
> > Jan 6 15:13:55 Kamailio-Server
/usr/sbin/kamailio[32426]: ERROR: tls<br>
> [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<br>
> [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL<br>
> routines:ssl3_get_server_certificate:certificate verify
failed<br>
> ><br>
> > Jan 6 15:13:55 Kamailio-Server
/usr/sbin/kamailio[32426]: ERROR: tls<br>
> [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<br>
> [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:<br>
> [core/tcp_read.c:1493]: tcp_read_req(): ERROR:
tcp_read_req: error reading<br>
> - c: 0x7f45242d9278 r: 0x7f45242d93a0 (-1)<br>
> ><br>
> > Jan 6 15:13:55 Kamailio-Server
/usr/sbin/kamailio[32427]: ERROR: tls<br>
> [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<br>
> [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL<br>
> routines:ssl3_get_server_certificate:certificate verify
failed<br>
> ><br>
> > Jan 6 15:13:55 Kamailio-Server
/usr/sbin/kamailio[32427]: ERROR: tls<br>
> [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<br>
> [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:<br>
> [core/tcp_read.c:1493]: tcp_read_req(): ERROR:
tcp_read_req: error reading<br>
> - 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" moz-do-not-send="true">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" moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
> ><br>
> > <a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">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" moz-do-not-send="true">www.asipto.com</a><br>
> ><br>
> > <a href="http://www.twitter.com/miconda"
rel="noreferrer" target="_blank" moz-do-not-send="true">www.twitter.com/miconda</a>
-- <a href="http://www.linkedin.com/in/miconda"
rel="noreferrer" target="_blank" moz-do-not-send="true">www.linkedin.com/in/miconda</a><br>
> ><br>
> > Funding: <a href="https://www.paypal.me/dcmierla"
rel="noreferrer" target="_blank" moz-do-not-send="true">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" moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
> > <a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">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" moz-do-not-send="true">http://www.voipembedded.com</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a
href="http://lists.kamailio.org/pipermail/sr-users/attachments/20210108/2e3d09f0/attachment-0001.htm"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.kamailio.org/pipermail/sr-users/attachments/20210108/2e3d09f0/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 9 Jan 2021 14:46:40 +0000<br>
From: Rob van den Bulk <<a
href="mailto:rob.van.den.bulk@gmail.com" target="_blank"
moz-do-not-send="true">rob.van.den.bulk@gmail.com</a>><br>
To: Carlos Mestanza T. <<a
href="mailto:mestacart@gmail.com" target="_blank"
moz-do-not-send="true">mestacart@gmail.com</a>><br>
Cc: "<a href="mailto:miconda@gmail.com" target="_blank"
moz-do-not-send="true">miconda@gmail.com</a>" <<a
href="mailto:miconda@gmail.com" target="_blank"
moz-do-not-send="true">miconda@gmail.com</a>>, "Kamailio
(SER) - Users<br>
Mailing List" <<a
href="mailto:sr-users@lists.kamailio.org" target="_blank"
moz-do-not-send="true">sr-users@lists.kamailio.org</a>><br>
Subject: Re: [SR-Users] Problems establishing SIP signaling
between<br>
MsTeams and Kamailio<br>
Message-ID:<br>
<<a
href="mailto:AM8PR08MB5554666278B67C6359764945FCAF0@AM8PR08MB5554.eurprd08.prod.outlook.com"
target="_blank" moz-do-not-send="true">AM8PR08MB5554666278B67C6359764945FCAF0@AM8PR08MB5554.eurprd08.prod.outlook.com</a>><br>
<br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Hallo, warning from Microsoft is "normal" till the first calls
are established.<br>
<br>
<br>
Sent from mobile, with due apologies for brevity and errors.
Rob van den Bulk<br>
<br>
<br>
________________________________<br>
From: Carlos Mestanza T. <<a
href="mailto:mestacart@gmail.com" target="_blank"
moz-do-not-send="true">mestacart@gmail.com</a>><br>
Sent: Thursday, January 7, 2021 9:41:44 PM<br>
To: <a href="mailto:rob.van.den.bulk@gmail.com"
target="_blank" moz-do-not-send="true">rob.van.den.bulk@gmail.com</a>
<<a href="mailto:rob.van.den.bulk@gmail.com"
target="_blank" moz-do-not-send="true">rob.van.den.bulk@gmail.com</a>><br>
Cc: <a href="mailto:miconda@gmail.com" target="_blank"
moz-do-not-send="true">miconda@gmail.com</a> <<a
href="mailto:miconda@gmail.com" target="_blank"
moz-do-not-send="true">miconda@gmail.com</a>>; Kamailio
(SER) - Users Mailing List <<a
href="mailto:sr-users@lists.kamailio.org" target="_blank"
moz-do-not-send="true">sr-users@lists.kamailio.org</a>><br>
Subject: Re: [SR-Users] Problems establishing SIP signaling
between MsTeams and Kamailio<br>
<br>
I am a friend of Willy and we are doing this integration,
today I create wildcard certificates in letsencrypt, for this
use acme.sh and integrate it with the DNS CLOUDNS provider,
the certificates were generated successfully, we replace the
old ones, in the LOGs it gives us understanding q accept the
certificates.<br>
<br>
[image.png]<br>
<br>
[image.png]<br>
<br>
<br>
But he has the same messages.<br>
<br>
<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24810]:
ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level
error<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24810]:
ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL
routines:ssl3_get_server_certificate:certificate verify failed<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24810]:
ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP:
52.114.132.46<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24810]:
ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination
IP: 161.35.44.66<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24810]:
ERROR: <core> [core/tcp_read.c:1493]: tcp_read_req():
ERROR: tcp_read_req: error reading - c: 0x7fdfc14a8cf8 r:
0x7fdfc14a8e20 (-1)<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24811]:
ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level
error<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24811]:
ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL
routines:ssl3_get_server_certificate:certificate verify failed<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24811]:
ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP:
52.114.7.24<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24811]:
ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination
IP: 161.35.44.66<br>
Jan 7 15:32:57 Kamailio-Server /usr/sbin/kamailio[24811]:
ERROR: <core> [core/tcp_read.c:1493]: tcp_read_req():
ERROR: tcp_read_req: error reading - c: 0x7fdfc1424528 r:
0x7fdfc1424650 (-1)<br>
Jan 7 15:33:06 Kamailio-Server /usr/sbin/kamailio[24804]:
ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level
error<br>
Jan 7 15:33:06 Kamailio-Server /usr/sbin/kamailio[24804]:
ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL
routines:ssl3_get_server_certificate:certificate verify failed<br>
Jan 7 15:33:06 Kamailio-Server /usr/sbin/kamailio[24804]:
ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP:
52.114.75.24<br>
Jan 7 15:33:06 Kamailio-Server /usr/sbin/kamailio[24804]:
ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination
IP: 161.35.44.66<br>
Jan 7 15:33:06 Kamailio-Server /usr/sbin/kamailio[24804]:
ERROR: <core> [core/tcp_read.c:1493]: tcp_read_req():
ERROR: tcp_read_req: error reading - c: 0x7fdfc1424528 r:
0x7fdfc1424650 (-1)<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24805]:
ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level
error<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24805]:
ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL
routines:ssl3_get_server_certificate:certificate verify failed<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24805]:
ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP:
52.114.132.46<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24805]:
ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination
IP: 161.35.44.66<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24805]:
ERROR: <core> [core/tcp_read.c:1493]: tcp_read_req():
ERROR: tcp_read_req: error reading - c: 0x7fdfc1494d20 r:
0x7fdfc1494e48 (-1)<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24806]:
ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level
error<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24806]:
ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS
write:error:14090086:SSL
routines:ssl3_get_server_certificate:certificate verify failed<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24806]:
ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP:
52.114.14.70<br>
Jan 7 15:33:07 Kamailio-Server /usr/sbin/kamailio[24806]:
ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination
IP: 161.35.44.66<br>
<br>
<br>
<br>
Atentamente<br>
<br>
Adalberto Carlos Mestanza T.<br>
<br>
<br>
<br>
El jue, 7 ene 2021 a las 8:08, <<a
href="mailto:rob.van.den.bulk@gmail.com" target="_blank"
moz-do-not-send="true">rob.van.den.bulk@gmail.com</a><mailto:<a
href="mailto:rob.van.den.bulk@gmail.com" target="_blank"
moz-do-not-send="true">rob.van.den.bulk@gmail.com</a>>>
escribi?:<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" moz-do-not-send="true">sbc.combivoipdom.nl</a><<a
href="http://sbc.combivoipdom.nl" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://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" moz-do-not-send="true">sr-users-bounces@lists.kamailio.org</a><mailto:<a
href="mailto:sr-users-bounces@lists.kamailio.org"
target="_blank" moz-do-not-send="true">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"
moz-do-not-send="true">sr-users@lists.kamailio.org</a><mailto:<a
href="mailto:sr-users@lists.kamailio.org" target="_blank"
moz-do-not-send="true">sr-users@lists.kamailio.org</a>>>;
Willy Valles Rios <<a href="mailto:willyvalles17@gmail.com"
target="_blank" moz-do-not-send="true">willyvalles17@gmail.com</a><mailto:<a
href="mailto:willyvalles17@gmail.com" target="_blank"
moz-do-not-send="true">willyvalles17@gmail.com</a>>><br>
CC: Carlos Mestanza T. <<a
href="mailto:mestacart@gmail.com" target="_blank"
moz-do-not-send="true">mestacart@gmail.com</a><mailto:<a
href="mailto:mestacart@gmail.com" target="_blank"
moz-do-not-send="true">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" moz-do-not-send="true">willyvalles17@gmail.com</a><mailto:<a
href="mailto:willyvalles17@gmail.com" target="_blank"
moz-do-not-send="true">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"
moz-do-not-send="true">sr-users@lists.kamailio.org</a><mailto:<a
href="mailto:sr-users@lists.kamailio.org" target="_blank"
moz-do-not-send="true">sr-users@lists.kamailio.org</a>><br>
<br>
<a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">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" moz-do-not-send="true">www.asipto.com</a><<a
href="http://www.asipto.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://www.asipto.com</a>><br>
<br>
<a href="http://www.twitter.com/miconda" rel="noreferrer"
target="_blank" moz-do-not-send="true">www.twitter.com/miconda</a><<a
href="http://www.twitter.com/miconda" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://www.twitter.com/miconda</a>>
-- <a href="http://www.linkedin.com/in/miconda"
rel="noreferrer" target="_blank" moz-do-not-send="true">www.linkedin.com/in/miconda</a><<a
href="http://www.linkedin.com/in/miconda" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://www.linkedin.com/in/miconda</a>><br>
<br>
Funding: <a href="https://www.paypal.me/dcmierla"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.paypal.me/dcmierla</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a
href="http://lists.kamailio.org/pipermail/sr-users/attachments/20210109/8317dbba/attachment-0001.htm"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.kamailio.org/pipermail/sr-users/attachments/20210109/8317dbba/attachment-0001.htm</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image.png<br>
Type: image/png<br>
Size: 5460 bytes<br>
Desc: image.png<br>
URL: <<a
href="http://lists.kamailio.org/pipermail/sr-users/attachments/20210109/8317dbba/attachment-0002.png"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.kamailio.org/pipermail/sr-users/attachments/20210109/8317dbba/attachment-0002.png</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image.png<br>
Type: image/png<br>
Size: 6528 bytes<br>
Desc: image.png<br>
URL: <<a
href="http://lists.kamailio.org/pipermail/sr-users/attachments/20210109/8317dbba/attachment-0003.png"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.kamailio.org/pipermail/sr-users/attachments/20210109/8317dbba/attachment-0003.png</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
sr-users mailing list<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank"
moz-do-not-send="true">sr-users@lists.kamailio.org</a><br>
<a
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
<br>
------------------------------<br>
<br>
End of sr-users Digest, Vol 188, Issue 9<br>
****************************************<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Kamailio (SER) - Users Mailing List
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-abbreviated" href="http://www.asipto.com">www.asipto.com</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a>
Funding: <a class="moz-txt-link-freetext" href="https://www.paypal.me/dcmierla">https://www.paypal.me/dcmierla</a></pre>
</body>
</html>