Hi everyone,
Normally I hate cross-posting on different fora, and I try to avoid it, but maybe you will forgive me this time.
I am migrating our OCS 2007 to R2 using the side-by-side migration and feel unsure about the necessary steps to integrate Exchange 2007 SP1 as detailed in this post:
http://social.microsoft.com/Forums/en-US/communicationsserversetup/thread/ea901e28-db1c-473b-90a9-027300395f37
After reading and thinking about the problem I believe that in a nutshell it boils down to this: Is it possible to keep a single dialplan, for two different OCS Standard(!) pools (and hence two Exchange UM IP gateway objects), using a single mediation server in a single forest and can the exchucutil.ps1 script safely handle this? Can I break something?
If it possible I can run the script, add the necessary objects, configure using OCSUMUtil and run both pools side-by-side while migrating the users and R1 mediation server.
I could create a new dialplan (new name but same functionality), but the disadvantage is that I need to reconfigure or add this dialplan to the Exchange UM-enabled mailboxes, and I would like to avoid that.
Thanks for your input!
Best Regards!
Wim
Wim,
Just an idea...
If you configure your OCS R2 Pool, to use the same location profile as the current OCS R1 pool, shouldn't your migrated users be routed to Exchange UM? Is your UM dial plan set to Secured?
When you move your UM (Auto Attendant, Subscriber Access) accounts to the new pool, you may need to reconfigure OCS-UM again (you can always run exchucutil -verify, and ocsumtuil to check)
-Ilse
Hi Ilse,
Thanks for your comment. I believe you are right. The R2 server is currently indeed using the same location profile as the R1 server. When a R2 user calls voicemail, I can see an event log on the R2 server displaying the URL of the correct Exchange server, but with a message that the Exchange server did not answer the call. On the Exchange server an event log is displayed stating that an incoming connection from the R2 server was denied because it was not a TLS peer (or a wrong certificate) => the call flow from the R2 server is correct.
Therefore I assume the problem is I need an additional UM IP Gateway for the same dial plan on the Exchange server. Exchange will then probably accept the connection from R2. I could create this manually or by using the Exchange integration script. Afterwards I can also create a new Subscriber access using the OCS integration util. I guess that from then on calls could start flowing normally. The "play on phone" function would probably not work, as only one Exchange UM IP gateway object can be configured to handle outgoing calls. During the migration that is not really a problem. After removal of the R1 server I can change the setting and remove the old object.
The problem is that I am not sure if this is supported, and if it corrupts my Exchange server setup. On the other hand I am also unsure whether the EXchutil script could do any damage, or performs additional changes behind the scenes that I cannot do manually. The fact is that when I rerun the script, the script would encounter two pools for the same dialplan. I searched a lot in documentation and the Internet, but did not find an explicit reference that this is allowed.
When I do the -verify now, the script reports that all permissions are set correctly, but that a UM IP Gateway object is missing for the R2 server.
So it could be easy to solve, but I get cold feet trying this on our live environment (no parallel test setup yet). Maybe thesedays the Exchange config is more resilient for stupid administrators than before and errors can be solved more easily, but I do not like the idea of trying unsupported things. Actually I find it strange that this topic, that every migration should encounter, is not discussed or described more.
Thanks for your input,
Best Regards
I decided to put my faith in the Exchange 2007 Management console and added a new Exchange UM IP Gateway object that points to our new R2 server. As soon as the object was created it was possible to call voice mail from R2 users. Missed call notifications are also coming in now. Great!
For now I left the option "Allow outgoing call through this gateway" switched ON for both gateways, and play-on-phone even works. :-)
Exchucutil.ps - verify showed no errors and two pools pointing to the same dialplan.
Nice.
But, feel free to comment on whether this is actually a good idea or not. :-)
Best Regards,
Hi Wim,
so it works in practice like it should according to the books :-)