I know out of all the ISDN customers I've got one of them had a strange
problem one day where his 2nd B channel would not authenticate properly. It
started putting an extra letter in his username. To verify it wasn't my
equipment I put my Radius server in debug mode and saw the extra letter
that way as well. I insisted to him that it wasn't us. It was an
intermittent problem. He sent that router in to be repaired and used
another brand in the meantime. It worked fine with the other brand. After
he got it back from "being repaired" it does the same thing on an
intermittent basis.
Another situation is where the phone company insisted the ISDN line was
fine all the way up to the customer's router. Well, as far as we were
concerned it wasn't. The ISDN line that we insisted wasn't working
correctly had been hit by lightning at least once and fried the Lucent ORU.
Fortunately, the customer had 2 ISDN lines so tried the other and it's been
working perfectly since.
Another customer has a strange problem on her ISDN line where it won't
connect some time and is really slow at either 64k or 128k. Bellsouth
insists it's not the line. She has supposedly had the ISDN router checked
out. She had the same exact problem with another local ISP.
Another customer had their ISDN line disconnect one morning. Our PM3 is
set to auto-reconnect using the Location type "Auto". The customer called
after they opened for business and asked "what the heck?" We found out by
accident when we called Bellsouth about their ISDN line that there was a
call being placed into their ISDN number so often it was producing a busy
signal when our PM3 called their Cisco 1604. We found that out by accident
because the BS tech said he saw a call going thru to the customer's ISDN
line. Well, I told him it wasn't me! He said it was a legitimate call and
not some kind of short or whatever.
Another one. Bellsouth is changing out area code from 502 to 270. They
sent everyone with ISDN lines a notice to change the router SPIDs after a
certain date. Well, we did and it didn't work. on some customer's ISDN
lines. Others successfully changed the SPID, it worked for a few weeks or
months and then one day the router needed to be turned off and turned back
on and the new SPID no longer worked. We had to change it back to the old
SPID.
Basically, we've found out that ISDN isn't as reliable as we thought it
was. At least with an analog modem you can try differnet techniques to make
it at least connect but with ISDN it usually either works or it doesn't.
Bill Dunn
VCI
At 11:00 AM 08/29/1999 -0500, Wayne M. Stenson wrote:
>
>
>>
>> > Having problems troubleshooting a mysterious disconnect on only one ISDN
>> > connection out of 22 total users. Router and Portmaster will display
>> > solid
>> > connections but until I reboot the Portmaster, the remote network
>> > cannot get
>> > to the internet. Any suggestions? I am out of ideas. Thanks.
>>
>> Sounds like a routing issue if they can connect but can not get to the net.
>
>Yes, it does sound like that doesn't. But its not. I've had a ticket open
>with Livingston support since a year ago. Its really a PPP problem. Rebooting
>the PM3 always fixes, temporarily. I've worked with both Livingston and
>Cisco on this problem with nothing but finger pointing by both organizations.
>
>Wayne
>
>--
>Wayne M. Stenson wstenson@inet-serv.com
>InterNetwork Services (612) 391-7300
>Maple Grove, MN (800) 488-7456
>A Minnesota Internet Access Provider (info@inet-serv.com)
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-modems' in the body of the message.
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-modems' in the body of the message.