Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-3816

FIWARE.Request.Tech.Data.Stream-oriented.CannotGetIntanceWorking

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      Hi,

      I have been fighting with this for a week now. The task is simple I want to
      install kurento 6.0 on my ubuntu VM and install/run the JS tutorials.

      This is what I did:

      1. Launched a new "Ubuntu Server 14.04.1 (x64)" VM
      ​(running in "Lannion 2" if that makes any diffrence) ​
      on my fiware/filab account and opened all TCP and UDP ports for it.
      2. Followed this http://www.kurento.org/docs/6.0.0/installation_guide.html
      to install KMS6 (also activated STUN)
      3. Followed this
      http://www.kurento.org/docs/6.0.0/tutorials/js/tutorial-1-helloworld.html
      to install helloworld tutorial
      4. When I go to http://IP:8080/ and hit "start", camera starts but I see
      only the "local stream"

      Also tried to do the above on a local server, but no luck also.

      Any idea what is going on, I followed the basic steps 1-4, and I do not
      understand why the example does not work especially that I do not get any
      error message during the whole install process.

      Thanks a lot,

      Hichem.

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

      [Created via e-mail received from: Hichem Boudali <hichem.boudali@gmail.com>]

      1. signature.asc
        0.2 kB
        Daniele Santoro

        Activity

        Hide
        danieles Daniele Santoro added a comment -

        Dear I’ve forwarded your request to the second level support.

        Best,
        Daniele

        _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fi-ware.org
        https://lists.fi-ware.org/listinfo/fiware-lab-help

        Show
        danieles Daniele Santoro added a comment - Dear I’ve forwarded your request to the second level support. Best, Daniele _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
        Hide
        llopez NaevaTeC Development Team added a comment -

        We have found a problem that may be causing your issue. Google has modified the IP of several of their public STUN servers. Due to this, the default STUN server configuration used by KMS is not working. This may be causing KMS instances running behind OpenStack NAT to fail in its default configuration (note that the FIWARE Lab runs on top of OpenStack).

        To solve this issue, please, do the following:

        Edit this file
        /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini

        Replace these lines:
        ; stunServerAddress=77.72.174.167 ; Only IP address are supported
        ; stunServerPort=3478

        With this

        stunServerAddress=64.233.184.127
        stunServerPort=19302

        IMPORTANT: remove the "; Only IP address are supported" at the end of the stunServerAddress config key, so that the lines are exacly as specified above.

        As a final checking step, and as a diagnosins tool, you can validate if a STUN server is working using this on-line tool:
        http://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/

        Show
        llopez NaevaTeC Development Team added a comment - We have found a problem that may be causing your issue. Google has modified the IP of several of their public STUN servers. Due to this, the default STUN server configuration used by KMS is not working. This may be causing KMS instances running behind OpenStack NAT to fail in its default configuration (note that the FIWARE Lab runs on top of OpenStack). To solve this issue, please, do the following: Edit this file /etc/kurento/modules/kurento/WebRtcEndpoint.conf.ini Replace these lines: ; stunServerAddress=77.72.174.167 ; Only IP address are supported ; stunServerPort=3478 With this stunServerAddress=64.233.184.127 stunServerPort=19302 IMPORTANT: remove the "; Only IP address are supported" at the end of the stunServerAddress config key, so that the lines are exacly as specified above. As a final checking step, and as a diagnosins tool, you can validate if a STUN server is working using this on-line tool: http://webrtc.github.io/samples/src/content/peerconnection/trickle-ice/
        Hide
        fw.ext.user FW External User added a comment -

        Hi,

        I think it is a general problem with fiware kurento instances.

        Tried http://kurento.lab.fiware.org:8081/ and also I see no remote stream.

        Could you have a look at this because I also have a Kurento instance on
        filab and it is not working for a few days now?

        Hichem.

        On 16 August 2015 at 20:00, Daniele Santoro <daniele.santoro@create-net.org>

        _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fi-ware.org
        https://lists.fi-ware.org/listinfo/fiware-lab-help

        Show
        fw.ext.user FW External User added a comment - Hi, I think it is a general problem with fiware kurento instances. Tried http://kurento.lab.fiware.org:8081/ and also I see no remote stream. Could you have a look at this because I also have a Kurento instance on filab and it is not working for a few days now? Hichem. On 16 August 2015 at 20:00, Daniele Santoro <daniele.santoro@create-net.org> _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
        Hide
        llopez NaevaTeC Development Team added a comment -

        We know about those problems and we are figuring out how to instantiate our very own STUN server in the FILAB and not be depending on Google STUN servers, whose IPs are modified almos daily.

        Sorry for the inconveniences.

        Show
        llopez NaevaTeC Development Team added a comment - We know about those problems and we are figuring out how to instantiate our very own STUN server in the FILAB and not be depending on Google STUN servers, whose IPs are modified almos daily. Sorry for the inconveniences.

          People

          • Assignee:
            llopez NaevaTeC Development Team
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: