WO1999034624A9

WO1999034624A9 - An automated paging device

Info

Publication number: WO1999034624A9
Application number: PCT/US1998/027381
Authority: WO
Inventors: Giora Eyran; Lisa Amberger; Phil Mccurry; Michael D Lynes
Original assignee: Bogen Communications Inc; Giora Eyran; Lisa Amberger; Phil Mccurry; Michael D Lynes
Priority date: 1997-12-24
Filing date: 1998-12-24
Publication date: 1999-09-23
Also published as: AU2307299A; WO1999034624A1

Abstract

A system for initiating pages over one or more paging devices (14) using a paging controller is presented. The paging device(s) can be virtually any type of overhead pager, local area pager, or wide area pager. The paging controller includes a firmware memory containing an operating system, a database memory containing paging protocols, and an audio content memory containing pre-recorded audio content. The paging controller also includes a digital communication interface for downloading the operating system to the paging controller. The paging controller can be connected to a PBX (10) and thereby allows callers to selectively initiate pages over the paging device(s) (14). The paging controller can also be used with the PBX to park a caller on an extension of the PBX (10) and then initiate a page for the called party over an overhead pager or local area pager.

Description

AN AUTOMATED PAGING DEVICE

Background nf the Invention

The present invention relates to automated paging devices. It also relates to an interface between pagers and a PBX and to the recording of audio content to be played on an overhead paging device.

Many businesses rely on a receptionist to locate employees who are not available at their phone when an incoming call is received for the employee. This is an inefficient use of the receptionist, who must keep track of employees in case the employee receives a phone call and must locate the employee when a call is received. Even businesses that utilize overhead paging often rely on a human receptionist to make the pages.

Existing "on-site" wireless paging devices offer limited solutions to the use of a human receptionist. These devices allow an employee to be paged within a limited range using a low power on-site transmitter. Many of these devices are automated, such that a human receptionist is not required to initiate the page. Examples of on-site paging devices include the Motorola PeopleFinder, the Rock Systems WaveLinks, and the Multitone Communications System, Ltd. Access 3000.

Existing on-site paging systems have several drawbacks. Many of these systems are limited to a single paging device. The use of a single device ignores the benefits of multiple paging devices, such as the complementary use of an overhead pager, a local area pager, and a wide area pager in the same system. Existing on-site paging systems also overlook the use of an overhead paging device to notify a called party of a caller waiting on a telephone line, without the intervention of a human operator. In view of these and other limitations, new and improved automated paging controllers are needed. Summary of the Invention

The present invention addresses the lack of automated paging in the office environment. The invention uses standard analog port interfaces to connect to virtually any PBX. It works with virtually any voice-mail, auto attendant, and overhead paging device.

The invention provides a solution to the problem of routing calls to paging devices. Incoming calls can be routed to the paging controller using the call forwarding features provided by a PBX. The paging controller then offers the caller the option to automatically page the called party and provides the interface to multiple paging devices.

The invention also provides a solution to the problem of notifying a called party of a . caller waiting on a telephone line, without the intervention of a human operator. The "park and meet-me" feature allows callers to reach a called party that is not at his or her telephone when the call is placed. The park and meet-me feature utilizes the park feature of the PBX to park an external call at a specific location on the PBX. The paging controller then initiates a page via local area or overhead paging informing the called party of the call and where it can be located on the PBX.

Brief Description of the Drawings

Figure 1 illustrates pager systems with peripherals arranged in a known arrangement;

Figure 2 illustrates a pager system configured in accordance with a preferred embodiment of the present invention;

Figure 3 illustrates a pager system configured in accordance with an alternative embodiment of the present invention; Figure 4 illustrates the paging controller of the preferred embodiment of the present invention;

Figure 5 further illustrates the paging controller of the preferred embodiment of the present invention;

Figure 6 illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 7 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 8 further illustrates the logic of a user selecting an announcement for the present invention;

Figure 9 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 10 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 11 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 12 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 13 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 14 further illustrates the logic of the paging controller of the preferred embodiment of the present invention; Figure 15 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 16 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 17 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 18 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 19 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 20 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 21 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 22 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 23 further illustrates the logic of the paging controller of the preferred embodiment of the present invention;

Figure 24 further illustrates the logic of the paging controller of the preferred embodiment of the present invention.

Description of the Preferred Embodiment In Figure 1, several known paging devices are illustrated in known configurations. Pages are known in the art as a broadcast alert signal to a party or parties. Paging devices are known in the art as means for transmitting pages to the party or parties. Paging devices include, as means of example only, overhead paging devices, which employ overhead speakers to broadcast an audible signal, and wireless paging devices, which transmit signals to wireless pagers, such signals resulting in an audible, visual, or tactile alert via the wireless pager. In Figure 1, a PBX 10 is uniquely connected to either an overhead pager and speaker 11 or a wireless paging device 12 which transmits to a wireless pager 14. In an alternative known embodiment, a voice-mail or auto attendant 13 is connected to the PBX 10.

Figure 2 illustrates an automated paging system configured in accordance with a prefe ed embodiment of the present invention. The paging controller 100 of the current invention is shown connected via a standard computer interface, preferably RS-232, to a wireless paging device 120. The wireless paging device 120 transmits to a wireless pager 121. The paging controller 100 is also connected to a PBX 110. The PBX 110 is then connected to an overhead pager 111, phone lines 114, and a voicemail system or an auto-attendant 115. The overhead pager 111 is connected to a speaker 112. Such voicemail systems and auto-attendants are well known in the art. The paging controller 100 is further connected to a local personal computer 130 directly or to a remote personal computer 131 via a modem 132. The paging controller 100 is connected to one or more external triggering device(s) 101 via a standard interface, preferably a nine-pin serial port. The external triggering device(s) 101 can be any type of trigger. By way of example only, appropriate external triggering devices 101 include infrared detectors, acoustic detectors, or contact/pressure switches. Figure 3 illustrates another embodiment of the present invention where the paging controller 100 is connected to a plurality of personal computers 135 via an Ethernet local area network 136.

Figure 4 illustrates the preferred embodiment of the paging controller 100 of the present invention. The paging controller 100 includes a microcontroller 260, a microcontroller RAM 261, a firmware memory 213, a database memory 211, an audio content memory 212, a first UART 220, a second UART 221, a plurality of codecs 230, an 1ST interface 240, and discrete logic 250. A codec, or signal coder-decoder, is a circuit for quantizing an analog signal into a digital signal and, conversely, retrieving an analog signal from a digital signal, and is well known in the art. The plurality of codecs 230 comprises one codec for each active port of the paging controller 100. The microcontroller RAM 261 stores instructions retrieved from the firmware memory 213 and database memory 211. The firmware memory 213, database memory 211, and audio content memory 212 can be any type of memory; however, a FLASH memory device is preferably used as it permits read/write access with high reliability, non-volatile data storage, and data integrity without a battery, as will be appreciated by one skilled in the art. The firmware memory 213, database memory 211, and audio content memory 212 can be separate physical devices; however, it is preferred that the firmware memory 213 and database memory 211 be partitions within a single memory device 210, as it allows a smaller memory footprint within the paging controller. It is preferred that the audio content memory 212 remain a separate device to allow the paging controller memory to be expanded to accommodate more users.

Figure 5 presents a further detailed description of the paging controller 100 of the preferred embodiment. The microcontroller device 350 includes the microcontroller 260, the microcontroller RAM 261, and the first UART 220 internal to the microcontroller device 350, attached to associated RS232 logic 300. The firmware memory 213 and database memory 21 are shown as a single FLASH memory device 301. while the audio content memory 212 is shown as a plurality of FLASH memory devices 302. Memory selection logic 303, well known in the art, is capable of selecting the memory locations within the FLASH memory devices 301 and 302. The microcontroller device 350 is attached to a voltage supervisor/watchdog circuit 304, well known in the art, to provide a proper reset to the microcontroller device 350. The second UART 221 is further detailed as a UART external to the microcontroller device 350. Associated RS232 logic 307 is connected to the second UART 221. The plurality of codecs 230 are detailed as a plurality of codecs 308 and an associated VOX detection circuit 314 attached to a first codec and a second codec of the plurality of codecs 308. This VOX detection circuit 314 is employed during voice recording on the 1ST interface 240. The 1ST interface 240 is further detailed as a plurality of Telco interfaces 306 with the associated plurality of 2-to-4 wire converters 309 and plurality of DTMF transceivers 310. The analog switches 316 allow the connection of the various Telco interfaces 306 to the DTMF transceivers 310. An outbound port 360 of the paging controller comprises a third Telco interface of the plurality of Telco interfaces 306 connected to a third codec of the plurality of codecs 308 and third DTMF transceiver of the plurality of DTMF transceivers 310, and does not have an associated VOX detection circuit. The discrete logic 250 is further detailed as the plurality of I/O devices 312 attached to the external inputs 311 and the plurality of DTMFs 307.

The firmware memory 213 stores the operating system code or firmware. The firmware, as will be apparent to one skilled in the art, is comprised of the set of microcontroller instructions necessary for proper operation of the specific application. The firmware instructs the microcontroller 260 to perform the required polling and processing operations inherent to the desired system behavior and properties. Referring to Figure 1, the firmware is downloaded' to- the firmware memory 213 via any device that can provide the proper instructions at the proper transmission speed, preferably a local personal computer 130, a remote computer 131, or a plurality of personal computers 135.

The database memory 211 stores the database of user information. The database is comprised of the paging protocol, or user options and instructions, associated with the user's extension. The user options comprise a selection of the paging devices through which the user wishes to be paged and other user selected options of the paging controller. The user instructions comprise scripts for local area and wide area pages. The paging protocol is entered into the database using the local personal computer 130, the remote computer 131, or the plurality of personal computers 135. The user's paging method can be modified in the database memory 211 by dialing a phone number associated with the paging controller 100 and selecting options provided by the firmware.

The audio content memory 212 stores audio content comprising voice prompts and voice recordings for extensions on the system. Site-specific audio content is recorded by dialing a phone number associated with the paging controller 100. The audio content is then digitized using one of the plurality of codecs 230. The digitized audio content is then stored in the audio content memory 212.

The microcontroller 260 accesses the audio content memory 212 to retrieve stored audio content based on the state of the active one of the phone lines 114 and inputs from the caller. The selected audio content is retrieved according to the firmware and sent to one of the plurality of codecs 230. The selected codec translates the selected audio content from a digital signal to an analog signal. The translated audio signal is then routed to the PBX 110, which causes the message to be broadcast on the active one of the phone lines 114.

The microcontroller 260 can be programmed to respond to discrete events by executing a programmed script. The discrete events include the output of the external triggering devices 101. The script can include, for example, a combination of overhead announcements, overhead pages, local pages and/or wide area pages. The script is stored in the database memory 211. On the occurrence of a discrete event, the microcontroller 260 polls the database memory 211 to determine if a response is required. If a script exists for the given discrete event, the microcontroller 260 accesses the audio content memory 212 for the audio content indicated-in the script. The selected audio content is then routed to the outputs indicted by the script.

In Figure 6, a typical phone call event to the service port of the paging controller 100 is diagrammed in a preferred embodiment of the firmware. In State 7, the paging controller 100 is on-hook waiting for a caller. The firmware returns to State 7 whenever a caller hangs up or a timeout occurs. In State 8 a ring is detected and the paging controller 100 answers the call. The firmware waits in State 8A for the called party to be identified via the called party identification ("CPID") feature in State 8 A, if it is enabled. (CPID is a feature of PBXs that is well known in the art.) The call is then initially processed in State 9. The caller can chose to either play an overhead announcement in State 9P or initiate a transfer of the call in State 10.

In Figure 7, the processing of State 9 is further described in a preferred embodiment. Callers will be told in State 9B2 that the paging service is unavailable if the called party has selected overhead paging but the corresponding name has not been recorded. Similarly, if the called party has disabled overhead paging and the caller selects overhead paging, the caller is told in State 9B3 that paging service is unavailable. If CPID was received, the firmware transitions from State 9 to State 9A or State 15. If CPID was not available, the firmware polls the caller in State 9B for the extension of the party he or she wishes to page. The firmware includes a confirmation function that, when enabled, plays the name of the called party or the number entered by the caller and asks the caller to confirm that the information is correct. The confirmation function is used at various times in the operation of the paging controller 100. For example, following State 9B, if confirmation is enabled, the firmware confirms the called extension in State 9C and waits for the caller to acknowledge that the extension is the one the caller intended. Regardless of whether confirmation is enabled, if the called party has enabled wide area paging, in State 15 the firmware collects the information to be displayed on the wide area pager, following State 9B (without confirmation) or State 9C (with confirmation). Similarly, if the called party has not enabled wide area paging, the firmware determines in State 9A whether the call is internal or external to the phone system containing the paging controller 100. State 9A can occur immediately after State 9, after polling in State 9B, or after confirmation in State 9C. If the caller is external and the called party has enabled local paging, the firmware proceeds to State 12P and parks the call while the local paging is made.

Figures 8 and 9 are similar to Figure 7, but clarify that the error states (States 9B2 and 9B3) can also be reached from State 9B and State 9C, respectively.

Figure 10 further describes the processing of State 9 in a preferred embodiment. If the firmware identifies the call as an internal call in State 9A, the caller can enter a number in State 9D where the caller can be reached. If confirmation is enabled, State 9E confirms that the caller properly entered the number. If the called party has a local area alphanumeric pager, then the caller can transition the firmware to State 9F, where the caller can choose to send one of a plurality of alphanumeric pages pre-programmed into the database. In State 9H the caller is told that the page was sent.

Figure 11 describes the process a user of the automated paging system who calls the system undertakes to play an overhead announcement or to program the paging controller 100. The firmware transitions to State 9P from State 9. If the user wishes to program the paging controller 100 the firmware transitions to State 20. In State 9Q, the user enters his or her extension. If the extension is valid, the firmware polls the user for his or her password in State 9R. If the password is valid, the user is allowed to select an overhead announcement in State 9S that is played in State 9T.

Figure 12 describes the case of transferring a call to a voicemail system. If the transfer can be accomplished without supervision by the paging controller 100, the transfer takes place after State 10 and the paging controller 100 and firmware are returned to State 7. If the paging controller system operator determines that supervision is required, a flag is set so that any transfer to voicemail initiates a script in State 11 before handing off the call to the voicemail system and returning to State 7. The voicemail script defines the series of digits that will be dialed in order to access a particular voicemail box. If CPID information was gathered in State 8 A, it is used in the voicemail script .

Figure 13 further describes the process of performing a local or overhead page for a called party. In State 12, the local or overhead page is made and the call is terminated. If call parking is available, the caller is told to wait in State 12P while the local or overhead page is made. The call is parked in State 12P2. The paging controller 100 and firmware wait in State 12P25 for the PBX to indicate that the call is successfully parked. The local or overhead page is made in State 12P3. This page preferably informs the called party where the call has been parked, so that the called party can retrieve the call. If the call cannot be successfully parked, the paging controller 100 and firmware attempt to reconnect with the caller in State 12Q. If the reconnect is successful, the caller is given the option of transferring to voicemail or the auto- attendant, if either is present, in State 7C.

Figure 14 further describes the process of performing a wide area page. In State 15 the digits to be sent to the pager are collected. If confirmation is enabled, the digits are confirmed in State.15 A. The page is initiated in State 16. Figure 24 also describes the situation where the desired paging operation is inoperative. If the paging operation is inoperative, the caller receives a message in State 14.

In Figure 15, the functions of the outbound port 360 of the paging controller 100 are diagramed in a preferred embodiment of the firmware. In State 17, the outbound port 360 of the paging controller 100 is idle. If an overhead page is requested by a caller through the paging controller 100, and the called party has activated overhead paging, the overhead page is initialized in State 18. In State 18A2, the firmware determines whether the overhead paging device 111 is busy. If it is busy, the firmware waits in State 18A until the overhead paging device 111 is no longer busy or the number of retries is exceeded. When the overhead paging device 111 is not busy, the requested overhead page is performed in State 18B. If the overhead paging device 111 continues to be busy until the number of retries is exceeded in State 18A2, or if an error occurs during the page of State 18B, the paging controller 100 and firmware attempt to recover the caller in State 18C. If the recovery is successful in State 18D, a message is played to the caller in State 18E.

If a page is requested by the caller, and the called party has activated wide area paging, the paging controller 100 places the request in an internal first-in/first-out queue for wide area pages. The paging controller 100 performs the first wide area page in the queue by seizing the outbound port 360. In State 17B, the paging controller 100 attempts to obtain a dial tone on the outbound port 360 . If a dial tone is obtained in State 17B. the paging controller 100 dials the number for the called party's wide area pager in State 17C. The digits collected in State 15 are then transmitted as part of the wide area paging script in State 17D.

Figure 16 illustrates the programming mode of a preferred embodiment of the paging controller 100 and firmware. The firmware transitions to State 20 if the caller selects the programming mode in State 9P. In State 20 the firmware requests a valid password from the caller. If the caller fails to take an action, the firmware times out in State 22. If the caller, now a ''programmer^'', enters the correct password, the firmware waits in State 21. In State 21 A the paging controller 100 and firmware wait for any calls in progress to clear the service ports. If the programmer reached the second port it will be necessary to transfer the programmer from the second port to the first port. Such a transfer requirement ensures that only one party will attempt to program the paging controller 100 at a time. Similarly, the outbound port 360 must be idle before State 23 to ensure that the paging controller does not attempt to initiate a page while the programmer is modifying the system. If such a transfer is initiated in State 21 A, it is completed in State 2 IB. When the service ports are cleared and the outbound port 360 is idle, in State 23 the programmer selects from a menu of programming functions. In State 24 the programmer has selected to change the recording of a user of the automated paging system. In State 30 the programmer has selected to make a change to the main greeting or an overhead announcement.

Figure 17 illustrates the programming method associated with recording a particular user's name in a preferred embodiment of the present invention. If there is no existing recording of the user's name, the firmware prompts the programmer for the name to be associated with the extension in State 25. In State 25A the paging controller 100 and firmware record the name. In State 24A an existing name recording of a user name is deleted. If no new name was recorded the programmer is returned to State 23. Otherwise, the paging controller attempts to save the recorded user name in State 27 A. If the memory is full, the programmer is returned to State 23.

Figure 18 illustrates the manner of recording user names and announcements in a preferred embodiment of the present invention. If the caller does not speak while recording an announcement, he is prompted again in State 33. If the caller does not speak while recording a name, he is prompted again in State 25. The announcement is recorded in State 34. The name is recorded in State 26.

Figure 19 illustrates possible states of the paging controller 100 and firmware after the user performs a programming function. After a caller records a name in State 26, the firmware can disconnect and return to State 7, can re-record the name in State 25, can erase the name in State 24A, or can return to the programming menu in State 23. After a response has been reviewed in State 27, the device can disconnect and return to State 7, can erase the name in State 24A, or can return to the programming menu in State 23. Similarly, after requesting if the caller would like to program another extension in State 28, the device can disconnect and return to State 7, or it can return to State 24 to wait for the extension to be input.

Figure 20 illustrates the programming options at the system level. After receiving the correct system password in State 30, the programmer is given the option of selecting an announcement to change in State 31. An announcement can include a number of standard elements, including, as examples only, phrases (e.g., "Please call"), names, or numbers. If the programmer chooses to delete a valid announcement, but the announcement does not exist, the programmer is returned to State 23. If the programmer chooses to edit one of the standard elements of an announcement, he makes the selection of which element to edit in State 31 A. A new announcement is recorded in State 33. If there is a valid announcement selected in State 31, the firmware confirms the selected announcement in State 32.

Figure 22 is a more detailed illustration of the steps involved in recording an announcement after the programmer has selected a valid announcement. If the operation times out from a lack of input from the programmer, the paging controller returns to State 7. In State 23 the programmer has chosen to return to the programming menu. If the programmer wishes to delete an existing name, the name is deleted in State 24A. If the programmer chooses to record a new announcement, the programmer is prompted in State 33 and the announcement is recorded in State 25A.

Figure 22 is also a detailed illustration of the steps involved in reviewing a recorded announcement. If the operation times out from a lack of input from the programmer, the paging controller returns to State 7. If the programmer wishes to delete an existing announcement, the announcement is deleted in State 24A. The recorded announcement is played for review in State 33. The programmer reviews the announcement in State 35 and indicates whether the recording is satisfactory. In State 23 the programmer has either chosen to return to the programming menu, or has indicated that the reviewed announcement is satisfactory.

Figure 23 illustrates the options available to the programmer, if the programmer successfully records an announcement. If the operation times out from a lack of input from the programmer, the paging controller returns to State 7. In State 23 the programmer has chosen to return to the programming menu. The programmer can choose to review another announcement

in State 31. Figure 24 illustrates the options available to a user to change the method by which the user wishes to be paged. The user is prompted to enter the extension for which the change to the paging method should apply in State 50. In State 51 the user is prompted for a password to change the paging method. In State 52, the user selects a method of paging which is confirmed in State 53.

It is understood that changes may be made in the above description without departing from the scope of the invention. It is accordingly intended that all matter contained in the above description and in the drawings be interpreted as illustrative rather than limiting.

Claims

1. A system for initiating pages, said system comprising: at least one paging device; and a paging controller including a firmware memory containing an operating system; a database memory containing paging protocols; an audio content memory for storing pre-recorded audio content; at least one output connectable to said at least one paging device; a digital communication interface for downloading the operating system to the firmware memory; and a user customized paging control logic responsive to said operating system and said paging protocol for initiating pages; wherein said paging controller is connected to said at least one paging device.

2. The system according to claim 1, further comprising: a PBX connected to at least one telephone line; and, wherein said paging controller further comprises at least one input and output connectable to said PBX, is connected to said PBX via said at least one input and output, and is operable to present audio content from said audio content memory over said telephone line in response to input from said telephone line.

3. The system according to claim 2, wherein said paging control logic selectively controls the use of said at least one paging device based upon said operating system, said paging protocol, the state of said phone line and inputs from said phone line.

4. The system according to claim 2, wherein said at least one paging device is an overhead pager or a local area pager, said PBX allows a call to be parked, and said paging control logic is responsive to said operating system and said paging protocols for selectively initiating a page on said at least one paging device in response to a call being successfully parked.

5. The system according to claim 2, wherein said paging controller further includes: a coder-decoder associated with each of said at least one input and output, for translating analog signals into digital signals and digital signals into analog signals, whereby audio content may be received into said audio content memory from said telephone line or read from said audio content memory and sent to said telephone line.

6. The system according to claim 5, wherein said audio content is retrieved from said audio content memory using said operating system and based upon the state of said phone line and inputs from said phone line.

7. The system according to claim 2, further comprising a plurality of paging devices, wherein at least one of said paging devices is an overhead paging device and is connected to said PBX.

8. The system according to claim 7, wherein said paging control logic is responsive to said operating system and said paging protocols for sending said audio content to said overhead paging device via said PBX.

9. The system according to claim 2, further comprising a plurality of paging devices, wherein at least one of said paging devices is a local area paging device.

10. The system according to claim 9, wherein said paging protocols include at least one script of an alphanumeric page.

11. The system according to claim 10, wherein said paging control logic is responsive to said operating system and said paging protocols for sending an alphanumeric page to said local area paging device.

12. The system according to claim 2, further comprising a plurality of paging devices, wherein at least one of said paging devices is a wide area paging device.

13. The system according to claim 12, wherein said paging control logic is responsive to said operating system for sending a numeric page to said wide area paging device.

14. The system according to claim 2, wherein said PBX further includes: means for identification of the phone number being called.

15. The system according to claim 14, wherein said paging control logic is responsive to said operating system, said paging protocols, and said called party identification for initiating a page.

16. The system according to claim 2, further comprising: a voicemail system or auto-attendant connected to said PBX.

17. The system according to claim 16, wherein said paging control logic is responsive to said operating system and said paging protocols for transferring a phone call to said voicemail system or auto-attendant.

18. The system according to claim 1 , further comprising: a detector for signaling the presence of a person or occurrence of an event with a detection signal, said paging controller being responsive to said detection signal to initiate at least one page.

19. A system for initiating pages, said system comprising: a plurality of paging devices; and a paging controller including a firmware memory containing an operating system; a database memory containing paging protocols; an audio content memory for storing pre-recorded audio content; at least one output connectable to said plurality of paging devices; a digital communication interface for downloading the operating system to the firmware memory; and a user customized paging control logic responsive to said operating system and said paging protocol for initiating pages; wherein said paging controller is connected to said plurality of paging devices.

20. The system according to claim 19, further comprising: a PBX connected to at least one telephone line; and, wherein said paging controller further comprises at least one input and output connectable to said PBX, is connected to said PBX via said at least one input and output, and is operable to present audio content from said audio content memory over said telephone line in response to input from said telephone line.

21. The system according to claim 20, wherein said paging control logic selectively controls the use of said plurality of paging devices based upon said operating system, said paging protocol, the state of said phone line and inputs from said phone line.

22. The system according to claim 20, wherein at least one of said plurality of paging devices is an overhead pager or a local area pager, said PBX allows a call to be parked, and said paging control logic is responsive to said operating system and said paging protocols for selectively initiating a age on said at least one overhead pager or local area pager in response to a call being successfully parked.

23. The system according to claim 20, wherein said paging controller further includes: a coder-decoder associated with each of said at least one input and output, for translating analog signals into digital signals and digital signals into analog signals, whereby audio content may be received into said audio content memory from said telephone line or read from said audio content memory and sent to said telephone line.

24. The system according to claim 23, wherein said audio content is retrieved from said audio content memory using said operating system and based upon the state of said phone line and inputs from said phone line.

25. The system according to claim 20, wherein at least one of said paging devices is an overhead paging device and is connected to said PBX.

26. The system according to claim 25, wherein said paging control logic is responsive to said operating system and said paging protocols for sending said audio content to said overhead paging device via said PBX.

27. The system according to claim 20, wherein at least one of said paging devices is a local area paging device.

28. The system according to claim 27, wherein said paging protocols include at least one script of an alphanumeric page.

29. The system according to claim 28, wherein said paging control logic is responsive to said operating system and said paging protocols for sending an alphanumeric page to said local area paging device.

30. The system according to claim 20, wherein at least one of said paging devices is a wide area paging device.

31. The system according to claim 30, wherein said paging control logic is responsive to said operating system for sending a numeric page to said wide area paging device.

32. The system according to claim 20, wherein said PBX further includes: means for identification of the phone number being called.

33. The system according to claim 32, wherein said paging control logic is responsive to said operating system, said paging protocols, and said called party identification for initiating a page.

34. The system according to claim 20, further comprising: a voicemail system or auto-attendant connected to said PBX.

35. The system according to claim 34, wherein said paging control logic is responsive to said operating system and said paging protocols for transferring a phone call to said voicemail system or auto-attendant.

36. The system according to claim 19, further comprising: a detector for signaling the presence of a person or occurrence of an event with a detection signal, said paging controller being responsive to said detection signal to initiate at least one page.