JP2002209239A - Caller number callback device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a caller number callback device that can automatically bill a speech charge on a company when a user possessing a mobile phone makes a call on a mobile phone for company business. SOLUTION: A private branch of exchange 1 detects a caller number from a call arrived in a callback trunk line by utilizing a caller number notice function of a public phone network and transfers the caller number to the caller number callback device 2, which automatically calls back the caller number.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an improvement in the function of a private branch exchange connected to a public communication network having a caller ID display function.

[0002]

2. Description of the Related Art Conventionally, a caller number is only displayed on a called telephone having a caller number display function when a call is received. Therefore, when a company calls a company from a personal or mobile telephone or fixed telephone, the individual who owns the telephone pays the fee.

[0003]

However, in the above-mentioned conventional method, the problem of the charge can be solved by holding a company-owned mobile phone in the case of a mobile phone, but there are two types, one for personal use and one for company use. I had to have a mobile phone.
In addition, when a personally owned mobile phone or fixed telephone was used, the individual had to pay a fee.

[0004] The use of collect calls can solve the problem of charges, but has the drawback that a fixed service charge is imposed on one call.

There is also a service called toll free,
In addition to the call charge, there is a drawback that a monthly usage charge is required for each line, and furthermore, there is a drawback that anyone can use it and cannot limit the users.

It is an object of the present invention to construct a system in which a registered person is always charged to the company even if a personal telephone is used irrespective of a portable telephone or a fixed telephone. .

[0007]

In order to solve the above-mentioned problem, the invention according to claim 1 is a caller ID callback apparatus added to a private branch exchange having a caller ID detection function, When the private branch exchange detects a caller number for a call arriving on the office line set up for callback, the caller is called back through the private branch exchange after the caller goes on-hook. It is characterized by.

According to the present invention, the caller (callback requester) can be automatically called back without answering the private branch exchange by detecting the caller number of the call arriving at the callback office line. .

According to a second aspect of the present invention, there is provided a caller ID callback apparatus according to the first aspect, wherein the caller ID detected by the private branch exchange is replaced with a caller ID registered in a database. It is characterized in that it is configured to collate and call back the caller number only when there is a match.

According to the present invention, a caller (callback requester) registered without responding at the private branch exchange is detected by detecting the caller number of a call arriving at the callback office line and checking the registered data with the registered data. ) Can only be called back.

According to a third aspect of the present invention, there is provided a caller ID callback apparatus according to the first and second aspects of the present invention, in which a call is made to an office line provided for a callback to request a callback. After the calling party, that is, the callback requester answers the callback call, the dialing signal input by the callback requester is analyzed in accordance with the voice guidance reproduced and transmitted through the private branch exchange to identify the service type, It is characterized by providing a service specified by the callback requester.

According to the present invention, it is possible to provide a service specified by a called party (callback requester) after making a caller callback for a call arriving at a callback office line.

According to a fourth aspect of the present invention, there is provided a caller ID callback apparatus according to the third aspect, wherein the callback requester inputs a dial signal in accordance with voice guidance reproduced and transmitted through the private branch exchange. Is analyzed to identify a transfer connection and a transfer destination number, and connect the callback requester to a designated transfer destination.

According to the present invention, the callback requester is
It is possible to connect to an arbitrary transfer destination by operation of the callback requester without human intervention.

According to a fifth aspect of the present invention, in the caller number callback device according to the fourth aspect, a class for defining a transfer range is provided for each caller number stored in the database. It is characterized by the following.

According to the present invention, the transfer destination can be restricted by the class given to the callback requester.

According to a sixth aspect of the present invention, there is provided a caller ID callback apparatus according to the first to fifth aspects, wherein the call charge required for the callback call and the transfer call is transmitted to the callback requester. It is characterized in that it is configured to charge within the private branch exchange.

According to the present invention, the call charge required for the callback call and the transfer call can be charged to the callback requester in the private branch exchange.

According to a seventh aspect of the present invention, in the caller number callback device according to the sixth aspect, a call charge limit is set for each caller number stored in the database, and a call-back request is made. When the call charge used by the user exceeds the limit, the transfer is not performed.

According to the present invention, the transfer call can be restricted by the amount of the call charge spent on the callback call and the transfer call.

The caller ID callback apparatus according to claim 8 of the present invention, in the invention according to claim 3, wherein the call-back requester reproduces and transmits through the private branch exchange after answering the callback call. The dial-up signal input by the callback requester is analyzed in accordance with the voice guidance to identify the wake-up service request, the wake-up service guidance is reproduced and transmitted, and the wake-up date and time dialed by the callback requester are identified accordingly. The callback requester is called back at a designated date and time.

According to the present invention, a callback call specifying a date and time can be used for a wake-up service.

According to a ninth aspect of the present invention, in the caller ID callback apparatus according to the third aspect, after the callback requester responds to the callback call, it is reproduced and transmitted through the private branch exchange. Analyzing the dial signal input by the callback requester in accordance with the voice guidance, identifying the message recording service request, reproducing and transmitting the recording service guidance, recording the voice of the callback requester, A callback destination number and a callback date and time to be dialed by the callback requester are identified, the callback destination number is called at a designated date and time, and a message is transferred.

According to the present invention, a callback requester can record a message and transfer the message to a designated destination at a designated date and time.

According to a tenth aspect of the present invention, there is provided a caller ID callback apparatus according to the third aspect, wherein after the callback requester answers the callback call,
According to the voice guidance reproduced and transmitted through the private branch exchange, the dial signal input by the callback requester is analyzed to identify that the request is an information retrieval service request, and to identify the information box number dialed by the callback requester. Then, the information stored in the information box of the message database is reproduced and transmitted to the callback requester.

According to the present invention, the information in the information box can be extracted by the callback requester designating the information box number.

The caller ID callback device according to claim 11 of the present invention is the caller ID callback device according to claim 10,
In the information retrieval service, when the information stored in the information box of the message database is reproduced and transmitted to the callback requestor, when the callback requester identifies the information as a facsimile signal, It is characterized in that the call request number of the output destination of the facsimile signal is input to the callback requester by a dial signal, and information is taken out from the designated facsimile apparatus.

According to the present invention, when the information in the information box specified by the callback requester is a facsimile signal, the information can be output by specifying the facsimile apparatus.

According to a twelfth aspect of the present invention, in the caller ID callback apparatus according to the first to eleventh aspects, a history of incoming and outgoing calls related to the callback is stored in a database. It is characterized by having comprised so that it may perform.

According to the present invention, the history of outgoing / incoming calls related to the caller ID callback can be recorded.

According to a thirteenth aspect of the present invention, in the caller ID callback device according to the first to twelfth aspects, the date and time zone for providing the caller ID callback service are arbitrarily set. It is characterized in that it can be configured.

According to the present invention, it is possible to set so that the day and time zone for providing the caller ID callback service can be automatically switched.

According to a fourteenth aspect of the present invention, there is provided a caller ID callback apparatus according to the first to thirteenth aspects, wherein various settings relating to the caller ID callback can be performed via the Internet. It is characterized by comprising.

According to the present invention, various settings of the caller ID callback device can be performed from the personal computer via the Internet.

According to a fifteenth aspect of the present invention, in the caller ID callback apparatus according to the seventh to eleventh aspects, when the callback is performed by designating the callback time, The present invention is characterized in that a voice guidance is provided to a called party when a call-back reservation has been made at the time of an incoming call.

According to the present invention, when the called party answers the callback call, it is possible to know when the call is reserved for the callback, so that the understanding of the call is quickened.

[0037]

FIG. 1 is a block diagram of a system according to an embodiment of the present invention. In FIG. 1, reference numeral 1 denotes a private branch exchange PBX, which is connected to a telephone network 3 which is a public communication network and the Internet 4. Here, for the incoming call from the telephone network 3, the private branch exchange PBX1 responds to the telephone exchange by the general office line and the call back office line having the caller ID detecting function according to the present invention. Are provided.

The telephone network 3 has a caller number display function, and the private branch exchange PBX1 detects a caller number for an incoming call at least for a callback line.

2 is a caller ID callback device CBM
Then, the callback control according to the present invention is performed.

The telephone network 3 and the Internet 4 are connected by a gateway GW 5 and can enter each other.

The telephone network 3 is connected to a facsimile FAX 6 and a subscriber telephone set SUB7. The telephone network 3 is connected to a mobile station MS9 wirelessly via a mobile telephone base station BS8.

The Internet 4 is connected to an Internet protocol subscriber telephone set IP-SUB10 and a personal computer PC11.

The private branch exchange PBX1 includes a private mobile telephone base station BS108, a personal station PS12 wirelessly connected to the base station, and an extension telephone EX.
T13 is connected.

Reference numeral 14 denotes a router R, which connects the Internet 4 to the local area network LAN 16,
The world wide web WWW server 15 is connected to the local area network LAN16.

The private branch exchange PBX1 includes a switch SW101 for performing exchange connection, a central control unit CC102, and a storage unit M.
The switch SW101 includes a general office line trunk COT105, a callback office line trunk COT106, an Internet protocol trunk IPT107, a private mobile phone base station BS108,
Talky trunk TOK109, line circuit LIN110 for extension telephones, line circuit LIN for callback device
111 are connected.

Here, a general office line trunk COT 105
Number from the telephone network 3 and the callback line C
The subscriber number for calling the OT 106 from the telephone network 3 is different, and the latter is open only to the owner of the telephone number registered in the database in the caller ID callback device.

The caller number callback device CBM2 is
Central processing unit CPU21, main memory MM22, database DB23, message database MSGDB24
And the line circuit LIN of the private branch exchange PBX1
Communication board COM for connection with 111
B25, a local area network interface LANIF 26 which is an interface with the local area network LAN16.

FIG. 2 shows an example of the type of the callback service according to the present invention. The type 1 simple callback means that the callback requester (caller) is transmitted from the mobile station MS9 which is a portable telephone, for example. When the callback line 106 of the private branch exchange PBX1 is called, the private branch exchange PBX1 detects the number of the originating mobile station MS9 without responding, and the callback requester calls back the originating mobile station MS9 after on-hook. To tell.

Types 2 to 4 are examples of services that can be set by a callback requester called by simple callback.

FIG. 3 shows a caller ID callback device CBM.
Reference numeral 2 denotes an example of a callback queue for performing callback, which is stored in the database DB23. Then, in the case of the type 1, the callback is performed immediately at the scheduled callback date and time in the case of the types 2 to 4.

FIG. 4 shows an example of the logging data indicating the history of the callback. The reception time for the callback request, the caller number (caller requester number), the call back date and time, the callback dial number, the call The back type, message box number, success or failure, number of retries, and the like are stored in the database DB23.

FIG. 5 shows an example of registration data of a caller number (callback requester number) permitted to be called back. Caller numbers not registered here are rejected for callback. This registration data includes the class indicating the transfer connection range for each caller ID, the password, the balance of the fee permitted to be used, and the billing data of the used city charge, toll charge, and international charge. Registration data is also stored in the database DB23.

FIG. 6 shows an example of class data for limiting a transfer destination when a callback requester requests a call transfer after a simple callback. The necessity of a password for confirming the registered person is determined. In FIG. 6, the connection to the Internet telephone is treated as a connection to an extension.

FIG. 7 shows the message database MSGDB.
As an example of the contents of 24, some messages are determined as a system, and some messages can be registered by a user of a caller ID callback device, and these are managed by a box BOX number.

FIGS. 8 to 12 are flowcharts of the main operation of the system.

Next, the outline of the operation will be described. Consider a case where an employee with a personally owned mobile phone wants to register a wake-up service from a remote location, or wants to call the extension telephone EXT13 of the private branch exchange PBX1. Employees have their own mobile phones, but would like to make calls in a way that would be charged to the company, as calling by the traditional method would charge their phone.

Referring to FIG. 8, the processing when a call arrives at the private branch exchange PBX1 will be described.

An employee holding his own mobile station MS9 dials the number of the callback office line of the private branch exchange PBX1. Mobile station MS
9 is connected to the central office trunk COT 106 through the mobile telephone base station BS8 and the telephone network 3 (step S101).
At this time, the telephone network 3 sends the number of the originating mobile station MS9 to the central office trunk COT.

The caller number sent to the central office trunk COT 106 is stored in the central control unit CC of the private branch exchange PBX1.
102 (step S102), the central processing unit CP passes through the local area network interface LANIF 104, the local area network LAN 16, and the local area network interface LANIF 26 in the caller ID callback device CBM2.
It is sent to U21 and collated with the registration data of FIG. 5 stored in the database DB23 (step S103).
If there is a caller number in the registration data, it is determined that connection is possible (step S104).

If the caller number is not included in the registration data, it is determined that connection is not possible, and the central processing unit CPU 21 sends an instruction to the central control unit CC 102 via the local area network LAN 16 to perform a response process (step). S110). Then, the receiving station line trunk COT 106 is connected to the talkie trunk TOK 109 (step S1).
11) After sending out the service unavailable guidance (step S112), disconnect the service (step S11).
3), end the process.

When the connection is permitted, a response to the effect that the callback has been accepted can be returned to the caller. However, since the purpose is to prevent the caller from being charged, the caller is not responded, and the caller is not responded. Wait for cutting (step S
105). If the caller does not disconnect but times out (step S106), if the telephone network 3 is the integrated services digital network ISDN, the private branch exchange PBX1 is forcibly disconnected (step S107).

The central processing unit CPU 21 transfers the callback information to a queue in the database DB 23,
It accumulates like O1 (step S108).

Then, the incoming line is released (step S1).
09) End the process.

Next, in the callback process shown in FIG. 9, the central processing unit CPU21 of the caller number callback device CBM2 reads out, for example, a NO1 callback dial from the queue (FIG. 3) of the database DB23 (step S201). ), Capture the empty communication board COMB25, activate the private branch exchange PBX1, and send out a callback dial. by this,
A call-back connection is made to the mobile station MS9 that has requested a callback via the route of the communication board COMB25, the line circuit LIN111, the central office trunk COT106, the telephone network 3, the base station BS8, and the mobile station MS9 (step S).
202).

When the call-back requester responds with the mobile station MS9 (step S203), the central processing unit CPU21 sets the communication board COMB2.
According to the response display from No. 5, a callback log is accumulated in the database DB 23, for example, as NO1 in FIG. 4 (step S204).

The central processing unit CPU 21 determines whether the type is 1 or other than 1 from the data in the queue (step S).
205).

When the type is 1, the message database MSG is sent from the communication board COMB25.
A message stored in the DB 24, for example, “XXX
Callback from X. Wake up service is '1 #'
, Message registration '2 #', transfer service '3 #'
Dial "#" and "4 #" to retrieve information. "(Step S206). The process then proceeds to the service registration operation shown in FIG.

If the callback other than the simple callback, that is, if the type is other than 1 in step S205, the callback requester responds and a message corresponding to the service from the caller number callback device CBM2, for example, , A message saying “Good morning. Wake up service.” Is sent out (step S2).
07).

When the transmission of the message is completed, disconnection of the called party (callback requester) is monitored (step S208),
Upon disconnection, the corresponding part of the callback queue of FIG. 3 in the database DB23 is cleared (step S211).
Finish the process.

If the called party does not disconnect at step S208, a timeout is monitored (step S20).
9) If a timeout occurs, forced disconnection is performed (step S)
210). As a result, the callback queue is cleared (step S211), and the process ends.

If the called party does not answer in step S203, the central processing unit CPU 21
The log data as shown in FIG. 4 is stored in step 3 (step S212), and a short retry is performed (step S213). Then, 1 is added to the number of retries so far (the number in FIG. 4) (step S214), and it is determined whether or not the retry is successful (step S215).

If the retry succeeds, the process proceeds to step S205. If the retry is not successful, a limit is set on the number of retries, and it is determined whether the number of retries has exceeded the limit (step S216). If not, the process returns to step S213 to continue the retry. If the number of retries exceeds the limit, the central processing unit C
The PU 21 clears the corresponding item from the queue in FIG. 3 (Step S217), and ends the processing.

The service registration process will be described with reference to FIG. In step S206 of the callback process of FIG. 9, guidance for service selection is played, so that the called party (callback requester) dials the desired service number, and the communication board COMB25 receives this (step S301).

The central processing unit CPU 21 analyzes the received dial number and determines whether or not it is a wake-up registration (in the present embodiment, whether or not the dial is “1 #”) (step S302). Central processing unit CPU for wakeup registration
21 wakes up the service guidance from the message database MSGDB 24 and sends it out as a voice from the communication board COMB 25 to the called party (callback requester) (step S303). The guidance is, for example, "Please enter the date and time to wake up and call by dial."

The called party (callback requester) inputs a desired date and time for the wake-up service by using a push-button dial (step S304). The communication board COMB25 converts the dialed date and time into voice by voice synthesis and notifies the dialed called party (callback requester) (step S30).
5). The called party (callback requester) checks whether the date and time are set correctly (step S30).
6) If incorrect, return to step S304 and re-enter the date and time.

If the date and time are set correctly, the called party (callback requester) instructs whether to register the wake-up time (step S307). For example, dial "0 #" for registration and dial "9 #" for no registration.

In the case of registration, the type 1 simple callback in the callback queue of FIG. 3 is rewritten to the type 2 wake-up service (step S30).
8) After revising the scheduled callback date and time to the date and time, disconnect the connection (step S319) and end the process.

If not registered, the queue of the simple callback used for this callback is cleared (step S318), and the connection is disconnected (step S319).

In step S302, the dial is set to "1".
If it is not "#", it is determined whether it is a message recording request, that is, whether the dial is "2 #" (step S309). If the dial is a message recording request, the process proceeds to message recording in FIG. 11 described later.

If the message is not a message recording in step S309, it is determined whether the request is a transfer connection request (step S310). When the transfer request number “3 #” in the above example is dialed, the process proceeds to the transfer process of FIG. 12 described later.

If it is not a transfer connection request in step S310, it is determined whether it is an information fetch request (step S311). When the information retrieval number "4 #" in the above example is dialed, the called party (callback requester) wants to retrieve information from the information box BOX.
Dial number and caller ID callback device CBM
2 (step S312).

In the caller number callback device CBM2, the central processing unit CPU21 transmits the corresponding message box B from the message database MSGDB24.
Take out information from OX, communication board CO
The call is sent to the called party (callback requester) through the MB 25 (step S313).

The called party (callback requester) determines whether or not the information is to extract a facsimile facsimile signal (step S314). If the information is to extract a facsimile facsimile signal, the output facsimile apparatus, for example, FIG.
Enter and set the FAX 6 telephone number (step S
315).

The central processing unit CPU 21 has a database D
After the type of the simple callback queue and the callback dial of the callback call shown in FIG. 3 in B23 are rewritten (step S308), the connection is disconnected (step S319), and the process ends.

In step S314, facsimile F
If the AX signal has not been taken out, after the information is received, the queue for the callback call in FIG. 3 is cleared (step S318), the connection is cut off (step S319), and the process ends.

If the information is not taken out in step S311, the request does not conform to any service, so that the service number difference guidance is sent to the called party (callback requester) (step S316), and the service is restarted. It is inquired whether to register or stop the service registration (step S317). If the service is to be re-registered, the process returns to step S301 and waits for reception of a dial signal.

When the service registration is stopped in step S317, the activated callback queue is cleared (step S318), and the connection is disconnected (step S3).
19) The process ends.

Next, the message recording process will be described with reference to FIG. If it is determined in step S309 in FIG. 10 that the request is a message recording request, the process proceeds to message recording in FIG. 11, and the caller ID callback device CBM2 sends recording service guidance from the communication board COMB25 to the called party (callback request). (Step S401).

After recording the message from the called party (callback requester) (step S402), the caller ID callback apparatus CBM2 reproduces the recorded message for confirmation and calls the called party (callback requester). ) (Step S403), and inquires whether re-recording is necessary (step S404). If it is necessary to re-record the message, the process returns to step S402 to re-record the message.

If the recorded content is good, the called party (callback requester) is inquired about whether to register the message (step S405). If there is an answer to register (eg, '0 #' dial), the message is registered, and the called party (callback requester) sets the callback dial number and the callback date and time (step S406). Using this information,
The simple callback queue of FIG. 3 that activated the callback call is rewritten to the queue of the message delivery service with the callback type (step S407), the callback connection is disconnected (step S409), and the process ends.

If the called party (callback requester) selects not to be registered in step S405, the callback queue that activated the callback is cleared (step S408), and the connection is disconnected. (Step S409) The process ends.

The transfer process shown in FIG. 12 will be described. FIG.
If the transfer connection is requested in step S310 of FIG. 0, the process proceeds to the transfer process of FIG. 12, and the central processing unit CPU21 of the caller number callback device CBM2 reads the registration data shown in FIG. Fetch the class and remaining charge corresponding to the callback called party (caller number in the registration data) (step S
501).

It is determined whether or not a password is necessary based on the contents of the same registration data (step S502). If not, the process jumps to step S506. If necessary, the called party (callback requester) is requested to input a password (step S503).

Here, it is confirmed whether the transfer processing is continued or canceled to the called party (callback requester) (step S504). If the transfer processing is not canceled, the inputted password is compared with the registered data in FIG. It is determined whether the password is correct (step S505).

If the password is incorrect, the flow returns to the password input mode in step S503, and the password is re-entered.

If the password is correct, a dial tone is sent out from the communication board COMB25, and the called party (callback requester) inputs the dial number of the transfer destination (step S506). Central processing unit CPU
21 analyzes the input dial number and first determines whether the transfer is to an extension (step S50).
7). If the transfer is to an extension, the process proceeds to step S509.

If the call is not a transfer to an extension, that is, if it is a local line call, a local line outside call, or an international call, the called party (callback requester) captured in step S501.
Then, it is determined whether the transfer is permitted by comparing with the class (step S508). If it is permitted, the process proceeds to step S509.

There is also a restriction that transfer is permitted depending on the class described above, but is not permitted if there is no remaining telephone charge. In the present embodiment, the transfer is made to the extension even if there is no remaining charge.

In step S509, after confirming the transfer destination dial, connection is made from the communication board COMB25 to the transfer destination via the private branch exchange PBX1.

It is checked whether the connection to the transfer destination is successful (step S510). If the connection is successful, the central processing unit CPU21 sends the local area network interface LANIF26 and the local area network L
The AN 16 sends the transfer information to the central control unit CC102 of the private branch exchange PBX1 via the local area network interface LANIF104, and connects the called party (callback requester) to the transfer destination under the control of the central control unit CC (step S511).

The central processing unit CPU 21 has a central control unit C
Information about the success or failure of the transfer from the C102 via the local area network LAN 16 is obtained (step S51).
2) If it succeeds, the billing information of the private branch exchange PBX1, that is, the information that the call charge to the transfer destination and the call charge of the callback are both charged to the called party (callback requester) is transmitted via the local area network LAN16. Private branch exchange P
It is sent to the charging device of BX1 (step S513). The charging information of the charging device is set so as to be stored also in the corresponding charge column of the registration data of FIG.

As a result, the callback queue in which the callback connection has been made is cleared from the queue shown in FIG. 3 (step S514), and the process ends.

If the transfer has failed in step S512, it is determined whether or not a retry has been performed (step S515). If the retry has not been performed, the flow returns to step S511 to perform a retry.

If the retry is over in step S515, the transfer failure guidance is sent to the called party (callback requester) (step S516), and the callback queue performing the callback connection is placed in the queue shown in FIG. Is cleared (step S517), the connection with the called party (callback requester) is disconnected (step S518), and the process ends.

In the case of a call to an area where the transfer is restricted in step S508, or in the case where the call is not restricted but there is no remaining charge, a guidance that cannot be transferred is sent to the called party (callback requester) ( In step S519), an inquiry is made as to whether or not to change the transfer destination and redial (step S520).
Returning to step 6, if no redial is made, the process proceeds to step S517.

In a callback service other than the transfer connection, a callback reservation can be made by designating a date and time to be called back like a wake-up service. When such a callback call is answered, when the callback is answered, the guidance of "what day and at what time is the reserved callback" is played, so that the callback responder can identify the callback call when answering. Becomes easier.

In the above description, the callback called party (callback requester) inputs and sets the date and time to be called back, the subscriber number or extension number to be called back by dial operation, etc., according to the voice guidance. Was the case.

In FIG. 1, various settings and the like from a personal computer PC 11 connected to the Internet 4
It would be very convenient to be able to browse queues, logging data, and registered data on the database DB23.

In this embodiment, the personal computer PC11 sends the Internet 4, the router R1
4. Access the World Wide Web WWW server 15 through the local area network LAN 16 and access the local area network interface LANIF2.
6, the central processing unit CPU 21 can be controlled. Therefore, it is possible to control the caller ID callback device CBM2 from the arbitrary place on the Internet 4 by the personal computer PC11.

By storing a calendar with a time table in the database DB23 of the caller ID callback device CBM2, the date and time for performing the caller ID callback service can be limited. Central processing unit CPU21
Sets the local area network LAN1 at the start and end times of the caller ID callback service.
6, the central control unit CC10 of the private branch exchange PBX1
By notifying the start and end of the service to the caller 2, the caller number callback service time can be determined independently of the operation time of the private branch exchange PBX1.

[0111]

According to the present invention, a private branch exchange is called using a personally owned portable telephone, and the caller is automatically called back from a caller ID callback device attached to the private branch exchange. Can be charged to
This has the effect of eliminating the inconvenience of carrying two mobile phones, a company-owned mobile phone and a personally owned mobile phone.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram according to an embodiment of the present invention.

FIG. 2 is an example of a type of a caller number callback service.

FIG. 3 is an example of a callback queue.

FIG. 4 is an example of logging data in a callback connection.

FIG. 5 is an example of registration data of a telephone number that can receive a callback service.

FIG. 6 is an example of a service class in a transfer connection.

FIG. 7 is an example of a message database.

FIG. 8 is a flowchart of processing at the time of receiving a call-back request call.

FIG. 9 is a flowchart of a callback process.

FIG. 10 is a flowchart of service registration.

FIG. 11 is a flowchart of message recording.

FIG. 12 is a flowchart of a transfer process.

[Explanation of symbols]

 Reference Signs List 1 Private branch exchange PBX 2 Caller ID callback device CBM 3 Telephone network 4 Internet 5 Gateway GW 6 Facsimile FAX 7 Subscriber telephone SUB 8 Mobile telephone base station BS 9 Mobile telephone MS 10 Internet subscriber telephone IP-SUB 11 Personal computer PC 12 Premise mobile phone PS 13 Extension phone EXT 14 Router R 15 WWW server 16 Local area network LAN

Claims (15)

[Claims] 1. A caller ID callback device added to a private branch exchange having a caller number detection function, wherein the private branch exchange originates a call that arrives on a central office line provided for callback. A caller ID callback device configured to call back the caller ID through the private branch exchange after the caller goes on-hook when the caller ID is detected. 2. The system according to claim 1, wherein the caller ID detected by the private branch exchange is compared with a caller ID registered in a database, and the caller ID is called back only when the caller ID matches. The caller ID callback device according to claim 1. 3. A voice guidance which is reproduced and transmitted through the private branch exchange after a caller who requests a callback by calling an office line provided for a call back, that is, a call requester answers the callback call. 3. The system according to claim 1, wherein the dial signal input by the callback requester is analyzed in accordance with the following to identify a service type, and the service specified by the callback requester is provided. Caller ID callback device as described. 4. Analyzing a dial signal input by the callback requester according to voice guidance reproduced and transmitted through the private branch exchange, identifies a transfer connection and a transfer destination number, and identifies the callback requester. 4. The caller ID callback device according to claim 3, wherein a connection is made to a designated transfer destination. 5. The caller ID callback device according to claim 4, wherein a class for defining a transfer range is provided for each caller ID stored in said database. 6. The caller number according to claim 1, wherein a call charge required for the callback call and the transfer call is charged to the callback requester in the private branch exchange. Callback device. 7. A call charge limit is set for each caller number stored in the database, and if the call charge used by the callback requester exceeds the limit, no transfer is performed. The caller ID callback device according to claim 6, wherein: 8. After the callback requester answers the callback call, the call requester wakes up by analyzing a dial signal input by the callback requester in accordance with voice guidance reproduced and transmitted through the private branch exchange. And wake-up service guidance is reproduced and transmitted, and the wake-up date and time to be dialed by the callback requester are identified according to the wake-up service guidance, and the callback requester is called back at a designated date and time. The caller ID callback device according to claim 3, wherein 9. After the call-back requester answers the call-back call, the dial-up signal input by the call-back requester is analyzed in accordance with voice guidance reproduced and transmitted through the private branch exchange, and a message recording service request is made. Then, the recording service guidance is reproduced and transmitted, the voice of the callback requester is recorded, the callback destination number dialed by the callback requester and the callback date and time are identified, and the designated date and time are identified. 4. The caller number callback device according to claim 3, wherein the caller number is called and the message is transferred. 10. After the call-back requester answers the call-back call, the dial-up signal input by the call-back requester is analyzed in accordance with voice guidance reproduced and transmitted through the private branch exchange, and the information retrieval service request is sent. And identifying the information box number to be dialed by the callback requester, and reproducing and sending the information stored in the information box of the message database to the callback requestor. The caller ID callback device according to claim 3, wherein: 11. In the information retrieval service, when information stored in an information box of the message database is reproduced and transmitted to the callback requester,
If the callback requester has identified the information as a facsimile signal, the call requester of the output destination of the facsimile signal is input to the callback requester by a dial signal, and the information is transmitted from the designated facsimile apparatus. 11. The caller ID callback device according to claim 10, wherein the caller ID callback device is configured to extract the caller ID. 12. An incoming call, associated with said callback,
12. The caller ID callback device according to claim 1, wherein a history of calls is stored in a database. 13. The caller ID callback device according to claim 1, wherein the date and time zone for providing the caller ID callback service can be arbitrarily set. 14. The caller ID callback apparatus according to claim 2, wherein various settings relating to the caller ID callback can be performed via the Internet. 15. A method in which when a callback is performed by designating a callback time, a voice guidance is provided to a called party when a call is reserved when a call is received by the callback. The caller ID callback device according to claim 7, wherein