bnguyen714
asked on
Moving a branch CallManager Express phone over to existing headquarter Cisco Unified CallManager.
I'm working at headquarter and we're running CUCM 6.0. We also have a small branch office that's running CME 3.1. Both offices/gateways are communicating just fine. We want to start moving the CME phones over to CUCM. A H.323 gateway is already configured. Route List/Group/Pattern is also configured. After adding the phones to CUCM, how do I get the CME phones to register with CUCM? Thank you in advance!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, you can use the existing CME as the second option 150 ip address. It is not true SRST, but works just fine as long as you have all the ephones and dn's assigned prior to failover. I usually set the system message on the CME as something like "system is in failover mode" so that users have some indication that they may have reduced phone services...
ASKER
So since my CME is already configured with all the ephones and has been operating for over a year now, I shouldn't have to do anything else except setting it as the secondary Option 150? All phones will retain the same extensions.
Correct
ASKER
One last question-- what about voicemail? How can I redirect the CME users over to Unity?
That's all handled by the call manager when the phones re-register with CM. Whatever voice mail pilot number is configured there...
Users won't be using the local CUE
Users won't be using the local CUE
ASKER
Can't we set CME 3.1 as the second Option 150 and use it as SRST? I guess I'm trying to avoid an upgrade if possible.