[WebRTC android application]

[Anuroop Jesu]

Hi kiran,

I used below android sample.

https://webrtc.org/native-code/android/

1. To start with  I tested with default http://appr.tc sever and it worked
as is.

2. secondly I have below local sever setup which also works.

Used ubuntu machine with 16.04 LTS
http for ICE indicator.
coturn for turn server
apprtc locally hosted for session
and collider.
My turn server have ssl enabled and I am using same cert.pem in turn sever
and Android device.

Let me know if you need some more information.

Regards
Anuroop


On Sun, Jun 24, 2018, 10:47 PM Kiran ND <kiran at algorythma.com> wrote:

> Hi.,
>
> Firstly thank you for all the replies.. and my sincere apologies for late
> reply.
> As i was out of office i had very limited access to my mails.
>
> This is the current update of tryout for the reply mails.
>
> 1) --disable-ssl
> >> I checked for its usage in the checked in git code, but i have
> hardcoded in my codebase in using Strict-SSL to false.
> If my understanding is not right please correct me.
>
> @Anuroop
> 2)  Settings->security->Install Certificates
> >> I was betting on this to get the connected, but still i get same error
> i copied cert.pem file to my android device installed it manually before i
> launch my application.
> Still i get the same error. Am i missing something.
>
> @All,
> If there any android version of webrtc code sample point me to it. It
> would be of great help
> Any inputs would be highly appreciated.
>
> Thank you
>
> Cheers,
> Kiran
>
> On Mon, Jun 18, 2018 at 9:50 PM, Anuroop Jesu <jesuas at gmail.com> wrote:
>
>> Hi Kiran,
>>
>> I have similar issue only difference is I using non-gstreamer WebRTC
>> android application.
>> To resolve issue I installed user certificates under
>> Settings->security->Install Certificates from SD card.
>> I used turn server for signalling and installed certificates which I used
>> on turn server.
>>
>> Regards
>> Anuroop
>>
>> On Mon, Jun 18, 2018 at 3:37 AM, Matthew Waters <ystreet00 at gmail.com>
>> wrote:
>>
>>> 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:
>>>
>>>   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);
>>>
>>>
>>> Cheers
>>> -Matt
>>>
>>>
>>> On 18/06/18 18:42, Kiran ND wrote:
>>>
>>> Hi.,
>>>
>>> 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.
>>> >> I have disabled ssl-strict checking in soup_session_new_with
>>> options(), still it doesnt help me much.
>>>
>>> session = soup_session_new_with_options (SOUP_SESSION_SSL_STRICT, FALSE,                                         SOUP_SESSION_SSL_USE_SYSTEM_CA_FILE, TRUE,        //SOUP_SESSION_SSL_CA_FILE, "/etc/ssl/certs/ca-bundle.crt",                                         SOUP_SESSION_HTTPS_ALIASES, https_aliases, NULL);
>>>
>>> As of a few hours ago, there's a new option for this on both the
>>> client and the server.
>>> >> What's the new option that is available?
>>>
>>> Thank you.
>>>
>>> Regards,
>>> Kiran
>>>
>>> On Mon, Jun 18, 2018 at 1:27 PM, Nirbheek Chauhan <
>>> nirbheek.chauhan at gmail.com> wrote:
>>>
>>>> On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <ystreet00 at gmail.com>
>>>> wrote:
>>>> >
>>>> > 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.
>>>> >
>>>>
>>>> As of a few hours ago, there's a new option for this on both the
>>>> client and the server.
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> gstreamer-devel mailing list
>>> gstreamer-devel at lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20180624/4f2b6b4c/attachment-0001.html>