User administration
Back / Forward | Help / User
The users are managed in this screen.
The users can be granted diverse access rights.
The way in which the user accesses the HomeServer is determined:
Internet browser, client program, list request, WAP, via LAN or Internet etc.
To create a new user, switch to the window on the left titled "User".
Place the mouse pointer on the "User" directory in the directory tree.
Press the right mouse button.
A pulldown menu opens. Select "Create user".
Or "New" in the menu bar.

To allow for a better overview, you can also sort several users, e.g. that are to have the same access rights, into directories. Directories can be created like users.
Data
The access data of the user are indicated in this screen.
Designation
The name of the user is indicated here. This information is required in the HS Expert.
User name
The name of the user is indicated here. The user logs into the HomeServer with this name.
Password
The password of the user is indicated here. The user logs into the HomeServer with this password.
A random number generator suggests a combination of characters.
WAP password
The password of the user is indicated here. The user logs into the HomeServer via WAP with this password. Only numbers are permitted.
A random number generator suggests a combination of numbers.
Alias
The alias name of the user is indicated here. This name is displayed in the buddy list.
PIN validity (in secs.)
After requesting the PIN, this is then valid for the time set here.
Yes, the user can receive visual alarms.
A defined Visu page is moved to the front in case of an event. There is a command for this.
Camera direct access
Yes: The camera picture is called up directly by the camera. The camera picture must be able to be called up directly in the browser from the point of view of the user.
Attention: We recommend that you always select this option when available! This reduces the load to the HomeServer.
IP restriction
Every internal user can be assigned one/several IP address(es) or an IP address area. The addresses entered here restrict the access.
The restriction is set from the combination of the TCP-IP address and the network mask.
Only those devices that have this IP address or are from this IP address area have access under this user to the HomeServer.
We recommend that you activate (enable) this option when first putting into operation!.
Example of an address area: 192.0.0.0 and appropriate network mask.

The list is edited using the control knobs to the right of it: Insert, Delete, Change/Edit
Restrict internal access to the following IP addresses
Yes: Access is only allowed via the following addresses.
No: Access is unrestricted. Access can be made via any TCP-IP address. Any restrictive entries in the list are not taken into consideration.
PIN request
The number that a user can use to request the PIN is entered in this screen.
For more information on this, refer to Portal procedure
Several numbers can be entered in this list
The user can request his PIN via these numbers.
Attention: This procedure can also be enabled on every telephone number.
This option can be selected under Project/PIN.
Entries made by the user always have priority when the HomeServer recognizes the number! It then only goes online for this number (if it is set here).

The list is edited using the control knobs to the right of it: Insert, Delete, Change/Edit.
Establish internet connection
Yes: The HomeServer connects to the internet, if there is no existing connection to the internet when the PIN is requested. This setting only refers to internet connections using ISDN.
Incoming connection
The PIN is requested with this number.
The leading zero must always be replaced by a star * . Example "*171123456". Leading numerals can also be replaced by a star. This is sometimes useful for connections abroad where the phone number has been incompletely transmitted.
Attention: Only one star * may be entered in the number!
User rights
The user rights are setup in this screen.
A difference is made between user interfaces (designs) and lists.

Administrator rights can be assigned.

The rights are always assigned differently for internal (LAN) and external (internet) access.

The following rules also apply:
  • Multiple user logins are allowed
  • A user can login up to 50 times from one IP address.
  • The total number of users is limited to 200 for each HomeServer
    • Interface
    The user rights for all types of access to the user interface are assigned here.
    Password
    Users can access the HomeServer using their user names and passwords via the internet browser (HTML), the WAP browser or the client program.
    PIN
    Users can access the HomeServer using their user names and PIN via the internet browser (HTML), the WAP browser or the client program.
    Password or PIN
    Users can access the HomeServer using their user names and password, or user names and PINs, via the internet browser (HTML), the WAP browser or the client program.
    Start with
    Menu, Query or Visu.
    This sets the type of start menu that the user is displayed first after logging on.
    Menu
    The user starts with this menu item.
    The user can see all menu items contained within the structure (hierarchical menu).
    A requirement for this is that the user is a member of the appropriate user group.
    The use of user groups is set in Use Project/Project/User groups.
    Visu
    The starting point of the Visu is set here. This can be different for each client.
    The Visu does not have a hierarchical menu. Anyone can call up any Visu page.
    The requirement for this is that the user is a member of the user group.
    read user groups.
    You can assign the reading rights via the access paths set (HTML, WAP, client program). The page can be displayed but no commands can be run. An example explains these contexts.
    Run user groups
    You can assign the rights to run commands via the access paths set in the above (HTML, WAP, client program). The page can be shown and commands can be run. An example explains these contexts.
    Lists
    The internal/external access rights to all lists (archive, login protocol, debug list, etc.) are assigned here.
    Administration
    The admin rights are assigned here.
    If a user has these rights then he can reprogram the HomeServer, as well as store and load the retentive data .
    At least one user is required to have these rights
    in order to program the network/internet/remote access of the HomeServer.