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

Park Issue 8.1.67 1

Status
Not open for further replies.

derry163

Technical User
Mar 18, 2005
46
US
Got a weird one. 1608 IP phones. Park 1,2,3 will be working fine for a day or two then all of a sudden when you place a call on any one of the park slots they all light up! Reboot or changing the call park slot numbers then merge fixes it.
 
Park slots assigned via User rights? Hopefully otherwise it is a lot of programming if you have to change it :)

if so you could try and make some of them locally programmed to see if that has any influence on the functionality.

Joe W.

FHandw, ACSS (SME), ACIS (SME)



Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.
 
Yes, via user rights. That would suck otherwise[bigsmile]. I Will try to program a few locally and see if that does anything. Thaks for the idea!
 
NP I had issues before with things being programmed via user rights so if something goes nuts I try that usually first

Good luck

Joe W.

FHandw, ACSS (SME), ACIS (SME)



Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.
 
User rights can go wrong, these days I create the user rights then copy the values to users rather than apply them to them, works better and doesn't lock the change :)



"No problem monkey socks
 
Same problem with softconsole and the receptionists' 9508 set. She has park 1 and 2 on both the phone and softconsole. When she clicks or drags to park 1 on the softconsole, park 1 is green, and park 2 is red on the 9508 set. Downgraded to 8.1(65) to clear. Not using user rights in my setup.
 
Has anyone talked to Avaya about the issue yet? Park being messed up is critical to most company's.
 
Did you raise it as a bug yet?
If not then do it.


BAZINGA!

I'm not insane, my mother had me tested!

 
Yeah, I am waiting for a sold to number to be created so I can open a ticket.
 
Very good as most just don't


BAZINGA!

I'm not insane, my mother had me tested!

 
My ticket will be done this week as well. Disti and Avaya wanted me to prove the last bug I ran across through monitor tracing. No time for that in this current install, will break it on my demo and send them what they want.
 
wspence,

Have you had this happen since the downgrade? I know its been a few days since you downgraded and wanted to see if it popped back up. I have the same issue with a receptionist phone and if the downgrade works then I will do it tonight.

I don't want to waste the time if it came back.
 
Signo, without a doubt it is gone, however my tech downgraded to 8.1(57)because that was all he had at the time to downgrade with. Today was go live, 3 receptionist all parking to the same 4 park slots, no problems.
We did try it also on on our office system at 8.1(65) but it was only a few calls and it worked everytime. It failed everytime we tried to park on 8.1(67).
 
Has a case been opened with Avaya on this issue? We are experiencing the same problem on 2 systems running 8.1(67). Unfortunately we cannot downgrade. We had issues with DTMF not working on AA over a SCN which is fixed in 67.
 
I have a case open
but I am still collecting data to send to Avaya as we have a hard time replicating it at the moment.

Joe W.

FHandw, ACSS (SME), ACIS (SME)



Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.
 
maddog1970, I think you can downgrade to 8.1.57 which has neither the SCN issues or the call park issues? Of course, if you're using any FP1 stuff (e.g. D100 DECT) then you're really stuck.

Still... how can they break something as fundemental as call park?

GB
 
it is not every park action that is causing grief.
I did testing this morning with the customer and I have been using the park in excess of 100 times and no problem whatsoever.
But when I did training last week I parked a call twice and the second time all 3 park zones where lighting up and stayed lit when I took the call off park.

Still park is one of the pillars of the PBX and should be tested better but who has time. Avaya likes to have BP's and customer do the testing for them it seems.

Joe W.

FHandw, ACSS (SME), ACIS (SME)



Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.
 
I also have had problems with park buttons on 8.1(67). they are assigned via user rights. the park buttons will all light up solid red. receptionist has a 9630 with (2) sbm24's. The phone will randomly freeze up as well. I have a ticket with Avaya and they are stumped!
 
We've deployed 67 at about 20 sites over the past 5 weeks. No one started noticing it until last week. (Saw it for the first time myself on our system last Thurs... went to open a case under the SME Expert provisions and we were told that without IPOSS in place on our sys they could not work the issue and needed to void the ticket). Haven't had time to follow up, but really glad everyone else seems to be on it!! :eek:)


 
I finally got a sold to created for this customer and just logged a ticket. I to had to downgrade to 8.1.57 to get park to work.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top