<div dir="auto"><div>Hi kiran,<div dir="auto"><br></div><div dir="auto">I used below android sample.</div><div dir="auto"><br></div><div dir="auto"><a href="https://webrtc.org/native-code/android/">https://webrtc.org/native-code/android/</a></div><div dir="auto"><br></div><div dir="auto">1. To start with I tested with default <a href="http://appr.tc">http://appr.tc</a> sever and it worked as is.</div><div dir="auto"><br></div><div dir="auto">2. secondly I have below local sever setup which also works.</div><div dir="auto"><br></div><div dir="auto">Used ubuntu machine with 16.04 LTS</div><div dir="auto">http for ICE indicator.</div><div dir="auto">coturn for turn server</div><div dir="auto">apprtc locally hosted for session</div><div dir="auto">and collider.</div><div dir="auto">My turn server have ssl enabled and I am using same cert.pem in turn sever and Android device.</div><div dir="auto"><br></div><div dir="auto">Let me know if you need some more information.</div><div dir="auto"><br></div><div dir="auto">Regards</div><div dir="auto">Anuroop </div><br><br><div class="gmail_quote"><div dir="ltr">On Sun, Jun 24, 2018, 10:47 PM Kiran ND <<a href="mailto:kiran@algorythma.com">kiran@algorythma.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi.,</div><div><br></div>Firstly thank you for all the replies.. and my sincere apologies for late reply. <div>As i was out of office i had very limited access to my mails.</div><div><br></div><div>This is the current update of tryout for the reply mails.<br></div><div><br></div><div><span style="font-size:12.8px">1) <span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">--disable-ssl</span></span></div><div><span style="font-size:12.8px"><span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">>> I checked for its usage in the checked in git code, but i have hardcoded in my codebase in using Strict-SSL to false.<br>If my understanding is not right please correct me.</span></span></div><div><span style="font-size:12.8px"><span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></span></div><div><span style="font-size:12.8px"><span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">@Anuroop </span></span></div><div><span style="font-size:12.8px"><span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">2) <span style="text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span> </span>Settings->security->Install Certificates</span></span></span></div><div><div>>> I was betting on this to get the connected, but still i get same error</div></div><div>i copied cert.pem file to my android device installed it manually before i launch my application.</div><div>Still i get the same error. Am i missing something.</div><div><br></div><div>@All,<br>If there any android version of webrtc code sample point me to it. It would be of great help</div><div>Any inputs would be highly appreciated.</div><div><br></div><div>Thank you</div><div><br></div><div>Cheers,</div><div>Kiran</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 18, 2018 at 9:50 PM, Anuroop Jesu <span dir="ltr"><<a href="mailto:jesuas@gmail.com" target="_blank" rel="noreferrer">jesuas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Kiran,</div><div><br></div><div>I have similar issue only difference is I using non-gstreamer WebRTC android application.</div><div>To resolve issue I installed user certificates under Settings->security->Install Certificates from SD card.</div><div></div><div>I used turn server for signalling and installed certificates which I used on turn server.<br></div><div class="gmail_extra"><br clear="all"><div><div class="m_-357306459127139460m_2371156150856533573gmail_signature" data-smartmail="gmail_signature"><div>Regards</div><span class="m_-357306459127139460HOEnZb"><font color="#888888"><div dir="ltr">Anuroop<br></div></font></span></div></div>
<br><div class="gmail_quote"><div><div class="m_-357306459127139460h5">On Mon, Jun 18, 2018 at 3:37 AM, Matthew Waters <span dir="ltr"><<a href="mailto:ystreet00@gmail.com" target="_blank" rel="noreferrer">ystreet00@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-357306459127139460h5">
<div text="#000000" bgcolor="#FFFFFF">
<div class="m_-357306459127139460m_2371156150856533573m_-595988538172921322moz-cite-prefix">In my musings with android, I also had
to use the set of bundled ca-certificates that the GStreamer
ndk-build machinery installs into the application like so:<br>
<pre> ca_certs = g_getenv("CA_CERTIFICATES");
g_assert (ca_certs != NULL);
g_print ("ca-certificates %s", ca_certs);
session = soup_session_new_with_options (SOUP_SESSION_SSL_STRICT, FALSE,
// SOUP_SESSION_SSL_USE_SYSTEM_CA_FILE, TRUE,
SOUP_SESSION_SSL_CA_FILE, ca_certs,
SOUP_SESSION_HTTPS_ALIASES, https_aliases, NULL);
</pre>
<br>
Cheers<br>
-Matt<div><div class="m_-357306459127139460m_2371156150856533573h5"><br>
<br>
On 18/06/18 18:42, Kiran ND wrote:<br>
</div></div></div><div><div class="m_-357306459127139460m_2371156150856533573h5">
<blockquote type="cite">
<div dir="ltr">Hi.,
<div><br>
</div>
<div><span style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">This
error usually means either you don't have certificates
installed correctly inside your app or you're attempting to
access a server that doesn't support https/wss and has the
necessary certificates setup. You can get around this
either installing the necessary ssl certificate chain for
your webrtc signalling server or disabling the ssl-strict
checking in the soup_session_new() function call.<br>
</span>>> I have disabled ssl-strict checking in
soup_session_new_with options(), still it doesnt help me much.<br>
<pre style="background-color:rgb(43,43,43);color:rgb(169,183,198);font-family:Menlo;font-size:9pt">session = soup_session_new_with_options (<span style="color:rgb(144,139,37)">SOUP_SESSION_SSL_STRICT</span><span style="color:rgb(204,120,50)">, </span><span style="color:rgb(144,139,37)">FALSE</span><span style="color:rgb(204,120,50)">,
</span><span style="color:rgb(204,120,50)"> </span><span style="color:rgb(144,139,37)">SOUP_SESSION_SSL_USE_SYSTEM_CA_FILE</span><span style="color:rgb(204,120,50)">, </span><span style="color:rgb(144,139,37)">TRUE</span><span style="color:rgb(204,120,50)">,
</span><span style="color:rgb(204,120,50)"> </span><span style="color:rgb(128,128,128)">//SOUP_SESSION_SSL_CA_FILE, "/etc/ssl/certs/ca-bundle.crt",
</span><span style="color:rgb(128,128,128)"> </span><span style="color:rgb(144,139,37)">SOUP_SESSION_HTTPS_ALIASES</span><span style="color:rgb(204,120,50)">, </span>https_aliases<span style="color:rgb(204,120,50)">, </span><span style="color:rgb(144,139,37)">NULL</span>)<span style="color:rgb(204,120,50)">;</span></pre>
<span style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">As
of a few hours ago, there's a new option for this on both
the</span><br style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">
<span style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">client
and the server.</span><br class="m_-357306459127139460m_2371156150856533573m_-595988538172921322gmail-Apple-interchange-newline">
>> What's the new option that is available?</div>
<div><br>
</div>
<div>Thank you.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Kiran</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jun 18, 2018 at 1:27 PM,
Nirbheek Chauhan <span dir="ltr"><<a href="mailto:nirbheek.chauhan@gmail.com" target="_blank" rel="noreferrer">nirbheek.chauhan@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters
<<a href="mailto:ystreet00@gmail.com" target="_blank" rel="noreferrer">ystreet00@gmail.com</a>>
wrote:<br>
><br>
> This error usually means either you don't have
certificates installed correctly inside your app or you're
attempting to access a server that doesn't support
https/wss and has the necessary certificates setup. You
can get around this either installing the necessary ssl
certificate chain for your webrtc signalling server or
disabling the ssl-strict checking in the
soup_session_new() function call.<br>
><br>
<br>
</span>As of a few hours ago, there's a new option for this
on both the<br>
client and the server.<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<p><br>
</p>
</div></div></div>
<br></div></div><span>_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">gstreamer-devel@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<br></span></blockquote></div><br></div></div>
</blockquote></div><br></div>
</blockquote></div></div></div>