Maybe it's not as crazy as it sounds. The situation is: A medical practice) has a T1 with PRI & DID. Most of the time that's enough. But Monday and Tuesday mornings their billing department and their medical assistants start calling out, and patients call in, and the T1 gets saturated.
One solution, of course, is to add a T1. But what about reducing the number of lines available for calling out? If we did that, patients would have a better chance (on average) of successfully calling in. The customer's staff would have more failed outbound calls, but that might not be as expensive as another T1.
Can anyone point me to the formulas for figuring out the right number of lines out versus lines in depending on expected loads? This isn't quite like the usual Erlang calculation (I think) because we're not allocating full-duplex trunks; we're imposing a kind of rationing that improves the odds for inbound callers.
(Cross-posted to general telephony because while this is a Nortel MICS the question applies to a lot of systems.)
One solution, of course, is to add a T1. But what about reducing the number of lines available for calling out? If we did that, patients would have a better chance (on average) of successfully calling in. The customer's staff would have more failed outbound calls, but that might not be as expensive as another T1.
Can anyone point me to the formulas for figuring out the right number of lines out versus lines in depending on expected loads? This isn't quite like the usual Erlang calculation (I think) because we're not allocating full-duplex trunks; we're imposing a kind of rationing that improves the odds for inbound callers.
(Cross-posted to general telephony because while this is a Nortel MICS the question applies to a lot of systems.)
