Article View: comp.dcom.telecom.tech
Article #189Re: Disconnect Timing (was Re: CALLER ID ~~ MYSTERY)
From: Dennis Wong
Date: Sun, 15 Dec 1996 00:00
Date: Sun, 15 Dec 1996 00:00
63 lines
4760 bytes
4760 bytes
Mark J. Cuccia wrote: > > Stanley Cline wrote: > > > > "Thomas C. Allard" <m1tca00@frb.gov> wrote: > > > > >I once got an unsolicted call and I just hung up without saying anything > > >other than "Hello" when I first answered the phone. She called right > > >back and said we must have been cut off. I said that we hadn't been > > > > What's REALLY bad is the telemarketers that "hang" the line -- that is, > > when you hang up THEY don't get dropped and when you try to call out > > they're STILL THERE! :( > > > > The CO in my area is screwed up and occasionally does this on > > NON-telemarketer calls -- I hang up and my line doesn't clear until the > > OTHER end hangs up as well. I have BellSouth looking into this. > > In many types of connections and switches (including inTER-switch calls), > the connection might not necessarily 'break' right away if the *called* > party hangs up first. It could take anywhere from five to thirty seconds for > the called party to be disconnected, available to make another outgoing > call, if the *calling* party hasn't hung up yet. > > It *used* to be, if the *entire* connection was done with step switches and > central offices, with *NO* panel/crossbar/ESS/Digital switching offices > involved in the connection, and with*out* any special > common-control/XB/timers patched into any of the step switches for the > calling party to hold up the connection 'forever' if they stayed offhook, no > matter what the called party did with their switch-hook. Of course, if telco > were informed by the called party that they couldn't place any calls, repair > and techs would trace out the connection, and manually 'break' it. > > Also, there can be an immediete forced disconnect... many times, when I call > the operator, even though I'm finished with my call, and ready to hangup, > the operator can 'force' me to a disconnect situation, before I even > actaully hangup. Sometimes, this can be done by radio station talk lines. On Some PBX systems ie. the Northern Telecom system. The phones have a "release" button on them. It makes you hang up the call. The radio station probaly uses a PBX. > The originating central office I'm in when I get a 'forced' disconnect from > my own c/o switch -- i.e. when the talkhost and I are finished with the > call, he 'releases' the call, but I get 'forced' disconnect to/in my own > central office. I think that 'class of service' indication is used as well > as SS7 signal delivery. > > I remember getting an immediete 'forced' disconnect when I called up > directory assistance in Guam, as 011+671-KLondike-5-1212. She answered "Guam > Directory, what listing?", and I asked for the main administrative office > number of GTA (Guam Telephone Authority). I went to 'auto-quote', "The > number is, 646-2100. Please make a note of this. Repeat, 646-2100. Thank you > for calling", and then had a 'forced disconnect supervision' from GTA, > through AT&T, to my own BellSouth switch. i.e., I was then hearing only the > 'rattling' clicks/pops from my own central office switch, a #1AESS. > > MARK J. CUCCIA PHONE/WRITE/WIRE/CABLE: HOME: (USA) Tel: CHestnut 1-2497 > WORK: mcuccia@mailhost.tcs.tulane.edu |4710 Wright Road| (+1-504-241-2497) > Tel:UNiversity 5-5954(+1-504-865-5954)|New Orleans 28 |fwds on no-answr to > Fax:UNiversity 5-5917(+1-504-865-5917)|Louisiana(70128)|cellular/voicemail
Technical Details
Message-ID:
<32B4D40A.17FC@mindlink.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<56r4jo$qp5@camel1.mindspring.com> <32916610.3149@worldnet.att.net> <3291A297.636C@worldnet.att.net> <56si1d$8lf@newstand.syr.edu> <57pq59$gjm@news.usf.edu> <32a194fe.5295808@nntp.ix.netcom.com> <57vqcr$khq@news2.his.com> <kevin-ya023480000212962043480001@news.his.com> <32A4346C.5D6D@net.com> <581gg7$gb5@news2.cais.com> <32A73BE9.3DBE@frb.gov> <32d58e37.101929376@news.mindspring.com> <32AF1B91.7430@mailhost.tcs.tulane.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10a9ce,8cb9bc158bc4606a X-Google-Attributes: gid10a9ce,public X-Google-Thread: f4e50,b04b4ce7cb859f48 X-Google-Attributes: gidf4e50,public X-Google-Thread: 101049,8cb9bc158bc4606a X-Google-Attributes: gid101049,public X-Google-Thread: 1038e3,b04b4ce7cb859f48 X-Google-Attributes: gid1038e3,public From: Dennis Wong <a15283@mindlink.net> Subject: Re: Disconnect Timing (was Re: CALLER ID ~~ MYSTERY) Date: 1996/12/15 Message-ID: <32B4D40A.17FC@mindlink.net> X-Deja-AN: 204337924 references: <56r4jo$qp5@camel1.mindspring.com> <32916610.3149@worldnet.att.net> <3291A297.636C@worldnet.att.net> <56si1d$8lf@newstand.syr.edu> <57pq59$gjm@news.usf.edu> <32a194fe.5295808@nntp.ix.netcom.com> <57vqcr$khq@news2.his.com> <kevin-ya023480000212962043480001@news.his.com> <32A4346C.5D6D@net.com> <581gg7$gb5@news2.cais.com> <32A73BE9.3DBE@frb.gov> <32d58e37.101929376@news.mindspring.com> <32AF1B91.7430@mailhost.tcs.tulane.edu> to: "Mark J. Cuccia" <mcuccia@mailhost.tcs.tulane.edu> content-type: text/plain; charset=us-ascii organization: MIND LINK! - British Columbia, Canada mime-version: 1.0 reply-to: a15283@mindlink.net newsgroups: comp.dcom.telecom.tech,misc.legal,dc.general,balt.general x-mailer: Mozilla 3.0Gold (Win95; I)