JP5055096B2 - IP telephone system, IP telephone exchange, IP telephone, and call state management method - Google Patents

Description

  The present invention relates to a technique for managing a call state of an IP telephone.

  In an IP telephone system having a plurality of IP telephones and an IP telephone exchange that accommodates these IP telephones, when a call control message cannot be normally transmitted and received between the IP telephone exchange and the IP telephone due to a network failure or the like , The call may not be performed normally.

  FIG. 18 is a sequence diagram for explaining an example of a case where a call control message cannot be normally transmitted and received between an IP telephone exchange and an IP telephone due to a network failure or the like in a conventional IP telephone system. Here, reference numeral 6 denotes an IP telephone exchange (IP-PBX), and reference numerals 7 a to 7 c denote IP telephones (IP-TEL) accommodated in the IP telephone exchange 6.

  The IP telephone 7a is off-hooked to start a call with the IP telephone 7b. When dial information is input, the information is transmitted to the IP telephone exchange 6 (S501). In response to this, the IP telephone exchange 6 transmits a ring tone to the IP telephone 7a and sends an incoming call to the IP telephone 7b (S502).

  The IP telephone 7b receives an incoming call from the IP telephone exchange 6 and outputs a ring tone. When off-hook is performed, off-hook information is transmitted to the IP telephone exchange 6 (S503). In response to this, the IP telephone exchange 6 transmits a call control message requesting “open call path” to each of the IP telephones 7a and 7b (S504).

  When receiving a call control message requesting “open call path” from the IP telephone exchange 6, the IP telephone 7a opens a call path from the IP telephone 7a to the IP telephone 7b. Similarly, when receiving a call control message requesting “open call path” from the IP telephone exchange 6, the IP telephone 7b opens a call path from the IP telephone 7b to the IP telephone 7a. As a result, a two-way call path is established between the IP telephone 7a and the IP telephone 7b (S505).

  Next, when the telephone call is finished and the on-hook is completed, the IP telephone 7a transmits on-hook information to the IP telephone exchange 6 (S506). Upon receiving this, the IP telephone exchange 6 transmits a call control message requesting “close call path” to each of the IP telephones 7a and 7b (S507).

  Here, it is assumed that the call control message requesting “close call path” transmitted from the IP telephone exchange 6 to the IP telephone 7b does not reach the IP telephone 7b due to a network failure or the like (S508).

  The IP telephone 7a receives a call control message requesting “close call path” from the IP telephone exchange 6 and closes the call path from the IP telephone 7a to the IP telephone 7b. On the other hand, since the IP telephone set 7b has not received a call control message requesting “close call path” from the IP telephone exchange 6, the call path from the IP telephone set 7b to the IP telephone set 7a remains open. (S509).

  After that, when the IP telephone 7c is off-hooked to start a call with the IP telephone 7a and dial information is input, the information is transmitted to the IP telephone exchange 6 (S510). In response to this, the IP telephone exchange 6 transmits a ring tone to the IP telephone 7c and sends an incoming call to the IP telephone 7a (S511).

  The IP telephone 7a receives an incoming call from the IP telephone exchange 6 and outputs a ring tone. When off-hook is performed, off-hook information is transmitted to the IP telephone exchange 6 (S512). In response to this, the IP telephone exchange 6 transmits a call control message requesting “open call path” to each of the IP telephones 7c and 7a (S513).

  When receiving a call control message for requesting “open call path” from the IP telephone exchange 6, the IP telephone 7c opens a call path from the IP telephone 7c to the IP telephone 7a. Similarly, when receiving a call control message requesting “open call path” from the IP telephone exchange 6, the IP telephone 7a opens a call path from the IP telephone 7a to the IP telephone 7c. As a result, a two-way call path is established between the IP telephone 7a and the IP telephone 7c (S514).

  However, the call path from the IP telephone 7b to the IP telephone 7a remains open (S515). For this reason, the IP telephone 7a receives the voice packet from the IP telephone 7c and the voice packet from the IP telephone 7b in duplicate, and cannot reproduce the voice normally.

Therefore, in the technique described in Patent Document 1, the IP telephone device retries a predetermined number of times when there is no reception response from the other party due to a network failure or the like. By logging out, the state of the own IP telephone managed by the IP telephone exchange is initialized (paragraph 0249, etc.).
JP 2003-209621 A

  However, in the technique described in Patent Document 1, since the IP telephone logs out from the IP telephone exchange, it is necessary to log in to the IP telephone exchange again so that the IP telephone can be used. Takes time.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to quickly restore the state of an IP telephone when a call control message cannot be normally transmitted and received between the IP telephone exchange and the IP telephone. It is in providing the technique which can be made to do.

  In order to solve the above-described problem, in the present invention, the IP telephone exchange is configured such that when the call state of the IP telephone managed by the IP telephone exchange does not match the actual call state of the IP telephone, A call control message for matching the two is transmitted to the IP telephone or the other party of the IP telephone.

For example, the present invention is an IP telephone system having a plurality of IP telephones and an IP telephone exchange accommodating the plurality of IP telephones,
The IP phone
A state notification means for notifying the IP telephone exchange of a call state of the own IP telephone;
The IP telephone exchange is
When the call state notified from the IP telephone does not match the call state of the IP telephone managed by the IP telephone exchange, the IP managed by the IP telephone or the own IP telephone exchange The telephone call partner has a matching means for transmitting a call control message for matching the call state notified from the IP telephone and the call state of the IP telephone managed by the own IP telephone exchange.

Further, the present invention is an IP telephone system having a plurality of IP telephones and an IP telephone exchange accommodating the plurality of IP telephones,
The IP phone
In accordance with an instruction from the operator, it has a recovery request notifying means for notifying the IP telephone exchange of a call state recovery request message,
The IP telephone exchange is
When the recovery request message is received from the IP telephone, if the own IP telephone exchange manages the other party of the IP telephone, the IP telephone and the other party are requested to open a call path. Send a call control message.

  ADVANTAGE OF THE INVENTION According to this invention, when the call control message cannot be normally transmitted / received between an IP telephone exchange and an IP telephone, the technique which can restore the state of an IP telephone rapidly can be provided.

  Embodiments of the present invention will be described below.

[First embodiment]
FIG. 1 is a schematic configuration diagram of an IP telephone system to which the first embodiment of the present invention is applied.

  As shown in the figure, in the IP telephone system of the present embodiment, a plurality of IP telephones (IP-TEL) 1 and an IP telephone exchange (IP-PBX) 2 are connected via a hub (HUB) 3 and a router (ROUTER) 4. Connected to the IP network 5.

  The IP phone 1 performs call control processing according to a protocol such as SIP (Session Initiation Protocol), establishes a call path with the other party, and performs voice communication processing according to a protocol such as RTP (Realtime Transport Protocol). Then, the call data is transmitted and received with the call partner via this call path.

  FIG. 2 is a schematic configuration diagram of the IP telephone 1.

  As illustrated, the IP telephone 1 includes a network interface unit 101, a man machine (MM) interface unit 102, a call control processing unit 103, a call processing unit 104, and a state notification unit 105.

  The network interface unit 101 is an interface for connecting the own IP telephone 1 to the IP network 5. In the present embodiment, any IP telephone 1 is connected to the IP network 5 via the hub 3 and the router 4.

  The MM interface unit 102 is a man-machine interface including a display unit such as an LCD, a handset unit such as a speaker and a microphone, and an input unit such as an operation panel.

  The call control processing unit 103 performs call control processing according to a protocol such as SIP, and establishes and disconnects a call path with the call partner.

  The call processing unit 104 performs voice communication processing according to a protocol such as RTP. As a result, call data is received from the call partner via the call path established by the call control processing unit 103, demodulated into voice data, and output from the MM interface unit 102. Also, the voice data input to the MM interface unit 102 is modulated into call data, and the call data is transmitted to the call partner via this call path.

  The state notification unit 105 performs a call state notification process for notifying the IP telephone switch 2 of the call state of the own IP telephone 1. FIG. 3A is a diagram schematically showing an example of a format of a call state notification message used by the state notification unit 105 to notify the IP telephone switch 2 of the call state of the own IP telephone 1. As shown in the figure, the call state notification message is, for example, a message type 1051 indicating that it is a call state notification message, the IP phone number 1052 of the own IP phone, a call state 1053 such as on-hook, off-hook, or in-call, and the IP It includes a telephone number 1054, a call partner IP address 1055, a call partner transmission port number 1056, and a call partner reception port number 1057.

  FIG. 4 is a flowchart for explaining the call state notification processing of the IP telephone 1.

  When the own IP phone 1 is off-hooked (YES in S101), the state notification unit 105 detects this via the call control processing unit 103. Then, the current call state of the IP telephone 1 is acquired from the call control processing unit 103 (S102), and a call state notification message indicating the call state is notified to the IP telephone exchange 2 via the network interface unit 101 ( S103). Then, the status notification unit 105 receives a call status notification instruction from the user via the MM interface unit 102 (YES in S104) or a predetermined time T (for example, 15 seconds) from the previous notification of the call status notification message. (YES in S105), the process returns to S102 to acquire the call state of the own IP telephone 1 and notify the IP telephone switch 2 of a call state notification message.

  When the own IP telephone 1 is on-hooked (YES in S106) and a message requesting “close call path” is received from the IP telephone exchange 2 (YES in S107), the state notifying unit 105 includes a call control processing unit. These are detected via 103. Then, the status notification unit 105 returns to S101 and waits for the IP phone 1 to be newly off-hooked.

  Returning to FIG. 1, the description will be continued. The IP telephone exchange 2 accommodates each IP telephone 1 and performs call control processing according to a protocol such as SIP to control establishment and disconnection of a call path between these IP telephones 1. Further, the IP telephone exchange 2 has the IP telephone 1 managed by the IP telephone exchange 2 and the actual call of the IP telephone 1 for each IP telephone 1 accommodated in the IP telephone exchange 2. If the state does not match, matching processing is performed to match the two.

  FIG. 5 is a schematic configuration diagram of the IP telephone exchange 2.

  As illustrated, the IP telephone exchange 2 includes a network interface unit 201, a call control processing unit 202, a call state management unit 203, a call state storage unit 204, and a matching processing unit 205.

  The network interface unit 201 is an interface for connecting the own IP telephone exchange 2 to the IP network 5. In the present embodiment, IP telephone exchange 2 is connected to IP network 5 via hub 3 and router 4.

  The call control processing unit 202 performs call control processing according to a protocol such as SIP, and controls establishment and disconnection of a call path between the IP telephones 1.

  The call state management unit 203 acquires the call state of each IP telephone 1 from the call control processing unit 202 and stores it in the call state storage unit 204.

  FIG. 6 is a diagram schematically showing the registered contents of the call state storage unit 204. As shown in the figure, the call state storage unit 204 stores a table 2040 associated with the IP telephone number of the IP telephone 1 for each IP telephone 1 accommodated in the own IP telephone exchange 2. In the table 2040, a call status record 2041 of the IP telephone 1 corresponding to the table 2040, which is acquired from the call control processing unit 202 by the call status management unit 203, is registered. A record 2041 registers a field 2042 for registering a call state (on-hook, off-hook, busy, etc.), a field 2043 for registering the IP telephone number of the call partner when there is a call partner, and a storage date and time of the record 2041. Field 2044.

  The matching processing unit 205 includes the latest call state stored in the call state storage unit 204 and the latest call state notified from the IP phone 1 for each IP telephone set 1 accommodated in the own IP telephone exchange 2. If they are not consistent with each other, a matching process for matching the two is performed.

  FIG. 7 is a flowchart for explaining the matching process of the IP telephone exchange 2.

  When the matching processing unit 205 receives the call state notification message from the IP telephone 1 via the network interface unit 201 (YES in S201), the matching processing unit 205 determines the open / close state of the call path corresponding to the call state 1053 of the call state notification message. . When the call state 1053 indicates “busy”, the open / close state of the call path is determined as “call path open”, and when the call state 1053 indicates a state other than “busy”, the call path is opened / closed. The state is determined as “call path closed”.

  In addition, the matching processing unit 205 acquires the IP telephone number 1052 of the IP telephone 1 that is the transmission source of the call state notification message from the call state notification message. Then, the latest record 2041 is retrieved from the table 2040 stored in the call state storage unit 204 in association with the IP phone number 1052, and the call corresponding to the call state registered in the field 2042 of this record 2041. The open / closed state of the path is determined by the same determination method as described above based on the call state 1053 of the call state notification message.

  The matching processing unit 205 correlates the open / close state of the call path corresponding to the call state 1053 of the call state notification message and the IP telephone number 1052 of the IP telephone 1 that is the transmission source of the call state notification message. The open / close state of the call path indicated by the call state registered in the field 2042 of the latest record 2041 of the table 2040 stored in 204 is compared (S202).

  If the two match (YES in S203), the process returns to S201 and waits for a new call state notification message from IP phone 1.

  On the other hand, if the two do not match (NO in S203), if the open / close state of the call path indicated by the call state registered in the field 2042 of this latest record 2041 is “call path open” (“call path open” in S204) ), The call control processing unit 202 is caused to transmit a call control message requesting “call path open” to the IP telephone set 1 that has transmitted the call state notification message (S205). On the other hand, if the open / close state of the call path indicated by the call state registered in the field 2042 of the latest record 2041 is “call path closed” (“call path closed” in S204), the call control processing unit 202 is notified of the call state. A call control message requesting “close call path” is transmitted to the IP telephone set 1 that has transmitted the notification message (S206).

  Next, an operation example of the IP telephone system to which the first embodiment of the present invention is applied will be described.

  FIG. 8 is a sequence diagram for explaining an operation example of the IP telephone system to which the first embodiment of the present invention is applied. Here, a case will be described as an example in which IP telephone 1 with IP telephone number “0001” makes a call to IP telephone 1 with IP telephone number “0004”.

  In FIG. 8, reference numeral 21 denotes a call path indicated by the call state 2042 of the latest record 2041 of the table 2040 stored in the call state storage unit 204 of the IP telephone exchange 2 in association with the IP telephone number “0004”. An open / closed state transition (referred to as management 21) is shown. Reference numeral 22 denotes a transition of the call path open / close state (referred to as notification 22) indicated by the call state 1053 of the call state notification message notified from the IP telephone 1 having the IP telephone number “0004” to the IP telephone exchange 2. Yes.

  The IP telephone 1 with the IP telephone number “0001” is off-hooked to start a call with the IP telephone 1 with the IP telephone number “0004”. When dial information is input, the information is transferred to the IP telephone exchange 2. Transmit (S301). Further, the call state notification process is started by using off-hook as a trigger (S301a). As a result, a call state notification message is periodically notified to the IP telephone exchange 2 from the IP telephone 1 having the IP telephone number “0001” (see FIG. 4).

  When the IP telephone exchange 2 receives the off-hook information and the dial information of the IP telephone 1 with the IP telephone number “0004” from the IP telephone 1 with the IP telephone number “0001”, the IP telephone exchange 2 rings the IP telephone 1 with the IP telephone number “0001”. And an incoming call is sent to the IP telephone 1 having the IP telephone number “0004” (S302).

  The IP telephone 1 with the IP telephone number “0004” receives an incoming call from the IP telephone exchange 2 and outputs a ring tone. When off-hook is performed, off-hook information is transmitted to the IP telephone exchange 2 (S303). Further, the call state notification process is started by using off-hook as a trigger (S303a). As a result, a call state notification message is periodically notified to the IP telephone exchange 2 from the IP telephone 1 having the IP telephone number “0004” (see FIG. 4).

  When the IP telephone exchange 2 receives the off-hook information from the IP telephone 1 with the IP telephone number “0004”, the IP telephone exchange 2 sends “call” to the IP telephone 1 with the IP telephone number “0001” and the IP telephone 1 with the IP telephone number “0004”. A call control message requesting “open path” is transmitted (S304). As a result, the management 21 changes from “close call path” to “open call path”.

  When receiving the call control message requesting “open call path” from the IP telephone exchange 2, the IP telephone 1 with the IP telephone number “0001” receives the IP telephone number “0004” from the IP telephone 1 with the IP telephone number “0001”. The call path to the IP telephone 1 is opened. Similarly, when the IP telephone 1 with the IP telephone number “0004” receives a call control message requesting “open call path” from the IP telephone exchange 2, the IP telephone number from the IP telephone 1 with the IP telephone number “0004”. A call path to the IP phone 1 of “0001” is opened. As a result, the notification 22 changes from “close call path” to “open call path”. In addition, a two-way call path is established between the IP telephone 1 with the IP telephone number “0001” and the IP telephone 1 with the IP telephone number “0004” (S305).

  Next, when the telephone call is terminated and on-hook is established, the IP telephone 1 having the IP telephone number “0001” transmits on-hook information to the IP telephone exchange 2 (S306). In response to this, the IP telephone exchange 2 transmits a call control message requesting “close call path” to each of the IP telephone 1 having the IP telephone number “0001” and the IP telephone 1 having the IP telephone number “0004”. (S307). As a result, the management 21 changes from “open call path” to “close call path”.

  Here, a call control message requesting “close call path” transmitted from the IP telephone exchange 2 to the IP telephone 1 having the IP telephone number “0004” is sent to the IP telephone 1 having the IP telephone number “0004” due to a network failure or the like. Is not received (S308).

  The IP telephone 1 with the IP telephone number “0001” receives the call control message requesting “close call path” from the IP telephone exchange 2 and receives the IP telephone number “0004” from the IP telephone 1 with the IP telephone number “0001”. ”Is closed. Thereby, the IP telephone 1 with the IP telephone number “0001” ends the call state notification process (S309a), and stops the notification of the call state notification message to the IP telephone exchange 2.

  On the other hand, since the IP telephone 1 having the IP telephone number “0004” has not received the call control message requesting “close call path” from the IP telephone exchange 2, the IP telephone 1 having the IP telephone number “0004” receives the IP The call path to the IP telephone 1 with the telephone number “0001” is kept open. Further, the IP telephone 1 having the IP telephone number “0004” continues to notify the call state notification message to the IP telephone exchange 2 without ending the call state notification process (S309).

  As a result, a mismatch occurs between the management 21 and the notification 22. Therefore, the IP telephone exchange 2 transmits again a call control message requesting “close call path” to the IP telephone 1 having the IP telephone number “0004” (S310). The IP telephone 1 with the IP telephone number “0004” receives the call control message requesting “close call path” from the IP telephone exchange 2 and receives the IP telephone number “0001” from the IP telephone 1 with the IP telephone number “0004”. ”Is closed. As a result, the notification 22 changes from “call path open” to “call path close”, and the inconsistency between the management 21 and the notification 22 is resolved. The IP telephone 1 with the IP telephone number “0004” ends the call state notification process (S310a), and stops the notification of the call state notification message to the IP telephone exchange 2 (S310).

  FIG. 8 shows the case where the IP telephone switch 2 manages the IP telephone set 2 when the call state of the IP telephone set 1 managed by the IP telephone switch 2 does not match the actual call state of the IP telephone set 1. FIG. 7 shows an example of a sequence in the case where the call state managed for No. 1 indicates “call path closed” and the call state notification message from the IP telephone 1 indicates “call path open”. According to the processing, when the call state managed by the IP telephone exchange 2 for the IP telephone 1 indicates “call path open” and the call state notification message from the IP telephone 1 indicates “call path close” By re-sending a call control message requesting “open call path” to this IP phone 1, the actual call state of this IP phone 1 is changed to P phone exchange. 2 by a transition to match the call state managed.

  The first embodiment of the present invention has been described above.

  In the present embodiment, the IP telephone exchange 2 uses the IP telephone switch 2 when the call state of the IP telephone 1 managed by the IP telephone exchange 2 is not consistent with the actual call state of the IP telephone 1. A call control message for automatically matching the actual call state of the telephone 1 with the call state managed by the own IP telephone exchange is automatically transmitted. For this reason, according to the present embodiment, even if the IP telephone exchange 2 and the IP telephone 1 cannot normally send and receive the call control message, the IP telephone 1 can be normally connected immediately after that. The state of can be recovered quickly.

  In the present embodiment, the IP telephone exchange 2 is managed by its own IP telephone exchange 2 because the call state notification message notified from the accommodated IP telephone 1 indicates “call path open”. When the call state of the IP telephone 1 indicates “call path closed”, a call control message requesting “close call path” is transmitted to the IP telephone 1. For this reason, according to the present embodiment, after this IP telephone 1 ends the call with the other party, a situation occurs in which the call path from this IP telephone 1 to this other party is kept open. Can be prevented.

  Further, in the present embodiment, the IP telephone exchange 2 is managed by the own IP telephone exchange 2 because the call state notification message notified from the accommodated IP telephone 1 indicates “call path closed”. When the call state of the IP telephone 1 indicates “call path open”, a call control message requesting “call path open” is transmitted to the IP telephone 1. For this reason, according to the present embodiment, it is possible to prevent a situation in which a call is continued in a state where a two-way call path is not established, that is, in a state where only one of the call paths is established. be able to.

  In the present embodiment, the IP phone 1 determines the open / close state of the call path based on the call state (on-hook, off-hook, busy, etc.) of the IP phone 1, and this determination is made instead of the call state notification message. A message including the result may be notified to the IP telephone exchange 2.

[Second Embodiment]
In the first embodiment described above, when the call state of the IP telephone 1 managed by the IP telephone switch 2 is not consistent with the actual call state of the IP telephone 1, the IP telephone switch 2 The IP telephone 1 is automatically transmitted with a call control message for matching the actual call state with the call state managed by the IP telephone exchange 2. On the other hand, in the present embodiment, the user is allowed to match the actual call state of the IP telephone 1 being used with the call state managed by the IP telephone exchange 2 or the IP telephone exchange 2. Is selected to match the call state managed by the user with the actual call state, and a call control message corresponding to the selection result is transmitted to the IP telephone set 1 or the call partner of the IP telephone set 1.

  The IP telephone system of the present embodiment is different from the IP telephone system of the first embodiment shown in FIG. 1 in that the following IP telephone 1A and IP telephone are used in place of the IP telephone 1 and the IP telephone exchange 2 described above. That is, the exchange 2A is used.

  FIG. 9 is a schematic configuration diagram of the IP telephone 1A.

  As shown in the figure, the IP telephone 1A of the present embodiment is different from the IP telephone 1 of the first embodiment shown in FIG. 2 in that a call continuation confirmation unit 106 is added. Other configurations are the same as those of the IP telephone 1 according to the first embodiment shown in FIG.

  When the call continuation confirmation unit 106 performs a call continuation confirmation process and receives a call continuation confirmation message from the IP telephone exchange 2A, the call continuation confirmation unit 106 confirms whether or not the user of the IP telephone 1A needs to continue the call and includes the result A continuation necessity message is transmitted to the IP telephone exchange 2A.

  FIG. 3B schematically shows an example of a format of a call continuation confirmation message transmitted to the call continuation confirmation unit 106 by the IP telephone exchange 2A. As shown in the figure, the call continuation confirmation message includes, for example, a message type 1061 indicating that it is a call continuation confirmation message. FIG. 3C is a diagram schematically illustrating an example of a format of a call continuation necessity message transmitted to the IP telephone exchange 2A by the call continuation confirmation unit 106. As illustrated, the call continuation necessity message includes, for example, a message type 1062 indicating a call continuation necessity message and a call continuation necessity 1063.

  FIG. 10 is a flowchart for explaining the call continuation confirmation process of IP phone 1A.

  When the call continuation confirmation unit 106 detects that the IP phone 1A is off-hooked via the call control processing unit 103 (YES in S121), the call continuation confirmation message is sent from the IP telephone exchange 2A via the network interface unit 101. Wait for it to come (S122). Then, if a call continuation confirmation message is received from IP telephone exchange 2A (YES in S122), for example, “Communication quality is unstable. A confirmation message for confirming whether or not to continue the call is output to the MM interface unit 102, such as “Please press the dial key“ 1 ”if not,” (S123).

  Next, the call continuation confirmation unit 106 waits for an instruction from the user regarding whether or not to continue the call (NO in S124, NO in S125). Then, if an instruction for necessity of continuing the call is received from the user via the MM interface unit 102 within a predetermined time t (for example, 30 seconds) (YES in S124), if this instruction content is intended to continue the call ( In S126, “necessary”), a call continuation necessity message including the call continuation “necessary” 1063 is transmitted to the IP telephone exchange 2A via the network interface unit 101 (S127).

  On the other hand, if the content of the instruction does not want to continue the call (“unnecessary” in S126), or if the user does not receive an instruction on whether or not to continue the call within the predetermined time t (NO in S124, YES in S125) ), A call continuation necessity message including the call continuation “unnecessary” 1063 is transmitted to the IP telephone exchange 2A via the network interface unit 101 (S128).

  The call continuation confirmation unit 106 detects that the own IP telephone 1A is on-hooked via the call control processing unit 103 (YES in S129), and requests a “call path close” from the IP telephone exchange 2A. When it is detected that the control message has been received via the call control processing unit 103 (YES in S130), the process returns to S121 and waits for the own IP telephone 1A to be newly off-hooked.

  Next, the IP telephone exchange 2A will be described.

  The IP telephone exchange 2A of the present embodiment is different from the IP telephone exchange 2 of the first embodiment shown in FIG. 5 in that it has the following matching processing section 205A instead of the matching processing section 205 described above. . Other configurations are the same as those of the IP telephone exchange 2 of the first embodiment shown in FIG.

  The matching processing unit 205A, for each IP telephone 1A accommodated in its own IP telephone exchange 2A, the latest call state 2042 stored in the call state storage unit 204 and the latest call notified from the IP telephone 1A If the state does not match, matching processing is performed to match the two.

  FIG. 11 is a flowchart for explaining the matching process of the IP telephone exchange 2A.

  11, S221 to S225 are the same as S201 to S205 of the matching process of the IP telephone exchange 2 shown in FIG. Therefore, only S226 and subsequent steps will be described.

  In S224, the call state registered in the field 2042 of the latest record 2041 of the table 2040 stored in the call state storage unit 204 in association with the IP telephone number 1052 of the IP phone 1A that is the transmission source of the call state notification message is When the call path open / close state shown is “call path closed” (“call path closed” in S204), the matching processing unit 205A continues the call to the IP telephone 1A that is the source of the call state notification message via the network interface unit 201. A confirmation message is transmitted (S226).

  Then, the matching processing unit 205A waits for a call continuation necessity message sent from the caller state notification message source IP telephone 1A (S227). When the received call continuation necessity message includes the call continuation “unnecessary” 1063 (“unnecessary” in S228), the matching processing unit 205A causes the call control processing unit 202 to send the call state notification message source IP telephone 1A. A call control message for requesting “close call path” is transmitted (S229).

  On the other hand, when the call continuation necessity message includes the call continuation “necessary” 1063 (“necessary” in S228), the matching processing unit 205A associates the call state notification message with the IP telephone number 1052 of the source IP telephone 1A. Then, the table 2040 stored in the call state storage unit 204 is referred to, and the IP telephone number of the call partner registered in the field 2043 of the latest record 2041 is specified. Then, the call control processing unit 202 performs call processing for the IP telephone number, and reestablishes a two-way call path between the call state notification message transmission source IP telephone 1A and the other party (S230). ).

  Next, an operation example of the IP telephone system to which the second embodiment of the present invention is applied will be described.

  FIG. 12 is a sequence diagram for explaining an operation example of the IP telephone system to which the second embodiment of the present invention is applied. Here, the case where IP telephone 1A with IP telephone number “0001” makes a call to IP telephone 1A with IP telephone number “0004” will be described as an example.

  In FIG. 12, reference numeral 23 denotes a call path open / close state indicated by the call state of the record 2041 in the table 2040 stored in the call state storage unit 204 of the IP telephone switch 2A in association with the IP telephone number “0004”. Transition (referred to as management 23). Reference numeral 24 denotes a call path open / close state transition (referred to as notification 24) indicated by the call state 1053 of the call state notification message notified from the IP telephone 1A having the IP telephone number “0004” to the IP telephone switch 2A. Yes.

  12, S331 to S339 are the same as S301 to S309 in the operation example of the IP telephone system to which the first embodiment shown in FIG. 8 is applied. Therefore, only S340 and subsequent steps will be described.

  The call control message requesting “close call path” transmitted from the IP telephone exchange 2A to the IP telephone 1A having the IP telephone number “0004” did not reach the IP telephone 1A having the IP telephone number “0004” due to a network failure or the like. As a result, when a mismatch occurs between the management 23 and the notification 24, the IP telephone exchange 2A transmits a call continuation confirmation message to the IP telephone 1A having the IP telephone number “0004” (S340). In response, IP phone 1A with IP phone number “0004” outputs a message for confirming whether or not to continue the call and accepts an instruction from the user. Then, a call continuation necessity message is transmitted to the IP telephone exchange 2A (S341). Here, it is assumed that a call continuation necessity message including call continuation “necessary” 1063 has been transmitted to IP telephone exchange 2A.

  When the IP telephone exchange 2A receives a call continuation necessity notification message including the call continuation “necessary” 1063 from the IP telephone 1A having the IP phone number “0004”, the IP telephone exchange 2A receives the call continuation necessity / non-necessity notification message from The table 2040 associated with the IP telephone number “0004” and stored in the call state storage unit 204 of the IP telephone exchange 2A is referred to, and the IP telephone having the IP telephone number “0004” is retrieved from the field 2043 of the latest record 2041. The IP telephone number “0001” of the call partner of 1A is specified. Then, with the IP telephone 1A having the IP telephone number “0004” as the calling side, the outgoing call processing to the IP telephone 1A having the IP telephone number “0001” is performed.

  That is, the IP telephone exchange 2A transmits a ringing tone to the IP telephone 1A having the IP telephone number “0004” and sends an incoming call to the IP telephone 1A having the IP telephone number “0001” (S342).

  The IP telephone 1A having the IP telephone number “0001” receives an incoming call from the IP telephone exchange 2A and outputs a ring tone. When off-hook is performed, off-hook information is transmitted to the IP telephone exchange 2A (S343). Further, the call state notification process is started by using off-hook as a trigger (S343a). As a result, a call state notification message from the IP telephone 1A having the IP telephone number “0001” is periodically notified to the IP telephone exchange 2A (see FIG. 4).

  Upon receiving off-hook information from the IP telephone 1A having the IP telephone number “0001”, the IP telephone exchange 2A makes a “call” to each of the IP telephone 1A having the IP telephone number “0001” and the IP telephone 1A having the IP telephone number “0004”. A call control message requesting “open path” is transmitted (S344). As a result, the management 23 changes from “call path closed” to “call path open”, and the discrepancy between the management 23 and the notification 24 is resolved.

  When the IP telephone 1A having the IP telephone number “0001” receives a call control message requesting “open call path” from the IP telephone exchange 2A, the IP telephone number “0004” is received from the IP telephone 1A having the IP telephone number “0001”. A call path to the IP telephone 1A is opened. On the other hand, the call path from the IP telephone 1A having the IP telephone number “0004” to the IP telephone 1A having the IP telephone number “0001” remains open. As a result, a two-way call path is re-established between the IP telephone 1A having the IP telephone number “0001” and the IP telephone 1A having the IP telephone number “0004” (S345).

  In FIG. 12, in response to an instruction from the user, a call continuation necessity message including a call continuation “necessary” 1063 is transmitted from the IP telephone 1A having the IP telephone number “0004” to the IP telephone exchange 2A. 11 is shown as an example. According to the matching process of FIG. 11, the call continuation request including the call continuation “unnecessary” 1063 is requested from the IP telephone 1A with the IP phone number “0004” in accordance with the instruction from the user. When the rejection message is transmitted to the IP telephone exchange 2A, the actual telephone call state of the IP telephone 1A is changed to the IP telephone by retransmitting the call control message requesting “close call path” from the IP telephone exchange 2A. Transition is made so as to match the call state managed by the exchange 2A.

  The second embodiment of the present invention has been described above.

  In this embodiment, the user of the IP telephone 1A matches the actual call state with the call state managed by the IP telephone exchange 2A, or the call state managed by the IP telephone exchange 2A is changed to the actual call state. Whether to match the status is selected, and a call control message is transmitted to the IP telephone 1A or the other party of the IP telephone 1A according to the selection result. Therefore, according to the present embodiment, it is possible to prevent a situation that the user does not want to occur. Other effects are the same as those in the first embodiment.

  In this embodiment as well, as in the first embodiment, the IP telephone 1A determines the call path open / closed state based on the call state (on-hook, off-hook, busy, etc.) of the own IP telephone 1A. Instead of the call state notification message, a message including this determination result may be notified to the IP telephone exchange 2A.

[Third embodiment]
In the first and second embodiments described above, the IP telephone exchanges 2 and 2A notify the call status of the IP telephones 1 and 1A managed by the IP telephone exchanges 2 and 2A, and notification from the IP telephones 1 and 1A. It is determined whether or not the actual call state is matched, and if both are not matched, matching processing is performed to match the two. On the other hand, according to the present embodiment, in accordance with an instruction from the IP phone, a bidirectional call path between the IP phone and the call partner of the IP phone is forcibly opened.

  The IP telephone system according to the present embodiment is different from the IP telephone system according to the first embodiment shown in FIG. 1 in that the following IP telephone 1B and IP telephone are used instead of the IP telephone 1 and the IP telephone exchange 2 described above. The exchange 2B.

  FIG. 13 is a schematic diagram of the IP telephone 1B.

  As shown in the figure, the IP phone 1B of the present embodiment is different from the IP phone 1 of the first embodiment shown in FIG. 2 in that a recovery request unit 107 is provided instead of the status notification unit 105. . Other configurations are the same as those of the IP telephone 1 according to the first embodiment shown in FIG.

  The recovery request unit 107 performs a recovery request process for requesting the IP telephone exchange 2B to recover the call path with the other party in accordance with the user instruction received via the MM interface unit 102.

  FIG. 14 is a flowchart for explaining recovery request processing of IP telephone 1B.

  When the recovery request unit 107 receives a recovery instruction from the user, for example, by pressing a recovery button provided on the operation panel of the MM interface unit 102 (YES in S151), whether or not the own IP telephone 1B is off-hooked. Is determined (S152). If an off-hook is detected via the call control processing unit 103 (YES in S152), the recovery request unit 107 requests the IP telephone switch 2B to recover the call path with the other party via the network interface unit 101. A message (recovery request message) is transmitted (S153). On the other hand, if it is not off-hook, that is, if it is on-hook (NO in S152), the recovery instruction from the user is ignored and the process returns to S151.

  FIG. 15 is a schematic diagram of the IP telephone exchange 2B.

  The IP telephone exchange 2B of the present embodiment differs from the IP telephone exchange 2 of the first embodiment shown in FIG. 5 in that a restoration processing unit 206 is provided instead of the matching processing unit 205. Other configurations are the same as those of the IP telephone exchange 2 of the first embodiment shown in FIG.

  The recovery processing unit 206 performs recovery processing for recovering the call path between the IP telephone 1B and the other party of the IP telephone 1B according to the recovery request message received from the IP telephone 1B via the network interface unit 201.

  FIG. 16 is a flowchart for explaining the restoration process of the IP telephone exchange 2B.

  When the recovery processing unit 206 receives the recovery request message via the network interface unit 201 (YES in S251), the recovery processing unit 206 stores the recovery request message in the call state storage unit 204 in association with the IP telephone number of the source IP telephone 1B of the recovery request message. The latest record 2041 is searched from the stored table 2040 (S252), and it is checked whether or not the IP telephone number of the call partner is registered in the field 2043 of this record 2041 (S253).

  If the IP telephone number of the other party is registered (YES in S253), the recovery processing unit 206 notifies the call control processing unit 202 to “call” for the other party and the IP phone 1B that has sent the recovery request message. A call control message requesting “open path” is transmitted (S254). On the other hand, if the IP telephone number of the other party is not registered (NO in S253), the recovery request message is ignored and the process returns to S251.

  Next, an operation example of the IP telephone system to which the third embodiment of the present invention is applied will be described.

  FIG. 17 is a sequence diagram for explaining an operation example of the IP telephone system to which the third embodiment of the present invention is applied. Here, the case where IP telephone 1B with IP telephone number “0001” makes a call to IP telephone 1B with IP telephone number “0004” will be described as an example.

  In FIG. 17, reference numeral 25 denotes a call path opening / closing indicated by the call state 2042 of the record 2041 of the table 2040 stored in the call state storage unit 204 of the IP telephone exchange 2B in association with the IP telephone number “0004”. A state transition (referred to as management 25) is shown. Reference numeral 26 indicates the actual call path open / close state transition (referred to as actual 26) of the IP telephone 1B having the IP telephone number “0004”.

  The IP telephone 1B having the IP telephone number “0001” is off-hooked to start a call with the IP telephone 1B having the IP telephone number “0004”. When dial information is input, the information is transferred to the IP telephone exchange 2B. Transmit (S351).

  When IP telephone exchange 2B receives off-hook information and dial information of IP phone 1B with IP phone number “0004” from IP phone 1B with IP phone number “0001”, ringing tone is sent to IP phone 1B with IP phone number “0001”. And an incoming call is sent to the IP telephone 1B having the IP telephone number “0004” (S352).

  The IP telephone 1B having the IP telephone number “0004” receives an incoming call from the IP telephone exchange 2B and outputs a ring tone. When off-hook is performed, off-hook information is transmitted to the IP telephone exchange 2B (S353).

  When the IP telephone exchange 2B receives off-hook information from the IP telephone 1B having the IP telephone number “0004”, the IP telephone switch 2B makes a “call” to each of the IP telephone 1B having the IP telephone number “0001” and the IP telephone 1B having the IP telephone number “0004”. A call control message requesting “open path” is transmitted (S354). As a result, the management 25 changes from “call path closed” to “call path open”.

  Here, the call control message requesting “open call path” sent from the IP telephone exchange 2B to the IP telephone 1B having the IP telephone number “0004” is sent to the IP telephone 1B having the IP telephone number “0004” due to a network failure or the like. Is not received (S355).

  When the IP telephone 1B having the IP telephone number “0001” receives the call control message requesting “open call path” from the IP telephone exchange 2B, the IP telephone number “0004” is received from the IP telephone 1B having the IP telephone number “0001”. The call path to the IP telephone 1B is opened. On the other hand, since the IP telephone 1B having the IP telephone number “0004” has not received the call control message requesting “open call path” from the IP telephone exchange 2B, the IP telephone 1B having the IP telephone number “0004” receives the IP The call path to the IP telephone 1B with the telephone number “0001” remains closed (S356). As a result, a mismatch occurs between the management 25 and the actual 26.

  Here, it is assumed that the user of the IP telephone 1B having the IP telephone number “0001” notices an abnormality (cannot hear the voice from the other party) and inputs a recovery instruction. In response to this, the IP telephone 1B having the IP telephone number “0001” confirms that the IP telephone 1B is off-hook, and sends a recovery request message to the IP telephone exchange 2B (S357).

  When the IP telephone exchange 2 receives the recovery request message from the IP telephone 1B with the IP telephone number “0001”, the IP telephone exchange 2 associates the IP telephone number “0001” with the latest information from the table 2040 stored in the call state storage unit 204. The record 2041 is searched, and it is confirmed that the IP telephone number “0004” is registered in the field 2043 of the record 2041. Then, a call control message requesting “open call path” is sent again to each of the IP telephone 1B (IP telephone number “0001”) and the IP telephone 1B with the confirmed IP telephone number “0004”. (S358).

  When receiving the call control message requesting “open call path” from the IP telephone exchange 2B, the IP telephone 1B having the IP telephone number “0004” receives the IP telephone number “0001” from the IP telephone 1B having the IP telephone number “0004”. The call path to the IP telephone 1B is opened. On the other hand, the call path from the IP telephone 1B with the IP telephone number “0001” to the IP telephone 1B with the IP telephone number “0004” remains open. As a result, the discrepancy between the management 25 and the actual 26 is resolved, and a two-way communication path is established between the IP telephone 1B having the IP telephone number “0001” and the IP telephone 1B having the IP telephone number “0004”. (S359).

  The third embodiment of the present invention has been described above.

  In the present embodiment, in accordance with the recovery request message from IP telephone 1B, the two-way call path between IP telephone 1B and the other party of IP telephone 1B is forcibly opened. Therefore, according to the present invention, for example, at the time of outgoing call processing, a call control message for requesting “call path open” is lost on the network and does not reach at least one of the IP telephone 1B on the outgoing side and the incoming side, Therefore, it is possible to eliminate the situation so that the call cannot be started normally.

  In addition, this invention is not limited to said embodiment, Many deformation | transformation are possible within the range of the summary. For example, the configuration of each of the IP telephones 1, 1A, 1B and the IP telephone exchanges 2, 2A, 2B is hardware-implemented by an integrated logic IC such as ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array). It may be a thing. Alternatively, in a computer equipped with an auxiliary storage device such as a CPU, memory, HDD, DVD-ROM, and NIC (Network Interface Card), the CPU loads a predetermined program from the auxiliary storage device onto the memory and executes it. It may be realized.

FIG. 1 is a schematic configuration diagram of an IP telephone system to which the first embodiment of the present invention is applied. FIG. 2 is a schematic configuration diagram of the IP telephone 1. FIG. 3A is a diagram schematically showing an example of a format of a call status message notified to the IP telephone exchange 2 by the status notification unit 105. FIG. 3B is a diagram showing a call made by the IP telephone exchange 2A. FIG. 3C is a diagram schematically illustrating an example of a format of a call continuation confirmation message transmitted to the continuation confirmation unit 106. FIG. 3C illustrates a call continuation requirement transmitted to the IP telephone switch 2A by the call continuation confirmation unit 106. It is the figure which represented typically an example of the format of a rejection message. FIG. 4 is a flowchart for explaining the call state notification processing of the IP telephone 1. FIG. 5 is a schematic configuration diagram of the IP telephone exchange 2. FIG. 6 is a diagram schematically showing the registered contents of the call state storage unit 204. FIG. 7 is a flowchart for explaining the matching process of the IP telephone exchange 2. FIG. 8 is a sequence diagram for explaining an operation example of the IP telephone system to which the first embodiment of the present invention is applied. FIG. 9 is a schematic configuration diagram of the IP telephone 1A. FIG. 10 is a flowchart for explaining the call continuation confirmation process of IP phone 1A. FIG. 11 is a flowchart for explaining the matching process of the IP telephone exchange 2A. FIG. 12 is a sequence diagram for explaining an operation example of the IP telephone system to which the second embodiment of the present invention is applied. FIG. 13 is a schematic diagram of the IP telephone 1B. FIG. 14 is a flowchart for explaining recovery request processing of IP telephone 1B. FIG. 15 is a schematic diagram of the IP telephone exchange 2B. FIG. 16 is a flowchart for explaining the restoration process of the IP telephone exchange 2B. FIG. 17 is a sequence diagram for explaining an operation example of the IP telephone system to which the third embodiment of the present invention is applied. FIG. 18 is a sequence diagram for explaining an example of a case where call control messages cannot be normally transmitted / received between an IP telephone exchange and an IP telephone in a conventional IP telephone system due to a network failure or the like.

Explanation of symbols

  1, 1A, 1B: IP telephone, 2, 2A, 2B: IP telephone exchange, 3: hub, 4: router, 5: IP network, 101: network interface unit, 102: MM interface unit, 103: call control processing unit 104: Call processing unit, 105: Status notification unit, 106: Call continuation confirmation unit, 107: Recovery request unit, 201: Network interface unit, 202: Call control processing unit, 203: Call state management unit, 204: Call state Storage unit, 205, 205A: matching processing unit, 206: recovery processing unit

Claims (7)

An IP telephone system having a plurality of IP telephones and an IP telephone exchange accommodating the plurality of IP telephones,
The IP phone
A state notification means for notifying the IP telephone exchange of a call state of the own IP telephone;
The IP telephone exchange is
When the call state notified from the IP telephone does not match the call state of the IP telephone managed by the IP telephone exchange, the IP managed by the IP telephone or the own IP telephone exchange the phone of the other party, have a matching means for transmitting a call control message for matching and call state notified from the IP telephone, the call state of the IP telephone local IP telephone exchange is managed,
The alignment means includes
When the call state notified from the IP telephone is a call path open and the call state of the IP telephone managed by the own IP telephone exchange is a call path close, the IP telephone is requested to close the call path. Send a call control message,
When the call state notified from the IP telephone is a call path closed and the call state of the IP telephone managed by the own IP telephone exchange is a call path open, the IP telephone is requested to open the call path. An IP telephone system characterized by transmitting a call control message . The IP telephone system according to claim 1,
The alignment means includes
When the call state notified from the IP telephone is a call path open, and the call state of the IP telephone managed by the own IP telephone exchange is a call path closed, a call continuation confirmation message is transmitted to the IP telephone. When a call continuation request message is received from the IP telephone as a response to the call continuation confirmation message, a call control message for requesting the call partner of the IP telephone managed by the own IP telephone exchange to open a call path If the call continuation request message is not received, a call control message requesting call path close is sent to the IP telephone. The IP telephone system according to claim 1 ,
The IP phone
In accordance with an instruction from the operator, the IP telephone exchange has a recovery request notification means for notifying the call state recovery request message,
The IP telephone exchange is
When the recovery request message is received from the IP telephone, if the own IP telephone exchange manages the other party of the IP telephone, the IP telephone and the other party are requested to open a call path. An IP telephone system characterized by transmitting a call control message. The IP telephone exchange according to any one of claims 1 to 3 . The IP telephone set according to any one of claims 1 to 3 . An IP telephone call state management method comprising:
The IP telephone is
Notifying the IP telephone exchange accommodating the own IP telephone of the call state of the own IP telephone,
The IP telephone exchange is
When the call state notified from the IP telephone does not match the call state of the IP telephone managed by the IP telephone exchange, the IP managed by the IP telephone or the own IP telephone exchange A call control message for matching the call state notified from the IP phone to the call partner of the phone and the call state of the IP phone managed by the IP telephone switch ;
When the call state notified from the IP telephone is a call path open and the call state of the IP telephone managed by the own IP telephone exchange is a call path close, the IP telephone is requested to close the call path. Send a call control message,
When the call state notified from the IP telephone is a call path closed and the call state of the IP telephone managed by the own IP telephone exchange is a call path open, the IP telephone is requested to open the call path. A call state management method characterized by transmitting a call control message . The call state management method according to claim 6 ,
The IP telephone is
In accordance with the operator's instructions, notify the IP telephone exchange accommodating the own IP telephone of a call state recovery request message,
The IP telephone exchange is
When the recovery request message is received from the IP telephone, if the own IP telephone exchange manages the other party of the IP telephone, the IP telephone and the other party are requested to open a call path. A call state management method characterized by transmitting a call control message.

Images