Revision Revision Revision Revision

Date
Revision

History
18 okt. 2012
v1.2
Version Comment Date
v1.0 Initial release 26 jan. 2011
v1.1 Added port requirements 1 jun. 2012
v1.2 Added google Maps 18 okt. 2012
Server specifications Server specifications

Platform
Memory
Hardware
Processing power
Storage
requirements
Network bandwidth
incoming
Network bandwith
outgoing
Network ports
zepcam stream
Network ports
viewers
User Interface
Streaming
capabilities
Geo Maps
Linux, 64bit intel (x64)
4Gb for 10 simultaneous zepcams; 8Gb for 20 simultaneous zepcams;
16Gb for 50 simultaneous zepcams.
Dedicated or virtualized. Larger deployments prefer dedicated server
due to realtime processing requirements.
10% per core per zepcam.
1 zepcam, 500kbit, 4 hours per day streaming, 2 months retention:
60Gbyte.
Simultaneous zepcam bandwith + overhead http requests for viewers
Simultaneous viewers + zepcam bandwith * 4. Motion jpeg output
requires approximately 4x more bandwith than H264.
TCP/IP + UDP 1194; TCP/IP 12945 (reachable from internet when
streaming over public network)
TCP/IP ports 80 and 1935 .
Via web interface or dedicated on monitor
RTMP (Flash), Transport Stream (mpeg2+h264 video+audio), iOS http
segmented, jpeg, motion-jpeg.
Internet connection required by viewer for google Maps integration.