.. welcome-to-voss-4-uc: Welcome to VOSS ------------------------- Overview ............ VOSS allows you to easily onboard customers and end users with collaboration services. The fulfillment procedures to achieve this objective may involve administrators at the provider, reseller, customer, and site levels of the hierarchy. This guide provides information about provisioning in VOSS, including provisioning steps and interactions between VOSS and the UC applications of vendors that VOSS supports. This guide also describes user and subscriber management, including LDAP-related move and push operations. This documentation includes several flowcharts to provide an overview of specific features and workflows for VOSS. See the index (f) for a list of these flowcharts. .. rubric:: Related topics * :ref:`default-and-custom-menus` * .. raw:: latex Dashboard and Menu Reference in the Core Feature Guide .. raw:: html Dashboard and Menu Reference .. multi-vendor-support: Multi vendor support ....................... VOSS supports provisioning and management of all unified communications (UC) applications, across multiple UC vendors (including Cisco, Microsoft, and Avaya), as single or multi vendor deployments: =========== =================================================================== Vendor Solution Microsoft See *Introduction to Microsoft UC Integration* in the Core Feature Guide. Provides a single, integrated, synchronized interface for managing the existing Microsoft Teams collaboration service, through the web portal, bulk-loading, or the REST API. * Connects to adjacent service management platforms * Configurable deployment templates support automated business processes * Workflows for migrating users * End-to-end management of Microsoft Teams, UC and collaboration solutions * License management * Extends Microsoft Teams * Supports complementary systems and applications to work alongside Microsoft Teams, such as Cisco Call Recording or Contact Center. Cisco Provides for customized UC app management via the following capabilities: * Webex App management * Onboarding workflows * Cisco contact center support * Flow-through provisioning * Multiple MACD use cases and workflows * ServiceNow integration * Northbound notification * Generic drivers * Supports complementary systems and applications to work alongside Cisco UC apps Avaya Manage Avaya enterprise voice, extended into Microsoft Teams. =========== =================================================================== .. rubric:: Related topics * .. raw:: latex Manage users in the Core Feature Guide .. raw:: html Manage users * .. raw:: latex Microsoft overview in the Core Feature Guide .. raw:: html Microsoft overview .. _gui-accessibility: Accessibility ............... .. _21.4|VOSS-896: .. _21.4-PB4|VOSS-1131: VOSS supports Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. A full Voluntary Product Accessibility Template (VPAT) report is available from your account team. To support accessibility, when using keyboard navigation, a black bar is enabled above the toolbar. When the cursor is in the URL box and the Tab key is pressed, this bar is displayed and has three menu items corresponding to three areas of the main user interface: ====================== ==================================================================================== Home screen From any form on the interface, return to the main user interface. This is equivalent to the Home button on the main toolbar, and can, for example be accessed by means of a screen reader shortcut. Skip to content On the main user interface, move the focus to the dashboard menu items. Press to move the focus to the first dashboard link. Skip to navigation On the main user interface, move the focus to the menu bar. The first menu item receives focus. ====================== ==================================================================================== The table provides examples of features in VOSS that are assessed for accessibility to support users with disabilities, including those who require assistive technologies, such as users who are unable to use a mouse, or those who are visually impaired: .. tabularcolumns:: |p{5cm}|p{10cm}| +----------------------------------------------------------+---------------------------------------------------------------------+ | Setting | Description | +==========================================================+=====================================================================+ | Title display in the browser | When choosing a menu option in the Admin Portal, the title | | | displays in the browser to give screen reader users an overview of | | | the page and to help them to move between open pages in their | | | browser. | +----------------------------------------------------------+---------------------------------------------------------------------+ | Buttons and images have alternative text | Buttons and images have accessible names and can be read by screen | | | readers. For example, paginator buttons that allow a | | | user to navigate to the first, next, previous, and last page on a | | | form. | | | | | | The alternative text displays when the mouse | | | pointer hovers over an image. Visually impaired users who are using | | | screen readers can hear the alternative text read out. Users | | | who have turned off images to speed up downloads or to save | | | bandwidth can view the alternative text. | +----------------------------------------------------------+---------------------------------------------------------------------+ | Heading elements appear in a sequentially-descending | Headings are properly ordered and do not skip levels. This conveys | | order | the semantic structure of the page, making it easier to navigate | | | and understand when using assistive technologies. For example, the | | | Login page contains a level-one heading, | | | and landmarks for the logo, input fields, and labels. | +----------------------------------------------------------+---------------------------------------------------------------------+ | Elements meet minimum color contrast ratio | Low-contrast text is difficult or impossible for many users to | | thresholds and can be changed | read. While some people need high contrast, for others, bright | | | colors (high luminance) are not readable. A Chrome plugin can be | | | installed (on the Chrome | | | browser), which allows the user to change the default colors | | | on a page. | +----------------------------------------------------------+---------------------------------------------------------------------+ | Zoom capability | VOSS supports zooming without losing any information or | | | functionality. | +----------------------------------------------------------+---------------------------------------------------------------------+ | Keyboard access and alternative visual focus | Many people cannot use a mouse and rely on the keyboard to | | | interact with the Web. People who are blind and some | | | sighted people with mobility impairments rely on the keyboard | | | or on assistive technologies and strategies that rely on | | | keyboard commands, such as voice input. | | | | | | In a browser that supports keyboard navigation with the Tab | | | key (for example, Firefox, IE, Chrome, and Safari): | | | | | | 1. Click in the address bar, then put your mouse aside and do | | | not use it. | | | #. Press the 'Tab' key to move through the elements on the page. | | | #. To move within elements such as select boxes or menu bars, | | | press the arrow keys. | | | #. To select a specific item within an element such as a drop-down | | | list, press the Enter key or Spacebar. | +----------------------------------------------------------+---------------------------------------------------------------------+ | ARIA roles have allowable attributes | * Children of ARIA roles, such as form arrays, panel title bars, | | | and tabs, are announced | | | * Landmarks and IDs are unique | | | * Table headers have text labels that are visible to screen readers | | | * Interactive controls are not nested | | | * Toggle fields have accessible names, for example, *Element: | | | List checkbox* | +----------------------------------------------------------+---------------------------------------------------------------------+ .. tabularcolumns:: |p{5cm}|p{10cm}| +----------------------------------------------------------+---------------------------------------------------------------------+ | Setting | Description | +==========================================================+=====================================================================+ | Dynamic forms | * All buttons, including those used for pagination on dynamic | | | forms, have | | | discernible text labels that can be read by a screen reader | | | * Links with the same name have a similar purpose to facilitate | | | keyboard navigation and the use of screen readers | +----------------------------------------------------------+---------------------------------------------------------------------+ | Breadcrumb navigation elements | Breadcrumbs have machine-readable labels to allow those using | | | assistive technologies to understand the site structure, to | | | facilitate navigation, and to provide context for their current | | | location. | +----------------------------------------------------------+---------------------------------------------------------------------+ | Pop-up dialogs | Form elements have accessible labels that properly identify the | | | element, for example, a screen reader is able to announce a | | | *Close* button as well as the header and content text on | | | *Confirmation* dialogs and other messages, and on *Search* and | | | *Hierarchy* pop-ups. | | | | | | Relationships between parent/child elements can be determined, for | | | example, in the hierarchy tree. | +----------------------------------------------------------+---------------------------------------------------------------------+ Compatibility ................ Prior to install or upgrade, it is recommended that you review the latest `VOSS Compatibility Matrix `_ for details on supported browsers and applications for your version. .. _unicode-limitations: Unicode limitations ..................... VOSS supports unicode characters only in the following fields: * User Information * Description * Contact Information (Address, City, State, Postal Code, Country, Extended Name, External Customer ID, Account ID, and Deal IDs) * Phone Label .. _conventions: Conventions used in this guide ............................... Formatting conventions '''''''''''''''''''''''' The table describes formatting conventions in the VOSS Product Suite documentation: +---------------------------+------------------------------------------------------+ | **Component** | **Formatting** | +===========================+======================================================+ | UI buttons and labels | Uses the same capitalization as displayed in the | | | user interface, formatted **bold**. | +---------------------------+------------------------------------------------------+ | Dashboard, menu, and | Formatted **bold** | | page names | | +---------------------------+------------------------------------------------------+ | Asterisk '*' after field | Indicates that the field is mandatory. | | name, e.g. Userid * | | +---------------------------+------------------------------------------------------+ Badges '''''''' VOSS Product Suite help topics typically display one or more badges (below the topic title) to indicate that the Help content is relevant only to a specific product, deployment type (Enterprise or Provider), admin level (for example, Customer admin, HCS admin, or Provider admin), or vendor (for example, Microsoft or Cisco, hybrid or multi-vendor). .. note:: Badges are typically used only for exceptions, that is, where functionality is available only for a specific product, deployment type, vendor type or vendor configuration, or where you must log in with a specific admin role. .. rubric:: Core label * :bdg-info:`Core` .. rubric:: Product / Feature badges Badges indicate whether a topic is relevant to the product or a feature. **Product** * :bdg:`UC Automation` * :bdg:`UC Monitoring` * :bdg:`Netflow Management` * :bdg:`UC Analytics` * :bdg:`Contact Center Management` .. **Feature** .. .. * :bdg:`Email Management` .. * :bdg:`License Management` .. * :bdg:`Meeting Room Management` .. * :bdg:`Phone Number Management` .. * :bdg:`Security Management` .. * :bdg:`AI Agent Management` .. rubric:: Deployment badges * :bdg-secondary:`provider-only` Indicates that this functionality is only available in Provider deployments. * :bdg-secondary:`enterprise-only` Indicates that this functionality is only available in Enterprise deployments. .. rubric:: Enabled Service badges Indicates that this functionality is only available in if the related service is enabled in **Global Settings**. * :bdg-primary:`Cisco CUCM` * :bdg-primary:`Cisco CUCX` * :bdg-primary:`Cisco WebEx` * :bdg-primary:`Cisco Webex App(Teams)` * :bdg-primary:`Cisco UCCX` * :bdg-primary:`Cisco Broadworks` * :bdg-primary:`Cisco UCCE` * :bdg-primary:`Cisco Webex Contact Center` * :bdg-primary:`Microsoft` * :bdg-primary:`Defender for Office` * :bdg-primary:`Defender for Endpoint` * :bdg-primary:`Defender for Identity` * :bdg-primary:`Cisco / Microsoft Hybrid` * :bdg-primary:`Avaya / Microsoft Hybrid` * :bdg-primary:`Avaya` * :bdg-primary:`Pexip` * :bdg-primary:`Zoom` * :bdg-primary:`VOSS Phones` * :bdg-primary:`Session Border Controller` * :bdg-primary:`Voice Automation` * :bdg-primary:`Defender for Cloud Apps` * :bdg-primary:`Operator Connect` .. rubric:: Vendor support badges * :bdg-primary:`Microsoft` Indicates that this functionality is relevant for Microsoft. * :bdg-primary:`Cisco` Indicates that this functionality is relevant for Cisco. * :bdg-primary:`Webex` Indicates that this functionality is relevant for Webex. .. rubric:: Vendor configuration badges * :bdg-dark-line:`hybrid` Indicates that this functionality is relevant to hybrid vendor configuration. * :bdg-dark-line:`multi-vendor` Indicates that this functionality is relevant to a multi vendor configuration. .. note:: If no vendor configuration badge is used, assume single vendor, for example, Microsoft-only environment. .. rubric:: Admin role badges Admin login roles are listed in order of highest access level to lowest access level. Provider and Enterprise admin are at the same level. You can find more information about VOSS roles and access levels in :ref:`role-based-access` * :bdg-info-line:`sys-admin` Log in as sysadmin. * :bdg-info-line:`hcs-admin` Log in as HCS admin. * :bdg-info-line:`reseller-admin` Log in as Reseller admin. * :bdg-info-line:`provider-admin` Log in as Provider admin. * :bdg-info-line:`enterprise-admin` Log in as Enterprise admin. * :bdg-info-line:`customer-admin` Log in as Customer admin. * :bdg-info-line:`site-admin` Log in as Site admin * :bdg-info-line:`self-service-admin` Log in as Self-service admin Context-sensitive Help files '''''''''''''''''''''''''''''''' The VOSS Product Suite Admin Portal ships with context-sensitive help files, which are associated with the relevant menu via the model type (visible in the URL). The example shows the **Configuration Templates** page, the model type in the URL (*data/ConfigurationTemplate*), and the Help file topic title, *Configuration Templates*. .. image:: /src/images/csh-and-model-types-1.png In addition to the help topic content, which may describe the feature, provide a task description, and additional details for the user interface, a default, auto-generated description is provided for the model. These model details may be further refined (filtered) via field display policies applied to the menu. .. image:: /src/images/csh-and-model-types-2.png Where models are associated with two or more menus in the user interface, the help file may be a general topic for the model type, or the context of the help file that displays may relate only generally to the menu you're working with. In this case, it is recommended that you view the latest documentation for the menu or feature via the Documentation website via a link at the top of the context-sensitive help or via the *Documentation and Resources* tab at: https://voss.portalshape.com For example, the ``data/File`` model is associated with the following menus: * Audit Report Files * File Management * Manage Greeting Files * MS-Teams MP3 Files * MS-Teams WAV Files