Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: Robert Halloran Newsgroups: comp.dcom.telecom Subject: Re: Info Needed on COLAN Message-ID: <10961@accuvax.nwu.edu> Date: 16 Aug 90 19:37:03 GMT Sender: news@accuvax.nwu.edu Organization: AT&T BL Middletown/Lincroft NJ USA Lines: 28 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 575, Message 9 of 11 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)? CO-LAN (at least the version I know about) is a data-over-voice network offered by some of the RBOC's. The user takes a VDM (voice-data mux), plugs it into the phone line, then connects the terminal/PC/whatever and the phone set into the VDM. The unit modulates the data stream above the voice band and carries it to the CO, where it is broken back out by another VDM there and typically fed into a Datakit VCS data switch for access to host services. The VDM can handle input to 19.2K baud. The user must be within three "wire-miles" of the CO for the VDM to be able to successfully drive the line. Our group (w/ NJ Bell) manages a CO-LAN for AT&T employees in four CO's of Monmouth county where the density makes it sensible (there must be a threshold number of potential users to justify parking the data switch at the CO). I know of at least one other CO-LAN for AT&T employees in northern NJ (the Murray Hill area). Bob Halloran Internet: rkh@mtune.dptg.att.com UUCP: att!mtune!rkh Disclaimer: If you think AT&T would have ME as a spokesman, you're crazed.