It's seems a though when and IP end user initiates an E-MAIL MESSAGE with a RETURN RECEIPT OR PRIORITY OPTION, that the receipt or priority info. is then deposited in the IP end-users UNITY voice mail. NO MESSAGE WAIT LIGHT is indicated on the phone. However, once you log into VOICE MAIL it states that you have how ever many NEW messages.<br><br><br>
Yes as strange as it sounds, what you describe is actually how its supposed to work. Theres a long, painful, convoluted story for why that is First, let me say that you can edit the registry to have receipts not be presented in the voice mail stack. You can change this behavior for 2.4.5 and later. Go to:
HKLM\ SOFTWARE\ Active Voice\ Conversations\ 1.0\
You should see a key there called Exclude Return Receipts thats a DWORD which defaults to 0. If you set this to 1 and restart Unity, receipts will no longer be included in the voice mail stack for all users. If you dont see the key name there you may have to add it. 2.4.6 build 102 should have it there by default but 2.4.5 didnt and upgrades may not add it automatically.
Now heres the brief version of why it works like that.
When we filter your inbox to parse out messages into separate stacks (voice mail, email, faxes, read vs. unread, urgent vs. normal) we have to pass in a very long string of message class strings to Exchange to get the counts back and assemble all the messages into order (ourselves, Exchange doesnt support server side sorting but thats another topic). Unfortunately, Exchange has a nasty little habit of leaking space into the PRIV.EDB store when your filter strings get longer than a set amount it reserves space for the filter results that then doesn't get fully recovered. Eventually itll eat up all your private store space which isnt recovered by online defrag and customers would have to run off line defrags to get them back. Ugly doesnt begin to describe this scenario. Also, the longer the filter strings, the longer it takes to work through your inbox and get the stacks setup...
So we couldnt get overly fancy and generate separate stacks for NDRs and return receipts and non deliverable faxes etc as we had originally wanted to since the filters would be much too long.
So the question came down to where to stick receipts and NDRs (we only filter on the beginning of the message class to determine if its a receipt or NDR, we dont know if its a fax receipt, voice mail or email again, gotta keep the filters reasonable). We opted to present them in the voice mail stack since all Unity subscribers will get that and not all will have email or fax stacks (and, of course, we couldnt make a separate stack for these which was the original plan).
So the MWIs dont go on for these guys since the notifier isnt picking them up as a voice mail but theyre presented in the voice mail stack. Odd, I know, but there was a method behind the madness. Were hoping to address this with Exchange 2000 which has a different filtering mechanism we can leverage and present a separate receipts stack which will make this much cleaner.
Probably way more than you wanted to know, but there you go
Actually I would like to retract my "works perfectly" posting. It works perfectly for delivery and read receipts, however, NDRs still show up as vmail messages. Is there some key that I can add like "Exclude NDR" or something like that to make it stop doing this?
NDRs are not a big problem on my email system. The reason I'm asking is because, in an earlier post, you seemed to indicate that the modification of the registry value would resolve the issue for receipts as well as NDRs as they are all dumped into the same 'stack'. When I told a user that the receipt problem has been resolved he happened to receive an NDR that showed up as a vmail and as egg on my face. If NDRs are not included in this fix then fine......
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4