So I've run some traffic reports and I'm noticing something strange... strange to the point of being completely baffling. I will admit that my ability to read these logs as they should be read pretty well stops at looking at peg counts, trunk numbers and potential killer trunks. I attempted to wrap my feeble mind around erlangs and have come well short. That said, I'm very well sure that the numbers I'm going to show you, shouldn't be happening. The thing is...I don't know how or why they are happening. I'm attaching herein for expert review a several hours span of traffic files. I'm paying special attention to the "Routes" section and the usage. Specifically routes 8 and 9.
Route 8 = calls to extension 2800 (our voicemail system)
Route 9 = calls to #4 + 5 to follow (ex: #426195) (This routes internal callers directly to a voicemail box greeting, bypassing actually calling an extension and being forwarded to 2800)
The peg counts seem about right and can be easily proven with SMDR. It's the usage numbers that just don't jive for me.
Routes
Route Peg Usage Busy Peg Overflow Busy Hour
Number (Erlangs) Peg Time
7 6 0.07 0 0 6 06:00
8 3 155.99 0 0 3 06:00
9 1 ***.16 0 0 1 06:00
11 7 0.10 0 0 7 05:00
6 0 0.00 0
10 0 0.00 0
12 0 0.00 0
13 0 0.00 0
14 0 0.00 0
15 0 0.00 0
18 0 0.00 0
200 0 0.00 0
---- ------ ----- ----- ----
17 7783.33 0 0 17
In the above excerpt, how does 1 peg = 7000+ Erlangs of usage?
Here we can see the 4 calls to the voicemail T1. (routes 8 and 9)
Trunk Groups
Outgoing Trk Trunk Group Usage Maximum
Group Number Label Peg (Erlangs) Busy Peg In Use/Avl.
1 PRI 7 0.10 0 2/ 69
3 MSDN 6 0.07 0 1/ 23
4 Voicemai 4 0.02 0 1/ 24
They just don't add up... HALP!