...
In the well-engineered example abovebelow, the H.323 traffic on these Gate Keepers is consistently within the Avaya recommended loads.
...
If Availability Manager cannot resolve the issue, then IT support staff are notified by SMS or email, significantly reducing response times, and very possibly likely avoiding a potential outage.
Example 2
In the example below, there has been an outage over the period of the report. A large number of H.323 stations on all gatekeepers deregistered for several hours between 04:00 AM and 11PM on the 12th and 12:00 AM on the 20th13th.
The phones were clearly not able to re-register to alternate resources. As only some stations deregistered, but all Gate Keepers were affected, the following conclusions can be reached at a glance:
- The incident was not caused by a server or application issue.
- The incident was not caused by the failure of one or more Gate Keepers (say in one Port Network).
- No Gate Keepers had their loading increase, therefore the phones could not see alternatives and connect to them.
Root Cause Analysis at a glance
...
In the next example below, all most H.323 registrations are currently against only one Gate Keeper even though there are possible alternatives - meaning a single point of failure exists.
...
- At least one more Gate Keeper should be configured immediately to remove the single point of failure.
- The enterprise security policy to log out of the phone is not being followed by most users, line managers should be notified.
