We recently started trying to configure the UM role in Exchange 2007 and had to buy an AudioCodes IP gateway to translate traffic from our legacy PBX into SIP traffic for the Exchange server.
Very early on we ran into an issue where we if we diverted a phone to the Exchange UM pilot number (i.e. re-direct all calls to voicemail) then if we called that phone we would get rejected.
A lot of diagnostics and tracing later, we discovered that the calls were being rejected by the UM server, and it was throwing a 1021 warning in the Application log. The message reads:
The Unified Messaging server rejected an incoming call with the ID “<call-ref-number>@<um-server-ip>”. Reason: “The Unified Messaging server cannot find a valid UM hunt group for “<extension>” associated with UM IP gateway “<um-server-ip>”.”
So the UM server was trying to find a hunt group for the extension that we were calling, and was thinking there wasn’t one configured. We did however have a hunt group configured! We had deleted the default hunt group on the ip gateway, and configured a new one with the pilot number as the pilot identifier…big mistake…
It turned out that when you configure a hunt group in UM, if you give it any Pilot Identifier number at all, that is the only number that it will be triggered for. So what you have to do is give it a blank Pilot Identifier! Trouble is you can’t do that, when you make a new hunt group the dialog will not let you create it without typing something in. So what do you do?
Well the answer is, delete and recreate the IP Gateway configuration object in the UM IP Gateways tab of the UM Organization Configuration section. That’s all you have to do! What happens is that when you create a new IP Gateway object it automatically creates a default hunt group with a blank pilot number – and that’s what we want.
Once you’ve done that you’ll be able to call the redirected phone and leave voicemail. Phew. Working UM system!
Lesson learned today: don’t configure things in UM if you don’t know what they’re for…
This week I decided to move this blog over to WordPress. For the last few years it’s been on Blogger and I’ve never really had cause to complain. However now that I know the power and flexibility of WordPress I’m ashamed that I kept it on Blogger for as long as I did!
I have tried to make sure all the old links still work so referrals from Google keep working, but if anyone discovers something missing or has any problems with the new site, please comment here and let me know.
Here’s looking forward to many more years of WordPressing!
I recently decided to learn about IPv6 and signed up to get my own IPv6 address range. It’s all free and your learn loads in the process.
Just visit http://www.tunnelbroker.net sign-up and get learning about IPv6!
They provide a free PPTP VPN tunnel service so you can set your laptop to have its own static IPv6 address no matter where you’re connecting to the internet from. Plus you get free DNS management and rDNS too!!!
I have to say, it’s pretty cool to be able to give my laptop a static forward and reverse AAAA record.
Oh and if you do it soon you might get a free T-shirt too. Just make sure you put in your correct home address details and T-shirt size in the personal details section. It’s all to aid promoting the switch to IPv6.
Posted in Guides, IT Stuff
|
Tagged ipv6
|
Sometimes you need to set the proxy settings for the System account or NetworkService account on a server. There’s a super easy way to do this using bitsadmin.
Set accounts to use a static proxy server with exclusions:
bitsadmin /util /setieproxy localsystem MANUAL_PROXY proxysrv:8080 “;*.consoto.com“
bitsadmin /util /setieproxy networkservice MANUAL_PROXY proxysrv:8080 “;*.consoto.com“
bitsadmin /util /setieproxy localservice MANUAL_PROXY proxysrv:8080 “;*.consoto.com“
Set account to use proxy.pac file:
bitsadmin /util /setieproxy localsystem AUTOSCRIPT http://contoso.com/proxy.pac
bitsadmin /util /setieproxy networkservice AUTOSCRIPT http://contoso.com/proxy.pac
bitsadmin /util /setieproxy localservice AUTOSCRIPT http://contoso.com/proxy.pac
Just replace the blue bits with your own organisations servers and pac file addresses, then run the commands for the relevant accounts you want to change from and administrative command-line window.
More info can be found here: http://msdn.microsoft.com/en-us/library/aa362813(VS.85).aspx
We’ve started using SafeNet ProtectDrive for encrypting all our XP laptops (and Bitlocker for all the rest that are using Windows 7), and occasionally we’ve found that one or two laptops refuse to get past the 32-bit vxBios boot loader screen. For whatever reason that it happens the temporary way around this is to press the shift key whilst the system powers-on and the 16-bit boot loader will kick in and let you in.
Unfortunately the administration guide for ProtectDrive does not explain how to make the 16-bit boot loader a permanent choice for the few machines that just can’t handle the 32-bit loader. So after contacting support and getting the answer I thought I’d post here how to do it to save someone else waiting the usual 6 hours or so before America wakes up and responds to the support query.
To make the 16-bit boot loader the default option when using ProtectDrive all you have to do is boot the machine up using the temporary method (pressing shift whilst it boots) then after logging in drop to the command line and run “setpb /16″ from the Tools folder on the original installation media. That changes the mbr to the 16-bit version.
You can also run “setpb /32″ to switch back to the 32-bit loader too.
Hope that helps someone!
