Partner Caller ID just says VMS all the time??

[kurmann]

Just put in a new ACS release 5.0 with Partner Voice Messaging PC card Release 3.0- Automated attendent picks up immediately- Everything is great except the caller ID always says "VMS" at the individual extensions when the call is transfered out of voicemail and onto any extension, Is there a way I get it to let me see the caller Id information? Any help would be greatly appreciated.. Thanks, Kyle

 

[telprog]

You should not let the Auto Attn. answer immediately, set it to 2 rings as the caller ID needs at least 1 ring for the info to come in. Also make sure you have #206 set to assigned and not VMS Line cover.

 

[kurmann]

I talked to a technichal support guy at Metrolinedirect.com and they said the caller Id will not go through the automated attendent unless I have a release 6.0 processor? anyone know if this is true or are they trying to sell me some more stuff?

 

[ttech]

you have to set the answer delay for 2 ring as stated above to let the system "get" the caller ID and after it is transfered to the extention it takes AT LEAST another 2 rings at the extention to see it. You can also press the line button that is ringing to see it sooner.

And yes it is an issuse that was resolved in R6

 

[telprog]

I use R5 in my office, caller ID comes in fine, but you will have the set the rings to give it a chance to send the info.

 

[392]

"Caller ID delivered to station when transferred from Auto Attendant" is what Avaya is touting as a new feature on R6.

The trouble with previous releases was that CID was not always forwarded on transferred calls, but was on held calls. Why, I have no clue. Some previous releases seemed to allow for xfered CID, but on an irregular basis.

I guess they figured out the bug and now it's a "feature". (que Microsoft rant here)

 

[kurmann]

Thanks for the help guys- for some reason I can't seem to get it programmed off of immediate automated attendent pickup though.. Went through the programming #506 about 5 times with the customer and no luck.. Guess I got to drive out there.. Thanks all

 

[telprog]

Are you having him use 1 for day and 2 for night? dumb question I know but had to ask.

 

[kurmann]

Yep- Had him press 1 for day mode and we set all the lines at 2 rings, and it seems like we would of fixed the problem, but for some reason the auto attendent still picks up on the first ring-

Any Chance that you have to specify to the system what specific hours of the day are considered day mode and night mode? We left night mode on immediate pickup so who the hell knows.

I respect the hell out of all you programmers out there (I guess I know why you charge so much now)- so many things you have to deal with, I'm just an install guy trying to save a few bucks by not hiring a programmer..

 

[392]

Ahem...you DID remove ringing from the voicemail extension ports, didn't you?

 

[TouchToneTommy]

As long as the voice mail ports are in hunt group 7, it is not necessary to change the ringing assignments. Even though it looks like they have immediate ring when looking through centralized telephone programming, the CallDistGroup and Hunt Group 7 parameters take over. No call rings to a VM port unless it is in #206-7 and has rung the number of rings in #506. You can test this by programming station ports on a 206 or 308 card into hunt group 7 and playing with them using a butt set.

 

[392]

Yeah, that's the way it's supposed to work, but I never rely on the system to cover my rear for programming steps I should have made. I'm too anal about things like that. How many of you guys remove ringing from extension ports on modules that don't exist? I can't help myself.....!

 

[itpphoneguy]

Hi 392,
Yup, I do to. Never give a program a chance to mess up. I had ext 76 answering intermittently until I removed line apperances. Go figure.
-Chris