I was trying to integrate Exchange UM, OCS and an audio codes gateway today & stumbled across something kinda quirky.
If you are trying to get UM and OCS integrated, you need to enabled TLS on your UM dialplan. That’s easy enough (set-umdialplan -identity MyDialplan -voipsecurity SIPSEcured)
What they don’t tell you explicitly, though, is that when you enabled TLS for one gateway/diaplan, it forces all dialplans/gateways to use it (current and future).
I found this out the hard way: I was trying to use my audiocode MP-114 to send calls to exchange AFTER I had already done the OCS integration.
The AudioCodes was trying to talk SIP on port 5060, but the UM server wasn’t listening. A quick netstat -a showed that the only port it was listening on was 5061. TLS!! doh!
I tried to run the set-umdialplan blahblah -unsecured on my gateway. It took it, but told me that "nothing had changed". (i.e. I’ll do this if you want, fool, but I’m telling you it’s not gonna work!)
Sure enough, it didn’t matter. I poked around on technet and found the odious source of the problem.
Oh well. I suppose I can just try and make TLS work on the Audio codes. I gave it a quick try by setting all the ports to 5061, but of course that wasn’t enough. I even tried importing the cert from the UM box to the audio codes, but that didn’t work.
