You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Tracks H.323 station registration, in unit quantity, over selected period of time. Measures all registration points (e.g. CLAN, Processor Ethernet).

  • Trouble shoot or run root cause analysis at a glance
  • Validate IP Network Region design
  • Ensure Gate Keeper resources are working within guidelines
  • Detect and raise alarms at an application level, rather than infrastructure level
  • Use as an indicator of potential network problems

Identifying traffic trends and the associated impact on IP Signaling capacity can mitigate otherwise unseen issues. Can be used in conjunction with Availability Management to identify pending capacity issues. 

Example 1

The example below shows a distribution of H.323 registration across all Gate Keepers. From this it is possible to validate crucial aspects of the design:

  • Confirms that the Gate Keepers are loaded within Avaya recommended tolerances
  • Confirms that the local gatekeeper preference allocation is working as designed
  • A quick count for each gatekeeper confirms that there are no issues with access lists or firewalls

In the well-engineered example above, the H.323 traffic on these Gate Keepers is consistently within the Avaya recommended loads. By setting a high water mark, Availability Manager can be used to try and resolve issues proactively when registrations step above the recommended maximum. If Availability Manager cannot resolve the issue, then IT support staff are notified by SMS or email, significantly reducing response times, and very possibly avoiding a potential outage.


  • No labels