Call Manager 3.0(7)<br>Unity 2.4.5 (73)<br>Exchange Server with integration to another Exchange Server both Service Pack 4<br><br>Just in the last day or two a delay has occurred in turning the MWI on/off. Sometimes 2 minutes, have seen as long as 40 minutes. <br><br>When manipulating (deleting, listening, etc) messages from the TUI, there is also a similar delay in seeing the message updated in Outlook.<br><br><br><br>Norm Cook<br>Gibson Petroleum Company Limited
I'd be interested in seeing a subscriber message activity report for someone having such problems. This will show new message activity and our reaction to it (i.e. sending out MWIs/notifications etc...). This would indicate if we're sending the MWIs and they're not being acted on properly or if we're not getting notification of message state chagnes in a timely fashion or what.
The fact that the outlook clients are not updating quickly, however, is interesting... we have nothing to do with that, obviously, so that would seem to point to slowness on the Exchange side of the fence, at least for the home server in question. We are updating the messages directly in the mail store of the user, not on our box and relying on it to sync up. If the outlook client is taking a while to update that info, it could be that the server iself is pegged for some reason or another (i.e. it's busy doing a defrag or something).
Problem Solved. The sync occurred every 8 minutes on the button. I had earlier made a change to our main Exchange server (Not Unity) to allow outlook client to access it through a firewall (See Microsoft article Q155831). I accidentally set both port numbers the same. Duh. Fixed it up and the MWI works perfectly.
It doesn't work if you set these to the same value: hklm\system\currentcontrolset\services\MSExchangeDS\Parameters\TCP/IP port hklm\system\currentcontrolset\services\MSExchangeIS\ParametersSystem\TCP/IP port
OK use with extreme caution. This is a system wide setting and will affect everyone. If someone gets cut off (i.e. a mobile phone user heads into a tunnel or something) the message they are listening to will be marked read and will appear at the end of the read message stack. If they have a lot of read messages, this can be a real pain to deal with.
Promise me youll be careful (and that you wont run in the house or jump on the bed and that youll eat all your vegetables before desert) Head to the registry and go to the branch at:
HKLM\ SOFTWARE\ Active Voice\ Conversations\ 1.0\ Message Playback\
The Message Playback branch will probably not be there, youll have to create it. In that folder youll need to create a new DWORD key named Upon Hangup Mark Read. Set it to 1 and itll do what the name implies a restart of Unity is required before this takes effect.
Not quite working correctly. When I use the TUI to retrieve the message the MWI goes off as soon as Unity starts playing the last message. I believe this is the correct behaviour. However, as soon as I hang up, the MWI comes back on and the Messages in Exchange become marked as Unread. If I choose to save or delete the message from the TUI it works fine. If I play the messages using Viewmail or Outlook, it works fine.
This is expected behavior for the default configuration... if a user hangs up without taking specific action on a message (i.e. saving it as read, deleting it, marking it new) we mark it new. The assumption being here that you may have gotten cut off and if we mark the message as read then you'd have to call back in and hunt through your read message stack to go find the message to hear the rest of it... rather annoying.
There is a registry setting in 2.4.6 that will let you change this behavior to markign it read instead. If you opt to exercise that option, proceed with catuion... in the world of cell phones this can be risky business. If you want to do that (and you've got your trust 2.4.6 version installed) let me know and I'll post the registry setting here.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.