MICS Cleanup

[alycera]

Still struggling with clearing out number ranges on our MICS. I'm trying to clear the 5xx range in order to use it as a destination code for routing to another MICS at another location. We are already using 4xx for a different location. I found a lot of b2 DNs in the 5xx range and changed them out. That seemed to work fine. However, I have sets designated in that range as well - a lot of them. These sets don't exist. I also believe they're associated with ports that don't exist either.

This system previously had an additional station module and an additional trunk module that have since been removed. The system still shows the ports, though. Shouldn't those go away when the modules are removed? Do I need to de-provision those modules in order to free up the phantom sets?

If not, is there a procedure to delete these sets? I just want them to go away. I can't seem to do anything with them since I changed all the DNs. Now their DNs don't even exist in the Port/DN mapping under maintenance. The only way I can see them is in "Terminals and Sets". However, I just can't seem to find a "delete" option!

Any thoughts?

 

[ajntek]

When you go into port/dn statusa and look at these dn's what port numbers are associated with them?

 

[alycera]

Thanks for the reply . . .

Since I changed all the 5xx DNs, I now cruise straight from 399 to 601 when looking at the DNs. They're gone from that view. So there are no port numbers to view.

However, if I go to terminals and sets and choose set #521, the set comes up! (As well as 50 or 60 others in that range). That's obviously why a 5xx destination code won't take for anything above 520. Again, no DNs show up in the port/dn status view though.

 

[joelunchpail]

i have changed dn's in the past and when looking at the old port if it is left unused it still shows the old dn number, so it shows eg. dn265 on 2 ports.but it didnt seem to affect anything as soon as a set was pluged into that port it assumed the new dn.
Have you tried (and i dont know if you can) disabling the unused ports. or maybe re booting the system might force the system to re assign those ports their new dns.


good luck

 

[alycera]

Thanks Joe,

I've looked everywhere I can think to disable. Haven't been able to find it. I also rebooted thinking that would reassign the ports -- both with set relocation on and with it off -- no luck.

Here's where I'm at now -- I dropped back ten and punted! They were using a line pool access code to activate a trunk for overhead paging (i.e. dial a "7" and it automatically opens up a line straight to the paging amp). That tied up all the 7XXs. We agreed that they can program a button for paging and dispense with the "7". That freed up the entire 7XX range so I tried "Change DNs" once again and was able to bounce all those "sets" into the 7XX range. The 5- destination code took with all ranges assigned and it appears I'm OK. The acid test will come later this week when I travel to the other location and bring it all together. Say a prayer for me!

Thanks folks!

 

[MarvO1]

The other thing that you might want to consider if you need your 7's back is to go to a 4 digit dialing plan. That will free up a lot of numbers for you. 4 digit dialing is so much easier if you are networking more than 1 KSU.

MarvO said it

 

[alycera]

I also thought about freeing up more numbers by instituting double or triple digit line pool codes. I assume that can be done, right? (i.e. 81 for pool B, 82 for pool C)

For the time being, I'm able to dispense with the access codes by burying the fuctionality into the routes/destination codes. All the users need to know right now is to use a "9" for outside calls.

4 digit dialing is on the table, but this is a low tech office (meat packing industry) that is fairly resistant to change. I believe with the solution at hand, it'll be almost transparent!

Thanks for all your help . . .