Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS5325422 A
Publication typeGrant
Application numberUS 08/150,591
Publication dateJun 28, 1994
Filing dateNov 10, 1993
Priority dateSep 28, 1982
Fee statusPaid
Also published asUS4783796
Publication number08150591, 150591, US 5325422 A, US 5325422A, US-A-5325422, US5325422 A, US5325422A
InventorsDavid J. Ladd
Original AssigneeVmx, Inc.
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
PBX telephone call control system
US 5325422 A
Abstract
A PBX telephone call control system is disclosed. The system provides a line interface unit connection between a plurality of subscriber line extensions and a private branch exchange (PBX) switching equipment. The call control system appears to the PBX like any other telephone extension within the office environment and provides the user with more features in conjunction with the pre-existing PBX equipment, providing expanded capabilities at a reasonable expense.
Images(2)
Previous page
Next page
Claims(1)
What is claimed is:
1. A method of completing plural incoming telephone calls concurrently to corresponding plural facilities of a telephone switching system using a corresponding plurality of station lines of the switching system, comprising the steps of:
receiving a plurality of requests for service arising respectively from the incoming telephone calls directed toward the telephone switching system;
transmitting an instructional message to the sources of the requests for service to transmit communication facilities identifying information;
receiving and temporarily storing communication facilities identifying information transmitted from said sources of requests in response to said instructional message;
requesting service of said telephone switching system using said station lines;
receiving dial tone on the station lines from the telephone switching system and preventing the dial tone from reaching each said source of request for service;
transmitting communication facilities identifying information resulting from said stored communication facilities identifying information on the station lines to the telephone switching system so that the telephone switching system can effect plural communication paths between respective communication facilities and the respective sources of the requests for service; and
causing the respective sources of requests for service to be connected to respective communication paths to provide for communication to the selected communication facilities.
Description

This is a continuation of application Ser. No. 07/200,705, filed May 31, 1988, abandoned which is a continuation of application Ser. No. 803,126, filed Nov. 29, 1985, Pat. No. 4,783,796.

BACKGROUND OF THE INVENTION

The present invention relates to PBX (private branch exchange) interface equipment.

A PBX can be defined as a telephone exchange serving a single organization, having a switchboard and associated equipment, usually located on the customer's premises. The PBX equipment provides for switching calls between any two extensions served by the exchange or between any extension and the national telephone system via a trunk or trunks to a central office. PBX equipment is, of course, well known in the prior art, as numerous manufacturers are providing many types of PBX equipment for virtually every type of business environment.

Typically, the PBX equipment provides connections between a plurality of telephone subscriber lines (extensions) such as those located in a typical office environment and a plurality of trunk lines, typically smaller in number than the subscriber lines. The PBX equipment provides switching functions which permit subscribers, under certain limitations, in an office environment to gain access as required to trunk lines, including WATS (wide area telephone service), DDD (direct distance dialing) and the like, for enabling connections of telephone calls.

As a user's business expands, it frequently becomes desirable to add more features to pre-existing PBX equipment, and to provide expanded capabilities at a reasonable expense. However, a problem in the prior art is that, in order for an installation to provide additional features for the installed PBX equipment, it has been difficult to upgrade the existing PBX equipment because of limitations of space, memory storage, power limitations and the like.

In addition, the general approach with upgrading existing PBX equipment is by connecting additional switching equipment between the existing PBX and the trunks themselves. A further problem with such an approach is excessive costs which necessarily are involved with installations of more expensive switching equipment to the trunk lines.

It would therefore be desirable to provide a system for providing additional capabilities to existing PBX equipment in an office environment while not excessively increasing the cost of such upgrading of the existing equipment.

In view of the above background, it is an objective of the present invention to provide an improved interface equipment for connection to existing PBX equipment.

SUMMARY OF THE INVENTION

The present invention relates to a PBX telephone call control system for use with PBX type switching equipment.

In one embodiment, the call control system includes a plurality of trunk lines, a plurality of telephone subscriber lines or extensions (such as would be in a typical office environment) and PBX (private branch exchange) switching apparatus connected between the subscriber lines and the trunk lines.

The call control system also includes line interface equipment connected to the subscriber lines and consequently to the PBX equipment. The line interface unit simulates another extension within the system to the PBX equipment.

Hence, in a typical operation, the call control system appears to the PBX just like any other telephone extension within the system. In one mode of operation, the system is "called" by a user wishing to use its services, and when the system (and more particularly the line interface unit) detects a ring voltage, it in turn gives an off-hook tone to "answer" the call and returns a dial tone.

The user hears the dial tone and dials the number he wishes. The call control system analyzes the number, requests an authorization code if necessary, selects the most economical route, and "flashes" the PBX to indicate that a desired call is in process, dials (using a dual tone multifrequency signaling circuit) the trunk access code and the called number, and finally hangs up to complete the transfer of the user to the appropriate trunk.

Among the features provided by the present invention to the user in a PBX environment are:

route optimization, which provides automatic selection of the least cost route for outgoing calls,

call queuing, which provides that, when a least cost route is not available, automatic callback to a user when the route does in fact become available,

toll restriction, which prevents unauthorized calls by requiring the user to enter an authorization code before a call will be placed, and

station message detail recording, which provides information on what number were called.

Another feature of the present invention is a "talker" circuit, which provides pre-stored voice messages to automatically indicate to a user whether the most economical route is available or, if not, what other routes are available thereby providing the user with the capability of either completing his call or waiting until a more economical trunk is available.

In accordance with the foregoing summary, the present invention achieves the objective of providing an improved PBX telephone call control system for use in a PBX environment.

Other objects and features of the present invention will become apparent from the following detailed description when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of a PBX telephone call control system according to the present invention.

FIG. 2 depicts a diagram of a line interface unit, which forms a portion of FIG. 1.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram illustrating the PBX telephone call control system as connected to the PBX (private branch exchange) interface. Before going into more detail concerning the drawings, a general system specification of one embodiment of the present invention will be described in some detail.

In operation, a user dials an access code for the system. Usually the access code will be the pilot number of a "hunt" group (an extension which, when dialed, will in turn cause to ring the first non-busy extension in a group of extensions). The user may hear a brief period of ringback tone before the system answers. When the system answers, the user will be given system dial tone.

The user then "dials" the feature desired. DIALTONE is removed after the first digit.

By looking at the digits dialed and its data bases, the system will then collect the necessary number of digits to complete the feature. In some special cases, such as international dialing, the system does not know how many digits to collect, and will wait until the user does not enter any more digits for an "interdigit timeout" (usually configured to be five seconds).

If the user dialed an illegal sequence of digits, the system will respond with the message "INVALID NUMBER, DIAL NUMBER" and the user will be given initial system DIALTONE.

If the user dialed any digit 0-9, the system enters the destination or external call function. If the system times out while waiting for the first destination digit, the system will respond with the message "ENTER NUMBER". If the user still does not respond before another timeout, the system will respond with the message "DIALED TOO SLOW" and then disconnect from the user. If the user starts entering his destination number and times out between digits, the system (with the following exception) will respond with the message "DIALED TOO SLOW" and then disconnect from the user. The exception is when the user has dialed an international number (starting with 01), a timeout will signal the system that all necessary digits have been entered. This is required because there is not a fixed length numbering plan for international dialing.

The digits *NNN (N is a digit 0-9) is the system speednumber feature. The number of N's is configurable from 1 to 3 depending on the number of speednumbers configured for the system.

Toll restriction is used to prevent certain people from dialing expensive calls. It is also used to allow people to dial certain numbers without identifying themselves.

If certain numbers are desired to be dialed by anyone and no identification of the caller is desired, these numbers should be listed in the "Exempt" table. These calls will be exempt from having the user be asked for his account code. The system default Class of Service (COS) will be used for these calls. Exempt numbers may be three or six digits long. They are area codes, area code + office codes, or office codes. If complete seven or ten digit numbers are to be exempt, the speednumber feature should be used for these numbers. If a specific office code for any area code, such as 555, is to be exempt, a special flag may be used preceding the 555 to flag a match on any area code.

If certain numbers are to be blocked from being dialed by everyone, these numbers should be listed in the "Blocked" table. Typical numbers may include, for example, Time. Blocked numbers can be up to ten digits long. If the number dialed is "blocked" the system responds with the message "RESTRICTED NUMBER DIALED" and then disconnects from the user.

If the number dialed was not Exempt or Blocked or a speed-number from which a COS could be found, the user will be asked to enter an Account code.

Account codes are used to determine the COS and extension number of the user. If the number dialed requires an account code to be entered, the system will respond with the message "ENTER ACCOUNT CODE". The user then enters the account code. If it is invalid, the system will respond with the message "INVALID ACCOUNT CODE, ENTER ACCOUNT CODE". The user is allowed three tries, after which the system will respond with the message "INVALID ACCOUNT CODE" and then disconnect from the user.

Route Optimization is used for both selecting the best route to use to place the call, and to provide toll restriction based on the COS of the user. Time of day or day of week changes are applied to the user's COS prior to continuing with route optimization.

If the call is a 0 or 0+digits call, the system parameter table is checked to see if the user has the minimum COS necessary to place this type of call. If so, the call is routed over the system default route, which is DDD. If the user does not have a high enough COS, the system will respond with the message "RESTRICTED NUMBER DIALED" and then disconnect from the user.

The system then searches the routing tables for the number dialed. When it finds a match, it then has a list of choices for route to use for that specific call. If no match is found, the system default list (which is DDD only) is used. A route describes a specific trunk group and information about the digits (strip Area Code. . . ) to be outpulsed.

If the first choice route cannot be used due to COS restrictions, the system will "Route and Advance" to the next choice route. If the COS of the user does not allow access to any route on the list, the system will respond with the message "RESTRICTED NUMBER DIALED" and then disconnect from the user. This is the usual method of toll restriction.

The system starts with the first choice route. If the user COS allows him access, and the route is known to be idle, the system flashes, dials the trunk access code, waits for external dial tone, outpulses the destination digits, and completes the transfer by hanging up.

If the first choice route cannot be used because it is busy, the system checks COS information to see if the user is required to queue on this route before advancing to the next route. If not, the next route is tried as described above. This continues all the way down the list of routes until an idle trunk is found.

Whenever the system is about to try the DDD route and there were cheaper but busy routes which the user could queue for but his high COS caused him not to be asked to wait, the system will respond with the message "CALL IS BEING PLACED ON AN EXPENSIVE ROUTE, PRESS STAR TO PROCEED, ENTER EXTENSION NUMBER TO CALLBACK QUEUE". There is a flag by COS telling if this question should be asked. If the user keys a #, the call is cancelled and the user is dropped to system dialtone.

If the user because of COS can use a route, his COS also allows him to callback queue for the route. A different flag by COS tells if the user can offhook queue for the route. If the user is required to queue for the first choice route, his COS is also checked to see if he can offhook queue for this route. If he can offhook queue, the system responds with the message "ALL ROUTES BUSY, XX CURRENTLY WAITING, PRESS STAR FOR OFFHOOK QUEUE, ENTER EXTENSION NUMBER FOR CALLBACK QUEUE". If he is not allowed to offhook queue, the system responds with the message, "ALL ROUTES BUSY, XX CURRENTLY WAITING, ENTER EXTENSION NUMBER FOR CALLBACK QUEUE". XX is the smallest number of people waiting for any of the routes he could queue on.

After the user enters his extension number, the system gives no confirmation, but just disconnects from the user. If the user enters a star, he goes into an offhook queue state, but also gets no confirmation. While a user is offhook queued, he will normally hear silence, and sometime "clicks" when he is put on hold to try for the trunk. If the user does nothing for a "first digit timeout" period (usually ten seconds), the system will assume he is not interested in queuing and will give the timeout message "PLEASE DIAL" with another three seconds, and if no response, disconnects from the user. Entering a "#" prior to system disconnect will cause the system to drop the user back to system DIALTONE. While waiting offhook, if the call is placed on a cheap route, no message is given to the user.

There is also a configurable limit to the number of ports to be used for offhook trunk queuing. If this limit is reached, the user will be asked if he wishes to callback (onhook) queue only.

Whenever the system is about to try the DDD route and there were cheaper but busy routes which the user could queue for but his high COS caused him not to be asked to wait, the system will respond with the message "CALL IS BEING PLACED ON AN EXPENSIVE ROUTE. PRESS STAR TO PROCEED, ENTER EXTENSION NUMBER TO CALLBACK QUEUE". There is a flag by COS telling if this question should be asked. Asking this question to an offhook queued person will force him to go to onhook queue if he wants to continue to wait. If he chooses to wait onhook for the cheap route, he will wait there with no timeout until one of the cheaper routes becomes available.

When a trunk becomes available for a queued call, or the user is route advanced to a route which has an available trunk, the system will call back the user at the extension number he has entered.

If the user does not answer, after ten minutes the system will try to call the user again when the trunk queued for is free. This retry is done only once, after which the queue is cancelled.

If the user presses *, the call is placed. If the user presses #, he requeues and will not be called back for ten minutes. This is used if he is occupied. If the user does nothing, or hangs up, the queue is cancelled and the system disconnects from the user.

If the call is going out over DDD, the system responds with the message "CALL TO XXX XXX XXXX IS BEING PLACED ON AN EXPENSIVE ROUTE, PRESS STAR TO PROCEED, PRESS POUND TO WAIT FOR A LOW COST ROUTE".

If the user presses in a *, the call is made. If the user presses in a #, the call is requeued on the more expensive routes with no timeout. Thus the system will wait forever, or until a cheap route becomes available.

Illustrative examples of the types of talker messages which can be generated are set forth below:

1. DIAL NUMBER

2. INVALID NUMBER, DIAL NUMBER

3. INVALID FUNCTION

4. INVALID SPEEDNUMBER, DIAL SPEEDNUMBER

5. ENTER ACCOUNT CODE

6. INVALID ACCOUNT CODE, ENTER ACCOUNT CODE

7. INVALID ACCOUNT CODE

8. RESTRICTED NUMBER DIALED

9. ALL ROUTES BUSY

10. ALL ROUTES BUSY, XX CURRENTLY WAITING, PRESS STAR FOR OFFHOOK QUEUE, ENTER EXTENSION NUMBER FOR CALLBACK QUEUE

11. ALL ROUTES BUSY, XX CURRENTLY WAITING, ENTER EXTENSION NUMBER FOR CALLBACK QUEUE

12. CALL IS BEING PLACED ON AN EXPENSIVE ROUTE, PRESS STAR TO PROCEED, ENTER EXTENSION NUMBER FOR CALLBACK QUEUE

13. CALL IS BEING PLACED ON MCI, PRESS POUND TO BYPASS

14. CALL IS BEING PLACED ON SPRINT, PRESS POUND TO BYPASS

15. CALL TO XXX XXX XXXX CAN BE PLACED, PRESS STAR TO PROCEED, PRESS POUND TO REQUEUE

16. CALL TO XXX XXX XXXX IS BEING PLACED ON MCI, PRESS STAR TO PROCEED, PRESS POUND TO BYPASS

17. CALL TO XXX XXX XXXX IS BEING PLACED ON SPRINT, PRESS STAR TO PROCEED, PRESS POUND TO BYPASS

18. CALL TO XXX XXX XXXX IS BEING PLACED ON AN EXPENSIVE ROUTE, PRESS STAR TO PROCEED, PRESS POUND TO WAIT FOR A LOW COST ROUTE

19. DIALED TOO SLOW

20. ALL ROUTES BUSY, XX CURRENTLY WAITING, PRESS STAR FOR OFFHOOK QUEUE

21. CALL IS BEING PLACED ON AN EXPENSIVE ROUTE, PRESS STAR TO PROCEED

Now that a general overview has been described, a specified example of the system's operation will be given in conjunction with a typical telephone call placed by a user. The specific example will be described with reference to FIGS. 1 and 2.

Referring now to FIG. 1, PBX 14 is connected to a plurality of trunk lines 16 and, in addition, to a plurality of conventional subscriber lines (or extensions) 12.

As previously described, PBS 14 provides for switching calls between any two extensions served by the exchange or between any extensions in the national telephone system via a trunk or trunks 16 to a central office (not shown). PBX 14 could be of any type well known in the art.

Subscriber lines 12 are connected to PBX 14 in the normal fashion. In addition, the system depicted in FIG. 1 shows a line interface unit 20 connected to subscriber lines 12 via bus 18. In a preferred embodiment, six lines are connected from line interface unit 20 to subscriber lines 12 via bus 18.

Line interface unit 20 is depicted in more detail in FIG. 2 and will be described in some detail below.

Referring again to FIG. 1, line interface unit 20 is connected to a talker circuit 22 via bus 24. Talker circuit 22 includes a Z80A microprocessor and includes up to 256K bytes of random access memory (RAM), with parity, and in addition a delta-mod codec. Talker circuit 22, as has been described above, provides a user with verbal instructions regarding whether a particular desired trunk or extension is available, and, in the alternative, if cheaper and/or more expensive routes are the only means available.

Such a talker circuit option provides, therefore, a user with specific instructions which are easily understood regarding gaining access to a desired economical trunk line, such as WATS or other more economical trunk. Talker circuit 22 will provide specific instructions to the user who is requesting access to a specified trunk such as a WATS and will advise the user request with other options available.

FIG. 1 also includes a main processor 30, which provides the system with general supervision of line interface unit 20. Processor 30 typically includes a Z80A microprocessor with RAM memory and other components illustrated for providing the necessary supervisory functions required.

Additional storage capability is provided to the system through a floppy controller/calendar circuit 40, which is connected to main processor 30 via bus 32. The floppy controller circuit 40 is in turn connected to a conventional floppy storage device 42 through bus 44.

Referring now to FIG. 2, a more detailed diagram of the line interface unit 20 of FIG. 1 is depicted.

In FIG. 2, line interface unit 20 is shown with only one of the six lines 18 (specifically line 18-1) which is connected to conventional subscriber lines (or tip-ring lines) 12 of FIG. 1.

In FIG. 2, the connections could be to two- or four-wire tip-ring pairs, as required by particular system necessities.

The relay off-hook circuit 52 is connected to the tip-ring pair 18 which, together with holding coil circuit 54 and transformer 56, provide the necessary coupling for "connecting" line interface unit 20 to the particular subscriber line.

Line interface unit 20 of FIG. 2 also includes a ring detect circuit 58, DTMF (dual tone multifrequency) decoder circuit 92 and dial tone detect circuit 94, all of which are connected to microprocessor 72, which is typically an 8048 microprocessor.

Microprocessor 72 in FIG. 2 is also connected to dual tone multifrequency generator circuits 74, 76, which are in turn connected to conventional multiplexer circuit 86.

Dial tone generator circuit 78 is also connected to multiplexer 86, together with test tone circuit 80 and silence circuit 88.

The output of line interface unit 20 via bus 24 is to talker circuit 22 with the output identified as bus 24-2 and the input bus identified as 24-1, as depicted in FIG. 2.

Multiplexer circuit 86 is controlled by microprocessor 72 and provides suitable multiplexing of desired signals through channel bank filter 84 and signal power limit circuit 82 for transformer coupling through transformer 56 to tip-ring pair 18.

In addition, microprocessor 72 is connected to a main processor via bus 28, via standard multibus interface 70, which is typically an 8-bit data bus.

Filter circuit 90 provides filtering for noise typically present in a subscriber environment. The signal power limit circuit 82 and channel bank filter 84 are also provided for required filtering of the system.

In order to illustrate in more detail one aspect of the present invention, a typical call sequence will be described in conjunction with the system depicted in FIGS. 1 and 2.

First assume an extension within the user environment desires to call another extension within the same complex via telephone subscriber lines 12.

Assume further that the second extension is a line connected to the present invention instead of another typical extension within the system.

The PBX 14 of FIG. 1 would then apply ring voltage to line interface unit 20. Ring detect circuit 58 of FIG. 2 would detect the ring voltage. Microprocessor 72 scans ring detect circuit 58, and after detecting the ring detect signal (for typically two samples), microprocessor 72 sends a code to main processor 30 of FIG. 1 telling processor 30 that the channel is being rung.

Main processor 30 sends a command to microprocessor 72 of FIG. 2 through bus 28 telling microprocessor 72 to activate off-hook relay 52.

Microprocessor 72, in response to this command, activates relay circuit 52 thereby answering the "call".

Main processor 30 sends a command to microprocessor 72, telling it to connect dial tone through generator circuit 78. Microprocessor 72 connects dial tone generator 78 to line 18-1.

The extension has now received the dial tone and now begins to "dial" the desired number. With a pushbutton type telephone subscriber set, dual tone multifrequency tones are generated, and DTMF decoder circuit 92 will detect valid digits. Microprocessor 72 reads this decoding and passes it to main processor 30. After the first digit, dial tone generator circuit 78 is connected and "silence" circuit 88 is connected to the subscriber line.

When main processor 30 determines it has enough digits to determine how to route the desired call, processor 30 sends an on-hook command to microprocessor 72, which in turn deactivates relay off-hook circuit 52. 400 milliseconds later, processor 30 tells microprocessor 72 to go back off-hook, and microprocessor 72 activates the off-hook relay circuit 52 (which is in effect a "flash" signal). The "flash" signal provides a technique for communicating with the PBX equipment.

Main processor 30 sends a command to microprocessor 72 to wait for dial tone. Microprocessor 72 scans dial tone circuit 94 waiting for two samples of tone present.

When dial tone is detected by detector circuit 94, microprocessor 72 sends a code back to main processor 30 telling it that tone has in fact been detected.

Main processor 30 sends a command to microprocessor 72 to "outpulse" (turn DTMF tones on and off) a trunk access code.

Main processor 30 then sends a command to microprocessor 72 to wait for the dial tone from the trunk, and when microprocessor 72 detects dial tone it tells main processor 30 of this event.

Main processor 30 then tells microprocessor 72 to "outpulse" the rest of the digits.

After the last digit is outpulsed, main processor 30 tells microprocessor 72 to go on-hook, and microprocessor 72 then sets relay off-hook circuit 52 on-hook, thereby disconnecting line interface unit 20 from the call request loop. The caller's desired number is handled thereon by PBX circuit 14.

A preferred embodiment of the PBX telephone call control system has been shown and described. As will be clear to those skilled in the art, variations of the system would come within the scope of the accompanying claims.

For example, the call control system provides call routing requests from internal extensions to external trunks, and from external trunks to internal extensions. The system also would provide additional call routing access such as from external trunks to other external trunks, as well as internal extensions. An example of such an external/internal routing access is if the user of the system were located outside of the system and wanted an information update or access to an internal extension through, for example, an in-WATS trunk line, he would merely need to call in to the call control system for the necessary update or routing to the internal extension. As another example, a caller could call into the system in order to access an external WATS trunk line.

Other aspects of the improved call control system include voice recognition, voice prompting aspects as described above, and voice storing and forwarding.

The last mentioned aspect would store messages and, upon request, transmit those voice messages over a long distance trunk line, conveying the messages at cheaper rates. The voice storing and forwarding feature could be achieved as illustrated in FIG. 2 by the line interface unit interfacing with a voice message switching (VMS) circuit 96, which is connected to analog expansion bus 24-2.

The VMS capability provides voice-storing, playback and forwarding capabilities, such as in a situation where a person calls into the system, leaves a voice message for another person, and is optionally transferred to a requested internal extension or external trunk. The system can, of course, provide necessary transfers of stored voice messages to any other extension within the system, or to any external trunk, thereby providing playback of the voice messages to the caller.

The overall system described above provides an improved PBX telephone call control system which adds additional features to existing PBX equipment, yet looks like any other extension to the rest of the system, while providing the necessary control of telephone call routing requests.

It is therefore intended that the scope of the present invention shall be limited only by the accompanying claims and any logical equivalents thereof.

Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US3111561 *Nov 23, 1959Nov 19, 1963American Telephone & TelegraphIntercept equipment
US3179750 *Dec 23, 1960Apr 20, 1965American Telephone & TelegraphPbx in-dialing circuit
US3347988 *Jun 17, 1963Oct 17, 1967Bolt Beranek & NewmanMethod of and system for remotelocation computer communication via telephone
US3482057 *Jan 28, 1966Dec 2, 1969IbmAutomatic intercept system
US3510598 *Oct 22, 1965May 5, 1970Salzberg Emmett RTelephone call diverter and answering device
US3614328 *Jun 24, 1969Oct 19, 1971Kenneth Eugene McnaughtonAutomatic subscriber answering service
US3793487 *Jun 26, 1972Feb 19, 1974Kilby JSystem for screening telephone calls
US3859473 *Jul 31, 1973Jan 7, 1975Stromberg Carlson CorpCentralized attendant service arrangement for PABX complex
US3867582 *Jun 12, 1973Feb 18, 1975United Business CommunicationsRemote control for private automatic branch telephone exchange
US3963875 *Nov 4, 1974Jun 15, 1976Stromberg-Carlson CorporationUniversal answer arrangement for a PABX
US3985971 *Jul 22, 1974Oct 12, 1976Colpoys John RTelephony
US3989901 *Apr 30, 1975Nov 2, 1976Message Center Systems, Inc.Optional telephone answering system
US3992587 *Aug 19, 1974Nov 16, 1976National Data CorporationRemote data line monitor
US4086438 *Mar 7, 1977Apr 25, 1978Teletech CorporationAutomatic interconnection system
US4088838 *Dec 20, 1976May 9, 1978Hitachi, Ltd.Voice response system
US4122308 *Jun 3, 1977Oct 24, 1978Utility Verification Corp.Telephone call metering device
US4139739 *Jul 5, 1977Feb 13, 1979Tdx Systems, Inc.Telecommunications call back system
US4152547 *Nov 29, 1977May 1, 1979Theis Peter FSelective monitor for an automatic telephone answering system
US4191855 *Aug 26, 1977Mar 4, 1980Hitachi, Ltd.Full duplex audio response device
US4200772 *Oct 18, 1976Apr 29, 1980Graphic Scanning Corp.Computer controlled telephone answering system
US4232199 *Oct 18, 1978Nov 4, 1980Summa Four, Inc.Special services add-on for dial pulse activated telephone switching office
US4255618 *Apr 18, 1979Mar 10, 1981Gte Automatic Electric Laboratories, IncorporatedDigital intercept recorder/announcer system
US4327251 *Mar 17, 1980Apr 27, 1982Radionics Inc.Automatic telephone directory message system
US4356351 *Oct 14, 1980Oct 26, 1982Ford Industries, Inc.Digital memory audio playback apparatus
US4371752 *Nov 26, 1979Feb 1, 1983Ecs Telecommunications, Inc.Electronic audio communication system
US4376875 *Nov 10, 1980Mar 15, 1983Mitel CorporationKeyless and indicatorless local telephone switching system
US4413158 *May 13, 1982Nov 1, 1983Danford Glenn SAutomatic call forwarding telephone apparatus
US4420656 *Aug 24, 1981Dec 13, 1983Michael FreemanInteractive telephone answering system
US4439635 *Feb 9, 1982Mar 27, 1984Peter F. TheisMessage delivery system
US4446553 *Oct 29, 1981May 1, 1984Gte Automatic Electric Labs Inc.Arrangement for multiple custom calling
US4484031 *Jun 21, 1982Nov 20, 1984Zale CorporationInterface circuit for a telephone system
US4488005 *May 13, 1982Dec 11, 1984Texas Instruments IncorporatedTelephone answering apparatus with call-screening capabilities
US4577062 *Sep 2, 1983Mar 18, 1986Butler National CorporationMethod for dispensing information
US4600814 *Oct 5, 1983Jul 15, 1986Manufacturing Administrations Management Systems, Inc.Automated system for establishing telephone voice connections
US4608640 *Jan 9, 1984Aug 26, 1986Nissan Motor Company, LimitedTrap regenerative device control apparatus
US4696028 *Mar 26, 1984Sep 22, 1987Dytel CorporationPBX Intercept and caller interactive attendant bypass system
US4975941 *Sep 21, 1987Dec 4, 1990Dytel CorporationCall processor for facilitating call completions
JPS4992908A * Title not available
JPS5690663A * Title not available
JPS5690664A * Title not available
JPS5754492A * Title not available
JPS56129469A * Title not available
JPS58187056A * Title not available
Non-Patent Citations
Reference
1"A Unique Monolithic AGC/Squelch Amplifier," AN-51, NS (Sep. 1971).
2"AC/DC to Logic Interface Optocoupler," HCPL-3700, Hewlett Packard (Feb. 1982).
3"AIS Automatic Intercept Service Versatile Efficient Information Service," Fujitsu Limited (date stamped 1972).
4"Applications of MT8860 Family of DTMF Receivers," Mitel Application Note (Aug. 1980).
5"Centrex-A Management Overview," Datapro Research Corp. (Nov. 1983).
6"Data Set 407 Interface Specification," AT & T (Jun. 1975).
7"Direct Inward Dialer", Telephonic Equipment Corp., p. D022956 (1981).
8"Direct Inward System Access":, Telephonic Equipment Corp., pp. D022965-22966(1981).
9"LF11508/LF13508 8-Channel Analog Multiplexer et al.," National Semiconductor (marked Jan. 1982).
10"LPC-10 Speech Synthesizer With On-Chip 20k Speech Data ROM," S3610, AMI (Aug. 1982).
11"Rohm Centralized Attendant Service," Rolm Corp (1979).
12"ROLMphone User Guide," pp. 2-4, 17, 24, 83, and 86 (Rolm, Jul. 1985).
13"S2559 DTMF Tone Generator," AN-101, AMI (Aug. 1982).
14"Sine Wave Oscillator," AN20-9 (undated).
15"Telephone Coupling Transformers," Litton Triad-Utrad Distributor Services, Form TCT-74 (undated).
16"Tone Decoder/Phase Locked Loop," Signetics (marked 1976).
17"TP3040/TP3040A PCM Monolithic Filter," National Semiconductor (marked 1982).
18"Unanswered Call Diverter," IBM Technical Disclosure Bulletin, vol. 25, No. 7A, Dec. 1982, pp. 3480-3481.
19 *A Unique Monolithic AGC/Squelch Amplifier, AN 51, NS (Sep. 1971).
20 *AC/DC to Logic Interface Optocoupler, HCPL 3700, Hewlett Packard (Feb. 1982).
21 *AIS Automatic Intercept Service Versatile Efficient Information Service, Fujitsu Limited (date stamped 1972).
22 *Applications of MT8860 Family of DTMF Receivers, Mitel Application Note (Aug. 1980).
23 *Centrex A Management Overview, Datapro Research Corp. (Nov. 1983).
24 *Data Communications, pp. 158 and 160 (Jul. 1983).
25 *Data Set 407 Interface Specification, AT & T (Jun. 1975).
26 *Direct Inward Dialer , Telephonic Equipment Corp., p. D022956 (1981).
27 *Direct Inward System Access :, Telephonic Equipment Corp., pp. D022965 22966(1981).
28E. Smith, "Glossary of Communications," p. 64 (Telephony Publishing Corp. 1971).
29 *E. Smith, Glossary of Communications, p. 64 (Telephony Publishing Corp. 1971).
30 *G. Langley, Telephony s Dictionary, p. 128 (2d.ed.), 1986.
31G. Langley, Telephony's Dictionary, p. 128 (2d.ed.), 1986.
32 *IEEE Standard Dictionary of Electrical and Electronics Terms, pp. 245 and 357 (3rd. ed. 1984).
33J. Peatman, "I/O Control" (Chap. 5-1), I/O Timing (Chap. 5-2), Real-Time Programming (Chap. 7-2), Microcomputer-Based Design (McGraw Hill, 1977).
34 *J. Peatman, I/O Control (Chap. 5 1), I/O Timing (Chap. 5 2), Real Time Programming (Chap. 7 2), Microcomputer Based Design (McGraw Hill, 1977).
35K. Tapper & P. Thatte, "GTD-1000 Digital PABX CAS Main/ACD," GTE Automatic Electric Journal, pp. 182-193 (Nov. 1980).
36 *K. Tapper & P. Thatte, GTD 1000 Digital PABX CAS Main/ACD, GTE Automatic Electric Journal, pp. 182 193 (Nov. 1980).
37L. Goeller, Jr. & J. Goldstone, "The ABCs of the PBX," Datamation, pp. 9-13 (Apr. 1983).
38 *L. Goeller, Jr. & J. Goldstone, The ABCs of the PBX, Datamation, pp. 9 13 (Apr. 1983).
39 *LF11508/LF13508 8 Channel Analog Multiplexer et al., National Semiconductor (marked Jan. 1982).
40 *LPC 10 Speech Synthesizer With On Chip 20k Speech Data ROM, S3610, AMI (Aug. 1982).
41M. Hills & S. Kano, "Programming Electronic Switching Systems-Real-Time Aspects and Their Language Implications," Section 2.4.2, Scheduling Functions Divided Systems, pp. 37-39, IEEE Telecommunications Series (Peter Peregrinus Ltd. 1976).
42 *M. Hills & S. Kano, Programming Electronic Switching Systems Real Time Aspects and Their Language Implications, Section 2.4.2, Scheduling Functions Divided Systems, pp. 37 39, IEEE Telecommunications Series (Peter Peregrinus Ltd. 1976).
43M. Weik, "Communications Standard Dictionary," pp. 238 and 364 (Van Nostrand Reinhold Co. 1983).
44 *M. Weik, Communications Standard Dictionary, pp. 238 and 364 (Van Nostrand Reinhold Co. 1983).
45R. Kaloian, "What if you cut over a new telecom system . . . and nobody used it?" Communication Age, pp. 46-47 and 50 (Sep. 1986).
46 *R. Kaloian, What if you cut over a new telecom system . . . and nobody used it Communication Age, pp. 46 47 and 50 (Sep. 1986).
47R. Zarlenga, "Business Telephones With Enhanced Features: The Old Phone Gets Smart," Telephony v. 199 n. 2 pp. 78-79 (Jul. 14, 1980) (abstract).
48 *R. Zarlenga, Business Telephones With Enhanced Features: The Old Phone Gets Smart, Telephony v. 199 n. 2 pp. 78 79 (Jul. 14, 1980) (abstract).
49 *Rohm Centralized Attendant Service, Rolm Corp (1979).
50 *ROLMphone User Guide, pp. 2 4, 17, 24, 83, and 86 (Rolm, Jul. 1985).
51 *S2559 DTMF Tone Generator, AN 101, AMI (Aug. 1982).
52 *Sine Wave Oscillator, AN20 9 (undated).
53T. Kopec & P. Lind, "Electronic Business Telephone," GTE Automatic Electric Journal pp. 34-40 (Mar. 1980).
54 *T. Kopec & P. Lind, Electronic Business Telephone, GTE Automatic Electric Journal pp. 34 40 (Mar. 1980).
55T. Smith, "Abc of the Telephone," p. 20, BNR Inc. (undated).
56 *T. Smith, Abc of the Telephone, p. 20, BNR Inc. (undated).
57 *Telephone Coupling Transformers, Litton Triad Utrad Distributor Services, Form TCT 74 (undated).
58 *Telephone Engineer and Management, p. 67 (Mar. 15, 1979).
59 *Telesis (AT&T), p. 32 (1982 one).
60 *The Teleconnect Dictionary, p. 177. (undated).
61 *Tone Decoder/Phase Locked Loop, Signetics (marked 1976).
62 *TP3040/TP3040A PCM Monolithic Filter, National Semiconductor (marked 1982).
63 *Unanswered Call Diverter, IBM Technical Disclosure Bulletin, vol. 25, No. 7A, Dec. 1982, pp. 3480 3481.
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US5471523 *Jul 14, 1993Nov 28, 1995Voysys CorporationTelephone call and voice processing system
US5588045 *Feb 3, 1995Dec 24, 1996Siemens Rdm Communications Inc.Voice/data transfer method and apparatus utilizing an alternate line
US5875242 *Jul 26, 1996Feb 23, 1999Glaser; Lawrence F.Telecommunications installation and management system and method
US5923745 *Feb 28, 1997Jul 13, 1999Teknekron Infoswitch CorporationRouting calls to call centers
US6185293Mar 16, 1998Feb 6, 2001Samsung Electronics Co., Ltd.Signal matching apparatus for exchanging signals between an analog switching system and a digital switching system
US6301353 *Aug 1, 2000Oct 9, 2001Mitel CorporationCommon automatic route selection leading digit strings
US6522743Apr 26, 1999Feb 18, 2003E-Talk CorporationRouting calls to call centers
US6677513May 29, 1998Jan 13, 2004International Business Machines CorporationSystem and method for generating and attenuating digital tones
US6707887 *Mar 16, 2001Mar 16, 2004Siemens Information And Communication Networks, Inc.System and method for automatic detection of loop start and ground start trunks
US7006078May 7, 2002Feb 28, 2006Mcquint, Inc.Apparatus and method for sensing the degree and touch strength of a human body on a sensor
US7864992Jun 18, 2004Jan 4, 2011Fingerprint Cards AbFingerprint sensor element
US8626375Mar 4, 2011Jan 7, 2014Bosch Automotive Service Solutions LlcMultiplexing device with provision for expansion
Classifications
U.S. Classification379/67.1, 379/214.01
International ClassificationH04M3/493, H04M3/533, H04M3/38, H04M3/22, H04M3/58, H04Q3/62, H04M3/42, H04M3/527
Cooperative ClassificationH04M3/493, H04M15/8044, H04Q3/625, H04M3/38, H04M3/382, H04M3/58, H04M3/42314, H04M3/2218, H04M2215/745, H04M3/533, H04M2215/42, H04M3/527
European ClassificationH04M15/80H, H04M3/527, H04M3/42P, H04Q3/62F, H04M3/38
Legal Events
DateCodeEventDescription
Feb 22, 2011ASAssignment
Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535
Effective date: 20110211
Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLAT
Dec 29, 2008ASAssignment
Owner name: AVAYA TECHNOLOGY LLC, NEW JERSEY
Free format text: CONVERSION FROM CORP TO LLC;ASSIGNOR:AVAYA TECHNOLOGY CORP.;REEL/FRAME:022071/0420
Effective date: 20051004
Jun 27, 2008ASAssignment
Owner name: AVAYA INC., NEW JERSEY
Free format text: REASSIGNMENT;ASSIGNOR:AVAYA TECHNOLOGY LLC;REEL/FRAME:021158/0290
Effective date: 20080625
Nov 28, 2007ASAssignment
Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT, NEW Y
Free format text: SECURITY AGREEMENT;ASSIGNORS:AVAYA, INC.;AVAYA TECHNOLOGY LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:020166/0705
Effective date: 20071026
Free format text: SECURITY AGREEMENT;ASSIGNORS:AVAYA, INC.;AVAYA TECHNOLOGY LLC;OCTEL COMMUNICATIONS LLC AND OTHERS;REEL/FRAME:20166/705
Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT,NEW YO
Nov 27, 2007ASAssignment
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT, NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNORS:AVAYA, INC.;AVAYA TECHNOLOGY LLC;OCTEL COMMUNICATIONS LLC;AND OTHERS;REEL/FRAME:020156/0149
Effective date: 20071026
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT,NEW YORK
Free format text: SECURITY AGREEMENT;ASSIGNORS:AVAYA, INC.;AVAYA TECHNOLOGY LLC;OCTEL COMMUNICATIONS LLC AND OTHERS;REEL/FRAME:20156/149
Jun 29, 2006ASAssignment
Owner name: OCTEL COMMUNICATIONS CORPORATION, NEW JERSEY
Free format text: MERGER;ASSIGNOR:VMX, INC.;REEL/FRAME:018015/0252
Effective date: 19950428
Nov 22, 2005FPAYFee payment
Year of fee payment: 12
Apr 9, 2002ASAssignment
Owner name: BANK OF NEW YORK, THE, NEW YORK
Free format text: SECURITY INTEREST;ASSIGNOR:AVAYA TECHNOLOGY CORP.;REEL/FRAME:012762/0098
Effective date: 20020405
Owner name: BANK OF NEW YORK, THE 5 PENN PLAZA, 13TH FLOOR NEW
Owner name: BANK OF NEW YORK, THE 5 PENN PLAZA, 13TH FLOORNEW
Free format text: SECURITY INTEREST;ASSIGNOR:AVAYA TECHNOLOGY CORP. /AR;REEL/FRAME:012762/0098
Mar 26, 2002ASAssignment
Owner name: AVAYA TECHONOLGY CORP., NEW JERSEY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LUCENT TECHONOLOGIES INC.;REEL/FRAME:012683/0613
Effective date: 20000929
Owner name: LUCENT TECHNOLOGIES INC., NEW JERSEY
Free format text: MERGER;ASSIGNOR:OCTEL COMMUNICATIONS CORPORATION;REEL/FRAME:012683/0483
Effective date: 19970929
Owner name: AVAYA TECHONOLGY CORP. 211 MOUNT AIRY ROAD BASKING
Owner name: AVAYA TECHONOLGY CORP. 211 MOUNT AIRY ROADBASKING
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LUCENT TECHONOLOGIES INC. /AR;REEL/FRAME:012683/0613
Owner name: LUCENT TECHNOLOGIES INC. 600 MOUNTAIN AVENUE MURRA
Owner name: LUCENT TECHNOLOGIES INC. 600 MOUNTAIN AVENUEMURRAY
Free format text: MERGER;ASSIGNOR:OCTEL COMMUNICATIONS CORPORATION /AR;REEL/FRAME:012683/0483
Sep 27, 2001FPAYFee payment
Year of fee payment: 8
Feb 23, 1998SULPSurcharge for late payment
Feb 23, 1998FPAYFee payment
Year of fee payment: 4