[Index]

Model: view/HybridMultiVendorVIEW

Hybrid Cisco-Microsoft Management

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

Overview

Use the Hybrid Subscriber Management: Cisco-Microsoft menu to provision and manage subscribers with Cisco and Microsoft devices and services.

Note

In the Business Admin Portal, these tasks can be carried out by means of the selection of a Subscriber Profile for the user where the Hybrid option is the selected Subscriber Profile and a Hybrid Service is selected.

Related Topics

the Number Inventory Updates for Hybrid Support topic under Number Management

Provisioning Workflow

To access the flowcharts, view the topic via Documentation and Resources at: https://voss.portalshape.com

Prerequisites

Workflow steps

Note

For a selected user from the User Management > Users menu, 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.

  1. Log in to the Admin Portal as a provider admin, at the customer level.

  2. Go to (default menu) Hybrid Cisco-Microsoft Management > Hybrid Subscriber Management: Cisco-Microsoft

  3. Choose the relevant site.

  4. On the Hybrid Subscriber Management: Cisco-Microsoft page:

  5. When managing a user who already has Cisco or Microsoft services, these services will be displayed in the list of fields on the Existing Services - User Status & Existing Services form.

  6. Select the required hybrid Service Type from the drop-down list.

    The Entitlement Profile and Quick Add Group are hidden as these are associated with the service type.

  7. 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.

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:

When selecting the Hybrid option in a Subscriber 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 subscriber 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 subscriber has service type Cisco-MS-Hybrid and is subsequently updated to service type Cisco-Only, MS Teams devices are removed from the subscriber, 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:

Related Topics

the Cisco - Microsoft Hybrid Number Inventory topic under Number Management

Multi Vendor Quick Add Subscriber provides a single page where you can:

User Provisioning

  1. Select a User from the username dropdown. This will show a list of users that have already been synced to VOSS Automate via LDAP. This could either be via Top Down or Bottom up syncing. For provisioning to be successful the device.cucm.UserIdentity field should match the UPN of the user in O365(MsolUser). If the user already has cisco services these will be displayed in the "User Status & Existing Services" section
  2. A Directory Number can be selected. If Cisco services exists the users 1st line will be displayed.
  3. The required Service Type should be selected. For more information see the Service Type descriptions.
  4. If displayed the Entitlement Profile can be changed. If the Entitlement Profile is configured in the Service Type this field will be hidden.
  5. A Quick Add Group can be selected to configure settings on the Teams user based on data.LyncQuickAddGroups-Teams. Otherwise Values will use the Microsoft Site Defaults

Service Types

Teams Licences

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

Title Description Details
Username * VOSS Automate username as per data.User
  • Field Name: username
  • Type: String
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
First Name
  • Field Name: firstname
  • Type: String
Last Name
  • Field Name: lastname
  • Type: String
Email Address
  • Field Name: email
  • Type: String
  • 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
PIN The corresponding CUCM and CUC user PIN will be set with this PIN
  • Field Name: pin
  • Type: String
  • Is Password: True
Manager
  • Field Name: manager
  • Type: String
Department
  • Field Name: department
  • Type: String
Telephone Number
  • Field Name: telephoneNumber
  • Type: String
Title
  • Field Name: title
  • Type: String
Home Number
  • Field Name: homeNumber
  • Type: String
User's Mobile Number
  • Field Name: mobileNumber
  • Type: String
Directory URI
  • Field Name: directoryUri
  • Type: String
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
  • 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
User Status & Existing Services
  • Field Name: existing
  • Type: Object
User Type
  • Field Name: existing.UserType
  • Type: String
CUCM User LDAP Directory Name
  • Field Name: existing.cucm_user_ldapDirectoryName
  • Type: String
CUCM User Identity / AD UserPrincipalName
  • Field Name: existing.cucm_user_identity
  • Type: String
Phones
  • Field Name: existing.phones
  • Type: String
Extension Mobility Profiles
  • Field Name: existing.ext_mobilities
  • Type: String
Voicemail Extension
  • Field Name: existing.voicemail
  • Type: String
WebEx
  • Field Name: existing.webex
  • Type: String
Single Number Reach
  • Field Name: existing.snr
  • Type: String
Webex App
  • Field Name: existing.spark
  • Type: String
Contact Center
  • Field Name: existing.contact_center
  • Type: String
Teams Licenses
  • Field Name: teams_licenses.[n]
  • Type: Array
Name
  • Field Name: existing.teams_licenses.[n].Name
  • Type: String
AccountSkuId
  • Field Name: existing.teams_licenses.[n].AccountSkuId
  • Type: String
Microsoft Teams Telephony License
  • Field Name: existing.teamsTelephonyLicense
  • Type: String
Microsoft 365 UserPrincipalName
  • Field Name: existing.teams_msol_upn
  • Type: String
User status
  • Field Name: user_status
  • Type: String
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.
  • Field Name: MultiVendorServiceType
  • Type: String
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
E164 Number
  • Field Name: line1E164
  • Type: String
Microsoft Teams
  • Field Name: ms_teams
  • Type: Boolean
Usage Location Location used for Microsoft Licensing
  • Field Name: usage_location
  • Type: String
LDAP User
  • Field Name: ldap_user
  • Type: String
Data User
  • Field Name: data_user
  • Type: String
CUCM User
  • Field Name: cucm_user
  • Type: String
MSOL User
  • Field Name: msol_user
  • Type: String
CS Online User
  • Field Name: csonline_user
  • Type: String
CUCM User LDAP Directory Name
  • Field Name: cucm_user_ldapDirectoryName
  • Type: String
Use Entitlement from Service Definition
  • Field Name: forceEp
  • Type: String
Use QAG from Service Definition
  • Field Name: forceQag
  • Type: String
Use MS Teams from Service Definition
  • Field Name: forceMsTeams
  • Type: String
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
custom_string_1
  • Field Name: custom_string_1
  • Type: String
custom_string_2
  • Field Name: custom_string_2
  • Type: String
custom_string_3
  • Field Name: custom_string_3
  • Type: String
custom_string_4
  • Field Name: custom_string_4
  • Type: String
custom_string_5
  • Field Name: custom_string_5
  • Type: String
custom_string_6
  • Field Name: custom_string_6
  • Type: String
custom_string_7
  • Field Name: custom_string_7
  • Type: String
custom_string_8
  • Field Name: custom_string_8
  • Type: String
custom_string_9
  • Field Name: custom_string_9
  • Type: String
custom_string_10
  • Field Name: custom_string_10
  • Type: String
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