JP6690967B2 - Private branch exchange, control method therefor, control program, and private branch exchange system - Google Patents

Description

  The present invention relates to a private branch exchange, a control method therefor, a control program, and a private branch exchange system, and more particularly to a private branch exchange having high convenience in maintaining functions and services, a control method therefor, a control program, and a private branch exchange system.

  A private branch exchange is a telephone exchange that connects multiple private branch telephones to the telephone network, and is a device that is installed and operated in a facility such as a company to control outgoing and incoming calls from outside lines and calls between extension lines. Is. When the facility is large-scale or the company has a plurality of bases, a wide area telephone network is constructed by connecting a plurality of private branch exchanges with a dedicated line.

JP, 10-210156, A JP-A-4-281658

  However, there are various private branch exchange services such as extension representatives and call pickups. However, when multiple private branch exchanges are used together to provide services, there may be cases where the services cannot be provided or operational The first problem is that restrictions occur. For example, extensions housed in a plurality of different private branch exchanges cannot be put in the same extension representative. In addition, it was not possible to pick up an incoming call to a telephone housed in another private branch exchange. This is because the private branch exchanges are connected to each other by a dedicated line, but the amount of information that can be transmitted and received through the interface of the dedicated line is small, and the telephone service can be provided only within this small amount of information.

  The second problem is that conventional private branch exchanges have different manufacturers and models but different operation methods and display styles even with the same service name. Since there are large differences in specifications between manufacturers and models, when trying to replace an old private branch exchange with a new private branch exchange, the difference in specifications often poses a problem. This is because, depending on each manufacturer and model, the extension and trunk, peripheral devices for providing specific services such as three-way conferences and announcements, and the hardware and control programs for accommodating them in the private branch exchange, This is because each manufacturer and model were independently developed, and they were not shared by manufacturers and models.

  A third problem is that when there are a plurality of IP private branch exchanges on the IP network that realize circuit switching between IP telephones operating on the IP network, even if IP telephones call each other between the IP private branch exchanges. However, the point is that call control is performed using a dedicated line interface. This is because the range to be controlled by the private branch exchange is divided by using a leased line in order to perform call control without considering the difference in the manufacturer, model, configuration, and service provided of the IP private branch exchange. is there.

  The fourth problem is that it is difficult to apply or port the station data of the private branch exchanges of different manufacturers to the private branch exchanges of other manufacturers. This is because each manufacturer defines a unit for setting data and a data structure by its own logic, and has not been standardized.

  For example, as an invention that attempts to solve the first problem, there is an invention according to Patent Document 1 that enables all subscribers in a network to be provided with a service equivalent to being accommodated in one exchange. Can be mentioned. However, the invention according to Patent Document 1 can be realized only by connecting private branch exchanges of the same model that implements the invention, and for example, does not solve the second problem. This is because, in the invention according to Patent Document 1, when the processing node to be controlled is another node, the communication path switch, subscriber circuit, and trunk circuit of the other node are controlled via the communication control unit, but the premises of another model This is because even if an attempt was made to implement it including an exchange, it did not support the functions and interfaces of the speech path switch, subscriber circuit, and trunk circuit of other models.

  Therefore, an object of the present invention is to provide a unified telephone service to extension telephones housed in each private branch exchange when a plurality of private branch exchanges of different manufacturers and models exist on the IP network. .

  According to a first aspect of the present invention, a private branch exchange, which controls one or more peripheral devices connected to the private branch exchange, and which includes call event information and first call status information in the peripheral device. A local control unit that virtualizes the peripheral device, and receives the call event information and the first call state information of the virtualized peripheral device from the local control unit, and receives the received A user control unit that transmits a call state transition instruction to the peripheral device and second call state information indicating a call state of a transition destination to the local control unit based on call event information and the first call state information. A private branch exchange is provided, wherein the local control unit controls the peripheral device based on the call state transition instruction and the second call state information received from the user control unit.

  According to a second aspect of the present invention, there is provided a control method used in a private branch exchange, wherein the local control unit controls one or more peripheral devices connected to the private branch exchange, and Obtaining call event information and first call status information and virtualizing the peripheral device; a user control unit from the local control unit, the call event information of the virtualized peripheral device and the first One call state information is received, and based on the received call event information and the first call state information, a call state transition instruction for the peripheral device, and a second call state information in the transition destination call state. Transmitting to the local control unit, the local control unit controls the peripheral device based on the call state transition instruction and the second call state information received from the user control unit. Control method characterized by having a-up is provided.

  According to a third aspect of the present invention, there is provided a control program used in a private branch exchange, the computer controlling one or more peripheral devices connected to the private branch exchange, and a call event in the peripheral device. Local control unit that acquires information and first call state information and virtualizes the peripheral device; and the call event information and the first call state information of the virtualized peripheral device from the local control unit. To the local control unit, based on the received call event information and the first call state information, a call state transition instruction for the peripheral device, and second call state information in the call state of the transition destination. The local control unit causes the peripheral device to operate based on the call state transition instruction and the second call state information received from the user control unit. A control program, characterized in that Gosuru is provided.

  According to the present invention, a unified telephone service is provided regardless of the manufacturer or model of the private branch exchange.

It is a figure which shows the structural example of a private branch exchange by embodiment of this invention. FIG. 6 is a conceptual diagram of a call state transition scenario according to an embodiment of the present invention. 9 is a table showing an example of call state information and a call state transition determination function in an “extension free” state in the call state transition scenario according to the embodiment of the present invention. 7 is a table showing an example of call state information and a call state transition determination function in a “1stDT (Dial Tone)” state in the call state transition scenario according to the embodiment of the present invention. 7 is a table showing an example of call state information and a call state transition determination function in a “dial” state of the call state transition scenario according to the embodiment of the present invention. 9 is a table showing an example of call state information and a call state transition determination function in a state of "extension call" in the call state transition scenario according to the embodiment of the present invention. 7 is a table showing an example of call state information and a call state transition determination function in a “two-way call” state of the call state transition scenario according to the embodiment of the present invention. 9 is a table showing an example of call state information and a call state transition determination function in a “ROT (Reorder Tone)” state in the call state transition scenario according to the embodiment of the present invention. 9 is a table showing an example of call state information and a call state transition determination function in a “BT (Busy Tone)” state in the call state transition scenario according to the embodiment of the present invention. 6 is a table showing an example of virtual telephone information according to the embodiment of the present invention. 6 is a table showing an example of virtual telephone group information according to the embodiment of the present invention. 5 is a table showing an example of numbering plan information according to the embodiment of the present invention. 4 is a table showing an example of trunk service information according to the embodiment of the present invention. FIG. 1 is a diagram showing a configuration example of a private branch exchange system using a private branch exchange according to an embodiment of the present invention. It is a figure which shows the example of an operation | movement flow when the off-hook of the extension is detected in embodiment of this invention. FIG. 1 is a diagram showing a configuration example of a private branch exchange when there are a plurality of private branch exchanges according to an embodiment of the present invention. It is a figure which shows the example of the operation flow at the time of implementing an extension call in embodiment of this invention.

(Outline of the invention)
Private branch exchanges provide a wide variety of telephone services, but actual users often do not use all the telephone services prepared by the manufacturer, but only use some services. Further, if attention is paid only to the voice connection pattern, it is almost the case that there are only two types of “connecting” and “vacant”, or three types including “reserved”. Therefore, if the call state and the state transition can be simplified and provided, the user can program the operation of the private branch exchange. In addition, instructions for call state transitions, which are the processing results, are given to extensions and trunks accommodated in private branch exchanges of manufacturers, peripheral devices and hardware that provide special services such as three-way conferences, multi-party conferences, and announcements. If it is possible to support, it will be possible to provide telephone services that go beyond the boundaries of manufacturers and models.

  In the present invention, in order to function regardless of differences in the specifications of the hardware of the private branch exchange, the extension or trunk to be accommodated, the interface, etc., special services such as extension or trunk, three-way conference, multi-party conference or announcement are provided. Virtualize the provided peripherals.

  Specifically, the processing of the private branch exchange is performed by the local control unit that directly controls the hardware, extension, trunk, and peripheral device, and by the user control unit that controls the extension, trunk, and peripheral device in a virtualized state. It divides into processing.

  The user control unit changes the call state according to the "call state transition scenario". The "call state transition scenario" includes "call state information" that defines transmission / reception of voice in each call state such as "two-way call" and "holding", screen display, etc. The condition for the state transition from the call state A to the call state B is determined by the "call state transition determination function" for each "call event" such as call, off-hook, hooking, and dialing.

  The "call state information" is input to the "call state transition determination function" defined for each "call event", and the next designation of the "call state" is output. The logic from the input to the output is created by the user.

  The database for operating the peripheral device is called “call service information” here, but the “call service information” is also created by the user and used in the “call state transition determination function”.

  The local control unit monitors the call event of the peripheral device, and when the call event occurs, notifies the user control unit of the "call state information" and the "call event information" of the peripheral device. The state of the peripheral device is changed according to the call state transition instruction given by the user control unit.

  If the local control unit of the private branch exchange can recognize the interface with the user control unit, it is possible to provide a service by coexisting a plurality of private branch exchanges of different manufacturers and models.

(First embodiment)
A first embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram of a private branch exchange 100 according to the present invention. The private branch exchange 100 provides a user control unit 110 that can be set / programmed by the user from the outside of the private branch exchange 100, and a special service such as an extension, a trunk, a three-way conference, another party conference, and an announcement accommodated in the private branch exchange 100. And a local control unit 120 that directly controls the provided peripheral device. It should be noted that although the constituent elements that are indispensable for the ordinary private branch exchange to operate normally are not shown in the figure, the private branch exchange 100 naturally includes such constituent elements.

  The user control unit 110 includes at least a call state transition scenario 111 including call state information that defines a call state of a peripheral device and a transition scenario of the call state, and a call state transition determination function that reflects the call state transition scenario 111. It holds the call service information 112 to be used.

  The local control unit 120 controls the hardware accommodated in the private branch exchange 100, the hardware control unit 121, the extension control unit 122 which controls the extension accommodated in the private branch exchange 100, and the trunk which is accommodated in the private branch exchange 100. In addition to the trunk control unit 123, the control unit 12X that manages and controls one or more peripheral devices XXX is included. For example, when the telephone connected to the extension goes off-hook, on-hook, or dials, the extension control unit 122 in the local control unit 120 detects the call event of the extension, and the local control unit 120 detects the call event. The extension state is replaced with the virtualized call event information and call state information, and the user control unit 110 is notified.

  The user control unit 110 uses the call event information and the call state information notified from the local control unit 120, and the call state transition scenario 111 and the call service information 112 stored in the user control unit 110, and the new state of the call. Then, the local control unit 120 is notified of the call state transition instruction and the new call state information. The local control unit 120 controls the actual extension according to the call state transition instruction of the virtualized extension notified from the user control unit 110 and the new call state information.

  Here, a call state transition scenario will be described with reference to FIGS. 2 and 3-1 to 3-7.

  FIG. 2 is a conceptual diagram of a call state transition scenario. Specifically, extension A, which is in the "J000 extension free" state, goes to the "J001 1st DT" state by going off-hook, and further, when the dialing to extension B is started, it becomes the "J002 dialing" state. Become. After that, by dialing all the digits to the extension B, if the extension B is empty, both the extension A and the extension B are in the "J003 extension call" state, and if the extension B is busy, the extension A Becomes the state of “J006 BT”. If B answers after the state of "J003 extension call", both extension A and extension B are in the state of "J004 two-way call". After that, when one of the extension A and the extension B goes on hook, one of them returns to the state of "J000 extension free", and the other goes through the state of "J005 ROT" and returns to the state of "J000 extension free" after on-hook. Note that "A" and "B" in the figure represent related extensions and trunks, and "A" described in the boxes indicating call states J000 to J006 indicate that they are the same extension. .. The user defines each call state from J000 to J006 and adds new call states if necessary. Furthermore, the user reflects the above call state transition scenario and uses the call state information notified from the local control unit 120, whether the transition between call states is possible, the call service information created by the user himself, etc. Create a call state transition determination function that is a function that determines

  FIGS. 3-1 to 3-7 are tables showing call state information in each call state that constitutes the above call state transition scenario, and a call state transition determination function used when each call event occurs in each call state. .

  Explaining FIG. 3A as an example, FIG. 3A shows call state information and a call state transition determination function in the call state of “J000 extension free” in the conceptual diagram of FIG. Here, "J000" is a symbol that is assigned so that the types of calls can be distinguished, and the symbol may be uniquely defined by the user. Further, “J000-A-S1” described in FIG. 3A is a symbol for identifying a call state, “A” indicates a device in the call state, and “S1” is an extension. Indicates the type. In FIG. 3A, depending on the type of extension, there are “S1” call state information and a call state transition determination function, and “S2” call state information and a call state transition determination function. This is because the available services and operations differ depending on the characteristics of the telephone, such as analog telephones, multi-function telephones, PHS, and softphones, and even if the same telephone is off-hook, an extension that directly calls a specific extension is available. This is because there is a case in which there is a common state transition. Along with this, a call state and a call state transition determination function are separately defined for each extension of “S1” and “S2”.

  The information from the line of "voice transmission 1" to the line of "valid call event" in FIG. 3A is information that can be recognized by both the user control unit 110 and the local control unit 120, and the user control It is also information notified from the unit 110 to the local control unit 120 together with the call state transition instruction.

  There are two types of "voice transmission 1" and "voice transmission 2" in "voice transmission" in Fig. 3-1, because it is assumed that voice is transmitted to a plurality of opponents. It is possible to define any number of "voice transmissions". Further, it is possible to define an arbitrary number of “voice receptions” for “voice reception 1”.

  The "timer" in FIG. 3-1 is information indicating the time remaining in the "J000 extension free" which is the call state of FIG. 3-1. In Fig. 3-1, the "timer" is "none", but in "J001 1stDT" of Fig. 3-2, the "timer" is "12 seconds", which is the 1stDT call state. Indicates the maximum time allowed. When 12 seconds has passed, the next call state is entered.

  The information in the row of “Valid call event” in FIG. 3-1 defines the call event that is valid in the state of “J000 extension free”, and when the call event occurs, “Call event occurrence The call state transition determination function "is used to determine the new state of the call. When a call event that is not defined as valid occurs, the call event is not notified to the user control unit 110, and the current call state is maintained.

  Next, the call service information will be described. 4-1 to 4-4 are examples of call service information. FIG. 4A is a table showing accommodation destinations of virtualized telephones, types of extensions, and service groups to which the telephones belong. FIG. 4-2 is a table showing each service group in which virtualized telephones are grouped. FIG. 4-3 is a table showing what kind of functions each number used in the private branch exchange system has and in what case it becomes effective. FIG. 4-4 is a table showing accommodation destinations and types of each trunk group. The call service information includes a database for operating extensions, trunks, and peripherals accommodated in the private branch exchange, and a database for determining whether to enable or disable the service according to which extension, Each of them can be newly defined, created, and modified by the user.

  Next, as will be described in detail later, the operation when the telephone set connected to the extension A (S1) is “off hook” in the “J000 extension free” state shown in FIG. 3A will be briefly described.

  When the local control unit 120 notifies the user control unit 110 of the call event information of “off-hook” in the telephone connected to the extension A (S1), the “when a call event occurs” illustrated in FIG. In the "call state transition determination function", the call state transition determination function PJ000A_S1_1 corresponding to "off-hook" is activated. This PJ000A_S1_1 is a function designed in advance by the user. By inputting the "call status information" of the extension A to this function, and if necessary, by referring to the database of "call service information" shown in FIGS. 4-1 to 4-4 from this function. , The extension A (S1) is set to "J001 1st DT". The user control unit 110 reads the call state information of the extension A (S1) of J001-A-S1 in “J001 1st DT” of FIG. 3-2 and notifies the local control unit 120 of the call state information. The local control unit 120 changes the extension A (S1) to the call state indicated by the call state information and waits for the next call event. Here, since the above PJ000A_S1_1 is a function designed in advance by the user, it is also possible to determine a transition instruction to a call state other than J001 by the design of the user.

  As described above, the local control unit 120 notifies the user control unit 110 of the call event information and the call state information, and the call state transition determination function is used to connect a certain call state and another call state. , There may be a case where the call service cannot be continued anymore due to logical contradiction, hardware failure, program abnormality, etc. In consideration of such a possibility, "J000 extension free" also serves as a call state for initializing the extension. If the call service cannot be continued anymore due to the above logical inconsistency, hardware failure, program error, etc., it is forcibly returned to the "J000 extension free" state to recover from the abnormal state, and It is possible to restart after restoration.

  Next, the operation of the present invention will be described using the private branch exchange system shown in FIG. 5 as an example.

  In the private branch exchange system shown in FIG. 5, private branch exchanges 100A, 100B, and 100C are connected on the same IP network.

  Further, the private branch exchange 100A accommodates the extension line 11A, the extension line 12A, and the office line 21A. The private branch exchange 100B accommodates the extension line 11B, the extension line 12B, and the office line 21B. The private branch exchange 100C accommodates the extension 11C, the extension 12C, the office line 21C, and the dedicated line 41C.

  The extension 11A, the extension 12A, and the office line 21A accommodated in the private branch exchange 100A are all directly connected to the IP network.

  The extension 11B, the extension 12B, and the office line 21B accommodated in the private branch exchange 100B are all accommodated in dedicated hardware in the private branch exchange 100B, and voice connection with the IP network is made via a gateway 31B which is a VoIP gateway device. Is possible.

  The extension 12C and the leased line 41C accommodated in the private branch exchange 100C are directly connected to the IP network, but the extension 11C and the office line 21C are accommodated in the dedicated hardware in the private branch exchange 100C and are the VoIP gateway devices. A voice connection with an IP network is possible via a gateway 31C.

  The operation until the telephone set connected to the extension 11A housed in the private branch exchange 100A goes "off hook" and sends "1stDT" will be described with reference to the flowchart of FIG.

  The extension 11A is in the "J000 extension free" state in FIG. When the telephone connected to the extension 11A goes off-hook, the local control unit 120 detects the call event "off-hook" of the extension 11A (STEP 1001) and informs the user control unit 110 of the call event "off-hook" of the extension 11A and the extension 11A. The current "call status information" is notified (STEP 1002).

  The user control unit 110 recognizes from the "call state information" of the extension 11A that the state is "J000 extension free", and reads the "J000 extension free" table in FIG. 3-1 during the call state transition scenario. Further, from the "virtual telephone information" in FIG. 4-1, it is recognized that the extension type of the telephone connected to the extension 11A (here, the telephone with the telephone number 30000) is S1, and " The call state transition determination function PJ000A_S1_1 of J000-A-S1 is activated from the table of "J000 free extension". The call state transition function PJ000A_S1_1 determines the next call state to be "J001 1stDT" based on the call state information and the like (STEP 1003).

  After that, the user control unit 110 inquires of the local control unit 120 whether it is possible to make a call state transition to a new call state "J001 1stDT" (STEP 1004).

  If the local control unit 120 returns a "transition OK" response to the user control unit 110 (STEP 1005), the call state transition instruction "J001 1st DT" of the extension 11A is transmitted to the local control unit 120 (STEP 1006).

  Upon receiving the call state transition instruction, the local control unit 120 controls the extension 11A so that the call state is as instructed (STEP 1007).

  Next, in the telephone connected to the extension 11A accommodated in the private branch exchange 100A, the operation at the time of dialing the number of the extension 11B accommodated in the private branch exchange 100B, that is, "J002" of "Call state transition scenario" The operation from "during dialing" to "J003 extension call" will be described. As described above, in this case, even between exchanges of different manufacturers and models, the local control unit of the other private branch exchange recognizes the "call state transition instruction" and "call state information" from one private branch exchange. If possible, as shown in FIG. 7, the user control unit 110A of the private branch exchange 100A can directly give an instruction to the local control unit 120B of the private branch exchange 100B.

  First, when the last digit of the extension 11B is dialed on the telephone connected to the extension 11A, the local control unit 120A detects the call event (STEP 2001).

  Subsequently, the local control unit 120A notifies the user control unit 110A of the above-mentioned call event "dial" and "dial number" and "call state information" (STEP 2002).

  The user control unit 110A refers to the table of "J002 dialing" in Fig. 3-3 from the "call state information" of the extension 11A that has been notified, and in the "call state transition function at the time of call event occurrence" The function PJ002A_S1_1 corresponding to "dial" is activated. The function PJ002A_S1_1 refers to the call service information 112A, determines that the dial destination is the extension 11B accommodated in the private branch exchange 100B, and determines to call the extension 11B (STEP2003). For example, when the “dialed number” is “20130”, it can be seen from the table in FIG. 4-3 that “20130” is a 5-digit extension. Further, it can be seen that the telephones with telephone numbers shown in FIGS. 4-1 to 20130 are telephones accommodated in the private branch exchange 100B and the extension type is S1.

  The user control unit 110A inquires of the local control unit 120B accommodating the extension 11B and the local control unit 120A accommodating the extension 11A as to whether or not the transition to "J003 extension call" is possible (STEP 2004 and STEP 2005).

  Upon receiving a reply of "transition OK" from both parties (STEP 2006 and STEP 2007), the user control unit 110A makes a call state transition to the local control unit 120B accommodating the extension 11B and the local control unit 120A accommodating the extension 11A. The instruction is transmitted (STEP 2008 and STEP 2009).

  Upon receiving the call state transition instruction, the local control unit 120B and the local control unit 120A control the extension 11B and the extension 11A, respectively, so that the call state is as instructed (STEP 2010 and STEP 2011).

  After that, the operation after the operation described in the flowchart of FIG. 8 is performed. However, when the telephone connected to the extension 11B answers the call from the extension 11A, the local control unit 120B sends the extension 11B to the user control unit 110A. Notifies that the telephone connected to is off-hook and the call state information of the extension 11B. The user control unit 110A instructs both the extension 11A and the extension 11B to transition to the call state of “J004 two-way call” shown in FIG. 3-5 in the call state transition scenario.

  The local control unit 120A of the private branch exchange 100A instructs the extension 11A to connect to the extension 11B, but since the local control unit 120B of the private branch exchange 100B is not directly connected to the IP network, it goes through the gateway 31B. The extension 11B is connected.

  Information such as an IP address required for these connections is notified at the same time when the "transition OK" is returned from the local control units 120A and 120B after confirming the call state transition.

  In the above description, when the telephone connected to the extension 11B answers the call from the extension 11A, the local control unit 120B notifies the user control unit 110A that the telephone is off-hook. The unit 110B may be notified. In this case, the user control unit 110B has the same specifications as the user control unit 110A, and needs to have the same database as the user control unit 110A.

(Other embodiments)
In the first embodiment, each private branch exchange has the user control unit. However, the user control unit may be mounted only on one private branch exchange of a plurality of private branch exchanges. Further, the user control unit may be mounted on a PC or server on the same IP network instead of the private branch exchange. On the contrary to the above, a plurality of user control units may be arranged on the IP network.

  In consideration of user convenience, a call state transition determination function and a database sample may be prepared in advance for telephone services that are frequently used. The user may use the samples of the functions and the database as they are, or customize and use them.

  According to the first embodiment and other embodiments described above, a unified telephone service can be provided regardless of the manufacturer and model of the private branch exchange.

  Further, it is possible to form an extension representative across a plurality of private branch exchanges and to receive an incoming call to a telephone housed in another private branch exchange by a call pickup. Even for services that span multiple private branch exchanges, telephone services can be provided as if they are accommodated in one private branch exchange without using a leased line interface.

  Furthermore, when replacing an old private branch exchange with a new private branch exchange, even if it is replaced with a private branch exchange of another manufacturer, the same database can be used and the same service can be used.

  In addition, users can create new call states and new services by building and programming databases themselves.

  Each part of the private branch exchange and the private branch exchange system can be realized by either hardware, software, or a combination thereof. Further, the switching method performed by the above network switch can also be realized by hardware, software, or a combination thereof. Here, to be realized by software means to be realized by a computer reading and executing a program, or by hardware operating according to microcode corresponding to the program.

  The program can be stored in various types of non-transitory computer readable media and can be supplied to the computer. Non-transitory computer readable media include various types of tangible storage media. Examples of the non-transitory computer readable medium include a magnetic recording medium (eg, flexible disk, magnetic tape, hard disk drive), magneto-optical recording medium (eg, magneto-optical disk), CD-ROM (Read Only Memory), CD- R, CD-R / W, and semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (random access memory)) are included. In addition, the program may be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The transitory computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

  The whole or part of the exemplary embodiments disclosed above can be described as, but not limited to, the following supplementary notes.

(Appendix 1)
A private branch exchange,
A local control unit that controls one or more peripheral devices connected to the private branch exchange, acquires call event information and first call status information in the peripheral devices, and virtualizes the peripheral devices.
From the local control unit, receives the call event information and the first call state information of the virtualized peripheral device, and based on the received call event information and the first call state information, And a user control unit for transmitting a call state transition instruction to the peripheral device and second call state information indicating the call state of the transition destination to the local control unit,
The private branch exchange, wherein the local control unit controls the peripheral device based on the call state transition instruction and the second call state information received from the user control unit.

(Appendix 2)
The private branch exchange described in Appendix 1,
The user control unit instructs the local control unit of the other private branch exchange to make a call state transition to one or more peripheral devices connected to the other private branch exchange, and the second call state in the call state of the transition destination. A private branch exchange characterized by transmitting information.

(Appendix 3)
A private branch exchange according to appendix 1 or 2,
When the user control unit determines a call state transition instruction for the peripheral device and the second call state information based on the call event information of the virtualized peripheral device and the first call state information. , Inputting and outputting at least one of virtual telephone information, virtual telephone group information, numbering plan information, and trunk service information for a call state transition function defined in advance reflecting a call state transition scenario. A private branch exchange characterized by using results.

(Appendix 4)
The private branch exchange according to any one of appendices 1 to 3,
The call state transition function, the virtual telephone information, the virtual telephone group information, the numbering plan information, and the trunk service information are set and changed by a user of the private branch exchange from outside the private branch exchange. Private branch exchange.

(Appendix 5)
A private branch exchange according to any one of appendices 1 to 4,
A private branch exchange system comprising: one or more peripheral devices connected to the private branch exchange.

(Appendix 6)
A first private branch exchange according to any one of appendices 1 to 4,
One or more peripherals connected to the first private branch exchange;
A second private branch exchange connected to the first private branch exchange;
And one or more peripheral devices connected to the second private branch exchange,
The second private branch exchange comprises a second local control unit for controlling the one or more peripheral devices connected to the second private branch exchange,
The user controller of the first private branch exchange calls the second local controller of the second private branch exchange for calls to the one or more peripheral devices connected to the second private branch exchange. Send the state transition instruction and the call state information in the call state of the transition destination,
The second local control unit of the second private branch exchange controls the one or more peripheral devices connected to the second private branch exchange based on the received call state transition instruction and the call state information. Private exchange system.

(Appendix 7)
The private branch exchange system according to attachment 5 or 6,
A private branch exchange system characterized in that all private branch exchanges are on the same IP network.

(Appendix 8)
A control method used in a private branch exchange,
A step in which the local control unit controls at least one peripheral device connected to the private branch exchange, acquires call event information and first call state information in the peripheral device, and virtualizes the peripheral device; When,
A user control unit receives the call event information and the first call status information of the virtualized peripheral device from the local control unit, and the received call event information and the first call status information. A call state transition instruction to the peripheral device, and a step of transmitting second call state information in the call state of the transition destination to the local control unit,
The said local control part has the step which controls the said peripheral device based on the said call state transition instruction | indication received from the said user control part, and the said 2nd call state information, The control method characterized by the above-mentioned.

(Appendix 9)
A control program used in a private branch exchange,
Computer,
A local control unit that controls one or more peripheral devices connected to the private branch exchange, acquires call event information and first call status information in the peripheral devices, and virtualizes the peripheral devices.
Receiving the call event information and the first call status information of the virtualized peripheral device from the local control unit, and based on the received call event information and the first call status information, the peripheral A call state transition instruction to the device, and functioning as a user control unit that transmits the second call state information in the call state of the transition destination to the local control unit,
The control program, wherein the local control unit controls the peripheral device based on the call state transition instruction and the second call state information received from the user control unit.

  The invention can be used in the field of private branch exchanges. Further, it can be used in the field of inter-office service.

11A 12A 11B 12B 11C 12C Extension 21A 21B 21C Station line 31B 31C Gateway 41C Private line 100 100A 100B 100C Private branch exchange 110 110A 110B User control unit 111 Call state transition scenario 112 Call service information 120 120A 120B Local control unit 121 Hardware control unit 122 Extension Control Unit 123 Trunk Control Unit 12X XXX Control Unit

Claims (9)

A private branch exchange,
A local control unit that controls one or more peripheral devices connected to the private branch exchange, acquires call event information and first call status information in the peripheral devices, and virtualizes the peripheral devices.
From the local control unit, receives the call event information and the first call state information of the virtualized peripheral device, and based on the received call event information and the first call state information, And a user control unit for transmitting a call state transition instruction to the peripheral device and second call state information indicating the call state of the transition destination to the local control unit,
The private branch exchange, wherein the local control unit controls the peripheral device based on the call state transition instruction and the second call state information received from the user control unit. The private branch exchange according to claim 1,
The user control unit instructs the local control unit of the other private branch exchange to make a call state transition to one or more peripheral devices connected to the other private branch exchange, and the second call state in the call state of the transition destination. A private branch exchange characterized by transmitting information. A private branch exchange according to claim 1 or 2, wherein
When the user control unit determines a call state transition instruction for the peripheral device and the second call state information based on the call event information of the virtualized peripheral device and the first call state information. , Inputting and outputting at least one of virtual telephone information, virtual telephone group information, numbering plan information, and trunk service information for a call state transition function defined in advance reflecting a call state transition scenario. A private branch exchange characterized by using results. The private branch exchange according to claim 3 ,
The call state transition function, the virtual telephone information, the virtual telephone group information, the numbering plan information, and the trunk service information are set and changed by a user of the private branch exchange from outside the private branch exchange. Private branch exchange. A private branch exchange according to any one of claims 1 to 4,
A private branch exchange system comprising: one or more peripheral devices connected to the private branch exchange. A first private branch exchange using the private branch exchange according to any one of claims 1 to 4;
One or more peripherals connected to the first private branch exchange;
A second private branch exchange connected to the first private branch exchange;
And one or more peripheral devices connected to the second private branch exchange,
The second private branch exchange comprises a second local control unit for controlling the one or more peripheral devices connected to the second private branch exchange,
The user controller of the first private branch exchange calls the second local controller of the second private branch exchange for calls to the one or more peripheral devices connected to the second private branch exchange. Send the state transition instruction and the call state information in the call state of the transition destination,
The second local control unit of the second private branch exchange controls the one or more peripheral devices connected to the second private branch exchange based on the received call state transition instruction and the call state information. Private exchange system.

The private branch exchange system according to claim 5 or 6, wherein
A private branch exchange system characterized in that all private branch exchanges are on the same IP network. A control method used in a private branch exchange,
A step in which the local control unit controls at least one peripheral device connected to the private branch exchange, acquires call event information and first call state information in the peripheral device, and virtualizes the peripheral device; When,
A user control unit receives the call event information and the first call status information of the virtualized peripheral device from the local control unit, and the received call event information and the first call status information. A call state transition instruction to the peripheral device, and a step of transmitting second call state information in the call state of the transition destination to the local control unit,
The said local control part has the step which controls the said peripheral device based on the said call state transition instruction | indication received from the said user control part, and the said 2nd call state information, The control method characterized by the above-mentioned. A control program used in a private branch exchange,
Computer,
A local control unit that controls one or more peripheral devices connected to the private branch exchange, acquires call event information and first call status information in the peripheral devices, and virtualizes the peripheral devices.
Receiving the call event information and the first call status information of the virtualized peripheral device from the local control unit, and based on the received call event information and the first call status information, the peripheral A call state transition instruction to the device, and functioning as a user control unit that transmits the second call state information in the call state of the transition destination to the local control unit,
The control program, wherein the local control unit controls the peripheral device based on the call state transition instruction and the second call state information received from the user control unit.

Images