Skip to end of metadata
Go to start of metadata

Access Levels

Administrators have the ability to grant access to users whose accounts have been locally created on SBC 1000/2000, and to users remotely authenticating.

The following table lists the different types of access roles and the functions they secure.

Access Role

Explanation

Administrator

Permission to manage (i.e. view/add/remove) the SBC 1000/2000 system through the User Interface.

Operator

Permission to manage a subset of the functions (non-service affecting) granted to Administrators. See details below.

Audit

Permissions to audit the logs on the SBC 1000/2000 system.

Read-only

Permission to only view the SBC 1000/2000 system through the User Interface.

REST

Permission to manage (i.e. view/add/remove) the SBC 1000/2000 system through the SBC Edge API. Users with this access level will not be able to access the web interface.

Configure SBC Edge Authentication for Non-mapped RADIUS User Classes

If a RADIUS user belongs to a Class that is not mapped to an SBC Edge access level, then a default access is used from the Missing User Class Access Level tab.

Operator Role

Authenticated SBC Edge users with Operator access level have the ability to make non-service affecting changes to the SBC Edge. Below are some examples of service affecting functions:

  1. Installing ASM updates as it will reboot the ASM.
  2. Changing the active partition as it will reboot the SBC.
  3. Installing a new license as it could impact active calls.
  4. Changing the Active Directory configuration as it could impact remotely authenticated users.