JP2001257726A - Information communication system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information communication system that continues switching control after a standby system gate keeper is selected in the case that an active system gate keeper conducting connection control between a public network connector connected to a public network and a computer terminal is failed. SOLUTION: An active system and a standby system use data of information such as system data and a terminal state in common. When the active system gate keeper is faulty due to occurrence of a fault, a standby system gate keeper is selected and the gate keeper becoming the active system keeper references the commonly shared data to continue the switching control.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer having a connection I / F for a computer network, voice input / output means, and a telephone means, a network device having a connection I / F for a public telephone network and a computer network, and an exchange processing. The present invention relates to an information communication system in which computers having means are connected by a computer network.

[0002]

2. Description of the Related Art With the development of the Internet and the like, systems for accessing various information service providers from a user terminal to a computer of an information service provider via a public network and receiving desired information services are increasing. Similarly, a user's telephone is used to make a telephone call to a computer system of an information service provider, and an information service or a commodity transaction by voice response is performed.

As an example of such an information service system, a computer system of an information service provider is constructed by a plurality of operator terminals, a server computer storing various service information and control information, a PBX for performing information exchange connection, and the like. Then, the PBX is connected to a public network, and a user terminal and an operator terminal of the public network are connected via the PBX to transmit and receive information.

However, building a system using a PBX is very expensive. Therefore, a multi-unit having a function of transmitting / receiving voice or video, or voice / video information to / from a public network connection device (router device) on a LAN. A telephone or PC terminal (user terminal) connected to a public network by connecting a media terminal (operator terminal) to a call control device (gate keeper device) for controlling connection between a public network connection device and a multimedia terminal. A system for transmitting and receiving information to and from the system has been constructed.

In the above-mentioned system, if a gate keeper (call control device) for controlling connection between the public network connection device and the multimedia terminal breaks down, communication between the public network connection device and the multimedia terminal cannot be maintained. There is a disadvantage to multiply.

[0006]

As described above, in the conventional system, when the gate keeper (call control device) breaks down, the system goes down and the communication between the public network connection device and the multimedia terminal cannot be maintained. was there.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems. A plurality of gatekeepers are provided, one of which is used as an active system, and the other is used as a standby system. In the event of a failure, the standby gatekeeper becomes a new active gatekeeper with reference to the data sharing shared between the active and standby systems, and performs voice communication between the public network connection device and the computer terminal (between the multimedia terminals). An object is to provide an information communication system to be maintained.

[0008]

In order to achieve the above object, an information communication system according to the present invention is connected to a plurality of computer terminals provided with voice input / output means and telephone means, a public network, and has a protocol conversion function. In an information communication system in which at least one router and a gatekeeper having exchange processing means between the computer terminal and the router are connected via a network, a plurality of gatekeepers having the exchange processing means are installed, and the plurality of gatekeepers are provided. When the active gatekeeper switches over to the standby gatekeeper due to the failure of the active gatekeeper, the new active gatekeeper refers to the shared data and continues the exchange control. It is characterized by performing.

[0009] The information communication system of the present invention includes at least system data set by a user among data shared by a plurality of gatekeepers provided with exchange processing means;
The call history data, terminal status, and call status are used as the shared data, and after the system switching, the newly active gatekeeper uses the data to perform a new outgoing / incoming process between the computer terminal and the router. , Call state retention,
It is characterized in that continuity of call history data is assured, and a new call processing service after a system switchover is performed on a call which is being held or held during a system switchover.

[0010] According to the present invention, the active gatekeeper has a failure by sharing data such as system data, terminal status, call history data, call status, transmission / reception history data between the active gatekeeper and the standby gatekeeper. When the standby gatekeeper is switched, the shared data can be used to continue exchange control, make new calls and receive calls, maintain the call state, guarantee the continuity of call history data, and provide new call processing services. .

In the information communication system according to the present invention, among data shared by a plurality of gatekeepers provided with the exchange processing means, system data set by a user, call history data, terminal status, call status, exchange control Signal transmission and reception history data as the shared data, after the system switching,
When the transmission / reception history data of the exchange control signal after the system switching is less than the transmission / reception history data of the exchange control signal before the system switching, when the system switching is performed by retransmitting the exchange control signal from the extension in the middle of the exchange process. It is characterized in that the exchange processing is continued for the call that was being exchanged.

According to the present invention, when the system is switched due to a failure,
Even if the transmission and reception data of the exchange control signal held by the standby gatekeeper is less than the data retained by the active gatekeeper, the call that was being exchanged due to the retransmission processing of the exchange control signal transmission and reception data of the extension terminal is performed. The exchange process can also be continued for.

[0013]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Various embodiments of an information communication system according to the present invention will be described below with reference to the drawings.

FIG. 1 shows the overall configuration of an information communication system according to the present invention. The extensions 11 to 1n are terminals configured by a computer having a computer network connection I / F, voice input / output means, and a telephone function. Multimedia routers (hereinafter, referred to as MMRs) 21 and 22
This is a public network connection device including a connection I / F between the public telephone network 30 and the computer network 100 and a protocol conversion unit. Each of the gatekeepers GK41 to GK42 is a call connection device including a computer network connection I / F, an exchange processing unit, and the like, and configured by a computer that connects the extensions 11 to 1n and the MMRs 21 and 22. These are connected by a computer network 100 to form an information communication system.

In the configuration shown in FIG. 1, the MMRs 21 and 22 can be constituted by one router. On the other hand, by multiplexing the gatekeepers GK41 and GK42, when the active gatekeeper GK fails due to a failure, the system can be continuously operated by switching to the standby gatekeeper GK. Hereinafter, the operation of the various embodiments controlled by the active and standby gatekeepers GK will be described.

FIG. 2 shows an active gatekeeper GK41 for sharing system data and terminal status set by the user.
A sequence is shown in which the standby system GK holds a call state at the time of system switching due to a failure and performs a new outgoing / incoming call after the system switching.
It is assumed that the gatekeepers GK41 and GK42 share the following setting data.

As system data, a called number "01234567"
The destination of “81” is extension 11 and the destination number “0123456782” is extension 12. As the terminal state, it is assumed that the extension 11 is empty and the extension 12 is busy.

It is assumed that when the extension 11 is empty and the extension 12 is busy, a failure occurs in the active gatekeeper GK41, and the gatekeeper GK42 becomes active due to system switching.

After system switching, the newly operating gatekeeper GK42
Receives the call establishment request signal from the MMR 21 with the called number "0123456782" (S10). The gatekeeper GK42 determines that the incoming call is to the extension 12 based on the shared system data, and also determines that the extension 12 is busy based on the shared terminal status.
A disconnection signal is transmitted for "busy" (S11). Next, the gatekeeper GK42 receives the called number “0123456781” from the MMR21.
Receives a call establishment request signal (S12). The gatekeeper GK42 determines that the called number is an incoming call to the extension 11 based on the shared system data, and relays the call establishment request signal to the extension 11 because the extension 11 is idle based on the shared terminal status (S13). ).

As described above, the operating system gatekeeper GK41
Standby gatekeeper GK4 even if a failure occurs due to a failure
2 functions as a newly active gatekeeper, and when receiving a call connection request from the MMR 41, connection control can be continued according to the state of the extension.

In FIG. 3, the system data set by the user, the terminal state, the call history data, and the gatekeeper operating system GK41 and the standby system GK42 which share the call state hold the call state at the time of system switching due to a failure. 4 shows a sequence for maintaining the continuity of the history data and performing a new call processing service after a system switchover for a call held at the time of system switchover. It is assumed that the gatekeepers GK41 and GK42 share the following setting data.

As system data, a called number "01234567"
The destination of "81" is called extension 11, and the destination of called number "0123456782" is called extension 12. As the terminal state, the extension 11 is empty and the extension 12 is busy. As call history data,
Date: 1999/10/01, Calling number: 0987654321, Calling terminal: MM
R41, Called number: 0123456781, Incoming terminal: Extension 11, Incoming time: 09:00:15, Response time: 09:00:20, Disconnect time: 09:05:
40. As the call state, call number: 1, originating terminal: MMR4
1. Incoming terminal: extension 12, call status: on hold.

The MMR 1 and the extension 12 make a call, and the extension 1
It is assumed that a failure occurs in the gatekeeper GK41 of the active system while the system 2 is suspended, and the gatekeeper GK42 becomes the active system by system switching. After the system switching, the gatekeeper GK42 receives the hold release request signal from the extension 12 (S20). The gatekeeper GK42 determines from the shared call state that the call between the MMR 21 and the extension 12 is on hold,
(S21). When the gatekeeper GK42 receives the hold release acceptance signal from the MMR 21 (S22), the gatekeeper GK42 relays the call to the extension 12 (S23) and changes the call state of the shared data to the busy state. Thereafter, when the gatekeeper GK42 receives the disconnection signal from the extension 12 (S24), the gatekeeper GK42 relays the disconnection signal to the MMR 21 (S25), and adds the disconnection call history to the call history data.

As described above, when a failure occurs in the active gatekeeper GK while the MMR 21 and the extension 12 are on hold,
The standby gatekeeper GK42 switches to the new operation system,
Under the control of the newly activated gatekeeper GK42, the hold release processing is performed, and the call and the disconnection processing can be performed.

FIG. 4 shows a gatekeeper operating system GK4 that shares system data, terminal status, call history data, call status, and exchange control signal transmission / reception data set by the user.
1. A sequence is shown in which the standby system GK 42 maintains a call state at the time of system switching due to a failure, maintains continuity of call history data, and continues exchange processing for a call that was being exchanged at the time of system switching. It is assumed that the gatekeepers GK41 and GK42 share the following data.

As the system data, the called number “01234567”
The destination of "81" is extension 11, and the destination of destination number "0123456782" is extension 12. As the terminal state, it is assumed that the extension 11 is empty and the extension 12 is busy. As call history data,
Date: 1999/10/01, Calling number: 0987654321, Calling terminal: MM
R41, Called number: 0123456781, Incoming terminal: Extension 11, Incoming time: 09:00:15, Response time: 09:00:20, Disconnect time: 09:05:
40. As the call state, call number: 1, originating terminal: MM
R41, called terminal: extension 12, call state: on hold. Date and time of transmission / reception of exchange control signal: October 10, 1999
1, time: 10:05:32, transmission / reception type: reception, call number: 1,
Transmission destination / sender: extension 11, control signal type: hold release request signal. As transmission / reception history data of the exchange control signal,
Date: 1999/10/01, time: 10:05:32, transmission / reception type: transmission, call number: 1, destination / sender: MMR21, control signal type: hold release request signal.

The call between the MMR 21 and the extension 12 is transferred to the extension 12
, The extension 12 transmits a hold release request signal to the active gatekeeper GK41 (S30).
It is assumed that after the K41 relays the message to the MMR 21 (S31), a failure occurs in the active gatekeeper GK41, and the gatekeeper GK42 becomes a new active system due to system switching.

After the system switching, the gatekeeper GK42 determines from the shared call state that the call between the MMR 21 and the extension 12 is on hold, and relays the hold release request signal to the MMR 21 based on the transmission / reception history data of the exchange control signal. It is determined that it is in the state. The MMR 21 detects system switching and transmits a hold release acceptance signal to the gatekeeper GK42 (S3).
2). Then, upon receiving the hold release acceptance signal from the MMR 21, the gatekeeper GK42 relays the signal to the extension 12 (S3).
3) The call state is changed to a busy state (S34). afterwards,
When the gatekeeper GK42 receives the disconnection signal from the extension 12 (S35), the gatekeeper GK42 relays the disconnection signal to the MMR 21 (S3).
6) The history of the disconnected call is added to the call history data of the shared data.

As described above, when a failure occurs in the active gatekeeper GK41 when a reservation release request is issued from the extension 12 to the MMR 21 while the MMR 21 and the extension 12 are on hold,
The standby system gatekeeper GK42 becomes the newly active system gatekeeper, and the operations of hold release, call, and disconnection can be continuously processed.

FIG. 5 is a diagram showing a sequence of exchange processing continuation by retransmission of the exchange control signal.

The active gatekeeper GK41 and the standby gatekeeper GK42, which share the system data, terminal status, call history data, call status, and exchange control signal transmission / reception data set by the user, when the standby gatekeeper is switched due to a failure, the standby gatekeeper. The transmission / reception data of the exchange control signal held in the GK42 is transmitted to the active gatekeeper GK41.
In the following, an operation will be described in which the exchange process can be continued for a call that was being exchanged by resending the exchange control signal transmission / reception data of the extension terminal when the data is less than the data stored in the extension terminal. It is assumed that the active gatekeeper GK41 and the standby gatekeeper GK42 share the following data (except for the exchange control signal transmission / reception data, GK41 and GK4).
2 is the same).

As system data, the called number “01234567”
The destination of "81" is extension 11, and the destination of destination number "0123456782" is extension 12. As the terminal state, it is assumed that the extension 11 is empty and the extension 12 is busy. As call history data,
Date: 1999/10/01, Calling number: 0987654321, Calling terminal: MM
R41, Called number: 0123456781, Incoming terminal: Extension 11, Incoming time: 09:00:15, Response time: 09:00:20, Disconnect time: 09:05:
40. As the call state, call number: 1, originating terminal: MM
R41, called terminal: extension 12, call state: on hold. Date and time as the exchange control signal transmission / reception history data of the old operating system:
1999/10/01, time: 10:04:50, transmission / reception type: transmission, call number: 1, destination / sender: extension 12, control signal type: hold acceptance signal. Also, as transmission / reception history data of the exchange control signal of the old operating system, date: 1999/10/01, time: 10:05:
32, transmission / reception type: reception, call number: 1, destination / sender:
Extension 12, control signal type: Hold release request signal. Further, as transmission / reception history data of the exchange control signal of the newly operating system, date: 1999/10/01, time: 10:04:50, transmission / reception type:
Transmission, call number: 1, destination / sender: extension 12, control signal type: hold acceptance signal.

The call between the MMR 21 and the extension 12 is transferred to the extension 12
, The extension 12 transmits a hold release request signal to the active gatekeeper GK41 (S120), and then a failure occurs in the active gatekeeper GK41, and the standby gatekeeper GK42 becomes a new active system due to system switching. .

After the system switching, the newly operating Kate Keeper GK42
Determines that the call between the MMR 21 and the extension 12 is on hold due to the shared call state. However, since the reception history of the hold release request signal is not held, the signal processing is not performed on the hold release request. At extension 12, the time until the reception signal for the transmitted hold release request signal is received has timed out, the transmission of the hold release request signal has been determined to have failed, and the hold release request signal is retransmitted to the new active gatekeeper GK42. (S121), the newly active gatekeeper GK42 relays it to the MMR 21 (S122).
Upon receiving the hold release request signal, the MMR 21 transmits a hold release acceptance signal to the newly active gatekeeper GK42 (S1).
23). And the new operation system gatekeeper GK42 is MMR
When a hold release acceptance signal is received from the terminal 21, the call is relayed to the extension 12 (S124), and the call state is changed to a busy state (S12).
5).

As described above, even when the transmission / reception data of the exchange control signal held by the standby gatekeeper GK42 is less than the data held by the active gatekeeper GK41 at the time of system switching due to a failure, the extension terminal is exchanged. By the retransmission processing of the control signal transmission / reception data, the exchange processing can be continued even for the call that was being exchanged.

FIG. 6 shows that, in an information communication system in which the system data and terminal status set by the user in the gatekeeper GK are shared, the extension stops the holding tone transmission of the call on hold when the system is switched due to a failure, and the call status is changed to the busy state. Is shown.

The call between the MMR 41 and the extension 12 is transferred to the extension 12
It is assumed that a failure has occurred in the gate keeper GK41 and that the gate keeper GK42 has been activated by system switching. Since the extension 12 that has detected the system switching does not hold the call state in which the newly active system gatekeeper GK42 is on hold, the hold tone transmission is stopped and the call state is switched to the busy state.

As described above, when a failure occurs in the active gatekeeper GK41 during the hold, it is possible to make a transition from the hold state to the talk state and transmit the hold sound as a voice message.

FIG. 7 shows the system data set by the user, the terminal status, the call history data, the gatekeeper active GK41 and the standby GK42 that share the call status. This shows how to select the longest terminal. Gatekeeper GK41, GK4
2 shares the following data, and the extension 11, extension 12, and extension 13 belong to the extension group 1, and the incoming call to the extension group 1 selects a terminal having a vacant state and the longest available time to receive a call. It is assumed that the gatekeepers GK41 and GK42 share the following data.

As the system data, the called number “01234567”
The destination of "80" is extension group 1. As the terminal state, the extension 11 is busy, the extension 12 is empty, and the extension 13 is empty. Call history data, date: 1999/10/01,
Calling number: 0987654321, Calling terminal: MMR41, Called number: 01
23456780, incoming terminal: extension 12, incoming time: 09:00:15, response time: 09:00:20, disconnection time: 09:05:40. Call history data, date: 1999/10/01, calling number: 098765
4321, calling terminal: MMR41, called number: 0123456780, receiving terminal: extension 13, receiving time: 09:05:45, response time: 09:05:
51, cutting time: 09:10:04. The call state is: call number: 1, calling terminal: MMR41, receiving terminal: extension 12, call state: talking.

While the MMR 41 and the extension 12 are talking, a failure occurs in the active gatekeeper GK41, and the system switching causes
It is assumed that the standby gatekeeper GK42 has been newly activated.

When the gatekeeper GK42, which has become the new operating system, receives the call establishment request signal from the MMR 21 with the called number "0123456780" (S50), the gatekeeper GK42 determines that the incoming call is to the extension group 1 based on the shared system data. Also, it is determined from the terminal status that the extensions 12 and 13 are idle, and it is further determined that the extension 12 has the longest idle time based on the call history data. As a result, the gatekeeper GK42 relays the call establishment request signal to the extension 12 (S51).

As described above, the operating system gatekeeper GK41
When a failure occurs in the switch to the standby gatekeeper GK42, a call connection request from the MMR 21 can be received by the control of the newly active gatekeeper GK42 within the maximum available time line.

FIG. 8 shows an active gatekeeper GK41, a standby gatekeeper GK42 and a newly added standby gatekeeper GK43 that share the system data set by the user when the user updates the system data. A sequence in which the GK 41 notifies the standby gatekeepers GK 42 and 43 of the update contents of the system data is shown.

When the user updates the contents of the system data, the system data of the active gatekeeper GK41 is updated. The active gatekeeper GK41 transmits the updated system data to the standby gatekeeper GK4.
2. Notify the GK 43 (S60, S61), and in response, update the system data internally managed by the standby gatekeepers GK42, GK43.

FIG. 9 shows an active gatekeeper GK41 and a standby gatekeeper GK4 for sharing call history data.
2. A sequence of notifying the standby gatekeepers GK42 and GK43 of the output call history data each time the active gatekeeper GK41 outputs the call history data in the GK43.

When the active gatekeeper GK41 receives a disconnection signal from the extension 11 while the MMR 21 and the extension 11 are in a call (S70), the gatekeeper GK41 switches to the MMR 21.
To the standby gatekeepers GK42 and GK43 (S7).
2, S73). In response, the gatekeepers GK42, G
K43 adds the call history data to the history data managed internally. In this way, call history data can be added from the active gatekeeper GK41 to the waiting gatekeepers GK42 and GK43.

FIG. 10 shows an active gatekeeper GK41, a standby gatekeeper GK42, and GK that share the terminal status.
At 43, a sequence is shown for notifying the standby gatekeepers GK42 and GK43 of the updated terminal status each time the active gatekeeper GK41 updates the terminal status. When the state of the extension 11 changes from “vacant” to “separated” and the active gatekeeper GK41 receives the terminal state change notification from the extension 11 (S80), the gatekeeper GK41 updates the terminal state of the extension 11 and updates the terminal state. Notifying the standby gatekeepers GK42 and GK43 of the terminal status that has been performed (S
81, S82). In response, the standby gatekeeper GK
42, the GK 43 updates the terminal state of the extension 11 to “away”. In this manner, the terminal gate status can be notified from the active gatekeeper GK41 to the standby gatekeepers GK42 and GK43.

FIG. 11 shows a sequence for notifying the terminal status from the terminal at the time of system switching. It is assumed that a failure occurs in the active gatekeeper GK41 when the terminal state of the extension 11 is “separated”, and the standby gatekeeper GK42 becomes a new active system due to system switching. The extension 11 that has detected the system switching notifies the newly active GK 42 of the terminal state (extension 11 is away from the seat) (S90). On the basis of this, the newly activated gatekeeper GK42 changes the terminal status of the extension 11 of the internal management to “separated”.
Update to As described above, the terminal status can be notified to the newly active gatekeeper GK42 by the notification from the extension 11 after the system switching.

FIG. 12 shows that the active gatekeeper GK41, the standby GK42, and the GK43, which share the terminal status, update the terminal status each time the active gatekeeper GK41 updates the terminal status.
2. A sequence for updating the terminal status by comparing the content notified to the GK 43 with the terminal status notified from the terminal at the time of system switching is shown.

When the state of the extension 11 changes from “empty” to “separated”, the active gatekeeper GK41 receives a terminal state change notification from the extension 11 (S100).
The active gatekeeper GK41 updates the terminal status of the extension 11 and notifies the standby gatekeepers GK42 and GK43 of the updated terminal status (S101, S10).
2). In response to this, the gatekeepers GK42 and GK43 provisionally update the terminal state of the internal management data of the extension 11 from "vacant" to "away".

Thereafter, a failure occurs in the active system gatekeeper GK41, and the active system gatekeeper GK42 is switched by system switching.
Has become the new operating system. Extension 11 that detected system switching
Notifies the newly active gatekeeper GK42 of the terminal status (S103). In response to this, Gatekeeper GK
Reference numeral 42 compares the temporarily updated terminal state of the extension 11 with the contents notified from the extension 11 after the system switching, and updates the terminal state of the internally managed extension 11 from "temporarily leaving" to "leaving" if they are equal. In this manner, the terminal status can be notified to the newly active gatekeeper GK42 by the notification from the extension 11 after the system switching.

FIG. 13 shows the active gatekeeper GK41 and the active gatekeeper GK42, GK43 which share the call state and the transmission / reception history data of the exchange control signal. Every time the standby gatekeeper GK4
2 shows a sequence for notifying the GK43.

The call between the MMR 21 and the extension 11 is transferred to the extension 11
Is suspended, and then the active gatekeeper G is
A hold release request signal is transmitted to K41 (S110), and it is assumed that the active gatekeeper GK41 has relayed to the extension 11 (S111). Operating system gatekeeper GK41 is MM
When the hold release acceptance signal is received from R21, transmission / reception history data of the exchange control signal is added. After relaying the hold release acceptance signal to the extension 11, the call state is changed to "talking". The active gatekeeper GK41 then transmits and receives the exchange control signal transmission / reception history data to the standby gatekeeper GK4.
2. Notify the GK 43 (S112, S113) and notify the call state to the standby gatekeepers GK42, GK43 (S114, S115). In response, the standby gatekeepers GK42 and GK43 add the transmission / reception history data of the exchange control signal to the internal management and update the call state. In this way, the active gatekeeper GK41 can notify the standby gatekeepers GK42 and GK43 of the history data and the call state of the exchange control signal.

FIG. 14 is a diagram showing a sequence for copying shared data by file copying. Working system,
The software 51 and 61 and the file monitoring application 5 for performing exchange processing with the standby gatekeepers 41 and 42
2, 62. In addition, an active file device 5
3, and the standby file device 63 includes system data storage files 54 and 64, call history data storage files 55 and 65, terminal status storage files 56 and 66, and call status storage files 57 and 67.

In the active gatekeeper GK41 and the standby gatekeeper GK42 that share the system data, call history data, terminal status, and call status set by the user, the contents of the file device 53 that stores the shared data on the active gatekeeper GK41 side Every time is changed, the file monitoring application 52 shares the data by copying the changed file (54 to 57) to the corresponding file (64 to 67) of the file device 63 of the standby gatekeeper GK42. Can be done.

The file monitoring application 52 of the active gatekeeper GK41 monitors the file device 53 in which the shared data is stored (S120). For example, it is assumed that the active gatekeeper GK41 has written the history data of one of the shared data in the file 55 (S
121). In response to this, the file monitoring application 52 copies the communication history data file 55 to the file 65 of the file device 63 of the standby gatekeeper GK42 (S122). The same processing is performed when the storage file of the system data, terminal state, and call state is changed.

As described above, various files stored in the file device of the active gatekeeper can be copied to the corresponding files of the file device of the standby gatekeeper.

[0059]

According to the present invention, the active gatekeeper and the standby gatekeeper share data such as system data, terminal status, call history data, call status, transmission / reception history data, and so on. If the gatekeeper fails and system switching is performed to the standby gatekeeper, continuation of exchange control, new outgoing / incoming calls,
It is possible to maintain the call state, guarantee the continuity of call history data, perform a new call processing service, and the like.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the overall configuration of an information communication system according to the present invention.

FIG. 2 is a diagram showing a new outgoing / incoming call sequence after system switching of the information communication system according to the present invention.

FIG. 3 is a diagram showing a new call processing sequence after system switching of the information communication system according to the present invention.

FIG. 4 is a diagram showing an exchange processing continuation sequence after system switching of the information communication system according to the present invention.

FIG. 5 is a diagram showing an exchange processing continuation sequence by retransmission of an exchange control signal at the time of system switching of the information communication system according to the present invention.

FIG. 6 is a diagram showing a sequence for switching a call state to a busy state from transmission of a hold tone at the time of system switching by an extension of the information communication system according to the present invention.

FIG. 7 is a diagram showing an incoming call sequence to a maximum free time extension at the time of system switching of the information communication system according to the present invention.

FIG. 8 is a diagram showing a system data sharing sequence by communication of the information communication system according to the present invention.

FIG. 9 is a view showing a history data sharing sequence of a call by communication of the information communication system according to the present invention.

FIG. 10 is a diagram showing a terminal state sharing sequence by notification of the information communication system according to the present invention.

FIG. 11 is a diagram showing a terminal state sharing sequence based on a notification from an extension after switching of the information communication system according to the present invention.

FIG. 12 is a diagram showing a terminal state sharing sequence based on a notification between gatekeepers at the time of terminal state change and an extension notification after system switching in the information communication system according to the present invention.

FIG. 13 is a diagram showing a call status and exchange control signal transmission / reception history data sharing sequence based on notification of the information communication system according to the present invention.

FIG. 14 is a view showing a data sharing sequence by file copying in the information communication system according to the present invention.

[Explanation of symbols]

11, 12, 1n Extension 21, 22 Multimedia router MMR (public network connection device) 30 Public network 41, 42, 43 Gatekeeper GK (call control device) 100 Network LAN

Continued on the front page (51) Int.Cl. ⁷ Identification code FI Theme coat II (Reference) H04M 11/00 303 H04L 13/00 311 9A001 F term (Reference) 5K019 AA08 BA53 BA62 BB02 CC01 DC02 EA16 EA24 5K030 HB01 HC01 HC14 HD03 HD06 JA13 JT06 KA05 LB01 LB15 LE03 MB01 MD02 5K035 AA03 AA04 BB03 BB04 LL14 5K051 AA01 CC02 DD01 DD13 EE07 FF02 FF16 GG06 5K101 KK02 LL02 MM01 QQ08 QQ11 VV03 VV04 VV05 9A001 BB01 KK01 BB01

Claims (16)

[Claims] 1. A plurality of computer terminals including voice input / output means and telephone means, at least one router connected to a public network and having a protocol conversion function, and exchange processing between the computer terminal and the router In an information communication system in which gatekeepers having means are connected by a network, a plurality of gatekeepers having the exchange processing means are installed,
The necessary data is shared among the multiple gatekeepers,
Information communication characterized in that when system switching is performed to the standby gatekeeper due to the occurrence of a failure in the active gatekeeper, the gatekeeper that has become the new active system continuously performs exchange control with reference to the shared data. system. 2. The data shared by a plurality of gatekeepers provided with the exchange processing means includes system data set by a user, call history data, terminal status, call status, and exchange control signal transmission / reception history data. Item 2. The information communication system according to Item 1. 3. Among the data shared by the plurality of gatekeepers provided with the exchange processing means, at least the system data set by the user and the terminal status are set as the shared data, and after the system switching, the new active system 2. The information communication system according to claim 1, wherein the new gatekeeper holds a new outgoing / incoming call process and a call state between the computer terminal and the router based on the data. 4. The data shared by a plurality of gatekeepers provided with the exchange processing means, at least system data set by a user, call history data, terminal status,
The call state is used as the shared data, and after the system switching, the newly active gatekeeper uses the data to perform a new outgoing / incoming call processing between the computer terminal and the router, hold a call state, and hold a call. 2. The information communication system according to claim 1, wherein a continuity of the history data is guaranteed, and a new call processing service after the system switching is performed for the call being held or held during the system switching. 5. The data shared by a plurality of gatekeepers provided with the exchange processing means, wherein the system data, call history data, terminal status, call status, and exchange control signal transmission / reception history data set by the user are shared. After the system switchover, the newly active gatekeeper uses the data to perform a new outgoing / incoming call processing between the computer terminal and the router, hold a call state, and maintain continuity of call history data. 2. The guarantee processing, a new call processing service after a system switchover for a call being held or held at the time of system switchover, and a switchover process being continued for a call that was being exchanged during the system switchover. Information communication system. 6. The data shared by a plurality of gatekeepers provided with the exchange processing means, wherein the system data, call history data, terminal status, call status, and exchange control signal transmission / reception history data set by the user are shared. If the transmission / reception history data of the exchange control signal after the system switching is less than the transmission / reception history data of the exchange control signal before the system switching, the exchange control signal is transmitted from the extension in the middle of the exchange process. 2. The information communication system according to claim 1, wherein the exchange processing is continued for a call that was in the middle of the exchange processing at the time of system switching by retransmitting the call. 7. The information communication according to claim 3, wherein upon detecting system switching, the computer terminal stops sending a hold tone for the call on hold, and sends a voice message or resumes the call. system. 8. The computer terminal having the longest available time before switching based on the shared call history data and terminal status in response to a call establishment request from the router, wherein the newly active gatekeeper is used. 5. The information communication system according to claim 4, wherein the communication partner can be selected as a connection partner. 9. The information communication system according to claim 1, further comprising means for notifying the updated system data from the active gatekeeper to the standby gatekeeper every time the user updates the system data. system. 10. The information communication system according to claim 1, further comprising: means for notifying the standby gatekeeper of the history data each time the active gatekeeper outputs the history data of the call. 11. The information communication system according to claim 1, further comprising means for notifying a terminal status at the time of system switching from the client to the newly active gatekeeper at the time of system switching. 12. The information communication system according to claim 1, further comprising means for notifying the standby gatekeeper each time the active gatekeeper updates a terminal state. 13. The newly active gatekeeper compares the terminal state at the time of system switching with the updated terminal state, and sets the terminal state at the time of system switching only when they match. The information communication system according to claim 10 or 11, wherein: 14. The information according to claim 1, further comprising means for notifying the standby gatekeeper of a call state and a call state in the middle of a switching process every time the active gatekeeper processes a call. Communications system. 15. A file for storing the shared data such as system data set by the user, call history data, terminal status, call status, and the like is provided, and each time the file is updated, a file is stored on an active gatekeeper. 6. The information according to claim 2, wherein software different from the software performing the exchange processing further includes means for copying these files to the file of the standby gatekeeper. Communications system. 16. The information communication system according to claim 10, wherein the terminal state at the time of system switching includes a terminal registration state with respect to the active gatekeeper, a terminal registration state with an extension group, and a state of an operator who uses the terminal. .