Happened to me on VM Pro upgrade from 9.0.4.0.18 to 9.1.0.166 cannot save changes in Control Panel (IP Office Voicemail Pro 32-Bit). Any new updates?
Thanks for the great site.
T1techhttp://files.engineering.com/getfile.aspx?folder=a17e2a59-1bc0-4c5b-a685-cb3cd83fd3fd&file=Registry_Error.rtf
Yes, and other phones work just fine, we have a large batch at 2.300 and cannot move past it, soon I will try and downgrade to an earlier release and then skip the 2.300
MrIPO, it was just a database restore, I was able to fumble through it and complete, Avaya documentation says to contact engineering, but that was not an option, thank you for the response.
Have a system with several 3626 Handsets and 3 have delayed MWI. Could be anywhere from 5 minutes to 5 hours to get the indication that there is VM. Anyone ever experience this? Also where can I find all the files for older Spectralink sets as Polycom is now the site spectralink.com connects...
Quote on SIP Licensing
"SIP Trunk Channels licenses is required in the IP Office configuration. These set the maximum number of simultaneous SIP calls supported by the IP Office. Multiple licenses can be added to achieve a cumulative maximum number of channels supported.
With our SIP provider we had to make sure our IP phone has a valid 10 digit number entered in all 3 fields on the SIP tab of the user. Maybe it is the same for yours.
Although that is a wonderful link, I am looking for more specific information on the Delta Diagnostics output as seen on page 42 of this document:
http://marketingtools.avaya.com/knowledgebase/ipoffice40en/mergedProjects/manuals/manual_pdfs/apps/delta_server_smdr.pdf
Anyone know where to find a description of the fields available in the Delta Diagnostics from Delta Server? I have browsed the knowledge base as far back as 2.1 and cannot seem to find this info. Any idea's are appreciated.
Be careful out there after you upgrade to 4.1(9) that you upgrade all manager versions which have access to your system. Had a customer connect to a 4.1(9) 406V2 with manager 3.2(54) and it will allow the connection and also accept the merge, but it puts the unit into a software reboot loop...
Follow the Remote Mailbox Access document from the knowledgebase. Once you have your *99 set up, in your AA set an action to normal transfer and point it to the SC *99, this will allow access to the VM system and request the user ext and pw.
Thanks Supernn, I follow where you are coming from, we have the flashing ACNT key, but when we press it, nothing happens, caller hears tones from the keys being pressed. Any further thoughts?
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.