Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems with transferring to extensions in 3.2

Status
Not open for further replies.

Infinity306

IS-IT--Management
Joined
Sep 9, 2005
Messages
255
Location
US
I checked and couldn't find any solutions listed but I have just upgraded to 3.2 and we use mainly Analog cordless phones here.. Problem is that the calls seem to drop off while ringing on the 2nd ring and then start up again right before VM picks up. we are useing autoattendant.. same happens with internal phone calls too.. Am I missing a setting that changed just enough to throw a wrench in to the equation? if this is 3.2 I will have to downgrade to 3.1. I can Downgrad the binary now without uninstalling and reinstalling admin software right? since 3.2 can handle 3.1? I guess VM pro would need to be downgraded though..
 
You can downgrade *.bin's.
All bins is in C:\Program Files\Avaya\IP Office\Manager if you don't change in installation process.
Simple cut and paste bins from this folder in new one.
And in this floder I mean C:\Program Files\Avaya\IP Office\Manager put old bin's.

Try upgrade from Manager.

Check Default No Answer Time on System->Telephony tab
 
You may want to set your ring type (on the station's TELEPHONY tab) to one long ring (I believe thats either RING 1 or RING 2). The cordless is seeing the double ring, as an invalid ring cycle, so its only partially responding. One of those settings is one long continuous ring, rather than a short-long ring. I had this issue back on 3.0, but was fixed in 3.1 (as you know).

Hope this helps.

Kris G.
 
Oh, and for analogs I'd recommend setting it this way for all 3 ring rings (Inside, Outside, & Ringback).

Kris G.
 
yeah I did catch that the ring type was a problem.. never seemed to cause trouble until the upgrade to 3.2 and downgrade back to 3.1 though for some reason..
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top