[c-nsp] Typical E1 provisioning

Jessup, Toby Toby.Jessup at qwest.com
Fri Aug 26 16:21:42 EDT 2005


I menat to say "1984 kb/s" ...

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jessup, Toby
Sent: Friday, August 26, 2005 12:57 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Typical E1 provisioning


I do not have experience with E1 services.

When E1 data services are ordered from most PTT/providers, such as for
Internet access, in most places today is the provisioned E1 an
untructured (unframed) 2048 kb/s data service or is structured 1908 kb/s
data service actially what most customers get when they ask for "E1" or
"G.703" (terminology used by vendors and providers can be inconsistent
or vague).

Is it general best-practice to use the Cisco ts16 command on structured
E1s used for data links?

Many providers offer data services using T1 ports in locations outside
of North America. In cases where the local PTT/provider does not support
T1 the PTT/provider may provision a structured E1 and a Cisco router
with an E1 adapter is configured to use time slots 1-24 (right?). Is
that all there is to it (on the CPE) when an SP T1-based service is
provisioned over local PTT E1? Any added performance problems with IMA
or MLP bundles in these converted scenarios?

Any other interesting gotcha's one ought to know about?

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list