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!

Resolving Conflicting Destination Codes

Status
Not open for further replies.

edoo

IS-IT--Management
Nov 18, 2003
22
US

I'm stumped creating a destination code of 419. The system will not take the last digit 9. The system accepts the 4 and 1 but not the 9. I've looked around the system for conflicts and have resolved all that I have found.

Here's where I have looked:
• Target Line Rec'd # for lines 157-284
(419 was programmed as the Rec'd # for line 179 but I removed it.)
• Call Park: 1
• External Access Codes: none
• Direct Dial numbers: DDial1 is internal to 221 all others are none
• Line Pool codes: 88
• Set Numbers: 221-348 & 637-706 (we only use up to x292)
• DISA DN: None
• Auto DN: 350

One more interesting note, the first available destination code after 400 is 477. The numbers 400 to 460 are all programmed as Rec'd # for target lines. These Rec'd numbers are all part of DID blocks that we have.

DID Blocks sending 3 Digits
• Block ending in 400-419
• Block ending in 440-499

If you're curious, the destination code will be used for sending the DID 215-4419 to a route that sends it over the T to the other site. This method has worked for other DID ending above 477 but not below.

Does anyone have an idea where more conflicts might be found? or why I might not be able to create this destination code?


Thanks for taking the time to read this post!


Current Setup
• MICS 6.0
• MCDN 4.0
• PRI
• T1 (p2p to other site)
• 6 Port Expansion
• NAM rel4
 
try going into port/dn status and put 419 in as a dn and see if it takes it then what it is.

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

Mind like a Steel trap - Once used forever clamped shut.

 

Port/DN staus for DN 419 comes up as:
Port: 0507
State: unequipped
Device: None
B1: 420
B2: 292

Hmmm... What if I were to disable it?
 
Don't know if the code becomes available for other uses if you disable the port.... one way to find out... try. Report back if it works.
 
You could try a dn change on that to an unassigned number, don't use a number that already exists even though the state is unequipped.

----------------------------
JerryReeve
Communications Systems Int'l
com-sys.com

Mind like a Steel trap - Once used forever clamped shut.

 
Sorry... my last post was incorrect.
(I was looking at DN420)

Here's the correct info

Port/DN staus for DN 419 comes up as:
Port: 0507
B2: 419
State: unequipped
Device: None

Pressing the >B1 gets:
B1: 291
State: idle
Device: ATA

Interesting note... the highest DN that the system accepts in the dn status is 476. Is this coincidental to the first working Destination Code of 477? Very interesting...
 
Disabling port 419 does not seem to work. The Destination code is not accepted.

So.. Next I thought I would try changing the DN.
I checked the status of the dn 461 and nothing came up.
I figure it would be ok to use... I hope.
After the change, the status of 419 came up with nothing.
DN461 came up as unequipped.
Looks good so far.
Now for the destination code...
Hmm... the destination code 419 still can't be programmed.

Thanks again... Can you think of anything else to try?
 
It turns out that you are all right. 419 is a valid DN.

I did a little reading and found out that on a 6 port expansion cartridge, B1 DNs go from 221 to 348 and B2 DNs go from 349 to 476.

This is why the first Destination code I'm able to use is 477. I guess it's impossible to create destination codes between 221 and 476.

Back to the think tank for me. I might post my DID problem soon. Maybe I can get some other ideas.

Thanks for all your help! It's much appreciated.
 
the fix will be to renumber the extensions

you cannot have destination numbers and extension numbers as the same, as jerryreeve says
 
I'm wondering if you found a solution to this problem yet. I'm trying to do the same thing, and not having success. Please Reply.
 
Nope.

This was part of a bigger puzzle in routing DIDs to other offices. I've gone about solving the destination codes by not using any codes that are valid DNs. I'm using Destination Codes 477 and higher. Seems to work ok. Not ideal but it works.

Dcnsan, What Destination Code are you trying to create and what are your end goals?
 
If you change DN 419 to somthing that is not used then you should be able to use it as a Desti Code.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top