Mivb Intrado Raybaum

MiVoice Business
RAY BAUM'S Act Solution Deployment

Guide for Intrado
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 Business Support for Section 506 of RAY BAUM’S Act and Kari´s Law ...................................... 2
Solution: MiVoice Business - RAY BAUM’s Act High Level Architecture with Intrado ............................. 3
Solution: Requirements for MiVoice Business - RAY BAUM Integration with Intrado
................................................................................................................................. 6
Establishing a Contract with Intrado ............................................................ 7
Solution: How the Integration Works .................................................................................................. 12

Non-fixed devices .................................................................................................. 12
Collecting Data ........................................................................................... 12
Fixed devices (legacy TDM devices) ....................................................................... 12
Collecting Data ........................................................................................... 13
Sending Data to Intrado ......................................................................................... 13
Emergency Callback and Extension Bind................................................................ 14
Solution: MiVoice Business Location ID Definition .............................................................................. 15
Solution: MiVoice Business Device RAY BAUM Support Summary....................................................... 16
Solution: MiVoice Business Functions with RAY BAUM Support .......................................................... 18
Solution: Mitel Applications with RAY BAUM’s Act Support ................................................................... 19
Solution: Mitel Applications without RAY BAUM Support ................................................................... 20
Solution: Deployment Diagrams .......................................................................................................... 21

MiVoice Business and MBG in a customer site ...................................................... 21
Multiple MiVoice Business Instances each with connectivity to a single MBG in a
customer site ......................................................................................................... 21
Multiple MiVoice Business Instances using a single MiVoice Business as a Trunking
Gateway to a single MBG in a customer site.......................................................... 22
MiVoice Business and two MBGs in a customer site ............................................. 23
Multiple MiVoice Business Instances using multiple MiVoice Business as a Trunking
Gateway to a single MBG in a customer site.......................................................... 24
Multiple MiVoice Business Instances using a dedicated MiVoice Business as
gateway to two MBGs in a customer site .............................................................. 25
Deploying Guide: MiVoice Business SIP Trunking to Intrado using MBG as an Outbound- Proxy. ........ 26
Configure MBG SIP Options ................................................................................... 26
Configure MBG definition for MiVoice Business .................................................... 26
Configure MBG SIP Trunking to Intrado ................................................................. 27
Configure MiVoice Business Trunking Gateways to use MBG as an outbound proxy
to Intrado............................................................................................................... 28
Configure Non-Trunking Gateways to use MiVoice Business Trunking Gateways to
Access Intrado ....................................................................................................... 35
Deployment Guide: Emergency Callbacks............................................................................................ 38
Deployment Guide: Defining Locations ............................................................................................... 40
Deployment Guide: Defining On-Premises Wire Maps ........................................................................ 41
Deployment Guide: Device Overview .................................................................................................. 42

Devices that use CESID (such as 69xx, Single Cell DECT, and 5634 Wireless) ......... 42
Devices that use Intrado’s 911 Location Manager (such as MiVoice Business
Console) ................................................................................................................. 51
Devices that use Geolocation (such as MiCollab SIP Soft- phone Client) ............... 53
Deployment Guide: 69xx MiNet .......................................................................................................... 57

On Premises ........................................................................................................... 57
Off Premises .......................................................................................................... 58
Deployment Guide: 53xx MINET (5304, 5312, 5320, 5320e, 5330e, 5340e).......................................... 59
On Premises ........................................................................................................... 59
Off Premises .......................................................................................................... 60
Deployment Guide: Legacy MINET 53xx .............................................................................................. 61

On Premises ........................................................................................................... 61
Off Premises .......................................................................................................... 61
Deployment Guide: Legacy MINET (50xx, 51xx, 52xx, 5560 IPT, Navigator) ......................................... 62
On Premises ........................................................................................................... 62
Off Premises .......................................................................................................... 62
Deployment Guide: 5540..................................................................................................................... 63
On Premises ........................................................................................................... 63
Off Premises .......................................................................................................... 64
Deployment Guide: MiVoice Business Console .................................................................................... 65

On Premise ............................................................................................................ 65
Off Premise ............................................................................................................ 66
Deployment Guide: Generic SIP .......................................................................................................... 67

On Premises ........................................................................................................... 67
Off Premises .......................................................................................................... 69
Deployment Guide: Single Cell DECT (SIP 6xx / IP 56xx)....................................................................... 72

On Premises ........................................................................................................... 72
Off Premises .......................................................................................................... 73
Deployment Guide: SIP DECT (6xx) ...................................................................................................... 74
Deployment Guide: RFP 12/14 Single Cell Solution ............................................................................. 78

On Premises ........................................................................................................... 78
Off Premises .......................................................................................................... 79
Deployment Guide: Multi-Cell SIP DECT (6xx) ...................................................................................... 80

On Premises ........................................................................................................... 80
Off Premises .......................................................................................................... 81
Deployment Guide: Multi-Cell IP DECT (56xx) ..................................................................................... 82

On Premises ........................................................................................................... 83
Off Premises .......................................................................................................... 83
Deployment Guide: 5634 Wi-Fi............................................................................................................ 82

On Premises ........................................................................................................... 82
Off Premises .......................................................................................................... 83
Deployment Guide: Legacy SIP (5302, 5505, 5624) .............................................................................. 84

On Premise ............................................................................................................ 84
Off Premise ............................................................................................................ 84
Deployment Guide: MiCollab MINET Soft- phone ................................................................................ 85

On Premise ............................................................................................................ 85
Off Premise ............................................................................................................ 86
Deployment Guide: MiCollab SIP Softphone ....................................................................................... 87

On Premises ........................................................................................................... 90
Off Premises .......................................................................................................... 90
Solution Deployment Guide - MiCollab Web Client ............................................................................. 91

On Premises ........................................................................................................... 94
Off Premises .......................................................................................................... 94
Deployment Guide: MiCollab Deskphone ............................................................................................ 95
Deployment Guide: MiCollab Mobile .................................................................................................. 96
Deployment Guide - Third-Party WebRTC Clients (via MBG) ............................................................... 97
Deployment Guide - WebRTC Anonymous Calls (via MBG) .................................................................. 98

Limitations ............................................................................................................. 98
Testing the Intrado Integration and Reading Call Detail Records(CDR) ................................................ 99
933 Test Calls ......................................................................................................... 99
911 Test Calls ......................................................................................................... 99
Call Detail Records(CDR) ...................................................................................... 100
Troubleshooting ................................................................................................................................ 102

Contacting Mitel Product Support ....................................................................... 103
Contacting Intrado Product Support .................................................................... 103
Acronyms, Abbreviations, and Glossary ............................................................................................ 104

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 Intrado. 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 adopted rules for implementing two federal laws that strengthen the
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, Notifi-
cation, and Dispatchable Location Requirements are described at the following link:
https://www.fcc.gov/mlts-911-requirements
FAQ about RAY BAUM’s Act can be found at the following link: https://www.fcc.gov/files/mltsfaqspdf
The RAY BAUM’s Act classifies devices into the following categories:
• Fixed MLTS devices - Devices that connect to a single end point (for example, a desk or office
phone) and are not capable of being moved to another endpoint by the end user, although they
might 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 Intrado 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 Intrado 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 Intrado 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 Intrado 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 Intrado 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 SECTION 506 OF RAY BAUM’S ACT AND
KARI´S LAW
MiVoice Business Support for Section 506

of RAY BAUM’S Act and Kari´s Law
MiVoice Business, as an 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.
For MiVoice Business, we have the following device categories:
• Fixed MLTS Devices e.g., Analog Devices
• Non-Fixed MLTS devices - IP Devices, SIP Devices, softphones, all teleworkers, and so on
In order to provide full support of the requirements above, MiVoice Business is integrated with Intrado in
USA, https://www.west.com/en_ca/safety- services/enterprise-e911-solutions/.
2
CHAPTER 3 SOLUTION: MIVOICE BUSINESS - RAY BAUM HIGH LEVEL ARCHITECTURE
WITH INTRADO
Solution: MiVoice Business - RAY BAUM’s

Act High Level Architecture with Intrado
MiVoice Business implements the RAY BAUM’s Act requirements in conjunction with Intrado as the
MiVoice Business 911 solution alone does not satisfy the legislated requirements for the RAY BAUM’s
Act for all non-fixed devices.
For Kari’s Law conformance, MiVoice Business can be pre-configured to support 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 Intrado and Intrado redirects the call to the appropriate Public Safety Answering Points
(PSAPs) based on the Civic Address of the location as identified by Intrado. Intrado’s email notification
system is sufficient for Kari’s Law local notification requirements as laid down by 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 Intrado during emergency
calls. Intrado looks up these Location identifiers to determine the ERL (Emergency Routing Location -
including Civic Address), which they then use for signaling to the PSAP. Intrado also validates the Civic
Address when the location is first created in their database. Intrado address validation includes all 50
states in the United States, as well as Puerto Rico and Canada. However, all calls from a Canadian
location will be routed to Intrado’s Emergency Call Relay Center(ECRC). The ECRC will answer the
emergency call and transfer it to the local emergency services.
With the RAY BAUM’s Act solution, the Mitel MiVoice Border Gateway (MBG) is used as the Session
Border Controller (SBC). If a customer has an existing MBG, this can be upgraded to Release 11.3 and
used for the connection to Intrado. Additionally, the MBG can be used for Remote Users (Teleworkers).
Standard engineering guidelines apply.
The integration described in this guide also requires that the customer has a valid service agreement with
Intrado. Mitel does not provide this service agreement directly.
Emergency Callbacks with Intrado use their Extension Bind feature, which temporarily maps a DID number
owned by Intrado to the DN of the emergency caller. If the emergency call drops, the PSAP will use the
“bound” DID to call the user back.
NOTE: It is recommended that the MiVoice Business integration use the Extension Bind feature. If this
feature is not used, the customer must program CPN/DID in order to route the call back through the
PSTN network to the PBX. The procedure for this is described in this document.
Figure 1 shows a high-level architectural view of the MiVoice Business RAY BAUM’s Act integration with
Intrado.
3
WITH INTRADO
The MiVoice Business RAY BAUM’s Act solution with Intrado Solution is composed of the following
components:
• Intrado
– A valid commercial agreement with Intrado. Part of setting up this agreement involves:
• Intrado’s Extension BIND feature
– From this agreement, you will need to obtain the following information from Intrado:
• Account ID - This is used by Intrado to isolate one Organization’s locations from those of another.
• Identification of the transport protocol to use with Intrado
• UDP on port 5060
• NOTE: This must be the configuration if Intrado’s Extension Bind feature is
enabled.
• TCP on port 5060
• TLS 1.2+ on port 5061 – Currently not supported on Intrado
• SIP Gateways
• HELD Service URL + Credentials
• 911 Location Manager - An application provided by Intrado that runs on select softphone devices.
• Access to the Intrado Portal - The main configuration portal
• Define Locations (ERLS)
• Define Subscribers (used to identify a caller specifically for callback purposes)
• Define the On-Premises wire map (Subnets, Wireless Access Points, Switches) to be used by
On-Premises HELD clients and On-Premise 911 Location Manager clients.
• MBG
– SIP Trunking to/from Intrado
– 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.
4
WITH INTRADO
• include 933 for testing
– DID and CPN Substitution per device (or location) that can make 911 calls.
– SIP Peer Profile dedicated to signaling with Intrado
– SIP Device Capabilities - For SIP Devices that provide location information.
– Class of Service - For devices that are going to use the 911 Location Manager application from
Intrado.
– Class of Service - For MINET teleworker devices.
– (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 Intrado SIP Gateways are down).
• 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 911 Location Manager application from Intrado
The Mitel MiVoice Border Gateway (MBG) is used as the SBC between MiVoice Business and Intrado in
the solution. A SIP trunk each is set up between MiVoice Business and MBG and between MBG and
Intrado.
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 Intrado, a web portal is used to set up the information required for 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 for an alternate
identification of a device or a user.
The majority of devices that are supported in the MiVoice Business portfolio are supported for the RAY
BAUM’s Act. The exception is off-premises 52xx and earlier 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 Intrado.
Additional steps are required for the overall solution as a whole but are not specific to Intrado and are
thus outside the scope of this document.
5
SOLUTION: REQUIREMENTS FOR MIVOICE BUSINESS - RAY BAUM INTEGRATION
CHAPTER 3 WITH INTRADO SOLUTION: MIVOICE BUSINESS - RAY BAUM HIGH LEVEL
ARCHITECTURE WITH INTRADO
Solution: Requirements for MiVoice Business - RAY BAUM

Integration with Intrado
Minimum SW
Product Release Minimum Requirements/Comments
MiVoice Business 9.2 At least one SIP Trunk route is required, along
with the SIP channel licenses for connecting to
the MBG.
NOTE: While it is not a minimum requirement, it
is recommended to have two MiVoice
Business instances for redundancy.
MBG 11.3 At least 1 MBG is required along with the
appropriate SIP Trunk licenses.
NOTE: While it is not a minimum requirement, it
is recommended to have two MBGs for
redundancy.
cMBG 11.1 SP1 At least 1 MBG along with the appropriate
licenses. NOTE: While it is not a minimum
requirement, it is recommended to have two
MBGs for redundancy.
MiCollab 9.4 SP1 Geolocation Support via HELD from Intrado
Location Information Server
69xx MiNET (6905, 1.7 Pop-up support (for supporting teleworker
6910, 6920, devices)
6930, 6940, 6970)
53xx MiNET 6.5.1 Pop-up support (for supporting teleworker
(5304,5312,5320,5 devices)
320 e,5330e,5340e,55
40 only)
SIP DECT 6xx 8.3 SP1 Device-based provisioning of a CESID that is to

be sent during calls.
IP DECT 56xx (ASCOM) 11.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 CESID that is to
RFP 14 Single Cell Solution RTX v610b1 be sent during calls.
5634 Wireless 3.0.2 Device-based provisioning to enable the
(ASCOM) sending of the MAC address of a connected
Wireless Base Station during calls.
6
Establishing a Contract with Intrado
The channel partner/customer must have an agreement with Intrado. It must be prepared with the
following information:
Item Comments
Locations The number of locations required to satisfy RAY BAUM’s Law.

Subscribers For the MiVoice Business solution, this will include all Users(and
members of Personal Ring Groups(PRGs) and devices not associated
with Users that can make emergency calls (for example, IP Device
Only, Lobby Phone, MiVoice Business Console, and so on.).
HELD Subscribers These are the number of devices/Subscribers that will provide
Geolocation (for example, MiCollab SIP Softphones, and so on). If this
service is required, a request to Intrado must be made to enable this
support so that the Authentication Tokens option is available under the
Administration tab to retrieve the token required.
911 Location Manager The number of users/devices that will require the NG911 application
Clients (for example, MiVoice Business Console and MiCollab MINET
Softphones)
Notification Clients The number of email address recipients for 911 Notifications to satisfy
Kari’s Law.
Network Maps feature This is required to be able to configure on-premise Subnets and
Wireless Access Points. I think we need this for 911 Location Manager
based devices.
911 Location Manager This optional application allows access to Intrado’s 911 Location
Manager application that is to be used for some softphones in the
MiVoice Business solution. If this application is required, a request to
Intrado must be made to enable this support so that the Authentication
Tokens option is available under the Administration tab to retrieve the
token required.
Callback Determination For Intrado to support emergency callbacks to Subscribers without a
Preference: DID number, Intrado must be asked to set the Callback Determination
Extension BIND Preference to Extension BIND feature (XBind). This optional feature
feature(XBind) binds an Intrado owned DID to an emergency caller’s internal DN for
use by a PSAP if an emergency call were to be dropped. The PSAP
would call the Intrado DID, and Intrado will route back to the MiVoice
Business. The SIP trunk to Intrado must also be configured as a
private SIP trunk.
NOTE: If this feature is enabled, the transport protocol of the SIP trunk
between MiVoice Business and Intrado must be UDP.
Location Determination For Intrado to properly associated a location from an emergency call
Preference: from the MiVoice Business, Intrado must be asked to set the Location
ERL ID in SIP header Determination Preference to ERL ID in SIP header.
NOTE: Without the Extension BIND feature, Intrado will expect the Subscriber ID (which identifies a
user/callback destination) to be a 10-digit Subscriber ID (caller’s DID) and an emergency callback will be
made to the MiVoice Business via the public PSTN. In that case, the MiVoice Business must be set up to
use CPN Substitution and DID for each end-point/user that can make an emergency call.
7
Additionally, if you are using a public PSTN trunk as a backup to Intrado, it is highly recommended to have
a CPN/DID for each device that can make a 911 call.
Intrado Portal - ERS (Emergency Routing Service)

The Intrado Portal is available via the web. The URL comes from Intrado in a welcome email. For more
detailed information about the use of this portal, see Intrado ERS User Guide.pdf, available from Intrado.
This is the main Intrado Portal for the configuration of the customer’s emergency solution. In order to
program the MiVoice Business solution, you will need to perform the following steps:
1. Identify the Account 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. This will be provided to
you by Intrado and there is more information in chapter Deployment Guide: MiCollab SIP Softphone.
8
3. Configure Locations (ERLS - Emergency Routing Locations)

– Step 1: Configure an Emergency Response Location(ERL) to be validated.
• ERL Name - Customer-defined label to identify the location
• House # - Civic Address provided to PSAP
• Street/Road - Civic Address provided to PSAP
• City - Civic Address provided to PSAP
• Country - Civic Address provided to PSAP
• State/Province - Civic Address provided to PSAP
• Postal Code - Civic Address provided to PSAP
• Location - The dispatchable location within the given civic address, provided to PSAP.
9
– Step 2: Configure the ERL’s Routing Options

• Delivery Method - The MiVoice Business solution supports only the PSAP delivery method.
• Custom Callback – If configured, the ERS Custom Callback number will override the callback
number sent by the MiVoice Business. It should be noted this callback is based on the location
of the caller as it is tied to the CESID/ERL ID, rather than the caller’s callback number.
• Email Notifications - Recommended to use the Intrado Account-based email notifications instead
of ERL-specific email notifications (see below).
• ERL ID – This step is VERY IMPORTANT, it should be manually entered and should match the
CESID that is associated the ERL configured in Step 1. This CESID must also be programmed
on the MiVoice Business. The MiVoice Business will be sending this CESID for an emergency
call in the SIP Invite for Intrado to link with the caller. The caller must match a Subscriber
provisioned on Intrado, as provisioned in Step 3.
10
– Step 3: Skip Enter Associations(optional)

• This step is not required and should be skipped.
11
4. Configure Subscribers. For the MiVoice Business solution, this includes all MiVoice Business Users
and non-user devices that can make 911 calls (For example, IP Device Only, Lobby Phones, and
MiVoice Business Console).
– Subscriber ID - For the MiVoice Business solution, it is highly recommended that you use private SIP
Trunks and Intrado’s Extension BIND feature. The difference between a private SIP trunk versus
and public SIP trunk it that a private SIP trunk will send information about the internal directory
number where public will send an external number(caller’s CPN/DID number). This configuration
is controlled by an option in the SIP Peer Profile, see Deploying Guide: MiVoice Business SIP
Trunking to Intrado using MBG as an Outbound- Proxy. for more details. So when using a private
SIP trunk with Intrado it means the Subscriber ID is the caller’s extensions provided in the <P-
Asserted-Identity> SIP Header, rather than the caller’s CPN/DID number. This is typically the
caller’s extension (or MDUG/Suite Pilot if the caller is a member of such groups). If they are using
a Public SIP Trunk, then the Subscriber ID, and thus the P-Assert-Identity header, should be the
device’s CPN/DID substitution value. In the screenshot below, the Subscriber ID is of 1000 is an
example of configuration for a PRIVATE SIP Trunk and 6136913499 is an example of configuration
for a PUBLIC SIP Trunk. See
– DID Range – Can be used to configure a range of 10 digit Subscribers. This would only be used if
they are using a Public SIP Trunk.
– Extension Range - Can be used to configure a range of non-10 digit Subscribers. This would only
be used if they are using a Private SIP Trunk.
12
When the Subscriber is created as described above, the ERL Information field for that user should be
Determined at Call Time, as seen for Subscriber 56141 and 13901 below.
For Subscriber 14666, this would have initially been Determined at Call Time as well but has
been updated with a location reported by an end user using the 911 Location Application or
MiCollab SIP Softphone as shown by the that the ERL ID is an Intrado generated Globally Unique
Identifier(GUID).
5. Configure the On-Premise wire map via Provisioning. This is used by the On-Premise HELD and 911
Location Manager clients.
– Subnets - Allow clients to determine their location based on IP address.
– Wireless Access Points - Allow clients to determine their location based on the MAC address of the
Wireless Access Point.
– Switches - Allow clients to determine their location based on L2 switch connectivity.
6. Obtain client installer/guides for HELD devices and 911 Location Manager clients provided by Intrado.
13
NON-FIXED DEVICES
CHAPTER 4 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 solution falls into three categories:
• Device’s that update Intrado’s LIS directly, and provide Geolocation data through the MiVoice
Business.
• Device’s that use Intrado’s 911 Location Manager application to update the Intrado’s LIS directly and
use the Subscriber ID (DN or CPN) from the MiVoice Business to associate the location.
– MiVoice Business Administrators will need to put a process in place to notify their end users on
how to install this application as well as instructions on how to configure it during installation.
When installed, user’s will be prompted for a Subscriber ID which needs to match a Subscriber ID
configured in the Intrado Portal. If using the Extension BIND feature, this will be the DN of the
device the using the application, unless the device is in an MDUG, in which case the MDUG
prime DN should be entered. If not using Extension BIND feature, this needs to be the user DID
number.
• Devices that use CESID, which is then broken down further:
– SIP Devices that provide a Wi-Fi Base Station MAC address in the SIP INVITE (PANI Header) or
200 OK
– SIP Devices that provide an ELIN/CESID in the SIP INVITE (FROM header) or 200 OK
– MINET devices that support STP/CDP/LLDP-MED, where the MiVoice Business will use the L2
information to look up a CESID.
– Devices that use the MiVoice Business pre-provisioned CESID
– Devices that have an associated IP Range to Zone mapping, use the Zone’s CESID (if programmed)
NOTE: Using the default CESID is not recommended.

MiVoice Business uses a priority order to determine which Emergency Information is used:
• 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 (must not be used as it might not be sufficient to satisfy the US Law).
In all cases, the Subscriber ID is used to determine the emergency callback destination and the caller’s
DN or CPN.
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.
12
SENDING DATA TO INTRADO
Collecting Data
For fixed devices, as no information is provided by the device, MiVoice Business uses the programmed
CESID to identify the location of the caller, and the device’s DN (or CPN) to determine the emergency
callback destination.
Sending Data to Intrado

After the 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
Intrado.
To conclude the process, Intrado will use the header information to look up the Location (Geo Location
or FROM field) and Subscriber ID (P- ASSERT-IDENTITY).
• If the Geolocation/Subscriber are valid, then the call is routed to the PSAP with the proper location and
callback information.
• If location/Subscriber are validated, then the call is routed to the PSAP with the proper location and
callback information.
• If the Subscriber or location cannot be identified by Intrado, the emergency call will be directed to
Intrado’s Emergency Call Relay Center for further triage.
NOTE: As per your contract with Intrado, calls that are directed to Intrado’s Emergency Call Relay
Center(ECRC) will entail an extra cost to the customer.
13
EMERGENCY CALLBACK
Emergency Callback and Extension Bind

Previously, the CESID was considered as a Location identifier and an Emergency Callback Number. For
RAY BAUM-enabled SIP Trunks, MiVoice Business separates the following two concepts:
• CESID remains the Location identifier for most devices (except Geolocation-enabled devices, and
softphones that use the Intrado 911 Location Manager application).
• Using Intrado’s Extension Bind feature allows them to provide an Intrado-owned DID to the PSAP, and
if an emergency callback is required, the PSAP calls Intrado’s DID, which they route back to the
Subscriber using the SIP Trunk to the MBG (which forwards it to the MiVoice Business).
NOTE: If this feature is enabled, the transport protocol of the SIP trunk between MiVoice Business
and Intrado must be UDP
Without Intrado’s Extension Bind feature, MiVoice Business provides CPN/DID for all users/devices that
can make 911 calls and the PSAP calls the MiVoice Business back directly through the public PSTN.
14
CHAPTER 5 SOLUTION: MIVOICE BUSINESS LOCATION
ID DEFINITION
Solution: MiVoice Business Location ID

Definition
The Location ID is a reference/identification used for identifying a device or several devices in MiVoice
Business that must be sent to Intrado and is usually the CESID assigned to the device. MiVoice Business
provides forms for various methods of associating a CESID with a device:
• 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 obtain their Location ID directly from Intrado, sent through the
MiVoice Business. As such, CESID need not be programmed on MiVoice Business. The DN (or CPN) is
used for linking the device to the location.
Devices that support sending the CESID/ELIN directly are programmed for this, and send the
CESID/ELIN through the MiVoice Business, and the Location ID need not be programmed on the MiVoice
Business. However, the CESID must match an Intrado ERL.
Devices that support Intrado’s 911 Location Manager updates the location directly from the application,
and do not need any CESID programmed on MiVoice Business. The DN (or CPN) is used for linking the
device to the location.
15
CHAPTER 6 SOLUTION: MIVOICE BUSINESS DEVICE RAY BAUM
SUPPORT SUMMARY
Solution: MiVoice Business Device RAY

BAUM Support Summary
The following table provides a list of supported devices, and the available options 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
NOTE: Legacy MINET devices
do not support LLDP-MED
5540 L2 to CESID mapping IP CESID Assignment
address to CESID mapping
MiVoice Business Console Intrado’s 911 Location Manager Intrado’s 911 Location Manager
IP to Zone to CESID Mapping
Generic SIP Device Geolocation/CESID provided by Geolocation/CESID provided by
NOTE: Mitel will need to certify the device BSSID to CESID the device BSSID to CESID
the solution with any Generic Mapping IP address to CESID Mapping Intrado’s 911 Location
SIP Device. mapping Intrado’s 911 Location Manager
Manager
Single Cell DECT (6xx/56xx in a CESID provided by the device CESID provided by the Device
single node setup IP address to CESID mapping
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, UC360, IP address to CESID mapping Not recommended
5624)
16
CHAPTER 6 SOLUTION: MIVOICE BUSINESS DEVICE RAY BAUM
SUPPORT SUMMARY
Device On-Premise Off-Premise (teleworker)
MiCollab MINET Softphone IP to Zone to CESID Mapping Intrado’s 911 Location Manager
(5020) Intrado’s 911 Location Manager
MiCollab SIP Softphone (UC Geolocation Geolocation
Endpoint)
MiCollab Web Client Geolocation Geolocation
MiCollab Deskphone Depends on the desk phone Depends on the desk phone
type type
MiCollab on Mobile Uses Native Dialer Uses Native Dialer
Analog CESID Assignment --
SIP ATA (Analog Terminal See Generic SIP See Generic SIP
Adaptors)
Third-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.
17
CHAPTER 7 SOLUTION: MIVOICE BUSINESS FUNCTIONS WITH RAY
BAUM SUPPORT
Solution: MiVoice Business Functions with

RAY BAUM Support
Apart from the devices, MiVoice Business supports many functions that might be used to make an
emergency 911 call. The supported MiVoice Business functions are as follows:
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 must log out and
then log in back.
SIP Hot Desking Depends on the SIP Device that you are logged
in to.
External Hot Desking Uses the incoming CLI if they are proxied on a
PUBLIC trunk.
If they are proxied on a PRIVATE trunk, then the
CESID programmed against the EHDU is used.
PRG The Location ID depends on the device itself (not
the PRG/MDUG Pilot); however, callbacks are
directed back to the PRG member meaning that
each member of the PRG needs to be configured
as a Subscriber on Intrado.
MDUG The Location ID depends on the device itself (not
the MDUG Pilot); however, callbacks are directed
back to the MDUG pilot.
Suites The Location ID depends on the device itself (not
the Suite Pilot); however, callbacks are directed
back to the Suite pilot.
18
CHAPTER 8 SOLUTION: MITEL APPLICATIONS WITH RAY BAUM SUPPORT
Solution: Mitel Applications with RAY

BAUM’s Act Support
MiVoice Business is integrated with different Mitel applications with RAY BAUM support. The following
Mitel applications support RAY BAUM:
• 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
• RFP 12/14 Single Cell Solution
19
CHAPTER 9 SOLUTION: MITEL APPLICATIONS WITHOUT RAY BAUM SUPPORT
Solution: Mitel Applications without RAY

BAUM Support
The following Mitel applications that do not support RAY BAUM:
• MiCAM - MiCollab Advanced Messaging
• MIR - Mitel Interaction Recording
• NPM – NuPoint Unified Messaging
• MPA - Mitel Performance Analytics
• Mitel Revolution
20
MIVOICE BUSINESS AND MBG IN A CUSTOMER SITE
CHAPTER 10 SOLUTION: DEPLOYMENT DIAGRAMS
Solution: Deployment Diagrams

This chapter covers possible deployments setups between MiVoice Business and the NG911 provider.
MiVoice Business and MBG in a customer site

The following architecture view shows the most basic setup between MiVoice Business and Intrado. An
emergency route is set up between MiVoice Business and Intrado’s SIP gateways using the single MBG
as an outbound proxy. A double SIP trunk between the customer site and Intrado is highly
recommended.
Refer to MBG documentation for MBG Redundancy SIP trunk configuration.
Multiple MiVoice Business Instances each with

connectivity to a single MBG in a customer site
The following architecture view shows a more complicated setup between multiple MiVoice Business
instances and a single MBG and Intrado. In this case, each MiVoice Business is set up with an
emergency route over between MiVoice Business and Intrado’s SIP gateways using the single MBG as
an outbound proxy. A double SIP Trunks between the customer site and Intrado is highly recommended.
21
MULTIPLE MIVOICE BUSINESS INSTANCES USING A SINGLE MIVOICE BUSINESS AS A TRUNKING GATEWAY TO A SINGLE MBG IN A
CUSTOMER SITE
NOTE: In this case, a single IP Trunk between MiVoice Business instances is all that is necessary, because
every MiVoice Business has its own emergency route to the MBG. This method might cost more because
you need SIP Trunk licenses for each MiVoice Business.
Multiple MiVoice Business Instances using a single

MiVoice Business as a Trunking Gateway to a single MBG
in a customer site
instances and a single MBG and Intrado, which reduces the number of SIP Trunks (and therefore licenses)
required. In this case, multiple MiVoice Business instances are set up with an emergency IP Trunking route
to a designated MiVoice Business set up with an emergency route between the gateway MiVoice Business
and Intrado’s SIP gateways using a single MBG as an outbound proxy. Double SIP Trunks between the
customer site and Intrado are highly recommended.
22
MIVOICE BUSINESS AND TWO MBGS IN A CUSTOMER SITE
NOTE:In addition to the normal IP Trunk route between MiVB1 and MiVB2, MiVB2 needs a dedicated
emergency IP Trunk route to MiVB1.
MiVoice Business and two MBGs in a customer site

The following architecture view below shows a redundant setup between MiVoice Business and Intrado.
SIP trunks are set up between MiVoice Business and Intrado’s SIP gateways using the MBGs as
outbound proxies. Double SIP trunks between the customer site and Intrado are highly recommended.
23
MULTIPLE MIVOICE BUSINESS InstanceS USING MULTIPLE MIVOICE BUSINESS AS A TRUNKING GATEWAY TO A SINGLE MBG IN A
CUSTOMER SITE
Multiple MiVoice Business Instances using multiple

MiVoice Business as a Trunking Gateway to a single MBG
in a customer site
The following architecture view shows a redundant setup between multiple MiVoice Business and multiple
MBGs and Intrado. SIP trunks between MiVoice Business and Intrado’s SIP gateways are set up using
the MBGs as outbound proxies. Double SIP trunks between the customer site and Intrado are highly
recommended.
24
25
MULTIPLE MIVOICE BUSINESS Instances USING A DEDICATED MIVOICE BUSINESS AS GATEWAY TO TWO MBGS IN A CUSTOMER SITE
NOTE: In this case, a single IP Trunk between the MiVoice Business instances is all that is necessary,
because every MiVoice Business has its own emergency route to the MBG. This method might cost more
as you need SIP Trunk licenses for each MiVoice Business.
Multiple MiVoice Business Instances using a dedicated

MiVoice Business as gateway to two MBGs in a customer
site
instances and a multiple MBGs and Intrado, which reduces the number of SIP Trunks (and therefore
licenses) required. In this case, multiple MiVoice Business instances are set up with an emergency IP
Trunking route to designated MiVoice Business instances set up with an emergency route between
MiVoice Business and Intrado’s SIP gateways using the MBGs as outbound proxies.
Double SIP Trunks between the customer site and Intrado are highly recommended.
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.
25
CONFIGURE MBG DEFINITION FOR MIVOICE BUSINESS
CHAPTER 11 DEPLOYING GUIDE: MIVOICE BUSINESS SIP TRUNKING TO INTRADO USING MBG AS AN
OUTBOUND- PROXY.
Deploying Guide: MiVoice Business SIP

Trunking to Intrado using MBG as an
Outbound- Proxy.
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
NOTE: All of these need not be MiVoice Business — 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: MBG must set the MiVoice Business SIP capabilities as UDP, TCP, and TLS.
26
CONFIGURE MIVOICE BUSINESS TRUNKING GATEWAYS TO USE MBG AS AN OUTBOUND PROXY
CHAPTER 11 TO INTRADO
Configure MBG SIP Trunking to Intrado
NOTE: Transport protocol

MBG does not support translating transport protocols to a given SIP Service provider. Therefore, the
MiVoice Business (Network Elements for both the MBG Outbound Proxy and Intrado), MBG (MiVoice
Business + SIP Trunk), and Intrado must use the same protocol for the given communication path.
If there is a need to support SIP Service Provider with different protocols, you can do the following:
• On MiVoice Business, create separate Outbound Proxies for each Transport Protocol (TCP, UDP,
and TLS) to the MBG(s).
• On the MBG, define the ICP to allow all the SIP capabilities (UDP, TCP, and TLS).
• On the MiVoice Business instances, create separate SIP Peer Profiles for each SIP Gateway with the
appropriate Transport Protocol and corresponding Outbound Proxy.
NOTE: TLS Support (Port 5061) - Intrado does not support TLS.
27
Configure MiVoice Business Trunking Gateways to use

MBG as an outbound proxy to Intrado
Create an Outbound Proxy Network Element for the MBG. Separate Network Elements are required if
multiple MBGs are used.
NOTE: Ensure that the MBG Outbound Proxy uses the same Transport Protocol as the Intrado SIP Trunk.
NOTE: If Multiple Transport Protocols are required (for other SIP Gateways), then configure multiple
outbound proxies to the same MBG for each protocol.
Create a Network Element(s) for the Intrado SIP Gateways. Separate Network Elements are required if
the Intrado has multiple SIP Gateways.
28
29
NOTE: Ensure that the MBG Outbound Proxy uses the same Transport Protocol as the Intrado SIP Trunk.
Create a SIP Peer Profile for Intrado 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 Intrado
SIP Gateways.
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 on
Simultaneous Calls their SIP trunks today, these may need to be modified on
and Minimum 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
30
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
Disable Reliable Signaling and This option needs to be set to YES if the Extension
Provisional Header Bind(XBind) feature is enabled.
Responses Manipulation
Emergency Call Signaling and CESID in From, Callback in PAI
Headers Header
Manipulation
Multilingual Name Signaling and Should be left to No, not supported by Intrado.
Display Header
Manipulation
User-Defined Signaling and E911-Organization-ID
Header Name Header
Manipulation
User-Defined Signaling and Organization ID provided by Intrado and available on the
Header Value Header Intrado Portal Account Dashboard in the General
Manipulation Information pane - > Account ID.
31
MiVoice Business Field Settings
Maximum Simultaneous Calls and Depending how a customer has configured these values on
Minimum Reserved Call Licenses their SIP trunks today, these might need to be modified on
existing SIP Peer Profiles, not just the new ones for the
vendors.
If a customer Reserved all their SIP trunks, they either need to
get more licenses, use the “free” ones, or unreserve some
amount for emergency calls.
A customer who already has amount Unreserved, might want
to unreserve some more.
Disable Reliable Provisional This option needs to be set to YES.
Responses
If the Intrado Extension BIND feature is enabled, enable inward dialing on the Trunk Attributes for the
Intrado SIP Peer.
32
Define Emergency ARS Routes for each of the Intrado SIP Peer Profiles. Separate ARS Routes are
required to support resilient routing to the primary and secondary Intrado SIP Gateways.
NOTE: ARS Routes are subject to COR restriction; therefore, if you restrict a device from calling an
Emergency Route, the call will fail.
33
NOTE: Forfull resiliency coverage, it is recommended to have at least two MiVoice Business Trunking
Gateways, and that each has four SIP Peer Profiles:
• Intrado1 using MBG1 as the outbound proxy
• Intrdao1 using MBG2 as the outbound proxy
The SIP peers must 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.
Adding each of these ARS Routes to the Route List is required.
(RECOMMENDED) Define ARS Route List with the Emergency ARS Routes for the Intrado SIP Peer
Profiles in order.
34
NOTE: As a “last resort”, non-emergency ARS routes can be added AFTER all Intrado Routes to handle
a case where Intrado is completely down. These final ARS Routes in the list must 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.
Define ARS Route Dialed Digits to use the previously defined ARS Route List. Ensure that 911 is dialable
without any prefix or suffix digits and.
NOTE: IFT/EFT sites might want to add a 933 ARS route for testing purposes.
35
CONFIGURE NON-TRUNKING GATEWAYS TO USE MIVOICE BUSINESS TRUNKING GATEWAYS TO
CHAPTER 11 ACCESS INTRADO DEPLOYING GUIDE: MIVOICE BUSINESS SIP TRUNKING TO INTRADO USING
MBG AS AN OUTBOUND- PROXY.
Configure Non-Trunking Gateways to use MiVoice

Business Trunking Gateways to Access Intrado
Create Emergency IP Trunking ARS Route to 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.
35
NOTE: Direct IP Trunking is not required (IP/XNET Trunk Groups can be used but is more complicated to
program).
(Optional) Define ARS Route List. Provide resilient routing to MiVoice Business Trunking Gateway(s) is
recommended.
Define ARS Route Dialed Digits to use the previously defined ARS Route List.
36
37
CHAPTER 12 DEPLOYMENT GUIDE: EMERGENCY CALLBACKS
Deployment Guide: Emergency Callbacks

For Emergency Callbacks, using the Intrado Extension Bind feature with a private SIP Trunk to Intrado is
suggested, because this eliminates the need of having to provide CPN/DID programming on each
user/device that can make an emergency call.
Otherwise, CPN Substitution and DID Services to complete the emergency callback can be programmed
as described in this section.
• CPN Substitution is used for identifying the Calling Party Number and is used as the Emergency Call-
back number.
NOTE: The same CPN is used for non-emergency and emergency calls.
NOTE: The CESID still replaces the CPN substitution number for emergency calls going over a SIP Peer
with the Emergency Call Header set to CESID in From, [and PAI] or Allow Privacy, CESID in PAI.
• The DID number is used by MiVoice Business to route an incoming call based on the Digits Dialed.
For a proper callback to occur, the CPN sent to Intrado must be routable back to the MiVoice Business
where the called digits are matched to the DID number and route the call to the programmed destination. It
is recommended to have a unique CPN/DID for each User/Device 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.
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)
38
CHAPTER 12 DEPLOYMENT GUIDE: EMERGENCY CALLBACKS
NOTE: Because the MiVoice Business/Intrado solution will not use the CESID as the callback
destination, the MiVoice Business Emergency DID Routing feature must be disabled in the Shared
System Options form.
NOTE: If Direct Inward Dialing Service is used, the Trunk Attributes for the incoming trunk must have Direct
Inward Dialing Service enabled.
39
CHAPTER 13 DEPLOYMENT GUIDE - DEFINING LOCATIONS
Deployment Guide: Defining Locations

The MiVoice Business Intrado solution requires that the administrator define locations (ERLS) as
required in the Intrado Portal. These ERL are typically linked to an MiVoice Business CESID based on
the ERL ID.
NOTE: The administrator is responsible for ensuring that the MiVoice Business CESID, ERL ID
programming, and the Intrado programming are aligned.
40
CHAPTER 14 DEPLOYMENT GUIDE - DEFINING ON-PREMISES WIRE MAPS
Deployment Guide: Defining On-Premises

Wire Maps
The MiVoice Business Intrado solution for On-Premise HELD clients (such as MiCollab SIP Softphone)
and 911 Location Manager clients (such as MiVoice Business Console, MiCollab MINET Softphones) use
Intrado’s ERS configuration to identify their location.
• Switches - Used for associating a location to a device based on wired connectivity to a L2 network
switch.
• Wireless Access Points - Used for associating a location to a device based on the MAC address of a
• Subnets - Used for associating a location to a device based on IP address configuration.
41
DEVICES THAT USE CESID (SUCH AS 69XX, SINGLE CELL DECT, AND 5634 WIRELESS)
CHAPTER 15 DEPLOYMENT GUIDE - DEVICE OVERVIEW
Deployment Guide: Device Overview

There are three different configuration models, depending on the device and its location. The information
on devices and their specific configuration model is detailed later in the document.
Devices that use CESID (such as 69xx, Single Cell DECT,

and 5634 Wireless)
Step 1:Add a location to the Intrado Portal.
Through the Provisioning portal, select add ERL, and define the location.
• ERL Name - Customer defined label to identify the location

42
After the address is validated, define the routing options.
• Custom Callback - If configured, the ERS Custom Callback number will override the callback number
sent by the MiVoice Business. It should be noted this callback is based on the location of the caller
as it is tied to the CESID/ERL ID, rather than the caller’s callback number.
• Email Notifications - Recommended to use the Intrado Account-based email notifications instead of
ERL specific email notifications (see below).
• ERL ID - CESID from the device or MiVoice Business must match the FROM in the SIP Invite.
Step 2: Program the CESID information in the MiVoice Business.
CESID Configuration Steps

Alternatives
CESID sent by Program the CESID on the SIP device.
the device NOTE: Configuration depends on the device type.
(limited to SIP On MiVoice Business, enable Emergency Info Provided by Device in the SIP
devices) Device Capabilities.
NOTE: Valid CESIDs are digit strings of 1-12 digits and length and 0-9 are the
43
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.
44
CESID Alternatives Configuration Steps
BSSID to CESID Mapping On the 5634 device, enable the MAC address of the Wireless Access
(limited to 5634) Point to be sent on all calls.
NOTE: Configuration depends on the device type.
On MiVoice Business, enable Emergency Info Provided by Device in
the SIP Device Capabilities.
On MiVoice Business, program the BSSID to CESID Mapping.
45
L2 to CESID Mapping (limited to On 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 MiVoice Business, configure the L2 to CESID Mapping.
NOTE: MiVoice Business supports only one device per L2 Port.
46
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.
47
On 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)
48
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.
49
DEVICES THAT USE INTRADO’S 911 LOCATION MANAGER (SUCH AS MiVoice Business Console)
CESID Assignment On MiVoice Business, program the CESID against the device in
the CESID Assignment form.
Some Off-Premise MiNET devices (For example, select 53xx,

69xx) 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.
50
Devices that use Intrado’s 911 Location Manager (such as

MiVoice Business Console)
Step 1: Add the enterprise FQDN
• Fully Qualified Domain Name (FQDN) - Used by the 911 Location Manager application to determine if
the client is on- site or off-site.
Step 2: Configure the Location Manager Subnets (optional) for off-site clients connecting through a VPN.
• Subnet Name - Customer-defined label to identify the subnet.
• Subnet Mask - IP address + Subnet Mask (CIDR format)
• LM Behavior - Determines whether an off-site client on this subnet must ask for the Location, or use
the location as programmed in step 4 below.
Step 3: Add a location to the Intrado Portal for On-Premise 911 Location Manager Clients.
Through the Provisioning portal, select add ERL, and define the location.
51
After the address is validated, define the routing options

• Email Notifications - Recommend that you use the Intrado Account-based email notifications instead
• ERL ID - CESID from the device or MiVoice Business, must match the FROM in the SIP Invite.
52
Step 4: Program the On-Premise wire map in the Intrado Portal for on-premise 911 Location Manager
clients.
Use SUBNETS to define an association between a Location and an IP address.
• Subnet NAME - Customer-defined name to help identify the subnet/location.
• Subnet MASK - IP address/Subnet Mask (CIDR format).
• ERL - Location of that subnet (defined in Step 1)
Use Wireless Access Points to define an association between a Location and the MAC address Wireless
of a Access Point.
• Wireless Access Point Name - Customer-defined name to help identify the Wireless Access
Point/Location
• BSSID - MAC Address of the Wireless Access Point. (Can be a list of BSSIDs).
• ERL - Location of that Wireless Access Point.
53
Step 5: Define the Subscriber in the Intrado Portal for all 911 Location Manager clients.
• Subscriber ID - If you are private SIP Trunks between the MiVoice Business and Intrado, this will be
the DN of the device, unless the device is in an MDUG, if in an MDUG, it is the prime DN of the
MDUG. If using a public SIP Trunk, this will be the CPN/DID for the user.
NOTE: If the customer has a network of multiple MiVoice Business clusters, care needs to be taken
on how to handle the Primary Node ID (PNI). The DN must be PNI prefixed unless you are using the
Strip PNI option in the SIP Peer Profile on MiVoice Business.
• What ERL to associate to - Select do not associate to any ERL. The 911 Location Manager application
adds the association when it detects a change.
Step 6: On MiVoice Business, enable CESID not required for Emergency Calls on the device’s COS
option, for all 911 Location Manager clients.
54
DEVICES THAT USE GEOLOCATION (SUCH AS MICOLLAB SIP SOFTPHONE CLIENT)
Step 7: Install the 911 Location Manager application on the same PC as the device (MiVoice Business
Console, MiCollab MiNET Softphone).
Devices that use Geolocation (such as MiCollab SIP Soft-

phone Client)
NOTE: How a HELD client determines if they are on-site vs off-site depends on the client.
NOTE: Whether a HELD client supports Subnets, Wireless Access Points, or Switches depends on the
individual clients.
Step 1: Add a location to the Intrado Portal for On-Premise HELD clients through the Provisioning portal,
select add ERL, and define the location.
Via the Provisioning portal, select add ERL, and define the location.
53
After the address is validated, define the routing options.

• Email Notifications - recommended to use the Intrado Account-based email notifications instead
• ERL ID - CESID from the device or MiVoice Business must match the FROM in the SIP Invite.
54
Step 2: Program the On-Premise wire map in the Intrado Portal for on-premise HELD clients
Use SUBNETS to define an association between a Location and an IP address.
• Subnet NAME - customer defined name to help identify the subnet/location.
• Subnet MASK - IP address/Subnet Mask (CIDR format).
• ERL - Location of that subnet (defined in Step 1)
Use Wireless Access Points to define an association between a Location and the MAC address of the
• Wireless Access Point Name - customer defined name to help identify the Wireless Access
Point/Location
• BSSID - MAC address of the Wireless Access Point. (Can be a list of BSSIDs).
• ERL - Location of that Wireless Access Point.
Use Switches to define an association between a location and a L2 Network Switch

Switches
• Switch name- customer defined name to help identify the switch/location.
• Chassis ID - ID of the Chassis (must match the information from the network switch)
• ERL - The location of the switch (used when there are no ports, or the ports have no ERL)
55
Ports
• Port name - customer defined name to help identify the port/location.
• Port ID - ID of the Port (must match the information from the network switch).
• ERL - The location of the port.
Step 3: Define the Subscriber in the Intrado Portal for all HELD clients
• Subscriber ID - If you are private SIP Trunks between the MiVoice Business and Intrado, this will be
the DN of the device. If using a public SIP Trunk, this will be the CPN if programmed, otherwise the
DN.
NOTE: The DN must be PNI prefixed, unless you are using the Strip PNI option in the SIP Peer Profile
(on the MiVoice Business).
• What ERL to associate to - Select do not associate to any ERL. The HELD client will update the
association when it detects a change.
Step 4: On the MiVoice Business, enable Emergency Info Provided by Device in the SIP Device
Capabilities
56
ON PREMISES
CHAPTER 16 DEPLOYMENT GUIDE: 69XX MINET
Deployment Guide: 69xx MiNet

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

• Program an ERL with ERL ID matching the
CESID of the L2 Port.
• Program a Subscriber to match the DN of
the user/device. (CPN if available and using
a public SIP Trunk)
MiVoice Business:
• Define the L2 to CESID Mapping
Device:
• None
IP to Zone to CESID Mapping Intrado:

CESID of Zone.
a public SIP Trunk)
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.
Device:
• None
57
OFF PREMISES
CHAPTER 16 DEPLOYMENT GUIDE: 69XX MINET
Off Premises
CESID Assignment Intrado:

CESID of CESID Assignment
a public SIP Trunk)
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
Intrado. The MiVoice Business will
generate an Audit Trail when the
notification has been acknowledged by
the user
Device:
• None.
58
ON PREMISES
CHAPTER 17 DEPLOYMENT GUIDE: 53XX MINET (5304, 5312, 5320, 5320E, 5330E, 5340E)
Deployment Guide: 53xx MINET (5304, 5312,

5320, 5320e, 5330e, 5340e)
On Premises

a public SIP Trunk).
MiVoice Business:
Device:
• None

CESID of the Zone.
a public SIP Trunk)
MIVOICE BUSINESS:
form
form.
Device:
• None
59
OFF PREMISES
CHAPTER 17 DEPLOYMENT GUIDE: 53XX MINET (5304, 5312, 5320, 5320E, 5330E, 5340E)
Off Premises

CESID of the CESID Assignment
a public SIP Trunk)
MiVoice Business:
• Define the CESID of the device.
the user
Device:
• None
NOTE: The device user will be notified of a possible
device move and will instruct them to contact the
Administrator to correct the location in Intrado.
The MiVoice Business will generate an Audit
Trail when the notification has been
acknowledged by the user.
60
ON PREMISES
CHAPTER 18 DEPLOYMENT GUIDE: LEGACY MINET 53XX
Deployment Guide: Legacy MINET 53xx
On Premises

MiVoice Business:
Device:
• None

CESID of the Zone.
MiVoice Business:
form
form.
Device:
• None
Off Premises
Not recommended as these devices do not support Device Move Detection
61
ON PREMISES
CHAPTER 19 DEPLOYMENT GUIDE: LEGACY MINET (50XX, 51XX, 52XX, 5560 IPT, NAVIGATOR)
Deployment Guide: Legacy MINET (50xx,

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

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

CESID of the CESID Assignment.
MiVoice Business:
form
form.
Device:
• None
Off Premises
Not recommended as these device do not support device move detection.
62
ON PREMISES
CHAPTER 20 DEPLOYMENT GUIDE: 5540
Deployment Guide: 5540
On Premises

MiVoice Business:
Device:
• None

CESID of the Zone.
MiVoice Business:
form
form.
Device:
• None
63
OFF PREMISES
CHAPTER 20 DEPLOYMENT GUIDE: 5540
Off Premises

MiVoice Business:
• Define the CESID of the device.
the user
Device:
• None
NOTE: The device user will be notified of a possible
device move and will instruct them to contact the
Administrator to correct the location in Intrado.
The MiVoice Business will generate an Audit
Trail when the notification has been
acknowledged by the user.
64
ON PREMISE
CHAPTER 21 DEPLOYMENT GUIDE: MiVoice Business Console
Deployment Guide: MiVoice Business

Console
On Premise
911 Location Manager Application Intrado:

(RECOMMENDED if device is wireless) • Program the enterprise FQDN
• Program the Network wire map as required
MiVoice Business:
• Enable the CESID not required for Emergency
Calls COS option.
Device:
• Install the Application given the
Subscriber ID.
• Manage the location via the 911 Location
Manager application.
(RECOMMENDED if device is wired) • Program an ERL with ERL ID matching the
CESID of Zone.
MiVoice Business:
form
form.
Device:
None
65
OOFF
FFPPREMISE
REMISE
CHAPTER 21 DEPLOYMENT GUIDE: D
MiVoice Business
EPLOYMENT GUIDE: Console
MiVoice
Business Console
Off Premise

• Program the enterprise FQDN
• Program the Location Manager subnets
MiVoice Business:
Calls COS option.
Device:
• Install the 911 Location Manager Application
given the Subscriber ID.
66
ON PREMISES
CHAPTER 22 DEPLOYMENT GUIDE: GENERIC SIP
Deployment Guide: Generic SIP

NOTE: Because each Generic SIP Softphone might have different implementations, Mitel will need to
certify the solution with each specific Generic SIP Set.
On Premises
Geo-Location Intrado:
MiVoice Business:
• Enable the Emergency Info Provided by
Device SIP Device Capability for the device.
Device:
• Program the Intrado HELD URL, account ID,
and token.
• Update the location
CESID provided by the device Intrado:

CESID of the device.
MiVoice Business:
• Enable the Emergency Info Provided by the
Device for the SIP Device Capability
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.
67
ON PREMISES
BSSID to CESID Mapping Intrado:

CESID of BSSID to CESID Mapping.
MiVoice Business:
• Define the BSSID to CESID the BSSID to
CESID
Device:
• Enable the MAC address of the Wireless
Access Point being used for the call to be sent.

CESID of Zone.
MiVoice Business:
form
form.
Device:
• None
68
OFF PREMISES

MiVoice Business:
Calls COS option.
Device:
NOTE: This option must be used only where 911
Location Manager application can be installed
alongside.
Off Premises
Geolocation Intrado:
MiVoice Business:
Device:
• Program the Intrado HELD URL, account ID,
and token.
• Update the location
69
OFF PREMISES

• Program a Location to match the CESID of the
device.
MiVoice Business:
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.
CESID of BSSID to CESID mapping.
MiVoice Business:
• Define the BSSID to CESID Mapping
Device:
• Enable the MAC address of the Wireless
Access Point being used for the call to be sent.
70
OFF PREMISES

MiVoice Business:
Calls COS option.
Device:
NOTE: This option must be used only where 911
Location Manager application can be installed
alongside.
71
ON PREMISES
CHAPTER 23 DEPLOYMENT GUIDE: SINGLE CELL DECT (6XX/56XX)
Deployment Guide: Single Cell DECT (SIP

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

MiVoice Business:
Device SIP Device Capability
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. Special characters or text is not
supported and may result in a failed
emergency call.
CESID of Zone.
MiVoice Business:
form
form.
Device: None
72
OFF PREMISES
CHAPTER 23 DEPLOYMENT GUIDE: SINGLE CELL DECT (6XX/56XX)
Off Premises

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. Special characters or text is not
supported and may result in a failed
emergency call.
73
CHAPTER 24 DEPLOYMENT GUIDE: SIP DECT (6XX)
Deployment Guide: SIP DECT (6xx)

As of SIP-DECT Release 8.3SP1, 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 has made.
An ELIN can be set for:
• the system
• a site
• a specific base station
The more specific parameter value is used to help 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 OMM web service or via OMP. Only the general activation of this
feature and the system-wide emergency location identification number can be set via the OMM
configuration files.
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.
Format Boolean
Range 1 or true (enable)0 or false (disable)
Default value False
74
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. 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 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
75
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 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
76
If ELIN support is enabled and at least one RFP has no ELIN assigned, a warning is displayed on the
status information page.
77
ON PREMISES
CHAPTER 25 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 Premises

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.
• 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.
78
ON PREMISES

CESID of Zone.
MiVoice Business:
form
form.
Device:
• None
79
OFF PREMISES
Off Premises

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.

characters or text is not supported and
may result in a failed emergency call.
79
ON PREMISES
CHAPTER 26 DEPLOYMENT GUIDE: MULTI-CELL DECT (6XX)
Deployment Guide: Multi-Cell SIP DECT

(6xx)
On Premises

MiVoice Business:
Device:
• ELIN must be configured on the Base
Station->Advanced->Emergency->ELIN
page. See section “Deployment Guide:
SIP DECT 6xx” for more details.
characters or text is not supported
and may result in a failed emergency
call.
80
ON PREMISES
Off Premises

MiVoice Business:
Device:
• ELIN must be configured on the Base
Station->Advanced->Emergency->ELIN
page. See section “Deployment Guide:
SIP DECT 6xx” for more details.
call.
81
ON PREMISES
CHAPTER 27 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.
82
ON PREMISES
On Premises

MiVoice Business:
Device:
• See configuration at start of chapter.
call.
Off Premises

MiVoice Business:
Device:
• See configuration at start of chapter.
call.
83
ON PREMISES
CHAPTER 28 DEPLOYMENT GUIDE: 5634 WI-FI
Deployment Guide: 5634 Wi-Fi
On Premises

• Program an ERL with ERL ID matching the CESID of the BSSID to
CESID mapping.
• Program a Subscriber to match the DN of the user/device. (CPN
if available and using a public SIP Trunk).
MiVoice Business:
• Enable the Emergency Info Provided by the Device SIP Device
Capability
Device:
82
OFF PREMISES
CHAPTER 28 DEPLOYMENT GUIDE: 5634 WI-FI
Off Premises

• Program an ERL with ERL ID matching the CESID of the BSSID to
CESID mapping.
• Program a Subscriber to match the DN of the user/device. (CPN
if available and using a public SIP Trunk).
MiVoice Business:
• Enable the Emergency Info Provided by the Device SIP Device
Capability
Device:
83
ON PREMISE
CHAPTER 29 DEPLOYMENT GUIDE: LEGACY SIP (5302, 5505, 5624)
Deployment Guide: Legacy SIP (5302, 5505,

5624)
On Premise

CESID of Zone.
MiVoice Business:
form
form.
Device:
• None
Off Premise
Not recommended.
84
ON PREMISE
CHAPTER 30 DEPLOYMENT GUIDE: MICOLLAB MINET SOFTPHONE
Deployment Guide: MiCollab MINET Soft-

phone
On Premise
Options Available Steps

(RECOMMENDED if device is wired) • Program an ERL with ERL ID matching the
MiVoice Business:
form
form.
Device:
• None
(RECOMMENDED if device is wireless) • Program the enterprise FQDN
MiVoice Business:
Calls COS option.
Device:
85
OFF PREMISE
CHAPTER 30 DEPLOYMENT GUIDE: MICOLLAB MINET SOFTPHONE
Off Premise

MiVoice Business:
Calls COS option.
Device:
86
CHAPTER 31 DEPLOYMENT GUIDE: MICOLLAB SIP SOFTPHONE
Deployment Guide: MiCollab SIP Softphone

NOTE: MiCollab Clients installed on a mobile device with a native Dialer (such as, Apple phones and
Android phones; not tablets), the native dialer will intercept emergency calls, and will not go through the
MiVoice Business.
Additional Configuration is required on MiCollab server for MiCollab SIP Softphones.

Via the MiCollab Server, configure the Location Service under MiCollab Client Service > Administrator
Interface > Enterprise Tab > Location Service Configuration.
Field Notes
Location Service Choose Intrado from the location service

dropdown.
URL The URL of Intrado location service.
Account Id This can be obtained from the Intrado location
service portal under the Administration Tab->
Authentication Tokens. This is the same Account
ID also displayed on the Account Dashboard page
in the General Information pane.
Token This can also be obtained from the Intrado
location service portal under the Administration
Tab-> Authentication Tokens.
Internal FQDN The Internal FQDN URL is required by Intrado.
This URL is accessible only through the office
network. Internal FQDN is used to determine
whether you are in office network or not.
Note: Internal FQDN will not be validated by the
server.
87
Virtual Environment The Virtual Environment checkbox must be

selected if the clients are running in a virtual
environment. This means that, the Virtual
Environment checkbox enables the administrator
to declare whether their clients are virtualized or
not; VMWARE Horizon, Citrix, or RDS.
The values for Account ID and Token can be found on the Intrado portal under Administration ->
Authentication Tokens.
Via the MiCollab Server, configure the Emergency Dial Plan under MiCollab Client Deployment>
Deployment Profiles > Emergency Numbers.
NOTE: IFT/EFT sites must enable 933 in the emergency number list for testing/integration.
88
Additionally, each MiCollab Client will need to install the Mitel Network Helper, and enter/confirm their
location in the MiCollab Client.
89
NOTE: This might appear slightly different based on the type of MiCollab Client.
90
ON PREMISES
On Premises
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 Premises
MiVoice Business:
MiCollab Server:
MiCollab Client:
Client
90
CHAPTER 32 SOLUTION DEPLOYMENT GUIDE - MICOLLAB WEB CLIENT
Solution Deployment Guide - MiCollab Web

Client
NOTE: IFT/EFT sites must enable 933 in the emergency number list for testing/integration.
Additional Configuration is required on MiCollab server for MiCollab SIP Softphones.
Via the MiCollab Server, configure the Location Service under MiCollab Client Service > Administrator
Interface > Enterprise Tab > Location Service Configuration.
Field Notes
Location Service Choose Intrado from the location service

dropdown.
URL The URL of Intrado location service.
Account Id This can be obtained from the Intrado location
service portal.
Token This can also be obtained from the Intrado
location service portal.
Internal FQDN The Internal FQDN URL is required by Intrado.
This URL is accessible only through the office
network. Internal FQDN is used to determine
whether you are in office network or not.
Note: Internal FQDN will not be validated by the
server.
Virtual Environment The Virtual Environment checkbox must be
selected if the clients are running in a virtual
environment. This means that, the Virtual
Environment checkbox enables the administrator
to declare whether their clients are virtualized or
not; VMWARE Horizon, Citrix, or RDS.
91
Via the MiCollab Server, configure the Emergency Dial Plan under MiCollab Client Deployment >
Deployment Profiles > Emergency Numbers.
Additionally, each MiCollab Client will need to install the Mitel Network Helper and enter/confirm their
location in the MiCollab Client.
92
NOTE: This might differ based on the MiCollab Client.
93
ON PREMISES
On Premises
MiVoice Business:
MiCollab Server:
• Define the Emergency dial plan
MiCollab Client:
Client
Off Premises
• Program a Subscriber to match the DN of the
user/device. (CPN, if available, while using a
public SIP Trunk).
MiVoice Business:
• Enable the Emergency information provided by
MiCollab Server:
MiCollab Client:
Client
94
CHAPTER 33 DEPLOYMENT GUIDE: MICOLLAB DESKPHONE
Deployment Guide: MiCollab Deskphone

Follow the instructions based on the device type of the Deskphone.
95
CHAPTER 34 DEPLOYMENT GUIDE: MICOLLAB MOBILE
Deployment Guide: MiCollab Mobile

MiCollab uses native dialer; Therefore, there is no interaction with the MiVoice Business solution for
emergency calls.
96
CHAPTER 35 DEPLOYMENT GUIDE - THIRD-PARTY WEBRTC CLIENTS (VIA MBG)
Deployment Guide - Third-Party WebRTC

Clients (via MBG)
NOTE: Because each third-party WebRTC Client might have different implementations, Mitel will need to
certify the solution with each specific Third-party WebRTC Client.
WebRTC is an HTML wrapper around the SIP protocol; therefore, it behaves like a Generic SIP device.
See above.
97
LIMITATIONS
CHAPTER 36 DEPLOYMENT GUIDE - WEBRTC ANONYMOUS CALLS (VIA MBG)
Deployment Guide - WebRTC Anonymous

Calls (via MBG)
WebRTC can provide anonymous calls support via a web-link. These web-links are not expected to be
routed from MiVoice Business to an emergency destination, and DO 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 different NG911 providers per tenant in the same system. For
example, the same NG911 provider needs to be used by all tenants in a given system.
98
CHAPTER 37 ACRONYMS, ABBREVIATIONS, AND GLOSSARY
Testing the Intrado Integration and Reading

Call Detail Records(CDR)
As part of on boarding with Intrado, customers will be required to go through a rigorous acceptance test
plan on a Demo system before officially going to Production.
Intrado offers a couple of ways to test emergency calls in Demo mode.
933 Test Calls

Customers can use the 933 service to confirm both Subscriber and Location(ERL) configuration. To
access this service, configure 933 calls to route the Intrado SIP trunks previously described in this guide,
along with all the other required endpoint, MiVoice Business and Intrado programming.
When the 933 test calls is made and Intrado IVR will answer the calls and audible confirm the callers
Subscriber ID and current Location(ERL). It will also allow the caller to make a recording to be played
back to the caller in the same call to confirm a 2-way audio path.
When the call is complete, a Call Detail Record(CDR) will be generated providing details of the call, more
details in the section below.
The Extension Bind(XBind) feature, if enabled, is not applied on these types of test calls.
933 test call support is also available on the Production system.
More information in Call Detail Record section below.
911 Test Calls

Customers can use the 911 service to confirm emergency callback configuration. These are NOT real
911 calls and will not go out to the PSAP, they are for testing only when in Demo mode. To access this
service, configure 91 calls to route the Intrado SIP trunks previously described in this guide, along with all
the other required endpoint, MiVoice Business and Intrado programming.
When the 911 test calls is made, Intrado will answer the call and the call should just be cancelled once
the caller hears ringback.
When the call is complete, a Call Detail Record(CDR) will be generated providing details of the call, more
details in the section below.
The Extension Bind(XBind) feature, if enabled, is not applied on these types of test calls.
More information in Call Detail Record section below.
99
Call Detail Records(CDR)
After the emergency test calls described above have been completed, what has been sent to Intrado by
the MiVoice Business can be reviewed in Intrado’s Call Detail Records(CDRs). These records can be
found below.
Once on this page, you should entries like below
It includes the following information:

• Start Time of the call
• Account Name the call is associated
• Call Type, where 911 is a 911 call and Test is a 933 call
• Call Status where Completed means the call was answered by Intrado or PSAP which applies to
933 calls only or real answered 911 calls, and Cancelled means the call was not answered, which
applies to 911 test calls only or real 911 calls that the caller dropped.
• Duration of the call once answered by Intrado or PSAP. Applies to 933 test calls and real 911
calls. It will be blank for Cancelled calls.
• Subscriber ID of the caller. This information is sent to Intrado in the PAI header of the SIP Invite by
the MiVoice Business and needs to match a Subscriber programmed on Intrado. If it does not
match a Subscriber, it will still be marked as Completed, but will be highlighted as RED and for real
911 calls, will go to the ECRC.
• ERL ID of the caller. This will be CESID configured on the MiVoice Business for the location the
caller is making the emergency call from and will be sent to Intrado in the FROM header of the SIP
Invite. If this does not match a programmed ERL ID, it will be marked RED and for real 911 calls,
will be sent to the ECRC. This will be populated by a GUID generated by Intrado for callers using
the E911 Location Manager application or endpoints using the HELD protocol like the MiCollab SIP
Client
• Address Information. This is the location Intrado has mapped their ERL ID from the CESID
provided in the FROM header of the SIP Invite for the MiVoice Business.
• Callback Number. This is the number the caller would be called back on should the emergency
call drop. For 933 test calls, this will always be Intrado’s main number, 514-745-2143 and should
not be used for callback testing purposes. For 911 test calls, this will be blank, however, if email
notifications are enabled for the ERL ID, the email notification will contain the callback number.
For real 911 calls it will be populated. The callback number presented in this field(and email
notification) will be DID/CPN number provided as the Subscriber ID if using Public SIP trunks with
Intrado. If using Private SIP Trunks with Intrado, where the Extension Bind feature is enabled, this
is the DID number assigned to the Subscriber ID received in the emergency call by the Extension
100
Bind feature. For 911 test calls, this number can be called through the PSTN from any phone to
confirm the calls reaches Intrado and they map to the correct Subscriber and caller receives a call
through the Intrado SIP trunks. The call can be answered to confirm audio path.
• Call Destination: Indicates where the call was routed. For successful test calls, this will be
VPSAP, Intrado’s Virtual PSAP. For real 911 calls, this will be PSAP. For test or real calls marked
RED due not finding a match for a Subscriber or location, this will be ECRC.
• Provisioned: If Yes, both a Subscriber and Location were found. If No, no Subscriber or Location
was found and the entry will be marked RED.
• Actions. The folder icon can be selected to provide more details about the call, included details of
the SIP Invite headers, as seen below. This information can be useful to further debug any issues.
• Much of this information was provided in the previous CDR table record and will just highlight
some additional fields of note.
o Account ID associated to this emergency call.
o ERL Determination Method. Indicates the lookup algorithm being used by Intrado to
match on Subscribers and ERLs. For the MiVoice Business solution, this should be
CUSTOMER_LOCATION_ID. If this field shows any other value, contact Intrado to
ensure the Location Determination Preference is set to ERL ID in SIP header for the
account.
o Account Mode. Indicates if you are using the account in Demo or Production mode.
o Incoming DNIS. Provides details of the SIP Invite TO header indicating the emergency
number called.
o Incoming FROM. Provides details of the SIP Invite FROM header indicating the CESID
sent from the MiVoice Business to Intrado to match an ERL ID. This will be set to
ANONYMOUS for calls from devices using the E911 Location Manager, endpoints
using the HELD protocol like the MiCollab SIP Client or calls in which the MiVoice
Business cannot find a CESID for.
o Incoming CONTACT. Provides details of the SIP Invite CONTACT header and it should
match the PAI. This field is not used in this solution.
o Incoming PAI. Provides details of the SIP Invite PAI header indicating the number that
will be used to match to an Intrado Subscriber.
o Incoming E911-Organization-ID. This should match the value configured in the User-
Defined Header Value field in the Intrado SIP Peer Profile and is provided by the E911-
Organization-ID header in the SIP Invite.
101
Troubleshooting
The intent of this section to help troubleshoot common issues in the solution and is not exhaustive.
Symptom Troubleshooting Steps
Intrado is not receiving • Capture a wireshark trace to confirm if the SIP Invite is leaving the MiVoice
emergency calls Business and MBG
• If the SIP Invite is not leaving the MBG, review MBG configuration and logs.
• If the SIP Invite is not leaving the MiVoice Business, review MiVoice Business
configuration and logs.
• If after reviewing the programming/logs and the calls are still not leaving the
MiVoice Business/MBG, contact Mitel Product Support.
• If the SIP Invite is leaving the MiVoice Business and/or MBG, confirm with
Intrado that the proper IP addresses are being used by Intrado and the
MiVoice Business/MBG.
Intrado’s CDRs for • Review CDR details to see what is being received and confirm the Subscriber
emergency calls are in the PAI is provisioned and/or the CESID provided in the FROM is
marked RED. provisioned.
• Confirm CDR ERL Determination Method is set to ERL ID in SIP header. If not,
contact Intrado to ensure the Location Determination Preference for the account
is set to ERL ID in SIP header.
• Confirm the Route Assignment is an Emergency route for emergency calls.
• If problems are still observed, contact Intrado Product Support
The Subscriber provided in • Confirm CDR ERL Determination Method is set to ERL ID in SIP header. If not,
the emergency call is contact Intrado to ensure the Location Determination Preference for the account
incorrect. is set to ERL ID in SIP header.
• If ERL Determination Method is correct confirm:
o Emergency Call Headers field in the SIP Peer Profile is set to CESID in From,
Callback in PAI.
o If Intrado Subscribers are configured as internal DNs, ensure the SIP Peer
Profile field Private Trunk is set to Yes.
o If Intrado Subscribers are configured as DIDs, ensure the SIP Peer Profile field
Private Trunk is set to No.
• If problems are still observed, contact Mitel Product Support
The location provided in the• Confirm CDR ERL Determination Method is set to ERL ID in SIP header. If not,
emergency call is incorrect. contact Intrado to ensure the Location Determination Preference for the account
• If ERL Determination Method is correct confirm:
o Emergency Call Headers field in the SIP Peer Profile is set to CESID in From,
Callback in PAI.
• If the call is made from device for which the MiVoice Business provides the
CESID, review the Deployment Guide chapter for that device in this document
regarding configuration.
• If the call is made from device that provides the CESID during an emergency
call, review the Deployment Guide chapter for that device in this document to
ensure configured correctly.
• If problems are still observed, contact Mitel Product Support.
Emergency Callbacks are • Confirm CDR ERL Determination Method is set to ERL ID in SIP header. If not,
not working contact Intrado to ensure the Location Determination Preference for the account
• If Intrado Subscribers are configured as internal DNs, contact Intrado to ensure
the Location Determination Preference is set to Extension Bind.
• If Location Determination Method is correct confirm:
o Emergency Call Headers field in the SIP Peer Profile Configuration is set to
CESID in From, Callback in PAI.
o If Intrado Subscribers are configured as internal DNs, ensure the SIP Peer
Profile field Private Trunk is set to Yes.
102
o If Intrado Subscribers are configured as DIDs, ensure the SIP Peer Profile field
Private Trunk is set to No
• If the Location Determination Method is set to Extension Bind, callbacks will be
coming to the MiVoice Business through the Intrado SIP trunk and care should
be taken to ensure the routing of these inbound calls are handled as these
calls will contain the internal DN is the FROM header of the SIP Invite.
Emergency Calls are not • Confirm CDR is displaying the value Emergency Organization ID in SIP Peer
routed to the correct Intrado Profile. If they do not match, contact Intrado Product Support.
account
Contacting Mitel Product Support

If it is required to contact Mitel Product Support, please be ready to provide the following:
1. Intrado Account Number
2. CDR from Intrado for any failed calls.
3. SIP trunk wireshark traces between the MiVoice Business and Intrado, including MBG.
4. SIP endpoint wireshark traces between a SIP endpoint making an emergency calls and the
MiVoice Business, including MBG if applicable.
5. Provide a CCS trace on the MiVoice Business for the failed call.
6. Software release versions for the MiVoice Business and MBG, along with system logs.
7. Firmware release versions of devices making the emergency calls, along with device logs
Contacting Intrado Product Support

If it is required to contact Intrado Product Support, please be ready to provide the following:
1. Intrado Account Number
2. Type of Mitel PBX being integrated as Intrado is supporting multiple Mitel PBXs, not just the
MiVoice Business.
103
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 Intrado solution, the CESID is only used as a location identifier by Intrado
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.
ECRC - Emergency Call Relay Center(ECRC). This Intrado service will be called if the emergency call
they have received from the PBX cannot find the Subscriber or Location of the caller. The ECRC will
answer the emergency call and transfer it to the local emergency services
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.
GUID - Globally Unique Identifier. It is a 128-bit integer number used to identify resources. Intrado
generates GUIDs for ERL ID locations for user’s reporting their location through the 911 Location
Manager or devices using the HELD protocol, like the MiCollab SIP Softphone.
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.
104
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)
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 MiVoice Business
clusters in the same MiVoice Business network.
PSAP - 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
105

Mivb Intrado Raybaum

Uploaded by

Copyright:

Available Formats

Mivb Intrado 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 Intrado 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

Solution: How the Integration Works .................................................................................................. 12

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

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

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

Solution: Mitel Applications with RAY BAUM’s Act Support ................................................................... 19

Solution: Mitel Applications without RAY BAUM Support ................................................................... 20

Solution: Deployment Diagrams .......................................................................................................... 21

Deployment Guide: Emergency Callbacks............................................................................................ 38

Deployment Guide: Defining Locations ............................................................................................... 40

Deployment Guide: Defining On-Premises Wire Maps ........................................................................ 41

Deployment Guide: Device Overview .................................................................................................. 42

Deployment Guide: 69xx MiNet .......................................................................................................... 57

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

Deployment Guide: MiVoice Business Console .................................................................................... 65

Deployment Guide: Generic SIP .......................................................................................................... 67

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

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

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

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

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

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

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

Deployment Guide: MiCollab MINET Soft- phone ................................................................................ 85

Deployment Guide: MiCollab SIP Softphone ....................................................................................... 87

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

Deployment Guide: MiCollab Deskphone ............................................................................................ 95

Deployment Guide: MiCollab Mobile .................................................................................................. 96

Deployment Guide - Third-Party WebRTC Clients (via MBG) ............................................................... 97

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

Troubleshooting ................................................................................................................................ 102

Acronyms, Abbreviations, and Glossary ............................................................................................ 104

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 Section 506

Solution: MiVoice Business - RAY BAUM’s

Solution: Requirements for MiVoice Business - RAY BAUM

SIP DECT 6xx 8.3 SP1 Device-based provisioning of a CESID that is to

Locations The number of locations required to satisfy RAY BAUM’s Law.

Intrado Portal - ERS (Emergency Routing Service)

3. Configure Locations (ERLS - Emergency Routing Locations)

– Step 2: Configure the ERL’s Routing Options

– Step 3: Skip Enter Associations(optional)

Solution: How the Integration Works

NOTE: Using the default CESID is not recommended.

Fixed devices (legacy TDM devices)

Sending Data to Intrado

Emergency Callback and Extension Bind

Solution: MiVoice Business Location ID

Solution: MiVoice Business Device RAY