Article View: alt.bbs.internet
Article #1889Do not use UUNET for ISDN access
From: David Thielen
Date: Mon, 16 Sep 1996 00:00
Date: Mon, 16 Sep 1996 00:00
51 lines
3115 bytes
3115 bytes
Hi; Here's the scoop. When we moved I switched to UUNET figuring that they had a better system than anyone else out there. When I signed on I was told that I could only get 128K access if, when I connected, both lines hit the same router (apparently they were waiting for a software update from Ascend). I was also told that within 2 months this would be fixed. Well, trying several times including a week straight where I tried at 2:00 - 3:00 AM - no luck on getting a 128K connection. And over 2 months passed and I was told that the router upgrade is still in the indefinite future. Now this is where it gets interesting -- because things can take longer than sales people promise. I have a permanent connection. Now, it would make sense to assign 1 router 1 set of call lines for a group with a permanent connection. Then each person in that group would get a 128K connection and nothing would be unused. This was discussed at UUNET and they decided to not do it. Why? No one knows. The second suggestion was to assign each router its own set of phone lines so you never have 1 line connect to 1 router and the second to another. Again, this was discussed at UUNET and they decided to not do it. My third request was for them to tell me if dialing in would/should give me a 128K connection at that time. While they have this capability, they will not do this. Why? No reason given. Here is what I think is happening. If they allow ISDN customers to connect at 128K, then they need twice the number of ISDN phone lines, twice the number of routers, and twice the bandwidth from those routers. So, by effectively limiting all ISDN users to 56K they cut their costs in half while still providing ISDN. And with quick talking sales people, no one realizes they are only getting half a line from UUNET. So, if you want full ISDN -- don't use UUNET. (And if you are in the D/FW area, call unicomp -- I got a FULL ISDN link from them with no problems.) - dave
Technical Details
Message-ID:
<323cc940.261245176@news1.alterdial.uu.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f9628,e83bc54c0148b90d,start X-Google-Attributes: gidf9628,public X-Google-Thread: f6a4e,e83bc54c0148b90d,start X-Google-Attributes: gidf6a4e,public X-Google-Thread: fb39a,e83bc54c0148b90d,start X-Google-Attributes: gidfb39a,public X-Google-Thread: f4f5d,e83bc54c0148b90d,start X-Google-Attributes: gidf4f5d,public X-Google-Thread: 100579,e83bc54c0148b90d,start X-Google-Attributes: gid100579,public X-Google-Thread: f5ebf,e83bc54c0148b90d,start X-Google-Attributes: gidf5ebf,public X-Google-Thread: 10bd82,e83bc54c0148b90d,start X-Google-Attributes: gid10bd82,public X-Google-Thread: fc7b2,e83bc54c0148b90d,start X-Google-Attributes: gidfc7b2,public From: dave@thielen.com (David Thielen) Subject: Do not use UUNET for ISDN access Date: 1996/09/16 Message-ID: <323cc940.261245176@news1.alterdial.uu.net> X-Deja-AN: 180834569 newsgroups: alt.bbs.internet,alt.internet,alt.internet.access.wanted,alt.internet.services,dfw.internet.providers,houston.internet.providers,me.internet,ne.internet.services,phl.internet