JP5136902B2 - Private branch exchange failover system and private branch failover method - Google Patents

Description

  The present invention provides a private telephone having at least a primary system function unit for centrally controlling a private telephone placed under the private branch exchange functioning as a primary system and a private telephone exchange acting as a secondary system. The present invention relates to an exchange failover system and method.

  A private telephone set placed at each office desk in one building is connected to one private branch exchange, and the private telephone may be controlled by one private branch exchange. However, for example, in a large-scale building, a plurality of private branch exchanges are placed for each floor, and private telephones for each floor are connected to the private branch exchanges on that floor. In this case, a private branch exchange functioning as a secondary system is placed on each floor, and a private branch exchange functioning as a primary system for centrally controlling these private branch exchanges is also placed.

  On the other hand, in recent years, a technique called CTI (Computer Telephony Integration) that integrates telephones and facsimiles into computer systems has become widespread.

In CTI, a computer including a CTI application and a CTI drive communicates with a private branch exchange functioning as a primary system, not a private branch exchange functioning as a secondary system.
JP 2004-235922 A

  By the way, when a private branch exchange that functions as a primary system fails, the failover function works, and one private branch exchange that has functioned as a secondary system until then functions as a new primary system. A private branch exchange.

  In such a case, the computer that had previously communicated with the private branch exchange that functions as the primary system needs to start communication with the private branch exchange that functions as the new primary system. There wasn't.

  Therefore, the present invention enables a computer compatible with CTI to start communication with a private branch exchange functioning as a new primary system even when the private branch exchange functioning as a primary system is changed. An object of the present invention is to provide a failover system for a private branch exchange and a failover method for the private branch exchange.

  According to the present invention, a primary system function unit for centralized control of a private telephone set placed under the private branch exchange functioning as a primary system and a private branch exchange functioning as a secondary system; Each of the plurality of private branch exchanges has a secondary system function unit that functions as a secondary system in which a private telephone is placed under the subordinate telephone. One private branch exchange functions as a primary system, and the other private branch exchanges are secondary When a failure occurs in the one private branch exchange that functions as the system and functions as the primary system, one of the private branch exchanges that have functioned as the secondary system until then becomes a new one. Failover of the private branch exchange that functions as the primary system A private branch exchange where each private branch exchange that is functioning as a secondary system knows the IP address of the private branch exchange that is currently functioning as the primary system and can be connected to a computer telephony integration server Is functioning as a secondary system, the private branch exchange indicates that the private branch exchange is not the private branch exchange functioning as the primary system and the IP address of the private branch exchange currently functioning as the primary system. The computer telephony integration server notified to the computer telephony integration server, and the computer telephony integration server receiving the notification treats the private branch exchange having the notified IP address as a private branch exchange functioning as a primary system. Failover system private branch exchange that features that connection is provided Te.

  Further, according to the present invention, a primary system function unit for centralized control of a private telephone placed under a private branch exchange functioning as a primary system and a private telephone located under a private branch exchange functioning as a secondary system Each of the plurality of private branch exchanges, one private branch exchange functions as the primary system, and the other private branch exchanges When a certain private branch exchange functioning as a secondary system and functioning as a primary system fails, one of the private branch exchanges functioning as the secondary system until then is The face of the private branch exchange that functions as the new primary system A private branch exchange in which each private branch exchange that is functioning as a secondary system knows the IP address of the private branch exchange that is currently functioning as a primary system and can be connected to a computer telephony integration server Is functioning as a secondary system, the private branch exchange indicates that the private branch exchange is not the private branch exchange functioning as the primary system and the IP address of the private branch exchange currently functioning as the primary system. The computer telephony integration server notified to the computer telephony integration server, and the computer telephony integration server receiving the notification treats the private branch exchange having the notified IP address as a private branch exchange functioning as a primary system. Failover method between exchanges that features that connection is provided Te.

  According to the present invention, even when a private branch exchange functioning as a primary system is changed, a computer compatible with CTI can start communication with a private branch exchange functioning as a new primary system. Become.

  The best mode for carrying out the present invention will be described below in detail with reference to the drawings.

  The primary private branch exchange (referred to as a private branch exchange that functions as a primary system. “Private branch exchange” is also referred to as “button telephone device”) goes down due to a network failure, etc., and fails over to another private branch exchange. Even when the operation is started as the proxy primary private branch exchange, the CTI server (computer including the CTI application and the CTI drive) 100 can automatically connect to the proxy primary device and continue the operation as the CTI server.

  When connected to the primary private branch exchange, the CTI server 100 obtains a list of IP addresses of private branch exchanges that can become proxy primary private branch exchanges.

  When the connection with the primary private branch exchange is disconnected, the private branch exchange operating as the proxy primary private branch exchange is searched based on the list of IP addresses of the private branch exchanges that can be acquired as the primary proxy private branch exchange. .

  When a private branch exchange not operating as a primary private branch exchange is connected from the CTI server, the private branch exchange notifies the CTI server of the IP address of the private branch exchange operating as the primary private branch exchange.

  Next, the configuration of the embodiment of the present invention will be described in detail with reference to the drawings.

  Referring to FIG. 1, the first embodiment of the present invention includes a computer 100 used as a CTI server, a private branch exchange 200, a private branch exchange 210, and a private branch exchange 220.

  The computer 100 is installed with a CTI driver 120 which is a program for communicating with the private branch exchange 200 via a LAN.

  The CTI driver 120 has an interface for the CTI application 110 to control telephones and lines accommodated in the private branch exchange.

  The CTI application 110 has a function of controlling telephones and lines accommodated in the private branch exchange using an interface provided by the CTI driver 120.

  Each of the private branch exchange 200, the private branch exchange 210, and the private branch exchange 220 has a redundant configuration. That is, the private branch exchange 200, the private branch exchange 210, and the private branch exchange 220 have both a portion that functions as a primary system and a portion that functions as a secondary system. Normally, the private branch exchange 200 operates as a primary system, and the primary system unit of the private branch exchange 200 centrally controls the secondary system unit of the private branch exchange 200, the secondary system unit of the private branch exchange 210, and the secondary system unit of the private branch exchange 220. .

  When the private branch exchange 210 detects that the private branch exchange 200 is disconnected from the network due to a failure or the like, the private branch exchange 210 starts centralized control instead of the private branch exchange 200 as a proxy primary system.

  In order for the CTI driver 120 to control the private branch exchange, it is necessary to connect to the primary private branch exchange performing centralized control.

  The CTI driver 120 has a function of monitoring the connection with the private branch exchange 200 using packets periodically transmitted from the private branch exchange 200.

  When connected to the private branch exchange 200, the CTI driver 120 has a function of acquiring and storing a list of IP addresses of private branch exchanges that can become proxy primary systems from the private branch exchange 200.

  When the CTI driver 120 detects that the connection with the private branch exchange 200 has been disconnected, the CTI driver 120 has a function of trying connection in order from the top of the list based on the stored list of IP addresses of the private branch exchange.

  If the private branch exchanges 200 and 210 are not operating as a primary system when they are connected from the CTI driver 120, the private branch exchanges 200 and 210 indicate that they are not private branch exchanges operating as a primary system, and at that time as a primary system. The CTI driver 120 is notified of the IP address of the private branch exchange that is operating.

  The CTI driver 120 is notified when the private branch exchange that has attempted connection is notified that the private branch exchange is not the private branch exchange operating as the primary system and the IP address of the private branch exchange operating as the primary system. Has a function of attempting to connect to a private branch exchange with an IP address.

  Next, the operation of the first embodiment of the present invention will be described in detail with reference to the flowcharts of FIGS.

  First, the CTI driver 120 tries to connect to the IP address of the private branch exchange set by the user (step A1 in FIG. 2). If connection cannot be established within a certain period of time, it is determined that the connection has failed and the process proceeds to step A3. Connections are attempted in order from the top of the stored IP address list (step A3). If the connection is successful, the connected private branch exchange is inquired as to whether or not the private branch exchange is operating as a primary system or a proxy primary system (step A4). Referring to the inquiry result, if the connected private branch exchange is not operating as a primary system or a proxy primary system, the process proceeds to step A6. If the connected private branch exchange is operating as a primary system or a proxy primary system, the process proceeds to step A7. The private branch exchange not operating as the primary system or the proxy primary system notifies the IP address of the private branch exchange currently operating as the primary system. The CTI driver 120 tries to connect to the notified IP address (step A6). If the private branch exchange is operating as a primary system or a proxy primary system, the CTI driver 120 inquires of the private branch exchange about the IP address of the private branch exchange that can operate as the proxy primary system (step A7). Finally, the information of the IP address list stored in the CTI driver 120 is updated with the IP address list notified from the private branch exchange (step A8).

  Next, the operation of this embodiment will be described using a specific example.

  When the private branch exchange 200, which is the primary system, is operating normally, it operates as follows.

  The CTI driver 120 connects to the private branch exchange 200 having the highest IP address in the list (step B1 in FIG. 3). If the connection is successful, the CTI driver 120 inquires whether the connected private branch exchange is operating as a primary system or a proxy primary system (step B2). When the connected private branch exchange 200 is notified that the private branch exchange 200 is operating as a primary system or a proxy primary system, the CTI driver 120 inquires of the private branch exchange 200 about an IP address list. The private branch exchange 200 notifies the private branch exchange 200 of the IP addresses of the private branch exchange 210 and the private branch exchange 220 (step B3).

  When a failure occurs in the private branch exchange 200 as the primary system and the CTI driver 120 cannot be connected to the private branch exchange 200, for example, the following operation is performed.

  If the connection is successful, the CTI driver 120 inquires whether it is primary (step B4). When notified from the connected private branch exchange 210 that the system is the primary system, the CTI driver 120 inquires of the IP address list (step B5).

  The first effect of the present embodiment is that the CTI driver can be connected to the changed private branch exchange even when the private branch exchange to be connected is changed due to failover of the private branch exchange.

  The reason is that an IP address list of private branch exchanges that may become connection destinations is acquired in advance from the private branch exchange.

  Next, the operation of another embodiment will be described.

  The operation up to Step B3 until a failure occurs in the private branch exchange 200 is the same as that in the above embodiment.

  When the head of the IP address list is not the proxy primary system, the operation is as follows.

  The CTI driver 120 is connected to the private branch exchange 220 (step C1 in FIG. 4). Here, it is assumed that the private branch exchange 220 is not a proxy primary system. If the connection is successful, the CTI driver 120 makes an inquiry to the private branch exchange 220 as to whether or not the private branch exchange 220 is operating as a primary system. In this example, since the private branch exchange 220 of the connection destination is not a proxy primary system, the private branch exchange 220 notifies that the private branch exchange 220 is not a proxy primary system and the IP address of the private branch exchange 210 (step C2). When notified of the IP address of the private branch exchange 210, the CTI driver 210 connects to the private branch exchange 210 using the IP address. If the connection is successful (step C3), the CTI driver 120 inquires of the private branch exchange 210 whether the private branch exchange 210 is operating as a proxy primary system (step C4). Next, the CTI driver 120 inquires of the private branch exchange 210 about the IP address list (step C5).

  Next, with reference to FIGS. 5 and 6, how to determine the private branch exchange that functions as the proxy primary system will be described.

  The private branch exchange 200 receives the keepalive from each of the private branch exchange 210 and the private branch exchange 220, and returns a keepalive response thereto (step S301).

  If a failure occurs in the private branch exchange 200, the private branch exchange 220 cannot return a keep-alive response, so the private branch exchange 210 and the private branch exchange 220 detect that a failure has occurred in the private branch exchange 200 (steps S302 and S303). ).

  Since connection is attempted again but there is no keep-alive response, private branch exchange 210 and private branch exchange 220 give up reconnection (steps S304 and S305).

  The surviving private branch exchange inquires all other private branch exchanges for the priority, and the surviving private branch exchange responds to the inquiry (steps S306 and S307). The priority order is determined according to the processing capacity of the private branch exchange, or mechanically determined from the first floor in the order that the floor rises.

  Next, each private branch exchange compares its own priority with all received priorities, and determines that it should function as a proxy primary system when its own priority is the highest. To do. In this embodiment, it is the private branch exchange 210 (step S308).

  The private branch exchange 210 that has determined that the local exchange is a private branch exchange that should function as a proxy primary system notifies the private branch exchange 220 of the IP address of the private branch exchange (step S309).

  Thereafter, communication between the private branch exchanges is started with the private branch exchange 210 as the private branch exchange of the primary system and the private branch exchange 220 as the private branch exchange of the secondary system (step S310).

1 is a block diagram showing a configuration of a system having a CTI server, a private branch exchange, and a private telephone according to an embodiment of the present invention. It is a flowchart which shows operation | movement of embodiment of this invention. It is a sequence diagram which shows the 1st Example of embodiment of this invention. It is a sequence diagram which shows the 2nd Example of embodiment of this invention. It is a sequence diagram (1/2) which shows operation | movement of the private branch exchange at the time of the failover of the private branch exchange by embodiment of this invention. It is a sequence diagram (2/2) which shows operation | movement of the private branch exchange at the time of the failover of the private branch exchange by embodiment of this invention.

Explanation of symbols

100 Computer 110 CTI Application 120 CTI Driver 200, 210, 220 Private Branch Exchange

Claims (4)

A primary system function unit for centralized control of a private telephone set under a private branch exchange functioning as a primary system and a private branch exchange functioning as a secondary system, and a private telephone set under the private telephone set Each of the plurality of private branch exchanges has a secondary system function unit that functions as a secondary system.
One private branch exchange functions as the primary system, and the other private branch exchange functions as the secondary system.
When a failure occurs in a certain private branch exchange that has functioned as a primary system, one of the private branch exchanges that functioned as a secondary system until then functions as a new primary system. A private branch exchange failover system,
Each private branch exchange acting as a secondary system knows the IP address of the private branch exchange currently acting as the primary system,
If the private branch exchange to which the computer telephony integration server can connect is functioning as a secondary system, the private branch exchange is not the private branch exchange that is functioning as the primary system, and the current primary system. And the IP address of the private branch exchange that functions as the computer telephony integration server,
The computer / telephony integration server having received the notification treats and connects the private branch exchange having the notified IP address as a private branch exchange functioning as a primary system. . When a failure occurs in one of the private branch exchanges functioning as the primary system, all the other private branch exchanges inquire about the priority order and respond to the priority order. Each of the devices determines whether its own priority is highest by comparing its own priority with the priority in response from all other private branch exchanges. Is determined that it will be a private branch exchange that will function as the primary system in the future, and that fact and its IP address are transmitted to all other private branch exchanges and all other private branch exchanges that have received it. The failover system according to claim 1, wherein the failover system recognizes that it is a private branch exchange that functions as a secondary system and retains the received IP address. A primary system function unit for centralized control of a private telephone set under a private branch exchange functioning as a primary system and a private branch exchange functioning as a secondary system, and a private telephone set under the private telephone set Each of the plurality of private branch exchanges has a secondary system function unit that functions as a secondary system.
One private branch exchange functions as the primary system, and the other private branch exchange functions as the secondary system.
When a failure occurs in a certain private branch exchange that has functioned as a primary system, one of the private branch exchanges that functioned as a secondary system until then functions as a new primary system. A private branch exchange failover method,
Each private branch exchange acting as a secondary system knows the IP address of the private branch exchange currently acting as the primary system,
If the private branch exchange to which the computer telephony integration server can connect is functioning as a secondary system, the private branch exchange is not the private branch exchange that is functioning as the primary system, and the current primary system. And the IP address of the private branch exchange that functions as the computer telephony integration server,
The computer telephony integration server that has received the notification treats and connects the private branch exchange having the notified IP address as a private branch exchange that functions as a primary system, and a failover method between the private branch exchanges . When a failure occurs in one of the private branch exchanges functioning as the primary system, all the other private branch exchanges inquire about the priority order and respond to the priority order. Each of the devices determines whether its own priority is highest by comparing its own priority with the priority in response from all other private branch exchanges. Is determined that it will be a private branch exchange that will function as the primary system in the future, and that fact and its IP address are transmitted to all other private branch exchanges and all other private branch exchanges that have received it. 4. The failover method according to claim 3, wherein the device recognizes that it is a private branch exchange that functions as a secondary system, and retains the received IP address.

Images