1. Do you have an Amazon AMI image? A: Yes, you can find it at the bottom of the page at http://www.evostream.com/downloads 2. How does your load balancing work – is it your own load balancer or does it work with other load balancers like Amazon’s ELB? A: Our load balancer could be used in conjunction with Amazon’s ELB. Our balancer is a web service that essentially creates duplicate EMS servers, from the standpoint of source streams. Each of the balance servers will have the same live streams available and so you can use the ELB to distribute client connections among them. 3. Have you down any customization to work well with Amazon EC2? A: The EvoStream Media Server works very well in virtualized environments, Amazon EC2 included. We also run well in HP’s cloud. 4. Is the Evostream server also an RTSP proxy? A: Not in the strict sense of the word. The EMS can certainly receive RTSP traffic and redistribute it as RTSP, but it is not a proxy/redirect. 5. When you mention an RTSP HTTP proxy, could you explain? Does the Evostream Media Server serve up RTSP-over-HTTP, while connecting to the source RTSP server via UDP? A: No, the EvoStream Media Server will not behave as an HTTP proxy, but if one was used, the EMS can request streams from it. Our Media Server can connect to a proxy via HTTP and request RTSP streams from it, completing the proxy pass-through. 6. From an RTSP via UDP stream, can the Evostream Media Server serve up HLS and HDS? A: Yes 7. For our live viewing, how short a time delay can we get with HLS? A: You can squeeze it down to about 12 seconds or so. Anything lower than that gets into very small file sizes and you risk clients constantly downloading files. 8. What is the minimum latency we can achieve for a live stream with HDS? A: Same story as with HLS 9. How can we secure published live streams? A: We have the concept of stream Aliasing, which allows you to protect your content. The EvoStream Media Server also supports RTMPS and RTSP client authentication. It will also support Verimatrix for HLS streams in the next release. 10. With Push-In Authentication, can each live stream have a different authentication or do they all have the same? A: You can set multiple username/password combinations, but any of those can be used to push in a stream. If you want to completely sandbox customers you can run multiple instances of the EMS on a single computer (with a single license). You just have to set custom ports for each instance. For RTMP sources, we also provide “mount points” which require users to push streams to a private Target Stream Name. 11. Does your RTSP deliver support RTSP interleave (via TCP), as well as over UDP? A: Yes, the EMS supports RTSP with RTP over UDP and TCP as well as MPEG-TS transport over UDP and TCP 12. What do we get with the Technical Support for $75? What is the turnaround time? A: We can generally schedule time for support within a day or so. Support can be as involved as dialing into your computer and working through installation, configuration, integration, etc with you. 13. Where is your development done? A: San Diego, Bucharest and Manila 14. If we need additional customization, can you accommodate us (and what would be the turnaround time), or could we get a source code license so we could create the APIs we need? A: Yes, we regularly provide development services for our (typically OEM) customers. If the need arises we would work out a Statement of Work and the work would be done accordingly. Turnaround time depends entirely on the SOW, but we are typically able to start work within a week of SOW approval. However, that is, of course, subject to any current time-sensitive development projects.