Path: utzoo!utgpu!watserv1!watmath!att!dptg!ulysses!andante!princeton!udel!wuarchive!cs.utexas.edu!umich!accuvax.nwu.edu!nucsrl!telecom-request From: CRW@icf.hrb.com (Craig R. Watkins) Newsgroups: comp.dcom.telecom Subject: Re: PA COCOT Checklist Message-ID: <13627@accuvax.nwu.edu> Date: 16 Oct 90 21:55:33 GMT Sender: news@accuvax.nwu.edu Organization: HRB Systems Lines: 24 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 10, Issue 741, Message 11 of 14 In article <13593@accuvax.nwu.edu>, Joel Upchurch writes: > Another couple of things to consider for your COCOT checklist: > 1. Does it try to charge you for long distance for local calls? From memory, I believe that the PA regulation is that the COCOT may not charge more than the tarrifed amount. Never had problems with that in this area, but then again, I avoid the suckers as much as possible. > 2. Does it comply with equal access requirements? This is an interesting point. My checklist was designed as a form for the PA PUC. From the regs that I read, I got the impression that PA doesn't have specific equal access regulations for COCOTs (although they might have been in a section that I didn't have a copy of). Craig R. Watkins Internet: CRW@ICF.HRB.COM HRB Systems, Inc. Bitnet: CRW%HRB@PSUECL.Bitnet +1 814 238-4311 UUCP: ...!psuvax1!hrbicf!crw