CN113746865B - Fault transfer method and device for VoIP terminal communication service - Google Patents
Fault transfer method and device for VoIP terminal communication service Download PDFInfo
- Publication number
- CN113746865B CN113746865B CN202111167740.0A CN202111167740A CN113746865B CN 113746865 B CN113746865 B CN 113746865B CN 202111167740 A CN202111167740 A CN 202111167740A CN 113746865 B CN113746865 B CN 113746865B
- Authority
- CN
- China
- Prior art keywords
- server
- target server
- request
- communication
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a fault transfer method and device for VoIP terminal communication service. The invention directly transmits the communication request to a standby server when the VoIP terminal abnormally responds to the communication request by the registered main server, and restores the communication service when the standby server normally responds to the communication request, and transmits the registration request to the standby server when the standby server abnormally responds to the communication request, if the standby server abnormally responds to the registration request, the communication request is continuously transmitted to the next standby server until the communication service can be restored on the currently inquired standby server or all the standby servers are inquired, thereby being capable of directly transferring the communication service to the standby server to operate when the registered main server of the VoIP terminal is down, being compatible with two scenes of communication service request processing to be carried out by registering and communication service request processing without registering, and being beneficial to improving the fault transfer efficiency of the communication service of the VoIP terminal.
Description
Technical Field
The present invention relates to the field of network communications technologies, and in particular, to a method and an apparatus for failover of a VoIP terminal communication service.
Background
Voice over IP (Voice over Internet Protocol, abbreviated VoIP) is a voice call technology that enables voice calls and multimedia conferences via Internet Protocol (IP), i.e., communications via the internet. The VoIP technology can be used for various internet access devices including VoIP phones, smartphones, personal computers, and the VoIP terminals interact data with servers of various VoIP service providers through cellular networks and WiFi to register, subscribe, talk, send short messages and other various VoIP services.
At present, most VoIP servers only support communication services such as subscription, conversation, short message sending and the like after successfully running registration services. When the main server registered by the VoIP terminal is down, the VoIP terminal needs to be registered on the standby server first to transfer the communication service to the standby server for operation, and the failure transfer efficiency of the communication service of the VoIP terminal is difficult to improve.
Disclosure of Invention
The invention provides a fault transfer method and a fault transfer device for a communication service of a VoIP terminal, which can directly transfer the communication service to a standby server for operation when a main server registered by the VoIP terminal is down, are compatible with two scenes that the communication service request processing can be carried out only after registration and the communication service request processing can be carried out even without registration, and are beneficial to improving the fault transfer efficiency of the communication service of the VoIP terminal.
In order to solve the above technical problem, in a first aspect, an embodiment of the present invention provides a method for failover of a VoIP terminal communication service, including:
when the communication request is successfully registered on the main server, sending a communication request to the main server, and when the main server abnormally responds to the communication request, selecting one standby server from all standby servers as a target server;
forwarding the communication request to the target server, and recovering the communication service corresponding to the communication request when the target server normally responds to the communication request;
when the target server abnormally responds to the communication request, a registration request is sent to the target server, and when the target server normally responds to the registration request, the communication request is forwarded to the target server again so as to recover the communication service;
and when the target server responds to the registration request abnormally, reselecting another standby server as a new target server, and retransmitting the communication request to the new target server until the communication service is restored or all the standby servers are selected.
Further, the selecting one standby server from all standby servers as the target server specifically includes:
and selecting the standby server with the highest priority from all the standby servers as the target server.
Further, when the target server responds to the communication request abnormally, a registration request is sent to the target server, specifically:
and when the response message of the target server to the communication request is not received within a first preset time, or the error response message of the target server to the communication request is received within the first preset time, sending the registration request to the target server.
Further, when the target server abnormally responds to the registration request, another standby server is reselected as a new target server, specifically:
and when the response message of the target server to the registration request is not received within a second preset time, or the error response message of the target server to the registration request is received within the second preset time, reselecting another standby server as the new target server.
In a second aspect, an embodiment of the present invention provides a failover apparatus for a VoIP terminal communication service, including a controller;
the controller is configured to perform:
when the communication request is successfully registered on the main server, sending a communication request to the main server, and when the main server abnormally responds to the communication request, selecting one standby server from all standby servers as a target server;
forwarding the communication request to the target server, and recovering the communication service corresponding to the communication request when the target server normally responds to the communication request;
when the target server abnormally responds to the communication request, a registration request is sent to the target server, and when the target server normally responds to the registration request, the communication request is forwarded to the target server again so as to recover the communication service;
and when the target server responds to the registration request abnormally, reselecting another standby server as a new target server, and retransmitting the communication request to the new target server until the communication service is restored or all the standby servers are selected.
Further, the selecting one standby server from all standby servers as the target server specifically includes:
and selecting the standby server with the highest priority from all the standby servers as the target server.
Further, when the target server responds to the communication request abnormally, a registration request is sent to the target server, specifically:
and when the response message of the target server to the communication request is not received within a first preset time, or the error response message of the target server to the communication request is received within the first preset time, sending the registration request to the target server.
Further, when the target server abnormally responds to the registration request, another standby server is reselected as a new target server, specifically:
and when the response message of the target server to the registration request is not received within a second preset time, or the error response message of the target server to the registration request is received within the second preset time, reselecting another standby server as the new target server.
The embodiment of the invention has the following beneficial effects:
by sending a communication request to a main server when the communication request is successfully registered on the main server, selecting one standby server from all standby servers as a target server when the main server abnormally responds to the communication request, forwarding the communication request to the target server, recovering a communication service corresponding to the communication request when the target server normally responds to the communication request, sending a registration request to the target server when the target server abnormally responds to the communication request, and re-forwarding the communication request to the target server to recover the communication service when the target server normally responds to the registration request, re-selecting another standby server as a new target server when the target server abnormally responds to the registration request, and re-forwarding the communication request to the new target server until the communication service is recovered or all the standby servers have been selected, the fault transfer of the VoIP terminal communication service is realized. Compared with the prior art, the embodiment of the invention directly forwards the communication request to the standby server when the main server registered by the VoIP terminal abnormally responds to the communication request, and restores the communication service when the standby server normally responds to the communication request, and sends the registration request to the standby server when the standby server abnormally responds to the communication request, if the standby server abnormally responds to the registration request, the communication request is continuously forwarded to the next standby server until the communication service can be restored on the currently inquired standby server or all the standby servers are inquired, thereby being capable of directly transferring the communication service to the standby server to operate when the main server registered by the VoIP terminal is down, being compatible with two scenes of communication service request processing to be carried out after registration and communication service request processing without registration, and being beneficial to improving the fault transfer efficiency of the communication service of the VoIP terminal.
Drawings
Fig. 1 is a flow chart of a method for failover of a VoIP terminal communication service in a first embodiment of the present invention;
fig. 2 is another flow chart of a failover method of a VoIP terminal communication service in a first embodiment of the present invention;
fig. 3 is a schematic structural diagram of a failover apparatus for VoIP terminal communication service according to a second embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made more apparent and fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be noted that, the step numbers herein are only for convenience of explanation of the specific embodiments, and are not used as limiting the order of execution of the steps. The method provided in this embodiment may be performed by a relevant terminal device, and the following description will take a VoIP terminal as an execution body.
As shown in fig. 1, a first embodiment provides a failover method of a VoIP terminal communication service, including steps S1 to S4:
s1, when successfully registered on a main server, sending a communication request to the main server, and when the main server abnormally responds to the communication request, selecting a standby server from all standby servers as a target server;
s2, forwarding a communication request to a target server, and recovering a communication service corresponding to the communication request when the target server normally responds to the communication request;
s3, when the target server abnormally responds to the communication request, a registration request is sent to the target server, and when the target server normally responds to the registration request, the communication request is forwarded to the target server again so as to recover the communication service;
s4, when the target server abnormally responds to the registration request, another standby server is reselected to serve as a new target server, and the communication request is retransmitted to the new target server until the communication service is restored or all the standby servers are selected.
Note that, the main server includes a UDP, TCP, TLS type server, and the standby server also includes a UDP, TCP, TLS type server; both the primary and backup servers support any type of transport protocol, preferably UDP, TCP, TLS type.
As an example, the VoIP terminal parses a plurality of servers IP1, IP2, IP3 from the registered domain name through the domain name server, and selects the server IP1 parsed first from the servers as a main server according to the parsing order IP1→ip2→ip3 of the servers, and both the remaining servers IP2, IP3 as standby servers, and sends a registration request to the main server IP1 to be successfully registered on the main server IP 1.
The server analysis process comprises the steps of executing the inquiry according to the filled registration information, inquiring the transmission type of registration by the dns naptr, inquiring the registration port by the dns srv, inquiring the registered IP address by the dns A and inquiring the dns server address by the dns A.
When the VoIP terminal successfully registers on the main server IP1, the VoIP terminal sends a communication request to the main server IP1 according to a communication requirement, for example, subscribes, calls or sends various communication service requests such as a short message, and when the main server IP1 normally responds to the communication request, the main server IP1 is considered to be in a normal available state, at this time, the VoIP terminal can normally operate the communication service, when the main server IP1 abnormally responds to the communication request, for example, the main server receives 503 an unreachable response, and considers that the main server IP1 is in a fault unavailable state, for example, a downtime problem occurs, at this time, the VoIP terminal triggers a fault transfer mechanism of the communication service, and selects a standby server IP2 which is first resolved from all standby servers as a target server according to a resolving sequence IP 2-IP 3 of all standby servers.
And forwarding the communication request to the target server IP2, and when the target server IP2 normally responds to the communication request, considering that the target server IP2 can operate the communication service in a registration-free state, immediately recovering the communication service corresponding to the communication request.
When the target server IP2 responds to the communication request abnormally, it is considered that the target server IP2 cannot operate the communication service in the no-registration state, and the registration request is sent to the target server IP 2.
When the target server IP2 normally responds to the registration request, the communication request is re-forwarded to the target server IP2 to restore the communication service.
When the target server IP2 responds to the registration request abnormally, the server IP3 which is analyzed first is selected from the rest standby servers as a new target server according to the analysis sequence IP 2-IP 3 of all the standby servers.
And forwarding the communication request to the target server IP3, and when the target server IP3 normally responds to the communication request, considering that the target server IP3 can operate the communication service in a registration-free state, immediately recovering the communication service corresponding to the communication request.
When the target server IP3 responds to the communication request abnormally, it is considered that the target server IP3 cannot operate the communication service in the no-registration state, and the registration request is transmitted to the target server IP 3.
When the target server IP3 normally responds to the registration request, the communication request is re-forwarded to the target server IP3 to resume the communication service.
When the target server IP3 responds to the registration request abnormally, since all the standby servers have been queried at this time, all the standby servers cannot operate the communication service and cannot register in the no-registration state, and then the registration request and/or the communication request is sent to the main server IP1 again after a certain time.
Considering that two types of servers are available, one can operate communication service in no registration state, and the other can only operate communication service in registration state, in this embodiment, by forwarding communication request directly to a standby server by VoIP terminal when the registered main server cannot respond to communication request abnormally, and recovering communication service when standby server responds to communication request normally, when standby server responds to communication request abnormally, initiating registration request to standby server, when registering to standby server successfully, re-initiating corresponding subscription, conversation or other non-registration service, when registering to standby server fails, continuing forwarding communication request to next standby server, and repeating the cycle until communication service can be recovered on currently queried standby server or all standby servers have been queried, thereby being capable of directly transferring communication service to standby server to operate when the registered main server of VoIP terminal is down, being compatible with two scenes of processing communication service request to be registered and processing communication service request to be performed, and being beneficial to improving failure transfer efficiency of VoIP terminal communication service.
In a preferred embodiment, the selecting a standby server from all standby servers as the target server is specifically: and selecting the standby server with the highest priority from all the standby servers as a target server.
In a preferred implementation of this embodiment, before the standby server with the highest priority is selected from all the standby servers as the target server, the priority of each standby server is defined according to the parsing order of all the standby servers.
Illustratively, the standby server that is first parsed out is selected from all standby servers as the target server.
In a preferred embodiment, when the target server responds to the communication request abnormally, a registration request is sent to the target server, specifically: and when the response message of the target server to the communication request is not received within the first preset time, or the error response message of the target server to the communication request is received within the first preset time, sending a registration request to the target server.
As an example, when a response message of the target server to the communication request is not received within the first preset time, or an error response message of the target server to the communication request is received within the first preset time, it is determined that the target server abnormally responds to the communication request, and the target server is considered to be unable to run the communication service in the unregistered state, the registration request is transmitted to the target server.
In a preferred embodiment, when the target server responds to the registration request abnormally, another standby server is reselected as a new target server, specifically: and when the response message of the target server to the registration request is not received within the second preset time, or the error response message of the target server to the registration request is received within the second preset time, reselecting another standby server as a new target server.
As an example, when a response message of the target server to the registration request is not received within the second preset time, or an error response message of the target server to the registration request is received within the second preset time, it is determined that the target server abnormally responds to the registration request, and it is considered that the target server cannot register, another standby server is reselected as a new target server.
As shown in fig. 3, a second embodiment provides a failover apparatus for VoIP terminal communication service, comprising a controller 21; a controller 21 for performing: when the communication request is successfully registered on the main server, sending a communication request to the main server, and when the main server abnormally responds to the communication request, selecting a standby server from all standby servers as a target server; forwarding a communication request to a target server, and recovering a communication service corresponding to the communication request when the target server normally responds to the communication request; when the target server responds to the communication request abnormally, a registration request is sent to the target server, and when the target server responds to the registration request normally, the communication request is forwarded to the target server again, so that the communication service is recovered; when the target server responds to the registration request abnormally, another standby server is reselected as a new target server, and the communication request is retransmitted to the new target server until the communication service is restored or all standby servers are selected.
Note that, the main server includes a UDP, TCP, TLS type server, and the standby server also includes a UDP, TCP, TLS type server; both the primary and backup servers support any type of transport protocol, preferably UDP, TCP, TLS type.
As an example, the VoIP terminal parses a plurality of servers IP1, IP2, IP3 from the registered domain name through the domain name server, and selects the server IP1 parsed first from the servers as a main server according to the parsing order IP1→ip2→ip3 of the servers, and both the remaining servers IP2, IP3 as standby servers, and sends a registration request to the main server IP1 to be successfully registered on the main server IP 1.
The server analysis process comprises the steps of executing the inquiry according to the filled registration information, inquiring the transmission type of registration by the dns naptr, inquiring the registration port by the dns srv, inquiring the registered IP address by the dns A and inquiring the dns server address by the dns A.
When the VoIP terminal successfully registers on the main server IP1, the VoIP terminal sends a communication request to the main server IP1 according to a communication requirement, for example, subscribes, calls or sends various communication service requests such as a short message, and when the main server IP1 normally responds to the communication request, the main server IP1 is considered to be in a normal available state, at this time, the VoIP terminal can normally operate the communication service, when the main server IP1 abnormally responds to the communication request, for example, the main server receives 503 an unreachable response, and considers that the main server IP1 is in a fault unavailable state, for example, a downtime problem occurs, at this time, the VoIP terminal triggers a fault transfer mechanism of the communication service, and selects a standby server IP2 which is first resolved from all standby servers as a target server according to a resolving sequence IP 2-IP 3 of all standby servers.
And forwarding the communication request to the target server IP2, and when the target server IP2 normally responds to the communication request, considering that the target server IP2 can operate the communication service in a registration-free state, immediately recovering the communication service corresponding to the communication request.
When the target server IP2 responds to the communication request abnormally, it is considered that the target server IP2 cannot operate the communication service in the no-registration state, and the registration request is sent to the target server IP 2.
When the target server IP2 normally responds to the registration request, the communication request is re-forwarded to the target server IP2 to restore the communication service.
When the target server IP2 responds to the registration request abnormally, the server IP3 which is analyzed first is selected from the rest standby servers as a new target server according to the analysis sequence IP 2-IP 3 of all the standby servers.
And forwarding the communication request to the target server IP3, and when the target server IP3 normally responds to the communication request, considering that the target server IP3 can operate the communication service in a registration-free state, immediately recovering the communication service corresponding to the communication request.
When the target server IP3 responds to the communication request abnormally, it is considered that the target server IP3 cannot operate the communication service in the no-registration state, and the registration request is transmitted to the target server IP 3.
When the target server IP3 normally responds to the registration request, the communication request is re-forwarded to the target server IP3 to resume the communication service.
When the target server IP3 responds to the registration request abnormally, since all the standby servers have been queried at this time, all the standby servers cannot operate the communication service and cannot register in the no-registration state, and then the registration request and/or the communication request is sent to the main server IP1 again after a certain time.
Considering that two types of servers are available, one can operate communication service in no registration state, and the other can only operate communication service in registration state, in this embodiment, by forwarding communication request directly to a standby server by VoIP terminal when the registered main server cannot respond to communication request abnormally, and recovering communication service when standby server responds to communication request normally, when standby server responds to communication request abnormally, initiating registration request to standby server, when registering to standby server successfully, re-initiating corresponding subscription, conversation or other non-registration service, when registering to standby server fails, continuing forwarding communication request to next standby server, and repeating the cycle until communication service can be recovered on currently queried standby server or all standby servers have been queried, thereby being capable of directly transferring communication service to standby server to operate when the registered main server of VoIP terminal is down, being compatible with two scenes of processing communication service request to be registered and processing communication service request to be performed, and being beneficial to improving failure transfer efficiency of VoIP terminal communication service.
In a preferred embodiment, the selecting a standby server from all standby servers as the target server is specifically: and selecting the standby server with the highest priority from all the standby servers as a target server.
In a preferred implementation of this embodiment, before the standby server with the highest priority is selected from all the standby servers as the target server, the priority of each standby server is defined according to the parsing order of all the standby servers.
Illustratively, the standby server that is first parsed out is selected from all standby servers as the target server.
In a preferred embodiment, when the target server responds to the communication request abnormally, a registration request is sent to the target server, specifically: and when the response message of the target server to the communication request is not received within the first preset time, or the error response message of the target server to the communication request is received within the first preset time, sending a registration request to the target server.
As an example, when a response message of the target server to the communication request is not received within the first preset time, or an error response message of the target server to the communication request is received within the first preset time, it is determined that the target server abnormally responds to the communication request, and the target server is considered to be unable to run the communication service in the unregistered state, the registration request is transmitted to the target server.
In a preferred embodiment, when the target server responds to the registration request abnormally, another standby server is reselected as a new target server, specifically: and when the response message of the target server to the registration request is not received within the second preset time, or the error response message of the target server to the registration request is received within the second preset time, reselecting another standby server as a new target server.
As an example, when a response message of the target server to the registration request is not received within the second preset time, or an error response message of the target server to the registration request is received within the second preset time, it is determined that the target server abnormally responds to the registration request, and it is considered that the target server cannot register, another standby server is reselected as a new target server.
In summary, the embodiment of the invention has the following beneficial effects:
by sending a communication request to a main server when the communication request is successfully registered on the main server, selecting one standby server from all standby servers as a target server when the main server abnormally responds to the communication request, forwarding the communication request to the target server, recovering a communication service corresponding to the communication request when the target server normally responds to the communication request, sending a registration request to the target server when the target server abnormally responds to the communication request, and re-forwarding the communication request to the target server to recover the communication service when the target server normally responds to the registration request, re-selecting another standby server as a new target server when the target server abnormally responds to the registration request, and re-forwarding the communication request to the new target server until the communication service is recovered or all the standby servers have been selected, the fault transfer of the VoIP terminal communication service is realized. According to the embodiment of the invention, the VoIP terminal directly forwards the communication request to one standby server when the registered main server abnormally responds to the communication request, and when the standby server normally responds to the communication request, the communication service is restored, when the standby server abnormally responds to the communication request, the registration request is sent to the standby server, if the standby server abnormally responds to the registration request, the communication request is forwarded to the next standby server continuously until the communication service can be restored on the currently inquired standby server or all the standby servers are inquired, so that the communication service can be directly transferred to the standby server to operate when the registered main server of the VoIP terminal is down, and two scenes of communication service request processing only when the registration is needed and communication service request processing can be carried out when no registration is needed are compatible, thereby being beneficial to improving the failover efficiency of the communication service of the VoIP terminal.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that changes and modifications may be made without departing from the principles of the invention, such changes and modifications are also intended to be within the scope of the invention.
Those skilled in the art will appreciate that implementing all or part of the above-described embodiments may be accomplished by way of computer programs, which may be stored on a computer readable storage medium, which when executed may comprise the steps of the above-described embodiments. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.
Claims (4)
1. A method for failover of a VoIP terminal communication service, comprising:
when the communication request is successfully registered on the main server, sending a communication request to the main server, and when the main server abnormally responds to the communication request, selecting one standby server from all standby servers as a target server;
forwarding the communication request to the target server, and recovering the communication service corresponding to the communication request when the target server normally responds to the communication request;
when the target server responds to the communication request abnormally, a registration request is sent to the target server, specifically: when a response message of the target server to the communication request is not received within a first preset time, or an error response message of the target server to the communication request is received within the first preset time, sending the registration request to the target server; and when the target server normally responds to the registration request, retransmitting the communication request to the target server again so as to recover the communication service;
when the target server abnormally responds to the registration request, another standby server is reselected as a new target server, specifically: when a response message of the target server to the registration request is not received within a second preset time, or an error response message of the target server to the registration request is received within the second preset time, reselecting another standby server as the new target server; and re-forwarding the communication request to the new target server until the communication service is restored or all of the standby servers have been selected.
2. The method for failover of VoIP terminal communication traffic of claim 1, wherein selecting one of the backup servers as the target server from all backup servers comprises:
and selecting the standby server with the highest priority from all the standby servers as the target server.
3. A device for transferring a communication service of a VoIP terminal, comprising a controller;
the controller is configured to perform:
when the communication request is successfully registered on the main server, sending a communication request to the main server, and when the main server abnormally responds to the communication request, selecting one standby server from all standby servers as a target server;
forwarding the communication request to the target server, and recovering the communication service corresponding to the communication request when the target server normally responds to the communication request;
when the target server responds to the communication request abnormally, a registration request is sent to the target server, specifically: when a response message of the target server to the communication request is not received within a first preset time, or an error response message of the target server to the communication request is received within the first preset time, sending the registration request to the target server; and when the target server normally responds to the registration request, retransmitting the communication request to the target server again so as to recover the communication service;
when the target server abnormally responds to the registration request, another standby server is reselected as a new target server, specifically: when a response message of the target server to the registration request is not received within a second preset time, or an error response message of the target server to the registration request is received within the second preset time, reselecting another standby server as the new target server; and re-forwarding the communication request to the new target server until the communication service is restored or all of the standby servers have been selected.
4. A device for failover of VoIP terminal traffic according to claim 3, characterized in that the selecting one of the backup servers as the target server is:
and selecting the standby server with the highest priority from all the standby servers as the target server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111167740.0A CN113746865B (en) | 2021-09-30 | 2021-09-30 | Fault transfer method and device for VoIP terminal communication service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111167740.0A CN113746865B (en) | 2021-09-30 | 2021-09-30 | Fault transfer method and device for VoIP terminal communication service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113746865A CN113746865A (en) | 2021-12-03 |
| CN113746865B true CN113746865B (en) | 2023-06-20 |
Family
ID=78725997
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111167740.0A Active CN113746865B (en) | 2021-09-30 | 2021-09-30 | Fault transfer method and device for VoIP terminal communication service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113746865B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101964806A (en) * | 2010-11-02 | 2011-02-02 | 深圳市共进电子有限公司 | Method for switching servers of SIP (Session Initiation Protocol) communication terminal |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101674313A (en) * | 2009-10-15 | 2010-03-17 | 杭州华三通信技术有限公司 | SIP registration method for server to actively inform user switching, system and device thereof |
| CN102684895B (en) * | 2011-03-09 | 2015-04-01 | 鸿富锦精密工业（深圳）有限公司 | Standby server and system and method for restoring registration of client side in master server |
| CN104065500A (en) * | 2013-03-21 | 2014-09-24 | 苏州方位通讯科技有限公司 | Register server hot backup method realized by SIP terminal |
| CN106936784B (en) * | 2015-12-30 | 2020-12-29 | 青岛海信宽带多媒体技术有限公司 | SIP (Session initiation protocol) registration method, terminal and system |
| CN112532452B (en) * | 2020-11-30 | 2023-10-31 | 厦门亿联网络技术股份有限公司 | Method, device, equipment and storage medium for switching main server and standby server of communication terminal |
-
2021
- 2021-09-30 CN CN202111167740.0A patent/CN113746865B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101964806A (en) * | 2010-11-02 | 2011-02-02 | 深圳市共进电子有限公司 | Method for switching servers of SIP (Session Initiation Protocol) communication terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113746865A (en) | 2021-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5865404B2 (en) | Gateway for enterprise network survivability using SIP | |
| US9319431B2 (en) | Methods, systems, and computer readable media for providing sedation service in a telecommunications network | |
| US8374079B2 (en) | Proxy server, communication system, communication method and program | |
| US8296447B2 (en) | Method for copying session information, call control server for executing the same, and computer product | |
| JP5173607B2 (en) | Communications system | |
| KR20050122227A (en) | System and method to provide interoperability between session initiation protocol and other messaging services | |
| CN103891255B (en) | Method for sip agent failover | |
| US8930768B2 (en) | System and method of failover for an initiated SIP session | |
| CN101606378A (en) | The method and system that is used for communication session initialization in the communication network | |
| CN103618747A (en) | Method and system for realizing session initiation protocol (SIP) information service | |
| CN113746865B (en) | Fault transfer method and device for VoIP terminal communication service | |
| US20230231731A1 (en) | Conference system | |
| US8117311B2 (en) | Communication method, server and medium on notification of session status | |
| CN113595765A (en) | Method and device for fault transfer of VoIP terminal registration service | |
| CN109120578B (en) | Method and device for realizing link connection processing | |
| CN110784943B (en) | Processing method and device for VoWiFi voice service disconnection and reconnection | |
| CN113992500B (en) | Main and standby server switching method and device suitable for VoIP terminal | |
| EP4274188B1 (en) | Switchover to another outbound p-cscf initiated by an ims of a communication network | |
| US20090228596A1 (en) | Method, server and terminal for implementing call directions | |
| EP4287583A1 (en) | Session border controller (sbc) system | |
| JP2010171852A (en) | Charging data generating method, call control method, communication system, information processing apparatus, and session control server for relaying | |
| CN113438220B (en) | Method for converting IP address in soft switching communication system and soft switching communication system | |
| WO2009136823A1 (en) | A terminal and a method for enabling the terminal to reach another terminal | |
| JP2014007617A (en) | Call control server, communication system, and call control method | |
| JP2010183480A (en) | Apparatus and method for controlling request transmission, system, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |