TW201906394A - Method, apparatus and computer readable storage medium for call management - Google Patents

Abstract

A method, apparatus and computer readable storage medium for call management are provided. The method for call management comprises storing a conference table for recording information of a proxy endpoint that has been added to a conference call and having a number of DSP channels greater than or equal to 2. The method further comprises receiving a call request; identifying one endpoint of the call request; determining whether there is a number of available proxy endpoints in the conference table, where the proxy endpoint is an available proxy endpoint if the number of the DSP channels of the proxy endpoint is greater than zero. If there are multiple available proxy endpoints in the conference table, the priority of each available proxy endpoint is calculated and the call request is redirected to the endpoint with the highest priority available proxy endpoint between.

Description

Method, device and computer readable storage medium for call management

The present invention relates to the field of communications, and in particular, to a method, apparatus, and computer readable storage medium for call management.

Existing VoIP phones are connected to the Public Switched Telephone Network (PSTN) via a gateway to enable multi-party conference calls. However, limited by the bandwidth of the standard telephone trunk or the maximum number of conference call system, whether the participant actively dials into the conference call system or is actively dialed out to the conference by the conference system, it is possible to face the same time. The problem that the number of occupied telephone lines exceeds the upper limit.

In view of the above, there is a need for a method, apparatus, and computer readable storage medium for call management that can increase the number of participants in a conference call while effectively reducing the number of calls established by the conference call.

The present invention provides a method for call management, the method comprising: storing a conference table for recording information of an agent endpoint that has joined a conference call and having a number of DSP channels greater than or equal to 2; receiving a call request; Identifying an endpoint associated with the call request; determining whether there are multiple available proxy endpoints in the conference table, wherein if the number of DSP channels of the proxy endpoint is greater than 0, the proxy endpoint is an available proxy endpoint Point; if there are multiple available agent endpoints in the conference table, calculate the priority of each available agent endpoint; and redirect the call request to the endpoint with the highest priority available agent Between endpoints.

The present invention also provides an apparatus for call management, the apparatus comprising: a processor; and a computer readable storage medium for storing at least one computer program and a conference table for recording Information of an agent endpoint joining a conference call and having a number of DSP channels greater than or equal to 2; wherein the computer program includes and is executed by the processor and performs the steps of: receiving a call request; identifying the call request An associated endpoint; determining whether there are multiple available proxy endpoints in the conference table, wherein if the number of DSP channels of the proxy endpoint is greater than 0, the proxy endpoint is an available proxy endpoint; There are multiple available agent endpoints in the conference table, then the priority of each available agent endpoint is calculated; and the call request is redirected to between the endpoint and the highest priority available proxy endpoint.

The present invention also provides a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps for the call management method.

Referring to FIG. 1, a schematic diagram of an application environment 100 for conducting a conference call according to an embodiment of the present invention is shown. The application environment 100 includes a first field 110 and a second field 150. In this embodiment, the first field domain 110 is communicably connected to the second field 150 via the PSTN 140. It should be noted that the first field 110 and the second field 150 may be located in different geographic spaces, or may be grouped on different network topologies in the same geographic space.

The first field field 100 described above includes a plurality of endpoints 110A-110M, a gateway 120, and a call manager 130. The plurality of endpoints 110A-110M are clients of the Voice over Internet Protocol (VOIP), and provide VOIP services for the terminal users. The plurality of endpoints 110A-110M may be terminal devices such as analog telephones, network telephones, or soft telephones. When the plurality of endpoints 110A-110M are software telephones, they can be run on user terminals of smart phones, personal computers or other media. The gateway 120 can be coupled to the plurality of endpoints 110A-110M to forward calls to the PSTN 140 to complete dial-in and dial-out of heterogeneous networks. In an embodiment, the gateway 120 can be coupled to the PSTN 140 via an analog or digital trunk, such as a T1 or E1 interface. The call manager 130 described above is coupled to the gateway 120 for managing configuration, registration, call management, and other telephony function management of the plurality of endpoints 110A-110M.

The second field field 150 described above includes a conference system 160, a call manager 170, and a gateway 180. The conference system 160 is a client of a multi-party conference call for providing a user to create a multi-party conference call or to participate in a multi-party conference call. The above call manager 170 is used to manage the creation, deletion, multi-party conference time management, multi-party conference call participant management, and the like of a multi-party conference call. The gateway 180 is coupled to the PSTN 140 and provides telephone and internet protocol call technology services to the conference system 160 and the call manager 170.

In one embodiment, the call manager 130, 170 includes a processor and a computer readable storage medium (not shown in FIG. 1). The above processor is a central processor of the call manager 130, 170, and may be composed of one or more integrated circuits, such as a single core or multi-core microprocessor or a microcontroller, to control the call manager 130, 170. Operation. The computer readable storage medium described above can be any form of computer readable storage medium such as a hard drive, flash memory or any other non-volatile storage medium. The storage device described above can store one or more computer programs for operating the call manager 130, 170 described above. The above computer program can be executed by the above described processor and includes a set of instructions or functional units that implement the features of the present invention.

In one embodiment, the call manager 130, 170 can be a computer program running on one or more computer devices, and the computer program of the call manager 130, 170 can be included in any type of computer readable storage medium. It should be noted that although the call manager 130, 170 is shown as a separately operable module in FIG. 1, in other embodiments, the call manager 130, 170 may be operated in the gateway 120. , 180 computer programs.

The plurality of endpoints 110A-110M may include respective telephone processors, which may be digital signal processors (DSPs) and include one or more DSP channels. In one embodiment, the plurality of endpoints 110A-110M are automatically registered with the call manager 130 with their own Media Access Control Address (MAC Address) and other parameters when powered on. The other parameters mentioned above may include the type, brand, model, user name and password of the endpoint. The call manager 130 can know the number of DSP channels of each endpoint according to the brand and model transmitted by the multiple endpoints 110A-110M, and further determine the role that the endpoint can play in the conference call according to the number of DSP channels. . If the number of DSP channels of the endpoint is equal to 1, the endpoint can only be an attendee in a conference call; if the number of DSP channels of the endpoint is greater than or equal to 2, the endpoint can be a participant in a conference call. Can also be an agent. In the embodiment of the present invention, the call manager 130 may redirect the call of the participant who wants to join the conference system 160 to the agent who has joined the conference system 160 in the same field, and the caller performs the follow-up. The voice data stream is mixed to reduce the number of calls to the gateway 120 at the same time.

In an embodiment, the call manager 130 can select a specific endpoint from among a plurality of agents as an agent of a new incoming call by an algorithm in time, such as the following equation:

P _priority = a ́RTT _local + b ́QoS _proxy + g ́Cap _proxy + w ́RTT _external (1)

The P _priority calculated by the above equation can be used as the _priority of the agent's endpoint, and the smaller the value, the higher the priority. The call manager 130 described above redirects the call of a new participant in a conference call to the agent with the highest priority.

The RTT _local is the Round-Trip Time (RTT) between the new participant and the agent who has dialed into the conference call. The value can be obtained in the following two ways: 1. When the above multiple endpoints 110A-110M are powered on, The ICMP echo request packet is actively broadcasted to obtain a delay time with other endpoints, and after registration to the call manager 130, the delay time with other endpoints is transmitted to the call manager 130; When a call is made between any two endpoints, the delay time can be obtained via a Real-Time Control Protocol (RTCP), and the endpoint actively transmits the delay time to the call manager 130 after the call ends.

The QoS _proxy is the set value of the agent itself related to the Quality of Service (QoS). The QoS setting value can be calculated from the agent's Type of Service (ToS) setting value or the differential service code point (DSCP) setting value. Generally, the DSCP setting value ranges from 0 to 63. The DSCP setting value is used to specify the priority of the packet in the QoS scheduling in the QoS mechanism. A larger value indicates a higher priority. If the agent has the DSCP setting value, the DSCP setting value can be directly taken out, and the DSP setting value is subtracted from 63 to be the QoS setting value. If the agent has only the ToS set value, the ToS set value must be mapped to a DSCP set value, and then the operation is performed to obtain the QoS set value. The source of the ToS set value or the DSCP set value of the agent has the following two ways: 1. After the agent registers with the call manager 130, the initial configuration is transmitted by the call manager 130 to the agent; The setting is performed on the endpoint by itself, and the endpoint actively transmits the set value to the call manager 130.

Cap _proxy is the number of remaining DSP channels currently available to the agent. The initial value of the value is the number of DSP channels supported by the hardware of the endpoint itself. The call manager 130 can know the number of DSP channels supported by the endpoint according to information such as the brand and model transmitted when the endpoint is registered. During a conference call, as more and more incoming participants' calls are redirected to a particular agent, the agent's Cap _proxy value is also decremented.

RTT _external is the delay between the agent and the gateway 120 described above. In an embodiment, the first field 110 may further include a plurality of external gateways, and the call manager 130 directs calls of different endpoints to different external gateways according to the setting, and the endpoints are The delay time between the gateways can be obtained via RTCP.

The a, b, g, and w system weight parameters, the manager or network administrator of the first field domain 110 may set the initial values of the weight parameters by using the call manager 130, and may also change according to different needs and environments. Adjust again, but the sum must be equal to 1. The set values of the weight parameters are suggested as follows: 1. If there are several high-order endpoints in the same field, that is, there are several endpoints with a high number of DSP channels, it is recommended to increase the g value, so that most The voice data stream is concentrated to a certain number of agent endpoints; second, if there are high-level agent endpoints in the adjacent field, it is recommended to increase the a value to reduce the voice delay after the mixing process; 3. If there are several endpoints with higher QoS settings in the network environment, it is recommended to increase the b value to improve the voice quality after the hybrid processing. Fourth, if the network environment, different endpoints will There are different routing paths to different external gateways. It is recommended to increase the w value to improve the speech quality after mixing. In an embodiment, the call manager 130 may store different conference tables for the different conference calls on the computer readable storage medium to record the RTT _local , QoS _proxy , and Cap _proxy of the agent who has joined the conference call. RTT _external and other parameter values. The above conference table may also contain an availability field for marking the availability of the agent. Wherein, if the agent currently has more DSP channels than 0, the role of the agent in the conference call may be an agent, so the availability field should be marked as available; if the agent is currently available When the number of DSP channels is equal to 0, the role of the agent in the conference call can only be a participant, so the availability field should be marked as unavailable accordingly.

Referring to FIG. 2, a flow chart of call management when an active conference call is performed according to an embodiment of the present invention is shown. In this embodiment, each of the endpoints 110A and 110B has one DSP channel, and the endpoints 110C and 110D respectively have two DSP channels as an example. Since the above-mentioned endpoints 110A and 110B only have one DSP channel, they can only be participants in a conference call; and the endpoints 110C and 110D respectively have two DSP channels, so in a conference call, it is possible to participate in the conference. It can also be an agent. FIG. 2 shows a flow of establishing an active conference call with the above-mentioned endpoints 110A, 110B, 110C, and 110D and the conference system 160. The main steps are as follows:

In step 201, the endpoint 110C dials the telephone number of the conference system 160, and the call manager 130 receives the call request of the endpoint 110C. The call manager 130 determines that the role of the endpoint 110C is the number of DSP channels, and the role may be an attendee or an agent.

Step 202: The call manager 130 establishes a communication connection between the endpoint 110C and the conference system 160, and notifies the endpoint 110C to open the multimedia interface to start transmitting and receiving voice data streams. The call manager 130 also records related parameters of the endpoint 110C, such as RTT _local , QoS _proxy , Cap _proxy, and RTT _external , in the conference table. The number of DSP channels of the endpoint 110C is originally 2. After the conference call of the conference system 160 is added, the call manager 130 updates the number of remaining DSP channels of the endpoint 110C to 1, and records the conference. The Cap _proxy parameter field in the table is marked as available in the Availability field.

Step 203, the endpoint 110A dials the telephone number of the conference system 160, and the call manager 130 receives the call request of the endpoint 110A. The call manager 130 described above is judged by the number of DSP channels of the above-mentioned endpoint 110A to be only an attendee.

Step 204: Since the agent currently participating in the conference system 160 has only the foregoing endpoint 110C, in the embodiment, the call manager 130 determines that the agent of the endpoint 110A is the endpoint 110C.

Step 205, the call manager 130 redirects the call request of the endpoint 110A to the endpoint 110C, and establishes a communication connection between the endpoint 110A and the endpoint 110C.

In step 206, the call manager 130 notifies the endpoint 110C to open the multimedia port, processes the voice data stream of the endpoint 110A, and performs subsequent mixing processing. Since the endpoint 110C has received the voice data stream of the endpoint 110A, the current number of remaining DSP channels is decremented to 0, so the call manager 130 updates the current remaining DSP channel number of the endpoint 110C in the conference table to 0. And marked as unavailable in the availability field.

Step 207, the endpoint 110B dials the telephone number of the conference system 160, and after receiving the call request of the endpoint 110B, the call manager determines that the endpoint can be a participant only by the number of DSP channels of the endpoint 110B.

In step 208, since the agent currently participating in the conference system 160 has only the foregoing endpoint 110C, and the endpoint 110C has no remaining number of DSP channels, and can only be an attendee, the endpoint 110B and the conference system 160 are established. Communication connection between.

In step 209, the call manager 130 notifies the endpoint 110B that the multimedia connection is enabled, and starts transmitting and receiving the voice data stream. At this time, the number of calls dialed by the gateway 120 to the PSTN 140 is 2, but a total of 3 endpoints participate in the conference call.

Step 210: The endpoint 110D dials the telephone number of the conference system 160. After receiving the call of the endpoint 110D, the call manager 130 determines that the endpoint may be an attendee by the number of DSP channels of the endpoint 110D, or may be agent.

Step 211, the call manager 130 establishes a communication connection between the endpoint 110D and the conference system 160, and notifies the endpoint 110D to enable the multimedia connection to start transmitting and receiving voice data streams. The call manager 130 records the relevant parameters of the endpoint 110D, such as RTT _local , QoS _proxy , Cap _proxy, and RTT _external , in the conference table. The number of DSP channels of the endpoint 110D is originally 2. After the conference call of the conference system 160 is added, the call manager 130 updates the current number of remaining DSP channels of the endpoint 110D to 1, and records the conference. The Cap _proxy parameter field in the table is marked as available in the Availability field.

Step 212, because there is a new agent, the call manager 130 re-determines that the agent of the endpoint 110B is the endpoint 110D.

Step 213, the call manager 130 redirects the call of the endpoint 110B to the endpoint 110D, and establishes a communication connection between the endpoint 110B and the endpoint 110D.

Step 214, the call manager 130 notifies the endpoint 110D to open the multimedia port, process the voice data stream of the endpoint 110B, and perform subsequent mixing processing. Since the endpoint 110D has received the voice data stream of the endpoint 110B, the current number of remaining DSP channels is decremented to 0, so the call manager 130 updates the current remaining DSP channel number of the endpoint 110D in the conference table to 0. And the availability field is marked as unavailable. At this time, the number of calls dialed by the gateway 120 to the PSTN 140 is still 2, but a total of 4 endpoints participate in the conference call.

If any endpoint is dropped during the conference call, the call manager 130 will update the conference table and wait for the user to redial, and then process the call request of the endpoint according to the foregoing procedure.

Referring to FIG. 3, a flow chart of call management when a passive conference call is performed according to an embodiment of the present invention is shown. In this embodiment, each of the endpoints 110A and 110B has one DSP channel, and the endpoints 110C and 110D respectively have two DSP channels as an example. Since the above-mentioned endpoints 110A and 110B only have one DSP channel, they can only be participants in a conference call; and the endpoints 110C and 110D respectively have two DSP channels, so in a conference call, it is possible to participate in the conference. It can also be an agent. FIG. 3 shows a flow of establishing a passive conference call between the endpoints 110A, 110B, 110C, and 110D and the conference system 160. The main steps are as follows:

Step 301, the call manager 130 receives the call request transmitted by the conference system 160, and the called party is the endpoint 110C. After the call manager 130 transmits the request to the endpoint 110C, it receives an acknowledgment response from the endpoint 110C, and the number of DSP channels of the endpoint 110C determines that it can be an attendee or an agent.

Step 302: The call manager 130 establishes a communication connection between the endpoint 110C and the conference system 160, and notifies the endpoint 110C to enable the multimedia connection to start transmitting and receiving voice data streams. The call manager 130 also records related parameters of the endpoint 110C, such as RTT _local , QoS _proxy , Cap _proxy, and RTT _external , in the conference table. The number of DSP channels of the endpoint 110C is originally 2. After the conference call of the conference system 160 is added, the call manager 130 updates the number of remaining DSP channels of the endpoint 110C to 1, and records the conference. The Cap _proxy parameter field in the table is marked as available in the Availability field.

Step 303, the call manager 130 receives the call request transmitted by the conference system 160, and the called party is the endpoint 110D. After the call manager 130 transmits the request to the endpoint 110D, it receives an acknowledgment response from the endpoint 110D, and the number of DSP channels of the endpoint 110D determines that it can be an attendee or an agent.

In step 304, the call manager 130 establishes a communication connection between the endpoint 110D and the conference system 160, and notifies the endpoint 110D to enable the multimedia connection to start transmitting and receiving voice data streams. The call manager 130 also records related parameters of the endpoint 110D, such as RTT _local , QoS _proxy , Cap _proxy, and RTT _external , in the conference table. The number of DSP channels of the endpoint 110D is originally 2. After the conference call of the conference system 160 is added, the call manager 130 updates the current number of remaining DSP channels of the endpoint 110D to 1, and records the conference. The Cap _proxy parameter field in the table is marked as available in the Availability field. At this time, the number of calls dialed into the gateway 120 by the PSTN 140 is 2, and a total of two endpoints participate in the conference call.

Step 305, the call manager 130 receives the call request transmitted by the conference system 160, and the called party is the endpoint 110A. After the call manager 130 transmits the request to the endpoint 110A, it receives an acknowledgment response from the endpoint 110A and determines that it can only be a participant by the number of DSP channels of the endpoint 110A.

Step 306, since the agent who has participated in the conference call has two endpoints, and the availability fields of both endpoints in the conference table are marked, the call manager 130 calculates the equation (1) to obtain the agents. The P _priority value of the person, and the agent of the above endpoint 110A is determined according to the P _priority value. In this embodiment, the QoS _proxy setting values of the endpoint 110C and the endpoint 110D are the same, and the RTT _local value and the RTT _external value of the endpoint C are both smaller than the RTT _local value and the RTT _external value of the endpoint 110D. For example. Said call session lookup table manager 130 acquires calculation equation (1) related to the desired parameter values, and the calculated value of the end point P _priority values P _priority 110C is smaller than the end D, i.e. above 110C endpoint The priority is higher than the priority of the above endpoint 110D. The call manager 130 determines that the agent of the endpoint 110A is the endpoint 110C according to the priority of each agent.

In step 307, the call manager 130 redirects the call to the endpoint 110C and establishes a communication connection between the endpoint 110A and the endpoint 110C.

Step 308, the call manager 130 notifies the endpoint 110C to open the multimedia port, process the voice data stream of the endpoint 110A, and perform subsequent mixing processing. Since the endpoint 110C has received the voice data stream of the endpoint 110A, the current number of remaining DSP channels is decremented from 1 to 0, so the call manager 130 updates the current remaining DSP channel number of the endpoint 110C to 0, and The Cap _proxy parameter field recorded in the conference table and marked as unavailable in the availability field.

Step 309, the call manager 130 receives the call request transmitted by the conference system 160, and the called party is the endpoint 110B. After the call manager 130 transmits the request to the endpoint 110B, it receives an acknowledgment response from the endpoint 110B and determines that it can only be a participant by the number of DSP channels of the endpoint 110B.

In step 310, since the above endpoint 110C has been marked as unavailable in the conference table, the available agents have only the above endpoint 110D. After the call manager 130 searches the conference table, it determines that the agent of the endpoint 110B is the endpoint 110D.

In step 311, the call manager 130 redirects the call to the endpoint 110D and establishes a communication connection between the endpoint 110B and the endpoint 110D.

In step 312, the call manager 130 notifies the endpoint 110D to open the multimedia port, processes the voice data stream of the endpoint 110B, and performs subsequent mixing processing. Since the endpoint 110D has received the voice data stream of the endpoint 110B, the current number of remaining DSP channels is decremented from 1 to 0, so the call manager 130 updates the current remaining DSP channel number of the endpoint 110D to 0, and The Cap _proxy parameter field recorded in the conference table and marked as unavailable in the availability field. At this time, the number of calls dialed into the gateway 120 by the PSTN 140 is still 2, but a total of 4 endpoints participate in the conference call.

In the middle of a passive conference call, if any endpoint is dropped, the same call management process as the active conference call will be adopted.

Referring to FIG. 4, a schematic diagram of a call management method flow 400 in accordance with an embodiment of the present invention is shown. The above process 400 is applied to the call manager 130 described above, and mainly includes the following steps:

Step S410, receiving a new call request. After receiving the new call request, the call manager 130 further performs the following steps: if it is an outgoing call request, confirm whether it is a call request of the same conference call via the called party's telephone number; if it is an incoming call request Then, it is confirmed by the calling party's telephone number whether it is a call request of the same conference call. If the conference call is newly established, the call manager 130 also creates a new conference table for managing the agents who have joined the conference call.

In step S420, it is determined whether the endpoint related to the call request can only be the participant of the above conference call. The specific judging step is as follows: if it is a dialed call request, it is judged according to the number of DSP channels of the calling party endpoint; if it is an incoming call request, it is judged according to the number of DSP channels of the called party endpoint. If the number of DSP channels of the foregoing endpoint is equal to 1, the endpoint can only be an attendee in the conference call; if the number of DSP channels of the endpoint is greater than or equal to 2, the endpoint may be in the conference call. Participants can also be agents. If the foregoing endpoint can only be the participant of the conference call, the process 400 continues to perform step S430; otherwise, the process branches to step S460.

In step S430, the call manager 130 determines, according to the conference table, whether an agent has participated in the conference call. If an agent has participated in the conference call, it is further determined in step S432 whether there are a plurality of available agents. If there are multiple agents available, the priority of each agent is calculated according to equation (1) in step S440, and the agent with the highest priority is used as the agent of the terminal, and the call is redirected to the The agent then performs the setup call of step S460. If there are no more available agents, it is further determined in step S434 whether there is an available agent. If there is an available agent, the call is redirected to the agent in step S450, and then the setup call of step S460 is performed; if there is no available agent, the setup call of step S460 is directly performed.

After the call setup is completed, in step S470, the call manager 130 further determines whether the relevant information related to the agent in the conference table needs to be updated, and if the new call has been redirected to the agent or the endpoint may be an agent, then Step S480 is executed to update the agent information in the conference table, in particular, the Cap _proxy parameter field for recording the current remaining DSP channel number and the availability field indicating availability; otherwise, the above process 400 is ended.

In another implementation, in the foregoing step S420, if it is determined that the endpoint may be an agent, after performing steps S460 to S480, the call manager 130 further determines whether any participant endpoint is not Redirecting to the agent endpoint, if there is an unredirected participant endpoint, the call manager 130 will perform steps S430 through S480 of the above-described process 400 to select the unredirected participant endpoint. Redirected agent.

In another implementation, in order to increase the number of endpoints participating in the same conference call as much as possible without increasing the number of calls dialed in or out of the same field, the call manager 130 may also be in the above manner. After step S410 of the process 400, the above step S430 is directly performed, so that the agent endpoint in the same conference call can process not only the voice data stream that can only be the participant endpoint but also the voice data of the same agent endpoint. flow.

In summary, the call management method of the call manager 130 described above can effectively reduce the number of external telephone lines of the gateway 120 occupied by the conference call, because the parameters in the equation (1) have taken into account the network environment. Maintain a certain conference call quality. The above call management method can fully support the active and passive teleconferencing systems, and the end user can have a better user experience without changing their usage habits.

In summary, the present invention complies with the requirements of the invention patent and submits a patent application according to law. The above description is only the preferred embodiment of the present invention, and equivalent modifications or variations made by those skilled in the art of the present invention should be included in the following claims.

100‧‧‧Application environment

110‧‧‧First field

120,180‧‧‧ gateway

130,170‧‧‧Call Manager

110A, 110B-110M‧‧‧ endpoint

140‧‧‧PSTN

150‧‧‧ second field

160‧‧‧Conference system

1 is a schematic diagram of an embodiment of an application environment for call management. 2 is a flow chart of an embodiment of call management during active conferences. 3 is a flow chart of an embodiment of call management during passive conferences. 4 is a flow chart of an embodiment of a call management method.

The above and many advantages of the invention will be readily apparent from the following detailed description of the preferred embodiments.

Claims (13)

A method for call management, the method comprising: storing a conference table for recording information of an agent endpoint that has joined a conference call and having a number of DSP channels greater than or equal to 2; receiving a call request; identifying the call request An associated endpoint; determining whether there are multiple available proxy endpoints in the conference table, wherein if the number of DSP channels of the proxy endpoint is greater than 0, the proxy endpoint is an available proxy endpoint; There are multiple available agent endpoints in the conference table, then the priority of each available agent endpoint is calculated; and the call request is redirected to between the endpoint and the highest priority available proxy endpoint. The method for call management according to claim 1, wherein the identifying an endpoint associated with the call request comprises: if the call request is an outgoing call, the endpoint is a calling party; if the call request For an incoming call, the endpoint is the called party. A method for call management as described in claim 2, wherein the priority calculation method of each available agent endpoint is: a ́RTT _local + b ́QoS _proxy + g ́Cap _proxy + w RTT _external , where a, b, g, and w are weight parameters; RTT _local is the delay time between the endpoint and the available proxy endpoint; QoS _proxy is the QoS setting of the available proxy endpoint; Cap _proxy is the current number of DSP channels remaining for the available proxy endpoint; and RTT _external is the delay time for the available proxy endpoint to forward the packet. A method for call management as described in claim 3, wherein a, b, g, and w are weighting parameters, and the sum is 1. The method for call management as described in claim 3, wherein the smaller the value of a ́RTT _local + b ́QoS _proxy + g ́Cap _proxy + w ́RTT _external , the higher the priority. The method for call management according to claim 1, further comprising, after redirecting the call request to the endpoint and the highest priority available proxy endpoint, according to the endpoint and the available The agent endpoint is currently updating the conference table by the number of remaining DSP channels. An apparatus for call management, the apparatus comprising: a processor; and a computer readable storage medium for storing at least one computer program and a conference table for recording that a conference call has been joined And the information of the agent endpoint of the DSP channel number greater than or equal to 2; wherein the computer program includes the instruction set and is executed by the processor, and the executing includes the following steps: receiving a call request; identifying an endpoint associated with the call request Determining whether there are multiple available proxy endpoints in the conference table, wherein if the number of DSP channels of the proxy endpoint is greater than 0, the proxy endpoint is an available proxy endpoint; if the conference table exists A plurality of available agent endpoints, the priority of each available agent endpoint is calculated; and the call request is redirected to between the endpoint and the highest priority available agent endpoint. The apparatus for call management of claim 7, wherein the identifying an endpoint associated with the call request comprises: if the call request is an outgoing call, the endpoint is a calling party; if the call request For an incoming call, the endpoint is the called party. The apparatus for call management according to claim 8, wherein the priority calculation method of each available agent endpoint is: a ́RTT _local + b ́QoS _proxy + g ́Cap _proxy + w RTT _external , where a, b, g, and w are weight parameters; RTT _local is the delay time between the endpoint and the available proxy endpoint; QoS _proxy is the QoS setting of the available proxy endpoint; Cap _proxy is the current number of DSP channels remaining for the available proxy endpoint; and RTT _external is the delay time for the available proxy endpoint to forward the packet. The device for call management according to claim 9, wherein a, b, g, and w are weighting parameters, and the sum is 1. The apparatus for call management according to claim 9 of the patent application, wherein the smaller the value of a ́RTT _local + b ́QoS _proxy + g ́Cap _proxy + w ́RTT _external , the higher the priority. The apparatus for call management according to claim 7, wherein the instruction set further performs the following steps: after redirecting the call request to the endpoint and the highest priority available proxy endpoint, according to The conference table is updated with the number of DSP channels currently remaining by the endpoint and the available agent endpoint. A computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor for implementing a call as claimed in any one of claims 1 to 6 The steps of the management method.