Re: (PM) [support@livingston.com: Re: [E108385] Adtran 2nd channel

Scott Drassinower (scottd@cloud9.net)
Tue, 28 Jul 1998 17:19:03 -0400 (EDT)

The debugging output that you are providing is largely useless, and it
isn't from the PM3. Since the PM3 is going to provide debugging info from
the telco and the actual contents of the PPP session, Lucent (or list
people potentially) are going to know exactly what is going on during the
call. Do you know what "NO_CIRCUIT_AVAIL or "NOT end2end ISDN" means from
the Adtran? Having the exact model of Adtran unit also can be pretty
helpful -- I think they make at least 3 different TAs.

We have never had DOSBS problems that I can recall. This is going back to
1996 with 5-BRI cards, to today with PM3s. As long as the telco got it
right, and the user got it right, the PM could get it right.

(fill in the name of a vendor) can only help you solve a problem if you
work with them and provide them with useful information. Providing
marginally useful debugging info that has unknown error codes and then
expecting a completely useful answer is unreasonable. Smacking around
support because you find their email formatting not to your liking,
because of a grammatical error, or because they are asking you to help
them obtain info that you don't want obtain, is kind of slimy.

If you need an answer quickly, pick up the phone. If you don't like the
answer you get on the phone, call back, or get a bossperson on the phone.
Did you or your customer even see if Adtran has updated firmware for their
product or speak to a higher up there to see if there is an Adtran issue
that their lower level support might be clueless about? Do you have any
other DOSBS customers that are using Netopia, 3Com, Ascend, or Motorola
equipment that are having problems?

--
 Scott M. Drassinower					    scottd@cloud9.net
 Cloud 9 Consulting, Inc.			       	     White Plains, NY
 +1 914 696-4000					http://www.cloud9.net

On Tue, 28 Jul 1998, Christopher Masto wrote:

> Ladies and Gentlemen, _this_ is the reason Livingston is No Longer My > Favorite Company. I wait a whole damn day for an answer and it's this > kind of shit. Forget the screwed-up quoting. Forget the grammar. > Forget the double spacing. I just wish that the people answering > support mail had a clue. Perhaps I wasn't perfectly clear and didn't > spell out that a customer dialing into us has MLPPP 2-channel ISDN, > makes a phone call on the POTS port of his TA (intentionally dropping > one of the channels), and occasionally it isn't reestablished when > he's done with the POTS call. But these people MAKE THE FRICKIN' BOX. > > It's not just this. It's also the time it took half a dozen > back-and-forth e-mails to get across the fact that DOVBS doesn't work > with a PM3 and a USR Courier I-Modem, despite what it says on > Livingston's web site, and when I asked them if they could just _try_ > it in their lab, I got back "sorry, we can't do that". > > I'm in a really lousy mood now. It's a very expensive product. It's > a very important product. And it's fast becoming a product product > with a hideously out-of-date, buggy, unsupported software base. My > original response to this message was "Are you on crack?! Please > reassign this ticket to someone who can read.". Then I took a short > walk (with all the customers calling to ask why their v.90, DOVBS, > etc. doesn't work, I don't have time for a long walk) and decided not > to send that. I just don't know what to do anymore; I'm sure there > are others out there who are as frustrated with this company as I am. > I hope we don't all have a collective aneurism from it. > > Deep breath. > > ----- Forwarded message from Steve Haug <support@livingston.com> ----- > > Date: Tue, 28 Jul 1998 11:28:14 -0700 > To: Christopher Masto <chris@netmonger.net> > From: Steve Haug <support@livingston.com> > Subject: Re: [E108385] Adtran 2nd channel reconnect problem > Cc: support@livingston.com > In-Reply-To: <19980727142014.A29224@netmonger.net> > Mime-Version: 1.0 > Content-Type: text/enriched; charset="us-ascii" > > At 02:20 PM 7/27/98 -0400, Christopher Masto wrote: > > > -Christopher > > > I need more information could you enter. > > > command>set console > > Command>set debug isdn on > > Commnad>set debug 0x51 > > > And dial the line in question. > > > -Please let me know > > > >One of our customers has reported that he occasionally encounters a > > >problem getting his second B channel reconnected. He uses an Adtran > > >ISDN TA (I don't know the exact model), and often makes/receives > > >analog calls, dropping the second channel of his ISDN connection. > > >Sometimes it doesn't come back. > > > > > >He has called Adtran and apparently they told him that it's the ISP's > > >fault; according to the diagnostic information they asked him to > > >connect, we're hanging up on them. They say that it will only try to > > >reestablish the connection once, so when this happens he has to > > >disconnect to get the second channel back. > > > > > >Do you have any thoughts on this? They say that the "NORMAL CLEARING" > > >lines are an indication of a problem on our end. > > > > > >We have a PM3 with PRI (AT&T 5ESS) running 3.8b15. > > > > > >----- Forwarded message from Dennis Baer ----- > > > > > >I have included a log of the failure to connect to the 2nd b channel after > > >disconnecting a voice call, just in case you cannot get file attachments. > > >The lower numbered lines indicated last operations. > > > > > > 1: NO_CIRCUIT_AVAIL > > > 2: Dialing ... 4 > > > 3: Disconnect 1 8324500 > > > 4: NORMAL_CLEARING > > > 5: Hang-up 2 > > > 6: Dialing ... 2 > > > 7: Disconnect 2 8324500 > > > 8: NORMAL_CLEARING > > > 9: Connected 2 8324500 > > >10: Dial 2 8324500 > > >11: NORMAL_CLEARING > > >12: Hang-up 2 12125551212 > > >13: Connected 2 12125551212 > > >14: NOT end2end ISDN > > >15: Dialing ... 2 > > >16: Disconnect 2 8324500 > > >17: NORMAL_CLEARING > > >18: MULTILINK PPP UP > > >19: Connected 2 8324500 > > >20: Dial 2 8324500 > > >21: END OF STATUS BUFFER > > > > > >Thank you. > > > > > >Dennis Baer > > > > > >----- End forwarded message ----- > > > > > >-- > > >Christopher Masto Director of Operations NetMonger Communications > > >chris@netmonger.net info@netmonger.net http://www.netmonger.net > > > > > > The problem (and the genius) regarding Microsoft's products is bloat. > > > Microsoft's penchant for producing overweight code is not an accident. > > > It's the business model for the company. ... > > > While [bloatware has] made Bill Gates the world's richest guy, it's > > > made life miserable for people who have to use these computers and > > > expect them to run without crashing or dying. > > > - JOHN DVORAK, PC Magazine > > > > > > > > Steve Haug, > > Technical Support Engineer > > Lucent Technologies, Remote Access Business Unit > > 4464 Willow Road, Pleasanton, CA 94568 > > support@livingston.com > > #925-737-2100 > > ----- End forwarded message ----- > > -- > Christopher Masto Director of Operations NetMonger Communications > chris@netmonger.net info@netmonger.net http://www.netmonger.net > > Microsoft does not innovate. It buys, imitates, or steals. It makes > things difficult for software developers, and thus eventually for > users. > - RICHARD BRANDSHAFT, San Jose Mercury-News > - > To unsubscribe, email 'majordomo@livingston.com' with > 'unsubscribe portmaster-users' in the body of the message. > Searchable list archive: <URL:http://www.livingston.com/Tech/archive/> >

- To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>