Introduction
Migrations to modern UC platforms such as WebEx, RingCentral, MIVB and Zoom can pose many challenges. Firstly, legacy PBXs do not have the same feature sets as UC platforms and although we may have the capabilities to provision a particular feature, the feature may not be comparable on the source PBX, it may not exist or not be available in the configuration.
This page outlines our support for provisioning from each vendor we can audit. Our LLD/Migration plan is designed to be edited where options don’t exist so even if the data is not available in the source PBX you can still successfully provision.
WebEx
For general guidance on migrating to WebEx please view our WebEx guide here Using UCentric to provision to Cisco Webex Calling
Provisioning support matrix
This matrix outlines our support for auditing each vendor we support and provisioning audit data to WebEx Calling.
A legend is included below this matrix, and the WebEx Feature list are all of the items that we can provision to WebEx.
Legend
Icon | Description | Notes |
|---|---|---|
 | This is feature is captured from the source platform and can be provisioned. | Formatting may still need to be applied, for instance a DDI will need to be in E164 number format. |
 | As above but only available on certain versions of this PBX, older variants may not contain this data. | |
 | Not applicable to existing PBX but defaults are applied and can be modified in LLD by using drop down | |
 | Not captured from PBX, this is because the information is either not available or contained in exports, API access or other audit method. | |
N/A | Not applicable to existing PBX or no comparable feature. | This will be the case on many legacy systems for features like user email addresses. |
Default | A default is applied to the LLD | This occurs when the existing PBX does not contain a particular feature. For instance although a location may be captured the PBX may only have the ability to have a default location for hunt groups. If the PBX does not have a location feature then a default location is automatically added to the LLD. |
Auto | Auto configured based on other information | This feature is auto configured when provisioning based. |
Manual | These features require manual input on LLD as they do not exist on may voice platforms or are not comparable | Licenses on legacy voice platforms do not map like for like with WebEx therefore manual input in LLD is needed. |
Managing Gaps
A lot of the systems we can audit have common gaps in what is available on the system, not applicable or not contained in the PBX backups. This section details these and how they can be managed.
Refer to our WebEx provisioning guide for more details on supported inputs for these fields Using UCentric to provision to Cisco Webex Calling
Locations: If locations from a system are not captured, then the “RegionName” or group location for each user/group should be changed and a matching entry should be added to the locations tab. By default all users and groups will be in the “Default” location.
Email: If we do not capture email addresses from a system then these should be added to the LLD for each user, alternatively they can be blended into an audit using an Active Directory extract UCentric ZT/SPA - User Manual
DDIs: If we do not capture DDIs/DIDs from this system, DDIs should be added to the LLD in E164 number format for each location and user if the user needs external calling. These should already be available for given location in WebEx prior to provisioning.
Call Forwarding: If call forwarding is not captured from this system and this is required then it should be added to the LLD. There are several call forwarding fields that can contain external numbers (E164 numbering) or extn numbers. Please contact us for an example.
Softkeys: If soft keys/key appearances/button labels for devices are not captured then they won’t be provisioned this includes user speed dials, BLF or other features set on a device.
Device MAC: If MAC addresses are not captured for devices, compatible devices will need a MAC address added to the LLD or the devices will be provisioned with an activation code sent to the user to activate at a later date.
Hunt Groups: If we do not capture hunt groups from a given system and if these are required on WebEx then they should be added to the LLD. Please contact us for an example.
Pickup Groups: If we do not capture pickup groups from a given system system and if these are required on WebEx then they should be added to the LLD. Please contact us for an example.
Auto Attendants: If we do not capture auto attendants from a given system and if these are required on WebEx then they should be added to the LLD. Please contact us for an example.
Auto Attendant Schedules: If we do not capture schedules from a given system, they should be added to the LLD if auto attendants are in use so that these can be provisioned to WebEx Calling.