Use the Hybrid Cisco-Microsoft Conversion page to provision and manage subscribers with Cisco and Microsoft devices and services.

Provisioning workflow

To access the flowcharts, view the topic via the release documentation at: https://documentation.voss-solutions.com/automate.html

Prerequisites

Enable the following Global Setting Enable Cisco / Microsoft Hybrid. See: Enabled Services at Global Settings.
To add new hybrid users, sync in the MS Teams users at the customer level. For the management of Microsoft users, see: Microsoft Quick Start.

Workflow steps

Note

For a user selected on the Users page, these hybrid user management tasks can also be carried out on the Hybrid Status tab of the user by selecting the Update Hybrid Status link.

Log in to the Admin Portal as a provider admin.
Go to Hybrid Cisco-Microsoft Conversion
Choose the relevant site.
Configure settings:
- In the Username field, select the user. MS Teams users should be synced in.
  
  The user's CUCM User Identity / AD UserPrincipalName should match MS Teams UserPrincipalName
- To include users higher in the hierarchy in the Username drop-down, select Include users at higher hierarchy.
When managing a user with existing Cisco or Microsoft services, these services display in the list of fields on the Existing Services - User Status & Existing Services form.
Select the required Hybrid Service type from the drop-down.

The Entitlement Profile and Quick Add Group are hidden as these are associated with the service type.
The Directory Number drop-down list is available to select a number after selecting a service type.

Note

If the "Cisco-MS-Hybrid" service type is selected, the choice of Directory Number (Internal or E164) will determine the provisioning.

For details on all the service types, see: Multi-Vendor Service Definitions.

Automatic Move of Microsoft Elements on Hybrid User Delete

When deleting a hybrid (Cisco/Microsoft) multi-vendor user from a site and that user has Microsoft (Teams/365) accounts, the system automatically moves the user's Microsoft-related models from the site to the customer level.

The following models are moved:

data/User
device/msteamsonline/CsOnlineUser
device/msgraph/MsolUser
device/msexchangeonline/UserMailbox

This behavior is implemented by a post-delete workflow, HybridMVS_RelationMoveAfterUserDeleteCleanupPWF, which runs only for hybrid MVS users and applies only to Microsoft elements. The models are moved, not purged. Because the Microsoft artifacts are moved to the customer, you can re-add the user at another site without manually relocating leftover Microsoft models.

If the user still exists in the Microsoft cloud portal, they will sync back into the system at the customer level on the next Microsoft sync.

Hybrid service definitions

Note

Consult with VOSS to customize the configuration of Hybrid Service Definitions as well as dialplan additions.

A hybrid service refers to a particular multi-vendor configuration in VOSS Automate and is characterized by a collection of settings, templates, and workflows that apply to the management of a user to whom it is assigned.

This collection then determines a particular set of vendor services, entitlement profiles, dial plan additions for the user as well as workflows to run during user management.

Note

Hybrid services require:

Configuration of the relevant multi-vendor devices on VOSS
Vendor device user sync into VOSS

When selecting the Hybrid option in a User Profile, a Hybrid Service can be selected and associated with the profile. This service in the profile is associated with a service definition.

Hybrid user management allows for devices and services to be added to or removed from a user in accordance with the current and newly selected hybrid service for a user. The workflows in the current hybrid service run to remove elements prior to the execution of workflows in the new hybrid service to add elements.

For example:

If a user has service type MS-Only-Hybrid and is subsequently updated to have no Microsoft service type, the user is updated to service type No-Hybrid-Service and associated entitlement profile.
If a user has service type Cisco-MS-Hybrid and is subsequently updated to service type Cisco-Only, MS Teams devices are removed from the user, preferred voicemail is updated to be "Cisco" instead of "MS-Teams" and all multi-vendor entitlement profiles are updated accordingly.

The following hybrid services are defined, with default attributes indicated:

Cisco-MS-Hybrid

User has both Cisco Devices and a Teams Device with an associated E164 number. Cisco Unified CM dial plan configuration allows incoming and outgoing calls.
- Quick Add Group: "System Quick Add Group Hybrid Enable User" - contains MS Teams User Template to enable MS Teams
- Class of Service and Entitlement Profile: by default empty. Select a Class of Service to apply to MS Teams users and their calling rights.
The service type offers automatic configuration of services according to the selected Directory Number in the Admin GUI: disabling Use next available line and then the selected Line.

This is carried out by a workflow selecting the appropriate dialplan template addition.

Important

Automate provides standard template additions to the standard Cisco HCS dialplan. Contact VOSS if you wish to use alternative dial plan additions.
- Both Cisco Devices and a MS Teams Device have an associated E164 number.
  
  The E164 Number is shared across all devices, for example:
  - INI entry = 3334567, mapped to E164 = +15553334567.
  - The number +15553334567 is set up in Microsoft as the line.
  Calls from colleagues with Cisco phones to the user's Cisco phone will simultaneously dial this phone and the MS Teams client. A SNR profile is used on the Cisco User to fork calls to the Teams Client.
- Internal number selected
  
  User has both Cisco Devices and a MS Teams Device with no associated E164 number. An E164 number is generated by adding a prefix (+88800) to the internal number for setup in Microsoft, for example:
  - INI = 3334567
  - The number +1888003334567 is generated for use in MS Teams for that user.
  The MS Teams user can dial:
  - internal MS Teams users
  - internal Cisco users
  - external PSTN number (off-net via CUCM)
Cisco-No-Services

All Cisco and Teams devices, multi-vendor services will be removed from the user.
- Quick Add Group: "System Quick Add Group Hybrid Disable User" - contains MS Teams User Template to disable MS Teams
- Class of Service and Entitlement Profile: by default empty Select a Class of Service to apply to MS Teams users and their calling rights.
Cisco-Only_MV_SD

User has only Cisco devices with an associated E164 Number. Multi-vendor, MS Teams services removed if present.
- Quick Add Group: "System Quick Add Group Hybrid Disable User" - contains MS Teams User Template to disable MS Teams
- Class of Service and Entitlement Profile: by default empty
MS-Only-Entvoice_MV_SD

User has only a MS Teams Device and selected Directory Number. MS Teams Dialplan.
- Quick Add Group: "System Quick Add Group Hybrid Enable User" - contains MS Teams User Template to enable MS Teams
- Class of Service and Entitlement Profile: by default empty Select a Class of Service to apply to MS Teams users and their calling rights.
MS-Only-Hybrid_MV_SD

User has only a MS Teams Device and selected Directory Number. Cisco Unified CM dial plan configuration allows incoming and outgoing calls. Cisco user services are removed if present.
- Quick Add Group: "System Quick Add Group Hybrid Enable User" - contains MS Teams User Template to enable MS Teams
- Class of Service and Entitlement Profile: by default empty Select a Class of Service to apply to MS Teams users and their calling rights.
MS-Only-No-Entvoice_MV_SD

User has only a MS Teams Device and no Directory Number. No MS Teams Dialplan.
- Quick Add Group: "System Quick Add Group Hybrid Disable User" - contains MS Teams User Template to disable MS Teams
- Class of Service and Entitlement Profile: by default empty Select a Class of Service to apply to MS Teams users and their calling rights.
No-Hybrid-Service_MV_SD

User has no Cisco or MS Teams Devices.
- Quick Add Group: "VOSS-QAG_ExecUser - 88XX SIP"
- Class of Service and Entitlement Profile: by default empty

Note

When managing the hybrid services of administrator users by means of bulk loader sheets:

Values for the mvs_hybrid_status field needs to be one of the service names as listed above.
To unset this value in a bulk load sheet, leave the cell value for the mvs_hybrid_status field empty.

Related topics

Cisco-Microsoft Hybrid Users
User profiles

Cisco - Microsoft Hybrid Number Inventory topic under Number Management

The MVS_QaS Workflow will check that the O365 user has an assigned license that has Entprise Voice capabalities. If a valid license is not found the workflow will fail. Alternatively it's possible for VOSS Automate to assign a valid license to the User. After assigning the license it may take some time for the change to appear on the Tenant, this is due to propogation delay in the Microsoft Cloud. The user will be marked as "Microsoft Update Pending", VOSS Automate will periodically check for this user in the Teams Tenant, once the User has appeared VOSS Automate will complete the configuration steps

Model Details: view/HybridMultiVendorVIEW

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title				Description	Details
Username *				VOSS Automate username as per data.User	Field Name: username Type: String MaxLength: 1024
Include users at higher hierarchy				Includes users above site level when searching	Field Name: lookUpForUser Type: Boolean
Fail Transaction if user not found				used with API to prevent creation of local users where LDAP is in use	Field Name: failIfNotFound Type: Boolean
Entitlement Profile				If Entitlement Profiles are used on the platform they can be selected or changed here. If the Entitlement profile is configured within a Service Type this field will be hidden.The field will initially display the default Entitlement Profile	Field Name: entitlement_profile Type: String MaxLength: 1024
First Name					Field Name: firstname Type: String MaxLength: 1024
Last Name					Field Name: lastname Type: String MaxLength: 1024
Email Address					Field Name: email Type: String MaxLength: 1024 Pattern: ^([^.@]+)(\.[^.@]+)@([^.@]+\.)+([^.@]+)$ Format:* email
Password				The corresponding CUCM, CUC and WebEx user password will be set with this password	Field Name: password Type: String Is Password: True MaxLength: 1024
PIN				The corresponding CUCM and CUC user PIN will be set with this PIN	Field Name: pin Type: String Is Password: True MaxLength: 1024
Manager					Field Name: manager Type: String MaxLength: 1024
Department					Field Name: department Type: String MaxLength: 1024
Telephone Number					Field Name: telephoneNumber Type: String MaxLength: 1024
Title					Field Name: title Type: String MaxLength: 1024
Home Number					Field Name: homeNumber Type: String MaxLength: 1024
User's Mobile Number					Field Name: mobileNumber Type: String MaxLength: 1024
Directory URI					Field Name: directoryUri Type: String MaxLength: 1024
Quick Add Group *				Can be used to configure settings on the Teams user based on data.LyncQuickAddGroups-Teams. Otherwise Values will use the Microsoft Site Defaults	Field Name: qagroup_name Type: String Target: data/QuickAddGroups Target attr: group_name MaxLength: 1024 Format: uri
Class of Service				Select the Class of Service to apply to the Teams Client. This controls what call types are dialable within the country dialplan (International, Premium, Service,....). The Class of Service behaviour maps directly equivalent CoS in CUCM.	Field Name: class_of_service Type: String MaxLength: 1024
User Status & Existing Services					Field Name: existing Type: Object
	User Type				Field Name: existing.UserType Type: String MaxLength: 1024
	CUCM User LDAP Directory Name				Field Name: existing.cucm_user_ldapDirectoryName Type: String MaxLength: 1024
	CUCM User Identity / AD UserPrincipalName				Field Name: existing.cucm_user_identity Type: String MaxLength: 1024
	Phones				Field Name: existing.phones Type: String MaxLength: 1024
	Extension Mobility Profiles				Field Name: existing.ext_mobilities Type: String MaxLength: 1024
	Voicemail Extension				Field Name: existing.voicemail Type: String MaxLength: 1024
	WebEx				Field Name: existing.webex Type: String MaxLength: 1024
	Single Number Reach				Field Name: existing.snr Type: String MaxLength: 1024
	Webex App				Field Name: existing.spark Type: String MaxLength: 1024
	Contact Center				Field Name: existing.contact_center Type: String MaxLength: 1024
		Teams Licenses			Field Name: teams_licenses.[n] Type: Array
			Name		Field Name: existing.teams_licenses.[n].Name Type: String MaxLength: 1024
			AccountSkuId		Field Name: existing.teams_licenses.[n].AccountSkuId Type: String MaxLength: 1024
	Microsoft Teams Telephony License				Field Name: existing.teamsTelephonyLicense Type: String MaxLength: 1024
	Microsoft 365 UserPrincipalName				Field Name: existing.teams_msol_upn Type: String MaxLength: 1024
User status					Field Name: user_status Type: String MaxLength: 1024
Service Type *				Select the required Service Type for the user. The Service Type defines the collection of settings that will be applied to Teams and CUCM to achieve different behaviours. Appropriate Service Types will be shown based on whether the selected line has an associated E164 number and will only retain a Hybrid status if the Service Type is Hybrid.	Field Name: MultiVendorServiceType Type: String MaxLength: 1024
Directory Number				Select line and associated E164 to configure in Teams.Value will default to users first line in CUCM. If line does not have an associated E164, a dummy E164 number will be generated.	Field Name: line1DN Type: String MaxLength: 1024
E164 Number					Field Name: line1E164 Type: String MaxLength: 1024
Microsoft Teams					Field Name: ms_teams Type: Boolean
Usage Location				Location used for Microsoft Licensing	Field Name: usage_location Type: String MaxLength: 1024
LDAP User					Field Name: ldap_user Type: String MaxLength: 1024
Data User					Field Name: data_user Type: String MaxLength: 1024
CUCM User					Field Name: cucm_user Type: String MaxLength: 1024
MSOL User					Field Name: msol_user Type: String MaxLength: 1024
CS Online User					Field Name: csonline_user Type: String MaxLength: 1024
CUCM User LDAP Directory Name					Field Name: cucm_user_ldapDirectoryName Type: String MaxLength: 1024
Use Entitlement from Service Definition					Field Name: forceEp Type: String MaxLength: 1024
Use QAG from Service Definition					Field Name: forceQag Type: String MaxLength: 1024
Use MS Teams from Service Definition					Field Name: forceMsTeams Type: String MaxLength: 1024
Display Line 1 CoS					Field Name: displayLine1CoS Type: Boolean
Is CUCM User Present				Default: false	Field Name: isCucmUserPresent Type: Boolean Default: false
Is Service Type No E164 No INI				Default: false	Field Name: isServiceTypeNoE164NoINI Type: Boolean Default: false
Customer Hierarchy					Field Name: customerHierarchy Type: String MaxLength: 1024
custom_string_1					Field Name: custom_string_1 Type: String MaxLength: 1024
custom_string_2					Field Name: custom_string_2 Type: String MaxLength: 1024
custom_string_3					Field Name: custom_string_3 Type: String MaxLength: 1024
custom_string_4					Field Name: custom_string_4 Type: String MaxLength: 1024
custom_string_5					Field Name: custom_string_5 Type: String MaxLength: 1024
custom_string_6					Field Name: custom_string_6 Type: String MaxLength: 1024
custom_string_7					Field Name: custom_string_7 Type: String MaxLength: 1024
custom_string_8					Field Name: custom_string_8 Type: String MaxLength: 1024
custom_string_9					Field Name: custom_string_9 Type: String MaxLength: 1024
custom_string_10					Field Name: custom_string_10 Type: String MaxLength: 1024
custom_boolean_1					Field Name: custom_boolean_1 Type: Boolean
custom_boolean_2					Field Name: custom_boolean_2 Type: Boolean
custom_boolean_3					Field Name: custom_boolean_3 Type: Boolean
custom_boolean_4					Field Name: custom_boolean_4 Type: Boolean
custom_boolean_5					Field Name: custom_boolean_5 Type: Boolean
custom_boolean_6					Field Name: custom_boolean_6 Type: Boolean
custom_boolean_7					Field Name: custom_boolean_7 Type: Boolean
custom_boolean_8					Field Name: custom_boolean_8 Type: Boolean
custom_boolean_9					Field Name: custom_boolean_9 Type: Boolean
custom_boolean_10					Field Name: custom_boolean_10 Type: Boolean

Model: view/HybridMultiVendorVIEW

Hybrid Cisco-Microsoft Conversion

Provisioning workflow

Model Details: view/HybridMultiVendorVIEW