JP6909383B2 - Call control device - Google Patents

Description

The present invention relates to a call control device that controls a group conference by telephone.

There is a call control device that enables simultaneous calls between multiple terminals. By constructing a call system using this call control device on the premises, for example, in a factory, a company building, etc., it is possible to have a group meeting by telephone on the premises.

As a conventional telephone system capable of realizing this type of group conference, Patent Document 1 discloses a technique that allows a participant of a group conference to easily recognize the start of a call of another participant. Patent Document 2 discloses a technique for notifying other participants of a terminal whose communication link has been disconnected during a group meeting. Patent Document 3 discloses a technique for encouraging participation of terminals that have not participated in a group meeting. Patent Document 4 discloses a technique for notifying participants when a preset group meeting holding time has elapsed.

Japanese Unexamined Patent Publication No. 2012-205149 Japanese Unexamined Patent Publication No. 2007-324797 Japanese Unexamined Patent Publication No. 2011-139212 Japanese Unexamined Patent Publication No. 2002-290571

Participation status, such as who was attending or was attending the meeting, or who was not or was not attending, during or after the group meeting was over. , There is a request that the organizer or participants of the conference want to know. However, with the techniques disclosed in Patent Documents 1 to 4 described above, the organizer or participants of the conference cannot accurately grasp the participation status.

The present invention has been made by paying attention to the above circumstances, and the first object of the present invention is to provide a call control device capable of grasping the participation status of a conference during the conference by using a terminal participating in the group conference. To do.

A second object is to provide a call control device capable of recording a history including the participation status of a group meeting after the group meeting is over.

In order to solve the above problems and achieve the object thereof, the first aspect of the present invention includes a holding request acquisition means, a participation request acquisition means, and a situation request acquisition means. The holding request acquisition means acquires information on a group meeting holding request by a call transmitted from a first terminal for which a communication link has been established with the base station. The participation request acquisition means acquires the participation request information for the group conference transmitted from the second terminal for which a communication link has been established with the base station. The status request acquisition means acquires the participation status request information for the group meeting transmitted from the first terminal or the second terminal. Then, the storage means are the unique information of the first terminal included in the holding request information for the group meeting, the unique information of the second terminal included in the participation request information for the group meeting, and the meeting from the first terminal. To make a holding instruction to be called all at once to the second terminal selected as a meeting member, and to realize a holding type group meeting between the first terminal and the terminal including the second terminal that has been called. Stores the holding type information included in the holding request information and the participatory information included in the holding request information for realizing a participatory group meeting between any terminals including the first terminal and the second terminal. do. Further, the detection means detects the unique information of the first terminal or the second terminal connected by the communication link by the disconnection detection means according to the disconnection of the communication link with the base station. Then, the creation means is based on the information stored by the storage means, the information detected by the disconnection detection means, the holding type information, and the participatory information, and the participation status of the holding type or the participatory type group meeting. This information is created so that the output means outputs the information to the first terminal or the second terminal, which is the source of the participation status request information, via the communication link.

In the second aspect, the storage means is associated with a group number that identifies a held group meeting, and is associated with a held setting table having unique information of terminals that are members of the group meeting, and the group number. A held state file having a record indicating participation / non-participation of a terminal that is a member of a group meeting is stored, and the creation means is based on the held state file, a participant list, a non-participant list, and the like. it is obtained so as to create a.

A third aspect further comprises a hold detection means for detecting the unique information of the first terminal or the second terminal in the call hold state among the first terminal or the second terminal for which the communication link has been established. Be prepared. Then, the creation means is designed to create information indicating the participation status in the group meeting by further adding the information detected by the hold detection means.

A fourth aspect further comprises a timekeeping means for timing the date and time. Then, the storage means further stores the date and time measured at the time of acquiring the holding request information as the start date / time information of the group meeting.

A fifth aspect further includes a determination means for determining the end of the group meeting based on the unique information of the first terminal or the second terminal detected by the disconnection detection means. Then, the storage means further stores the date and time measured at the time when the end of the group meeting is determined as the end date / time information of the group meeting.

The sixth aspect is the unique information of the first terminal included in the holding request information for the group meeting stored by the storage means and the unique information of the second terminal included in the participation request information for the group meeting. , The start date / time information and the end date / time information of the group meeting are saved in association with the information for identifying the group meeting.

According to the first aspect, in the terminals participating in the group conference, it is possible to accurately grasp the participation status in the group conference based on the unique information of each terminal participating in the conference during the conference. can.

According to the second aspect, in the terminals participating in the group conference, the group conference is started based on the unique information of each terminal participating in the conference or the unique information of each terminal not participating in the conference during the conference. It is possible to accurately grasp the participation status of.

According to the third aspect, among the terminals participating in the group conference, among the terminals participating in the conference during the conference, the terminals in the call hold state can be accurately grasped.

According to the fourth aspect, from the information stored by the storage means, it is possible to accurately grasp the date and time of the group meeting and the participation status of the group meeting.

According to the fifth aspect, from the information stored by the storage means, it is possible to accurately grasp the end date and time of the group meeting and the participation status in the group meeting.

According to the sixth aspect, the history information of the group meeting including the date and time when the group meeting is held and the date and time when the group meeting ends can be stored together with the participation status of the group meeting.

The figure which shows the whole structure of the call system provided with the IP telephone server device as one Embodiment of a call control device. The block diagram which shows the main part structure of the IP telephone server apparatus. The schematic diagram which shows the data structure of the holding type setting table. The schematic diagram which shows the data structure of the participatory setting table. The schematic diagram which shows the data structure of the holding type state table. The schematic diagram which shows the data structure of the participatory state table. A flow chart showing the processing procedure of the request processing unit at the time of inputting the special number of the holding type group. The flow chart which shows the processing procedure of the request processing part at the time of inputting a participatory group special number. The flow chart which shows the processing procedure of the request processing part at the time of holding signal input. The flow chart which shows the processing procedure of the request processing part at the time of holding release signal input. The flow chart which shows the processing procedure of the request processing part at the time of on-hook signal input. A flow chart showing the processing procedure of the request processing unit when the status confirmation special number is input. The flow chart which shows concretely the procedure of the history processing in FIG. The figure which shows an example of the screen of a participant list and the screen of a non-participant list. The figure which shows an example of the screen of the holding type history list and the screen of the participation type history list.

Hereinafter, an embodiment according to the present invention will be described with reference to the drawings. In each drawing and its description below, the same elements are designated by the same reference numerals.
(Constitution)
FIG. 1 is a diagram showing an overall configuration of a call system 1 including an IP telephone server device 10 which is an embodiment of a call control device. The communication system 1 includes a plurality of base stations BS1, BS2, ..., A control device 20, a private branch exchange (PBX) 30, an IP telephone server device 10, and a monitor device 40.

The base stations BS1, BS2, ... Form the radio areas E1, E2, .... The base stations BS1, BS2, ... Are connected to the wireless terminals MT11, MT12, MT13, MT21, MT22, MT23, ... Existing in the wireless areas E1, E2, ... Via a wireless line. The wireless terminals MT11, MT12, MT13, MT21, MT22, MT23, ... Are, for example, PHS terminals. In FIG. 1, three wireless terminals MT11, MT12, MT13, MT21, MT22, MT23, ... Are shown, but the number is not particularly limited. Therefore, in the following, the wireless terminals MT11, MT12, and MT13 existing in the wireless area E1 are collectively referred to as the wireless terminal MT1, and the wireless terminals MT21, MT22, and MT23 existing in the wireless area E2 are collectively referred to. Notated as wireless terminal MT2.

The base stations BS1, BS2, ... Are connected to the control device 20. The control device 20 is connected to the private branch exchange 30. The private branch exchange 30 is connected to a public network such as a telephone network or the Internet. With these connections, the wireless terminals MT1, MT2, ... Existing in the wireless areas E1, E2, ... Can make an extension call between each other and can make an outside line call via the private branch exchange 30. It is also possible to connect an information terminal such as a smartphone or a personal computer having a voice call function to the control device 20 to make an extension call or an outside line call.

The IP telephone server device 10 is connected to the control device 20 via the premises network NW. The premises network NW is composed of, for example, a LAN (local area network). The IP telephone server device 10 is also referred to as an IP telephony server, and controls simultaneous calls between a plurality of wireless terminals MT1, MT2, .... This control enables group meetings by telephone calls using a plurality of wireless terminals MT1, MT2, ....

The monitoring device 40 is connected to the IP telephone server device 10 via, for example, a dedicated line. The monitoring device 40 monitors the status of a group meeting controlled by the IP telephone server device 10. As the monitoring device 40 of this type, for example, a personal computer can be applied.

FIG. 2 is a block diagram showing a main configuration of the IP telephone server device 10. The IP telephone server device 10 includes a control unit 11, a storage unit 12, a communication interface unit 13, an input / output interface unit 14, and a clock unit 15.
The control unit 11 includes a computer configured by connecting a CPU (central processing unit), a ROM (read-only memory), and a RAM (random-access memory) by a system bus as basic hardware, and is stored in the ROM. Performs various types of information processing based on the operating system and application program.

The storage unit 12 stores various types of information necessary for the control unit 11 to perform various types of information processing. As the storage unit 12, for example, a well-known storage device such as an HDD (hard disk drive) or an SSD (solid state drive) that can be written and read at any time can be used.

Under the control of the control unit 11, the communication interface unit 13 transmits and receives voice data and control data to and from the wireless terminals MT1, MT2, ... According to RTP (real-time transport protocol) via the premises network NW. ..
The input / output interface unit 14 is connected to the input unit 41 and the display unit 42 of the monitor device 40, and performs input / output processing for data transfer with the monitor device 40 under the control of the control unit 11. Incidentally, the input unit 41 is, for example, a keyboard, a pointing device, or the like. The display unit 42 is, for example, a liquid crystal display or the like. A touch panel may be used as the input unit 41 and the display unit 42.

The clock unit 15 clocks the current date and time. Here, the clock unit 15 realizes a timekeeping means.

In the IP telephone server device 10 having such a configuration, the control unit 11 has a function as an exchange control unit 111, a request determination unit 112, and a request processing unit 113 in order to control a group conference by a telephone call. Here, before explaining these functions, a brief description of group meetings will be given.

Group meetings include held group meetings and participatory group meetings. In the holding type group conference, terminals MT1, MT2, which are registered as participants, are registered as participants by operating and inputting a conference special number instructing the conference to be held from terminals MT1, MT2, .... A group meeting is held between the terminals MT1, MT2, ... In the participatory group conference, a group conference is held by allowing the terminals MT1, MT2, ... To enter the conference by operating and inputting the conference special number from any terminal MT1, MT2, ....

The IP telephone server device 10 corresponds to a holding type group meeting and a participatory group meeting. That is, the exchange control unit 111 conforms to the DECT (digital enhanced telecommunications) method, and performs processing for establishing a session by SIP (session initiation protocol) between terminals MT1, MT2, ... Participating in a group conference, for example. .. The request determination unit 112 determines various requests transmitted from the terminals MT1, MT2, .... The request processing unit 113 performs data processing related to, for example, a holding type group meeting or a participatory group meeting according to the request determined by the request determination unit 112.

Further, in order to realize the above functions, the IP telephone server device 10 uses a part of the storage area of the storage unit 12 as a holding type setting table 121, a participatory setting table 122, a holding type state file 123, and a participatory state file. It is used as 124, a holding type history file 125, and a participatory type history file 126.

As shown in FIG. 3, the holding type setting table 121 is associated with a group number that identifies the holding type group meeting, and is associated with a meeting special number (holding type group special number) for instructing the holding or participation in the holding type group meeting. ), The number of members, and an extension number corresponding to the number of members. The number of members is the number of terminals MT1, MT2, ... Registered as members of the held group conference identified by the corresponding group number, and the extension number is the unique number assigned to the terminals MT1, MT2, ... Information. In the holding type setting table 121, a group number and a holding type group special number registered in advance as a holding type group meeting, and the number and extension number of terminals MT1, MT2, ... Belonging to the group are set. Here, the holding type setting table 121 realizes the setting means.

In the participatory setting table 122, as shown in FIG. 4, a meeting special number (participatory group) instructing to hold or participate in the participatory group meeting is associated with the group number that identifies the participatory loop meeting. It has an area to store the special number). In the participatory setting table 122, a group number registered in advance as a participatory group meeting and a participatory group special number are set.

The open state file 123 has an area for storing the open state record 123R having the data structure shown in FIG. The holding type status record 123R is composed of data related to the holding type group meeting being held. That is, the holding type status record 123R includes a group number, a holding type group special number, a meeting holding date and time, a meeting ending date and time, and member information. The member information includes the extension numbers of terminals MT1, MT2, ... Registered as members in the held group meeting identified by the group number in the same record, the time of participation in the same held group meeting, and the time of withdrawal. Includes talk time and status. The status identifies each status of non-participation, organizer, participant, organizer pending and participant pending. Incidentally, in the present embodiment, the status indicating the non-participation status is "0", the status indicating the status of the organizer is "1", the status indicating the status of the participants is "2", and the status indicating the status of the organizer being held. Is set to "3", and the status indicating the state in which the participant is pending is set to "4". The open state file 123 can store a plurality of open state records 123R at the same time.

The participatory state file 124 has an area for storing the participatory state record 124R of the data structure shown in FIG. The participatory state record 124R is composed of data relating to an ongoing participatory group meeting. That is, the participatory state record 124R includes a group number, a participatory group special number, a meeting date and time, a meeting end date and time, and participant information. Participant information includes the extension numbers of terminals MT1, MT2 ... Includes time and status. The status identifies each status of organizer, participant, organizer pending and participant pending. Incidentally, in the present embodiment, the status indicating the status of the organizer is "1", the status indicating the status of the participants is "2", the status indicating the status of the organizer is "3", and the status of the participants is pending. The status indicating is set to "4". The participatory state file 124 can store a plurality of participatory state records 124R at the same time.

The holding type history file 125 has an area for accumulating the holding type state record 123R of the holding type group meeting that has finished holding.
The participatory history file 126 has an area for accumulating the participatory state record 124R of the participatory group meeting that has finished holding.

(motion)
7 to 13 are flow charts showing main information processing procedures executed by the request processing unit 113 according to the request determined by the request determination unit 112. 14 and 15 are examples of screens displayed on the display devices of the terminals MT1, MT2, .... The procedure shown in FIGS. 7 to 13 is realized by causing the CPU to execute a program stored in the program storage area of the ROM or RAM of the control unit 11. The processing contents shown in FIGS. 7 to 13 and described below are examples, and the processing procedure and processing contents are not particularly limited as long as similar results can be obtained. Similarly, the contents of the screens shown in FIGS. 14 and 15 and described below are examples, and the displayed contents are not particularly limited as long as similar results can be obtained.

Therefore, next, the group conference control operation of the IP telephone server device 10 will be described with reference to FIGS. 1 to 15. First, the control operation related to the holding and participation of the held group meeting will be described. Here, as an example of the holding type group meeting, it is assumed that the user of the terminal MT11 is the organizer and the users of the terminals MT12, MT13, MT21, MT22, and MT23 are members.

The user of the terminal MT11, which is the organizer of the holding type group conference, first operates the terminal MT11 to make a call. Then, when the communication link with the base station BS1 is established, the user inputs the holding type group special number set in the holding type group meeting to be held. The data of the holding type group special number input by the terminal MT11 is wirelessly transmitted from the terminal MT11 and sent to the IP telephone server device 10 via the base station BS1 and the control device 20. In the IP telephone server device 10, when the request determination unit 112 recognizes that the data received via the control device 20 is the holding type group special number, the request processing unit 113 is notified of the holding type group special number. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG. 7.

First, the request processing unit 113 determines whether or not the holding type group meeting specified by the holding type group special number has not been held as step Sa1. In the holding type group meeting being held, the holding type state record 123R including the holding type group special number is stored in the holding type state file 123. If the corresponding held-type state record 123R is not stored in the held-type state file 123, the request processing unit 113 determines that the held-type group meeting has not been held (YES in Sa1). In that case, the request processing unit 113 acquires the holding type group special number as the holding request information of the group meeting by telephone. Then, the request processing unit 113 acquires the date and time clocked by the clock unit 15 as the conference holding date and time in step Sa2. Then, the request processing unit 113 creates the holding type state record 123R including the holding type group special number and the meeting holding date and time as step Sa3, and saves it in the holding type state file 123. At this time, the request processing unit 113 acquires the group number associated with the holding type group special number and the extension numbers of all the members from the holding type setting table 121. Then, the request processing unit 113 adds the group number to the open state record 123R. Further, the request processing unit 113 adds member information including the extension numbers of all the members to the holding type state record 123R as step Sa4. The participation time, withdrawal time, and talk time of the member information are set to "Null". The status is "0".

As step Sa5, the request processing unit 113 detects the extension number of the terminal MT11, which is the source of the holding type group special number, via the exchange control unit 111. Then, the request processing unit 113 sets the participation time of the member information including the extension number of the terminal MT11 among the member information added to the holding type state record 123R in step Sa6 as the time of the meeting holding date and time. Further, the request processing unit 113 sets the status of the member information to "1" indicating the organizer. After that, the request processing unit 113 adds terminals MT12, MT13, MT21, MT22 to which the extension number included in the member information whose participation time is “Null” among the member information added to the holding type state record 123R as step Sa7 is assigned. , MT23 is instructed to make a call to the exchange control unit 111. With the above, the request processing unit 113 ends the processing when the unheld holding type group special number is input.

The exchange control unit 111, which receives a call command from the request processing unit 113, simultaneously calls the terminals MT12, MT13, MT21, MT22, and MT23. When, for example, the user of the terminal MT21 off-hooks in response to this call, a communication link is established with the base station BS2. Here, when the user inputs the same holding type group special number to participate in the group meeting, the data of the holding type group special number is wirelessly transmitted from the terminal MT21, and the IP telephone server device via the base station BS2 and the control device 20. Sent to 10. In the IP telephone server device 10, when the request determination unit 112 recognizes that the data received via the control device 20 is the holding type group special number, the request processing unit 113 is notified of the holding type group special number. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG. 7.

That is, the request processing unit 113 determines whether or not the holding type group meeting specified by the holding type group special number has not been held as step Sa1. At this time, the holding type state record 123R including the holding type group special number is stored in the holding type state file 123. Therefore, the request processing unit 113 determines that the holding type group meeting is being held (NO in Sa1). In that case, the request processing unit 113 acquires the holding type group special number as information on requesting participation in the group meeting by telephone. Then, the request processing unit 113 acquires the time measured by the clock unit 15 as the conference participation time in step Sa8. Further, the request processing unit 113 detects the extension number of the terminal TM21 of the holding type group special number transmission source via the exchange control unit 111 as step Sa9. Then, as step Sa10, the request processing unit 113 sets the participation time of the member information including the extension number of the terminal TM21 among the member information included in the holding type state record 123R as the conference participation time. Further, the request processing unit 113 sets the status of the member information to "2" indicating a participant. With the above, the request processing unit 113 ends the processing when the holding type group special number being held is input.

In this way, for example, by inputting the holding type group special number of the holding type group meeting which has not been held from the terminal MT11, the user of the terminal MT11 can become the organizer of the holding type group meeting. Then, the IP telephone server device 10 creates a holding type state record 123R in which the holding type group special number and the group number associated with the holding type group special number are set, and stores the holding type state record 123R in the holding type state file 123. In the holding type state record 123R, the date and time when the holding type group special number is input in the terminal MT11 is stored as the meeting holding date and time. In addition, member information including the extension numbers of the terminals MT11, MT12, MT13, MT21, MT22, and MT23 that are members of the holding type group meeting is added to the holding type status record 123R. The status included in each member information is "0" except for the member information for the organizer's terminal MT11. The status of the member information for the organizer's terminal MT11 is "1". Further, in the member information for the terminal MT11 of the organizer, the time of the meeting date and time is stored as the participation time. That is, based on this member information, the user of the terminal MT11 is managed as the organizer of the held group meeting.

On the other hand, for example, by inputting the same holding type group special number in response to an incoming call from the terminal MT21, the user of the terminal MT21 can become a participant of the holding type group conference. Then, in the IP telephone server device 10, the status of the member information including the extension number of the terminal MT21 of the holding type status record 123R including the holding type group special number is changed from "0" to "2". Then, in this member information, the time when the holding type group special number is input on the terminal MT21 is stored as the participation time. That is, based on this member information, the user of the terminal MT21 is managed as a participant in the held group meeting.

Such an operation is the same when the holding type group special number is input in response to an incoming call from other terminals MT12, MT13, MT22, MT23. In other words, for example, when the holding type group special number is not input from the terminal MT12, the status of the member information including the extension number of the terminal MT12 remains "0". That is, the user of the terminal MT12 is managed as a non-participant by this member information.

Next, the control operation related to the holding and participation of the participatory group meeting will be described. Here, as an example, it is assumed that the user of the terminal MT12 is the organizer of the participatory group conference, and the users of the terminals MT22 and MT23 are the participants of the group conference.

The user of the terminal MT12, which is the organizer of the participatory group conference, first operates the terminal MT12 to make a call. Then, when the communication link with the base station BS1 is established, the organizer inputs the participatory group special number set in the participatory group conference to be held. The data of the participatory group special number input by the terminal MT12 is wirelessly transmitted from the terminal MT12 and sent to the IP telephone server device 10 via the base station BS1 and the control device 20. In the IP telephone server device 10, when the request determination unit 112 recognizes that the data received via the control device 20 is a participatory group special number, the request processing unit 113 is notified of the participatory group special number. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

First, the request processing unit 113 determines whether or not the participatory group meeting specified by the participatory group special number has not been held as step Sb1. In the participatory group meeting being held, the participatory state record 124R including the participatory group special number is stored in the participatory state file 124. If the corresponding participatory state record 124R is not stored in the participatory state file 124, the request processing unit 113 determines that the participatory group meeting has not been held (YES in Sb1). In that case, the request processing unit 113 acquires the participatory group special number as information on requesting the holding of a group meeting by telephone. Then, the request processing unit 113 acquires the date and time clocked by the clock unit 15 as the conference holding date and time in step Sb2. Then, the request processing unit 113 creates a participatory state record 124R including the participatory group special number and the date and time of the meeting as step Sb3, and saves the participatory state record 124R in the participatory state file 124. At this time, the request processing unit 113 acquires the group number associated with the participatory group special number from the participatory setting table 122. Then, the request processing unit 113 adds the group number to the participatory state record 124R.

As step Sb4, the request processing unit 113 detects the extension number of the terminal MT12, which is the source of the participatory group special number, via the exchange control unit 111. Then, the request processing unit 113 adds the participant information including the extension number to the participatory state record 124R as step Sb5. Further, in step Sb6, the request processing unit 113 sets the participation time of the participant information as the time of the meeting holding date and time, and sets the status as “1” indicating the organizer. The withdrawal time and talk time of this participant information shall be "Null". With the above, the request processing unit 113 ends the processing when the unheld participatory group special number is input.

On the other hand, for example, when a user of the terminal MT22 participates in a participatory group conference, the user operates the terminal MT22 to make a call. Then, when the communication link with the base station BS2 is established, the participant inputs the participatory group special number set in the participatory group conference to be participated. The data of the participatory group special number input by the terminal MT22 is wirelessly transmitted from the terminal MT22 and sent to the IP telephone server device 10 via the base station BS2 and the control device 20. In the IP telephone server device 10, when the request determination unit 112 recognizes that the data received via the control device 20 is a participatory group special number, the request processing unit 113 is notified of the participatory group special number. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

First, the request processing unit 113 determines whether or not the participatory group meeting specified by the participatory group special number has not been held as step Sb1. At this time, the participatory state record 124R including the participatory group special number is stored in the participatory state file 124. Therefore, the request processing unit 113 determines that a participatory group meeting is being held (NO in Sb1). In that case, the request processing unit 113 acquires the participatory group special number as information on requesting participation in the group meeting by telephone. Then, the request processing unit 113 acquires the time measured by the clock unit 15 as the conference participation time in step Sb7. Further, the request processing unit 113 detects the extension number of the terminal MT22 of the participatory group special number transmission source via the exchange control unit 111 as step Sb8. Then, the request processing unit 113 adds the participant information including the extension number to the participatory state record 124R as step Sb9. Further, in step Sb10, the request processing unit 113 sets the participation time of the participant information as the conference participation time and the status as “2” indicating the participants. The withdrawal time and talk time of this participant information shall be "Null". With the above, the request processing unit 113 ends the processing when the participatory group special number being held is input.

In this way, for example, by inputting the participatory group special number of the participatory group meeting that has not been held from the terminal MT12, the user of the terminal MT12 can be the organizer of the participatory group meeting. Then, the IP telephone server device 10 creates a participatory state record 124R in which the holding type group special number and the group number associated with the special number are set, and stores the participatory state record 124R in the participatory state file 124. In the participatory state record 124R, the date and time when the participatory group special number is input in the terminal MT12 is stored as the conference holding date and time. In addition, participant information including the extension number of the terminal MT12 and the status "1" is added. The time of the meeting date and time is also set as the participation time in this participant information. That is, based on this member information, the user of the terminal MT12 is managed as the organizer of the participatory group meeting.

On the other hand, in order to participate in the participatory group meeting being held, for example, by inputting the same participatory group special number from the terminal MT22, the user of the terminal MT22 can become a participant of the participatory group meeting. Then, in the IP telephone server device 10, participant information including the extension number of the terminal MT22 and the status "2" is added to the participatory state record 124R including the participatory group special number. Then, in this participant information, the time when the participatory group special number is input on the terminal MT22 is stored as the participation time. That is, based on this participant information, the user of the terminal MT22 is managed as a participant in the participatory group conference.
Such an operation is also the same when, for example, a participatory group special number being held is input from another terminal MT23. Here, the control unit 11 of the IP telephone server device 10 realizes the holding request acquisition means and the participation request acquisition means. Further, the control unit 11 realizes the storage means in conjunction with the storage unit 12.

By the way, the terminals MT1, MT2, ... Have a hold function for temporarily holding a call. For example, when the user operates the hold button provided on the terminals MT1, MT2, ..., The terminals MT1, MT2, ... Are put on hold. Further, a hold signal is transmitted from the terminals MT1, MT2, ... According to the operation of the hold button. The hold signal is transmitted to the control device 20 via the base stations BS1, BS2, ... With a communication link established, and is sent to the IP telephone server device 10 via the premises network NW.

Now, it is assumed that a user of the terminal MT11, which is the organizer, operates the hold button during the holding of the held group conference. Then, in the control unit 11 of the IP telephone server device 10, the request determination unit 112 analyzes the hold signal and notifies the request processing unit 113 of the hold of the terminal MT11. This notification includes the extension number of the terminal MT11. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

First, the request processing unit 113 detects the extension number included in the notification as step Sc1. Next, the request processing unit 113 searches the holding type state file 123 and the participatory state file 124 as step Sc2, and confirms whether or not the member information or the participant information including the extension number exists. If the member information or participant information including the extension number does not exist (NO in Sc2), the request processing unit 113 executes another process.

In this example, the member information including the extension number exists in the open state record 123R (YES in Sc2). Therefore, the request processing unit 113 confirms whether or not the status of the corresponding member information is "1" in step Sc3. If the status is not "1" (NO in Sc3), the request processing unit 113 confirms in step Sc4 whether or not the status of the corresponding member information is "2". If the status is not "2" (NO in Sc4), the request processing unit 113 executes another process.

In this example, the status of the corresponding member information is "1" (YES in Sc3). Therefore, the request processing unit 113 sets the status of the corresponding member information to "3" in step Sc5. With the above, the request processing unit 113 ends the processing when the notification of hold is received.

Similarly, it is assumed that a user of the terminal MT23, which is a participant, operates the hold button during the holding of the participatory group meeting. In this case as well, in the control unit 11 of the IP telephone server device 10, the request determination unit 112 analyzes the hold signal and notifies the request processing unit 113 of the hold of the terminal MT23. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

That is, the request processing unit 113 detects the extension number included in the notification as step Sc1, searches the held state file 123 and the participatory state file 124 as step Sc2, and performs member information or participant information including the extension number. Check if exists. In this example, the participant information including the extension number of the terminal MT23 exists in the participatory state record 124R (YES in Sc2). Since the status of the participant information is "2" (YES in Sc4), the request processing unit 113 sets the status of the participant information to "4" in step Sc6. With the above, the request processing unit 113 ends the processing when the notification of hold is received.

In this way, when the organizer of the group conference being held operates the hold button of the terminals MT1, MT2, ..., The status of the member information or the participant information including the extension number of the terminals MT1, MT2, ... It becomes "3". That is, the users of the terminals MT1, MT2, ... Are managed as being held by the organizer. In addition, when a participant of the group conference being held operates the hold button of the terminals MT1, MT2, ..., The status of the member information including the extension number of the terminals MT1, MT2, ... Or the participant information is "4". ". That is, the users of the terminals MT1, MT2, ... Are managed as pending participants. Here, the control unit 11 realizes the holding means by the process of step Sc2 of FIG.

On the other hand, the pending terminals MT1, MT2, ... Are released from the hold when, for example, the hold button is operated again. At this time, the hold release signal is transmitted from the terminals MT1, MT2, .... The hold release signal is transmitted to the control device 20 via the base stations BS1, BS2, ... Where the communication link is established, and is sent to the IP telephone server device 10 via the premises network NW.

Now, it is assumed that the user of the terminal MT11, which is managed as being held by the organizer, operates the hold button again. Then, in the control unit 11 of the IP telephone server device 10, the request determination unit 112 analyzes the hold release signal and notifies the request processing unit 113 of the release of the hold of the terminal MT11. The hold release notification includes the extension number of the terminal MT11. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

First, the request processing unit 113 detects the extension number included in the notification as step Sd1. Next, the request processing unit 113 searches the holding type state file 123 and the participatory state file 124 as step Sd2, and confirms whether or not the member information or the participant information including the extension number exists. If the member information or participant information including the extension number does not exist (NO in Sd2), the request processing unit 113 executes another process.

In this example, the member information including the extension number exists in the holding type state record 123R (YES in Sd2). Therefore, the request processing unit 113 confirms whether or not the status of the corresponding member information is “3” in step Sd3. If the status is not "3" (NO in Sd3), the request processing unit 113 confirms in step Sd4 whether or not the status of the corresponding member information is "4". If the status is not "4" (NO in Sd4), the request processing unit 113 executes another process.

In this example, the status of the corresponding member information is "3" (YES in Sd3). Therefore, the request processing unit 113 sets the status of the corresponding member information to “1” as step Sd5. With the above, the request processing unit 113 ends the processing when the notification of the release of the hold is received.

Similarly, it is assumed that a user of the terminal MT23, which is managed as a participant pending, operates the hold button again. In this case as well, in the control unit 11 of the IP telephone server device 10, the request determination unit 112 analyzes the hold release signal and notifies the request processing unit 113 of the release of the hold of the terminal MT23. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

That is, the request processing unit 113 detects the extension number included in the notification as step Sd1, searches the held state file 123 and the participatory state file 124 as step Sd2, and performs member information or participant information including the extension number. Check if exists. In this example, the participant information including the extension number of the terminal MT23 exists in the participatory state record 124R (YES in Sd2). Since the status of the participant information is "4" (YES in Sd4), the request processing unit 113 sets the status of the participant information to "2" in step Sc6. With the above, the request processing unit 113 ends the processing when the notification of hold is received.

In this way, when the user of the terminals MT1, MT2, ... Managed as being held by the organizer operates the hold button again, the member information or participant information including the extension number of the terminals MT1, MT2, ... Status changes from "3" to "1". That is, the users of the terminals MT1, MT2, ... Are managed again as the organizer. In addition, when the user of the terminals MT1, MT2, ... Managed as being held as a participant is operated again, the status of the member information or the participant information including the extension number of the terminals MT1, MT2, ... Changes from "4" to "2". That is, the users of the terminals MT1, MT2, ... Are managed again as participants.

By the way, the organizer and the participants of the holding type group meeting or the participatory group meeting leave the meeting by on-hooking the terminals TM1, TM2, .... If there is an on-hook in the terminals TM1, TM2, ..., The on-hook signal is transmitted from the terminals MT1, MT2, .... The on-hook signal is transmitted to the control device 20 via the base stations BS1, BS2, ... With a communication link established, and is sent to the IP telephone server device 10 via the premises network NW. Further, the communication link established between the terminals MT1, MT2, ... And the base stations BS1, BS2, ... Is disconnected.

Now, it is assumed that a user of the terminal MT21, which is a participant, is on-hook during the holding of a held group meeting. Then, in the control unit 11 of the IP telephone server device 10, the request determination unit 112 analyzes the on-hook signal and notifies the request processing unit 113 of the on-hook. The on-hook notification includes the extension number of the terminal MT21. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

First, the request processing unit 113 detects the date and time clocked by the clock unit 15 as the on-hook date and time in step Se1. Further, the request processing unit 113 detects the extension number included in the on-hook notification as step Se2. Then, the request processing unit 113 searches the holding type state file 123 and the participatory state file 124 as step Se3, and confirms whether or not the member information or the participant information including the extension number of the terminal MT21 exists. If the member information or participant information including the extension number of the terminal MT21 does not exist (NO in Se3), the request processing unit 113 executes another process.

In this example, the member information including the extension number of the terminal MT21 is included in the holding type state record 123R (YES in Se3). Therefore, the request processing unit 113 sets the withdrawal time of this member information as the on-hook date and time in step Se4. Further, the request processing unit 113 calculates the elapsed time from the participation time to the departure time of the member information in step Se5, and sets the elapsed time as the talk time.

After that, the request processing unit 113 confirms whether or not the group meeting is completed as step Se6. In this case, the member information including the extension number of the terminal MT21 is included in the holding type state record 123R. Therefore, the request processing unit 113 checks the withdrawal time or the talk time of all the member information of the held type state record 123R. Then, if the withdrawal time or the talk time of all the member information is not "Null", the request processing unit 113 determines that the meeting is over. If there is even one member information whose withdrawal time or talk time is "Null", the request processing unit 113 determines that the meeting has not ended. If the meeting has not ended (NO in Se6), the request processing unit 113 ends the processing when the on-hook notification is received.

On the other hand, in the case of the end of the meeting (YES in Se6), the request processing unit 113 sets the meeting end date and time of the held type state record 123R as the on-hook end date and time as step Se7. Next, the request processing unit 113 confirms whether the meeting completed as step Se8 is a holding type group meeting or a participatory group meeting. In this case, since the member information including the extension number of the terminal MT21 is included in the holding type state record 123R, the request processing unit 113 determines that the holding type group meeting has ended (YES in Se8). Then, the request processing unit 113 saves the holding type state record 123R in the holding type history file 125 as step Se9. Further, the request processing unit 113 deletes the held type state record 123R from the held type state file 123 as step Se10. With the above, the request processing unit 113 ends the processing when the on-hook notification is received.

Similarly, it is assumed that, for example, the user of the terminal MT12, which is the organizer, is on-hooked during the holding of the participatory group meeting. In this case as well, in the control unit 11 of the IP telephone server device 10, the request determination unit 112 analyzes the on-hook signal and notifies the request processing unit 113 of the on-hook. The on-hook notification includes the extension number of the terminal MT12. Upon receiving this notification, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG.

That is, the request processing unit 113 detects the date and time clocked by the clock unit 15 as the on-hook date and time in step Se1. Further, the request processing unit 113 detects the extension number included in the on-hook notification as step Se2. Then, the request processing unit 113 searches the holding type state file 123 and the participatory state file 124 as step Se3, and confirms whether or not the member information or the participant information including the extension number of the terminal MT21 exists. In this case, since the participant information including the extension number of the terminal MT12 is included in the participatory state record 124R (YES in Se3), the request processing unit 113 sets the departure time of the participant information on-hook as step Se4. The time of the date and time. Further, the request processing unit 113 calculates the elapsed time from the participation time to the withdrawal time of the participant information in step Se5, and sets the elapsed time as the talk time.

After that, the request processing unit 113 confirms whether or not the group meeting is completed as step Se6. In this case, the participant information including the extension number of the terminal MT12 is included in the participatory state record 124R. Therefore, the request processing unit 113 checks the withdrawal time or the talk time of all the participant information of the participatory state record 124R. Then, if the withdrawal time or the talk time of all the participant information is not "Null", the request processing unit 113 determines that the conference is over. If there is even one participant information whose withdrawal time or talk time is "Null", the request processing unit 113 determines that the meeting has not ended. If the meeting has not ended (NO in Se6), the request processing unit 113 ends the processing when the on-hook notification is received.

On the other hand, in the case of the end of the meeting (YES in Se6), the request processing unit 113 sets the meeting end date and time of the participatory state record 124R as the on-hook end date and time as step Se7. Next, the request processing unit 113 confirms whether the meeting completed as step Se8 is a holding type group meeting or a participatory group meeting. In this case, since the participant information including the extension number of the terminal MT12 is included in the participatory state record 124R, the request processing unit 113 determines that the participatory group meeting has ended (NO in Se8). Then, the request processing unit 113 saves the participatory state record 124R in the participatory history file 126 as step Se11. Further, the request processing unit 113 deletes the participatory state record 124R from the participatory state file 124 as step Se12. With the above, the request processing unit 113 ends the processing when the on-hook notification is received.

In this way, in the holding type state record 123R stored in the holding type state file 123, all the organizers and participants of the holding type group conference specified by the holding type group special number turn on the terminals MT1, MT2, ... When you leave the meeting, it is saved in the holding history file 125. At this time, the conference holding time, the conference end time, and member information (participation time, end time, talk time, status) are recorded in the holding type status record 123R. Similarly, in the participatory state record 124R stored in the participatory state file 124, all the organizers and participants of the participatory group conference specified by the participatory group special number on-hook the terminals MT1, MT2, ... When you leave the meeting, it is saved in the participatory history file 126. At this time, the participation type status record 124R records the conference holding time, the conference end time, and the participant information (participation time, end time, talk time, status). Here, the control unit 11 of the IP telephone server device 10 cooperates with the storage unit 12 to realize the history storage means. Further, the control unit 11 realizes the disconnection detecting means by the process of step Se2 of FIG. 11, and realizes the end determination means by the process of step Se6.

By the way, the IP telephone server device 10 has the terminal MT1. The user of MT2, ... It has a function that makes it possible to check the participation status of group meetings using MT2, .... Therefore, next, this participation status confirmation function will be described.

The user who confirms the participation status inputs a special number (status confirmation special number) for instructing the confirmation of the participation status from the terminals MT1, MT2, ... Which have a communication link established with the base stations BS1, BS2, .... When the status confirmation special number is input to the terminals MT1, MT2, ..., The data of the status confirmation special number is wirelessly transmitted from the terminals MT1, MT2, ..., And the IP phone is transmitted via the base stations BS1, BS2, ... And the control device 20. It is sent to the server device 10. In the IP telephone server device 10, when the request determination unit 112 recognizes that the data received via the control device 20 is the status confirmation special number, the request processing unit 113 is notified of the status confirmation special number. The request processing unit 113 acquires this notification as participation status request information for the group meeting. Then, the request processing unit 113 starts information processing of the procedure shown in the flow chart of FIG. Here, the control unit 11 of the IP telephone server device 10 realizes the status request acquisition means.

First, the request processing unit 113 detects the extension numbers of the terminals MT1, MT2, ... Which are the sources of the status confirmation special numbers via the exchange control unit 111 as step Sf1. Then, the request processing unit 113 searches the holding type state file 123 and the participatory state file 124 as step Sf2, and confirms whether or not the member information or the participant information including the extension number exists. If the corresponding member information or participant information does not exist, the group meeting in which the terminal MT11, which is the sender of the status confirmation special number, is participating is not held. In this case (NO in Sf2), the request processing unit 113 shifts to the history processing described later.

On the other hand, if the corresponding member information or participant information exists, a group meeting in which terminals MT1, MT2, ... Which are the senders of the status confirmation special number are participating is being held. In this case (YES in Sf2), the request processing unit 113 participates in step Sf3 as to whether the extension numbers of the terminals MT1, MT2, ... Check if it is included in the participant information of the type state record 124R.

When it is included in the member information of the held state record 123R (YES in Sf3), the request processing unit 113 sets the participant list and the non-participant list as step Sf4 based on the data of the held state record 123R. create. That is, the request processing unit 113 creates a participant list from the extension numbers of the member information whose statuses are "1", "2", "3", and "4" among the member information included in the held type status record 123R. Then, create a participant list from the extension number of the member information whose status is "0".

On the other hand, when it is included in the participant information of the participatory state record 124R (NO in Sf3), the request processing unit 113 participates as step Sf5 based on the data of the participatory state record 124R. Create a list of people. That is, the request processing unit 113 creates a participant list from the extension number of the participant information included in the participatory state record 124R.

After creating the participant list or the non-participant list in this way, the request processing unit 113 confirms whether or not the request is pending as step Sf6. That is, the request processing unit 113 confirms the presence / absence of member information or participant information having a status of “3” or “4”. Then, when the member information or the participant information having the status "3" or "4" exists (YES in Sf6), the request processing unit 113 sets the member information or the member information having the status "3" or "4" in step Sf7. The extension number of the participant information is detected from the participant list, and a predetermined pending mark is given to the extension number. If the member information or participant information having a status of "3" or "4" does not exist (NO in Sf6), the request processing unit 113 does not execute the process of step Sf7.

After that, the request processing unit 113 transmits the list created in the processing of step Sf4 or step Sf5 as step Sf8 to the terminals MT1, MT2, ... Which are the senders of the status confirmation special number, so that the exchange control unit 111 Notify to. Upon receiving this notification, the exchange control unit 111 transmits the data of the list created in the process of step Sf4 or step Sf5 to the terminals MT1, MT2, ... Which are the senders of the status confirmation special number. With the above, the request processing unit 113 ends the processing when the status confirmation special number is input.
Here, the control unit 11 of the IP telephone server device 10 realizes the creation means by the processing of steps Sf4 and Sf5. Further, the control unit 11 realizes the output means by the processing of step Sf8.

The terminals MT1, MT2, ... That have received the list data can display the participant list or the non-participant list on the display device. FIG. 14 shows an example of the participant list screen D11 and the non-participant list screen D12, respectively. On the screens D11 and D12, the four-digit number is the extension number of the terminals MT1, MT2, ... Further, on the participant list screen D11, the star mark given to the extension number is an example of the hold mark.

In the case of terminals MT1, MT2, ... Participating in the held group meeting, the participant list screen D11 and the non-participant list screen D12 can be displayed. For example, the participant list screen D11 is displayed as the default, and when the button "*" for instructing the display switching is operated, the non-participant list screen D11 is displayed. After that, when the above button "*" is operated, the screen returns to the participant list screen D11. With this configuration, even on the display devices of terminals MT1, MT2, ... be able to.

On the other hand, in the case of the terminals MT1, MT2, ... Participating in the participatory group meeting, only the participant list screen D11 is displayed. Therefore, the user who is participating in the participatory group meeting can check the participant list as appropriate.

As described above, according to the present embodiment, in the terminals MT1, MT2, ... Participating in the holding type or participatory group meeting, the group is based on the unique information of each terminal participating in the meeting during the meeting. It is possible to accurately grasp the participation status of the meeting.

Further, according to the present embodiment, in the terminals MT1, MT2, ... Participating in the held group conference, the unique information of each terminal participating in the conference or the unique information of each terminal not participating in the conference during the conference is held. Based on the information, it is possible to accurately grasp the participation status of group meetings.

Further, according to the present embodiment, among the terminals participating in the holding type or participatory group meeting, among the terminals participating in the meeting during the meeting, the terminals in the call hold state are accurately grasped. Can be done.

Further, according to the present embodiment, in the holding type history file 125 or the participatory history file 126, the history information of the group meeting including the holding date and time and the ending date and time of the group meeting is stored together with the participation status in the group meeting. Can be done.

FIG. 13 is a flow chart showing the procedure of the history processing described above. The request processing unit 113 has detected the extension numbers of the terminals MT1, MT2, ... Which are the sources of the status confirmation special numbers, but the member information or participant information including the extension numbers is the holding type status file 123 and the participation type status file. If it does not exist in 124, the process proceeds to history processing.

First, the request processing unit 113 searches the holding type history file 125 as step Sg1. Then, the request processing unit 113 confirms whether or not the open state record 123R including the member information of the extension number exists as step Sg2. When the corresponding held state record 123R exists (YES in Sg2), the request processing unit 113 creates a held history list from the member information of the extension number included in the held state record 123R as step Sg3. do. On the other hand, if the corresponding open state record 123R does not exist (NO in Sg2), the request processing unit 113 does not execute the process of step Sg3.

Next, the request processing unit 113 searches the participatory history file 126 as step Sg4. Then, the request processing unit 113 confirms whether or not the participatory state record 124R including the participant information of the extension number exists as step Sg5. When the corresponding participatory state record 124R exists (YES in Sg5), the request processing unit 113 obtains the participatory history list from the participant information of the extension number included in the participatory state record 124R as step Sg6. create. On the other hand, when the participatory state record 124R does not exist (NO in Sg5), the request processing unit 113 does not execute the process of step Sg6.

After that, the request processing unit 113 confirms whether or not the history list has been created as step Sg7. When the history list is created by at least one of the processes of step Sg3 or step Sg6 (YES in Sg7), the request processing unit 113 transfers the history list to the terminals MT1, MT2, ... Notify the exchange control unit 111 to transmit. Upon receiving this notification, the exchange control unit 111 transmits the history list created in the process of step Sg3 or step Sg6 to the terminals MT1, MT2, ... Which are the senders of the status confirmation special number. With the above, the request processing unit 113 ends the processing when the status confirmation special number is input.
On the other hand, if the process of step Sg3 or step Sg6 is not executed and the history list is not created (NO in Sg7), the request processing unit 113 ends this process without executing the process of step Sg7. do.

Here, the control unit 11 of the IP telephone server device 10 realizes the creation means by the processing of steps Sg3 and Sg6. Further, the control unit 11 realizes the output means by the processing of step Sg8.

The terminals MT1, MT2, ... That have received the history list can display the held history list or the participatory history list on the display device. FIG. 15 shows an example of the screen D21 of the holding type history list and the screen D22 of the participatory history list, respectively. On the screens D21 and D22, the 8-digit number on the left indicates the date of the conference. The symbol "A" in the center of the screen indicates the organizer, and "B" indicates the participants. When the status of the member information is "1", the user of the terminals MT1, MT2, ... Is the organizer, so the symbol "A" is displayed. When the status of the member information is "2", the user of the terminals MT1, MT2, ... Is a participant, so the symbol "B" is displayed. The time on the left side of the screen indicates the talk time.

The terminals MT1, MT2, ... Of the users who participated in both the held group meeting and the participatory group meeting can display the held history list and the participatory history list on the display device. For example, the holding type history list screen D21 is displayed as the default, and when the button "*" for instructing the display switching is operated, the participatory history list screen D22 is displayed. After that, when the above button "*" is operated, the screen returns to the holding type history list screen D21. With this configuration, even with terminals MT1, MT2, ... Display devices with limited screen sizes, users who participated in the group conference can check the held history list and the participatory history list as appropriate. can.

As described above, according to the present embodiment, the users of the terminals MT1, MT2, ... Who participated in the held or participatory group conference use the terminals MT1, MT2, ... You can easily know the time.

(Other embodiments)
The participant list and the non-participant list are not limited to those on the screens D11 and D12 shown in FIG. For example, the user name of the terminal may be displayed instead of the extension number of the terminal. In addition, the number of participants or non-participants may be displayed. Similarly, the holding type history list or the participatory type history list is not limited to that of the screens D21 and D22 shown in FIG. For example, since the number of participants and the holding time and ending time of the conference can be obtained from the holding type or participatory type history files 125 and 126, such information may be displayed in the history list.

A member of the holding type group meeting may declare absenteeism from the meeting by inputting a predetermined special number from terminals MT1, MT2, ... In advance. In this case, in the holding type setting table 121, the absentee flag is set in association with the extension numbers of the terminals MT1, MT2, ... That have declared absenteeism. Then, in step Sa4 of FIG. 7, when adding the member information of all the members, the status of the terminals MT1, MT2, ... With the absentee flag set is set to, for example, "9". By doing so, the non-participant list created in step Sf4 of FIG. 12 can be further divided into an absentee list and a non-participant list.

In the above embodiment, the mute state may be included in the hold state. Alternatively, the hold state and the mute state may be managed separately. By doing so, not only the pending terminal but also the muted terminal can be identified from the participant list.

The output destination of the history list is not limited to the terminals MT1, MT2, ... The display may be output to the display unit 42 of the monitoring device 40 via the input / output interface unit 14. In this case, since the amount of information that can be displayed on the display unit 42 is considered to be sufficiently larger than that of the display devices of the terminals MT1, MT2, ... Information can be displayed.

The embodiments include the inventions described below.
A communication link has been established between the holding request acquisition means for acquiring the holding request information of a group conference by a call transmitted from the first terminal for which a communication link has been established with the base station, and the base station. The participation request acquisition means for acquiring the participation request information for the group meeting transmitted from the terminal 2 and the first communication link connected by the communication link in response to the disconnection of the communication link with the base station. The end of the group meeting based on the disconnection detecting means for detecting the unique information of the terminal 1 or the second terminal and the unique information of the first terminal or the second terminal detected by the disconnection detecting means. The end determination means for determining the above, the unique information of the first terminal included in the holding request information for the group meeting acquired by the holding request acquisition means, and the group meeting acquired by the participation request acquisition means. The unique information of the second terminal included in the participation request information, the start date / time information of the group meeting timed by the timekeeping means at the time when the holding request information is acquired by the holding request acquisition means, and the end determination. When the end of the group meeting is determined by the means, the storage means for storing the end date and time information of the group meeting timed by the timekeeping means and the information stored by the storage means are identified for the group meeting. A call control device including a history storage means for storing information in association with the information to be used.

The present invention is not limited to the above embodiment, and can be variously modified at the implementation stage without departing from the gist thereof. In addition, each embodiment may be carried out in combination as appropriate, and in that case, the combined effect can be obtained. Further, the above-described embodiment includes various inventions, and various inventions can be extracted by a combination selected from a plurality of disclosed constituent requirements. For example, even if some constituent requirements are deleted from all the constituent requirements shown in the embodiment, if the problem can be solved and the effect is obtained, the configuration in which the constituent requirements are deleted can be extracted as an invention.

1 ... Call system, 10 ... IP phone server device, 11 ... Control unit, 12 ... Storage unit, 13 ... Communication interface unit, 14 ... Input / output interface unit, 20 ... Control device, 30 ... Private branch exchange (PBX), 40 ... Monitor device, 111 ... exchange control unit, 112 ... request determination unit, 113 ... request processing unit, 121 ... held type setting table, 122 ... participatory setting table, 123 ... held type state file, 124 ... participatory state file, 125 ... Held history file, 126 ... Participatory history file, MT1, MT2 ... Terminal, BS1, BS2 ... Base station, NW ... Private branch network.

Claims (6)

A holding request acquisition means for acquiring information on a group meeting holding request by telephone, which is transmitted from the first terminal for which a communication link has been established with the base station.
Participation request acquisition means for acquiring participation request information for the group meeting, which is transmitted from a second terminal for which a communication link has been established with the base station.
A status request acquisition means for acquiring participation status request information for the group meeting transmitted from the first terminal or the second terminal, and
The unique information of the first terminal included in the holding request information for the group meeting acquired by the holding request acquisition means and the first item included in the participation request information for the group meeting acquired by the participation request acquiring means. The unique information of the second terminal and the conference holding instruction from the first terminal are simultaneously called to the second terminal selected as a conference member, and the first terminal and the second terminal called are called. The holding type information included in the holding request information for realizing the holding type group meeting between the terminals including the above terminals, and the participation type between the first terminal and any terminal including the second terminal. A storage means for storing the participatory information included in the holding request information for realizing a group meeting, and
A disconnection detecting means for detecting unique information of the first terminal or the second terminal connected by the communication link in response to the disconnection of the communication link with the base station.
The unique information of the first terminal and the unique information of the second terminal stored by the storage means, and the unique information of the first terminal or the second terminal detected by the disconnection detecting means. A means for creating information indicating the participation status of the holding type or the participatory group meeting based on the holding type information and the participatory type information.
An output means that outputs information created by the creation means to the first terminal or the second terminal, which is the source of the participation status request information acquired by the status request acquisition means, via the communication link. ,
A call control device comprising. The storage means
A holding-type setting table having unique information of the terminal that is a member of the group meeting in association with a group number that identifies the holding-type group meeting.
A holding type state file having a record indicating participation / non-participation of a terminal that is a member of the group meeting in association with the group number is stored.
The creation means
The call control device according to claim 1, wherein a participant list and a non-participant list are created based on the held state file. A hold detection means for detecting unique information of the first terminal or the second terminal in a call hold state among the first terminal or the second terminal for which the communication link has been established.
Further equipped,
The call control device according to claim 1 or 2, wherein the creation means further adds information detected by the hold detection means to create information indicating a participation status in the group meeting. Timekeeping means to time the date and time,
Further equipped,
The call control according to claim 1, wherein the storage means further stores the date and time measured by the timekeeping means at the time when the holding request information is acquired by the holding request acquisition means as the start date and time information of the group meeting. Device. An end determination means for determining the end of the group meeting based on the unique information of the first terminal or the second terminal detected by the disconnection detecting means.
Further equipped,
The call according to claim 4, wherein the storage means further stores the date and time timed by the timekeeping means as end date and time information of the group meeting when the end determination means determines the end of the group meeting. Control device. The unique information of the first terminal included in the holding request information for the group meeting stored by the storage means, the unique information of the second terminal included in the participation request information for the group meeting, and the group. A history storage means that saves the start date and time information and end date and time information of a meeting in association with the information that identifies the group meeting.
5. The call control device according to claim 5.

Images