|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
Sorry, tried to use the quote feature but got an error message…
Nope. You would need to delete and re-add the mailboxes, program keymaps, forward path, attendant station, outgoing access, etc, etc, etc.
Swapping stations via DB Studio should only be used as a last resort when you’re not on site.
Like I said previously, get yourself a punch tool and learn how to use it.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jan 2011
Posts: 33
Member
|
Member
Joined: Jan 2011
Posts: 33 |
ya... i have a punch tool and have used them before but the idea of playing around with a call center's 50+ active lines is a little daunting :S ...
is there an easy way to keep associated features with an extension if i'm moving them around? such as vm box and key shortcuts and stuff?
i noticed that when i move phones around our huntgroup and stuff stays working (assumably because its only looking for extensions not address.)
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
There is no way to keep programming associated with an extension in place when swapping via DB Studio. It sounds like you’ve been lucky that the existing programming worked and the people can use their phones. Obviously, all the phones that have been moved were already members of the hunt group, so calls got to the agents.
I can recall having to go in and straighten out disasters caused by customers making “a few minor changes†to their systems.
Punching down cross-connects is no big deal; especially with only 50 phones. If this system is going to be your project moving forward, now’s the time to document everything and clean up anything messy. It may take a few hours of your time now, but the payoff will be huge down the road.
|
|
|
|
Joined: Jan 2011
Posts: 33
Member
|
Member
Joined: Jan 2011
Posts: 33 |
ya you are right. so on the punch-down block (PBX? i hope i'm using the right terminology) all i would need to do is move the 4 wires (looks like 2 blue and 2 orange for each line?) to the new "port", which would change the "address" i see in DB but would maintain the extension and all features.
just trying to make sure i got it before i start pulling up these tiny wires lol.
also, has anyone run into an issue with the current wires being really short, as in they may not reach from one port to another?
|
|
|
|
Joined: Jan 2011
Posts: 33
Member
|
Member
Joined: Jan 2011
Posts: 33 |
Originally posted by jeffmoss26: The 'address' is the node, slot, card, and port that each particular phone is attached to. Example... your 1:05.02.01 would be node 1, card 5, slot 5, port 1 and could in theory be any extension...say 105. For whatever reason you decide to move the person on extension 105 to a different office. The old way would be to actually move jumpers, every time. With the newer systems it can be done through programming, as the others have said.
You have it correct in your last paragraph- ok so now i'm a little confused. you're saying that the best way to move a phone now is to use the DB Studio since we have a newerish system? wont this loose features and vm box etc like DND has said?
|
|
|
|
Joined: Jan 2011
Posts: 33
Member
|
Member
Joined: Jan 2011
Posts: 33 |
to add to my last post i'm mostly asking because its goning to take a long time to be able to properly trace which wires on the cross-connect are going where... so in the meantime i need a solution that wont cause the entire system to go screwy.
i just need to be able to have full control over where phones get located and be able to keep thier pre-programed features.
|
|
|
|
Joined: Dec 2002
Posts: 9,429 Likes: 3
Member
|
Member
Joined: Dec 2002
Posts: 9,429 Likes: 3 |
The blocks are just called blocks. The cabinet would be called a KSU. PBX just refers to a large phone system, Private Branch eXchange.
Jeff Moss Moss Communications Computer Repair-Networking-Cabling MBSWWYPBX, JGAE
|
|
|
|
Joined: Sep 2005
Posts: 206
Member
|
Member
Joined: Sep 2005
Posts: 206 |
Just a note about swapping. I used to swap extensions on older systems remotely, un-associating mailboxes and changing the extensions around in programming. Intertel ended up telling me that they were getting reports of databases getting corrupted from that though.
|
|
|
Forums84
Topics94,516
Posts639,968
Members49,848
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
136
guests, and
33
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|