Inherited MICS 8x32 + startalk flash + 13 7310 gets re-applied 2

[o6efb]

I recently inherited a norstar NT7B53 chassis with 2 ea NT7B75GA-93 4 loop modules. The software cartridge says release 1 T1 and so far everything leads me to believe its correctly identified. Also included were 13 7310 sets.

If anyone could help with some general questions for a newbie to norstar equipment (I've administered an SL-1 so I'm familiar with ports, DNs, TNs, DISA, etc just never worked on any equipment that didn't weigh several hundred pounds.)

Q1 - the 7B75 module seems to be available in 2 varieties, one that supports CLID and one that doesn't. Is there a positive query to do from the config prompt prior to changing the answer timing and set info for CLID (old users' trunks didn't have CLID but new user has it). From what I can tell the R1T1 software supports CLID but my trunk cartridges may need to be upgraded.

Q1.5 - Before setting up all the sets and VM trees is there a good reason to upgrade the software in this? In fact, can 7.1 even be put into a frame that has run R1T1 for over a decade? If I did have to upgade the 4-loop cartridge to get CLID can I mix a CLID-able 4-loop with an older non-CLID 4-loop cartridge? Only 3 of the 5 new customer's lines have CLID so having 4 trunks with CLID capability is more than sufficient but nowhere do the manuals make it clear that mixing trunk cartridge variants is a valid setup.

Q2 - There is a DISA configuration prompt in the programming menu which doesn't make sense if you have 8 loop trunks and no DID. Without converting to a DID trunk system is there a way to implement DISA features even if one incomming line had to be permanently allocated to DISA?

Q3 - And last but not least, an important function of this new installation is not the typical sets and lines usage rather using the norstar flash VM to transfer calls to outside lines, for example having the choice to leave a voicemail message or ring a cellular phone. One line is sort of reserved for that purpose already by the customer. Any good advice on how to accomplish this in the voicemail programming would be appreciated.

And yes, I really would like to have a cliff notes or idiots guide to norstar for telecom professionals but the people on this forum have had the best possible answers so far on the internet - thanks for your time and help!

EFB

 

[curlycord]

1. List the card #'s if need help to determine, programming wont tell you.
7.1 can be used but requires Release 2 NVRAM cartrige.Cards can be mixed in any slot.

2. What part did not make sense? Not sure why you would need to convert to DID.

3. CCR can transfer External if their is an option.
F983/OTHER/CCR/ADMIN/PATH1/cahnge to Transfer/Ext (External)

=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[HughRunyan]

First CID is not available on R1 T1 that i know of You can upgrade to 7.1 But this is the tricky part you ether have to upgrade to 3.0 first or do Feature **startup and as the system is applying template Power the system off and replace the feature card. As for the CID card you can mix them without any trouble To setup outside transfer you will need to build a ccr tree and set one of the option to external transfer to set a trunk to answer with DISA in trunk config set the trunks to auto answer and then with DISA to use the remote access feature you will have to set this up as well

 

[curlycord]

To upgrade to 7.1 you need 2 upgrade tools, best to reprogram from start.
R1T1 does support CLID however a note that vesions R1T1 to 5.1 will only allow one set to Auto show call ID, all other users would need to invoke F811.
6.1 and up will allow any amount and not restricted to one set.....sets need to have lines Ring at the set to auto show unless call is transfered by a set or vmail.
Also if setting up vmail AA to answer (instead of human) make sure it is set to answer at 2 rings to let Call ID pass from the Telco between first and second ring.



=----(((((((((()----=
curlycord

http://www.curlycord.com

 

[o6efb]

Curly/Hugh -

Thanks for your fast response. As for the card numbers:

MICS
Software cart NT7B72FA-93 (F could be E the label is so old - Above it says Release 1 T1)
slots 1&2 (skinny ones) VACANT
SLOT 3 NT7B75GA-93 rel 02B (NEW LABEL)
SLOT 4 NT7B75GA-93 (NO REL #) (OLD LABEL)

NORSTAR FLASH
CHASSIS NTAB2456 0006 REL 01A NNTNM040E8SYZ 1999/11/09
FLASH 4CH. H/W

(Flash) SOFTWARE CARD NNTM040E7LGD 1999/11/02
NT5B78EB 0002 Rel 02
E/F FLASH VM 2.0.10 FEAT CART
MADE IN CANADA 2001/05

(Flash) expansion
NNTM040E8QFP 1999/11/09
NTAB2385 0003 REL 01B
EXPANSION CARTRIDGE 2001/05

The flash unit was recently replaced when the [OLD] original 2-port flash box in the system went belly up. It was wired into the system on ports 132 and 131 with 2 line cords, center pair only, but was clearly marked a 2 port unit.

Can anyone tell from the numbers if the new (replacement) is a 2 port or 4 port voicemail? The original wiring into the MICS was left alone when it was replaced, and only used the center pair of each RJ14 cord. I know they paid around 1K for the replacement flash just a few months ago and am not sure if they bought a 4 port or 2 port unit. The chassis on the new unit makes reference to "4 ch h/w" which might suggest it is a 4 channel box.

As for determining the external ability I built a quick and dirty CCR and found that after a CCR was defined it had an INT EXT prompt followed by the prompt

LINE POOL NUMBER - so I am confident external calls can be handled by VM with proper tree programming

I'm curious now if this VM has 4 ports. I should probably add the other two if they exist by copying port 131 down to 130 and 129 and wiring up the second pairs on the RJ14 assuming that is how a 4 port flash is installed (My VM experience is limited to OCTEL systems so any help would be greatly appreciated on the wiring interface.)

I'm also a bit confused as the MICS refers to the lines "normally" for me i.e. 001 002 003 004 025 026 027 028 but the flash just numbers the lines 1,2,3,4,5,6,... - is there a mapping between MICS lines and flash lines?

Regarding DISA - I downloaded a bunch of PDFS and at least two made reference to requiring a trunk card called a DID/DISA to make use of DISA. The reference in programming on R1T1 to DISA is under A) configuration -> 5 Miscellaneous -> DISA DN: XXXX. None of the trunks have ever been set to auto answer, they all went directly to the auto attendant and company directory for direction previously. My inexperience with KSUs is showing here as all my SL1 incomming lines were DID trunks, so setting up DISA meant assigning a DN that would arrive on the DID line and become the DISA inbound number. Perhaps I should read more on auto answer trunks.

In thanks for your fast help - a bit of (old) telecom humor. One weekend I had scheduled with my NT rep to upgrade our SL1 from analog sets to the much more space efficient digital sets & line cards. This meant pulling the end off the SL1 chassis and powering it off, something that had never been done before, then installing the new digital line cards. The old chassis end had to be moved over, so the NT rep came in and deconfigured everything, pulled out all the cables so that part was dead and unbolted it, then told me to go ahead with the physical move and page him once it was out of the way to upgrade.

3 hours prior to the shutdown I had gathered a crew to push the old end off the row of Sl1 cabinets and looked between the gap to see there were no 25 pr cables left thanks to our NT rep's hard work. As they were pushing it everyone stopped and called me over as there was one pair - a wht/blu - still wired between the dead expansion bay and the main SL1 which was still powered up, running, and not due to go down for 3 more hours.

I assumed it must be one analog line someone snuck through the chassis for neatness to avoid the bix frame and wire a wall phone in the pbx room. I'll just cut it and figure out later what TN / DN it had and configure a new digital set. I snipped the 24 ga white/blue wire and suddenly the entire phone room went from roaring like a jet to dead silent - you could hear a pin drop. All the phones were dead. I ran outside to my car and paged our NT REP with a -911 as a crowd of angry users were gathering around the phone room. (yea this was the day of pagers and car phones) - he called right back and I explained he left one pair connected and when I cut it everything in the room died at once.

It turned out that one innocent white/blue pair was the EPO circuit and went from cabinet to cabinet then back to the recitifier & battery room to kill the -48VDC. After closing the EPO circuit it took an hour to restore communictions to 9000 users whos phones went down 3 hours early.

I never assume anything about any pair now unless I verify it with someone who knows, hence my questions to the group.

Thanks again for your responses. I'd prefer not to buy new software if I can avoid it and just upgrade one trunk card since outbound lines are not going to need CID. I just don't want to violate any configuration rules or software limitations.

Your responses are very helpful - anyone who knows what my VM system has or doesn't would be greatly appreciated now. Unfortunately my manuals were mostly just scanned and can't be searched (attempts to OCR them were a disaster - I have a few that got OCRed and look like they were encrypted instead)

EFB