Data analysis guidelines for trunk group reports

Last Updated : Oct 31, 2012 |
Prolog information
The following guidelines are intended to show an easy and fast method of determining whether the collected data is invalid or questionable. These guidelines represent the least you should do for validation. Perform additional validation as necessary.
Use the list performance trunk-group report to obtain an overall indication of those trunk groups that may be providing poor service. The five trunk groups with the highest percentage of blocking are listed in the list performance summary report. However, this report (summary) has the following limitations:
  • The Group Blocking shown on this report is the percentage of blocking for outgoing and two-way trunk groups. For incoming trunk groups, the Group Blocking value is the percentage of all trunks busy (ATB). A high value for either % ATB or the % Out Blocking is an indication of possible traffic load problems.
  • A two-way trunk group with undesirable incoming blocking do not show any problems on this report, since only outgoing blocking is displayed on two-way trunks.
Use data from the Trunk Group Measurements report for a more accurate estimate of service levels on incoming and two-way trunk groups. To validate the Trunk Group Measurements report, verify the following data is in order:
  • Total Usage (in CCS) should not exceed 36 times group size. For example, with two trunks, the total usage measured should not exceed 2 X 36 = 72 CCS.
  • On incoming trunks, total seizures should be equal to total incoming seizures.
  • Incoming trunk groups should have a queue length of zero.
  • The number of incoming calls should never be greater than the total number of calls carried by all trunks in the group.
  • Outgoing trunk groups should indicate zero as their number of incoming calls.
  • Out-of-service trunks should never be greater than group size.
  • For trunk groups with queues, the two fields (Calls Queued and Queue Overflow) should total the number displayed in the Group Overflow field.
  • For trunk groups with queues, the Queue Overflow field is incremented whenever a call finds the all trunks busy condition and the queue is full.
  • For trunks groups without queues, the Calls Queued and Queue Overflow fields are always zero. The blocked call count is reflected in the Group Overflow field.
  • If the Percent Outgoing Blocking field shows a value greater than zero, the Queue Overflow (if a queue is administered for the trunk group), Queue Abandon, and Group Overflow fields should also have values greater than zero.
  • Measurement hour data reported in the System Status Report (for example, monitor system view1 or monitor system view2) should correspond to those shown on the hourly trunk group measurements and performance reports.