Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: "Marc T. Kaufman" Newsgroups: comp.dcom.telecom Subject: Re: Info Needed on COLAN Message-ID: <10935@accuvax.nwu.edu> Date: 15 Aug 90 15:50:49 GMT Sender: news@accuvax.nwu.edu Organization: Computer Science Department, Stanford University Lines: 23 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 573, Message 11 of 12 In article <10885@accuvax.nwu.edu> lih@probe.att.com writes: >Can anyone give a description or refer me to some documentation on >COLAN (Central Office Local Area Network)? DAVID systems has a PBX cum Ethernet which has been sold to Ameritech as a CO LAN. There are Ethernet jacks on the back of the phone sets, and any Ethernet capable equipment can be plugged in. Once the data gets to the PBX switch, it is turned into real Ethernet. "Real" Ethernet devices on coax can also be used with the system. Switches can be connected via coax, Ethernet, or (multiple) T-1 spans. Ethernet packets can be gatewayed between switches on any of these links. The CO LAN concept has all voice traffic directed to Centrex (thus removing the voice features of the PBX), while letting the PBX connect Ethernet packets within itself, and, via links to the CO, to other DAVID switches (hence: CO LAN). Marc Kaufman (kaufman@Neon.stanford.edu)