pj@pnet51.orb.mn.org (Paul Jacoby) (12/15/90)
I have been experiencing a problem with a local system I call. The system is running a Telebit T2500, and is setup for V.32 connects. Calling with my shiny new Practical Peripherals 9600SA modem (which, incidentally, works great when properly configured), I can make a V.32/V.42bis connection with no problems. After that, I can generally do my thing for a number of minutes. Then, with no real warning, the T2500 will lock up completely. I cannot even drop the connection by popping back to command mode and typing ATh. I must cycle power on my end to clear the connections. The sysop of the system says has encountered the same problems dialing into his own board from his other V.32 modem (MultiTech). Is this a problem that anyone else has seen? In the meantime, MNP connections are working just fine. There appears to be something flaky with V.32/V.42bis connects. -----------------------------------------------------------------------------. | UUCP: {crash tcnet}!orbit!pnet51!pj | RTFD = Read The Silly Doc! | | INET: pj@pnet51.orb.mn.org | | `-----------------------------------------------------------------------------'
ddl@husc6.harvard.edu (Dan Lanciani) (12/16/90)
In article <3628@orbit.cts.com>, pj@pnet51.orb.mn.org (Paul Jacoby) writes: | | I have been experiencing a problem with a local system I call. The system is | running a Telebit T2500, and is setup for V.32 connects. Calling with my | shiny new Practical Peripherals 9600SA modem (which, incidentally, works | great when properly configured), I can make a V.32/V.42bis connection with no | problems. | After that, I can generally do my thing for a number of minutes. Then, with | no real warning, the T2500 will lock up completely. I cannot even drop the | connection by popping back to command mode and typing ATh. I must cycle power | on my end to clear the connections. I see a similar problem with two T2500s running in V.32 mode. (That should avoid finger-pointing at the-other-modem-maker...) I find that a retrain operation (AT&R) will "fix" the situation every time. The line-quality register is 100 before, during, and after the problem appears so I don't think it is really the retrain operation that fixes it, but rather some side effect. The whole thing happens at least every few hours of use. There does seem to be a bug in the T2500's V.32 mode. Telebit technical support wasn't very helpful on this. They first suggested sending ^Q (I mentioned I had already tried that) and then said that it sounded too hard to reproduce the problem. Odd that they couldn't leave a couple of modems up for a few hours... I appreciate the fact that Telebit got stuck with a bad V.32 chip set in the T2500, and that the T1600 is their hope for the future, but I also think they might still support the (relatively new) T2500s out there. (Unless there is a free upgrade that I missed... :) Dan Lanciani ddl@harvard.*
casey@gauss.llnl.gov (Casey Leedom) (12/20/90)
| From ddl@husc6.harvard.edu (Dan Lanciani) | | I appreciate the fact that Telebit got stuck with a bad V.32 chip set in | the T2500, and that the T1600 is their hope for the future, but I also | think they might still support the (relatively new) T2500s out there. | (Unless there is a free upgrade that I missed... :) I must have missed it too. What's worse, even with the T1600, Telebit, unlike many other modem manufactures, hasn't made any announced commitment to take on V.32bis when it's standardized. This plus the recently rotten technical support response (not because of the technicians, but because there are just too few of them), plus no announced upgrade path for the T2500 is causing me to re-evaluate my Telebit recommendation to others at LLNL. Since we buy a *LOT* of modems and my recommendation carries a *LOT* of weight here, we're talking about Telebit losing a fairly major account ... Unfortunately this note will fall of deaf ears since I've been informed that Telebit no longer monitors this newsgroup. In fact, as I understand it, modems@telebit.com is also no longer read ... Yet another cause for concern. I like Telebit a lot and I recommended their modems for good reason, but if they start screwing around with us this way, they're going to lose our business. Casey