Have a provider here in Michigan that is suppling my customer with a voice/data 3mb circuit. The router they are using is an Adtran 908e. Everything has been working for about 8 months but recently started getting problems. The customer at times cant dial out or receive calls. They reboot the Magix and after the Magix comes back up everything works. Checked errors on system and showed D channel inoperative also b channel not released. Provider did not see any errors on their end. Verified settings with provider. They were set at 5ESS in router but had no other sub setttings(custom). They said the only setting they had was for 5ess. I told them that I needed custom. Does anyone know anything about the Adtran 908e and if the only setting is 5ess. Thanks in advance!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Integrated Access with Adtran 908e? on Magix R4
- Thread starter mode1
- Start date
TouchToneTommy
Vendor
I recently did one where they set the Adtran to 4ESS, saying that the only protocol they had on 4 was AT&T Custom. Don't know if that will help!
dagwoodsystems
Programmer
Though a 5ESS can support NI-x protocol (just as a Nortel DMS supports AT&T Custom protocol), it wasn't always that way. That's probably why so many old school techs and manufacturers use the term "5ESS" interchangeably or in place of "AT&T Custom".
Last week a buddy of mine spent the better part of the day out at his customer's site. The situation was similar to yours in that it was a 3MB circuit that had been working for several months prior. In his case though, there were only 12 channels used for the voice piece.
The short version of the story is that the customer experienced a day-long power failure which, of course, caused to PRI to go down. Though the customer never opened a trouble ticket, an overenthusiastic tech on the carrier side got the bright idea to destroy and rebuild the circuit as a means to restore the service.
Naturally, there were no notes on the provider's end that anything like that happened. Correction: The fourth technician finally admitted it, but it took a lot of effort on Chris' part to hold his ground and a second DS1 board to dismiss the carrier's insistence that CPE failure was to blame. In the end it was not only a protocol mismatch (big surprise), but the two physical circuits at the Adtran needed to be swapped because the telco's channel mapping was whack.
You can tell your grandkids that story...just first tell them to stay the hell out of telecom so that they don't die young.
Tim Alberstein
Last week a buddy of mine spent the better part of the day out at his customer's site. The situation was similar to yours in that it was a 3MB circuit that had been working for several months prior. In his case though, there were only 12 channels used for the voice piece.
The short version of the story is that the customer experienced a day-long power failure which, of course, caused to PRI to go down. Though the customer never opened a trouble ticket, an overenthusiastic tech on the carrier side got the bright idea to destroy and rebuild the circuit as a means to restore the service.
Naturally, there were no notes on the provider's end that anything like that happened. Correction: The fourth technician finally admitted it, but it took a lot of effort on Chris' part to hold his ground and a second DS1 board to dismiss the carrier's insistence that CPE failure was to blame. In the end it was not only a protocol mismatch (big surprise), but the two physical circuits at the Adtran needed to be swapped because the telco's channel mapping was whack.
You can tell your grandkids that story...just first tell them to stay the hell out of telecom so that they don't die young.
Tim Alberstein
Telecomboy
Programmer
If you are not using all channels, I did have an issue with one recently. They were using 10 channels and I had it programmed for 10 channels, but they were still seeing those lines seize channels on their adtran. I finally busied-out the lines they weren't using on the PRI to solve the issue. I've never had to do that before, but the provider claimed becuase those channels were still trying to sieze lines it was causing the PRI to go down.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question