Path: utzoo!telecom-request Date: Tue, 16 Apr 91 20:07:18 GMT From: "Steven S. Brack" Newsgroups: comp.dcom.telecom Subject: Caller*ID From US PBXs Reply-To: "Steven S. Brack" Message-ID: Organization: Nyx, Public Access Unix (sponsored by U. of Denver Math/CS dept.) Sender: Telecom@eecs.nwu.edu 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 297, Message 14 of 15 Lines: 33 In article 443114@acadvm1.uottawa.ca (Eric Skinner) writes: X-Telecom-Digest: Volume 11, Issue 283, Message 3 of 8 > Bell returns the number of the calling trunk, which may be the correct > number to call, or which may be an outgoing-only trunk leading from a PBX. > The company's main number or a DID number would be appropriate in this > case. When I dial the local Pizza-Hut delivery number, their display returns the number of the outgoing trunk (614) 291-276X I'm on, not my phone number. It kind of surprised me that local businesses were getting any ID at all from Ohio Bell, as I didn't think Ohio Bell was approved to offer a service that looks & acts exactly like Caller*ID. Anyway, some details about our system: The University runs its own switch, and you can dial nearly any University phone directly from off campus by dialing 29N-XXXX, where N-XXXX is the on-campus extension number, N being a 2 or a 3. My questions: (1) What will Caller*ID show as my number? (2) What does E911 get as my number? (3) What would an Ohio Bell trace show as my number? P.S.: Any telecommers in the Columbus area: you may be interested in the tour of Ohio State's Telecommunications Center. Steven S. Brack Steven.S.Brack@osu.edu I don't speak for OSU. BitNet: Steven.S.Brack%osu.edu@ohstvmsa.bitnet