KR100374334B1 - METHOD FOR SUPPORTING VoIP TELECOMMUNICATION OF NON-RAS ENDPOINT IN GATEKEEPER - Google Patents

Abstract

The present invention relates to a procedure and an implementation method for enabling voiceover IP calls within a gatekeeper zone between endpoints that are not registered with the gatekeeper and do not support the gatekeeper's basic signaling protocol. A method for supporting a voice over IP call to a non-ALS endpoint in a gatekeeper control area configured by connecting a server with a keeper and a plurality of endpoints, the registration information of the plurality of non-ALS endpoints A step of setting a forced online flag in the terminal, a step of checking the forced online flag value of the corresponding non-RS endpoint to which the call is to be made, and the forced online information of the corresponding non-RS endpoint If set to normal, In the same manner as the locked endpoint, the online registration of the endpoint is performed, and if the forced online information of the endpoint is set to 'no', the non-ALS endpoint does not allow voiceover IP call. And loading the registration information of the corresponding non-ALS endpoint into the gatekeeper's memory, thereby providing a voice over IP call support method for the non-ALS endpoint in the gatekeeper. .

Description

METHOOD FOR SUPPORTING VoIP TELECOMMUNICATION OF NON-RAS ENDPOINT IN GATEKEEPER}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a GateKeeper, and in particular, Voice over IP (VoIP) between endpoints that do not support RAS (Registration / Admission / Status), which is the basic signaling protocol of the gatekeeper. Internet Protocol) is a method of enabling a call within a gatekeeper zone.

Gatekeeper is one of the H.323 entities defined in the H.323 protocol, which is the multimedia communication standard of ITU-T (International Telecommunication Union-Telecommunication), and is a packet-based network (IP-based network). H.323 endpoints (eg, Gateway, Terminal, Multipoint Control Unit, etc.) are grouped into a control area defined as Zone to control, manage, and register. It is equipment.

Typically, the gatekeeper's main functions are address translation (translating alias names or destination numbers into network addresses (IP addresses)), call admission (RAS); gates in H.323. Protocols related to the keeper) and Bandwidth Control (Bandwidth Control, which allocates bandwidth, which is a limited resource of the network, to each endpoint and checks whether the limit is reached), and Call Control (Call Control) The ability to connect / disconnect calls between endpoints, all done in the middle of the gatekeeper), and additional maintenance features such as billing and statistics.

There is one gatekeeper in the zone, one control area for integrated control, management, and registration of H.323 endpoints in a packet-based network (IP-based network), and one or more H.323 endpoints. It consists of In addition, a plurality of gatekeepers may be gathered to form a multi-zone and have another gatekeeper for controlling the multi-zone.

Gatekeeper's basic signaling protocol, RAS, is a protocol that implements the basic interface between gatekeepers and endpoints such as terminals, gateways, and MCUs. In RAS, the gatekeeper is a server and the endpoints are clients. In other words, RAS is an essential element and underlying protocol for the gatekeeper, the server, to manage, control, and monitor the status of the client endpoints.

In RAS (Registration / Admission / Status), Registration is the process of registering its presence as a client with a gatekeeper whose endpoint is a server. Admission is the process by which the gatekeeper checks the endpoint for compliance with the rules of H.323 and the corresponding zone, and grants access to the VoIP network. Here, access to the VoIP network means the initial setup process of the VoIP call. In addition, H.323's rule is to check whether the Alias Name, which is the endpoint's Registration Identity, is duplicated with other endpoints, and the zone's rule is to check if the endpoint is registered with the gatekeeper.

The status is that the endpoint periodically reports its information and current status to the gatekeeper so that the gatekeeper gets the information it needs to operate and control the endpoint. do.

As mentioned above, RAS is a very important and underlying protocol for VoIP calls and gatekeepers. However, many of the conventional VoIP equipments are gateways and IP terminals that do not implement the RAS interface, overlooking the importance of the gatekeeper.

Therefore, in the non-RAS endpoints existing in the current VoIP network, there is a problem that the conventional gatekeeper does not support VoIP calls between non-RAS endpoints.

Accordingly, an object of the present invention is to provide a service for a non-RAS endpoint that does not support RAS in the gatekeeper, thereby supporting a free VoIP call service between the endpoint that supports RAS and the endpoint that does not support RAS To provide.

In accordance with the above object, the present invention, in the gatekeeper control VoIP network zone where the gatekeeper is installed, and the various endpoints are connected, the Force-Online flag (Flag) in the registration information of each non-RAS endpoint ), The process of checking the forced online flag value of the non-RAS endpoint to communicate with, and the forced RAS protocol if the forced online information of the non-RAS endpoint is set to 'Yes'. If the online registration process is the same as the endpoint registered by the terminal and the forced online information of the corresponding non-RAS endpoint is set to 'No', the non-RAS endpoint does not operate by the normal RS protocol. Therefore, the process of not allowing voice over IP calls, and the registration information of the corresponding non-RAS endpoint to the gatekeeper's memory Characterized in that the loading process.

1 is a block diagram showing a voice over IP network configuration having a gatekeeper zone to which the present invention is applied;

2 illustrates direct voiceover IP call signaling from an LA endpoint to a non-LA endpoint via a gatekeeper according to the present invention;

3 is a diagram illustrating routed voice over IP call signaling from an LA endpoint to a non-AL endpoint via a gatekeeper according to the present invention;

4 illustrates direct voiceover IP call signaling from a non-ALS endpoint to an LA endpoint via a gatekeeper according to the present invention;

5 is a diagram illustrating routed voice over IP call signaling from a non-ALS endpoint to an LA endpoint via a gatekeeper according to the present invention;

6 illustrates a routing table in a gatekeeper according to the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the reference numerals to the components of the accompanying drawings, it should be noted that the same reference numerals have the same reference numerals as much as possible even if displayed on different drawings. Also in the following description and in the accompanying drawings, numerous specific details are set forth in order to provide a more thorough understanding of the present invention. It will be apparent to those skilled in the art that the present invention may be practiced without these specific details. And a detailed description of known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

FIG. 1 is a block diagram showing a voice over IP network configuration having a gatekeeper zone to which the present invention is applied. Referring to FIG. 1, the overall configuration of the present invention will be described.

As shown in FIG. 1, the gatekeeper 26 is a standalone IP terminal 10, which is a variety of endpoints connected to the Internet / Intranet 18, via a gatekeeper controlled VoIP network (zone) 20, remote operation. Stations 12, gateways 16 and other IP gateways 14 are connected and directly connected to gateways 22, 24, 28 via a gatekeeper controlled VoIP network (zone) 20.

6 illustrates a routing table in a gatekeeper according to the present invention. An exemplary embodiment of the present invention will be briefly described with reference to FIG. 6 as follows.

If any endpoint attempts to make a call from 'Busan' to '02 -123-4567 ', the endpoint is' Seoul' which is the destination from access code '02' as shown in the routing table of FIG. Connect to the gateway specified in IP table index '8' to be routed to the gateway installed locally. Area code '02', which is the destination access code of the endpoint, is cut off, and the gateway calls the number '123-4567' to get on the Public Switched Telecommunications / Telephone Network (PSTN). In other words, it is necessary to use an IP network between the gateway in Busan and the gateway in Seoul, and use the PSTN only from the gateway in Seoul to the endpoint.

On the other hand, when attempting to make a call to the telephone number '062-888-1234' from the endpoint of 'Seoul', the endpoint is the 'Gwangju' destination from the access code '062' as shown in the routing table of FIG. Attempt to connect to the gateway specified in IP table index '1' to be routed to the local gateway. However, as shown in FIG. 6, since the 'Gwangju' area is a non-gateway installation area, the gatekeeper 26 routes the call to a gateway installed in the vicinity of Daejeon. Then, in Daejeon, using PSTN, try to make a long distance call to '062-888-1234'. Therefore, the gateways of Seoul and Daejeon use IP networks, and the non-RAS endpoints that cannot support RAS by using PSTN from the gateway of Daejeon to the endpoints of Gwangju area. VoIP call service in gatekeeper is also possible.

A VoIP call support method for a non-RAS endpoint in a gatekeeper according to the present invention will be described in detail with reference to FIGS.

First, in the present invention, 'direct call signaling' is a 'set / call progress /' after RAS signaling of ARQ (Acknowledgment Request) and ACF (Acknowledgment) / ARJ (Acknowledgment) between the call transmitting endpoint and the gatekeeper. A series of call setup signaling, consisting of 'alarm / connection', represents the VoIP call procedure when not passing through the gatekeeper. On the other hand, if only the call receiving end point supports RAS, after call establishment signaling is performed in the 'setup / call progress' process, ARQ (acknowledge request) and ACF (acknowledge confirmation) between the call receiving end point and the gatekeeper are performed. RAS signaling of / ARJ is rejected, and call setup signaling 'alarm / connection' is performed without going through gatekeeper.

In the present invention, 'routed call signaling' is defined after RAS signaling of ARQ (Acknowledgment Request) and ACF (Acknowledgment Confirmation) / ARJ (Acknowledgment Rejection) between the call originating endpoint and the gatekeeper supporting RAS. A series of call setup signaling consisting of setup / call progress / alarm / connection indicates a VoIP call procedure when passing through a gatekeeper. On the other hand, if only the call receiving end point supports RAS, after call establishment signaling is performed in the 'setup / call progress' process, ARQ (acknowledge request) and ACF (acknowledge confirmation) between the call receiving end point and the gatekeeper are performed. RAS signaling of / ARJ (rejection of approval) is performed, and call setup signaling 'alarm / connection' process is performed.

For reference, if both call originating endpoint and call receiving endpoint do not support RAS, the gatekeeper can be placed in the middle because each endpoint needs to know each other's IP address and alias so that VoIP calls can be made. It should be understood that there is no, and are not the subject of discussion of the present invention. In addition, in order to facilitate a clear description and understanding of the present invention, in the drawings of the present invention, the RAS message is shown in bold solid line and the call signaling message is shown in thin solid line.

2 is a diagram illustrating direct voiceover IP call signaling from an LA endpoint to a non-LA endpoint via a gatekeeper according to the present invention.

First, referring to FIG. 2, VoIP call signaling without passing through the gatekeeper 1 150 between the call originating endpoint 1 100 supporting RAS and the call receiving endpoint 2 200 not supporting RAS will be described. do.

As a first process, endpoint 1 (100) transmits an ARQ (call authorization request) 102 signal to gatekeeper 1 150 for a VoIP call with endpoint 2 200 (1). In response, gatekeeper 1 150 transmits signal ACF (call acknowledgment) or ARJ (call rejection) 104 to endpoint 1 (100). The endpoint 1 (100) receiving this then sends a SETUP (106) signal to the endpoint 2 (200) (3), which then calls CALL PROCEEDING from the endpoint 2 (200) 108 ), And (4) the ALERTING (alarm) 110 signal (5) and CONNECT (112) signal (6).

Meanwhile, FIG. 3 is a diagram illustrating routed voice over IP call signaling from an RS endpoint through a gatekeeper to a non-RS endpoint according to the present invention. Unlike FIG. 2, the gatekeeper 1 (150) is shown. VoIP call signaling is performed through

4 is a diagram illustrating direct voice over IP call signaling from a non-ALS endpoint to an LA endpoint via a gatekeeper according to the present invention.

First, referring to FIG. 4, VoIP call signaling without passing through gatekeeper 1 450 between a call originating endpoint 1 400 that does not support RAS and a call receiving endpoint 2 500 that supports RAS will be described. do.

As a first process, endpoint 1 (400) sends a SETUP (402) signal to endpoint 2 (500). In response, endpoint 2 500 transmits signal CALL PROCEEDING 404 to endpoint 1 400 (2). And the call receiving end point 2 (500) supporting the RAS transmits an ARQ (call approval request) 406 signal to the gatekeeper 1 (450) (3), in response to the gatekeeper 1 (450) The ACF (call rejection) or ARJ (call rejection) 408 signal is transmitted (40). Upon receiving a response to the call acknowledgment from gatekeeper 1 450, endpoint 2 500 transmits an ALERTING 410 signal (5) and a CONNECT (412) signal (6). ).

FIG. 5 is a diagram illustrating routed voice over IP call signaling from a non-ALS endpoint to an RS endpoint through a gatekeeper according to the present invention. Unlike FIG. 4, the gatekeeper 1 450 is illustrated. VoIP call signaling is performed through

Next, if only the source endpoint is non-RAS and the destination endpoint is RAS, if the source endpoint is a gateway and a personal computer terminal, and if the destination endpoint is a gateway and a netmeeting PC, respectively Is divided into a case of passing through a gatekeeper and a case of not. And the VoIP call support method procedure according to the present invention will be described with reference to the routing table shown in FIG.

In addition, if the source endpoint is RAS and only the destination endpoint is non-RAS, then the gateway to the gateway, the NetMeeting PC to the gateway, the NetMeeting PC to the NetMeeting PC, and the Gateway to the NetMeeting PC are passed through the gatekeeper. In this case and otherwise, the VoIP call support method according to the present invention will be described with reference to FIG. 6.

First, if only the originating endpoint is non-RAS and the destination endpoint is RAS, and if the gateway attempts to make a VoIP call to the gateway through the gatekeeper, in the gatekeeper options of the originating gateway, remove the GateKeeper_Connection field. After disabling, try to connect the call through the gatekeeper (1). At this time, the gateway side sets the IP of the corresponding access code in the routing table as the gatekeeper and sets the corresponding Access_Code_Delete value to 'FALSE'. In the gatekeeper stage, the IP of the corresponding access code in the routing table is set as the destination gateway, and the corresponding Access_Code_Delete value is cut by Del_Length. Then, the destination gateway normally enables the GateKeeper_Connection field (2).

Secondly, if the gateway attempts to make a VoIP call to the gateway without going through the gatekeeper, try disabling the GateKeeper_Connection field in the Gatekeeper option of the originating gateway and then attempting to make a call without going through the gatekeeper ( One). At this time, the gateway stage sets the IP of the corresponding access code of the routing table as the destination gateway and cuts the corresponding access code. The gatekeeper stage accepts the destination gateway without having to set the IP of the corresponding access code in the routing table as the destination gateway. Then, the destination gateway normally enables the GateKeeper_Connection field.

Thirdly, when attempting to make a VoIP call from the PC to the gateway through the gatekeeper, the gateway IP is gated by calling the gateway using 'gateway' rather than 'using the gatekeeper when calling'. After setting to the keeper's IP, try to connect the call through the gatekeeper. At this time, the access code and IP address of the destination gateway must be registered in the routing table of the gatekeeper in advance, and the corresponding Access_Code_Delete must be cut by Del_Length. Then, the destination gateway normally enables the GateKeeper_Connection field.

Fourth, if you are trying to make a VoIP call from your PC to your PC without going through the gatekeeper, use the gateway to call the gateway IP instead of using the gatekeeper to call the originating NetMeeting PC. After setting the IP of the destination NetMeeting PC, try to connect the call without using the gatekeeper (1). At this time, the destination NetMeeting PC normally sets the 'use gatekeeper when calling' and calls the alias (Alias) as the destination number. Therefore, the gatekeeper only needs to approve the destination without converting the destination alias to IP.

Fifth, when attempting to make a VoIP call from the gateway to the NetMeeting PC through the gatekeeper, in the gatekeeper option of the source gateway, attempt to connect the call through the gatekeeper after disabling the GateKeeper_Connection field. . At this time, the gateway end inputs the prefix of the corresponding NetMeeting PC in the routing table in the form of an access code, and sets the matching IP as the gatekeeper. The Access_Code_Delete value is set to 'FALSE'. The gatekeeper stage checks whether the destination NetMeeting PC is registered online in the endpoint registration information screen (1), and normally sets the NetMeeting PC to 'use gatekeeper when calling'. Then, the alias of the NetMeeting PC is called with the destination number (2).

Sixth, when attempting to make a VoIP call to the NetMeeting PC directly from the gateway, rather than through the gatekeeper, in the Gatekeeper option of the source gateway, connect the call without a gatekeeper after disabling the GateKeeper_Connection field. Try. At this time, the gateway end inputs the prefix of the corresponding NetMeeting PC in the routing table in the form of an access code, and sets the matching IP as the destination NetMeeting PC. The Access_Code_Delete value is set to 'FALSE'. In addition, the gatekeeper does not need to change the alias name to the IP of the destination NetMeeting PC, confirms whether the destination NetMeeting PC is registered online (1) and checks the destination NetMeeting PC. Set it normally to 'use gatekeeper on call' (2). Then, the alias of the NetMeeting PC is called as the destination number (3).

Then, if the source endpoint is RAS and only the destination endpoint is Non-RAS, then from gateway to gateway, net meeting PC to gateway, net meeting PC to net meeting PC, and gateway to net meeting PC In the case of passing through the gatekeeper and otherwise, the VoIP call supporting method according to the present invention will be described with reference to FIG. 6.

First, when attempting to make a VoIP call from the gateway to the gateway through the gatekeeper, type Non-RAS in the endpoint properties for the Non-RAS gateway and set the forced online flag to 'Yes'. To force it to be online (1). Then, enable the GateKeeper_Connection field in the gatekeeper option of the source gateway. It then attempts to connect the call through the gatekeeper. In the gatekeeper stage, the IP of the corresponding access code of the routing table is set as the destination gateway. At this point, the destination endpoint is not an endpoint that supports RAS, but it is forced online because the gatekeeper must know the address. The destination gateway disables the GateKeeper_Connection field.

Secondly, when attempting to make a VoIP call from the gateway to the gateway without going through the gatekeeper, for the non-RAS gateway, set the type to Non-RAS in the endpoint properties and set the forced online flag to 'Yes'. To force it online (1). Then, enable the GateKeeper_Connection field in the gatekeeper option of the source gateway. It then attempts to connect the call through the gatekeeper. In the gatekeeper stage, the IP of the corresponding access code of the routing table is set as the destination gateway. At this point, the destination endpoint is not an endpoint that supports RAS, but it is forced online because the gatekeeper must know the address. The destination gateway disables the GateKeeper_Connection field.

Thirdly, when attempting to make a VoIP call from the NetMeeting PC to the gateway through the gatekeeper, set the type to Non-RAS in the endpoint properties for the Non-RAS gateway and set the forced online flag to ' Change it to Yes' to force it to come online (1). By using the gatekeeper when calling the starting NetMeeting PC, the IP address of the gatekeeper and the NetMeeting PC alias are set, and the call is attempted through the gatekeeper. The access code and IP address of the destination must be registered in advance with the gatekeeper. At this point, the destination gateway is not an endpoint that supports RAS, but it is forced online because the gatekeeper must know the address. The destination gateway disables the GateKeeper_Connection field.

Fourthly, when attempting to make a VoIP call from a NetMeeting PC directly to a NetMeeting PC without going through a gatekeeper, set the Type to Non-RAS in the endpoint properties for the Non-RAS Gateway. Force the online state by changing the online flag to 'Yes' (1). The alias and IP address are then registered for the actual NetMeeting PC. By using the gatekeeper when calling the starting NetMeeting PC, the IP address of the gatekeeper and the NetMeeting PC alias are set, and a call connection is not made through the gatekeeper. In addition, the destination NetMeeting PC is set to 'call using gateway'. The nickname of the starting NetMeeting PC is called with the destination number.

Fifthly, when attempting to make a VoIP call from the gateway to the NetMeeting PC through the gatekeeper, set the type to Non-RAS in the endpoint properties for the Non-RAS gateway and set the forced online flag to ' Change it to Yes' to force it to come online (1). The alias and IP address are then registered for the actual NetMeeting PC. Then, enable the GateKeeper_Connection field in the gatekeeper option of the source gateway. It then attempts to connect the call through the gatekeeper. On the other hand, the gatekeeper stage sets the IP of the corresponding nickname of the subscriber profile to the destination NetMeeting PC in advance in step (1). The destination NetMeeting PC is then set to Call Using Gateway. The nickname of the starting NetMeeting PC is called with the destination number.

Sixth, when attempting to make a VoIP call from the gateway directly to the NetMeeting PC without going through the gatekeeper, for the non-RAS gateway, set the type to Non-RAS in the endpoint properties and the forced online flag. Change to 'Yes' to force it to be online (1). The alias and IP address are then registered for the actual NetMeeting PC. Then enable the GateKeeper_Connection field in the Gatekeeper option of the source gateway. It then attempts to connect the call through the gatekeeper. On the other hand, the gatekeeper stage sets the IP of the corresponding nickname of the subscriber profile to the destination NetMeeting PC in advance in step (1). The destination NetMeeting PC is then set to Call Using Gateway. The nickname of the starting NetMeeting PC is called with the destination number.

In the above description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. Therefore, the scope of the present invention should not be defined by the described embodiments, but should be determined by the equivalent of claims and claims.

As described above, the present invention enables end services that support RAS by enabling services for non-RAS endpoints that do not support RAS in the gatekeeper in non-RAS endpoints that exist in the current VoIP network. There is an advantage of providing a method to support free VoIP call service between an endpoint and an endpoint that does not support RAS.

Claims (1)

Claims [1] A method for supporting a voiceover IP call to a non-ALS endpoint in a gatekeeper control area configured by connecting a server with a gatekeeper and a plurality of endpoints, Setting a mandatory online flag on registration information of the plurality of non-ALS endpoints; Checking the forced online flag value of the corresponding non-ALS endpoint to which the call is to be made; If the compulsory online information of the corresponding non-ALS endpoint is set to 'Yes', registering the endpoint online with the endpoint registered by the normal RS protocol; If the forced online information of the corresponding endpoint is set to 'no', the non-LA endpoint does not allow voice over IP calls; The voice over IP call support method for the non-ALS endpoint of the gatekeeper, characterized in that the process of loading the registration information of the corresponding non-ALS endpoint into the memory of the gatekeeper.