AWalker@RED.RUTGERS.EDU (*Hobbit*) (04/29/87)
Isn't this a bit redundant in these CCIS-ridden days? Also, it seems rather improper for an office to assume that any occurrence of 2600 on a subscriber loop indicates possible fraud. First of all, if someone wanted to defraud he'd just hike down to the nearest pay phone. Second, there are a lot of OCC switches that respond to 2600, so the phone co has another think coming if they believe I'm committing toll fraud every time I clobber one of them upon completion of a call. Fooey. The user-end symptoms of 2600 detection seem to be as follows: Beeeep. Switch disconnects your call, or whatever its fancy. Some switches drop the connection to the office completely, forcing the call to throw back to the office and return dial tone within a few seconds. At any rate, in the background one can hear a small "grack" sort of click -- I would assume that this indicates the bridging-in of the more sophisticated "fraud detection" equipment that would listen for and report various other tones. This is un-bridged again after about 20 seconds if nothing else happens. I could determine this because in some offices the bridging equipment is flakey and introduces extra line hum while it's connected. Would someone closer to the technical end of the above like to explain how this works in greater depth? And what is generally done with the generated reports when there's obviously no "fraud" happening on a given loop? _H* -------