Configuration manual for 2N IP intercoms
•
•
•
To pair a user with a mobile device, use the user's page in the intercom phone book. Physically,
you can pair a user locally using the USB Bluetooth module connected to your PC or remotely
using an integrated Bluetooth module. The results of both the pairing methods are the same.
The following data is transmitted to a mobile device for pairing:
Location identifier
Location encryption key
User Auth ID
Encryption Key for Pairing
An encryption key other than that used for communication after pairing is used in the pairing
mode for security reasons. This key is generated automatically upon the intercom first launch
and can be re-generated any time later.
Encryption Key Administration
The intercom can keep up to 4 valid encryption keys: 1 primary and up to 3 secondary ones. A
mobile device can use any of the 4 keys for communication encryption. The encryption keys are
fully controlled by the system administrator. It is recommended that the encryption keys should
be periodically updated for security reasons, especially in the event of a mobile device loss or
intercom configuration leak.
The primary key can be re-generated any time. Thus, the original primary key becomes the first
secondary key, the first secondary key becomes the second secondary key and so on. Secondary
keys can be deleted any time.
When a key is deleted, the 2NMobile Keyusers that still use this key will not be able to
authenticate themselves unless they have updated the encryption keys in their mobile devices
before deletion. The mobile device keys are updated at every use of the 2NMobile
Keyapplication.
•
Note
The encryption keys are generated automatically upon the intercom first launch
and saved into the intercom configuration file. We recommend you to re-generate
the encryption keys manually before the first use to enhance security.
To Next Page
Loading...
Need help?
General
