[WebRTC android application]

[kiran]

Hi all,

I am building an android webrtc application using gstreamer, i am using https://github.com/centricular/gstwebrtc-demos code as reference or starting version of my code.

I have got my code compiled and built but when i execute it i am executing it i get this below error message. ( Android application)
I could find which function fails but could not figure out what could be the reason for this.
Any inputs or pointers to address this error would be appreciated.

Error messages

06-16 16:04:01.833 11397-11553/org.algorythma.algostreamer I/GLib+stdout: Failed in Connecting to signalling server The server did not accept the WebSocket handshake. 

06-16 16:04:01.833 11397-11553/org.algorythma.algostreamer E/GLib+stderr: The server did not accept the WebSocket handshake.

Thank you

Regards,

Kiran

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Matthew Waters]

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.

Cheers
-Matt

On 18/06/18 15:22, Kiran ND wrote:

Hi all,

I am building an android webrtc application using gstreamer, i am using https://github.com/centricular/gstwebrtc-demos code as reference or starting version of my code.

I have got my code compiled and built but when i execute it i am executing it i get this below error message. ( Android application)
I could find which function fails but could not figure out what could be the reason for this.
Any inputs or pointers to address this error would be appreciated.

Error messages

06-16 16:04:01.833 11397-11553/org.algorythma.algostreamer I/GLib+stdout: Failed in Connecting to signalling server The server did not accept the WebSocket handshake. 

06-16 16:04:01.833 11397-11553/org.algorythma.algostreamer E/GLib+stderr: The server did not accept the WebSocket handshake.

Thank you

Regards,

Kiran

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nirbheek Chauhan]

On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <[hidden email]> 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
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[kiran]

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 <[hidden email]> wrote:

On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <[hidden email]> 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
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nirbheek Chauhan]

On Mon, Jun 18, 2018 at 2:12 PM Kiran ND <[hidden email]> wrote:
> 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?
>

Running with --help will always tell you what options are available.
It's --disable-ssl.
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Matthew Waters]

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 <[hidden email]> wrote:

On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <[hidden email]> 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
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Jesu Anuroop Suresh]

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.

On Mon, Jun 18, 2018 at 3:37 AM, Matthew Waters <[hidden email]> 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 <[hidden email]> wrote:

On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <[hidden email]> 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
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[kiran]

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 <[hidden email]> 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.

On Mon, Jun 18, 2018 at 3:37 AM, Matthew Waters <[hidden email]> 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 <[hidden email]> wrote:

On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <[hidden email]> 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
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Jesu Anuroop Suresh]

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 <[hidden email]> 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 <[hidden email]> 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.

On Mon, Jun 18, 2018 at 3:37 AM, Matthew Waters <[hidden email]> 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 <[hidden email]> wrote:

On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <[hidden email]> 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
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[kiran]

Thanks a lot Anuroop.

Will update you soon..

On Mon, Jun 25, 2018 at 11:26 AM, Anuroop Jesu <[hidden email]> wrote:

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 <[hidden email]> 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 <[hidden email]> 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.

On Mon, Jun 18, 2018 at 3:37 AM, Matthew Waters <[hidden email]> 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 <[hidden email]> wrote:

On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters <[hidden email]> 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
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel