cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
313
Views
0
Helpful
4
Replies

Unity Mailbox size limits and filtering

brian-henry
Level 4
Level 4

Is there an max/recommended size for a Unified Messaging Environment? I heard that 100MB for a size limit?

Does Unity always filter thru all the inbox for a new message or just when you have saved messages of all types like fax, e-mail, vm?

I know if a person deletes a large number of e-mails then Unity goes thru the entire Inbox to see what is there are far as new, deleted, etc..

1 Accepted Solution

Accepted Solutions

lindborg
Cisco Employee
Cisco Employee

Couple things here.

First, in recent versions of 4.x we rely on indexing services in Exchange for keeping the filters up to date for message count and generating the mailstack for voice, fax, receipts,emails that are presented to the caller when they dial in. Unity does not construct that index on the fly when you log in any longer unless for whatever reason it is not up to date when we do (i.e. it's a newly imported mailbox or the indexing service has not gotten to it yet or the like).

When a subscriber is imported into Unity we insert requests for that mailbox's inbox on the Exchange service to keep an index of messages based on type/read status such that when we log in we can quickly get a message count to present and construct a stack of messages in fairly short order. This is far, far faster than doing it on the fly and has helped sites with very large inboxes get acceptable performance. The indexes, once established, are updated by Exchange whenever the inbox changes (new message added, marked read, removed...). There can be a window of time from when a subscriber is added and their indexes are up to snuff, however.

So, assuming you're on 4.1 or later and using Exchange, I don't believe there is any specific mailbox limit where UM performance will start to break down.

View solution in original post

4 Replies 4

lindborg
Cisco Employee
Cisco Employee

Couple things here.

First, in recent versions of 4.x we rely on indexing services in Exchange for keeping the filters up to date for message count and generating the mailstack for voice, fax, receipts,emails that are presented to the caller when they dial in. Unity does not construct that index on the fly when you log in any longer unless for whatever reason it is not up to date when we do (i.e. it's a newly imported mailbox or the indexing service has not gotten to it yet or the like).

When a subscriber is imported into Unity we insert requests for that mailbox's inbox on the Exchange service to keep an index of messages based on type/read status such that when we log in we can quickly get a message count to present and construct a stack of messages in fairly short order. This is far, far faster than doing it on the fly and has helped sites with very large inboxes get acceptable performance. The indexes, once established, are updated by Exchange whenever the inbox changes (new message added, marked read, removed...). There can be a window of time from when a subscriber is added and their indexes are up to snuff, however.

So, assuming you're on 4.1 or later and using Exchange, I don't believe there is any specific mailbox limit where UM performance will start to break down.

Thanks again! I know from the book Cisco Unity Deployment and Solutions Guide showed that I guess Unity in the pass did the index in RAM on the unity server.

Will there be an updated version of this book in the future?

No plans for an updated book that I know of... I'm still figuring out how to spend the $22.50 I made from my participation on it. Can't say what the other guys may be doing, though.

Ha!, I figured that at least you made $23.00!

Thanks for all you help and the book is pretty informative.

Brian