[Index]

Model: view/TeamsQuickSubscriber

System Message: WARNING/2 (<string>, line 2)

Title underline too short.

Microsoft Teams Quick Add Subscriber
==============================

The Microsoft Quick Add Subscriber feature provides provides a simple interface for allocating supported Microsoft UC services to users that have been added to Microsoft Active Directory and synchronized into VOSS-4-UC from Microsoft Lync / Skype for Business.

The interface is for service additions and the detailed configuration is hidden from administrators delegated to perform these operations. The detailed configuration is typically managed by a customer administrator or above using the Configuration Templates specified in Microsoft Quick Add Groups.

The VOSS-4-UC user interface will disable the option of adding Microsoft Lync / Skype for Business if the user already has Microsoft Lync / Skype for Business.

Multi-vendor Quick Add Subscriber

The Multivendor Quick Add Subscriber feature enables administrators to add both Cisco and Microsoft UC services to subscribers.

NOTE: Cisco and Microsoft Workflows are combined without modifying the underlying Quick Add Subscriber feature of the solution that is extended by installing the applicable VOSS-4-UC add-on.

Microsoft Quick Add Subscriber Workflow

The workflow supports adding the following Microsoft UC services:

If the required AD User is not in the dropdown list:

If the Skype for Business check box is selected:

If the Voicemail check box is selected:

If the Office 365 check box is checked:

Below see the workflow for provisioning online services.

NOTE: If the workflow is rolled back for whatever reason and the creation of a Mailbox is reversed by disabling the mailbox then it has the effect of the AD user's email address being blanked out, which is comes from disabling the mailbox.

Microsoft Quick Add Subscriber Online

The following conditions apply when adding services to a Subscriber enabled for MS Online Services:

If the Subscriber has Voicemail or Skype for business the following options will be disabled : * Voicemail * SFB Enabled

If the Subscriber does not have Voicemail and/or Skype for Business you can choose to enable the subscriber by just checking the voicemail and/or SfB Enable check boxes. This will enable the Subscriber with on-prem services.

If the voicemail checkbox is checked and the Online Mailbox/Voicemail checkbox is checked, the Subscriber will be provisioned for online mailbox and Ummailbox services.

If the SfB Enabled checkbox and the Online Skype for Business checkbox is checked the Skype for Business service will be provisioned online.

NOTE: The Microsoft Quick Add Group selected needs to contain the MS Online Licenses required for the options selected.

Microsoft Hybrid 2-stage provisioning

In the case where Active Directory is synchronized with MS online (i.e. a Hybrid deployment) the provisioning of online service can only be completed once ADFS Dir Sync has been completed. When a Quick Add Subscriber operation is performed before a new AD user has been synchronized with MS Online, VOSS will persist the MS Online Provisioning request. Outstanding online provisioning requests can be seen in the "Services Allocated" tab of Subscribers.

A scheduled task is provided as part of sample templates that periodically synchronizes VOSS with MS Online Users. The scheduled task processes any outstanding MS Online Provisioning requests and deletes them once completed.

Microsoft Quick Add Subscriber Online Provisioning Workflow

The workflow supports adding the following Microsoft Online Services in a hybrid deployment:

If the Online Skype for Business check box is selected:

Processing Online Provisioning Requests:

Model Details

Title Description Details
Username *
  • Field Name: username
  • 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
Usage Location * MS Licensing Usage Location
  • Field Name: usage_location
  • Type: String
  • Target: data/LyncDefaults
Directory URI
  • Field Name: directoryUri
  • Type: String
Quick Add Group * Default: default
  • Field Name: qagroup_name
  • Type: String
  • Target: data/LyncQuickAddGroups-Teams
  • Target attr: group_name
  • Default: default
  • Format: uri
Existing Services
  • Field Name: existing
  • Type: Object
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
SfB Id
  • Field Name: existing.lync_id
  • Type: String
Exchange UM ID
  • Field Name: existing.ExchangeUM_id
  • Type: Integer
SIP Address
  • Field Name: existing.sip_address
  • Type: String
Single Number Reach
  • Field Name: existing.snr
  • Type: String
User status
  • Field Name: user_status
  • Type: String
Lines
  • Field Name: lines.[n]
  • Type: Array
Directory Number
  • Field Name: lines.[n].directory_number
  • Type: String
Voice
  • Field Name: voice
  • Type: Boolean
Phones
  • Field Name: phones.[n]
  • Type: Array
Phone Name Name of phone to provision for e.g. SEPABCDEFABCDEF
  • Field Name: phones.[n].phone_name
  • Type: String
  • Target: device/cucm/Phone
  • Target attr: name
  • Format: uri
Extension Mobility
  • Field Name: mobility
  • Type: Boolean
Voicemail
  • Field Name: voicemail
  • Type: Boolean
Online Mailbox/Voicemail
  • Field Name: online_voicemail
  • Type: Boolean
WebEx
  • Field Name: webex
  • Type: Boolean
SfB Enabled
  • Field Name: lync
  • Type: Boolean
Online Skype for Business
  • Field Name: online_sfb
  • Type: Boolean
lync_details
  • Field Name: lync_details
  • Type: Object
SIP Address
  • Field Name: lync_details.sip_address
  • Type: String
Phone Number
  • Field Name: lync_details.phone_number
  • Type: String
Extension
  • Field Name: lync_details.ext
  • Type: String
Id
  • Field Name: lync_details.id
  • Type: String
Office365 Enabled
  • Field Name: office365
  • Type: Boolean
Microsoft Teams
  • Field Name: ms_teams
  • Type: Boolean
Single Number Reach
  • Field Name: snr
  • Type: Boolean
SNR Mobile Number
  • Field Name: mobile_number
  • Type: String
Jabber Device When adding a Jabber device also specify a line to be associated. The first line specified will be used for any Jabber device added here.
  • Field Name: jabber
  • Type: Boolean
Jabber Agent
  • Field Name: jabber_agent
  • Type: String
  • Choices: ["Android", "CSF", "iPad", "iPhone"]
Jabber Devices
  • Field Name: jabber_devices.[n]
  • Type: Array
Jabber Agent
  • Field Name: jabber_devices.[n].jabber_agent
  • Type: String
  • Choices: ["Android", "CSF", "iPad", "iPhone"]
Device Name
  • Field Name: jabber_devices.[n].device_name
  • Type: String
Mobile Identity
  • Field Name: jabber_devices.[n].mobile_identity
  • Type: Boolean
Destination
  • Field Name: jabber_devices.[n].mobile_identity_destination
  • Type: String
Enable Self Provisioning
  • Field Name: self_service_id
  • Type: Boolean
Self Provisioning User Profile
  • Field Name: self_provisioning_profile
  • Type: String
  • Target: device/cucm/UserProfileProvision
  • Target attr: name
  • Format: uri
LDAP User
  • Field Name: ldap_user
  • Type: String
Normalized User
  • Field Name: normalized_user
  • Type: String
CUCM User
  • Field Name: cucm_user
  • Type: String
CUCM User LDAP Directory Name
  • Field Name: cucm_user_ldapDirectoryName
  • Type: String
Phone Template
  • Field Name: phone_template
  • Type: String
Phone Type
  • Field Name: phone_type
  • Type: String
Phone Protocol
  • Field Name: phone_protocol
  • Type: String
API reference for view/TeamsQuickSubscriber