Search results

  1. F

    Licensing issue via web proxy

    Thanks, this solved our problem. But oh boy, you need to make it easier to set. There are proxy settings in the flashphoner.properties file, why not just use that for all proxy connections?
  2. F

    Licensing issue via web proxy

    I have run tcpdump (filtering only port 443 and 8181) and something (I would assume WCS) is trying to access my.flashphoner.com (52.57.65.20) via port 443, where it should actually be making a connection to an IP on port 8181 (the proxy). I have emailed the logs.
  3. F

    Licensing issue via web proxy

    Because the site where the WCS server is installed is behind a web proxy we had to edit the file /usr/local/FlashphonerWebCallServer/bin/proxy.sh We then managed to activate our license (Web Call Server Monthly Subscription) via /usr/local/FlashphonerWebCallServer/bin/activation.sh However...
  4. F

    Problem connecting to camera via RTSP

    No, I did not change flags. At least not before we had issues. But someone could have, who knows.
  5. F

    Problem connecting to camera via RTSP

    Problem solved: on chrome://flags I simply clicked "Reset all to default" Would love to know what flag caused it...
  6. F

    Problem connecting to camera via RTSP

    We are in a very restrictive environment and we cannot use flash (or at least we cannot update it so that it will work) We solved the whole RTSP issue by setting the following properties: ip =10.196.204.52 ip_local =0.0.0.0 Setting ip_local to 0.0.0.0 makes WCS not bind sockets to a specific...
  7. F

    Supported Windows OS for WebRTC

    What is the minimum versions of Windows and Google Chrome (or firefox) that will display WebRTC using h264 and VP8 and encodings? I.e. do you have a list (or matrix) of supported platforms for WebRTC video feeds? e.g. chould we expect to have a WebRTC feed to display in Windows Server 2012 R2...
  8. F

    Problem connecting to camera via RTSP

    Also, when the server will be used it would be used from machines on 10.196.204.0/24 (without any card on 14.196.202.0/24). So it kind of does not make sense to have flashphoner (only) bind to 14.196.202.52, because only the cameras are on 14.196.202.0/24. The "local" network is seen as...
  9. F

    Problem connecting to camera via RTSP

    that made the RTSP work, but wont stream the feed to the browser. Your demo app actually says "PLAYING" this time round, but no video: The image grab above (where we loaded the demo app) is on a machine also with 2 network cards: 10.196.204.35/24 (def gw 10.196.204.1) 14.196.202.50/24 (no gw)...
  10. F

    Problem connecting to camera via RTSP

    Here is the codec information: I have done a tcpdump (only of the second network card where the camera is located and only of IP 14.196.202.21), and I sent it to logs@flashphoner.com We probably should note that we have 2 interfaces: 10.196.204.52/24 (def gw 10.196.204.1) 14.196.202.52/24...
  11. F

    Problem connecting to camera via RTSP

    We having trouble connecting to an RTSP feed from a camera (which we want to stream to a web page via WebRTC). We get the following in flashphoner.log: The RTSP feed definitely works, because if we use VLC, it plays the video feed from the same RTSP URL We can also telnet to the camera's RTSP...
  12. F

    Web Call Server apt-get

    Is there any published package (on some repository, if not the default) that we can install Web Call Server via apt-get in linux (Ubuntu)?
  13. F

    Release notes

    Where do we get your latest release notes. I'v tried http://docs.flashphoner.com/display/WCS/Release+notes (via Google) but it gives a "Service Temporarily Unavailable", but it has been doing it for weeks now.
Top