Mivb Redsky Raybaum

MiVoice Business
RAY BAUM'S Act Solution Deployment

Guide for RedSky
Release 10.0 SP1

Document Version 1.0
May 2023
Notices
The information contained in this document is believed to be accurate in all respects but is not
warranted by Mitel Networks™ Corporation (MITEL®). The information is subject to change
without notice and should not be construed in any way as a commitment by Mitel or any of its
affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for
any errors or omissions in this document. Revisions of this document or new editions of it may
be issued to incorporate such changes. No part of this document can be reproduced or
transmitted in any form or by any means - electronic or mechanical - for any purpose without
written permission from Mitel Networks Corporation.
Trademarks
The trademarks, service marks, logos and graphics (collectively “Trademarks”) appearing on
Mitel's Internet sites or in its publications are registered and unregistered trademarks of Mitel
Networks Corporation (MNC) or its subsidiaries (collectively "Mitel") or others. Use of the
Trademarks is prohibited without the express consent from Mitel. Please contact our legal
department at [email protected] for additional information. For a list of the worldwide Mitel
Networks Corporation registered trademarks, please refer to the
website:http://www.mitel.com/trademarks.
®,™ Trademark of Mitel Networks Corporation
© Copyright 2023, Mitel Networks
Corporation All rights reserved

Contents
MiVoice Business .................................................................................................................................. 1
What's new in this Document ............................................................................................................... 7
Kari’s Law and RAY BAUM’S Act ............................................................................................................ 1

How does a customer know if they need any of the RAY BAUM Enhancements? ... 1
MiVoice BusinessSupportforRAYBAUM'SActSection 506 and Kari's Law ............................................... 2
Solution: MiVoice Business - RAY BAUM High Level Architecture with RedSky...................................... 3
Solution: Requirements for MiVoice Business - RAY BAUM Integration with RedSky ............................ 7
Establishing a Contract with RedSky ........................................................................ 8
Access Control List of the MBG Servers with RedSky ................................... 9
Horizon Mobility Setup - RedSky Portal ..................................................... 10
Solution: How the Integration Works .................................................................................................. 15

Non-fixed Devices .................................................................................................. 15
Collecting Data ........................................................................................... 15
Sending Data to RedSky ............................................................................. 15
Fixed Devices (legacy TDM devices)....................................................................... 16
Collecting Data ........................................................................................... 16
Sending Data to RedSky ............................................................................. 16
Emergency Callback ............................................................................................... 17
Solution: MiVoice Business Location ID Definition .............................................................................. 18
Solution: MiVoice Business Device RAY BAUM Support Summary....................................................... 19
Solution: MiVoice Business Functions with RAY BAUM Support .......................................................... 21
Solution: Mitel Applications with RAY BAUM Support ........................................................................... 22
Solution: Mitel Applications Without RAY BAUM Support .................................................................. 23
Solution: Deployment Diagrams .......................................................................................................... 24

MiVoice Business and MBG in a Customer Site ..................................................... 24
Multiple MiVoice Business Instances Connected to a Single MBG ......................... 24
Multiple MiVoice Business Instances Using a Single MiVoice Business as a Trunking
Gateway to a Single MBG ...................................................................................... 25
MiVoice Business and Two MBGs in a Customer Site ............................................ 26
Multiple MiVoice Business Instances Using Multiple MiVoice Business as a Trunking
Gateway to a Single MBG ...................................................................................... 27
Multiple MiVoice Business Instances Using a Dedicated MiVoice Business as
Gateway to Two MBGs ........................................................................................... 28
Deploying Guide: MiVoice Business SIP Trunking to RedSky (MBG as Outbound-Proxy)...................... 30

Configure MBG SIP Options ................................................................................... 30
Configure MBG Definition for MiVoice Business Instances.................................... 30
Configure MBG SIP Trunking to RedSky ................................................................. 32
Configure MiVoice Business Trunking Gateways to Use MBG as RedSky Outbound
Proxy...................................................................................................................... 33
Configure Non-trunking Gateways to Use MiVoice Business Trunking Gateways to
Access RedSky........................................................................................................ 37
Deployment Guide: Emergency Callbacks............................................................................................ 40
Deployment Guide: Defining Locations ............................................................................................... 42
Deployment Guide: Defining On-Premise Wire Maps .......................................................................... 43
Deployment Guide: Device Overview .................................................................................................. 44

Devices that use CESID (e.g., 69xx, Single Cell DECT, 5623 Wireless)..................... 44
Devices That Use the RedSky MyE911® Application (e.g., MiVoice Business
Console). ................................................................................................................ 53
Devices that Use Geo-location (e.g., MiCollab SIP Softphone Client) ........................ 58
Deployment Guide: 69xx MiNet .......................................................................................................... 63

On Premise ............................................................................................................ 63
Off Premise ............................................................................................................ 63
Deployment Guide: 53xx MINET (5304, 5312, 5320, 5320e, 5330e, 5340e).......................................... 64
On Premise ............................................................................................................ 64
Off Premise ............................................................................................................ 65
Deployment Guide: Legacy MINET 53xx .............................................................................................. 66

On Premise ............................................................................................................ 66
Off Premise ............................................................................................................ 66
Deployment Guide: Legacy MINET (50xx, 51xx, 52xx, 5560 IPT, Navigator) ......................................... 67
On Premise ............................................................................................................ 67
Off Premise ............................................................................................................ 67
Deployment Guide: 5540..................................................................................................................... 68

On Premise ............................................................................................................ 68
Off Premise ............................................................................................................ 69
Deployment Guide: MiVoice Business Console .................................................................................... 70

On Premise ............................................................................................................ 70
Off Premise ............................................................................................................ 71
Deployment Guide: Generic SIP .......................................................................................................... 72

On Premise ............................................................................................................ 72
Off Premise ............................................................................................................ 73
Deployment Guide: Single Cell DECT (SIP 6xx / IP 56xx)....................................................................... 75

On Premise ............................................................................................................ 75
Off Premise ............................................................................................................ 76
Deployment Guide: SIP DECT (6xx) ...................................................................................................... 77
Deployment Guide: RFP 12/14 Single Cell Solution ............................................................................. 81

On Premise ............................................................................................................ 81
Off Premise ............................................................................................................ 82
Deployment Guide: Multi-Cell SIP DECT (6xx)...................................................................................... 82

On Premise ............................................................................................................ 82
Off Premise ............................................................................................................ 82
Deployment Guide: Multi-Cell IP DECT (56xx) ..................................................................................... 84

On Premise ............................................................................................................ 85
Off Premise ............................................................................................................ 85
Deployment Guide: 5634 Wi-Fi ........................................................................................................... 84

On Premise ............................................................................................................ 84
Off Premise ............................................................................................................ 85
Deployment Guide: Legacy SIP (5302, 5505, 5624) .............................................................................. 86

On Premise ............................................................................................................ 86
Off Premise ............................................................................................................ 86
Deployment Guide: MiCollab MINET Soft- phone ................................................................................ 87
On Premise ............................................................................................................ 87
Off Premise ............................................................................................................ 88
Deployment Guide: MiCollab SIP Softphone ....................................................................................... 89

On Premise ............................................................................................................ 92
Off Premise ............................................................................................................ 92
Solution Deployment Guide - MiCollab Web Client ............................................................................. 93

On Premise ............................................................................................................ 96
Off Premise ............................................................................................................ 96
Deployment Guide: MiCollab Desk phone ........................................................................................... 97
Deployment Guide: MiCollab Mobile .................................................................................................. 98
Deployment Guide - 3rd Party WebRTC Clients (via MBG) ................................................................... 99
Deployment Guide - WebRTC Anonymous Calls (via MBG) ................................................................ 100

Limitations ........................................................................................................... 100
Acronyms, Abbreviations, and Glossary ............................................................................................ 101

What's new in this Document
This section describes changes in this document due to new and changed functionality in RAY BAUM'S
Act Solution Deployment Guide for RedSky. The changes are summarized in the following table:
Table 1: Document Version 1.0
Feature/Enhancement Document Updates Location Publish Date
_
_ No changes have been made to May 2023
this document for the 10.0 SP1
release
CHAPTER 1 KARI’S LAW AND RAY BAUM’S ACT
Kari’s Law and RAY BAUM’S Act

In August 2019, the USA government has adopted rules for implementing two federal laws that strengthen
emergency calling: Kari’s Law and Section 506 of RAY BAUM’S Act.
The Multi-line Telephone Systems (MLTS) – Kari’s Law and RAY BAUM’S Act 911 Direct Dialing,
Notification, and Dispatchable Location Requirements is described in the following link.
https://www.fcc.gov/mlts-911-requirements
FAQ about RAY BAUM’s Act can be found in the following link. https://www.fcc.gov/files/mltsfaqspdf RAY
BAUM classifies devices into:
• Fixed MLTS devices - devices that connect to a single end point (e.g., a desk or office phone) and are
not capable of being moved to another endpoint by the end user, although they may be capable of
being moved to a different endpoint by a professional installer or network manager.
• Non-Fixed MLTS devices - devices that the end user can move from one endpoint to another without
assistance.
How does a customer know if they need any of the RAY

BAUM Enhancements?
The primary reason for a customer requiring the RedSky solution to meet RAY BAUM'S requirements is
that their deployment has OFF-PREMISE users/devices, such as Teleworker devices and/or Mitel Phone
Manager PC softphones.
If a customer only has analog ON-PREMISE devices, the RedSky solution is not required and CESID
programming can be done as it is done today. However, the customer may be required to purchase
additional CESIDs (DID numbers) to accommodate their deployment should their office be large enough
to require more granularity in defining a dispatchable location.
If a customer only has ON-PREMISE users/IP devices in their deployment, the RedSky solution is not
required. However, if the customer has IP devices, there are new and existing features on the MIVB,
such as IP Range to CESID(existing) and BSSID to CESID Mappings(new), that may be required to help
track the location of IP devices when they are moved ON-PREMISE.
If a customer is limited to analog ON-PREMISE devices and ON-PREMISE users/IP devices in their
deployment, the above is still applicable and the RedSky solution is not required.
In addition, the customer may be required to purchase additional CESIDs to accommodate their
deployment should their office be large enough to require more granularity in defining the dispatchable
location
If a customer only has only ON-PREMISE users and devices and their office is small enough in area to
only require a single CESID, the RedSky solution is not required, nor the configuration of the MIVB
CESID mapping features to support RAY BAUM’S Act, and they can continue to program the CESID as
they do today.
In this document, Section 506 of RAY BAUM's Act and Kari´s Act is called RAY BAUM'S for
simplification.
1
CHAPTER 2 MIVOICE BUSINESS SUPPORT FOR RAY BAUM'S ACT SECTION 506 AND
KARI'S LAW
MiVoice Business Support for RAY BAUM'S

Act Section 506 and Kari's Law
MiVoice Business, as a MLTS, implements Section 506 of RAY BAUM Act and Kari´s law support in
conjunction with third party Next Generation of 911 emergency services providers in the USA.
NOTE: In this document, Section 506 of RAY BAUM’S Act and Kari´s law is called RAY BAUM for
simplification.
For the MiVoice Business, we have the following device categories:
• Fixed MLTS Devices - Analog Devices
• Non-Fixed MLTS devices - IP Devices, SIP Devices, softphones, all teleworkers, etc.
In order to provide full support of the requirements above, the MiVoice Business is integrated RedSky
as a provider in USA and Canada.
This guide describes the integration between MiVoice Business and RedSky Technologies E911
solutions (https://www.redskye911.com).
2
CHAPTER 3 SOLUTION: MIVOICE BUSINESS - RAY BAUM HIGH LEVEL ARCHITECTURE
WITH REDSKY
Solution: MiVoice Business - RAY BAUM

High Level Architecture with RedSky
MiVoice Business implements RAY BAUM in conjunction with RedSky as the MiVoice Business 911
solution alone does not satisfy the legislated requirements for RAY BAUM for all non-fixed devices.
For Kari’s Law direct dialing of 911, the MiVoice Business can be pre-configured for the direct dialing of
911 (emergency calls), without having to dial any suffix, prefix or access code. The 911 calls are sent via
SIP trunk to RedSky and RedSky will redirect the call to the appropriate Public Safety Answering Point
(PSAP) based on the Civic Address of the location as identified by RedSky. Any Horizon Mobility®
notification methods, including SMS, email, or Emergency On-Site Notification (EON) will meet Kari’s
Law. The MiVoice Business notifications (including Mitel Revolution) provide supplemental information
and are not sufficient to satisfy Kari’s Law on their own.
NOTE: The MiVoice Business solution primarily sends Location identifiers to RedSky during emergency
calls. RedSky will look up these Location identifiers to determine the Civic Address which they then use in
the signaling to the PSAP. RedSky also validates the Civic Address when the location is first created in
their database. Redsky address validation includes all 50 states in the United States, as well as Puerto
Rico, Guam, Virgin Islands and Canada. However, all calls from a Canadian location will first be routed
to the National Call Center to verbally confirm the caller’s location.
With the RAY BAUM’s Act solution the Mitel MiVoice Border Gateway (MBG) is used as SBC (Session
Border Controller) between MiVoice Business and RedSky. If a customer has an existing MBG this can
be upgraded to release 11.3 and used for the connection to RedSky. Additionally, the MBG can be used
for Remote User (Teleworkers). Standard engineering guidelines apply.
The integration described in this guide also requires that the customer has a valid service agreement with
RedSky. Please note that Mitel does not provide this service agreement directly.
RedSky does not have any integrated DID server for Emergency Callbacks. As a result, the MiVoice
Business Solution with RedSky will need to use CPN and DID features of the MiVoice Business to provide
Emergency Callback support. In particular, the recommendation is to have a CPN and DID per user in
order to provide emergency callback to the actual device that made the emergency call.
NOTE: While having a CPN/DID per location may suffice, the emergency callback would only be routed to
a single device for that area, which may not be ideal.
The figure 1, below shows a high-level architectural view of the MiVoice Business RAY BAUM integration
with RedSky using MiVoice Business.
3
WITH REDSKY
The MiVoice Business RAY BAUM solution with RedSky Solution is composed of the following
components:
RedSky
• A valid commercial agreement with RedSky. Part of setting up this agreement involves:
– Pre-authorization of the MBG(s) External Internet address with RedSky
– Identification of the transport protocol to use with RedSky,
• UDP on port 5060
• TCP on port 5060
• TLS v1.2+ on port 5061
– From this agreement, you will need to obtain the following information from RedSky:
i. Pre-authorization of the MBG(s) External Internet address with RedSky
ii. RedSky SIP Gateways - These trunks must be pre-configured and tested during the
implementation and integration between the MiVoice Business and RedSky. This can be
validated by use of a 933 test number.
RedSky Horizon Mobility Portal

The main configuration portal for RedSky.
• Define Users - In particular:
– Emergency On-Site Notification (EON) Users, required for notifications
– Basic User/Enterprise Users, required for devices that will use the MyE911® application for location
identification.
• Define Locations
• Guides to RedSky applications, in particular the RedSky Horizon User Guide, MyE911® User Guides
(for Windows/Mac).
4
WITH REDSKY
• Define the On-Premise wire map (MAC, LLDP, BSSID, IP Ranges) for On-Premise HELD clients
and On- Premise MyE911® application clients.
• Downloadable applications for:
– MyE911® application - RedSky provided application to run along-side select softphone devices.
– Emergency On-Site Notification application - RedSky provided application that provides a
alerts/histories of emergency calls.
Organization ID - This is used by RedSky to isolate one Organization’s locations from another. This
information is also available in the RedSky Portal.
HELD URL - This is used by some devices to update their location directly to RedSky LIS (Location
Information Server).
HELD+ Secret - This is used by RedSky to authenticate client access to the RedSky LIS. This information
is also available in the RedSky Portal.
MBG
• SIP Trunking to/from RedSky
• Network Definition - MiVoice Business Systems
• Teleworker support
MiVoice Business
• Network Elements - SIP Peer for MBG, Outbound Proxy for MBG
• Emergency ARS Dialed Digits - Going out an Emergency ARS Route using SIP Trunks to MBG.
– include 933 for testing
• (optional) ARS Route List to support resilient routing over SIP to multiple MBGs. Each emergency call
route to the MBG must be marked as Emergency.
• (optional) ARS Route List with non-emergency TDM Route. As a last resort (if both SIP Trunks to the
MBGs and/or RedSky SIP Gateways are down).
• DID and CPN Substitution per device (or location) that can make 911 calls.
• SIP Peer Profile dedicated to signaling with RedSky.
• SIP Devices Capabilities - For devices SIP Devices that provide information.
• Class of Service - For devices that are going to use the MyE911application from RedSky.
• Class of Service - For MINET teleworker devices.
MiCollab
• MiCollab Server:
– Defining the Location Service Configuration in MiCollab Server
– Defining the emergency numbers for the MiCollab Mobile SIP softphone (including 911 and 933)
• MiCollab Client:
– Installing the Mitel Network Helper
– Adding/Managing their Location
MiVoice Business Console

• Location Management via MyE911® application from RedSky
The Mitel MiVoice Border Gateway (MBG) is used as SBC (Session Border Controller) between MiVoice
Business and RedSky.
A SIP trunk is setup between MiVoice Business and MBG and between MBG and RedSky.
5
WITH REDSKY
The MiVoice Business contains emergency identification information for select devices that is used with
the overall RAY BAUM’S Act solution. More details on the supported devices and location identification
are provided later in this document.
With Horizon Mobility portal is used to setup the information required to the solution to work properly. The
information required depends on the provider, but some information is mandatory. For example, civic
address, valid DID for callback calls (10 digits), valid DID number, extension number or alternate
identification of a device or a user.
The majority of devices that are supported in the MiVoice Business portfolio are supported for RAY BAUM.
The exception is off premise 52xx and prior generation devices.
Additional MBGs are used for Remote Users (Teleworkers) using 53xx/69xx MINET, MiCollab clients and
SIP Phones (6900 series).
The remainder of this document describes the additional programming requirements for RedSky.
Additional steps are required for the overall solution as a whole but are not specific to RedSky and are
thus outside the scope of this document.
6
CHAPTER 4 SOLUTION: REQUIREMENTS FOR MIVOICE BUSINESS - RAY BAUM INTEGRATION
WITH REDSKY
Solution: Requirements for MiVoice

Business - RAY BAUM Integration with
RedSky
Minimum
Product Minimum SW Release Requirements/Comments
MiVoice Business 9.2 At least one SIP Trunk route is

required, including the SIP
Channel licenses for connecting
to the MBG.
NOTE: While it’s not the
minimum requirements, it is
recommended to have two
MiVoice Business
instances for redundancy.
MBG 11.3 Minimum 1 MBG in the solution
with the appropriate SIP Trunk
licenses.
MiVoice Business
cMBG 11.1 SP1 Minimum 1 MBG in the solution
with the appropriate licenses.
MiVoice Business
MiCollab 9.4 Geo Location Support via HELD
from RedSky’s Location
Information Server
69xx MiNET (6905, 6910, 6920, 1.7 Pop-up support (for supporting
6930, 6940, 6970) teleworker devices)
53xx MiNET 6.5.1 Pop-up support (for supporting
(5304,5312,5320,5320 teleworker devices)
e,5330e,5340e,5540 only)
SIP DECT 6xx 8.3 SP1 Device based provisioning of a
CESID that is to be sent during
calls.
7
ESTABLISHING A CONTRACT WITH REDSKY
WITH REDSKY
Minimum
Product Minimum SW Release Requirements/Comments
IP DECT 56xx (ASCOM) 11.1.6 Device based provisioning of a

CESID that is to be sent during
calls.
RFP 12 Single Cell Solution RTX v530b6 Device based provisioning of a
RFP 14 Single Cell Solution RTX v610b1 CESID that is to be sent during
calls.
5634 Wireless (ASCOM) 3.0.2 Device based provisioning to
enable sending of the MAC
Address of connected Wireless
Base Station during calls.
Establishing a Contract with RedSky

The channel partner/customer must have an agreement with RedSky. They should be prepared with the
following information:
Item Comments
MBG(s) External IP Address RedSky maintains an Access Control List to limit

access to their SIP Gateways. The MiVoice
Business solution will require the MBG(s)
External IP Addresses to be added to the Access
Control List
SIP Transport Protocol RedSky’s Access Control List limits the Transport
Protocol allowed for the SIP Gateway.
Buildings/Locations The number of locations required to satisfy RAY
BAUM’s Law.
HELD Clients These are the number of devices/subscribers that
will provide Geolocation (e.g., MiCollab SIP
Softphones, etc.).
MyE911 application The number of users/devices that will require the

NG911 application (e.g., MiVoice Business
Console, MiCollab MINET Softphones, etc.)
EON clients The number of EON application installs required
to satisfy Kari’s Law.
NOTE: RedSky also provides email/SMS
notifications that do not require EON clients.
During the initial setup with RedSky the following connectivity Worksheet is typically used.
8
WITH REDSKY
Info
IP Address of Termination Point MBG(s) WAN FQDN or IP Address.

This is used by RedSky’s Access Control List
(see below)
Transport Method RedSky only supports a single transport protocol
for their SIP Trunk and will need to be
determined at setup time.
Primary Gateway Identifies the Primary SIP Peer for the MiVoice
Business, and SIP Trunk for the MBG.
Secondary Gateway Identifies the Secondary SIP Peer for the MiVoice
Business, and SIP Trunk for the MBG
Access Control List of the MBG Servers with RedSky

RedSky SIP Gateways will only accept calls from pre-authorized customers. For the MiVoice Business
solution, this means that customers must have RedSky pre-authorize the MBG(s) external IP/FQDN. If the
RedSky SIP Gateway receives a SIP INVITE from an unknown SIP client, a "403", "Forbidden" will be
sent back.
This also must include which Transport Protocol is being used (UDP vs TCP vs TLS 1.2+).
NOTE: For the MiVoice Business solution, the MBG(s) are required to be allowed to RedSky.
9
WITH REDSKY
Horizon Mobility Setup - RedSky Portal

The RedSky Portal is available via the web. The URL will come from the RedSky via a welcome email.
For more detailed information on the use of this portal, see Horizon Mobility® User Guide.pdf available
from RedSky.
This is the main RedSky portal for configuration of the customer’s location information. In order to program
the MiVoice Business solution you will need to:
1. Identify the Organization ID, used when setting up the MiVoice Business SIP Peer Profile, and
MiCollab Server.
2. Identify the HELD URL and HELD credentials for your HELD enabled clients.
10
WITH REDSKY
NOTE:The HELD URL will come from RedSk y via welcome email.
3. Configure Buildings/Locations with the alternate ID using the CESID from the MiVoice Business.
4. Configure the On-Premise wire map via Network Discovery. This is used by On-Premise HELD
and MyE911:registered: clients.
NOTE: RedSky prioritizes the Network Discovery order as: MAC, LLDP, BSSID, IP Ranges
NOTE: The IP Ranges form has two lists:
– Private IP Range - Defines the association between a location and an IP Address range (e.g., the
PC’s IP Address)
– Trusted IP Range - Used by RedSky as an Access Control List to only allow select devices to
connect. This should be the PUBLIC address (e.g., from https://whatismyipaddress.com/).
For more information see Network Discovery Overview manual available in the RedSky portal.
5. Configure Device Users - for MyE911:registered: users (e.g., MiVoice Business Console), and HELD
users (e.g., MiCollab SIP Softphone Clients).
11
WITH REDSKY
6. Configure Emergency On-Site Notifications (EON) Users
a. Add Emergency On-Site Notifications Users - Users that can install/manage the EON client as
well as receive Alerts. An EON User can only be added if you have purchased an Enhanced
Notification License.
b. Add an Alert Subscription - For Kari’s Law, you will need to create a subscription Alert Type of
Emergency Call Received. Others are optional, but highly recommended. Add email and/or SMS
recipients.
c. Add an Alert Template - For Kari’s Law, the standard Emergency Call Alert Template is enough.
12
WITH REDSKY
7. Provide Application installs/guides as needed.
13
WITH REDSKY
14
NON-FIXED DEVICES
CHAPTER 5 SOLUTION: HOW THE INTEGRATION WORKS
Solution: How the Integration Works
Non-fixed Devices
A non-fixed device is a device that the end user can move from one location to another without assistance.
Collecting Data
For non-fixed devices, the MiVoice Business internal logic will check for Geo-location, BSSID, MAC
address, ELIN/CESID, IP address. Additional information can be added in the MiVoice Business
database to complement the information received from the device. The additional information needs to
be added in the system by the system admin.
NOTE: MiVoice Business uses a priority order on the Emergency Info:
• Geolocation – provided by HELD enabled devices.
• BSSID – provided by Wi-Fi Base Stations in the SIP INVITE (PANI header) or 200 OK
• CESID – provided by SIP DECT and IP DECT in the SIP INVITE (FROM header) or 200 OK
• L2 to CESID
• Manual/Automatic CESID
• Zone CESID(IP to Zone to CESID Mapping and Zone to CESID Mapping)
• Default CESID (should not be used as it is probably not sufficient to satisfy the US Law).
Sending Data to RedSky

After MiVoice Business has collected the information from the device side, it builds the information to be
sent in the SIP trunk, including the appropriate SIP headers required by the provider (based on the SIP
Peer configuration).
After that, the call is sent to MBG, which will transparently pass through the supported SIP Headers to
RedSky.
To conclude the process, RedSky will validate the information received and will take the appropriate
action, if data is correct the call is sent directly to the PSAP (Emergency Center). If the information is not
correct, then the call is redirected to the National Call Center for further triage. These calls to the
National Call Center incur an extra cost. In addition, all calls from a Canadian location will first be routed
to the National Call Center to verbally confirm the caller’s location, but these calls do not incur an extra
cost.
15
FIXED DEVICES (LEGACY TDM DEVICES)
NOTE: For emergency calls from Canadian locations RedSky will direct the call first through a national
operator to verify the caller’s location and will transfer the call to the appropriate PSAP (with the location
provided by RedSky).
Fixed Devices (legacy TDM devices)

Fixed device is a device that cannot be moved to another place in the enterprise without assistance from
a professional installer or network manager.
Collecting Data
For fixed devices, as no information is provided by the device the MiVoice Business will use the
programmed CESID. This information needs to be added in the system by the system admin.
Sending Data to RedSky

After MiVoice Business has collected the information from the device side, it builds the information to be
sent in the SIP trunk, including the appropriate SIP headers required by RedSky.
After that, the call is sent to MBG which will transparently pass through the supported SIP Headers to
RedSky.
To conclude the process, RedSky will validate the information received and will take the appropriate
action. If data is correct the call is sent directly to the PSAP (Emergency Center). If the data is not correct,
then the call is redirected to the National Call Center for further triage.
NOTE: Calls that are redirected to the National Call Center will be an extra cost to the customer.
16
EMERGENCY CALLBACK
Emergency Callback
Previously the CESID was considered a Location identifier and an Emergency Callback Number. For the
RAY BAUM enabled SIP Trunks, the MiVoice Business will separate the two concepts:
• CESID remains the Location identifier for most devices (i.e., except Geo-Location enabled devices,
and softphones that will use a RedSky provided application to provide location).
• The CPN Substitution/DID or DN of the device will be used to support Emergency Callback (required
for RedSky).
RedSky does not support emergency callbacks and requires that the PSAP route emergency calls back
through the public PSTN.
17
CHAPTER 6 SOLUTION: MIVOICE BUSINESS LOCATION
ID DEFINITION
Solution: MiVoice Business Location ID

Definition
The Location ID is a reference/identification used to identify a device or several devices in the MiVoice
Business that is to be sent to RedSky and will (for the most part) be the CESID assigned to the device.
The
MiVoice Business provides forms for various methods of associating a CESID:
• L2 to CESID mapping - Associates a device connected to a Layer 2 switch (either via LLDP-MED, CDP
or STP) with a given CESID. This is the preferred method for associating a CESID with a device
because it is based on the physical connection rather than on a logical one. In the CESID
assignment form, the CESID Updating field should be set to Automatic. However, this option
requires specialized hardware, which might not be available for all devices.
• BSSID to CESID mapping - Allows a MAC address of a Wireless Access Point (WAP) to be associated
with a CESID. This allows the MiVoice Business to find the associated MAC address. This option
requires manual updating whenever the Wireless Access Point is moved.
• IP to Zone to CESID mapping - Allows a device in each IP range to be associated with a CESID (by
associating the IP range to a Zone in the Location Specification form and then assigning a CESID to
the Zone in the Network Zone form). This option requires that the IP Address ranges can be
sufficiently segmented to provide sufficient granularity to satisfy RAY BAUM requirements.
• Zone to CESID mapping – Similar to IP to Zone to CESID mapping, except the Zone is not
determined by the IP address range in the Location Specification form, but rather the zone statically
assigned to the device. This option is not recommended for non-fixed IP devices because if the
device is moved to another zone, the move will not automatically be detected.
• CESID Assignment - Allows a device to be assigned a CESID directly, where the CESID Updating
field should be set to Manual. NOTE: Hot Desk Users will use the CESID of the registered directory
number of the based device (RegDN). This option should only be used by fixed devices, such as
analog devices, or teleworkers.
NOTE: Devices that support HELD will obtain their Location ID directly from RedSky, and will be sent
through the MiVoice Business, as such there doesn’t need to be any Location ID programmed on the
MiVoice Business. The DN (or CPN) will be used to link the device to the location.
Devices that support sending the CESID/ELIN directly are programmed on the device and will be sent
through the MiVoice Business. As such there doesn’t need to be any Location ID programmed on the
MiVoice Business. However, the CESID must match a RedSky Location.
Devices that support MyE911 application will update the location directly from the application itself and
will not need any Location ID programmed on the MiVoice Business. The DN (or CPN) will be used to link
the device to the location.
18
CHAPTER 7 SOLUTION: MIVOICE BUSINESS DEVICE RAY BAUM
SUPPORT SUMMARY
Solution: MiVoice Business Device RAY

BAUM Support Summary
The following table is a list of Supported Devices, and the available options they have for supporting RAY
BAUM. Details on how to actually program each option follows later in the document.
Device On-Premise Off-Premise (teleworker)
69xx MINET L2 to CESID mapping CESID Assignment

IP Address to CESID mapping
53xx MINET L2 to CESID mapping CESID Assignment
(5304, 5312, 5320, 5320e, IP Address to CESID mapping
5330e, 5340e)
Legacy 53xx MINET L2 to CESID mapping Not recommended
(not covered above) IP Address to CESID mapping
Legacy MINET (50xx, 51xx, L2 to CESID mapping Not recommended
52xx), 5560 IPT, Navigator IP Address to CESID mapping
NOTE: Legacy MINET devices
do not support LLDP-MED
5540 L2 to CESID mapping CESID Assignment
IP Address to CESID mapping
MiVoice Business Console MyE911® Application IP to Zone MyE911
to CESID Mapping
Generic SIP Device Geo-Location Geo-Location
NOTE: Mitel will need to certify CESID provided by the device CESID provided by the device
the solution with any Generic BSSID to CESID Mapping BSSID to CESID Mapping
SIP Device. IP Address to CESID mapping MyE911® Application
MyE911® Application
Single Cell DECT CESID provided by the device CESID provided by the Device
(6xx/56xx in a single node IP Address to CESID mapping
setup)
RFP 12/14 Single Cell CESID provided by the device CESID provided by the device
Solution (Programmed as IP Address to CESID mapping
Generic SIP on the MiVoice
Business)
Multi cell DECT 6xx CESID provided by the Device CESID provided by the Device
Multi cell DECT 56xx CESID provided by the Device CESID provided by the Device
5634 Wi-Fi BSSID to CESID Mapping BSSID to CESID Mapping
Legacy SIP (5302, 5505, IP Address to CESID mapping Not recommended
UC360, 5624)
19
CHAPTER 7 SOLUTION: MIVOICE BUSINESS DEVICE RAY BAUM
SUPPORT SUMMARY
Device On-Premise Off-Premise (teleworker)
MiCollab MINET Softphone IP to Zone to CESID MyE911® Application

(5020) Mapping MyE911®
Application
MiCollab SIP Softphone (UC Geo Location Geo Location
Endpoint)
MiCollab Web Client Geo Location Geo Location
MiCollab Deskphone Depends on the deskphone Depends on the deskphone
type type
MiCollab on Mobile Uses Native Dialer Uses Native Dialer
Analog CESID Assignment Manual CESID
SIP ATA (Analog Terminal See Generic SIP See Generic SIP
Adaptors)
3rd Party WebRTC Client (via See Generic SIP See Generic SIP
MBG)
WebRTC Anonymous Call (via -- Dialing Not expected/supported.
MBG) No additional location
information is being sent.
20
CHAPTER 8 SOLUTION: MIVOICE BUSINESS FUNCTIONS WITH RAY
BAUM SUPPORT
Solution: MiVoice Business Functions with

RAY BAUM Support
Beyond the devices, the MiVoice Business supports many functions that might be used to make an
emergency 911 call. The supported MiVoice Business functions:
MiVoice Business Feature Description
Multicall/Keyline Depends on the physical device.

Auto DN Registration Depends on the physical device type
MINET Hot Desking Uses the CESID of the RegDN
NOTE: The HDU obtains the CESID from the
RegDN at login time. If the CESID of the RegDN
is changed, the Hot Desk User should be logged
out and logged back in.
SIP Hot Desking Depends on the SIP Device that you are logged
onto.
External Hot Desking Will use the incoming CLI if they are proxied on a
PUBLIC trunk.
If they are proxied on a PRIVATE trunk, then we
will use the CESID programmed against the
EHDU.
MiTAI Depends on the device that is being monitored.
MDUG/PRG Depends on the device itself (not the MDUG/PRG
Pilot).
CPN/DID should be the PRG/MDUG pilot
Suites Depends on the device itself (not the Suite)
CPN/DID should be the Suite Pilot
21
CHAPTER 9 SOLUTION: MITEL APPLICATIONS WITH RAY BAUM SUPPORT
Solution: Mitel Applications with RAY BAUM

Support
MiVoice Business is integrated with different Mitel Application with RAY BAUM support. Supported
applications with RAY BAUM support.
• MiVoice Business Console
• MiCollab
• MBG – MiVoice Border Controller
• MiCC-B - MiContact Center Business for MiVoice Business
• MiCC-B - MiContact Center Business for SIP
• SIP DECT
• IP DECT (Ascom) OIG (via MiTAI)
• RFP 12/14 Single Cell Solution
22
CHAPTER 10 SOLUTION: MITEL APPLICATIONS WITHOUT RAY BAUM SUPPORT
Solution: Mitel Applications Without RAY

BAUM Support
There are some Mitel applications that does not require RAY BAUM support, they are:
• MiCAM - MiCollab Advanced Messaging
• MIR - Mitel Interaction Recording
• NPM – NuPoint Unified Messaging
• MPA - Mitel Performance Analytics
• Mitel Revolution
23
MIVOICE BUSINESS AND MBG IN A CUSTOMER SITE
CHAPTER 11 SOLUTION: DEPLOYMENT DIAGRAMS
Solution: Deployment Diagrams

This chapter covers possible deployments setup between MiVoice Business and RedSky.
MiVoice Business and MBG in a Customer Site

The architecture view below shows the most basic setup between MiVoice Business and RedSky. An
emergency route is setup over SIP trunk between MiVoice Business and a single MBG, then MBG has
two SIP trunks towards RedSky SIP gateways for redundancy purpose. The double SIP trunks between
the customer site and RedSky are highly recommended.
Refer to MBG documentation for MBG Redundancy SIP trunk configuration.
Multiple MiVoice Business Instances Connected to a Single

MBG
The architecture view below shows a more complicated setup between multiple MiVoice Business
instances and a single MBG and RedSky. In this case, each MiVoice Business is setup with an
emergency route over SIP Trunk directly to the MBG, then MBG has two SIP trunks towards RedSky SIP
gateways for redundancy purpose. The double SIP Trunks between the customer site and RedSky are
highly recommended.
24
MULTIPLE MIVOICE BUSINESS INSTANCES USING A SINGLE MIVOICE BUSINESS AS A TRUNKING GATEWAY TO A SINGLE MBG
NOTE: In this case, a single IP Trunk between the MiVoice Business instances is all that is necessary,
since every MiVoice Business will have its own emergency route out to the MBG. This method may cost
more as you will need SIP Trunk licenses from each MiVoice Business.
Multiple MiVoice Business Instances Using a Single

MiVoice Business as a Trunking Gateway to a Single MBG
instances and a single MBG and RedSky that reduces the SIP Trunks (and thus licenses) required. In
this case, multiple MiVoice Business are setup with an emergency IP Trunking route to a designated
MiVoice Business setup with an emergency route over SIP Trunk directly to the MBG, then MBG has two
SIP trunks towards RedSky SIP gateways for redundancy purpose. The double SIP Trunks between the
customer site and RedSky are highly recommended.
25
MIVOICE BUSINESS AND TWO MBGS IN A CUSTOMER SITE
NOTE: In addition to the normal IP Trunk route between MiVB1 and MiVB2, the MiVB2 will need a
dedicated emergency IP Trunk route to MiVB1.
MiVoice Business and Two MBGs in a Customer Site

The architecture view below shows a redundant setup between MiVoice Business and RedSky. SIP
trunks are setup between MiVoice Business and the two MBGs, then each MBG has two SIP trunks
towards RedSky SIP gateways for redundancy purpose. The double SIP trunks between the customer
site and RedSky are highly recommended.
26
MULTIPLE MIVOICE BUSINESS INSTANCES USING MULTIPLE MIVOICE BUSINESS AS A TRUNKING GATEWAY TO A SINGLE MBG
Multiple MiVoice Business Instances Using Multiple

MiVoice Business as a Trunking Gateway to a Single MBG
The architecture view below shows a redundant setup between multiple MiVoice Business and multiple
MBGs and RedSky. SIP trunks are setup between MiVoice Business and the two MBGs, then each MBG
has two SIP trunks towards RedSky SIP gateways for redundancy purpose. The double SIP trunks
between the customer site and RedSky are highly recommended.
27
MULTIPLE MIVOICE BUSINESS INSTANCES USING A DEDICATED MIVOICE BUSINESS AS
CHAPTER 11 GATEWAY TO TWO MBGS
SOLUTION: DEPLOYMENT DIAGRAMS
NOTE: In this case, a single IP Trunk between the MiVoice Business instances is all that is necessary,
since every MiVoice Business will have its own emergency route out to the MBG. This method may cost
more as you will need SIP Trunk licenses from each MiVoice Business.
Multiple MiVoice Business Instances Using a Dedicated

MiVoice Business as Gateway to Two MBGs
instances and a multiple MBGs and RedSky that reduces the SIP Trunks (and thus licenses) required. In
this case, multiple MiVoice Business are setup with an emergency IP Trunking route to designated
MiVoice Business setup with an emergency route over SIP Trunk directly to the MBG, then MBG has two
SIP trunks towards RedSky SIP gateways for redundancy purpose. The double SIP Trunks between the
customer site and RedSky are highly recommended.
28
MULTIPLE MIVOICE BUSINESS INSTANCES USING A DEDICATED MIVOICE BUSINESS AS
CHAPTER 11 GATEWAY TO TWO MBGS
SOLUTION: DEPLOYMENT DIAGRAMS
NOTE: In addition to the normal IP Trunk route between the MiVoice

Business instances, non-trunking
gateway MiVoice Business instances will need an emergency IP Trunk route to MiVB1 and MiVB2
29
CONFIGURE MBG DEFINITION FOR MIVOICE BUSINESS INSTANCES
CHAPTER 12 DEPLOYING GUIDE: MIVOICE BUSINESS SIP TRUNKING
TO REDSKY (MBG AS OUTBOUND-PROXY)
Deploying Guide: MiVoice Business SIP

Trunking to RedSky (MBG as Outbound-
Proxy)
NOTE:RedSky only supports outbound calls and does not support inbound calls. Additional SIP Trunks
may be required for general PSTN access, including emergency callback numbers.
Configure MBG SIP Options
The SIP Options above can be found under System -> Settings - > SIP options.
Ensure that the Access Profile values are set to Public for the Protocols you plan to support.
Configure MBG Definition for MiVoice Business Instances
NOTE: This doesn’t have to be all MiVoice Business instances, as that would require SIP Trunk
licenses on each MiVoice Business. However, it is recommended that at least a pair of MiVoice
Business instances be able to route directly to the MBG(s). NOTE: The MBG should set the MiVoice
Business’s SIP capabilities as “UDP, TCP, TLS”
30
CONFIGURE MIVOICE BUSINESS TRUNKING GATEWAYS TO USE MBG AS REDSKY OUTBOUND PROXY
CHAPTER 12 DEPLOYING GUIDE: MIVOICE BUSINESS SIP TRUNKING TO REDSKY (MBG AS OUTBOUND-PROXY)
Configure MBG SIP Trunking to RedSky
NOTE: Transport protocol

MBG does not support translating transport protocols to a given SIP Service provider. So, the MiVoice
Business (Network Elements for both the MBG Outbound Proxy and RedSky), MBG (MiVoice Business
+ SIP Trunk), for Redsky must all use the same protocol for the given communication path.
If there is a need to support SIP Service Provider with other protocols as well, you can.
• On the MiVoice Business create separate Outbound Proxies for each Transport Protocol (TCP,
UDP, TLS) to the MBG(s).
• On the MBG define the ICP to allow all the SIP capabilities (i.e., “UDP, TCP, TLS”).
• On the MiVoice Business create separate SIP Peer Profiles for each SIP Gateway with the
appropriate Transport Protocol and corresponding Outbound Proxy.
NOTE: TLS Support (Port 5061)

When using TLS support RedSky will validate the SIP certificate used by MBG when using TLS as the
Transport Protocol. By default, the MBG will use a self-signed certificate which must be replaced with a
publicly signed certificate using MSL --> Web Server → Configure Web Server.
32
Configure MiVoice Business Trunking Gateways to Use

MBG as RedSky Outbound Proxy
Create an Outbound Proxy Network Element for the MBG. Separate Network Elements are required if
there are multiple MBGs being used.
NOTE: Ensure that the MBG Outbound Proxy uses the same Transport Protocol as the RedSky SIP Trunk.
NOTE:If Multiple Transport Protocols are required (i.e., for other SIP Gateways), then configure multiple
outbound proxies to the same MBG for each protocol.
Create a Network Element(s) for the RedSky’s SIP Gateways. Separate Network Elements are required
if the RedSky provider has multiple SIP Gateways.
33
NOTE: Ensure that the MBG Outbound Proxy uses the same Transport Protocol as the RedSky SIP Trunk.
Create a SIP Peer Profile for RedSky SIP Gateway(s) specifying the MBG(s) as the outbound proxy.
Separate SIP Peer Profiles are required to support resilient routing to the primary and secondary RedSky
SIP Gateways.
34
MiVoice Business Tab Setting

Field
SIP Peer Profile Basic Mandatory. Enter an alphanumeric string up to nine
Label characters for the SIP Peer Profile.
Network Element Basic Mandatory. Select the appropriate Network Element name
(programmed in the Network Elements form) from the pull-
down list.
Maximum Basic Depending how a customer has configured these values
Simultaneous Calls on their SIP trunks today, these may need to be modified
and Minimum on existing SIP Peer Profiles, not just the new ones for the
Reserved Call Vendors.
Licenses If a customer Reserved all their SIP trunks, they either
need to get more licenses, use the “free” ones, or
unreserve an amount they would like for emergency calls.
If they have left some Unreserved, the customer may want
to unreserve some more.
Outbound Proxy Basic The Network Element for the MBG Outbound Proxy
Server
Private SIP Trunk Call Routing This existing field may need to be configured to determine if
we are sending Internal vs External numbers to the
Vendors. The current recommendation is these trunks
should always be PRIVATE. The only reason to keep
PUBLIC would be if EVERY SINGLE USER and DEVICE
on the MiVoice Business has their own unique DID number.
Trunk Group Label Signaling and Enter the trunk group label to insert into the Contact header
Header of SIP URIs. The "tgrp" tag is defined in RFC 4904.
Manipulation
Emergency Call Signaling and Use E911 Headers
Headers Header
Manipulation
Multilingual Name Signaling and Optional if customer wants to see the UTF-8 names of
Display Header users in the Redsky notifications.
Manipulation
User-Defined Signaling and E911-Organization-ID
Header Name Header
Manipulation
User-Defined Signaling and Organization ID provided by RedSky and available on the
Header Value Header Redsky Portal Dashboard in the IDs and Access Codes
Manipulation pane - > HELD Company ID
35
Define Emergency ARS Routes for each of the RedSky SIP Peer Profiles. Separate ARS Routes are
required to support resilient routing to the primary and secondary RedSky SIP Gateways.
NOTE: ARS Routes are subject to COR restriction, so if you are restricting a device from calling an
Emergency Route, the call will fail.
NOTE: For a full resiliency coverage, it is recommended that have at least 2 MiVoice Business Trunking
Gateways, and each should have 4 SIP Peer Profiles:
• RedSky1 using MBG1 as the outbound proxy
• RedSky2 using MBG2 as the outbound proxy.
The SIP Peers should have a low Invite Ringing Response Timer (1-2 seconds) under the timer tab.
Programming Emergency ARS Routes for each of these SIP Peer Profiles is required.
36
Adding each of these ARS Routes to the Route List is required.

(RECOMMENDED) Define ARS Route List with the Emergency ARS Routes for the RedSky SIP Peer
Profiles in order.
NOTE: As a “last resort” non-emergency ARS route can be added AFTER all RedSky Routes to handle a
case where RedSky is completely down. These final ARS Routes in the list should be non-Emergency
because the Emergency information programmed on the MiVoice Business is incomplete and cannot be
relied upon for normal calls over the PSTN.
37
CONFIGURE NON-TRUNKING GATEWAYS TO USE MIVOICE BUSINESS TRUNKING GATEWAYS TO ACCESS REDSKY
Define ARS Route Dialed Digits to use the previously defined ARS Route List. Ensure that 911 is dialable
without any prefix or suffix digits.
NOTE: IFT/EFT sites may want to add a 933 ARS route for testing purposes.
Configure Non-trunking Gateways to Use MiVoice

Business Trunking Gateways to Access RedSky
Create Emergency IP Trunking ARS Route to the MiVoice Business Trunking Gateway, this is on top of
any IP Trunking for regular calls. Separate ARS Routes are required for resilient routing to the MiVoice
Business Trunking Gateways.
37
NOTE: Direct IP Trunking is not required (IP/XNET Trunk Groups can be used but is more finicky to
program).
(Optional) Define ARS Route List. Recommended to provide resilient routing to MiVoice Business
Trunking Gateway(s).
Define ARS Route Dialed Digits to use the previously defined ARS Route List.
38
39
CHAPTER 13 DEPLOYMENT GUIDE: EMERGENCY CALLBACKS
Deployment Guide: Emergency Callbacks

RedSky provides outgoing SIP Trunk support only (i.e., MiVoice Business to MBG to RedSky to PSAP
only). In order to provide Emergency Callback support, the PSAP must callback via the public PSTN
Network. As a result, for RedSky, we require CPN Substitution and matching DID to be programmed
based on their customer needs.
• CPN Substitution is used to identify the Calling Party Number and will be used as the Emergency Call-
back number when using RedSky.
NOTE: The same CPN will be used for non-emergency and emergency calls.
• The DID number is used by the MiVoice Business to route an incoming call based on the Digits
Dialed.
For a proper callback to occur the CPN sent to RedSky must be routable back to the MiVoice Business
where we will match the called digits to the DID number and route the call to the programmed destination.
It is recommended to have a unique CPN/DID for each Device/User to ensure that the emergency callback
is routed back to the device/user that originated the emergency call.
On the MiVoice Business, program the CPN Substitution for the device in the Associated Directory
Number form(or alternatively the User and Services Configuration form). This is to program a number
directly to an extension. CPN Substitution can also be configured in the Zone Assignment or DID Ranges
for CPN Substitution form if it is desired the emergency callback, should the emergency call drop, ring
another more central number.
40
CHAPTER 13 DEPLOYMENT GUIDE: EMERGENCY CALLBACKS
On the MiVoice Business, program the DID for the device in the Direct Inward Dialing Service form (or
alternatively the User and Services Configuration form)
NOTE: Since the MiVoice Business RedSky solution requires using the CPN Substitution number for
Emergency Call- back, the MiVoice Business Emergency DID Routing feature should be disabled in the
Shared System Options form. The Emergency DID Routing feature uses the CESID the Emergency
Callback, which is not what we want.
NOTE: If Direct Inward Dialing Service is used, the Trunk Attributes for the incoming trunk must have Direct
Inward Dialing Service enabled.
41
CHAPTER 14 DEPLOYMENT GUIDE - DEFINING LOCATIONS
Deployment Guide: Defining Locations

The MiVoice Business RedSky solution requires that the administrator define buildings/locations as
required in the RedSky Portal. These locations (Location Identification Type = alternate ID) will be
typically linked to a MiVoice Business CESID.
NOTE: The administrator is responsible for ensuring that the MiVoice Business programming aligns with
the RedSky programming.
42
CHAPTER 15 DEPLOYMENT GUIDE - DEFINING ON-PREMISE WIREMAPS
Deployment Guide: Defining On-Premise

Wire Maps
The MiVoice Business RedSky solution for On-Premise HELD clients (e.g., MiCollab SIP Softphone,
etc.) and MyE911® clients (e.g., MiVoice Business Console, MiCollab MINET Softphones) will use
RedSky’s Network Discovery configuration to identify their location.
• MAC Address - Used to associate a location to a device based on MAC Address
• LLDP - Used to associate a location to a device based on wired connectivity to a L2 network switch.
• BSSID - Used to associate a location to a device based on the MAC address of a Wireless Access
Point.
• IP Ranges - Used to associate a location to a device based on IP Address configuration.
43
DEVICES THAT USE CESID (E.G. 69XX, SINGLE CELL DECT, 5623 WIRELESS)
CHAPTER 16 DEPLOYMENT GUIDE - DEVICE OVERVIEW
Deployment Guide: Device Overview

Basically, this boils down to 3 different configuration models, depending on the device and its location.
Which devices uses which specific configuration model is detailed later in the document.
Devices that use CESID (e.g., 69xx, Single Cell DECT, 5623
Wireless)
Step 1: If required add a new building in the RedSky Portal.
NOTE: When Override Organization Name is enabled, users can provide a different name for the building
or additional information that will be shown at the public safety answering point (PSAP) when a 911 call
is placed from any of its locations. The Organization Administrator can change the Name, Address,
Supplemental Information, and the Organization Name Override value.
Step 2: Add a Location in the RedSky Portal.
RedSky Device User ID Field Notes
Identification Type Use Alternate ID

Alternate ID CESID from the MiVoice Business/device
Location Information Description of location (e.g.,
Room/Floor/Apt/Suite).
44
Step 3: Program the CESID information in the MiVoice Business.
45
CESID Alternatives Configuration Steps
CESID sent by the Program the CESID on the SIP device.

device (limited to SIP NOTE: Configuration will depend on the device type.
devices) On the MiVoice Business, enable Emergency Info Provided by Device in
the SIP Device Capabilities
NOTE: Valid CESIDs are digit strings of 1-12 digits and length and 0-9 are
the only valid digits. While these devices themselves may allow other
characters as they support multiple Mitel PBXs, the MIVOICE
BUSINESS will not pass along the CESID it does not meet the MiVoice
Business criteria.
46
BSSID to CESID Mapping (limited On the 5634 devices, enable the MAC Address of the Wireless
to 5634) Access Point to be sent on all calls.
NOTE: Configuration will depend on the device type.
On the MiVoice Business, enable Emergency Info Provided by
Device in the SIP Device Capabilities.
On the MiVoice Business program the BSSID to CESID Mapping
47
L2 to CESID Mapping (limited to On the MiVoice Business, configure the L2 Connectivity Detection
MINET sets) Protocol in the Default CESID form. The available options are
STP, CDP, or LLDP.
NOTE: Not all MINET devices support LLDP
On the MiVoice Business, configure the L2 to CESID Mapping
NOTE: The MiVoice Business only supports one device per L2 Port.
48
IP to Zone to CESID Mapping • On the MiVoice Business, define the IP Address range to
Zone ID in either the Location Specification or Location
Specific IPv6 form.
49
On the MiVoice Business, configure the CESID against the Zone

in the Network Zones form.
On the MiVoice Business, set the Zone Assignment to Default for

the device in the User and Service Configuration form(or Station
Attributes form)
50
Zone to CESID Mapping On the MiVoice Business, configure the CESID against the
Zone in the Network Zone Assignment form.
On the MiVoice Business, set the Zone Assignment to Default or

Manual for the device in the User and Service Configuration form.
51
CESID Assignment On the MiVoice Business, program the CESID against the device
in the CESID Assignment form.
Some Off-Premise MINET devices (e.g., select 53xx, 69xx) will

also need to enable the Device Move Detection Class of Service
Option. When enabled, a pop-up will be presented to the end
user indicating the device has detected a possible change of
location and to contact their administrator to provide the new
location. Once acknowledged by the end user, the MiVoice
Business will generate an Audit log indicating which device
acknowledged the move.
Step 4: On the MiVoice Business, program the CPN Substitution for the device
52
Step 5: On the MiVoice Business, program the DID for the device.
NOTE: Using System Speed Calls is another means of providing DID access.
53
DEVICES THAT USE THE REDSKY MYE911® APPLICATION (E.G. MiVoice Business Console)
Devices That Use the RedSky MyE911® Application

(e.g., MiVoice Business Console).
Step 1: Program the On-Premise wire map via Network Discovery.
Network Discovery Mode Comments
MAC Address Used to associate a location to the MAC Address

of a device
LLDP Used to associate a location to the L2
Chassis/Port of a Layer 2 enabled network
switch.
MyE911 application must enable LLDP during the
installation. If enabled during the installation,
LLDP becomes a toggleable setting.
BSSID Used to associate a location to the MAC Address
of a Wireless Access Point
IP Ranges Used to associate a location to an IP Address
range of a given device.
The MyE911® Application can operate in two modes, and will automatically select the appropriate mode:
• On-Premise, where the application can query the RedSky LIS for a known location (see Network
Discovery Mode)
• Off-Premise, where the application can update the RedSky LIS (Location Information Server) with the
location information entered by the user.
53
The MyE911® Application will obtain the location information from the RedSky LIS and associate the
location to the RedSky User associated when the application was installed. The softphone will be linked
to the RedSky User based on the Identification Type.
Step 2: Program a User in the RedSky Portal.
54
RedSky Device User ID Field Corresponding MiVoice Notes

Business Field
Email -- Used by MyE911 application
during registration to identify the
Device User.
First Name -- First name of the user. (Does
not have to align with
MiVoice Business)
55
RedSky Device User ID Field Corresponding MiVoice Notes

Business Field
Last Name -- Last name of the user. (Does
not have to align with
MiVoice Business)
Identification Type Device User ID or Phone Use Device User ID if there is
Number no CPN/DID number for the
device on the MiVoice
Business. Otherwise, use
Phone Number.
Phone Number CPN of the device
Callback Number -- Not used, as the MiVoice
Business will provide the
callback number
Device User ID DN of the device If the device is a member of a
PRG/MDUG, then the CPN or
DN of the PRG/MDUG pilot
should be used.
NOTE: If the customer has network of multiple MiVoice Business clusters, care needs to be taken on how
to handle the Primary Node ID(PNI). If using the DN of the device, the Device User ID should be PNI
prefixed unless you have the Strip PNI SIP Peer option enabled.
NOTE: If using Device User ID, the SIP Peer Profile(s) for RedSky should be set to Private.
Step 3: On the MiVoice Business, enable CESID not required for Emergency Calls on the device’s COS
option.
Step 4: On the MiVoice Business, program the CPN Substitution for the device.
56
NOTE: Using System Speed Calls is another means of providing DID access.
57
DEVICES THAT USE GEO-LOCATION (E.G. MICOLLAB SIP SOFTPHONE CLIENT)
Step 6: Install the MyE911application on the same hardware running the softphone client. For more
instructions on the MyE911 application, see MyE911® for Windows User Guide.pdf, MyE911® for
macOS Guide.pdf, or MyE911® for Mobile User Guide.pdf
Devices that Use Geo-location (e.g., MiCollab SIP Softphone

Client)
Step 1: Program the On-Premise wire map via Network Discovery.
Network Discovery Mode Comments
MAC Address Used to associate a location to the MAC Address

of a device
LLDP Used to associate a location to the L2
Chassis/Port of a Layer 2 enabled network
switch.
BSSID Used to associate a location to the MAC Address
of a Wireless Access Point
IP Ranges Used to associate a location to an IP Address
range of a given device.
Devices that use HELD (http enabled location data) to get Geo-Location will automatically be detected in
the RedSky Portal.
NOTE: If there are no Network Discovery entries for a given HELD device, the HELD device will create an
automatic entry from the HELD client. This entry will persist in the RedSky database and take precedence
over any Network Discovery entries.
58
These HELD devices can operate in two modes:

• On-Premise, where they can query the RedSky LIS for a known location (see Network Discovery
Mode)
• Off-Premise, where they can update the RedSky LIS (Location Information Server) with the location
information entered by the user.
The device will obtain the location information from the RedSky LIS and then send this Geo-Location
information to the MiVoice Business at call time, and the MiVoice Business will transparently pass Geo-
Location onto RedSky.
59
Step 2: Configure the device’s integration with the RedSky LIS.

NOTE: Configuration will depend on the actual device.
Step 3: On the MiVoice Business, enable Emergency Info Provided by Device in the SIP Device
Capabilities
60
Step 4: On the MiVoice Business, program the CPN Substitution for the device
61
Using System Speed Calls is another means of providing DID access.
62
ON PREMISE
CHAPTER 17 DEPLOYMENT GUIDE: 69XX MINET
Deployment Guide: 69xx MiNet

See the general Solution Deployment Guide - Devices for more details on programming each option.
On Premise
Options Available Programming Steps
L2 to CESID Mapping (RECOMMENDED) RedSky:

• Program a Location to match the device’s
CESID.
MiVoice Business:
• Define the CESID Mapping
• Define the Emergency Callback handling
(CPN/DID)
Device:
None.
Off Premise
CESID Assignment RedSky:

• Program a Location to match the device’s
CESID.
MiVoice Business:
• Define the CESID
• Enable the Device Move Detection COS
option. When enabled, the device user
will be notified of a possible device move
and will instruct them to contact the
Administrator to correct the location in
Redsky portal. The MiVoice Business
will generate an Audit Trail when the
notification has been acknowledged by
the user
(CPN/DID)
Device:
• None.
63
ON PREMISE
CHAPTER 18 DEPLOYMENT GUIDE: 53XX MINET (5304, 5312, 5320, 5320E, 5330E, 5340E)
Deployment Guide: 53xx MINET (5304, 5312,

5320, 5320e, 5330e, 5340e)
On Premise

• Program a Location to match the CESID of the
L2 Port.
MiVoice Business:
• Define the L2 to CESID Mapping
(CPN/DID)
Device:
None
IP to Zone to CESID Mapping RedSky:
• Program a Location match the CESID of the
Zone.
MiVoice Business:
• Define the IP Address Range to Zone in
Location Specification form
• Define Zone CESID in Network Zones
form
• Set device’s Zone Assignment Method to
Default in the User and Services
Configuration form(or Station Assignment
form.
(CPN/DID)
Device:
• None
64
OFF PREMISE
CHAPTER 18 DEPLOYMENT GUIDE: 53XX MINET (5304, 5312, 5320, 5320E, 5330E, 5340E)
Off Premise

device
MiVoice Business:
• Define the CESID of the device.
the user
(CPN/DID)
Device:
• None
65
ON PREMISE
CHAPTER 19 DEPLOYMENT GUIDE: LEGACY MINET 53XX
Deployment Guide: Legacy MINET 53xx
On Premise

L2 Port.
MiVoice Business:
(CPN/DID)
Device:
• None

Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
• None
Off Premise
Not recommended as these devices do not support Device Move Detection
66
ON PREMISE
CHAPTER 20 DEPLOYMENT GUIDE: LEGACY MINET (50XX, 51XX, 52XX, 5560 IPT, NAVIGATOR)
Deployment Guide: Legacy MINET (50xx,

51xx, 52xx, 5560 IPT, Navigator)
On Premise

L2 Port.
MiVoice Business:
• Define the L2 to CESID Mapping to be CDP
(These legacy MiNET devices do not support
LLDP-MED).
(CPN/DID)
Device:
• None

Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
• None
Off Premise
Not recommended as these devices do not support device move detection.
67
ON PREMISE
CHAPTER 21 DEPLOYMENT GUIDE: 5540
Deployment Guide: 5540
On Premise

L2 Port.
MiVoice Business:
(CPN/DID)
Device:
• None

Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
• None
68
OFF PREMISE
CHAPTER 21 DEPLOYMENT GUIDE: 5540
Off Premise

device.
MiVoice Business:
• Define the CESID of the device.
the user.
(CPN/DID)
Device:
• None
69
ON PREMISE
CHAPTER 22 DEPLOYMENT GUIDE: MiVoice Business Console
Deployment Guide: MiVoice Business

Console
On Premise
MyE911® Application RedSky:

(RECOMMENDED if device is wireless) • Program a Device User and ensure the
Alternate ID matches the MiVoice Business’
CPN/DID or DN for the device.
MiVoice Business:
• Enable the CESID not required for Emergency
Calls COS option.
(CPN/DID)
Device:
• Install the MyE911® Application given the
Device User email address.
• Manage the location via the MyE911®
application.
(RECOMMENDED if device is wired) • Program a Location match the CESID of the
Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
None
70
OFF PREMISE
CHAPTER 22 DEPLOYMENT GUIDE: MIVOICE BUSINESS CONSOLE
Off Premise

• Program a Device User and ensure the
Alternate ID matches the MiVoice Business’
MiVoice Business:
Calls COS option.
(CPN/DID)
Device:
application.
71
ON PREMISE
CHAPTER 23 DEPLOYMENT GUIDE: GENERIC SIP
Deployment Guide: Generic SIP

NOTE: Since each Generic SIP Softphone may have different implementations, Mitel will need to certify
the solution with each specific Generic SIP Set.
On Premise
Geo-Location RedSky:
• None
MiVoice Business:
• Enable the Emergency Info Provided by
Device SIP Device Capability for the device.
Device:
• Program the RedSky HELD URL, organization
ID, and secret.
• Update the location
CESID provided by the device RedSky:
device.
MiVoice Business:
• Enable the Emergency Info Provided by the
Device for the SIP Device Capability
(CPN/DID)
Device:
• Program the CESID against the device.
• NOTE: The string entered in the Location ID
field must conform to the CESID rules of the
MiVoice Business, where only digits 0-9 are
valid, up to a maximum of 12 digits.
Special characters or text is not supported
and may result in a failed emergency call.
72
ON PREMISE
BSSID to CESID Mapping RedSky:

device.
MiVoice Business:
Device for the SIP Device Capability.
• Define the BSSID to CESID Mapping.
(CPN/DID).
Device:
• Enable the MAC Address of the Wireless
Access Point being used for the call to be sent.
73
OFF PREMISE

Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
• None
Alternate ID matches the MiVoice Business’s
MiVoice Business:
Calls COS option.
(CPN/DID)
Device:
application.
Off Premise
None
MiVoice Business:
Device:
• Program the RedSky HELD URL, organization
ID, and secret. Update the location.
73
OFF PREMISE

device.
MiVoice Business:
(CPN/DID)
Device:
• Program the CESID against the device.
BSSID to CESID Mapping RedSky:
device.
MiVoice Business:
• Define the BSSID to CESID Mapping
(CPN/DID)
Device:
• Enable the MAC Address of the Wireless
Access Point being used for the call to be sent.
Alternate ID matches the MiVoice Business
MiVoice Business:
Calls COS option.
(CPN/DID)
Device:
application.
74
ON PREMISE
CHAPTER 24 DEPLOYMENT GUIDE: SINGLE CELL DECT (6XX/56XX)
Deployment Guide: Single Cell DECT (SIP

6xx / IP 56xx)
This is just a 6xx/56xx using a single cell.
On Premise

device.
MiVoice Business:
(CPN/DID)
Device:
• See the Multi-Cell DECT solution below based
on 6xx vs 56xx device.
• NOTE: The string entered in the Location
ID field must conform to the CESID rules of
the MiVoice Business, where only digits 0-
9 are valid, up to a maximum of 12 digits.
Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
• None
75
OFF PREMISE
CHAPTER 24 DEPLOYMENT GUIDE: SINGLE CELL DECT (6XX/56XX)
Off Premise

device.
MiVoice Business:
Device:
• See the Multi-Cell DECT solution below based
on 6xx vs 56xx device.
• NOTE: The string entered in the Location
ID field must conform to the CESID rules of
the MiVoice Business, where only digits 0-
9 are valid, up to a maximum of 12 digits.
76
CHAPTER 25 DEPLOYMENT GUIDE: SIP DECT (6XX)
Deployment Guide: SIP DECT (6xx)

Starting from SIP-DECT release 8.3 SP1, SIP-DECT supports providing an Emergency Location
Identification Number (ELIN) in the SIP signaling of incoming and outgoing calls. This helps the call
server (SIP proxy) to determine the correct public-safety answering point (PSAP) depending on where
the call was made.
An ELIN can be set for:
• The system
• A site
• A specific base station
The parameter value that is more specific among the three is used for accurate identification.
If ELIN support is enabled, the configured ELIN value is sent in the FROM header field of the SIP invite
and the P-Asserted-Identity field of the 200 OK. The ELIN is a string of up to 31 characters. There is no
specific limitation on character set. Characters are escaped in the SIP header if necessary.
Examples:
From: "Extension 5115"
<sip:[email protected];elin=0123456789>;tag=f-5899462600ef0a1c P-Asserted-
Identity: <sip:5115@ example.com;elin=0123456789>
The configuration can be done via the Open Mobility Manager (OMM) web service or via OM
Management Portal (OMP). Only the general activation of this feature and the system-wide emergency
location identification number can be set via the OMM configuration files.
NOTE: The string entered in the Location ID field must conform to the CESID rules of the MiVoice
Business, where only digits 0-9 are valid, up to a maximum of 12 digits. Special characters or text is not
supported and may result in a failed emergency call.
Parameter / Group System emergency location identification

number enabled
Description The parameter “enabled” of the system
emergency location identification number
configuration enables the sending of the
configured ELIN in the SIP signaling.
77
Format Boolean
Range 1 or true (enable)0 or false (disable)

Default value False
OMP System/ Advanced settings / Emergency location
/ Emergency location identification number /
Enabled
OMM Web Advanced: System/ Advanced / Emergency
location
MOM Web N/A
OMM configuration files <SetELIN enable="1"/>
DECT Phone N/A
User configuration files N/A

number
Description The system parameter "Emergency call
identification number" provides the system-wide
valid emergency call identification number. This
value is used when a more specific ELIN set is
not available. The parameter can be used for
small systems in which the same ELIN must be
used for all base stations.
Format String
Range Up to 31 characters
Default value Empty
OMP System/ Advanced settings / Emergency location
/ Emergency location identification number /
Number
OMM Web Advanced: System/ Advanced / Emergency
location
MOM Web N/A
OMM configuration files <SetELIN enable="0123456"/>
DECT Phone N/A

number
78
Description The system parameter "Emergency call

identification number" provides the system-wide
valid emergency call identification number. This
value is used when a more specific ELIN set is
not available. The parameter can be used for
small systems in which the same ELIN must be
used for all base stations.
NOTE: The number entered must conform to the
CESID rules of the MiVoice Business, where only
digits 0-9 are valid, up to a maximum of 12 digits.
Special characters or text is not supported and
may result in a failed emergency call.
Format String
Range Up to 31 characters.
Default value Empty
OMP Sites/ Emergency location identification number
OMM Web Sites/ Emergency location identification number
MOM Web N/A
OMM configuration files N/A
DECT Phone N/A
Parameter / Group Base station’s emergency location

identification number
Description The base station parameter “Emergency location
identification number” provides an emergency
location identification number for a specific base
station.
Format String
Range Up to 31 characters.
Default value Empty
OMP DECT base stations/ Emergency location
identification number
OMM Web Base Stations/ Emergency location identification
number
MOM Web N/A
OMM configuration files N/A
DECT Phone N/A
79
If ELIN support is enabled and at least one RFP has no ELIN assigned, a warning is displayed on the
status information page.
80
ON PREMISE
CHAPTER 26 DEPLOYMENT GUIDE: RFP 12/14 SINGLE CELL SOLUTION
Deployment Guide: RFP 12/14 Single Cell

Solution
This is programmed as a Generic SIP Device on the MiVoice Business.
On Premise

device.
MiVoice Business:
Device:
• The ELIN(CESID) must be configured on the
Base Station web page called “Emergency Call
Configuration”. On the same page, valid
emergency numbers can also be configured.

Zone.
MiVoice Business:
form
81
ON PREMISE
form.
Device:
• None
Off Premise

device.
MiVoice Business:
Device:
• The ELIN(CESID) must be configured on the
Base Station web page called “Emergency Call
Configuration”. On the same page, valid
emergency numbers can also be configured.

82
ON PREMISE
CHAPTER 27 DEPLOYMENT GUIDE: MULTI-CELL DECT (6XX)
Deployment Guide: Multi-Cell SIP DECT

(6xx)
On Premise

device.
MiVoice Business:
(CPN/DID)
Device:
• ELIN must be configured on the Base Station-
>Advanced->Emergency->ELIN page. See
section “Deployment Guide: SIP DECT 6xx” for
more details.
Off Premise
82
ON PREMISE
device.
MiVoice Business:
(CPN/DID)
Device:
>Advanced->Emergency->ELIN page. See
section “Deployment Guide: SIP DECT 6xx” for
more details.
83
ON PREMISE
CHAPTER 28 DEPLOYMENT GUIDE: MULTI-CELL DECT (56XX)
Deployment Guide: Multi-Cell IP DECT

(56xx)
As of IP-DECT 56xx Release 11.6, IP-DECT supports providing an Emergency Location Identification Number
(ELIN) in the SIP signaling of incoming and outgoing calls. This helps the call server (SIP proxy) to determine the
correct public-safety answering point (PSAP) depending on where the call has made.
The ELIN is configured on the Device Overview page of the base station by clicking on the device name.
Which then opens a pop-up where the Location ID(ELIN tag in SIP Signaling) can be entered, as well as an option
description which is only used as notes for a System Administrator.
NOTE: The string entered in the Location ID field must conform to the CESID rules of the MiVoice
Business, where only digits 0-9 are valid, up to a maximum of 12 digits. Special characters or text is not
supported and may result in a failed emergency call.
84
ON PREMISE
On Premise

device.
MiVoice Business:
(CPN/DID)
Device:
>Advanced->Emergency->ELIN page
Off Premise

device.
MiVoice Business:
(CPN/DID)
Device:
>Advanced->Emergency->ELIN page
85
ON PREMISE
CHAPTER 29 DEPLOYMENT GUIDE: 5634 WIFI
Deployment Guide: 5634 Wi-Fi
On Premise
BSSID to CESID RedSky:

Mapping • Program a Location to match the CESID of the device.
MiVoice Business:
• Enable the Emergency Info Provided by the Device for the SIP
Device Capability
• Define the Emergency Callback handling (CPN/DID) Device:
84
OFF PREMISE
CHAPTER 29 DEPLOYMENT GUIDE: 5634 WIFI
Off Premise
BSSID to CESID RedSky:

Mapping • Program a Location to match the CESID of the device.
MiVoice Business:
• Enable the Emergency Info Provided by the Device for the SIP
Device Capability
• Define the Emergency Callback handling (CPN/DID) Device:
85
ON PREMISE
CHAPTER 30 DEPLOYMENT GUIDE: LEGACY SIP (5302, 5505, 5624)
Deployment Guide: Legacy SIP (5302, 5505,

5624)
On Premise

Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
• None
Off Premise
Not recommended.
86
ON PREMISE
CHAPTER 31 DEPLOYMENT GUIDE: MICOLLAB MINET SOFTPHONE
Deployment Guide: MiCollab MINET Soft-

phone
On Premise
Options Available Steps

(RECOMMENDED if device is wireless) • Program a Device User and ensure the
MiVoice Business:
Calls COS option.
(CPN/DID)
Device:
application.
(RECOMMENDED if device is wired) • Program a Location match the CESID of the
Zone.
MiVoice Business:
form
form.
(CPN/DID)
Device:
• None
87
OFF PREMISE
CHAPTER 31 DEPLOYMENT GUIDE: MICOLLAB MINET SOFTPHONE
Off Premise

MiVoice Business:
• Enable the CESID not required for
Emergency Calls COS option.
(CPN/DID)
Device:
application.
88
CHAPTER 32 DEPLOYMENT GUIDE: MICOLLAB SIP SOFTPHONE
Deployment Guide: MiCollab SIP Softphone

NOTE:MiCollab clients installed on a mobile device with a native dialer (e.g., Apple PHONE, Android
PHONE, not tablets), the native dialer will intercept emergency calls, and will not go through the MiVoice
Business.
Additional configuration is required for MiCollab SIP Softphones.
Via the MiCollab Server, configure the Location Service under MiCollab Client Service > Administrator
Interface > Enterprise Tab > Location Service Configuration.
Via the MiCollab Server, configure the Emergency Dial Plan under MiCollab Client Deployment>
Deployment Profiles > Emergency Numbers.
Field Notes
Location Service RedSky

URL RedSky LIS Server URL
HeldOrgId HELD Organization ID
Secret HELD+ Secret Key
Confirm Secret HELD+ Secret Key
89
Field Notes
Virtual Environment If the Virtual Environment checkbox is checked,

then the clients are virtualized. That means, the
Virtual Environment checkbox will enable the
administrator to declare whether their clients are
running in a virtual environment or not, i.e.
VMWARE Horizon, Citrix, or RDS.
NOTE: IFT/EFT sites should enable 933 in the emergency number list for testing/integration.
Additionally, each MiCollab client will need to install the Mitel Network Helper and enter/confirm their
location in the MiCollab Client.
90
NOTE: This may differ based on the MiCollab Client.
91
ON PREMISE
On Premise
• None
MiVoice Business:
MiCollab Server:
• Define the Location Service Configuration.
• Define the Emergency dial plan
MiCollab Client:
• Install the Mitel Network Helper
• Enter/update their location in the MiCollab
Client
Off Premise
• None
MiVoice
Busines
s:
MiCollab Server:
MiCollab Client:
Client
92
CHAPTER 33 SOLUTION DEPLOYMENT GUIDE - MICOLLAB WEB CLIENT
Solution Deployment Guide - MiCollab Web

Client
NOTE: IFT/EFT sites should enable 933 in the emergency number list for testing/integration.
Additional configuration is required for MiCollab SIP Softphones.
Via the MiCollab Server, configure the Location Service under MiCollab Client Service > Administrator
Interface > Enterprise Tab > Location Service Configuration.
Via the MiCollab Server, configure the Emergency Dial Plan under MiCollab Client Deployment>
Deployment Profiles > Emergency Numbers.
Field Notes
Location Service RedSky

URL RedSky LIS Server URL
HeldOrgId HELD Organization ID
93
Field Notes
Secret HELD+ Secret Key

Confirm Secret HELD+ Secret Key
Virtual Environment If the Virtual Environment checkbox is checked,
then the clients are virtualized. That means, the
Virtual Environment checkbox will enable the
administrator to declare whether their clients are
running in a virtual environment or not, i.e.
VMWARE Horizon, Citrix, or RDS.
Additionally, each MiCollab client will need to install the Mitel Network Helper and enter/confirm their
location in the MiCollab Client.
94
95
ON PREMISE
On Premise
• None
MiVoice
Busines
s:
MiCollab Server:
MiCollab Client:
Client
Off Premise
• None
MiVoice
Busines
s:
MiCollab Server:
MiCollab Client:
Client
96
CHAPTER 34 DEPLOYMENT GUIDE: MICOLLAB DESKPHONE
Deployment Guide: MiCollab Desk phone

Follow the instructions based on the device type of the Desk phone.
97
CHAPTER 35 DEPLOYMENT GUIDE: MICOLLAB MOBILE
Deployment Guide: MiCollab Mobile

Uses native dialer, so there is no interaction with the MiVoice Business solution for emergency calls.
98
CHAPTER 36 DEPLOYMENT GUIDE - 3RD PARTY WEBRTC CLIENTS (VIA MBG)
Deployment Guide - 3rd Party WebRTC

Clients (via MBG)
NOTE: Since each 3rd Party WebRTC Client may have different implementations, Mitel will need to certify
the solution with each specific 3rd Party WebRTC Client.
WebRTC is just a HTML wrapper around the SIP protocol, so it would behave like a Generic SIP device.
See above.
99
LIMITATIONS
CHAPTER 37 DEPLOYMENT GUIDE - WEBRTC ANONYMOUS CALLS (VIA MBG)
Deployment Guide - WebRTC Anonymous

Calls (via MBG)
WebRTC can provide anonymous calls support via a weblink. These web-links are not expected to be
routed from the MiVoice Business to an emergency destination and will NOT provide any location
information.
Limitations
• Mobile phones – Mobile phones are not part of the MiVoice Business solution with RAY BAUM as
they use the native phone function to provide the location services information during an
emergency call.
• The MiVoice Business does not support RedSky connections per tenant in the same system. E.g.,
RedSky needs to be used by all tenants in a given system.
100
CHAPTER 38 ACRONYMS, ABBREVIATIONS, AND GLOSSARY
Acronyms, Abbreviations, and Glossary

BSSID - Basic Service Set Identification. MAC address of a Wireless Access Point (WAP) CESID - Caller
Emergency Service Identification, equivalent to ELIN.
CESID - Customer Emergency Service Identification. A CESID is sent to a PSAP during an emergency
call and is used as a key in the Automatic Location Information (ALI) database to find a location for the
caller and it is also the call back number should the emergency call drop and therefore must be a
dialable PSTN number. In the Redsky solution, the CESID is only used as a location identifier by
Redsky to map to an ERL ID to find a dispatchable Civic Address to send to the PSAP and the callback
number is sent separately, not tied to the CESID.
COR - Class of Restriction – To limit a station’s access to certain Class of Service Options.
COS - Class of Service – A level of service defined by a specific set of features that controls an
extension’s access to these features.
CPN - Calling Party Number – A number to identify the device or user who initiated the call.
DID - Direct Dialing Inwards – Allows an external caller to dial an internal extension without having to go
through an attendant or operator.
ELIN - Emergency Location Identification Number also known as CESID. ERS - Emergency Routing
Services.
Fixed devices- Fixed device is a device that cannot be moved to another place in the enterprise without
assistance from a professional installer or network manager.
HELD- HTTP-Enabled Location Delivery. Protocol used for retrieving location information from a server
within a network.
LIS - Location Information Server provided by Intrado that allows an organization to enter location
information (including civic address, floor/room/suite/apt, and so on) to be used during emergency calls.
LLDP- Link Layer Discovery Protocol – An IEEE standard (801.1AB) that provides a vendor-neutral
method for Ethernet network devices such as switches, routers, and wireless LAN access points to
advertise and store the information about themselves to other nodes on the network.
LLDP-MED- Link Layer Discovery Protocol-Media Endpoint Discovery MBG – Mitel Border Gateway
MOM- Multi OMM Manager. Multi-OMM-Manager (MOM) delivers full local site survivability for large
geographical distributed multi-site-DECT networks with the benefit of central user management, roaming
between sites and overall messaging. The MOM solution is scalable over small and large sites and
expands the total system capacity for a managed SIPDECT network from 10,000 to 50,000 users
OMM- Open Mobility Manager. System configuration is managed through Mitel SIP-DECT’s web service
portal Open Mobility Manager (OMM), which features a status display with event logs, statistics and real-
time monitoring. Parameter changes can be applied to multiple entries (such as RFPs) at once and
statuses of SIP-DECT RFPs can be monitored for system alarm states
OMP- Om Management Portal. Mitel SIP-DECT reduces administrative effort by automatically creating
handset data in large systems when a new subscription is added and allowing administrators to import
user data from external sources.
MLTS - Multi Line Telephone System. Equivalent to a PBX, but is the nomenclature used in the RAY
BAUM’S Act.
NANP – North American Numbering Plan (https://en.wikipedia.org/wiki/North_American_Number-
ing_Plan)
101
Non-fixed devices – A non-fixed device is a device that the end user can move from one endpoint to
another without assistance.
PAI header - P-Asserted-Identity header
PANI header- P-Access-Network-Info header PSAP - Public Safety Answering Points

PNI – Primary Node Id. MiVoice Business identifier to differentiate between different MiVoive Business
clusters in the same MiVoice Business network.
PSAP 0- Public Safety Answering(or Access) Point. A call center where emergency calls (like police, fire
brigade, ambulance) initiated telephony device are terminated.
SBC – Session Border Controller
102

Mivb Redsky Raybaum

Uploaded by

Copyright:

Available Formats

Mivb Redsky Raybaum

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mivb Redsky Raybaum

Uploaded by

Copyright:

Available Formats

MiVoice Business

RAY BAUM'S Act Solution Deployment

Release 10.0 SP1

®,™ Trademark of Mitel Networks Corporation

© Copyright 2023, Mitel Networks

Corporation All rights reserved

What's new in this Document ............................................................................................................... 7

Kari’s Law and RAY BAUM’S Act ............................................................................................................ 1

MiVoice BusinessSupportforRAYBAUM'SActSection 506 and Kari's Law ............................................... 2

Solution: How the Integration Works .................................................................................................. 15

Solution: MiVoice Business Location ID Definition .............................................................................. 18

Solution: MiVoice Business Device RAY BAUM Support Summary....................................................... 19

Solution: MiVoice Business Functions with RAY BAUM Support .......................................................... 21

Solution: Mitel Applications with RAY BAUM Support ........................................................................... 22

Solution: Mitel Applications Without RAY BAUM Support .................................................................. 23

Solution: Deployment Diagrams .......................................................................................................... 24

Deploying Guide: MiVoice Business SIP Trunking to RedSky (MBG as Outbound-Proxy)...................... 30

Deployment Guide: Emergency Callbacks............................................................................................ 40

Deployment Guide: Defining Locations ............................................................................................... 42

Deployment Guide: Defining On-Premise Wire Maps .......................................................................... 43

Deployment Guide: Device Overview .................................................................................................. 44

Deployment Guide: 69xx MiNet .......................................................................................................... 63

Deployment Guide: Legacy MINET 53xx .............................................................................................. 66

Deployment Guide: 5540..................................................................................................................... 68

Deployment Guide: MiVoice Business Console .................................................................................... 70

Deployment Guide: Generic SIP .......................................................................................................... 72

Deployment Guide: Single Cell DECT (SIP 6xx / IP 56xx)....................................................................... 75

Deployment Guide: SIP DECT (6xx) ...................................................................................................... 77

Deployment Guide: RFP 12/14 Single Cell Solution ............................................................................. 81

Deployment Guide: Multi-Cell SIP DECT (6xx)...................................................................................... 82

Deployment Guide: Multi-Cell IP DECT (56xx) ..................................................................................... 84

Deployment Guide: 5634 Wi-Fi ........................................................................................................... 84

Deployment Guide: Legacy SIP (5302, 5505, 5624) .............................................................................. 86

Deployment Guide: MiCollab SIP Softphone ....................................................................................... 89

Solution Deployment Guide - MiCollab Web Client ............................................................................. 93

Deployment Guide: MiCollab Desk phone ........................................................................................... 97

Deployment Guide: MiCollab Mobile .................................................................................................. 98

Deployment Guide - 3rd Party WebRTC Clients (via MBG) ................................................................... 99

Deployment Guide - WebRTC Anonymous Calls (via MBG) ................................................................ 100

Acronyms, Abbreviations, and Glossary ............................................................................................ 101

Table 1: Document Version 1.0

Feature/Enhancement Document Updates Location Publish Date

Kari’s Law and RAY BAUM’S Act

How does a customer know if they need any of the RAY

MiVoice Business Support for RAY BAUM'S

Solution: MiVoice Business - RAY BAUM

RedSky Horizon Mobility Portal

MiVoice Business Console

Solution: Requirements for MiVoice

MiVoice Business 9.2 At least one SIP Trunk route is

IP DECT 56xx (ASCOM) 11.1.6 Device based provisioning of a

Establishing a Contract with RedSky

MBG(s) External IP Address RedSky maintains an Access Control List to limit

MyE911 application The number of users/devices that will require the

IP Address of Termination Point MBG(s) WAN FQDN or IP Address.

Access Control List of the MBG Servers with RedSky

Horizon Mobility Setup - RedSky Portal

6. Configure Emergency On-Site Notifications (EON) Users

7. Provide Application installs/guides as needed.