Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!telecom-request From: 443114@acadvm1.uottawa.ca (Eric Skinner) Newsgroups: comp.dcom.telecom Subject: Re: Maestro Phones From Northern Telecom Message-ID: Date: 15 Mar 91 16:04:44 GMT Sender: Telecom@eecs.nwu.edu Organization: TELECOM Digest Lines: 33 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 205, Message 6 of 11 In TELECOM Digest Volume 11, Issue 199, Andrew Farmer writes: > Bell Canada returns the string "Long Distance" for all LD calls and > "Unknown Number" for calls from local/non-displayable numbers. The > Maestro phone, however, doesn't store the "Long Distance" string -- it > just stores them as "Unknown". Just the other day I received a collect call from a local payphone. I would have expected it to display "Unknown" as the call was placed through the operator, but instead, the display was "Long Distance." Go figure. About a week ago I spoke with someone at Bell Canada customer service about the fact that Caller*ID (here, at least) displays the actual originating phone number, instead of the billing phone number (ie. it might display any of a company's actual trunk numbers). She recorded my complaint, and indicated that "changes" to Caller*ID's implementation were forthcoming in June, but would not give me any further details. Eric Skinner 443114@acadvm1.uottawa.ca University of Ottawa +1 613 230 0261 [Moderator's Note: Probably the reason it said 'long distance' was because the payphone was a COCOT, and the Alternate Operater Disservice involved in handling the collect call was not really an Operator, and they splashed the call via DDD from some other location. Your telco saw it coming in from another LATA as just a regular call. PAT]