I upgraded to IP 4.2.20 and VM Pro 4.2.32
When I call in the auto attendant picks up and then I dial a extension. But happens and 5 secs later I hit 0 and then all the phone rings because 0 is the All phone rings hunt group.
Has anyone experience this problem?
I think I found a fix. In 4.2 VMPro has an option to time out each call received. If no activity in 2 seconds it will drop them but it gives you a few retries before dropping.
Thanks everybody.
Hi,
How can I setup VMPro to drop a caller after they timeout like 3 times in the auto attendant menu.
Currently I am having phantom calls that are stuck in the auto attendant and it is taking up a line. In order for me to free up the lines I have to reboot the systme.
Many thanks
Hello,
I am currently experiencing odd disconnect behaviors. When someone dial my extension and others extension, it rings 1 time and disconnect. It happens over SCN and direct extension dialing. Has anyone experiencing this problem too?
IPO-4.2.4
Thanks
Millsey,
I think the upgrade did do something. Because I upgraded my VM Pro server to the latest patch.
The best resort is to swap out the USB for a Serial dongle. Its fairly inexpensive and can saves you a lot of headache down the road.
Hi,
This odd behavior just started for me today.
Two IPO 406V2 4.1201 updates
1 central VM Pro connected to 1 IPO with serial dongle. Keys are valid.
2 IPO connected via SCN with the license server pointing to 1 IPO with serial dongle.
Calls come in via 2 IPO AutoAttendant works via SCN...
Same problem again but this time I ran sysmonitor to trace the issue.
I found an error message: "Lic: Rainbow token file not received/invalid from 192.168.42.xxx"
192.168.42.xxx is my VM Pro server.
The VM Pro Server is on 4.1.40
Windows 2003 Server SP2
USB Dongle
There are two IP Office one is connected directly and the other is via SCN over the VPN.
Both VM and Auto Attendant stop working due to the license became invalid on the IPO which is connected locally.
I checked the keyserver...
My License became invalid again.
Does any tech know if this is a bug?
I did the steps of Telecomboy and the license still became invalid after 24 hours.
Also I am running 4.1.1201
The funny thing is I rebooted VM Pro server after it came back up, I then proceeded to reboot each IPO 406V2 and now it works again.
I hope Avaya knows about this bug because this never happened to me before.
Probably its time to switch over to a Cisco IP phone system.
It worked and now the license became invalid again.
after updating the keyserver...i think version 4.1.40 is just too bugy
has anyone else experience this problem?
Hello,
another issue came up after the upgrade from 3.0.69 to 4.1.12
Music On Hold is not working. All it does is a double beep silence and double beep. I have an external source plug into the back.
Everything was working fine on version 3.0.69.
Any switch that I need to turn on?
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.