Congestion Count - logged/persistent?

[Steerpike58]

I know my IPO system is becoming resource constrained -VCM and VM channels. I've just upgraded to 4.1 and appreciate the 'Congestion Count' and 'Last Date of Congestion' feature in 'System Status'. I want to start closely monitoring this and use the info to decide what to upgrade next.

Two questions:
1) Is there any log file anywhere that will show 'all' congestion issues - not just a total count and date of last occurrence? I've poked around in the delta server logs with no luck, and read the manuals, googled, etc. Ideally, I'd like to see the date/time of EACH incident, not just last.
2) If the info shown in System Status is the best I can get, then how 'persistent' are these counts? Will a system restart reset counter to 0? If not, how would one reset the counter to zero?

I can find no info on this and my BP does not know either.

Thanks!

 

[ronromano]

If you are on 4.1 you need to be careful of congestion counts. If you are not on 4.1.95011, then you have a bug that will, in certain circumstances, cause voice mail not to answer and the congestion count to go very high.

First, get on this level before you start to figure out if you need more VM ports or not.

I don't know why you would need to know the reasons for the congestion to VM or to VCM for that matter, I would think the fact that there is congestion would be enough. But to answer your question as far as I know there is not. If you reboot the IPO the count goes to zero.

http://www.nu-tel.com

 

[Steerpike58]

Where do I find the detailed version info? I've looked at the version shown on the 'select IP Office' screen; in 'advanced->Upgrade'; and in 'Control Unit'. Everything shows the same - 4.1(9).

I just checked on the Avaya site, can't find any downloads since the 4.1 GA release of December '07, which is what I have installed.

Please elaborate!
Thanks

 

[tlpeter]

Call your BP to do it


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Steerpike58]

Call my BP to do what? My BP did the upgrade and will be back next week. I would hope that, if there is a critical update for my system, he would have known about it and applied it.

Can anyone tell me how to determine the exact version information of my system? Thanks!

 

[tlpeter]

You have the correct version
If your BP can not find what the problem is then get another one
The 4.1.95011 version is a special version and is not downloadable for everyone
If your BP does not have it he should contact Avaya for it


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[ProviderReborn]

Your BP has installed the correct current GA release.
However the interim build listed resolves a data channel issue (AS well as many many more) and I would suggest you get your BP to sort this out ASAP.
It is very easy for them to get hold of this release as long as they are not a 2 bit wanna be reseller.

ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.

 

[Steerpike58]

Thanks. So if I HAD that interim build, I presume I would see the referenced version number in the various places I was looking (I just wanted to be sure I was looking in the right place). I've asked my BP to look into getting and applying the fix.

As of now, I am not aware of any 'problem' in need of fixing, other than a potential lack of resources. I'm considering a complete replacement of the IPO for a new system (CM) due to our high availability needs, so I'm reluctant to spend more on the IPO if I can avoid it. Whether I can avoid it or not, short term, depends on the accuracy of the 'congestion count' information being discussed here. If I'm seeing a lot of congestion, I obviously need to take short term action. If I see one issue a week, maybe I can let it go. I was hoping to see a log of 'when', but it seems I'll just have to make do with 'last occurrence'. I've only had one incident in two weeks of operation at 4.1, so far.

The interesting thing is, that congestion incident does not correspond to any usage in the smdr logs - so maybe I am suffering from the bug mentioned here. Thanks for the input.

 

[Telecomboy]

The bug doesn't effect every unit according to my Avaya rep. I have multiple units out there and have only had to apply the patch to (1) of them. The others all seem to run fine. If your congestion count is low and you have no complaints of calls not being answered by voicemail, I wouldn't worry about it.

 

[ProviderReborn]

I caused by some specific feature set that could be programmed in the huntgroup or the way in which calls are transferred to them I believe i read.

ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.

 

[qtelcom]

As a customer/end user, you shouldn't be jumping up and down for the interim releases, unless you know it fixes your specific issue. yes they do fix certain bugs, if they apply, but they have been known to break or cause issue's in others area's that worked just fine on the previous GA release.

The 4.1.95011 release and associated vmpro release gave me some headaches for a customer that disappeared when downgraded to 4.1.9. "Interim" releases should only be applied if it fixes the bug that applies to you and doesn't break other critical functions you need. A good business partner will know this, and the associated bugs in each release and how they affect their particular customer.