FAQ

TOTAL 143 COUNT
73 Software Q. Can I use ISS systems on VPN? 2015-07-06
A.

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.


72 Software Q. Can I use NAT routers and WAN connection in ISS system? 2015-07-06
A.

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[1] or Motion Adpative Transmission (MAT)[2] feature if your IP camera supports it to reduce the Live watch network traffic for the IP cameras/video encoders supporting these features.

  • NAT traversal

    • 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




 

[1] 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.

 

[2] 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.

71 Software Q. What about Network environment for ISS? 2015-07-06
A.

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.


70 Software Q. What about server specifications for ISS service and client software? 2015-07-06
A.

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


69 Software Q. Where do I install each ISS service? 2015-07-06
A.

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[1]. 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.

 

 


 

[1]  4 core CPU can handle upto 8ch in VA service


68 Software Q. What Port does Admin service use? and what about NAT traversal? 2015-07-06
A.

ISS Admin service uses TCP 11001 port. If the service is behind a NAT router, you need to port forward TCP 11001 on the router, so that ISS Client and other services can connect to it.

You can configure this port number on the server running the service using ISS Service Manager.


67 Software Q. What happens if ISS Admin service crashes? 2015-07-06
A.

All ISS client software will stop working.

(Event) Monitoring, (Live) Streaming, and VA services will stop working. Backup service will stop working. Federation services will not be able to work with the ISS System with its Admin service crashed.

However, Recording service will continue to work, but it will be able to record Event related IP video streams only for the IP devices registered to itself only. It is because, for cross Recording service boundary event associated recording, IP camera events are collected by (Event) Monitoring service and then routed through Admin service to the other Recording service. This can not be done because Admin service is crashed.


66 Software Q. What happens if ISS Admin service crashes? 2015-07-06
A.

All ISS client software will stop working.

(Event) Monitoring, (Live) Streaming, and VA services will stop working. Backup service will stop working. Federation services will not be able to work with the ISS System with its Admin service crashed.

However, Recording service will continue to work, but it will be able to record Event related IP video streams only for the IP devices registered to itself only. It is because, for cross Recording service boundary event associated recording, IP camera events are collected by (Event) Monitoring service and then routed through Admin service to the other Recording service. This can not be done because Admin service is crashed.


65 Software Q. What happens when I install more than one ISS Admin service? 2015-07-06
A.

Nothing. You are creating a new ISS system. You will need to have a new ISS license, or it will be running in demo mode. You maybe able to register IP devices, but recording may not work. Because if an IP camera is registered to two different ISS Systems, Recording may not work properly with IP cameras using ISS protocol because two ISS Systems will be competing to establish a recording session with the IP camera. IP cameras using ISS protocol allow only one recording connection session. The Recording service that establishes the recording connection to the IP cameras will keep the recording session. The other Recording service will keep trying to connect to the IP cameras, and fail.


64 Software Q. What happens when I uninstall ISS Admin service? 2015-07-06
A. Don’t do it. You will lose everything until you restore the iexp Service Database file to restore all the services, and device list.