JP6224927B2 - Incoming call management apparatus and incoming call management system - Google Patents

Description

  The present invention relates to a technique for managing incoming calls to a plurality of telephones.

  For example, Patent Document 1 discloses a technique for automatically rejecting an incoming call when a nuisance call such as a prank call, a persistent call for advice or a one-way call is made. Patent Document 1 accumulates incoming call history information including a caller's telephone number and call time at the time of incoming call to a telephone, and incoming call history information corresponding to a call time condition of N times or more and M seconds or less per unit time. The telephone number of the caller is extracted from the caller, and thereafter, the incoming call from the caller is rejected.

JP 2012-70246 A

According to the invention disclosed in Patent Document 1, by sharing a telephone number of a caller that rejects an incoming call within a telephone system that accommodates a plurality of telephones, incoming calls from this caller are uniformly received by all the telephones. Can be refused.
However, inconvenience may occur due to the uniform determination of whether or not incoming calls can be made to all telephones. For example, for certain telephones, we would like to reject incoming calls for unwanted calls so as not to disturb the user. There are cases where it is desirable to intentionally receive an incoming call even if it is a nuisance call for the purpose of collecting information. If the sender's phone number is not notified, you can reject the incoming call, but it is customary to make a call with the sender number hidden, or if the sender number is mistakenly hidden The incoming call from the caller who made the call as a notification is rejected in the same way as the nuisance call. Exceptionally, there is a method of registering the telephone number of the sender that permits or rejects incoming calls. However, if the number of telephone numbers that should be registered becomes enormous, the human burden of registration is excessive. May be.
As described above, if it is determined whether or not an incoming call can be made based only on the caller's phone number and whether or not the phone number is notified, some inconvenience is likely to occur for the caller or the user of the caller.
Therefore, an object of the present invention is to perform control related to incoming calls in accordance with the relationship between a caller and a callee.

In order to solve the above-described problems, an incoming call management device according to the present invention is an incoming call management device that manages incoming calls to a plurality of telephones from an external telephone network. A storage unit storing a list designating incoming call processing including whether or not incoming calls can be received, and any one of the plurality of telephones from the external telephone network When an incoming call addressed to the destination is accepted, a source information acquisition unit that acquires source information of a source of the incoming call, a destination information acquisition unit that acquires destination information about the one telephone, and A specifying unit for specifying the incoming call processing specified for the set of the caller information acquired by the caller information acquisition unit and the callee information acquired by the callee information acquisition unit based on the list; The specified by the specifying unit A reception control unit for controlling the signal processing performed as to the incoming call, after the connection during or connection between the source and said one of the telephone in accordance with the incoming call, call blocking operation performed in the phone An incoming call rejection operation detecting unit for detecting an incoming call, and when the incoming call rejection operation is detected, an incoming call to the telephone by a caller source number that is a caller telephone number of an incoming call addressed to the one telephone is rejected A registration processing unit for registering the incoming call processing specified in the list in the list .

In the incoming call management device of the present invention, the device itself may be a device different from the private branch exchange that performs control for establishing a communication path of the plurality of telephones and the external telephone network .

In call management device of the present invention, the source information comprises a source ID wherein a calling telephone number, the destination information, see contains the destination number is a telephone number of the destination, the The incoming call rejection operation detection unit detects an operation by an operation key assigned with a DTMF (Dual Tone Multi Frequency) signal performed in the one telephone as the incoming call rejection operation, and the registration processing unit receives the incoming call. The outgoing call stored in the storage unit for storing the outgoing call source number, the incoming call destination number, and the incoming call date and time when the incoming call rejection operation is detected after the connection between the corresponding caller and the one telephone is completed Among the original numbers, the telephone number of the telephone in which the incoming call rejection operation is detected is the incoming call destination number, and the incoming call to the telephone with the caller number having the latest incoming date and time is rejected. Boss was an incoming process, it may be registered to the list.

An incoming call management system according to the present invention is an incoming call management system comprising an incoming call management device that manages incoming calls to each of a plurality of telephones from an external telephone network, and a server device that is communicably connected to the incoming call management device. The incoming call management apparatus stores a list in which an incoming call process including whether or not an incoming call can be received is specified for a set of caller information indicating a caller and callee information indicating a callee. And a source information acquisition unit for acquiring source information of a source of the incoming call when an incoming call addressed to any one of the plurality of telephones is accepted from the external telephone network; A destination information acquisition unit that acquires destination information regarding the one telephone, a source information acquired by the source information acquisition unit, and a destination information acquired by the destination information acquisition unit. Specified above The signal processing, a specifying unit for specifying, based on the list, a receiving controller for controlling the incoming call processing in which the identifying unit has identified as performed for the incoming call, the originator in accordance with the incoming call An incoming call rejection operation detecting unit for detecting an incoming call rejection operation performed on the telephone during or after connection to the one telephone, and an incoming call addressed to the one telephone when the incoming call rejection operation is detected A registration processing unit for registering, in the list, an incoming call process designated to reject an incoming call to the telephone set by a caller source number that is a call source telephone number, and an incoming call history indicating an incoming call history of the plurality of telephone sets a first collecting unit for collecting information, the reception history information in which information of said stored list and was collected in the storage unit, and a transmission processing unit for transmitting to the server device, the server device From the incoming management apparatus, the same showing said source information included in the second and collection unit, collected information of the list to collect information and the reception history information of the list that is transmitted by the transmission processing unit Based on the number of senders and the number of incoming histories from the same sender indicated by the incoming call history information , the sender number that is the telephone number of the sender to be registered in the list stored in the storage unit is specified. And a notification processing unit that notifies the specified caller source number to the incoming call management device.

In the incoming call management system according to the present invention, the incoming call management device and the server device are different from a private branch exchange that performs control for establishing a communication path of the plurality of telephones and the external telephone network. Also good.

  ADVANTAGE OF THE INVENTION According to this invention, control regarding an incoming call can be performed according to the relationship between a transmission origin and an incoming call destination.

1 is a diagram showing an overall configuration of an incoming call management system according to an embodiment of the present invention. The block diagram which shows the hardware constitutions of the incoming call management apparatus of the embodiment. The figure which shows the structural example of the telephone number list | wrist of the embodiment. The figure which shows the structural example of the group list | wrist of the embodiment. The figure which shows the structural example of the policy list | wrist of the embodiment. The figure which shows the structural example of the incoming call process list | wrist of the embodiment. The figure which shows the structural example of the sharing refusal number list | wrist of the embodiment. The block diagram which shows the hardware constitutions of the service server of the embodiment. The figure which shows the structural example of the exclusive database and shared database of the embodiment. 2 is an exemplary diagram showing a functional configuration of an incoming call management apparatus according to the embodiment. FIG. The sequence diagram which shows the flow of a process in the local telephone system of the embodiment. The sequence diagram which shows the flow of a process in the local telephone system of the embodiment. Explanatory drawing of the specific example of the incoming call process in the private telephone system of the embodiment. Explanatory drawing of the specific example of the incoming call process in the private telephone system of the embodiment. Explanatory drawing of the specific example of the incoming call process in the private telephone system of the embodiment. The sequence diagram which shows the registration process of the troublesome telephone number with the telephone of the embodiment. The flowchart which shows the procedure of the automatic registration of the troublesome telephone number of the embodiment.

Embodiments of the present invention will be described with reference to the drawings. Hereinafter, an example in which the incoming call management system of the present invention is applied to an incoming call management system 100 provided with a plurality of local telephone systems 1 for controlling external lines and internal lines will be described.
FIG. 1 is a diagram showing the overall configuration of the incoming call management system 100. As shown in FIG. 1, the incoming call management system 100 includes a plurality of local telephone systems 1 and a service server 50. The private telephone system 1 includes an incoming call management device 10, a relay device 20, a PBX (Private Branch eXchange) 30, and a plurality of telephones 40. The private telephone system 1 is connected to a telephone line TL that is an external telephone network. Here, the telephone line TL is an ISDN (Integrated Services Digital Network) line as a digital line network, and more specifically, an INS 1500 line or an INS 64 line. The incoming call management device 10 is a computer device such as an in-house server or a personal computer, and manages incoming calls to the telephone 40 in response to incoming calls coming from the telephone line TL. The incoming call management device 10 connects to a network NW exemplified by an Internet line and performs network communication.

  The relay device 20 is connected to each of the telephone line TL, the incoming call management device 10 and the PBX 30 and relays signal transmission via a speech path established between the telephone line TL and the telephone 40. The relay device 20 has a function of simultaneously establishing a multi-channel communication path. Further, the relay device 20 detects a caller number that is a telephone number of a caller of an incoming call by using a number display function or a caller number notification function. Further, the relay device 20 detects a destination number that is a destination telephone number based on the incoming call.

  Furthermore, the relay device 20 executes an incoming call process regarding whether or not an incoming call can be made to the destination specified by the incoming call. As this incoming call processing, when an incoming call addressed to one telephone 40 is accepted, the relay device 20 rejects the incoming call to that telephone and forwards the incoming call to another telephone, and announces to the caller There is a case where an announcement process for sending a voice or a busy process for making a busy state (busy state) may be executed. In the incoming call process, the relay device 20 may execute a recording process for recording a call voice based on a voice signal transmitted through a call path established between the telephone line TL and the telephone 40. When the recording process is executed, the relay apparatus 20 transmits a recording voice file of the call voice to the incoming call management apparatus 10.

  The PBX 30 is a private branch exchange, and is connected to each of the relay device 20 and the plurality of telephones 40. The PBX 30 establishes a communication path between the telephone line TL and the telephone 40, and control for connecting the telephones 40 with extensions. Control for. Further, when receiving an incoming call addressed to the telephone 40 from the telephone line TL, the PBX 30 accumulates history information indicating an incoming history for each incoming call. The history information includes, for example, information such as the presence / absence of a response of the telephone 40 to an incoming call, a transmission source number, a destination number, an incoming call reception date / time, and a length of time for which a communication path is established (that is, a call time). Including. The PBX 30 has a function of outputting the accumulated history information so that it can be displayed on a specific computer.

The telephone 40 is a general-purpose telephone having operation keys corresponding to the symbols 0 to 9, #, *. FIG. 1 shows telephones 40 a to 40 f among a plurality of telephones 40. In FIG. 1, in order to prevent the figure from becoming complicated, one connection line is shown for each department without showing all the connection lines between the PBX 30 and the telephone 40. The telephones 40a and 40b are arranged in the technical department. The telephone 40c is disposed outside the public relations. The telephone 40d is disposed in the secretary room. The telephone 40e is disposed in the sales department. The telephone 40f is disposed at the support window. The four-digit numerical value shown in association with the telephones 40a to 40d shown in FIG. 1 means a part of each dial-in telephone number.
Here, the information processing apparatus Ca is a general-purpose personal computer used for the same person as the telephone 40a, and is connected to the network NW. The information processing device Cb is a general-purpose personal computer used for the same person as the telephone 40b, and is connected to the network NW.

  Each of the plurality of local telephone systems 1 included in the incoming call management system 100 may have a different configuration such as the number and type of the telephones 40, but has the basic configuration described with reference to FIG. In addition, each incoming call management device 10 of the plurality of local telephone systems 1 is communicably connected to the service server 50 via the network NW. The service server 50 is a server device that communicates with each incoming call management device 10 of the private telephone system 1 to collect and distribute data.

FIG. 2 is a block diagram illustrating a hardware configuration of the incoming call management device 10. As shown in FIG. 2, the incoming call management device 10 includes a control unit 11, an operation unit 12, a display unit 13, a network communication unit 14, an external connection terminal 15, and a storage unit 16.
The control unit 11 includes a processor (control device) having a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory). The CPU controls each unit of the incoming call management device 10 by reading the control program stored in the ROM or the storage unit 16 into the RAM and executing it. The operation unit 12 includes an operation device such as a keyboard and a mouse, and accepts an operation performed by an operator (for example, an administrator of the private telephone system 1). The display unit 13 includes a liquid crystal display, for example, and is a display device that displays various screens. The network communication unit 14 is an interface for transmitting / receiving data to / from an external device by connecting to the network NW and performing network communication. The external connection terminal 15 is an interface for connecting the relay device 20. The external connection terminal 15 is a USB (Universal Serial Bus) standard interface, for example, and is connected to the relay apparatus 20 via a USB cable. The storage unit 16 includes, for example, a hard disk device, and stores a control program executed by the control unit 11. In addition to this, the storage unit 16 stores a telephone number list 161, a group list 162, a policy list 163, an incoming call processing list 164, and a shared rejection number list 165.

FIG. 3 is a diagram illustrating a configuration example of the telephone number list 161. As shown in FIG. 3, the telephone number list 161 is a list in which an outgoing / incoming name field, a telephone number field, a nuisance telephone field, an outgoing / incoming attribute field, a creation date / time field, and an update date / time field are associated with each other. is there.
In the outgoing / incoming name field, the name of the outgoing side or incoming side is written. In the telephone number field, the telephone number of the caller or receiver is written. Information (flag) indicating whether or not the telephone number of the same record is a nuisance call is written in the nuisance call field. When “nuisance” is written in the nuisance call field, the nuisance call source number (hereinafter referred to as “nuisance call number”) is written as the first caller number in the telephone number field of the same record. Means that If the nuisance call field is blank, it means that a sender number that is not a nuisance telephone number is written in the telephone number field of the same record. In the example shown in FIG. 3, the telephone number of the record in which “Sales 1” or “Sales 2” is written in the outgoing / incoming call name field is the nuisance telephone number.

Information indicating whether the telephone number of the same record is the telephone number of the calling side or the called side is written in the outgoing / incoming attribute field. When “OUT” is written in the outgoing / incoming call attribute field, it means that the telephone number of the same record is the caller number. When “IN” is written in the outgoing / incoming call attribute field, it means that the telephone number of the same record is the telephone number of the incoming call destination. In the creation date / time field, the creation date / time of the record, that is, the date / time when the information of this record was newly registered is written. In the update date / time field, the latest date / time when the record information is updated is written.
As described above, a telephone number is registered in the telephone number list 161 for each of the calling side and the receiving side.

FIG. 4 is a diagram illustrating a configuration example of the group list 162. As shown in FIG. 4, the group list 162 is a list in which an outgoing / incoming call group field, an outgoing / incoming call name field, an outgoing / incoming call attribute field, a creation date / time field, and an update date / time field are associated with each other.
In the outgoing / incoming call group field, the group name when the telephone numbers registered in the telephone number list 161 are grouped according to a predetermined classification is written. In the outgoing / incoming call name field, the same information as the outgoing / incoming call name field of the telephone number list 161 described in FIG. 3 is written. For example, in the group list 162, two telephone numbers of “customer 1 charge mobile phone” and “customer 1 ○ × sales office” are registered as telephone numbers belonging to the outgoing / incoming group “customer 1”. In the group list 162, two telephone numbers “Sales 1” and “Sales 2” are registered as telephone numbers belonging to the outgoing / incoming call group “nuisance call”.
Information having the same meaning as the field of the same name in the telephone number list 161 is written in each of the outgoing / incoming attribute field, the creation date / time field, and the update date / time field of the group list 162.
As described above, the group to which the telephone numbers registered in the telephone number list 161 belong is registered in the group list 162.

  FIG. 5 is a diagram illustrating a configuration example of the policy list 163. As shown in FIG. 5, the policy list 163 associates a source group field, a destination group field, an incoming call processing name field, a status field, a recording field, a creation date / time field, and an update date / time field. List. FIG. 5 shows a record number for uniquely identifying each record in the policy list 163.

  In the sender group field, the name of the sender group, which is the group to which the sender belongs, is written. In addition to the outgoing / incoming groups whose information is registered in the group list 162, the sender group includes senders such as “non-notification”, “nuisance call”, “public phone”, “all”, and “shared rejection number list”. Indicates one of the sender groups indicating the classification of. In the destination group field, the name of the destination group indicating the group to which the destination belongs is written. The destination group is registered in the group list 162 and indicates any one of the destination groups indicating the category of the destination, “all”, in addition to the destination group.

In the incoming call processing name field, the name of the incoming call processing designated for the set of the source group and the destination group of the same record is written. Information on whether or not the policy of each record is valid is written in the status field. The policy for records written as “valid” in the status field is valid, and the policy for records written as “invalid” in the status field is invalid. In the recording field, information indicating whether or not the relay device 20 performs the recording process during a call in the group of the source group and the destination group of the same record is written. When “o” is written in the recording field, it is designated to execute the recording process, and when “x” is written in the recording field, it is designated not to execute the recording process.
Information having the same meaning as the field having the same name in the telephone number list 161 and the like is written in each of the creation date field and update date field of the policy list 163.
As described above, in the policy list 163, policies of a transmission source group and a reception destination group that are conditions for executing an incoming call process are registered.

FIG. 6 is a diagram illustrating a configuration example of the incoming call processing list 164. As shown in FIG. 6, the incoming call processing list 164 includes an incoming call process name field, an incoming call process type field, an announcement file path field, a dial-in number field, a playback count field, a creation date / time field, and an update date / time field. Is a list in which
In the incoming call processing name field, the same information as the incoming call processing name field of the policy list 163 is written. Information indicating the type of incoming call processing is written in the incoming call processing type field. When “dial-in” is written in the incoming call processing type field, it is specified that the incoming call specified by the incoming call is rejected and the incoming call is transferred by dial-in. When “announce” is written in the incoming call processing type field, it is specified that the incoming call to the destination specified by the incoming call is rejected and the announcement process is performed.

In the announcement file path field, information indicating the location of the announcement file used for the announcement processing is written when “announce” is designated in the incoming call processing type field of the same record. As the dial-in number, when dial-in is designated in the incoming call processing type field of the same record, the dial-in number used for this dial-in is written. In the playback count field, when “announce” is specified in the process type field of the same record, the number of playbacks of the announcement file used for the announcement process (for example, the continuous playback count) is written.
Information having the same meaning as the field of the same name in the telephone number list 161 and the like is written in each of the creation date field and the update date field of the incoming call processing list 164.
As described above, in the incoming call processing list 164, an incoming call execution method is registered.

FIG. 7 is a diagram illustrating a configuration example of the sharing rejection number list 165. As illustrated in FIG. As shown in FIG. 7, the sharing rejection number list 165 is a list in which a sharing rejection number field, a sender name field, and a registration date field are associated with each other. In the shared rejection number field, a nuisance telephone number (hereinafter referred to as “shared rejection number”) as a second transmission source number shared by the local telephone system 1 in the incoming call management system 100 is written. In the sender name field, the name of the sender corresponding to the nuisance telephone number is written. In the registration date field, the registration date of the sharing rejection number in the sharing rejection number list 165 is written.
As described above, the sharing rejection number used in the incoming call management system 100 is registered in the sharing rejection number list 165.

  Each list of the telephone number list 161, the group list 162, the policy list 163, the incoming call processing list 164, and the sharing rejection number list 165 is updated by the control unit 11, for example. The control unit 11 updates each list of the telephone number list 161, the group list 162, the policy list 163, and the incoming call processing list 164 in accordance with the operation of the operation unit 12 performed by an administrator or the like. For example, the control unit 11 executes a browser to display a predetermined management screen on the display unit 13, receives an operation on the management screen, and updates each list. In addition, the control unit 11 performs network communication with the service server 50 by the network communication unit 14 to notify the service server 50 of the nuisance telephone numbers in the telephone number list 161, and the sharing rejection number notified from the service server 50. Or registration to the share rejection number list 165.

  FIG. 8 is a block diagram illustrating a hardware configuration of the service server 50. As shown in FIG. 8, the service server 50 includes a control unit 51, a network communication unit 52, and a storage unit 53. The control unit 51 includes a processor (control device) having a CPU, a ROM, and a RAM. The CPU controls each unit of the service server 50 by reading the control program stored in the ROM or the storage unit 53 into the RAM and executing it. The network communication unit 52 is an interface for connecting to the network NW and performing network communication. The storage unit 53 includes a hard disk device, for example, and stores a control program executed by the control unit 51. In addition to this, the storage unit 53 includes a dedicated database 531 and a shared database 532.

  FIG. 9 is a diagram illustrating a configuration example of the dedicated database 531 and the shared database 532. As shown in FIG. 9A, the dedicated database 531 is a database in which identification code, nuisance telephone number, caller name, and registration date are associated with each other. The identification code is identification information that uniquely identifies each of the private telephone systems 1. The nuisance telephone number is a nuisance telephone number registered in the telephone number list 161 in the private telephone system 1 identified by the identification code of the same record. The sender name is the name of the sender corresponding to the nuisance telephone number of the same record. The registration date is the registration date of the nuisance telephone number of the same record in the dedicated database 531.

As shown in FIG. 9B, the shared database 532 is a database in which each information such as a sharing refusal number, a sender name, a point total, and a registration date is associated. The sharing rejection number is a sharing rejection number managed by the service server 50. The sharing rejection number in the sharing database 532 is basically synchronized with that registered in the sharing rejection number list 165 of the incoming call management device 10, but may not be synchronized. The sender name is the name of the sender corresponding to the sharing rejection number of the same record. The point total matches the number of sharing rejection numbers of the same record registered as nuisance telephone numbers in the dedicated database 531. In the shared database 532, a nuisance telephone number that is equal to or greater than the threshold of the total points (for example, 10 points or more) is registered as a sharing rejection number. The registration date is a registration date of the sharing rejection number of the same record in the shared database 532.
Note that the above-described example of the registration condition of the share rejection number in the share rejection number list 165 and the method for calculating the point total is merely an example, and the specific content is not limited to a specific mode.

FIG. 10 is a block diagram illustrating a functional configuration of the incoming call management device 10. As shown in FIG. 10, when the control unit 11 executes the control program, the incoming call management device 10 includes a transmission source information acquisition unit 101, a destination information acquisition unit 102, a specification unit 103, and an incoming call control unit 104. And the function equivalent to the registration process part 105 and the incoming call rejection operation detection part 106 is implement | achieved.
When the local telephone system 1 accepts an incoming call addressed to the telephone 40 from the telephone line TL, the transmission source information acquisition unit 101 acquires transmission source information indicating the source of the incoming call. The sender information includes the sender number when the sender number is notified. The sender information includes information that can specify whether or not the sender number is notified (sender number notification / non-notification) and the attributes of the sender phone (for example, a subscriber phone, a public telephone, or outside the display area). The destination information acquisition unit 102 acquires destination information regarding the telephone 40 that is the destination of the incoming call. This destination information includes the destination number of the destination specified by the incoming call.

  The specifying unit 103 stores in the storage unit 16 the incoming call processing specified for the set of the caller information acquired by the caller information acquisition unit 101 and the callee information acquired by the callee information acquisition unit 102. Identify based on each list.

  The incoming call control unit 104 controls the incoming call received by the private telephone system 1 to perform the incoming call processing specified by the specifying unit 103. Here, the incoming call control unit 104 instructs the relay apparatus 20 to execute the incoming call processing specified by the specifying unit 103. The relay device 20 executes an incoming call process instructed by the incoming call management device 10.

  The registration processing unit 105 manages data registration processing for each list stored in the storage unit 16. For example, the registration processing unit 105 registers data in each list in accordance with an operation performed on the operation unit 12 of the incoming call management device 10 or an instruction from the personal computers Ca and Cb. Also, the registration processing unit 105 performs a registration process for registering the sharing rejection number notified from the service server 50 in the sharing rejection number list 165. The registration processing unit 105 refers to each list stored in the storage unit 16 so as to designate at least the incoming call processing for rejecting the incoming call to the telephone 40 for the caller source number of the incoming call addressed to the telephone 40. Data may be registered. In this case, the registration processing unit 105 registers the caller number in the telephone number list 161, and designates the incoming call process for rejecting the incoming call by the transfer process, the announcement process, or the busy process for the caller number. Register data in each list. For example, the registration processing unit 105 writes the caller source number for rejecting an incoming call in a record in which “nuisance” is written in the nuisance call field in the telephone number list 161.

The incoming call rejection operation detection unit 106 detects an incoming call rejection operation performed on the telephone 40 when the caller and the telephone 40 are connected in response to the incoming call. When the incoming call rejection operation is detected by the incoming call rejection operation detecting unit 106, the registration processing unit 105 uses the caller source number of the incoming call that is the basis for establishing the call path as a nuisance telephone number as a telephone number list. 161 is registered.
The transmission processing unit 107 transmits the information of the list stored in the storage unit 16 (specifically, the nuisance telephone number of the telephone number list 161) to the service server 50.

  When the control unit 51 executes the control program, the service server 50 realizes functions corresponding to the collection unit 501 and the notification processing unit 502. The collection unit 501 collects information on the list transmitted by each transmission processing unit 107 of the plurality of incoming call management apparatuses 10 and updates the dedicated database 531 and the shared database 532. The notification processing unit 502 notifies each of the plurality of incoming call management devices 10 of the share rejection number to be registered in the share rejection number list 165 based on the list information collected by the collection unit 501. At this time, the notification processing unit 502 determines a sharing rejection number to be notified based on the dedicated database 531 and the shared database 532.

Next, the operation of the incoming call management system 100 will be described.
FIG. 11 is a sequence diagram showing the flow of processing when the incoming call management device 10 and the service server 50 communicate.
The control unit 11 of the incoming call management device 10 accesses the service server 50 through the network communication unit 14 at a predetermined timing, for example, once a day, and transmits the information (list information) of the nuisance telephone numbers in the telephone number list 161. A transmission process is performed (step S101). For example, the control unit 11 may transmit only the information of unsent nuisance telephone numbers to the service server 50 or may transmit information of all nuisance telephone numbers in the telephone number list 161.
The control unit 51 of the service server 50 receives and collects the nuisance telephone numbers by the network communication unit 52, and updates the dedicated database 531 based on the collected nuisance telephone numbers (step S102). Here, the control unit 51 registers the nuisance telephone number in association with the identification code in the dedicated database 531 for each private telephone system 1.

Next, the control unit 51 updates the shared database 532 (step S103). The control unit 51 counts each nuisance telephone number registered in the dedicated database 531 and sums the count values. Then, the control unit 51 registers the nuisance telephone number whose point total is equal to or larger than the threshold and satisfies the registration condition as a sharing rejection number in the sharing database 532. Next, based on the updated shared database 532, the control unit 51 transmits a registration notification for notifying the sharing rejection number to be registered to each of the plurality of incoming call management devices 10 by the network communication unit 52 ( Step S104).
The control unit 11 of the incoming call management device 10 updates the sharing rejection number list 165 according to the registration notification received by the network communication unit 14 (step S105). Specifically, the control unit 11 registers a share rejection number to be newly registered included in the registration notification by adding a record to the share rejection number list 165.
Through the above processing, the troublesome telephone number and the sharing rejection number between the incoming call management device 10 and the service server 50 are synchronized.
Note that the opportunity to synchronize the nuisance telephone number between the incoming call management device 10 and the service server 50 may be different from the opportunity to synchronize the sharing rejection number.

FIG. 12 is a sequence diagram showing the flow of processing in the private telephone system 1 when an incoming call is accepted.
When an incoming call addressed to the telephone set 40 is accepted from the telephone line TL (step S1), the relay device 20 transmits source information indicating the source of the incoming call to the incoming call management device 10 (step S2). The control unit 11 of the incoming call management device 10 acquires source information from the relay device 20 via the external connection terminal 15 (step S3). Next, the relay device 20 transmits destination information indicating the destination based on the incoming call to the incoming call management device 10 (step S4). The control unit 11 of the incoming call management device 10 acquires destination information from the relay device 20 via the external connection terminal 15 (step S5).
Next, the control part 11 specifies the transmission origin group to which a transmission origin belongs based on the acquired transmission origin information (step S6). For example, the control unit 11 specifies all the source groups to which the source of the incoming call belongs from among the source groups whose information is registered in the policy list 163. That is, the source information here includes information that can identify the source group whose information is registered in the policy list 163. Next, the control unit 11 specifies a destination group to which the destination belongs, based on the acquired destination information (step S7). For example, the control unit 11 identifies all the source groups to which the destination specified by the incoming call belongs among the destination groups whose information is registered in the policy list 163. That is, the destination information here includes information that can identify a destination group whose information is registered in the policy list 163.

Next, the control unit 11 specifies the incoming call process specified for the source group specified in the process of step S6 and the destination group specified in the process of step S7 (step S8). Here, the control unit 11 specifies the incoming call processing name specified for the combination of the source group and the destination group based on the policy list 163. Further, the specific execution method of the incoming call processing is specified based on the record of the incoming call processing name specified from the policy list 163 in the incoming call processing list 164. Then, the control unit 11 controls the incoming call received in the process of step S1 to perform the incoming process specified in the process of step S8 (step S9). Specifically, the control unit 11 transmits an instruction to execute incoming processing to the relay device 20. The control unit 11 refers to each record of the policy list 163 in FIG. 5 in ascending order of record number, and sets the combination of the transmission source group specified in the process of step S6 and the destination group specified in the process of step S7. The incoming call processing is specified based on the matching record. The relay device 20 performs an incoming call process in accordance with an instruction from the incoming call management device 10 (step S10).
A specific example of the incoming call processing will be described below with reference to FIGS.

  When the incoming call group accepts an incoming call specifying the destination of the “support window”, the incoming call management device 10 determines the caller ID and the caller ID based on the policy of record number “1” in the policy list 163. Regardless of the presence or absence of notification or the like, the relay device 20 is controlled so as to permit the incoming call to the telephone 40f of the support window (see FIG. 13A). In this case, the relay device 20 transmits (transfers) the received incoming call to the PBX 30 in response to an instruction from the incoming call management device 10. In this incoming call process, the relay device 20 executes a call voice recording process. When the recording process is executed, the incoming call management device 10 acquires a recorded voice file indicating the recorded call voice from the relay device 20 and stores it in the storage unit 16.

  When the caller group accepts an incoming call from the caller of “business partner 1”, the incoming call management apparatus 10 determines the business partner regardless of the callee based on the policy of the record number “2” in the policy list 163. The relay device 20 is controlled so as to perform a transfer process for transferring the incoming call to the telephone 40a in charge (see FIG. 13B). In this case, the relay device 20 executes the transfer process by rewriting the destination number with the dial-in number “0001”. In this incoming call process, the relay device 20 executes a call voice recording process.

  Next, when the caller group accepts an incoming call from the caller of “business partner 2”, the call receiving management device 10 does not depend on the callee regardless of the callee based on the policy of the record number “3” in the policy list 163. Then, the relay device 20 is controlled so as to perform a transfer process of transferring the incoming call to the telephone set 40b in charge of the customer 2 (see FIG. 13C). In this case, the relay device 20 performs the transfer process by rewriting the destination number with the dial-in number “0002”. In this incoming call process, the relay device 20 executes a call voice recording process.

  Next, when the call origin group accepts an incoming call from the “employee mobile” call originator, the incoming call management device 10 is designated by the incoming call based on the policy of the record number “4” in the policy list 163. The relay device 20 is controlled so as to permit the incoming call to the called party (see FIG. 13D).

  Next, when an incoming call is received from a sender whose source group is “not notified”, the incoming call management device 10 determines that the destination is “sales department” based on the policy of record number “5” in the policy list 163. ", The relay device 20 is controlled so as to permit the incoming call to the destination specified by the incoming call (see FIG. 14A). Strictly speaking, when the incoming call is an incoming call whose source is “not notified” and the incoming destination is not a “support window”, the incoming call management device 10 records the record number “5” in the policy list 163. Incoming call processing is performed according to the policy.

  Next, when the caller group accepts an incoming call from the caller of “nuisance call”, the incoming call management device 10 does not depend on the callee regardless of the callee based on the policy of the record number “6” in the policy list 163. The relay apparatus 20 is controlled so as to perform an announcement process for rejecting the incoming call and reproducing the rejection announcement (see FIG. 14B). In this case, the relay device 20 performs the announcement process based on the announcement file of the file path “C: \ Talkies \ deny.wav” in the incoming call processing list 164. In this announcement processing, for example, a message “Cannot connect from this number” is reproduced, and the incoming call management device 10 notifies that the incoming call is rejected due to the caller.

  Next, when the caller group accepts an incoming call from the caller of “public telephone”, the call reception management device 10 is based on the policy of the record number “7” in the policy list 163 regardless of the callee. The relay apparatus 20 is controlled so as to perform the announcement process for rejecting the incoming call and reproducing the public telephone announcement (see FIG. 14C). In this case, the relay device 20 performs the announcement process based on the announcement file of the file path “C: \ Talkies \ public.wav” in the incoming call processing list 164. In this announcement process, for example, a message “Cannot connect from a public telephone” is reproduced, and the incoming call management apparatus 10 notifies that the incoming call is rejected because the caller is a public telephone.

  Next, when the caller group accepts an incoming call from the caller of the “shared rejection number list”, the call management device 10 relates to the callee based on the policy of the record number “8” in the policy list 163. First, the relay device 20 is controlled to reject the incoming call and perform a transfer process for transferring the incoming call to the telephone 40d outside the negotiation (see FIG. 14D). In this case, the relay device 20 performs the transfer process by rewriting the destination number with the dial-in number “0003”. That is, when registered as a nuisance call, the incoming call is transferred to the telephone 40c outside the bargainer regardless of which destination is specified. In this incoming call process, the relay device 20 executes a call voice recording process. By performing this incoming call processing, the private telephone system 1 can always deal with incoming calls from the shared rejection number outside the negotiation.

  Next, when the incoming call group accepts an incoming call from the “non-notification” source, the incoming call management device 10 is based on the policy of the record number “9” in the policy list 163 regardless of the destination. The relay device 20 is controlled so as to perform the announcement process for rejecting the incoming call and reproducing the public telephone announcement (see FIG. 15A). In this case, the relay apparatus 20 performs the announcement process based on the announcement file of the file path “C: \ Talkies \ 186.wav” in the incoming call processing list 164. However, since it is assumed that the policy does not correspond to the policy with the record number “5” in the policy list 163, the incoming call management apparatus 10 sets the policy with the record number “9” in the policy list 163 when the destination is not the sales department. Perform incoming call processing accordingly. In this announcement process, for example, a message “Please notify the number and try again” is reproduced, and the incoming call management device 10 notifies that the incoming call is rejected due to non-notification of the number.

Next, when the incoming call group receives the incoming call designating the destination of “officer”, the incoming call management device 10 is based on the policy of the record number “10” in the policy list 163, regardless of the transmission source. The relay device 20 is controlled so as to perform transfer processing for transferring the incoming call to the telephone 40d in the secretary room (see FIG. 15B). In this case, the relay device 20 performs the transfer process by rewriting the destination number to the dial-in number “0004”. In this incoming call process, the relay device 20 executes a call voice recording process.
When an incoming call that does not correspond to any of the above policies is accepted, the incoming call management device 10 rejects the incoming call based on the policy of the record number “11” in the policy list 163 and sets the busy state. The relay device 20 is controlled so as to perform busy processing (see FIG. 15C).
Here, the case where all policies are valid (that is, the status field is “valid”) has been described. However, if there is a policy that is invalid (that is, the status field is “invalid”), the incoming call management apparatus 10 does not apply the policy.
As described above, the incoming call management device 10 controls the relay device 20 so as to perform incoming call processing corresponding to a pair of a caller and a callee.

By the way, registration of a troublesome telephone number can be performed by operating the telephone 40. FIG. 16 is a sequence diagram showing the flow of registration processing for an unwanted telephone number using the telephone 40.
When an incoming call according to the incoming call from the telephone line TL is permitted and this incoming call is transmitted from the relay device 20 to the PBX 30 (step S11), the incoming call is transferred from the PBX 30 to the telephone 40 (step S12). When the telephone 40 responds to this incoming call by off-hook, a communication path is established and a call is started (step S13). The user of the telephone set 40 determined to be a nuisance call during this call performs an incoming call rejection operation for instructing to register the caller source number as a nuisance telephone number by operating the telephone set 40. This incoming call rejection operation is, for example, an operation of an operation key such as “999 #”. The incoming call rejection operation to be performed by the user is determined in advance.

  When the incoming call rejection operation is accepted (step S14), the telephone 40 transmits a DTMF (Dual Tone Multi Frequency) signal assigned to the corresponding operation key to the PBX 30 every time the operation key is operated (step S15). . In communication using a DTMF signal, for example, codes 0 to 9, *, and # are expressed by a combination of sound signals in two frequency bands, a low group and a high group. An operation signal composed of the combination of the DTMF signals is transmitted from the PBX 30 to the relay device 20 and transmitted to the incoming call management device 10 (steps S16 and S17). The control unit 11 of the incoming call management device 10 acquires this operation signal from the relay device 20. When detecting the incoming call rejection operation, the control unit 11 registers the caller source number of the incoming call, which is the basis of the connected call path, in the telephone number list 161 as a nuisance telephone number (step S18). Since the DTMF signal is transmitted even during a call, the caller number registered as a nuisance call is specified accurately, and the artificial burden associated with registration is reduced.

  In the incoming call management system 100 according to the embodiment described above, the incoming call processing is executed in accordance with the relationship between the caller and the callee. For example, compared to the case where uniform control is performed according to the caller number, Inconvenience for the user on the receiving side and the receiving side can be reduced. In the incoming call management system 100, for example, even for incoming calls from the same source, the incoming call processing differs depending on the destination specified by the incoming call. As a result, it is possible to deal with incoming calls from a sender that is known in advance as a nuisance call, such as keeping incoming calls to the same telephone 40, and it becomes easier to deal with nuisance calls. Further, in the incoming call management system 100, even for an incoming call to the same destination, the incoming call processing differs depending on the origin of the incoming call. Accordingly, it is possible to allow only a specific caller to receive a call in units of telephones 40. For example, it is easy for a user of the caller to make a call to an appropriate callee reliably.

The present invention may be implemented in a form different from the above-described embodiment. Moreover, you may combine each of the modification shown below.
The incoming call management device 10 may have a function of automatically registering an unwanted telephone number in the telephone number list 161.
FIG. 17 is a flowchart showing a procedure of automatic registration processing for annoying telephone numbers.
The control unit 11 of the incoming call management device 10 acquires the history information accumulated in the PBX 30 and analyzes the acquired history information (step S201). Next, the control part 11 determines a troublesome telephone number based on the analysis result of historical information (step S202). For example, the control unit 11 may receive a specific incoming call from a same source more than a predetermined number of times per unit time to a different destination or a specific number of incoming calls to the same department or a predetermined number of times per unit time. The sender number that satisfies the registration conditions is determined as a nuisance telephone number. The registration conditions may be other conditions such as the total number of incoming calls, as long as the conditions for predicting the nuisance telephone number are determined in advance. Then, the control unit 11 performs a registration process for registering the determined nuisance telephone number in the telephone number list 161 (step S203).

In the embodiment described above, the incoming call management device 10 rejects an incoming call based on the shared rejection number list 165, but may not perform an incoming call rejection based on the shared rejection number list 165. In this case, in the incoming call management system 100, the local telephone system 1 does not have to be configured to communicate with the service server 50, and the service server 50 can be omitted.
Also, the incoming call management device 10 performs the same incoming call processing when receiving an incoming call from a shared rejection number in the shared rejection number list 165 and when receiving an incoming call from a nuisance telephone number in the telephone number list 161. You may control to perform.
Further, in the policy list 163, further conditions may be specified as application conditions for each policy, such as time conditions such as days of the week and time zones to which each policy is applied.

In the above-described embodiment, when an incoming call rejection operation during a call is detected, the incoming call management device 10 registers the nuisance telephone number in the telephone number list 161. If the incoming call rejection operation can be detected after the call ends (that is, after connection), the incoming call management device 10 may detect the incoming call reject operation after the call ends and register the nuisance telephone number in the telephone number list 161. For example, when the PBX 30 is configured to have the function of the incoming call management device 10, the incoming call management device 10 can detect an incoming call rejection operation after the call ends.
For example, the incoming call management device 10 registers, as a nuisance telephone number, the caller source number of the call path established immediately before detecting the call rejection operation. For example, it is assumed that the incoming date and time, the caller number, and the callee number are stored in the PBX 30 and it is determined that the call rejection operation is performed immediately after the telephone 40 ends the call with the nuisance call. In this case, the incoming call management device 10 searches the PBX 30 for a nuisance telephone number based on the telephone 40 that has performed the incoming call rejection operation and the date and time when the incoming call rejection operation was detected. If an incoming call rejection operation is performed after a call, even if an operation signal as a DTMF signal is transmitted from the telephone 40 to the incoming call management device 10, a sound based on the DTMF signal is transmitted to the person who is the source of the nuisance call. Can not be heard.
It should be noted that the present invention does not necessarily require a configuration for registering a nuisance telephone number triggered by detection of an incoming call rejection operation.

The record number of the policy list 163 of the above-described embodiment may be replaced with the priority of each policy. That is, the incoming call management device 10 refers to policies in descending order of priority, and searches for a policy that matches the group of the caller group and the callee group.
In the above-described embodiment, the incoming call management apparatus 10 also determines the incoming call rejection based on the shared rejection number list 165 based on the policy list 163. However, for example, the incoming call management device 10 is configured not to determine based on the policy list 163. May be. For example, if there is an incoming call from the transmission source of the shared rejection number in the shared rejection number list, the incoming call management device 10 may immediately perform the incoming call processing according to the transmission source corresponding to the shared rejection number. Good.

The service server 50 may collect incoming call history information indicating the incoming call history of the telephone 40 in the private telephone system 1 from the incoming call management device 10. For example, the incoming call management device 10 acquires the incoming call history information from the relay device 20 or the PBX 30 and transmits it to the service server 50 at a predetermined timing (for example, when the processing of FIG. 11 is executed). When the service server 50 collects the incoming call history information, the service server 50 stores the collected incoming call history information in the storage unit 53. The service server 50 may display the incoming call history indicated by the incoming call history information stored in the storage unit 53 so that the server administrator or the like can view it, ”and performs the processing described below based on this incoming call history information. May be.
The service server 50 refers to the incoming call history information from the transmission source specified by the sharing rejection number registered in the dedicated database 531 and the shared database 532, and every time there is an incoming call from this transmission source, the point of the dedicated database 531 A predetermined point (for example, 0.5 point for each incoming call) is added to the total. In this way, the points added based on the incoming call history information can be used when different point totals are set as conditions for registering the shared rejection number in the shared rejection number list 165 for each private telephone system 1.

In the embodiment described above, the incoming call management device 10 acquires the caller information including the caller number and the callee information including the callee number from the relay device 20. However, when the incoming call management device 10 and the relay device 20 have a function of specifying the caller group by sharing the telephone number list 161 and the group list 162, the incoming call management device 10 The incoming call processing may be specified by acquiring the transmission source information that can specify the transmission source group. In this case, the incoming call management device 10 does not have to acquire the caller number. Further, when the relay device 20 has a function of specifying a destination group, the incoming call management device 10 may acquire caller information that can specify the destination group, and specify incoming processing. In this case, the incoming call management device 10 does not have to acquire the called party number.
Further, the transmission source group and the destination group described in the above-described embodiment are merely examples, and groups indicating other classifications may be used.

The configuration of the list and the configuration of the database described in the above-described embodiment are merely examples. For example, a list obtained by integrating two or more lists described in the above-described embodiment into one list may be used. For example, in the private telephone system 1, the incoming call processing may be specified directly from the caller number and the callee number without grouping the caller and the callee. In this case, the policy list 163 may be written with data specifying the incoming call processing for the combination of the caller number and the callee number.
In addition, the incoming processing includes transfer processing, announcement processing, and busy processing. However, other processing for rejecting incoming calls may be included. Conversely, the processing is described in the above-described embodiment. A part of the processing may be omitted.
The transfer process is not limited to the process of transferring the incoming call to the telephone 40 in the same private telephone system 1, but is the process of transferring the incoming call to another telephone outside the private telephone system 1, such as a predetermined call center. May be.

The incoming call management device of the present invention may be realized by, for example, a device integrated with the relay device 20, or may be realized by a device integrated with the PBX 30.
Further, the incoming call management device 10 and the service server 50 may communicate not via the network NW but via the telephone line TL.
In addition, when the incoming call management device 10 registers the nuisance telephone number in the telephone number list 161, or when detecting an incoming call rejection operation for registering the nuisance telephone number, the incoming call management apparatus 10 immediately sends the nuisance telephone number to the service server 50. May be notified.

Examples of telephone services that can be employed in the present invention include a telephone service that uses VoIP (Voice over IP) technology, a telephone service that uses an optical fiber line, a cable TV line, and a carrier line. There is a telephone service. The telephone line that can be employed in the present invention may be a line other than a digital line such as an analog telephone line or an optical line, and the specific type thereof is not limited. In addition, the incoming call management system of the present invention can support both a telephone service using a fixed telephone network and a telephone service using a mobile communication network, and a wired, wireless, or a telephone line TL that combines them is used. May be. Therefore, in the incoming call management system of the present invention, the telephone is not limited to a fixed telephone, but a telephone that makes a call using an established communication path, such as a mobile phone, a PHS (Personal Handy-phone System), a smartphone, and an IP phone. If it is.
Further, the on-site telephone system 1 of the above-described embodiment is not limited to the one installed in the company, and the installation place is not particularly limited as long as the telephone 40 is configured.
In the local telephone system 1, a plurality of telephones 40 may be received in response to one incoming call. Also in this case, the incoming call management device 10 may control the relay device 20 so as to execute incoming call processing according to the incoming call destination information regarding each telephone 40.

In addition, the function realized by the incoming call management device of the present invention can be realized by one of hardware resources and software resources or their cooperation. For example, the present invention can be provided as a program executed by a computer.
When the function of the incoming call management device of the present invention is realized using a program, this program can be a magnetic recording medium (magnetic tape, magnetic disk (HDD (Hard Disk Drive), FD (Flexible Disk), etc.)), optical recording. It may be provided in a state stored in a computer-readable recording medium such as a medium (such as an optical disk), a magneto-optical recording medium, or a semiconductor memory, or may be distributed via a network. Further, the present invention can be grasped as an incoming call management method performed by a computer.

DESCRIPTION OF SYMBOLS 1 ... Local telephone system, 10 ... Incoming call management apparatus, 100 ... Incoming call management system, 101 ... Originator information acquisition part, 102 ... Destination information acquisition part, 103 ... Identification part, 104 ... Incoming call control part, 105 ... Registration processing part , 106 ... incoming call rejection operation detection section, 107 ... transmission processing section, 11 ... control section, 12 ... operation section, 13 ... display section, 14 ... network communication section, 15 ... external connection terminal, 16 ... storage section, 161 ... telephone Number list, 162 ... Group list, 163 ... Policy list, 164 ... Incoming call processing list, 165 ... Shared rejection number list, 20 ... Relay device, 30 ... PBX, 40, 40a to 40f ... Telephone, 50 ... Service server, 501 ... Collection unit 502 ... Notification processing unit 51 ... Control unit 52 ... Network communication unit 53 ... Storage unit 531 ... Dedicated database 532 ... Shared data Over the nest.

Claims (5)

An incoming call management device for managing incoming calls to each of a plurality of telephones from an external telephone network,
A storage unit for storing a list designating an incoming call process including whether or not an incoming call can be received for a set of caller information indicating a caller and callee information indicating a callee;
When an incoming call addressed to any one of the plurality of telephones is accepted from the external telephone network, a transmission source information acquisition unit that acquires transmission source information of a transmission source of the incoming call;
A destination information acquisition unit for acquiring destination information about the one telephone;
A specifying unit for specifying the incoming call processing specified for a set of the caller information acquired by the caller information acquisition unit and the callee information acquired by the callee information acquisition unit based on the list; ,
An incoming call control unit that controls the incoming call processing specified by the specifying unit to be performed on the incoming call ;
An incoming call rejection operation detection unit for detecting an incoming call rejection operation performed on the telephone during or after connection between the caller in response to the incoming call and the one telephone;
When the incoming call rejection operation is detected, the incoming call processing designated to reject the incoming call to the telephone set by the caller source number that is the caller telephone number of the incoming call addressed to the one telephone set is added to the list. An incoming call management device comprising a registration processing unit for registration . The own device is a device different from the private branch exchange that performs control for establishing a communication path of the plurality of telephones and the external telephone network.
The incoming call management apparatus according to claim 1. The sender information includes a sender number that is the telephone number of the sender,
The destination information, only contains the destination number is the telephone number of the destination,
The incoming call rejection operation detection unit detects an operation with an operation key assigned with a DTMF (Dual Tone Multi Frequency) signal performed in the one telephone as the incoming call rejection operation,
When the incoming call rejection operation is detected after the connection between the caller corresponding to the incoming call and the one telephone set is terminated, the registration processing unit displays the caller number, the callee number, and the call reception date and time. Among the caller numbers stored in the storage unit for storing, the telephone number of the telephone in which the incoming call rejection operation is detected is the callee number, and the telephone number by the caller number with the newest call reception date is sent to the telephone Register the incoming call processing specified to reject the incoming call to the list.
The incoming call management apparatus according to claim 1. An incoming call management system comprising: an incoming call management device that manages incoming calls to each of a plurality of telephones from an external telephone network; and a server device that is communicably connected to the incoming call management device,
The incoming call management device includes:
A storage unit for storing a list designating an incoming call process including whether or not an incoming call can be received for a set of caller information indicating a caller and callee information indicating a callee;
When an incoming call addressed to any one of the plurality of telephones is accepted from the external telephone network, a transmission source information acquisition unit that acquires transmission source information of a transmission source of the incoming call;
A destination information acquisition unit for acquiring destination information about the one telephone;
A specifying unit for specifying the incoming call processing specified for a set of the caller information acquired by the caller information acquisition unit and the callee information acquired by the callee information acquisition unit based on the list; ,
An incoming call control unit that controls the incoming call processing specified by the specifying unit to be performed on the incoming call;
An incoming call rejection operation detection unit for detecting an incoming call rejection operation performed on the telephone during or after connection between the caller in response to the incoming call and the one telephone;
When the incoming call rejection operation is detected, the incoming call processing designated to reject the incoming call to the telephone set by the caller source number that is the caller telephone number of the incoming call addressed to the one telephone set is added to the list. A registration processing unit to register;
A first collection unit for collecting incoming history information indicating incoming histories of the plurality of telephones;
A transmission processing unit that transmits the list information stored in the storage unit and the collected incoming call history information to the server device, and
The server device
A second collection unit that collects the list information and the incoming call history information transmitted from the incoming call management device by the transmission processing unit;
Based on the number of incoming call history from the same source indicated by the number of call source information has the same source shown and the reception history information included in the collected information of said list, stored in the storage unit An incoming call management system comprising: a notification source that identifies a caller number that is a telephone number of a caller to be registered in a list and notifies the caller management apparatus of the identified caller number . The incoming call management device and the server device are devices different from a private branch exchange that performs control for establishing a communication path of the plurality of telephones and the external telephone network.
The incoming call management system according to claim 4.

Images