Ports Are Too Busy to Make Notification Calls Promptly

When the ports that make notification calls are also set to perform other operations, they may be too busy to make notification calls promptly. You can improve notification performance by dedicating a smaller number of ports to making notification calls exclusively.

Systems that handle a large volume of calls may require additional ports to improve notification performance.

To Review Port Configuration for Message Notification

Step 1 In the Cisco Unity Administrator, go to the System > Ports page.

Step 2 Review the existing port configuration and determine whether one or more ports can be set to dial out for message notification only.

Not Enough Ports Are Set for Message Notification Only

When a small number of ports are set to make notification calls and Cisco Unity takes a lot of messages, the notification ports may not always be able to dial out promptly.

If the percentage of ports used for dialing out for message notification exceeds 70 percent usage during peak periods, review the existing port configuration and determine whether more ports can be set to dial out for message notification only.

If the percentage of ports used for dialing out for message notification does not exceed 70 percent usage during peak periods, the number of notification ports is adequate. Contact the Cisco Technical Assistance Center (TAC) to resolve the problem.

To Determine Whether the Number of Message Notification Ports Is Adequate

Step 7 (Optional) To generate a report, on the Port Availability tab, click Run Report.

Step 8 If the percentage of ports used exceeds 70 percent usage during peak periods, go to the System > Ports page in the Cisco Unity Administrator, then continue with Step 9.

If the percentage of ports used does not exceed 70 percent usage during peak periods, the number of message waiting indication ports is adequate.

Step 9 Review the existing port configuration and determine whether more ports can be set to dial out for message notification only.

Confirming That the Phone System Sends Calls to the Ports Set to Answer Calls

If the phone system is programmed to send calls to a port on Cisco Unity that is not configured to answer calls, Cisco Unity will not answer the call.

To Confirm That Calls Are Being Sent to the Correct Cisco Unity Ports

Step 1 In the Cisco Unity Administrator, go to the System > Ports page.

Step 2 Note which ports are set to answer calls.

Step 3 In the phone system programming, confirm that calls are being sent only to those ports that are set to answer calls. Change the phone system programming if necessary.

Step 4 If you make a change to the phone system programming, restart the Cisco Unity server.

Cisco Unity Partner Exchange Server Is Down or Is Disconnected

Messages recorded while the partner Exchange server is down or disconnected are stored in the Unity Messaging Repository (UMR) until the server is brought back up. Because calls for message notification are not made until a message is actually delivered to a subscriber, the delay experienced between the time a message is recorded and its delivery and the sending of the notification is dependant on the length of time that the primary Exchange server was down or disconnected.

Message Notification Setup Is Inadequate

When a subscriber complains that notification calls are not being received when expected, the problem may be with the notification settings.

To Determine Whether Notification Setup Is Adequate

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Message Notification page for the subscriber.

Step 2 In the Device list, click the correct notification device.

Step 3 Confirm with the subscriber that the notification device is applicable to the needs of the subscriber. If the subscriber has selected a very busy phone for Cisco Unity to call, ask if there is an alternate phone or pager to use for message notification.

Step 4 Confirm with the subscriber that the notification schedule is consistent with the days and times that the subscriber is available to receive notification calls.

Notification Attempts Are Missed

A subscriber who is frequently away from or busy using a notification device may repeatedly miss notification attempts. To the subscriber, it appears that Cisco Unity has delayed message notification.

To Resolve Missed Notification Attempts

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Message Notification page for the subscriber.

Step 2 In the Device list, click the correct notification device.

Step 3 In the Notification Options section, check the Restart Notification Each Time a New Message Arrives check box.

Step 4 In the Try Again How Many Times fields, increase the numbers so that Cisco Unity makes more notification calls when the device does not answer or is busy.

Step 5 In the How Many Minutes To Wait Between Tries fields, decrease the numbers so that Cisco Unity makes notification calls more often when the device does not answer or is busy.

Step 6 In the If Notification Fails field, select Pager as a backup device if the subscriber has a pager available for use. Also enter settings and a schedule for the pager.

Step 7 Suggest that the subscriber set up an answering machine for the notification phone, so that notification calls are received even when the subscriber is unavailable.

When Cisco Unity is set to call a phone that has an answering machine, confirm with the subscriber that the answering machine greeting is short enough so that the machine starts recording before the notification message is repeated.

Repeat Notification Option Is Misunderstood

Setting Cisco Unity to repeat notification at a particular interval when there are still new messages can be useful for subscribers who receive a lot of messages but who do not want immediate notification. However, when a subscriber chooses not to have Cisco Unity restart notification each time a new message arrives, setting a long interval between repeat notification calls may lead the subscriber to believe that Cisco Unity is delaying notification.

To Resolve a Repeat Notification Problem

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Message Notification page for the subscriber.

Step 2 In the Device list, click the correct notification device.

Step 3 In the Notification Options section, in the field next to the Repeat Notification If There Are Still New Messages After This Many Minutes check box, set a shorter interval, such as 15 minutes.

MAPI Logon Delay After Restarting the Cisco Unity Server

Restarting the Cisco Unity server may result in delayed message notification until MAPI logon to all subscriber mailboxes has been completed. Depending on the size of the subscriber database, it could take several hours to complete the MAPI logon.

Message Notification Is Not Working at All for a Subscriber in Cisco Unity 8.x

SMS Notifications Are Not Working at All

A possible cause for this problem is that the information in the System Type field on the SMSC Configuration page in the Cisco Unity Administrator is not capitalized correctly. To confirm that this is the cause, check the Notifier logs. When SMS traces are turned on, the log files indicate that "SmppBindTransmitter failed."

If this is the case, check the SMPP configuration detail provided to you by the SMS provider for the correct capitalization. Then, enter the information in the System Type field in the Cisco Unity Administrator exactly as specified by the SMS provider.

Only Certain Types of Messages Are Set to Trigger Notification

Cisco Unity can be set so that a subscriber is notified only of certain types of messages. For example, if subscriber notification is set up only for fax and urgent voice messages, email and regular voice messages will not cause Cisco Unity to make a notification call.

To Change the Message Types That Trigger Notification Calls

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Message Notification page for the subscriber.

Step 2 In the Device list, click the correct notification device.

Step 3 In the Notify Subscriber Of section, verify the selected message types with the subscriber.

Access Code for an External Line Is Missing

To place an external call, a subscriber usually must dial an access code to get an external line (for example, 9). When the phone system requires an access code, an external message notification phone number set in Cisco Unity must include the access code.

In addition, some phone systems may require a brief pause between dialing the access code and being connected to an external line.

To Verify an Access Code

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Message Notification page for the subscriber.

Step 2 In the Device list, click the correct notification device.

Step 3 In the Phone Number box, confirm that the correct access code is included before the phone number. If the phone system requires a pause, enter two commas between the access code and the phone number (for example, 9,,5551234).

Notification Number Is Incorrect or the Device Is Disabled or Not Working

The subscriber may have entered a wrong phone number for Cisco Unity to call. Also, when a subscriber disables notification to a phone or pager, Cisco Unity will not attempt a notification call to the device regardless of the other notification settings.

To Verify a Device Phone Number and Status

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Message Notification page for the subscriber.

Step 2 In the Device list, click the correct notification device.

Step 3 In the Phone Number box, confirm that the correct access code and phone number are entered for the device.

Step 4 In the Status section, confirm that the device is set to Enabled.

To Test a Notification Device

Step 1 If the notification device is a cellular phone or pager, ask the subscriber to have it available for the test.

If the notification device is a home phone or another phone away from the office, ask the subscriber to have someone available to answer the phone during the test.

Step 4 On Phone 1, dial the notification number set in Cisco Unity for the device.

If the pager is activated or the phone rings, you have confirmed that Cisco Unity can call the device.

If the pager is not activated or the phone does not ring, there may be a problem with the device. Consult the documentation from the device manufacturer, or ask the subscriber to obtain a different notification device and repeat the test.

Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Message Notification page for the subscriber.

Step 2 Under Notification Options, in the Switch field, note the phone system that is assigned to the device.

Step 3 Go to the System > Ports page for the phone system that is assigned to the device.

Step 4 Confirm that the phone system assigned to the notification device has at least one port designated for message notification. Correct the port settings if necessary.

Step 5 If you made a change, click the Save icon.

Message Notification Announcements Appear in Subscriber Mailboxes

If Cisco Unity does not reject forwarded message notification announcements, they will fill subscriber mailboxes. Enable the rejection of forwarded message notification calls by doing the following procedure.