[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Seattle 56k/ISDN Busy Signals
This is what I've heard back from the folks at MegaPOP thus far
regarding Seattle busy signals and other problems:
>Robert, I will forward on to the Seattle engineer here, as it does
>sound from the items you detail out below, that there is more
>happening then just a potential capacity problem.
>
>I will touch base with him not only on the "near capacity" the
>utilities report(and if it truly is resulting in a max port situation
>and in need of additional PRI/equipment), but also what may be the
>cause of the "Your call did not go through." messages. As you stated
>below, capacity issues should not result in this type of recording.
And...
>Robert,
>According to our most recent Network Status meeting held this past
>Monday, I do not recall the engineer managing the Seattle location
>reporting seeing a capacity problem in Seattle yet, but it was
>reported that usage was climbing and *nearing* capacity.
>
>However, when I look at our "Port Utilization" utility that all of us
>here have access to here, it certainly does appear to be close enough
>(97.0%) that it very well could be maxing-out. That utility is a
>"snap-shot" and averages, so anything in that range could be touching
>in at 100% at times during prime usage hours (8 -10, as you stated),
>causing intermittent busies.
>
>That engineer comes in today at 10:00am Central and I will most
>certainly follow up with him to find out just when we will plan on
>having equipment out there and when additional PRI that were
>previously ordered, will be available. I will share with you later
>today, whatever I am able to uncover from him.
I will continue request frequent status updates and keep you all
posted on what MegaPOP is doing to correct this condition.