| 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.
Typically, it is advised to run ISS Setup in the same subnet where the IP devices are running for security issues. |
|||
| 60 | Software | Q. All the services are installed, and IP devices are added/registered to ISS Admin service. Can I remotely configure the IP devices? or Upgrade the firmware? | 2015-07-06 |
|
A.
Use ISS Setup, and you can remotely configure the following devices:
You can upgrade the firmware of the following devices:
[1] Only supporting the setup of the ONVIF compatible parameters exposed by the ONVIF devices. |
|||
| 59 | Software | Q. How do I add/register services on Admin service? | 2015-07-06 |
|
A.
When you install ISS services[1] on one or more servers, ISS Setup wizard will ask for the connection information of the Admin service during installation. Using this information, each service will report itself to its Admin service. An admin user will have to register these services to be included in the ISS System. Use ISS Setup to do this. Launch ISS Setup, and login to the Admin service. Select Services icon and use + icon to register these services.
[1] except ISS Federation service |
|||
| 58 | Software | Q. What is the recommended server specification? | 2015-07-06 |
|
A.
It is recommended run the service on a dedicated server if possible. ISS Admin service does not use as much computing resources as other services. Typically you will be running ISS Admin service and ISS (Event) Monitoring service on one server. Please refer to the manual for the recommended server specifications. |
|||
| 57 | Software | Q. All ISS services[1] / IP devices / users will have to be registered to an ISS Admin service. So, in a way, ISS Admin defines a boundary of an ISS System. | 2015-07-06 |
|
A.
When an ISS service is launched, it reports itself to its ISS Admin service to download its configuration information as well as connection information of other ISS services. When you login to an ISS system with ISS Client, you are logging into ISS Admin service, and then your ISS Client software is granted access to different IP devices, or services. ISS Client downloads information about where to find, how to connect to different devices or services using the directory of the Admin service. ISS Admin service is a very crucial part of ISS System. If the Admin service is down, all ISS Clients will lose its connection immediately. Recording service will continue to recording IP video streams, but only for the IP video streams registered to itself because Recording service can not access Admin service that mediates Events from Monitoring service.
[1] except ISS Federation service |
|||
| 56 | Software | Q. What is the ISS Admin service? | 2015-07-06 |
|
A.
In an ISS System, you work with many IP devices, and then a group of ISS services that provide many different features and functions. You will use ISS Client to use ISS System. All of these services are configured using ISS Setup after logging into the ISS Admin service. Typically, you would want to limit which user groups can access these configurations using ISS Setup to change the recording schedule or event schedules. IP cameras/video encoders using ISS protocol and ISS compatible DVRs are supported in ISS Systems. Also, ONVIF and 3rd party cameras are supported by ISS Admin service. You can have only one ISS Admin service in one ISS System. No separate per channel License is required for ISS Admin service as long as you have an ISS Recording License. |
|||
| 55 | Software | Q. Default port information used in IDIS Solution Suite | 2015-07-06 |
|
A.
Federation service: 11000 Admin service: 11001 Recording service: 11002 Streaming service: 11003 Monitoring service: 11004 Backup service: 11005 Video Wall service: 11006 Video Analytic service: 11007 Upgrade service: 10011 Video Wall agent service: 12000 |
|||
| 54 | Video Recorder | Q. DirectIP NVRs with Dual FW copies in the NAND Flash memory and how it works | 2015-07-06 |
|
A.
DirectIP NVR keeps two copies of FW and NVR setup(configuration) images on its NAND memory. Usually its first copy is used for normal operation. Once in a while NAND Flash Memory may fail, causing the unit to fail to boot up properly to load the linux/NVR apps. When a DirectIP NVR detects 20 consecutive booting failures, it switches its active partition to the second copy to load the FW/setup properly. (It takes about 45sec for a full booting for DR-4/6100, DR-4/6200 series, so 20 rebooting will take about 15 min or so) First try pin hole reset and if the unit still continues to reboot, wait about 15 min or so. hope this helps |
|||
