FAQ

ISS Admin service provides the following services:

• License authentication

  • ISS Admin service authenticates licenses: Recording ch license, (Live) Streaming server/ch license.

  • check current license information using ISS Service Manager on the server running from the Admin service or use WibuKey Tester program on each server.

  • add License certificate using ISS Service Manager on the server running from the Admin service.

• Directory service of these services/devices/users,
  for example

  • connection information to services, like External IP address/port information

  • login information to the registered IP devices

• Management service of services/devices/users

  • registration of services/devices/users

  • service database management (backup/import)

  • configuration of services,
    for example,

    • storage setting/preparation of Recording services

    • recording schedule of IP cameras

    • event handling,

      • event act schedule, and target user

      • when to send out an email notification upon a specific event

      • configure Live Popup for a specific event

  • updating firmware of devices

  • set up users and groups

    • create/manage users and groups

    • grant different levels of access privileges to different user groups

    • grant access to certain IP cameras for a specific user group

    • create layout, sequence, map, etc

Please refer to the following site and user guide.

Site: http://www.idisglobal.com/support/bandwidth

User guide: T2. Network_bandwidth_and_storage_estimator document

You can estimate the HDD storage capacity and network bandwidth by adjusting the stream parameters of each camera after selecting the NVR and camera.

Please download the guiding document for our recording storage and network bandwidth estimator.

Please refer to the T3. How to upgrade the firmware of DirectIP NVR and camera document.

0: Striping without mirroring or parity

1 + 0: Striped set from a series of mirrored drives

5: Block-level striping with distributed parity

Please refer to the http://en.wikipedia.org/wiki/RAID site for detail information.

1. Recommended SFP module

-    Finisar, FTLF1318P3BTL, SFP 1.25G LX / Single Mode 1310nm 10km LC with DDM

-    Finisar, FTLF8519P3BNL, SFP 2.125G SX / Multi-Mode 850nm 500m LC with DDM

2. Compatible SFP module

-    Fottu, APS31123CDL20, SFP 1.25G LX / Single Mode 1310nm 20km LC with DDM

-    Fottu, APS85123CDL05, SFP 1.25G SX / Multi Mode 850nm 550m LC with DDM

-    Fottu, APSB35123CDL20, SFP 1.25G LX / Single Mode 1310nm (Tx) 20km LC with DDM Bi-Di Transceiver

-    Fottu, APSB53123CDL20, SFP 1.25G LX / Single Mode 1550nm (Tx) 20km LC with DDM Bi-Di Transceiver

• 1ch license for 1 IP camera

• 1ch license for 1, 1ch IP video encoder

• 1~4ch licenses for one 4ch IP video encoder, depending on how many analog cameras are using the service[1]

• 1~16ch licenses for 1 4/8/16ch IP video encoder, depending on how many analog cameras are using the service

[1] Note that this is different from Recording ch license

• 1ch license for 1 IP camera

• 1ch license for 1 1ch IP video encoder

• 4ch licenses for 1 4ch IP video encoder, regardless of how many analog cameras are using the service

• 1ch license for 1/4/8/16ch DVR/NVR

You can plug in up to 8 Wibu keys.

Depending on the type of 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 need to 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.

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 times, 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 megapixel cameras. If you need to access the ISS system from the 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 Adaptive 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 to VA events. Typically, you do not need to forward the 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 profiles 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.

It is strongly recommended that you use a LAN environment with the Gigabit network for all your ISS systems. If you use a 100Mbps network, you can only have a handful number of IP cameras.

For example, 2MP H.264 real-time (30ips) IP video stream can reach up to 4~12Mbps. If you are recording 10 of them and trying to do live monitoring, the 100Mbps bandwidth would not be enough.

It 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 running 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 service 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 the Incoming port range in the glossary.

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

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.