Path: utzoo!utgpu!watserv1!ria!uwovax.uwo.ca!telecom-request From: ole@csli.stanford.edu (Ole J. Jacobsen) Newsgroups: comp.dcom.telecom Subject: AT&T Problem Solved Message-ID: Date: 15 Mar 91 16:28:09 GMT Sender: Telecom@eecs.nwu.edu Organization: TELECOM Digest Lines: 19 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 208, Message 12 of 14 Finally, late Wednesday the long distance problem I described was solved to by AT&T Long Distance Repair. The tech apparently had great difficulties convincing her supervisors that it was possible to make the call via other carriers, but *not* via AT&T. If you did, the result would be endless ringing at a bogus number which never answered, and according to the tech, "we don't test ring-no-answers..." The problem turned out to be an incorrect routing entry in the San Jose office, new prefixes are indeed entered manually which can lead to these kinds of problems. I wonder if I would have been able to get this fixed if there hadn't been other carriers ....? Ole J Jacobsen, Editor & Publisher ConneXions--The Interoperability Report Interop, Inc., 480 San Antonio Road, Suite 100, Mountain View, CA 94040, USA Phone: (415) 941-3399 FAX: (415) 949-1779 Email: ole@csli.stanford.edu Direct:(415) 917-2215