Can anyone tell me how to calculate trunk capacity.
For example: I have 735 users and 369 trunks (116 PRI, 72 T-1, 111 COT, 70 LD Tie). How do I tell is this is over trunked or they are okay or need more.
You're very busy, or over. Can you get a trunk utilazation report from your carriers? As part of Maint. it is usually included semi- or anually for free.
Most formulas are forecasts of what you expect when Planning and Engineering, I think over trunked would require your Historical Utilization for a time frame, as well as, your own traffic, you pulling traffic?
We are engineering another site and we are looking at 3036 users. How do we determine how many trunks or PRIs we wiil need. It is a combination of a call center and regular business operation. But lets just say a regular business for now.
Conig is based on 85% utilization. You will have to use Planning and Engineering guide, which houses many formulas for configuration. Here is just one page on app config, many pages on network and loop config follow:
Application engineering Page 281 of 498Large System Planning and EngineeringA Meridian 1 Option 81C can have up to 256 loops. With 32 loops per module, our initial estimate of 3 network modules was correct. Because the configuration requires a Meridian 1 Option 81C, it is not necessary to check the card slot limitation.2Real-time requirementThe worksheet has been shortened to include only that features that are being used in this configuration. The charges for Symposium assume the “simple script”, which is defined as “calls routed directly to an agent Total loops (Sum of entries under column B)=___67___(NL)Note: All calculations should be rounded up to the next integer.*Iterative procedure may be needed, if the number of network modules required was not correctly estimated at the outset. Conclusion: NL <= 16, Meridian 1 Option 51C, Succession 1000M Half Group 16 < NL <= 32 Meridian 1 Option 61C CP PII, Succession 1000M Single Group 32 < NL <= 256 Meridian 1 Option 81C CP PII (8 group), Succession 1000M Multi GroupTDS/CON loops = 6three Network Modules is initially estimatedN1 = [(600) ÷ 30] = 20loops for agent, supervisor sets and trunksN2p = [(900) ÷ 30] = 30loops for PRI trunksN31 = [112 ÷ 30] = 4loops for MIRAN portsN32 = [112 ÷ 16] = 7loops for MM (MIVR) portsTotal required loops = 6 + 20 + 30 + 4 + 7 = 67Table 83 Worksheet for network loop calculation (example) (Part 2 of 2)Column A Column B (Loops)
remember a call center needs almost a trunk per station.. one the other end of the usage, a hotel needs one trunk per 40 stations.. the best way to determine your current trunk level is with a traffic study.. ld 2.. or your provider can give you a traffic study external to the switch. most providers give there cust one per year at no cost.. 80 percent is very high for a non call center.. usually runs below 50 percent.. we have 8000 plus users and run almost 30 percent.. we do not get all busy EVER.. this is a hosp and we have 50 users in acds.. we handle 14000 calls per week to the consoles with all 8000 stations having it's own did (ddi).. we have less then 1000 patient rooms, they are low usage.. under 10 percent..
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.