9/1/2010


Everything appears to be working but ExchangeMWI is not lighting my lamp

Make sure you have two or more test UM users


What demo users are MWI enabled

Open the Event Viewer and look for the event ID 500. This will list the first five users that are enabled for MWI.

When using a standard user account with SSL (not a Domain Admin) ExchangeMWI is unable to create preferences and a create preference error 100 is seen in the Event log.

Reason: When using SSL the ExchangeMWI service is running as the user in the Domain section of “Exchange MWI Configurations”. While running the service as that user it inherits the user’s permissions and prevents standard user from altering the ExchangeMWI program’s folder.

Remedy: They are three different ways you can fix this and only one remedy is needed.
1) Give the user Domain Admin rights
2) Add the user to the local administrator’s group
3) Give the user read/write permissions to the ExchangeMWI folder


How to get SSL working if your domain doesn’t have self enrollment enabled

Using the user account in the Domain section of “Exchange MWI Configurations” log into Exchange OWA with Internet Explorer. https://mailserver.yourdomain.com/owa

1) Click on the certificate and then click “View Certificate”
2) On the bottom click Install Certificate
3) The Certificate wizard appears
4) Leave the defaults and click next then click finish.
5) Within “Exchange MWI Configurations” check Secure (http) in the Client Access Role section
6) Click the save button
7) Start the service and review the event log for any errors

Exchange UM is working but ExchangeMWI is not

Possible Reason: Many times in CallManager the SIP trunk’s inbound Calling Search Space doesn’t include the internal phones. This will cause SIP error message 404, representing those users are not found in the realm.

Remedy: Double check your Calling Search Space and the partitions associated to it.

Look at the route pattern associated with the SIP trunk and it’s partition

Windows 2008 Server Issues

1. After installing ExchangeMWI the application “Exchange MWI Configurations” does not have proper rights to it own folder. This prevents the application from creating the preference file and working correctly.

Reason: Do to the new security Improvement in Windows 2008 the program folders are protect with a more restricted ACL applied to the folder.

Remedy: Add the *user manually to the application’s folder, either
Program Files\AaronSoftware\ExchangeMWI
Program Files (x86)\AaronSoftware\ExchangeMWI

*The user to add depends on the user currently logged into the sever editing the applications preferences. Example: If you are logged in as bjones, bjones should be added with full permissions to the folder.

Notes: I’m highly considering moving the preferences to a better location to prevent this issue from occurring in the future.

ExchangeMWI configuration with Cisco CME

We recently found a workaround for CME to implement ExchangeMWI without using the callout feature. The new code within CME is to use 255.255.255.255 instead of the server's IP running ExchangeMWI.

mwi-server ipv4:255.255.255.255 expires 3600 port 5060 transport tcp unsolicited