What's the proper way to move phones, TN's, etc...

[33788]

I am wanting to move the user below. Trying to get the proper way of doing it. Also when moving a user will they keep the same TN or a new TN that is already in that location? Any help would be appreciated. Thanks.

MOVE FROM:

DN 7426
CPND
NAME Jane Doe
XPLN 27
DISPLAY_FMT FIRST,LAST
TYPE SL1
TN 006 0 00 00 KEY 00 H MARP DES 3V228 5 MAY 2005
(2009)

TO:
DN 7367
CPND
NAME Not Assigned
XPLN 27
DISPLAY_FMT FIRST,LAST
TYPE SL1
TN 011 0 00 11 KEY 00 H MARP DES 3V227 8 JUL 2002
(2009)

 

[33788]

Oh yeah if you can provide me the codes also to move the phones. I have it here also but want to verify if what I'm doing is correct or wrong cause some of this info. I have is all wrong. Thank ahead.

 

[mluckie1]

I prefer moving the crossconnect. This will cause the least amount of problems.

 

[33788]

Hmmm, mluckie1 I've heard some people say that B4. Can you explain it in more detail that maybe an option for me instead. I'm very new at this telecom stuff so please don't mind my many questions.

 

[Pete87]

First, I agree with mluckie1, that to move the phone from point A to point B it's best to move the crossconnect.
If I understand you correctly, you want to move ext. 7426 from TN 6.0.0.0 to TN 11.0.0.11. If that't correct, you can use LD 20:
REQ: cpy 1
TYPE: 2009
CFTN: 6.0.0.0
TN: 11.0.0.11
DN: 7367

When your sure you have the correct data on 11.0.0.11, you can delete TN 6.0.0.0 and change the DN of 11.0.0.11 to 7426. Hope this helps.

 

[johnpoole]

pete's right, i mov 20 phones a week, with 8000 on site, we stay sorta busy. a lot of my moves are between remote ipe's so i have ot move the station building to building. i always disu x x x x then do the mov. i keep one tn vacant, to use as a soft tn. 4 0 0 0, to swap two phones, i disu both sets, them mov x x x x to 4 0 0 0, then mov z z z z to x x x x, then mov 4 0 0 0 to z z z z.. the disu is redundant, but if someone starts a conf, or park, it could cause a problem.. i have software moved 100k phones without any corruption. NEVER MOV OR COPY AN ACD SET i've never met a switchman that disagrees with that statement..

REQ: disu 64 0 14 14

REQ: mov
TYPE: 2616
TNTN   64 0 14 14
TOTN 4 0 0 0

that is a load 11 command that can be accessed thru ld 20. if you can move the jumper just as easy, do it that way. i almost never do the jumper move because i am to lazy to walk over to the frame


john poole
bellsouth business
columbia,sc

 

[33788]

Thanks all. I'm like John to lazy right now and to much going on. John what is a ACD set, I've heard you talk about many times. So tell me if I'm wrong but when you use the move command it doesn't move the TN correct? It moves everything else but the TN? So the user would get a new TN if I don't do what John says basically.

 

[mluckie1]

Trace the wire coming off of both TN's to the feeder pr or cable number. Then pull the existing crossconnect and run to new location. I have heard of coruption when using the move and copy commands.
John, with all those phone moves I'm amazed you still find time to share your vast expertise.

 

[Pete87]

I started using copy because I too heard of coruption when using the move command on earlier software versions. Never had a problem with copy, but it sound's like they have corrected the problem with the move command too. That's good to know, thank's for the update.

 

[johnpoole]

people seem to think that when i'm typing i must be working.. 81 c, rls 3, call pilot and symposium, voip with cisco managers, 8231 stations 31 buildings about 2000 acres. but they are 3 of us, i do mostly just software. and with scripts, my job gets easy.. example alt 8, enter a dn, highlight the tn, return.. that prints the tnb. alt 7, the screen stops to let me pick a vacant line for the lamp.. remove or add a mail to a set, 3 sec.

john poole
bellsouth business
columbia,sc