sundance-communications.com Forums Telephony Discussion Phone & VoIP Systems NEC Telephones & Systems 2000 ips IM-16 no voicemail light on phones and pilot problems

This particular phone system has been beating us up for a while. 2000 IPS w/ cp24 cpu card, about a dozen digital extensions and 200 analog. We had an AD-40 that handles voicemail for the digital extensions but we could never get voicemail integration to work. I have had 3 different tech companies look at it and all of them have been scratching their head.

I have confirmed the cable is good by moving the cable to a different site with an AD-64 and MCI works.

I ended up "finding" a gently used im-16lx card with software, license, manuals, for cheap so I decided to move from this ad-40 that was built before I was able to sustain conscious thought. (Like come on, the internet doesnt have much info on OS/2 WARP anymore)

So I went through the install, followed the manual step by step, set up the group, a test vm box, etc... The hardest thing was moving the extensions on len000-007 to somewhere else and waiting on backups so I could undo things if it went south.

The only steps I didnt follow was to tell the system to use MCI. after I determined that it wasnt working, I went through the MCI instructions and connected everything and that didnt work either.

Does anybody have any ideas on where I should look for this? I cant find any documentation or any similar problems. Because we have had multiple hands working on this problem I think the problem is the phone system has a few settings out of whack, and the instructions assume the settings are defaulted.

Or maybe I have a bad CPU card?

2nd problem: VM pilot is 3000 on len100 (first port of an analog cards in pim1, my analog cards start at len101 onwards.) and the vm extensions are 3001-3004 when they were on the AD-40, and now are 3001-3008. Whenever a user dials 3000 to access voicemail, it asks for which extension do you want to call. When you dial 3001 it asks for a pin number. Basically the system sees that the caller when you dial the vm ports directly but not the pilot. After setting up the group via the IM-16 documents dialing 3000 would error, so I had to e600 3000 > 3001 but im sure thats the wrong way and my group might not be set up correctly.

Or should I set the pilot to 2999 and ports from 3000-3007?

Sorry for the wall of text.

First things first, do you have an Ap00 card or are you trying to do the MCI via the CPU?

How is the hunt group set up for the voicemail?

How are you connecting the AD40 to the telephone system?

Forgive me if some questions are a little basic but I have little experience with the AD40 as it didn't really hit the Australian market (that I remember) but all VMs are basically the same in most aspects

Well the AD-40 is the old system which we are trying to decomission. Trying to move to the IM-16 because we thought the problem was with either the MCI link or the AD-40 box itself.

We were trying to do MCI via the CP-24 cpu card. AD-40 was hooked up as 4 digital lines and a MCI serial cable. No AP00

And basic is fine, Im a voip guy that doesnt know much about these systems myself.

The goal: VM indication lights working with an IM-16 card.

for the hunt group and full email setup, (I save all of my moc commands so I have a papertrail to go back to):

I think the E600 might have been the wrong thing to do, or maybe I have to pick a LEN that doesnt have a card plugged in, or I am missing something for the group. Thoughts?

All of this was pretty much verbatum from the "neaxmail im-16 lx installation guide"

After this failed attempt I shut the card down and then pulled it out, then power cycled the system so my changes werent saved. (I do have a backup before I did this.)

My plan was to fire up another cabinet and new cpu card and single digital card and start from scratch to see if i could get it to work.

MCI programming documents are at www.nectekhelp.com
Make sure that your MCI cable is a rvs cable. Confirm it by reading the white label taped to one side. A norm cable is for a modem. In a pinch, a MAT cable will work.

Basic question but you say the problem is the VM lights, have you checked Cmd 1303 for the extensions?

3000 didn't work because you missed telling it which group it is in in cmd 172

Oh and then in cmd E50 set 3000 to 0

Don't miss the fact that your Dterm stations for voicemail (3001-3008) will need to have the buttons programmed in a specific manner to interface with the IM16, also make sure CM93 and CM13 is set correctly for those ports.

D

As soon as I return to this site next week I will try everything listed here as I think it might work because I dont specifically remember doing some of the things everybody suggested. I would do it remotely but its kind of hard when the card itself is on my truck. -_-

And I am trying NOT to use MCI. I dont want to have to plug a cable into the cpu card to go 6 inches to the im-16. according to the manual the default config doesnt use MCI and that MCI is optional. Am I misunderstanding what I want to do?

Thanks for this R4+Z. I set this and removed e600>3000 and it now asks for a security code instead of dial an extension. This has been beating me up for a while.

I ran out of time today so Ill be back up here later in the week to swap back over to the IM-16 and see if we can get the indicator light working.