The Trunk Group Consolidated report summarizes traffic data from multiple trunk groups into a single report over the period of a month. By using CTRL + Click or SHIFT + Click multiple trunk groups can be selected to appear in a single report.
This allows engineers to accurately assess the number of trunks required when:
- Multiple trunk groups have been configured yet the trunk group is actually a single entity
- Issues exist where the Communication Manager limitation on trunk group size prevents accurate reporting
- Modelling is required to accurately scope the size of SIP trunks to replace ISDN or CO trunks
Virsae samples traffic regularly so does not rely on manufacturer information alone and produces very accurate numbers.
Video Overview
Example 1
The graph below has been run against trunk groups 10 and 13 which actually operate as a single trunk group. We can see the combined total peak occupancy was 166 of the 180 trunk members equipped. The Erlang modelling on the right hand axis supports this.
Example 2
The graph below has been run against trunk groups 70, 72, 91 and 92. These are currently separate trunk groups running into media gateways at regional sites. The engineer wants to scope the size of a single SIP trunk group, delivered into a centralized data center, to replace these ISDN trunk groups.
As trunk groups operate more efficiently when combined, there should be a substantial reduction in the number of SIP members required.
We can see the combined total peak occupancy was 78 of the 180 trunk members equipped. The Erlang modelling on the right hand axis shows further savings and calculates that only about 65 members will actually be required. This is due to the fact that the Erlang calculation takes into account that it is highly improbable that the peak occupancy across all trunk groups will align. The engineer running this report can confidently say moving to a single SIP trunk group will reduce the number of channels required from the current 180 to 65.
