It looks like the problem was not fixed, just delayed. Strangely, it only happens once every few days and I can't find any rhyme or reason for it. The event logs never show anything. Does anyone have any further suggestions for troubleshooting or fixing? Thanks.
My letters were garbled and unreadable too; if you navigate to the program directory and right-click on the voicemail executable, you can go to the Version tab and find out what version it is.
For what it's worth, downgrading to 3.1.15 has worked flawlessly so far. I'll keep my fingers crossed.
I have VM Pro version 3.1.15 already downloaded and convenient to install. Should this version be fine or are there any known issues I should be aware of with it?
VM Server is running Windows XP Pro SP2, it's a P4 2.8Ghz, 256 MB of RAM.
Thanks for your help.
Occasionally Voicemail Pro will stop responding and any calls that are directed to Voicemail simply drop. From the computer running Voicemail Pro I can see that the service is unresponsive. I'm not able to stop it from the services.msc console. I have to manually kill it and then restart it...
Well, that's stupid.
Is there a reason Avaya doesn't think anybody would be interested in this kind of information for a hunt group with normal users? Or does another product exist that I should look into?
At the very least, what I really want is a product that gives me a good view of who's...
I installed CBC using a demo license from our Avaya reseller. It starts fine and appears to connect to the phone system, but when I go to select groups to view, none of my hunt groups show up. The only groups that show up are "trunk groups" that include all of our Small Community Networking...
We were doing IPSEC as well, with a Sonicwall TZ170 on one end (the end with the IP phones) and a Sonicwall Pro 3060 on the other (with the control unit).
The problem cleared itself up after we moved from a VPN over cable modem to a point-to-point T1. So, at least in our case, it didn't look like it was a software, control unit, or configuration problem, but just some really strange network issue.
I tried to upgrade an IP 406 last night to 3.1(29) and the upgrade failed; had to go on-site and use the DTE port. I don't know if it was just bad luck, but even after erasing the config it wouldn't boot with the ip406.bin included with the CD download. So, anyone who hasn't tried this, you...
I have a problem with dialing out on a PRI line with my IP softphone. I can dial internal numbers or receive a call and everything works fine, but if I dial out my calls terminate after 1 minute and 36 seconds, give or take a second or two.
When I watch in Monitor, I see an error line:
ERR...
I just set up a new call flow at one of the sites I administer. One of the features is an auto attendant that, when a number is pushed, goes to an assisted transfer to a number; no answer or busy does an assisted transfer to another number. If that one is not answered or busy, it transfers...
I'm in a bad predicament now. I guess it's from trusting vendors too much, but I have several systems in an SCN setup, and some need to be 3.0+ for 5410 support, and some apparently need to be 2.x for 4400 support. Will there be any SCN issues with running 2.x and 3.x systems on the same...
I recently upgraded our systems (IP 406 and IP 403 systems) to 3.0(59) from 2.1(27) and I've found that the 4400 phones stopped working. The 4406 and 4412 sets are just fine. Is there a guide somewhere to how these have to be programmed in 3.0? I've tried checking and unchecking idle line...
Working in what way? I can dial extensions on other systems, and it'll pop up the user names, but it won't ring on the other end. Going from the other systems back to the new one, it'll ring, but no sound will be transmitted.
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.