Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: wobbly_head_bob on January 12, 2015, 11:21:50 AM
-
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!
-
That's interesting.
I don't think I have an answer for that one.
But, take a look at the reports for individual trunks.
You may see some that are pegged at .99 erlangs. This means they been in use for the entire hour.
If you have multiple trunks that show that then that may explain how usage can be so high with only one peg.
If you do have trunks pegged at .99, do a reso on them to see if they are tied to other trunks.
If yes, busy/rts them.
Ralph
-
Looking that the trunks individually:
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
2 0 0.00 0
----- -------- ----
17 0.20 0
Trunks
Trunk Trunk Peg Usage In Peg Usage Out
Number Label In (Erlangs) Out (Erlangs)
2134 PRI 0 0.00 1 0.00
2135 PRI 0 0.00 1 0.02
2136 PRI 0 0.00 1 0.00
2137 PRI 0 0.00 1 0.02
2138 PRI 0 0.00 1 0.01
2139 PRI 0 0.00 1 0.01
2140 PRI 0 0.00 1 0.01
2141 PRI 0 0.00 0 0.00
2202 MSDN 0 0.00 1 0.01
2203 MSDN 0 0.00 1 0.00
2204 MSDN 0 0.00 1 0.01
2205 MSDN 0 0.00 1 0.00
2206 MSDN 0 0.00 1 0.03
2207 MSDN 0 0.00 1 0.00
2216 MSDN 1 0.00 0 0.00
2217 MSDN 1 0.00 0 0.00
2218 MSDN 1 0.00 0 0.00
2408 Voicema 0 0.00 1 0.00
2409 Voicema 0 0.00 1 0.00
2410 Voicema 0 0.00 1 0.00
2411 Voicema 0 0.00 1 0.01
2424 Voicema 0 0.00 0 0.00
2101 0 0.00 0 0.00
2102 0 0.00 0 0.00
2103 0 0.00 0 0.00
2104 0 0.00 0 0.00
2105 0 0.00 0 0.00
2106 0 0.00 0 0.00
2107 0 0.00 0 0.00
2108 0 0.00 0 0.00
2109 0 0.00 0 0.00
2110 0 0.00 0 0.00
2111 0 0.00 0 0.00
2112 0 0.00 0 0.00
2113 0 0.00 0 0.00
2114 0 0.00 0 0.00
2115 0 0.00 0 0.00
2116 0 0.00 0 0.00
2117 0 0.00 0 0.00
2118 0 0.00 0 0.00
2119 0 0.00 0 0.00
2120 0 0.00 0 0.00
2121 0 0.00 0 0.00
2122 0 0.00 0 0.00
2123 0 0.00 0 0.00
2124 0 0.00 0 0.00
2125 0 0.00 0 0.00
2126 0 0.00 0 0.00
2127 0 0.00 0 0.00
2128 0 0.00 0 0.00
2129 0 0.00 0 0.00
2130 0 0.00 0 0.00
2131 0 0.00 0 0.00
2132 0 0.00 0 0.00
2133 0 0.00 0 0.00
2142 0 0.00 0 0.00
2143 0 0.00 0 0.00
2144 0 0.00 0 0.00
2145 0 0.00 0 0.00
2146 0 0.00 0 0.00
2147 0 0.00 0 0.00
2148 0 0.00 0 0.00
2149 0 0.00 0 0.00
2150 0 0.00 0 0.00
2151 0 0.00 0 0.00
2152 0 0.00 0 0.00
2153 0 0.00 0 0.00
2154 0 0.00 0 0.00
2155 0 0.00 0 0.00
2156 0 0.00 0 0.00
2157 0 0.00 0 0.00
2158 0 0.00 0 0.00
2159 0 0.00 0 0.00
2160 0 0.00 0 0.00
2161 0 0.00 0 0.00
2162 0 0.00 0 0.00
2163 0 0.00 0 0.00
2164 0 0.00 0 0.00
2165 0 0.00 0 0.00
2166 0 0.00 0 0.00
2167 0 0.00 0 0.00
2168 0 0.00 0 0.00
2169 0 0.00 0 0.00
2201 0 0.00 0 0.00
2208 0 0.00 0 0.00
2209 0 0.00 0 0.00
2210 0 0.00 0 0.00
2211 0 0.00 0 0.00
2212 0 0.00 0 0.00
2213 0 0.00 0 0.00
2214 0 0.00 0 0.00
2215 0 0.00 0 0.00
2219 0 0.00 0 0.00
2220 0 0.00 0 0.00
2221 0 0.00 0 0.00
2222 0 0.00 0 0.00
2223 0 0.00 0 0.00
2301 0 0.00 0 0.00
2302 0 0.00 0 0.00
2303 0 0.00 0 0.00
2304 0 0.00 0 0.00
2305 0 0.00 0 0.00
2306 0 0.00 0 0.00
2307 0 0.00 0 0.00
2308 0 0.00 0 0.00
2309 0 0.00 0 0.00
2310 0 0.00 0 0.00
2311 0 0.00 0 0.00
2312 0 0.00 0 0.00
2313 0 0.00 0 0.00
2314 0 0.00 0 0.00
2315 0 0.00 0 0.00
2316 0 0.00 0 0.00
2317 0 0.00 0 0.00
2318 0 0.00 0 0.00
2319 0 0.00 0 0.00
2320 0 0.00 0 0.00
2321 0 0.00 0 0.00
2322 0 0.00 0 0.00
2323 0 0.00 0 0.00
2401 0 0.00 0 0.00
2402 0 0.00 0 0.00
2403 0 0.00 0 0.00
2404 0 0.00 0 0.00
2405 0 0.00 0 0.00
2406 0 0.00 0 0.00
2407 0 0.00 0 0.00
2412 0 0.00 0 0.00
2413 0 0.00 0 0.00
2414 0 0.00 0 0.00
2415 0 0.00 0 0.00
2416 0 0.00 0 0.00
2417 0 0.00 0 0.00
2418 0 0.00 0 0.00
2419 0 0.00 0 0.00
2420 0 0.00 0 0.00
2421 0 0.00 0 0.00
2422 0 0.00 0 0.00
2423 0 0.00 0 0.00
----- ------- ----- -------
3 0.01 17 0.20
I can account for the 0.20 in outgoing, and attribute the 0.01 on incoming to three very short calls on the MSDN link... but the more than 7700? Nope. I've rebooted this particular controller and have seen the usage numbers restored to normal levels, I will be watching to see if the numbers start to creep. I'm thinking that maybe the usage stat is adding up over time instead of resetting and recalculating per hour.
-
After the reboot, the usage numbers did return to normal...for a time. They are starting to build up again without resetting to 0, at least that's the only way to account for this.
There's just no way it's possible for Route 9 to have 1 peg and more than 7000 Erlangs.
Using the Erlang formula that would be 1 (peg count) multiplied by the average call hold time X (as we don't know this value) divided by 3600 (seconds in an hour) should = 7000 (rounding way down)
That would mean the 1 single call was on the phone for *drum roll*.... 25.2 MILLION seconds.
? I'm so confused.
-
Sounds like you may have stumbled into a bug.
Ralph