JP2003169079A - Voip trunk bypass system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve a deterioration in scalability in a fault and to actualize VOIP network constitution with high reliability. <P>SOLUTION: In a device which determines and manages a trunk termination destination of PBXs (2, 3) whose scalability of termination is to be improved by constructing a termination group with a plurality of VOIP trunks, a VOIP trunk (1-a') of an origination-side PBX (1) is provided with alternative address information for bypassing in the case that a connection with a normally connected device is disabled so as to evade such cases that the trunks in the same termination group become unable to terminate in the case of a failure of connection with the device, thereby enabling a bypass connection with the alternative address. In a preferred example, a general trunk in the group is enabled to terminate, for example, if a VOIP trunk 2-a being a representative trunk of the termination-side PBX 2 cannot be connected because of a fault. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a VO capable of voice transmission in an internet protocol (IP) network.
It is suitable for application to the incoming call diversion processing in a network system using the IP (Voice over IP) technology, and more specifically, it determines the trunk destination of a PBX that forms an incoming call group by a plurality of VOIP trunks. The present invention relates to a bypass method that is advantageous when a device that performs management is included.

[0002]

BACKGROUND OF THE INVENTION With the recent development of the Internet in recent years, data and voice are transmitted to corporate networks such as communication networks connecting a plurality of bases (each business office, etc.). An IP network in which signals and signals are integrated and transmitted is being used, and as a result, a movement to reduce the operation cost of the network has been activated. Introducing a system that enables voice transmission in such an IP network can be expected to reduce the operating cost of the entire in-company network system.

Against this background, PBXs having a structure in which a VOIP trunk is mounted and connected to an IP network have been developed and provided in the past, and this fulfills the above demands. Where VOIP
The trunk is a trunk for connecting a PBX via an IP network and transmitting a voice signal, and is used as a VOI for a trunk device for line connection, control, etc.
Although it is equipped with P function, such VOIP
A PBX using a configuration in which a trunk is mounted and connected to an IP network is used, for example, by installing and using each of the above-mentioned bases in the company as an incoming / outgoing PBX.
It can be used to build a VOIP network.

In that case, the scalability (sca
It is necessary to improve the reliability (extensibility) and quality, but in consideration of such points, if the following configuration is adopted, it is possible to improve the scalability of incoming calls. . That is, the PBX as described above
As a receiving side, a configuration is used in which a receiving group is composed of a plurality of VOIP trunks, and a device for determining / managing such a PBX trunk destination is used. Is adopted,
It is also effective in terms of quality such as improving the scalability of incoming calls and ensuring communication.

5 to 8 show comparative examples which will be referred to in comparison with the embodiments of the present invention described later.
Shows a system configuration in the case where a PBX including a plurality of VOIP trunks is included in the network, and FIGS. 6 and 7 show VOIs in the comparative example.
FIG. 6 is a diagram for explaining the principle of P trunk incoming processing.

In FIG. 5, PBXs 1, 2, 3, and 4 are
The PBXs each have a VOIP trunk and are connected to an IP network.

VOIP in each PBX 1, 2, 3, 4
The trunk is connected to the IP network 100 via routers 12, 22, 32, 42 for connecting to the IP network, respectively. In the illustrated example, regarding the VOIP to be accommodated and mounted, the PBX 1 is VOIP1-a.
, While PBX4 has VOIP4-a, while PB
X2 has a plurality of VOIP2-a, 2-b, 2-c,
In addition, an example in which the PBX 3 also has a plurality of VOIPs 3-a and 3-b is shown. In addition, on the PBX3 side,
A reference numeral 33 indicates a gatekeeper (GK) as a control device for setting an IP path. This will be discussed further below.

In the above system, each P is basically
Each of the BXs 1, 2, 3, and 4 has a VOIP trunk for connecting a PBX via the IP network 100 and transmitting a voice signal, and the voice signal can be transmitted as a transmitting side and a receiving side. Is a PB with multiple VOIPs
In X2 and X3, when an incoming call is received, it is possible to configure an incoming call group with a plurality of VOIP trunks owned and to make an incoming call bypass to an empty trunk in the group. When a PBX having such a plurality of VOIP trunks is set as a called party, an incoming call to the VOIP trunk is
It can be performed as follows based on the determination / management of the destination (trunk) as described below.

Taking the case where the PBX2 is the receiving side as an example, one of the methods for receiving a VOIP trunk is as follows.
As with the terminating PBX2, its multiple VOIPs
One of the trunks 2-a, 2-b, and 2-c is defined as a representative trunk, and this has a representative trunk attribute (for example, the VOIP trunk 2-a is a representative trunk), and another VOIP. The trunks (VOIP trunks 2-b, 2-c) are adapted to be used as general trunks.

Regarding the relationship between the representative trunk and the general trunk, the general trunks 2-b and 2-c are, for example, periodically and when the CODEC line status (whether there is an empty line) changes. In addition, while transmitting information such as an IP address, a port number, a line state, etc. to the representative trunk 2-a, on the representative trunk 2-a side,
This should be monitored, and general trunks 2-b, 2-c
By receiving the above information transmitted from the VOIP trunk 2-b, which is a general trunk in the same group,
The state of 2-c can be identified.

However, for example, when the PBX 1 is used as the calling side (originating station), the VOIP trunk 1-a on the calling side performs address setting registration data (see FIG. The IP address and port number corresponding to the line number are extracted from 6), and first the representative VOI of the receiving side in the PBX2 forming the above-mentioned receiving group.
A P trunk (VOIP trunk 2-a) is connected.

FIGS. 6 and 7 show the basic contents and procedure of the method of determining the destination. The connection processing flow to the destination trunk of FIG. 7 is a step of extracting the IP address and port number corresponding to the destination line number from the normal connection address information registration data illustrated in FIG. 6 (S1).
0); TC for the extracted IP address and port number
P / IP (Transmission Control Protocol / Interne
t Protocol) Step for executing connection establishment processing (S20); Step for checking whether establishment is established (OK) (S30); When establishment OK is reached, a call setup (SETUP) message is sent to the established connection. In the step of transmitting (S40), if there is a delay (establishment N
In the case of G), the call connection processing may be stopped and the aboard processing may be performed (S50).

Therefore, the PBX from the above PBX1
In the case of an incoming call to the destination 2, the VOIP trunk 1-a of the originating PBX 1 corresponds to the normal connection address information registration data in order to connect to the representative VOIP trunk 2-a of the receiving PBX 2. Address information (for example, IP address “192.168.2.
49.1 ”, port number“ 16384 ”) and a TCP / IP connection is established for the extracted address information (IP address, port number) (S10,
S20), it is checked (S30).

Here, the representative VOIP trunk of the receiving side 2-
a is a general trunk (V
Since the states of the OIP trunks 2-b and 2-c) can be identified, the line states of the general trunks in the same group are identified and the destination is determined. Specifically, T
When the CP / IP connection is established, the destination is determined by round robin including the representative trunk 2-a (self trunk), and the destination is the self trunk 2-a.
If you decide to, by performing the normal incoming call processing,
In addition, when the other general trunks 2-b and 2-c are decided, the IP addresses, port numbers, line states, etc. are transferred from the general trunks 2-b and 2-c to the representative trunk 2-a as described above. Based on this information, the destination trunk 1-a is notified of the detour destination address information such as the destination of the incoming call, and upon receipt of such an instruction, the destination trunk 1-a is notified. This can be realized by causing 1-a to execute call setup for the incoming call trunk (2-b, 2-c) of the detour (S40).

Further, in addition to the above-described method of circumventing the incoming call, in which the representative trunk controls the incoming call to the VOIP trunk in the incoming call group, in the case where the incoming call group is also formed by a plurality of VOIP trunks, All the VOIP trunks are general trunks as described above, and an external gatekeeper (GK) performs the functions of the representative trunks described above to realize the above-described determination of the destination trunk at the time of incoming call. can do. The PBX 3 side in FIG. 5 mentioned above is also shown as an example of a system when such a method is adopted. In this case, the VOIP trunk 3-by the external gatekeeper 33, not by the VOIP trunk itself in the incoming call group.
A plurality of VOIP trunks 3-a and 3-b, which are configured to control incoming calls to a and 3-b and are included in the incoming-side PBX 3 in the network and which form an incoming call group, are all general trunks. The function of instructing which VOIP trunk (3-a, 3-b) in the incoming call group to connect is implemented by the gatekeeper 33.

Thus, by providing a plurality of VOIP trunks mounted on the PBX, it is possible to improve the scalability of incoming calls, and one VOIP trunk has only one PB.
Compared with the case where X4 is the receiving side, the incoming call scalability is higher in the PBX3 that can configure the incoming call group with two VOIP trunks, and the incoming call group is configured with three more VOIP trunks than the PBX3. The PBX2, which has already been used, has higher incoming call scalability and greater expandability. However, the following consideration can point out the following points that are still insufficient and can be improved.

That is, while the above advantages can be expected, in a device for determining / managing a trunk destination of a PBX in which an incoming call group is composed of a plurality of VOIP trunks and the scalability of incoming calls is improved, if,
When the connection to the device fails, the situation is such that the trunks in the same incoming call group cannot receive the call.

For example, when the representative trunk (VOIP trunk 2-a) in the PBX 2 is used as such a device, the representative trunk 2 of the incoming group may be obtained by the VOIP trunk receiving method as described above.
If a failure occurs in -a, it is not possible to make an ordinary trunk (VOIP trunk 2-b, 2-c) in the group receive an incoming call from another station (the originating PBX in the network). Here, the sequence diagram of FIG. 8 shows such an example, and this diagram shows the system configuration diagram (FIG. 5),
The above trunk incoming process is provided for explaining the operation when the PBX equipped with a plurality of VOIP trunks in the system cannot receive incoming calls when a failure occurs. In the sequence diagram, the VOIP trunk 1-
In the transmission from the PBX 1 having a, the receiving PBX
No TCP / IP connection can be established to the VOIP trunk 2-a, which is the representative trunk in No. 2 (x mark), so that the other VOIP trunk 2-b (even if the other VO
(Even if IP trunk 2-b is an empty trunk)
The state where connection is disabled is shown. Therefore, including the representative trunk and other general trunks, the VOIP trunks in the incoming group (hence the PBX2
2) A situation occurs where you cannot receive an incoming call. This is a multiple VOI
Although it is trying to improve the scalability by constructing an incoming call group with the P trunk, it means that it cannot be utilized to the full advantage.

Further, as described with respect to the case of the PBX 3, even if the method of determining the called party by using the gatekeeper 33 is used, there is a similar problem. That is, in this method, if a failure occurs due to the gatekeeper going down, it is impossible to reach all VOIP trunks in the network managed by the gatekeeper. Therefore, the same situation as above is brought about. For example, an incoming call cannot be received by any of the VOIP trunks 3-a and 3-b in the incoming call group whose incoming call is controlled by the gatekeeper 33 (as a result, the incoming call cannot be received by the PBX 3).

Therefore, it is desirable to determine a trunk destination of the PBX which configures an incoming call group with a plurality of VOIP trunks to improve the scalability of incoming calls.
In the device that manages, it is possible to avoid the problem that trunks in the same incoming call group cannot be received when the connection to the device fails, improving the deterioration of scalability at the time of failure, etc. That is, it is possible to realize a highly effective VOIP network configuration. It is also desirable that the above can be realized for the representative trunk of the VOIP trunk or the gatekeeper device that constitutes the above-mentioned incoming call group. For example, if the representative trunk becomes unconnectable due to a failure. It is possible to allow general trunks in the group to receive calls.

Based on the above consideration, the present invention has a device capable of eliminating the above disadvantages and determining / managing the trunk destination of the PBX forming a destination group by a plurality of VOIP trunks. In this case, even if a failure occurs in the device, it is possible to improve the deterioration of scalability due to the failure and to realize a highly reliable VOIP network configuration. Is.

[0022]

According to the present invention, the following VOIP trunk detour system is provided. That is, a VO that connects PBXs via the Internet protocol network and transmits audio signals.
A detouring method applicable to a network system having an IP trunk on each of the originating and terminating PBXs, and having a PBX forming an incoming call group by a plurality of VOIP trunks in the system and
In the device for determining / managing the trunk destination of the BX, the VOIP trunk of the originating PBX is provided with the VOIP trunk so as to prevent the VOIP trunk in the incoming group from being unable to receive when the connection to the device fails. It is characterized in that it has means for providing alternative address information for making a detour when connection to the device is impossible, and enabling detour connection to the alternative address.

According to the present invention, an incoming call group is constituted by a plurality of VOIP trunks, and the destination of the trunk of the PBX that determines the scalability of incoming calls is determined /
An alternative to bypass the VOIP trunk of the originating PBX when the connection to the device to be managed fails so that the VOIP trunk in the incoming call group cannot be blocked Address information is provided to enable a bypass connection to the alternative address.
Thus, it is possible to provide a good solution from the point of view mentioned above, and according to the present invention, a plurality of VOIs can be provided.
Even if the device at the address normally connected to the PBX that constitutes the incoming call group on the P trunk is in a connection disabled state due to a failure or the like, it is possible to bypass to the alternative address.
It is possible to improve the deterioration of scalability in the event of a failure, etc., and to realize a highly reliable VOIP network configuration.

In a preferred embodiment of the present invention, a PBX that has a plurality of VOIP trunks, configures an incoming call group with a plurality of VOIP trunks, and bypasses the incoming call to an empty trunk in the group, thereby improving the scalability. In a configured network system, multiple VOIPs
As a device for determining / managing a trunk destination of a PBX that forms an incoming call group by a trunk, when one of the plurality of VOIP trunks is a representative trunk and the other is a general trunk, the representative trunk, or Targeting gatekeepers in PBXs where all of the multiple VOIP trunks are general trunks, the above bypass connection is possible even if these cannot be connected due to a failure, and the above is realized in the same manner. If possible.

When the device for determining / managing the trunk destination is the representative trunk, the PBX on the originating side in the network has a plurality of VOIs constituting the incoming group.
A control method that recognizes the address information of the representative trunk of the P trunk, first connects to the representative trunk when connecting to the called side, and receives an instruction as to which trunk in the incoming group to connect to, and , The VOIP trunk mounted on the originating PBX must be provided with address information of another trunk within the same incoming call group that substitutes for the representative trunk when the connection to the representative trunk of the receiving side fails, and must be registered in advance on the originating side. When the connection to the designated trunk on the receiving side fails, the connection is bypassed to the alternative trunk to perform connection processing so that even if the representative trunk on the called side cannot be connected, the incoming trunk can be called. The present invention can be preferably implemented. In the case of a gatekeeper, all the VOIP trunks forming the incoming call group accommodated in the incoming call side PBX in the network are general trunks, and an instruction to which trunk in the incoming call group to connect is given. In a system where an external gatekeeper is used to perform the function, the gatekeeper is duplicated by providing the above detour means, and even if the normally used gatekeeper cannot be connected, it is diverted to the other gatekeeper. Configure to allow incoming calls on the called trunk,
The present invention can be preferably implemented. In a preferred example of the present invention, the alternative address information is provided with information for identifying whether or not there is a detour, so that it is possible to select whether or not the detour should be executed, and the present invention can be suitably implemented. it can.

[0026]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. 1 to 3 and 4 are diagrams for explaining the embodiment of the present invention. Of these, Figure 1
FIG. 1 is a system configuration diagram of an embodiment of the present invention, and
FIG. 2 shows an example of the contents of the normal connection address information registration data and the alternative address information registration data including the alternative address information registration data introduced according to the present invention, and FIG. 3 shows the alternative address information registration data. An example of the connection processing flow to the destination trunk that realizes the detour to the alternative address by using also is shown. These are also shown in comparison with FIGS.
FIG. 3 is also a diagram for explaining the principle of the method of the present invention.

As in the case of FIG. 5, FIG. 1 shows a system including a PBX having a plurality of VOIP trunks in the network. Also in this example, PBXs 1, 2, 3, and 4 are shown, each of which is equipped with a VOIP trunk and is connected to an IP network.

Each of these four PBXs accommodates extension telephones 11, 21, 31 and 41 (representing one of a plurality of extension telephones), and is used as, for example, a corporate network as described above. When configuring a VOIP network, it can be installed and used as a private branch exchange (private branch office) at each base (four business offices of various scales, etc.). The VOIP trunks in each PBX 1, 2, 3, 4 are routers 12, 22, 3 respectively.
2, 42 are connected to the IP network 100.

PBX via the IP network 100
Regarding the VOIP trunk that connects the question and transmits the voice signal, the PBX 1 connects the VOIP trunk 1-a 'and the PVO 1
BX4 is a VOIP trunk 4-a, PBX2 is a plurality of VOIP trunks 2-a, 2-b, 2-c, and PBX3 is a plurality of VOIP trunks 3-a, 3-b.
Each is housed and installed.

Here, when the PBX 1 having the VOIP trunk 1-a 'becomes the calling side (originating station) when making and receiving a call in the present network system, the PBX 1 equipped with the VOIP trunk of the calling side PBX (thus , PBX1 VOIP trunk 1-a ') is provided with alternative address information (FIG. 2B) at the time of connection failure with respect to a normal connection address, which will be described later, and is preliminarily registered on the originating side. As an example, this is exemplified in the present embodiment. In addition, VOIP trunk 4-
PBX4 with a has a VO like PBX2,3
It is shown as an example of a case where the incoming group is not configured in the IP trunk. On the other hand, PBX2 and PB
X3 is shown as a PBX that has multiple VOIP trunks, configures an incoming call group with the multiple VOIP trunks, and bypasses the incoming call to an empty trunk within the group to improve scalability. In the network system of No. 1, the PBXs 1 and 4 above,
It is configured to have the PBXs 2 and 3.

In this embodiment also, as an apparatus for determining / managing a trunk destination of a PBX for which an incoming call group is configured by a plurality of VOIP trunks to improve the scalability of incoming calls, Figure 5
As described in Section 7, in the case of PBX2, one of the plurality of VOIP trunks 2-a, 2-b, and 2-c is the representative trunk and the other is the general trunk, The representative trunk (for example, VOIP trunk 2-a in FIG. 1) is used, and the PB
In the case of X3, it is based on a method using an external gatekeeper 33.

In addition to this, in the present embodiment, in the device (including the VOIP trunk 2-a and the gatekeeper 33) that determines / manages the trunk destination of the PBX, the connection to the device fails. In order to solve the problem that trunks in the same incoming call group cannot receive calls when it does, improve the deterioration of scalability at the time of failure and realize a highly reliable VOIP network configuration,
An alternative address information is provided for bypassing the connection to the device normally connected to the VOIP trunk on the calling side, and a means for enabling a bypass connection to the alternative address is introduced.

Specifically, for example, in FIG. 1, PBX1
Is the originating side, and the representative trunk (VOIP trunk 2
In the example in which the PBX2 using -a) is set as the called side, the calling side PBX1 in this network has a plurality of VOIP trunks 2 that form a called group in the PBX2.
-A, 2-b, 2-c recognize the address information of the representative trunk (VOIP trunk 2-a), and first connect the representative trunk (VOIP trunk 2-a) when connecting to the receiving side.
To the VOIP trunk 1-a ′ mounted on the originating PBX 1 and adopting a control method for receiving an instruction to which VOIP trunk in the incoming group to connect to. Trunk (VOIP
When the connection to the trunk 2-a) fails, the address information of another trunk within the same incoming call group, which is an alternative to the representative trunk (VOIP trunk 2-a), is provided and registered in advance on the outgoing call side, so that the incoming call side can be registered. If the connection to the representative trunk (VOIP trunk 2-a) of 1 is failed, the representative trunk (VOIP trunk 2-
Even if it is not possible to connect to a), it is configured so that the incoming trunk can be called. Further, the above method can be similarly applied to the case where the PBX 3 using the gatekeeper 33 is set as the receiving side. As shown in FIG. 1, in addition to the gatekeeper 33 which is normally connected by duplicating the gatekeeper. By providing another gatekeeper 34 to be bypassed when connection to the gatekeeper fails, even if the normally used gatekeeper 33 cannot be connected, it is bypassed to the other gatekeeper 34 so that the incoming trunk can be reached. Can be configured as. In this case, the alternative address for the bypass connection can be assigned and set on the other gatekeeper 34 side, and the alternative address information can be registered in advance on the calling side.

For this reason, in this embodiment, in FIGS. 2 and 3, which also serves to explain the principle of the method of the present invention, FIGS.
As shown in contrast to the above, the data content of FIG. 6 includes data (FIG. 2B) for registering an alternative address when the connection fails for the normally connected address. With such a configuration, the originating side can refer to the alternative address registration data and recognize the alternative address even when the connection fails in the connection process to the destination trunk, and thus the process can be continued. Becomes Furthermore, in the connection processing flow to the destination trunk, if the connection to the normal connection address fails,
Processing for extracting the alternative address information from the alternative address information registration data and connecting to the alternative address if a detour is possible is added (FIG. 3).

Here, for example, a configuration can be adopted in which the contents of the alternative address information are added with information for identifying the presence / absence of a detour, and in this case, the destination trunk is further delivered. In the connection processing flow of, it is possible to incorporate processing for checking whether detour execution is necessary by using the additional information regarding the presence or absence of detour and selectively switching whether or not detour execution is performed based on the result. If set to, it will be more effective. In the data content of FIG. 2 and the connection processing flow to the destination trunk of FIG. 3, such a configuration is also taken into consideration.

Looking at the connection processing flow to the destination trunk of FIG. 3, this is the same step S as in the case of FIG.
In addition to the processing of 10 to S50, the following processing is performed. That is, as the processing in the case of establishment NG in step S30, a step of extracting detour presence / absence information corresponding to the destination line number from the alternative address information registration data (S31), and determining whether or not there is a detour destination and detouring If there is no destination, the process proceeds to step S50, and if there is a detour destination, the process switches to step S35 or below (S32).
If there is a detour destination, a step (S35) of extracting the IP address and port number corresponding to the line number of the destination from the alternative address information registration data, and the step S35.
Followed by T for the extracted IP address and port number
The step of executing the CP / IP connection establishment process (S36), and the establishment success (O
K), and if the establishment is OK, step S
40, and a step (S37) of switching the processing to step S50 in the case of establishment NG.

According to this, for example, when the PBX 2 is the receiving side, the calling side VOIP trunk 1-a 'at the calling station (PBX 1) is the receiving side representative trunk 2-a (normal connection destination).
When a connection failure is encountered, it can be diverted to a pre-registered alternative address. Basically, the registration data is, as illustrated in FIGS. 2 (A) and 2 (B), for an address to be normally connected to one called number, and when connection to the normal destination fails. An alternative address to connect can be registered. And, preferably, the information indicating the presence / absence of the detour in the alternative address information registration data used when the connection is lost can be registered as "present" or "absent".

On the sending side, basically, when there is no response for a certain period of time in response to a connection connection request to a normal destination by using the information of the address to be normally connected and the alternative address for this, at that time Thinks that the connection to the normal destination fails due to a failure or the like and the detour connection should be made, and tries to connect to the alternative address (step S
30 → ... → S35 → S36). Then, if this succeeds, it is possible to send a call setup (SETUP) message to the alternative address (step S37 →
S40). After that, the call connection process can be executed, and in the case of FIG. 8, if the representative trunk of the incoming call group fails and the connection cannot be established, another VOIP in that group cannot be connected.
I couldn't make it to the trunk,
According to the above configuration, even if a failure occurs in the representative trunk 2-a and the connection cannot be established, another trunk in the same group can receive an incoming call.

[Specific Example 1 (for PBX2)]: FIG.
8 is a sequence diagram showing an example of a bypass connection at the time of such a failure, which is shown in comparison with FIG. 8. Hereinafter, a more specific description will be given with reference to FIGS. Now, in FIG. 1, the originating side PBX 1 is V
It is assumed that the OIP trunk 1-a 'performs a connection process for the terminating PBX 2 according to the process flow of FIG. 3 for the VOIP trunk 2-a that is the representative trunk of the terminating group (steps S10 and S20). .

The processing in this case may be the same as that already described in FIG. 7 and the like. In order to connect to a normal destination, the normal connection address information registration data (FIG. 2 (A)) indicates that the incoming call is received. The above address information (IP address, port number) may be extracted and the TCP / IP connection establishment processing may be executed. Note that here, an address to which a normal connection is made (for example, the IP address “192.16
8.249.1 ”, port number“ 16384 ”) and the representative VOIP trunk 2-a is set, the alternative destination address when the connection fails is as shown in FIG. 2B. After the information is set to "Yes", its alternative address (for example, IP address "1
192.168.249.2 ", port number" 1638
4 ”) to the VOIP trunk 2 within the same incoming call group.
It is assumed that b is set.

In the connection processing as described above, the connection is V as shown in the state (1) of the sequence diagram of FIG.
If the OIP trunk 2-a fails (TCP / IP connection to the VOIP trunk 2-a cannot be established (mark x): NG established in step S30), then in the present process flow, first, an alternative From the alternative address information registration data (FIG. 2 (B)) in which the information for identifying the presence / absence of a bypass is added to the address information content of another trunk in the same incoming call group, the bypass presence / absence information corresponding to the destination line number is extracted. Then, based on this, it is judged whether or not there is a detour destination, and it is checked whether or not detour execution is necessary (steps S31, S).
32). Here, as will be described later, in the case where the information of "without" is set in the information regarding the presence or absence of the detour, step S35 and the subsequent steps are skipped, and step S5 is performed.
The process flow can be ended by proceeding to 0.

However, since the information about the presence / absence of a detour is set to "present" as described above,
Step S35 and subsequent steps are selected, as shown in FIG. 3, the address information of the detour destination is extracted from the alternative address information registration data (FIG. 2 (B)), and the connection processing is performed again with respect to the VOIP trunk 2-b (alternative trunk). (Step S3
5, S36). In this way, the VOIP trunk 1-a 'of the originating PBX 1 can recognize the alternative address when the normal connection is lost, and can continue the process for the alternative trunk.

According to the above-described method according to the comparative example of FIGS. 5 to 8, the registration side information of FIG. 6 is used as the registration address information which can be recognized as pre-registered data on the transmission side in the connection process. Since it depends on the content of the address information registration data, therefore, the originating VOIP trunk 1-a (FIG. 5) can first recognize the address information of the representative VOIP trunk 2-a which is the normal connection destination of the terminating PBX 2. However, only that can be recognized (Fig. 7). That is, if the connection itself to the representative VOIP trunk fails, the VOIP trunk 1-a becomes the trunk 2-in the incoming group from the representative VOIP trunk 2-a that is no longer connectable. While the notification of address information such as b is not received (as a result, the PBX 2 cannot receive the call (FIG. 8)), the detour method does not have such a situation and the alternative address when the normal connection is lost is given. It is recognizable.

Then, the state (2) in the sequence diagram of FIG.
If the connection is successful (caller side VOI
Successful establishment of TCP / IP connection from P trunk 1-a 'to VOIP trunk 2-b (in case of establishment OK in step S37), call setup processing is continued for VOIP trunk 2-b, and VOIP trunk 2 -B
As shown in the state (3) of the sequence diagram of FIG. 4, the VOI
A SETUP message (call setup message) is transmitted from the P trunk 1-a '(step S40), and thus
To its VOIP trunk 2-b, and hence the terminating PB
An incoming call can be made to X2.

In this way, the detour processing can be executed,
According to this, the VOIP trunks 2-a, 2-b, 2-
In c, the device (the VOIP trunk 2-a that is the representative trunk of the incoming call group) of the address that is normally connected to the station (PBX2) forming the incoming call group is in a connection impossible state due to a failure or the like. However, since it becomes possible to make a detour to the device of the alternative address, that is, the VOIP trunk 2-b, it is possible to improve the deterioration of scalability at the time of a failure or the like, and to realize a more reliable VOIP network configuration.

[Specific Example 2 (for PBX3)]:
According to the detour method as described above, the same thing as above can be realized also when the PBX 3 using the gatekeeper is set as the receiving side. In this case, in addition to the gatekeeper 33 that is normally connected, another gatekeeper 34 that should be bypassed when the connection to the gatekeeper 33 fails is introduced, and even if the gatekeeper 33 cannot be connected, the other gatekeeper 33 is connected. The alternate address for the bypass connection is assigned to the other gatekeeper 34 side and set so that the incoming call can be received by the called side trunk by detouring to 34, and the alternative address information is registered in advance on the calling side. To

As mentioned above, the receiving side PBX 3 of FIG. 1 configures an incoming call group with a plurality of VOIP trunks to determine / manage the destination of the trunk of the PBX for improving the scalability of incoming calls. A gatekeeper is used as a device for performing the VOIP of the PBX3.
This is an example of the configuration that controls the incoming call to the trunks 3-a and 3-b. However, as described in [Specific Example 1 (PBX2)], the originating side P
Since the VOIP trunk 1-a 'accommodated in the BX1 can recognize an alternative address when a normal connection is lost, the gatekeeper has a dual configuration, that is, the trunk destination is determined / determined as described above. It is possible to duplicate the gatekeepers used as the management device as the gatekeepers 33 and 34 as shown in FIG.

Then, the gatekeepers 33, 34
As for the normal connection address information registration data and the alternative address information registration data of FIGS. 2 (A) and 2 (B),
The address to connect normally (for example, IP address "19
2.168.250.4 ”, port number“ 1639
0 ”), one of the gatekeepers 33 is set, and when the connection fails, a bypass destination alternative address (for example, IP address“ 192.168.250.5 ”, port number“ 163 ”).
90 "), the other gatekeeper 34 may be set. Further, the information regarding the presence / absence of the detour may be set to “present”. The relationship between the gatekeeper 33 and the gatekeeper 34 is basically the representative VOIP trunk 2-a that is normally connected in the above [Specific Example 1 (PBX2)] and the detour destination when the connection fails. This is the same as the relationship with the VOIP trunk 2-b.

Therefore, when the gatekeeper 33 is set to the normally connected address and the gatekeeper 34 is set to the alternative address as described above, if the detouring process is executed according to the process flow of FIG. , Originating PBX
Gatekeeper 3 from 1 VOIP trunk 1-a '
In the process of connecting to the third gatekeeper 33, even if the connection to the gatekeeper 33 fails, the other gatekeeper 34
A detour connection is possible to the VOIP trunk 3-
Incoming calls can be made to a and 3-b. In this case, all VOIP trunks managed by the gatekeeper 34 and accommodated in the PBX 3 can be set as the incoming trunks.

In this way, the detour process can be executed by the receiving side PBX 3 as well, and similarly, the VOIP trunk 3-
Stations (PBX3) that make up the incoming call group with a and 3-b
On the other hand, even when the device of the address normally connected (in this example, the gatekeeper 33) becomes unconnectable due to a failure or the like, it is possible to bypass the device of the alternative address, that is, the other gatekeeper 34. It is possible to improve the deterioration of scalability in the event of a failure and to realize a more reliable VOIP network configuration.

[Specific Example 3 (When selecting whether or not to perform detour execution ]
)]: As described above, in the network system of FIG. 1, the PBX 4 having the VOIP trunk 4-a is
It is shown as an example of one that does not form an incoming call group like the above PBX2 and PBX3, and when it becomes the incoming call side in the network, the incoming call side PBX4 in FIG.
Is a system in which a VOIP trunk does not form an incoming call group.

In this embodiment, it is possible to adopt a configuration in which information for identifying the presence / absence of a detour is additionally provided, and alternative address information registration data (FIG. 2 (B)), information indicating whether or not there is a detour is registered, so that step S31 in FIG.
In the process of 32, as described above, it is possible to select whether or not detour execution is necessary. Therefore, the connection process to the receiving side PBX 4 which does not form the receiving group can be executed without any problem. If the extracted detour presence / absence information is set to "none" in the processes of steps S31 and S32, the processes of steps S35 to S37 are all skipped,
The processing flow of FIG. 3 can be ended in step S50, which means that even if steps S35 to S37 for detour execution are incorporated in the processing, as a result,
It is substantially equivalent to the processing flow of FIG. 7, and the addition of these steps S35 to S37 to the processing flow of FIG. 7 does not cause any influence on the connection processing for the receiving side PBX 4.

On the other hand, the selection of whether or not the detour execution is necessary can bring about the following fineness. That is, for example, in the detouring process for the terminating side PBX2 as described in [Specific Example 1 (PBX2)], a case where it is not desired to detour to the VOIP trunk 2-b due to, for example, maintenance may be assumed.
If a configuration that enables selection of whether or not detour execution is required by providing information for identifying the presence or absence of detour is also applicable to such a case, as described above, if the VOIP trunk 2 -If you don't want to divert to b,
By setting the presence / absence of detour of the alternative address information registration data to "none", the detour can be stopped. Therefore, in this case, in addition to the above effects, it is possible to flexibly respond to the case where it is not desired to make a detour due to maintenance or the like, and when the detour is required and the detour is necessary, the detour connection can be appropriately performed. If not, the above-described selection processing is possible so that the detour processing is not executed, and the processing becomes more detailed. The present invention can also be implemented in consideration of such a configuration.

[Brief description of drawings]

FIG. 1 is a system configuration diagram for explaining an embodiment of the invention.

FIG. 2 is a diagram showing an example of contents of normal connection address information registration data and alternative address information registration data.

FIG. 3 is a diagram showing an example of a connection processing flow to a destination trunk.

FIG. 4 is a sequence diagram showing a state of detour at the time of failure.

FIG. 5 is a system configuration diagram of a comparative example when compared with the present invention, in comparison with the present invention.

FIG. 6 is a diagram showing an example of contents of normal connection address information registration data in the same system.

FIG. 7 is a diagram showing a processing flow for connecting to a destination trunk in the same system.

FIG. 8 is likewise a sequence diagram for explaining a fault in the system.

[Explanation of symbols]

1 PBX (originating PBX) 1-a 'VOIP trunk 2, 3, 4 PBX (incoming PBX) 2-a, 2-b, 2-c VOIP trunk 3-a, 3-b VOIP trunk 4-a VOIP trunk 11,21,31,41 Extension telephone 12, 22, 32, 42 Router 33,34 Gatekeeper

   ─────────────────────────────────────────────────── ─── Continued front page    F term (reference) 5K030 GA11 HB01 HC01 HD01 JA13                       KA16 LB08 MA07 MB16 MD02                 5K051 AA01 AA09 CC01 CC02 FF02                       FF17 GG03 GG06 GG14 HH16                       LL07

Claims (5)

[Claims] 1. A VOI for connecting a PBX and transmitting a voice signal via an internet protocol network.
It is a detour method applicable to a network system that has P trunks in each of the originating and terminating PBXs, and has a PBX that constitutes an incoming call group by a plurality of VOIP trunks in the system and also has a trunk destination of the PBX. To prevent the VOIP trunk in the incoming call group from being unable to receive an incoming call when the connection to the device that makes the decision / management fails.
VOIP trunk detouring method, characterized in that the VOIP trunk of the originating PBX is provided with means for providing alternative address information for detouring when connection to the device is not possible, and enabling detour connection to the alternative address. . 2. A network system including a PBX which has a plurality of VOIP trunks, configures an incoming call group with a plurality of VOIP trunks, and bypasses incoming calls to an empty trunk in the group to improve scalability. In the case where one of the plurality of VOIP trunks is a representative trunk and the other is a general trunk, as an apparatus for determining / managing a trunk destination of a PBX forming an incoming call group by the plurality of VOIP trunks, , Its designated trunk, or its multiple VOIPs
2. The VOIP trunk detour system according to claim 1, wherein a gatekeeper in a PBX in which all trunks are general trunks is used. 3. The VOIP trunk detour system according to claim 2, wherein a device that determines / manages a trunk destination of a PBX forming a destination group by the plurality of VOIP trunks is the representative trunk, The calling side PBX recognizes the address information of the representative trunk, and when connecting to the called side that constitutes the called group, first performs a connection process for the called trunk so that A control system that receives an instruction as to which trunk to connect to is adopted, and a VOIP trunk mounted on the originating PBX has the same incoming call that substitutes for the representative trunk when the connection to the representative trunk fails. Address information of another trunk in the group is provided as alternative address information, and this A VOIP trunk detouring method characterized in that, when the connection to the representative trunk fails by performing registration on the calling side in advance, the connection processing is performed by detouring to the alternative trunk. 4. The VOIP trunk detouring method according to claim 2, wherein the device for determining / managing a trunk destination of a PBX forming a destination group by the plurality of VOIP trunks is the gatekeeper, The plurality of VOIP trunks forming the incoming call group accommodated in the incoming call side PBX in the network are all general trunks, and the function of instructing which trunk in the incoming call group to connect is an external gate concerned. In the case of implementation with a keeper, even if it is not possible to connect to the gatekeeper that is normally used by duplicating the gatekeeper, it is possible to bypass the other gatekeeper and receive on the receiving side trunk VOIP trunk detour method. 5. The VOIP trunk detouring method according to claim 1, wherein by providing information for identifying whether or not there is a detour in the alternative address information, it is possible to select whether detouring is necessary or not. A VOIP trunk detouring method characterized by: