PBX Admin Basic
PBX Admin Basic
Version 3
Administrator's Guide
(Basic)
Version
Brekeke PBX Version 3 Administrator’s Guide (Basic)
Copyright
This document is copyrighted by Brekeke Software, Inc.
Copyright © 2014 Brekeke Software, Inc.
This document may not be copied, reproduced, reprinted, translated, rewritten or readdressed in
whole or part without expressed, written consent from Brekeke Software, Inc.
Disclaimer
Brekeke Software, Inc. reserves the right to change any information found in this document
without any written notice to the user.
Trademark Acknowledgement
LINUX is a registered trademark of Linus Torvalds in the United States and other countries.
Red Hat is a registered trademark of Red Hat Software, Inc.
Windows is a trademark or registered trademark of Microsoft Corporation in the United
States and other countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may
be trademarks of their respective owners.
Other logos and product and service names contained in this document are the properties
of their respective owners.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
1. INTRODUCTION ...................................................................................... 7
1.1. Editions......................................................................................................................... 7
2. INSTALLATION........................................................................................ 7
3. MAINTENANCE ..................................................................................... 10
4. UNINSTALL ........................................................................................... 11
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
5.16. Setting Up Busy Lamp Field, Presence and Shared Call Appearance................. 26
5.23. ARS Route with Resource Setting (Brekeke PBX v3.1.x and later)...................... 37
5.25. DID............................................................................................................................... 40
6. SETUP ITEMS........................................................................................ 42
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
6.5. DID............................................................................................................................... 57
6.8. Notes........................................................................................................................... 59
6.9. Extensions.................................................................................................................. 59
6.9.1. System Administrator ............................................................................................... 59
6.9.2. Group Extensions..................................................................................................... 59
6.9.3. Schedule Extensions ............................................................................................... 62
6.9.4. IVR Extensions......................................................................................................... 62
6.9.5. Conference Extensions............................................................................................ 65
6.9.6. Callback Extensions................................................................................................. 66
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
1. Introduction
This document explains the basic configuration of Brekeke PBX. For more advanced setting
instructions and product information, please refer to the Brekeke PBX Administrator’s Guide
(Advanced).
1.1. Editions
Brekeke PBX comes in several editions in order to meet the needs of different users:
Edition Explanation
Product trial prior to purchase with Pro Edition’s feature set.
Evaluation
This license is free of charge.
Designed for businesses and services that need sophisticated call
Commercial
management and advanced features.
Commercial - Designed as a platform that provides hosted IP-PBX service for
Multi-Tenant option Service Providers.
2. Installation
2.1. System Requirements
OS Microsoft Windows XP or later, and Linux
Java 6 or later (32-bit / 64-bit)
Java 9 Brekeke products are confirmed to run on Java provided by Oracle Sun
Microsystems.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
both PBX and the bundled SIP Server, the Brekeke PBX server has started successfully. If
the Status is [Inactive], the server has not started successfully, the error should be shown.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
3. Maintenance
3.1. Back Up / Restore
You can back up current configurations and messages in users’ voicemail box from Brekeke
PBX Admintool menu [Maintenance] > [Back Up]. We recommend backing up Brekeke PBX on
a regular basis. You can restore the backup data from the menu [Maintenance] > [Restore].
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
4. Uninstall
4.1. Uninstall from Windows OS
1) Kill all Java processes (java.exe) used by Brekeke PBX from Task Manager.
2) Navigate to Start / All Programs / Brekeke PBX / Uninstall Brekeke PBX. The uninstaller will
uninstall Brekeke PBX automatically.
9 If the uninstaller fails to delete the folder (C:\Program Files\Brekeke\pbx), you will need to restart the
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Depending on the system UA’s location, codecs and Brekeke PBX feature requirements, the
user or system administrator can choose a suitable phone type for each phone ID assigned in a
Brekeke PBX user extension.
1) From Brekeke PBX Admintool > [PBX Admin] > [Tenants], display all current tenants
2) In this example we will create a tenant named "test".
Click on [New Tenant] button to input "test" as tenant name
3) Once the tenant is created, go to this tenant setup menu by clicking on the tenant name
4) Clicking on [Options] menu under this tenant to set tenant users and sessions limit from
[Capacity] section and enable required features for this tenant from [Features] section.
9 Lower-case letters, digits, dots and underscores are valid characters for a tenant name.
For Brekeke Multi-Tenant PBX, default system administrator “sa” is the only administrator for
whole system. “sa” administrator needs to create a tenant administrator at the time a tenant is
created, and authorizes tenant administrators for accessing tenant DID and system notes.
By logging in as a tenant administrator from Brekeke Multi-Tenant PBX admintool, each
enterprise client administrator can define his company extensions system.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
following settings:
[Extension] 100
[Login Password] 100
[Login Password (confirm)] 100
[User Type] User
There is no default user login password. If no login password is set at the time a user is
created, that user cannot login to the account from Brekeke PBX Admintool.
3) Edit the user account settings as needed.
4) There is no default voicemail access PIN set at the time a user is created. Set the user’s
voicemail box PIN from the user’s [Settings] page. Please refer to the sections below for
more information about voicemail.
5) At the user’s [Phones] page, the user extension number or <tenant>_<extension>
(Multi-Tenant PBX) will be automatically set as this user’s default phone number in the first
[Phone ID] field at the time the user is created.
If the user’s phones have any numbers other than the default phone number, you can
assign these numbers to any [Phone ID] on the [Phones] page and select the proper [Type]
for each assigned phone. Please check the following sections for more details about
assigning phones to user extensions.
6) Create other user extensions 101-105 as above.
To change user settings, click the user’s extension number from the [PBX Admin] > [Extensions]
> [Users] list, or select a user from the [User] menu on the left-hand panel and navigate to each
page under the selected user.
For Brekeke Multi-Tenant PBX, go to Brekeke PBX Admintool > [PBX Admin] > [Tenant].
Click on the tenant name and then go to this tenant [Extensions] > [Users] page.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Type Type 1
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
The phone ID field can be a SIP UA’s user ID, which is registered at Brekeke PBX bundled SIP
server, or a PSTN number that belongs to the user of this Brekeke user extension. Any devices
with a phone ID number assigned under a Brekeke PBX user extension can apply Brekeke PBX
features to the call.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
For those SIP UAs that do not send “SUBSCRIBE” message for MWI, you can create a new
phone type and set [MWI (NOTIFY without SUBSCRIBE)] field as on and select this phone type
from the PBX user extension [Phones] page where these SIP UAs are assigned. Then Brekeke
PBX will send voicemail notification even there is no “SUBSCRIBE” message for MWI sent from
these SIP UAs.
Here are some other ways of using the Call Pickup feature:
♦ Answer Calls That Are Directed to a Ring Group
Calls directed to a Simultaneous Ring Group extension can be answered from any user
extension using Call Pickup. (For details on how to set up a Ring Group, please refer to the
“Setting Up Ring Groups” section.)
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Dialing *1000 (the Simultaneous Ring Group extension number) enables a user to pick up
any calls within the Ring Group. Incoming calls can still be answered by dialing *<group
extension ID>, such as *101, *102. However, using the group extension ID to pick up call
does not require you to remember each user extension ID in the group. The *<ring group
extension ID> feature even works when a call is made directly to a single extension (e.g.,
103) or when the call comes through the Auto Attendant to a extension which is set in ring
group extension.
You may specify a Call Pickup Group (such as “1000”) for a user extension at [Settings] >
[Call Pickup Group]. When there is an incoming call to any user extension in the
Simultaneous Ring Group extension 1000 > [Group Extensions] field (in this case,
extensions 101-105), you can answer the call by dialing * (Star) only.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
In this example, the call will ring the user extensions in the [Hunt group extensions*] field
one-by-one with a five-second interval (Ringer time) between calling each user extension. If all
of the group extensions (101-105) are busy or do not answer, the call will be queued. If any
member becomes available within the interval set in [Waiting time in the queue (sec)], Brekeke
PBX will ring the first available extension in the group for the length of ringer time in this
extension user setting, then wait for the time of [Call interval (msec)](3000 ms) before ringing
the next available extension in the group. If all members continue to be busy after the specified
interval at [Waiting time in the queue (sec)], the call will be forwarded to the destination set in
[Forwarding destination (No answer)]. In this example, the call will be forwarded to user 100.
The music that the caller hears while waiting on hold can be changed by uploading a new sound
file in the [Sound files] > [Music on hold] field.
In this example, the incoming call to Auto Attendant 1002 will hear the default greeting voice
prompt to input an extension.
If there is no input in 20 seconds ([DTMF timeout (sec)]), Brekeke PBX will ask the caller to
re-input the extension. After five times of no extension input ([Max retry count]), the call will be
forwarded to the destination that is set in the [Default operator] field.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
If the caller inputs an extension number, the call will transfer to the extension whose ID is the
same as the first three digits ([Max input digits]). If the transfer recipient does not answer the call
within ten seconds ([Ring timeout (sec)]), Brekeke PBX will stop ringing the input extension and
Auto Attendant will ask the caller to input a different extension number.
When [Transfer to unregistered users] is enabled, the caller can apply Brekeke PBX features
from Auto Attendant, such as accessing a voicemail box, call pickup and so on.
9 Note that a proper value must be set in the Auto Attendant > [Max input digits] field in order to allow a
caller’s input.
Optionally, an audio file for the Auto Attendant greeting can be uploaded from the Auto
Attendant > [Sound files] section.
In this example, incoming calls to extension 5555 during business hours are directed to the Auto
Attendant at extension 1002. After business hours, callers are scheduled to hear, “To speak with
a live operator, please call during regular business hours. Our regular business hours are
Monday through Friday, 9 a.m. to 6 p.m.”
You can use the following settings to set up such a scenario:
1) Create an Auto Attendant 1003 and upload an after business hour greeting to [Greeting
messages] under Auto Attendant 1003.
2) From [Extensions] > [Schedule], click [Create a new schedule] button.
3) Set as follows:
[Extension] 5555
[Default Forwarding Schedule] > [Call Forwarding] > [Destination] 1003
4) Click the [Add Forwarding Schedule] button.
Set [Forwarding Schedule 1] as follows:
Set the [Forward To] > [Call Forwarding] > [Forwarding Destination] field to 1002.
Click the [Conditions] tab and set the [Date/Time] section as follows:
[Term] set schedule starting and ending Date and Year.
[Days] Check 1st - 5th and Monday through Friday.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
In this example, incoming calls during business hours go directly to user 100’s assigned
phone(s). However, during user 100’s lunch break, you can send incoming calls directly to
voicemail. User 100 can enter DND (Do Not Disturb) mode by switching between pre-defined
inbound plans to route incoming calls to his/her voicemail temporarily during lunchtime.
The following samples show two different ways of implementation. More samples about
changing active plan with switch plan are available at Brekeke Wiki:
http://wiki.brekeke.com/wiki/Switch-plan-in-user-extension
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
your SIP phone for information on how to set up the Conference Call feature.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
1) From [Extensions] > [Conference], click the [Create a new conference] button.
2) Set as follows:
[Extension] 2000
Leave all other settings as default.
3) Save the settings.
With the above settings, any user can enter the conference room by dialing 2000.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
When a caller dials a Callback extension, the caller will hear a ring tone. If the caller hangs up
before the ringer times out, Brekeke PBX will send an INVITE to the caller, who will then be
connected to the number set in the [Callback callee] field. In this example, the caller will be
connected to Auto Attendant 1002.
When a caller who dials a Callback extension does not hang up before ringer timeout, the call
will be directed to the destination set in the [Forwarding destination (No answer)] field.
available) or the caller’s phone number played after the voice prompt. In this case, you need to set
A list of SIP phones that work with the Brekeke PBX paging function, as well as its sample
configuration are available at the Brekeke Wiki:
http://wiki.brekeke.com/wiki/paging-function_phone-list
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
5.16. Setting Up Busy Lamp Field, Presence and Shared Call Appearance
♦ BLF (Busy Lamp Field)
With BLF, when there is a call to a monitored phone, the corresponding key lamp on the
monitoring phone will flash and the call can be picked up from the monitoring phone.
♦ SCA (Shared Call Appearance)
With SCA, users can monitor the external line status and select an available line to place an
outbound call or to answer incoming calls.
♦ Presence
With presence, Brekeke PBX can handle presence SUBSCRIBE requests from phones and
return NOTIFY responses about the status of the monitored phones, such as "available" or
"on the phone."
A list of SIP phones that work with these functions, as well as their sample configurations are
available at the Brekeke Wiki:
http://wiki.brekeke.com/wiki/BLF-SCA-and-Presence
Video can be enabled from several locations in Brekeke PBX: Options, ARS Settings and User
Settings. Video setting enabled in the phone type set under Users > [Phones] -> [Phone Type]
has the highest priority. When the default setting is defined in [Phone Type] > [Video] field, the
video setting under [ARS] route will be applied if the call can apply any route. When video
setting in both User [Phone Type] and ARS route is set to the default, the [Video] setting at
[Options] will be applied to the call.
The following steps show how to enable video for the phone assigned to a Brekeke PBX user
extension.
1) From Brekeke PBX Admintool > [Options] > [Phone Type] page, create a new phone type
2) At new phone type setting page, set [Video] field as on and set proper audio codecs in
[Codec Priority] field.
3) Save the new phone type and restart Brekeke PBX from admintool.
4) From a PBX user extension > [Phones] page, select the phone type created above at the
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
[Type] field under the phone which supports video for the call. And save the changes.
5) The call between PBX users with video phone type or from/to external user through ARS
route with [Video] field set as "on" will have video feature.
SRTP can be enabled from several locations in Brekeke PBX: Options, ARS Settings and User
Settings. SRTP setting enabled in the phone type set under Users > [Phones] -> [Phone Type]
has the highest priority. When the default setting is defined in [Phone Type] > [SRTP] field, the
SRTP setting under [ARS] route will be applied if the call can apply any route. When SRTP
setting in both User [Phone Type] and ARS route is set to the default, the [SRTP] setting at
[Options] will be applied to the call.
From Brekeke PBX v3.1.x, by clicking [View] in the ARS route list’s [Status (Reg/Route)] column,
the details of an active ARS route can be displayed. An ARS rule can also be edited by clicking
the ARS route name. If the ARS rule is a template with the [Template] field checked, you can
click [Edit Template] on the [Variable Setting] page to change the template setup and the
variables’ setups for each route under the template.
In Brekeke Multi-Tenant PBX, the tenant name needs to be set for any ARS rule that will be
used exclusively by a specific tenant. The tenant name is set in the ARS rule > [General] >
[Tenant] field.
By assigning a tenant name in ARS rules for inbound calls, Brekeke Multi-Tenant PBX will
associate inbound calls with this tenant and will route inbound calls to the proper tenant
extensions.
By assigning a tenant name in the ARS rules for outbound calls, Brekeke Multi-Tenant PBX will
look for the ARS route for this tenant, determine who the caller is and then route the call to the
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
destination set for this tenant. If no tenant name is assigned in the ARS outbound route, the
route will apply to calls from any tenant.
♦ Registration
Register your VoIP gateway port SIP number at Brekeke PBX bundled SIP Server. Brekeke
PBX will accept calls from this gateway even if the gateway is not registered at Brekeke
PBX bundled SIP Server.
If a provider needs authentication information from a caller who makes outbound calls from
UAs to an ITSP, Brekeke PBX will send the username and password that are set in this
section to the provider in an IP address or in the domain set in the [Proxy Address] field.
♦ Patterns
Define Patterns IN and OUT to receive and send calls from/to SIP devices and services.
♦ Priority
It is useful to set priorities when there are multiple options for making calls, such as when
you have multiple PSTN gateways for outbound calls or when you subscribe to multiple
VoIP service providers. A lower number holds the higher priority.
♦ Max Sessions
Set the [Max Sessions] field to define the maximum number of sessions that can be
handled by each pattern, such as when there is a limited number of Gateway channels or
subscribed lines for your SIP services. Setting this field to “-1” specifies an unlimited
number of sessions.
For ARS routes in the same group, there is only one session counter. The session counter
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
for the group will increase by one when there is a call through any ARS route in this group,
regardless of what is specified in Pattern IN or OUT. If this session counter is equal to any
pattern [Max Sessions] value that is set in the same group’s ARS routes, the next matched
session cannot apply to this pattern (IN or OUT) or to any ARS routes when all of the
patterns’ [Max Sessions] for the ARS routes in the same group are set to the same value.
From [Field Settings], administrators can set a global variable’s field type, name and description,
and can also choose whether or not a global variable will be displayed on the ARS top page.
♦ Common Settings
Common variables can be accessed from any route created under the same ARS template.
Updating a common variable will affect the ARS routes under the current ARS template.
From [Field Settings], administrators can set a common variable’s field type, name, initial
value and descriptions, and can also choose whether a common variable will be displayed
on the [Variable Settings] page.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Sample script:
if( v1 == 3333 )
v5= "192.168.200.20";
else
v5= "192.168.200.30";
Set the above script in the [Route Local Settings] > [Field Settings] -> [Script] field. If a
route has variable v1 with value 3333, this route variable v5 will be set as “192.168.200.20”
automatically. The route variable v5 will be set as “192.168.200.30” when variable v1 is set
to any value other than 3333.
By using these plug-ins, you can search for a caller's number in a telephone directory (making
notes under [Options] > [Notes] to save data list) and handle the call as your need, such as,
decline the call, change the caller ID, or redirect the call.
For the details about the Brekeke PBX default plug-ins and how to configure ARS route to use
the plug-ins, please refer to “Developer's Guide: ARS plug-in”.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
9 Default ARS rule “gw2” is the setup template for two-stage dialing.
Use the following settings to register the gateway at the Brekeke PBX bundled SIP server. Many
PSTN Gateways have a short interval between sessions, during which time the line is
unavailable. You can modify the [Session interval (ms)] field setting to reflect this delay as
needed.
9 In Brekeke PBX v3.1.x, check the [Template] field to enable the [Variable Setting] page.
[Registration]
Register URI sip:&v1@127.0.0.1 Register expire (sec) 3600
Proxy address 127.0.0.1 Register update period (%) 90
User Password
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
[Patterns – OUT]
Matching patterns Deploy patterns
From
To sip:([0-9]{7,25})@ sip:$1@gw_IPaddress
In this example, Regular Expressions were used to define the Matching and Deploy patterns. A
Brekeke PBX user who dials a number that has between 7 and 25 digits will be considered as a
PSTN call. Brekeke PBX will apply the above ARS Route and the call will be sent to the
gateway.
If you use multiple VoIP Gateways for outbound calls, you can define more detailed dialing
patterns in [Matching patterns] > [To], as well as change the [Priority] field as necessary to
define the usage order of Gateways. Please note that lower numbers hold the higher priority.
You can use the [Max Sessions] field to define the total number of sessions handled by each
pattern.
Two-Stage Dialing
If your VoIP Gateway supports Two Stage Dialing, have the gateway’s PSTN port register with
Brekeke PBX bundled SIP server. Let’s suppose the gateway’s PSTN port has the SIP user
name 111. To call a PSTN number, dial the gateway’s registered PSTN port number (in this
example, it’s number 111) and then dial the destination PSTN number. Alternatively, you can
configure the DTMF setting at the ARS Route OUT pattern so that the dialed numbers will be
sent to the gateway as DTMF tones.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
The OUT pattern to send a destination number by DTMF in Two-Stage Dialing is as shown
below:
Patterns – OUT
Matching patterns Deploy patterns
From From
To sip:111(.+)@ To sip:111@gw_IPaddress
DTMF $1
9 If a delay is needed before sending a DTMF call, set the [DTMF] field as {file_name}$1. Default files
are {120ms}, {240ms}, {500ms}, {1sec} and {2sec}. Customized files can be uploaded from Brekeke
PBX Admintool > [PBX Admin] > [Voice prompts] and set [Language]: Common.
Acquiring the information shown below is necessary to connect with a third-party SIP server.
Phone number 6504106636
SIP server IP address sample_proxy.com
User ID 6504106636
Password 6636
9 Depending on the provider, there may be restrictions for connecting to services, such as available
information or equipment used to connect. Please contact your VoIP service provider for more
details.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
[Registration]
Field name Sample settings Explanation
Register
sip:&v1@sample_proxy.com Enter SIP URI.
URI
Can be omitted when Proxy address is
Proxy
sample_proxy.com the same as the one in the [Register URI]
address
field.
User &v1 Set value at [Variables Settings] page.
Password Set value at [Variables Settings] page.
(Brekeke &v2 This field will be displayed in text format
PBX v3.0.x) after saving.
[Patterns – IN]
In the Patterns – IN example below, Brekeke PBX user extension 100 (“&v3” value, set at the
[Edit Variables] page) is set to ring when a call comes through a third-party SIP server. Leaving
the “From” field blank carries over the Caller ID information.
Matching patterns Deploy patterns
To sip:&v1@ &v3
9 Check [Apply to Request URI instead of To] when To header sent from ITSP is different from To
[Patterns – OUT]
Patterns – OUT defines patterns for converting the SIP URI to match your VoIP provider’s
header format requirements. In the example below, dialed numbers with 7 to 25 digits will be
directed through the VoIP service provider. To ensure that the recipient’s caller ID display will
function, the “From header” will change according to the rules of the provider. Set [Priority] and
[Max Sessions] as you need.
Matching patterns Deploy patterns
From “&v1” <sip:&v1@sample_proxy.com>
To sip:([0-9]{7,25})@ sip:$1@sample_proxy.com
9 Some VoIP service providers restrict the connection when the FROM or TO header information is
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
[Variables ]
Click the [Variables] link at the upper-right corner of the ARS Route template page. On the
[Variable Setting] page, select [New Route] and assign values to variables defined in the above
Patterns – IN and Patterns – OUT.
Route Name Route 6504106636 (Brekeke PBX v3.1.x and later)
Tenant A tenant name (Multi-Tenant PBX)
Password / v2 6636
v1 6504106636
v3 Specify a Brekeke PBX extension number, such as 100.
9 For Brekeke PBX v3.0.x, set related variables from the [Edit Variables] page.
In the following example, two ARS routes are created: “ITSP_A” and “MyGateway.” The route
with the highest priority, “ITSP_A,” will be used for outbound calls with a dialing numbers that
have 7 to 25 digits. If there is no response within four seconds (Response timeout: 4000 ms) for
INVITE messages or a “500-599” response is received, Brekeke PBX will continue searching for
the next route that matches the outbound session request. In this case, the next-highest
prioritized route, “MyGateway,” will be chosen as the alternative route for the session. Since the
recovery time is set to one hour (3600000 ms) in “ITSP_A,” the matching sessions will be routed
through route “MyGateway” for one hour after the failover. If “ITSP_A” is running again within an
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
hour, the sessions will once again be routed through the highest priority route, “ITSP_A.”
Parameters
Next route on Disable on
Yes Yes
failure registration failure
Response
4000 Error codes 500-599
timeout (ms)
Recovery
3600000 Disable on failure This route
time (ms)
♦ [Disable on registration failure] is set to “yes” in Route “ITSP_A.” When registration is not
working property at the “ITSP-A” route, it will be disabled and the “MyGateway” route will
be used instead.
♦ [Disable on failure] is set as “This route,” which will disable the whole route. If there are
other IN/OUT patterns defined in this route, they will be unusable when failover happens. If
[Disable on failure] is set as “This pattern,” it will only disable the current pattern, so other
patterns in this route will still be usable.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Patterns – OUT
OUT – 1 Matching patterns Deploy patterns
Priority 100 From From
Max
4 To sip:([0-9]{7,25})@ To sip:$1@GW_IPaddress
sessions
5.23. ARS Route with Resource Setting (Brekeke PBX v3.1.x and later)
When multiple ARS routes for Shared Call Appearance (SCA) are set with the same name in the
[Resource] field, Brekeke PBX SCA users will have more ARS route choices for making
outbound calls than by using the ARS settings without this [Resource] setup.
Set up the ARS template and Brekeke PBX users as described below and assign phones with
the Shared Call Appearance feature enabled to users.
Route Template:
[General]
Route name outbound
Template checked
Line key checked
Resource &v9
[Patterns – OUT]
OUT – 1 Matching patterns Deploy patterns
Priority &v1 From From
Max
&v2 To sip:([0-9]{7,25})@ To sip:$1@&v3
sessions
Variable Setting:
Route Name v1 v2 v3 v9
1 90 1 192.168.200.10 gw
2 90 -1 192.168.200.20 itsp
3 100 1 192.168.200.30 gw
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
User: 101
[Settings] -> [Resource map]
line/1=gw/1
line/2=itsp/1
When user 100 makes an outbound call from a phone with shared line 1, the call will apply route
“outbound*1” with resource set as “gw” and the call will be sent to the destination IP
192.168.200.10.
While user 100 is talking, if user 101 also makes an outbound call from shared line 1, the call will
apply route “outbound*3” with resource also set as “gw” and will be sent to the destination IP
192.168.200.30.
Because route “outbound*1” with resource “gw” has the [Max Sessions] variable v2 set to 1 and
one session from user 100 is using this route, Brekeke PBX looks for the next available route
with resource “gw” for the user 101 outbound call, which is route “outbound*3.”
If user 101 makes an outbound call from shared line 2, the call will apply route “outbound*2” with
resource “itsp” and will be sent to IP 192.168.200.20.
Route Template:
[General]
Route name outbound
Template checked
Group &v8
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
[Patterns – OUT]
OUT – 1 Matching patterns Deploy patterns
Priority &v1 From From
Max
&v2 To sip:([0-9]{7,25})@ To sip:$1@&v3
sessions
Variable Setting:
Route Name v1 v2 v3 v8 v9
1 90 1 192.168.200.10 group1 gw
2 90 -1 192.168.200.20 itsp
3 100 1 192.168.200.30 group1 gw
4 110 1 192.168.200.40 group2 gw
User: 101
[Settings] -> [Resource map]
line/1=gw/1
line/2=itsp/1
If user 100 makes an outbound call from shared line 1, the call will apply route “outbound*1” with
resource set as “gw” and group as group1 and the call will be sent to the destination IP
192.168.200.10.
While user 100 is talking, if user 101 also makes an outbound call from shared line 1, the call will
apply route “outbound*4” with the resource set as “gw” and the group as group2 and the call will
be sent to the destination IP 192.168.200.40.
As explained in the above section about Max Sessions, routes in the same group use the same
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
session counter. In this example, routes “outbound*1” and “outbound*3” with resource “gw” are
both in “group1” and both routes have the [Max Sessions] variable v2 set to 1. When user 100 is
making a call through route “outbound*1,” the number of sessions in group1 is 1, which will
reach the [Max Sessions] in both routes “outbound*1” and “outbound*3.” Brekeke PBX will then
look for the next available route with resource “gw” for user 101’s outbound call. This is route
“outbound*4.”
The above example explains that the [Resource] setting is used for Brekeke PBX users to look
for available routes to make outbound calls and that the [Group] setting is used to limit max
sessions through the routes of both Patterns – IN and Patterns – OUT in the same group.
9 Multiple groups can be set in an ARS route [Group] field with group names separated by commas.
9 When a session goes though a route set with multiple groups, the session counter of the related
5.25. DID
From the [DID] menu, administrators can access and modify the active routes setup.
For Multi-Tenant PBX, only the active DID route related to the tenant will appear in tenant
administrator accounts. Tenant administrators can modify the route fields as necessary.
The following steps show how to enable DID access for a route and to set DID access
privileges.
Step 1: Enable DID Menu
1) Log in to Brekeke PBX Admintool as system administrator (sa).
2) Go to the [Options] > [User Access Settings] page in the [Admin Menu] section.
3) Select on in [DID] menu.
Step 2: Enable a Route’s DID Access
1) Log in to Brekeke PBX Admintool as system administrator (sa).
2) Go to [ARS] and select an active ARS route template that can be accessed from a non-sa
administrator’s [DID] menu.
3) Go to the selected route template’s [Variable Setting] page, click on the [Field Settings] link
next to [Route Local Settings].
4) Select [Yes …] in the [DID] field.
[No] disables access to the routes from the DID menu in administrators’ accounts.
[Yes (Modify only)] enables access to the active routes under the route template from
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
5) For Brekeke Multi-Tenant PBX, set the tenant administrator’s access privilege for each
variable to one of the following options:
[Tenant Access (List)] enables or disables displaying of the variable in the route table of
tenant administrator accounts.
[Tenant Access (Edit)], if checked, allows the variable settings to be modified from tenant
administrator accounts. If unchecked, the variable settings will not be modifiable from
tenant administrator accounts.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
6. Setup Items
6.1. Start / Shutdown
At the [Start / Shutdown] page, the system administrator can perform the following functions:
Check Brekeke PBX and its bundled SIP Server running status; check current events, such as
ARS route registration history; restart or shutdown Brekeke PBX and bundled SIP Server.
6.2. Options
The following list displays the settings under the [Options] menu, which is only available to
system administrators:
6.2.1. Settings
♦ General Settings
Name Default value Description
Auto: Brekeke PBX starts up automatically with the
Tomcat (Brekeke PBX HTTP Service).
Start up Auto
Manual: Start up manually.
Options: Auto / Manual
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Ringing timeout Amount of time to wait for an answer from the dialed
240000
(ms) party after ringing starts.
Maximum length of time a call can last in talking,
Talking timeout
259200000 measured by the amount of time since the last SIP
(ms)
packet was received. Value 0 signifies infinite.
Maximum number of SIP servers or Brekeke PBX
Max hop number 20
that a call can go through (hop number).
Days to keep call
90 Number of days to keep call logs.
logs
Session Timer Interval to allow UAs and SIP server to determine
0
(sec, 0=disable) whether the SIP session is still active.
Interval to send keep-alive packets to UAs during a
Session keep alive
600 call when RTP relay is set to off and session timer
(sec)
has not been used.
RTP Session Timeout value for Brekeke PBX awaiting the next
600000
Timeout (ms) RTP packet.
Enable (on) / Disable (off) for using reliable
100rel off
provisional responses (1xx series).
RFC2833 on Enable (on) / Disable (off) RFC2833 setting.
Web service security – used by Brekeke PAL and
Valid client IP
Brekeke Web Service; Set with regular expressions
pattern
of the PAL and Web Service clients IP pattern.
Java VM
Parameters passed to VM.
arguments
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
♦ Email Settings
Name Default value Description
The SMTP server address for sending email
SMTP Server notifications when the user receives a new
voicemail message.
SMTP port 25 SMTP server’s listening port.
SMTP Enable (on) / Disable (off) SMTP authentication
on
authentication setting.
Encrypted Enable (on) / Disable (off) Encrypted Connection
off
connection (SSL) (SSL), available since version 2.3.
Address of the POP3 server (for POP-before-SMTP
POP3 server
authentication).
POP3 port 110 POP3 server’s listening port.
Email account username for the above SMTP
User
server.
Password Email account password.
Password
Input field for confirming the above password.
(confirm)
Email address
Email notification sender’s address.
(from)
Email subject for the email notifications.
The following variables can be configured:
{from}: SIP URI who left the voicemail message
{to}: voicemail box’s SIP URI
voicemail({to})
Email subject {from-number}: number in {from}
: from {from}
{to-number}: number in {to}
{time}: time when the messaged is recorded
{recording-length}: length in time of the recorded
message
from:{from}
to:{to}
Email body for email notifications.
time:{time}
Email body Variables that can be used in this field are the same
recording
as in the [Email subject] above.
length(sec):{re
cording-length
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
♦ PAL Settings
Name Default value Description
Sends notification to Brekeke PAL or Brekeke PAL
Notification for
yes WebSocket application (or not) when a user phone
registration
has registered.
Web service security – used by Brekeke PAL
Valid WebSocket
WebSocket; Set with regular expressions of the
client IP Pattern
WebSocket clients IP pattern .
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
6.2.6. Advanced
The [Advanced] field allows you to set properties that do not have corresponding fields in
Brekeke PBX Admintool. Please refer to other manuals and tutorials regarding the type of
properties that may be edited here.
Name Description
Language Choose folder in which to save an uploaded file.
Name for the uploaded file in the folder.
Name If the file name is the same as the system default sound file, the
uploaded sound file will be played.
Description A memo shown on the GUI to describe the file usage.
To upload a file, click the [Browse] button. Select the file you want to
File name
upload and click [Upload]. The upload will then start.
To download a recorded sound file, click Download ( ). The file will
Download
be downloaded to your PC as a WAV file.
To delete a recorded sound file, click Delete ( ). The selected file(s)
Delete
will be deleted.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
You may use sound-recording applications, such as Windows Microsoft Sound Recorder, to
record sound files. We recommend that you adjust the pause and sound level to suit your
needs.
route displayed under [Running Status]. Selecting [Settings] will display all ARS Routes.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
♦ Registration
Name Default value Description
SIP URI that is used to register Brekeke PBX at a
remote registrar server. Leave this blank when there
Register URI
is no need to register Brekeke PBX to any remote
registrar server.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
♦ Pattern – IN
Default
Name Description
value
Priority 100 Lower numbers hold a higher priority.
Specify the number of sessions
(including RINGING and BYE
Max sessions -1
sessions) that are allocated to the
route.
Disabled unchecked Enable / Disable this pattern.
Specify a matching rule for the From
header using regular expressions.
Matching patterns From
When the field is left blank, all calls will
be considered as matched.
Specify a matching rule for the To
header using regular expressions.
To
When the field is left blank, all calls will
be considered as matched.
Plugin Java class name for the plug-in.
Parameters that will be used by the
Param
plug-in.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
♦ Patterns – OUT
Default
Name Description
value
Priority 100 Lower numbers hold a higher priority.
Specify the number of sessions
(including RINGING and BYE
Max sessions -1
sessions) that are allocated to the
priority.
Disabled unchecked Enable / Disable this pattern.
Specify a matching rule for the From
header using regular expressions.
From
When the field is left blank, all calls will
be considered as matched.
Specify a matching rule for the To
header using regular expressions.
To
When the field is left blank, all calls will
be considered as matched.
Mostly designed for multiple ITSP
Matching patterns
User ^.+$ accounts, it specifies the users to which
this ARS Route applies.
Specifies the users in the class to
Class
which this ARS Route applies.
Plugin Java class name for the plug-in.
The parameters which will be used by
Param
the plug-in.
The pattern of the value returned by the
Return
plug-in.
Specify replace patterns for the From
Deploy patterns From
header using regular expressions.
Specify replace patterns for the To
To
header using regular expressions.
Destination IP address. May omit entry
Target when the destination IP address is
specified in the To header domain.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Options:
This route, This pattern, This group
6.5. DID
Displays a list of DID-enabled routes. Administrators can modifiy enabled route fields, such as
changing the destination extension where inbound calls to a related DID number will be sent.
For more detailed setting instructions, please refer to the DID section above.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Name Description
Total Total number of system active sessions
ID Call ID
Status Call status: In progress, Talking
UAs Users’ phone numbers in the current session
6.6.1. Status
Name Description
ID Call ID
Status Call status
Call park The number that has been parked
Conference Conference number
Start Time the call begins
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
6.8. Notes
This menu item is used by Brekeke PBX plug-ins to access text data or to save script files for
IVR script users. You can also use it for writing some memos.
Name Description
Name Name of the note
Description Brief description of the note
Define if this note can be accessed by users, as well as what the
User access level access level is.
Select from “No Access,” “Read only” or “Read/Write.”
Note Text field where you can write your own notes
6.9. Extensions
On the left menu panel, click the [Extension] menu. Select different extension tabs and create
extensions. Click extension ID to edit this extension setting.
For user extension setting details, refer to the Brekeke PBX User Guide.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Sound Files
Name Description
Audio file that contains the music/sound that
Music on hold
will be played when the caller is on hold.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Name Description
Calls will be forwarded to the destination set
Default forwarding schedule* here when no other schedules can be
applied to the call.
Calls will be directed to the destination set
Forwarding schedule [n]
here when the conditions are met.
Multiple schedule plans can be created under
Plan [n] a single extension.
The active plan will be applied to calls.
Specify the schedule when a plan will be
Timer 1/Timer 2
active.
♦ Auto Attendant
Name Default value Description
Extension Extension ID
Type Auto Attendant Extension type
Description Extension description
Language English Select IVR language.
Max input digits 4 Maximum number of input digits
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Sound Files
Name Description
Greeting message that is played for the Auto
Greeting message
Attendant.
A message to prompt the caller to re-enter the
Retry message
number when an input error has occurred.
Audio file that contains the music/sound that
Music on hold
will be played when the caller is on hold.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
♦ Switch Plan
Name Default value Description
Extension Extension ID
Type Switch Plan Extension type
Description Extension description
Language English Select IVR language.
By calling this extension, the caller extension’s
Plan number 2 [Inbound] page active plan value will change to the
value set here.
When set to yes, the plan number will be set as the
active plan when a user calls this extension. The
active plan will switch back to plan 1 when the user
calls this extension again.
On/Off Yes
When set to no, the plan number will be set as the
active plan when a user calls this extension, but will
not switch back to plan 1, regardless of how many
times the user calls this extension.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
Sound Files
Name Description
Audio file that contains the music/sound that
Music on hold while waiting will be played while waiting for other
attendees to join the conference.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
7.1. Tenants
From this menu, a system administrator can create a new tenant, delete a tenant and copy and
modify existing tenant settings.
9 Shutting down Brekeke Multi-Tenant PBX from Admintool is required when deleting a tenant.
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
The format for accessing tenant-level notes from Brekeke PBX plug-ins is as follows:
<tenant_name>.<note_name>
♦ Capacity
Name Description
Maximum users Maximum number of user extensions allowed under this tenant
Maximum sessions Maximum number of concurrent sessions allowed for this tenant
Maximum recording Maximum number of concurrent recording sessions allowed for this
sessions tenant
Maximum G.729 Maximum number of concurrent G.729 sessions allowed for this tenant
p-adm-b3.3.x_140214
BREKEKE SOFTWARE, INC.
♦ Features
Name Description
Voicemail Enable or disable this feature for the tenant
Auto-Attendant Enable or disable this feature for the tenant
Conferencing Enable or disable this feature for the tenant
Call Recording Enable or disable this feature for the tenant
Round Robin –
Enable or disable this feature for the tenant
Topdown
Call Queue Enable or disable this feature for the tenant
PAL Enable or disable this feature for the tenant
p-adm-b3.3.x_140214