Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!netsys!vector!telecom-gateway From: jsol@bu-it.bu.edu (Jonathan Alan Solomon) Newsgroups: comp.dcom.telecom Subject: Local vs. Toll Message-ID: Date: 3 Jul 89 17:32:53 GMT Sender: news@vector.Dallas.TX.US Lines: 14 Approved: telecom-request@vector.dallas.tx.us X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@vector.dallas.tx.us X-TELECOM-Digest: volume 9, issue 223, message 2 of 4 I don't think the NJ DPU decision was meant to lower the number of local calls in a given exchange. I think what was meant was that if a town is connected to more than one exchange (local calling area boundary) which would normally cause a toll be charged, that now that call is local. New England Telephone has had that in place for years. You sometimes have to dial 1 first even for local calls in NET's rural areas, but the DPU here guarantees the same thing. Calls from anywhere within a municipality are local calls, even if the exchange boundaries differ. It's a billing hack. They just simply have to change their billing records so that the call is local. --jsol