JP2006050198A - Telephone exchange testing device, and method thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a telephone exchange testing device suitable for testing a telephone exchange function to be performed in response to an API, and to provide its method. <P>SOLUTION: When various kinds of information are set, a PC 42 issues the first API to a PBX server 24. The PC 42 gives a time stamp to the issued API, etc., so as to define it as a log. When the PBX server 24 transmits a control command to the PBX 20 in response to the received API, the PBX 20 returns an event, etc., corresponding to the control command. The PBX server 24 transmits the returned event to the PC 42. The PC 42 gives the time stamp to the event, etc., from the PBX server 24 and defines it as the log. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a telephone exchange testing apparatus and method for testing a telephone exchange.

Services that provide various telephone exchange functions to users by controlling telephone exchanges with computers have been put into practical use.
In order to use this service, the application software running on the user's computer issues an API (Application Programming Interface) to the computer that controls the telephone exchange, thereby executing the telephone exchange function. Become.

Further, for example, Patent Documents 1 to 3 disclose a method for testing a telephone exchange.
However, none of the above patent documents discloses a method suitable for testing a telephone exchange function performed in accordance with an API.
JP 2000-353107 A JP 2000-354263 A JP 2001-268226 A

  The present invention has been made from the above background, and it is an object of the present invention to provide a telephone exchange testing apparatus and method suitable for testing a telephone exchange function performed in accordance with an API.

  In order to achieve the above object, a telephone exchange test apparatus according to the present invention is a telephone exchange test apparatus for testing a telephone exchange that performs call control for a call according to an API (Application Programming Interface) from the outside. Call control information accepting means for accepting call control information necessary for the telephone exchange, an API corresponding to the accepted call control information is issued to the telephone exchange, and the telephone exchange testing means for testing the telephone exchange; Log creating means for creating a log including at least the issued API and the time when the API was issued;

  Preferably, the telephone exchange further includes response accepting means for returning a response according to the API from the outside to the outside and accepting a response returned from the telephone exchange, and the log creating means is , Further creating a log including at least the accepted response and a time at which the response was accepted.

  Preferably, the call control information accepting means includes call management information used for managing the call, operation information indicating an operation performed for the call, and state information indicating the state of the call. Are accepted as the call control information including one or more combinations of the above.

  Preferably, the call control information accepting unit displays the call control information, accepts an operation for the displayed call control information, and generates the call control information according to the accepted operation.

Preferably, the call management information is attached to a telephone information specifying a telephone accommodated in the telephone exchange, a user identifier of a user of the telephone exchange, a machine constituting the telephone exchange and relating to a call. A machine identifier, a password to access the switch, and
Including the call identifier, or any one or more combinations thereof.

  Preferably, the operation information includes telephone identification information for identifying a telephone accommodated in the telephone exchange, dial operation, hold operation, consultation operation, response operation, reacquisition operation, conference operation for the identified telephone, And telephone operation information including a transfer operation and an unconfirmed transfer operation or any one or more combinations thereof.

  The telephone exchange test method according to the present invention is a telephone exchange test method for testing a telephone exchange that performs call control for calls in accordance with an external API (Application Programming Interface), the call control information required for the call control. And issuing an API according to the accepted call control information to the telephone exchange, testing the telephone exchange, and including at least the issued API and a time when the API was issued Create a log.

  Preferably, the telephone exchange further returns a response according to the API from the outside to the outside, further accepts the response returned from the telephone exchange, and the accepted response and the response are accepted. A log including at least the recorded time is created.

  The program according to the present invention is a program for testing a telephone exchange that performs call control for calls in accordance with an external API (Application Programming Interface), and accepts call control information necessary for call control. A telephone switch test step of issuing an API according to the accepted call control information to the telephone switch and testing the telephone switch; the issued API; and the API being issued And causing the computer to execute a log creating step for creating a log including at least the time.

  Preferably, the telephone exchange further returns a response according to the API from the outside to the outside, further causes the computer to execute a response accepting step for accepting the response returned from the telephone exchange, and the log generation The step further creates a log including at least the accepted response and the time when the response was accepted.

  ADVANTAGE OF THE INVENTION According to this invention, the telephone switch testing apparatus suitable for the test of the telephone switching function performed according to API, and its method are provided.

  Hereinafter, the best embodiment of the present invention will be described.

[Telephone communication system 1]
FIG. 1 is a diagram illustrating a telephone communication system 1 to which a telephone exchange test according to the present invention is applied.
As shown in FIG. 1, a telephone communication system 1 includes a private branch exchange (PBX) 20 connected to another person's telephone or the like (another communication node 122) via a network 120 such as a public telephone network. , A PBX server 24 that controls the PBX 20, and a call center 3 that performs telephone communication with the communication node 122.

The call center 3 includes one or more call desks 4-1 to 4-k (k ≧ 1).
In the following, in the telephone communication system 1, when a plurality of components are collectively described as “call desks 4-1 to 4-k”, they are simply abbreviated as “call desk 4”. There are things to do.
In addition, the components of the telephone communication system 1 such as the communication node 122, the PBX 20, the PBX server 24 (the PBX 20 and the PBX server 24 may be configured integrally), and the PC 42 may be collectively referred to simply as a node. is there.

The call center 3 is used, for example, for communication by telephone between an operator and a user in a computer manufacturer.
Each of the call desks 4 includes a telephone 40 and a computer (PC) 42.
The telephone 40 is a multi-function telephone for the PBX 20 that includes, for example, button switches and display devices for using various functions. The telephone 40 is connected to the PBX 20 and communicates with other telephones 40 or communication nodes 122. Used for calls.
The PC 42 is connected to the PBX server 24 via a LAN (not shown) or the like, and is used for operations on the PBX server 24.

The telephone communication system 1 provides various functions to the operator and the user of the communication node 122 by these components.
That is, in the telephone communication system 1, a function realized by cooperation between the PBX 20 and the PBX server 24 is provided.
As an example of functions realized by the cooperation between the PBX 20 and the PBX server 24, for example, the control from the PBX server 24 to the PBX 20 is performed according to the operation on the PBX server 24 from the PC 42 of each call desk 4 of the call center 3. Each time a call between the operator and the user of the communication node 122 is completed in the order on the list of the communication nodes 122 created in advance, an automatic call is made to each of the plurality of communication nodes 122. Function can be mentioned.

[PBX20]
FIG. 2 is a diagram illustrating the configuration of the PBX 20 shown in FIG.
As shown in FIG. 2, the PBX 20 includes network interfaces (network IFs) 200-1 to 200-m, a speech path switch 202, a call control device 204 (described later with reference to FIG. 3), and telephone IFs 206-1 to 206-. n (m, n ≧ 1).

With these components, the PBX 20 performs call control according to the control command from the PBX server 24 and provides a telephone communication function between the telephone 40 and the communication node 122.
In addition, the PBX 20 informs the PBX server 24 of information indicating these events (hereinafter referred to as “events”) every time an event such as a successful call path setting, a setting failure, a call origination, and a call termination occurs. Output).

In the PBX 20, the call control device 204 controls each component of the PBX 20 according to a control command from the PBX server 24 and performs call control.
The network IF 200 provides an interface function between the communication node 122 (FIG. 1) and the speech path switch 202 and the call control device 204.

The speech path switch 202 sets a speech path between the network IF 200 and the telephone IF 206 under the control of the call control device 204, and exchanges PCM voice data between them.
In the following description, a case where the speech path switch 202 performs line switching and PCM voice data exchange will be described as a specific example. However, the speech path switch 202 may perform storage exchange of packetized voice data.
The telephone IF 206 provides an interface function between the telephone 40 and the communication path switch 202 and the call control device 204.

[Event]
The events that the PBX 20 outputs to the PBX server 24 are, for example, as follows.
These event handler specifications are, for example, API specifications defined in http://www.cisco.com/univercd/cc/td/doc/product/icm/icm46/cti/geodcstk/dcserver.pdf It is along.

(1) New Call (call identification number, destination telephone number, incoming telephone number, caller information)
OnNewCallAppearance2 ():
OnNewCallAppearance2 () is a function activated by an event notified to the client application by the COM server called the DCS server when an event of the PBX server 24 is transmitted to the PC 42, and a pointer indicating the call object and CallAppearance2 is handled as an argument. To take.
In addition to the arguments (telephone number, caller information), parameters such as a device number, customer number, and priority may be attached to this COM object according to the configuration of the ICM.
(2) End Call (call identification number)
OnEndCallAppearance2 ():
As with OnNewCallAppearance2, it takes a pointer indicating CallAppearance2 as an argument.

(3) OnSuccess ():
OnSuccess () is a function activated by an event notifying that the API call processing via the DCS_API has succeeded, and takes an API call identifier as an argument.
For example, the success notification of the call to MakeCall () is OnSuccess (eMakeCallMethod), and the success notification of the call to AnswerCall () is OnSuccess (eAnswerCallMethod).
Whether or not a processing request is transmitted by each call is returned as a return value, but a series of processing is performed on the PBX 20 side, and success or failure is notified thereafter.

(4) OnFailure ():
(5) OnControlFailure ():
(6) OnControlFailureEx ():
OnFailureConf (), OnControlFailureConf (), OnControlFailureConfEx () take the same arguments as OnSuccess () as described in the above documents 4-18 to 4-19, but DCS_API is implemented with an identifier without Conf unlike the manual. It had been.
Therefore, in Phone1.5, messages are in line with the implementation, such as OnFailure (enumBrainMethodType mtype, long FailureCode), OnControlFailure (enumBrainMethodType, long ControlFailureCode), OnControlFailureEx (enumBrainMethodType, long ControlFailureCode, long PeripheralErrorCode),

  For example, the failure notification message for MakeCall () is actually OnControlFailure (eMakeCallMethod, FailureCode == 0), and the failure notification message for RetrieveCall () is OnControlFailure (eRetrieveCallMethod, ControlFailureCode == 13) And OnControlFailureEx (eRetrieveCallMethod, ControlFailureCode == 13, PeripheralErrorCode == 0).

(7) AgentStateChange (extension number, person in charge identifier, operator state identifier):
OnAgentStateChange (): This event is notified from the PBX 20 when the state of the operator, in particular, the state as an index indicating whether or not the incoming call can be delivered to a number serving as a queue changes.
The PBX server 24 (ICM and its DCS subsystem) notifies each client application (Phone1.5 is one of them) of the event by calling the event handler OnAgentStateChange () registered by the PBX server 24 (ICM and its DCS subsystem).
In addition to the above, a password and a physical extension number may be included.

(8) UpdateCurrentCallStatus (call identification number, call status identifier):
OnUpdateCurrentCallStatus: Indicates that the current call status has changed.

In (7) AgentStateChange (), the following states (1) to (11) may be included as additional information.
For example, the PBX server 24 that has received AgentStateChange calls the event handler OnAgentStateChange () registered by the client application with a call ID and a flag indicating the state.

(1) eLogin: The state where the operator has logged in to the PBX server 24.
(2) eLogout: The state where the operator has logged out from the PBX server 24.
(3) eNotReady: the operator is not ready for delivery of calls from the queue.

(4) eTalking: The operator is on a call.
Whether or not another call can be received during a call, which indicates that the operator is talking, not that the call is not received in the sense that another call cannot be received, depends on the type, setting and operation of the PBX 20. Dependent.

(5) eAvailable: A state in which the operator can use the call delivery destination from the queue.
(6) eWorkNotReady: The operator is working and not ready for call delivery from the queue.
(7) eWorkReady: The operator is working but is ready for call delivery from the queue.

(8) eBusyOther: The operator is busy with other factors and cannot receive calls from the queue.
(9) eReserved: A state in which the operator is reserved for subsequent processing of the PBX server 24.

(10) eUnknown: The operator is in an unknown state to the PBX server 24.
(11) eHold: The operator is on hold.

[PBX server 24, PC 42, call control device 204]
FIG. 3 is a diagram illustrating the configuration of the PBX server 24, the PC 42 shown in FIG. 1, and the call control device 204 of the PBX 20 shown in FIG.
As shown in FIG. 3, the PBX server 24 and the PC 42 include a CPU 102, a memory 104, a main body 100 including a timer (not shown) for generating time information, an input / output device 106 including a display device and a keyboard, and the like. It comprises a communication device 110 that communicates with a node, a recording device 112 such as a CD device / HDD, and a function realization unit 118 that provides an interface function between the call control device 204 and the communication path switch 202.

  That is, the PBX server 24, the PC 42, and the call control device 204 have a component as a computer having a communication function with other nodes and a function specific to each node.

[PBX control program 240]
FIG. 4 is a diagram showing a PBX control program 240 operating on the PBX server 24 shown in FIGS.
As shown in FIG. 4, the PBX control program 240 includes a PBX-IF unit 242, a PBX control unit 244, a PC-IF 246, a log management unit 248, and a log database unit (log DB unit) 250.
The PBX control program 240 is supplied to the PBX server 24 via the recording medium 114 (FIG. 3), loaded into the memory 104 and executed (the same applies to the following programs).

In the PBX control program 240, the PBX-IF unit 242, the PBX control unit 244, and the PC-IF 246 have received and received an API (Application Programming Interface) from the PC 42 (FIGS. 1 and 3) and an event from the PBX 20. A control command for causing the PBX 20 to perform call control corresponding to the API and the event is generated and output to the call control device 204 (FIG. 2) of the PBX 20.
Further, the PBX-IF unit 242, the PBX control unit 244, and the PC-IF 246 output the return value for the API from the PC 42 and the event received from the PBX 20 to the PC 42 together with the accompanying information.

The return value will be described.
When the test program 44 running on the PC 42 makes an API call to send a specific request to the PBX server 24, the PBX server 24 accepts the request and redraws it to the corresponding processing request to the PBX 20. And execute.
The return value is a value indicating whether or not the API call is successful, and if it fails, at what stage and how it failed. In the case of DCS_API, an integer type return value is defined.
An argument is invalid and an error occurs before sending to the PBX server 24, or it cannot be sent to the PBX server 24 due to a network error or the like, but it was sent to the PBX server 24, but the receiving procedure did not end normally and timed out. Or how much the processing request is executed, such as checking the status of the PBX server 24 or PBX 20, and the PBX server 24 refusing to receive it, or the PBX server 24 receiving it but postponing sending the request to the PBX 20 Depending on what has been done, various statuses will be notified.

[API]
The API issued from the PC 42 to the PBX server 24 (PBX control program 240) is, for example, as follows.
(1) MakeCall (): Dial (calling), () contains the destination telephone number and accompanying information indicating the calling method.
In addition to destinations that can be specified by the normal calling method performed on the telephone, there are various parameters such as PBX 20 and timeout settings that are valid according to the setting, the number of ringing tones, and other call identification numbers for making related calls. is there.
There is also a data field that is valid for an extension destination under the control of the PBX server 24.
(2) AnswerCall (): Response to an incoming call, and () contains accompanying information indicating a call identification number.
(3) ReleaseCall (): Restoration (disconnection) after the call is terminated, and additional information indicating the call identification number is entered in ().
(4) HoldCall (): Call is held, and additional information indicating a call identification number is entered in ().
(5) RetrieveCall (): Re-acquisition and reconnection of the call, and additional information indicating the call identification number is entered in ().
(6) MakeCC (): Consultation, () contains call identification number, consultation destination, and incidental information indicating whether or not to switch to conference call when the other party answers.
Hold the other party and make a call to another destination.
In addition to the destinations that can be specified by the usual consultation method performed on the telephone, there are various parameters such as the PBX 20 and the timeout setting that is enabled according to the setting, the number of ringing tones, and other call identification numbers for calling in association. is there.
There is also a data field that is valid for an extension destination under the control of the PBX server 24.
(7) TransferCall: Transfer of a call, and additional information indicating a call identification number is entered in ().
(8) ConferenceCall: Conference call, and additional information indicating a call identification number is entered in ().
(9) SingleStepTransferCall (): Unconfirmed transfer of call, and accompanying information indicating a call identification number is entered in ().
(10) SetCallAppearance (): Reconnect

The log management unit 248 creates a log by attaching time information (time stamp) to APIs, events, and control commands processed by the PBX-IF unit 242, the PBX control unit 244, and the PC-IF 246 according to an instruction from the PC 42 or the like. To do.
The log management unit 248 stores and manages the created log in the log DB 250 and outputs the log stored in the log DB 250 in response to a request from the PC 42 or the like.

[Test program 44]
FIG. 5 is a diagram showing a test program 44 that operates on the PC 42 shown in FIGS.
As shown in FIG. 5, the test program 44 includes a user interface unit (UI unit) 440, an API-DB 442, a state management unit 444, a session management unit 446, an API processing unit 448, a monitor unit 450, a log management unit 452, and a log. It consists of DB 454 and server IF 456.

FIG. 6 is a diagram showing a log created by the test program 44 shown in FIG.
The test program 44, for example, issues an API to the PBX server 24 and implements a function based on cooperation between the PBX server 24 and the PBX 20 (illustrated by a dotted line in FIG. 5), or instead of this application. It is executed on the PC.

With these components, the test program 44 issues an API to the PBX server 24, adds a time stamp to the issued API and its return value, and stores it as a log, as shown in FIG.
Further, as shown in FIG. 6, the test program 44 attaches a time stamp to the event returned from the PBX server 24 and its accompanying information, and stores it as a log.
These pieces of information stored as a log by the test program 44 are used for tests such as cooperative operation of the PBX 20 and the PBX server 24.

FIG. 7 is a diagram illustrating a GUI (Graphical User Interface) image 48 displayed by the UI unit 440 of the test program 44 shown in FIG.
FIG. 8 is a diagram illustrating a setting dialog that is activated prior to the GUI image 48 illustrated in FIG. 7.
The UI unit 440 displays the GUI image 48 shown in FIG. 7 on the input / output device 106 (FIG. 3) of the PC 42, and the user (application creator, developer of the PBX server 24 / PBX 20) is displayed on the GUI image 48. ) Is received and the processing of each component of the test program 44 is controlled.

As shown in FIG. 7, the GUI image 48 includes an initial setting file setting unit 480, a session management information setting unit 482, a state selection unit 484, a telephone operation unit 486, a call selection unit 488, a log display unit 490, and an end button 492. Including.
Actually, for example, a dialog box named a setting dialog shown in FIG. 8 is started before the GUI image 48, and after confirming and correcting the contents of the initial setting file, the process proceeds to the GUI image 48. .

The initial setting file setting unit 480 is used to display the file name of an initial setting file (ini file) that includes the settings to be made to the PBX 20 for the test and the designation of the PBX server 24.
In addition to the settings defined in the initial setting file, the test program 44 sets the PBX 20 and accesses the PBX server 24 according to the contents of the initial setting file based on the setting change according to the user operation on the setting dialog. Etc.

The session management information setting unit 482 is used to set session management information necessary for session management.
The session management information includes information (not shown) for connection between the application of the PC 42 to be developed and the PBX server 24, an extension used in the same call desk 4 (FIG. 1) and associated with the PC 42 ( An extension number of the telephone 40), authentication information (person ID) of an operator (FIG. 1) using the telephone 40, information (instrument) used to associate the telephone 40 with the telephone IF 206 (FIG. 2), and , Password, etc. are set.

In the “disconnect” button in the session management information setting unit 482, “connect” and “disconnect” are actually toggle-displayed.
When the setting of the extension number or the like for the session management information setting unit 482 is completed, when the user clicks a button displayed as “Connect”, an API (ConnectEx ()) is issued to the PBX server 24, and the PBX A session with the server 24 is established, and the button display is “disconnected”.
In this state, when the user clicks a button labeled “Disconnect”, an API (Disonnect ()) is issued to the PBX server 24, the session with the PBX server 24 is disconnected, and the button is displayed. Becomes “connection”.
In the “disconnect” button in the session management information setting unit 482, “connect” and “disconnect” are actually toggle-displayed.
When setting of the extension number and the like for the session management information setting unit 482 is completed, the user

The state selection unit 484 is used for issuing an API (SetAgentState ()) that sets the extension set by the session management information setting unit 482 to a selected state.
The state labels (Login to Hold) selected by the state selection unit 484 correspond to the states (eLogin to eHold) as shown below. The state is set as one of the arguments of SetAgentState ().

(1) Login: eLogin,
(2) Logout: eLogout,
(3) NotReady: eNotReady,
(5) Talking: eTalking,
(6) Available: eAvailable,
(7) WorkNotReady: eWorkNotReady,

(8) WorkReady: eWorkReady,
(9) BusyOther: eBusyOther,
(10) Reserved: eReserved,
(11) Unknown: eUnknown,
(12) Hold: eHold,

The state selection unit 484 is used for issuing an API (SetAgentState ()) that sets the extension set by the session management information setting unit 482 to a selected state.
The state labels (Login to Hold) selected by the state selection unit 484 correspond to the states (eLogin to eHold) as shown below. The state is set as one of the arguments of SetAgentState ().

FIG. 9 is a diagram showing API information stored in the API-DB 442 shown in FIG.
Each button of the telephone operation unit 486 is associated with one or more APIs issued from the PC 42 to the PBX server 24 as shown below.
(1) Dial: MakeCall (),
(2) Response: AnswerCall (),
(3) Disconnect: ReleaseCall (),
(4) Hold: HoldCall (),
(5) Re-acquisition: RetrieveCall (),
(6) Reconnection: ReleaseCall (), SetCallAppearance (), RetrieveCall (),
(7) Consultation: MakeCC (),
(8) Transfer: TransferCall,
(9) Conference: ConferenceCall,
(10) Unconfirmed transfer: SingleStepTransferCall (),
The operation indicated by each button of the telephone operation unit 486 and one or more API1 to APIp (p ≧ 1) are associated with each other as illustrated in FIG. 9 and stored in the test program 44.

The call selection unit 488 is used to select one of the calls in the PBX 20.
Each call in the PBX 20 is uniquely assigned an identifier (eg 16777990 in FIG. 7), and the setting made in the state selection unit 484 is applied to the call selected in the call selection unit 488.

In the log display unit 490, logs generated by the log management unit 452 are sequentially displayed.
The end button 492 is used to end the test program 44 and save information such as a log obtained as a result of the test.

Refer to FIG. 5 again.
The state management unit 444 manages the state of the call that is the object of the test by the test program 44 in accordance with the contents of the initial setting file and the state set in the state selection unit 484 of the GUI image 48 (FIG. 7). .
The session management unit 446 manages the extension (telephone 40) that is the subject of the test by the test program 44 in accordance with the contents of the initial setting file and the setting of the GUI image 48 in the session management information setting unit 482.

The server IF 456 performs communication processing between the PC 42 (test program 44) and the PBX server 24 (FIG. 1).
The API processing unit 448 creates an API with attached information (parameters, etc.) according to the settings for the GUI image 48, and transmits the created API to the PBX server 24 via the monitor unit 450 and the server IF 456. .
The monitor unit 450 monitors the API transmitted to the PBX server 24 and the return value and event returned from the PBX server 24 via the server IF 456, and the API, return value, and The event is output to the log management unit 452.

As shown in FIG. 6, the log management unit 452 creates a log by associating the API, return value, and event input from the monitor unit 450 with these incidental information and a time stamp, and stores the log in the log DB 454. Remember and manage.
The log management unit 452 displays the log stored in the log DB 454 on the input / output device 106 (FIG. 3) or the like in response to a user operation via the UI unit 440, or the communication device 110, the recording device 112, and the like. Output to the outside via the recording medium 114.

[Overall processing of cooperative function test]
Hereinafter, an overall process when the cooperation function of the PBX 20 and the PBX server 24 is tested in the telephone communication system 1 will be described.
FIG. 10 is a diagram showing a communication sequence showing a cooperation function test process (S10) of the PBX 20 and the PBX server 24 in the telephone communication system 1 (FIG. 1).
In step 100 (S100), the user performs an operation on the GUI image 48 (FIG. 7) displayed by the test program 44 (FIG. 5) on the input / output device 106 (FIG. 3) of the PC 42, and the initial setting file and session. Set management information and telephone operation information.

In step 102 (S102), when the setting by the user is completed, the PC 42 (test program 44; FIG. 5) issues the first API in the series of APIs to the PBX server 24.
In step 104 (S104), as shown in FIG. 6, the test program 44 adds a time stamp to the API issued to the PBX server 24, its return value, and these incidental information, and creates a log. , Remember and display.

In step 106 (S106), the PBX server 24 transmits a control command to the PBX 20 in accordance with the API from the PC 42 (test program 44).
In step 108 (S108), the PBX 20 returns an event corresponding to the control command together with the accompanying information.

In step 110 (S110), the PBX server 24 transmits the event from the PBX 20 and its accompanying information to the test program 44.
In step 112 (S112), as shown in FIG. 6, the test program 44 creates a log by adding a time stamp to the event from the PBX server 24 and its accompanying information, and stores and displays it.

Similarly, in the processing from step 114 (S114) to step 124 (S124), APIs are sequentially issued from the PC 42 to the PBX server 24, and logs such as APIs and logs such as events are created, stored and stored. Is displayed.
As described above, the log created by the PC 42 (test program 44) is compared with the log created by the PBX server 24 (PBX control program 240; FIG. 4). It is used for testing of functions to be realized and development of application programs that operate on the PC 42.

  The present invention can be used in an apparatus for testing a telephone exchange.

It is a figure which illustrates the telephone communication system with which the telephone switch test concerning this invention is applied. It is a figure which illustrates the structure of PBX shown in FIG. FIG. 3 is a diagram illustrating the configuration of the PBX server, the PC shown in FIG. 1, and the call control device of the PBX shown in FIG. 2. It is a figure which shows the PBX control program which operate | moves on the PBX server shown in FIG. 1, FIG. It is a figure which shows the test program 44 which operate | moves on PC shown in FIG. 1, FIG. It is a figure which shows the log which the test program shown in FIG. 5 produces. It is a figure which illustrates the GUI (Graphical User Interface) image which the UI part of the test program shown in FIG. 5 displays. It is a figure which illustrates the setting dialog started prior to the GUI image shown in FIG. It is a figure which shows the API information which API-DB shown in FIG. 5 memorize | stores. It is a figure which shows the communication sequence which shows the test process (S10) of the cooperation function of PBX and a PBX server in a telephone communication system (FIG. 1).

Explanation of symbols

1 ... Telephone communication system,
120 ... Network,
122... Communication node,
20 ... PBX,
200: Network IF,
202 ... Call path switch,
204... Call control device,
100 ... body,
102 ... CPU,
104: Memory,
106: I / O device,
110: Communication device,
112... Recording device,
114... Recording medium,
118 ... function realization part,
206 ... Telephone IF,
24 ... PBX server,
240 ... PBX control program,
242 ... PBX-IF section,
244 ... PBX control unit,
246: Log management unit,
250: Log DB.
3 ... call center,
4 ... Call desk,
40 ... telephone,
42 ... PC,
44 ... test program,
440 ... UI unit,
442 ... API-DB,
444 ... Status management unit,
446 ... Session management unit,
448 ... API processing unit,
450 ... monitor unit,
452 ... Log management unit,
454 ... Log DB,

Claims (8)

A telephone exchange test apparatus for testing a telephone exchange that performs call control for calls according to an external API (Application Programming Interface),
Call control information accepting means for accepting call control information necessary for the call control;
A telephone exchange test means for issuing an API corresponding to the accepted call control information to the telephone exchange and testing the telephone exchange;
A telephone exchange testing apparatus comprising: a log creating unit that creates a log including at least the issued API and a time at which the API is issued. The telephone exchange further returns a response according to the API from the outside to the outside,
Response accepting means for accepting a response returned from the telephone exchange;
The telephone exchange testing device according to claim 1, wherein the log creating unit further creates a log including at least the accepted response and a time at which the response is accepted. The call control information accepting means includes
Call management information used for managing the call;
Operation information indicating an operation performed for the call; and
The telephone exchange test apparatus according to claim 2, wherein the telephone exchange test apparatus accepts the call control information including state information indicating the state of the call, or any one or more combinations thereof. The call control information accepting means includes
Displaying the call control information;
Accepting an operation on the displayed call control information;
The telephone exchange test apparatus according to claim 3, wherein the call control information corresponding to the accepted operation is generated. The call management information is
Telephone information for identifying telephones accommodated in the telephone exchange;
A user identifier of a user of the telephone exchange;
A machine identifier constituting the telephone exchange and attached to the machine involved in the call;
A password for accessing the exchange; and
The telephone switch testing device according to claim 1, comprising the call identifier, or any one or more combination thereof. The operation information is
Telephone identification information for identifying telephones accommodated in the telephone exchange;
Dialing the identified telephone,
Hold operation,
Consultation operation,
Answer operation,
Re-acquisition operation,
Conference operations,
The telephone exchange test apparatus according to claim 5, further comprising: telephone operation information including a transfer operation and an unconfirmed transfer operation or any one or more combinations thereof. A telephone exchange test method for testing a telephone exchange that performs call control for calls according to an external API (Application Programming Interface),
Accepting call control information necessary for the call control;
Issuing an API according to the accepted call control information to the telephone switch, testing the telephone switch;
A telephone exchange test method for creating a log including at least the issued API and the time when the API was issued. A program for testing a telephone exchange that performs call control for calls according to an external API (Application Programming Interface),
A call control information accepting step for accepting call control information necessary for the call control;
A telephone switch testing step of issuing an API according to the accepted call control information to the telephone switch and testing the telephone switch;
A program for causing a computer to execute a log creation step of creating a log including at least the issued API and a time at which the API is issued.

Images