MICS Extension Numbers “XC” System

[Jason24]

I recently upgrade the software and added a second fiber card on a MICS to add additional station modules. The first fiber card (on the right) has three trunk modules on the top three fiber ports and three station modules on the bottom three fiber ports. The current extensions are 221-300. After connecting one of the new station modules to the bottom fiber port on the second fiber card (on the left) the extension start at 477. Is this normal or is something not right? Is there a way to have them start at 301?

Thanks,

Jason

 

[hawks]

If you move the trunk mods to the second fiber and put the station mods on the first.

 

[hawks]

Sorry I don't think the trunk mod can go on card 1

 

[Jason24]

I haven't tested it, but I'm pretty sure like you said, the trunk mods have to be on the first card on the right. Even if they could be moved, the number sequence would still be off between the two cards (300+(16*3)=348).

Jason

 

[allworxguy]

You don't say which MICS version you have. But in any case, that is correct you can only put trunk modules on the 1st expansion card.

The reason there is a skip in DN's is because of the B2 DN's on the KSU and existing expansion ports including the ones reserved for the ports being used by the trunk modules.

KSU + 6 port expansion module have reserved 96 B1 DNs 221 -349 (these are the primary DN's that you program and call). In addition to these DN's, 96 B2 DN from 350 - 446 have been mapped.

Therefore the 1st B1 DN available to the new expansion card is 447 (why it comes up as 477 I'm not sure or is this a typo?)

The only way to correct this is to restart the system.

One thing you can try is unplug the lowest trunk module (mod 6), plug in your new station mod and let it come up (should be DN's 301-317, turn on set relocation, unplug the station module and re-plug it into the new expansion module and re-plug your trunk module. My only concern is you may lose the programming on the lines in the trunk module. Not sure if this will work but's worth a shot.

Or you can use Change DN old 477 new 301.

Marv ccna

http://www.telemarv.ca

Sales, Installation & Service for Norstar, BCM & Allworx
Serving Ottawa and Eastern Ontario since 1990

 

[Jason24]

Software version is 7.1.

Will preforming the system restart as you suggested cause any programming to be lost when disconnecting the trunk module?


Jason

 

[allworxguy]

restart will default and require a complete reprogramming. It will correct your problem though.

moving the modules around only requires a reboot.

Marv ccna

http://www.telemarv.ca

Sales, Installation & Service for Norstar, BCM & Allworx
Serving Ottawa and Eastern Ontario since 1990

 

[hawks]

You don't have to do a restart to change the trunk mod. all you need to do is disable the mod in software, remove power from TRUNK MOD, put in the statiom mod and power up, go and change the mod in Hardware then Enable.
But you might be able to just use Change DN to do what you want, you can change a Range of DN's.

 

[Jason24]

Therefore the 1st B1 DN available to the new expansion card is 447 (why it comes up as 477 I'm not sure or is this a typo?)

I just double checked, it's definitely starting at 477.

Does it matter that both fiber cards are combo cards?

restart will default and require a complete reprogramming. It will correct your problem though.

Are you saying a power cycle will default the system with the new hardware connected?

Is there any downside to just doing the change DN method?

Jason

 

[allworxguy]

Power cycling probably will will not affect programming. I say probably because as they say sh!t happens. You should always have a current back up available. CAUTION NEVER REMOVE AN EXPANSION CARD ONCE IT HAS BEEN INSTALLED. This will result in a defaulting of the system and changing SYS ID resulting in any installed keycodes becoming inoperative.

A restart: F**STARTUP will default the system. See the above caution.

Does it matter that both fiber cards are combo cards?
No

Is there any downside to just doing the change DN method?
The only downside is the mapping of port - DN is no longer default, which can be problematic in the future. Change DN and Set Relocation are features put in for non-technicians to move phones around. We rarely use them because of the mapping issue.

Also, Hawks is correct power cycling is not required to move modules around.

Marv ccna

http://www.telemarv.ca

Sales, Installation & Service for Norstar, BCM & Allworx
Serving Ottawa and Eastern Ontario since 1990

 

[Jason24]

There aren't any installed keycodes for PRIs or anything, but the system is relatively large and I would rather not have to reprogram from scratch (I assume and backup & restore would be useless in this situation?) I'm honestly thinking it may be better to just leave it as is unless you think that may lead to problems down the road.

Jason

 

[hawks]

Leaving them as is will not lead to any problems other than maybe someone complaining why does my extension start with a 4. You can change the DN also with no problem just follow Allworxguy's lead and make sure you document the new port dn locations. Either way should work for you.