CN101051883B - Service switching method and system after main voice server fault restoring - Google Patents
Service switching method and system after main voice server fault restoring Download PDFInfo
- Publication number
- CN101051883B CN101051883B CN2007100973398A CN200710097339A CN101051883B CN 101051883 B CN101051883 B CN 101051883B CN 2007100973398 A CN2007100973398 A CN 2007100973398A CN 200710097339 A CN200710097339 A CN 200710097339A CN 101051883 B CN101051883 B CN 101051883B
- Authority
- CN
- China
- Prior art keywords
- voice server
- voip
- main
- voice
- standby
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000011084 recovery Methods 0.000 claims abstract description 38
- 230000004044 response Effects 0.000 claims description 58
- 230000001360 synchronised effect Effects 0.000 claims description 48
- 238000001514 detection method Methods 0.000 claims description 19
- 239000000523 sample Substances 0.000 claims description 7
- 230000001960 triggered effect Effects 0.000 abstract 1
- 230000008569 process Effects 0.000 description 13
- 230000007246 mechanism Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000006855 networking Effects 0.000 description 4
- 238000010276 construction Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
The switching method includes steps: the standby voice server (SVS) detects whether fault of the main voice server (MVS) is recovered; if yes, through triggered message of IP voice (VoIP) protocol, SVS sends information of fault recovery of MVS to voice terminal; voice terminal switches the service to MVS. The invention also discloses a method for synchronizing data between voice servers, which includes steps: through synchronization message in VoIP protocol, first voice server sends self-data needed to synchronize to second voice server; second voice server carries out synchronization for self saved data. Since VoIP protocol is intrinsic protocol for voice server and voice terminal, thus, in the invention, voice server and voice terminal does not need to support other protocol additionally so as to raise versatility of device, increase flexibility to implement service, and enhance capability for constructing network.
Description
Technical Field
The present invention relates to network communication technology, and in particular, to a method and system for service switching after failure recovery of a primary voice server.
Background
Voice over IP (VoIP) technology is a technology for transmitting voice data in an IP network in a packet-switched manner. In the VoIP technology, in order to prevent a service interruption due to a failure of one voice server, a method of backing up the voice server is used to provide a service to a voice terminal. Fig. 1 is a schematic diagram illustrating a service provided by a voice server backup method in the prior art. Fig. 2 is a flow chart of a prior art implementation of voice server backup. Referring to fig. 1 and 2, in the prior art, a process for implementing a voice server backup includes the following steps:
step 201: setting a main voice server and a standby voice server supporting a private protocol.
Step 202: and a database is respectively integrated on the main voice server and the standby voice server.
Step 203: the main voice server and the standby voice server utilize databases integrated in the main voice server and synchronize the working state information of the main voice server and the information corresponding to the voice terminal.
In this step 203, the primary voice server and the standby voice server implement data synchronization by using a synchronization mechanism between the databases, and the process may be: the main voice server records the working state information of the main voice server and various information corresponding to the voice terminal in a database integrated with the main voice server, a database integrated with the standby voice server subscribes to the database integrated with the main voice server by using a publishing-subscribing mechanism, the database integrated with the main voice server sends the working state information written by the main voice server and various information corresponding to the voice terminal to the database integrated with the standby voice server by using a publishing mode, and the standby voice server obtains the working state information of the main voice server and various information corresponding to the voice terminal from the integrated database, so that data synchronization between the main voice server and the standby voice server is completed.
In addition, in order to enable a backup group composed of the main voice server and the standby voice server to perform voice data interaction with a third-party voice server in other areas, in the prior art, a database is integrated on the third-party voice server, and the third-party voice server determines whether the working state of the main voice server is normal or not through a synchronization mechanism between the database of the third-party voice server and the database in the main voice server, so as to determine whether to send a message to the normally working main voice server or to the standby voice server which replaces the main voice server to work when the main voice server fails.
Step 204: and the voice terminal detects the fault of the main voice server and switches the service to the standby voice server.
Step 205: when the main voice server is recovered from the fault, the standby voice server determines the recovery of the fault of the main voice server according to the working state information of the main voice server, which is synchronized from the database of the main voice server, of the database of the standby voice server.
Step 206: and the standby voice server informs the voice terminal that the main voice server is recovered to be normal by using a preset message of a private protocol.
Step 207: and the voice terminal switches the service to the main voice server.
The above-mentioned process from step 205 to step 207 describes a service switching method after the primary voice server failure is recovered in the prior art; the process of step 202 and step 203 describes the data synchronization method between voice servers in the prior art.
It can be seen from the service switching method after the failure recovery of the primary voice server in the prior art that, in the prior art, after the failure recovery of the primary voice server, the standby voice server notifies the voice terminal of the information that the primary voice server recovers to normal by using the private protocol, so that the voice terminal can switch the service back to the primary voice server. The method for notifying the voice terminal through the private protocol requires that the voice server and the voice terminal must support the private protocol, that is, the most common voice server and voice terminal supporting the VoIP protocol cannot realize the service switching after the failure recovery of the main voice server, so the universality of the equipment is greatly reduced, the flexibility of service realization is limited, and the networking capability is reduced.
Moreover, it can be seen from the data synchronization method between the voice servers in the prior art that, in the prior art, synchronization of data between different voice servers, such as the primary voice server and the standby voice server or the third-party voice server and the primary voice server, is achieved by using a synchronization mechanism between databases. The method of using the database synchronization requires that a commercial database must be integrated on the voice server, that is, the most common voice server supporting the VoIP protocol cannot realize data synchronization, so the universality of the device is greatly reduced, the flexibility of service realization is limited, and the networking capability is reduced.
Disclosure of Invention
In view of the above, a first object of the present invention is to provide a method for service switching after failure recovery of an active voice server, a second object of the present invention is to provide a method for synchronizing data between voice servers, a third object of the present invention is to provide a system for implementing service switching after failure recovery of an active voice server, a fourth object of the present invention is to provide a standby voice server, and a fifth object of the present invention is to provide a voice server so as to improve the universality of devices.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a service switching method after fault recovery of a main voice server comprises the following steps:
the standby voice server detects whether the fault of the main voice server is recovered, if so, the standby voice server sends the fault recovery information of the main voice server to the voice terminal through an IP voice VoIP protocol trigger message, and the fault recovery information of the main voice server comprises the name and/or address information of the main voice server required when the voice terminal is connected to the main voice server; the voice terminal switches the service to the main voice server;
the third party voice server sends the VoIP registration request message to the main voice server, if the main voice server is normal, the main voice server returns a successful response message of VoIP registration, the third-party voice server judges whether the successful response message of VoIP registration returned by the main voice server can be received, if so, determining that the main voice server is normal, setting the main voice server as an effective voice server in a backup group consisting of the main voice server and the standby voice server, otherwise, determining that the main voice server is in failure, the third party voice server receives the VoIP registration success response message returned by the standby voice server, and sets the standby voice server as an effective voice server in the backup group; and when the destination address of the VoIP call request received by the third-party voice server is the address of the backup group, the third-party voice server sends the VoIP call request to the current effective voice server in the backup group.
The step of detecting whether the fault of the main voice server is recovered by the standby voice server comprises the following steps:
after the main voice server fails, synchronizing the working state information of the main voice server by a database pre-integrated in a standby voice server from the database pre-integrated in the main voice server, detecting whether the working state information of the main voice server synchronized by a database of the standby voice server is normal or not by the standby voice server, and if so, determining that the failure of the main voice server is recovered;
or,
after the primary voice server fails, the standby voice server sends a VoIP registration request message to the primary voice server, judges whether a VoIP registration success response message returned by the primary voice server can be received or not, and determines that the primary voice server fails to recover if the VoIP registration success response message returned by the primary voice server can be received.
The method further comprises the following steps: after the main voice server fails, the voice terminal sends a VoIP protocol detection message to the standby voice server;
the VoIP protocol trigger message is as follows: a reject response message for the VoIP protocol probe message.
The VoIP protocol detection message is a VoIP registration request message; the reject response message for the VoIP protocol probe message is a VoIP registration reject response message.
The method further comprises the following steps: the main voice server sends the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message; and the standby voice server synchronizes the data stored by the standby voice server according to the received VoIP protocol synchronization message.
The data to be synchronized comprises: and the information corresponding to the voice terminal in the main voice server.
After receiving the VoIP protocol request message sent by the standby voice server, the main voice server executes the step of sending the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message;
or,
and after the configuration information of the voice terminal in the main voice server changes, executing the step of sending the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message.
The VoIP protocol request message is a VoIP registration request message, and the VoIP protocol synchronization message is a VoIP registration success response message.
A system for realizing service switching after fault recovery of a main voice server comprises: a main voice server, a standby voice server, a voice terminal and a third-party voice server, wherein,
the standby voice server is used for detecting whether the fault of the main voice server is recovered or not, if so, the fault recovery information of the main voice server is sent to the voice terminal through a VoIP protocol trigger message, and the fault recovery information of the main voice server comprises the name and/or address information of the main voice server required when the voice terminal is connected to the main voice server; the VoIP registration request message is sent by the third-party voice server, and a VoIP registration success response message is returned to the third-party voice server;
the voice terminal switches the service to the main voice server after receiving the VoIP protocol trigger message;
the main server is used for receiving the VoIP registration request message sent by the third-party voice server and returning a VoIP registration success response message to the third-party voice server;
the third-party voice server is used for sending a VoIP registration request message to the main voice server, judging whether a VoIP registration success response message returned by the main voice server can be received or not, if so, determining that the main voice server is normal, setting the main voice server as an effective voice server in a backup group consisting of the main voice server and the standby voice server, otherwise, determining that the main voice server is in failure, sending the VoIP registration request message to the standby voice server, receiving the VoIP registration success response message returned by the standby voice server, and setting the standby voice server as the effective voice server in the backup group; and the server is further used for sending the VoIP call request to the current effective voice server in the backup group when the destination address of the received VoIP call request is the address of the backup group.
The standby voice server further sends the VoIP registration request message to the main voice server after the main voice server fails, and detects that the failure of the main voice server is recovered after receiving a VoIP registration success response message replied by the main voice server.
The main voice server further sends data to be synchronized in the main voice server to a standby voice server through a VoIP protocol synchronization message;
and the standby voice server further synchronizes the data stored by the standby voice server according to the received VoIP protocol synchronization message.
The primary voice server includes: a synchronous data processing unit and a transceiving unit, wherein,
the receiving and sending unit is used for sending the VoIP protocol request message sent by the standby voice server to the synchronous data processing unit and sending the VoIP protocol synchronous message carrying the data to be synchronized sent by the synchronous data processing unit to the standby voice server;
and the synchronous data processing unit is used for generating a VoIP protocol synchronous message carrying data to be synchronized after receiving the VoIP protocol request message or after the configuration information corresponding to the voice terminal is changed, and sending the VoIP protocol synchronous message to the receiving and sending unit.
Therefore, in the invention, in the service switching process after the failure recovery of the main voice server, the standby voice server notifies the voice terminal of the failure recovery information of the main voice server by using the message of the VoIP protocol, instead of notifying by using the private protocol message in the prior art, and the VoIP protocol is the inherent protocol of the voice server and the voice terminal, so that the voice server and the voice terminal in the invention do not need to additionally support other protocols, thereby improving the universality of equipment, increasing the flexibility of service realization and improving the networking capability.
In addition, in the invention, when the voice server synchronizes data, the voice server can utilize the message of VoIP protocol to complete the synchronization of various data, but not the prior art to utilize the newly added database to realize, because the VoIP protocol is the inherent protocol of the voice server and the voice terminal, the voice server and the voice terminal in the invention do not need to additionally configure the database, thereby improving the universality of the equipment, increasing the flexibility of service realization and improving the networking capability. Meanwhile, a database does not need to be configured, so that the cost of the voice server is greatly reduced.
Drawings
Fig. 1 is a schematic diagram illustrating a service provided by a voice server backup method in the prior art.
Fig. 2 is a flow chart of a prior art implementation of voice server backup.
Fig. 3 is a flowchart of implementing service switching after failure recovery of the active voice server in the embodiment of the present invention.
Fig. 4 is a schematic structural diagram of a system for implementing service switching after failure recovery of a primary voice server in the embodiment of the present invention.
Fig. 5 is a schematic diagram of the structure of a standby voice server in the present invention.
Fig. 6 is a schematic diagram of a voice server implementing data synchronization in the present invention.
Fig. 7 is a schematic diagram of another voice server for implementing data synchronization in the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail with reference to the accompanying drawings and specific embodiments.
The equipment characteristics of the universal voice server and the voice terminal are analyzed, and in the VoIP technology, all the voice servers and the voice terminal support the VoIP protocol, so that if the inherent VoIP protocol of the voice server and the voice terminal can be utilized to realize the service switching after the fault recovery of the main voice server and realize the data synchronization between the voice servers, the requirements on the voice server and the voice terminal can be greatly reduced, and the universality of the voice server and the voice terminal is improved.
To address the above mentioned features, the present invention provides a method for switching services after a failure recovery of a primary voice server, the method comprising: the standby voice server detects whether the fault of the main voice server is recovered, if so, the standby voice server sends the fault recovery information of the main voice server to the voice terminal through a VoIP protocol trigger message; and the voice terminal switches the service to the main voice server.
In the service switching method after the primary voice server failure is recovered, the voice terminal can further send the VoIP protocol detection message to the standby voice server after the primary voice server fails, so that the VoIP protocol trigger message sent by the standby voice server can be a response rejection message aiming at the VoIP protocol detection message.
Fig. 3 is a flowchart of implementing service switching after failure recovery of the active voice server in the embodiment of the present invention. Referring to fig. 3, in a specific embodiment of the present invention, a process of implementing service switching after a failure of an active voice server is recovered specifically includes the following steps:
step 301: and the voice terminal detects the fault of the main voice server and switches the service to the standby voice server.
Step 302: the standby voice server detects the failure of the main voice server.
Here, the standby voice server may detect the failure of the active voice server in two ways:
mode 10, detection is made by using a database synchronization mechanism in the prior art.
In the method 10, as in the prior art, a database is integrated on both the primary voice server and the standby voice server, and the database in the primary voice server records the current operating state information of the primary voice server. Thus, when the primary voice server fails, the database in the primary voice server will update the recorded working state information to a failure, and then the database in the standby voice server synchronizes the working state information of the primary voice server from the database in the primary voice server, and the standby voice server detects that the working state information of the primary voice server synchronized by the database of the standby voice server is a failure, and can determine that the primary voice server fails.
Mode 20, detection is made using VoIP protocol messages.
This mode 20 is a preferred mode for realizing this step. In this manner 20, the active voice server and the standby voice server do not need to integrate databases, but the standby voice server obtains various information including the operating status information of the active voice server by exchanging VoIP protocol request messages and VoIP protocol response messages. The specific process can be as follows: the standby voice server periodically sends a VoIP registration request message to the main voice server, and if the main voice server is in a fault state, a VoIP registration success response message cannot be returned to the standby voice server; therefore, after the standby voice server sends the VoIP registration request message, whether the VoIP registration success response message returned by the main voice server can be received or not is judged, and if not, the main voice server is determined to be in failure.
Step 303: after the voice terminal determines that the main voice server is in fault, the voice terminal periodically sends VoIP protocol detection messages to the standby voice server.
Step 304: after the primary voice server fails, the standby voice server detects whether the failure of the primary voice server is recovered, if so, step 306 is executed, otherwise, step 305 is returned.
Here, the standby voice server may detect whether the failure of the active voice server is recovered by the following two ways:
the first way is to use the database synchronization mechanism in the prior art to detect.
In the first mode, as in the prior art, a database is integrated on both the main voice server and the standby voice server, and the database in the main voice server records the current working state information of the main voice server. Therefore, when the fault of the main voice server is recovered, the database in the main voice server updates the recorded working state information to be normal, then the database in the standby voice server synchronizes the working state information of the main voice server from the database in the main voice server, the standby voice server detects whether the working state information of the main voice server synchronized by the database of the standby voice server is normal, and if so, the fault recovery of the main voice server is determined.
And the second mode is detection by using VoIP protocol messages.
The second mode is a preferred mode for implementing this step. In the second mode, the primary voice server and the standby voice server do not need to integrate databases, but acquire various information including the working state information of the primary voice server through the VoIP protocol message. The specific process is as follows: after the main voice server fails, the standby voice server periodically sends a VoIP registration request message to the main voice server, and if the main voice server fails and is recovered to be in a normal state, a VoIP registration success response message is returned to the standby voice server; therefore, after the standby voice server sends the VoIP registration request message, whether the VoIP registration success response message returned by the main voice server can be received or not is judged, if yes, the fault recovery of the main voice server is determined, and if not, the fault recovery of the main voice server is determined.
Step 305: the standby voice server sends a successful response message for the VoIP protocol probe message to the voice terminal, and returns to perform step 304.
When the step is executed, because the main voice server still fails, the standby voice server can send a successful response message aiming at the VoIP protocol detection message to the voice terminal, so that the voice terminal determines that the voice terminal currently serves the voice terminal still is the standby voice server through the successful response message, and determines that the main voice server still fails.
Step 306: and the standby voice server sends the fault recovery information of the main voice server to the voice terminal through the response rejection message aiming at the VoIP protocol detection message.
When the step is executed, because the fault of the main voice server is recovered, the standby voice server can send the rejection response message aiming at the VoIP protocol detection message to the voice terminal, so that the voice terminal determines that the current voice server is changed into the main voice server through the rejection response message, and determines that the fault of the main voice server is recovered.
In this step, the information about the fault recovery of the active voice server may include a name and/or address information of the active voice server, which is required when the voice terminal is connected to the active voice server, for example, an IP address and port information of the active voice server, and a server name GK-id.
Step 307: and the voice terminal switches the service to the main voice server.
The specific implementation of this step is the same as the process of switching the service to the primary voice server by the voice terminal in the prior art, that is, the voice terminal registers with the primary voice server, and performs subsequent service interaction with the primary voice server after the registration is successful.
It should be noted that there is no fixed execution sequence between the steps 301 and 302 and between the steps 303 and 304.
In the above steps 302 and 304, preferably, the standby voice server and the active voice server may detect the operating state of the active voice server by exchanging the VoIP registration request message and the VoIP registration success response message, instead of detecting the operating state of the active voice server by using the database synchronization mechanism in the prior art. Similarly, in the present invention, a third-party voice server that needs to perform information interaction with a backup group composed of a standby voice server and a main voice server may also detect an effective voice server in the backup group by using a VoIP registration request message and a VoIP registration success response message without using a database synchronization mechanism in the prior art, and the specific implementation process includes:
the third party voice server sends the VoIP registration request message to the main voice server, if the main voice server is normal, the main voice server returns a successful response message of VoIP registration, the third-party voice server judges whether the successful response message of VoIP registration returned by the main voice server can be received, if so, determining that the main voice server is normal, setting the main voice server as an effective voice server in a backup group consisting of the main voice server and the standby voice server, otherwise, determining that the main voice server is in failure, the third party voice server receives the VoIP registration success response message returned by the standby voice server, and sets the standby voice server as an effective voice server in the backup group; and when the destination address of the VoIP call request received by the third-party voice server is the address of the backup group, the third-party voice server sends the VoIP call request to the current effective voice server in the backup group.
Correspondingly, the invention provides a service switching system after the fault of the main voice server is recovered. Referring to fig. 4, the system includes: a main voice server, a standby voice server and a voice terminal, wherein,
the standby voice server is used for detecting whether the fault of the main voice server is recovered or not, and if so, the information of the fault recovery of the main voice server is sent to the voice terminal through a VoIP protocol trigger message;
and the voice terminal is used for switching the service to the main voice server after receiving the VoIP protocol trigger message.
In the system shown in fig. 4, the standby voice server further sends a VoIP registration request message to the primary voice server after the primary voice server fails, and detects that the failure of the primary voice server has recovered after receiving a VoIP registration success response message sent by the primary voice server.
Correspondingly, the invention provides a standby voice server. Referring to fig. 5, the standby voice server includes: a state detection unit, a VoIP message construction unit and a transceiving unit, wherein,
the state detection unit is used for detecting whether the fault of the main voice server is recovered or not, and if so, sending a trigger notification to the VoIP message construction unit;
the VoIP message constructing unit is used for constructing a VoIP protocol trigger message carrying the fault recovery information of the main voice server after receiving the trigger notice, and sending the VoIP protocol trigger message to the receiving and sending unit;
and the receiving and sending unit is used for sending the received VoIP protocol trigger message carrying the fault recovery information of the main voice server to the voice terminal.
In the standby voice server shown in fig. 5, the VoIP message constructing unit further constructs a VoIP registration request message, and sends it to the transceiver unit;
the receiving and sending unit is used for further sending the VoIP registration request message to the main voice server and sending a VoIP registration success response message sent by the main voice server to the state detection unit;
the state detection unit detects that the fault of the main voice server is recovered after receiving the VoIP registration success response message sent by the receiving and sending unit.
In addition, the invention also provides a method for synchronizing data between voice servers, which comprises the following steps: the main voice server sends the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message; and the standby voice server synchronizes the data stored by the standby voice server according to the received VoIP protocol synchronization message.
In the method for synchronizing data between voice servers provided by the present invention, the data to be synchronized sent by the main voice server may include: and the information corresponding to the voice terminal in the main voice server.
In addition, in the method for synchronizing data between voice servers provided by the invention, the standby voice server can further send the VoIP protocol request message to the main voice server, so that the main voice server executes the processing of sending the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message after receiving the VoIP protocol request message; or, the main voice server may also perform the above-mentioned processing of sending the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message after the configuration information of the voice terminal in the main voice server changes.
Correspondingly, the invention also provides a voice server for realizing the process of synchronizing data among the voice servers. Referring to fig. 6, the voice server includes: a VoIP message construction unit, a data synchronization unit, and a transceiving unit, wherein,
a VoIP message constructing unit, which is used for constructing a VoIP protocol request message and sending the VoIP protocol request message to the receiving and sending unit;
the receiving and sending unit is used for sending the VoIP protocol request message to other voice servers, receiving a VoIP protocol synchronization message which carries data to be synchronized and is sent by other voice servers, and sending the VoIP protocol synchronization message to the data synchronization unit;
and the data synchronization unit is used for synchronizing the stored data according to the data carried in the VoIP protocol synchronization message.
For the voice server shown in fig. 6, the voice server requests synchronization of data stored in the voice server of the receiving party through a VoIP protocol request message. In particular, the voice server shown in fig. 6 may be a backup voice server.
Correspondingly, the invention also provides a voice server for realizing the process of synchronizing data among the voice servers. Referring to fig. 7, the voice server includes: a synchronous data processing unit and a transceiving unit, wherein,
the receiving and sending unit is used for sending the VoIP protocol request message sent by other voice servers to the synchronous data processing unit and sending the VoIP protocol synchronous message carrying the data to be synchronized sent by the synchronous data processing unit to the other voice servers;
and the synchronous data processing unit is used for generating a VoIP protocol synchronous message carrying data to be synchronized after receiving the VoIP protocol request message or after the configuration information corresponding to the voice terminal is changed, and sending the VoIP protocol synchronous message to the receiving and sending unit.
For the voice server shown in fig. 7, the voice server transmits data to be synchronized to other servers through VoIP protocol synchronization messages. Specifically, the voice server shown in fig. 7 may be a primary voice server.
It should be noted that, in the process shown in fig. 3 for implementing service switching after the primary voice server recovers from the failure, the VoIP protocol probe message sent by the voice terminal to the standby voice server may be any VoIP message capable of triggering the standby voice server to reply the response message, such as a VoIP registration request message or a server capability query message of the VoIP protocol. When the VoIP protocol detection message is a VoIP registration request message, the successful response message of the VoIP protocol detection message is a VoIP registration successful response message, and the refusal response message of the VoIP protocol detection message is a VoIP registration refusal response message.
In the method for synchronizing data between voice servers provided by the present invention, the VoIP protocol request message may be any VoIP message that can trigger the receiver to reply the response message, such as a VoIP registration request message or a server capability query message of VoIP protocol; accordingly, the VoIP protocol synchronization message is a response message to the VoIP protocol request message. For example, when the VoIP protocol request message is a VoIP registration request message, the VoIP protocol synchronization message is a VoIP registration success response message.
Specifically, the VoIP registration request message in the present invention may be, for example: a REGISTER message of a Session Initiation Protocol (SIP), or an RRQ message of an h.323 protocol, or an RSIP message of an MGCP protocol, or an SVC _ CHG _ REQ message of an h.248 protocol. At this time, the corresponding VoIP registration success response messages are respectively: 200OK message, RCF message, RSIP _ RSP message carrying registration success information, SVC _ CHG _ REPLY message carrying registration success information. And, the corresponding VoIP registration rejection response messages are respectively: a 3XX message, an RRJ message, an RSIP _ RSP message carrying registration rejection information, and an SVC _ CHG _ REPLY message carrying registration rejection information.
It should be noted that the scheme for implementing service switching after failure recovery of the main voice server and the scheme for synchronizing data between voice servers provided by the present invention can be applied to both the main voice server and the standby voice server for implementing VoIP. That is, the standby voice server can notify the voice terminal that the failure of the main voice server is recovered by using the scheme of realizing service switching after the failure of the main voice server is recovered, and meanwhile, the standby voice server can also synchronize data with the main voice server by using the method for synchronizing data between the voice servers provided by the invention.
In the present invention, the voice terminal may be any terminal that can implement VoIP, for example, a gateway or an IP phone.
In short, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (12)
1. A service switching method after fault recovery of a main voice server is characterized by comprising the following steps:
the standby voice server detects whether the fault of the main voice server is recovered, if so, the standby voice server sends the fault recovery information of the main voice server to the voice terminal through an IP voice VoIP protocol trigger message, and the fault recovery information of the main voice server comprises the name and/or address information of the main voice server required when the voice terminal is connected to the main voice server; the voice terminal switches the service to the main voice server;
the third party voice server sends the VoIP registration request message to the main voice server, if the main voice server is normal, the main voice server returns a successful response message of VoIP registration, the third-party voice server judges whether the successful response message of VoIP registration returned by the main voice server can be received, if so, determining that the main voice server is normal, setting the main voice server as an effective voice server in a backup group consisting of the main voice server and the standby voice server, otherwise, determining that the main voice server is in failure, the third party voice server receives the VoIP registration success response message returned by the standby voice server, and sets the standby voice server as an effective voice server in the backup group; and when the destination address of the VoIP call request received by the third-party voice server is the address of the backup group, the third-party voice server sends the VoIP call request to the current effective voice server in the backup group.
2. The method of claim 1, wherein the step of the backup voice server detecting whether the failure of the active voice server is recovered comprises:
after the main voice server fails, synchronizing the working state information of the main voice server by a database pre-integrated in a standby voice server from the database pre-integrated in the main voice server, detecting whether the working state information of the main voice server synchronized by a database of the standby voice server is normal or not by the standby voice server, and if so, determining that the failure of the main voice server is recovered;
or,
after the primary voice server fails, the standby voice server sends a VoIP registration request message to the primary voice server, judges whether a VoIP registration success response message returned by the primary voice server can be received or not, and determines that the primary voice server fails to recover if the VoIP registration success response message returned by the primary voice server can be received.
3. The method of claim 1, further comprising: after the main voice server fails, the voice terminal sends a VoIP protocol detection message to the standby voice server;
the VoIP protocol trigger message is as follows: a reject response message for the VoIP protocol probe message.
4. The method of claim 3, wherein the VoIP protocol probe message is a VoIP registration request message; the reject response message for the VoIP protocol probe message is a VoIP registration reject response message.
5. The method according to any one of claims 1 to 4, characterized in that the method further comprises: the main voice server sends the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message; and the standby voice server synchronizes the data stored by the standby voice server according to the received VoIP protocol synchronization message.
6. The method of claim 5, wherein the data to be synchronized comprises: and the information corresponding to the voice terminal in the main voice server.
7. The method according to claim 5, wherein the active voice server executes the step of sending the data to be synchronized in the active voice server to the standby voice server through the VoIP protocol synchronization message after receiving the VoIP protocol request message sent by the standby voice server;
or,
and after the configuration information of the voice terminal in the main voice server changes, executing the step of sending the data to be synchronized in the main voice server to the standby voice server through the VoIP protocol synchronization message.
8. The method of claim 7, wherein the VoIP protocol request message is a VoIP registration request message and the VoIP protocol synchronization message is a VoIP registration success response message.
9. A system for realizing service switching after fault recovery of a main voice server is characterized by comprising: a main voice server, a standby voice server, a voice terminal and a third-party voice server, wherein,
the standby voice server is used for detecting whether the fault of the main voice server is recovered or not, if so, the fault recovery information of the main voice server is sent to the voice terminal through a VoIP protocol trigger message, and the fault recovery information of the main voice server comprises the name and/or address information of the main voice server required when the voice terminal is connected to the main voice server; the VoIP registration request message is sent by the third-party voice server, and a VoIP registration success response message is returned to the third-party voice server;
the voice terminal switches the service to the main voice server after receiving the VoIP protocol trigger message;
the main server is used for receiving the VoIP registration request message sent by the third-party voice server and returning a VoIP registration success response message to the third-party voice server;
the third-party voice server is used for sending a VoIP registration request message to the main voice server, judging whether a VoIP registration success response message returned by the main voice server can be received or not, if so, determining that the main voice server is normal, setting the main voice server as an effective voice server in a backup group consisting of the main voice server and the standby voice server, otherwise, determining that the main voice server is in failure, sending the VoIP registration request message to the standby voice server, receiving the VoIP registration success response message returned by the standby voice server, and setting the standby voice server as the effective voice server in the backup group; and the server is further used for sending the VoIP call request to the current effective voice server in the backup group when the destination address of the received VoIP call request is the address of the backup group.
10. The system of claim 9, wherein the standby voice server further sends a VoIP registration request message to the primary voice server after the primary voice server fails, and detects that the failure of the primary voice server has recovered after receiving a VoIP registration success response message returned by the primary voice server.
11. The system of claim 9, wherein the active voice server further sends data to be synchronized in itself to the standby voice server via VoIP protocol synchronization messages;
and the standby voice server further synchronizes the data stored by the standby voice server according to the received VoIP protocol synchronization message.
12. The system of claim 11, wherein the active voice server comprises: a synchronous data processing unit and a transceiving unit, wherein,
the receiving and sending unit is used for sending the VoIP protocol request message sent by the standby voice server to the synchronous data processing unit and sending the VoIP protocol synchronous message carrying the data to be synchronized sent by the synchronous data processing unit to the standby voice server;
and the synchronous data processing unit is used for generating a VoIP protocol synchronous message carrying data to be synchronized after receiving the VoIP protocol request message or after the configuration information corresponding to the voice terminal is changed, and sending the VoIP protocol synchronous message to the receiving and sending unit.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100973398A CN101051883B (en) | 2007-05-11 | 2007-05-11 | Service switching method and system after main voice server fault restoring |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007100973398A CN101051883B (en) | 2007-05-11 | 2007-05-11 | Service switching method and system after main voice server fault restoring |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101051883A CN101051883A (en) | 2007-10-10 |
| CN101051883B true CN101051883B (en) | 2011-04-20 |
Family
ID=38783100
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007100973398A Expired - Fee Related CN101051883B (en) | 2007-05-11 | 2007-05-11 | Service switching method and system after main voice server fault restoring |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101051883B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101262528B (en) * | 2008-02-03 | 2011-01-05 | 中兴通讯股份有限公司 | A multi-gateway backup method for voice access of network call |
| CN101668193A (en) * | 2008-09-02 | 2010-03-10 | 华为技术有限公司 | Play switching method and system |
| CN101640611B (en) * | 2009-08-26 | 2012-05-30 | 烽火通信科技股份有限公司 | Method for synchronizing and switching active and standby modules of VOIP voice service in real time |
| CN102111459B (en) * | 2009-12-28 | 2013-11-06 | 中兴通讯股份有限公司 | Call maintenance method and device in active/standby switching of IP voice equipment |
| CN102083134B (en) * | 2011-02-15 | 2014-07-09 | 华为技术有限公司 | Service processing method and device as well as wireless network controller |
| CN102523203B (en) * | 2011-12-02 | 2014-07-09 | 华为技术有限公司 | Method, device and system for voice call |
| CN104065500A (en) * | 2013-03-21 | 2014-09-24 | 苏州方位通讯科技有限公司 | Register server hot backup method realized by SIP terminal |
| CN103236947A (en) * | 2013-04-23 | 2013-08-07 | 厦门亿联网络技术股份有限公司 | Method for switching main server and standby of VOIP (voice over Internet phone) |
| CN106559235A (en) * | 2015-09-28 | 2017-04-05 | 西安艾润物联网技术服务有限责任公司 | The switching method and apparatus of embedded server running status |
| CN109905550A (en) * | 2019-03-01 | 2019-06-18 | 上海市共进通信技术有限公司 | The method for realizing the adaptive handoff functionality of VOIP server |
| CN110502368B (en) * | 2019-08-14 | 2022-07-26 | 出门问问(武汉)信息科技有限公司 | Dialogue fault tolerance method, central control equipment, system and readable storage medium |
| CN113114777B (en) * | 2021-04-22 | 2022-07-01 | 善理通益信息科技(深圳)有限公司 | Disaster recovery method and device for multi-node high-availability cluster |
| CN115604234B (en) * | 2022-11-15 | 2023-03-10 | 深圳市华曦达科技股份有限公司 | VoIP server self-adaptive switching method, system and storage medium |
| CN117424680B (en) * | 2023-12-19 | 2024-03-15 | 深圳鼎信通达股份有限公司 | Dual-computer hot standby switching circuit, control method and system thereof and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1897561A (en) * | 2005-07-12 | 2007-01-17 | 中兴通讯股份有限公司 | Method for protecting VOIP digital signal processing channel |
-
2007
- 2007-05-11 CN CN2007100973398A patent/CN101051883B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1897561A (en) * | 2005-07-12 | 2007-01-17 | 中兴通讯股份有限公司 | Method for protecting VOIP digital signal processing channel |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101051883A (en) | 2007-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101051883B (en) | Service switching method and system after main voice server fault restoring | |
| CN109391979B (en) | Method, device and system for restoring P-CSCF (proxy-Call Session control function) fault | |
| JP4111793B2 (en) | Relay system | |
| EP2536118B1 (en) | Providing resilient digital telephony services for wireless devices | |
| CN101730984A (en) | Methods, systems, and computer program products for providing fault-tolerant service interaction and mediation function in a communications network | |
| CN101035036B (en) | Legal monitoring system and method | |
| CN101068378B (en) | Method, system and equipment for realizing multimedia information service system disaster recovery | |
| WO2011099523A1 (en) | Pcrf, fault recovery method, and system | |
| CN102123374A (en) | Method and system for realizing termination domain selection | |
| CN101543117A (en) | Handoff of dual mode mobile device between an IP network and a PLMN | |
| JP2009500896A (en) | Method and apparatus for multi-mode conversation over a wireless network | |
| KR101620809B1 (en) | A method for sip proxy failover | |
| CN101702712B (en) | Detection technology and voice call backup linkage method and device thereof | |
| CN103138984A (en) | Method and system of disaster recovery back serving call session control function | |
| CN101159536B (en) | Media gateway node condition synchronizing method in dual-home network | |
| EP2774323B1 (en) | Method, communication system and non-transitory computer readable medium for optimizing network performance after a temporary loss of connection | |
| CN102804910A (en) | Connection establishing method, fault processing method, communication system and device thereof | |
| You et al. | Robust hierarchical mobile IPv6 (RH-MIPv6): an enhancement for survivability and fault-tolerance in mobile IP systems | |
| JP4583433B2 (en) | Relay system | |
| JP4229291B2 (en) | Location information management server, location information management method | |
| CN102045687A (en) | Method and system for establishing association relationship of combined nodes | |
| US20080232354A1 (en) | Ip telephone system, ip exchange, ip terminal, ip exchange backup method, and login method for ip terminal | |
| CN102625406B (en) | A kind of application layer signalling route guard method and equipment | |
| JP4274380B2 (en) | Area information management server device, SIP server device, area information management method | |
| RU2360377C2 (en) | Double connection method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: NEW H3C TECHNOLOGIES Co.,Ltd. Address before: 310053 Hangzhou science and Technology Industrial Park, high tech Industrial Development Zone, Zhejiang Province, No. six and road, No. 310 Patentee before: HANGZHOU H3C TECHNOLOGIES Co.,Ltd. |
|
| CP03 | Change of name, title or address | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110420 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |