Fiberme FCM630A User manual

FIBERME Communications LLC.
FCM630A Series IP PBX
Emergency Calls Guide

P a g e 1
Table of Contents
INTRODUCTION..........................................................................................................................3
SCENARIO OVERVIEW.............................................................................................................4
CONFIGURATION STEPS.........................................................................................................5
Customize Notification Prompts........................................................................................................................... 5
Email Notification ................................................................................................................................................... 6
Step 1: Configure Email Settings on the PBX................................................................................................ 6
Step 2: Enable Alert notification for Emergency calls................................................................................... 7
Adding Emergency Numbers............................................................................................................................... 8
Emergency Recordings.......................................................................................................................................11
Emergency Location Mapping ........................................................................................................................... 11
USE CASE SAMPLE ................................................................................................................13
Scenario for VoIP trunks (Kari’s Law and Ray Baum’s Act compliant)........................................................13
Table of Figures
Figure 1: Recording Custom Prompt....................................................................................................................... 5
Figure 2: Email Settings Sample............................................................................................................................. 6
Figure 3: Alert Contacts Configuration.................................................................................................................... 7
Figure 4: Activate Alert Events................................................................................................................................. 8
Figure 5: Emergency Number Configuration......................................................................................................... 9
Figure 6: 911 Emergency Sample......................................................................................................................... 11
Figure 7: Emergency Recording............................................................................................................................ 11
Figure 8: Emergency Location Mapping............................................................................................................... 12
Figure 9: Email Notification.....................................................................................................................................14
Figure 10: System Events (Emergency Calls)..................................................................................................... 14

P a g e 2
Table of Tables
Table 1: Emergency Numbers Parameters .......................................................................................................... 10
Table 2: Emergency Location Mapping Parameters........................................................................................... 12

P a g e 3
INTRODUCTION
On critical situations, having the ability to make emergency calls to ask for help is a must for any telephony
system, whether it’s public telephony system such as GSM network or PSTN network, or the private local
telephony system managed by the PBX on premises.
FIBERME’s enterprise-grade IP-PBX provides users with the ability to manage such type of calls to help
users deal with critical situations and make emergency calls for help. These calls need to have higher
priority than regular calls, categorized depending on the emergency service called and the ongoing situation
as well as the possibility to notify related personal about the situation (guards, first aid ... etc.).
FCM630A provide the administrator with all tools necessary to configure and adapt the PBX with such
situations, making it possible for users to easily press buttons or dial codes/numbers to make emergency
calls.
The FCM630A are now in full compliance with Kari’s Law and Ray Baum’s Act, please refer to the
following link for more information: https://www.fcc.gov/mlts-911-requirements
We will cover on this guide all needed steps to configure emergency calls on FCM IP-PBX series.

P a g e 4
SCENARIO OVERVIEW
To illustrate the functionality of emergency calls on the FCM630A, we will be using the following scenario
where company ABC has already deployed a FCM630A as their main PBX system along with FAP26XX
phones for users.
Company ABC uses a SIP trunk as their main exit point.
Users are allowed to make external calls depending on the established routing policy (permissions,
privileges, PIN codes …etc) while respecting the following requirements and complying to Kari’s Law and
Ray Baum’s Act:
• All users should be able to dial emergency number at any time without adding prefix or any
restrictions.
• The system admin would be receiving email alert notification about the made emergency calls.
• Other members should be notified when an emergency call is being made.
• A call back should be possible when the call disconnects.
• Information about location, such as the address and other location information should be sent
during the Emergency call.
• Emergency calls should go over the main SIP trunk.
• Users are only allowed to dial following emergency numbers: 911, 811 and 711 with the first one
having the highest priority and the last the least.

P a g e 5
CONFIGURATION STEPS
In the following sections, we will be covering all necessary steps to configure the system to fulfill the
requirements discussed on the scenario overview section. First, we need to setup the prompts that we will
be played to the users when someone dials an emergency number.
Note: If no custom prompt is configured, the PBX will play the default one.
Customize Notification Prompts
In order to create a custom prompt that will be used as notification when an emergency
call is initiated, users need to log to the web administration page of the FCM under “PBX
Settings →Voice Prompt →Custom Prompt” then they have two choices:
1. Upload a pre-recorded prompt by pressing the button but the file should respect
the following specs:
• PCM encoded.
• 16 bits.
• 8000Hz mono.
• In .mp3 or .wav format; or raw/ulaw/alaw/gsm file with .ulaw or .alaw suffix.
• File size under 5M.
Note: If uploading a compressed file, the file must have .tar/.tgz/.tar.gz suffix, name must contain only
letters, numbers or special characters -_. and the file size must be less than 30MB.
2. Record a new custom prompt by clicking on then select the recording station on
which you want to record.
Figure 1: Recording Custom Prompt

P a g e 6
Now that the custom prompt is ready, we will be using it as vocal notification to some users, but what about
the system admin who usually received notifications via email?
For that we will need to setup alert events and enable email notification when emergency calls occur to
notify the administrator(s) about the situation.
Email Notification
To configure and enable email notification there are basically two easy steps.
Step 1: Configure Email Settings on the PBX.
To setup email settings on the FCM, log into the web UI under “System Settings →Email Settings” and
set the parameters to send emails via the PBX. Users have two choices (either smtp client or MTA ‘transfer
agent’). Below is a screenshot of configuration of SMTP client used with google mail (Gmail).
Figure 2: Email Settings Sample

P a g e 7
After this, users can press the button in order to verify and confirm that the configured
email settings are valid and working fine.
Notes:
• Users have the ability also to customize the emails that will be sent by the FCM under the tab
“Email Template” for multiple tasks (Fax Sending, CDR, Alert Events …etc).
• Users can check the email send logs under “Email Send Log” tab to view the history of the emails
that were sent by the FCM.
Step 2: Enable Alert notification for Emergency calls.
Next, we need to enable the alert event for the emergency calls as well as email notification
or this type of events. First, make sure to configure the alert contacts under the menu
“Maintenance →System Events →Alert Contact” as shown below.
Figure 3: Alert Contacts Configuration
After this, users need to enable the alert notification for emergency calls under « Alert Events List » tab.

P a g e 8
Figure 4: Activate Alert Events
Adding Emergency Numbers
On this section we provide the steps to configure the different emergency numbers
that users in company ABC are allowed to dial and set the priority for each one as
described on the requirement sections.
We assume that the admin has already configure the trunks and inbound/outbound
routing policy to send calls to the external networks (ITSP). If you need details
about those configurations, you can check the following how to guides:
• Managing Outbound and Inbound calls on FCM.
• SIPTrunk Configuration Guide.

P a g e 9
To configure emergency numbers, users need to follow below steps:
1. Navigate on the web GUI under “Call Features →Emergency Calls”.
2. Click on to add a new emergency number.
3. Configure the required fields “Name, Emergency Number, Trunk(s) to be used to reach the number
and Members Notified”.
4. Set the Emergency level for the number (ex: Significantly Urgent was used for 911 on this case)
5. Save and apply the configuration.
Figure 5: Emergency Number Configuration

P a g e 10
Users could follow same model to add the rest of numbers and assign each one the required level.
The table below gives more description of theconfiguration parameters when creating emergency numbers.
Table 1: Emergency Numbers Parameters
Name
Configure the name of the emergency call.
For example, "emergency911","emergency211" and etc.
Emergency Number
Config the emergency service number. For example,"911","211" and etc.
Emergency Level
Select the emergency level of the number. The available levels are:
1-Not Urgent
2-Moderately Urgent
3-Significantly Urgent
Disable Hunt on Busy
If this option is not enabled, when the lines of trunks which the coming
emergency call routes by are completely occupied, the line-grabbing
function will automatically cut off a line from all busy lines so that the
coming emergency call can seize it for dialing out.
Note: This option is not enabled by default.
Custom Prompt
This option sets a custom prompt to be used as an announcement to the
person receiving an emergency call. The file can be uploaded from the
page "Custom Prompt". Click "Prompt" to add additional record.
Use Trunks
Select the trunks for the emergency call. Select one trunk at least and
select five trunks at most.
Members Notified
Select the members who will be notified when an emergency call occurs.
Strip
Specify the number of digits that will be stripped from the beginning of the
dialed number before the call is placed via the selected trunk.
Prepend
Specify the digits to be prepended before the call is placed via the trunk.
Those digits will be prepended after the dialing number is stripped.
Auto Record
If enabled, the calls using this extension or trunk will be automatically
record, default is disabled
Note: Emergency recording will be also available under Emergency
RecordingTab.
Send Recording File
If enabled the recordings will be sent to the configured Email address(es)
Email Address
Used to specify Email address(es) for Emergency calls recordings.
Below is a screenshot of the configured numbers following company’s ABC requirements.

P a g e 11
Figure 6: Emergency Numbers
Emergency Recordings
The FCM630A allows users to record the Emergency calls and retrieve the recording from Web
GUI→Call Features→Emergency Calls→Emergency Recordings.
To record the Emergency call, users need to enable "auto record" from the Emergency calls configuration,
save the setting and apply the change. When the Emergency call starts, the call will be automatically
recorded in .wav format. The recording files will be listed as below once available. Users could click on
to download the recording or click on to delete the recording. Users could also download all recording
files by clicking on “Download All”, or delete multiple recording files at once by clicking on “Delete” after
selecting the recording files.
Figure 7: Emergency Recording
Emergency Location Mapping
In compliance with Kari’s Law and the Ray Baum’s Act, FCM’s Emergency Calls feature now supports
emergency location mapping. This will allow users to associate subnets with emergency location
identification numbers (ELINs), which can then be used by E911 service providers for example to determine
the location of callers. The new options can be found under Call Features→Emergency
Calls→Emergency Location Mapping.

P a g e 12
To create an Emergency Location Mapping, click on the Add button and the following window will appear.
Figure 8: Emergency Location Mapping
Table 2: Emergency Location Mapping Parameters
ELIN
The DID number that will be sent to E911 providers for example, who will
then use it to determine the location of the emergency caller. This number
will be displayed as the caller’s CID number and will overwrite the
extension or trunk’s CID number (if configured). CID name is not affected.
Warning: If the trunk used for the emergency call has a PAI header
configured, the callee’s endpoint may display that information instead of
the ELIN number.
Subnet
The subnet of the location that will be covered by the ELIN. The FCM will
determine which ELIN to send out based on the subnet that the emergency
caller’s phone is in.
Location
The specific area covered by the ELIN. This information is just for the
FCM’s administrator’s own reference.
Additionally, FCM supports callback now to the original extension that dialed the emergency in case the
call disconnects. If the callee (Emergency number) dials the ELIN to join the caller, the call will be routed
back to the original emergency caller’s extension.
Note: The Emergency Location Mapping is only supported for SIP trunk.

P a g e 13
USE CASE SAMPLE
Scenario for VoIP trunks (Kari’s Law and Ray Baum’s Act compliant)
• John has Sip phone 1 registered on FCM with subnet 192.168.5.0 and the ELIN associated to this
subnet is 1122334455 like shown on Emergency Location Mapping configuration.
• Jane has sip phone 2 registered on FCM with subnet 172.16.1.0 and the ELIN associated to this
subnet is 8185551234.
If John calls 911, the FCM will send the caller ID 1122334455 to trunk provider because he is registered
in the subnet 192.168.5.0/24 while if Jane is the one calling 911 Emergency number, the caller ID that will
be sent in this case will be 8185551234.
1122334455 and 8185551234 are DIDs which will be used for calling back in case the call disconnected.

P a g e 14
After the call has been initiated, we can see also that FCM is sending notification calls to the selected users
which could be personal for first aid at the company, and they will hear the custom prompt configured on
911 emergency number, if non-specified then the default prompt will be played.
The system admin, did receive on the fly the following Email notification.
Figure 9: Email Notification
Also, events notifications can be seen on the FCM’s web UI under « Maintenance →System Events ».
Figure 10: System Events (Emergency Calls)