site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
2112
Share Topic
Posting?
Links: ·ASI Transport Partner Lookup (by state)
page: 1 · 2 · 3
AuthorAll Replies

JDav

join:2003-08-20
Saint Clairsville, OH

reply to RadioDoc

Re: Welcome to the ASI forum

Start an new topic OHnetquy.... This has been here for a while. Maybe someone will respond to a new one!!!


Corona
It's cool, I'm takin it back
Premium
join:2000-03-14
Dallas, TX
Reviews:
·AT&T U-Verse

reply to OHnetguy

said by OHnetguy:

I'm curious as to what types of things you'll be able to answer and what types of tests you all can run.

You've got ASI Techs here - they can do darn near anything
said by OHnetguy:

I do have a question - So far, three customers we've set up out of one CO all see 15xx/160 sync rates on their 1.5/128 plans, but they all consistently get speed tests no greater than 1250 kbit down. The same applies if they are just downloading from our local facilities. Is this typical? I realize there is likely overhead - Just wondering if the overhead we are talking about is extra overhead due to the L2TP tunneling and such or if the overhead is the same whether we provide it or SBC provides direct to customer.

In the Ameritech region, ASI provides the hand-off via L2TP exclusively. You typically see 80-85% throughput of the actual sync rate.
said by OHnetguy:

Oh - another question. If we have a customer who is obviously syncing lower than what they originally ordered and whom is not having any other apparent troubles besides the low sync rate, are you guys able to test these lines and uncap just like the SBC direct guys do over on the other forum?

Yep
said by OHnetguy:

One more question. When you all refer to capping - is this directly seen by the sync rate indicated on the modem? I.e. if a customer ordered 1.5/128 and showed sync rates of 1.5/160 for some time and now all the sudden they are syncing at 768/160 - is this capping? Or can 'capping' be happening at a point down the line where the sync rate actually shows 1.5/160 but in actuality the line is capped at 768?
Capping refers to the sync rate only. There are only 2 "choke points" in the Ameritech model: 1. sync rate at the DSLAM, 2. profile in the ASI Redback.

Hope that answers your questions!
--
There are 10 types of people in the world: Those who understand binary, and those who don't...
my site
Short Bus Kids Radio!!

OHnetguy
Premium
join:2003-01-16
Toronto, OH

reply to JDav

said by JDav:
Start an new topic OHnetquy.... This has been here for a while. Maybe someone will respond to a new one!!!
JDav,

Good point man - I shoulda done that. What was I thinking But I see you got it covered. Thanks man.

Mike

OHnetguy
Premium
join:2003-01-16
Toronto, OH

reply to Corona

said by Corona:
You've got ASI Techs here - they can do darn near anything

In the Ameritech region, ASI provides the hand-off via L2TP exclusively. You typically see 80-85% throughput of the actual sync rate.

Capping refers to the sync rate only. There are only 2 "choke points" in the Ameritech model: 1. sync rate at the DSLAM, 2. profile in the ASI Redback.

Hope that answers your questions!

Corona,

Sure does answer 'em. I appreciate it! If 80-85% of sync is normal, then I think we're looking good.

So if we order 1.5/128 on behalf of a customer, then the Redback profile reflects that and the only thing that would change (as long as we didn't actually issue a change in the order) is the sync rate at the DSLAM (in the event that somehow you all determine its taking too many errors at the higher rate) ?

Thanks again,

Mike


Corona
It's cool, I'm takin it back
Premium
join:2000-03-14
Dallas, TX

reply to RadioDoc
yep

page: 1 · 2 · 3

Sunday, 03-Jun 23:32:01 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics