ops manager SCHMAC error

[Mitelpassion]

Hi,

I recently ran a scheduled moves adds and changes for about 180 odd phones. It was updates whereby I moved the IP extensions from one node to another and made them resilient.

More than 90% failed with an error stating that the voicemail box must be on the same node as the extension is moving to. I don't want to move the voicemailbox, it must stay on the initial node.

The weird thing is if I do this manually, I don't get an error. Any ideas?

I've previously done this before and have not seen the error.

Thanks in advance

 

[kwbMitel]

At a guess, the template you are using does not designate the correct controller for the VM.

When you did it manually, did you use the same template?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

there's no diff between the template I use when manually doing it or when doing it automatically....

the funny thing is some of the phones worked....
about to move 200 phones but don't want to do this manually

thanks for the reply so far

 

[Mitelpassion]

ok, the phones that didn't work had voicemail but ent manager didn't have it listed. believe it's a design thing and there's a dpar for it.

the template didn't have a default element however the problem is that the phones that I'm moving have voicemail boxes on different controllers.

 

[kwbMitel]

If the mailbox is created outside of OPS, it will not be aware. OPS has to create the mailbox to include it in its DB.

If you are brave (and Careful) I have a workaround for you.

You need SDS enabled and all of the resilient set options turned on.

1 - Make the phone resilient to the destination controller.
2 - Sync using OPS
3 - Manually change the remote directory on the destination system to reverse the Primary and Secondary systems
4 - Sync using OPS (sync will fail on original system)
5 - Manually Change remote directory on original system
6 - Sync with OPS (may or may do anything, can't remember)
7 - Reset Phone (will home to its new controller)
8 - Use OPS to turn off Resiliency
9 - Clean up failed sync's in OPS TEL DIR Utilities.

Done:
This method has the benifit of retaining ALL data associated with the phone and will have no impact on the VM.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.