JP4448750B2 - Private telephone exchange service system - Google Patents

Description

  The present invention relates to a private branch exchange service system that provides a private branch exchange function to a plurality of groups such as a plurality of companies via an IP network using a shared private branch exchange.

  The IP Centrex service is a network service provider or service provider that uses at least one private branch exchange, that is, an IP-PBX device, to provide a PBX function to a plurality of customers such as companies via an IP network. This is a private telephone exchange service to be provided, and realizes a so-called outsourcing form in which the exchange work that has been realized in the customer's facility is outsourced. With this service, the customer can reduce the initial cost associated with the introduction of the IP telephone service, and is excellent in economy and convenience in that the maintenance work related to the customer-installed PBX can be saved.

With reference to the description of Patent Document 1, a private branch exchange system operating on a public network line is disclosed. According to the configuration of the private branch exchange system, when a user tries to make a call connection, the user sends a call connection request including identification information of a user group to which the user belongs to via the terminal. To the exchange server connected to the line. The exchange server accommodates a plurality of user groups, authenticates the terminal of the user based on identification information of the user group of the user making a call connection request, and Provide telephone exchange. As a result, a form in which a plurality of user groups share and use an exchange device on the public network can be realized.
JP 2003-324524 A

  However, in the conventional system, since different user groups such as a plurality of companies share at least one exchange server, the use by one user group is restricted due to the existence of other user groups. There was a case. For example, identifiers such as login account names are not allowed to be duplicated between groups, and it is not permitted to define arbitrary account names. There is a problem that it is difficult to perform flexible customization for each group.

  An object of the present invention is to exchange private telephones based on setting information that can be flexibly set for a group of one company or the like without being aware of the existence of other groups in a system including a shared private branch exchange. It is to provide a private telephone exchange service system that provides functions.

The private telephone exchange service system according to the present invention includes at least one IP-PBX, and provides a private telephone exchange service to a plurality of groups each consisting of a plurality of telephone terminals based on the setting information for each group. a private branch exchange service system providing via the IP network by -PBX, the identifier of each said group, at least one IP address allocated to each of the groups, the IP address management table that associates An IP address management table holding means for holding, an account management table holding means for holding an account management table in which the identifier is associated with at least one account, and the setting update request in response to a setting update request for the setting information an identifier corresponding to the IP address of the source of the An identifier detection means for detecting from the IP address table, the detected identifier with the set the account management table search to set updating the transmission of the setting information corresponding to the account as a key and account contained in the update request A setting update permission unit that is originally permitted, and a setting information update unit that updates the setting information of the group according to the setting update information corresponding to the setting update request.

  According to the private branch exchange service system of the present invention, when a setting update request for a setting update request for setting information is made, it is possible to distinguish a user group such as a company identification from the IP address of the access source. Given. Thereby, in the use of one group, flexible setting is possible without being aware of the existence of other groups.

Embodiments of the present invention will be described in detail with reference to the accompanying drawings.
<First embodiment>
FIG. 1 shows a first embodiment of the present invention, and shows an overall configuration including an IP Centrex system which is a private branch exchange service system according to the present invention. The IP Centrex system 10 includes an IP-PBX group that includes a provisioning system 11 that sets and manages setting information for each group of companies and the like, and at least one or more IP telephone exchanges that realize an exchange function of the IP Centrex service. 31 and a provider IP network 30 to which the provisioning system 11 and the IP telephone exchange group 31 are connected.

  The carrier IP network 30 is an IP network held by a carrier providing the Centrex service, and includes the A company IP network 40 and the B company which are networks of subscribers who use the Centrex service, that is, a plurality of companies, respectively. An IP network 50 is connected via a suitable gateway device (not shown). In the present embodiment, an example in which two company groups are accommodated is shown, but the present invention is not limited to this number, and it is possible to accommodate two or more groups.

  The IP-PBX group 31 includes at least one or a plurality of IP-PBXs. For example, the IP-PBX 32 performs a private telephone exchange function according to setting information 33 set by the provisioning system 11. The setting information 33 includes terminal information and extension numbers of a plurality of telephone terminals accommodated by the IP-PBX 32, and various setting information such as call group setting information is set by the provisioning system 11.

  Connected to the A company IP network 40 are an operation terminal 41 for setting and updating setting information in the provisioning system 11 and an A company telephone terminal group 42 including a plurality of telephone terminals which are IP phones. Similarly, an operating terminal 51 for updating setting information and a B company telephone terminal group 52 including a plurality of telephone terminals that are IP telephones are connected to the B company IP network 50. An IP address group 43 is assigned to each telephone terminal of the operation terminal 41 and the telephone terminal group 42 connected to the A company IP network 40. An IP address group 53 is assigned to each telephone terminal of the operation terminal 51 and the telephone terminal group 52 connected to the B company IP network 50. As a specific example of the IP address assignment method, at least one global address that can uniquely identify a network node as a whole network including the carrier IP network 30 is assigned to one company IP network, A method of giving a local address that can be uniquely identified in the corporate IP network is conceivable.

  FIG. 2 shows a more detailed configuration of the provisioning system 11 shown in FIG. The provisioning system 11 is a server device composed of one computer, and the software configuration thereof includes a login management unit 12 that accepts login from the operation terminal 41 or 51, a login authentication unit 13 that performs login authentication, and a user's A user management table 15 for managing information, an account management table 16 for managing login authentication data, an IP address authenticating unit 14 for authenticating an IP address assigned to each terminal of each company, And an IP address management table 17 for managing the IP address of each company. Here, each company corresponds to the A company and the B company in the description of FIG. Each terminal corresponds to, for example, the operation company 41 and each of the telephone terminals constituting the telephone terminal group 42 in the case of company A.

  FIG. 3 illustrates the relationship and setting example of each table in the first embodiment. The provisioning system 11 includes a user management table 15 that manages terminal information and extension numbers that define telephone terminal identification and specifications using a user ID as a key, and authentication at the time of login to the provisioning system 11 using a company identifier as a key. Account management table 16 for managing the account name, password, and user ID used for the IP address group 43 or 53 consisting of the start and end of the IP address assigned to the company identifier and the company (see FIG. 1) ) Includes an IP address management table 17 for managing the range of each company.

  Referring to the figure, by searching the IP address management table 17 from the IP address of the transmission source at the time of login, the corresponding group is detected by the company identifier as identification data. By searching the account management table 16 using this company identifier, the account name set for each company corresponding to the company identifier and the corresponding password are determined. As a result, it is possible to authenticate the sender who logs in using the account name and password as input conditions. In addition, the user name and the user ID are determined from the account name, and the terminal information of the telephone terminal and the setting information such as the extension number given to the user corresponding to the account name by searching the user information table 15 The user who has logged in with the account name can refer to and update the setting information.

  FIG. 4 shows a processing procedure in the provisioning system of the first embodiment. Here, in the provisioning system 11, in response to a login request from the operation terminal 41 or 51 of the company, the operation until the operation screen list is displayed on the terminal screen after the login authentication is configured as shown in FIGS. The description will be given with reference to the elements as appropriate.

  First, the login management unit 12 accepts a login request from a company user (step S101), and issues an authentication request to the login authentication unit 13 using the account name and password as input conditions (step S102). The login authentication unit 13 accepts the authentication request (step S103), and makes a transmission source authentication request to the IP address authentication unit 14 in order to authenticate the transmission source company (step S104).

  The IP address authentication unit 14 searches the IP address management table 17 using the source address as a key, and acquires a company identifier as an authentication result of the source company (step S105). Next, the company identifier is returned to the login authentication unit 13 as a result of the authentication (step S106). In response to this, the login authentication unit 13 searches the account management table 16 using the company identifier and the account name as keys, and acquires a password (step S107). Next, authentication is performed to check the acquired password against the input account (step S108). Next, the authentication result is returned to the login management unit 12 (step S109).

  When the authentication is normally performed, the login management unit 12 acquires user information from the user management table 15 using the user ID as a key (step S110), and edits the operation screen list (step S111). Next, the operation screen list is displayed on the operation terminal 41 or 51 of the transmission source company as a menu for the IP center service (step S112). Thereafter, the provisioning system 11 updates the setting information of the IP-PBX group 30 after updating each table according to the setting update information of the logged-in user.

In the first embodiment described above, the provisioning system 11 includes the IP address authentication unit 14 that performs authentication of the access source based on the IP address management table 17 from the address of the operation terminal 41 or 51 of the transmission source, that is, the access source. Is provided. This makes it possible to determine the identity of the login request source company from the source address. That is, the user who accesses the provisioning system 11 does not need to be aware of the existence of another company such as inputting the identification information of the company at the time of login. Further, since there is no need to be aware of the existence of other companies, account names can be arbitrarily determined within the company. The administrator of each company can log in to the provisioning system 11 using this account name, and update service settings such as telephone number planning, pickup group settings, and extension representative settings.
<Second embodiment>
FIG. 5 shows a more detailed configuration of the provisioning system in the second embodiment. The second embodiment is based on the configuration of the centronics system 10 in the first embodiment shown in FIG.

  The software configuration of the provisioning system 11 includes a login management unit 12, a login authentication unit 13, a user management table 15, an account management table 16, an IP address authentication unit 14, an IP address management table 17, and a first implementation. Use that includes the same as in the example, and further allows customization of the functions that can be used for each user based on the usable function table 19 that manages the data of the functions that can be used for each user. A possible function management unit 18 is included.

  FIG. 6 illustrates the relationship and setting example of each table in the second embodiment. The provisioning system 11 includes a user management table 15, an account management table 16, and an IP address management table 17, and further includes an available function table 19 as in the case of the first embodiment. . The usable function table 19 is data for managing usable function information for each user, and whether or not dial-in, call group, and hunt group can be used by using the user ID as key information (for example, illustrated). As specified) is included.

  Referring to the figure, by searching the IP address management table 17 from the IP address of the transmission source at the time of login, the corresponding group is detected by the company identifier as identification data. By searching the account management table 16 using this company identifier, the account name set for each company corresponding to the company identifier and the corresponding password are determined. As a result, it is possible to authenticate the sender who has logged in using the account name and password as input conditions. In addition, the user name and the user ID are determined from the account name, and the terminal information of the telephone terminal and the setting information such as the extension number given to the user corresponding to the account name by searching the user information table 15 Can be accessed. Further, the available function table 19 is searched from the user ID, and each of dial-in, call group that defines the range of call pickup, hunt group that defines the representative telephone, and the like that are functions that can be used for the user. Functional information is determined. A user who logs in with the account name can refer to and update the setting information including the usable function.

  FIG. 7 shows a processing procedure in the provisioning system of the second embodiment. Here, in the provisioning system 11, in response to a login request from the company operation terminal 41 or 51, the operation until the operation screen list is displayed on the terminal screen after the login authentication is configured as shown in FIGS. The description will be given with reference to the elements as appropriate.

  First, the login management unit 12 accepts a login request from a company user (step S201), and issues an authentication request to the login authentication unit 13 using the account name and password as input conditions (step S202). The login authentication unit 13 accepts the authentication request (step S203) and makes a transmission source authentication request to the IP address authentication unit 14 in order to authenticate the transmission source company (step S204).

  The IP address authentication unit 14 searches the IP address management table 17 using the source address as a key, and acquires a company identifier as an authentication result of the source company (step S205). Next, the company identifier is returned to the login authentication unit 13 as a result of authentication (step S206). In response to this, the login authentication unit 13 searches the account management table 16 using the company identifier and account name as keys, and acquires a password (step S207). Next, authentication is performed to check the acquired password against the input account (step S208). Next, the authentication result is returned to the login management unit 12 (step S209). When the authentication is normally performed, the login management unit 12 acquires user information from the user management table 15 using the user ID as a key (step S210).

  Next, the login management unit 12 makes a usable function list acquisition request to the usable function management unit 18 in order to obtain usable function information set for the user (step S211). In response to this, the usable function management unit 18 refers to the usable function management table 19 and obtains a list of usable functions of the user using the user ID as a key (step S212). Then, it returns to the login management part 12 (step S213). In response to this, the login management unit 12 edits the operation screen list from the available function list (step S214), and then the login management unit 12 causes the company operation terminal 41 or 51 to display the operation screen list. (Step S215). Thereafter, the provisioning system 11 updates the setting information of the IP-PBX group 30 after updating each table according to the setting update information of the logged-in user.

In the second embodiment described above, the provisioning system 11 has means for managing function list information that can be used for each user, so that the user can use the preset function information when logging in. The screen list that can be operated for each user is edited and provided. Accordingly, it is possible to set whether or not each function of the dial-in, call group, and hunt group can be used for each user, and various customizations according to the actual situation of the company are possible.
<Third embodiment>
FIG. 8 shows a more detailed configuration of the provisioning system in the third embodiment. The third embodiment is based on the configuration of the Centronics system 10 in the first embodiment shown in FIG.

  The software configuration of the provisioning system 11 includes a login management unit 12, a login authentication unit 13, a user management table 15, an account management table 16, an IP address authentication unit 14, an IP address management table 17, and usable functions. The management unit 18 and the usable function table 19 are included as in the second embodiment, and the user information is managed hierarchically based on the user hierarchy management table 21. It includes a user hierarchy management unit 20 that enables operation of user information of subordinate users.

  FIG. 9 illustrates the relationship and setting example of each table in the third embodiment. The provisioning system 11 includes a user management table 15, an account management table 16, an IP address management table 17, and an available function table 19 as in the case of the second embodiment, and further includes a user hierarchy. A management table 21 is included. The user hierarchy management table 21 holds user hierarchy management data including an administrator ID and a user ID.

  Referring to the figure, by searching the IP address management table 17 from the IP address of the transmission source at the time of login, the corresponding group is detected by the company identifier as identification data. By searching the account management table 16 using this company identifier, the account name set for each company corresponding to the company identifier and the corresponding password are determined. As a result, it is possible to authenticate the sender who logs in using the account name and password as input conditions.

  In addition, the user name and the user ID are determined from the account name, and the terminal information of the telephone terminal and the setting information such as the extension number given to the user corresponding to the account name by searching the user information table 15 Can be accessed. Further, the user hierarchy management table 21 is searched from the user ID, and the user ID belonging to the lower level in the hierarchy for the user is determined. By searching the usable function table 19 and the user management table 15 using the user ID belonging to the lower level as a key, it becomes possible to access the setting information of these users, and refer to and update the settings. Can do.

  FIG. 10 shows a processing procedure in the provisioning system 11 of the third embodiment. Here, in the provisioning system 11, in response to a login request from the company operation terminal 41 or 51, the operation until the operation screen list is displayed on the terminal screen after login authentication is configured as shown in FIGS. The description will be given with reference to the elements as appropriate.

  First, the login management unit 12 accepts a login request from a company user (step S301), and issues an authentication request to the login authentication unit 13 using the account name and password as input conditions (step S302). The login authentication unit 13 receives the authentication request (step S303), and makes a transmission source authentication request to the IP address authentication unit 14 in order to authenticate the transmission source company (step S304).

  The IP address authenticating unit 14 searches the IP address management table 17 using the source address as a key, and acquires a company identifier as an authentication result of the source company (step S305). Next, the company identifier is returned to the login authentication unit 13 as a result of the authentication (step S306). In response to this, the login authentication unit 13 searches the account management table 16 using the company identifier and account name as keys, and acquires a password (step S307). Next, authentication is performed to verify the acquired password against the input account (step S308). Next, the authentication result is returned to the login management unit 12 (step S309). When the authentication is normally performed, the login management unit 12 acquires user information from the user management table 15 using the user ID as a key (step S310).

  Next, the login management unit 12 sends a usable function list acquisition request to the usable function management unit 18 in order to obtain usable function information set for the user (step S311). In response to this, the usable function management unit 18 refers to the usable function management table 19 and obtains a list of usable functions of the user using the user ID as a key (step S312). Then, it returns to the login management part 12 (step S313).

  Next, the login management unit 12 makes a request for acquiring user hierarchy information to the user hierarchy management unit 20 in order to acquire user information to be managed under the corresponding user (step S314). In response to this, the user hierarchy management unit 20 refers to the user hierarchy management table 21 and searches for the administrator ID part by the user ID, and when the management target user information exists under the corresponding user. The user information list is acquired (step S315). Then, this is returned to the login management part 12 (step S316). The login management unit 12 edits the operation screen list from the previous usable function list and user information list (step S317). Next, the operation screen list is displayed on the company operation terminal 41 or 51 (step S318). Thereafter, the provisioning system 11 updates the setting information of the IP-PBX group 30 after updating each table according to the setting update information of the logged-in user.

  In the third embodiment described above, by adding a user hierarchy table to the subscriber information management method of the provisioning system 11, the range of operable data can be defined for each user. That is, for a plurality of users in a company, the provisional functions can be differentiated between hierarchies such as a hierarchical relationship such as an administrator or a managed person. Furthermore, by differentiating the provided functions, it is possible to limit the range of data that can be handled according to the user's hierarchy, and it is possible to ensure the security in the company according to the hierarchy.

  The configuration of each processing unit in the plurality of embodiments described above shows a logical functional configuration, and does not limit the hardware and software configurations on mounting. Similarly, the configuration of each table shows a logical data configuration, and does not limit the software configuration on mounting.

  The private branch exchange service system according to the present invention can be implemented not only by a telecommunications carrier operating as a telecommunications service but also by many operators such as Internet service providers.

BRIEF DESCRIPTION OF THE DRAWINGS It is a block diagram which shows the 1st Example of this invention, and shows the whole structure containing the IP Centrex system which is a private telephone exchange service system by this invention. FIG. 2 is a block diagram showing a more detailed configuration of the provisioning system shown in FIG. 1. It is explanatory drawing explaining the relationship and setting example of each table in a 1st Example. It is a sequence diagram which shows the process sequence in the provisioning system of a 1st Example. It is a block diagram which shows the more detailed structure of the provisioning system in a 2nd Example. It is explanatory drawing explaining the relationship and setting example of each table in a 2nd Example. It is a sequence diagram which shows the process sequence in the provisioning system of a 2nd Example. It is a block diagram which shows the more detailed structure of the provisioning system in a 3rd Example. It is explanatory drawing explaining the relationship and setting example of each table in a 3rd Example. It is a sequence diagram which shows the process sequence in the provisioning system of a 3rd Example.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Centrex system 11 Provisioning system 12 Login management part 13 Login authentication part 14 IP address authentication part 15 User management table 16 Account management table 17 IP address management table 18 Usable function management part 19 Usable function table 20 User hierarchy management part 21 User hierarchy management table 30 Provider IP network 31 IP-PBX group 32 IP-PBX
33 Setting information 40, 50 Corporate IP network 41, 51 Operation terminal 42, 52 Telephone terminal group 43, 53 IP address group

Claims (6)

A private telephone exchange service is provided to the plurality of groups each including a plurality of telephone terminals including at least one IP-PBX via the IP network by the IP-PBX based on the setting information for each group. A private telephone exchange service system,
And identifier of each group, and the IP address management table holding means for holding the IP address management table associating at least one IP address assigned to each of said groups,
Account management table holding means for holding an account management table in which the identifier is associated with at least one account;
An identifier detection means for detecting in accordance with the configuration update request for the setting information, the identifier corresponding to the source IP address of the configuration update request from the IP address table,
A setting update permission means for searching the account management table using the detected identifier and an account included in the setting update request as a key and allowing the transmission source to update settings for setting information corresponding to the account ;
Setting information update means for updating the setting information of the group according to the setting update information corresponding to the setting update request;
A private branch exchange service system characterized by including:
  The private branch exchange service system according to claim 1, wherein the setting update permission means permits the setting update in response to a setting update request accompanied by an account name that can be arbitrarily determined for each group.   3. The telephone exchange service providing system according to claim 2, wherein the setting update permission means permits setting update for setting information applied only to a user's telephone terminal corresponding to the account name.   The setting update permission unit is configured not only for the user's telephone terminal corresponding to the account name but also for a plurality of user's telephone terminals based on predetermined information that defines a hierarchical relationship between the users for each group. 3. The telephone exchange service providing system according to claim 2, wherein setting update for the applied setting information is permitted.   The telephone exchange service providing system according to any one of the preceding claims, wherein the setting information includes at least terminal information and an extension number of each of the telephone terminals.   6. The telephone exchange service providing system according to claim 5, wherein the setting information includes setting information for controlling at least one use function of each use function of dial-in, call group, and hunt group.

Images