It's not a matter of how many PRI's per T1, but a matter of what your customers are doing with the connections. We successfully ran 8 incoming T1's via a single 'net T1 that was not heavily loaded until the 9th and 10th incoming lines came up (the second 'net T1 was late, as is usually the case). We also had numerous deicated accounts and colos as well. When the latency started to rise we ordered the new circuits. All the while our clients consistently rate our "speed" to be much better than our competitors. This is all changing right now though, because more users are doing bandwidth intensive things. We have ordered additional 'net T1's to cover the bandwidth growth, but we still are not pinched on the two we have with 16 incoming dialup T1's and PRI's from the telco. Mark Thornton San Marcos Internet, Inc. 512-393-5300 ----- Original Message ----- From: Scot Desort <scot@njaccess.net> To: usr list <usr-tc@lists.xmission.com> Sent: Friday, February 18, 2000 9:11 PM Subject: (usr-tc) OT: Survey - Backhauling traffic from POP's
Off-topic survey:
I am investigating some POP alternatives for our network. These POPs will be dialup only. They will be co-located within the CLEC switch or remote central office.
I am looking for information on how most of you backhaul the dialup traffic to your networks. I find it curiously strange that more CLECs do not have fiber in their facilities that connect them to IP backbones like UUNET, Sprint or CW (at least that's the way it is here in NJ). My first inclination was not to backhaul, but obtain a separate feed to one of the backbones right in the colo/switch, but this is not an option. So, I am left to backhaul.
What is the most cost-effective way to do this? Assuming that these POPs will be relatively small, not requiring A DS3 to backhaul, how many PRI dialup trunks can be supported for each T1 backhaul to my network? Or, is there a more efficient way to do it? The CLEC's use a 3 to 1 rule -- 3 PRI's with relatively moderate traffic can be supported by 1 T1 backhaul. I have my doubts here as well.
Thoughts, comments, suggestions are welcomed, off-list if you prefer.
-- Scot Desort Network Operations Manager NJ Internet Access scot@njaccess.net
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.