Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Data
-
HD-Enabler:Kurento
Description
Please find my answers below...
<https://jira.fiware.org/browse/HELP-4970#>
Luis López Fernández
<https://jira.fiware.org/secure/ViewProfile.jspa?name=llopez> added a
comment - Yesterday
We cannot reproduce the issue in our facilities. For being able to track
the problem we need this information:
1. Where are you deploying Kurento? Is it in the FILAB? In which
flavour? If it is out of FILAB, please, provide detailed information on
the type of machine where you are deploying including type of CPU,
available memory and available HD.
It is a Softlayer's VM with 8Gb RAM, 2 x Intel Xeon CPU E5-2683 v3 at
2.00GHz, 100GB HD. It runs Ubuntu 14.04.3 LTS with latest updates applied.
2. Are you using a STUN or TURN server for Kurento? You can find this
information in the /etc/kurento/webrtcendpoint configuration files.
Please, share them with us.
Yes. We use our own STUN/TURN server implemented by way of
rfc5766-turn-server version 3.2.5.9.
3. Which browser are you using for both presenter and the viewer? Are
you using a STUN / TURN server at the browser-side?
I'm not specifically using a STUN/TURN server in the browser side
- Presenter is Firefox 41.0.2
- Viewer runs Chrome 46.0.2490.80
Best regards,
Alberto.
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Alberto Bambala Arbea <alberto.bambala@vento.tv>]
Activity
It has been re-opened as HELP-4970. I'm closing this issue.
We have performed extensive tests and we cannot reproduce the behaviour you describe under any use case (i.e. virtual infrastructure, phisical hardware, STUN, TURN or direct connectivity)
Without any further information, my guess is that the problem is coming from the Softlayer network. Perhaps it is doing something to the traffic (e.g. filtering or dropping packets) after the 18 minutes.
The only recommendation I can provide you is to deploy your application at the FILAB. It it fails overthere, we can debug it without problems. Otherwise, debuggin in Softlayer is not possible for us.
Best.
Hi Luis,
We finally narrowed the problem and we think that it is related somehow
to SoftLayer as you pointed in you email. We've being testing our app in
Filab several days now and Kurento didn't crash so far.
A ticket was opened in the SoftLayer's support system and their support
team is working on the case.
Thanks a lot for your assistance.
Kind regards,
Alberto.
We have performed extensive tests and we cannot reproduce the behaviour you describe under any use case (i.e. virtual infrastructure, phisical hardware, STUN, TURN or direct connectivity)
Without any further information, my guess is that the problem is coming from the Softlayer network. Perhaps it is doing something to the traffic (e.g. filtering or dropping packets) after the 18 minutes.
The only recommendation I can provide you is to deploy your application at the FILAB. It it fails overthere, we can debug it without problems. Otherwise, debuggin in Softlayer is not possible for us.
Best.