Exchange Server 2007 Unified Messaging is designed to integrate voice and fax functionality into Exchange Server...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
If your company is preparing for Exchange 2007 deployment and is already running Asterisk, an open-source IP PBX telephony system, there is a way to make the two systems coexist within the same organization.
On his blog, programmer Alan Dutton provides instructions on how to connect Asterisk to Microsoft Exchange 2007 for Unified Messaging, so they'll work side-by-side in the same phone system.
The example documented in the abovementioned article involves running Asterisk as a VMWare image of Trixbox (a Linux distribution with Asterisk pre-installed and pre-configured), and Exchange 2007 with Unified Messaging.
If someone dials in and connects to Asterisk, and then punches 666666, they'll be forwarded to the Exchange 2007 auto-attendant. If they dial 55, they'll be forwarded to the Exchange 2007 Subscription.
The exact number to dial for each is arbitrary, and I believe it can be changed as long as it doesn't conflict with other commands. (I suspect the author's choice of 666666 is a joke.)
According to Alan Dutton, a few things still don't work yet. For one, caller ID is not passed from SIPX to Exchange Server, so voice messages forwarded in this manner are tagged as "anonymous." Additionally, the instructions for dialing out from Exchange Server are included in the linked article, but have not been tested by the author yet.
About the author: Serdar Yegulalp is editor of Windows Insight, a newsletter devoted to hints, tips, tricks, news and goodies for all flavors of Windows users.
There is a much more detailed description of how to access Exchange 2007 Unified Messaging features using the open-source tools Asterisk, Trixbox and sipX.
I read this article and thought you might be interested in the instructions I wrote about configuring Asterisk and sipX to work with Exchange Server. I built upon Alan's post, clarified a few things, and also fixed a few problems with his instructions.
Do you have comments on this tip? Let us know.
Please let others know how useful this tip was via the rating scale below. Do you have a useful Exchange Server or Microsoft Outlook tip, timesaver or workaround to share? Submit it to SearchExchange.com. If we publish it, we'll send you a thank-you gift only an IT geek could love.