Traffic made easy
From Jaymzworld
Contents |
Introduction
This is intended to be a simple job aid to help you determine if there are traffic problems or if additional analysis is required. Five reports are included that are instrumental in determining if there are traffic issues.
Trunk Group Summary
TRUNK GROUP SUMMARY REPORT
Peak Hour For All Trunk Groups: 1000
%
Grp Grp Grp Grp Meas Total Total Inc. Grp Que Call Que Que Out % Out
No. Siz Type Dir Hour Usage Seize Seize Ovfl Siz Qued Ovf Abd Srv ATB Blk
1 238 isdn two 1000 4268 2970 2970 0 0 0 0 0 0 0 0
2 238 isdn two 1000 6037 2486 0 0 0 0 0 0 0 0 0
3 1 co two 1100 2 15 15 0 0 0 0 0 0 3 0
15 190 isdn two 900 2762 740 740 0 0 0 0 0 0 0 0
16 190 isdn two 1100 2175 791 791 0 0 0 0 0 0 0 0
17 190 isdn two 900 2309 657 657 0 0 0 0 0 0 0 0
18 214 isdn two 900 3028 792 792 0 0 0 0 0 0 0 0
25 118 isdn two 1000 4103 3082 0 817 0 0 0 0 0 19 20
26 118 isdn two 1000 1884 852 0 0 0 0 0 0 0 0 0
33 142 isdn two 1000 727 349 136 0 0 0 0 0 0 0 0
The Trunk Group Summary Report is mainly used to determine if a trunk group is sized properly. The number in the TOTAL USAGE column on the busiest day for the trunk group can be compared to the retrial table to determine how many trunks are needed. If a trunk group has no usage, the existence of the trunk group should be questioned. Also, you want to look at the OUT SRV (Out of Service) column to see if any trunks were out of service during the study. Advise the account team of any out of service trunks. The GRP OVER FLOW (Group Over Flow) column should also be reviewed. If there is data in this column, the trunk group is over flowing to another trunk group to help handle the usage. The route patterns should be reviewed before you add any additional trunks.
Occupancy
OCCUPANCY BUSIEST 3-MINUTE INTERVALS MEASUREMENTS
Date of Static CP SM Idle Total Tandem Total Intcom Inc Out Pnet
Occurrence Occ Occ Occ Occ Calls Calls Atmpts Atmpts Atmpts Atmpts
Atmpts
04/21/05:36 81 3 6 10 8 1 43 25 8 8 2
04/21/14:36 8 14 3 75 673 68 1015 388 255 280 92
04/22/15:00 7 14 2 77 827 82 1243 427 301 363 152
04/23/09:48 15 22 37 26 624 74 955 351 274 228 102
04/23/10:27 9 12 3 76 639 81 1020 370 285 262 103
04/26/10:27 8 14 0 78 773 119 1188 407 335 293 153
04/26/11:21 8 14 0 78 782 92 1148 359 367 318 104
04/26/13:12 9 14 3 74 792 104 1237 407 314 366 150
The Processor Occupancy Report is used to determine if the processor is in trouble. Look at the CP OCC column (Call Processing Occupancy). The number should be under 57% (The CP design limit and total design limits are (57%, 80%) for G3r and S8700 servers, and (52%, 70%) for all other systems) which is the maximum the processor can handle. If you see a number around 57%, seek the help of a Traffic Analyst. The 3 minute busiest interval report can be used to review the "bursty" traffic.
The Total Atmpt column is the number of call attempts made during the measurement interval. This number is the sum of the intercom, incoming, outgoing and private network attempts. If the CP OCC column has the same number for each day, look to the total attempt column to determine which day was busiest.
If the % ABAN column is above 50%, bring this to the account teams attention. What is the reason for the high abandoned rate?
Tone Receiver Summary
TONE RECEIVER SUMMARY MEASUREMENTS
Meas Total Peak Total Peak Total Peak
Hour Type Req Req Queued Queued Denied Denied
1400 DTMF 13422 46 0 0 0 0
2300 GPTD 0 0 0 0
1500 CC-TTR 3306 32 0 0 0 0
2300 CC-CPTR 0 0 0 0
2300 CC-MFCR 0 0 0 0
The Tone Receiver Summary Report provides information on the number of calls queued or denied a TTR resource. Look at the last four columns on the right side of the report. If there are any calls denied then the switch needs additional TTR resources (TN748, TN744 or TN2182). If calls are queued, additional resources may be needed. If the peak request column is greater than the total available you should see some queued or denied. This means additional TTR resources are needed. Off port network searches for a TTR resource can be critical if a DS1C remote EPN is involved. Remember there are a maximum of 92 talk paths available (if all four DS1 circuits are installed). Therefore, off port network searches for a TTR resource can tie up the available talk paths.
The search algorithm for a TTR resource is as follows: TN748 (any vintage), TN744, TN744A, TN744B, then TN744C, TN744D or TN2182. If you have Multiple Location Support software (R7 and later) activated the search algorithm may be different.
If you have off PN searches for a TTR resource, check for TN748D, TN744, TN744A or TN744B. Be concerned if the PN is going off PN 100% of the time or if the PN is a DS1C.
Note that the S8700 IP-Connect does NOT share tone detection resources across PNs. Accurately detecting call progress tones that have been possibly compressed by a voice coder like G729 is problematic -- more so, if the network is lossy. Instead of having a single pool of resources as in a traditional CSS or Multi-connect, there is a pool per PN.
(i.e. If you have a single IPSI and one TN744 in a Port Network, the total available for that Port Network only would be 16)
The list measurement reports have not evolved to handle the difference, disregard the Total Avail heading. The same type of issue exists with G700/S8300s. The G700s have tone detection resources but they cannot be used by ports in traditional PNs or vice-a-versa.
Tone Receiver Detail
TONE RECEIVER DETAIL MEASUREMENTS
PN PN Peak Total Peak
Hour PN Type Req Alloc Alloc Off-PN Off-PN
1400 1 DTMF 414 414 5 0 0
2300 1 GPTD 0 0 0 0 0
1500 1 CC-TTR 128 128 4 0 0
2300 1 CC-CPTR 0 0 0 0 0
2300 1 CC-MFCR 0 0 0 0 0
The Tone Receiver Detail Report is used to determine if TTR balancing is required. The last two columns on the right will show if any port network had to look to another port network for a resource. Only one port network is shown above, but the report will show the data for every port network. Going off port network for a TTR resources is not necessarily a major issue for fiber connected port networks as long as no calls were queued or denied (Tone Receiver Summary Report). However, this can be an issue with DS1C remote port networks (see the note below under port network link blockage report for DS1Cs). The switch operates more efficiently if it uses the resources in a port network before looking to another port network for a TTR resource.
Port Network Blockage
PORT NETWORK LOAD BALANCE STUDY REPORT
TOTAL CALLS
Time Division Multiplexed(TDM) Port Network(PN) Link
Meas -------------------------------- --------------------------------
PN Hour Usage Peg Peak Blockage %Occ Usage Peg Peak Blockage %Occ
1 1400 7275 10484 229 0 42 6754 8430 220 0 24
2 1500 11758 13833 385 0 67 10288 9941 344 0 37
3 1400 11217 12937 375 0 64 9932 8382 331 0 36
4 1400 6155 6766 216 0 35 5636 4659 191 0 20
5 1000 3457 4213 137 0 20 3379 3491 133 0 12
6 1500 4770 5102 164 0 27 4548 3776 153 0 16
7 1000 10719 10694 360 0 62 9807 7190 333 0 36
8 1400 3905 4399 138 0 22 3239 2690 119 0 12
9 900 6192 5838 226 0 36 5057 3460 197 0 18
10 1500 6684 5770 246 0 38 5435 3292 191 0 20
11 1400 9564 9384 313 0 55 7849 5800 262 0 28
The Port Network Blockage Report is used to determine if the port network is blocking calls. If so, the switch may need to be balanced or have additional port networks added. Look at the Usage column on the left side of the report (TDM). If the usage is over 14652, or the peak time slot is over 483, then the port network is blocking calls. When this occurs, a value will appear in the BLKG field. If the usage is getting close to 14652, then action should be taken to prevent blocked calls. This means balancing trunks and stations over multiple port networks.
A port network can typically accommodate 6 to 7 DS1 cards. This is a general rule. Each switch and application is unique. A port network can have as few as four DS1 cards with heavy traffic or more than seven DS1 cards with the same amount of traffic.
If you have a DS1C remote EPN look at the PEAK field on the right of the report (PN LINK). If the peak is approaching 184 (assuming four T1s are present; 136 for three, 88 for two and 40 for one), there may be blockage between the main location and the DS1C location. This indicates that the switch does not have sufficient fiber time slots to support the traffic between the main and the remote location. Additional DS1C port networks may be needed to serve the remote location, or trunks may need to be installed at the remote location to handle outbound and inbound traffic.
Checklist for DS1s
Determine if the DS1s are line side or trunk side. How many trunk side DS1s are in each port network? If there is high usage or blockage at the PN level, a rebalance may be required if there are more than 7 DS1s in a port network.
