Source record · tier 2 current vendor documentation
Design Guide for Cisco Unity Connection 15 - Single Inbox
- Publisher
- Cisco Systems
- URL
- https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/design/guide/b_15cucdg/b_15cucdg_chapter_010100.html
- Published
- 2025-08-12
- Updated
- unknown
- Accessed
- 2026-09-30
- HTTP status
- 200
- License
- Cisco proprietary documentation; no-redistribution; short excerpts and locators only
Source notes citing this source
- Cisco advises configuring message aging to permanently delete messages in the Unity Connection deleted items folder when single inbox is used. in context
- Cisco says round-trip latency between Unity Connection and the Office 365 server should not exceed 250 ms. in context
- A voice message deleted in Outlook, including from the Outlook Deleted Items folder, is only moved to the deleted items folder in Unity Connection and is not permanently deleted there. in context
- Cisco says the quota of each Exchange mailbox should be increased by the size of the quota of the corresponding Unity Connection mailbox when single inbox is configured. in context
- For a single inbox user, voice messages are first stored in Unity Connection and immediately replicated to the user's Exchange or Office 365 mailbox. in context
- The Connection Mailbox Sync service uses four connections by default; above 2,000 users or 80 ms round-trip latency the design guide's formula is connections = (single-inbox users * (latency in ms + 15)) / 50,000, with a maximum of 64 and never fewer than four. in context
Cite this source record
APA
WarmTransfer. (2025, August 12). Design Guide for Cisco Unity Connection 15 - Single Inbox. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cuc15-design-single-inbox
BibTeX
@misc{warmtransfer-cisco-cuc15-design-single-inbox,
title = {Design Guide for Cisco Unity Connection 15 - Single Inbox},
author = {{WarmTransfer}},
year = {2025},
url = {https://warmtransfer.net/knowledge/sources/cisco-cuc15-design-single-inbox},
note = {Cisco Systems, accessed 2026-09-30}
}