Search results

  1. M

    AWS Marketplace AMI for CDN and autoscaling

    Max, the marketplace AMI used Amazon Linux AMI 1 which is going to reach end of support. Also many packages are not available to install like coturn (which is available in Amazon linux 2 but not in Amazon Linux 1) https://aws.amazon.com/amazon-linux-ami/ Can you please update the Flashphoner...
  2. M

    AWS Marketplace AMI for CDN and autoscaling

    Thank you Max. I will check.
  3. M

    AWS Marketplace AMI for CDN and autoscaling

    Hi Max, With AWS Market place AMI, is that possible to change, delete and add REST API users and its password during launching instance. I mean in launch template userdata. https://docs.flashphoner.com/display/WCS52EN/AWS+load+balancer+with+auto+scale+quick+setup
  4. M

    HLS edge server not playing

    Yes Max.
  5. M

    I would like to get HSL url

    Hi Pitchaya, You can play the stream using HLS URL by following below format http://{SERVER_IP OR DOMAIN_NAME}}:8082/{streamname}/{streamName}.m3u8 SERVER_IP or DOMAIN_NAME is the server where the stream got published. Also check 8082 is allowed.
  6. M

    HLS edge server not playing

    But the edge server will show the active CDN routes once the stream is published in origin server. I mean when this REST call "rest-api/cdn/show_routes" is executed and the stream is published in origin server, even if no one tries to play the stream on edge that API call will show the stream...
  7. M

    HLS edge server not playing

    okay. Thank you Max. I have one more question, when a stream is published in origin server and what is the maximum time needed for edge server to retrieve that stream from origin? Will the edge server pull the stream immediately from origin server?
  8. M

    HLS edge server not playing

    okay. I am checking on that. Also is it possible to add multiple domains to whitelist in the flashphoner properties file. If it is not, can you add that feature because streaming will be played from various web apps, so adding new server for each web app will not be a good approach. Requesting...
  9. M

    HLS edge server not playing

    @Max I have another question. We have an android app where HLS stream can be played by the users. If the ACAO has to be set with domain name to whitelist, it will not work with mobile app. right? Is there any way we can do the same for mobile apps?
  10. M

    HLS edge server not playing

    You should add the following parameters to flashphoner.properties on HLS Edge servers behind load balancer hls_access_control_headers=Access-Control-Allow-Origin: http://load-balancer-domain:8081;Access-Control-Allow-Methods: GET, HEAD;Access-Control-Max-Age: 3000;Access-Control-Expose-Headers...
  11. M

    AWS Marketplace AMI for CDN and autoscaling

    Thanks for the update Max. Will check on that.
  12. M

    HLS edge server not playing

    Yeah. I fixed that. I hope that is not the issue with CDN connections. Sorry Max. I can't give SSH access due to privacy concerns. I will check with the steps you shared and come back to you again.
  13. M

    AWS Marketplace AMI for CDN and autoscaling

    Great Max. Thanks for the update. But you said in above thread that Marketplace AMI can't be used with autoscaling since there is some billing issues with that AMI. Is that fixed now?
  14. M

    Multiple Edge servers behind AWS LB not communicating

    Thanks Max. I fixed that.
  15. M

    HLS edge server not playing

    Thanks Max. Please check the config files below Origin server #server ip ip ={PUBLIC_IP} ip_local ={LOCAL_IP} #webrtc ports range media_port_from =31001 media_port_to =32000 #codecs codecs...
  16. M

    HLS edge server not playing

    I fixed the issue by updating to latest build but after update, WCS CDN failed to push streams from origin to edge servers. Any additional configurations is need to be done with the latest build? When I logged in as admin and ran "show cdn-nodes", it doesn't show the edge servers, same as in...
  17. M

    Multiple Edge servers behind AWS LB not communicating

    Thank you. I have already added what you said but still CORS issue happens where there are mutiple edge servers behind load balancer.
  18. M

    HLS edge server not playing

    I have already added like below in all edge servers hls_access_control_headers=Access-Control-Allow-Origin: *;Access-Control-Allow-Methods: GET, HEAD;Access-Control-Max-Age: 3000;Access-Control-Expose-Headers: Accept-Ranges, Content-Range, Content-Encoding, Content-Length Still CORS issue is...
  19. M

    Multiple Edge servers behind AWS LB not communicating

    @Max this issue is happening again. After enabling stickiness in load balancer, it worked for few weeks. But all of a sudden now, it is not working. Is there any configuration change happened?
  20. M

    HLS edge server not playing

    That issue got resolved by restarting the webcall server. But I am continuouslu getting below error 13:07:21,509 ERROR WCSAgent - API-ASYNC-pool-12-thread-3 ed6bef02-4c76-4680-8208-be4500c4324d Stream 32565-1594643557-764140 local failed 13:08:25,355 ERROR MuxDecoder -...
Top