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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Partner T1 Card Question
- Thread starter ttech
- Start date
There have been reports of spontaneous system resets when the T-1 card is installed. I don't believe there has been a definitive answer as to why, nor have work-arounds been offered.
I have to believe that if 100% of the T-1 modules caused resets, they would have pulled the card from production. But with any new device/product/software, 6 months and one bug fix is typical before stability is achieved. Just ask anyone who runs any Microsoft product.......
I have to believe that if 100% of the T-1 modules caused resets, they would have pulled the card from production. But with any new device/product/software, 6 months and one bug fix is typical before stability is achieved. Just ask anyone who runs any Microsoft product.......
OldPhoneGuy
Technical User
Well, I suppose we could return to the old Bell System days where key systems and PBX's were in R&D for five years before they were released by Bell Labs for general use. Competition forces the end user being the testing facility. As 392 said, Just ask anyone who runs any Microsoft product.......
One of the worst offenders was Win Communications out of Atlanta. Early on, we were a prime dealer of Walker/Win products in a large city 250 miles away. When the 100D was released, we were sent several CPUs with versions lettered like "M" or "S". All the others were versions "R1.2" or such.
When we needed tech support, it was learned that the lettered versions were "field test beta" products, aka FTBs. There were extra "goodies" packed in the eproms we had no control over that they wanted to see if they failed before releasing them to the generral market as "R2.x" CPUs. Several times on one unit we had engineers calling in from Japan who re-wrote the eproms under the direction of the code writers in Malaysia while the system was running! I couldn't believe that. That was more like an Alpha CPU, not even close to a Beta. But there is at least one "M" unit that is still plugging away in a very busy federal office, so not all were bad.
So, given the choice between a fairly well engineered product from Avaya that may have some performance issues found after widespread implementation and a company that sends Alpha products to you as an unwitting participant in a field test, I'll take the Avaya edge every time!
When we needed tech support, it was learned that the lettered versions were "field test beta" products, aka FTBs. There were extra "goodies" packed in the eproms we had no control over that they wanted to see if they failed before releasing them to the generral market as "R2.x" CPUs. Several times on one unit we had engineers calling in from Japan who re-wrote the eproms under the direction of the code writers in Malaysia while the system was running! I couldn't believe that. That was more like an Alpha CPU, not even close to a Beta. But there is at least one "M" unit that is still plugging away in a very busy federal office, so not all were bad.
So, given the choice between a fairly well engineered product from Avaya that may have some performance issues found after widespread implementation and a company that sends Alpha products to you as an unwitting participant in a field test, I'll take the Avaya edge every time!
itpphoneguy
Technical User
Hi 392,
I second you there. Once you get to level three tech support at Avaya, you get the straight goods. I know they will work with you past midnight to get a system up!
I won't comment on Microsloppy except to say I also run other OS's that are stable.
-Chris
I second you there. Once you get to level three tech support at Avaya, you get the straight goods. I know they will work with you past midnight to get a system up!
I won't comment on Microsloppy except to say I also run other OS's that are stable.
-Chris
If it were the only source of dialtone for the system and/or the customer relied on the phone for cash flow or life issues (telemarketer/sales, service dispatch, medical facility), I'd wait. If it were a "normal" customer who was getting a deal on the T-1 and could stand a system reset now and then, I'd go for it. Copper backup is wise no matter the installation or use. Redundancy has its place, just in case of the unknown.
I have two ACS's with the T1 and one works great but the other does spontaneous system resets, the one that doesn't have any problems is about 6 months newer and gets worked twice as hard as the one that resets. Wonder if perhaps they have fixed the problem.
Just as a basic precaution ... we have a few in service that are working perfectly. I highly recommend using a REAL ACS R5.0 (upgraded to 6.0) or verified NEW R6.0 as there have been minor chip and board component changes after ACS R3.0/R4.0. In other words ... be sure to use NEWER/NEWEST style processors with the T-1, not an ACS R3.o or older or even R4.0 - upgraded to R6.0.
Just like Microsoft ... to play with the previous examples ... many of the problems that MS has had with their various software products have been with specific configurations/combinations of hardware in the PC or Server. The core software code didn't change and would run fine on 90% of the PCs out there - well except for occasional "blue screens of death".
My point is that some of the T-1 problems have been from the complex mix of components and inputs during installations of the new T-1 mod. Anyone familiar with a T-1 install knows what those can be just from the LEC/carriers side alone. My tier 4 Avaya contact says Avaya is preparing to release soon some info about these config problems. Who can guess what it will be.
Andrew Roach
President - Drew Telecom Group, Inc.
Lucent/Avaya Voice Mail-Component-Transtalk Repair Specialists
Lucent/Avaya Telecom Brokers/Resellers
drew@triton.net
269-685-5400 - voice
269-685-5500 - fax
Just like Microsoft ... to play with the previous examples ... many of the problems that MS has had with their various software products have been with specific configurations/combinations of hardware in the PC or Server. The core software code didn't change and would run fine on 90% of the PCs out there - well except for occasional "blue screens of death".
My point is that some of the T-1 problems have been from the complex mix of components and inputs during installations of the new T-1 mod. Anyone familiar with a T-1 install knows what those can be just from the LEC/carriers side alone. My tier 4 Avaya contact says Avaya is preparing to release soon some info about these config problems. Who can guess what it will be.
Andrew Roach
President - Drew Telecom Group, Inc.
Lucent/Avaya Voice Mail-Component-Transtalk Repair Specialists
Lucent/Avaya Telecom Brokers/Resellers
drew@triton.net
269-685-5400 - voice
269-685-5500 - fax
thephonelady
Vendor
Hi- If you are an Avaya Business Partner you can go on the Business Partner site and download a patch for R6 with T1. The patch is supposed to fix this problem and it will tell you what version of r6 needs the fix
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Question
- Question