KR20090005455A - Linkage and db management system of ip pbx - Google Patents

Abstract

A method for linking a plurality of IP-PBXs which are independently dispersed and a DBMS thereof are provided to realize the communication between IP-PBX subscribers through the extension communication without constructing an additional exclusive line by using one administration IP-PBX in each building where a plurality of companies exist. An IP- PBX(10) has a closed user group function. A database(20) stores subscriber information of IP-PBXs installed in each building, terminal position information and routing information. A database synchronization module(30) is linked with databases of the IP-PBXs installed in the other buildings to manages dispersed IP-PBX subscriber databases. The IP-PBX subscriber information of the databases is integratedly managed according to each building. The database synchronization module performs a corresponding transaction for adding/deleting/updating members, and synchronizes the dispersed IP-PBX subscriber information.

Description

Linkage and DB management system of IP PBX which are distributed independently and independently {IP PBX}

The present invention relates to an enterprise managed IP-PBX (IP Switching System) for providing VoIP (Internet Telephony) service, and to the configuration and management of a subscriber database (DB) for interworking independently distributed IP-PBX.

VoIP is a communication service technology that converts voice data into Internet protocol data packets on a computer network to enable voice calls, such as telephone calls in a general telephone network.

The IP-PBX collectively refers to a server and related application software that performs basic call processing and various messaging related processes in a VoIP system.

IP-PBXs are classified into Hosted IP-PBXs and Managed IP-PBXs, depending on their location and management.

In the hosted IP-PBX scheme, a remote service provider (SP) provides IP-PBX and applications to subscribers, and subscribers rent and use VoIP systems.

In other words, the service provider is responsible for the management and maintenance of the IP-PBX and all IP-PBX related tasks.

On the other hand, managed IP-PBX (hereinafter referred to as IP switch) method is a type in which a company purchases an IP switch and installs it in the company, and only the Internet line is provided by the service provider.

This method requires the purchase of an IP exchanger when constructing a service, but it can reduce fixed service expenses, and it is possible to introduce various applications according to its characteristics by owning an IP exchanger.

However, the problems of the conventional method are increased IP-PBX construction cost, lack of interworking solution between IP-PBX, reduced service reliability when constructing IP-PBX central subscriber DB, and increased construction cost when interworking multiple IP-PBX and IMPS.

The problems of the conventional method are summarized as follows.

First, as shown in FIG. 1, the initial construction cost of the entire building according to the construction of the managed IP-PBX increases for each company occupying each building.

 Second, there is currently no interworking solution between managed IP-PBXs.

Therefore, independently installed IP-PBX is composed of a local subscriber DB does not work with other IP-PBX subscriber DB.

In the case of companies distributed in multiple buildings because interworking between local DBs is not supported, extension call service is not possible because subscriber DB is not integrated.

As a result, an internal call is required to build a separate leased line or to modify routing tables.

Third, a problem arises when constructing a subscriber DB centrally in order to integrate multiple IP-PBXs.

Existing IP-PBX system does not provide a solution for interworking of multiple IP-PBXs.

Therefore, in consideration of the interworking of independent IP-PBXs, if the subscriber DB is centrally configured as a single DB to provide services, as shown in FIG. Internet phone service) is not available.

Lastly, in order to provide IP-PBX-based additional services, the construction cost for system configuration increases when IMPS services are provided. Due to the deterioration of PSTN network of wired communication service providers and the necessity of providing IP-based integrated multiservices other than voice communication services, it is necessary to accommodate various additional services of VoIP technology.

As such, in the related art, IP-PBX construction cost increases, IP-PBX interworking solution lacks, IP-PBX central subscriber DB deployment, service reliability decreases, and multiple IP-PBX and IMPS integration costs increase.

In the present invention, to solve such a conventional problem,

(a). In each building, only one managed IP-PBX with the addition of the Closed User Group (CUG) function, which allows multiple customers to separate and operate the system through the same system, Tenants can be accommodated to provide services by dividing the extension and the trunk line group for each tenant, thereby providing the desired services for each company in the building, and for each company in the building. The implementation of managed IP-PBX prevents the initial installation cost of the entire building from increasing.

(b). The present invention provides an interworking solution between a plurality of independently distributed managed IP-PBX, to build an IP-PBX subscriber DB for each building for interworking IP-PBX, and to interwork with other buildings and DB management (Synchronization according to indexing, subscriber addition / deletion / update), integrated management of subscriber DB of the same company distributed in two or more buildings allows free communication between members of the same company located in distributed buildings. It was made possible.

The interworking and DB management system of a plurality of IP-PBXs independently distributed in the present invention,

A plurality of IP-PBXs with CUG functions installed in each building, a database installed for each installed in each building, and a subscriber DB, terminal location information, and routing information of IP-PBXs are registered and stored, and data installed in other buildings. The DB synchronization module installed for the database and the clients (IP phones, soft phones) for the distributed IP-PBX subscriber DB management through interworking with the base is characterized in that it is configured.

According to the present invention, it is possible to reduce the initial deployment cost of the enterprise IP-PBX, and by maintaining integrated management of the IP-PBX subscriber DB, it is possible to reduce the maintenance costs by enabling the internal call of the enterprise distributed in multiple buildings ,

According to the present invention, the construction cost is reduced by using one managed IP-PBX for each building in which a plurality of companies are located, and by distributing subscriber DBs in each building, the Internet is more reliable than the centralized subscriber DB structure. Since it can provide telephone service, communication cost can be reduced by treating as an extension call using IP-PBX subscriber DB information without establishing a separate lease line.

In addition, when one central subscriber DB is configured for interworking with multiple IP-PBXs, even if call setup is made in the same building, the subscriber DB of the public network should always be accessed, so that if the network is disconnected, there is a global service failure. Can be generated. However, according to the present invention, by integrating and managing subscriber DBs of companies distributed in various buildings, it is possible to provide reliable Internet telephony services for subscribers.

Such a configuration and operation of the present invention will be described in detail with reference to the embodiment shown in FIG. 3 as follows.

Installed in each building

IP-PBX (10) having a CUG (Closed User Group) function, and a database (20) registered and stored subscriber information, terminal location information, routing information of IP-PBX (10) installed in each building It is configured to include a database synchronization module 30 for distributed IP-PBX subscriber DB management through interworking with the database 20 of the IP-PBX 10 installed in another building.

In the present invention, the IP-PBX 10 is installed in each building, the database 20 is configured to enable group management for each company in the building, and the enterprises having subscribers distributed between buildings. The database synchronization module 30 is configured for DB interworking management.

The IP-PBX subscriber information of the database 20 is integratedly managed for each building in which a plurality of companies reside, and each building has a structure in which the database 20 is distributed.

The IP-PBX subscriber information of a company distributed in two or more buildings has a plurality of entire databases 20 of the company for each building.

To add, delete, or renew members of a distributed company, perform the relevant transaction and synchronize the distributed IP-PBX subscriber information.

To this end, the database synchronization module 30 is configured.

The database 20 includes IP-PBX subscriber information, terminal location information, and routing information.

IP-PBX subscriber information is information of a subscriber who is a service provider, terminal location information is a call routing request and location information of a service target terminal (client), and routing information is information for call connection connection.

Table 1 shows an example of subscriber information of IP-PBX.

CUG ID Subscribed Closed User Group Name Public Number Subscriber's Public Number Extension number Subscriber's extension UID Subscriber's Authentication ID Password Subscriber's Authentication Password name Subscriber name Call service Call related service information ... ...

The present invention having such a configuration provides interworking between IP-PBXs, integrates IP-PBX subscriber information of members of the same company geographically dispersed, and uses subscriber DB information when calling between distributed members of the same company. Enable internal call service.

First, subscriber information integration is as follows.

Free management of subscriber information of the same company distributed in two or more buildings is possible by extension telephone.

Recognize the called party information of another building as a member of the same company by referring to the integrated subscriber information during call setup.

To this end, there is a plurality of identical subscriber information in a distributed building. The IP-PBX subscriber information schema is shown in Table 1.

As shown in FIG. 3, when the subscriber information of the 'a' building is changed, the subscriber information of the 'b' building is made by the database synchronization module 30.

Subscriber information synchronization of the database 20 may be implemented using a high availability solution disaster recovery (DR) solution with real-time data replication.

For this reason, when the A company member of the 'A' building calls into the A company of the 'I' building, the member of the same company is recognized as a member of the same company due to retrieving the subscriber information of the database 20 located in the 'A' building and using the IP network To make an internal call possible.

The IP-PBX subscriber information in Table 1 provides additional service functions, subscriber related data generation and inquiry procedures, and information required for call setup.

This information includes the user group name (CUG ID), extension number, subscriber name, subscriber's location information, subscriber's device information, public number, and subscriber ID / authentication password for user registration. (ID / PW), supplementary service information (call related supplementary service information), and the like.

The user group information (CUG ID) enables grouping of subscribers in the system and provides a function of allowing various additional functions to be used independently between groups.

In addition, users can create, delete, and change groups.

As shown in Figure 4, an extension call flow diagram of a company with organizations distributed in different buildings. (A 'Building A <->' I 'Building A).

For call setup, terminal location information including subscriber information, call routing request and location information of a target terminal, and routing information for call connection connection are required.

When the call setup request (①) is generated, it is determined whether the target subscriber (phone number) is the extension number of the same CUG member in the building, a subscriber located in a geographically dispersed building, or a general number other than the CUG member. The decision is made by referring to the subscriber information. (②)

As a result of the phone number judgment, if the member of the same group, the location information (③) and routing information of the call connection request terminal and the call connection request terminal are checked (④), and the call is made to the IP-PBX of the corresponding call connection request telephone number. Perform routing (⑤)

If it is not a call between CUG members, a normal call routing connection is made.

5 is a flowchart showing a subscriber addition registration procedure in the system proposed by the present invention.

There can be an operational web server that can be used according to the operation of the user for addition, modification and deletion of user information.

For example, the subscriber addition registration will be described.

First, the 'A' company in the case of a distributed company will be described. 'A' is a single company distributed in 'G' or 'B'.

Company A of 'A' Building performs registration of new subscriber addition using subscriber management web application.

According to the subscriber information of the database 20, the company A recognizes that the organization is distributed in the 'a' or 'building', and the database synchronization module 30 uses the location information of the distributed 'b' building to determine the ' The IP-PBX subscriber information of the building is updated.

 If only a single building exists, when a new subscriber registration transaction of Company B of the 'A' building occurs, only the IP-PBX subscriber information of the 'A' building is updated.

6 is a flowchart for subscriber deletion (subscriber information update) in the system proposed by the present invention.

As described above, the present invention performs configuration and management of subscriber DB for interworking with a plurality of IP-PBXs that are independently distributed, thereby enabling IP-PBX services in a building through one IP-PBX in a building, and distributed among buildings. It is possible to provide a system that enables the internal call and IP supplementary services between companies.

1 is a view showing the configuration of a conventional IP-PBX.

Figure 2 is a conventional central subscriber database configuration diagram (example according to IP-PBX subscriber database integration)

3 is a view showing the configuration of the interworking and database management system of a plurality of IP-based exchange (IP PBX) independently distributed in the present invention.

4 is an extension call flow diagram of a company having organizations distributed in different buildings, in accordance with the present invention.

5 is a flowchart showing a subscriber addition registration procedure according to the present invention.

6 is a flowchart for deleting a subscriber (subscriber information update) in the present invention.

Claims (3)

Installed in each building, IP-PBX with CUG (Closed User Group) function that enables group management of each company in the building, additional service function of IP-PBX installed in each building, subscriber related data generation and inquiry procedure, Independently comprising a database containing information necessary for call setup, and a database synchronization module for distributed IP-PBX subscriber DB management through interworking with the database of IP-PBX installed in another building Interworking and database management system of multiple IP-based exchanges (IP PBX) distributed. The database of claim 1, wherein the database includes subscriber information, terminal location information, and routing information. The subscriber information includes the user group name (CUG ID), extension number, subscriber name, location information of the subscriber, device information of the subscriber, public number, and subscriber ID / authentication for user authentication. Interworking and database management system of a plurality of independent IP-based exchange (IP PBX), characterized in that it comprises a password (ID / PW), supplementary service information (Call related supplementary service information). When a call setup request is made, it is determined whether the target subscriber (telephone number) is the extension of the same CUG member in the building, a subscriber located in a geographically dispersed building, or a general number that is not a CUG member. Process, As a result of the telephone number judgment, when the members of the same group check the location information and routing information of the call connection request terminal and the call request terminal, the call routing process is performed to IP-PBX of the corresponding call connection request telephone number. and, If the call between the CUG member is not connected between the call routing connection of a plurality of independent IP-based exchange (IP PBX) and database management system, characterized in that the process consists of making a general call routing connection connection.

Images