US 6,665,376 B1Grant
Selectively activated integrated real-time recording of telephone conversations with automated documentation of consent to call recording
Issue Date:2003-12-16
•30 Claims
•29 Drawing Sheets
Abstract
A system for controlling and monitoring the recording of telephone calls in institutions such as jails and correctional facilities, and for obtaining consent to such recording and monitoring. Calls are recorded automatically in response to the occurrence of specific triggering events, as pre-defined under software control by a system administrator. Triggering events may include, for example, use of a specific line, attempts to use particular features (such as three-way calling), attempts to dial particular telephone numbers, or use by a particular person. Consent to recording or monitoring is obtained from either the calling or called party, or both, in a language selected for such party. Evidence of which prompts were played to request consent, the language of such prompts, and whether consent was given is stored in a computer readable record. Recorded calls are digitized and stored in standard MS-DOS files on either a local computer system or a remote computer across a network. Stored digitized recordings may be selected for playback under software control by a system administrator. The system of the present invention allows control of recordings from within a conventional telephone system. The integrated nature of the system provides cost savings and improved flexibility.
Metadata
Assignee
- T-Netix, Inc.
Inventor
- Barry D. Brown
Application Information
Application Number:US 09/178,367
Filing Date:1998-10-23
Priority Date:1998-10-23
Art Unit:7
Classifications
IPC:
H04M 164
Field of Search:
379112379 7379 8801379223379 671379372379 8822379 8379 3201379 9301455556
Patent Drawings (29 sheets)
Description
Background of the Invention
[0002] 1. Field of the Invention
[0003] This invention relates to the field of telecommunications, and more particularly to a system and method of automatically obtaining consent to the recording and/or monitoring of telephone calls, and the creation of persistent records of such consent.
[0004] 2. Description of the Related Art
[0005] Currently there exist various systems for automatically recording telephone calls in facilities, such as correctional facilities, in response to various types of triggering events or conditions. U.S. Pat. No. 5,535,261 generally describes one such automated and integrated telephone call recording system, and is incorporated by reference herein.
[0006] One of the issues that now arise in the recording of telephone calls is a concern for the privacy rights of the calling and called parties. Various state and/or federal laws require that the consent of either the calling party, the called party, or both, be obtained in order to record or monitor a telephone call. This requirement pertains regardless of whether the telephone call is placed and recorded between two private telephones, or in a sophisticated integrated telephone call recording system, as described in the above referenced patent, or between such telephone system and a telephone connected to the Public Basic Telephone Network.
[0007] However, in the context of integrated telephone call recording systems, such as may be used in prisons, jails, or other detention facilities, the legal requirements for consent to recordation impose substantial administrative burdens and technical hurdles, without providing any specific details about how such consent should be obtained. The technical challenges include providing an efficient, fast, and robust system that can accommodate obtaining consent from different parties in any of a number of different languages. The ability to handle multiple languages is important since prisons house inmates speaking a variety of different languages. In order to meaningfully consent to recordation of a telephone call, an inmate calling party or a called party must be able to understand a request for consent in their own language. Administrative burdens include creating and maintaining credible records of which evidence of the parties' consent can be easily established without requiring lengthy testimony by records custodians. Again, the legal requirements do not define how a system is to satisfy these technical and legal requirements.
[0008] Accordingly, it is desirable to provide an automated system which provides prompts for consenting to the recording of a telephone call in a variety of languages, either automatically or at the selection of a party to the call, and which creates and maintains useful records which establish the consent of the various parties.
Summary of the Invention
[0009] The preferred embodiment of the present invention operates in a telephone system for institutions such as jails and correctional facilities. It allows administrators to control and monitor the recording of telephone calls made by or to inmates, to automatically obtain their consent to the recording of such telephone calls, and provides computer-based records which evidence such consent.
[0010] In accordance with the present invention, there is provided a system and method for obtaining the consent of either a calling party, a called party, or both, to the recording or monitoring of a telephone call. The calling party places a telephone call to a called party by inputting a telephone number. The calling party also selects a language for hearing various prompts provided during processing of the telephone call. The telephone number and other parameters are checked to determine whether the telephone call may be recorded, or whether recording is prohibited. For example, the telephone number may be recorded in a file as being blocked for recording. Where recording is allowed, the calling party is prompted to consent to the recording of the telephone call. Where recording is not allowed, a prompt is played informing the calling party that the telephone call will not be recorded. The prompt is provided in the language selected by the calling party. An indication of which prompt was played and which language it was played in is stored in a call detail record for the telephone call. The telephone call is then placed to the called party.
[0011] A selection of a language for prompting the called party is made. The selection may be made by the calling party, by a system administrator, or by the called party. Alternatively, a number of prompts in different languages may be played so that a specific language selection is not required. Also, a previous language selection by a called party may be stored and used to select the language for prompts on subsequent telephone calls. An indication of which prompt was played to the called party, and in which language, is preferably stored in the call detail record. The called party's response to the prompt, such as consenting to the recording of the telephone call, is also preferably stored in the call detail record.
[0012] Recording of the telephone call, if allowed, then takes place upon the occurrence of certain defined triggering events. If recording is not allowed for whatever reason, then the triggering events do not cause recording. In an alternative embodiment, even if recording is prevented, for example, the telephone number being blocked for recording, the system administrator can issue a command over a network to initiate recording of the telephone call, and override the blocking restriction. Thus the network commands can override blocking restrictions on the telephone number.
[0013] In this manner, the system provides for automated management of consent to the recording of telephone calls. The present invention accommodates different legal requirements, including those that require the consent of the calling party, both the calling and called party, or neither party. The call detail record, preferably storing the identification of which prompts, languages, and the responses of the parties, provides a useful record of these facts. The call detail record can be easily authenticated in a legal proceeding if necessary to prove consent to the telephone recording.
[0014] The present invention may be embodied in computer executable software which provides the various functions of establishing telephone calls, selecting languages for prompts to the calling and called parties, prompting the calling and/or called party for consent to recording of the telephone call, and recording inputs indicating consent or refusal to recording of the telephone call. The present invention also encompasses a call detail record, persistently stored in a computer readable medium, which stores data for a telephone call to a telephone number indicating which prompts were played to the calling party and/or called party (e.g. prompts either requesting consent or informing that the telephone call will not be recorded), what language the prompts were played in, and whether the calling and/or called party gave consent to recording, if required.
Brief Description of the Drawings
[0015] FIG. 1 is a block diagram of the preferred embodiment of the invention.
[0016] FIGS. 2A and 2B are a flowchart showing the overall operation of the invention.
[0017] FIG. 3A is a sample Main Screen of the preferred embodiment of the invention.
[0018] FIG. 3B is a sample Secondary Screen of the preferred embodiment of the invention.
[0019] FIGS. 4A and 4B are sample entry screens for the System Parameter File.
[0020] FIGS. 5A, 5B, 5C, and 5D are sample entry screens for the Channel Parameter File.
[0021] FIG. 6 is a sample entry screen for the Number Control File Showing the Block Recording field.
[0022] FIG. 7 is a sample entry screen for the NPANXX Control File.
[0023] FIG. 8 is a sample entry screen for the NPA Control File.
[0024] FIG. 9 is a sample entry screen for the NXX Control File.
[0025] FIG. 10 is a sample entry screen for the Fraud Control Parameter File.
[0026] FIG. 11 is a block diagram of the software organization of the system.
[0027] FIGS. 12A to 12H show the structure of GWMAIN.EXE.
[0028] FIGS. 13A13B, 13C, and 13D are a flowchart showing the operation of GWMAIN.EXE.
[0029] FIG. 14 is an illustration of the call detail record.
Description of the Preferred Embodiment
[0030] The preferred embodiment of the present invention operates as an integral part of a telephone system such as the CPS-4000 offered by Gateway Technologies, Inc. Referring now to FIG. 1, there is shown a block diagram of a typical hardware environment for the present invention. The CPS-4000 telephone system 100 includes a standard personal computer 101, together with a conventional telephone interface board 102 and a speech digitizing board 103. Such boards are available from companies such as Dialogic, Rhetorex, and PIKA. Boards 102 and 103 are connected to disk storage 105 and (if desired) a network 106 via a conventional ISA bus 107. System 100 also includes line control cards 104 for providing switching and access control for the outside telephone lines and for calling phones connected to system 100. Cards 104 are connected to computer 101 via a parallel port 108.
[0031] Computer 101 contains central processing unit (CPU) 109 that runs software program instructions, stored in program storage 110, which direct CPU 109 to perform the various functions of system 100. Parameter and Control File Storage 114 stores information that is used by CPU 109 in performing the program instructions, as described below. Storage 114 is also preferably used for persistent storage of call detail records for the telephone calls. Random access memory (RAM) 111 is used as workspace while performing program instructions and other functions. The system administrator interacts with system 100 by supplying commands via one or more user input devices 112 (such as a keyboard, mouse, and the like). The system administrator can also control the system from a remote location over network 106. A display screen 113 may be used to provide status information and to prompt the administrator for commands.
[0032] In the embodiment illustrated herein, the hardware elements of computer 101 are conventional components of a personal computer or workstation. The inventive aspects of the present invention lie primarily in the software instructions, stored in program storage 110, that control the hardware elements shown in FIG. 1, and the control and parameter files stored in 114.
[0033] Referring now to FIG. 2, there is shown a flow chart of the overall operation of the system in accordance with the present invention. First, an administrator specifies 202 which telephone lines will be subject to recording, and identifies particular events that will trigger recording. The administrator also establishes consent parameters specifying whether consent is required by calling party, the called party, both, or neither. The administrator also establishes default conditions for selecting which language prompts will be used for obtaining consent to recording of telephone calls. This is done under software control, using input devices 112 and display screen 113 to modify control information as will be described in more detail below. These conditions are set in various flags, which are referenced during operation, as described with respect to FIGS. 13A-13D, below.
[0034] For each call made by or to an inmate, steps 203 to 216 as shown in FIGS. 2A-2B are performed.
[0035] The call is placed 203. The CPS-4000 system software automates this step. In processing the call, the system checks control and parameter files as described below, in order to determine whether the call should be blocked 215. If so, the call is blocked 216.
[0036] Then, the system checks 204 whether the call is being placed on a line that was specified for recording by the system administrator. This is done by checking control and parameter files as described below. If the line has been specified for recording, the system proceeds to step 217. If not, the system proceeds to step 210.
[0037] The system determines 217 whether consent is required for recording or monitoring of the telephone call. This determination is made from the consent parameters set by the system administrator generally, and/or for the particular telephone number being dialed for the telephone call. If consent is not required, the system continues at step 205, below.
[0038] If consent is required, the system plays 219 the appropriate prompts in a selected language to either or both the calling party and called party, as required by the consent parameters and using default language selections, and determines whether consent is given. If consent is given the system continues at step 205. If consent is not given, the system block 216 the telephone call.
[0039] The system then waits until either a triggering event occurs 205 or the call is completed 206. In order to determine whether a triggering event has occurred, the system consults parameter and control files 114, which contain definitions and specifications as to which events should trigger recordings, as described below. The system also monitors activity on the telephone line to check whether any of the specified triggering events has occurred.
[0040] In an alternative embodiment of the present invention, trigger events are also received over the network 106 in the form of network commands issued by, for example, a system administrator. Thus, if a call is not being recorded, but during the call process, it is observed that the call may be important and that recording the call could be beneficial, then the system administrator can override the issue a network command to trigger the recording of the call. These network commands can override any existing parameters in the number control file which would have otherwise prevented recording of the telephone call.
[0041] If the call is completed before a triggering event occurs, the system proceeds to step 210. If a triggering event occurs first, the system records the call 207, digitizes the recording 208, stores the digitized recording 209, and stores descriptive information regarding the call 215.
[0042] If there are more calls to be processed 210, the system returns to step 203. If not, the administrator may select recordings 211 to be played back. This is done under software control, using input devices 112 and display screen 113 to view information describing stored recordings and to select recordings. Selected recordings are converted 212 from digital form to analog, and the system then plays them back 213.
[0043] In the preferred embodiment, the above steps are performed under the control of software programs that are stored in program storage 110. Referring now to FIG. 11, there is shown the organizational structure of the software programs and associated files. The software programs include a main program, GWMAIN.EXE 1101, and eight support programs: SYSFILE.EXE 1102, CHNFILE.EXE 1103, IDSCR.EXE 1104, NPA.EXE 1105, NXX.EXE 1106, CTLFILE.EXE 1107, NPANXX.EXE 1108, and NUMBER.EXE 1128. The support programs are used to provide administrator access to parameter and control files, as shown in FIG. 11: System Parameter File SYSFILE.DTA 1109, Channel Parameter File CHNSCR1.DTA 1110, ID Files 1111, NPA Control File NPA.DTA 1112, NXX Control File NXX.DTA 1113, Fraud Control Parameter File 1114, NPANXX Control File NPANXX.DTA 1115, and Number Control File NUMBER.DTA 1127.
[0044] ID Files 1111 include three components: PIN.DTA file 1123 containing information about the inmates; PINS.DTA file 1124 containing information about the allowed numbers for the inmates, including whether recordings should be made for particular numbers when called by particular inmates; and PINSET.DTA file 1125 containing Class of Service information that can be used to selectively activate recordings based on the selection of the Class of Service for the telephone call. These files are used for validation of the called number and to set certain parameters during the call. Specifically, these files contain fields that activate the digital recording feature automatically if the system administrator has indicated that recordings are to take place. Thus, recordings can be made for particular called numbers, particular inmates placing calls, or by a combination of the two parameters. The system administrator can also control recordings on a line-per-line basis using a keyboard function key.
[0045] Also included are: drivers 1116 such as Dialogic D40, for providing communication between the Disk Operating System (DOS) of computer 101 with boards 102 and 103; a database management system 1117 such as Btrieve, for maintaining database files 1126, various language files 1118 including, among other things, prompts and messages recorded in various languages, file indexes 1119; and a files configuration file named FILES.DAT 1120.
[0046] A DOS batch file called START.BAT 1122 initializes the required drivers, namely D40DRV.EXE and BTRIEVE.EXE in the preferred embodiment. START.BAT 1122 also selects the desired operating characteristics of GWMAIN.EXE 1101 by the use of command line parameters. The following is a representative list of command line parameters that may be used in the preferred embodiment:
[0047] v=display version number and exit
[0048] b=Gateway Line Interface boards are being used
[0049] r=this implementation is allowed to make recordings
[0050] px=use parallel port x for communication with the Line Interface Boards
[0051] d=turn off DTMF detection
[0052] l=no loop current extenders on boards
[0053] f=turn off full reporting on F7 display
[0054] c=concentrator in use
[0055] e=screen saver turned on
[0056] a=allow Free call cut-through without wait for answer detection
[0057] x=switch relays on messages for Rhetorex boards
[0058] 0=single zero DTMF detection enabled
[0059] The following is a typical START.BAT file 1122:
[0060] @ echo off
[0061] d40drv-e512
[0062] btrieve/p:4096/f:32/m:64
[0063] gwmain-r-b-p1
[0064] Language files 1118 are ADPCM compressed, digitized voice prompts stored in a standard DOS file. This file is then indexed using file indexes 1119 to allow access to each of the voice prompts within the file. The voice prompts include various prompts for requesting consent to recording or monitoring of telephone calls and various messages to inform whether recording and/or monitoring may be performed during a call. In the preferred embodiment, language files 1118 are designated as english.vox and spanish.vox, and file indexes 1119 are designated as index.1, index.2, etc. Additional language files and file indexes may also be provided.
[0065] In the preferred embodiment, descriptive information concerning calls is placed in output files called Call Detail Record (CDR) files 1121. These files are stored on drive “D:” in a subdirectory called CDR. The files include information such as start time, stop time, calling number, called number, user id, call disposition codes, error codes, and validation codes. FIG. 14 illustrates the structure of a call detail record. Persistent storage of the call detail records allows for subsequent retrieval and authentication to establish whether a particular telephone call was recorded, and if so, whether consent was given, and in which language prompts were played for such consent. In a preferred embodiment, the clock used to generate timestamps for the call detail record is synchronized with the system clock that is part of the call processing system which generates a call log of each telephone call that is made. In this manner, the call log record of when a telephone call was made can be easily matched against the call detail record to show that consent was given for recording that telephone call, since the times in both records are matched.
[0066] Database files 1126 include other files used by the system, including: .nme, for storing user names during call progress; .cnrm, for storing called party names for person-to-person collect calls; EMERG.LOG, for storing information about emergency calls made within the facility using an internal alarm system; RECORD.LOG, for storing information about recordings; DEBUG.DTA, for storing debugging data; and .nbr, for storing callback numbers. The designation “ ” refers to a number indicating a particular telephone line. Thus, for example, the name for line 15 would be stored in file 15.nme.
[0067] FILES.DAT 1120 is a data file used by the system to determine the location of necessary files for GWMAIN.EXE 1101. For each file needed by the system, FILES.DAT 1120 lists a file identifier and a path indicating the location of the file in Parameter and Control File Storage 114. The following is a typical FILES.DAT file 1120:
[0068] NUMBER, d: number number.dta
[0069] SYSTEM, sysfile.dta
[0070] CHANNEL, chnscr1.dta
[0071] GRID, idscr.dta
[0072] NXX, nxx.dta
[0073] NPA, npa.dta
[0074] NPANXX, npanxx.dta
[0075] INDEX1, c: main speech index.1
[0076] INDEX2, c: main speech index.2
[0077] INDEX3, c: main speech index.3
[0078] INDEX4, c: main speech index.4
[0079] LNG 1, c: main speech english.vox
[0080] LNG2, c: main speech spanish.vox
[0081] CDR, d: cdr
[0082] RECORD, d: recs
[0083] Recordings are stored in disk storage 105 at a location specified by the RECORD identifier of FILES.DAT 1120.
GWMAIN.EXE
[0084] GWMAIN.EXE 1101 is the main program for controlling the operation of the system. GWMAIN.EXE 1101 is an event-driven, real-time, multitasking program that runs in conjunction with MS-DOS 5.00. It is modular in design, allowing for control of complex functions while facilitating program maintenance and updates for future applications. GWMAIN.EXE 1101 uses parameter files and control files 1109-1127 that can be easily changed to maximize flexibility and ease of support.
[0085] The structure of GWMAIN.EXE 1101 is shown in FIGS. 12A-12H. Each of the items shown in these figures is described in Table 1 below:
| TABLE 1 | |
|---|---|
| Routine Reference Number | Description |
| chkargs 1201 | Parses command line parameters, scts global variables based on |
| parameters | |
| sysexit 1202 | Closes all files, writes closing CDR record, shuts down all lines, exits |
| from program | |
| get--fnames 1203 | Reads and parses FILES.DAT file |
| sysinit 1204 | Initializes device drivers, opens files, initializes all lines and variables |
| get--system--info 1205 | Reads in SYSFILE.DTA information |
| setup--dcb 1206 | Initialized Device Control Block using information from SYSFILE.DTA |
| set--idle--flag 1207 | Sets flag to force serialization of DOS commands such as disk |
| reads/writes - will not set flag or allow further operation on the line while | |
| flag is set | |
| write--btrv--log 1208 | Writes error log on any error during use of a database file |
| clear--idle--flag 1209 | Resets DOS serialization flag |
| curoff 1210 | Turns off screen cursor |
| get--lcctrl--info 1211 | Reads LCCTRL.DTA file |
| get--channel--info 1212 | Read CHNSCRLDTA file - sets up channel parameter block using read |
| information | |
| read--file 1213 | Read information from CHNSCRLDTA file |
| move--data--in 1214 | Move channel information into Channel Parameter Block |
| start--clock 1215 | start interrupt driven clock and time and date display |
| commissary--active 1216 | Compares current date/time with Commissary setup and sets/resets |
| commissary open flag | |
| open--btrv--files 1217 | Opens database files for use by the system |
| open--other--files 1218 | Opens speech files |
| setup--channels 1219 | Initializes each line |
| getch1 1220 | Waits for key press |
| setport 1221 | Sets relays on Line Interface board via parallel port |
| write--cdr 1222 | Writes CDR record into daily CDR file |
| check--time 1223 | Synchronizes PC clock with CMOS “real-time” clock, checks to see if |
| upload files needs to be checked, screen displays updated | |
| disp--msg 1224 | Displays line status information on screen |
| disp 1225 | Routine to write text directly to video memory |
| check--loop--current 1226 | Checks Line Interface Board to see if loop current change has occurred |
| check--inside 1227 | Checks inside line loop current |
| check--outside 1228 | Checks outside line loop current |
| check--loop--drop--time 1229 | Checks length of loop current drop |
| check--for--phone--onhk 1230 | Checks to see if inside phone is on-hook |
| blank--screen 1231 | Screen saver routine |
| displ 1232 | Routine to write text directly to video memory and ignore screen updates |
| while screen is blanked | |
| check--reboot--okay 1233 | Makes sure that no lines are in use |
| reboot 1234 | reboots system |
| check--random 1235 | Checks to see if random interval has elapsed for playing anti-fraud |
| messages | |
| display--debug--screen 1236 | displays screen of information useful during debugging |
| display--current--screen 1237 | redraws current screen |
| disp--screen1 1238 | displays primary screen |
| rst--bottom 1239 | clears system message area of screen |
| disp--screen2 1240 | display secondary screen |
| disp--calls 1241 | displays call count information on secondary screen |
| disp--okay 1242 | displays okay count information on secondary screen |
| disp--deny 1243 | displays denied count information on secondary screen |
| disp--bad 1244 | displays bad count information on secondary screen |
| waitevt 1245 | main loop - waits for event to be reported back from device drivers |
| check--for--out--of | checks to see if out-of-service time has occurred |
| --service 1246 | |
| disp--screen3 1247 | displays third screen |
| display--screen--msgs 1248 | displays call progress information |
| disp--screen3--data 1249 | displays third screen information |
| check--for--uploads 1250 | checks to see if upload file exists |
| parse--num--rec 1251 | parses number record from upload file and updates NUMBER.DTA |
| strtok1 1252 | parses string based on comma delimiter |
| parse--??????--rec 1253 | parses specified record type from upload file and updates local files |
| get--upload--records 1254 | reads upload records from upload file |
| time--change--check 1255 | checks to see if daylight savings time change is needed |
| lines--open 1256 | used by time--change--check to make sure no lines are being used when |
| time is changed | |
| kbhit1 1257 | routine that tells if key has been pressed |
| get--input 1258 | read keyboard and perform commands |
| clr--bottom 1259 | clear System Messages area |
| new--verify 1260 | verify called number using local tables |
| check--blockcode 1261 | check NUMBER.DTA, NPANXX.DTA, NPA.DTA and NXX.DTA files |
| for block code | |
| check--for--number 1262 | verifies that number is in NUMBER.DTA |
| check--limits 1263 | checks to see that fraud limits have not been exceeded |
| get--cos--limits 1264 | get class of service limits from file |
| check--rollover 1265 | see if fraud limits should be rolled over |
| to--julian 1266 | converts MM/DD/YY to Julian date |
| from--julian 1267 | converts Julian date to MM/DD/YY |
| dow 1268 | returns day of week |
| set--call--parameters 1269 | sets record, alarm, etc. based on data in NUMBER.DTA |
| check--npanxx 1270 | checks number in NPANXX.DTA file |
| check--npa 1271 | checks number in NPA.DTA file |
| check--nxx 1272 | checks number in NXX.DTA file |
| disp-sys--msg 1273 | displays message in system message area of screen |
| prt--codes 1274 | prints debugging codes on screen |
| stop--clock 1275 | turns off real time clock and time and date display |
| watch--dog--long 1276 | sets hardware watchdog to 30 minutes |
| curon 1277 | turns cursor on |
[0086] When GWMAIN.EXE 1101 runs, it accepts command line parameters specifying various options and configurations, including:
[0087] Specification of the type of interface boards 102, 103 and line control cards 104 being used;
[0088] Specification of which port to use to communicate with line control cards 104;
[0089] Specification of interrupt lines for boards 102, 103; and
[0090] Enablement of DTMF detection during a call (to terminate the telephone connection when certain digits are dialed during a call).
[0091] As described above, command line parameters are specified in a DOS batch file named START.BAT 1122 that initializes the system by loading GWMAIN.EXE 1101 in a conventional manner.
[0092] Referring now to FIGS. 13A to 13D, there is shown a flowchart of the operation of GWMAIN.EXE in the preferred embodiment.
[0093] The system checks 1301 to see if the telephone is off-hook. If so, it displays “WAIT” 1302. Then, it prompts 1303 the calling party to select a language for playing various prompts, including prompts regarding whether the telephone call may be recorded. If the calling party presses “1”, the system uses 1304 English; if the user presses “2”, the system uses 1305 Spanish. Additional languages beyond English and Spanish may also be offered, with corresponding input numbers, and decoding logic. If the user presses “3” or an invalid selection, or if there is a timeout, the system considers this to be an invalid selection 1306, informs the user that the call cannot be completed 1307, checks that the calling party has hung up, 1309, and if not, sounds a “fast busy” signal 1308, until the phone is hung up, and returns to step 1301.
[0094] After a language has been selected, the system prompts the calling party 1310 to dial a telephone number. If the calling party dials an invalid number or there is a timeout 1311, the system informs the calling party that the telephone number is not valid 1312A, checks that the calling party has hung up 1309, and returns to step 1301.
[0095] If the calling party dials a valid telephone number 1312B, the system checks to see whether the telephone number is authorized 1314 by referring to the control files described above. If not authorized, the system informs the calling party that the telephone number is restricted 1313 and returns to step 1309. If the telephone number is authorized, the system checks 1315 to see whether any limits have been exceeded for this telephone number. If the calling party has reached a maximum number of denied calls 1316, a maximum number of accepted calls 1317, a maximum number of minutes called 1319, or a maximum number of attempted calls 1331 to the number, the system returns to step 1309, preventing the telephone call from taking place. If none of the limits have been exceeded 1318, the system proceeds to check whether a recording is to be made of the telephone call.
[0096] First, the system sets 1320 a record flag for this call to “off” to establish a default condition that this call will be not recorded unless certain tests are satisfied.
[0097] The system then tests 1321 whether a record flag has been set in the NUMBERS.DTA file 1127 for this telephone number. If this flag is set, then the call should be recorded unless other selections or events override and if the calling party and/or called party give the appropriate consents, as previously determined by the site administrator.
[0098] If the record flag is set, then the system checks 1323 whether a no-record flag has been set for this telephone number in the NUMBERS.DTA file 1127. This flag is used to indicate that no recording of telephone calls to this telephone number are allowed, for example, where the telephone number is for an attorney. If the no-record flag is set, then the system updates 1326 the call detail record for the telephone call to indicate that no recording is to be made of the telephone call.
[0099] If the NUMBER.DTA file 1127 does not indicate that the telephone call should be recorded, then the system checks 1324 whether the PIN.DTA file 1123 indicates that recordings are to be made. If so, the system again checks 1323 the no-record flag, as above.
[0100] If the flag in the PIN.DTA file 1123 is not set, then the system checks 1327 the PINSET.DTA file 1125 (class of service) to determine if the telephone call should be recorded. If so, the system checks 1323 the no-record flag, as above.
[0101] If the no-record flag is not set, and any one of record flags in the NUMBERS, PIN, and PINSET data files is set, then the telephone call may be recorded, and so the record flag is set 1322. This enables the telephone to be recorded.
[0102] At this point, the system tests 1322A whether a play record message flag is set. This flag is set by the system administrator where consent of the calling party is required. If set, the system will attempt to obtain the calling party's consent to recording the telephone call by playing 1325 a first prompt, in the language previously selected by the calling party, requesting that the calling party consent to the recording/monitoring of the telephone call. The system checks 1328 whether calling party pressed “1” to consent to the recording. If so, the system updates 1327 the call detail record with a consent flag, indicating that the calling party has consented to the recording. The language in which the prompt was played may also be recorded in the call detail record. This information may be subsequently used to efficiently prove that consent to the recording was given by the calling party by simply producing and authenticating the call detail record for this telephone call.
[0103] If the calling party did not consent to the recording, the system returns to step 1309.
[0104] Next, the system prompts the calling party 1329 to state his or her name; this name is recorded for subsequent playback to the called party. The system then dials the phone number 1332, and waits until an event is detected 1333. If busy 1334, the system so informs the calling party 1338 and returns to step 1309. If a Special Intercept Tone (a triple tone generated by the telephone company to indicate that the number has been disconnected or the network is busy; also called SIT) has sounded 1335, or there is no ring 1336, or there is no answer 1356, the system so informs the calling party 1339 and returns to step 1309.
[0105] If a connection is made 1337, the system now determines the language in which to prompt the called party for a consent to the recording of the telephone call, and to obtain this consent. First, the system checks 1341 whether an English flag is set in the SYSTEM.DTA file. If so, then the system sets 1343 the language of this second prompt to be English.
[0106] If the English flag is not set, then the system checks 1345 whether a multi-language flag is set in the SYSTEM.DTA file. If so, then the system 1347 queues all of the different language prompts for sequential playback to the called party. In this fashion, the called party hears the request for consent to recording in several different languages, without having to select which language to hear the prompt in.
[0107] If the multi-language flag is not set, then the system checks 1349 whether a called party language has been pre-selected, in which event a specific language has been designated for the second prompt. Pre-selection may be made by the system administrator, the calling party (via a prompt requesting the calling party to select the language, similar to steps 1303-1305), or by a previous selection by the called party. If the pre-selected flag is set, then the system sets 1351 the language for the second prompt to the pre-selected language.
[0108] If the pre-selected flag is not set, then the system checks 1353 whether the called party selection flag is set. This flag indicates that the called party is to select the language for the second prompt. The system then requests 1355 the called party to select a language, similar to the steps by which the calling party selected the language for the first prompt, in steps 1303-1305. The calling party's key press input is processed to determine the selected language, and the system sets 1359 the language to the selected language. In this fashion the calling party may have the first consent prompt in one language, and the called party may have the second consent prompt in another language. The called party's language selection may be stored in association with the telephone number in the NUMBERS.DTA file for subsequent use as the pre-selected language the next time that telephone number is called. In this fashion, the language for this prompt need only be selected one time by the called party. This feature is beneficial since it reduces the amount of time the telephone call is connected, and thus reduces additional telephone charges.
[0109] If the called party selection flag is not set, then the system defaults and sets 1357 the language of the second prompt to the language previously selected by the calling party.
[0110] The above steps represent a large variety of steps for selecting the language of the second prompt. In alternate embodiments, some of these may be eliminated, or used in various different orders or combinations.
[0111] Once the language of the second prompt is selected, the system checks 1361 whether the no-record flag is set. As above, this flag will determine whether the telephone call can be recorded. If set, the system plays 1363 the appropriate prompt informing the called party that the telephone call is confidential and will not be recorded or monitored. The system next prompts 1365 the called party that there is a collect call from the calling party, inserting the recording of the calling party's name into the prompt playback. The called party is requested to press “0” to accept the call charges. The system checks 1367 whether the call is accepted, by testing the called party's keypress. If the call is not accepted, then the system returns to step 1309. If the call is accepted, then the system updates 1379 the call detail record to indicate which prompt was played (here the prompt indicating that the telephone call is not recorded), and the prompt language that was used for the prompt.
[0112] If the no-record flag is not set at step 1361, then the system checks 1399 whether the ask called party flag is set. This flag indicates that the called party must consent to recording of the telephone call separately from accepting the call. This flag is set by the system administrator according to the state or federal law applicable to the prison or detention facility. The ability for the system administrator to set this flag makes the present invention flexible and adaptable for use in different jurisdictions, since some jurisdictions may require specific called party consent, and others may not. The system proceeds to obtain the called party's consent to recording and/or monitoring of the telephone call.
[0113] If the ask called party flag is set, then the system provides for an explicit consent to recording, and a separate consent to acceptance of the telephone call. First, the system prompts 1369 the called party with the second prompt in the selected language, informing the called party that the telephone call may be recorded or monitored, and requesting an input of “0” if the called party consents to such recording. The system tests 1371 whether consent was given by the called party. If not, the system returns to step 1309, terminating the telephone call.
[0114] If consent is given, then the system next prompts 1373 whether the called party will accept the charges for the collect call, as above. The system checks 1367 whether the called party accepts the charges. If so, the system proceeds to update 1379 the call detail record to indicate which prompts were played (here the prompts for requesting consent and acceptance) and which language was used for these prompts to the called party. In this fashion there is a computer readable record which identifies the specific prompts that were played to both the calling and called parties, and the languages of the prompts. This information is useful in legal proceedings to demonstrate the parties' knowing consent to any recording or monitoring of the telephone call. Consolidation of the indications of consent and language into a single call detail record for a specific telephone call simplifies the authentication of the record, and the evidence of consent. If the call is not accepted, then the system terminates the call, and continues at step 1309.
[0115] If the ask called party flag is not set, then it is not necessary to obtain specific consent to the recording/monitoring of the telephone call. Accordingly, in this embodiment, a single prompt is played 1375 informing the called party that the telephone call may be recorded/monitored, and requesting the called party to either accept or decline to consent to recording and to accept the telephone call and charges. If the call is accepted 1367, then the call detail record is updated 1379, again indicating the prompt that was played and the language. If the call is not accepted, then the call is terminated, and the system returns to step 1309.
[0116] Once the system has updated 1379 the call detail record, the system lets the telephone call proceed 1381. While the conversation takes place, the system checks for the occurrence of events. When an event is detected 1382, the system reacts as follows.
[0117] If a 3-way telephone call is initiated 1387, the system checks 1391 the control files to determine whether recordings are to be made for 3 way telephone calls. If not, the system returns to step 1381, and continues to monitor for events. If so, and if allowed, it starts recording 1392 and returns to step 1381. When a telephone call is recorded 1392, a flag may be set in the call detail record indicating this fact
[0118] If the calling party hangs up 1388, the system returns to step 1309.
[0119] If there are only 60 seconds remaining in the time limit for this telephone call or for this telephone number 1383, the calling party is so informed 1384 and the system returns to step 1381.
[0120] If there are only 15 seconds remaining in the time limit for this telephone call or for this number 1385, the calling party is so informed 1386 and the system returns to step 1381.
[0121] If the time limit is reached for this telephone call or for this number 1389, the system terminates the telephone call, returning to step 1309.
[0122] Optionally, if a network command 1395 is received by the system from the system administrator, then the system can begin recording of the telephone call, even if the no record flag was set for this telephone number; in this manner the system administrator can record a telephone call, for example, if the inmate calling party waives confidentiality of the telephone call to an attorney.
[0123] Optionally, if the system detects 1393 that the calling party is dialing digits, attempting to conference another party in, or otherwise contact another party, the system can terminate the telephone call, begin recording of the call, or other processes, depending on what event was detected, and either returning to step 1381 or returning to step 1309 on termination.
[0124] The above described method of operation thus provides for a fully automated process of requesting and obtaining the consent of either the calling party or the called party, in any of a variety of languages, and further provides for the creation of a computer readable, persistent record which can be used to prove that consent was given.
[0125] Referring to FIG. 14, there is shown a diagram of a call detail record and its fields. The call detail record 1400 is stored in a computer readable memory or medium, such as RAM 111, or more preferably in persistent storage, such as storage 114. The call detail record 1400 includes the following fields particular to the present invention. A message played field 1402 stores the flags which indicate which prompts were played, for both the calling party and the called party, and the languages they were played in. Flags indicating which prompt was played may also encode which language, by having each combination of prompt and language identified by a specific flag or field code. In the disclosed embodiment this field is updated in steps 1327 and 1389.
[0126] The recorded field stores the flag indicating whether the telephone call was in fact recorded. This field is optional, and used in embodiments where evidence of whether a particular call was or was not recorded is desired.
[0127] The accept code field stores flags indicating whether the calling party and/or the called party consented to the recording of the telephone call, and also whether the called party accepted the charges for the telephone call.
[0128] Persistent storage makes the call detail record for a telephone call makes this record available for use in legal proceedings that challenge whether the telephone call was legally recorded. The evidence of which prompts were played, and whether the parties consented to the recording is useful information that can be easily authenticated in a legal proceeding, and used to establish the parties' consent.
[0129] Referring now to FIG. 3A, there is shown a Main Screen 300 for the system, as it would appear on display screen 113. Main Screen 300 includes the following information about the telephone lines:
[0130] Ln 301: The line number.
[0131] Status 302: The current operational state of a telephone call. For example, when INSTRUCT is displayed, the system is playing a voice prompt instructing the calling party to dial zero plus the number he or she wishes to call (step 1310 in FIG. 13). When ASK NAME is displayed, the system is asking the calling party to state his or her name (step 1329). When GET NAME is displayed, the system has asked the calling party to state his or her name and is now waiting for the recording of the name to complete (between steps 1329 and 1330). When THANKS is displayed, the system is playing a message saying “Thank you for using Gateway Technologies” (step 1380).
[0132] Number 303: The ten-digit number being called. If only seven digits were dialed, the system prefixes the number with the local area code.
[0133] Zone 304: The physical location of the telephone connected to the line.
[0134] Time 305: The elapsed time of the call.
[0135] Referring now to FIG. 3B, there is shown a Secondary Screen 311 for the system, as it would appear on display screen 113. The user can switch between the two screens at will. Secondary Screen 300 includes the following information about the telephone lines:
[0136] Ln 301: The line number.
[0137] Current state 306: Equivalent to status 302 shown in FIG. 3A.
[0138] Calls 307: The total number of calls attempted from the telephone.
[0139] Okay 308: The number of accepted calls made from the telephone.
[0140] Deny 309: The number of calls that were completed but denied by the called party.
[0141] Bad 310: The number of calls that were attempted but not completed for some reason. Includes busy signals, no answer, and the like.
[0142] System Parameter File 1109 The System Parameter File 1109 specifies configuration and operational parameters relevant to the operation of GWMAIN.EXE 1101. The system administrator uses support program SYSFILE.EXE 1102, also known as the System Parameter File Editor, to supply configurations and parameters to be stored in the System Parameter File 1109. Entry screens for the System Parameter File Editor are shown in FIGS. 4A and 4B. The following is a description of each of the items stored in the System Parameter File 1109:
[0143] System ID This parameter is used by the system in naming the Call Detail Record (CDR) files. A new CDR file is created using the Year, the Site ID, and the day of the year each 24 hours. (For example, a Site named TSTOA would have a CDR file named 92TSTOA. 180 for Jun. 29, 1992.)
[0144] Site Name This parameter contains the Site Name and is used to print the report headers on reports generated by the AWS-4000. It is also displayed on the secondary screen for GWMAIN.EXE.
[0145] System PW The System Password is used to protect sensitive portions of the system from unauthorized use.
[0146] Lines This parameter is used to tell the system how many active lines are to be installed. If a system is using nine lines of an available twelve lines, setting this parameter to ‘9’ will cause the system to display IDLE on lines 10, 11 and 12 rather than the usual ON-HOOK on the GWMAIN.EXE primary screen.
[0147] Callback # This number is used by the internal alarm system (if activated) as the number to call if an emergency call is placed. This would normally be the Administration Office where the AWS-4000 is located.
[0148] Debug Disp Setting this parameter to ‘Y’ will display various debug information on the screen while the system is running. You may be requested to turn on this feature by Gateway Support Personnel if you are having problems with your system. You may also activate the Debug Display by press F8 on the console or monitoring workstation keyboard.
[0149] Debug Write Setting this parameter to ‘Y’ will write various debug information to a file that can be processed by Gateway Technologies, Inc. to determine what is causing a problem with your system. You may be requested to turn this feature on by a Gateway Support technician. You may also activate this feature by pressing Alt-F8 on the console or monitoring workstation keyboard.
[0150] Time Slice Ticks This parameter determines the maximum amount of time the multi-tasking kernel will allow for a process before placing it on hold and letting other processes run. This value is in CPU clock ticks and should not be modified except under instruction from Gateway Technologies, Inc. The default value is 20.
[0151] DTMF Interdigit This parameter determines the amount of time between DTMF digits when the system is dialing out. The default value is 5 and it should not be changed without specific instructions from Gateway Technologies, Inc.
[0152] DTMF Duration This parameter defines the length of time, in 10 millisecond increments, that a DTMF tone sounds. This option is only active on out-bound dialing, it's default is 10 (100 ms) and it should not be changed without specific instructions.
[0153] Ring On Detect This parameter is the length of time, in 10 millisecond increments, that the system will use to determine that ring voltage is present on the telephone line. The default value is 3 (30 milliseconds) and should not be changed.
[0154] Ring Off Detect This parameter is the length of time, in 10 millisecond increments, that the system will use to determine that ring voltage has disappeared on the line. The default is 5 (50 ms) and should not be changed.
[0155] Off-hook Delay The off-hook delay is the amount of time between the time you request the Dialogic Card to take the phone off-hook and the time an off-hook event is generated by the system. This value allows the relays to debounce and prevents problems during call processing. The default value is 50 (500 ms) and should not be changed.
[0156] Silence Debounce This value, in 10 millisecond increments, is the amount of time at the end of a possible silence period that is ignored in determining whether a silence period has actually occurred. The default value is 4 (40 ms) and should not be changed.
[0157] LC Off Time This value, in 10 millisecond increments, is the length of time that Loop Current must be absent before the system returns a Loop Current Drop event. The default is −1, which sets the detection to the smallest possible value (This setting controls the maximum length of time a pulse dial pulse is allowing loop current to flow. It is not currently used in any CPS-4000 system. The default value is 50 (500 ms) and should not be changed.
[0158] PD Min Make This setting controls the minimum length of time a pulse dial digit will allow loop current to flow. It also is not currently used in any CPS-4000 system. The default value is 2 (20 ms) and should not be changed.
[0159] PD Interdigit This value controls the maximum interdigit timing on pulse dialing. It is not currently used on any CPS-4000 system. The default is 15 (150 ms) and should not be changed.
[0160] PD Min Break This value is the minimum interdigit timing on pulse dialing. It is not currently used on any CPS-4000 system. The default is 2 (20 ms) and should not be changed.
[0161] Ring Reset This value is the length of time between possible ring detection and a second ring detection where the first possible ring is dropped from consideration. The default value is 80 (800 ms) and should not be changed.
[0162] Local Area Code This is the local area code. It is appended internally by the system to all seven digit dialed numbers for lookup in the NUMBER File for verification, since all numbers are stored in the Number File as ten digit phone numbers.
[0163] Maximum Name Record This value is the length of time allowed for an inmate to record his name. The default value is 3 seconds and probably should not be changed. Do not set this value to less than 2 seconds since the timing is plus or minus 1 second.
[0164] Allow Phone Testing Setting this parameter to ‘Y’ will allow you to go to an inmate phone, dial 123456789 and have the system dial the local Central Office and record the outside line number. It will then play back the outside line number. The default value is ‘N’ and should only be changed during installation of the system. This feature is for diagnostic purposes only.
[0165] Beep on Drop This parameter will turn on a beeping tone if the phone is left off hook.
[0166] Beep Dialing Setting this field to ‘Y’ will turn off call progress monitoring and activate the call progress prompts, i.e. the line was busy, etc.
[0167] Outside Line Numbers These fields contains the outside line numbers of each inmate phone line. You must fill out all AVAILABLE lines or the GWMAIN.EXE program will not run. These numbers are used during the billing process so it is important that they be correct.
[0168] Local Dialing Prefix This field is used to store a dialing prefix that is necessary for all local calls (dialed seven digits and marked local in the NPANXX file, see below). This number is prepended to each local call. For example, if the phone lines are behind a PBX that requires that a ‘9’ be dialed before an outgoing number, you would put a ‘9’ in this field.
[0169] IntraLATA Dialing Prefix This field is used to store a dialing prefix for all IntraLATA calls (dialed seven digits but not marked local in the NPANXX file, see below). This number is prepended to each IntraLATAcall.
[0170] Long Distance Dialing Prefix This field is used to store a dialing prefix for all Long Distance calls (dialed ten digits). This number is prepended to all Long Distance calls. For example, if you want to route all calls through AT&T, you would place 102881 in this field. If you want to use the designated carrier, place a ‘1’ in this field.
[0171] System Start Time This field is the time the system will begin to allow phone calls. The System Start Time is stored in military format (00:00-23:59) and overrides any values in the Channel Parameter File (see below). The default start time is midnight (00:00).
[0172] System Stop Time This field is the time the system will stop allowing phone calls. It is stored in military time format and overrides any values in the Channel Parameter File (see below). The default stop time is midnight (24:00).
[0173] Recycle Time This field is the time, in military format, that the system will reboot each day. If you have an AWS-4000 system, you will want this value to remain at 00:00 (do not reboot), otherwise the standard value is 03:00 (3:00 A.M.).
[0174] Message # for 1st Branding Indicate which long distance or other telephone service is being used.
[0175] Message # for 2nd Branding Same.
[0176] Message # for Identification Identifies the name of the facility.
[0177] Message # for Location Indicates the location of the facility.
[0178] Language Support First-English, Second-Spanish, Third and Fourth-Optional other languages.
[0179] Maximum Attempts/Number/Day The maximum number of call attempts allowed in one day before the number is automatically blocked by the system. Default is 50.
[0180] Allow Person/Person Collect Setting this field to ‘Y’ turns on the Person-to-Person collect calling for the entire system.
[0181] Line Locations These fields are displayed on the GWMAIN.EXE primary screen as Zone and are only used for administration information.
[0182] Channel Parameter File 1110 The Channel Parameter File 1110 specifies operational parameters for each individual telephone line. The system administrator uses support program CHNFILE.EXE 1103, also known as the Channel Parameter File Editor, to supply parameters to be stored in the Channel Parameter File 1110. Entry screens for the Channel Parameter File Editor are shown in FIGS. 5A, 5B, 5C, and 5D. The following is a description of each of the items stored in the Channel Parameter File 1110:
[0183] Channel Number This parameter is the line number you are modifying. Value may range from ‘1’ to ‘24’.
[0184] Time Limit This is time, in seconds, that you are allowing a call to continue. The default value is 900 seconds (15 minutes). Other common values are 3600 seconds (1 hour) and 1800 seconds (½ hour).
[0185] ID System Setting this value to ‘Y’ turns on the base Gateway Restricted ID (GRID) system, requiring an inmate to enter an ID before making a call, but not requiring Administration Approved phone numbers.
[0186] Full Setting this value to ‘Y’ activates the full Gateway Restricted ID (GRID) system, requiring an inmate to enter an ID before making a call and requiring that Administration Approved phone numbers be available before allowing a call.
[0187] Pulse Detect Setting this value to ‘Y’ activates the pulse detection feature of the CPS-4000, allowing the called party to accept a collect call using a pulse dial phone. Setting this value to ‘N’ will only allow DTMF capable phones to accept CPS-4000 generated calls. The default is ‘Y’ and should not be changed.
[0188] Passive Accept Making this field a ‘Y’ allows all calls from the CPS-4000 to be accepted without active acceptance by the called party. The default value is ‘N’ and should not be changed.
[0189] Start This is the time that this channel will begin to allow phone calls. It is overridden by the value in the System Start Time in the System Parameter File (see above). It is in military time.
[0190] Stop This is the time that this channel will stop allowing phone calls. It is overridden by the value in the System Stop Time in the System Parameter File (see above). It is in military time format.
[0191] DTMF Detection Time This value is the length of time a DTMF tone must be present to be detected by the channel. The default value is 5 (50 ms) and should not be changed.
[0192] DTMF Edge Event This value can be either ‘1’ or ‘2’. A ‘1’ signifies that the DTMF tone is detected on the leading edge of the tone (which may cause large numbers of false detects) and a ‘2’ signifies that the DTMF tone is detected on the trailing edge (which may show up in recordings). The default for the CPS-4000 is ‘2’ and should not be changed.
[0193] DTMF Receive Guard Time This value is used to guard against false DTMF detection. The default value is ‘0’ and should not be changed.
[0194] Commissary Active This field is used to turn on/off commissary access for the specified line.
[0195] Silence Compression Delay This value is the length of time in milliseconds that a silent period must exist before it is compressed by the system. The default value is 200 and should not be changed.
[0196] Number of Rings before No Answer This field is the number of rings that the system will wait before returning a “No Answer” event. The default is ‘4’ but typical values range from ‘4’ to ‘6’.
[0197] Delay before Call Analysis Begins This is length of time, in 10 millisecond increments, that the system waits after completing dialing before beginning call analysis, which determines whether the phone was busy, rang with no answer, detected an intercept tone, etc. The default value is 25 (250 ms) and should not be changed.
[0198] Time out delay on no signal This is the number of milliseconds the system will wait during call analysis if there is no detectable signal before returning a No Ringback event. The default value is 4000 and should not be changed.
[0199] Delay before LC drop is a connect This value is the length of time after a Loop Current drop has been detected before the system will return an Answered event. The default value is −1 (disabled) and should not be changed.
[0200] Delay before returning a LC drop This is length of time after a loop current drop has been detected before the system returns a loop current drop event. The default is 10 (100 ms) and should not be changed.
[0201] Return Connect on leading edge This parameter determines whether the Loop Current drop is returned on the leading edge (1) or trailing edge (2) on a connect. Since the CPS-4000 does not use loop current drop to determine connect this value is not actually used. The default is 2 and should not be changed.
[0202] Time out for continuous signal This is the amount of time the call analysis will wait if a continuous signal is present (outside line is bad) before returning a No Ringback Event. The default is 650 ms and should not be changed.
[0203] Tolerance above 1st low This is the percentage amount of acceptable deviation allowed for the short low signal. The default is 13 and should not be changed.
[0204] Tolerance below 1st low This is the percentage amount of acceptable deviation allowed below for the short low signal. The default is 13 and should not be changed.
[0205] Tolerance above 2nd low This is the percentage amount of acceptable deviation allowed above for the long low signal. The default is 13 and should not be changed.
[0206] Tolerance below 2nd low This is the percentage amount of acceptable deviation allowed below for the long low signal. The default is 13 and should not be changed.
[0207] Tolerance above high This is the percentage amount of acceptable deviation allowed above for the high signal. The default is 13 and should not be changed.
[0208] Tolerance below high This is the percentage amount of acceptable deviation allowed below for the high signal. The default is 13 and should not be changed.
[0209] Max time for 1st low to detect busy This is the maximum time in 10 millisecond increments allowed for the short low on a busy signal. The default is 90 (900 ms) and should not be changed.
[0210] Max time for 2nd low to detect busy This is the maximum time in 10 millisecond increments allowed for the long low on a busy signal. The default is 90 (900 ms) and should not be changed.
[0211] Max time for high to detect busy This is the maximum time in 10 millisecond increments allowed for the high signal on a busy signal. The default is 90 (900 ms) and should not be changed.
[0212] Number of additional states before busy This is the number of additional cycles that the system must detect on a busy signal before returning a busy event. The default is 0 and should not be changed.
[0213] Smallest silence Interval This is the smallest interval of silence that the system will accept as a silent event. The default is 15 (150 ms) and should not be changed.
[0214] Smallest sound Interval This is the smallest interval of sound that the system will accept as a no-silence event. The default is 19 (190 ms) and should not be changed.
[0215] Max time for short low detected as double ring This is the maximum time for the short low period if this is to be detected as a double ring. The default is 90 (900 ms) and should not be changed.
[0216] Min time for long low detected as double ring This is the minimum time for the long low period if the signal is to be detected as a double ring. The default is 225 (2250 ms) and should not be changed.
[0217] Enable Operator Intercept Detection Placing a ‘Y’ in this field will enable Special Intercept Tone (SIT) detection. The default is ‘Y’ and should not be changed.
[0218] Min Intercept duration for detection This is the minimum length of time the SIT tone must be present before being detected as a SIT tone. The default is 10 (100 ms) and should not be changed.
[0219] Silence Trailing Edge Debounce The minimum amount of silence that will be recorded if silence compression recording is being used. The default is 0 and should not be changed.
[0220] High Size This value is checked against the length of the high period to determine which low maximum to use. The default is 90 (900 ms) and should not be changed.
[0221] Low Max A Maximum low period before connect if length of high period>high size. The default is 700 (7000 ms) and should not be changed.
[0222] Low Max B Maximum low period before connect if length of high period. The ring number you wish call analysis to begin. The default is 1 and should not be changed.
[0223] High ceiling Maximum length of high period if retraining is required. The default is 78 and should not be changed.
[0224] Low ceiling Maximum length of short low period if retraining is required. The default is 58 and should not be changed.
[0225] Low allowed frequency The lower boundary in hertz for frequency detection. The default is 900 and should not be changed.
[0226] High allowed frequency The upper boundary in hertz for frequency detection. The default is 1000 and should not be changed.
[0227] Min time within frequency for detect The minimum amount of time the signal must be within the specified frequencies before SIT detection event is generated. The default is 5 (50 ms) and should not be changed.
[0228] Bad signal reject percentage This is the percent of time the signal frequency can be outside of the boundaries and still be detected. The default is 20 and should not be changed.
[0229] Max answer duration The length of time before a connect is assumed if no other event is generated. The default is 1000 (10000 ms) and should not be changed.
[0230] Silence deglitching value The minimum amount of silence required before sound is considered an answer event. The default is 60 (600 ms) and should not be changed.
[0231] You will need to complete a Channel Parameter File record for each channel used in the CPS-4000.
[0232] Number Control File NUMBER.DTA 1127 The Number Control File stores information regarding every number that has been called. It is also used for blocking and unblocking particular numbers, allowing passive acceptance of specific numbers, or triggering alarms and/or recordings when particular numbers are called. The system administrator uses support program NUMBER.EXE 1128 to supply information regarding each number. An entry screen is shown in FIG. 6. The following is a description of each of the items in the Number Control File:
[0233] Number The ten digit telephone number.
[0234] Date Last Verified/Changed The date of the last time this record was modified.
[0235] Verified/Changed by The initials of the last person to modify this record.
[0236] Count Since Changed/Verified The number of call attempts to this number since the last manual change to this record.
[0237] Count Since Reset The number of call attempts to this number since the Maximum calls/Number/Day limit has been reached and reset.
[0238] Allow Passive Accept Whether this number is allowed to use passive accept.
[0239] Block Code This is block code used by the system. The usual block codes are either UOK if you want to allow calls to the number or HBL if you want to block calls to the number. You may also use FRE for free calls, or SPL to splash calls to the local operator.
[0240] Dialing Instructions This field is used if you want to have special dialing instructions for a specific number. This field is prepended to the number before dialing.
[0241] Local Call Normally, local calls are determined in the NPANXX file (see below). However, if a call is to be dialed 0+7, or if you have special dialing instructions, you will need to set this field to ‘Y’ if the number is a local call.
[0242] Record Calls to This Number Setting this field to ‘Y’ will record all calls made to this number.
[0243] Alarm Calls to This Number Setting this field to ‘Y’ will cause an alarm to sound at the CPS-4000 when a call is made to this number.
[0244] Attempt Counter This field is used by the CPS-4000 to track the number of call attempts made to this number. It should not be changed.
[0245] Accept Counter This field is used by the CPS-4000 to track the number of accepted calls made to this number. It should not be changed.
[0246] Time Counter This field is used by the CPS-4000 to track the number of seconds of talk time made to this number. It should also not be changed.
[0247] Attempt Date The date of the first attempt made to this number after the last rollover date. It is filled in by the CPS-4000 and should not be changed.
[0248] Accept Date This is the date of the first accept after the last rollover date. It is also filled in by the CPS-4000 and should not be changed.
[0249] Time Date This field is filled in by the CPS-4000 and should not be changed. It is the date of the first accept after the last rollover date.
[0250] Attempt Override Setting this flag to ‘Y’ will de-activate the attempt tracking feature of the CPS-4000. Normally, this is left as ‘N’.
[0251] Accept Override Setting this flag to ‘Y’ will de-activate the accept tracking feature of the CPS-4000. Normally, this is left as ‘N’.
[0252] Time Override Setting this flag to ‘Y’ will de-activate the time tracking feature of the CPS-4000. Normally, this is left as ‘N’.
[0253] No Record This flag is used to indicate that telephone calls to this phone number are not to be recorded, no matter what other record settings may be in effect.
[0254] NPANXX Control File NPANXX.DTA 1115 The NPANXX Control File NPANXX.DTA 1115 stores information regarding area codes and telephone exchanges. It permits blocking and unblocking exchanges, selection of particular exchanges where all calls are local calls, and the like. The system administrator uses support program NPANXX.EXE 1108 to supply information regarding each exchange. An entry screen is shown in FIG. 7. The following is a description of each of the items in the NPANXX Control File 1115:
[0255] NPANXX The six digit NPANXX (Area code+Exchange).
[0256] Date Last Verified/Changed The date of the last time this record was modified.
[0257] Verified/Changed by The initials of the last person to modify this record.
[0258] Passive Accept Setting this field to ‘Y’ allows all calls to this NPANXX to be accepted passively.
[0259] Block Code This is block code used by the system. The usual block codes are either UOK if you want to allow calls to this NPANXX or HBL if you want to block calls to this NPANXX. You may also use FRE for free calls, or SPL to splash calls to the local operator. Note that this applies to the WHOLE NPANXX.
[0260] Dialing Instructions This field is used if you want to have special dialing instructions for a specific NPANXX. This field is prepended to the number before dialing.
[0261] Local Call You will need to set this field to ‘Y’ if the NPANXX is a local call.
[0262] NPA Control File NPA.DTA 1112 The NPA Control File NPA.DTA 1112 stores information regarding telephone area codes. It permits blocking and unblocking area codes, allowing free calls in certain area codes, and the like. The system administrator uses a support program NPA.EXE 1105 to supply information regarding each exchange. An entry screen is shown in FIG. 8. The following is a description of each of the items in the NPA Control File 1112:
[0263] NPA The three digit NPA (Area code).
[0264] Date Last Verified/Changed The date of the last time this record was modified.
[0265] Verified/Changed by The initials of the last person to modify this record.
[0266] Passive Accept Setting this field to ‘Y’ allows all calls to this NPA to be accepted passively.
[0267] Block Code This is the block code used by the system. The usual block codes are either UOK if you want to allow calls to this NPA or HBL if you want to block calls to this NPA. You may also use FRE for free calls, or SPL to splash calls to the local operator. Note that this applies to the WHOLE NPA.
[0268] Dialing Instructions This field is used if you want to have special dialing instructions for a specific NPA. This field is prepended to the number before dialing.
[0269] NXX Control File NXX.DTA 1113 The NXX Control File NXX.DTA 1113 stores information regarding particular exchanges in all area codes. The system administrator uses support program NXX.EXE 1106 to supply information regarding the NXX to be blocked. An entry screen is shown in FIG. 9. The NXX control file contains three fields for each record: the NXX to be blocked, the date of last modification of the record, and the initials of the person who last modified the record.
[0270] Fraud Control Parameter File 1114 The Fraud Control Parameter File 1114 is used to set restrictions on inmate calling patterns to reduce fraudulent use of the telephone system. The system administrator uses support program CTLFILE.EXE 1107 to set parameters regarding calling patterns. An entry screen is shown in FIG. 10.
[0271] In the preferred embodiment, the Fraud Control Parameter File 1114 allows the system administrator to specify a number of local and/or long distance calling pattern parameters. Each such parameter specifies an amount field, a period field, and a roll-over field. The amount field specifies the maximum number of calls permitted (if set to zero, the parameter is disabled). The period field specifies the time period for measuring the maximum number of calls (i.e., daily, weekly, or monthly). The roll-over field specifies when successive time periods will begin (i.e., on a particular day of the week or a particular day of the month).
[0272] File 1114 stores the above information with respect to the following: the number of call attempts that will be allowed to a specific number; the number of accepted calls that will be allowed to a specific number; and the number of minutes of conversation that are allowed for a specific number. Once any of these parameters are exceeded for a specific number, the system can either block future calls or supply a trigger for recording future calls. The system administrator may specify which action is to be taken when a parameter is exceeded. This information is stored in Number Control File NUMBER.DTA 1127 and ID Files 1111. Recording may also be triggered if a 3-way call or call forwarding attempt is detected, as described above in connection with the discussion of GWMAIN.EXE.
[0273] Control files 1112-1115 specify parameters that may be applied to call blocking or call monitoring. Thus, for example, Fraud Control Parameter File 1114 may indicate that, after a certain number has been called a given number of times, the system will record all subsequent calls to that number. Alternatively, File 1114 may specify that all subsequent calls to that number may be blocked. Thus, the present invention provides improved flexibility for the system administrator to specify how certain types of calls should be handled.
Claims
I claim:
1. A computer implemented method of obtaining consent to the recording of telephone calls, comprising:
establishing a call record of a telephone call made by a calling party to a called party;
playing a first prompt requesting the calling party to consent to, or to refuse a recording of the telephone call;
receiving a first input signal from the calling party in response to the first prompt indicating either the calling party's consent or the refusal of consent to the recording of the telephone call;
storing an indication of the either the calling party's consent or refusal of consent to the recording of the telephone call in the call record; and
blocking the telephone call in response to the received first input signal when the received first input signal indicates the calling party's refusal of consent to the recording of the telephone call.
2. The method of claim 1, further comprising:
storing in the call record an indication of the language in which the first prompt was played.
3. The method of claim 1, further comprising:
playing a second prompt requesting a called party to consent to or refuse the recording of the telephone call;
receiving a second input signal from the called party indicating either the called party's consent or refusal; and
storing an indication of either the called party's consent or refusal in the call record.
4. The method of claim 3, further comprising:
storing in the call record an indication of the language in which the second prompt was played.
5. The method of claim 3, wherein playing a second prompt further comprises:
playing the second prompt in a plurality of languages.
6. The method of claim 3, wherein playing a second prompt further comprises:
playing the second prompt in a language selected by the calling party.
7. The method of claim 6, further comprising:
storing in the call record an indication of the language in which the second prompt was played.
8. The method of claim 3, wherein playing a second prompt further comprises:
playing the second prompt in a first default language, and in a second, different language selected by the calling party.
9. The method of claim 3, wherein playing a second prompt further comprises:
prompting the called party to select a language for the second prompt; and
playing the second prompt in the language selected by the called party.
10. The method of claim 9, further comprising:
storing in the call record an indication of the language in which the second prompt was played.
11. The method of claim 3, further comprising:
determining from a telephone number of the telephone call whether a language for the second prompt has been selected;
responsive to a language for the second prompt having been previously selected, playing the second prompt in the selected language;
responsive to a language for the second prompt having not been previously selected, prompting the called party to select a language for the second prompt, and storing an indication of the selected language in association with the telephone number.
12. The method of claim 11, further comprising:
storing in the call record an indication of the language in which the second prompt was played.
13. The method of claim 3, wherein playing a second prompt further comprises:
determining from a telephone number of the telephone call whether a language for the second prompt has been selected;
responsive to a language for the second prompt having been previously selected, playing the second prompt in the selected language;
responsive to a language for the second prompt having not been previously selected, prompting the calling party to select a language for the second prompt, and storing an indication of the selected language in association with the telephone number.
14. The method of claim 13, further comprising:
storing in the call record an indication of the language in which the second prompt was played.
15. The method of claim 1, further comprising:
playing a second prompt informing a called party that the telephone call may be recorded;
receiving a second input signal from the called party indicating either the called party's acceptance or refusal of the telephone call; and
storing an indication of either the called party's acceptance or refusal in the call record.
16. The method of claim 1, further comprising:
storing an indication of whether or not the telephone call was recorded in the call record.
17. The method of claim 1, further comprising:
maintaining synchronized clocks in a call processing system from which the telephone call is made and in a call recording system in which the telephone call is recorded;
storing in the call record a time at which the telephone call is recorded; and
storing in a call recording log in the call recording system the time at which the call is recorded, such that the times in the call record and the call recording log are the same.
18. The method of claim 1, further comprising:
determining from a telephone number of the telephone call whether the telephone call may be recorded;
responsive to determining that the telephone call may be recorded:
playing the first prompt; and
storing an indication in the call record that the first prompt was played; and
responsive to determining that the telephone call may not be recorded:
playing a second prompt indicating that the telephone call will not be recorded.
19. The method of claim 18, further comprising:
storing an indication in the call record that the second prompt was played; and
storing an indication in the call record that the telephone call was not recorded.
20. The method of claim 1, further comprising:
determining from a telephone number of the telephone call whether the telephone call may be recorded;
responsive to determining that the telephone call may be recorded:
playing the first prompt; and
storing an indication in the call record that the first prompt was played; and
responsive to the first input signal indicating that the calling party refuses the recording of the telephone call, terminating the telephone call; and
responsive to the first input signal indicating that the calling party consents to the recording of the telephone call, completing the telephone call.
21. A computer readable medium for use in a telephone call recording system, comprising:
a call record stored in the computer readable medium and including:
a telephone number of a called party associated with a telephone call;
an indication of at least one of:
a prompt that was played informing the calling party that the telephone call may be recorded;
a prompt that was played informing the calling party that the telephone call would not be recorded;
an indication of the calling party's consent or refusal of consent to recording of the telephone call in response to the prompt informing the calling party that the telephone call may be recorded; and
an indication that the call was blocked in response to the indication of the calling party's refusal of consent to the recording of the call.
22. The computer readable medium of claim 21, wherein the call record further comprises:
an indication of a language of the prompt that was played.
23. The computer readable medium of claim 21, wherein the call record further comprises:
an indication of whether the telephone call was recorded or not.
24. The computer readable medium of claim 21, wherein the call record further comprises:
an indication of at least one of:
a prompt that was played informing the called party that the telephone call may be recorded;
a prompt that was played informing the called party that the telephone call would not be recorded; and
an indication of the called party's consent to the recording of the telephone call.
25. The computer readable medium of claim 24, wherein the call record further comprises:
an indication of a language of the prompt played to the called party.
26. A computer program product for obtaining consent to the recording of telephone calls, comprising:
a computer readable medium;
an executable computer program stored on the computer readable medium, for controlling a computer system to perform the operations of:
receiving from a calling party a telephone number of a called party to completing a telephone call;
playing a first prompt requesting the calling party to consent to the recording of the telephone call;
receiving a first input signal from the calling party in response to the first prompt indicating either the calling party's consent or the refusal;
storing an indication of either the calling party's consent or refusal to consent to the recording of the telephone call received from the first input signal; and
blocking the telephone call in response to the indication of the calling party's refusal to consent to the recording of the telephone call from the received first input signal.
27. A computer program product for obtaining consent to the recording of telephone calls, comprising:
a computer readable medium;
a plurality of recorded prompts in at least two different languages, and including:
at least one prompt indicating that a telephone call will not be recorded;
at least one prompt indicating that a telephone call may be recorded;
a computer executable program stored on the computer readable medium for controlling a computer system to perform the operations of:
establishing a telephone call to an input telephone number from a calling party to a called party;
selecting a language for, and at least one of, the prompts for playing to the calling party as to whether the telephone call to the input telephone number is to be recorded;
playing the selected prompt in the selected language to the calling party;
recording an input from the calling party in response to the selected prompt as to whether the calling party consents or refuses to consent to recording of the telephone call; and
blocking the telephone call in response to the recorded input when the recorded input indicates that the calling party refuses to consent to the recording of the telephone call.
28. The computer program product of claim 27, wherein the executable computer program on the computer readable medium further control the computer system to perform the operations of:
selecting a language for, and at least one of, the prompts for playing to the called party as to whether the telephone call to the input telephone number is to be recorded;
playing the selected prompt in the selected language to the called party; and
recording an input from the called party as to whether the called party consents to recording of the telephone call.
29. A computer system for obtaining consent to the recording of telephone calls, comprising:
a storage device for storing a plurality of recorded prompts in at least two different languages, including:
at least one prompt indicating that a telephone call will not be recorded;
at least one prompt indicating that a telephone call may be recorded;
a memory;
a telephone interface for coupling the computer system to a telephone network;
a processor coupled to the memory for executing a computer program stored in the memory; and
a computer program stored in the memory for controlling the computer system to perform the operations of:
establishing a telephone call to an input telephone number from a calling party to a called party;
selecting a language for, and at least one of, the prompts for playing to the calling party as to whether the telephone call to the input telephone number is to be recorded;
playing the selected prompt in the selected language to the calling party;
recording an input from the calling party in response to the selected prompt as to whether the calling party consents or refuses to consent to recording of the telephone call; and
blocking the telephone call when the input from the calling party indicates refusal to consent to the recording of the telephone call.
30. A computer implemented method of obtaining consent to the recording of telephone calls, comprising:
establishing a call record of a telephone call made by a calling party to a called party;
playing a first prompt requesting the calling party to consent to, or to refuse a recording of the telephone call;
receiving a first input signal from the calling party in response to the first prompt that indicates either the calling party's consent or the refusal of consent to the recording of the telephone call;
storing an indication of either the calling party's consent or refusal of consent to the recording of the telephone call in the call record as indicated by the first input signal; and
overriding an indication of a refusal in the received first input signal if recording of the call is necessary.
Patent Citations (88)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3851121(A) | 1974-11-01 | Marvin | Applicant |
| US4001513(A) | 1977-01-01 | Naylor | Applicant |
| US4002848(A) | 1977-01-01 | Stein | Applicant |
| US4188508(A) | 1980-02-01 | Rogers et al. | Applicant |
| US4310726(A) | 1982-01-01 | Asmuth | Applicant |
| US4518825(A) | 1985-05-01 | Brinkerhoff et al. | Applicant |
| US4559416(A) | 1985-12-01 | Theis et al. | Applicant |
| US4602129(A) | 1986-07-01 | Matthews et al. | Applicant |
| US4696031(A) | 1987-09-01 | Freudberg et al. | Applicant |
| US4726057(A) | 1988-02-01 | Doerry et al. | Applicant |
| US4799255(A) | 1989-01-01 | Billinger et al. | Applicant |
| US4815120(A) | 1989-03-01 | Kosich | Applicant |
| US4885765(A) | 1989-12-01 | Shirakawa | Applicant |
| US4896348(A) | 1990-01-01 | Grantland et al. | Applicant |
| US4899375(A) | 1990-02-01 | Bauer et al. | Applicant |
| US4901341(A) | 1990-02-01 | Carter et al. | Applicant |
| US4922519(A) | 1990-05-01 | Daudelin | Applicant |
| US4922520(A) | 1990-05-01 | Bernard et al. | Applicant |
| US4924488(A) | 1990-05-01 | Kosich | Applicant |
| US4933966(A) | 1990-06-01 | Hird et al. | Applicant |
| US4933967(A) | 1990-06-01 | Lo et al. | Applicant |
| US4935956(A) | 1990-06-01 | Hellwarth et al. | Examiner |
| US4937862(A) | 1990-06-01 | Kosich | Applicant |
| US4993068(A) | 1991-02-01 | Piosenka et al. | Applicant |
| US5020095(A) | 1991-05-01 | Morganstein et al. | Examiner |
| US5023869(A) | 1991-06-01 | Grover et al. | Applicant |
| US5023906(A) | 1991-06-01 | Novas | Applicant |
| US5033088(A) | 1991-07-01 | Shipman | Applicant |
| US5054059(A) | 1991-10-01 | Stern et al. | Applicant |
| US5063593(A) | 1991-11-01 | Kwon | Applicant |
| US5109405(A) | 1992-04-01 | Morganstein | Applicant |
| US5131024(A) | 1992-07-01 | Pugh et al. | Applicant |
| US5150357(A) | 1992-09-01 | Hopner et al. | Applicant |
| US5163083(A) | 1992-11-01 | Dowden et al. | Applicant |
| US5187740(A) | 1993-02-01 | Swaim et al. | Applicant |
| US5200995(A) | 1993-04-01 | Gaukel et al. | Applicant |
| US5210789(A) | 1993-05-01 | Jeffus et al. | Examiner |
| US5222120(A) | 1993-06-01 | McLeod et al. | Applicant |
| US5229764(A) | 1993-07-01 | Matchett et al. | Applicant |
| US5276731(A) | 1994-01-01 | Arbel et al. | Applicant |
| US5305312(A) | 1994-04-01 | Fornek et al. | Applicant |
| US5309505(A) | 1994-05-01 | Szlam et al. | Applicant |
| US5311589(A) | 1994-05-01 | Bennett et al. | Applicant |
| US5319702(A) | 1994-06-01 | Kitchin et al. | Applicant |
| US5325427(A) | 1994-06-01 | Dighe | Applicant |
| US5327489(A) | 1994-07-01 | Anderson et al. | Applicant |
| US5329578(A) | 1994-07-01 | Brennan et al. | Applicant |
| US5335266(A) | 1994-08-01 | Richardson, Jr. et al. | Applicant |
| US5345595(A) | 1994-09-01 | Johnson et al. | Applicant |
| US5351287(A) | 1994-09-01 | Bhattacharyya et al. | Applicant |
| US5355403(A) | 1994-10-01 | Richardson, Jr. et al. | Applicant |
| US5369699(A) | 1994-11-01 | Page et al. | Examiner |
| US5375161(A) | 1994-12-01 | Fuller et al. | Applicant |
| US5442696(A) | 1995-08-01 | Lindberg et al. | Applicant |
| US5452347(A) | 1995-09-01 | Iglehart et al. | Applicant |
| US5465293(A) | 1995-11-01 | Chiller et al. | Applicant |
| US5471519(A) | 1995-11-01 | Howe et al. | Applicant |
| US5483582(A) | 1996-01-01 | Pugh et al. | Applicant |
| US5483593(A) | 1996-01-01 | Gupta et al. | Applicant |
| US5485507(A) | 1996-01-01 | Brown et al. | Examiner |
| US5535261(A) | 1996-07-01 | Brown et al. | Examiner |
| US5539812(A) | 1996-07-01 | Kitchin et al. | Applicant |
| US5544231(A) | 1996-08-01 | Cho | Examiner |
| US5606604(A) | 1997-02-01 | Rosenblatt et al. | Applicant |
| US5617471(A) | 1997-04-01 | Rogers et al. | Applicant |
| US5627887(A) | 1997-05-01 | Freedman | Applicant |
| US5651056(A) | 1997-07-01 | Eting et al. | Applicant |
| US5655013(A) | 1997-08-01 | Gainsboro | Applicant |
| US5722418(A) | 1998-03-01 | Bro | Applicant |
| US5724404(A) | 1998-03-01 | Garcia et al. | Applicant |
| US5745553(A) | 1998-04-01 | Mirville et al. | Applicant |
| US5796811(A) | 1998-08-01 | McFarlen | Applicant |
| US5799068(A) | 1998-08-01 | Kikinis et al. | Applicant |
| US5805685(A) | 1998-09-01 | McFarlen | Applicant |
| US5809125(A) | 1998-09-01 | Gammino | Applicant |
| US5883945(A) | 1999-03-01 | Richardson et al. | Applicant |
| US5960064(A) | 1999-09-01 | Foladare et al. | Applicant |
| US6064963(A) | 2000-05-01 | Gainsboro | Examiner |
| US6072860(A) | 2000-06-01 | Kek et al. | Examiner |
| US6134320(A) | 2000-10-01 | Swan et al. | Examiner |
| US6141406(A) | 2000-10-01 | Johnson | Applicant |
| US6169789(B1) | 2001-01-01 | Rao et al. | Examiner |
| US6188751(B1) | 2001-02-01 | Scherer | Applicant |
| US6249570(B1) | 2001-06-01 | Glowny et al. | Examiner |
| US6366653(B1) | 2002-04-01 | Yeh et al. | Examiner |
| US6529602(B1) | 2003-03-01 | Walker et al. | Examiner |
| US2001/0041590(A1) | 2001-11-01 | Silberfenig et al. | Examiner |
| JP5-30193 | 1993-05-01 | Applicant |
Non-Patent Literature (21)
- HR solutions, http://ww.solutionshrd.com/methods_of_electronic_monitoring.htm, p. 4 of 5, Telephone Surveillance.Applicant
- Jones International, http://www.jonesencyclo.com/encyclo/update/ecpa.html, 1-7, Electronic Communications Privacy Act.Applicant
- Bahl, L. “A Maximum Likelihood Approach to Continuous Speech Recovery,” Readings in Speech Recognition Ed. A. Waibel and K. Lee, Morgan Kaufmann Publishers, pp 308-319, IEEE 1983.Applicant
- Batten, A. “Personal Communications Service and the Intelligent Network,” British Telecommunications Engineering, vol 9, pp 88-91 Aug. 1990.Applicant
- Lee, K. “Large-Vocabulary Speaker-Independent Continuous Speech Recognition Using HMM,” Carnegie Mellon University Department of Electrical and Computer Engineering, CMU-CS-88-148 Apr. 1988.Applicant
- System 20, Nov. 1992, Specially designed for correctional facilities, from County Jails to State and Federal Prisons. VAC.Applicant
- Telematic “ConQuest III Intimate Telephone System” Nov. 1992.Applicant
- “LazerPhone User Reference Manual,” 150 pages, edition and publisher unknown.Applicant
- “LazerPhone Inmate Telephone System, Users Manual Version 1.0,” pp 1-29, published Oct. 1998 by Schlumberger Technologies, Inc./Global Tel*Link of Mobile, Alabama.Applicant
- “LazerPhone Inmate Telephone System, Users Manual Version 1.0,” pp 1-29, published Mar. 1999 by Schlumberger Technologies, Inc./Global Tel*Link of Mobile, Alabama.Applicant
- “LazerVoice Digital Recording System Inmates Services, Users Manual Version 2.22,” pp 1-41, published Apr. 28, 1998 by Schlumberger Technologies, Inc./LazerVoice of Mobile, Alabama.Applicant
- Brochures entitled “LazerPhone—Powerful Performance Uncompromising Standards,” 4 pages, published 1998 Schlumberger Technologies, Inc. of Mobile, Alabama.Applicant
- Brochure entitled “LazerVoice—Simply Perfect,” 5 pages, published 1998 Schlumberger Technologies, Inc. of Mobile, Alabama.Applicant
- “Chapter I. System Overview” from LazerPhone Technical Manual, pp. 1.1-1.6, published by Schlumberger Technologies, Inc. of Mobile, Alabama.Applicant
- “Chapter VI. Facility Install & Network” from LazerPhone Technical Manual, 24 pages, published by Schlumberger Technologies, Inc. of Mobile, Alabama.Applicant
- Patent Abstracts of Japan; Publication No. 05-030193 dated May 2, 1993; Application No. 03-178582; Inventor Nakano Masakazu; Applicant NEC Corp.Applicant
- Readings in Speech Recognition, Edited by Alex Waibel and Kai-Fu Lee; A Maximum Likelihood Approach to Continuous Speech Recognition.Applicant
- British Telecommunications Engineering dated Aug. 1990 (Aug. 27-Sep. 1, 1990); Personal Communications Services and the Intelligent Network.Applicant
- S3.7 Large-Vocabulary Speaker-Independent Continuous Speech Recognition Using HMM; Kai-Fu Lee and Hsiao-Wuen Hon.Applicant
- System 20; Specially designed for correctional facilities from County Jails to State and Federal Prisons; VAC.Applicant
- Tele-Matic Corporation; Conquest III Inmate Telephone System.Applicant