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

Issue retrieving parked calls & disconnected busy

Status
Not open for further replies.

tehtec

Technical User
Aug 29, 2005
26
US
If you park a call, then recieve the DISCONNECTED message and busy signal (ex: get dialtone and wait, it will disconnect you.)

If you try to retrieve the call, call is dropped and call appearances are blank, status shows CONN and timer runs until you place another call.

Anyone know if this is a known issue?
 
What software load? There was a problem with one of the earlier 3.0 builds in regards to parked calls.
 
So far I've only been able to try it in 3.1.44

Do you not get the same error on the version you're using?

This happens when you try to retrieve a call from park while the display is showing DISCONNECTED. The call is dropped and the status shows CONN and the timer runs.

I've tried this using a 4412 and a 4620, same result.
 
seems like and old bug is back. still not ready to even try 3.1. I'm in wait and see mode for a while.

In regards to your park issue. How do you have the buttons programed? I assume you have the feature programed as park and have assigned a number in the other field. I stay with single digit numbers. park 1 park 2 and so on...

have you tried to park/ride using the short code *37* and *38* to see if the call even is parked?

what does sys mon say?
 
Yeah, I am using feature buttons programmed as park with a number in the other field.

When the phone displays DISCONNECTED, you cannot dial until you open up another line, so its not possible to dial *38* to ride call and get this error. (3.1.44)

And in 3.0.69 if you recieve the NUMBER BUSY or INCOMPATABLE message on your display, its the same story.

It seems like every time you get a busy signal and then try to pick up a call without first hanging up or getting dialtone will result in the call being dropped and the display showing CONN with no appearances lit.

And sysmon didn't show anything exciting about this.

Anyway this error doesn't come up very often and it doesn't seem like it would be a high priority for Avaya, so I think I'm just gonna pretend it doesn't happen.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top