View Subscribers
In the Admin Portal, you can view a summary list of all subscribers (at the current hierarchy and down),
which includes details of each subscriber’s currently provisioned services, grouped by vendor.
To view subscribers in the Admin Portal, go to (default menus):
The table describes columns in the Subscribers summary list:
Column Heading |
Description |
|---|
Role |
Subscriber role, typically a self-service user role. |
Sync Source |
The source application of user data, for example:
LOCAL indicates that the user has been manually created in VOSS Automate and has not been synced from LDAP
or from Cisco Unified CM.
CUCM indicates that the user exists on both VOSS Automate and Cisco Unified CM, and is not synced from LDAP.
The user may have been created first on VOSS Automate (top-down) or created on Cisco Unified CM and synced
into VOSS Automate (bottom-up).
As for User .
|
User Type |
End User, Admin - associated with the user role |
Auth Method |
As for User . |
Entitlement
Profile |
The Entitlement Profile associated with the Subscriber. |
Located At |
Displays an abbreviated version of the hierarchy showing the lowest
point in the hierarchy. The hierarchy type is shown in brackets.
When you filter on this column, do not use text included inside
the brackets in the filtering criteria. For example:
“SiteName (Site)”, where (Site)= the hierarchy node type, only
search using the “SiteName” portion of the field. |
PrimaryLine |
The subscriber’s primary extension number, as selected from the
Pattern drop-down list when adding the subscriber.
For Multi Vendor only, the line extension used as the primary line (a pre-allocated administrator line, and
associated E164 number).
|
ExtMobility |
If a Subscriber is associated with more than one extension
mobility profile on the Unified CM, and you sync with VOSS Automate,
only the first extension mobility profile is displayed in this
list view. |
Single Number
Reach |
The remote destination number configured for the subscriber. Only
if supported. |
Voice |
Multi vendor subscribers only. The subscriber’s provisioned phones, listed by vendor. |
Voicemail |
The Voicemail number allocated to the subscriber.
In a multi vendor environment, the subscriber’s provisioned voicemail services are listed by vendor.
|
Conferencing |
Enabled or disabled.
In a multi vendor environment, the subscriber’s conferencing services are listed by vendor, for example,
Webex Teams, MS Teams, Pexip, Zoom.
|
Collaboration |
Multi vendor subscribers only. The subscriber’s messaging services, listed by vendor, for example, WebEx,
MS Teams, Zoom. |
Column Heading |
Description |
|---|
Webex Teams |
Defines whether a subscriber is enabled for Webex Teams. |
Contact Center |
Enabled or blank. Indicates the contact center agent’s Team and
extension if the subscriber is an agent. |
Phone |
The phone associated with the subscriber. When you filter on this
column, the results include all phones at the hierarchy level and
below, regardless of the Phone column in which they reside. |
Phone 2 |
The second phone associated to the subscriber. |
Phone n |
The number of phone columns displayed in the list view will be the
same as the maximum number of associated to a particular
subscriber. For example, if a subscriber is associated to 10
phones, the list view will show 10 Phone columns. |
Device |
IP Address or Host Name. |
Related Topics
Add a Subscriber
This procedure adds a subscriber in VOSS Automate.
Note
If Enable CSS filtering is enabled at the customer dial plan, available calling
search spaces includes only those marked as a Class of Service in (default menus)
Dial Plan Management > Site > Class of Service at the particular site. If
another CSS is required, you can add custom CSSs in a CSS field if you know
the exact syntax.
If Enable CSS filtering is disabled, the list of available calling
search spaces includes all CSSs that are configured on VOSS Automate.
To add a subscriber:
Log in to the Admin Portal as Customer admin or Site admin.
Note
When logged in as the Customer admin for a specific site, all fields described in this
procedure are visible.
When logged in as the Site admin, only a subset of fields are available.
Go to (default menus) Subscriber Management > Subscribers.
On the Subscribers page, click Add.
If you’re logged in as Customer admin, choose the site where you want to add the subscriber.
Configure subscriber details on the tabs of the form:
User tab
Phones tab
Extension Mobility tab
Single Number Reach tab
Voicemail tab
Webex tab
Webex Teams tab
Pexip Conference tab
Contact Center tab
Click Save.
Repeat this procedure to add another subscriber.
User Tab
The User tab defines the user details of a VOSS Automate subscriber you’re adding or updating.
Note the following:
Only alphanumeric characters are allowed.
For Cisco users, available entitlement profiles are imported from Unified CM.
When choosing an existing device (phone) to associate with a user and then saving the form, the
Phones tab is populated with the phone details.
When adding a LDAP user as a subscriber, Password fields are hidden, and
Enable Mobility is enabled by default, when any of the following is included or added:
A remote destination phone
Mobile identity for a phone
Remote destination profile (RDP)
If subscriber self-provisioning is set up (allowing subscribers to add their own
smart devices, such as company or personal phones), and Enable Mobility is
disabled (checkbox cleared), then the setting is enabled when subscribers add a company
or personal phone via the Self-service interface.
To enable Extend and Connect in VOSS Automate:
On the Users tab, select the Enable Mobility checkbox.
Add the following three groups of users:
Standard CCM End Users
Standard CTI Enabled
Standard CCM Admin User
For subscribers entitled to Webex Teams, you can add a standalone Webex
Teams user by completing the following minimum fields on the User tab, then go directly to the
Webex Teams tab: Userid, Last Name, Email Address
To provide access to EMCC (only customers configured for EMCC), select
Enable EMCC.
The group you choose in BLF Presence Group (configured in Cisco Unified Administration),
specifies destinations the subscriber can monitor.
Note
BLF Presence Group authorization works with BLF Presence Groups to allow or
block presence requests between groups. The Busy Lamp Field default is set
according to the selected number and specifies the Standard Presence Group
that is configured with installation.
For Primary Extension, the pattern you choose specifies the lines available to the subscriber. Your choice
displays in the Primary Line column on the Subscribers list view.
Subscriber Language and Role is set up in the Site Defaults of the subscriber’s site hierarchy. If this
is not specified, hierarchy defaults apply.
Phones Tab
On the Phones tab you can add or update a subscriber’s phone.
To add a phone:
On the Phones tab, click Add.
Provide a device name, description, product type, device protocol, phone button
template, and device security profile.
Note
Values for the following fields are dynamic, and change based on options selected in associated
fields.
Product Type
Device Protocol
Phone Button Template
Device Security Profile
For example, when adding a device name with the product prefix and MAC address,
79XX-type phones have the device name ‘SEP’ prefixed, while ATA-type phones have ‘ATA’ prefixed
to the MAC address. Field validation and tooltips provide guidance when you select the product type.
Click Save.
Consider the following when adding a phone:
You can override the Phone Button Template value. Either choose another option, or
type in a custom value. The value is applied on Unified CM if the Unified CM allows it for the phone type.
Modify phone-specific settings, such as DND Option, Do Not
Disturb, and Hot Line Device.
Note
Available phone settings depend on the selected product type (phone type),
the device protocol (for example, SIP or SCCP), and the Field Display Policy (FDP) applied by the
administrator.
You can choose a Mobile User ID Name from the drop-down list when a Dual-Mode
Phone for Android or iPhones is selected. This associates the selected user to
the Mobile Identity feature on this phone and must match the Userid added on
the User tab.
Advanced settings fields are updated automatically for the phone based
on the phone type. The phone is automatically associated to the user and is
then displayed as an associated device for the subscriber after you save.
When associating a phone that is also associated with another user,
the Owner User ID defaults to the first user.
Line assignments are added in the Line section:
The Pattern field only shows lines with status Available or Used.
Pattern options in Route Partition Name are based on the selected partition selected. You
can type in a custom pattern value.
Enduser - identifies the user for Presence; you can add a new User ID
Note
VOSS Automate adds the user first and then adds the User ID.
Speed dial information is added in the Speeddial section. Available options depend on the
selected Phone Button Template.
Busy lamp field information is added to the Busy Lamp Field section. Options include:
Position
Label
Blf Destination
Add busy lamp field directed details in the Blf Directed Call Park section. Values depend on the
values on a valid Directed Call Park on Unified CM.
Specify add on modules (if any) in Add On Module. The phone type must support the model you choose.
Leave Load Name blank, unless you want to overwrite the default.
Add a valid IP phone service subscription to the phone, in the Services section:
Choose the IP phone service from the Service Name field.
Note
Subscribing a phone or a device profile to a service auto-populates the URL field in Services. To
populate this field, when a service is added or updated the system retrieves the URL and a custom
parameter (if any) from device/cucm/IpPhoneService.
To add the service to the device, add a number as the Uri button index to the Url Button Index
field. If you don’t add a number, only the service is added.
In the Mobile Identity section, configure mobile identity details when selecting a
Dual-Mode Phone.
These fields are auto-populated from the Device Name field: Name, and Dual-Mode Device.
Choose a mobility profile.
Mandatory. Specify a value for Destination Number. This option determines the destination number
that is dialed when a call is made to the dual-mode phone.
In the Remote Destination section, to configure your remote destinations
when a Dual Mode Phone or Cisco Spark Remote Device is selected as the
Product.
Note
Remote destinations represent the mobile (or other) phones that are able to accept
transfer from the desktop phone and can be used to initiate calls. Set the Pattern for the
Line Association to the Route Partition name. If you enter more than one
Pattern and the new Pattern is not on the system, enter the Route Partition Name manually.
The Owner User Id and Dual Mode Device Name fields are auto populated.
When a CTI Remote Device is selected as the Product, a CTI Remote Destination
section replaces Remote Destination. This allows you to configure your
remote destinations specifically for a CTI Remote Device. The Owner User Id and
CTI Remote Device fields are auto populated.
In the Vendor Config section, view and edit the configuration settings for each
device. Available configuration settings depend on each product type chosen. Update the settings as
required.
Note
The administrator password from the AdminLoginDetails in Unified CM is not stored
in VOSS Automate. Data in VOSS-4UC is obtained from Unified CM.
VOSS Automate cannot disable the Override Enterprise/Common Phone Profile Settings
setting once this check box has been enabled in the Unified CM GUI. This setting may be
disabled on Unified CM (if required).
Extension Mobility Tab
The Extension Mobility tab configures a subscriber’s extension mobility settings.
Consider the following:
Only one EM Profile can be added for extension mobility in VOSS Automate. If
a subscriber is associated with more than one EM profile on the Unified CM,
and you sync with VOSS Automate, both will be displayed:
Values for the following fields are dynamic, based on selections in associated fields:
Product
Protocol
Phone Button Template
Note
For details of configuration options on this tab, see the descriptions for the
Phones tab. The exception is remote destination information, which is
not relevant for extension mobility.
Ensure that you associate the extension mobility profile and target
phone for login with the extension mobility service.
If the Enable Extension Mobility Cross Cluster (EMCC) feature is enabled on
the User tab, you must choose a CSS for this device from the Extension
Mobility Cross Cluster CSS drop-down. The selected CSS is used as the device
CSS that gets assigned to the phone when the user logs in to this remote phone.
New CSS’s or existing CSS’s can be added or modified in Unified CM. Refer to
the Cisco Unified Communications Manager Features and Services Guide for more
details if required.
See also Configure Extension Mobility Profile to add or edit an extension mobility
profile, and associate it to one or more subscriber.
Single Number Reach Tab
On the Single Number Reach tab, note that you cannot add more than one
Remote Destination Profile for Single Number Reach. However, you can add more
than one Remote Destination Rdp.
To enable Extend and Connect in VOSS Automate, first complete the following
task:
Select the Enable Extend and Connect check box.
Select the CTI remote device that you created from the CTI Remote Device
Name drop-down list.
Voicemail Tab
The Voicemail tab configures the subscriber’s voice mail service, provided a valid
Cisco Unity Connection server is available.
When configuring voicemail:
PIN and Password can be left blank. In this case, the default
credential policy on the Cisco Unity Connection is used.
If the user on Cisco Unity Connection is LDAP integrated, the Password field
is visible but should be ignored.
The Voicemail Line drop-down list only shows lines with status ‘Available’
or ‘Used’ that are not already configured for Voicemail.
Note
The Cisco Unity Connection (CUC) server uses this line as a caller ID, so you should set it to the
subscriber’s default line.
When adding Voicemail for a subscriber, all Call Forward To Voicemail check
boxes, except Call Forward All, are enabled on the chosen Line, and the
Voicemail Profile setting will be set based on the Site Default Doc setting
“Default CUCM Line Voicemail Profile” (Site Management > Defaults > Line Defaults).
WebEx Tab
The WebEx tab configures the subscriber’s Webex details, if a valid server is available. The mandatory
fields on this tab are populated with the values entered on the User tab.
Note
Any updates on the User tab do not update these values; values are populated
only during the Add workflow.
Webex Teams Tab
The Webex Teams tab adds a Webex Teams User and enables a subscriber’s services and roles.
Consider the following:
Webex Teams is only available when:
The following fields are read only and cannot be edited: Login Enabled and Invite Pending
Once you have successfully added the subscriber as a Webex Teams user, the
Webex Teams column displays status Enabled for this subscriber.
The Subscriber e-mail address is required to enable Webex Teams for the Subscriber.
Pexip Conference Tab
The Pexip Conference tab adds and configures the subscriber’s Pexip services.
Consider the following:
The Pexip Conference tab is only available if a Pexip Conference service has
been configured at the required hierarchy (via the Quick Add Subscriber Group).
Conferencing must be enabled in the entitlement profile associated with the subscriber.
Once a subscriber is successfully added as a conferencing user, you can view the service
as an enabled service in the Conferencing column on the Subscribers list.
Delete a Subscriber
This procedure deletes and unprovisions a subscriber.
Log in to the VOSS Automate Admin GUI as a Customer admin or Site admin.
Note
All fields are available to Customer admins at the site. Only a subset of
fields display for Site admins.
Choose the relevant site.
Go to (default menus) Subscriber Management > Subscribers.
Select the checkbox for each subscriber you want to remove; then click Delete.
Click Yes to confirm.
The deleted subscriber is removed from the list. All elements
associated with the subscriber are removed, except lines.
Note
For scenarios that include an LDAP-integrated Cisco Unified Communications
Manager, users are deleted from the LDAP directory and not
from the VOSS Automate system. Set up a data sync to synchronize the removal of
the user.
