A method, apparatus and system for restoring VoIP call links

Abstract

This invention discloses a VoIP call link recovery method, apparatus, and system. When a terminal loses its link with the registration server, it first determines whether the user is currently in a call. If so, it initiates a registration recovery request to the registration server and sends a registration renewal packet. Upon receiving the registration renewal packet, the registration server responds with signaling and checks the terminal's response. If the response is normal, the terminal sends a reINVITE packet to the registration server, triggering a link update between the registration server and the MCU server. The registration server then sends the reINVITE packet to the MCU server, and the MCU re-records the terminal's network information. This method achieves seamless reconnection of the registration link, effectively improving user call efficiency and experience.

Description

Technical Field

[0001] This invention relates to the field of link recovery, and more particularly to a method, apparatus and system for VoIP call link recovery. Background Technology

[0002] Currently, VoIP deployments typically separate the registration service and the call service. After a terminal establishes a reliable connection with the registration service, subsequent calls reuse this link, so the call service records the terminal's link information. If, during a call, the registration link is lost due to various network issues, the call service does not update the link information after the registration link reconnects and continues to use the old link. Updates are only made when the call process is triggered, causing any subsequent call announcements or call controls issued by the call service to fail to reach the terminal. Summary of the Invention

[0003] This invention provides a VoIP call link recovery method, system, device, and medium, which enables seamless recovery of the call link after the registration link is disconnected, thereby improving call efficiency and experience.

[0004] To address the aforementioned technical problems, embodiments of the present invention provide a VoIP call link recovery method, comprising:

[0005] Collect the call status after the registration link with the first server is disconnected, and determine whether to reconnect the registration link based on the call status;

[0006] If the call status is "in progress", the registration link information will be reconnected according to the preset method.

[0007] If the call status is "not in a call," then report the user registration failure.

[0008] In this embodiment, when the terminal loses connection with the registration server, it first determines whether the user is in a call. If the user is in a call, it sends a registration recovery request to the registration server to seamlessly reconnect the registration link, thereby improving the user's call efficiency and experience.

[0009] As a preferred solution, the registration link is reconnected according to a preset method, specifically:

[0010] Initiate a registration recovery request to the first server and send the registration renewal package to the first server;

[0011] The registration link is updated based on the response status of the first server to the registration renewal package.

[0012] In this embodiment, the terminal initiates the registration service recovery and sends a registration renewal packet to the registration server. After receiving the registration renewal packet, the registration server responds by checking whether the terminal's response is normal. If the response is normal, the server starts the link update, thereby achieving seamless reconnection of the registration link.

[0013] As a preferred solution, the registration process is updated as follows:

[0014] Send the reINVITE packet data to the first server;

[0015] After receiving the reINVITE packet data, the first server sends it to the second server;

[0016] The second server receives the reINVITE packet data and updates the registration link based on the reINVITE packet data.

[0017] In this implementation, when updating the link, the terminal sends a reINVITE packet to the registration server, triggering a link update between the registration server and the MCU server. The registration server then sends the reINVITE packet to the MCU server, and the MCU re-records the terminal's network information. This method achieves seamless reconnection to the registration link, which can effectively improve user call efficiency and experience.

[0018] As a preferred solution, the reINVITE packet data is sent to the first server, specifically as follows:

[0019] Collect information data from the existing INVITE packet data in the first server, including CALL-ID, From-tag, and To-Tag;

[0020] The information data is stored in the reINVITE packet data and sent to the first server.

[0021] As a preferred option, the reINVITE packet data includes the terminal IP, terminal disconnection, TCP terminal protocol, TLS terminal protocol, and terminal socket.

[0022] As a preferred option, after reconnecting the registration link, the terminal device can receive all call notifications and call controls sent by the second server.

[0023] To address the aforementioned technical problems, embodiments of the present invention provide a VoIP call link recovery device, comprising an information collection module, an information judgment module, and an information request module;

[0024] The information collection module is used to collect the call status after the connection with the first server registration link is broken;

[0025] The information judgment module is used to determine whether to reconnect to the registration link based on the call status;

[0026] The information request module is used to initiate a registration recovery request from the first server so that the first server can reconnect to the registration link.

[0027] As a preferred embodiment, the information request module includes a sending unit and an updating unit;

[0028] The sending unit is used to initiate a registration recovery request to the first server and send the registration renewal packet to the first server;

[0029] The update unit is used to update the registration link based on the response status of the first server to the registration renewal packet.

[0030] To address the aforementioned technical problems, this invention provides a VoIP call link recovery system, comprising a VoIP call link recovery device, a registration server, and an MCU server, wherein the VoIP call link recovery device executes the VoIP call link recovery method as described in this invention.

[0031] The VoIP call link recovery device is connected to the registration server, and the registration server is connected to the MCU server.

[0032] As a preferred embodiment, the registration server is used to receive registration recovery requests so that the first server can reconnect to the registration link;

[0033] The VoIP call link recovery device is used to collect the call status after the connection with the first server registration link is disconnected, and to determine whether to reconnect the registration link based on the call status. If the call status is in progress, the registration link is reconnected according to a preset method. If the call status is out of progress, the registration link is disconnected.

[0034] The MCU server is used to receive reINVITE packet data and update the registration link based on the reINVITE packet data.

[0035] In this embodiment, when the terminal loses its connection with the registration server, it first determines whether the user is in a call. If in a call, it initiates a registration recovery request to the registration server and sends a registration renewal packet to the registration server. After receiving the registration renewal packet, the registration server responds and checks the terminal's response. If the response is normal, the terminal sends a reINVITE packet to the registration server, triggering a link update between the registration server and the MCU server. The registration server then sends the reINVITE packet to the MCU server, and the MCU re-records the terminal's network information. This method achieves seamless reconnection of the registration link, effectively improving user call efficiency and experience. Attached Figure Description

[0036] Figure 1 : A flowchart illustrating an embodiment of a VoIP call link recovery method provided by the present invention;

[0037] Figure 2 : A registration flowchart of an embodiment of a VoIP call link recovery method provided by the present invention;

[0038] Figure 3 : This is a schematic diagram of another embodiment of a VoIP call link recovery device provided by the present invention. Detailed Implementation

[0039] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0040] Example 1

[0041] Please refer to Figure 1 This invention provides a VoIP call link recovery method, which includes steps 101 to 103, each of which is detailed below:

[0042] Step 101: Collect the call status after the registration link with the first server is disconnected, and determine whether to reconnect the registration link based on the call status.

[0043] In this embodiment, if the terminal loses connection with the registration server due to network jitter or other network reasons, the system determines whether the terminal is still in a call after the connection with the first server is lost by checking whether the phone is still in a call interface or whether the server has call resources occupied by the account. Based on the call status, the system determines whether to reconnect the registration link.

[0044] Optionally, the registration link can be reconnected according to a preset method, specifically:

[0045] Initiate a registration recovery request to the first server and send the registration renewal package to the first server;

[0046] The registration link is updated based on the response status of the first server to the registration renewal package.

[0047] Step 102: If the call status is "in a call", then reconnect the registration link according to the preset method.

[0048] In this embodiment, if the call status is determined to be in progress, no user registration failure is reported. Instead, a seamless reconnection of the registration link is initiated. After the link is successfully reconnected, the terminal initiates registration service recovery using a TCP or TLS connection and sends a registration renewal packet. The Call-ID, from-tag, and to-tag of the signaling are the same as those sent to the server in the previous registration signaling. If the server responds with a 200 OK response to the registration renewal packet, it indicates that the link has been successfully reconnected. At this point, a reINVITE packet is initiated, with the Call-ID, from-tag, and to-tag of the signaling being the same as those sent to the server in the previous INVITE signaling. This triggers a link update between the registration service and the MCU service. The MCU re-records the terminal's network information, which includes, but is not limited to, the terminal IP, terminal disconnection, TCP terminal protocol, TLS terminal protocol, and terminal socket. Any subsequent call announcements and call controls issued by the MCU can be sent to the terminal.

[0049] As an example of this embodiment, such as Figure 2 As shown, the terminal initiates a registration service with the registration server. After establishing a TCP or TLS connection, the terminal initiates a call. The connection is multiplexed during registration. Once the call signaling reaches the registration server, it is forwarded to the MCU server. The MCU service records the terminal's network information, including the terminal's IP address, connection status, terminal protocol (TCP / TLS), and terminal socket.

[0050] Due to network jitter or other network issues, the terminal loses connection with the registration server. In this case, the user assumes a call is in progress and therefore does not report a registration failure. Instead, a seamless reconnection to the registration link is initiated. Once the reconnection is successful, the registration service is restored, and a registration renewal packet is sent to the registration server. The Call-ID, from-tag, and to-tag of this packet are the same as the previous registration signaling sent to the server. If the server responds with a 200 OK response, it indicates that the registration service has successfully reconnected. At this point, a reINVITE packet is initiated to trigger a link update between the registration service and the MCU service. The Call-ID, from-tag, and to-tag of this packet are the same as the previous INVITE signaling sent to the server. The MCU then re-records the terminal's IP address, the connection status, the terminal protocol (TCP / TLS), and the terminal socket information. Any subsequent call announcements and call control messages issued by the MCU can then be sent to the terminal.

[0051] Optionally, update the registration link, specifically:

[0052] Send the reINVITE packet data to the first server;

[0053] After receiving the reINVITE packet data, the first server sends it to the second server;

[0054] The second server receives the reINVITE packet data and updates the registration link based on the reINVITE packet data.

[0055] Optionally, the reINVITE packet data is sent to the first server, specifically as follows:

[0056] Collect information data from the existing INVITE packet data in the first server, including CALL-ID, From-tag, and To-Tag;

[0057] The information data is stored in the reINVITE packet data and sent to the first server.

[0058] Optionally, the reINVITE packet data includes the terminal IP, terminal disconnection, TCP terminal protocol, TLS terminal protocol, and terminal socket.

[0059] In this embodiment, the reINVITE packet data includes, but is not limited to, the terminal IP, terminal disconnection, TCP terminal protocol, TLS terminal protocol, and terminal socket.

[0060] Optionally, after reconnecting the registration link, the terminal device can receive all call announcements and call controls sent by the second server.

[0061] Step 103: If the call status is "not in a call", report the user registration failure.

[0062] In this embodiment, if the terminal loses its connection with the registration server due to network jitter or other network reasons, and the user is not on a call, the user registration failure will be reported.

[0063] By sending a registration recovery request to the registration server and concurrently sending a registration renewal packet to the registration server, the registration server receives the registration renewal packet and responds with a signaling message. If the response is normal, the terminal sends a reINVITE packet to the registration server, triggering a link update between the registration server and the MCU server. The registration server then sends the reINVITE packet to the MCU server, and the MCU re-records the terminal's network information. This method achieves seamless reconnection of the registration link, which can effectively improve user call efficiency and experience.

[0064] Example 2

[0065] Accordingly, see Figure 3 , Figure 3This is a schematic diagram of an embodiment of the VoIP call link recovery device provided by the present invention. As shown in the figure, the VoIP call link recovery device includes: an information acquisition module 301, an information judgment module 302, and an information request module 303, wherein the specific units of each module are as follows:

[0066] The information collection module 301 is used to collect the call status after the connection with the first server registration link is broken;

[0067] The information judgment module 302 is used to determine whether to reconnect to the registration link based on the call status;

[0068] The information request module 303 is used for the registration recovery request initiated by the first server to enable the first server to reconnect to the registration link.

[0069] In this embodiment, the information request module 303 includes a sending unit 3031 and an updating unit 3032;

[0070] The sending unit 3031 is used to initiate a registration recovery request to the first server and send the registration renewal package to the first server;

[0071] The update unit 3032 is used to update the registration link according to the response status of the first server to the registration renewal package.

[0072] For a more detailed explanation of the working principle and process of this embodiment, please refer to the relevant description in Embodiment 1.

[0073] The VoIP call link recovery device is used for VoIP call link recovery. When the terminal loses its link with the registration server, it first determines whether the user is in a call. If in a call, it sends a registration recovery request to the registration server and sends a registration renewal packet to the registration server. After receiving the registration renewal packet, the registration server responds and checks the terminal's response. If the response is normal, the terminal sends a reINVITE packet to the registration server, triggering a link update between the registration server and the MCU server. The registration server then sends the reINVITE packet to the MCU server, and the MCU re-records the terminal's network information. This method achieves seamless reconnection of the registration link, effectively improving user call efficiency and experience.

[0074] Example 3

[0075] Accordingly, the VoIP call link recovery system provided by the present invention includes a VoIP call link recovery device, a registration server, and an MCU server.

[0076] The VoIP call link recovery device performs the VoIP call link recovery method as described in Example 1.

[0077] The VoIP call link restoration device is connected to the registration server, and the registration server is connected to the MCU server.

[0078] In this embodiment, the registration server is used to receive a registration recovery request so that the first server can reconnect to the registration link;

[0079] The VoIP call link recovery device is used to collect the call status after the connection with the first server registration link is disconnected, and to determine whether to reconnect the registration link based on the call status. If the call status is in progress, the registration link is reconnected according to a preset method. If the call status is out of progress, the registration link is disconnected.

[0080] The MCU server is used to receive reINVITE packet data and update the registration link based on the reINVITE packet data information.

[0081] For a more detailed explanation of the working principle and process of this embodiment, please refer to the relevant description in Embodiment 1.

[0082] Compared to existing technologies, this invention provides a VoIP call link recovery method. When the terminal loses its link with the registration server, it first determines whether the user is currently in a call. If so, it initiates a registration recovery request to the registration server and sends a registration renewal packet. Upon receiving the registration renewal packet, the registration server responds with signaling and checks the terminal's response. If the response is normal, the terminal sends a reINVITE packet to the registration server, triggering a link update between the registration server and the MCU server. The registration server then sends the reINVITE packet to the MCU server, and the MCU re-records the terminal's network information. This method achieves seamless reconnection of the registration link, effectively improving user call efficiency and experience.

[0083] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. In particular, it should be noted that any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention for those skilled in the art.

Claims

1. A method for restoring a VoIP call link, characterized in that, include Collect the call status after the registration link with the first server is disconnected, and determine whether to reconnect the registration link based on the call status; If the call status is "in a call", the registration link will be reconnected according to the preset method. If the call status is "not in a call", then report the user registration failure. Determining whether to reconnect to the registration link based on the call status is as follows: The system determines whether the user is still in a call after the connection with the first server is broken by checking whether the phone is still in a call interface or whether the server has call resources occupied by the account. When reconnecting the registration link according to the preset method, specifically: Send a reINVITE packet to the first server to trigger a link update between the first server and the second server.

2. The VoIP call link recovery method as described in claim 1, characterized in that, The reconnection of the registration link according to the preset method specifically includes: The system initiates a registration recovery request to the first server and sends a registration renewal package to the first server. The registration link is updated based on the response status of the first server to the registration renewal package.

3. The VoIP call link recovery method as described in claim 2, characterized in that, The update registration link is as follows: Send the reINVITE packet data to the first server; After receiving the reINVITE packet data, the first server sends it to the second server; The second server receives the reINVITE packet data and updates the registration link based on the reINVITE packet data.

4. The VoIP call link recovery method as described in claim 3, characterized in that, Sending the reINVITE packet data to the first server specifically involves: Collect information data from the existing INVITE packet data in the first server, wherein the information data includes CALL-ID, From-tag, and To-Tag; The information data is stored in the reINVITE packet data and sent to the first server.

5. The VoIP call link recovery method as described in claim 3, characterized in that, The reINVITE packet data includes the terminal IP, terminal disconnection, TCP terminal protocol, TLS terminal protocol, and terminal socket.

6. The VoIP call link recovery method as described in claim 1, characterized in that, After the registration link is reconnected, the terminal device can receive all call notifications and call controls sent by the second server.

7. A VoIP call link restoration device, characterized in that, include: Information collection module, information judgment module, and information request module; The information collection module is used to collect the call status after the connection with the first server registration link is broken; The information judgment module is used to determine whether to reconnect to the registration link based on the call status; The information request module is used to initiate a registration recovery request from the first server so that the first server can reconnect to the registration link; Determining whether to reconnect to the registration link based on the call status is as follows: The system determines whether the user is still in a call after the connection with the first server is broken by checking whether the phone is still in a call interface or whether the server has call resources occupied by the account. When reconnecting the registration link according to the preset method, specifically: Send a reINVITE packet to the first server to trigger a link update between the first server and the second server.

8. The VoIP call link recovery device as described in claim 7, characterized in that, The information request module includes a sending unit and an updating unit; The sending unit is used to initiate a registration recovery request to the first server and send the registration renewal package to the first server; The update unit is used to update the registration link according to the response status of the first server to the registration renewal package.

9. A VoIP call link recovery system, characterized in that, It includes a VoIP call link recovery device, a registration server, and an MCU server, wherein the VoIP call link recovery device performs the VoIP call link recovery method as described in any one of claims 1 to 6; The VoIP call link recovery device is connected to the registration server, and the registration server is connected to the MCU server.

10. A VoIP call link recovery system as described in claim 9, characterized in that, The registration server is used to receive registration recovery requests so that the first server can reconnect to the registration link; The VoIP call link recovery device is used to collect the call status after the connection with the first server registration link is disconnected, and to determine whether to reconnect the registration link based on the call status. If the call status is in progress, the registration link is reconnected according to a preset method. If the call status is out of progress, the registration link is disconnected. The MCU server is used to receive reINVITE packet data and update the registration link based on the reINVITE packet data information.

Images