Answers to the questions most frequently asked.Search our FAQ database to find andview listed articles relating to your questions.
Total 125 count ( 8/ 18 page)
Depending on the type of the license, you need to provide it to the corresponding server running its corresponding service. For example, Recording ch or (Live) Streaming ch/server licenses have to be provided to the server running ISS Admin service. for Backup ch license, you provide it to each Backup server.
There are 3 different groups of licenses available for ISS v1.7.0.
Recording ch license
(Live) Streaming ch license
(Live) Streaming server license
Backup ch license
Federation ch license
 Typically, you will be plugging the wibu key license to the server running the corresponding service.
Wibu key is a USB license key that comes with ISS. You always need to have the wibu key plugged in the server running its corresponding service(s) at all time, or else, ISS System will stop working immediately.
Yes, but the network bandwidth and network delay overhead on the VPN may become a problem. It is advised to isolate IP video stream traffic within one subnet as much as possible, and limit VPN access to ISS client software for casual use only.
ISS system typically would have many mega pixel cameras. If you need to access ISS system from WAN side, there are a few things that you need to understand:
IP video stream isolation
install all IP devices and services on one Gb LAN
so that all recording traffic is isolated in one Gb LAN
for ISS Client access, you may want to use Dynamic MultiStream Control or Motion Adpative Transmission (MAT) feature if your IP camera supports it to reduce the Live watch network traffic for the IP cameras/video encoders supporting these features.
External IP Address/port setup
you have to use ISS Service Manager on each server to configure External IP address for each service.
refer to ISS Service Manager section to find out how to do this
other ISS services or ISS Clients will use these external IP address settings if they are connecting from WAN side of the NAT router
Port forwarding is required for the followings:
Admin service (TCP 11001): for login and to get connection information for the registered ISS services and devices
Recording service(s) (TCP 11002): to access the recorded video. if you have multiple Recording services, you will have to use a different port for each service, and forward the corresponding port respectively
(Live) Streaming service (TCP 11003): to subscribe to live video streams. the target devices have to be configured to use Streaming service. If you have multiple Streaming services, then you have to use a different port for each service, and forward the corresponding port respectively
Monitoring service (TCP 11004): to subscribe to events, required for all event related operations in ISS Client such as Event spot, Map, Event handling, etc
Video Analytics service (TCP 11007): to subscribe VA events. Typically, you do not need to forward Video Analytics service (TCP 11007) port because only ISS (Event) Monitoring service needs to access VA services and they are installed in the same subnet.
Backup service(s) (TCP 11005): to access back up video. if you have multiple Backup services, you will have to use a different port for each service, and forward the corresponding port respectively
Federation service(s) (TCP 11001): for login and to get connection information for the registered ISS systems
 You can use ISS Client to switch between different IP video streams for different layout automatically by assigning different video profile for different IP video streams. Your IP camera/video encoder must support this feature. Check ISS Client->Preferences->Video Enhancement section to enable it.
 This is an IP camera/video encoder feature. IP camera/video encoders can be set to decrease the frame rate (image per second:ips) if they sense there be no video motion detected in the scene.
It is strongly recommended that you use LAN environment with Gigabit network for all your ISS system. If you use 100Mbps network, you can only have a handful number of IP cameras.
For example, 2MP H.264 real time (30ips) IP video stream in can reach upto 4~12Mbps. If you are recording 10 of them, and trying to do live monitoring, 100Mbps would be not be enough bandwidth.
Please refer to the manual for the specifications. The general rule of thumb is
● (Live) Streaming service uses a lot of bandwidth and CPU resources
● Video Analytics service uses a lot of CPU/Memory resources
● Admin or (Event) Monitoring services are moderately resource demanding
● Recording services require high speed storages
● PCs to run ISS Client software need to have a good VGA card, and CPU to decode multiple streams of IP video streams
It really depends on your budget. ISS System is very flexible in terms of where to install different services. Ideally, you may want to have one server run only one service. Typically, you will run Admin/(Event) Monitoring services on one server, and Recording, (Live) Streaming and VA services on three separate servers respectively.
But if your system is 32ch max, you may run all the services: Admin, Monitoring, Recording, Streaming on one server, and VA services on another server. VA service takes a lot of CPU resources. If you are installing multiple services on one PC server, such as (Live) Streaming service and Recording service on the same PC server, you need to assign different (RTP) incoming port ranges for them. Refer to Incoming port range in the glossaries.
 4 core CPU can handle upto 8ch in VA service