Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bu.edu!telecom-request
From: csense!bote@uunet.uu.net (John Boteler)
Newsgroups: comp.dcom.telecom
Subject: Answer Supervision From Loop Start Circuits
Message-ID: <74365@bu.edu.bu.edu>
Date: 9 Feb 91 17:06:20 GMT
Sender: news@bu.edu.bu.edu
Organization: TELECOM Digest
Lines: 26
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 104, Message 8 of 9


Tom Lowe describes a costly and painful procedure for extracting
answer supervision from NJ Bell.

Although my suggestion may not meet his exact requirements, it does
work flawlessly for my voice response systems.

Solution: order CENTREX. That's it! No special tariffs, no unnecessary
pain (other than the usual CENTREX programming screw-ups), and you get
features as part of the deal. The answer supervision is provided as an
OSI (Open Switch Interval) at least on 3*Way calls, and possibly on
single outbound calls when served by a #1ESS. #5s and their ilk are
another question.

This comes in handy for several applications I have running right now;
after finding damn few PBX manufacturers which sell PBX providing loop
interrupt to the stations, I like CENTREX better every day.

[Author's Note: Would ground start circuits provide the signalling
desired? Since they are engineered circuits, it would seem that such
signalling could be provided without a lot of pain. I don't see DOD
trunks as being special: many PBXs are configured this way.]

 
John Boteler   bote@csense                {uunet | ka3ovk}!media!csense!bote
SkinnyDipper's Hotline: 703 241 BARE | VOICE only, Touch-Tone(TM) signalling