Troubleshooting Guide for Cisco Unity Connection Release 15 - Troubleshooting Notification Devices

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/troubleshooting/guide/b_15cuctsg/b_15cuctsg_chapter_010000.html

Published

2025-08-22

Updated

unknown

Accessed

2026-10-02

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Notification devices added in Unity Connection Administration are active at all hours by default, so users may be notified at unexpected times until a schedule is set in the Cisco PCA. in context
• The On Notification Failure > Send To failover option used to cover missed phone/pager notification attempts is not available for SMTP notification devices. in context
• A maximum of three custom HTML-type notification devices can be created per user through the Bulk Administration Tool. in context
• For HTML notifications not arriving, Cisco's checklist is: the HTML notification device is enabled on the user, its email address is present and correct, an SMTP smart host is configured, and the Connection SMTP Server and Connection Notifier services are running. in context
• When a Unity Connection notification device does not work at all, the first checks are that the device's Enabled check box is selected and that its notification schedule is active at the time notification should occur. in context
• A notification device triggers only for the message types selected in its Notification Rule Events; for example a device set to trigger on urgent voice messages only does not fire for regular voice messages. in context
• When notification is slow for many users, Cisco says to run the Port Activity Report (Serviceability > Tools > Reports) and, if notification port usage exceeds 70 percent at peak, configure additional ports for message notification; below 70 percent, contact Cisco TAC. in context
• Notification device schedules are changed in the Cisco Personal Communications Assistant, not in Unity Connection Administration; Administration reaches it via the device page's Edit Notification Device Details link. An inactive schedule is the documented cause of intermittent notification. in context
• In SMS notification traces, 'SmppConnect failed' indicates Unity Connection could not connect to the SMPP provider, 'SmppBindTransmitter failed' indicates an authentication failure with the provider, and 'SmppSubmitSm failed' indicates message submission to the provider failed. in context
• For SMS notification failures Cisco directs administrators to verify the provider settings under System Settings > Advanced > SMPP Providers against the provider's specification and to enable the SMS Device micro trace at level 30. in context
• When SMTP notifications fail for multiple users, Cisco says to confirm a smart host is set at System Settings > SMTP Configuration > Smart Host, that the smart host accepts messages from the Unity Connection server, and that the Connection SMTP Server and Connection Notifier services are running. in context
• For SMTP notification delivery problems the notification-devices chapter recommends SMTP micro trace levels 10, 11, 12 and 13, with level 18 adding network message detail. in context

Cite this source record

APA

WarmTransfer. (2025, August 22). Troubleshooting Guide for Cisco Unity Connection Release 15 - Troubleshooting Notification Devices. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cuc15-tsg-notification-devices

BibTeX

@misc{warmtransfer-cisco-cuc15-tsg-notification-devices,
  title  = {Troubleshooting Guide for Cisco Unity Connection Release 15 - Troubleshooting Notification Devices},
  author = {{WarmTransfer}},
  year   = {2025},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-cuc15-tsg-notification-devices},
  note   = {Cisco Systems, accessed 2026-10-02}
}