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

Class of restriction question 1

Status
Not open for further replies.

thesaxxon

Programmer
Jun 1, 2011
5
US
Hey guys, I'm still making my way through the mess I've inherited with my new job. I was looking through my list of Class of Restrictions and one is labeled as "Possibly Corrupted". Is this even possible? And if so, is there a way to see what has been corrected? Thanks in advance guys.​
 
It is remotely possible - possibly cleared by a reset system 4 (that takes down the whole pbx...) I'd leave well enough alone :)
 
I have never heard of a cor getting corrupted what so ever

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Yeah, I think most of the guys that "oversaw" the telecom responsibilities before me didn't know a whole lot, so I wasn't sure what had happened to make them think that it was corrupted. I just wanted to make sure, thanks for the input guys!
 
It could possibly be corrupted, and they didn't want to fix it.

If you have a support contract, I would ignore it and wait until you get an EECRS or Corruption message. Then call and get them to fix it.
 
The previous guys might have thought that the COR was bad as it has restriction settings which they didn't understand and therefore called it corrupted. You can try and assign it to a test station and make a few calls. Wouldn't think you could be causing any harm with that.
 
Software corruption and software bugs can be difficult to determine without lots of testing and experience.
Tools for troubleshooting and resolution of these issues are not generally available to customer logins.
Software corruption is cleared by reading and writing into memory of the pbx software. Bugs are fixed with
patch activation and upgrades to soft loads. Reloads are certainly an option when clearing issues of this
nature, but MOST translation corruption issues are saved to your backup only to be reloaded into memory with resets.
There are issues "where memory that causes issues" can be cleared with resets becuase a save translation does
not save status, but only saves translation data. COR is translation data and a group controlled restriction
for that COR is in status memory.

Tools vary based on age of software. Some are built into the pbx software like core dumps, mini-core dumps,
mst, tcm and debugger and the highest diagnostic tools interface with Avaya's computers that contain
source code for that software.
The later the software version, the better the tools. Tools without access, training, and experience are not much help.

These issues are usually resolved by Avaya Engineers and Developers or someone with access to these resources.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top