Has anyone ever done a point-to-point from the US to a country where they use E1s? How does that work? As near as I can tell, T1s and E1s are not compatible. I'm sure this is done all the time, but I'm stuck at where to start.
E-1s are 32 channels, T-1 are 24 channels, so I don't see how they could be capatible. If u are a Avaya technician u could call ETAC in denver, but they only talk to Avaya or Avaya partner technicians.
I imagine what has to been done is to make the E-1 side a T-1, beings how E-1 is not legal on public networks in the USA. U would think that there would be something on the subject at support.avaya.com though.
I just thinking out loud again but have you tried a TN464 on the US side and translate it as E1. This way you can have E1 on both sides. On the DS1 page change the bit rate from 1.544 (T1) to 2.048 (E1). The circuit has to be 2.048 from the carrier.
Thank you both. We did try just setting it to an E1, but it fails even Test #138. It's just not compatible with the local system when it's set as an E1. I did call tech support (which isn't always fun) and they said the carrier is responsible for converting it. So, in the US it's set as a T1, in the other country it's set as an E1 (missing 6 channels) and the carrier converts it in the network. Thanks again.
There are third party converters that can translate, and I'm SURE lucent has a card.
T-1 24 channel uses robbed bit signaling, which places supervision (A+B bits) into each channel's data stream innternal to the channel it's supervising.
E-1 uses channels 16 and 32 to carry all the channel supv'n.
Virtually all switch manu's make an E-1 card (because they want to sell their switches internationally. Simple for them to do also because almost all switches are designed with a 32 timeslot backplane, (because the CPU uses 32 bit). then CPU just ignores slots 25 through 32.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.