Sunday, April 29, 2007

Accessing Exchange 2007 Unified Messaging: Part 1 - Requirements

You
Although this process involves setting up and working with Linux servers, you don’t actually need any Linux experience. I provide the step by step instructions, and most of the configuration we do is through a browser. In the Troubleshooting section, I provide some information about troubleshooting issues that may arise. I have very little hands on Linux experience myself, so if I can put these instructions together, you’ll have no problems following them. I do make the assumption that you are familiar with Exchange technology and terminology, and know how to install an Exchange server. I won’t be providing any information about the setup of the Exchange Server itself, although it’s a fairly straight forward process. For troubleshooting purposes, you will need to know a bit about network monitoring, and be able to make sense of packet captures. Hopefully if all goes well, you won’t need to worry about this part.

Exchange Server 2007
First thing you are going to need is a Microsoft Exchange Server. You have two options here. Firstly, you can download the trial version from http://www.microsoft.com/downloads/details.aspx?FamilyID=444c259e-605f-4a82-96d5-a2f448c9d4ff&DisplayLang=en. This gives you a 120-day fully functional trial version that can be upgraded to a full version at any time. That’s more than enough time to get a system up and running and do some testing. Alternatively, (and I highly recommend this option) you can purchase a subscription to Microsoft TechNet (http://technet.microsoft.com/subscriptions/). For about AU$500 a year, you get access to full versions of almost all Microsoft products (servers, applications, operating systems, etc) for testing and evaluation purposes. They are the same products you get if you purchase them at retail, just with a different End User License Agreement. Basically, you can’t use them as ‘production’ systems. But for testing purposes, you have no worries. This subscription is a must have for any Windows engineer who wants to stay on top of Microsoft technology.

sipX
sipX is a Linux based IP-PBX system. It provides gateway and call routing functionality between VoIP systems. It does not have functionality to connect directly to the PSTN. For that task we need Asterisk. It does, however, handle SIP/TCP, which Asterisk does not. So in our case, we will not utilise the PBX features of sipX, and merely use it as a translation service. These instructions are based on the VMWare virtual machine that can be downloaded from the VMware Appliance Marketplace. You can download VMware Server for free from http://www.vmware.com/products/server/. Alternatively, you can download sipX and install it manually from http://www.sipfoundry.org/.

Asterisk
Asterisk is also a Linux based IP-PBX package. It a highly customisable system, that provides all traditional PBX functionality, as well as the ability to connect to the PSTN by various means. We will connect via an external PSTN/VoIP gateway, but there is lot of documentation out there for connecting your own PSTN hardware to the Asterisk system. Once again, these instructions are based on the preconfigured VMware virtual machine downloaded from http://www.trixbox.org/. Trixbox is a preconfigured distribution of Asterisk with several easy to use management tools running on CentOS. Once again, if you prefer you can download the installation package and do a clean install, but these instructions will not cover that process. The memory requirements for the Asterisk/Trixbox and sipX server are fairly low at around 300 MB each. I have all 3 servers running in VMWare virtual machines on a Pentium D with 4GB RAM, and it runs acceptably for testing purposes.

Optional – a PSTN-VoIP service
If you want to be able to call your Exchange server from the PSTN, you will need a VOIP/PSTN gateway service. You can use an over-the-counter hardware device to make use of your existing physical phone line, or obtain a PSTN number from a VoIP provider. These instructions will detail the latter. Most ISPs these days will offer a VoIP service, and in the case of my ISP, it comes bundled with my ADSL connection. If your ISP doesn’t offer this service, there are plenty of companies out there that will. Fire up your favourite search engine and have a look in your area for VoIP providers. If you don’t want to dial in to your Exchange server from the public phone network, you can still use a soft phone from any internet connected PC to access Outlook Voice Access. Follow the instructions, but you can stop after you have installed the sipX server. Asterisk is only required if you want PSTN access.

Document Conventions
Throughout this documentation, I will use the following color codes.
Information or code you have to enter will appear in blue
Where you need to substitute information relevant for your network, for example, where one of my IP addresses appears, that text will appear in green.
Where I reference something that appears verbatim on the screen, that text will appear in red.


6 comments:

pestouille@gmail.com said...

Hi,

We have got the X86 32bits version of Exchange 2007 installed (in a Xen virtual environment) but due to the 32bits limitation our experience will be over when the 120 days will be reached. Do you know a way to "activate" the product with a 32 bit host ?

We have the serial but don't know if it's possible (and where) we could put it in.

Any help is well appreciated.

Thank you.

Adrien

Ryan said...

Hi Adrien,

You use the Exchange Management Shell with the command

set-ExchangeServer MYSERVER -ProductKey xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

This will upgrade the trial version to the full version.

Ryan

J.vandenHeuvel said...

Hi,

yesterday I followed the complete instruction. There is a minor mistake in updating the sipxpbx you use the code: yum –y update sipXpbx
But that doesn't work. You need to type al small characters: yum –y update sipxpbx.

Further more I did not get it to work... I Have a Brand new HP Server Dual core XEON and installed the 64bit Exchange on it. Than I installed VMWare workstation on it and run the 2 images installed and configured as told in this article. When I Dial 222 it waits for a time and after that I get an unreachable tone in my SoftPhone. Dialing to asteriks and vise-versa to sipx works fine... Exchange is configured as in this manual.
Another thing is, when I dial (from local lan) to number 100 (auto attendant on the sipx) the sound quality is REAL BAD. Slow speaking stottering voice.
Should I Install the Virtual Machines on a different server? Or do you have any idea?

Further more I wanna thank you for this great Manual!

Best Regards,

Joep van den Heuvel
netherlands

Ryan said...

Hi Joep,

Thanks for picking that up... damn autocorrect! I have ammended the post.

Regarding your issue, there is a known problem with timeouts when trying to contact the Exchange server. See my post on how to resolve these issues. Otherwise, get a hold of Ethereal, and do a SIP packet trace to see what is going on and send it to me. (ryan at lithiumblue dot com).

I wouldnt worry about the sipX autoattendant if you dont plan on using it. SIP traffic is very lightweight, and is only used to setup a connection between two endpoints. In this case, your phone and Exchange. The sipX server itself doesn't carry any voice traffic.

Let me know how you go

Ryan

Terry said...

the link to your Cent OS Appliance is not working. The download is VERY SLOW. I finally got it downloaded and it is telling me it is currupt when I unzip it?

Ryan Newington said...

Hi Terry,

The VM is not actually mine, its one I found on the VMware Appliance Marketplace that does the job. Any CentOS 5 VM will do the job if you are having trouble with the provided version.

You could also try one of the previous versions listed here:

http://www.symbiosoft.net/products.html

Cheers

Ryan