Voice Client Screen Flow

Voice Client Screen Flow

Using this configuration, when a user signs in they are presented with the three roles. Each role is uniquely identified and organized by the value of U100, U200, and U300. The dep_role and dep_role_desc appear in the display.
Select Role
Select Role
Figure 6 and Figure 7 show the available extension groups for the Associate and Dept Mgr roles.
Associate Extension Groups
Associate Extension Groups
Note that in the extensions table (Figure 4), all Associates have ‘dep_auto’ set to yes. When an associate selects one of the Associate departments, the Extension Manager finds an available extension from the department's pool of five and assigns it to the user.
The Dept Managers, Fashion-home, and Consumables have ‘dep_auto’ set to no. When a user selects one of these departments, the user is prompted to select one of the available extensions, as shown in Figure 8. General Managers, Figure 9, have the same option.
Fashion Home Extension Selection
Fashion Home Extension Selection
General Manager Extension Selection
General Manager Extension Selection
Dept. Mgr Extension Groups
Dept. Mgr Extension Groups
This leads to the device consuming old licenses. Voice Client does not refresh the license validity unless the license check interval has elapsed, the token has been scanned, or the system has been rebooted. Since the license validation interval is 90 days, the Voice Client might not pull the license for 90 days. The device checks the license validity date in various locations where the license was used and displays an error message such as " Your License Has Been Expired."When the Voice Client takes extensions from the Extension Manager, it fetches the available license with the farthest expiry date.
EXM always returns the available license with the farthest expiration date. This is performed when the Voice Client takes extensions from EXM.
When the device license is synchronized from the Extension Manager to the Provisioning Manager, the device license data is pushed to the Provisioning Manager. At that time, the Provisioning Manager checks whether the device-license data exists. If it exists, the Provisioning Manager compares which of them is the latest and updates the data in the Provisioning Manager only if the Extension Manager has the latest data. Before license synchronization, if we have a license with quantity two, the Voice Client can fetch 2 licenses from the Extension Manager and 2 licenses from the Provisioning Manager. So, a total of 4 devices can be fetched.