The purpose of this doc is to give an example as to how to configure a AudioCodes IP gateway for use with an Exchange 2007 Unified Messaging demo. I’ve looked around the web and I’ve looked at AudioCodes’ own documentation. It’s all kinda fuzzy, so I thought I’d write my own How-To and save people the trouble. The docs on how to set up a UM server are pretty straightforward, but getting the gateway seemed like a bigger mystery.
My Environment
In my scenario, I have:
-
An Exchange 2007 UM server
- AutoAttendant ext. 2500
- Subscriber access ext. 2100
- MP-114 2FXS/2FX0 gateway
- 2 Analog phones
-
2 Exchange users configured for UM
- User1 ext. 3001
- User2 ext. 3002
In this example, I am not connecting to a PBX (you’d normally use the FXO ports to connect to the PBX) but instead I’m using the analog phones to make calls into the Exchange UM server. This setup is good enough to showcase the main features of UM, but you’d never use it in production.
Getting the MP-114 on the network
The factory default IP address of the gateway is: 10.1.10.10. Unfortunately there is no easy way to change this, so the best thing to do is to connect the gateway’s Ethernet interface to a switch or hub, then connect your PC to the same switch or hub. You’ll have to change your IP to something on the 10.1.10.X network, and use a 255.255.0.0 subnet mask. Once you do that, you can browse to http://10.1.10.10
Configuring the MP-114
The default username is: Admin and the default password is: Admin
Once you authenticate successfully, you’ll see the initial config screen:
First things first, assign an IP address to the machine. You’re going to want to assign an address that is on the same network as your Exchange UM server. In my case, that is the 10.10.10.X network.
Once you’ve entered the new IP and subnet mask, click "Reset" – this will save the config and restart the gateway.
Configuring the gateway to talk to Exchange
Change your PC’s NIC to have an address on the same subnet (for me, again, it’s the 10.10.10.X network) and the browse the gateway’s new IP address. In my case, it’s http://10.10.10.2
At the initial config screen, enter in the the IP of the Exchange UM server in the "proxy IP Address". For me, it’s 10.10.10.9
IMPORTANT NOTE: Even though this is counter-intuitive, DO NOT select "working with Proxy". This definitely breaks things.
Once you’ve update the proxy IP, click "Reset".
Go to the Protocol Management/Protocol Definition/General page and change SIP transport to TCP
Once you have updated the settings, Click "Submit".
Go to the protocol management/ protocol definition/ dialing & DTMF screen
Change max digits to 4. Click submit.
I changed this to 4 because I am dealing with only 4 digit extensions. If you leave the default (5) it will wait around for the 5th digit.
Configuring the Gateway to route calls to Exchange
Click on the "Routing Table" link and select the "Tel to IP" submenu item.
In this example, the destination prefix is 2* so the gateway will route any numbers starting with "2" to the exchange UM server. You can put in a * for "source phone prefix" so that it routes all calls, no matter which phone originated the call. Lastly, enter in the IP address of UM server in the Dest IP address field.
I’ve got it configured like this because in Exchange UM, my auto attendant is ext 2500 and my subscriber access is number 2100. I want all calls bound for those 2 numbers to be sent to UM. If you fail to put this in, no calls will go to UM. Obviously, if your AutoAttendant or Subscriber Access numbers start with 3, then you’d put a "3*" into the "Dest Phone Prefix" field.
When you have updated the info, click Submit
Configuring the analog phones
As I mentioned in the intro, I bought a couple cheap analog phones for this demo kit. I plugged them into the back of the MP-114 in ports 1 and 2 (both FXS ports). I wanted to assign them phone numbers in the gateway, so Click on the "End point phone numbers" link and enter the relevant info.
I used these numbers because I have 2 subscribers in Exchange; one has extension 3001 and the other 3002.
Notice that the subscribers’ extensions (3001 and 3002) are not called directly by the gateway. you are going to call the subscriber access number (2100) and the mailbox number gets passed via caller ID to exchange.
When you call into UM from one of these numbers, it recognizes your ext and prompts you for your pin.
If I were to have assigned a random number (e.g. 5000) to these phones, when you call UM, it doesn’t recognize you (nobody with the ext. 5000 lives on my exchange server) and it will play the generic default greeting.
Click "submit".
That’s it!
I’ve found that saving the config on the gateway, then cycling the power tends to clear up any wacky issues. Yeah, it sounds stupid, but, hey it’s a cheap gateway!!
im my audiocode 5 id are showing unregistered and they are nt working.rest 17 are registered and are working .pls help me