I got it to work to ring a HG with a user in it, but Zeacom uses a HG with no users in it. When you dial 888 you get Zeacom VM. But on my test system it only dials 888 if i have an actual user with a phone in it. Since the Zeacom is tied to the IPO through analog ports I'm trying to get a HG...
BAS1234- Do you have the file that made it happen on your phones? I've tried it like we discussed at pressing the button will not send the user to 888.
Shawn -Fort Worth
ACIS - SME Communications
IP Office
On site now, and can't interrupt service again till after hours tonight. I'm afraid the problem I'll have is the file even says, "## Note:
## This parameter setting is ignored for extensions
## configured as 96xx station types on the call server."
I'll try a few things tonight. I can't adjust...
The 46XX file reads,
## Voice Mail Telephone Number
## Specifies the telephone number to be dialed
## automatically when the telephone user presses the
## Messaging button. The specified number is used to
## connect to the user?s Voice Mail system.
##
## Note:
## This parameter...
We needed the VM Pro to set up an Auto Attendant menu to password protect the conference bridges. We have it turned off now due to the VM button on the 9630s and the softphones confusing people. I'll try the group setting in the morning.
Avaya says it is the responsibility of the DevConnect partner and Zeacom (the DevConnect) says they don't have anything to do with programming the Avaya equipment. So while they point their fingers at each other my customer can't use the button. The 46XX file that I would think we need to...
We have a new install with an IP Office 500 V2 with 7.0.23 but we are using Zeacom voice mail. I need to have the Message button on the 9630 IP phones to transfer to Zeacom VM at extension 888. Would also like to be able to rout the same feature for the softphones.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.