Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Moving Extension between switches 2

Status
Not open for further replies.

mkrice2

IS-IT--Management
Sep 26, 2006
41
US
OK Here goes,

3 locations all opt11
outed tn to cdp from location 1 to location 2
ld 87'd to create the new cdp for that extension in switch 1.

Here is the post of that

REQ prt
CUST 0
FEAT cdp
TYPE dsc
DSC 8417
DSC 8417
FLEN 0
DSP LSC
RLI 13
NPA
NXX

Built a new 3903 at site 2. (Went fine)
When I prt in ld 87 for site 2 here is what I see.

FEAT cdp
TYPE dsc
DSC 8417
DSC 841
FLEN 0
DSP LSC
RLI 13
NPA
NXX

I cannot program key 00 for 8417.


REQ: chg
TYPE: 3903
TN 25 0
ECHG yes
ITEM key 00 scr 8417
SCH0371
KEY

I know the TN works because I've tried a different DN. Is there something in the CDP that would cause this?

Why does it show two DSC (one for 8417 and one for 841?)

Thanks alot in advance.

Matt

 
Here is the post of the TN is site 2:

REQ: prt
TYPE: tnb


TN 25 0
DATE
PAGE
DES

DES 8417
TN 025 0 00 00
TYPE 3903
CDEN 8D
CUST 0
FDN 8580
TGAR 1
LDN NO
NCOS 4
SGRP 0
RNPG 0
SCI 0
SSU 0000
LNRS 16
XLST
SCPW 6740
CLS CTD FBD WTA LPR MTD FNA HTA TDD HFA GRLD CRPD STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLA VCE DRG1
POD DSX VMD CMSD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUA DPUA DNDD CFXA ARHA FITD CLTD ASCD
CPFD CPTD ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN CDMR
CPND_LANG ENG
RCO 0
HUNT 8580
LHK 1
LPK 0
PLEV 02
CSDN
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17 TRN
18 AO6
19 CFW 16
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27 CLT
28 RLT
29
30
31
DATE 2 JUN 2008
 
Hi mkrice2,

As a general statement all numbers must be unique within a node or system. Therefore within the 3 option 11's the numbering scheme must be unique within each individual system.

You cannot have a DSC and an SCR with the same number in the same node or system. The idea for the DSC is to tell the system where to send or find this particular number or digit string outside the existing system.

It sounds like you are trying VNR but am not sure ?

Hope this helps...



TGD



 
redo thar cdp with the 841 in it. Your not building dsc and then trying to have that as a dnb on the same pbx are you?

if I dsc 84

I can't have 84xx

84xx is built on the receiving end that my dsc points to

Mato' Was'aka
 
No, I built the 84XX on the receiving end that dsc points to.

I just can't seem to key the 3903 programmed with that dn of 8417.

So do I need to out the dsc in site 2 where I want the DN to show up? If so, how?

TIA
 
BigIndian is correct,

In site 2 you need to out DSC 841, and build new steering codes for 8410, 8411, 8412, 8413, 8414, 8415, 8416, 8418, 8419. Then you will have 8417 available to use as a local DN, and still have routing in place for the rest of the 841x numbers.
 
OK, so I outed 841, keyed the number up on the 3903 set at site two. Now, if I have any 841x numbers that are suppose to ring, will they?

TIA
 
So here is my next question.

I've got the above working thanks to BigIndian, now I need to move 4 more extensions the same way. I don't want to build physical phones but have them appear on the newly built 8417. What are your recommendations?

Thanks again BigIndian. I have read hundreds of posts in this group and you are spot on.
 
Any DN can only appear at 1 site. If you have a DN at site A that you want to move to site B or C, you must:

1. out the DN at site A, build it as a steering code to the proper tie route.

2. At the site where the DN is moving to (site B or C), remove any conflicting DNs of shorter length, and rebuild steering codes for the gap you have created.

3. Program the DN at the destination site.
 
mkrice2 (IS/IT--Management) 2 Jun 08 14:52
OK, so I outed 841, keyed the number up on the 3903 set at site two. Now, if I have any 841x numbers that are suppose to ring, will they?
If they are at site 2 then yes. But DSC 841 at site 2 was saying that any calls to extension 841x are to be sent via RLI 13 to site 1 so it's a fair bet that site 2 has no other 841x numbers.

But, if you still have any phones with an extension of 841x at site 1 that folks at site 2 need to dial as a local extension then, as allenmac said, at site 2 you'll need to build new steering codes for extensions 8410/8411/8412/etc. You'll have extension 8417 available to use as a local DN at site 2 and still have routing in place for the rest of the 841x numbers at site 1.

Regards,
Harry
"The legitimate powers of government extend to such acts only as are injurious to others. But it does me no injury for my neighbour to say there are twenty gods, or no god. It neither picks my pocket nor breaks my leg." --Thomas Jefferson
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top