sundance-communications.com/forum Forums TDM Business Telephone Systems NEC Telephones & Systems 8100 UM8000 programming

Hi all, I don't post often. I have been working with NEC 2400/2000/electra, Nortel, Shoretel, etc. for 15+ years but I am a little new to IPKII/8100.

Anyhow, I just started setting up my 3rd one in my lab and I first upgraded the 8100 to 2.0 and got the UM8000 upgraded to the latest version also.

Then I logged into the voice mail via web and initialized it, telling it the 16 ports behind the UM8000 blade.

Then, I noticed the IP phones had a VMail key and that webpro showed a VM pilot of 3999. Sure enough, it seems as though no further VM programming is necessary on the 8100 side? Is this right?

I know the last 2 8100 systems I installed I had to program, hunt groups, etc, per the UM8000 install manual.

Thanks for any input about this. I am unsure if I should just leave it alone since it seems to be working or go through the programming steps in the UM8000 installation manual.

There is a wizard for the VM integration, it sounds like this was ran? On my 8100's with ver 2.0 I still need to build my department group. I prefer to do this anyway so I have cookie cutter database's.

Thanks for your reply. I swear I didn't run any wizards (just the voice mail setup where I typed in the 16 extension numbers for the ports) If I look at 8100 programming with webpro I now notice that department group 64 was created and also department pilot 3999 assigned to the 64th slot of 11-07. I think this must be new for 2.0. It wasn't immediately apparent to me that DG #64 was being used until I saw it referenced in 45-01, but now that I see the basic programming is in place I am not going to mess with it.

Can you check one of your 8100r2 systems to see if there is any DG #64 programmed that maybe you didn't notice?

Maybe this has to do with the way I initialized my system also.

I put all blades in the system first.
1:CP00
2:PRI
3:8+8LC
4:VM00
5:4COT
6:EMPTY

Then I stuck a USB with 2.0 software and turned system on with load button held for about 10 seconds. Waited for upgrade, pulled USB and rebooted.

Maybe if I loaded the system without the blades it might not have automagically programmed things for me. I know the IVS2000 works this way with the C-load and I always make sure to B-load (or sometimes C-load with all cards unseated) so I can program from scratch and not have to wonder what the system might have programmed for me..

I'll have to try that. Since the IPK II was released I was trained to cold start the CPU 1st, then insert my cards/blades one at a time. This prevents the ports from not lining up right in the database.

Remember with the 8100 just about everything is open including 16 voice mail ports for 60 days, after that if nothing has been licensed its not going to do anything.

FYI, I have a cheat sheet on disabling the extra ports that come wih the 60 day license. This helps especially when port count is important. Also you do have to build the voicemail ports, i.e. department group, hunt, members etc. I have built many IPK11s and SV8100 with this voicemail. If you would like I put together a easy cheat sheet on installing the IPK11/SV8100 and when I'm at my home computer I can email them to you.

Hi thanks for the offer, but I have now confirmed (myself and with NTAC) that this is correct behavior and the 8100 correctly recognizes the UM8000 blade and programs a working department group with members, etc. as dept. group 64. Of course, this is only true if you initialize your 8100 with the blades inserted.

I think you are right and it is prudent to delete ports that are not licensed. For example, redo the voice mail department group for 8 ports if that is all your UM8000 is licensed for. I would love to see your cheat sheet re: licenses.

I noticed this as well with my last 8100 install. I usually delete the default info though and reprogram anyway. We typically use dept group 10 and pilot of 200 or 300.... not a big deal.

D