FAQ

TOTAL 145 COUNT
75 Software Q. Where do I plug in Wibu key? 2015-07-06
A.

Depending on the type of the license, you need to provide it to the corresponding server running its corresponding service[1]. 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.

  • Admin group

    • Recording ch license

    • (Live) Streaming ch license

    • (Live) Streaming server license

  • Backup group

    • Backup ch license

  • Federation group

    • Federation[1] ch license

 

 


 

[1] Typically, you will be plugging the wibu key license to the server running the corresponding service.


74 Software Q. What is Wibu Key? 2015-07-06
A.

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.

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.
63 Software Q. What happens when I delete a registered service from Admin service? 2015-07-06
A. All other services will be decommissioned immediately. For example, if it was a Recording service, recording will be stopped immediately, and ISS Client won’t be able to access the recorded video on the decommissioned Recording service. The recorded data will be preserved in the decommissioned Recording service. If you have a backup of iexp file, you may be able to regain the access to the recorded video, you need to re-register it to the Admin service, and then reload iexp file to it.
62 Software Q. All the services are installed, and registered to Admin service, how do I configure them? 2015-07-06
A.

Use ISS Setup,

    Login to the Admin service with a user account that is a member of a group with proper Setup authorities like ISS service setup and ISS schedule setup

    Select Services icon to see all the registered services.

    Double click a service or use [/] edit icon to configure the selected service

Typically, you will be first adding/registering IP devices, assigning them to different services, and  then configuring the services, such as setting up Storages for Recording service, configuring VA parameters, etc.

Refer to each Service section for further service related details.


61 Software Q. I can use ISS System without any problem, but I cannot remotely setup the IP devices. What is wrong? 2015-07-06
A.

If you are connecting to ISS Admin service behind a NAT router using ISS Setup, IP address scope issue may arise: IP devices and ISS Admin service are running in the same subnet behind the NAT router, but ISS Setup is connecting from the outside of the NAT router. In most of this case, the registered IP addresses of the IP devices are private IP addresses, and ISS Setup won’t be able to use the private IP addresses when it is connecting from the outside of the NAT router.

You can address this issue for IP cameras/video encoders using ISS protocol and ISS compatible DVRs/NVRs by using FEN and forwarding the corresponding ports. But when you have many different IP devices, even this approach is not manageable.

  • configure all IP cameras/video encoders using ISS protocol and ISS compatible DVRs/NVRs to use FEN

  • forward the admin port for each of them

  • register them to ISS Admin using FEN names

Typically, it is advised to run ISS Setup in the same subnet where the IP devices are running for security issues.