Norstar Voicemail Question - Moving mailboxes 1

[luv2ski]

should have moved x-conn not changed the ext number...first try a reboot of vm if still issue delete mb's and rebuild the ones with problems...next time ask before you do or call a vendor

ski season has started

 

[MackMasterson]

The vendor is the one that told me to move DN's. I always ask first...

 

[galfaro]

He may have ment physically.
Gabriel

 

[MackMasterson]

I told him exaclty what I wanted to do....move user locations...he told me to use Old DN/New DN is system programming to move them. I will reboot my voicemail tonite and see what happens...Thanks!

 

[MackMasterson]

Hoping you can help...

I had to move some user around in the office, and was able to move their extensions using the Old DN/New DN in system programming, but for some reason, when the user tries to get to voicemail, it is sending it to the voicemail account for the person who used to be there. I have tried to re-attach the voicemail boxes to the extensions, but it still wants to go to the old voicemail box. This person is working off-site, so I need to keep this box active. Any thoughts??

 

[talaphone]

using the Old DN/New DN is not a good idea, it will change the default port/dn config, if something goes wrong with the system everything will be messed up and you will spend hours trying to figure out the old setup (unless you have a very small system) , x-connect is the best way to move users around.

 

[Roldan]

Mack,

If you would have unassigned the mailboxes for the phones you were going to change first, then change extensions, then re-assign mailboxes; this would not have been an issue. However, moving the physical cross-connect wires is always better.

Louie Roldan

http://www.4vertex.com

 

[MackMasterson]

So the way to go is to go into the VM admin, remove the extensions for the mailboxes and then move the extensions?

Got it...

 

[FletcherP]

Leave the VM box on the DN and move the cross connect. It's that simple. Keep the system square, don't set relocate, it will keep your system happy and your Voice Mail won't spaz out.

 

[jiniguez]

Just incase this happens again in the future and you have a person you trust on the other end is that you can activate set relocation on the system. This will allow you to move two sets at one time. Hence all programming including voicemail boxes will move. Some people think its the same as Changing DN's but you can have problems as you just experienced. As long as the jacks are active to the Norstar this is a good feature for remote programmers.

 

[FletcherP]

Set relocation is not a good alternative to moving cross connects. The set relocation can screw up a system with voice mail, especially large systems, without notice ports will tag on to MODS you don't even have active. This will show DNs that are way out of normal DN list and causing VM boxes to be attached to non assigned ports. KISS method is the best. Move your cross connects.

 

[Roldan]

Well as I stated and so did others, the best way is to move the physical cross connect wires if you are moving phones. I was only saying that if the mailboxes would have been removed first, you would have not had the problem that you experienced. But I've said it before and I'll say it again, move the cross connect wires and you'll have no problems, for sure.

Louie Roldan

http://www.4vertex.com

 

[thephoneboy]

I have never had a problem with set relocation. Although I prefer to move the cross connect. Many customers are not comfortable with changing cross connect wires. I always have customer change one phone at a time and make sure it comes up properly before they move the next phone. Then I alway have them turn Set relocation off. P.S.I am not as an expert like most folks on this sight. This is just my opinion. Good luck.

Sincerely, thephoneboy