Failed by ICE keep alive occurs after updating to 5.0.3100

[ysk-i]

Hi,
I run WCS on AWS EC2 Ubuntu16.04.
After updating from 5.0.2874 to 5.0.3100, "Failed by ICE keep alive" occurs.
Is it necessary to change any configuration?

I'll send logs and flashphoner.properties.

 

[Max]

Hello
Try to disable firewall.
Make sure main UDP ports are open and reachable [31000-32000] by default.
https://flashphoner.com/docs/wcs5/w...l?additional_tools-ports_routing_checking.htm

 

[ysk-i]

Thank you for your reply.
I confirmed that my EC2 instance received packets from a client.
https://flashphoner.com/docs/wcs5/w...l?additional_tools-ports_routing_checking.htm

Firewall(ufw) has been disabled and UDP ports[31000-32000] are opened in the security group.

Ver.5.0.2874 had worked well. After updating to 5.0.3100 by the following, playstream failed.
'servicewebcallserver update'

 

[Max]

Hello
Please send access details to the server to support@flashphoner.com
We will check.

 

[ysk-i]

I have already sent access details with forum link at Thu, 10 May 2018 11:01:13 +0900.

 

[Max]

Hello
You had sent logs. We checked logs.
Now we would like to check it immediately on the server.

As an option please try to add setting:

stun_freshness_timeout=1000000000

to flashphoner.properties
and restart server
let us know if it helps

 

[Karan Bhansali]

hi,

I have the same issue, no it did not help

 

[Karan Bhansali]

hi,

I have the same issue, no it did not help

 

[Max]

Hello
Please provide ssh access to your server. We will check.
support@flashphoner.com

 

[ysk-i]

Hi,
stun_freshness_timeout=1000000000 did not work.

 

[Max]

Are you using any blockers?
As reported here:
https://forum.flashphoner.com/threads/ublock-on-chrome-trigger-failed-by-ice-keep-alive.11486/
"Failed by ICE keep alive" can be raised if blocker is used.

 

[Max]

Hello

We have recently checked AWS instance
1. Open AWS marketplace page.
https://aws.amazon.com/marketplace/pp/B01D1L5EAK
2. Subscribe in few clicks.
3. Make sure instance has started in Amazon EC2 - Instances
4. Connect to the instance over SSH.
5. Update instance.
service webcallserver update
6. WCS has been updated to the latest 3150.
7. Test Two Way Streaming example (works).
8. Test RTSP playback example (works).

Testing scope: Chrome 66, Windows 10, no blocker extensions.

 

[ysk-i]

Thank you for the information.
I created a new instance from the marketplace AMI, and I confirmed that RTSP playback from a public IP camera worked well.
However, when connecting to an IP camera via software VPN (SoftEther VPN) "Failed to connect to rtsp tream" occured.
(ping from the EC2 instance to the IP camera succeeded.)

I sent logs to logs@flashphoner.com

 

[Max]

Hello
Try

ip_local=0.0.0.0

in flashphoner.properties
It looks like RTSP is bound on non-VPN address and that's why it does not connect to the IP cam over VPN.

 

[Max]

I have the same issue, no it did not help

Hello Karan Bhansali
We have got access to your server.
However it seems you are trying to configure case SIP as RTMP.
If so, please create a new forum thread and describe your case there.

 

[ysk-i]

Thank you for your information.
I tried

ip_local=0.0.0.0

however, ip_local=0.0.0.0 was replaced with the EC2's local IP during WCS restarting.

 

[Max]

Hello
Yes. WCS automatically set ip_local to EC2 local address on AWS system.
To disable this behavior,
Edit file

/etc/init.d/webcallserver

Find and comment the following line:

check_amazon

Example:

#check_amazon

Then IP will not be changed during restart.

 

[ysk-i]

Thank you!
This works well on both of Amazon Linux and Ubuntu.

ip = {public IP of EC2}
ip_local = 0.0.0.0

 

[lalit]

I am facing same issue in RHEL 7.5
stun_freshness_timeout=1000000000 did not work.
It seems it is a bug in flashphoner that displays when run on a RHEL
I have running version 5.0.3406

 

[Max]

I am facing same issue in RHEL 7.5
stun_freshness_timeout=1000000000 did not work.
It seems it is a bug in flashphoner that displays when run on a RHEL
I have running version 5.0.3406

Hello
This thread is closed. Please create a new one.
I'm sure you have another issue cause.