1.  After logging in, click on ‘My Profile’ in the upper right corner.

2. Click on ‘Modify’ to enter the settings page.

3. Click on ‘Do you agree to receive email?’ to start receiving notification emails.

In the case of its IP Camera, you can check the Video/Audio output at the same time by entering the following RTSP command into the VNC player.
E.g.) rtsp://{ip address}:554/onvif/media?profile=Profile1

– If you want to test audio only, you can use the following RTSP command (H.265 Camera Only)
E.g.) rtsp://{ip address}:554/trackID=90
– If the audio is not heard in VNC, etc., check the Audio Track or Output device information setting in the Audio menu.

We noticed that his IDLA does not offer the DC-T6233HRXL as available for IDLA service.
I checked our IDLA and have the same issue. We have DC-D6233HRXL connected but it doesnt appear in the IDLA availability list.
 

A :
DC-T6233HRXL is VA Edge camera which support Line crossing, Loitering, Object detection.

IDLA does not support IDIS VA Edge camera.
If you want to use that camera o IDLA service,
It needs to change DC-T6233HRXL to DC-T3233HRXL.

it can be changed by firmware upgrade.

Beide functies zijn gebeurtenissen die optreden wanneer het scherm door iemand wordt bedekt. ​​
Het verschil tussen de twee functies is dat Video Blind geen Video Blind off-bericht genereert totdat de schermbedekking is opgelost,
Tempering zorgt voor aan- en uitzetten wanneer schermbedekkingen optreden, ongeacht of de schermbedekkingen zijn opgelost.

Yes, the camera’s own SD recording status is not displayed on the OSD.
The recording status OSD is displayed by referring to the recording status information sent by the device, but the camera does not deliver the information.

An additional IP camera can be connected to the LAN/POE OUT PORT of DV-1304-A, and POE is provided.
However, it is necessary to connect a DC 48V Adapter to use it.

Refer to the following for details on the power supply.

0. 0. DV-1304-A can be powered w/ two power sources
1. 1. when powered via PoE (802.3at class 4 25W)
=> when powered w/ PoE, only the DV-1304-A works and it will draw max 25W
=> the PoE power draw in the NVR is showing total. please ignore the per channel power consumption

2. 2.  when powered by DC 48V@1A on the DC power in terminal (48VDC@0.8A = 38.4W)
=> the PoE Out on DV-1304-A is only powered when DC power is used
=> it will draw max 1A and use about 38.4W for both DV-1304-A and PoE out
=> it can supply 48V@0.35A max on the port PSE (16.8W), so it’s about, 802.3af class3 (15.4 W max)

Make sure the time is synchronized on both devices and check “Using Onvif Option” if it’s available.

Yes. You can use the camera but please note that the support will be limited for umcompatible cameras.

[NVR] SMTP 503 Error

This error often reported an email account is provided by Google Gmail.

Go to Google account > Personal Setting > Untick Unknown Source Checkbox.

A. In general, setup should be done 3 sides to use a network keyboard.

1. Keyboard local side : Device setting page from IDIS Discovery Tool : Register Server

2. ISS setup side : Register a network keyboard at Device tab.

3. ISS Client setup side : Turn on “Use Network Keyboard” option from Preferences.

A. The error message means that the device sessions are fully occupied.

Try to remove some sessions or close connections from Clients.

A. CGNAT means Carrier-grade NAT and this is used a solution for IP address exhaustion.

Lots of Internet Service Providers(ISP) implementing this device in 3 network infrastructure.

This could impact on the stability of FEN connection on your client devices.

In this case, call local ISP and ask them opt-out from CGNAT Pool. Implementing a FEN relay service also can be a solution for this issue.

A. Prepare a PC and connect HDMI encoder. Run the video on the PC and register the HDMI encoder to NVR or ISS.

A. The debug information is extracted based on the time of extraction.

After first export, based on the existing file, only the new debug is extracted.

Therefore, if there is no new information, it will have same size. On the contrary, if there is new, it extract new information only.

A. CGNAT means Carrier-grade NAT and this is used a solution for IP address exhaustion. Lots of Internet Service Providers(ISP) implementing this device in there network infrastructure.
This could impact on the stability of FEN connection on your client devices. In this case, call local ISP and ask them opt-out from CGNAT pool.

A. FEN relay server is a server that relays data from IDIS device to client software.

This often can overcome a limitation caused by complex network infrastructure.

However, additional configuration and decision have to made by customers.

A. There won’t be problem in the snow-covered image.

However, if there is a snowman or a snowy, it can cause misrecognized problems.

A. No, IDIS Mobile Plus doesn’t support Playback Audio yet.

A. Because the status is notified to the FEN server every 3 minutes, the connection is maintained.

A. When installing and operating ISS on a cloud server such as Azure, the basic h/w information of the server could be changed, [Cloud authentication method] must be used for the license registration method.
If customer uses the license type, ISS is designed to accept and update the authentication method from the cloud server from time to time to maintain License authentication.

To do this, the server must always be connected to the Internet.

A : Yes, they can use the same login information, if one channel is just created on ISS, one of the apps is able to be registered,
But another will be failed to register, because the channel will be full.

In this case, the one channel for app2 needs to be created.

A : first of all, It requires IDIS Mobile camera channel on ISS in advance, and then the Mobile camera accesses Admin service.
Then, the image traffic flows to Mobile Camera => ISS Mobile service => ISS Streaming service => Live view or ISS Recording service

A : for this, Admin, Streaming, Monitoring, Mobile service must be installed. And Recording service is also required for the recording.

A.

In the past, you could select which interface (LAN, RS232, 485, etc.) to use in the Text-In setting within the Event, but in the recently released new firmware, this part has been organized and functionally separated.

Changes
– Add Device Type/Port settings to be used in TextIn in advance in “DEVICE->Connector” as shown below, and then
Changed the way to select the Connector to use in “Event->Text-In”.

Please visit “Technology Partners” page
https://www.idisglobal.com/index/techpartner

A: Go to IDIS Solution Suite Setup -> Device -> Select Device -> Open Tree menu -> Select Camera -> Edit Device -> Turn on Associated Audio Channel

The device must support audio.

A: Yes, the 2 camera models can record audio, and listen to audio from live monitoring.

Q. When I try to register the Mobile camera app to the ISS, it fails. Why?

A.

IDIS Mobile camera app is classified as 3rd party device license, not IDIS Device license according to company regulations.
Therefore, 3rd party device number must be added to the license as much as the number of mobile camera apps to be registered.

This is because in the TR-4216 products, a policy to apply weights to bitrate to reinforce image quality at low tips has been applied.

Yes. It is recorded as ‘Fan Error(CPU)’.

The event logs are stored in HDD, so there is no number limit.
However, if the recording data is overwritten due to HDD capacity, also the event logs for the overwritten recording are deleted.

Yes. When it inserted in IDIS Network Camera, it will be automatically formated in our filesystem.

Yes

IDIS Center for iHDP is a S/W to access the HDD of NVR frome a PC to enable playback Therefore, Complete data has to be stored in a single HDD.(RAID 1+0, 5, 6 store different parts of data in each HDDs)

Use RAID HDD playback through remote access from iRAS to NVR.

There is no priority, and if either works, it is synchronized immediately.

Both have same capacity (Up to 256GB)

If ‘Anti-flicker On/Off’ doesn’t solve it, you should find a value that improves in the following way.

Go to ‘Anti-flicker Off’ -> ‘Exposure Control’ -> ‘Manual’
And, Set Shuter speed Min and Max value the same and manually find a value that improves flicker by setting the value to a multiple of 60.
(ex. 1/60, 1/120

No, there is no way yet.

Without RTC battery, Camera returns to 1/1/1971 when rebooting.

PoE (IEEE 802.3at class 4) supported 8 ports, 50W
There are group limitations :
Port 1 ~ 4 : 37W
Port 5 ~ 8 : 37W

The guaranteed time is 1 week.

For 8-ports model, it supports upto 8 IEEE 802.3af and upto 2 IEEE 802.3at.

For 16-ports model, it supports upto 16 IEEE 802.3af and upto 4 IEEE 802.3at.

Frequent Power On/Off operations are difficult to recommend

No, you can’t use.

Up to 16

We provide ‘AE Target Gain’ function as ‘Auto Gain Control’
You can set ‘Camera Setup -> Video Tab -> Exposure -> AE Target Gain’

Users can generate the “Email” and “Callback” event when the SD card is in/out
“Camera Setup ➔ Event ➔ System Event ➔ Disk In/Out”

Since Person Match service uses recording(= Playback session) serssion of Recorder.
so, In ISS recording service, upto 10 session can be available,
In NVR side, upto 2 session is available.
however, If a Client is using the recording session of NVR, 1 Person match service is available.

No. Depending on your situation, you may want to Detach > Install on a different server. / However, since it is a cost issue, I would like to recommend installing it in the PM server as much as possible.

No, Recorded Footage mode does not use MariaDB

Yes, if Person Match is not set, IDLA is not stored in MariaDB.

Both services are using the same VA Engine(called IDLE), there is no difference in recognition rate, and the specification is the same as upto 50 object simultaneous monitoring. However, note that the optimal performance is upto 16ch.

Person Match Service Licenses
The Video Analytics (IDLA) and Person Match Services use and share the ISS VA license. If you are already using the IDLA, the PM service is provided as a free upgrade.

Even when adding multiple PM service in a single Admin Service, it is used as the total number of channels purchased.

As PM service is in Federation, the IDLA license for PM service should be included to Federation license,
As PM service is in Admin, the IDLA license for PM service should be included to Admin license.

Person Match Service at Federation service
Person Match is also available in Federation service.
As mentioned above, when performing PM search, data traffic increases instantaneously because the PM service directly accesses multiple recorders or recording services to retrieve and analyze data.
In other words, it should be used in a space with sufficient bandwidth of the network. In other words, if you need to install PM service in the location where Federation is installed, it is necessary to review beforehand whether the network bandwidth and latency are sufficient.
However, when building a system, you need to understand the operation method and data flow in order to build it correctly.
Case1: When FED (Federation) has a PM license
Case2: When ADM registered in FED has a PM license

Case1: When PM service is registered in FED
PM search can be done at ISS FED CLIENT. ISS FED CLIENT can perform PM search for all cameras.

However, if the network bandwidth between the recorder (ADM) and PM (FED) is insufficient due to the system structure, the search speed may be quite reduced, so please be careful.
For example, if the bandwidth between a bank’s ATM and the monitoring center is very limited, it can be a problem when performing PM search.
In this case, Case2: When ADM registered in FED has a PM license.
In this case, Federation should have IDLA(PM) license.
As many as IDLA(PM) license applied, user can search the number of channel(IP camera)

Case2 : When ADM registered in FED has a PM license
As above, if the bandwidth between ATM and monitoring center is low, Case 1 is not appropriate.
In this case, while building PM service on the ATM side, it is built on site to secure sufficient bandwidth for VA.

Note: In this case, PM search cannot be run for the camera of ATM2.
For PM service, PM serivce must be installed in the admin service.
In this case, Federation dose not need to have IDLA license, but Admin license should have it.
(With above diagram, ATM2 site cannot use Person match service, because there is no Person match service installed)

Q: I am monitoring real-time video over 144 channels by connecting 4 monitors with Intel i7 + Quadro P1000 (GPU) configuration.
By the way, up to the 2nd monitor is normal, but from the 3rd monitor, the video is cut off. Why is that and what should be done?

A:
1) Intel i7 CPU
+) i7 CPU also has a grade, but the general i7 has 4 cores (Quad Core).
From a multimedia data processing point of view, this is an intermediate specification.
+) CPU selection is very important in real-time monitoring operation of more than 144 channels (cameras) in a configuration of 4 monitors.
2) Quadro P1000 GPU
+) The P1000 has the advantages of low power and easy multi-monitor configuration, but it is a low-spec GPU.
+) It is a better GPU than the GPU used in development, so it is difficult to conclude that the current information is the cause of the issue.

** Issue identification
+) If the CPU occupancy exceeds 90% and the phenomenon is reproduced, there is a high probability that it is a CPU issue.
+) CPU usage is less than 85%, but if the phenomenon is reproduced, there is a high probability that it is a GPU or MEM (out of memory) issue.
In addition to +), it is necessary to review the overall operating environment (OS / CPU / MEM / GPU / Device Driver / Etc)

** check item
1) Check camera stream settings and dynamic multi-stream control configuration
2) Check the camera stream encoding codec (H.264)
+) H.264 has much less decoding load than H.265.
+) It is recommended to use the H.264 codec for the stream used for multi-channel monitoring.
3) Activating camera settings intelligent codec
4) Default value is recommended for Client S/W setting (Preference – Video Enhancement)
+) In a low-end GPU environment, it is necessary to check the phenomenon depending on whether High-Quality Downscaling is used.

This mode is almost the opposite of ‘Pre-Processed Footage mode’ in operation.
When PM service is executed, it directly accesses the recorder or Recording service, accesses the recorded data and performs analysis (IDLA).
Also, this mode can do PM search with any camera (the biggest difference from Pre-processed Footage mode)

Advantages :

‘Pre-Processed Footage mode’ costs a lot when building a service, but Recorded Footage mode doesn’t require IDLA VA service and MariaDB for pre-processed VA metadata like the above configuration. (In other words, the construction cost is lower than the Pre-Processed Footage mode.)
So, if the cost of H/W is burdened, you can use this mode.

Person Match / Pre-Processed Footage
Among those two modes, the one with the fastest search speed is Pre-Processed Footage. This function classifies objects in advance (pre-processing), stores them in a separate database server (MariaDB), and searches through PM service if necessary. It has the advantage of faster search speed compared to Recorded Footage mode.
Also, when PM service is running, it is good because the search session resource is not consumed because it connects to MariaDB instead of directly connecting to the recorder. Devices like NVR only have two search sessions, so if there are many users who use ISS playback at the same time, the search session of NVR full may occur and PM search of NVR may not be possible.

In summary, the advantages of Pre-Processed Footage are:
– Fast search speed
– It is suitable for the system environment that has the restriction of search session such as NVR or TVR.

However, this service also has its weakness.
– Increased cost: IDLA Server and MariaDB storage capacity are required because pre-processing is required using IDLA and DB is stored by building MariaDB. That incurs additional costs.
+ However, if you are a user who already uses IDLA, there is no cost issue. (You only need to add as much storage capacity as MariaDB)

– Restriction that only cameras analyzed through IDLA can be used:
+ Data analyzed in advance through IDLA are stored in MariaDB, and this data is used by PM service, so there is a limitation that only cameras analyzed through IDLA can be used. / There is a restriction that other cameras cannot use PM service.
+ But you have to think about this, there are some cameras all people must pass through. For example, building entrances, checkout counters.

Therefore, it is necessary to recognize the pros and cons of the function and introduce the most appropriate service to the customer.

There is an IDIS Deep Learning Engine called IDLE, and using it, we are providing an IDIS VA(Video Analytics) technology called IDLA.
This time, we would like to introduce another VA technology called Person Match, which is a type of IDLA.

IDIS Person Match (hereinafter, PM) is a function that VA directly finds the person you are looking for.
If you find the person you are looking for in the video and run PM search, you can easily find out when and where the person is.
In the days without PM technology, security officers or police officers had to manually search through numerous CCTV footage for a very long time to solve a case. But now they don’t have to.

This PM is a service belonging to ISS VA (IDLA), so IDLA license is used.
This also means that customers who already use IDLA can use PM service for free.

This IDIS PM service has two main modes.
– Person Match / Pre-Processed Footage
– Person Match / Recorded Footage mode

VA Dashboard is a graph that shows the trend of problem occurrences, which means it does not represent an exact value of the events.

In other words, rather than displaying the total number of events, events that have occurred during one minute are counted as Violation 1.
If all 23 mask violation events occur within 1 minute, VA Dashboard counts them as 1.

A customer can misunderstanding about the current interval time of 1 minute has been received, and we intend to reduce it to 10 seconds.
Then, a value similar to the customer’s intended result may be displayed.

I was able to change the camera IP settings in DirectIP 1.0 NVR.

However, please note that the IP setting function in the tool is not supported after moving to the DirectIP2.0 generation.

The reason why the customer guessed that it would be difficult to meet IK10 after checking the exterior material
It is likely that the judgment was made by looking at the plastic exterior parts.
The exterior plastic parts used in this product use a PC mixed material that can easily absorb shock, and the basic thickness of 3T is applied to prevent damage to ensure safety.

ISS has a Backup service module, you can use this service and back it up and store the NVR’s HDD separately as replacement HDDs.

– How to configure of ISS

1. Uncheck ‘Overwrite backup data when the disk is full’
When assign HDD storage on Backup service, ‘Overwrite backup data when the disk is full’ should be unchecked so that Overwrite feature stop.

2. Check ‘Notification of Disk Almost Full’ as 90%

3. When setting the backup for the first time, it is recommended to set “first / summary backup or event backup”.
This is due to the network throughput performance and h/w performance limitations of the Recorder.

4. If the HDD is full and needs replacement, as shown in the picture below,
Make a note of the last recorded date/time before replacement, and when you connect a new HDD and reconfigure backup, you can start recording from the time you wrote the note.

5. There is currently no function in ISS that gives an alarm when starting a new HDD recording.

– how it works 
+ please refer to Page. 263 on ISS v3.5 or higher version manual.
+ the traffic flows as below :
Camera(device) > Streaming service > RTP Streaming service > RTP Client

– how to connect to it 
+ RTSP URL rule of the RTP Streaming service is as follows:

rtsp://[RTP Streaming Service IP]:[rtsp port]/
idis?trackID=[device identifier number]&
streamID=[stream index]&audio=[0 or 1]

i.e :  rtsp://192.168.10.100:554/idis?camera=4&video=h264

– It uses the streaming service ?
+ Yes, so NVRs and cameras must be added to Streaming service

‘Optimization’ has two functions :

Optimization’ pre-tests whether the newly added HDD is appropriate for recording.

(+ set Buffer size, # of camera, etc)

If the result is pass, the newly HDD is appropriate for recording.

For example, if you set 32 cameras for optimization and it passes the pre-test, the HDD guarantees 32 recordings.
However, it doesn’t guarantee over 32 cameras. It may be possible or not.

If you set 48 channels for optimization and it passes, the HDD guarantees upto 48 cameras, so you can add 16 more cameras whenever you want.

Type 2 : X-frame method
Type 5 : LongGop & ROI method
(It is not written in the manual, so it is written as type 2,5 in the menu.)

Type 2 : Below 3 are the unit of the compression rate. The higher the compression rate means the higher the “loss compression” rate leads to lower the traffic. However, there may be a deterioration in image quality.
+ LOW
+ NORMAL
+ HIGH

Please check C:\IDR-system\temp folder

Common mistake is not setting the time properly. The server needs to communicate with Microsoft server, so the time needs to be set correctly.

This feature is to set the storing  period of VA data(e.g. people counting data).

They have nothingto do with HDD capacity, Recording ratio, HDD overwrite. Recording priorities are related to recording quality.

1. Event when full-time recording : Event recording quality

2. Panic recording when full-time recording : Panic recording quality

3. Panic recording when event-recording : Panic recording quality

4. Event when Panic recording : Panic recording quality

> There is no option to overwrite ‘Panic Recording’ at the end. Use ‘Recording data protection’ function.

There are “Stereographic”, “Equidistant”, “Orthogonal” projections generally.

IDIS Camera :

1. Panoramic Fisheye : Stereographic

2. Normal Lens : Equidstant

-DC-Y1514W : Equidstant

-DC-Y3C14WRX : Equidstant

-NC-Y6513RX : Equidstant

-NC-Y8C13WRX : Stereographic

-DC-Y6C16WRX : Equidstant

-DC-Y6516WRX : Equidstant

Here are two reasons :

1. To prevent diffuse reflection by top cover during night.

2. To prevent the top cover from entering the angle of view.

If UDP is not available when accessing UDP, it will pass through ‘Relay Server’. ‘Relay Server’ is in Korea and have capacity limitations, so, it lead to decline in speed.

When using ‘Port Forwarding’, it doesn’t pass through ‘Relay Server’ and directly connected between devices.(Speed Up)

We recommend ‘Port Forwarding’ when using FEN.

The IDIS camera stores the time information ever frame when recording.

If there is the time information delivered by RTSP, information is generated.
However, if not, the time information is generated based on the time when the RTSP frame arrives at the Client.

Yes, If HDD is full, it overwrites timelapse data on panic recording data.

However, Panic recording data can be maintained by using ‘recording data protection’ function.

Yes records forever. However, if overwrite is off, it stops panic recording when HDD is full.

Q. Example :

1. 09:00 ~ 21:00 : timelapse recording

2. 21:00 ~ 09:00 : event recording

In this case, is it possible to search only event recording when search 9/1 00:00:00 ~ 9/30 24:00:00 ?

A. Event log must remain when event is set in the recorder whether it is set ‘Timalapse recording’ or ‘Event recording’ or ‘No recording’.

Therefore, Search for daily time zones by specifying Scope in Event Search.

SAVM function is only for IDIS cameras, not 3rd party camera.

Camera supports SAVM and NVR just accesses camera to use SAVM.

Unlike NVR, TVI recorder cannot change the audio recording codec.

Only uses G.726(fixed).

Ex) TR-2504 : Playback speed as below.

Playback

– 120/100 ips@ CIF, 2CIF, D1, 960H(NTSC/PAL)
– 120/100 ips@ HD(30p/25p)
– 120/100 ips@ FHD(30p/25p)
– 72ips@ 3MP, 60 ips@ 4MP, 40 ips@ 5MP

Recording per ch ips

– Recording below 2m. – 30ips.
– 3M recording ips : 18ips
– 4M recording ips : 15ips.
– 5M recording ips : 10ips.

FHD playback means that 30ips per second is played per channel when played on a four-division screen. (total = 30ips * 4 = 120ips)

Likewise, 3M is recorded 18ips per ch, so playback at full speed at 72ips when it is four-division screen.(4M at 60ips, 5M at 40ips)

For example, “4ch 1080p synchronous playback” means that 2M camera will be played at full speed on a four-division screen on a 4CH recorder.

(But, It’s not ‘Synchronous Playback’, if there are other interference during playback such as iRAS watch/search connection, clip copy etc)

1. Description

This document guides how to access ISS WEB service from remote site

<Tested network diagram>

Remote PC access local ISS server by Web service

2. How to configure

#1. Install ISS with latest firmware

+ install ADM, MON, STR, WEB Service

+ and add devices(NVR, IPC..)

#2. Open ISS service manager and each services should set ‘External IP address’

+ the address of External IP is the Router’s uplink IP

+ at least, ADM, STR, WEB, (MON) service should be set.

#3. Go to Router setting,

Set Port forwarding as below service ports.

11001 ~ 11009 (ISS service port)

8080 (ISS Web service port)

#4. Run Chrome or IE and enther ‘<Router’s uplink:8080>

Then you can access ISS web and watch live view.

Note : if web service does not work, restart the service once and try again.

IS-1100 does not support SATA HDD. You must use an NLSAS TYPE HDD.

DirectIP 1.0 Camera and DV-2232 should be in the same network.
In some cases, DirectIP 1.0 cameras requires additional settings to use DV-2232 COVID-19 video analytics.
If you cannot see the VA working on the IDIS Center, please change camera protocol as DirectIP

If the PIR sensor is not working, please check your NVR is on a ‘Self-Guard’ mode.
PIR Sensor is working on ‘Self-Guard’ mode.

No, IDIS products only support FTP.

Device – Delivers information periodically every 3 minutes & as soon as a change happens
FEN – Update as soon as information is delivered

IDIS Camera Compatibility list to Millstone VMS can be found on the web site of Millstone systems as the below images show.

Go to Milestone Systems website, and find ‘Supported Devices.’

Click XProtect Corporate.

Type ‘IDIS’ and search.

[NVR / TVR(HD analog DVR)]

rtsp://user-id:password@<nvr-ip-address>:port/trackID=<camera-number>&streamID=<stream-number>

e.g) rtsp://admin:password@10.0.125.57:554/trackID=3&streamID=2

[Network Camera]

rtsp://ID:password@IP Address: RTSP Port/trackID=’Stream number’

* Default RTSP Port:554

The existing DirectIP 1.0 protocol has two modes, DirectIP mode, and IDIS mode, so you have to reboot the camera to change each mode.
DirectIP 2.0 protocol can take advantage of all the advantages of DirectIP mode and IDIS mode depending on whether accounts are created without rebooting in a single mode.

The most prominent difference between them is security.

DirectIP 1.0 uses MAC Address-based mutual authentication for convenient authentication without setting password.

DirectIP 2.0 has become more secure with Certificate-based mutual authentication. Now IP camera and NVR exchange and store respective certificates.

When a DirectIP 2.0 NVR re-establishes a connection with a paired IP camera, the authentication process begins with checking and comparing each other’s certificates to the stored certificates. If the certificates match, both devices are confirmed by each other, the communication session is established.

Please contact your local distributor or IDIS office where you bought IDIS products from.
We will guide you to find your password without losing any recorded data.

Please find the contact details for our offices from the link below.
https://www.idisglobal.com/index/contact

The existing DirectIP 1.0 protocol has two modes, DirectIP mode and IDIS mode. You have to reboot the camera to change each mode.
DirectIP 2.0 protocol is a unified form of two modes. Without rebooting, the protocol can take advantage of all the advantages of DirectIP mode and IDIS mode.

In DirectIP 2.0, a camera boots up as a DHCP client looking for a DHCP server for about 40 seconds. If no DHCP server is found, it starts up with a linked-local IP address.

By creating a user’s custom name (FEN name) simply from a DirectIP NVR, its device info and network parameters (including Device name, MAC address, IP address, port info, NAT type, product info etc.) are automatically registered in the DirectIP FEN server running in the cloud. The user is able to access the site remotely using this custom name instead of an IP address, as the FEN server keeps hold of the local device’s connection on the network even in a DHCP environment with dynamic changing IP.

FEN service uses UDP hole punching for NAT traversal to gather address information of two ends, a NVR and a remote client, and NAT type in a site where a NVR is or a remote client is should support UDP communication.

[NAT types supporting UDP communication]
– Open internet
– Cone types (Full cone, Restricted cone, Port restricted cone)

[NAT types not supporting UDP communication]
– UDP blocked
– Symmetric
– Symmetric UDP firewall

For audio detection, the device (ex. DirectIP camera) calculates the average power of audio signal that is transmitted for specific times (6.5 seconds).

If current audio signal’s power is much higher than the power threshold of audio signal (based on the average power of audio signal), then audio detection is enabled.

That is,

1. Gather audio signal for 6.5 seconds
2. Calculate the average power of audio signal
3. Compare current power of audio signal with the power threshold of audio signal
4. Decide whether audio is detected or not.

The threshold of power level is determined by the audio sensitivity level.

* Sensitivity level 1: two times (6dB) higher than the average power of audio signal

……..

* Sensitivity level 5: 1.2 times (1.6dB) higher than the average power of audio signal

Normally, NVRs or network switching hubs are PSEs (Power Sourcing Equipments) and have no consideration about the PoE and DC power because they generates the PoE power using DC power and have no collision between PoE and DC power.

However, cameras are PDs (Powered Devices) and should select one of PoE or DC power if both powers are supplied. So, if both PoE and DC power are supplied to the camera, the camera use DC power first, and send power status message to PSE via signal lines, then PSE recognizes that the camera use DC power and stop supplying PoE power to the camera.