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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya Partner disconnect problem

Status
Not open for further replies.

bryanfarrish

Technical User
Jul 25, 2004
13
US
I have a band new Avaya Parnter ACS R6 with Partner VMS R6, and 34D keysets, and on a Verizon CO in California. Very intermittently, when a call comes in and gets routed through the VM, exactly 5 seconds after a user answers it, it gets dropped. At that exact instance, the user who answered the inbound call hears a two-tone signal, similar to a french police siren (the outside caller hears nothing, however, just a dead line.) It's the same tone that you get if you leave a Partner line or intercom engaged and unattended for a minute or so. The tone is not coming from the CO, it's definately from the Partner, since you can generate same tone even if you are not connected to the CO (again, by leaving a line or intercom engaged and unattended).

The drop happens about every 10 or 20 incoming calls. It can happen on any line, any extension, and while any number of people are using the system. One interesting point... it always happens 5 seconds after a user answers an incoming call, NO MATTER how long the caller had been listening to a prompt before choosing an extension. And, amazingly enough, if a call is connected normally (not dropped), but the user puts the call on hold, then when the call is returned to it can still happen, again, exactly 5 seconds after returning to the call. And it's ONLY on incoming calls.

The local vendor has double checked the wiring and programming, and we've had the lines tested and re-tested by Verizon. Any help appreciated.

Bryan
 
I think its something in the transfer sequence

I bet you could get the same results by putting a call on hold and then transferring it to another extension. bypassing the vm

 
We did try testing the transfer from extension to extension at least 30 times... nothing. Maybe we should try more. But even if it dropped, what would it tell us?
 
But even if it dropped, what would it tell us?

it would tel you to look at all the factors that affect transfer.

you have to look at whats actully happening here

vn answers the call plays prompt

caller makes a selection

vm puts the call on hold and transfers it to your extension

it seems to me the problem is a incomplete transfer

in which case it should also appear on a extesnion to extension transfer

did you try both supervised and non supervised transfers ?

off course the fact that its intermetant makes it really hard to troubleshoot





 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top