Ascotel® IntelliGate® 150/300 as of I7.9
144 Configuration
syd-0210/1.7 – I7.9 – 12.2009
Entering the processes in the log
Each access attempt generates an entry in the corresponding list.
In the case of a remote maintenance access an entry will not be generated if re-
mote maintenance is barred or if "CLIP required" is set to "Yes" in the configuration
and no CLIP is received.
5. 4 Enabling remote access
With remote access the user is authenticated using his user name and password.
The user account must also be assigned an authorization profile in which the inter-
face access "Remote maintenance via dial-up access" is enabled.
5. 4. 1 Access enabled by local users
Remote access can be enabled in three ways:
• via */# procedures (see page 145)
• With the AIMS Configuration Manager, if "AIMS authorization level = Attendant"
in the authorization profile.
• Using the System Assistant on the Office 45 if "AIMS authorization level = Attend-
ant" in the authorization profile.
It can be revoked again automatically or manually.
All enabling procedures have equal authorization status. This means that remote
access can be enabled using an */# procedure for example, and then barred again
using the "Remote maintenance" setting in AIMS or with the System Assistant on
the Office 45.
When remote maintenance is activated, the event message "Remote Maintenance
Enabled" is sent to the local printer and to all the terminals registered in message
group 8.
Remote access can be enabled or barred using the */# procedures both from the
idle state and the talk state, e.g. after an enquiry.
The authorization to activate / deactivate remote access using */# procedures can
be allocated in the user configuration ("Remote maintenance = Yes").
When the system is initialized, the authorizations of all users are restricted.
To Next Page
Loading...
