JPH05336559A - Automatic private branch exchange - Google Patents

Abstract

PURPOSE:To relieve the call without interrupting current even if any fault occurs on each interface part under the control of a main control part even in the automatic private branch exchange of decentralized control system. CONSTITUTION:If a fault occurs on line wire interface parts 29 and 30 or extension interface parts 19 and 20 under the control of the main control part, a fault call storage part 43 in which the number of calls in a calling state at the time of the fault occurrence is counted through the faulty interface part and stores the counted numbers indicates the fault occurrence state of the interface part; and a fault call flag 44 which makes only the on-hook detection of a calling party effective for the on-hook detection of a fault call are provided.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a private automatic branch exchange having a failure recovery function.

[0002]

2. Description of the Related Art FIG. 3 is a block diagram showing the structure of a conventional private automatic branch exchange. Hereinafter, a configuration of a conventional private automatic branch exchange will be described with reference to the drawings. 51 to 54
Are internal telephones, 55 to 58 are external telephones, 59 is an internal automatic exchange main body for performing exchange processing, and 60 and 61 are the internal telephones 51 to 52 and 53.
An extension interface unit connected to ~ 54 for hook detection and control of extension telephones, control units 62, 63 for controlling extension telephones, data transmission units 64, 65 for transmitting / receiving data, extension telephone control It is composed of storage units 66 and 67 and timers 68 and 69 for storing control data required in the case. Reference numerals 70 and 71 denote external line interface units that are connected to the external lines 55 to 56 and 57 to 58 to take electrical interfaces and control the internal lines.
Similarly to 0 and 61, control units 72 and 73, data transmission units 74 and 75, a storage unit 76 that stores control data necessary for outside line control,
It consists of 77 and timers 78 and 79. Reference numeral 80 is a data transmission unit capable of transmitting / receiving data to / from the extension line interface unit and the external line interface unit, 81 is a communication path unit for switching a voice transmission line, and 82 is a center for controlling both the interface units to perform exchange processing. The control unit 83 is a storage unit that holds the control data used in both the interface units and a call control task that carries out call management (a task is a program divided by function) and a diagnostic task program that performs fault / diagnostic management. is there.

With respect to the conventional private automatic branch exchange constructed as described above, an example of a failure in the case where the control data stored when the respective interface units are started up and the stored control data is destroyed occurs is first described in (1). Describe the transmission procedure of various control data required by each interface unit in advance, (2)
A method of detecting a failure of control data destruction in each interface unit and a method of expanding recovery processing will be described.

(1) A procedure for transmitting control data to each interface unit will be described with reference to FIG. When the power of the main automatic branch exchange 59 is turned on, the control unit 82 stores in the storage unit.
The program in 83 is read and executed sequentially. The call control task and all interface units are in a non-operational state and wait for activation from the diagnostic task (S1). The diagnostic task activates all interface units in the activation wait state (S2). All the activated interface units diagnose whether or not the storage unit is readable and writable (S3), and wait for a storage unit diagnosis request from the diagnostic task via the data transmission unit. When the diagnostic task sends an operation start notification to the call control task in the activation message waiting state (S4), the call control task changes the state from the non-operation state to the idle state and starts the operation (S5).
Next, the diagnostic task shifts to the diagnostic processing of each activated interface unit, and data corresponding to each interface unit is designated as NG (S6), and the storage unit 83
Is set (when NG is set, the call control task excludes the interface unit from the operation target), and a storage unit diagnosis request is transmitted (S7). The interface unit that has received the storage unit diagnosis request transmits a storage unit diagnosis response corresponding to the diagnosis result to the diagnosis task (S8). Diagnosis result is OK
If so, the diagnostic information OK is set in the storage unit 83 (S1
At the same time, the control data corresponding to each interface unit is read from the storage unit 83 (S11) and transmitted to the interface unit (S12), and the interface unit receiving the control data writes the control data to the corresponding storage unit (S11). S13).
The diagnostic task that has completed the transmission of control data to the interface unit sends an operation start notification (S14), starts the operation of the interface unit, and calculates the check sum (calculates the sum of the control data) of the control data. Then, the data is written in the corresponding storage unit (S15). The diagnostic task is to complete the diagnosis of all interface parts and the transmission of the operation start notification (S16).
Then, the operation is started by shifting to the empty state (S17).

(2) A fault detection / restoration processing method of control data destruction in each interface section will be described with reference to FIG. The interface unit activates a corresponding timer for control data diagnosis during operation (S21). When the time out occurs, the check sum is calculated again (S2
2, S23), comparing with the data written in the storage unit,
If it is OK, the process of activating the timer is repeated again, but if it is NG, the control data failure notification is transmitted to the diagnostic task via the corresponding data transmission unit (S25). Upon receiving the control data failure notification, the diagnostic task sets the diagnostic information corresponding to the corresponding interface unit to NG (S2
6) The interface unit in which the failure has occurred is disabled, the interface unit failure is transmitted to the call control task (S27), and all calls through the failed interface unit are forcibly terminated (S28, S29). To restore the fault interface part, follow the startup procedure already described in (1).
Processing such as restarting was being executed.

[0006]

However, in the above-mentioned conventional private automatic branch exchange, when a failure occurs in the control data of the interface section, it is considered that the normal processing cannot be executed thereafter, and all the data are transferred through the failure interface section. Therefore, there is a problem in that the call in progress is suddenly terminated because the call is forcedly terminated.

SUMMARY OF THE INVENTION The present invention solves the above-mentioned conventional problems, and an object of the present invention is to provide a private automatic branch exchange capable of executing failure processing without affecting the communication state even if a failure occurs in the interface section. It is what

[0008]

In order to achieve the above object, the present invention has a fault call storage unit for counting the number of calls in a call state via a fault interface unit and a fault call flag for storing a fault occurrence state. Is provided with a storage unit.

[0009]

With the above construction, even if a failure occurs in the interface section, it becomes possible to protect a call in a call state when the failure occurs.

[0010]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing the configuration of a private automatic branch exchange according to an embodiment of the present invention. In FIG. 1, 10 to 13 are extension telephones, 14 to 17 are outside lines, 18 is an automatic exchange main body for performing exchange processing, and 19 and 20 are connected to the extension telephones 10 to 11 and 12 to 13 to hook the extension telephones. An extension interface unit that performs detection and control, stores control units 21 and 22 that controls extension telephones, data transmission units 23 and 24 that enables data transmission / reception, and stores various control data necessary for extension telephone control. Storage unit 25, 26,
It consists of timers 27 and 28. 29 and 30 are the outside lines 14 to
An external line interface unit that is connected to 15 and 16 to 17 and takes an electrical interface to perform control. Like the internal line interface units 19 and 20, control units 31 and 32, data transmission units 33 and 34, and external line control units. It is composed of storage sections 35 and 36 and timers 37 and 38 for storing various control data that are necessary at the time. 39 is a data transmission unit that enables data transmission / reception with the extension interface unit and the external interface unit, 40 is a communication path unit that switches the voice transmission line, and 41 is a center that controls both interface units and performs exchange processing. The control unit 42 is a call control task responsible for various control data and call management used in the both interface units (a task is a program divided by function) and a failure /
A storage unit that holds a diagnostic task program that performs diagnostic management, 43 is a part of the storage unit 42, and a fault call storage unit that stores information for determining whether or not a fault processing transition is possible when a fault occurs, 44 is the It is a fault call flag that stores the fault occurrence status of both interface units. FIG. 2 is a sequence chart showing the processing from the detection of a failure to the start of the diagnostic processing.

Regarding the private automatic branch exchange constructed as described above, under the condition that the outside line 16 and the extension telephone 10 are in a call and the outside line 17 is unused, the control data stored in the storage part 36 of the outside line interface part 30. The operation will be described below assuming that is destroyed for some reason. When the control data is destroyed, the timer 38 is activated to periodically execute the control data diagnostic process, and the diagnostic result becomes NG, and the external line interface unit 30 transmits the diagnostic task to the data transmission units 34 and 39.
A control data failure notification is transmitted via (S31). The diagnostic task that received the control data failure notification is stored in the storage unit 42.
The diagnostic information corresponding to the inside external line interface section 30
By setting it to G (S32), the call control task does not use the external line interface unit 30 in which the fault has occurred, and an interface fault request is sent to the call control task to notify that the external line interface unit 30 has failed. It is transmitted (S33). The call control task that has received the interface failure request manages the number of calls in the call state (1 in this assumption) calculation by software via the outside line interface section 30 by software. This is done by adding the number of calls in progress (S34). In addition, the call transition processing is performed only when the on-hook detection of the call partner (extension telephone 10 in this assumption) is performed, and the on-hook detection message is sent to the diagnostic task when the on-hook detection message is received. Settings are made (S35), and an interface fault response with the number of active calls added is sent to the diagnostic task as a response message (S36). The diagnostic task that received the interface fault response is
The number of calls is set in the fault call storage unit 43 (S37), and the termination of the fault call is waited (S38). On-hook of the extension telephone 10 is detected by the extension interface unit 19 and transmitted to the call control task via the data transmission units 23 and 39. The call control task that has received the on-hook detection message (S43) refers to the faulty call flag 44 and sets the flag, and therefore sends the on-hook detection message to the diagnostic task.
After (S45), the faulty call flag 44 is reset (S46),
An end call process is executed to disconnect the call path between the outside line 16 and the extension telephone 10 by controlling the call path unit 40 (S47), and returns to an idle state.
(S48). On the other hand, the diagnostic task that received the on-hook detection message sets the number of failed calls in the failed call storage unit 43 to 1
If the number of faulty calls becomes 0 (S39) and the number of faulty calls becomes 0, the faulty interface unit shown in the conventional example is restarted and the process shifts to the diagnostic process (S40, S41).

[0012]

As described above, according to the present invention, even if a failure occurs in the interface section accommodated in the private automatic branch exchange,
Since the diagnosis / recovery process can be performed without affecting the call in the call state, there is an effect that the call in progress does not suddenly end.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a private automatic branch exchange according to an embodiment of the present invention.

FIG. 2 is a sequence chart showing processing from failure detection to diagnosis processing start-up according to an embodiment of the present invention.

FIG. 3 is a block diagram of a conventional private automatic branch exchange.

FIG. 4 is a sequence chart showing a startup process in a conventional private automatic branch exchange.

FIG. 5 is a sequence chart showing processing from failure detection to diagnosis processing activation in a conventional private automatic branch exchange.

[Explanation of symbols]

10, 11, 12, 13, 51, 52, 53, 54 ... Extension telephone, 14,
15, 16, 17, 55, 56, 57, 58 ... Outer line, 18, 59 ... Private branch exchange main unit, 19, 20, 60, 61 ... Extension interface unit, 21, 22, 31, 32, 41, 62, 63 , 72, 73, 82 ... Control unit, 23, 24, 33, 34, 39, 64, 65, 74, 75, 80 ... Data transmission unit, 25, 26, 35, 36, 42, 66, 65, 76, 77,
83 ... storage unit, 27, 28, 37, 38, 68, 69, 78, 79 ... timer, 29, 30, 70, 71 ... external line interface unit, 4
0, 81 ... Call path section, 43 ... Fault call storage section, 44 ... Fault call flag.

Claims (1)

[Claims] 1. An external line interface unit that controls an interface with an external line, an internal line interface unit that controls an interface with an internal telephone, a storage unit that holds various control information necessary for exchange processing, the external line interface unit, and the internal line interface. A private automatic exchange having a control unit for controlling a storage unit and a storage unit, and a data transmission unit capable of transmitting and receiving control data among the external line interface unit, the internal line interface unit, and the control unit, in the storage unit, By providing a fault call flag that stores a fault occurrence status in the external line interface unit and the extension line interface unit, and a fault call storage unit that counts the number of calls in the faulty external line interface unit or extension interface unit, Interface part Or an internal interface section fails, the interface section (external interface section or internal interface section) where the failure occurred
An automatic private branch exchange, characterized in that, when all the calls related to (1) are terminated, recovery control is performed on the interface part in which the failure has occurred to prevent interruption of the call during the call when a failure occurs.