JP4564640B2 - VoIP Gateway device - Google Patents

VoIP Gateway device Download PDF

Info

Publication number
JP4564640B2
JP4564640B2 JP2000306267A JP2000306267A JP4564640B2 JP 4564640 B2 JP4564640 B2 JP 4564640B2 JP 2000306267 A JP2000306267 A JP 2000306267A JP 2000306267 A JP2000306267 A JP 2000306267A JP 4564640 B2 JP4564640 B2 JP 4564640B2
Authority
JP
Japan
Prior art keywords
gatekeeper
gateway
registration
gateway device
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
JP2000306267A
Other languages
Japanese (ja)
Other versions
JP2002118617A (en
Inventor
栄司 黒澤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Engineering Ltd
Original Assignee
NEC Engineering Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Engineering Ltd filed Critical NEC Engineering Ltd
Priority to JP2000306267A priority Critical patent/JP4564640B2/en
Publication of JP2002118617A publication Critical patent/JP2002118617A/en
Application granted granted Critical
Publication of JP4564640B2 publication Critical patent/JP4564640B2/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Description

【０００１】
【発明の属する技術分野】
本発明は、ＶｏＩＰ（Ｖｏｉｃｅ Ｏｖｅｒ ＩＰ）装置を用いた呼接続制御に関し、特にGatekeeper装置等に障害が発生した場合においてGateway装置間の呼接続を制御する技術に関する。
【０００２】
【従来の技術】
一般に、VoIP Gateway装置を用いた接続Gatekeeper装置に障害が発生した場合は、Gateway装置間の呼の接続を確立する際、図７のような基本構成において、Gateway装置２は、PBX/TEL１より入力された電話番号（局番号＋端末番号）を受信し、電話番号に対応する接続先をGatekeeper装置９に問い合わせする。上記問い合わせは、Gateway装置２および６とGatekeeper装置９との間で、呼の接続要求メッセージ（ARQ-Admission ReQuest)に電話番号を含めて送出することにより、Gateway装置２または６は、Gatekeeper装置９より、呼の接続を要求する。一方、ARQメッセージを受信したGatekeeper装置９は、Gatekeeper装置９の判断により呼の接続許可メッセージ(ACF-Admission Confirm)を返送することにより接続許可を通知し、また接続拒否メッセージ（ARJ-Admission ReJection）を返送することにより接続拒否を通知する。Gatekeeper装置９は、主にネットワーク上の局番号を一括管理するもので、自装置内に電話番号と接続先との検索および変換機能を有しており、接続許可メッセージ（ACF）内に、電話番号から変換した接続先情報をGateway装置に対して通知する。Gateway装置２は、接続先情報を含むGatekeeper装置９からの応答に基づき、Gateway装置６に対して呼接続メッセージを送出し、呼を確立する事ができる。
【０００３】
【発明が解決しようとする課題】
しかしながら、図８のようにGatekeeper装置９またはGateway装置２とGatekeeper装置９との間のネットワークに障害が発生した場合、呼の接続要求が発生すると、接続先問い合わせ（ARQ）に対する応答（ACF）が期待できないため、電話番号から接続先を変換できず、呼の接続を確立することができない。
【０００４】
そこで、本発明の目的を、かかる障害が発生した場合であっても、交換機からの呼接続要求に対してGateway装置間の呼接続を確立することができることとする。
【０００５】
【課題を解決するための手段】
本発明によれば、ＩＰネットワークに接続された交換機と、ＩＰネットワーク上の電話番号に対応する接続先をデータベースとして一括管理するＧａｔｅｋｅｅｐｅｒ装置と、ＩＰネットワークと前記交換機の間に設けられ、前記Ｇａｔｅｋｅｅｐｅｒ装置に対して交換機から受信した電話番号に対応する接続先を問い合わせる複数のＧａｔｅｗａｙ装置とで構成されるネットワークシステムにおいて、
前記Ｇａｔｅｗａｙ装置は、前記Ｇａｔｅｋｅｅｐｅｒ装置が備える前記データベースと同等のデータベースと、周期的に前記Ｇａｔｅｋｅｅｐｅｒ装置に対して自装置を識別できる信号を送信する手段と、
前記自装置を識別できる信号に対するＧａｔｅｋｅｅｐｅｒ装置からの応答信号を受信する手段と、
前記Ｇａｔｅｋｅｅｐｅｒ装置からの応答信号の受信可否により該Ｇａｔｅｋｅｅｐｅｒ装置に自装置が登録されたか否かを登録する状態登録手段と、前記状態登録手段により自装置と前記Ｇａｔｅｋｅｅｐｅｒ装置との間の障害を検知する障害検知手段とを有しており、
前記障害検知手段により障害の発生が検知された後に当該Ｇａｔｅｗａｙ装置に接続される交換機から呼の接続要求を受けた場合には、当該Ｇａｔｅｗａｙ装置の前記データベースを用いて接続先を特定し、当該Ｇａｔｅｗａｙ装置及び接続先Ｇａｔｅｗａｙ装置の状態登録手段を参照して呼の接続処理を実行し呼の確立を行うことを特徴とするＶｏＩＰネットワークシステムを得ることができる。
【０００６】
また、上述の発明においてさらに、前記自装置識別信号を、Ｇａｔｅｋｅｅｐｅｒ装置への自装置情報を登録するためのＲＲＱ（Registration ReQuest）とし、また前記応答信号をＲＣＦ（Registration Confirm）又はＲＲＪ（Registration ReJection）とすることを特徴とするＶｏＩＰネットワークシステムを得ることができる。
【０００７】
【発明の実施の形態】
以下に、本発明の一実施の形態について、図１〜６を用いて説明する。
【０００８】
本発明では、まず図１に示すようにGateway装置２及び６には、Gatekeeper装置９が蓄積する局番号と接続先の変換情報１０と同等の情報１５及び１７を蓄積する。更に、各Gateway装置は、Gatekeeper装置９の障害発生を検知するため、Gatekeeper装置９に対して、周期的に自装置情報を登録するためのＲＲＱ（Registration ReQuest）メッセージを送信する（１１，１２，１３，１４）。なお、本処理に用いているＲＲＱメッセージとは、ITU-T H255.0勧告内で規定されており、Gateway装置とGatekeeper装置との間での登録手順、アドレス検索手順を行うものである。
【０００９】
ＲＲＱメッセージを受信したGatekeeper装置９は、Gateway装置に対して応答（ＲＣＦ-Registration Confirm又はＲＲＪ-Registration ReJection）メッセージ（１２，１４）を返送する。
【００１０】
ＲＲＱメッセージの応答としてＲＣＦメッセージを受信したGateway装置２及び６は、自装置情報のGatekeeper装置９への登録が成功したことを認知すると同時に、Gatekeeper装置９とGatekeeper装置９とGateway装置間のネットワークに異常及び障害が発生していないことを認知し、自装置内にもつ登録状態をい「登録」とする（１６）。
【００１１】
図２にGateway装置内の登録状態判定手順を示す。Gatekeeper装置９への登録処理（Ｓ１）において、自装置の情報をＲＲＱメッセージとして送信する。Gateway装置は、Gatekeeper装置からの登録許可メッセージ（ＲＣＦ）を受信するか否かをＳ２により判別し、ＲＣＦを受信している場合には、処理（Ｓ３）において自装置の登録状態を登録する。一方、登録不許可となるか、Gatekeeper装置からの応答メッセージを受信できない場合は、自装置の登録状態を未登録とする（Ｓ４）。
【００１２】
次に、図３用いて呼接続の手順について説明する。Gateway装置は、まず呼の接続要求があるかを判別する(S1)。呼の接続要求がある場合には、自装置の登録状態を参照し(S2)、状態が”登録”である場合には、Gatekeeper装置に対して接続先を問い合わせる(S4)。一方、状態が”未登録”の場合には、Gateway装置自装置内に蓄積する局番号と接続先との検索および変換情報を用い、接続先を決定する(S3)。そして、決定した接続先に対し、呼接続処理をおこなう(S5)。次に呼接続処理が正常に処理されたか否かを判定し(S6)、正常に接続できた場合には通話処理(S7)を行う。また、呼接続できなかった場合には、呼の接続処理を終了する。
【００１３】
次に図４に、ネットワークに障害が発生した場合に関して説明する。Gatekeeper装置９と各Gateway装置(2,6)間のネットワークに異常および障害(１７)が発生し、Gatekeeper装置９からの応答（RCF/RRJ）メッセージが返送されない場合、各Gateway装置２及び６は、Gatekeeper装置９またはGatekeeper装置９との間のネットワークに異常および障害(１７)が発生していると認識し、自装置内にもつ登録状態(１３，１６)を”未登録”とする。
【００１４】
本発明では、Gateway装置は上記RRQメッセージをGatekeeper装置に対して周期的に送信し、Gatekeeper装置への自装置情報の登録を行うと共に、Gatekeeper装置およびGatekeeper装置との間のネットワークに異常および障害が発生しているか否かを検知することが可能となる。
【００１５】
よって、図４のようにGatekeeper装置またはGatekeeper装置との間のネットワークに異常および障害が発生し、呼の接続に必要な局番号と接続先を変換できない場合、Gateway装置はGatekeeper装置の障害を検知し、呼の接続において自装置内に蓄積する局番号と接続先の変換情報を用い、接続先に対して呼の接続処理を実施し、呼の確立を可能とする。
【００１６】
このようにして、Gatekeeper装置またはGatekeeper装置とGateway装置との間に障害が発生し、呼の確立において、その機能を使用できない場合、Gateway装置内に蓄積する局情報を用い、呼の確立を可能にする。
【００１７】
図５、接続要求するGateway装置とGatekeeper装置との間のネットワークに障害が発生している場合を示す。２は接続要求元のGateway装置、６は接続要求先のGateway装置、９はGatekeeper装置、４は中継ネットワークを示している。また、１０，１４，１６は各装置に蓄積している電話番号と接続先の変換情報を示し、１５，１７は各Gateway装置の登録状態を示している。
【００１８】
図５構成において、Gateway装置２とGatekeeper装置９との間のネットワークに障害が発生しているため、Gateway装置２が周期的に送出する登録メッセージ（RRQ）に対して、Gatekeeper装置９は応答メッセージ（RCF）を送出することができない。従って、Gateway装置２の登録状態(１５)は”未登録”となる。このとき、Gateway装置６とGatekeeper装置９との間のネットワークは正常であるため、Gateway装置６の登録状態は”登録”となる。この場合においてGateway装置２より呼接続要求があると、Gateway装置２は自装置の登録状態が”未登録”であるため、自装置内の登録情報(１４)より、接続先を決定し、接続先をGateway装置６として呼接続処理を行う。
【００１９】
図６は、Gatekeeper装置に障害が発生している場合を示す。図６は、接続要求するGateway装置とGatekeeper装置との間のネットワークに障害が発生した場合の構成を示している。 ２は接続要求元のGateway装置、６は接続要求先のGateway装置、９はGatekeeper装置、４は中継ネットワークを示している。また、１０，１３，１５は各装置に蓄積している電話番号と接続先の変換情報を示し、１４，１６は各Gateway装置の登録状態を示している。
【００２０】
図６の構成において、Gatekeeper装置９に障害が発生しているため、Gateway装置２およびGateway装置６が周期的に送出する登録メッセージ（RRQ）に対して、Gatekeeper装置９は応答メッセージ（RCF）を送出することができない。従って、Gateway装置２とGateway装置６の登録状態(１４，１６)は”未登録”となる。この場合においてGateway装置２より呼接続要求があると、Gateway装置２は自装置の登録状態が”未登録”であるため、自装置内の登録情報(１４)より、接続先を決定し、接続先をGateway装置６として呼接続処理を行う。
【００２１】
【発明の効果】
以上、本発明によれば、Gateway装置２は、Gatekeeper装置またはGatekeeper装置との間のネットワークに障害が発生した場合であっても、自装置内の登録状態を確認することにより、呼接続を行うことが可能となる。
【図面の簡単な説明】
【図１】本発明の一実施の形態を示すネットワーク構成図である。
【図２】Ｇａｔｅｗａｙｓ装置の登録状態を判定する手順を示したフローチャート。
【図３】補発明の一実施の形態における呼接続手順を示すフローチャート。
【図４】本発明を適用したネットワークシステムにおいてネットワーク障害が発生した場合のシステム構成図。
【図５】本発明を適用したネットワークシステムにおいてＧａｔｅｗａｙ装置とＧａｔｅｋｅｅｐｅｒ装置間に障害が発生した場合のシステム構成図。
【図６】本発明を適用したネットワークシステムにおいてＧａｔｅｋｅｅｐｅｒ装置に障害が発生した場合のシステム構成図。
【図７】従来技術のネットワークシステム構成図。
【図８】従来のネットワークシステムに障害が発生した場合のシステム構成図。
【符号の説明】
１、７ 交換機
２，６ Ｇａｔｅｗａｙ装置
４ ＩＰネットワーク
９ Ｇａｔｅｋｅｅｐｅｒ装置
１０、１５，１７ Ｇａｔｅｋｅｅｐｅｒ装置に備える局番号と接続先の変換情報[0001]
BACKGROUND OF THE INVENTION
The present invention relates to call connection control using a VoIP (Voice Over IP) device, and more particularly to a technique for controlling call connection between Gateway devices when a failure occurs in a Gatekeeper device or the like.
[0002]
[Prior art]
In general, when a failure occurs in a connected Gatekeeper device using a VoIP Gateway device, the Gateway device 2 is input from the PBX / TEL 1 in the basic configuration as shown in FIG. The received telephone number (station number + terminal number) is received and the Gatekeeper device 9 is inquired about the connection destination corresponding to the telephone number. The inquiry is sent between the gateway devices 2 and 6 and the gatekeeper device 9 including the telephone number in the call connection request message (ARQ-Admission ReQuest). Then, a call connection is requested. On the other hand, the Gatekeeper device 9 that has received the ARQ message notifies the connection permission by returning a call connection permission message (ACF-Admission Confirm) according to the judgment of the Gatekeeper device 9, and the connection rejection message (ARJ-Admission ReJection). The connection rejection is notified by returning. The Gatekeeper device 9 mainly manages the station numbers on the network collectively. It has a function for searching and converting the telephone number and the connection destination in its own device, and in the connection permission message (ACF) The gateway device is notified of the connection destination information converted from the number. The gateway device 2 can establish a call by sending a call connection message to the gateway device 6 based on the response from the gatekeeper device 9 including the connection destination information.
[0003]
[Problems to be solved by the invention]
However, when a failure occurs in the network between the Gatekeeper device 9 or the Gateway device 2 and the Gatekeeper device 9 as shown in FIG. 8 , when a call connection request is generated, a response (ACF) to the connection destination inquiry (ARQ) is received. Since it cannot be expected, the connection destination cannot be converted from the telephone number, and the call connection cannot be established.
[0004]
Therefore, an object of the present invention is to establish a call connection between Gateway devices in response to a call connection request from an exchange even when such a failure occurs.
[0005]
[Means for Solving the Problems]
According to the present invention, an exchange connected to an IP network, a Gatekeeper device that collectively manages a connection destination corresponding to a telephone number on the IP network as a database, and the Gatekeeper device provided between the IP network and the exchange. In a network system composed of a plurality of Gateway devices that inquire the connection destination corresponding to the telephone number received from the exchange,
The Gateway device has a database equivalent to the database included in the Gatekeeper device and means for periodically transmitting a signal that can identify the device to the Gateway device .
Means for receiving a response signal from a Gatekeeper device with respect to a signal capable of identifying the device;
A state registration unit that registers whether or not the device is registered in the Gatekeeper device based on whether or not a response signal is received from the Gatekeeper device, and a failure between the device and the Gatekeeper device is detected by the state registration device. Fault detection means,
When a call connection request is received from the exchange connected to the Gateway device after the failure detection means detects the occurrence of the failure, the connection destination is identified using the database of the Gateway device, and the Gateway is It is possible to obtain a VoIP network system characterized in that call connection processing is performed by referring to state registration means of the device and the connection destination gateway device to establish a call.
[0006]
Further, in the above-described invention, the device identification signal is an RRQ (Registration ReQuest) for registering the device information to the Gatekeeper device, and the response signal is an RCF (Registration Confirm) or RRJ (Registration ReJection). Thus, a VoIP network system can be obtained.
[0007]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to FIGS.
[0008]
In the present invention, first, as shown in FIG. 1, the gateway devices 2 and 6 store information 15 and 17 equivalent to the station number stored in the Gatekeeper device 9 and the conversion information 10 of the connection destination. Further, each Gateway device periodically transmits an RRQ (Registration ReQuest) message for registering its own device information to the Gatekeeper device 9 in order to detect the occurrence of a failure in the Gatekeeper device 9 (11, 12, 13, 14). Note that the RRQ message used in this process is defined in the ITU-T H255.0 recommendation and performs a registration procedure and an address search procedure between the Gateway device and the Gatekeeper device.
[0009]
Upon receiving the RRQ message, the Gatekeeper device 9 returns a response (RCF-Registration Confirm or RRJ-Registration ReJection) message (12, 14) to the Gateway device.
[0010]
The gateway devices 2 and 6 that have received the RCF message as a response to the RRQ message recognize that the registration of their own device information to the gatekeeper device 9 has been successful, and at the same time, the gateway device 9 and the network between the gatekeeper device 9 and the gateway device. Recognizing that no abnormality or failure has occurred, the registration status of the own apparatus is designated as “registration” (16).
[0011]
FIG. 2 shows a registration status determination procedure in the gateway device. In the registration process (S1 ) to the Gatekeeper device 9, information about the device itself is transmitted as an RRQ message. The gateway device determines whether or not to receive a registration permission message (RCF) from the gatekeeper device in S2, and if receiving the RCF, registers the registration state of the own device in processing (S3). On the other hand, if registration is not permitted or a response message from the Gatekeeper device cannot be received, the registration status of the device itself is unregistered (S4).
[0012]
Next, a call connection procedure will be described with reference to FIG. The Gateway device first determines whether there is a call connection request (S1). When there is a call connection request, the registration status of the own device is referred to (S2), and when the status is “registration”, the connection destination is inquired to the Gatekeeper device (S4). On the other hand, when the status is “unregistered”, the connection destination is determined using the search and conversion information of the station number and the connection destination stored in the gateway device itself (S3). Then, call connection processing is performed for the determined connection destination (S5). Next, it is determined whether or not the call connection process is normally processed (S6). If the call connection process is normally connected, a call process (S7) is performed. If the call connection cannot be established, the call connection process is terminated.
[0013]
Next, a case where a failure occurs in the network will be described with reference to FIG. When an abnormality or failure (17) occurs in the network between the Gatekeeper device 9 and each Gateway device (2, 6), and the response (RCF / RRJ) message from the Gatekeeper device 9 is not returned, each Gateway device 2 and 6 Then, it is recognized that an abnormality and a failure (17) have occurred in the Gatekeeper device 9 or the network with the Gatekeeper device 9, and the registration status (13, 16) in the own device is set to “unregistered”.
[0014]
In the present invention, the Gateway device periodically transmits the RRQ message to the Gatekeeper device, registers its own device information with the Gatekeeper device, and there is an abnormality or failure in the network between the Gatekeeper device and the Gatekeeper device. It is possible to detect whether or not it has occurred.
[0015]
Therefore, as shown in Fig. 4, when an abnormality or failure occurs in the Gatekeeper device or the network between the Gatekeeper device and the station number and connection destination required for call connection cannot be converted, the Gateway device detects the failure of the Gatekeeper device. Then, by using the station number and connection destination conversion information stored in the own apparatus in connection of the call, call connection processing is performed on the connection destination, thereby enabling the call to be established.
[0016]
In this way, if a failure occurs between the Gatekeeper device or the Gatekeeper device and the Gateway device, and the function cannot be used in establishing a call, the call can be established using the station information stored in the Gateway device. To.
[0017]
FIG. 5 shows a case where a failure has occurred in the network between the Gateway device that requests connection and the Gatekeeper device. Reference numeral 2 denotes a connection request source Gateway apparatus, 6 denotes a connection request destination Gateway apparatus, 9 denotes a Gatekeeper apparatus, and 4 denotes a relay network. Further, 10, 14, and 16 indicate telephone number and connection destination conversion information stored in each device, and 15 and 17 indicate the registration status of each Gateway device.
[0018]
In the configuration of FIG. 5, since a failure has occurred in the network between the Gateway device 2 and the Gatekeeper device 9, the Gatekeeper device 9 responds to a registration message (RRQ) periodically sent by the Gateway device 2. (RCF) cannot be sent. Accordingly, the registration state (15) of the gateway device 2 is “unregistered”. At this time, since the network between the gateway device 6 and the gatekeeper device 9 is normal, the registration state of the gateway device 6 is “registered”. In this case, if there is a call connection request from the gateway device 2, the gateway device 2 determines the connection destination from the registration information (14) in the own device because the registration status of the own device is “unregistered”. Call connection processing is performed with the gateway device 6 as the destination.
[0019]
FIG. 6 shows a case where a failure has occurred in the Gatekeeper device. FIG. 6 shows a configuration when a failure occurs in the network between the Gateway device and the Gatekeeper device that request connection. Reference numeral 2 denotes a connection request source Gateway apparatus, 6 denotes a connection request destination Gateway apparatus, 9 denotes a Gatekeeper apparatus, and 4 denotes a relay network. 10, 13 and 15 indicate telephone number and connection destination conversion information stored in each device, and 14 and 16 indicate the registration status of each Gateway device.
[0020]
In the configuration of FIG. 6, since a failure has occurred in the Gatekeeper device 9, the Gatekeeper device 9 sends a response message (RCF) to the registration message (RRQ) periodically transmitted by the Gateway device 2 and the Gateway device 6. It cannot be sent out. Therefore, the registration state (14, 16) of the gateway device 2 and the gateway device 6 is “unregistered”. In this case, if there is a call connection request from the gateway device 2, the gateway device 2 determines the connection destination from the registration information (14) in the own device because the registration status of the own device is “unregistered”. Call connection processing is performed with the gateway device 6 as the destination.
[0021]
【The invention's effect】
As described above, according to the present invention, the gateway device 2 performs call connection by checking the registration state in the own device even when a failure occurs in the gatekeeper device or a network with the gatekeeper device. It becomes possible.
[Brief description of the drawings]
FIG. 1 is a network configuration diagram showing an embodiment of the present invention.
FIG. 2 is a flowchart showing a procedure for determining a registration state of the Gateways apparatus.
FIG. 3 is a flowchart showing a call connection procedure according to the embodiment of the supplementary invention.
FIG. 4 is a system configuration diagram when a network failure occurs in a network system to which the present invention is applied.
FIG. 5 is a system configuration diagram when a failure occurs between a Gateway device and a Gatekeeper device in a network system to which the present invention is applied.
FIG. 6 is a system configuration diagram when a failure occurs in the Gatekeeper device in the network system to which the present invention is applied.
FIG. 7 is a configuration diagram of a conventional network system.
FIG. 8 is a system configuration diagram when a failure occurs in a conventional network system.
[Explanation of symbols]
1, 7 Exchange 2, 6 Gateway device 4 IP network 9 Gatekeeper device 10, 15, 17 Conversion information of station number and connection destination provided in Gatekeeper device

Claims (2)

ＩＰネットワークに接続された交換機と、ＩＰネットワーク上の電話番号に対応する接続先をデータベースとして一括管理するＧａｔｅｋｅｅｐｅｒ装置と、ＩＰネットワークと前記交換機の間に設けられ、前記Ｇａｔｅｋｅｅｐｅｒ装置に対して交換機から受信した電話番号に対応する接続先を問い合わせる複数のＧａｔｅｗａｙ装置とで構成されるネットワークシステムにおいて、
前記Ｇａｔｅｗａｙ装置は、前記Ｇａｔｅｋｅｅｐｅｒ装置が備える前記データベースと同等のデータベースと、周期的に前記Ｇａｔｅｋｅｅｐｅｒ装置に対して自装置を識別できる信号を送信する手段と、
前記自装置を識別できる信号に対するＧａｔｅｋｅｅｐｅｒ装置からの応答信号を受信する手段と、
前記Ｇａｔｅｋｅｅｐｅｒ装置からの応答信号の受信可否により該Ｇａｔｅｋｅｅｐｅｒ装置に自装置が登録されたか否かを登録する状態登録手段と、前記状態登録手段により自装置と前記Ｇａｔｅｋｅｅｐｅｒ装置との間の障害を検知する障害検知手段とを有しており、
前記障害検知手段により障害の発生が検知された後に当該Ｇａｔｅｗａｙ装置に接続される交換機から呼の接続要求を受けた場合には、当該Ｇａｔｅｗａｙ装置の前記データベースを用いて接続先を特定し、当該Ｇａｔｅｗａｙ装置及び接続先Ｇａｔｅｗａｙ装置の状態登録手段を参照して呼の接続処理を実行し呼の確立を行うことを特徴とするＶｏＩＰネットワークシステム。An exchange connected to the IP network, a Gatekeeper device that collectively manages a connection destination corresponding to a telephone number on the IP network as a database, and provided between the IP network and the exchange, and received from the exchange to the Gatekeeper device In a network system composed of a plurality of Gateway devices that inquire about the connection destination corresponding to the telephone number,
The Gateway device has a database equivalent to the database included in the Gatekeeper device and means for periodically transmitting a signal that can identify the device to the Gateway device .
Means for receiving a response signal from a Gatekeeper device with respect to a signal capable of identifying the device;
A state registration unit that registers whether or not the device is registered in the Gatekeeper device based on whether or not a response signal is received from the Gatekeeper device, and a failure between the device and the Gatekeeper device is detected by the state registration device. Fault detection means,
When a call connection request is received from the exchange connected to the Gateway device after the failure detection means detects the occurrence of the failure, the connection destination is identified using the database of the Gateway device, and the Gateway is A VoIP network system characterized in that call connection processing is performed by referring to state registration means of a device and a connection destination gateway device to establish a call. 前記自装置識別信号を、Ｇａｔｅｋｅｅｐｅｒ装置への自装置情報を登録するためのＲＲＱ（Registration ReQuest）とし、また前記応答信号をＲＣＦ（Registration Confirm）又はＲＲＪ（Registration ReJection）とすることを特徴とする請求項１記載のＶｏＩＰネットワークシステム。The self-device identification signal is RRQ (Registration ReQuest) for registering self-device information to the Gatekeeper device, and the response signal is RCF (Registration Confirm) or RRJ (Registration ReJection). Item 2. The VoIP network system according to Item 1.
JP2000306267A 2000-10-05 2000-10-05 VoIP Gateway device Expired - Fee Related JP4564640B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2000306267A JP4564640B2 (en) 2000-10-05 2000-10-05 VoIP Gateway device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2000306267A JP4564640B2 (en) 2000-10-05 2000-10-05 VoIP Gateway device

Publications (2)

Publication Number Publication Date
JP2002118617A JP2002118617A (en) 2002-04-19
JP4564640B2 true JP4564640B2 (en) 2010-10-20

Family

ID=18786989

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2000306267A Expired - Fee Related JP4564640B2 (en) 2000-10-05 2000-10-05 VoIP Gateway device

Country Status (1)

Country Link
JP (1) JP4564640B2 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002237907A (en) * 2001-02-09 2002-08-23 Yoji Takeuchi Internet ip telephone communication system enabling voice call between two parties through use of exclusive telephone set over the internet, and exclusive telephone set for internet ip telephone communication system, management method for ip address information used for basic data of internet ip telephone communication function, automatic reception transmission method for reception/transmission between the internet ip telephone communication exclusive set and general telephone, and computer-readable recording medium for recording internet ip telephone communication program

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000209282A (en) * 1999-01-13 2000-07-28 Fujitsu Ltd Voice gateway and its path selection method

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3623669B2 (en) * 1998-09-29 2005-02-23 日本電気エンジニアリング株式会社 INTERNET CONNECTION SYSTEM, GATEWAY DEVICE, INTERGATEWAY CONNECTION METHOD, AND RECORDING MEDIUM
JP3689580B2 (en) * 1999-01-29 2005-08-31 株式会社日立製作所 Internet telephone connection method, bandwidth management device, and gatekeeper device
JP2000244581A (en) * 1999-02-19 2000-09-08 Fujitsu Ltd Internet telephony void system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000209282A (en) * 1999-01-13 2000-07-28 Fujitsu Ltd Voice gateway and its path selection method

Also Published As

Publication number Publication date
JP2002118617A (en) 2002-04-19

Similar Documents

Publication Publication Date Title
US7843903B2 (en) Methods, systems, and computer program products for emergency 911 (E911) registration assistance for subscribers using portable internet protocol (IP) communications devices
US7260084B2 (en) Method for establishing a connection from a terminal of a communication network to a network-external connection destination, and associated apparatus and network
US20050180317A1 (en) Server backup device
US20030028398A1 (en) Method for transmitting jobs between computer systems, and computer system and program therefor
JP5235292B2 (en) Computer system, method for migrating to backup system, program for migrating to backup system, monitoring device, terminal device, and backup system
US8565125B2 (en) Services based two way voice service recording and logging
AU2005200060A1 (en) Managing routing path of voice over internet protocol (VoIP) system
JP2006157612A (en) Network telephone system, and server apparatus and telephone terminal for the system
CN101355559A (en) Interface apparatus, main apparatus and control method for use in the interface apparatus
US7545798B2 (en) Communication system for controlling a call portion
JP4576115B2 (en) VoIP gateway device and method for controlling call arrival and departure in VoIP gateway device
US8054955B2 (en) Telephone system, associated exchange, and transmission control method
US20070206745A1 (en) Communication system and transfer control method together with telphone device, communication device, and program used for same
JP4564640B2 (en) VoIP Gateway device
JP7064132B2 (en) Fault monitoring system and fault monitoring method
JP4228318B2 (en) Network facsimile machine and network factory system
JP4541333B2 (en) Terminal device, system, method, and program
JP2007124036A (en) Server apparatus
JP5214368B2 (en) Communication monitoring system and communication monitoring method
JP2009033453A (en) Telephone exchange apparatus and control method used in the telephone exchange apparatus
JP4757719B2 (en) Network system, IP telephone terminal, and network device switching method used therefor
US20030081593A1 (en) Method for charging internet phone network
JP2008236470A (en) Ip telephone terminal and ip telephone system
JP2008306375A (en) Voip-gw apparatus
JP4256277B2 (en) VoIP gateway device and position information transmission method

Legal Events

Date Code Title Description
A711 Notification of change in applicant

Free format text: JAPANESE INTERMEDIATE CODE: A712

Effective date: 20030428

RD03 Notification of appointment of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7423

Effective date: 20030428

RD01 Notification of change of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7421

Effective date: 20050329

RD01 Notification of change of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7421

Effective date: 20070124

A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20070911

RD01 Notification of change of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7421

Effective date: 20080618

RD01 Notification of change of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7421

Effective date: 20090515

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20100216

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20100323

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20100524

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20100720

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20100802

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20130806

Year of fee payment: 3

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

LAPS Cancellation because of no payment of annual fees