Answers to the questions most frequently asked.Search our FAQ database to find andview listed articles relating to your questions.
Total 117 count ( 8/ 17 page)
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.
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.
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.
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.