montyzummer
IS-IT--Management
Ok really strange one ... or maybe not
CM 5.2.1 only happens to 4621 handsets with CC firmware , occasionally the mute button will stop working on the sets , you check in sat on the station form and sure enough its set to no , so you have to busy the set change to yes and release and all is good again.
The phones all back up to a http server with the bruri setting , the back up files are all correct and I can not see reference to mute buttons in the back up file , all these phones have agents log in to them (elite) the 46xx file has no direct ref to mute enabled except
## MUTESTAT specifies whether the Mute button is enabled or disabled when CCBTNSTAT is 0.
But this is only for 16xx phones , my next step is to mst a test culprit and just see what I can get , in case it needs to go to Avaya , just after for some ideas or if this has been seen before , there is an article on the Avaya site that kind of references this , with the busy out as a fix , but I just want to know how the hell its happening , im going to look at MIB files as there is a new tool Avaya have on there support forum that looks cool ......but you guys may have some good ideas or indeed locations in log files that I can go a searching , this happens at least 5 times a week to totally separate phones and they are totally locked down with the opstat setting(not that I think that has any bearing) ideas please ???
APSS (SME)
ACSS (SME)
ACIS (UC)
CM 5.2.1 only happens to 4621 handsets with CC firmware , occasionally the mute button will stop working on the sets , you check in sat on the station form and sure enough its set to no , so you have to busy the set change to yes and release and all is good again.
The phones all back up to a http server with the bruri setting , the back up files are all correct and I can not see reference to mute buttons in the back up file , all these phones have agents log in to them (elite) the 46xx file has no direct ref to mute enabled except
## MUTESTAT specifies whether the Mute button is enabled or disabled when CCBTNSTAT is 0.
But this is only for 16xx phones , my next step is to mst a test culprit and just see what I can get , in case it needs to go to Avaya , just after for some ideas or if this has been seen before , there is an article on the Avaya site that kind of references this , with the busy out as a fix , but I just want to know how the hell its happening , im going to look at MIB files as there is a new tool Avaya have on there support forum that looks cool ......but you guys may have some good ideas or indeed locations in log files that I can go a searching , this happens at least 5 times a week to totally separate phones and they are totally locked down with the opstat setting(not that I think that has any bearing) ideas please ???
APSS (SME)
ACSS (SME)
ACIS (UC)
