CN117793286A - Conference calling method and conference system - Google Patents

Abstract

The invention relates to the technical field of video conferences and discloses a conference calling method and a conference system, wherein the method is applied to a conference platform, a calling management module sends a calling instruction to a target calling server, and the calling instruction comprises a terminal identifier of a target terminal; the target call server determines a target registration server corresponding to the target terminal according to the terminal identification, sends a first call request to the target registration server, and sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identification, wherein the first redirection call instruction comprises a network address of the target call server; if the target call server receives the second redirection call instruction, a second call request is sent to the target terminal through a call link, and when the call link is the target terminal sending the second redirection call instruction, the call link is established according to the network address in the first redirection call instruction. The invention can flexibly allocate resources for the call service and the registration service.

Description

Conference calling method and conference system

Technical Field

The invention relates to the technical field of video conferences, in particular to a conference calling method and a conference system.

Background

With the continuous progress of technology, video conference technology has been gradually turned to software from early, mainly depending on hardware devices, and has begun to be popularized to various industries and fields. As video conferencing systems become popular, the conference capacity is also expanding. Early software videoconferencing systems were typically limited in conference capacity to between tens and hundreds of people, while some advanced videoconferencing systems now can support concurrent participation by thousands or even tens of thousands.

In the actual use process of the large-capacity video conference, the scene of the oversized concurrent conference is very few, and there is often an oversized number of registered online numbers, and the number of concurrent calls is far smaller than the registered number.

This serious asymmetry in registration and call levels can cause the videoconference platform to significantly reduce the resource utilization of the videoconference if the corresponding number of registration resources are limited based only on the concurrent call load that it can handle when carrying out load handling. If a corresponding number of call resources are prepared according to the concurrent registration load, the corresponding call resources are wasted. It is often a significant cost to the user to purchase these rarely used resources.

The resources required for registration and call are often inconsistent as well as the amount of capacity that can be handled. For signaling interaction level, registration is a lighter interaction process than call, and the number of signaling and the transactions (authentication, registration, deletion) to be done are simple and quick, so that a large amount of registration information can be processed concurrently. For calls, the level of concurrency that can be handled is much less, as it involves more signaling and mobilized resources (authentication, user lookup, conference room resource viewing, media resource, forwarding resource, etc.).

How to maximize the utilization rate of resources becomes a problem to be solved.

Disclosure of Invention

In view of the above, the present invention provides a conference call method and a conference system, so as to solve the problem that the prior art cannot maximize the resource utilization.

In a first aspect, the present invention provides a conference call method, applied to a conference platform, where the conference platform includes: the system comprises a target registration server, a target call server and a call management module, wherein the call management module sends a call instruction to the target call server, and the call instruction comprises a terminal identifier of a target terminal; the target call server receives a call instruction, determines a target registration server corresponding to a target terminal according to a terminal identifier, and sends a first call request to the target registration server, wherein the first call request comprises the terminal identifier; the target registration server receives a first call request, and sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address of the target call server; if the target call server receives the second redirection call instruction, a second call request is sent to the target terminal through a call link, and when the call link is the target terminal sending the second redirection call instruction, the call link is established according to the network address in the first redirection call instruction.

The conference platform applicable to the conference call method provided by the embodiment of the invention comprises the registration server and the call server, wherein the registration server provides the registration service, and the call server provides the call service, namely, the registration service and the call service are separated in the conference platform. After the registration service and the call service are separated into different servers, when the conference platform initiatively initiates a call to the target terminal, the call management module sends a call instruction to the target call server, the target call server determines a target registration server corresponding to the target terminal according to the terminal identification and sends a first call request to the target registration server, the target registration server sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identification, and after the target terminal receives the first redirection call instruction, a call link is established between the target terminal and the target call server according to the network address of the target call server in the first redirection call instruction, so that the target call server can send a second call request to the target terminal according to the call link, and call interaction between the conference platform and the target terminal is established. Therefore, by implementing the invention, even if the registration service and the call service are separated, the normal call between the conference platform and the target terminal can be realized, the situation that the conference platform cannot find the called target terminal does not exist, and on the basis, corresponding resources can be respectively configured for the registration service and the call service according to the load generated by registration and the load generated by call, so that the resource utilization rate is maximized.

In an alternative embodiment, the first call request includes a call identifier, the target registration server obtains a terminal identifier and a call identifier according to the first call request, and sends a first redirecting call instruction to the target terminal to a registration link corresponding to the terminal identifier, where the first redirecting call instruction includes a network address and a call identifier of the target call server; transmitting redirection notification information to the target call server, wherein the redirection notification information is used for notifying the target call server that the first call request is redirected; if the target call server receives the second redirecting call instruction, before executing the step of sending the second call request to the target terminal through the call link, the method further comprises: judging whether the call identifier in the second redirecting call instruction is the same as the call identifier in the first call request; and if the call request is the same, the step of sending a second call request to the target terminal through the call link is executed.

In an alternative embodiment, before the step of sending the call instruction to the target call server by the call management module, the method further comprises: the target registration server receives a registration request of a target terminal, wherein the registration request comprises a terminal identifier of the target terminal; when a registration request is sent, a registration link between a target terminal and a target registration server is established; after the target terminal is successfully registered, the registration correspondence between the terminal identification of the target terminal and the network address of the target registration server is stored.

In an alternative embodiment, the conference platform includes a plurality of call servers, and the call management module determines the target call server based on load balancing according to load information of each call server.

In an alternative embodiment, if the session platform uses the SIP protocol, after receiving the first call request, the target registration server sends a first MESSAGE to the target terminal through a registration link corresponding to the terminal identifier, where the first MESSAGE carries the call identifier and a network address of the target call server, and is used to characterize a first redirected call instruction of the first call request; the target registration server sends redirection notification information to the target call server through a custom 308 signaling message; the target call server receives a second MESSAGE with a second redirection call instruction and a call identifier sent by the target terminal

In an alternative embodiment, if the target registration server receives the call failure information sent by the target terminal, the call failure information is forwarded to the target call server.

In an alternative embodiment, the target registration server receives a third call request sent by the target terminal, and sends a fourth call request to the call management module based on the third call request; the call management module sends the network address of the target call server to the target registration server; the target registration server receives the network address of the target call server, and sends a call redirection message to the target terminal, wherein the call redirection message comprises the network address of the target call server; the target call server receives a fifth call request sent through a target call link established by the target terminal according to the network address of the target call server.

In a second aspect, an embodiment of the present invention provides a conference system, including a target terminal and a conference platform, where the conference platform includes: the system comprises a registration server, a call server and a call management module, wherein the call management module sends a call instruction to a target call server, and the call instruction comprises a terminal identifier of a target terminal; the target call server receives a call instruction, determines a target registration server corresponding to a target terminal according to a terminal identifier, and sends a first call request to the target registration server, wherein the first call request comprises the terminal identifier; the target registration server receives a first call request, and sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address of the target call server; the target terminal receives the first redirection call instruction, establishes a call link according to a network address in the first redirection call instruction, and sends a second redirection call instruction to the target call server through the call link; the target call server receives the second redirecting call indication and sends a second call request to the target terminal through the call link.

In an alternative embodiment, the first call request includes a call identifier, the target registration server obtains a terminal identifier and a call identifier according to the first call request, and sends a first redirecting call instruction to the target terminal to a registration link corresponding to the terminal identifier, where the first redirecting call instruction includes a network address and a call identifier of the target call server; after receiving the second redirecting call instruction, the target call server further comprises, before executing the step of sending the second call request to the target terminal through the call link: judging whether the call identifier in the second redirecting call instruction is the same as the call identifier in the first call request; and if the call request is the same, the step of sending a second call request to the target terminal through the call link is executed.

In an alternative embodiment, the target terminal sends a third call request to the target registration server; the target registration server sends a fourth call request to the call management module according to the third call request; the call management module sends the network address of the target call server to the target registration server; the target registration server receives the network address of the target call server, and sends a call redirection message to the target terminal, wherein the call redirection message comprises the network address of the target call server; the target terminal receives the call redirection message, establishes a target call link according to the network address of the target call server contained in the call redirection message, and sends a fifth call request to the target call server through the target call link; the target call server receives the fifth call request.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow diagram of a conference call method according to an embodiment of the invention;

fig. 2 is a schematic diagram of an interaction flow between a target terminal and a conference platform when the conference platform initiates a call to the target terminal in the conference system according to an embodiment of the present invention;

fig. 3 is a schematic diagram of an interaction flow between a target terminal and a conference platform when the target terminal initiates a call to the conference platform in the conference system according to the embodiment of the present invention;

fig. 4 is a schematic diagram of an interaction flow between a target terminal and a conference platform when the conference platform initiates a call to the target terminal when the conference call method provided by the embodiment of the present invention is applied to SIP protocol;

fig. 5 is a schematic diagram of an interaction flow between a target terminal and a conference platform when the conference call method provided by the embodiment of the present invention is applied to a SIP protocol and the target terminal initiates a call to the conference platform.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. 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.

In the use process of the video conference system, the registration service and the call service are often required to be put together, because in the public network environment, the terminal is often registered to the platform through network address translation (Network Address Translation, NAT), and when the platform needs to call the terminal when the conference is started, the terminal needs to be called through the network link from the terminal to the platform. Otherwise, according to the penetration rule of the NAT, the called terminal cannot be found through other paths. Therefore, in the related art, a registration service and a call service are required to be deployed in a common server, but due to serious asymmetry of registration and call levels, if a corresponding number of registration resources are limited only according to the concurrent call load amount that it can handle, the resource utilization of the video conference may be greatly reduced. If a corresponding number of call resources are prepared according to the concurrent registration load, the corresponding call resources are wasted greatly. It is often a significant cost to the user to purchase these rarely used resources. Therefore, the video conference platform cannot maximize the resource utilization rate when carrying out load processing.

In accordance with an embodiment of the present invention, a conference call method embodiment is provided, it being noted that the steps shown in the flowchart of the figures may be performed in a computer system, such as a set of computer executable instructions, and, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order other than that shown or described herein.

In this embodiment, a method for conference calling is provided, which is characterized in that the method is applied to a conference platform, and the conference platform includes: the system comprises a registration server, a call server and a call management module, wherein the registration server is used for providing registration service, the call server is used for providing call service, and the flow comprises the following steps as shown in figure 1:

in step S101, the call management module sends a call instruction to the target call server, where the call instruction includes a terminal identifier of the target terminal.

In the embodiment of the invention, when the conference platform needs to actively initiate a call to the target terminal, a call instruction is sent to the target call server through the call management module, and the target call server executes call service according to the call instruction.

In an alternative embodiment, different terminals correspond to different terminal identifications.

In an alternative embodiment, each terminal registers in the conference platform, and the terminal identifier of the terminal that completes registration is stored in the call management module, so that the call management module can initiate a call to each terminal according to the terminal identifier of each terminal.

Step S102, the target call server receives the call instruction, determines a target registration server corresponding to the target terminal according to the terminal identification, and sends a first call request to the target registration server, wherein the first call request comprises the terminal identification.

In an alternative embodiment, a plurality of terminals may be registered in one registration server, that is, the network address of one registration server corresponds to the terminal identifier of a plurality of terminals, after the terminal is registered in the registration server, the association relationship between the terminal identifier and the network address of the registration server may be stored, after the target call server receives the call instruction, the network address of the target registration server corresponding to the terminal identifier may be determined according to the terminal identifier in the call instruction based on the association relationship between the terminal identifier and the network address of the registration server, so that the target call server sends the first call request to the network address.

In step S103, the target registration server receives the first call request, and sends a first redirecting call instruction to the target terminal through the registration link corresponding to the terminal identifier, where the first redirecting call instruction includes the network address of the target call server.

In an alternative embodiment, the target terminal is required to register to the conference platform through the target registration server, and when the target terminal initiates registration to the target registration server, the target terminal establishes a registration link with the target registration server, so that after receiving the first call request, the target registration server can find the registration link connected with the target terminal, and thus send a first redirecting call instruction to the target terminal through the registration link.

In the embodiment of the present invention, the first redirecting call instruction includes the network address of the target call server, so that the target terminal can establish a connection with the target call server according to the network address of the target call server, so that the target call server can directly initiate a call request to the target terminal.

In an alternative embodiment, after the target registration server sends the first redirecting call instruction to the target terminal, the target registration server sends redirecting notification information to the target call server to notify the target call server that the first call request has been redirected.

In an alternative embodiment, after receiving the first redirecting call instruction, the target terminal sends a second redirecting call instruction to the target call server if the target terminal can be called at this time. In the embodiment of the present invention, the target registration server sends a first redirecting call instruction to the target terminal, which is used for informing the target terminal: the target server needs to initiate a call to it; a second redirecting call instruction sent by the target terminal to the target call server is used for informing the target server: the target terminal has received the redirected call indication corresponding to the first call request and established a call link indicating that it can currently be initiated.

In an alternative embodiment, after receiving the first redirecting call instruction, if the target terminal cannot be called at this time, the target terminal sends call failure information to the target registration server, where the call failure information includes a reason that the target registration server cannot be called currently, and after receiving the call failure information, the target registration server forwards the call failure information to the target call server.

In an alternative embodiment, if the target terminal does not make any reply within the preset duration, the target call server executes a corresponding timeout scheme, if no reply is received beyond the preset duration, and the target call server re-initiates a call request to the target registration server.

Step S104, if the target call server receives the second redirection call instruction, the second call request is sent to the target terminal through the call link, and when the call link is that the target terminal sends the second redirection call instruction, the call link is established according to the network address in the first redirection call instruction.

In an alternative embodiment, after the target call server sends the second call request, corresponding media resources, forwarding resources, etc. are allocated for the current call.

In an alternative embodiment, if the target call server achieves normal call interaction with the target terminal after sending the second call request to the target terminal, the target call server sends a success indication to the call management module for characterizing that the call to the target terminal is successful.

In an alternative embodiment, if the target call server sends the second call request to the target terminal, the target terminal returns call success information, and normal call interaction with the target terminal is characterized.

The conference platform applicable to the conference call method provided by the embodiment of the invention comprises the registration server and the call server, wherein the registration server provides the registration service, and the call server provides the call service, namely, the registration service and the call service are separated in the conference platform. After the registration service and the call service are separated into different servers, when the conference platform initiatively initiates a call to the target terminal, the call management module sends a call instruction to the target call server, the target call server determines a target registration server corresponding to the target terminal according to the terminal identification and sends a first call request to the target registration server, the target registration server sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identification, and after the target terminal receives the first redirection call instruction, a call link is established between the target terminal and the target call server according to the network address of the target call server in the first redirection call instruction, so that the target call server can send a second call request to the target terminal according to the call link, and call interaction between the conference platform and the target terminal is established. Therefore, by implementing the invention, the registration service and the call service are separated, normal call between the conference platform and the target terminal can be realized on the basis of separating the registration service from the call service, the situation that the conference platform cannot find the called target terminal is avoided, and on the basis, corresponding resources can be respectively configured for the registration service and the call service according to the load generated by registration and the load generated by call, so that the resource utilization rate is maximized.

In an alternative embodiment, the first call request includes a terminal identifier and a call identifier, and the call identifier is generated by the target call server.

The target registration server obtains a terminal identifier and a call identifier according to the first call request, and sends a first redirection call instruction to the target terminal to a registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address and a call identifier of the target call server.

The target registration server sends redirection notification information to the target call server, wherein the redirection notification information is used for notifying the target call server that the first call request is redirected;

if the target call server receives the second redirecting call instruction, before executing the step of sending the second call request to the target terminal through the call link, the method further comprises:

judging whether the call identifier in the second redirecting call instruction is the same as the call identifier in the first call request;

and if the call request is the same, the step of sending a second call request to the target terminal through the call link is executed.

That is, in the embodiment of the present invention, the first call request sent by the target call server to the target registration server includes the call identifier, when the target registration server sends the first redirection call instruction to the target terminal, the target registration server carries the call identifier corresponding to the first call request, when the target terminal receives the first redirection call instruction and sends the second redirection instruction to the target call server, the target call server also carries the call identifier, compares the call identifier carried by the second redirection instruction with the call identifier generated when the first call request is sent by the target call server and has been redirected, if the two call identifiers are the same, the second call request is sent to the target terminal sending the second redirection instruction, and through the call identifier, it can be ensured that the target call server can establish call interaction with the correct target terminal.

In an alternative embodiment, before executing the step S101, the method provided by the embodiment of the present invention further includes:

firstly, a target registration server receives a registration request of a target terminal, wherein the registration request comprises a terminal identifier of the target terminal; a registration link between the target terminal and the target registration server is established upon sending the registration request.

In the embodiment of the invention, before the target terminal sends the registration request, a registration link with the target registration server is established, and then the registration request is sent to the target registration server through the registration link, so that the registration on the conference platform is realized.

And then, after the target terminal is successfully registered, storing the registration correspondence between the terminal identification of the target terminal and the network address of the target registration server.

In an alternative embodiment, there may be a plurality of registration servers in a conference platform, where the target registration server establishes a correspondence between the terminal identifier and its own network address, and sends the correspondence to the target call server, so that after receiving the call instruction sent by the call management module, the target call server can send the first call request to the corresponding target registration server according to the correspondence between the terminal identifier and the network address of the target registration server. In other alternative embodiments, the correspondence may be placed in a server or storage space accessible to other call servers.

In an alternative embodiment, after the target terminal completes registration on the target registration server, the target registration server also stores the terminal identifier of the target terminal to the call management module, so that the call management module can initiate a call instruction according to the pre-stored terminal identifier.

In an alternative embodiment, if the target terminal is successfully registered in the target registration server, the target registration server sends a reply of successful registration to the target terminal. Otherwise, sending a reply of registration failure to the target terminal.

In an alternative embodiment, the conference platform comprises a plurality of call servers, and the call management module determines the target call server based on load balancing according to load information of each call server.

In an alternative embodiment, the call management module selects a target call server according to a preset selection policy to send a call instruction to, and may, for example, select the call server with the smallest load as the target call server to send the call instruction to.

In an alternative embodiment, the conference platform includes a plurality of registration servers, and the target call server determines a target registration server corresponding to the target terminal according to a correspondence between the terminal identifier and a network address of the registration server.

That is, in the embodiment of the present invention, each registration server receives registration requests from different terminals, and the target call server stores the correspondence between the network addresses of a plurality of registration servers and the terminal identifiers of the terminals, so that after receiving the call instruction, the target registration server corresponding to the terminal identifier in the call instruction can be determined.

In an alternative embodiment, when the target terminal actively initiates a call request to the conference platform, the method includes:

(1) The target registration server receives a third call request sent by the target terminal and sends a fourth call request to the call management module based on the third call request.

In the embodiment of the invention, the target terminal establishes the registration link when executing the registration operation with the target registration server, so that when the target terminal initiatively initiates a call, a third call request needs to be sent to the target registration server through the registration link.

In an alternative embodiment, the target registration server may directly forward the third call request to the call management module, or may format-convert the third call request and send the third call request to the call management module.

(2) The call management module sends the network address of the target call server to the target registration server.

In an alternative embodiment, when the conference platform includes a plurality of call servers, the call management module selects a target call server from the plurality of call servers according to a preset rule, and sends a network address of the selected target call server to the target registration server. For example, based on the current call situation of each call server, a corresponding target call server is selected based on the load balancing principle.

(3) The target registration server receives the network address of the target call server, and sends a call redirection message to the target terminal, wherein the call redirection message comprises the network address of the target call server.

In the embodiment of the invention, the call redirection message containing the network address of the target call server is sent to the target terminal, and the target terminal can establish a target call link with the target call server so as to perform call interaction with the target call server through the target call link.

(4) The target call server receives a fifth call request sent through a target call link established by the target terminal according to the network address of the target call server.

In an alternative embodiment, after receiving the fifth service request, the target call server allocates a corresponding media resource, forwarding resource, etc. for the current call.

The embodiment of the invention also provides a conference system, which comprises a target terminal and a conference platform, wherein the conference platform comprises: registration server, call server and call management module.

When the conference platform initiates a call request to the target terminal, the call flow is as shown in fig. 2.

The call management module sends a call instruction to the target call server, wherein the call instruction comprises the terminal identification of the target terminal.

The target call server receives a call instruction, determines a target registration server corresponding to the target terminal according to the terminal identifier, and sends a first call request to the target registration server, wherein the first call request comprises the terminal identifier.

The target registration server receives a first call request, and sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address of the target call server. And sending redirection notification information to the target call server, wherein the redirection notification information is used for notifying the target call server that the first call request is redirected.

The target terminal receives the first redirecting call instruction, establishes a call link according to the network address in the first redirecting call instruction, and sends a second redirecting call instruction to the target call server through the call link.

The target call server receives the second redirecting call indication and sends a second call request to the target terminal through the call link.

It should be noted that, before the conference platform initiates a call to the target terminal, the target terminal is registered through the registration server in the conference platform, and the registration is successful.

In an alternative embodiment, as shown in fig. 2, the target call server, after receiving the second redirecting call instruction, sends a redirecting call instruction reply to the target terminal, and then sends a second call request to the target terminal through the call link. After the target terminal and the target call server normally interact, the target call server sends the successful calling information to the call management module.

In an optional embodiment, the first call request includes a call identifier, the target registration server obtains a terminal identifier and a call identifier according to the first call request, and sends a first redirecting call instruction to the target terminal to a registration link corresponding to the terminal identifier, where the first redirecting call instruction includes a network address and a call identifier of the target call server; after receiving the second redirecting call instruction, the target call server further comprises, before executing the step of sending the second call request to the target terminal through the call link: judging whether the call identifier in the second redirecting call instruction is the same as the call identifier in the first call request; and if the call request is the same, the step of sending a second call request to the target terminal through the call link is executed. The details are described in the above embodiments, and are not repeated here.

In an alternative embodiment, when the target terminal initiates a call request to the conference platform, the call flow is as shown in fig. 3. In the conference platform, interactions between the registration server, the call server, and the call management module are not represented in fig. 3.

The target terminal sends a third call request to the target registration server.

The target registration server sends a fourth call request to the call management module according to the third call request; the call management module sends the network address of the target call server to the target registration server.

The target registration server receives the network address of the target call server, and sends a call redirection message to the target terminal, wherein the call redirection message comprises the network address of the target call server.

The target terminal receives the call redirection message, establishes a target call link according to the network address of the target call server contained in the call redirection message, and sends a fifth call request to the target call server through the target call link.

The target call server receives the fifth call request.

After the server and the target terminal interact with each other in normal call, the target terminal calls into the call management module.

The details are described in the above embodiments, and are not repeated here.

The method and system provided in the above embodiments are applicable to different video conference protocols, such as SIP protocol, H323 protocol, etc., and can be designed based on specific video conference protocols according to requirements. In the embodiment of the invention, the application of the SIP protocol is taken as an example, and the signaling design and flow of a specific video conference protocol are described.

The procedure by which the terminal is called is shown in figure 4,

(1) The terminal (MTx) sends REGISTER information to a target registration server (Rx) for registration;

(2) If the registration is successful, the target registration server sends 200OK to the terminal, wherein the 200OK is a reply to the REGISTER information;

(3) The target call server (Cx) determines a target terminal based on a call instruction of the call management module, searches the position of a registration server where a called call is located (i.e. searches a corresponding registration server based on a target terminal identifier), after determining the target registration server (Rx), the target call server (Cx) sends an INVITE (Request: MT1; CALLID) to the target registration server (Rx), wherein the INVITE is used for initiating a call, the INVITE comprises the Request and the CALLID, the Request represents a call object, the call object is a terminal with a terminal identifier of MT1 in FIG. 4, and the CALLID represents a call identifier;

(4) The target registration server sends a custom 308 signaling message to the target call server, 308 is a sip standard rfc3261 3xx class indicating redirection, 308 is undefined, corresponding to here custom a 308 signaling message indicating that the call is redirected without a redirect destination address, because even if carrying a redirect destination address, it cannot pass through the NAT connection terminal.

(5) The target call server sends an ACK, which is a reply message to the INVITE transaction, to the target registration server.

(6) The target registration server sends a MESSAGE (Redirect-to: url of Cx) MESSAGE to the terminal MT1, where the MESSAGE is used to send a MESSAGE in the sip, and the MESSAGE content is customized corresponding to the first MESSAGE, and is customized to be used as a Redirect call instruction MESSAGE, where the Redirect call instruction MESSAGE carries the network address (url) and the CALLID of the call server.

(7) The terminal sends a 200OK to the target call server for returning the first MESSAGE in the steps;

(8) The terminal sends a MESSAGE (redirection indication + CALLID) to the target call server, corresponding to a second MESSAGE carrying the redirection indication and the CALLID.

(9) The target call server sends a 200OK to the terminal for the second MESSAGE.

(10) The target call server sends an INVITE (Request: call server Cx; CALLID) to the terminal, wherein the current Request is the target call server and the CALLID is the call identifier.

(11) The terminal sends a 200OK to the target call server for the INVITE message described above.

(12) The target call server sends an ACK to the terminal.

The process of terminal active call is as shown in fig. 5:

(1) The terminal sends REGISTER information to the target registration server for registration.

(2) If the registration is successful, the target registration server sends 200ok to the terminal, wherein 200ok is a reply of the REGISTER information in (1).

(3) The terminal sends an INVITE (Request: a conference number) to the target registration server, carrying the conference number.

(4) The destination registration server sends 301 (url redirected to Cx) to the terminal, 301 indicating that the call is redirected and carrying the redirected destination url, which in this embodiment is the url to which a certain destination call server is going.

(5) The terminal sends an ACK to the target registration server for replying to the redirect message 301 message.

(6) And the terminal sends the INVITE carrying the conference number to the target call server.

(7) The target call server sends a 200OK to the terminal for replying to the INVITE in (6).

(8) The terminal sends an ACK to the target call server.

Although embodiments of the present invention have been described in connection with the accompanying drawings, various modifications and variations may be made by those skilled in the art without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope of the invention as defined by the appended claims.

Claims (10)

1. A conference call method, applied to a conference platform, the conference platform comprising: a registration server, a call server and a call management module,

the call management module sends a call instruction to a target call server, wherein the call instruction comprises a terminal identifier of a target terminal;

the target call server receives the call instruction, determines a target registration server corresponding to the target terminal according to the terminal identifier, and sends a first call request to the target registration server, wherein the first call request comprises the terminal identifier;

the target registration server receives the first call request, and sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address of the target call server;

And if the target call server receives a second redirection call instruction, sending a second call request to the target terminal through a call link, wherein the call link is established according to a network address in the first redirection call instruction when the target terminal sends the second redirection call instruction.

2. The method of claim 1, wherein the first call request includes a call identifier,

the target registration server acquires the terminal identifier and the call identifier according to the first call request, and sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address of the target call server and the call identifier;

transmitting redirection notification information to the target call server, wherein the redirection notification information is used for notifying the target call server that the first call request is redirected;

if the target call server receives a second redirecting call instruction, before executing the step of sending a second call request to the target terminal through the call link, the method further comprises:

Judging whether the call identifier in the second redirection call instruction is the same as the call identifier in the first call request;

and if the call request is the same, executing the step of sending a second call request to the target terminal through the call link.

3. The method of claim 1, wherein prior to the step of the call management module sending a call instruction to the target call server, the method further comprises:

the target registration server receives a registration request of the target terminal, wherein the registration request comprises a terminal identifier of the target terminal; establishing the registration link between the target terminal and the target registration server when the registration request is sent;

and after the target terminal is successfully registered, storing the registration corresponding relation between the terminal identification of the target terminal and the network address of the target registration server.

4. The method of claim 1, wherein the conference platform includes a plurality of call servers,

the call management module determines the target call server based on load balancing according to the load information of each call server.

5. The method of claim 2, wherein, if the SIP protocol is used in the conferencing platform,

After receiving the first call request, the target registration server sends a first MESSAGE to the target terminal through a registration link corresponding to the terminal identifier, wherein the first MESSAGE carries the call identifier and a network address of the target call server and is used for representing a first redirected call instruction of the first call request;

the target registration server sends the redirection notification information to the target call server through a custom 308 signaling message;

and the target call server receives a second MESSAGE which is sent by the target terminal and carries the second redirection call instruction and the call identifier.

6. The method of claim 1, wherein the step of determining the position of the substrate comprises,

and if the target registration server receives the call failure information sent by the target terminal, forwarding the call failure information to the target call server.

7. The method as recited in claim 1, further comprising:

the target registration server receives a third call request sent by the target terminal and sends a fourth call request to the call management module based on the third call request;

The call management module sends the network address of the target call server to the target registration server;

the target registration server receives the network address of the target call server and sends a call redirection message to the target terminal, wherein the call redirection message comprises the network address of the target call server;

the target call server receives a fifth call request, which is sent through a target call link established by the target terminal according to the network address of the target call server.

8. A conferencing system comprising a target terminal and a conferencing platform, the conferencing platform comprising: a registration server, a call server and a call management module,

the call management module sends a call instruction to a target call server, wherein the call instruction comprises a terminal identifier of a target terminal;

the target call server receives the call instruction, determines a target registration server corresponding to the target terminal according to the terminal identifier, and sends a first call request to the target registration server, wherein the first call request comprises the terminal identifier;

The target registration server receives the first call request, and sends a first redirection call instruction to the target terminal through a registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address of the target call server;

the target terminal receives the first redirection call instruction, establishes a call link according to a network address in the first redirection call instruction, and sends a second redirection call instruction to the target call server through the call link;

and the target call server receives the second redirection call instruction and sends a second call request to the target terminal through the call link.

9. The conference system of claim 8, wherein the first call request includes a call identifier,

the target registration server acquires the terminal identifier and the call identifier according to the first call request, and sends a first redirection call instruction to the target terminal to the registration link corresponding to the terminal identifier, wherein the first redirection call instruction comprises a network address of the target call server and the call identifier; transmitting redirection notification information to the target call server, wherein the redirection notification information is used for notifying the target call server that the first call request is redirected;

After receiving the second redirecting call instruction, the target call server further comprises, before executing the step of sending the second call request to the target terminal through the call link:

judging whether the call identifier in the second redirection call instruction is the same as the call identifier in the first call request;

and if the call request is the same, executing the step of sending a second call request to the target terminal through the call link.

10. The conference system of claim 8, further comprising:

the target terminal sends a third call request to the target registration server;

the target registration server sends a fourth call request to the call management module according to the third call request;

the call management module sends the network address of the target call server to the target registration server;

the target registration server receives the network address of the target call server and sends a call redirection message to the target terminal, wherein the call redirection message comprises the network address of the target call server;

the target terminal receives the call redirection message, establishes a target call link according to a network address of a target call server contained in the call redirection message, and sends a fifth call request to the target call server through the target call link;

The target call server receives the fifth call request.