JP4810446B2 - Management system for managing communication device, communication device and management method thereof - Google Patents

Description

  The present invention relates to a management system for managing a communication device, a communication device and a management method therefor, and more particularly to a plurality of voice over IP (VoIP) voice IPs in an Internet Protocol (IP) telephony system. ) The present invention relates to a management system for managing terminals, its communication device and management method.

  In the IP telephony system, a multimedia gateway controller (MGC) controls a plurality of VoIP terminals via an IP network. Examples of the IP network include the Internet, an intranet, and a LAN (Local Area Network), and examples of the VoIP terminal include a media gateway, a media converter, and an IP phone.

  Conventionally, in an IP telephony system, a periodic health check from the MGC is performed as a means for diagnosing the normality of a VoIP terminal, and the period for performing the health check is uniquely determined regardless of the VoIP terminal. ing. The MGC issues diagnostic requests to the VoIP terminal at regular intervals, waits for a response from the target VoIP terminal, and detects the state of the VoIP terminal. When the MGC determines that the VoIP terminal is abnormal based on the response result of the target VoIP terminal, the MGC issues a reset instruction as a rescue measure to the corresponding VoIP terminal. The VoIP terminal that has received the reset instruction immediately executes the reset process and the registration process for the MGC, and restarts. Thereby, the VoIP terminal tries to recover from the abnormal state.

  However, in this method, the MGC performs a health check on a plurality of VoIP terminals. Therefore, when MGC determines that a plurality of VoIP terminals are abnormal at the same time due to excessive load on the connected network, the MGC resets the plurality of VoIP terminals to be controlled at about the same time. Issue instructions. Therefore, a plurality of VoIP terminals execute reset processing and registration processing all at once. As a result, the following problems are caused.

  First, transmission and reception of registration messages between MGC and a plurality of VoIP terminals causes further increase in network traffic. In addition, the processing load of MGC becomes excessive.

  Secondly, until the VoIP terminal completes the reset process and the registration process, the function of the corresponding VoIP terminal is disabled, so that a plurality of VoIP terminals are disabled at the same time. Therefore, when a redundant system or a communication layer is constructed with a plurality of VoIP terminals, there is a possibility that the advantage cannot be fully utilized.

  Patent Document 1 discloses a method for avoiding an increase in network traffic by changing the health check interval. In this method, the polling interval from the management device to the device to be managed is dynamically changed according to the traffic status of the network. The polling means that the management device issues a diagnosis request for the status of the management target device to the management target device at regular intervals, and the management target device returns a response to the diagnosis request. It is.

Japanese Patent Laid-Open No. 10-327148

  However, this method also has the same problem as described above when the management apparatus manages a plurality of management target apparatuses. In addition, when polling is performed at different timings among a plurality of management target devices, the polling interval must be dynamically changed for each of the plurality of management target devices. Therefore, this management device is required to perform a very complicated operation. In addition, the management device has a problem that the management of a plurality of devices to be managed is concentrated.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a management system, a communication device and a management method for efficiently managing a plurality of communication devices by distributing network traffic.

  A management system according to the present invention is a management system for managing a plurality of communication devices, a plurality of communication devices, and a management device for transmitting and managing periodic instructions to the plurality of communication devices; A network that connects the plurality of communication devices and the management device, each of the plurality of communication devices includes a first timer that counts a first set time until the self reboot process, When an abnormality is detected, the self is rebooted after the first set time has elapsed.

  A communication apparatus according to the present invention is a communication apparatus that is managed by receiving a periodic instruction from the outside via a network, and is a first timer that counts a first set time until the self reboot process When the abnormality is detected, the self is rebooted after the first set time has elapsed.

  The management method according to the present invention includes a plurality of communication devices, a management device that transmits and manages periodic instructions to the plurality of communication devices, and a network that connects the plurality of communication devices and the management device. A management method for managing a plurality of communication devices in a management system comprising: a plurality of communication devices, each of the plurality of communication devices counting a first set time until rebooting itself, In each of the devices, when an abnormality is detected, the self is rebooted after the first set time has elapsed.

  In the management system for managing communication devices according to the present invention, and the communication device and management method according to the configuration and method described above, each of the plurality of communication devices can be used even when the plurality of communication devices detect an abnormality at the same time. However, after counting the first set time, the self-reboot process is performed so that a plurality of communication devices are prevented from performing the reboot process at the same time. Therefore, the management system, the communication device, and the management method for managing the communication device according to the present invention have an effect of distributing network traffic and efficiently managing a plurality of communication devices.

  Next, the best mode for carrying out the present invention will be described in detail with reference to the drawings. In addition, the Example shown below shows a specific example so that this invention may be understood easily, and this invention is not necessarily limited only to the content of these Examples.

  Hereinafter, a management system, a communication device, and a management method for managing a communication device according to an embodiment of the present invention will be described in detail. In this embodiment, an IP (Internet Protocol) telephony system will be described as an example of a management system, a VoIP (Voice over IP) terminal as an example of a communication apparatus, and an MGC (Multimedia Gateway Controller) as an example of a management apparatus. . FIG. 1 is a block diagram showing a configuration of an IP telephony system according to an embodiment of the present invention. Hereinafter, description will be given based on this drawing. In FIG. 1, an IP telephony system 10 according to an embodiment of the present invention includes an MGC 2, a network 100, and VoIP terminals 1-1 to 1-n (where n is an integer of 2 or more). The MGC 2 performs call control of the VoIP terminals 1-1 to 1-n via the network 100. The network 100 includes the Internet, an intranet, a LAN (Local Area network), and the like. The VoIP terminals 1-1 to 1-n include a media gateway, a media converter, an IP phone, and the like.

  The VoIP terminals 1-1 to 1-n are connected to the same network and have the same or different functions. In addition, each of the VoIP terminals 1-1 to 1-n has a self-reboot function. The self-reboot function is a function that performs reset processing on the own terminal. In addition, each of the VoIP terminals 1-1 to 1-n has a function of uniquely determining a period until execution of self-reboot. This period is set by the self-reboot waiting timer as the first timer. Further, each of the VoIP terminals 1-1 to 1-n includes means for communicating between VoIP terminals having the same or different functions. The communication means has a function of exchanging the value of the self-reboot waiting timer of each terminal and setting the value different for each terminal.

  Each of the VoIP terminals 1-1 to 1-n further includes a health check instruction waiting function. The health check instruction waiting function is a function of waiting for a health check instruction from the MGC with respect to the terminal itself. The period for waiting for the health check is set as the second timer by the health check instruction waiting timer.

  The VoIP terminals 1-1 to 1-n are normally diagnosed by a regular health check from the MGC 2. When the MGC 2 recognizes any of the VoIP terminals 1-1 to 1-n as abnormal, the MGC 2 issues a reset instruction to the corresponding VoIP terminal. Then, the corresponding VoIP terminal that has received the reset instruction executes reset processing at a timing specific to the terminal itself, and restarts. Note that the own terminal-specific timing is the timing at which the self-reboot waiting timer value for each terminal times out. As described above, the self reboot waiting timer value is exchanged between VoIP terminals in advance, and is set to a different value for each terminal. Therefore, in the embodiment of the present invention, even when abnormality occurs simultaneously in the VoIP terminals 1-1 to 1-n, the timings at which the corresponding VoIP terminals perform the registration process on the MGC 2 are different from each other. Therefore, the load on the MGC 2 and the network 100 can be reduced.

  In addition, each of the VoIP terminals 1-1 to 1-n has a normal function of its own terminal, but when an abnormality associated with an excessive load on the connected network 100 is detected, reset processing is performed at a timing specific to the own terminal. It has a function of executing and restarting. The timing is set by a self-reboot waiting timer value that is different for each terminal. Therefore, in the embodiment of the present invention, the timing at which the VoIP terminals 1-1 to 1-n perform the registration process on the MGC 2 is different, and the load on the MGC 2 and the network 100 can be reduced.

  Furthermore, although the functions of each of the VoIP terminals 1-1 to 1-n are normal, when the MGC 2 detects an abnormality in the network 100, the MGC 2 issues a reset instruction to the VoIP terminals 1-1 to 1-n at the same time. To do. Alternatively, even if the functions of each of the VoIP terminals 1-1 to 1-n are normal, but the MGC2 erroneously recognizes the VoIP terminals 1-1 to 1-n and the network 100 as abnormal due to the abnormality, the MGC2 A reset instruction is issued simultaneously to the VoIP terminals 1-1 to 1-n. However, the VoIP terminals 1-1 to 1-n that have received the reset instruction execute the reset process at the timing specific to the terminal as described above, and restart the VoIP terminals 1-1 to 1-n. Therefore, the timings at which the VoIP terminals 1-1 to 1-n perform the registration process on the MGC 2 are different from each other. Therefore, in the embodiment of the present invention, the load on the MGC 2 and the network 100 can be reduced.

  Furthermore, since the timings at which the VoIP terminals 1-1 to 1-n perform the registration process on the MGC 2 are different, the VoIP terminals 1-1 to 1-n are prevented from being simultaneously disabled. There is also an effect.

  Hereinafter, a management system, a communication device, and a management method for managing the communication device according to the first embodiment of the present invention will be described in detail.

  FIG. 2 is a block diagram illustrating a configuration of the VoIP terminal according to the first embodiment of the present invention. Note that the VoIP terminals 1 to 1-n in FIG. In FIG. 2, the VoIP terminal 1 includes a CPU (central processing unit) 11, a main memory 12, a storage device 13, and a communication control unit 14. The main memory 12 stores a control program 12a executed by the CPU 11. The storage device 13 can be used as a work area when the CPU 11 executes the control program 12a. The communication control unit 14 controls communication via the network 100.

  The storage device 13 includes a terminal specific information storage area 131 and a terminal specific timer value storage area 132. The terminal unique information storage area 131 stores information unique to the VoIP terminal 1. The information unique to the VoIP terminal is, for example, a MAC (Media Access Control) address, an IP address, or the like. The terminal specific timer value storage area 132 stores a specific variable generated by performing arithmetic processing with an arbitrary function using information specific to the VoIP terminal 1. The unique variable is a self reboot waiting timer value unique to the terminal. That is, the self-reboot waiting timer value is first calculated from the information unique to the terminal stored in the terminal unique information storage area 131 and stored in the terminal unique timer value storage area 132 as the unique value of each terminal. Thereafter, the communication control unit 14 exchanges the self reboot waiting timer value with another VoIP terminal via the network 100. As a result, when the self-reboot waiting timer values are the same or approximate, the self-reboot waiting timer value is calculated again and set to a different value for each terminal. On the other hand, the health check instruction waiting timer value may be stored as a unique value of each terminal in the terminal unique information storage area 131 in consideration of the network state.

  In the VoIP terminal 1, each of the CPU 11, main memory 12, storage device 13, and communication control unit 14 is connected by an internal bus 110. The IP telephony system according to the first embodiment of the present invention has the same configuration as the IP telephony system 10 according to the embodiment of the present invention shown in FIG. Further, the configuration of each of the VoIP terminals 1-1 to 1-n in FIG. 1 is the same as that of the VoIP terminal 1 shown in FIG.

  Next, the operation of the IP telephony system according to the first embodiment of the present invention will be described below. FIG. 3 is a flowchart showing the exchange operation of the self-reboot waiting timer value in the VoIP terminal according to the first embodiment of the present invention. FIG. 4 is a first sequence chart showing an operation when an abnormality is detected in the VoIP terminal according to the first embodiment of the present invention. FIG. 5 is a second sequence chart showing an operation when an abnormality is detected in the VoIP terminal according to the first embodiment of the present invention. Hereinafter, the operation of the IP telephony system according to the first embodiment of the present invention will be described with reference to FIGS. The processing of the VoIP terminals 1-1 and 1-2 in FIGS. 3 to 5 is realized by the CPU 11 executing the control program 12a in the main memory 12. In addition, here, the VoIP terminals 1-1 and 1-2 are described as representatives among the VoIP terminals 1-1 to 1-n, but the same operation is performed in other VoIP terminals. Note that the VoIP terminal has the same or different functions.

  First, with reference to FIG. 3, the exchange operation of the self reboot waiting timer value in the VoIP terminals 1-1 and 1-2 of the IP telephony system 10 will be described below. Each of the VoIP terminals 1-1 and 1-2 has a function of judging an abnormality of the opposing MGC 2 or the connected network 100 and rebooting itself. More specifically, each of the VoIP terminals 1-1 and 1-2 has a function of uniquely calculating and determining the time until execution of self-reboot. The time is set in the terminal specific timer value storage area 132 as a self-reboot waiting timer value specific to the VoIP terminal. Note that this function may be configured to be set for each of the VoIP terminals 1-1 and 1-2 from the MGC 2 side when the VoIP terminals 1-1 and 1-2 are started up.

  The VoIP terminal 1-1 performs arithmetic processing with an arbitrary function using a pre-owned inherent variable, such as a MAC address or an IP address (step S1 in FIG. 3), and generates a self-reboot waiting timer value unique to the terminal. (Step S2 in FIG. 3). This self-reboot waiting timer value is used as a waiting time for performing a self-reboot. Here, consider a case where a plurality of VoIP terminals 1-1 to 1-n execute registration processing for the same MGC 2 at the same time. In that case, there is a possibility that the MGC 2 falls into an excessive load or the network 100 becomes an excessive load. In order to prevent this, the self-reboot waiting timer value must be generated in consideration of the time for each of the VoIP terminals 1-1 and 1-2 to execute the registration process.

  The plurality of VoIP terminals 1-1 and 1-2 arranged under the same MGC 2 have a function of exchanging self-reboot waiting timer values between the respective terminals. That is, each of the VoIP terminals 1-1 and 1-2 has information exchange means as means for mutually confirming the calculated self-reboot waiting timer value. This information exchanging means is realized by the CPU 11, main memory 12, storage device 13, and communication control unit 14 via the network 100.

  In each of the VoIP terminals 1-1 and 1-2, at the time of start-up, the terminals mutually communicate with each other by information exchange means regularly or irregularly and exchange the calculated self-reboot waiting timer value ( Step S3 in FIG. Here, when the self-reboot waiting timer value is the same or approximate (steps S4 and S11 in FIG. 3), each terminal recalculates the self-reboot waiting timer value according to an arbitrary predetermined function. Then, resetting is performed (steps S5 and S12 in FIG. 3). Each of the VoIP terminals 1-1 and 1-2 also exchanges the self-reboot waiting timer value with other VoIP terminals (not shown) (S6 and S13 in FIG. 3). On the other hand, when the self-reboot waiting timer value is not the same or approximate value (steps S4 and S11 in FIG. 3), each terminal does not perform resetting, and sets the self-reboot waiting timer value with other VoIP terminals. Exchange (S6, S13 in FIG. 3).

  Next, an abnormality detection method in the MGC 2 and the VoIP terminal 1-1 of the IP telephony system according to the first embodiment of the present invention will be described with reference to FIG.

  The VoIP terminal 1-1 starts a health check instruction waiting timer set in advance to a predetermined value (a1 in FIG. 4), and then shifts to a state waiting for a health check instruction from the MGC 2. If the VoIP terminal 1-1 receives a health check instruction from the MGC 2 corresponding to the self terminal within the time of the health check instruction waiting timer (a2 in FIG. 4), the VoIP terminal 1-1 clears the health check instruction waiting timer (FIG. 4). 4 a3), the function state is immediately determined (a4 in FIG. 4). Then, the VoIP terminal 1-1 returns a health check response together with information indicating the function state (a5 in FIG. 4).

  On the other hand, when the VoIP terminal 1-1 does not receive a health check instruction from the MGC 2 corresponding to its own terminal within the time of the health check instruction waiting timer preset to a predetermined value (a6, a7 in FIG. 4), The self-reboot waiting timer is started (a8 in FIG. 4). As a result, the VoIP terminal 1-1 shifts to a state waiting for a health check instruction from the MGC 2. Thereafter, when the VoIP terminal 1-1 receives the health check instruction within the self-reboot waiting timer time (a9 in FIG. 4), the health check instruction waiting timer and the self-reboot waiting timer are cleared (FIG. 4). a10, a11). Further, similarly to the above, the VoIP terminal 1-1 immediately determines the functional state (a12 in FIG. 4), and returns a health check response together with information indicating the functional state (a13 in FIG. 4). Then, the VoIP terminal 1-1 again activates the health check instruction waiting timer, and shifts to a state waiting for the health check instruction from the MGC 2.

  Furthermore, with reference to FIG. 5, the abnormality detection method in MGC2 and the VoIP terminal 1-1 of the IP telephony system by Example 1 of this invention is demonstrated.

  The VoIP terminal 1-1 starts a health check instruction waiting timer set in advance to a predetermined value (b1 in FIG. 5), and then shifts to a state waiting for a health check instruction from the MGC 2. If the VoIP terminal 1-1 receives a health check instruction from the MGC 2 corresponding to the terminal within the time of the health check instruction waiting timer (b2 in FIG. 5), the VoIP terminal 1-1 clears the health check instruction waiting timer (FIG. 5). 5 b3), the function state is immediately determined (b4 in FIG. 5). Then, the VoIP terminal 1-1 returns a health check response together with information indicating the function state (b5 in FIG. 5).

  On the other hand, when the VoIP terminal 1-1 does not receive a health check instruction from the MGC 2 corresponding to its own terminal within the time of the health check instruction waiting timer preset to a predetermined value (b6 and b7 in FIG. 5), The self-reboot waiting timer is started (b8 in FIG. 5). As a result, the VoIP terminal 1-1 shifts to a state waiting for a health check instruction from the MGC 2. When the VoIP terminal 1-1 does not receive a health check instruction from the MGC 2 corresponding to the self terminal within the time of the self reboot waiting timer (b9 and b10 in FIG. 5), the VoIP terminal 1-1 It is determined that there is an abnormality or an abnormality in the connected network 100. Then, the VoIP terminal 1-1 immediately executes self-reboot (b11 in FIG. 5), and then executes registration processing for the corresponding MGC 2 (b12 in FIG. 5). In this way, the VoIP terminal 1-1 performs restarting.

  As described above, in the first embodiment, when the VoIP terminal recognizes the abnormality when the MGC or the network is abnormal, the VoIP terminal executes the reset process at a timing specific to the terminal and restarts it. . Therefore, the timing at which the VoIP terminal performs registration processing on the MGC is different from each other. Therefore, in the first embodiment, it is possible to reduce the load on the MGC 2 and the network due to the registration processing of the VoIP terminal.

  Furthermore, in the first embodiment, since the VoIP terminal executes the reset process at a timing specific to the terminal itself, the timing at which the VoIP terminal becomes unusable is different. As a result, the first embodiment also has an effect of preventing all the lines from being unusable.

  Hereinafter, a management system, a communication device, and a management method for managing the communication device according to the second embodiment of the present invention will be described in detail.

  FIG. 6 is a sequence chart showing an operation in the VoIP terminal when an abnormality is detected by MGC according to the second embodiment of the present invention. With reference to FIG. 6, an abnormality detection method in the MGC 2 and the VoIP terminal 1-1 of the IP telephony system according to the second embodiment of the present invention will be described. The IP telephony system according to the second embodiment of the present invention has the same configuration as the IP telephony system 10 according to the embodiment of the present invention shown in FIG. The VoIP terminals 1-1 to 1-n constituting the IP telephony system 10 have the same configuration as the VoIP terminal 1 according to the first embodiment of the present invention shown in FIG. 6 is realized by the CPU 11 shown in FIG. 2 executing the control program 12a in the main memory 12.

  Next, the operation of the IP telephony system according to the second embodiment of the present invention will be described below. When the MGC 2 determines that the VoIP terminal 1-1 or the connected network 100 is abnormal, it issues a reset instruction as a remedy for the corresponding VoIP terminal 1-1 (c1 in FIG. 6). Upon receiving the reset instruction, the VoIP terminal 1-1 starts a self-reboot waiting timer that is preset to a predetermined value (c2 in FIG. 6). The VoIP terminal 1-1 waits for the time set by the self-reboot waiting timer (c3 in FIG. 6), and immediately executes a reset process (c4 in FIG. 6). Thereafter, the VoIP terminal 1-1 executes a registration process for the corresponding MGC 2 (c5 in FIG. 6). In this way, the VoIP terminal 1-1 performs restarting.

  As described above, in the second embodiment, when the MGC determines that the VoIP terminal or the network is abnormal, the MGC issues a reset instruction to a plurality of VoIP terminals simultaneously. However, each reset instruction target VoIP terminal performs a reset process at a specific timing and restarts. Therefore, the timing at which the VoIP terminal performs registration processing on the MGC is different from each other. Therefore, in the second embodiment, it is possible to reduce the load on the MGC and the network due to the registration processing of the VoIP terminal.

  Furthermore, in the second embodiment, since the VoIP terminal executes the reset process at a timing specific to the terminal itself, the timing at which the VoIP terminal becomes unusable is different. As a result, the second embodiment also has an effect of preventing all the lines from being in an unusable state.

  The above-described embodiment is a preferred embodiment of the present invention, and various modifications can be made without departing from the scope of the present invention. For example, the above-described embodiments may be used in combination.

It is a block diagram which shows the structure of the IP telephony system by embodiment of this invention. It is a block diagram which shows the structure of the VoIP terminal by Example 1 of this invention. It is a flowchart which shows the exchange operation | movement of the self reboot waiting timer value in the VoIP terminal by Example 1 of this invention. It is a 1st sequence chart which shows the operation | movement at the time of detecting abnormality in the VoIP terminal by Example 1 of this invention. It is a 2nd sequence chart which shows the operation | movement at the time of detecting abnormality in the VoIP terminal by Example 1 of this invention. It is a sequence chart which shows the operation | movement in the VoIP terminal at the time of detecting abnormality by MGC by Example 2 of this invention.

Explanation of symbols

1-1 to 1-n VoIP terminal 2 MGC
10 IP Telephony System 100 Network 1 VoIP Terminal 11 CPU (Central Processing Unit)
12 Main memory 12a Control program 13 Storage device 14 Communication control unit 110 Internal bus 131 Terminal specific information storage area 132 Terminal specific timer value storage area

Claims (27)

In the management system, a plurality of communication devices,
A management device that transmits and manages periodic instructions to the plurality of communication devices;
A network connecting the plurality of communication devices and the management device;
Each of the plurality of communication devices,
A first timer for counting a first set time until the self is rebooted, and when an abnormality is detected, after the first set time has elapsed, the self is rebooted ;
A communication control unit that exchanges the first set time between the plurality of communication devices via the network, and sets the first set time to be different from each other;
A management system for managing a communication device , wherein even when a reset instruction is received from the management device, the self is rebooted after the first set time has elapsed . Each of the plurality of communication devices is
A central processing unit, a main memory, and a storage device;
The self-reboot process is performed by the central processing unit executing a control program stored in the main memory based on the first set time stored in the storage device. The management system according to claim 1, wherein: Each of the plurality of communication devices is
A second timer for counting a second set time until waiting for a periodic instruction from the management device;
If the instruction does not arrive from the management device within the second set time,
3. The self-reboot process is performed when the instruction is not received before the first set time elapses after starting the first timer. Management system. If the instruction is not received from the management device within the second set time, or if the instruction is received before the first set time elapses, the second timer and the first 4. The management system according to claim 3 , wherein the value of the timer is cleared and the process returns to a state of waiting for a periodic instruction from the management apparatus. The anomaly management system according to any one of claims 1 to 4 wherein each of the plurality of communication devices, characterized in that it is detected by the instruction from the management apparatus does not reach. The anomaly management system according to any one of claims 1 to 5, wherein the management device is at least one of the anomalies and the network abnormality. The instruction and the management system according to any one of claims 1 to 6, characterized in that for each of the plurality of communication devices, is to instruct to perform normality judgment. The management apparatus management system according to any of claims 1 to 7, characterized in that it is the call control each of the plurality of communication devices. Wherein the plurality of communication devices, the management system according to any one of claims 1 to 8, characterized in that a VoIP (Voice Over Internet Protocol) terminal. The management apparatus management system according to any of claims 1 to 9, characterized in that a multimedia gateway controllers. The management system according to any one of claims 1 to 10 , wherein the network is an Internet protocol network. In a communication device managed by receiving periodic instructions from the outside via a network,
A first timer for counting a first set time until the self is rebooted ;
A communication control unit that exchanges the first set time with another communication device via the network ,
When an abnormality is detected, after the first set time has elapsed, the self is rebooted ,
The first set time is set to a value different from that of the other communication device;
The communication apparatus according to claim 1, wherein even when an external reset instruction is received, the self-reboot process is performed after the first set time has elapsed . The communication device further includes a central processing unit, a main memory, and a storage device,
The self-reboot process is performed by the central processing unit executing a control program stored in the main memory based on the first set time stored in the storage device. The communication device according to claim 12, characterized in that: A second timer for counting a second set time until waiting for a periodic instruction from the outside;
If the instruction does not arrive from the outside within the second set time, start the first timer, and if the instruction is not received before the first set time elapses, The communication apparatus according to claim 12 or 13 , wherein the communication apparatus reboots itself. If the instruction is not received from the outside within the second set time, the first timer is started, and if the instruction is received before the first set time elapses, 15. The communication device according to claim 14, wherein the values of the timer No. 2 and the value of the first timer are cleared and the routine returns to a state of waiting for a periodic instruction from outside. The anomaly, a communication device according to any one of claims 12 to claim 15, characterized in that it is detected by the instruction from the external does not reach. The instruction and the communication apparatus according to any one of claims 12 to claim 16, characterized in that to the communication device, and to instruct to perform health diagnostics. Communication apparatus according to any one of claims 12 to claim 17, characterized in that it is a call control from the outside. The communication device, VoIP communication apparatus according to any one of claims 12 to claim 18, characterized in that a (Voice Over Internet Protocol) terminal. In a management system comprising a plurality of communication devices, a management device that transmits and manages periodic instructions for the plurality of communication devices, and a network that connects the plurality of communication devices and the management device,
In each of the plurality of communication devices, the first set time until the self reboot process is counted,
In each of the plurality of communication devices, when an abnormality is detected, after the first set time has elapsed, the self is rebooted ,
The first set time is exchanged between the plurality of communication devices via the network, and the first set time is set to be different from each other,
Sending a reset instruction from the management device to each of the plurality of communication devices,
In each of the plurality of communication devices, the reset instruction is received,
The management method for managing the plurality of communication devices, wherein the plurality of communication devices that have received the reset instruction perform a reboot process on the self after the first set time has elapsed . 21. The management method according to claim 20 , wherein the reboot process is performed by a central processing unit executing a control program based on the first set time. In each of the plurality of communication devices, a second set time until a periodic instruction is waited from the management device is counted,
If the instruction is not received from the management device within the second set time, the first set time is counted and the instruction is not received before the first set time elapses. The management method according to claim 20 or 21 , wherein the self is rebooted. When the instruction is not received from the management device within the second set time, the first set time is counted and the instruction is received before the first set time elapses. 23. The management method according to claim 22 , wherein the count of the second set time and the first set time is returned to zero, and the process returns to a state of waiting for a periodic instruction from the management apparatus. The management method according to any one of claims 20 to 23 , wherein each of the plurality of communication devices is detected when the instruction does not reach from the management device. The management method according to any one of claims 20 to 24 , wherein the abnormality is at least one of an abnormality of the management device and an abnormality of the network. The instruction and the management method according to any one of claims 20 to claim 25, characterized in that for each of the plurality of communication devices, is to instruct to perform normality judgment. The management device management method according to any one of claims 20 to claim 26, characterized in that it is the call control each of the plurality of communication devices.

Images