No changes.
In Cisco Unity Connection, some of the features that are available to
users with voice mailboxes are controlled by class of service (COS),
including features for which you need user licenses. You can update the
settings in a COS to enable or disable features and functionality at any
time. The changes that you make affect all COS members.
Because a COS defines limits and permissions for using Cisco Unity
Connection, its settings should be appropriate for the group of users
that you are adding. For example, a COS:
- Controls access to features, such as Text to Speech email or live reply.
- Controls how users interact with Connection. For example, a COS
dictates the maximum length of user messages and greetings, whether
users can choose to be listed in directory assistance, and whether users
can send messages to a system distribution list.
- Specifies the restriction table used to control the phone
numbers that users can use for message notification, call transfer, and
other tasks.
Keep in mind that if you change the COS that is specified on a user
template page, any user accounts that have already been created based on
that template are not reassigned to the new COS. In contrast, when you
modify the settings in a COS, the changes affect both new and existing
members, so you can update COS settings before and after you create user
accounts. You can also reassign a user to a different COS at any time.
No changes.
A COS is specified in each user template; thus, a user is assigned to
the COS that is specified in the template on which the user account is
based. If you find that the settings for a particular COS are no longer
appropriate for an individual user or several users, you can reassign
the users to another COS at any time. (Changing the COS that is
specified in a template does not affect user accounts that have already
been created.)
The following lists the users as members of COS:
| Class of Service Membership |
| Class Of Service | Members |
Voice Mail User COS
| Detected Change ID | 1 | | Detected Change | Updated record 'Voice Mail User COS' | | Detected Object | Class of Service Membership | | Detected Date (UTC) | 2/29/2024 12:04:29 PM | | Detected Date (Local) | 2/29/2024 1:04:29 PM | | Child ID | 2 | | | Alias | First Name | Last Name | Display Name | Extension | | agent1 | agent1 | UCCX | agent1 UCCX | +61290004001 | aps01
| Detected Change ID | 2 | | Detected Change | Added record with key 'aps01' | | Detected Object | Class of Service Membership | | Detected Date (UTC) | 2/29/2024 12:04:29 PM | | Detected Date (Local) | 2/29/2024 1:04:29 PM | | Parent ID | 1 | | aps | 01 | aps 01 | +61290004176 |
|
Each user that you add in Cisco Unity Connection is based on a template.
Settings from the template are applied to the user as the new user is
created or imported. (Changes to template settings do not affect
existing users.)
Users with voice mailboxes are end users; users without voice mailboxes are system administrators.
Connection has the following User Template types
- User With Mailbox: For users who need to receive voice mail or use
personal call routing rules and other features of Cisco Unity
Connection.
- User Without Mailbox: For users who do not need to receive
voice mail, but need to be given access to administer the system. Users
without voice mailboxes do not have a phone extension and are not
counted as licensed users.
No changes.
Each call handler that you add in Cisco Unity Connection is based on a
template. Settings from the template are applied to the call handler as
the call handler is created. (Changes to template settings do not affect
existing call handlers.)
Connection comes with the following predefined call handler templates, which you can modify but not delete:
- System Call Handler Contact Template: The settings on this template are suitable for most contacts.
- System Call Handler Template: The settings on this template are suitable for most call handlers.
Before you create call handlers, review the settings in the template
that you plan to use and determine whether you need to make changes or
create new templates. For each template, you will want to consider
enabling the appropriate transfer, caller input, greetings, and message
settings for the call handlers that you plan to create. If you change
settings on a call handler template, the new settings will be in effect
only for new call handlers that are created by using that template.
Deleting a call handler template will not affect any call handlers that
were based on that template when they were created. Note that you cannot
delete the default templates.
No changes.
Each contact that you add in Cisco Unity Connection is based on a
template. Settings from the template are applied to the contact as the
new contact is created or imported. (Changes to template settings do not
affect existing contacts.)
No changes.
Intelligent Notifications deliver rich, customizable, and actionable
voice message notifications. When connected to the corporate network,
they provide users the ability to play, reply, forward, mark unread, and
delete a specific message.
The following Notification Templates are configured:
No changes.
Custom variables give flexibility to populate content in an HTML
notification. Administrators are allowed to create different custom
variables that can be used while creating the HTML-based notification
templates. For example, the custom variables can be used in case of
defining a particular company's name, address, any numbers, or URLs.
Custom Graphics define graphic objects which can be inserted in an HTML
notification. Administrators are allowed to create Custom Graphics that
can be used while creating the HTML-based notification templates.
No changes.
Replaceable Images overwrite default images used by notifications to users.
The administrator has rights to replace the default images for the following status items:
- Deleted_message
- MWI_OFF, MWI_ON
- Read_message, Unread_message
- Read_urgent_message, Unread_urgent_message
These images can anytime reset to default through the Restore Default
option given on the Search Replaceable Images page. The addition or
deletion of any image is not allowed in the given default list.
No changes.
| Contacts (Summary) |
| Alias | First Name | Last Name | Display Name | Department | Extension | Partition | 1st Alternate Name | 1st SMTP Proxy Address | List in directory |
Contact1
| Detected Change ID | 3 | | Detected Change | Updated record 'Contact1' | | Detected Object | Contacts (Condensed) | | Detected Date (UTC) | 2/29/2024 12:04:50 PM | | Detected Date (Local) | 2/29/2024 1:04:50 PM | | Child ID | 4 | | Contact1 | Last1
Last12
| Detected Change ID | 4 | | Detected Change | Updated field 'Last Name' from Last1 to Last12 | | Detected Object | Contacts (Condensed) | | Detected Date (UTC) | 2/29/2024 12:04:50 PM | | Detected Date (Local) | 2/29/2024 1:04:50 PM | | Parent ID | 3 | | Contact1 Last1 | | | cuc218 Partition | | | Y |
When a user addresses a message to a system distribution list, the local
Cisco Unity Connection location parses the distribution list
membership. The sending location first addresses messages to any VPIM
users that are on the distribution list. Next, the sending location
checks to see if there are any remote Connection users in the
membership; if so, it sends a single message to each location that homes
these remote users, addressed to the distribution list (the home
locations each parse the message and deliver to their local users).
Finally, the sending location checks for local users in the distribution
list membership, and delivers the message to each of them.
Connection includes the following predefined system distribution lists:
All Voice Mail Users, Undeliverable Messages, and All Voicemail-Enabled
Contacts. Each Connection server in your organization has a distinct
version of each of these lists. If you have not changed the names of
these lists to be unique, during initial replication each server
automatically adds the remote server name to the display name of any
remote lists whose names overlap with local list names.
By default, the predefined lists on each Connection location have the
same recorded voice name, and the All Voice Mail Users and All
Voicemail-Enabled Contacts lists have the same extension at each
location (the Undeliverable Messages list by default is not assigned an
extension, because users do not typically address messages to this
list). When setting up Digital Networking, you should consider modifying
the recorded voice name of each All Voice Mail Users list and each All
Voicemail-Enabled Contacts list; if you do not, users can hear a
confusing list of choices when they address messages by name to one of
these lists. When users address by extension to a list whose extension
overlaps that of another list, they reach the first list that is located
when Connection searches the partitions of the user search space in
order.
Tip : Distribution lists can be nested such that a distribution list
contains other lists. You can create one master All Voice Mail Users
distribution list that contains the All Voice Mail Users list of each
Connection location.
The following distribution lists are configured:
| Distribution List |
| Name | Details |
allvoicemailusers
| Detected Change ID | 5 | | Detected Change | Updated record 'allvoicemailusers' | | Detected Object | System Distribution Lists | | Detected Date (UTC) | 2/24/2024 6:05:05 PM | | Detected Date (Local) | 2/24/2024 7:05:05 PM | | Child ID | 6 | | | Distribution List | | Display Name | All Voice Mail Users | | Extension | 99991 | | Partition | cuc218 Partition | | Replicate to Remote Sites Over Intersite Links | Y | | Allow Contacts | N | | Accept Messages from Foreign Systems | N | | Replicate to SRSV Branches | N | | Distribution List Members | | Distribution List Members | aps01
| Detected Change ID | 6 | | Detected Change | Updated field 'Distribution List Members::Distribution List Members' : aps01 | | Detected Object | System Distribution Lists | | Detected Date (UTC) | 2/24/2024 6:05:05 PM | | Detected Date (Local) | 2/24/2024 7:05:05 PM | | Parent ID | 5 | | | Alternate Names | | Alternate Names | |
|
Interview handlers collect information from callers by playing a series
of questions that you have recorded, and then recording the answers
offered by callers. For example, you might use an interview handler to
take sales orders or to gather information for a product support line.
You can specify who receives the messages for the interview handler,
whether the message is marked for dispatch delivery, whether the message
is marked urgent, and what action to take next on the call after a
message is left.
When all the answers have been recorded, they are forwarded as a single
voice message, with beeps separating the answers, to the recipient (user
or distribution list) that you designate in the interview handler
configuration.
No changes.
Directory handlers provide directory assistance that callers can use to
reach Cisco Unity Connection users who have mailboxes and who are listed
in the directory.
When a caller searches for a user name or part of a name, a directory
handler looks up the extension and routes the call to the appropriate
user. Callers can also enter an extension to place a call from a
directory handler; the extension is checked against the applicable
outcalling restriction table if the caller is a user, or against the
Default Outdial restriction table if the caller is an outside caller.
There are two types of directory handlers:
- Phone Keypad: Callers enter search information or extensions by using the phone keypad.
- Voice Enabled: Requires voice-recognition option.callers say
the first name and last name (or alternate names) of the Connection user
that they want to reach, or enter an extension by saying the individual
digits in the extension.
No changes.
Interview handlers collect information from callers by playing a series
of questions that you have recorded, and then recording the answers
offered by callers. For example, you might use an interview handler to
take sales orders or to gather information for a product support line.
You can specify who receives the messages for the interview handler,
whether the message is marked for dispatch delivery, whether the message
is marked urgent, and what action to take next on the call after a
message is left.
When all the answers have been recorded, they are forwarded as a single
voice message, with beeps separating the answers, to the recipient (user
or distribution list) that you designate in the interview handler
configuration.
No changes.
Indicate whether Cisco Unity Connection plays a recording to callers
before allowing them to leave a message for the user or call handler.
You can also indicate whether all callers hear the recording or only
unidentified callers:
- Do Not Play Recording: Before they leave a message, callers hear only the user or call handler greeting.
- Play Recording to All Callers: Before they leave a message,
users and outside callers hear the user or call handler greeting and
then the recording.
- Play Recording Only to Unidentified Callers: Before they leave a
message, outside callers hear the user or call handler greeting and
then the post-greeting recording. Likewise, users who call from a phone
that is not associated with their account and do not sign in to
Connection hear the post greeting recording.
Default: Do Not Play Recording.
Direct rules handle calls from users and outside callers that are dialed
directly to Connection. The predefined direct routing rules are:
- Attempt Sign-In: Calls from users are routed to the user logon conversation.
- Opening Greeting: Calls from outside callers are routed to the Opening Greeting.
No changes.
Forwarded rules handle calls that are forwarded to Connection from
either a user extension or from an extension that is not associated with
a user account (such as a conference room). The predefined forwarded
routing rules are:
- Attempt Forward: All calls forwarded from a user extension are routed to the user greeting.
- Opening Greeting: Calls forwarded from an extension that is not
associated with a user account are routed to the Opening Greeting.
No changes.
A mailbox store is a database for voice messages (who each message was
sent to, when it was sent, the location of the WAV file on the hard
disk, and so on).It points to an operating-system directory for voice
message WAV files.
An administrator with the required permissions can create up to four
additional mailbox stores. Each additional mailbox store includes:
- Another mailbox-store database for information on voice messages
that are saved in that mailbox store. The database is presized for an
average of approximately 40 messages each for 10,000 users, or about
1.25 GB. (The database application currently being used for Connection
cannot dynamically resize a database after it is created.)
- Another operating-system directory for the voice message WAV files and other message attachments saved in that mailbox store.
Although there is one mailbox-store database for each mailbox store,
there is only one directory database for the entire system. If you
create an additional mailbox store and move the mailboxes for selected
users to the new store, the directory information for the users remains
in the directory database that was created when Connection was
installed.
After you create a new mailbox store, you can either move existing
mailboxes into the new store or you can create new mailboxes in the new
store.
| Mailbox Store |
| Mailbox Store | Server | Display Name | System | Mounted | Maximum Size
Before Warning (MB) |
UnityMbxDb1
| Detected Change ID | 7 | | Detected Change | Updated record 'UnityMbxDb1' | | Detected Object | Mailbox Stores | | Detected Date (UTC) | 2/29/2024 12:05:03 PM | | Detected Date (Local) | 2/29/2024 1:05:03 PM | | Child ID | 8 | | cuc218 | Unity Messaging Database -1 | Y | Y | 15001
15002
| Detected Change ID | 8 | | Detected Change | Updated field 'Maximum SizeBefore Warning (MB)' from 15001 to 15002 | | Detected Object | Mailbox Stores | | Detected Date (UTC) | 2/29/2024 12:05:03 PM | | Detected Date (Local) | 2/29/2024 1:05:03 PM | | Parent ID | 7 | |
This section lists the membership of user mailboxes within the mailbox stores:
No changes.
To help control the size of user voice mailboxes, Cisco Unity Connection
lets you specify quotas, or limits, on the maximum size of voice
mailboxes. By default, Connection is configured with the following
systemwide mailbox size quotas:
|
Quota Level
|
Mailbox Size That Triggers Quota Action
|
Action When Quota Is Reached
|
Recording Time in Minutes Before Quota Is Reached
|
|
G.711 Mu-Law
|
G.711 A-Law
|
G.726 32 Kbps
|
PCM 8 kHz
|
G.729a
|
|
Warning |
12 megabytes |
The user is warned that the mailbox is reaching the
maximum size allowed. |
25 |
25 |
50 |
50 |
200 |
|
Send |
13 megabytes |
The user is prevented from sending any more voice
messages. |
27 |
27 |
54 |
54 |
217 |
|
Send/ Receive |
14 megabytes |
The user is prevented from sending or receiving any
more voice messages. |
31 |
31 |
61 |
61 |
246 |
The following following systemwide mailbox size quotas are configured:
No changes.
The system will send mailbox quota alert emails to users once a mailbox
quota has been reached. This section defines the subject line and body
text fields for this alert email. Each language that is installed on the
system has a separate mailbox quota alert.
The following mailbox quota alerts messages are defined:
No changes.
To help ensure that the hard disk where voice messages are stored does
not fill up, you can configure Cisco Unity Connection message aging
rules to automatically:
- Move read messages to the Deleted Items folder after a specified number of days. This rule is disabled by default.
- Permanently delete messages in the Deleted Items folder after a specified number of days. This rule is enabled by default.
- Based on the age of the messages, permanently delete secure messages that have been touched in any way (for example by
- saving, deleting, or opening but then saving messages as new). This rule is disabled by default.
- Based on the age of the messages, permanently delete all secure
messages regardless of whether users have listened to or touched the
messages in any way. This rule is disabled by default.
You can enable or disable these message aging rules, and you can specify
a different number of days for each rule. You can also enable or
disable the message aging policy; disabling the policy means that the
rules are not enforced regardless of their settings.
If the message aging policy is enabled, and if one or more message aging
rules are enabled, you can still disable message aging for individual
users on the Voice Mailbox page. However, if the message aging policy is
disabled, you cannot enable it for individual users.
No changes.
For each message aging rule, you can specify whether Connection sends
email alerts to users prior to taking the aging action that is
associated with the rule. This gives users time to review and act on the
applicable messages. You specify the number of days between the time
that Connection sends the alert and the time that the message aging
action takes place.
Alerts cannot be sent to users unless the Corporate Email Address field
for each user contains a valid email address. Connection must also be
configured to relay messages through an SMTP smart host.
You can customize the text in the email alerts or you can use the
default text. The default subject line and body text are different for
the alerts related to each aging rule, and they can be customized
separately. All message aging policies use the same five rules.
No changes.
The Message Recording Expiration feature guarantees that a voice message
that is stored on the Cisco Unity Connection server cannot be listened
to after it reaches a set expiration date, regardless of whether the
message has been forwarded to another Connection recipient. Message
Recording Expiration is a systemwide setting, and thus cannot be applied
only to a subset of users.
You set the number of days after which messages arrive that they will
expire. At expiration, message recordings are automatically replaced
with a decoy recording that says, 'The message has expired.'
Typically, message aging rules are sufficient for enforcing
message-retention policies. Note, however, that when a message is
forwarded, the forwarded message is considered a new message and its age
is reset. If you are concerned that users may forward messages in an
attempt to circumvent the message-retention policy, consider enabling
the Message Recording Expiration feature. The message recording and
transcription (if any) expire based on the date that the original copy
of the message arrived, regardless of user forwarding.
By default, the Message Recording Expiration feature is not enabled.
If you enable the Message Recording Expiration feature, we recommend
that you configure the expiration time frame to be two to three times
longer than the message aging time frame. (For example, if all of your
messages are marked secure by default and you have a message aging
policy set to permanently delete all secure messages older than 60 days,
configure message recordings to expire in 180 days.)
Note that the Message Recording Expiration feature does not apply to
messages that have been forwarded to personal email addresses or to
message recordings that have been saved locally to user workstations. To
prevent users from saving local copies or forwarding voice messages to
personal email addresses, consider configuring Connection to mark all
messages as secure.
Connection applies the Message Recording Expiration feature to messages
in the mailboxes of recipients that are homed on the Connection server.
For example, if User A homed on Connection server A sends a message to
User B homed on Connection server B, the message will be subject to
message expiration only if the Message Recording Expiration feature is
enabled on server B.
No changes.
Cisco Unity Connection Survivable Remote Site Voicemail (Connection
SRSV) is a backup voicemail solution that allows you to receive voice
messages during WAN outages. This is a new feature starting with CUC
version 9.1. It works in conjunction with Cisco Unified Survivable
Remote Site Telephony (SRST) for providing voicemail service to a branch
when the connectivity with the central Connection voicemail service is
lost.
Connection SRSV is used in the centralized Cisco Unified Communications
Manager and Cisco Unity Connection environment with multiple branch
offices or small sites. It provides limited voicemail and auto-attendant
features that remain in synchronization with the central Connection
voicemail service so that when the WAN outage or failure occurs, the
Connection SRSV solution can provide voicemail service to the
subscribers at the branch.
The following branches are configured:
Central to how Digital Networking works is an object referred to as a
Cisco Unity Connection location. Each Connection server (or cluster) on
the network is represented by a single Connection location, which is
created locally during installation and which cannot be deleted from the
server itself. When you join the server (or cluster) to a Digital
Network, a Connection location is created for the server (or cluster) on
all other locations in the network, and these locations automatically
begin to perform directory synchronization with the new location. If you
remove the server (or cluster) from the Digital Network, the
corresponding Connection location is removed from all other locations on
the network, and its directory information is automatically removed
from these locations (and vice versa). A Connection location can only
belong to a single Digital Network. As soon as you join one server to a
location on the Digital Network, any other locations on the network are
notified of the new location and begin to exchange directory information
with the new location.
All objects that you create on a particular location are said to be
"homed" on that location. To modify the properties of an object or to
delete the object, you must use the administration tools on the location
that homes the object. Each location has its own directory of users and
other objects, and replicates a subset of these objects and their
properties to other locations; the collection of objects and object
properties that are replicated among locations is referred to as the
Connection directory.
In the context of Digital Networking, an object that is homed on a
location is sometimes referred to as local for that location (for
example, a local user) and an object that is homed on a different
location is referred to as remote.
No changes.
When you use the recommended approach of configuring a single Cisco
Unity Connection location on the Digital Network as a bridgehead to
handle all VPIM locations, the VPIM location data and all contacts at
the VPIM location (including automatically created contacts) are
replicated to other locations in the network. When a VPIM message is
sent to or from a user at another Connection location, the message first
passes to the bridgehead, which handles forwarding the message to the
destination server.
The following VPIM locations are configured:
Unified messaging services are used to synchronize Cisco Unity
Connection and Exchange mailboxes (single inbox) on Exchange servers.
The following Unified messaging services are configured to access Exchange server(s).
The following table list the status of the unified messaging
configuration of each Cisco Unity Connection user for Microsoft Exchange
and for Unified Messaging and Cisco Unified MeetingPlace.
When the SpeechView feature is enabled, Cisco Unity Connection uses a
third-party external transcription service to convert voice messages to
text. When a voice message arrives, it is delivered to the mailbox of
the recipient with a blank text attachment. When the completed
transcription is returned by the transcription service, the text
attachment is updated with the text of the transcription, or with an
error message if there was a problem with the transcription. Only the
first 500 characters of a message transcription are provided, so longer
messages are truncated. However, users have access to the original
recording in its entirety.
Connection sends the audio portion of a voice message to the
transcription service, without details about the sender or recipients of
the message. Communication between Connection and the external
transcription service is secured by using S/MIME over SMTP.
To use SpeechView, users must belong to a class of service that enables
transcriptions of voice messages. Members of the class of service can
view the transcriptions of their messages by using an IMAP client that
is configured to access their Connection messages. The original voice
message remains attached to the transcribed text message.
The following are the settings for the Transcription Service for SpeechView:
The following Nuance Transcription Error codes are configured:
No changes.
Video
services allow Unity Connection to integrate with video server to store
and retrieve all the video messages and greetings recorded by the user.
In addition, it allows Unity Connection to verify the state of video
server, codecs, and user credentials used with video server.
After
configuring video services in Unity Connection, the administrator needs
to configure video service accounts for each user.
In Cisco Unity Connection, you create partitions as a way to group
together objects to which callers and users can address messages or
place calls while interacting with Connection. One or more partitions
can be grouped together as members of a search space, and a partition
can be a member of more than one search space. The following types of
objects belong to a partition:
- Users with mailboxes (primary extension)
- User alternate extensions
- Contacts (including VPIM contacts)
- System distribution lists
- System call handlers
- Directory handlers
- Interview handlers
- VPIM locations
- In addition, you can use user templates, contact templates, and
system call handler templates to set the partition membership for new
objects of these types.
Extensions must be unique within a partition, although partitions can
contain objects that do not have an associated extension (for example,
some contacts and system distribution lists). The names of objects do
not have to be unique within a partition. System contact phone numbers
also do not need to be unique within a partition.
In general, objects can only be a member of a single partition, although
a user can have a primary extension in one partition and an alternate
extension in a different partition.
No changes.
Search spaces are used to define the search scope of objects (users,
distribution lists, and so on) that a user or outside caller can reach
while interacting with Cisco Unity Connection. For example, the search
scope that is applied to a user identifies which users, distribution
lists, or VPIM contacts the user can address messages to. The search
scope that is applied to a user also identifies which users and system
contacts the user can call by name dialing when using the
voice-recognition conversation.
The following types of objects can use a search space for their search scope:
- Users with mailboxes
- Routing rules (both direct and forwarded)
- System call handlers
- Phone directory handlers
- Voice-enabled directory handlers
- VPIM locations
- In addition, you can use user templates, contact templates, and
system call handler templates to set the search scope for new objects
of these types.
A search space is comprised of one or more ordered partitions. When
Connection searches for an object on behalf of a caller, it searches the
partitions in the order in which they are arranged in the search space.
While extensions must be unique within a partition, they do not need to
be unique within a search space, so you can use search spaces to handle
dial plans that have overlapping extensions.
No changes.
This section contains the general global settings for Cisco Unity Connection:
No changes.
The Cisco Unity Connection cluster feature provides high availability
voice messaging through two Connection servers that are configured in a
cluster. Under normal conditions, the Connection servers are both
active.
When one of the servers stops functioning (for example, when it is shut
down for maintenance), the remaining server assumes responsibility for
handling all incoming calls for the cluster. The remaining server also
assumes responsibility for the database and message store, which are
both replicated to the other server when the connection and its
functionality are restored.
The following cluster member servers are configured:
No changes.
The following services are present on this server:
No changes.
For Connection users who are not linked to user data in an LDAP
directory, this authentication rule applies both to voice mail passwords
and to web passwords.
For Connection users who are linked to user data in an LDAP directory,
this authentication rule applies only to voice mail passwords. Web
authentication and failed logon attempts will be handled by the LDAP
directory, not by Connection.
The following Authentication Rules are configured:
No changes.
System Roles are the predefined roles provided by Unity Connection.
No changes.
System Roles are the predefined roles provided by Unity Connection. This is the list of users with these roles.
No changes.
Custom Roles are the roles that the administrator creates based on the requirements.
Custom Roles are the roles that the administrator creates based on the
requirements. This is the list of users assigned these custom roles.
Restriction tables allow you to control which phone numbers users and administrators can use for:
- Transferring calls-including both the numbers users can enter for
transferring their calls, and the numbers that outside callers can enter
when using Caller system transfers.
- Recording and playback by phone from Cisco Unity Connection
applications, when the phone is the designated recording and playback
device in the Media Master.
- Delivering faxes to a fax machine.
- Sending message notifications.
For example, you can specify that users have calls transferred only to
internal extensions or that faxes are delivered only to local phone
numbers. Restriction tables are applied regardless of how a user or
administrator accesses Cisco Unity Connection. They do not affect the
phone numbers that users can dial when they are not logged on to
Connection.
Each class of service specifies for its members a restriction table for
call transfers, one for message notification, and one for fax
deliveries. The restriction table can be the same for all three, or
different for each. Because users without mailboxes (typically,
administrators) are not assigned to a class of service, Connection
applies the default restriction tables (default transfer, default
outdial, or default fax) to actions taken by these types of users,
including actions taken on behalf of other users.
The following Restriction Tables are configured:
No changes.
This information shows the status of licensed features for the
Connection server. For features that are licensed for a number of seats,
the report displays the number of used and unused seats.
The following table defines the license parameters for Cisco Unity Connection features:
|
License Parameter
|
Feature
|
Description
|
|
LicAdvancedUserMax |
TTS and ASR (advanced) users |
Sets the maximum number of users who can use
voice recognition. |
|
LicIMAPSubscribersMax |
Users with IMAP access to voice messages |
Sets the maximum number of users who can use a
third-party IMAP client to access voice messages. |
|
LicMaxMsgRecLenIsLicensed |
Voice message recordings longer than 30 seconds allowed |
Depending on whether the parameter is present in any of the installed license files, determines the maximum length
of recorded messages:
If the parameter is not present in any of the installed license files
(the License Usage report shows a value of "No"), the maximum
message length is 30 seconds regardless of the settings in
Cisco Unity Connection Administration. |
|
LicRealspeakSessionsMax |
Text to Speech sessions |
Sets the maximum number of simultaneous Text to
Speech (TTS) sessions allowed on the Cisco Unity Connection server.
|
|
LicRegionIsUnrestricted |
U.S. English usage and personal call routing
rules allowed |
Depending on whether the parameter is present
in any of the installed license files, determines whether the
English-United States language and personal call transfer rules are
allowed:
If
the parameter is not present in any of the installed license files
(the License Usage report shows a value of "No"), the English-United
States language and personal call transfer rules are not allowed.
If
the parameter is present in any of the installed license files (the
License Usage report shows a value of "Yes"), the English-United
States language and personal call transfer rules are allowed. |
|
LicServerBackend |
(not used) |
This parameter may be present in a license file
but does not affect the Cisco Unity Connection server. |
|
LicServerVoiceRec |
(not used) |
This parameter may be present in a license file
but does not affect the Cisco Unity Connection server. |
|
LicSubscribersMax |
Users with voice mailboxes |
Sets the maximum number of voice messaging
users allowed in Cisco Unity Connection. |
|
LicUCxnUpgrades |
License files from previous releases allowed
|
Depending on whether the parameter is present
in any of the installed license files, determines whether
Cisco Unity Connection will use license files from an earlier
version of Connection:
If
the parameter is not present in any of the installed license files
(the License Usage report shows a value of "No"), license files from
an earlier version of Connection cannot be used.
If
the parameter is present in any of the installed license files (the
License Usage report shows a value of "Yes"), license files from an
earlier version of Connection can be used. |
|
LicUnityVoiceRecSessionsMax |
Voice recognition sessions |
Sets the maximum number of simultaneous voice
recognition sessions (or ports) allowed on the Cisco Unity
Connection server. |
|
LicVMISubscribersMax |
Cisco Unity Inbox users |
Sets the maximum number of users who can be
enabled to access the Cisco Unity Inbox. There is no restriction on
the number of users who can access the Cisco Unity Inbox at one
time. |
|
LicVoicePortsMax |
Voice ports |
Sets the maximum number of Cisco Unity
Connection voice messaging ports that can be installed on the
Connection server. |
|
LicVPIMIsLicensed |
VPIM Networking delivery locations allowed |
Depending on whether the parameter is present
in any of the installed license files, determines whether VPIM
Networking is allowed:
If
the parameter is not present in any of the installed license files
(the License Usage report shows a value of "No"), VPIM Networking is
not allowed.
If
the parameter is present in any of the installed license files (the
License Usage report shows a value of "Yes"), VPIM Networking is
allowed. |
The following licenses are available:
| Licenses |
| Server | Licensed Seats For: | Feature Name | Limit | Cluster Limit | Used | Unused |
cuc228
| Detected Change ID | 9 | | Detected Change | Updated record 'cuc228' | | Detected Object | Licenses | | Detected Date (UTC) | 2/24/2024 6:06:48 PM | | Detected Date (Local) | 2/24/2024 7:06:48 PM | | Child ID | 10, 11 | | Users with voice mailboxes | LicSubscribersMax | 10 | 10 | 1
2
| Detected Change ID | 10 | | Detected Change | Updated field 'Used' from 1 to 2 | | Detected Object | Licenses | | Detected Date (UTC) | 2/24/2024 6:06:48 PM | | Detected Date (Local) | 2/24/2024 7:06:48 PM | | Parent ID | 9 | | 9
8
| Detected Change ID | 11 | | Detected Change | Updated field 'Unused' from 9 to 8 | | Detected Object | Licenses | | Detected Date (UTC) | 2/24/2024 6:06:48 PM | | Detected Date (Local) | 2/24/2024 7:06:48 PM | | Parent ID | 9 | |
License files, which enable the features purchased by the customer, are
required for configuring a new Cisco Unity Connection system and for
adding or changing licensed features.
Multiple license files can be installed on a Cisco Unity Connection
server. Each installed license file may enable one or more features. All
of the installed license files combined enable the features that the
customer wants.
Each license file (except for the demonstration license file) is
registered to the MAC address of the network interface card (NIC) on the
Cisco Unity Connection server.
Schedules (and associated sets of holidays) are one of the variables
that Cisco Unity Connection uses to manage calls: call handler transfer
rules can be varied based on a schedule and schedules can be applied to
routing rules to change call routing patterns for different time
periods. Schedules also affect when some user and call handler greetings
play.
Connection offers two predefined schedules: All Hours, and Weekdays,
both of which can be modified. (By default, the Weekdays schedule is
configured to observe standard hours from 8 a.m. through 5 p.m. Monday
through Friday, and to observe the predefined Holidays schedule, which
does not contain any dates or times.)
For each schedule that you create or modify, you can identify multiple
ranges of hours and days that make up the standard and closed hours, and
associate a holiday schedule that defines specific holiday dates and
times:
No changes.
When a Holiday setting is in effect, Cisco Unity Connection plays
holiday greetings (if enabled) and observes closed hours transfer rules.
You can set up several years of holidays at a time. Because many
holidays occur on different dates each year, confirm that the holiday
schedule remains accurate annually.
No changes.
The Global Nickname list is a comprehensive list of common nicknames
that Cisco Unity Connection considers when a caller uses voice
recognition to place a call or to address messages. For example,
Connection considers "Bill," "Billy," and "Will" to be nicknames for the
name "William."
If a user has an uncommon name or if others know the user by a different
name (for example, a maiden name) consider adding these alternate names
for the user. Alternate names improve the likelihood of Connection
placing a call when callers ask for the user by name. You can add and
remove nicknames from this list by using Cisco Unity Connection
Administration.
The following nicknames are configured:
No changes.
Message subject lines are visible when users view and listen to messages
in the Cisco Unity Inbox, an IMAP client, an RSS client, or any other
visual client that displays the message subject. Subject lines are not
presented to users when they listen to voice messages by phone.
You can configure both the wording and the information that is included
in the subject line of voice messages, including localizing the subject
line according to the language of the recipient.
The subject lines of the following message types can be defined:
- Outside Caller Messages
Messages from callers who are not Cisco Unity Connection users, and also
from Connection users who send messages without first logging on to
Connection or who have not been automatically identified as Connection
users by the Identified User Messaging feature. This includes messages
that are left for a system call handler.
- User to User Messages
Messages from callers who have either logged on to Connection, or have
been automatically identified as Connection users because Identified
User Messaging is enabled. This includes messages that are left from
users for a system call handler.
- Interview Handler Messages
Messages that are left for interview handlers.
- Live Record Messages
Messages containing conversations that users recorded while they talked to callers.
Subject lines for call handler messages use the definition of outside
caller messages or user to user messages, depending on whether the call
handler message is from an outside caller or a user.
No changes.
When Cisco Unity Connection is integrated with a third-party message
store, Connection uses Text to Speech (TTS) to describe message
attachments for users who check their messages on the phone. For
example, an attachment with the extension .jpg is described as 'an
image.'
The following TTS description(s) for message attachments are configured:
No changes.
Enterprise parameters for Cisco Unity Connection provide default
settings that apply to all services in Cisco Unified Serviceability.
The following list contains all Enterprise Parameters:
No changes.
Service parameters for Cisco Unity Connection allow you to configure different services in Cisco Unified Serviceability.
The following list contains all Service Parameters:
No changes.
Cisco Unity Connection can integrate with the Cisco Fax Server so that
users can do the following while on the phone or while using the Cisco
Unity Inbox:
- Receive faxes that are sent to the fax extension for the user.
Depending on the system configuration, faxes will be available in the
user mailboxes or in the user IMAP clients.
- Forward the faxes that they receive to a fax machine for printing.
- Forward the faxes that they receive to another user.
Inbound faxes are sent to the fax extension for the user. The Cisco Fax
Server uses its email gateway to route the fax through SMTP to the user
mailbox on the Connection server. The Text to Speech (TTS) feature
cannot read faxes.
No changes.
If the check box 'Enable Synchronizing from LDAP Server' is enabled,
Cisco Unity Connection gets basic information on Connection users from
the LDAP directories that you specify on the LDAP Directory
Configuration page. Data is synchronized only for the Connection users
that you created by importing users from the LDAP directory. Connection
does not automatically create new Connection users when new users are
added to the LDAP directory.
If you want to use LDAP authentication, you must enable LDAP synchronization.
No changes.
Cisco Unity Connection LDAP directory configurations specify which users
in the LDAP directory are imported into Connection. For each LDAP
directory configuration, a user search base is specified, which is the
position in the LDAP directory tree where Connection begins its search
for user accounts.
Connection imports all users in the tree or subtree (domain or OU)
specified by the search base. A Connection server or cluster can only
import LDAP data from subtrees with the same directory root, for
example, from the same Active Directory forest.
No changes.
Connection web applications authenticate user names and passwords
against the user name and web application password in the Connection
database if LDAP Authentication is enabled.
When users sign in to Connection by phone, Connection always
authenticates based on the voicemail password in the Connection
database, never based on any value in the LDAP directory.
No changes.
LDAP Custom Filters allow for additional control over which LDAP users
are imported into Cisco Unity Connection. subset of LDAP user accounts
to become Connection users
When creating LDAP directory configurations in Connection, both a user
search base and an LDAP filter must be specified. As applicable, create
filters that integrate with the user search bases that you will specify
for the maximum of five LDAP directory configurations that you can
create.
Each filter must adhere to the LDAP filter syntax specified in RFC 4515,
'Lightweight Directory Access Protocol (LDAP): String Representation of
Search Filters.'
Unity Connection 11.5(1) SU 3 and later provides an enhancement to the
SAML SSO and non SSO login experience for Jabber users by providing the
support of OAuth 2.0 Authorization Code Grant Flow. For faster login,
Authorization Code Grant Flow requires an Authorization Server (Authz
Server) to provide the access and refresh tokens to the Jabber client.
In Unity Connection, the publisher server of Cisco Unified CM associated
with a phone system is configured as an Authz server. After configuring
an Authz server, Unity Connection uses the authorization keys provided
by the Authz server to validate the token of a Jabber client. If
authorization keys are changed on Cisco Unified CM, you must synchronize
the keys between Unity Connection and Authz server. You can configure
multiple Authz server by providing the credential of Cisco Unified CM
associated with the phone system.
CORS is a specification that allows client applications to process
cross-origin requests in a more secure way. Typically for a web
application, cross-origin requests from the original domain (where the
application originated) to another domain are forbidden by the web
browser due to a Single Origin Policy. CORS provide a way for the web
browser and server to interact and determine whether or not to allow
cross-origin request. CORS standard uses HTTP headers to establish an
agreement between the web browser and the Unity Connection server to
provide services to permitted domains.
Unity Connection provides support to the client applications of a cross
domain server to access content on a Unity Connection server directly by
creating an entry for cross domain server in Unity Connection. The
entry for cross domain server must pre-exist in Unity Connection to
process the CORS requests.
Unity Connection has extended the Single Sign On (SAML SSO) endpoint to support CORS.
By using SMTP, Cisco Unity Connection can send text notification to
notify users that they have received a new message or calendar event.
Text notifications can be sent to any device that supports SMTP, for
example, email addresses, cell phones, and text pagers.
To enable Connection to send text notifications by using SMTP, your
Connection server must be configured to relay messages through a smart
host. If Connection is configured to deliver text notifications but has
not been configured to relay messages to a smart host, the notification
attempt fails and the notification is put in the Connection SMTP Server
badmail folder.
When a Connection user receives a new message, Connection can send a
text notification to an email address. (When you set up this type of
notification, you can configure Connection to include a link to the
Cisco PCA in the body of the email message. On the Edit Notification
Device page for the user, check the Include a Link to Cisco PCA in
Message Text check box.)
No changes.
Digital Networking uses SMTP to transmit both directory information and messages between Cisco Unity Connection servers.
If any pair of servers in the Digital Network cannot transmit and
receive SMTP messages directly (for example, because a firewall
separates the servers), you must configure these servers to route these
messages through an SMTP smart host.
Cisco Unity Connection can use the Short Message Peer-to-Peer (SMPP)
protocol to send message notifications in the Short Message Service
(SMS) format to cell phones and other SMS-compatible devices when users
receive new messages.
An advantage of using SMS is that the user device often receives message
notifications much faster than when using SMTP.
A Cisco Unity Connection conversation is a set of prerecorded prompts
and menu options that callers hear as they interact with Connection by
phone. It is organized into two main conversations-one for outside
callers and one for Connection users. This chapter details the
Connection conversation global settings.
No changes.
This section contains parameters for Cisco Unity Connection to relay messages for users to another SMTP server.
No changes.
Each Cisco Unity Connection server (or cluster) has a maximum number of
users that it can serve. When the messaging needs of your organization
require more than one Connection server or cluster, or you need a way to
combine multiple Connection directories or to internetwork Connection
with Cisco Unity, you can link Connection servers or clusters together
to form sites, and link a Connection site with another Connection site
or with a Cisco Unity site to form a Cisco Voicemail Organization.
The following Intrasite Networking settings are configured:
No changes.
This section contains the advanced global settings for phone system integrations.
No changes.
Cisco Unity Connection is automatically set to gather and store data from which you can generate reports.
This section contains the advanced global settings for the reports generation:
-
Milliseconds Between Data Collection Cycles: Set by default to 30
minutes (1,800,000 milliseconds). This setting controls the amount of
time Connection waits between cycles of gathering report data.
- Days to Keep Data in Reports Database: Set by default to 90
days. Note that even if you specify more than this number of days in the
time range for the report you are generating, the number of days of
data is limited by what you set here.
- Maximum Records in Report Output: Set by default to 25,000
records. The maximum value allowed for this field is 30,000 records. If
the report you want to generate exceeds the maximum number of records
allowed, you can generate the report in pieces, for example by reducing
the date range or number of user accounts included in each iteration.
Note : The Maximum Records in Report Output setting for the User Message
Activity Report has been restricted to 15,000 records-rather than the
default of 25,000 records-because of the size of the report.
- Minimum Records Needed to Display Progress Indicator: Set by
default to 2,500 records. The maximum value allowed for this field is
10,000 records. The purpose of the progress indicator is to warn you if
the report you request is large and likely to take a long time to
complete. In Connection, reports are generated from within a browser,
and the browser session must be kept open while the report is being
generated. Depending on the size of the database, and the type of report
being generated, a report can take a long time to generate; meanwhile,
you are unable to use the browser, and must keep the Connection
Administration session open.
No changes.
This section contains the administrator global settings for the Connection Cluster:
No changes.
This section contains the advanced global settings for Telephone Record and Play (TRAP):
No changes.
This section contains the advanced global settings for the disk:
No changes.
The Cisco Personal Communications Assistant (PCA) is a website that
provides users with access to the Cisco Unity web tools, which allow
users to manage messages and personal preferences in Connection. The web
tools available in the Cisco PCA include:
- Cisco Unity Assistant
- Cisco Unity Inbox
- Cisco Unity Personal Call Transfer Rules
This section contains the advanced global settings for the Cisco Personal Communications Assistant (PCA):
No changes.
As an alternative to checking messages by phone or using the Cisco Unity
Inbox or an IMAP client, users can retrieve voice messages by using an
RSS reader. In order to use the RSS Feed feature, users must be assigned
to a class of service that is configured to allow them to use the Cisco
Unity Inbox and RSS Feeds, and the Connection Inbox RSS Feed service
must be activated and started.
RSS (most commonly translated as "Really Simple Syndication" but
sometimes "Rich Site Summary") is a family of web feed formats used to
publish frequently updated works (such as blog entries, news headlines,
audio, and video) in a standardized format.
This section contains the advanced global settings for RSS:
No changes.
This section contains the advanced global settings for the Connection Cluster:
No changes.
Cisco Unity Connection can integrate with the Cisco Fax Server so that
users can do the following while on the phone or while using the Cisco
Unity Inbox.
This section contains the advanced global settings for the fax:
No changes.
This section contains the advanced global settings for External Services:
No changes.
Applications that use the Cisco Unity Connection Messaging Interface
(CUMI) can access secure message recordings (audio attachments) for
playback.
These settings affect all client applications that use CUMI to access
messages. This includes several Connection client applications, such as
the Cisco Unity Connection Web Inbox and Cisco ViewMail for Microsoft
Outlook.
The following CUMI API settings are configured:
No changes.
The phone system pages in Cisco Unity Connection Administration identify
the phone systems that Cisco Unity Connection integrates with. In
Connection Administration, a phone system has one or more port groups,
which in turn have voice messaging ports.
| Phone Systems |
| Name | Details |
PhoneSystem
| Detected Change ID | 12 | | Detected Change | Updated record 'PhoneSystem' | | Detected Object | Phone System | | Detected Date (UTC) | 2/29/2024 12:04:28 PM | | Detected Date (Local) | 2/29/2024 1:04:28 PM | | Child ID | 13 | | | Phone System | | Default TRAP Phone System | Y | | Message Waiting Indicators | | Send Message Counts | N | | Use Same Port for Enabling and Disabling MWIs | N | | Force All MWIs Off for this Phone System | N | | Call Loop Detection by Using DTMF | | Enable for Supervised Transfers | N | | Enable for Forwarded Message Notification Calls (by Using DTMF) | N | | DTMF Tone To Use | A | | Guard Time (msecs) | 2500 | | Call Loop Detection by Using Extension | | Enable for Forwarded Message Notification Calls (by Using Extension) | Y | | Phone View Settings | | Enable Phone View | N | | CTI Phone Access User Name | | | Outgoing Call Restrictions | | Restrictions | Enable outgoing calls | | AXL Servers | | AXL Servers |
< No records found > | | AXL Server Settings | | Username | | | Cisco Unified Communications Manager Version | | | Enable End User PIN Synchronization for Primary AXL Server | N | | Ignore Certificate Errors | Y | | Phone System Associations | | Phone System Associations | | User Alias | MWI | Notification Device | | agent1 | 1 MWIs Referenced | 4 Notification Devices Referenced | | operator | 1 MWIs Referenced | 4 Notification Devices Referenced | | undeliverablemessagesmailbox | 1 MWIs Referenced | 4 Notification Devices Referenced | aps01
| Detected Change ID | 13 | | Detected Change | Added record with key 'aps01' | | Detected Object | Phone System | | Detected Date (UTC) | 2/29/2024 12:04:28 PM | | Detected Date (Local) | 2/29/2024 1:04:28 PM | | Parent ID | 12 | | 1 MWIs Referenced | 4 Notification Devices Referenced |
|
|
Port groups hold most of the integration configuration settings and some
or all of the voice messaging ports for Cisco Unity Connection.
While most phone system integrations need only
one port group, multiple port groups may be needed in the following
circumstances:
- For integrations with phone systems through PIMG/TIMG units, each
PIMG/TIMG unit is connected to one port group with the applicable voice
messaging ports. For example, a system that uses five PIMG units
requires five port groups, one port group for each PIMG unit.
-
For integrations with other phone systems, an additional port group with
its own voice messaging ports may be used for testing a new
configuration or for troubleshooting.
Voice messaging ports provide the connections for calls between Cisco
Unity Connection and the phone system. You can add voice messaging ports
after the phone system has been created. The number of voice messaging
ports that you add cannot bring the total number of voice messaging
ports for all port groups to more than the maximum number of voice
messaging ports that are enabled by the Connection license files.
The voice messaging ports let Cisco Unity Connection receive calls (for
example, to record a message) and let Connection make calls (for example
to send message notifications or to set MWIs).
Each voice messaging port can belong to only one port group. Port
groups, when there are several, each have their own voice messaging
ports. The total voice messaging ports belonging to all port groups must
not exceed the maximum number of voice messaging ports that are enabled
by the Connection license files.
Speech Connect uses voice-enabled directory handlers that allow both
employees and outside callers to say the name of an employee and
instantly get connected, without having to navigate an audio-text tree,
and without knowing the extension of the employee. For easy access for
employees, you can configure a Speech Connect speed dial on user phones.
No changes.
When multiple phone systems are integrated with Cisco Unity Connection,
you may want to set up a phone system trunk so that calls on one phone
system can be transferred to extensions on another phone system. Phone
system trunks are accessed by dialing extra digits (for example, dialing
9) before dialing the extension.
The SIP certificate is used only by SIP trunk integrations with Cisco
Unified CM 7.0 and later, and is required for authentication of the
Cisco Unity Connection voice messaging ports.
The following SIP certificates are present:
The SIP security profile is used only by SIP trunk integrations with
Cisco Unified CM 7.0 and later, and is required for authentication of
the Cisco Unity Connection voice messaging ports.
The following SIP security profiles are present:
No changes.
