Users
Creating Users
1. Log in as system administrator “sa”.
Go to [PBX] > [Extensions] > [Users] page.
For Brekeke PBX MT Edition, go to [PBX] > [Tenants]. Click [New Tenant] to create a new tenant. When the tenant page opens, go to [Extensions] > [Users] page.
* Super admin “sa” cannot be deleted.
2. Click [Create a new user]. At the user [Account] page, set up the user account information.
Example:
[Extension] 300
[Login Password] your_password (password used to log in to Brekeke PBX Admintool).
[User Type] (select Admin or User)
* There is no default user login password. If no login password is set at the time a user is created, that user cannot log in to the account from Brekeke PBX Admintool.
User Access Settings
The System Administrator (sa) can limit access to various Brekeke PBX menu settings in the [PBX] > [Options] > [User Access Settings] section. This selection will be applied to all administrators and users in the system. Note that the items in the [Admin Menu] sections are only available to administrators.
Default Values of User Extensions
The following table outlines the default values included for Brekeke PBX user extensions. If you change these settings, the functionality of the product may differ from the examples shown in this manual.
To change user settings, click a user’s extension number from the [PBX] > [Extensions] > [Users] list, or select a user from the [User] drop-down menu on the left-hand panel.
In Brekeke PBX MT Edition, go to [PBX] > [Tenants], click on the user’s tenant name and go to the [Extensions] > [Users] page.
| Page name | Setting item | Details of default values | |
| Settings | Call pickup group | Same group as the administrator | |
| Greeting message | Default system greeting | ||
| Email notification | off | ||
| Phones | Phone 1 > [Phone ID] | – Same as user extension
– <tenant>_<extension> (MT Edition) |
|
| Type | Type 1 | ||
| Inbound | Plan | Plan 1 (Active) | |
| Forward To > | [Phones] | All phones are selected as forwarding destinations. When an incoming call to this user is received, Brekeke PBX will forward the call to all phones. | |
| Forward To > | [Ringer Time (sec)] | 90 seconds | |
| Forward To > | [Forwarding destinations (Busy)] | Forwards to user’s voicemail | |
| Forward To > | [Forwarding destinations (No answer)] | Forwards to user’s voicemail | |
| Account | Language | Same language as the administrator who created this user | |
Assigning Phones to User Extensions
Up to four different phone IDs can be assigned to each Brekeke PBX user extension. The default phone ID is assigned in the [Phone 1] > [Phone ID] field and is the same as the Brekeke PBX user extension from when this user was created. For Brekeke PBX MT Edition, it is in the format of tenant name and user extension (as <tenant_name>_<extension>).
The phone ID field can be a SIP UA’s user ID, which is registered at the bundled SIP server of Brekeke PBX, or a PSTN (analog or mobile) number that belongs to the user of this Brekeke user extension. Any devices with a phone ID number assigned to the user extension can use features of Brekeke PBX, such as call conference and call recording.
For Brekeke PBX MT Edition, we recommend using the format <tenant_name>_<extension> as the SIP UA’s ID (phone number) used to register in the bundled SIP server of Brekeke PBX. This will make phone ID management much simpler and will also help to avoid ID conflicts among different tenants within the same system. (What is “Phone ID”)
Phone Type
System administrators can define customized phone types at [PBX] > [Options] > [Phone Type].
In v3.4.X or later, Brekeke PBX supports WebRTC. If WebRTC clients connect to Brekeke PBX, system administrators need to make WebRTC available at “Phone Type.” You can set it as follows:
- Select phone type at [PBX] > [Options] > [Phone Type], then set WebRTC to “yes.”
- Enable changed phone types as follows:
v3.3 or earlier -> Restart PBX
v3.4 or later -> Push “Apply” button on [Phone Type] page (no need to restart PBX).
You also need WebSocket handling available to use WebRTC connection.
[SIP SERVER] > [Configuration] > [SIP] > [WS (WebSocket)] > [WS-handling] on