Cisco Bug: CSCsz75494 - BriCheckMessageRates and BriCheckMeters need to be documented.
Dec 29, 2016
- Cisco Unified Contact Center Enterprise
Known Affected Releases
7.0(0) 7.1(1) 7.2(1) 7.5(1)
Symptom: BriCheckMessageRates and BriCheckMeters need to be documented in the Avaya ACD Supplement guide. BriCheckMessageRates (Default: FALSE for CMS configurations, TRUE for CMS-less configurations). This value indicates whether the PIM should measure the ASAI message rates or not. TRUE indicates that is should measure. BriCheckMeters (Default: FALSE for CMS configurations, TRUE for CMS-less configurations). This value indicates whether the PIM should throttle the ASAI message rates or not. A TRUE value indicates that it should enable message metering (e.g. throttle outgoing messages). The dynamic registry field, BriMaxOutstandingMessages, is used in conjunction with this registry field to indicate how many ASAI messages can be outstanding (pending a response from the CVLAN Server). Once the PIM has reached the maximum number of outstanding messages, it will not send anymore until at least one pending ASAI message has been received. At startup, the PIM will send ASAI messages as fast as it can up to the limit as controlled by the number of outstanding messages. High priority outgoing messages take precedence over normal priority outgoing messages. The PIM also uses message metering to ensure that it does not exceed the maximum number of active associations per ASAI link (see the dynamic registry field, MaxActiveAssocPerASAILink). Conditions: ICM with Avaya ACD.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases