Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

WebEx Feature

...

We don't have a way to export this macro.

...

MX-One

...

OmniPCX

...

FreePBX

...

BCM

...

CM

...

IP Office

...

INDeX

...

5000

...

Broadworks

...

CS2K

...

CME

...

CUCM

...

BTeX

...

ROLM, 9751

...

Teams

...

MiVB

...

SX2000

...

MiVoice Connect

...

MiVoice Office 250

...

MiVoice Office 400

...

NEAX

...

Sopho/IS3000

...

Meridian, Succession, CS1000, CS1K

...

One425

...

HiPath 4000

...

HiPath 3xxx series/HiCom 150

...

iSDX

...

OpenScape Voice OSV

...

OpenScape Business OSB

...

Locations/Location Name

...

(tick)

...

(warning)

...

(error)

/macMigrations 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

image-20241219-163101.pngImage Added

Legend

Icon

Description

Notes

image-20241219-164052.pngImage Added

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.

image-20241219-164153.pngImage Added

As above but only available on certain versions of this PBX, older variants may not contain this data.

image-20241219-164109.pngImage Added

Not applicable to existing PBX but defaults are applied and can be modified in LLD by using drop down

image-20241219-164125.pngImage Added

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.