If you’ve deployed Exchange Server 2007 for your UM platform to house your company voicemail and enable voice access to said mail and all the other sundry things involved, you may have noticed something. It looks, on initial blush that the CODEC used for the voicemail is a per dial-plan setting and can’t be customized outside of that.
I have found otherwise. The reasons you may want to this are primarily for email access from non Windows platforms. The default, and arguably the best CODEC is WMA. The kicker is that iPhone, BlackBerry, Android Phones, as well as Mac OSX, and Linux clients all can’t decode WMA files without effort by the end user or technical staff.
Using the set-UMMailbox command you can modify the "CallAnsweringAudioCodec” on the users mailbox.
The largest use case I’ve seen for this is for iPhone, BlackBerry and Android clients on your network. Neither of these devices come with the ability to decode WMA and neither are easily made to be able to decode WMA. Now you say, how do you know which users are using a non Windows Mobile device to ActiveSync data from your servers. I have help for you here as well.
On a per user basis you could comb through your users with get-activesyncdevicestatistics –mailbox <user mailbox name>, but a better solution exists. Export-ActiveSyncLog. The only requirement here is that you haven’t stopped IIS logging on the ActiveSync IIS virtual directories.
You run this command against the folder in which your IIS logs live, pointing it at a log file and specifying an output path.
The output is 6 CSV files. The Users.csv is the one you care about here. You may want to do this analysis over a couple of recent days just to make sure you don’t miss people. Opening it with Excel you can sort by the “Device Type” column. iPhone, and Android clients will need to have their CallAnsweringAudioCodec modified.
I hope this helps you in making your users more connected and productive.
