PBX Assessment

Report Generated On: 8-Sep-2020

Report Name: Example PBX Assessment

Disclaimer: The PBX Assessment report was auto-generated by the Univonix PBX Assessment
system and the data included is a representation of the customer data only. E&OE. The report
has been prepared for the exclusive use and benefit of the addressee(s) and solely for the
purpose for which it is provided. Unless we provide express prior written consent, no part of this
report should be reproduced, distributed or communicated to any third party. We do not accept
any liability if this report is used for an alternative purpose from which it is intended, nor to any
third party in respect of this report.

This document was auto-generated by Univonix

Table of Content
1 Introduction ......................................................................................................................................................... 3

1.1 Getting the Most from Your Assessment ..................................................................................................... 3

1.2 How to Read This Document ........................................................................................................................ 3

1.3 Feature Parity Challenges ............................................................................................................................. 4

2 Configuration Resources ...................................................................................................................................... 4

2.1 Files ............................................................................................................................................................... 4

3 Legacy PBX Review ............................................................................................................................................... 5

4 Cisco End Users & Extension Analysis .................................................................................................................. 5

4.1 Statistics ........................................................................................................................................................ 5

4.2 Feature Parity ............................................................................................................................................... 6

4.2.1 Overview ............................................................................................................................................... 6

4.2.2 Detailed Breakdown .............................................................................................................................. 7

5 Groups ................................................................................................................................................................ 10

5.1 Feature Parity Analysis ............................................................................................................................... 10

5.1.1 Overview ............................................................................................................................................. 10

5.1.2 Detailed Overview ............................................................................................................................... 11

6 Devices ............................................................................................................................................................... 12

6.1 Device Summary ......................................................................................................................................... 12

6.2 Device Details ............................................................................................................................................. 13

6.2.1 Detailed Device Breakdown. ............................................................................................................... 13

7 Glossary of Terms............................................................................................................................................... 15

Page 2 of 15
1 Introduction

1.1 Getting the Most from Your Assessment

The results presented in this document are an aggregated analysis of the data extracted from your CUCM. The
report analyzes and evaluates multiple aspects of your PBX configuration that affect migration from CUCM
into Microsoft Teams and is designed to shine a light on areas of complexity you might face. This report
delivers more than just raw numbers and data, it tells a story, the important information is found ‘between
the lines’, or in this case ‘behind the numbers’. The report will deliver deep insight and business value when
read in this way and integrated into your decision-making process towards moving your telephony system into
Microsoft Teams.1

1.2 How to Read This Document

The report uses color-coding to clearly define and sort feature parity gaps:

Green – designates entities such as lines and hunt groups that have been automatically assessed as migratable
to Microsoft Teams without any loss in feature functionality.

Yellow – designates entities such as lines and hunt groups, that can be migrated to Microsoft Teams but
where some feature functionality will be lost. The business impact of losing these features should be carefully
reviewed.

Example features where functionality will be lost:

Forward On Busy; is a feature that is not supported by Microsoft Teams

Simultaneous Ring to Multiple Destinations; Microsoft Teams enables Simultaneous Ring, but to only one
destination

Blue – designates entities whose migration status cannot be determined automatically. They must be
manually reviewed and will require a business decision and/or technical solution to resolve.

Examples:

End Users with Multiple Extensions; Microsoft Teams supports only one primary phone line per user. A
technical workaround could be adding configuration to the SBC whereas a business decision could be to
remove the extra lines.

Analog Phone; Microsoft Teams does not support analog phones directly. A technical solution could be to
connected the analog phones to Microsoft Teams via an on-prem SBC. Another solution might be to
connect these lines to IP phones

1
All product names, trademarks and registered trademarks are property of their respective owners

Page 3 of 15
Be aware, entities marked in green are not always supported out of the box and may require manual
customization.

Entities marked in yellow may have been configured in the CUCM for legacy reasons or reasons no longer
relevant when moving to Microsoft Teams. Typically, these features can be easily removed without any
business impact. For example, in most cases, Wakeup Call (which enables a user to book a call to their phone
as a reminder) can be removed with minimal business impact.

Carefully reviewing the various yellow-marked features can deliver a dramatic increase in the number of
entities that can be seamlessly migrated to Microsoft Teams.

The statistics in the Device and Extension sections of this report will help you scope the number and type of
devices you will need to replace and help you estimate the number of lines and licenses that will be required.

1.3 Feature Parity Challenges

Legacy PBX systems such as CUCM have existed for decades. Over the years, various features have been
added, however, many are seldom used. Modern UC system’s typically include a smaller set of telephony
features than those found in legacy systems, as a result there are feature gaps.

In addition, CUCM and Microsoft Teams use different data modeling that also leads to feature parity issues.

The CUCM data model consists of several main entities and flexible configuration options: end users, devices,
and lines. There can be a many-to-many relationship between the entities, e.g. a user may have multiple
devices, a device can have multiple lines, a line can be assigned to multiple devices.

Part of the migration effort is to convert the legacy PBX’s data model into the Microsoft Teams data model.
Some of the data can be easily converted whereas some conversions can have several solutions and will
require manual review.

2 Configuration Resources
The following table lists the files used for generating this report.

2.1 Files
File Name File Type Process Date
CUCM-Export.zip CUCM 12.5.1 6-Sep-2020

Page 4 of 15
3 Legacy PBX Review
Following are key high-level numbers extracted from the analysis of the CUCM configuration data:
Category Count Comment
Extensions 23,449 Lines that are associated with an end user or a standalone device
Cisco End Users 17,746
Orphan Cisco End Users 7,021 A Cisco End User not associated with any device or associated
with a device that has no lines; Subtotal of the Cisco End Users
Cisco Devices 30,880 A detailed breakdown is presented in section 6
Devices with Lines 30,026 Out of the total number of Cisco Devices
Devices without Lines 854 Out of the total number of Cisco Devices
Standalone Devices 14,228 A device that is not associated with an end user out of the total
number of devices
Devices enabled for extension 8,500 Out of the total number of Cisco Devices
mobility
CTI Ports 15 Number of CTI ports
Hunt Groups 360 Number of hunt pilots
Pickup Groups 421
Subscribed Services 6 Number of Subscribed Services used by Cisco Devices
Table 1 - Overview

4 Cisco End Users & Extension Analysis

4.1 Statistics
Description Count
Total number of Cisco End Users 17,746
Cisco End Users associated with a single physical device 369
Cisco End Users associated with multiple physical devices 1,943
Cisco End Users associated with both analog and non-analog devices 2
Cisco End Users associated with a PC softphone 10,600
Cisco End Users associated with a mobile application 1,669
Cisco End Users that have extension mobility 10,843
Orphan Cisco End Users 7,021
Table 2 - End User Statistics

Description Count
Total number of extensions 23,449
Extensions shared between multiple Cisco End Users and/or standalone devices 125
Cisco End Users associated with a single extension 10,205
Cisco End Users associated with multiple extensions 520
Standalone devices associated with a single extension 13,513
Standalone devices associated with multiple extensions 1
Table 3 - Extension Statistics

Page 5 of 15
4.2 Feature Parity
4.2.1 Overview
In order to identify feature parity gaps, the CUCM data model is mapped and compared to the Microsoft
Teams data model. From the 17,746 Cisco End Users, there are 10,725 associated with a device that has at
least one line and are convertible to a Microsoft Teams user (8 of these Cisco End Users are associated with
CTI ports). The remaining 7,021 Cisco End Users are orphans and no feature parity analysis was carried out on
these users.

There are 14,228 standalone devices that were mapped to 12,256 Microsoft Teams Common Area Phones.
This delta between the number of CUCM standalone devices and Microsoft Teams CAP’s is due to the variance
in data models between CUCM and Microsoft Teams. For example, in CUCM multiple physical devices that are
configured with the same line/s, will be converted to a single CAP in Microsoft Teams.

The analysis also found 300 analog devices. Therefore, the total number of analyzed entities for feature parity
is 23,273.
Target Entity Type Count
User 10,717 Feature Parity Analysis to Microsoft
Common Area Phone 12,256 Teams
Analog Phone 300 2%
Total 23,273
Table 4 - Target Entity Types 25%

73%

16972 Full feature parity 5779 Partial feature parity

522 Require manual review

Figure 1 - Feature Parity Analysis to Microsoft Teams

Page 6 of 15
4.2.2 Detailed Breakdown
The following table details the line and device features currently configured in the CUCM. Devices that have
no lines associated to them are not included. The count column indicates the usage of this feature; individual
entities can use more than one feature and each will be counted separately (e.g. a single end-user that has
both simultaneous ring and forward on no answer will be counted in both categories).
# Status Feature Count CUCM Feature Description Comment
Teams supports only one
primary phone line per user.
Cisco End Users There are some workarounds
User with more than one
1 with Multiple 520 that might overcome this
extension.
Extensions limitation, e.g. configuration in
the SBC or add a delegation to a
dummy user with the extra line.
Teams does not support analog
Analog telephone device that is
phones directly. However, in
connected to a remote gateway
2 Analog Phone 300 many cases, they can be
(e.g. connector to Fax, Intercom,
connected to Teams via an on-
Alarm etc.).
prem SBC.
The same phone extension is Teams supports only one phone
associated with more than one number per user. In the case of
3 Shared Line 98
user/phone. This scenario might Boss/Admin scenario, Teams
indicate boss/admin relationship. supports delegation.
Adaptor that interfaces with Teams does not support analog
legacy analog telephones, fax adaptors directly. However, in
4 Analog Adaptor 92 machines, analog conference many cases they can be
telephones and other analog connected to Teams via an on-
devices to IP based telephony. prem SBC.
Standalone Device
Public / common area phone with Teams CAP supports only a
5 with multiple 1
more than one extension. single extension
extensions
Customized client services with Teams has a rich API for
Subscribed
6 8,944 which users can interact via the developing 3rd party
Services
keypad and display. applications.
Automatically forward external
(i.e. from the PSTN) incoming
Forward
calls when the phone is not
7 Unregistered 3,208 Not supported by Teams.
registered with the PBX (e.g.
External
telephone is not powered on or
not connected to the network).
Forward No Answer is
Automatically forward external
Forward No supported. However, Teams
8 3,205 (i.e. from the PSTN) incoming
Answer External does not distinguish between
calls when there is no answer.
internal and external calls.
Automatically forward internal
(i.e. within the organization)
Forward
incoming calls when the phone is
9 Unregistered 3,180 Not supported by Teams.
not registered with the PBX (e.g.
Internal
telephone is not powered on or
not connected to the network).

Page 7 of 15
# Status Feature Count CUCM Feature Description Comment
Automatically forward incoming
calls (regardless of their source)
Forward when the phone is not registered
10 1,016 Not supported by Teams.
Unregistered with the PBX (e.g. telephone is
not powered on or not connected
to the network).
Forwards calls when the hunt list
is exhausted or timed out, and
Forward No the associated hunt-pilot for
11 902 Not supported by Teams.
Coverage coverage specifies "Use Personal
Preferences" for its final
forwarding.
Automatically forward all calls
12 Forward on Busy 467 (regardless of their source) when .
the line is busy.
Provides user with the ability to
be reached via a single enterprise
phone number that rings on both Teams supports simultaneous
Time Based
13 417 their desk phone and another ring. However, this cannot be
Simultaneous Ring
destination (e.g. cellular) configured based on time of day.
simultaneously, based on
configured schedule.
Automatically forward internal Forward No Answer is
Forward No (i.e. within the organization) supported. However, Teams
14 202
Answer Internal incoming calls when there is no does not distinguish between
answer. internal and external calls.
Forwards internal calls when the
hunt list is exhausted or timed
Forward No out, and the associated hunt-pilot
15 145 Not supported by Teams.
Coverage Internal for coverage specifies "Use
Personal Preferences" for its final
forwarding.
Forwards external calls when the
hunt list is exhausted or timed
Forward No out, and the associated hunt-pilot
16 124 Not supported by Teams.
Coverage External for coverage specifies "Use
Personal Preferences" for its final
forwarding.
Automatically forward only
Forward On Busy internal (i.e. within the
17 117 Not supported by Teams.
Internal organization) incoming calls
when the line is busy.
Automatically forward only
Forward On Busy external (i.e. from the PSTN)
18 110 Not supported by Teams.
External incoming calls when the line is
busy.
Provides user with the ability to
be reached via a single enterprise Teams enables users to use
Simultaneous Ring
phone number that rings on both single number reach by
19 to Multiple 49
their desk phone and more than configuring Simultaneous Ring,
Destinations
1 destination (e.g. cellular) however only to one destination
simultaneously

Page 8 of 15
# Status Feature Count CUCM Feature Description Comment
Devices with BLFs configured
Teams inherently supports
monitor the real-time status of
monitoring user status but does
20 Busy Lamp Field 15 another user at a directory
not enable incoming calls to be
number or SIP URI and enable
picked up
incoming calls to be picked up.
Enable user to forward all calls to
21 Forward All 2,942
a directory number.
Automatically forward incoming
Forward No
22 665 calls (regardless of their source)
Answer
when there is no answer.
Devices with speed dials
23 Speed Dials 428
configured.
Provides user with the ability to
be reached via a single enterprise
phone number that rings on both
24 Simultaneous Ring 259
their desk phone and another
destination (e.g. cellular)
simultaneously
The same phone extension is
associated with more than
25 Delegated Line 27
user/phone in a boss/admin
relationship
Table 5 - Feature Parity Detail

Page 9 of 15
5 Groups

5.1 Feature Parity Analysis

5.1.1 Overview
In order to identify Hunt and Pickup Group feature parity gaps, the CUCM data model is mapped and
compared to the Microsoft Teams data model.

Following the analysis of Hunt and Pickup Group configuration data in CUCM, there are 360 Hunt Groups and
421 Pickup groups that are convertible to Microsoft Teams.

Note: Orange in the graph denotes Hunt Groups or Pickup Groups configured in the system, without any
associated extensions. This suggests that the group is probably not being used and might be leftover from
past configurations.

Hunt Groups & Pickup Groups

Feature Parity Analysis to
Microsoft Teams
250
188 192
180
200
150
100 75
51 46 49
50
0
0
Hunt Groups Pickup Groups

Full Feature Parity Partial Feature Parity

Manual Review Empty Groups

Figure 2 - Hunt Groups & Pickup Groups Feature Parity Analysis to Microsoft Teams

Page 10 of 15
5.1.2 Detailed Overview
The following table details the Hunt and Pickup group feature parity gaps currently configured in the CUCM.
# Status Feature Count
Call Pickup Groups
1 with non-user 180
entries
Hunt Groups with
2 75
non-user entries
3 Call Pickup Groups 370
Hunt Groups with
4 67
Call Pickup
Call Pickup Groups
5 49
with no members
Hunt Groups with
6 46
no members
Hunt Groups with
Hunt Algorithms
7 30
that are not
Supported
Hunt Groups with
Called, Calling or
8 3
Connected Number
Transformations
9 Hunt Groups 188
Table 6 - Group Feature Parity Detail
CUCM Feature Description Comment
Members of a call pickup group
can answer a call that comes in
Teams Group Call Pickup
on a directory number other
supports only users and CAPs
than their own within the pickup
(e.g. not external PSTN or
group. These groups also
analog).
include Analog or external lines
numbers
A Hunt Group is the method of
distributing phone calls from a
Teams call queues supports only
single telephone number to a
users or CAPs as agents (i.e. not
group of several extensions.
analog or external numbers).
These groups have Analog or
external lines numbers
Members of a call pickup group
can answer a call that comes in
on a directory number other
than their own within the pickup
group.
Teams supports Call Pickup.
Calls to a Hunt Group with call
However, it does not
pickup can be answered
differentiate between calls made
remotely from another device
to a hunt group and calls made
using a predefined number.
directly to the user.
Call Pickup Groups configured, This is probably a legacy
without any associated configuration and can be
extensions. ignored.
Hunt Groups configured, This is probably a legacy
without any associated configuration and can be
extensions. ignored.
A Hunt Group algorithm is used
to determine where to route the Teams supports call queues that
call when the current extension gives similar functionality.
is unable to answer the However, Teams, does not have
incoming call. These hunt an equivalent hunt algorithm
groups use algorithms that that is used in the source PBX.
cannot be mapped.
When a call is received by this
Teams supports call queues that
hunt group either the called
gives similar functionality.
number, calling number or
However, in Teams, number
connected number will be
transformation is not supported.
transformed.
A Hunt Group is the method of
distributing phone calls from a
single telephone number to a
group of several extensions.
Page 11 of 15
6 Devices

6.1 Device Summary

Below is the breakdown of the device types following the analysis of CUCM configuration data (excluding
unused devices).

DEVICES BREAKDOWN

CTI Port 15

Telepresence 78

Analog Adapter 92

Wireless IP Phone 215

Audio Conference Phone 257

Analog Phone 306

Video Phone 342

Mobile Phone 4468

IP Phone 7976

Soft Phone 16284

0 2000 4000 6000 8000 10000 12000 14000 16000 18000

Figure 3 - Devices Breakdown Graph

Device Type Count

CTI Port 16
Telepresence 78
Analog Adapter 99
Wireless IP Phone 219
Audio Conference Phone 259
Analog Phone 389
Video Phone 349
Mobile Phone 4,488
IP Phone 8,014
Soft Phone 16,969
Total 30,033
Table 7 - Devices Breakdown Table

Page 12 of 15
6.2 Device Details
6.2.1 Detailed breakdown of CUCM device types by device model and count.
Device Type Model Count Device Type Model Count
IP Phone Cisco 6921 2,652 Video Phone Cisco 7985 2
Cisco 7811 1 Cisco 8845 63
Cisco 7821 416 Cisco 8865 2
Cisco 7841 4 Cisco 8941 73
Cisco 7861 5 Cisco 8945 60
Cisco 7906 17 Cisco 9951 9
Cisco 7911 863 Cisco 9971 32
Cisco 7931 86 Cisco Cius 1
Cisco 7940 46 Cisco DX650 5
Cisco 7941 2,647 Cisco DX80 33
Cisco 7942 554 Cisco Webex DX80 4
Cisco 7945 171 Cisco Webex Room Kit 57
Cisco 7960 219 Cisco Webex Room Kit Mini 1
Cisco 7961 130 Cisco Webex Room Kit Plus 7
Cisco 7962 92 Total 349
Cisco 7965 24
Cisco 7975 14 Device Type Model Count
Cisco 8811 2 Telepresence Cisco Telepresence Codec 2
Cisco 8841 41 C40
Cisco Telepresence Codec 3
Cisco 8861 5
C60
Cisco 8961 2
Cisco Telepresence EX90 4
Third-party SIP Device 21
Cisco Telepresence MX200 4
(Advanced)
G2
Third-party SIP Device 2
Cisco Telepresence MX300 21
(Basic)
G2
Total 8,014
Cisco Telepresence MX700 4
Cisco Telepresence MX800 5
Device Type Model Count Dual
Audio Cisco 7832 45 Cisco Telepresence Profile 52 1
Conference (C40)
Phone Cisco Telepresence Quick Set 3
Cisco 7936 34 C20
Cisco 7937 88 Cisco Telepresence SX10 6
Cisco 8831 83 Cisco Telepresence SX20 25
Cisco 8832 6 Total 78
Cisco 8832NR 3
Total 259 Device Type Model Count
Soft Phone Cisco IP Communicator 2
Device Type Model Count Cisco Jabber for Tablet 2,243
Analog Cisco ATA 186 86 Cisco Spark Remote Device 9
Adapter Cisco Unified Client Services 14,714
Cisco ATA 187 12 Framework
Cisco ATA 190 1 Cisco Unified Personal 1
Total 99 Communicator

Page 13 of 15
 Total 16,969
Device Type Model Count
CTI Port Cisco CTI Port 14 Device Type Model Count
CTI Remote Device 2 Wireless IP Cisco 7925 25
Total 16 Phone
Cisco 8821 10
Device Type Model Count Spectralink IPDECT 184
Analog Analog Phone 389 Total 219
Phone
Total 389 Device Type Model Count
Mobile Phone Cisco Dual Mode for Android 2,218
Cisco Dual Mode for iPhone 2,270
Total 4,488
Table 8 - Detailed Device Breakdown

Page 14 of 15
7 Glossary of Terms
The terms and definitions in the table below are related to their usage in the PBX Assessment report.
Term Definition
Analog Adapter An Analog Telephone Adapter device (e.g. connector to Fax, Intercom, Alarm, etc.).
Analog Phone An Analog Telephone device that is connected to a remote gateway (e.g. connector
to Fax, Intercom, Alarm, etc.).
Audio Conference Phone An Audio Conference desk phone device.
Common Area Phone A device that is not associated with a user. Also referred to as Standalone Device or
(CAP) Utility Phone
CTI Computer Telephony Integration (CTI) enables users to take advantage of
computer-processing functions while making, receiving, and managing telephone
calls. CTI applications allow you to perform such tasks as retrieving customer
information from a database using a caller ID, or to work with the information
gathered by an Interactive Voice Response (IVR) system to route a customer’s call,
along with their information, to the appropriate customer service representative.
Device Profile A device profile comprises the set of attributes (services and/or features), e.g. line
number, forwarding, that will appear on the phone when the associated user logs
in.
Devices Hardware or software telephony clients configured in the legacy PBX. Devices can
be associated to one or multiple extensions.
Feature Parity Requires This indicates an issue that needs to be manually reviewed before migration to
Manual Review Microsoft Teams. Users will not be able to migrate to Microsoft Teams unless
issues of this type are resolved.
Full Feature Parity This indicates that the user can migrate to Microsoft Teams and get the same
functionality.
Hunt Group A Hunt Group is the method of distributing phone calls from a single telephone
number to a group of several phone extensions.
IP Phone A desktop phone also referred to as a handset device.
Legacy PBX The telephony system which is being assessed and reported in this document.
Line A telephone number configured on the legacy PBX.
Orphan Cisco End-User An end-user that is not associated with any device or device profile.
Partial Feature Parity This indicates that the feature is currently not fully supported by Microsoft Teams.
Users configured with this feature can be migrated but might lose some
functionality. In some cases, 3rd party solutions can close the gap.
Pickup Group Group of users authorized to answer calls to a telephone extension within that
group of users.
Software Client An Android / iOS / PC Software client device.
Standalone Device A device that is not associated with a user. Also referred to as Common Area Phone
in Microsoft Teams.
Telepresence An Advanced Video Conferencing device.
Users End users that are configured on the legacy PBX. Users can be associated to
multiple devices and device profiles.
Video Phone A handset device with video capabilities.
Wireless IP Phone A wireless handset device.
Table 9 - Glossary of Terms

Page 15 of 15