"Steven S. Brack" <sbrack@isis.cs.du.edu> (04/17/91)
In article <telecom11.283.3@eecs.nwu.edu> 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
"Fred R. Goldstein" <goldstein@delni.enet.dec.com> (04/24/91)
In article <telecom11.297.14@eecs.nwu.edu>, sbrack@isis.cs.du.edu (Steven S. Brack) writes... > (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? In general, if you are behind a PBX, then the public network knows only about the PBX trunk or group you're on. In some cases the trunk will return a hunt pilot, in others its own number, depending upon how it's set up. But none of the above three services can know your extension number, even though it can be dialed directly. Extension info is passed from the CO to PBX on incoming calls (DID service) only. On Centrex, it would show the number for your extension. Story behind the story: Back in the olden days (when steppers were used), the telco used to provide two kinds of Centrex. Centrex-CO used CO switches; that's what we have today. Centrex-CU put a switch (usually a Bell 701 stepper!) on customer premises and delivered a similar service. (Generally you paid about a quarter/month/phone less for -CU, essentially as compensation for the switchroom space.) Centrex-CU did deliver your extension number for billing purposes, 911, etc. (If they had 911 back then!) This was done via a data link from the switch to the CO, reporting which extension had seized which trunk. When the stepper went away, this service was made available to newer PBX users, under the name "Automatic Identified Outward Dialing" (AIOD). Many PBXs of the day, such as Dimension, supported it. BUT it was frightfully expensive, something like $3/month/extension. Since it didn't bill for WATS or FX, few customers found it useful. When 1983 came (when the FCC ordered all PBXs detariffed; this had noth ing to do with divestiture!), the last few remaining Centrex-CU systems were handed over to AT&T and repriced as PBXs. The previously-bundled trunks, including both DID and AIOD, went under telco tariffs. The total price went WAY up. I'm not sure if modern PBXs even support AIOD. The telcos priced it out of the market. ISDN, on the other hand, includes the capability, so it may make a comeback. (If they don't charge for it. They have no justification to charge, since it's built in to the protocol.) AIOD would make caller*ID behave in the expected fashion. Fred R. Goldstein Digital Equipment Corp., Littleton MA goldstein@delni.enet.dec.com voice: +1 508 952 3274 Do you think anyone else on the planet would share my opinions, let alone a multi-billion dollar corporation?
John Higdon <john@zygot.ati.com> (04/24/91)
"Fred R. Goldstein" <goldstein@delni.enet.dec.com> writes: > I'm not sure if modern PBXs even support AIOD. The ITT 3100 still supports it. I have found it useful for using LD carriers that provide "account code" billing. Used with FGB, the switch calls the 950 number, outputs the company's authorization code, the called number, and then an account code based on the extension making the call. When the bill comes, it lists all the calls BY EXTENSION. Everyone knows this and abuse has dropped to virtually zero. John Higdon | P. O. Box 7648 | +1 408 723 1395 john@zygot.ati.com | San Jose, CA 95150 | M o o !
Vance Shipley <vances@xenitec.on.ca> (04/29/91)
"Fred R. Goldstein" <goldstein@delni.enet.dec.com> writes: > I'm not sure if modern PBXs even support AIOD. The SL-1 (or Meridian 1 if you prefer) by Northern Telecom does. Vance Shipley vances@ltg ..uunet!watmath!xenitec!ltg!vances
"Steven S. Brack" <sbrack@isis.cs.du.edu> (05/04/91)
In article <telecom11.301.3@eecs.nwu.edu> goldstein@delni.enet.dec.com (Fred R. Goldstein) writes: X-Telecom-Digest: Volume 11, Issue 301, Message 3 of 10 > In article <telecom11.297.14@eecs.nwu.edu>, sbrack@isis.cs.du.edu > (Steven S. Brack) writes... >> (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? > In general, if you are behind a PBX, then the public network knows > only about the PBX trunk or group you're on. In some cases the trunk > will return a hunt pilot, in others its own number, depending upon how > it's set up. But none of the above three services can know your > extension number, even though it can be dialed directly. Extension > info is passed from the CO to PBX on incoming calls (DID service) > only. Ohio State's PBX is an NT SL100. It is possible to dial a 7D number from outside the system & reach my phone, or almost any other. I apologize if I wasn't clear about the system OSU uses. OSU actually bought Ohio Bell's old 42X- exchange CO, and uses it for both its switch and its offices. Funny seeing a windowless building with offices in it. From my conversation with their switch engineer, OSU has T1 to Ohio Bell, and a Litel POP. It's not your "typical" PBX system. > On Centrex, it would show the number for your extension. > Centrex-CU did deliver your extension number for billing purposes, > 911, etc. (If they had 911 back then!) This was done via a data link > from the switch to the CO, reporting which extension had seized which > trunk. > When the stepper went away, this service was made available to newer > PBX users, under the name "Automatic Identified Outward Dialing" > (AIOD). Many PBXs of the day, such as Dimension, supported it. > I'm not sure if modern PBXs even support AIOD. > AIOD would make caller*ID behave in the expected fashion. I know local services getting ANI don't get the "true" number, and (after much cajoling and pleading) the ONI read back to me by Sprint (we switched to them a few weeks ago -- Sprint has some network interface problems with our lines, but that "will be fixed in the next software upgrade") was for the trunk I was on, not my actual number. Our system occupies the entirety of the 292- & 293- prefixes, with about 1000 extra internal numbers not directly reachable from the Bell side. PS: I had an interesting tour of OSU's telecom facility. They have great plans for the future, including full ISDN and other goodies. Personally, I'm waiting for Ohio Bell to sue for "unfair competition" 8) 8) Steven S. Brack sbrack@nyx.cs.du.edu I am not speaking for the Ohio State University. Now, if only I could convince them of that 8)
carroll@cs.washington.edu> (05/14/91)
In article <telecom11.331.4@eecs.nwu.edu> "Steven S. Brack" <isis!sbrack@uunet.uu.net> writes: > Funny seeing a windowless building with offices in it. It's even funnier working in one. Trust me. Jeff Carroll carroll@ssc-vax.boeing.com