Table Of Contents
System Settings
Overview: System Settings
Configuration Settings
Software Versions
Recording Settings
Audio Codecs
Contacts
Phone Languages Settings
GUI Languages Settings
Schedule Settings
Holiday Settings
Licensing Status
Authentication Settings
Voice Messaging Port Settings
SMPP Provider Settings
Integration Settings
Cisco CallManager Integration
SIP Integration
Circuit-Switched Phone System Integration Via PIMG (Intel PBX-IP Media Gateway) Units
Circuit-Switched Phone System Integration Via Voice Cards
Remapping Extension Numbers
About the Remapping Feature
Setting Up Cisco Unity to Remap Extension Numbers
Syntax and Examples
System Settings
Overview: System Settings
Before Cisco Unity can be set up to handle calls and messages, some basic system settings must be entered.
See the following sections in this chapter for more information:
•
Configuration Settings—This section provides information about the configuration settings.
•Software Versions—This section details where to find version numbers for Cisco Unity and other software components.
•Recording Settings—This section provides information about recording settings.
•Contacts—This section details where you can enter the names and phone numbers of the people responsible for maintaining or administering the Cisco Unity server.
•Phone Languages Settings—This section provides information about the language played for subscribers and unidentified callers.
•GUI Languages Settings—This section provides information about the language in which the Cisco Unity Administrator and Cisco Personal Communications Assistant are displayed.
•Schedule Settings—This section explains how to set up system schedules.
•Holiday Settings—This section explains how to set up holidays to work with Cisco Unity schedules.
•Licensing Status—This section provides information about user and feature licenses.
•Authentication Settings—This section provides information about logon, password, and account lockout policy settings for subscribers accessing Cisco Unity web clients.
•Voice Messaging Port Settings—This section provides information about setting up voice ports.
•SMPP Provider Settings—This section explains how to set up the SMPP providers that Cisco Unity will use when sending SMS messages to subscriber wireless devices.
•Integration Settings—This section provides information on the phone system integration settings that are displayed.
•Remapping Extension Numbers—This section describes how to remap the calling numbers and forwarding numbers of calls that Cisco Unity handles to the extensions of your choice.
Configuration Settings
Configuration settings contain general Cisco Unity settings such as the default schedule, system security, and the cleanup interval for log files, as well as information about the Cisco Unity server.
Caution If you have a Cisco Unity failover system, configuration settings (except schedules and holidays) are not replicated between the primary and secondary servers. You must change values manually on both servers.
Use Table 26-1 to learn more about configuration settings. See the following for additional information on these related topics:
•Offering subscribers the Cisco Unity Inbox—See the "Setting Up the Cisco Personal Communications Assistant" section on page 6-5.
•Setting up enhanced phone security—Refer to the "Setting Up Enhanced Phone Security" section in the "Authentication for Cisco Unity Applications" of the Cisco Unity Security Guide. (The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.)
•Identifying the default system schedule—See the "Schedule Settings" section.
•Log-based Cisco Unity reports—See the "About Report Data" section on page 24-2.
Table 26-1 System > Configuration > Settings Page
Field
|
Considerations
|
Default Schedule
|
Select the default schedule, which is used for all Cisco Unity operations unless specifically changed for a call handler, subscriber account, or call routing table.
Default: Weekdays.
|
Use 24-Hour Time Format for Conversation and Schedules conversation
|
Check this check box to use a 24-hour time format for all Cisco Unity operations. For example, 1:00 p.m. is shown as 13:00 in the Cisco Unity Administrator, and subscribers hear 13:00 when listening to the timestamps for their messages over the phone.
When this check box is left unchecked, Cisco Unity uses the 12-hour clock format as the system default.
|
Enable Spelled Name Search
|
Check this check box to allow subscribers to address messages to other subscribers by spelling the subscriber first or last name over the phone. In addition, when this check box is checked, subscribers who are editing private lists can search for subscribers by spelling the subscriber name over the phone. Addressing by name requires lettered keypads on subscriber phones.
Note that checking this check box does not prevent subscribers from searching for subscribers by entering subscriber extensions over the phone when editing private lists or addressing messages. In the subscriber conversation, subscribers can switch between addressing by name and addressing by extension by pressing the # key twice.
When this check box is unchecked, subscribers can search for subscribers over the phone only by entering subscriber extensions. In addition, the option to address by spelled name cannot be used on the Subscribers > Conversation page and in the Cisco Unity Assistant. (Note that in version 3.1 and earlier, the Cisco Unity Assistant was known as the ActiveAssistant, or AA.)
Default: Check box checked.
|
Play The "Still Searching..." Prompt
|
Indicate how many times Cisco Unity should play a "Still searching..." prompt when searching for subscriber messages. Cisco Unity searches for two seconds and then plays the "Still searching..." prompt. Once Cisco Unity has played the prompt the number of times that you specify, it searches for messages for two more seconds and then cancels the search.
This setting does not enable the Message Locator feature for subscribers. You specify whether subscribers can use the Message Locator feature on the Features page for subscriber templates and individual subscribers.
Default: Two times. (Cisco Unity searches for messages for approximately 10 seconds before canceling the search and prompting the subscriber to either enter new search criteria or play any search results.)
|
Responding to Phone Menus
|
For each caller, you can specify the following:
•How long Cisco Unity waits for subscriber to press a first key after playing a menu. This setting is also known as the "First Digit Timeout." The range of valid entries is 500 to 10,000 milliseconds. Default: 5000 milliseconds.
•How long Cisco Unity waits for additional key presses after subscriber has pressed a key. This setting is also known as the "Interdigit Timeout." The range of valid entries is 1000 to 10,000 milliseconds. Default: 3000 milliseconds.
•How many times Cisco Unity repeats a menu if the subscriber has not responded to a menu. The range of valid entries is 0 to 10. Default: 1.
All three of the above settings control the phone menus for the following "conversations," which are heard by outside callers and subscribers (as applicable): subscriber Main menu, After Message menu, Ask To Hold menu, Hold Status, and System Transfers. The timeouts for the conversations played to validate subscriber IDs and passwords (Sign-In conversations) are also controlled by the first two settings above. For security reasons, however, you cannot change the number of times Cisco Unity repeats the menus for the Sign-In conversations.
To adjust the time that Cisco Unity waits for a second key before acting upon the first (known as the "double-key timeout"), use the Advanced Settings tool. To learn more, refer to the Advanced Settings tool Help (in the Unity Settings list, click Conversation—Set "Double Key Press" Time). The Advanced Settings tool is available in Tools Depot.
|
RSA Two Factor
|
Check this check box to enable enhanced phone security, which uses RSA two-factor user authentication. To use enhanced phone security, an ACE/Server must be installed and configured for your system. Additionally, you must create a new class of service (COS) or modify an existing COS for the subscribers who are using enhanced phone security.
To disable enhanced phone security, uncheck this check box, and then change every affected COS to use regular phone security. Otherwise, subscribers who are members of an enhanced phone security COS will not be allowed to log on to Cisco Unity.
Default: Check box not checked.
|
Subscribers Are Identified as Message Senders Only If They Log On
|
Check this check box to disable identified subscriber messaging (ISM) systemwide. ISM affects what subscribers hear when they call other subscribers from their primary or alternate extensions and are forwarded to the greetings of the subscribers they call. If they then leave a message, ISM affects what the called subscriber hears and can do when listening to the message.
When ISM is enabled, Cisco Unity recognizes that the calling extension is associated with a subscriber and accordingly plays the internal greeting of the called subscriber. Additionally, when the called subscriber later listens to the message, Cisco Unity plays the recorded voice name of the subscriber who left the message and allows the called subscriber to record a reply.
This field is applicable only when the phone system provides caller and called party information to Cisco Unity. It is a systemwide setting that is not configurable for an individual subscriber or subscriber template.
Regardless of whether ISM is enabled, when a subscriber logs on to the Cisco Unity conversation before sending a message ("Press 2 to send a message"), Cisco Unity correctly identifies the message as being from the subscriber.
Default: Check box not checked.
|
Cisco Personal Communications Assistant (PCA)
|
Enter the URL for the Cisco Personal Communications Assistant (PCA) so that it is automatically included as a link in the body of the e-mail message that is sent to subscribers who have Cisco Unity Inbox message notifications set up. (Subscribers use the Cisco PCA to access their Cisco Unity Inboxes.)
Note that the Media Master, which is displayed on many Cisco PCA pages, is not available across a firewall that blocks DCOM communications.
You can set up Cisco Unity Inbox message notification on the message notification pages for subscribers or subscriber templates.
|
Cleanup Interval for Logger Data Files in Days
|
Indicate how often data files should be deleted. Cisco Unity waits the specified number of days before automatically deleting the files. Log-based Cisco Unity reports are based on the data stored in these files.
Default: Seven days.
|
Cleanup Interval for Logger Diagnostic Files in Days
|
Indicate how often diagnostic files should be deleted. Cisco Unity waits the specified number of days before automatically deleting the files.
Default: Seven days.
|
Cleanup Interval for Report Files in Days
|
Indicate how often report files should be deleted. Cisco Unity waits the specified number of days before automatically deleting the files.
Note that you specify how long Cisco Unity stores the data used in log-based reports in the Cleanup Interval for Logger Data Files in Days field.
Default: Seven days.
|
Replicate Cisco Unity Directory Objects
|
Choose Changed Objects to manually synchronize changes from the Active Directory or Exchange 5.5 Directory into the Cisco Unity SQL database. For example, changing the distribution list by which the directory handler is scoped requires a synchronization.
Synchronization takes place automatically when the Cisco Unity directory services (AvDSAD and AvDSGlobalCatalog) poll the directory for any changes to be applied to the SQL database, which usually occurs within 15 to 20 minutes after the directory handler scope change is made in the Cisco Unity Administrator. However, you can also initiate the synchronization immediately by choosing Changed Objects.
Choose All Objects only if Cisco Unity has been down for a considerable length of time.
|
Cisco Unity Computer Settings
|
Display only. This setting shows the name of the Cisco Unity server and the Windows Domain name.
|
Fax Settings
|
This setting shows the name of the fax domain.
|
Disk Usage
|
Display only. This setting shows, in megabytes, the total, used, and free disk space on the Cisco Unity server.
|
Display Fields Required for Cisco Unity Bridge Networking on Subscribers Profile Page
(used only when the Bridge Networking option is configured for messaging with Octel systems)
|
Check this check box to display the Unity Node Serial Number and Legacy Mailbox ID fields on the Subscribers Profile and Add Subscriber pages.
The Unity Node Serial Number and Legacy Mailbox ID are required for all Cisco Unity subscribers who will be messaging with subscribers on an Octel system via the Cisco Unity Bridge. Without these numbers, a Cisco Unity subscriber cannot send messages to nor receive messages from Octel subscribers.
Default: Check box not checked.
|
Substitute Recipient
|
Select the subscriber or public distribution list that will receive messages left for a call handler or interview handler, if the subscriber originally configured for this purpose is at any time deleted in the Cisco Unity Administrator.
By default, the Example Administrator is configured as the Substitute Recipient. We recommend that you review this setting periodically, and update it if you wish to use a different substitute, so that these entities can be properly reassigned any time a subscriber is deleted.
|
Substitute Owner
|
Select the subscriber or public distribution list to which Cisco Unity will assign ownership of a distribution list, call handler, directory handler, or interview handler, if the subscriber originally configured for this purpose is at any time deleted in the Cisco Unity Administrator. Select a recipient type from the list, then click Select Subscriber or Select Distribution List.
By default, the Example Administrator is configured as the Substitute Owner. We recommend that you review this setting periodically, and update it if you wish to use a different substitute, so that these entities can be properly reassigned any time a subscriber is deleted.
|
Substitute After Message Call Handler
|
Select the call handler that will be associated with the After Message Action setting (on a subscriber account, subscriber template, or call handler) or with the After Interview Action setting (on an interview handler), if the subscriber originally configured for this purpose is at any time deleted in the Cisco Unity Administrator.
By default, the Goodbye call handler is configured as the Substitute After Message Call Handler. We recommend that you review this setting periodically, and update it if you wish to use a different substitute, so that these entities can be properly reassigned any time a subscriber is deleted.
|
Substitute Exit Call Handler
|
Select the call handler that will be associated with the If Caller Exits setting on a directory handler, if the subscriber originally configured for this purpose is at any time deleted in the Cisco Unity Administrator.
By default, the Goodbye call handler is configured as the Substitute Exit Call Handler. We recommend that you review this setting periodically, and update it if you wish to use a different substitute, so that these entities can be properly reassigned any time a subscriber is deleted.
|
Software Versions
The System > Configuration > Software Versions page displays the Cisco Unity serial and build numbers, and the version numbers for several Cisco Unity components and for the Microsoft Windows 2000 Server. If you ever contact the Cisco Technical Assistance Center (TAC), you may need to refer to this information.
Recording Settings
The Recordings page contains settings for recording time limits and for silence thresholds (the amount of silence before Cisco Unity assumes the caller is no longer on the line) before, during, and after recordings.
Caution Modifying the settings on the System > Configuration > Recordings page changes the registry on the Cisco Unity server. For Cisco Unity failover, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated.
Audio Codecs
Cisco Unity supports the audio codecs listed in Table 26-2.
Table 26-2 Supported Audio Codecs
Audio Codec
|
Approximate File Size, 1-Minute Message
|
Quality Rating
|
G.711 Mu-Law and A-Law
|
480 KB
|
Excellent
|
G726 32 Kbps
|
240 KB
|
Fine
|
Dialogic OKI ADPCM 8Khz
|
240 KB
|
Fine
|
Dialogic OKI ADPCM 6Khz
|
180 KB
|
Fine
|
GSM 6.10
|
98 KB
|
Fine
|
G.729a
|
60 KB
|
Good
|
Note GSM 6.10 is supported for playback on a Pocket PC, and is a higher quality recording format than MP3.
For information on choosing and implementing audio codecs, refer to the White Paper: Audio Codecs and Cisco Unity, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_white_papers_list.html.
Use the following table to learn more about recording settings.
Table 26-3 System > Configuration > Recordings Page
Field
|
Considerations
|
Allowed Time for Recording in Milliseconds
|
Select the number of milliseconds for the DTMF clip length. This setting indicates how much to truncate the end of a recording when a message is terminated with a touchtone.
Default: 170 milliseconds.
|
Allowed Time for Short Recording in Seconds
|
Select the number of seconds that Cisco Unity uses as a cutoff for short and long recordings. Recordings shorter than this number are considered to be a short recording; recordings longer than this number are considered to be a long recording.
Default: Ten seconds.
|
Allow How Much Silence Before Time Out in Seconds
|
Select the number of seconds after which Cisco Unity will end the message, greeting, or recorded name if the subscriber or caller has not begun speaking. A value lower than two or three seconds may not give the subscriber or caller enough time to begin speaking.
Default: Five seconds.
|
Discard Any Recording Less Than in Seconds
|
Select the minimum length of recordings, in seconds, for messages or greetings. Note that this setting is not applied to recorded names.
Default: One second.
|
Short Recording (Short Recording Trail Limit or Less)
|
Select the number of seconds of silence that Cisco Unity uses to detect the end of a short recording. When Cisco Unity detects a pause equal to the number of seconds specified, Cisco Unity assumes that the speaker has finished recording the message, greeting, or recorded name. Callers are more likely to pause longer during long messages, so you may want to set a smaller pause length for short recordings than for long recordings. Cisco Unity uses the Allowed Time for Short Recording in Seconds setting to determine whether a recording is short or long.
Default: Two seconds.
|
Long Recording (Over Short Recording Trail Limit)
|
Select the number of seconds of silence that Cisco Unity uses to detect the end of a long recording. When Cisco Unity detects a pause equal to the number of seconds specified, Cisco Unity assumes that the speaker has finished recording the message, greeting, or recorded name. Callers are more likely to pause longer during long messages, so you may want to set a greater pause length for long recordings than for short recordings. Cisco Unity uses the Allowed Time for Short Recording in Seconds setting to determine whether a recording is short or long.
Default: Three seconds.
|
Contacts
The System > Configuration > Contacts page is where you enter the names and phone numbers of the people responsible for maintaining or administering the Cisco Unity server. This information might be useful to a technician who is accessing Cisco Unity from off-site.
Phone Languages Settings
Phone languages are the languages in which Cisco Unity can play system prompts to subscribers and callers. You specify a default phone language and other systemwide phone language settings, as well as the default Text to Speech (TTS) language, which is the language that subscribers hear when their e-mail is read to them over the phone. Note that to use TTS languages, your organization must have TTS e-mail and the applicable languages installed. See the "Setting Up Languages" section on page 8-1 for more information about using multiple languages.
You can customize the language settings for specific Cisco Unity components such as subscriber accounts, routing rules, call handlers, interview handlers, and directory handlers. See the "Specifying Phone Languages" section on page 8-3 for information about customizing language settings for individual Cisco Unity components.
Caution If you have a Cisco Unity failover system, phone languages settings are not replicated between the primary and secondary servers. You must change values manually on both servers.
Use the following table to learn more about phone languages settings.
Table 26-4 System > Configuration > Phone Languages Page
Field
|
Considerations
|
License Counts - Total
|
Display only. This setting shows the total number of phone language licenses for your installation, which determines how many phone languages can be loaded at one time. Note that the number of phone language licenses does not limit the number of phone languages actually installed on the Cisco Unity server.
|
License Counts - Loaded
|
Display only. This setting shows the number of languages in the Loaded list.
|
License Counts - Unused
|
Display only. This setting shows the number of unused phone language licenses. Note that this number might not be the same as the number of languages in the Available list.
|
Available
|
This list displays the languages that have been installed on the Cisco Unity server but that are not currently loaded.
When you load a language by moving it from the Available list to the Loaded list, the Loaded and Unused License Count fields are adjusted accordingly. You can move languages to the Loaded list only if the Unused License Count is greater than zero.
|
Loaded
|
This list displays the languages that can be selected for use by the subscriber conversation and various Cisco Unity components such as call handlers.
When you unload a language by moving it from the Loaded list to the Available list, the Loaded and Unused License Count fields are adjusted accordingly. Any call handlers or other Cisco Unity components that were using the unloaded language will now be reset to use the default phone language.
|
Default Phone Language
|
Select the default language in which system prompts are played to subscribers and callers. Only the languages shown in the Loaded list can be chosen as the default language.
|
Default Text to Speech Language
|
Select the default language that subscribers hear when having their e-mail read to them over the phone. This is typically the same language that you selected in the Default Phone Language field with the following exceptions:
•If you selected Australian or New Zealand English as your phone language, select either United States English or UK English as your default Text to Speech language.
•There is no applicable Text to Speech language available for Czech or Korean.
|
GUI Languages Settings
The settings on the GUI Languages page determine the languages in which the Cisco Unity Administrator pages can be displayed. You specify a default GUI language and other systemwide GUI language settings.
To change the GUI language used in the Cisco Unity Administrator or the Cisco Personal Communications Assistant, select a language in the browser. (Subscribers use the Cisco PCA website to access the Cisco Unity Assistant and the Cisco Unity Inbox. Note that in version 3.1 and earlier, the Cisco Unity Assistant was known as the ActiveAssistant, or AA; the Cisco Unity Inbox was known as the Visual Messaging Interface, or VMI.)
For the Cisco Unity Administrator, note that the language selected in the browser must be one of the languages in the Loaded list on the GUI Languages page. If the language that you select in the browser is not among the loaded languages, Cisco Unity uses the default GUI language. For the Cisco PCA, the language selected in the browser must be one of the languages that the Cisco PCA offers.
Caution If you have a Cisco Unity failover system, GUI languages settings are not replicated between the primary and secondary servers. You must change values manually on both servers.
Use the following table to learn more about GUI languages settings.
Table 26-5 System > Configuration > GUI Languages Page
Field
|
Considerations
|
License Counts - Total
|
Display only. This setting shows the total number of GUI language licenses for your installation, which determines how many GUI languages can be loaded at one time. Note that the number of GUI language licenses does not limit the number of GUI languages actually installed on the Cisco Unity server.
|
License Counts - Loaded
|
Display only. This setting shows the number of languages in the Loaded list.
|
License Counts - Unused
|
Display only. This setting shows the number of unused GUI language licenses. Note that this number might not be the same as the number of languages in the Available list.
|
Available
|
This displays the languages that have been installed on the Cisco Unity server but that are not currently loaded.
When you move a language from the Available list to the Loaded list, the Loaded and Unused License Count fields are adjusted accordingly. You can move languages to the Loaded list only if the Unused License Count is greater than zero.
|
Loaded
|
This displays the languages that can be used in the browser display of the Cisco Unity Administrator.
When you unload a language by moving it from the Loaded list to the Available list, the Loaded and Unused License Count fields are adjusted accordingly.
|
Default GUI Language
|
Select the default GUI language from the Loaded list. Cisco Unity uses the default GUI language only if the language selected in the browser is not among the loaded GUI languages.
|
Schedule Settings
Schedules are one of the variables that Cisco Unity uses to manage calls. The standard and closed subscriber and call handler greetings play according to the days and times that you specify in a schedule.
Cisco Unity offers two predefined schedules: All Hours - All Days, and Weekdays, both of which can be modified. In addition, you can create up to 64 schedules for your organization to accommodate the standard working hours of different groups of employees. You can use either of the predefined schedules, or a new schedule that you create, as the default schedule for Cisco Unity. The default schedule is used for all call handlers, subscriber templates, and call routing tables, unless you specify a different schedule for each call handler, subscriber account, or call routing table to follow.
For each schedule that you create or modify, you identify the hours and days that make up the standard and closed hours, and whether the schedule changes for holidays:
Standard hours
|
The hours and days that make up the normal business hours, when the organization is open. Standard hours can include multiple time ranges and different time ranges on different days. (For example, standard hours for an organization might be Monday through Friday from 8 a.m. to 12 p.m. and 1 p.m. to 5 p.m., to accommodate a lunch break, and Saturday from 9 a.m. to 1 p.m.)
|
Closed hours
|
The hours and days not identified as standard hours are considered nonbusiness hours, when the organization is closed.
|
Holidays
|
The time range defined on the System > Holidays page when the organization is closed. See the "Holiday Settings" section for information about identifying holidays.
|
To Create a New Schedule
Step 1 In the Cisco Unity Administrator, go to the System > Schedules page.
Step 2 Click the Add icon.
Step 3 In the Add a Schedule dialog box, enter information as applicable in the Name field.
Step 4 Select New Schedule or Based on Existing Schedule. If you select Based on Existing Schedule, select the applicable schedule in the Based On field.
Step 5 Click the Add button.
Step 6 Check the Observe Holidays check box, if applicable.
Step 7 Click boxes on the schedule grid until all open (standard) half hours are white and all closed half hours are gray. Note that you can use the Copy Day's Schedule field and >> functions to avoid clicking the same blocks for more than one day.
Step 8 Click the Save icon.
Step 9 To use this new schedule as the Cisco Unity default schedule, do the following "To Specify the Default Schedule" procedure.
To Specify the Default Schedule
Step 1 In the Cisco Unity Administrator, go to the System > Schedules page, and click Change Default Schedule from any schedule page.
Note that when you click the link, you leave the schedule page, and move to the System > Configuration > Settings page.
Step 2 In the Default Schedule field, click the schedule you want to use as the default for new call handlers, subscriber templates, and call routing tables.
Step 3 Check the Use 24-Hour Time Format for Conversation and Schedules check box to use a 24-hour time format for all schedules, if desired.
Step 4 Click the Save icon.
To Modify an Existing Schedule
Step 1 In the Cisco Unity Administrator, go to the System > Schedules page.
Step 2 Click the Find icon.
Step 3 Double-click the schedule that you want to modify.
Step 4 Change settings as applicable, and then click the Save icon.
Step 5 To use this new schedule as the system default schedule, do the "To Specify the Default Schedule" procedure.
Use the following table to learn more about schedule settings.
Table 26-6 System > Schedules Page
Field
|
Considerations
|
Observe Holidays
|
Check this check box to have Cisco Unity play closed (off-hour) greetings and to observe closed transfer rules on the dates defined on the System > Holidays page.
|
Click Individual Blocks to Set Hours
|
Click the blocks in the grid to change from closed to open (standard) hours. Click a block again to undo your change. Note that you can set open (standard) and closed hours for one day, then use the Copy Day's Schedule box to copy the settings to other days.
|
Copy Day's Schedule
|
Select a day to copy from the list, then select which days to copy the schedule settings to. Use the Copy Day's Schedule field and >> functions to avoid clicking the same blocks for more than one day.
|
Holiday Settings
When a Holiday setting is in effect, Cisco Unity plays closed greetings and observes closed transfer rules. You can set up several years of holidays at a time, and you can copy the holidays from one year to the next, adjusting dates as necessary. Because many holidays occur on different dates each year, confirm that the holiday schedule remains accurate annually.
To Identify Days as Holidays
Step 1 In the Cisco Unity Administrator, go to the System > Holidays page.
Step 2 Click the Add icon.
Step 3 In the Add a Holiday dialog box, select the month, day, and year of the holiday.
Step 4 Click the Add button.
To Modify a Holiday
Step 1 In the Cisco Unity Administrator, go to the System > Holidays page.
Step 2 Click the date of the holiday listed for the applicable year.
Step 3 In the Edit Holiday For field, change settings as applicable, and then click the Save icon.
Use the following table to learn more about holiday settings.
Table 26-7 System > Holidays Page
Field
|
Considerations
|
Edit Holiday For
|
Enter the applicable year, month, and day for the holiday that you want to modify.
|
Licensing Status
When your organization purchased Cisco Unity, licenses were assigned according to the number of users and the number of voice messaging ports. In addition, your organization may have purchased licenses for optional features. You can view the number of licenses purchased, and the number that are used and unused, from the System > Licensing page. If you need additional licenses, contact your reseller.
Authentication Settings
Authentication settings dictate the logon and lockout policy that applies when subscribers access Cisco Unity by using the Cisco Personal Communications Assistant (PCA). If the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, the policy that you specify on the System > Authentication page also applies when subscribers use the Cisco Unity Administrator or the Status Monitor to access Cisco Unity.
Changes to authentication settings affect all Cisco Unity subscribers. You cannot change authentication settings for individual subscriber accounts, though you can lock out individual subscriber accounts to prevent subscribers from using the Cisco PCA, Cisco Unity Administrator, or Status Monitor to access Cisco Unity. (For details, see the "Subscriber Account Settings" section on page 14-6.)
Related Documentation
•To understand how authentication works with Cisco Unity web applications, refer to the "Authentication for Cisco Unity Applications" chapter of the Cisco Unity Security Guide.
•Consider that when subscribers log on to the Cisco PCA, their credentials are sent across the network to Cisco Unity in clear text. The same is true if the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method. For increased security, we recommend that you set up Cisco Unity to use the Secure Sockets Layer (SSL) protocol. Refer to the "Using SSL to Secure Client/Server Connections" chapter in the Cisco Unity Security Guide. The guide is available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_maintenance_guides_list.html.
Use the following table to learn more about authentication settings. Note that authentication settings represent a different logon and lockout policy from the one that applies when subscribers access Cisco Unity by phone. For information on setting up the account policy that applies when subscribers access Cisco Unity by phone, see the "Account Policy Settings" chapter.
Table 26-8 System > Authentication Page
Field
|
Considerations
|
Remember Logons for __ Days
|
If desired, check this check box and enter the number of days that Cisco Unity will store logon information. When you check this check box, Cisco Personal Communications Assistant (PCA) logons are stored as encrypted cookies on the subscriber workstation. In addition, the Log On page for the Cisco PCAoffers subscribers the following options:
•Remember User Name
•Remember Domain
When subscribers specify that Cisco Unity remember their user name or domain, subscribers will not have to enter them the next time that they log on to the Cisco PCA. Instead, the fields are automatically populated in the Log On page.
Allowing subscribers to specify whether Cisco Unity remembers their credentials may reduce support desk requests for the information. Alternatively, for security reasons, you may not want the Log On page to offer subscribers the above options. If this is the case, uncheck this check box to prevent the options from appearing on the Log On page, and require that subscribers enter their user name and domain each time that they log on to the Cisco PCA.
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
Default: Blank.
|
Remember Passwords for __ Days
|
If desired, you can check this check box and enter the number of days that Cisco Unity will store password information. When you check this check box, Cisco Personal Communications Assistant (PCA) passwords are stored as encrypted cookies on the subscriber workstation. In addition, the Log On page for the Cisco PCA offers subscribers the Remember Passwords option.
When subscribers specify that Cisco Unity remember their password, they will not have to enter it the next time that they log on to the Cisco PCA. Instead, the password field is automatically populated in the Log On page.
Allowing subscribers to specify whether Cisco Unity remembers their password may reduce support desk requests for resetting forgotten passwords. Alternatively, for security reasons, you may not want the Log On page to offer subscribers the option. If this is the case, uncheck this check box to prevent the Remember Password option from appearing on the Log On page, and require that subscribers enter their password each time that they log on to the Cisco PCA.
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
Default: Blank.
|
Session Key Duration
|
This field indicates the length of time that the browser can be left unattended before Cisco Unity automatically logs the subscriber off the Cisco Personal Communications Assistant (PCA).
The value in IIS dictates the browser session duration, but you can use this field to change the value for the Session Timeout field in IIS. When you change the value for the Session Timeout field directly in IIS, however, the changes you make are not reflected here.
Regardless of whether you update the session duration here or directly in IIS, the new timeout value applies the next new browser session.
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
Default: 20 minutes.
|
Disallow Blank Passwords
|
Check this check box so that subscribers are prohibited from logging on to the Cisco Personal Communications Assistant (PCA) without entering a password in the Log On page, even if the Windows account policy allows blank passwords.
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
|
Lock Out Accounts
|
Check this check box if you want to specify an account lockout policy for the subscribers who use the Cisco Personal Communications Assistant (PCA).
When this check box is checked, enter the applicable values in the following fields:
•Accounts Are Locked Out For __ Minutes
•Accounts Will Lock Out After __ Logon Attempts
•Reset Account Lockout Counters After __ Minutes
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
Default: Check box checked.
|
Accounts Are Locked Out For __ Minutes
|
Enter the number of minutes that Cisco Unity will prevent subscribers from accessing Cisco Unity by using the Cisco Personal Communications Assistant (PCA).
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
This option is unavailable when the Lock Out Accounts check box is unchecked.
Default: 30 minutes.
|
Accounts Will Lock Out After __ Logon Attempts
|
Enter the number of failed logon attempts after which subscribers cannot access Cisco Unity by using the Cisco Personal Communications Assistant (PCA).
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
This option is unavailable when the Lock Out Accounts check box is unchecked.
Default: Five attempts.
|
Reset Account Lockout Counters After __ Minutes
|
Enter the number of minutes after which Cisco Unity will clear the count of failed logon attempts to the Cisco Personal Communications Assistant (PCA), unless the failed logon limit is already reached and the account is locked.
If IIS is configured so that the Cisco Unity Administrator and the Status Monitor use the Anonymous authentication method, this setting also applies to subscribers logging on to the Cisco Unity Administrator and to the Status Monitor.
This option is unavailable when the Lock Out Accounts check box is unchecked.
Default: 30 minutes.
|
Voice Messaging Port Settings
Each voice messaging port on the Cisco Unity server can be set to perform one or more of these functions:
•Answer incoming calls from unidentified callers and from subscribers dialing in to Cisco Unity.
•Dial out to notify subscribers of voice, fax, and e-mail messages.
•Dial out to allow system administrators and subscribers to use the phone as a recording and playback device in Cisco Unity applications. (The phone is offered as a recording and playback device in the Media Master, which appears on pages of the Cisco Unity Administrator, Cisco Unity Assistant, and Cisco Unity Inbox, and in ViewMail.)
You can adjust the maximum number of rings that Cisco Unity waits for when making these dial-out calls. Refer to the Advanced Settings tool Help (in the Unity Settings list, click Administration—Set Maximum Number of Rings to Wait for TRAP Calls). The Advanced Settings tool is available in Tools Depot.
(Note that in version 3.1 and earlier, the Cisco Unity Assistant was known as the ActiveAssistant, or AA; the Cisco Unity Inbox was known as the Visual Messaging Interface, or VMI.)
•Dial out to turn message waiting indicators (MWIs) on and off.
•Dial out to deliver outbound AMIS messages (some systems may not have this feature).
•(Only integrations of Cisco CallManager 4.1 and later with Cisco Unity 4.0(5) and later) Enable authentication and encryption.
•(Only integrations of Cisco CallManager 4.1 and later with Cisco Unity 4.0(5) and later) Enable encryption of the media stream.
The number of voice messaging ports set for answering and dialing out depends on many factors, such as:
•The total number of voice messaging ports available.
•The number of subscribers who will use message notification and how often they will receive notifications.
•For circuit-switched phone systems that integrate via voice cards, whether your integration is serial or analog (analog integrations use voice messaging ports to turn MWIs on and off, while serial integrations do not). Circuit-switched phone systems that integrate via Intel NetStructure PBX-IP Media Gateway units (PIMG units) use voice messaging ports to turn MWIs on and off.
•Whether your organization communicates primarily through e-mail or voice mail.
Each voice messaging port can be set to perform more than one function (for example, to answer calls and to dial out message notifications). When the voice messaging ports perform more than one function and are very active (for example, answering many calls), the other functions may be delayed until the voice messaging port is free (for example, MWIs cannot be turned on until there are fewer calls to answer). For best performance, use the first voice messaging ports only for incoming calls and the last ports only for dialing out. This eliminates the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity takes the port off-hook to dial out.
In a typical installation, the installer sets up voice messaging ports for Cisco Unity, but you can modify them on the Ports page. Before changing port settings, however, monitor the voice messaging port activity. Refer to the Port Usage Analyzer, available in Tools Depot.
Note If you have a Cisco Unity failover system, voice messaging port settings are not replicated between the primary and secondary servers. You must change voice messaging port settings on both servers.
Use the following table to learn more about port settings.
Table 26-9 System > Ports Page
Field
|
Considerations
|
Extension
|
Enter the extension for the port as assigned on the phone system.
|
Enabled
|
Check this check box to enable the port. The port is enabled during normal operation.
Uncheck this check box to disable the port. When the port is disabled, calls to the port get a ringing tone but are not answered. Typically, the port is disabled only by the installer during testing.
|
Answer Calls
|
Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from subscribers.
|
Message Notification
|
Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports, which typically are those with the highest port numbers for the phone system.
|
Dialout MWI
(not used by serial or SMDI integrations)
|
Check this check box to designate the port for turning MWIs on and off. Assign Dialout MWI to the least busy ports, which typically are those with the highest port numbers for the phone system.
|
AMIS Delivery
(available with the AMIS licensed feature only)
|
Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.
This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.
Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.
|
TRAP Connection
|
Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports, which typically are those with the highest port numbers for the phone system.
|
Security Mode
(available only with Cisco Unity 4.0(5) and later when integrated with Cisco CallManager 4.1 and later)
|
Click the applicable security mode:
•Non-secure—The integrity and privacy of call-signaling messages will not be ensured because call-signaling messages will be sent as clear (unencrypted) text and will be connected to Cisco CallManager through a non-authenticated port rather than an authenticated TLS port. In addition, the media stream cannot be encrypted, even when the Media Encryption check box is checked.
•Authenticated—The integrity of call-signaling messages will be ensured because they will be connected to Cisco CallManager through an authenticated TLS port. However, the privacy of call-signaling messages will not be ensured because they will be sent as clear (unencrypted) text. In addition, the media stream can be encrypted when the Media Encryption check box is checked.
•Encrypted—The integrity and privacy of call-signaling messages will be ensured on this port because they will be connected to Cisco CallManager through an authenticated TLS port, and the call-signaling messages will be encrypted. In addition, the media stream can be encrypted when the Media Encryption check box is checked.
|
Media Encryption
(available only with Cisco Unity 4.0(5) and later when integrated with Cisco CallManager 4.1 and later)
|
Check this check box to encrypt the media stream that is sent through this port.
Note Both end points must be registered in authenticated or encrypted mode. When one end point is set for authenticated mode and the other is set for encrypted mode, the media stream will be encrypted. However, if one end point is set for non-secure mode and the other is set for encrypted mode, the media stream will not be encrypted. Also, if an intervening device (such as a transcoder or gateway) is not enabled for encryption, the media stream will not be encrypted.
|
SMPP Provider Settings
Before you can offer SMS (SMPP) message notifications to subscribers, you must set up Cisco Unity so that it can communicate with the SMS Center (SMSC) that is affiliated with the mobile messaging service provider(s) that your organization has contracted with to provide SMS messaging services.
When you have an account, the service provider sends you the information necessary to configure an application like Cisco Unity—known as an External Short Message Entity (ESME)—to use the SMPP protocol to send text messages to the SMPP server at the SMSC. Then you enter the information on the System > SMPP Provider page.
Use the procedures in this section to create and modify SMPP providers. You can create as many SMPP providers as you need. The providers that you add are available to all subscribers to use for SMS (SMPP) message notifications unless you specify otherwise. Consider that the more SMS (SMPP) message notifications that Cisco Unity sends to subscriber devices, the higher the costs to your organization (depending on the account, service providers typically charge for each SMS message or group of messages). For this reason, you may want to restrict the use of this feature to a group of subscribers by assigning owner(s) to the SMPP provider(s) that you create.
Note When the Cisco Unity server is set up behind a firewall, configure the TCP port that is used by the SMPP server to connect to Cisco Unity to allow incoming and outgoing communication between Cisco Unity and the SMPP server.
For a general overview of how SMS (SMPP) message notifications work, see the "SMS (SMPP) Message Notifications" section on page 6-15. As applicable, see the "Subscriber Template Message Notification Settings" section on page 10-25 or the "Subscriber Message Notification Settings" section on page 14-29 to enable SMS (SMPP) message notifications. Subscribers can also set up SMS (SMPP) message notifications for themselves in the Cisco Unity Assistant.
To Create an SMPP Provider
Step 1 In the Cisco Unity Administrator, on the System > SMPP Provider page, click the Add icon.
Step 2 In the Add SMPP Provider dialog box, in the Provider Name field, enter the name that you want to represent the service provider in Cisco Unity applications.
The name you enter here will be listed on the Provider SMPP lists displayed on the SMS (SMPP) message notification pages for subscribers and subscriber templates in the Cisco Unity Administrator, as well as in the Cisco Unity Assistant.
Step 3 Do one of the following:
•To allow all subscribers to use this provider, skip to Step 4.
•To restrict provider use to a particular subscriber, click the Assign button. Then, select the applicable subscriber from the list. (Note that once you save the provider, the owner is not displayed in the Cisco Unity Administrator. For this reason, consider naming a provider accordingly when you assign one to a particular subscriber.)
Step 4 For the remainder of the page, enter information as applicable in the fields provided. Depending on the SMSC used by your service provider(s), you may not need to complete every field. To determine which fields are required, refer to the documentation on setting up a messaging server to communicate with the SMSC that your service provider sent you. You can also use Table 26-10 to learn more about SMPP provider settings.
Tip For multilingual systems, consider adding an SMPP provider for each language that subscribers use and then name and configure the providers accordingly. (Use the Data Coding field to specify language preference.)
Step 5 Click the Save icon.
To Modify an SMPP Provider
Step 1 In the Cisco Unity Administrator, go to any System > SMPP Provider page.
Step 2 Click the Find icon.
Step 3 Double-click the SMPP Provider that you want to modify. (Note that you cannot modify provider ownership.)
Step 4 Change settings as applicable, and then click the Save icon.
Use Table 26-10 to learn more about SMPP provider settings. Depending on the SMSC used by your service provider(s), you may not need to complete every field on the System > SMPP Provider Settings page. To determine which fields are required, refer to the documentation on setting up a messaging server to communicate with an SMSC that your service provider sent you. For technical details about the SMPP protocol, review the SMPP Protocol Specification for the applicable SMPP version you configure Cisco Unity to use. The document is available on the Internet.
Table 26-10 System > SMPP Provider Settings Page
Field
|
Considerations
|
Provider Name
|
Enter the name that will represent the service provider in Cisco Unity applications. The name you enter here will be listed on the Provider SMPP lists displayed on the SMS (SMPP) Message Notification pages for templates and individual subscribers in the Cisco Unity Administrator, as well as in the Cisco Unity Assistant.
For multilingual systems, consider adding an SMPP provider for each language that subscribers use and then name and configure the providers accordingly. (Use the Data Coding field to specify language preference.)
|
SMPP Version
|
Indicate the version of the SMPP protocol that the SMPP server uses to communicate with ESMEs like Cisco Unity.
This field corresponds to the interface_version in the SMPP Protocol Specification.
|
SMPP Server Host Name
|
Enter the IP address or host name of the SMPP server at the SMSC.
|
SMPP Server Port Number
|
Enter the port used by the SMPP server to connect to an ESME like Cisco Unity.
Note When the Cisco Unity server is set up behind a firewall, you must configure the TCP port to allow incoming and outgoing communication between Cisco Unity and the SMPP server.
|
User Name
|
Enter the name or system ID associated with the account that your organization has with the SMSC as provided by your service provider. Cisco Unity uses the information in this field to identify itself when communicating with the SMPP server at the SMSC.
This field corresponds to the system_id in the SMPP Protocol Specification.
|
Password
|
Enter the password associated with the account that your organization has with the SMSC as provided by your service provider. Cisco Unity uses the information in this field to identify itself when communicating with the SMPP server at the SMSC.
This field corresponds to the password in the SMPP Protocol Specification.
|
Address Range
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The SMPP server uses the address range to communicate with the Cisco Unity server. You may need to enter a set of addresses or a single address.
This field corresponds to the address_range in the SMPP Protocol Specification.
|
System Type
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field categorizes the type of ESME that is communicating with the SMPP server at the SMSC. For example, an application like Cisco Unity may be categorized as a "VMS" (voice mail system).
Caution This field is case-sensitive. Check the SMPP configuration documentation from your service provider for the correct capitalization, then enter it here exactly as specified.
This field corresponds to the system_type in the SMPP Protocol Specification.
|
ESME Type of Number (TON)
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field defines the type of number (TON) that subscribers can use when specifying the To and From fields for SMS (SMPP) message notification in the Cisco Unity Administrator and the Cisco Unity Assistant.
Select the applicable value from the list to specify:
•0—Unknown
•1—International
•2—National
•3—Network Specific
•4—Subscriber Number
•5—Alphanumeric
•6—Abbreviated
This field corresponds to the addr_ton in the SMPP Protocol Specification. The addr_ton and addr_npi values tell the SMSC how to interpret the address found in the address_range field.
|
ESME Numbering Plan Identity (NPI)
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field defines the numeric plan indicator that subscribers can use when specifying the To and From fields for SMS (SMPP) message notification in the Cisco Unity Administrator and the Cisco Unity Assistant.
Select the applicable value from the list to specify:
•0—Unknown
•1—ISDN (E163/E164)
•3—Data (X.121)
•4—Telex (F.69)
•6—Land Mobile (E.212)
•8—National
•9—Private
•10—ERMES
•14—Internet (IP)
•18—WAP Client ID
This field corresponds to the addr_npi in the SMPP Protocol Specification. The addr_ton and addr_npi values tell the SMSC how to interpret the address found in the address_range field.
|
Source TON
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field defines the type of number (TON) that subscribers can use when specifying the To and From fields for SMS (SMPP) message notification in the Cisco Unity Administrator and the Cisco Unity Assistant.
Select the applicable value from the list to specify:
•0—Unknown
•1—International
•2—National
•3—Network Specific
•4—Subscriber Number
•5—Alphanumeric
•6—Abbreviated
This field corresponds to the source_addr_ton in the SMPP Protocol Specification. The source_addr_ton and source_addr_npi values tell the SMSC how to interpret the address found in the source_addr (From) field.
|
Source NPI
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field defines the numeric plan indicator that subscribers can use when specifying the To and From fields for SMS (SMPP) message notification in the Cisco Unity Administrator and the Cisco Unity Assistant.
Select the applicable value from the list to specify:
•0—Unknown
•1—ISDN (E163/E164)
•3—Data (X.121)
•4—Telex (F.69)
•6—Land Mobile (E.212)
•8—National
•9—Private
•10—ERMES
•14—Internet (IP)
•18—WAP Client ID
This field corresponds to the sourece_addr_npi in the SMPP Protocol Specification. The source_addr_ton and source_addr_npi values tell the SMSC how to interpret the address found in the source_addr (From) field.
|
Destination TON
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field defines the type of number (TON) that subscribers can use when specifying the To and From fields for SMS (SMPP) message notification in the Cisco Unity Administrator and the Cisco Unity Assistant.
Select the applicable value from the list to specify:
•0—Unknown
•1—International
•2—National
•3—Network Specific
•4—Subscriber Number
•5—Alphanumeric
•6—Abbreviated
This field corresponds to the dest_addr_ton in the SMPP Protocol Specification. The dest_addr_ton and dest_addr_npi values tell the SMSC how to interpret the address found in the destination_addr (To) field.
|
Destination NPI
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field defines the numeric plan indicator that subscribers can use when specifying the To and From fields for SMS (SMPP) message notification in the Cisco Unity Administrator and the Cisco Unity Assistant.
Select the applicable value from the list to specify:
•0—Unknown
•1—ISDN (E163/E164)
•3—Data (X.121)
•4—Telex (F.69)
•6—Land Mobile (E.212)
•8—National
•9—Private
•10—ERMES
•14—Internet (IP)
•18—WAP Client ID
This field corresponds to the dest_addr_npi in the SMPP Protocol Specification. dest_addr_ton and dest_addr_npi values tell the SMSC how to interpret the address found in the destination_addr (To) field.
|
Service Type
(optional)
|
If applicable, enter the value provided to you by your service provider. (If your provider did not specify a value, leave the field blank.) The information in this field allows an ESME like Cisco Unity to do the following:
•Use enhanced messaging services such as the replace previous notification option.
•Control the teleservice used on the air interface.
The following generic service types are defined:
•(blank)
•CMT Cellular Messaging
•CPT Cellular Paging
•VMN Voice Mail Notification
•VMA Voice Mail Alerting
•WAP Wireless Application Protocol
•USSD Unstructured Supplementary Services Data
Other applicable values are service provider-specific.
|
Data Coding
(optional)
|
If applicable, select the character set that you want each SMS message converted to when the messages are sent to the SMS device. (If your provider did not specify a value, leave the field blank.) For multilingual systems, consider creating a separate SMPP provider for each character set that you want to offer to subscribers.
Select the applicable value from the list to specify:
•0—GSM 3.38 Default Alphabet: 7 bit
•1—ASCII: 7 bit (Windows code page 20127 or 20105)
•3—Latin 1: 8 bit (Windows code page 28591 or 1252)
•5—Japanese: 16 bit* (Windows code page 20932 or 932)
•6—Cyrillic: 8 bit (Windows code page 28595 or 1251)
•7—Latin/Hebrew: 8 bit (Windows code page 28598 or 1255)
•8—USC-2: 16 bit (Unicode)
•14—Korean: 16 bit* (Windows code page 1361 or 949)
* Multi-bit character set: most characters are 16 bit; some are 8 bit.
|
Replace Previous Notification if Possible
(optional)
|
Check this box to have Cisco Unity request that the SMSC or SMS device will replace one or more previously submitted message notifications with the latest one. Depending on whether the subscriber device is turned on or off, message notifications are replaced as follows:
•When the device is on, Cisco Unity submits message notifications to the SMSC, which forwards them to the device. If the source address, destination address, and protocol ID fields in a new message notification match the same fields in a previous one, the device replaces the previous one with the latest.
•When the device is off or otherwise disconnected from the GSM network, Cisco Unity submits message notifications to the SMSC. The SMSC replaces any message notifications that are still pending delivery with the latest one if the source address, destination address, and service type match the same fields in the new message notification.
In both scenarios, the subscriber receives only the latest message notification.
Note Service providers may not support some or all of the above functionality. For example, some providers may support replacing previous notifications only when the device is either turned on or off. Other providers may not support replacing previous notifications at all.
This field corresponds to the replace_if_present_flag and the protocol_id fields in the SMPP Protocol Specification.
|
Integration Settings
The integration settings are specified during installation in the Cisco Unity Telephony Integration Manager (UTIM), which configures Cisco Unity to work with the phone system. When the integration is set up, you should not need to change the integration settings, but you can review them on the Integration page or revise them in UTIM.
Note If you have a Cisco Unity failover system, changes to the integration settings must be made in UTIM on each server individually. Integration settings are not replicated between the primary and secondary servers.
To view the integration settings for the phone system, in the left pane of the Cisco Unity Administrator, click the name of the phone system integration that you entered in UTIM.
Use the applicable tables to learn more about integration settings:
•Cisco CallManager Integration
•SIP Integration
•Circuit-Switched Phone System Integration Via PIMG (Intel PBX-IP Media Gateway) Units
•Circuit-Switched Phone System Integration Via Voice Cards
Cisco CallManager Integration
Table 26-11 System > Integration > Cisco CallManager Page
Field
|
Considerations
|
Integration Type
|
Display only. This field displays the name of the Cisco CallManager integration entered in UTIM.
|
Switch File
|
Display only. This field displays the Cisco Unity phone configuration file (also called switch.ini file) that is being used to initialize the integration.
|
Primary Server
|
Display only. This field displays the IP address of the primary Cisco CallManager server. This address was entered in UTIM.
|
Secondary Server
|
Display only. This field displays the IP address of the secondary Cisco CallManager server, if applicable. This address was entered in UTIM.
|
Device Name Prefix
|
Display only. This field displays the prefix Cisco CallManager adds to the device name for the voice messaging ports. This prefix was entered in UTIM and must match the prefix used by Cisco CallManager.
|
MWI On Extension
|
Display only. This field displays the extension that Cisco CallManager uses to turn MWIs on. This extension was entered in UTIM.
|
MWI Off Extension
|
Display only. This field displays the extension that Cisco CallManager uses to turn MWIs off. This extension was entered in UTIM.
|
Reconnect After CallManager Failback
|
Display only. This field displays whether Cisco Unity will automatically reconnect to the primary Cisco CallManager server after Cisco CallManager failover has been corrected. The setting Yes indicates that automatic reconnection is enabled. This value was set in UTIM.
|
SIP Integration
Table 26-12 System > Integration > SIP Page
Field
|
Considerations
|
Integration Type
|
Display only. This field displays the name of SIP integration entered in UTIM.
|
Switch File
|
Display only. This field displays the Cisco Unity phone configuration file (also called switch.ini file) that is being used to initialize the integration.
|
Primary Server
|
Display only. This field displays the IP address of the primary SIP proxy server. This address was entered in UTIM.
|
Secondary Server
|
Display only. This field displays the IP address of the secondary SIP proxy server, if applicable. This address was entered in UTIM.
|
Cisco Unity SIP Port
|
Display only. This field displays the IP port on Cisco Unity that callers and the SIP proxy server use to connect to voice mail. This port was entered in UTIM.
|
SIP Contact Line Name
|
Display only. This field displays the voice messaging line name that subscribers use to contact Cisco Unity and that Cisco Unity uses to register with the SIP proxy server. This line name was entered in UTIM.
|
Preferred Codec
|
Display only. This field displays the codec that Cisco Unity first attempts to use on outgoing calls. This codec was selected in UTIM.
|
Preferred Transport Protocol
|
Display only. This field displays the preferred transport protocol that Cisco Unity uses. This value was set in UTIM.
|
Authenticate with SIP Proxy Server
|
Display only. This field displays whether Cisco Unity authenticates with the SIP proxy server. The setting Yes indicates that authentication is enabled. This value was set in UTIM.
|
Authentication Name
|
Display only. This field displays the name that the SIP proxy server uses for authentication. This name was entered in UTIM.
|
Circuit-Switched Phone System Integration Via PIMG (Intel PBX-IP Media Gateway) Units
Table 26-13 System > Integration > PIMG Page
Field
|
Considerations
|
Integration Type
|
Display only. This field displays the name of PIMG (Intel PBX IP Media Gateway) integration entered in UTIM.
|
Switch File
|
Display only. This field displays the Cisco Unity phone configuration file (also called switch.ini file) that is being used to initialize the integration.
|
PIMG SIP Port
|
Display only. This field displays The IP port of the PIMG unit that Cisco Unity uses for SIP communication. This port was entered in UTIM.
|
Cisco Unity SIP Port
|
Display only. This field displays the IP port on Cisco Unity that callers and the PIMG unit use to connect to voice mail. This port was entered in UTIM.
|
SIP Contact Line Name
|
Display only. This field displays the voice messaging line name that subscribers use to contact Cisco Unity and that Cisco Unity uses to register with the SIP proxy server. This line name was entered in UTIM.
|
Preferred Codec
|
Display only. This field displays the codec that Cisco Unity first attempts to use on outgoing calls. This codec was selected in UTIM.
|
Preferred Transport Protocol
|
Display only. This field displays the preferred transport protocol that Cisco Unity uses. This value was set in UTIM.
|
Authenticate with SIP Proxy Server
|
Display only. This field displays whether Cisco Unity authenticates with the PIMG unit. The setting Yes indicates that authentication is enabled. This value was set in UTIM.
|
Authentication Name
|
Display only. This field displays the name that the PIMG unit uses for authentication. This name was entered in UTIM.
|
Circuit-Switched Phone System Integration Via Voice Cards
Table 26-14 System > Integration > Circuit-Switched Via Voice Cards Page
Field
|
Considerations
|
Integration Type
|
Display only. This field displays the name of integration entered in UTIM.
|
Switch File
|
Display only. This field displays the Cisco Unity phone configuration file (also called switch.ini file) that is being used to initialize the integration.
|
PBX Manufacturer
|
Display only. This field displays the phone system manufacturer selected in UTIM.
|
PBX Model
|
Display only. This field displays the phone system model selected in UTIM.
|
PBX Software Version
|
Display only. This field displays the phone system software version selected in UTIM.
|
Remapping Extension Numbers
This section provides the following information on remapping extension numbers:
•About the Remapping Feature
•Setting Up Cisco Unity to Remap Extension Numbers
•Syntax and Examples
About the Remapping Feature
The extension remapping feature lets you convert to the extensions of your choice the calling numbers and forwarding numbers of calls handled by Cisco Unity. This feature is useful, for example, when the phone system cannot map multiple extension numbers on a subscriber phone to a single Inbox.
Remapping can change one or both of the following extension numbers in a call:
•Calling number (the number from which a call originates). For example, Cisco Unity changes the calling number of calls so that the caller ID appears to be a different extension than the one that actually placed the call.
•Forwarding number (the number that a call is going to). For example, unanswered calls to all line extensions on a single phone can be forwarded to the Inbox of a single subscriber; or unanswered calls to phones not assigned to subscribers can be forwarded to the Inbox of a supervisor.
Setting Up Cisco Unity to Remap Extension Numbers
This section includes a procedure for enabling the remapping feature. You can create multiple files in either or both of two directories:
•In the Calling directory, one or more .exm files remap caller ID numbers.
•In the Forwarding directory, one or more .exm files remap numbers that Cisco Unity provides with calls it forwards.
When you create remapping instructions in an .exm file in a directory, Cisco Unity remaps only the type of extension number that the directory is named for. For example, if you want to remap only the extensions that Cisco Unity provides with calls it forwards, you enter the instructions in an .exm file in the Forwarding directory; in this circumstance, the Calling directory needs no .exm file.
In each directory, you can have several .exm files with different file names but with the same .exm extension. This helps you to organize the remapping information. For example, you could create two files in a directory: Ports_1-12.exm and Ports_13-24.exm. Cisco Unity reads all files that have the .exm extension in these directories.
To Remap Extension Numbers
Step 1 On the Cisco Unity server, browse to the CommServer\IntLib\ExtensionMapping directory. In this directory is the file Sample.txt and two more directories: Calling and Forwarding.
Step 2 To remap calling numbers, go to the Calling directory.
Step 3 In a text editor application, create a new .exm file, or open a currently existing .exm file.
For an example, open the file Sample.txt in the CommServer\IntLib\ExtensionMapping directory.
Caution When opening an .exm file in a text editor, do not associate the file with the text editor by checking the Always Use This Program To Open check box in the Open With dialog box. Otherwise, the .exm file will be saved as a .txt file and the remapping feature will ignore the file.
Step 4 Enter [Range] and press Return to create a section for indicating which voice messaging ports will be monitored for remapping calls.
An .exm file can have only one [Range] section.
Step 5 Enter ports= followed by the numbers of the voice messaging ports, separated by commas. Ranges are designated by a hyphen (-) without spaces. To monitor all voice messaging ports, enter ports=* on this line. Then press Return.
For example, you might enter:
ports=1,2,5-34
Step 6 To create a section for the remapping rules, press Return, enter [Number Mappings], and then press Return.
An .exm file can have only one [Number Mappings] section.
Step 7 Enter one remapping rule on the line, and then press Return.
See the remapping rule examples in the following "Syntax and Examples" section. The rule format is:
<original number>, <new number>
The rules cannot include spaces between digits. However, the numbers must be separated by a comma and a single space. Wildcard characters cannot appear at the beginning of a number.
Step 8 For all remaining rules, repeat Step 7.
Step 9 Save and close the .exm file.
Step 10 To remap forwarding numbers, browse to the directory CommServer\IntLib\ExtensionMapping\Forwarding.
Step 11 Repeat Step 3 through Step 9 to remap forwarding numbers.
Step 12 For extension remapping to take effect, restart the Cisco Unity software.
Syntax and Examples
Table 26-15 shows the wildcard characters you can use in the .exm files.
Table 26-15 Wildcard Characters
Wildcard
|
Result
|
*
|
Matches zero or more digits.
|
?
|
Matches exactly one digit. Use ? as a placeholder for a single digit.
|
Table 26-16 gives examples for the syntax and results of rules in the .exm files.
Table 26-16 Syntax Examples
Rule
|
Original Number
|
New Number
|
2189, 1189
3189, 1189
4189, 1189
|
2189
3189
4189
|
1189
1189
1189
|
2???, 1???
|
2189
2291
|
1189
1291
|
3???, 1???
|
3189
3291
|
1189
1291
|
8???, 61???
|
8000
8765
|
61000
61765
|
123*, 44*
|
12300
12385
|
4400
4485
|
Cisco Unity executes rules in the order they appear in the .exm file. For example, the .exm file might contain the following rules:
1234, 1189
3189, 1189
4189, 1189
123?, 8891
The extension 1234 would be remapped to 1189 while extensions 1233 and 1235 would be remapped to 8891, because the rule mapping 1234 appears earlier.
An .exm file might contain the following:
[Range]
ports=1,2,5-34
[Number Mappings]
2189, 1189
3189, 1189
4189, 1189
8???, 9???
Feedback
