JP2008005543A - Private branch exchange with caller number callback function - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To automatically charge a company with a charge for a telephone call in the case of making a telephone call on company business with a portable telephone set owned by an individual. <P>SOLUTION: This private branch exchange with a caller number callback function is configured to receive dial in such a status that dial from a caller terminal is receivable according to the response of the caller terminal to callback to the caller terminal, and to perform exchange processing according to the received dial. In the case of transmitting guidance to make the caller terminal select a transfer service or an information extraction service to the caller terminal when a reception means is set in such a status that dial is receivable, the caller terminal is made to select the transfer service or the information extraction service from dial from the caller terminal, and then the service corresponding to the pertinent selection is provided. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a private branch exchange with a caller number callback function that improves the function of a private branch exchange connected to a public communication network having a caller number display function.

Conventionally, the caller number is only displayed on a called telephone having a caller number display function when a call is received. Therefore, when making a company call from a mobile phone or a fixed phone owned by an individual to a company, the individual who owns the phone paid a fee. Moreover, the technique of patent document 1 is known.
Japanese Patent Laid-Open No. 11-088504

  However, in the conventional system as described above, in the case of a mobile phone, the problem of the charge can be solved if the mobile phone owned by the company is held, but two mobile phones for personal use and the company must be provided. In addition, when a personally owned mobile phone or fixed phone is used, the individual has to pay a fee.

  In addition, if the collect call is used, the problem of the charge is solved, but there is a disadvantage that a fixed service charge is imposed for one call.

  There is a service called toll-free, but in addition to calling charges, there is a drawback that a monthly usage fee is charged for each line, and there is also a disadvantage that anyone can use it and cannot limit users.

  It is an object of the present invention to construct a system in which a charge is always charged to a company for a call of a registered person even when a personal telephone is used regardless of whether it is a cellular phone or a fixed telephone.

  In order to solve the above-described problems, the present invention acquires a caller number when an incoming call to a callback station line for performing a callback is detected, and the caller number matches a caller number registered in advance. If it is recognized that the caller number matches the caller number registered in advance by the number checker and the number checker for checking whether or not the call has been made, without responding to the incoming call to the station line On-hook detection means for waiting for the on-hook of the caller terminal, and when the on-hook detection means detects the on-hook of the caller terminal, the caller terminal sends out the caller number to the office line and makes a call back to the caller terminal. Callback means to perform and reception to receive a dial in a state of receiving a dial from the caller terminal according to a response of the caller terminal to the callback And a private branch exchange with a caller number callback function for performing a call back to a caller number having a switching process means for performing an exchange process in response to a dial received by the receiving means. A guidance sending means for sending a guidance for selecting a transfer service or an information retrieval service to the caller terminal when the caller terminal is in a possible state, and the exchange processing means is transferred by dialing from the caller terminal A service or an information retrieval service is selected, and a service corresponding to the selection is provided.

  According to the present invention, it is possible to automatically call back a caller (callback requester) without answering at the private branch exchange by detecting the caller number of the call that has arrived on the callback line.

  FIG. 1 is a configuration 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 and the Internet 4 which are public communication networks. Here, for incoming calls from the telephone network 3, two groups of different telephone numbers, a general office line to which the exchange responds at the private branch exchange PBX1 and a callback office line having a caller number detection function according to the present invention. Is provided.

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

  A caller ID callback device CBM 2 controls the callback according to the present invention.

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

  A facsimile FAX 6 and a subscriber telephone SUB7 are connected to the telephone network 3, and are connected wirelessly to a mobile station MS9 via a mobile phone base station BS8.

  An Internet protocol subscriber telephone IP-SUB 10 and a personal computer PC 11 are connected to the Internet 4.

  The private branch exchange PBX1 is connected with a private mobile phone base station BS108, a personal station PS12 wirelessly connected to the base station, and an extension telephone EXT13.

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

  The private branch exchange PBX1 includes a switch SW101 for performing exchange connection, a central control device CC102, a storage device MEM103, and a local area network interface LANIF104. The switch SW101 includes a general station trunk COT105, a callback stationline trunk COT106, an Internet protocol. A trunk IPT 107, a local mobile phone base station BS108, a talky trunk TOK109, an extension telephone line circuit LIN110, and a callback device line circuit LIN111 are connected.

  Here, a subscriber number for calling a general office line trunk COT 105 from the telephone network 3 and a subscriber number for calling the callback office line COT 106 from the telephone network 3 are separately provided. It is open only to the owner of the phone number registered in the database.

  The caller ID callback device CBM2 includes a central processing unit CPU21, a main memory MM22, a database DB23, a message database MSGDB24 control device, a communication board COMB25 for connecting the line circuit LIN111 of the private branch exchange PBX1, and a local area network LAN16. The local area network interface LANIF 26 is an interface.

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

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

  FIG. 3 shows an example of a callback queue for the caller ID callback device CBM2 to perform a callback, which is stored in the database DB23. Then, in the case of type 1, the callback is performed immediately in the case of type 2 or type 4, when the scheduled callback date / time is reached.

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

  FIG. 5 is an example of registration data of a caller number (callback requester number) that is allowed to be called back. Caller numbers not registered here are rejected from callback. This registration data includes the class that indicates the transfer connection range for each caller ID, the password, the balance of charges allowed for use, and the billing data for local charges, toll charges, and international charges used. Registration data is also stored in the database DB23.

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

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

  8 to 12 are flowcharts of main operations of the system.

  Next, an outline of the operation will be described. Consider a case where an employee with a personal mobile phone wants to register a wake-up service from a remote location, or to call the extension telephone EXT13 of the private branch exchange PBX1. Employees have their own mobile phone, but when they make a call using the conventional method, the charge is charged to their phone, so they want to make a call in a way that is charged to the company.

  The processing when an incoming call is made to the private branch exchange PBX1 will be described with reference to FIG.

  An employee having his own mobile station MS9 dials the number of the callback station line of the private branch exchange PBX1. The mobile station MS9 is connected to the local line trunk COT106 through the mobile phone 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 local trunk COT106.

  The caller number sent to the local trunk COT 106 is detected by the central controller CC102 of the private branch exchange PBX1 (step S102), and is stored in the local area network interface LANIF104, the local area network LAN16, and the caller number call back device CBM2. The data is sent to the central processing unit CPU 21 through the local area network interface LANIF 26 and collated with the registration data of FIG. 5 stored in the database DB 23 (step S103). If there is a caller ID in the registered data, it is determined that connection is possible (step S104).

  If the caller ID 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 CC102 via the local area network LAN 16 to perform response processing (step S110). Then, the incoming line trunk COT 106 is connected to the talkie trunk TOK 109 (step S111), a guidance that cannot be serviced is transmitted (step S112), and the call is disconnected (step S113), and the process is terminated.

  Even if the connection is possible, the caller can receive a response indicating that the callback has been accepted, but here the purpose is to prevent the caller from being charged, so the caller disconnects and the caller disconnects. (Step S105). If the caller does not disconnect and the timeout occurs (step S106), if the telephone network 3 is the integrated service digital network ISDN, the private branch exchange PBX1 forcibly disconnects (step S107).

  The central processing unit CPU 21 stores the callback information in the queue in the database DB 23 as shown in NO1 in FIG. 3 (step S108).

  Then, the incoming line is released (step S109), and the process ends.

  Next, in the callback processing shown in FIG. 9, the central processing unit CPU21 of the caller ID callback device CBM2 reads, for example, the NO1 callback dial from the queue of the database DB23 (FIG. 3) (step S201), and is free. The communication board COMB25 is captured, the private branch exchange PBX1 is activated, and a callback dial is transmitted. As a result, the callback connection is established to the mobile station MS9 that requested the callback through the route of the communication board COMB25-line circuit LIN111-station line trunk COT106-telephone network 3-base station BS8-mobile station MS9 (step S202).

  When the callback requester responds at the mobile station MS9 (step S203), the central processing unit CPU21 accumulates the callback log in the database DB23 by the response display from the communication board COMB25, for example, as NO1 in FIG. 4 (step S204). ).

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

  When the type is 1, the message stored in the message database MSGDB 24 from the communication board COMB 25, for example, “Callback from XXX. Wake up service for '1 #' and message registration for '2 #'. Call back guidance “3 #” for service and “4 #” for information retrieval ”(step S206). Then, the process proceeds to the service registration operation shown in FIG.

  If the callback is not a 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 ID callback device CBM2, for example, “Good morning” There is a wake-up service "message is sent (step S207).

  When the message has been sent, the disconnection of the called party (callback requester) is monitored (step S208). If the message is disconnected, the corresponding part of the callback queue in FIG. 3 in the database DB23 is cleared (step S211). End.

  If the called party does not disconnect in step S208, the time-out is monitored (step S209), and if the time-out occurs, the forced disconnection is performed (step S210). 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 CPU21 accumulates logging data as shown in FIG. 4 in the database DB23 (step S212), and retries after a short time (step S213). Then, 1 is added to the number of retries so far (number of times shown in FIG. 4) (step S214), and it is determined whether the retry is successful (step S215).

  If the retry is successful, 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 exceeds the limit (step S216). If not, the process returns to step S213 to continue the retry. When the number of retries exceeds the limit value, the central processing unit CPU 21 clears the corresponding item from the queue of FIG. 3 (step S217), and ends the process.

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

  The central processing unit CPU 21 analyzes the received dial number and determines whether it is a wake-up registration (in this embodiment, whether the dial is “1 #”) (step S302). If it is a wake-up registration, the central processing unit CPU 21 extracts the wake-up service guidance from the message database MSGDB 24 and sends it as a voice from the communication board COMB 25 to the called party (call-back requester) (step S303). The guidance is, for example, “Please enter the date and time when you want to wake up.”

  The called party (call-back requester) wakes up by the push button dial and inputs the desired date and time (step S304). The communication board COMB 25 converts the dialed date and time into voice by voice synthesis, and asks the called party (call back requester) to dial (step S305). The called party (callback requester) checks whether the date and time have been set correctly (step S306), and if wrong, returns to step S304 to input the date and time again.

  If the date and time are set correctly, the called party (callback requester) instructs whether or not to register the wake-up time (step S307). For example, “0 #” is dialed when registering, and “9 #” is dialed when not registering.

  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 S308), the callback scheduled date and time are rewritten to the date and time, and then the connection is made. Disconnect (step S319) and the process ends.

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

  If it is determined in step S302 that the dial is not “1 #”, it is determined whether the message recording is requested, that is, whether the dial is “2 #” (step S309). If dialing is a message recording request, the process proceeds to message recording shown in FIG.

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

  If it is not a transfer connection request in step S310, it is determined whether it is an information retrieval request (step S311). When the information retrieval number “4 #” in the above example is dialed, the called party (callback requester) dials the information box BOX number from which information is to be retrieved and inputs it to the caller number callback device CBM2. (Step S312).

  In the caller number callback device CBM2, the central processing unit CPU21 extracts information from the corresponding message box BOX from the message database MSGDB24 and sends it to the called party (callback requester) through the communication board COMB25 (step S313).

  The called party (call-back requester) determines whether or not the information is a facsimile FAX signal extraction (step S314). If the information is a facsimile FAX signal extraction, the output facsimile apparatus, for example, the FAX 6 in FIG. A telephone number is input and set (step S315).

  The central processing unit CPU 21 rewrites the simple callback queue type and callback dial of the callback call shown in FIG. 3 in the database DB 23 (step S308), disconnects the connection (step S319), and ends. It becomes.

  If the facsimile FAX signal is not taken out in step S314, after receiving the information, the callback call queue shown in FIG. 3 is cleared (step S318), the connection is disconnected (step S319), and the process ends.

  If the information is not retrieved in step S311, the request does not match any service, so a service number difference guidance is sent to the called party (callback requester) (step S316), and the service is re-registered. An inquiry is made as to whether to stop service registration (step S317). When re-registering the service, the process returns to step S301 and waits for reception of a dial signal.

  When stopping the service registration in step S317, the activated callback queue is cleared (step S318), the connection is disconnected (step S319), and the process is terminated.

  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 receives the recording service guidance from the communication board COMB25. (Step S401).

  The caller ID callback device CBM2 records the message from the called party (callback requester) (step S402), and then plays the recorded message for confirmation to let the called party (callback requester) hear it. (Step S403), an inquiry is made as to whether or not re-recording is necessary (Step S404). If it is necessary to re-record, the process returns to step S402 to record the message again.

  If the recorded content is good, it asks the called party (callback requester) whether or not to register the message (step S405). If there is an answer to register (for example, “0 #” dial), a message is registered and a callback dial number and a callback date and time are set from the called party (callback requester) (step S406). Using this information, the simple callback queue of FIG. 3 that initiated the callback call is rewritten to a queue for which the callback type is the message delivery service (step S407), and the callback connection is disconnected (step S409). ) End the process.

  If the called party (callback requester) selects not to register in step S405, the callback queue that activated the callback is cleared (step S408), and then the connection is disconnected (step S409). ) End the process.

  The transfer process in FIG. 12 will be described. When the transfer connection is requested in step S310 in FIG. 10, the process proceeds to the transfer process in FIG. 12, and the central processing unit CPU21 of the caller ID callback device CBM2 stores the registration data shown in FIG. The class corresponding to the callback called party (caller number in the registration data) and the remaining charge are taken in (step S501).

  Whether or not a password is necessary is determined from 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, the called party (callback requester) confirms whether to continue or cancel the transfer process (step S504). If not cancelled, the entered password is checked against the registration data shown in FIG. Whether or not (step S505).

  If the password is incorrect, the process returns to the password input mode in step S503, and the password is input again.

  If the password is correct, a dial tone is transmitted from the communication board COMB 25, and the called party (call-back requester) is allowed to input the transfer destination dial number (step S506). The central processing unit CPU 21 analyzes the input dial number and first determines whether the transfer is to an extension (step S507). If the transfer is to an extension, the process proceeds to step S509.

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

  There is a restriction that the transfer is permitted depending on the above-mentioned class but not permitted when there is no remaining telephone charge. In the present embodiment, even if there is no remaining charge, it is transferred to the extension.

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

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

  The central processing unit CPU 21 obtains information on the success or failure of the transfer via the local area network LAN 16 from the central control unit CC102 (step S512). If it is successful, the accounting information of the private branch exchange PBX1, that is, the call charge to the transfer destination and the call Information that the back call charge is billed to the called party (callback requester) is sent to the billing apparatus of the private branch exchange PBX1 via the local area network LAN 16 (step S513). The billing information of the billing device is set so as to be stored in the corresponding charge column of the registration data in FIG.

  As a result, the callback queue that has made the callback connection is cleared from the queue of FIG. 3 (step S514), and the process is terminated.

  If the transfer fails in step S512, it is determined whether or not the retry is over (step S515). If the retry is not over, the process returns to step S511 to perform the retry.

  If retry over occurs in step S515, a transfer failure guidance is sent to the called party (callback requester) (step S516), and the callback queue that made the callback connection is cleared from the queue of FIG. (Step S517), the connection with the called party (call-back requester) is disconnected (Step S518), and the process is terminated.

  In the case of a call to the area where transfer is restricted in step S508, and when there is no remaining charge even though it is not restricted, guidance that cannot be transferred is sent to the called party (callback requester) (step S519). Then, an inquiry is made as to whether or not to redial by changing the transfer destination (step S520). If redialing is performed, the process returns to step S506, and if not redialing, the process proceeds to step S517.

  In callback services other than transfer connection, callback reservation can be made by specifying the date and time of callback as in the case of a wake-up service. When responding to such a callback call, the callback responder can identify the callback call at the time of answering by giving the guidance “What time of day is reserved callback” when answering the callback. Becomes easier.

  The above explanation is for the case where the callback called party (calling back requester) inputs and sets all of the callback date and time, the subscriber number or extension number to be called back by dialing in accordance with the voice guidance. It was.

  In FIG. 1, it is very convenient if various settings, queues on the database DB 23, logging data, and registered data can be viewed from the personal computer PC 11 connected to the Internet 4.

  In the present embodiment, the personal computer PC11 can access the World Wide Web WWW server 15 through the Internet 4, the router R14, and the local area network LAN16, and can control the central processing unit CPU21 through the local area network interface LANIF26. ing. 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 timetable 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. The central processing unit CPU21 informs the central control unit CC102 of the private branch exchange PBX1 of the start and end of the service via the local area network LAN 16 at the time of starting and ending the caller ID callback service. The caller ID callback service time can be determined independently of the operation time of the PBX 1.

  As described above, the present invention calls a private branch exchange using a personally-owned mobile phone and automatically calls back from a caller ID callback device attached to the private branch exchange. Since it can be charged and the inconvenience of carrying two mobile phones owned by the company and privately owned mobile phones can be eliminated, the function of the private branch exchange connected to the public communication network having a caller ID display function is improved. It is suitable for a private branch exchange with a caller number callback function.

It is a system configuration figure in an embodiment of the invention. It is an example of the classification of caller number callback service. It is an example of a callback queue. It is an example of the logging data in a callback connection. It is an example of the registration data of the telephone number which can receive a callback service. It is an example of the service class in a transfer connection. It is an example of a message database. It is a flowchart of the process at the time of arrival of a callback request call. It is a flowchart of a callback process. It is a flowchart of service registration. It is a flowchart of message recording. It is a flowchart of a transfer process.

Explanation of symbols

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 phone base station BS
9 Mobile phone MS
10 Internet subscriber phone IP-SUB
11 Personal computer PC
12 On-site mobile phone PS
13 Extension telephone EXT
14 Router R
15 WWW server 16 Local area network LAN

Claims (1)

A number verification means for acquiring a caller number when detecting an incoming call to a callback station line for performing a callback, and checking whether the caller number matches a caller number registered in advance; An on-hook detection unit that waits for an on-hook of the caller terminal without responding to an incoming call to the local line, when the caller number is recognized by the number matching unit to match a caller number registered in advance; When the on-hook detection means detects the on-hook of the caller terminal, the call-out means for sending the caller number to the office line and making a call back to the caller terminal; And receiving means for receiving the dial in a state of receiving the dial from the caller terminal according to the response of the sender terminal, and received by the receiver means In Caller ID callback function PBX to perform a callback to the caller number and a replacement processing unit configured to perform exchange processing according to dial,
A guidance sending means for sending a guidance for selecting a transfer service or an information retrieval service for the caller terminal when the receiving means is in a dial-receivable state;
The exchange processing means selects a transfer service or an information retrieval service by dialing from the caller terminal, and then provides a service according to the selection. .

Images