JP2005348143A - Ip telephone service method and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an IP telephone service method and system capable of providing IP telephone services to users continuously, even when maintenance operation such as software update is performed. <P>SOLUTION: The IP telephone service method and system are a method which selectively makes one out of a plurality of call control servers to respond to a service request each time when a service request is made from a telephone terminal, and provides IP telephone services to the telephone terminal, and a system comprising the plurality of call control servers. Responding to an update request for updating software installed in the plurality of call control servers, at least one out of the plurality of call control servers is left as a response permitted server, the others are made to be response inhibit servers, and the response inhibit servers are inhibited to respond to a new service request from the telephone terminal. After waiting for the completion of IP telephone services being already in the course of providing by the response inhibit servers, the software to be installed in the response inhibit servers is updated. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an IP telephone service method and system for providing an IP telephone service to a telephone terminal using a call control server, and in particular, updates software provided in the call control server in parallel with the IP telephone service. The present invention relates to an IP telephone service method and system.

  As a method for performing software update without interrupting service in a conventional telephone exchange network, there is a method entitled “Call Relief Method at File Replacement” (see Patent Document 1). This disclosed method is configured by a method of selecting a connection destination processor for each line. However, although this method can be applied to an existing telephone exchange network, it cannot be applied to a connectionless IP telephone network.

On the other hand, in an information communication system arranged on a connectionless LAN, a plurality of call control servers are divided into an active system and a standby system, and when a failure occurs, the standby call control server is switched to the active system. A configuration is disclosed in which call control is continued regardless of the failure (see Patent Document 2). Therefore, it is conceivable to apply this method to the IP telephone service system in order to update the software by regarding the software update of the call control server as one failure state.
Japanese Patent Laid-Open No. 05-327872 JP 2001-3186194 A

  In application of such a conventional method, in order to update the installed software, all calls in a call must be disconnected when switching from the active server to the standby server. This is because the standby server cannot recognize the state of the active call that is recognized by the active server, and the in-call state in order to avoid a mismatch between the state recognized by the standby server and the state of the terminal. This is because all calls must be disconnected. However, such a forced interruption of a call during a call significantly deteriorates the service quality of the IP telephone service.

  An object of the present invention is to provide an IP telephone service method and system capable of continuously providing an IP telephone service to a user even during maintenance operations such as software update.

  The IP telephone service method according to the present invention is an IP telephone service method for selectively responding one of a plurality of call control servers for each service request from a telephone terminal and providing the telephone terminal with the IP telephone service. Yes, in response to an update request for updating software provided in the plurality of call control servers, at least one of the plurality of call control servers is left as a response permission server, and the other is set as a response prohibition server. A setting step for setting a setting for prohibiting the response of the response prohibition server to the new service request, and an update for updating the software of the response prohibition server after waiting for completion of the IP telephone service already provided by the response prohibition server And a step.

  The IP telephone service system according to the present invention includes a plurality of call control servers, and selectively responds to one of the plurality of call control servers for each service request from the telephone terminal to In response to an update request for updating software provided in the plurality of call control servers, at least one of the plurality of call control servers is left as a response permission server, and the other is responded A setting means for setting a prohibition server to prohibit the response prohibition server from responding to a new service request from the telephone terminal, and waiting for completion of the IP telephone service already provided by the response prohibition server, Update means for updating software of the prohibited server.

  According to the IP telephone service method and system of the present invention, when software update is necessary, one of a plurality of call control servers is set as a response prohibition server, and a new service request is sent to the response prohibition server. In addition to the prohibition, a configuration is provided in which software of the response prohibition server is updated after completion of a call already in service. By performing such processing also for other call control servers, software update of the entire system is achieved. As a result, it is possible to continue to provide the IP telephone service to the user even during maintenance operations such as software updates.

Embodiments of the present invention will be described in detail with reference to the accompanying drawings.
<First embodiment>
FIG. 1 shows a first embodiment of the present invention and shows the configuration of the entire system. In the IP telephone system according to the present invention, MGC servers 101 and 102 that provide an IP telephone service as call control servers are connected to a plurality of TAs (Terminal Adapters) 111 to 11n (n is a positive number) via an IP network 121. ing. Each of TAs 111 to 11n is a terminal adapter that relays an analog telephone, to which an analog telephone is connected. Each of TAs 111 to 11n communicates with MGC servers 101 and 102 using a function for interconverting voice and IP packets of analog telephones and MGCP (Media Gateway Control Protocol) to provide IP telephone services to analog telephones. With functions. An extended DNS server 121 is connected to the IP network 122. The extended DNS server 121 has a DNS (Domain Name System) function that provides mutual conversion between a host name and an IP address in response to a request from a client terminal.

  The MGC servers 101 and 102 have a function of providing an IP telephone service by performing call control using MGCP for each of the TAs 111 to 11n. The two servers of the MGC servers 101 and 102 are normally in a response permission state in which one of them permits the provision of IP telephone service (hereinafter referred to as an ACT state, and a server in such a state is also referred to as an ACT system) The other is operated in a response prohibition state (hereinafter referred to as an SBY state, and a server in such a state is also referred to as an SBY system) in which new provision of IP telephone service is prohibited. If a failure occurs in one MGC server in the ACT state and the provision of the IP telephone service becomes impossible, the MGC server in the SBY state enters the ACT state and takes over the provision of the previous IP telephone service. Operation is done. As shown in FIG. 1, it is assumed that different IP addresses “ABCD” and “ABCE” are assigned to the MGC servers 101 and 102, respectively, and the values of A to E are in the range of 0 to 255. It is a positive number.

  FIG. 2 shows a more detailed functional configuration of the MGC servers 101 and 102 shown in FIG. The MGC servers 101 and 102 include an IP interface 131, an ACT-SBY management unit 132, call control software 133, and a software update unit 134. The IP interface 131 is an interface that connects the IP network 122 and each functional unit included in the apparatus. The ACT-SBY management unit 132 performs control of the ACT-SBY state of the device itself, which is an MGC server, monitors the ACT state of other MGC servers, which are other devices, and manages software update start and end. . In particular, the ACT-SBY management unit 132 has a function of transmitting an ACT notification to the extended DNS server 121 when the apparatus itself transitions from the SBY state to the ACT state due to software update or occurrence of a failure. This ACT notification includes information giving the IP address and host name of the MGC server itself. Note that in this embodiment, the same host name is assigned to each of the MGC servers 101 and 102.

  The call control software 133 is software that provides call control as an IP telephone service to the TAs 111 to 11n via the IP interface 131 and the IP network 122. “Ver.N” appended to the call control software 133 in this figure means that the version number of the call control software 133 is the version number represented by the numerical value N. The IP telephone service protocol executed by the call control software 133 is, for example, a protocol compliant with MGCP (Media Gateway ControI Protocol, see RFC 2705 of IETF). The software updating unit 134 has a function of updating the call control software 133 and can be realized by using an FTP (Fi1e Transfer Protocol 1, refer to RFC 959 of IETF) method.

  FIG. 3 shows a more detailed functional configuration of the extended DNS server 121 shown in FIG. The extended DNS server 121 includes a server list 141, a DNS service unit 142, a server state management unit 143, and an IP interface 144.

  The server list 141 is a table that describes the correspondence between host names and IP addresses. The DNS service unit 142 provides a DNS service (see RFC 1034, RFC 1035, RFC 1123, RFC 2181 of IETF) to other devices on the IP network 122 based on the information in the server list 141. The server state management unit 143 receives ACT notifications from the MGC servers 101 and 102 and updates information in the server list 141. The IP interface 144 is an interface that connects the IP network 122 and each functional unit. As the feature of the extended DNS server 122 in the present embodiment, the extended DNS server 122 includes the MGC server 101 and 102 in the ACT state and the host name (here, mgc1.m) in addition to the normal DNS service function. xxx.co.jp) mapping function.

  FIG. 4 illustrates a setting example of the server list 141 illustrated in FIG. In this example, the MGC server 101 is assumed to be an ACT state MGC server, and the IP address “A.B.C.D” of the MGC server 101 is assigned to the host name “mgc1.xxx.co.jp”. On the other hand, the MGC server 102 is an MGC server in the SBY state, and no host name is assigned to the IP address “A.B.C.E” of the MGC server 102. As illustrated, the server list 141 further includes other MGC servers in the ACT state (see FIG. 5) for the other host names “mgc2.xxx.co.jp” and “mgc3.xxx.co.jp”. IP addresses “ABCF” and “ABCG” (not shown in FIG. 1) can also be set.

  With respect to the states of the MGC servers 101 and 102, each of the TAs 111 to 11n designates an MGC server that regularly provides a telephone service using only the host name. For example, it is assumed that an analog telephone connected to the TA 111 makes a call. In this case, the TA 111 inquires of the extended DNS server 121 about the IP address of the MGC server using the host name “mgc1.xxx.co.jp”. The extended DNS server 121 maps the host name and the IP address of the MGC server in the ACT state, and returns it to the TA 111. That is, the IP address “A.B.C.D” of the MGC server 101 in the ACT state is returned to the host name “mgc1.xxx.co.jp”. As a result, the IP address passed from the extended DNS server 122 to each of the TAs 111 to 11n is always the IP address of the MGC server in the ACT state. It should be noted that each of TAs 111 to 11n can receive calls from either MGC server 101 or 102.

  FIG. 5 shows a processing flow of the MGC server. First, in step S01, the MGC server is activated. In step S02, it is determined whether the MGC server is activated as an SBY system or an ACT system. The setting of whether to start in the ACT system or the SBY system at the time of startup is described in, for example, the setting file of the MGC server. When starting in the ACT system, the process proceeds to step S08, and when starting in the SBY system, the process proceeds to step S03.

  In step S03, it is determined whether to end the MGC server. If it is determined in step S03 that the process ends (Y), the process proceeds to the process in step S17. If it is determined in step S03 that the process does not end (N), the process proceeds to step S04. In step S04, the SBY-ACT management unit of the MGC server checks the status by accessing the SBY-ACT management unit of the other MGC server. In step S05, the result of the status check of the other MGC server is determined. If the SBY-ACT management of the other MGC server does not respond (Y), it is determined that a failure has occurred in the other MGC server, and the process proceeds to step S08. When another system MGC server responds (N), it moves to process S06. In step S06, it is determined whether there is a call control software update request. For example, if a software update instruction command is input from the outside via the software update unit (Y), the process proceeds to step S07. If nothing is input from the outside (N), the process returns to step S03. In step S07, the call control software is updated. When the software update is completed, the process proceeds to step S08.

  In step S08, IP phone service provision is started. After the process S08, a new call can be accepted. In step S09, the extended DNS server is notified that the ACT system has been started. As a result, new calls from the TA are transmitted to the local MGC server thereafter. In step S10, an IP telephone service is provided. In step S11, it is determined whether to end the MGC server. If it is determined in the process S11 that the process is to be ended (Y), the process proceeds to the process S17, and the MGC server executes an end process. If it is determined not to end in the process S11 (N), the process proceeds to the process S12. In step S12, it is determined whether there is a call control software update request. For example, when a software update instruction command is input from the outside via the software update unit (Y), the process proceeds to step S13. If nothing is input from the outside (N), the process returns to step S10.

  In step S13, it is confirmed whether or not there is a call managed by the local MGC server. If there is a call in the process S18, the process proceeds to the process S14 to continue to provide the IP telephone service. In order not to affect the IP service, the MGC server repeats steps S18 to S14 until all managed calls are completed. When all the managed calls are finished, the process proceeds to step S15. In step S15, the IP telephone service is terminated. In step S16, the call control software is updated. When the software update is completed, the process proceeds to step S03 and operates as an SBY MGC server.

  FIG. 6 shows a processing flow of the extended DNS server. First, in step S21, the extended DNS server is activated. In step S22, it is determined whether or not to terminate the extended DNS server. If there is an end instruction (Y), the process proceeds to the end process of step S23, the DNS service is stopped, and the extended DNS server is turned off. If there is no end command (N), the process proceeds to the process after process S24.

  In step S24, it is determined whether or not the IP interface of the extended DNS server has received an ACT notification from the MGC server. If received (Y), the process proceeds to step S25. Steps S25 to S26 are processing of the extended DNS server when the ACT system of the MGC server is switched due to a failure or the like, and when the software of the MGC server is updated. In step S25, the server state management unit receives the ACT notification from the IP interface, analyzes the ACT notification, and acquires the IP address and host name included in the ACT notification. Next, in step S26, the server state management unit extracts the entry corresponding to the host name of the ACT notification from the server list, and changes the IP address to the IP address of the ACT notification. If there is no entry in the server list, a new entry is generated. As a result of the above step S26, the entry in the server list is updated. After that, when the TA inquires the extended DNS server for the host name, the updated IP address is returned. When the process S26 is completed, the process returns to the process S22.

  If it is determined in step S24 that an ACT notification is not received (N), the process proceeds to step S27, where it is determined whether a host name has been inquired from TA. In the process S27, when there is no inquiry (N), the process returns to the process S22. If there is an inquiry (Y) in the process S27, the process proceeds to the process S28. In step S28, the DNS service unit searches the server list using the host name inquired from the TA as a key, returns the IP address of the corresponding entry to the TA, and returns to step S22. The above is the processing of the extended DNS server.

  FIG. 7 shows a processing procedure of the entire system at the time of software update in the first embodiment. Here, initially, it is assumed that the MGC server 101 is in the ACT state and the MGC 102 is in the SBY state. At this time, in step S31, a call is made from TA 113 to TA 114. Next, in step S32, the TA 113 inquires the extended DNS server 121 about the IP address of the MGC server. Next, in step S33, the extended DNS server 121 returns the IP address of the MGC server 101 in the ACT state. In step S35, in response to the response, the TA 113 and TA 114 access the MGC server 101 using the IP address and receive a call connection service. During this time, in step S34, the MGC server 101 performs the service according to a procedure based on MGCP. As a result, a call can be made between TA 113 and TA 114.

  At this time, it is assumed that it is necessary to update the software of the MGC server from ver.N to ver.N + 1. Since the MGC server 102 is in the SBY state, the software can be updated without affecting the IP telephone service. Therefore, in step S36, the MGC server 102 updates the call control software to be installed. After the software update, in step S37, the MGC server 102 enters the ACT state, and transmits an ACT notification to the extended DNS server 121. The ACT notification includes the IP address “A.B.C.E” and the host name “mgc1.xxx.co.jp”.

  In step S38, upon receiving the ACT notification, the extended DNS server 121 updates the IP address of the entry “mgc1.xxx.co.jp” from “A.B.C.D” to “A.B.C.E”. In this state, it is assumed that TA 115 makes a call (call) in step S51. Next, in step S52, the TA 115 inquires the extended DNS server 121 about the IP address of the MGC server. Next, in step S53, the extended DNS server 121 responds with the IP address of the MGC server 102 in the ACT state. As a result, the TA 115 thereafter accesses the MGC server 102 as an MGC server that provides a telephone service. An IP telephone service to the TA 115 is provided from the MGC server 102. The extended DNS server 121 always returns the IP address “A.B.C.E” of the MGC server 102 in response to inquiries from the TAs 111 to 11n related to new calls that occur thereafter. Therefore, it should be noted that a telephone service request by a new call does not occur to the MGC server 101.

  On the other hand, in step S39, the MGC server 101 determines whether there is a call in progress. In step S40, the MGC server 101 waits until the call is ended when there is a call in progress. On the other hand, when there is no call in progress, that is, when all calls using the MGC server 101 are completed, the MGC server 101 enters the SBY state. At this time, since the MGC server 101 does not accept a new call, the service is not affected even if the MGC server 101 enters the SBY state. If all the calls are completed, the call control software of the MGC server 101 is updated in step S41. Thereafter, the service is continued with the MGC server 101 as the SBY system and the MGC server 102 as the ACT system. With the above operation, software update can be realized without interrupting the service.

As described above, in the first embodiment, the duplicated MGC server and the extended DNS server are linked to operate the duplicated MGC server at the time of software update. By returning the IP address of the MGC server operated with the new version of software to the TA, the software can be updated without interruption of service. In the present embodiment, there is one pair of MGC servers with a duplex configuration, but the present invention can be applied even when there are a plurality of pairs of MGC servers with a duplex configuration.
<Second embodiment>
FIG. 8 shows the configuration of the entire system in the second embodiment. As in the first embodiment, the configuration of the second embodiment includes a plurality of MGC servers 201, 202, 203, and 204, TA 211 to 21n, and an extended DNS server 222 that provide IP telephone services via an IP network 221. Connected. The difference from the first embodiment is that it is composed of three or more MGC servers. In the second embodiment, unlike the first embodiment, the MGC server does not have a duplex configuration, and three MGC servers 201, 202, and 203 in the ACT state, and one MGC server 204 in the SBY state It is the composition which consists of. The IP addresses “ABCD”, “ABCE”, “ABCF”, and “ABCG” are assigned to the MGC servers 201, 202, 203, and 204, respectively. Assume that “mgcl.oki.co.jp”, “mgc2.oki.co.jp”, and “mgc3.oki.co.jp” are allocated as host names. Further, the detailed functional configuration of each device including the MGC servers 201, 202, 203, and 204 and the extended DNS server 222 is the same as that of the first embodiment (see FIGS. 2 to 4).

  FIG. 9 shows a processing flow of the MGC server in the second embodiment. First, in step S61, the MGC server is activated. In step S62, it is determined whether the MGC server is activated as an SBY system or an ACT system. The setting whether to start in the ACT system or the SBY system at the time of start-up can be realized, for example, by describing it in the setting file of the MGC server. When starting in the ACT system, the process proceeds to step S67, and when starting in the SBY system, the process proceeds to step S63.

  In step S63, it is determined whether to end the MGC server. When the process ends (Y), the process proceeds to the end process of step S78. If the process does not end (N) in the process S63, the process proceeds to the process S64. In step S64, it is determined whether to update the software. For example, when a software update instruction command is input from the outside via the software update unit (Y), the process proceeds to step S65. If nothing is input from the outside (N), the process returns to step S63. In step S65, the call control software is updated. When the software update is completed, the process proceeds to step S66. In step S66, it is determined whether there is another MGC server operating with the old version software. If it is determined in step S66 that there is such an MGC server, the process proceeds to step S67, and the IP telephone service of the MGC server operating with the old version software is taken over. On the other hand, if it is determined in step S66 that there is no old version of the MGC server, the process returns to step S63.

  In step S67, IP phone service provision is started. After the process S67, a new call can be accepted. In step S68, the MGC server notifies the extended DNS server that it has been started in the ACT system, and thereafter, the TA transmits a new call to the local server. In step S69, the MGC server provides an IP telephone service. In step S70, it is determined whether to end the MGC server. If it is determined in the process S10 that the process is to be ended (Y), the process proceeds to the process S78, and the MGC server executes an end process. If it is determined in step S70 that the process will not end (N), the process proceeds to step S71. In step S71, it is determined whether to update the call control software. For example, when a software update instruction command is input from the outside via the software update unit (Y), the process proceeds to step S72. If nothing is input from the outside (N), the process returns to step S69.

  In step S72, it is confirmed whether there is a call managed by the MGC server itself. If there is such a call, the process proceeds to step S73, and the IP telephone service is continuously provided. In order not to affect the IP service, the MGC server repeats steps S72 to S73 until all managed calls are completed. When all the managed calls are finished, the process proceeds to step S74. In step S74, the SBY state is entered and the IP telephone service is terminated. In step S75, the call control software is updated. When the software update is completed, the process proceeds to step S76.

  In step S76, the MGC server determines whether there is another MGC server operating with the old version software. If it is determined in step S76 that there is such an MGC server, the process proceeds to step S67, and the IP telephone service of the MGC server in the ACT state operating with the old version software is taken over. On the other hand, if it is determined in step S66 that there is no old version of the MGC server, the process returns to step S63 and operates as an SBY-based MGC server. With the above operation, software update is realized without interruption of service. The operation of the extended DNS server in the second embodiment is the same as that in the first embodiment.

  FIG. 10 shows a processing procedure of the entire system at the time of software update in the second embodiment. With reference to this figure, the entire processing procedure in the second embodiment will be described.

  First, as an initial state of the entire system, it is assumed that three of the MGC servers 201, 202 and 203 are in the ACT state and one of the MGC 204 is in the SBY state. In step S81, the extended DNS server 221 updates the server list to reflect the ACT state based on the ACT notification from each server. Here, it is assumed that the version numbers of the software installed on the four MGC servers 201, 202, 203, and 204 are all ver.N.

  In step S82, when a new call occurs from the TA, the extended DNS server 221 assigns it to any of the MGC servers 201, 202, and 203. Next, in step S83, the software of the MGC server 204 operating as the SBY system is updated from ver.N to ver.N + 1. Since the MGC server 204 is in the SBY state, it does not affect the IP telephone service, so that software can be updated. After the software update, the MGC server 204 enters the ACT state.

  In step S84, the MGC server 204 notifies the extended DNS server 221 of this ACT state. At this time, it is searched whether there is another MGC server operating with the old version software, and if it exists, one of the MGC servers operating with the old version software is selected and taken over. Here, it is assumed that the MGC server 203 is selected as the MGC server operating with the old version software. That is, the MGC server 204 transmits an ACT notification including the IP address “A.B.C.G” and the host name “mgc3.oki.co.jp” to the extended DNS server 221.

  In step S85, the extended DNS server 221 updates the server list in response to this ACT notification. As a result, a new call to the MGC server 203 that was previously operating with the old version software is set to be transmitted to the MGC server 204 thereafter. Calls that existed before the software update are provided by the MGC server 203. When all calls using the MGC server 203 are completed, the MGC server 203 enters the SBY state.

  In step S86, the software of the MGC server 204 operating as the SBY system is updated from ver.N to ver.N + 1. At this time, since the MGC server 203 does not accept a new call, the service is not affected even if the MGC server 203 enters the SBY state. After the software update, the MGC server 203 enters the ACT state.

  In step S87, the MGC server 203 notifies the extended DNS server 221 of this ACT state. At this time, another MGC server operating with the old version software is searched for, and if it exists, one of the MGC servers operating with the old version software is selected and taken over. Here, it is assumed that the MGC server 202 is selected as the MGC server operating with the old version software. That is, the MGC server 203 sends an ACT notification including the IP address “ABCE” and the host name “mgc2.oki.co.jp” associated with the MGC server 202 so far to the extended DNS server 221. Send to.

  In step S88, the extended DNS server 221 updates the server list in response to this ACT notification. As a result, a new call to the MGC server 202 that was previously operated by the old version software is set to be transmitted to the MGC server 203 thereafter. Calls that existed before the software update are provided by the MGC server 203.

  In steps S89 and S90, the above procedure is repeated in the same manner to update the software of the MGC servers 202 and 201 from ver.N to ver.N + 1. Thereby, the software update of all the MGC servers is realized without stopping the IP telephone service.

  As described above, in the second embodiment, as in the first embodiment, the software can be updated without interrupting the service. In addition, since the second embodiment is not a duplex configuration as in the first embodiment, the service is interrupted if there is one SBY MGC server, although the reliability at the time of failure occurs is inferior. Since the software can be updated, the number of servers can be reduced as compared with a configuration in which a plurality of duplex configurations are used.

  In the first and second embodiments, MGCP is used as the IP telephone protocol. However, the present invention is not limited to this, and SIP (refer to Session Initiation Protocol 1, RFC 3261 of IETF) or Megaco ( It can also be realized using other IP telephone protocols such as Media Gateway Control and RFC 3015 of IETF). Further, although a form in which an analog telephone is directly connected to an IP network using a terminal adapter has been shown, the present invention can be applied to a form in which the telephone terminal is present on the fixed telephone network or mobile telephone network side. is there.

  In the above embodiment, the software to be updated is limited to the call control software. However, the present invention is not limited to this, and any one of various software installed in the call control server is updated. It is also possible to target.

1 is a block diagram illustrating a configuration of an entire system according to a first embodiment of this invention. FIG. 2 is a block diagram showing a more detailed functional configuration of an MGC server shown in FIG. 1. FIG. 2 is a block diagram showing a more detailed functional configuration of an extended DNS server shown in FIG. 1. It is explanatory drawing which shows the example of a setting of the server table contained in the extended DNS server shown by FIG. It is a flowchart which shows the processing flow of an MGC server. It is a flowchart which shows the processing flow of the extended DNS server. It is a sequence diagram which shows the process sequence of the whole system at the time of the software update in a 1st Example. It is a block diagram which shows the 2nd Example of this invention and shows the structure of the whole system. It is a flowchart which shows the processing flow of the MGC server in a 2nd Example. It is a sequence diagram which shows the process sequence of the whole system at the time of the software update in a 2nd Example.

Explanation of symbols

101, 102, 201, 202, 203, 204 MGC server 121, 221 Extended DNS server 122, 222 IP network 111-11n, 211-21n TA
133 Call control software

Claims (9)

An IP telephone service method for providing IP telephone service to a telephone terminal by selectively responding to one of a plurality of call control servers for each service request from the telephone terminal,
In response to an update request for updating software provided in the plurality of call control servers, at least one of the plurality of call control servers is left as a response permission server, and the other is set as a response prohibition server. A setting step for setting to prohibit a response of the response prohibition server to a service request;
An update step of waiting for completion of the IP telephone service already provided by the response prohibition server and updating the software of the response prohibition server;
An IP telephone service method comprising:   2. The IP telephone service method according to claim 1, further comprising a resetting step of resetting the response prohibition server as a response permission server in response to completion of the software update.   The setting step is a step of setting one of the plurality of call control servers as a response prohibition server, and the setting step, the updating step, and the resetting step are performed for each of the plurality of call control servers. 3. The IP telephone service method according to claim 2, further comprising a step of repeating.   In the setting step, the host name included in the service request is associated with the IP address of the response permission server, the correspondence between the host name and the IP address of the response prohibition server is removed, and a new one from the telephone terminal 2. The IP telephone service method according to claim 1, wherein the IP telephone service method is a step of making a setting for prohibiting a response of the response prohibition server to a service request. An IP telephone service system that includes a plurality of call control servers, selectively responds to one of the plurality of call control servers for each service request from a telephone terminal, and provides the telephone terminal with the IP telephone service. And
In response to an update request for updating software provided in the plurality of call control servers, at least one of the plurality of call control servers is left as a response permission server, and the other is set as a response prohibition server. Setting means for making a setting for prohibiting the response of the response prohibition server to a service request;
Updating means for updating software of the response prohibition server after waiting for completion of the IP telephone service already provided by the response prohibition server;
An IP telephone service system comprising:   6. The IP telephone service system according to claim 5, further comprising resetting means for resetting the response prohibition server as a response permission server in response to completion of the software update.   The setting means is means for setting one of the plurality of call control servers as a response prohibition server, and for each of the plurality of call control servers, the setting step, the updating step, and the resetting step are performed. 7. The IP telephone service system according to claim 6, further comprising means for repeating.   The setting means associates the host name included in the service request with the IP address of the response permission server, removes the correspondence between the host name and the IP address of the response prohibition server, and creates a new one from the telephone terminal. 6. The IP telephone service system according to claim 5, wherein the IP telephone service system is configured to prohibit a response of the response prohibition server to a service request.   9. The IP telephone service system according to claim 8, further comprising a DNS server, wherein the setting unit is provided in the DNS server.

Images