JP4242539B2 - Callback control method in IP telephone system, callback control system, and recording medium recording callback control program - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a callback control method in an IP telephone system, which performs bidirectional real-time data communication in an IP network such as the Internet in which a plurality of IP telephone terminals and gatekeepers are accommodated with respective IP addresses, a callback control system, And a recording medium on which a callback control program is recorded.
[0002]
[Prior art]
In the IP telephone system, a destination can be specified by a method of making a call using an IP address from one IP telephone terminal to another IP telephone terminal, or a server called a gatekeeper that manages the IP telephone. There is a method in which an alias address (nickname, e-mail address, etc.) and an IP address of a telephone terminal are registered and a telephone call is made to another IP telephone terminal using the alias address. In the latter method, an alias address unique in the usage environment is registered and used in association with the IP address.
[0003]
Such a conventional method will be described with reference to FIGS. FIG. 9 is a diagram showing the configuration of the IP telephone system. As shown in the figure, an IP telephone terminal (A) 1 and an IP telephone terminal (B) 3 are connected to an IP network 5, and a gatekeeper (GK) 7 is a server that manages the IP telephone in the IP network 5. It is connected. Each of the IP telephone terminal (A) 1 and the IP telephone terminal (B) 3 is installed with IP telephone terminal software 1a and 3a in addition to a microphone and a speaker connected thereto.
[0004]
The IP address and the alias address of the IP telephone terminal (A) 1 are “10.20.30.40” and “ANDO”, respectively, and the IP address and the alias address of the IP telephone terminal (B) 3 are respectively “10.20.30.50” and “MIYAZAKI”.
[0005]
In the IP telephone system configured as described above, each IP telephone terminal registers its own alias address and IP address in the gatekeeper 7 as described above, so that the IP telephone terminal (A) 1 has its own alias address and IP address. A registration packet for registering the address is transmitted to the gatekeeper 7 (process Z71 in FIG. 10). Upon receiving this registration packet, the gatekeeper 7 returns a reply packet indicating that this registration packet has been registered to the IP telephone terminal (A) 1 (process Z73). Similarly, the IP telephone terminal (B) 3 transmits a registration packet for registering its own alias address and IP address to the gatekeeper 7 (process Z75), and receives a reply packet from the gatekeeper 7 (process Z77). Through the above processing, the alias address and IP address of each IP telephone terminal are registered in the gatekeeper 7.
[0006]
Next, the IP telephone terminal (A) 1 obtains the IP address of the IP telephone terminal (B) 3 necessary for calling the IP telephone terminal (B) 3 to obtain the alias of the IP telephone terminal (B) 3. An inquiry packet specifying the address “MIYAZAKI” is transmitted to the gatekeeper 7 (process Z81). In response to this inquiry packet, the gatekeeper 7 returns a reply packet notifying the IP telephone terminal (B) 3 of the IP address “10.20.30.50” to the IP telephone terminal (A) 1 (process Z83).
[0007]
When receiving the IP address “10.20.30.50” of the IP telephone terminal (B) 3 from the gatekeeper 7, the IP telephone terminal (A) 1 uses this IP address to send the IP telephone terminal (B) 3 to the IP telephone terminal (B) 3. On the other hand, a call packet, that is, a call message is transmitted (process Z85). Since each message is transmitted and received in a packet format, the term “message” or “packet” is used in the same way in the drawings and this description.
[0008]
When a call message is transmitted from the IP telephone terminal (A) 1 to the IP telephone terminal (B) 3, the IP telephone terminal (B) 3 returns a connection message to the IP telephone terminal (A) 1 ( Process Z87), the IP telephone terminal (A) 1 and the IP telephone terminal (B) 3 are connected to start a voice call (process Z89).
[0009]
In general, since an alias address is more familiar to humans than an IP address, as described above, a telephone call is often made using the gatekeeper 7. Note that the ITU-T recommendation H.264 describes the call connection method of the IP telephone system, the gatekeeper usage method, and the voice call method. 323 is famous.
[0010]
[Problems to be solved by the invention]
As described above, even when the IP address of the destination IP telephone terminal is acquired from the gatekeeper and the IP telephone terminal is called, the destination IP telephone terminal is the terminal software, and this terminal software is not activated. In such a case, there is a problem that it is not possible to make a call to the IP telephone terminal.
[0011]
In general, software installed and used on a PC is not always activated on a general-purpose PC. Conventionally, when such IP telephone terminal software of the other party is not activated, it is necessary to give up the call or store the message in a server or the like by voice mail or the like.
[0012]
However, if you want to contact immediately, you will often want to request a callback from the other party, but even if it is stored as voice mail, unless the IP telephone terminal software is started on the other party's IP telephone terminal, It's difficult to get a callback right away because you don't know its existence.
[0013]
In addition, the user of the destination IP phone terminal reads the voice mail and then manually inputs the callback destination IP address or the like into the terminal software. is there.
[0014]
In addition, there is a problem that extra equipment for accumulating voice mail is required for the server and the like, which is uneconomical.
[0015]
The present invention has been made in view of the above, and an object of the present invention is to notify a call-back request to the other party even when the other party's IP phone terminal software is not activated, so that the other party can be simplified. An object of the present invention is to provide a callback control method, a callback control system, and a recording medium in which a callback control program is recorded in an IP telephone system capable of performing a callback by operation.
[0016]
[Means for Solving the Problems]
In order to achieve the above object, the present invention according to claim 1 is an IP telephone system in an IP network in which a plurality of IP telephone terminals and gatekeepers are accommodated with respective IP addresses. A registration message for registering its own terminal information including is sent to the gatekeeper, and the gatekeeper registers the terminal information of the registered IP telephone terminal in the registration history table based on the registration message received from the IP telephone terminal. The IP phone terminal that is the sender sends a destination inquiry message to the gatekeeper to specify the alias address of the IP phone terminal that is the destination, and makes a call when the gatekeeper receives the destination inquiry message. Callback message that inquires whether to send mail to the other party The sender IP telephone terminal sends a callback mail transmission request message to the gatekeeper in response to the callback mail transmission inquiry message, and when the gatekeeper receives the callback mail transmission request message, The registration history table is searched to determine whether a destination e-mail address corresponding to the destination alias address included in the destination inquiry message is registered in the registration history table, and the gatekeeper determines the result of the determination. When the other party's e-mail address is registered in the registration history table, a phone call file containing the terminal information of the caller is created, and the gatekeeper sends a callback mail with the caller call file as an attachment to the other party Send to e-mail address and gate key If it is determined as a result of the determination that the other party's e-mail address is not registered in the registration history table, the terminal information of the other party's IP telephone terminal that is the callback mail destination and the callback mail transmission request message Terminal information of the source IP telephone terminal that is the sender of the IP telephone terminal is registered in the callback request table, and the gatekeeper is registered in the callback request table as the destination IP telephone terminal that is the callback destination When the registration message is received from the destination IP phone terminal, the terminal information of the destination IP phone terminal is registered in the registration history table, the e-mail address of the destination IP phone terminal is extracted, and the gatekeeper sends the source IP address from the callback request table. The terminal information of the phone terminal is extracted, and the phone call file containing this source terminal information is extracted. The gist is that the gatekeeper transmits a callback mail having the telephone call file as an attached file to the electronic mail address of the destination IP telephone terminal.
[0017]
In the present invention described in claim 1, when the gatekeeper receives the destination inquiry message from the source IP telephone terminal, it issues a callback email transmission inquiry message inquiring whether or not to send a callback email to the destination. When the caller email transmission request message is received from the sender, the registration history table is searched, and whether or not the destination e-mail address corresponding to the destination alias address is registered in the registration history table. If the call history file is registered in the registration history table, a phone call file including the terminal information of the caller is created, and the callback mail with the call call file as an attached file is set as the destination e-mail address. If the email address is not registered in the registration history table The terminal information of the destination IP telephone terminal that is the callback mail destination and the terminal information of the source IP telephone terminal that is the source of the callback mail transmission request message are registered in the callback request table, and this call When a registration message is received from an IP telephone terminal registered as a destination IP telephone terminal as a callback destination in the back request table, the terminal information of the destination IP telephone terminal is registered in the registration history table, and The e-mail address of the destination IP phone terminal is extracted, the terminal information of the caller IP phone terminal is extracted from the callback request table, a phone call file including the caller terminal information is created, and the phone call file is Send the callback mail as an attached file to the email address of the destination IP phone terminal Therefore, even when the other party's IP phone terminal software is not running, a callback mail with a telephone call file attached can be sent to the other party. By clicking, it is possible to make a callback telephone call without entering a callback destination e-mail address, and the usability can be significantly improved. In addition, since the other party's e-mail address is extracted from the registration history table in the gatekeeper, the user does not need to check the other party's e-mail address, which is efficient. Furthermore, since the callback request is transmitted as a mail attached with a telephone outgoing mail, the capacity is extremely small as compared with the voice mail, and a server such as a gatekeeper is not burdened.
[0018]
According to a second aspect of the present invention, in the IP telephone system in the IP network in which a plurality of IP telephone terminals and gatekeepers are accommodated with respective IP addresses, the IP telephone terminal includes an e-mail address. Registration message transmission means for transmitting a registration message for registering terminal information to the gatekeeper, and a partner for transmitting a destination inquiry message to the gatekeeper in order to make a call by designating the alias address of the IP telephone terminal as the destination Receiving a callback mail transmission inquiry message from the gatekeeper, and a callback mail related transmission / reception means for returning a callback mail transmission request message to the gatekeeper in response to the message, the gatekeeper comprising: Receive from IP phone terminal Registration history table for registering the terminal information of the registered IP telephone terminal based on the registered message, and whether or not to send a callback mail to the destination IP telephone terminal when receiving the destination inquiry message from the IP telephone terminal Callback mail transmission inquiry message transmission means for transmitting a callback mail transmission inquiry message to the caller IP telephone terminal, and when a callback mail transmission request message is received from the caller IP telephone terminal, the registration history table is searched. A destination registration determination means for determining whether or not an email address of a destination IP telephone terminal corresponding to the alias address of the destination included in the destination inquiry message is registered in a registration history table; As a result, the e-mail address of the destination IP phone terminal is registered. If registered in the history table, the first call origination file creation means for creating the call origination file including the terminal information of the originator, and the e-mail address of the destination IP telephone terminal as a result of the determination are registered. If it is determined that it is not registered in the history table, the terminal information of the destination IP telephone terminal that is the callback mail destination and the terminal information of the source IP telephone terminal that is the source of the callback mail transmission request message are A callback request table to be registered, and terminal information of the destination IP telephone terminal when a registration message is received from an IP telephone terminal registered as a destination IP telephone terminal as a callback destination in the callback request table Is registered in the registration history table, and the e-mail address of the destination IP phone terminal is extracted. A destination e-mail address extracting means, a second telephone call file creating means for extracting the terminal information of the caller IP telephone terminal from the callback request table and creating a telephone call file including the caller terminal information; Callback mail transmission means for transmitting a callback mail having the telephone call file created by the first or second telephone call file creation means as an attached file to the e-mail address of the destination IP telephone terminal. The gist.
[0019]
In the present invention described in claim 2, when the gatekeeper receives the destination inquiry message from the source IP telephone terminal, it issues a callback email transmission inquiry message inquiring whether or not to send a callback email to the destination. When the caller email transmission request message is received from the sender, the registration history table is searched, and whether or not the destination e-mail address corresponding to the destination alias address is registered in the registration history table. If the call history file is registered in the registration history table, a phone call file including the terminal information of the caller is created, and the callback mail with the call call file as an attached file is set as the destination e-mail address. If the email address is not registered in the registration history table The terminal information of the destination IP telephone terminal that is the callback mail destination and the terminal information of the source IP telephone terminal that is the source of the callback mail transmission request message are registered in the callback request table, and this call When a registration message is received from an IP telephone terminal registered as a destination IP telephone terminal as a callback destination in the back request table, the terminal information of the destination IP telephone terminal is registered in the registration history table, and The e-mail address of the destination IP phone terminal is extracted, the terminal information of the caller IP phone terminal is extracted from the callback request table, a phone call file including the caller terminal information is created, and the phone call file is Send the callback mail as an attached file to the email address of the destination IP phone terminal Therefore, even when the other party's IP phone terminal software is not running, a callback mail with a telephone call file attached can be sent to the other party. By clicking, it is possible to make a callback telephone call without entering a callback destination e-mail address, and the usability can be significantly improved.
[0020]
Further, according to the present invention, in the IP telephone system in the IP network in which a plurality of IP telephone terminals and gatekeepers are accommodated with respective IP addresses, the IP telephone terminal includes its own e-mail address. A registration message for registering information is transmitted to the gatekeeper. The gatekeeper registers the terminal information of the registered IP telephone terminal in the registration history table based on the registration message received from the IP telephone terminal, and becomes a transmission source. The IP phone terminal sends an addressee inquiry message to the gatekeeper in order to make a call by designating the alias address of the IP phone terminal as the destination, and when the gatekeeper receives the destination inquiry message, the callback mail is sent to the destination. Callback mail transmission inquiry message that inquires whether or not to send The sender IP phone terminal returns a callback mail transmission request message to the gatekeeper in response to the callback mail transmission inquiry message. When the gatekeeper receives the callback mail transmission request message, the registration history The table is searched to determine whether or not a destination e-mail address corresponding to the destination alias address included in the destination inquiry message is registered in the registration history table. If the destination e-mail address is registered in the registration history table, a phone call file including the terminal information of the caller is created, and the gatekeeper sends a callback mail with the phone call file as an attachment to the destination e-mail. Sent to the address, and the gatekeeper If it is determined that the other party's e-mail address is not registered in the registration history table, the terminal information of the other party's IP telephone terminal that is the callback mail destination and the origin that is the sender of the callback mail transmission request message The terminal information of the original IP telephone terminal is registered in the callback request table, and the gatekeeper receives a registration message from the IP telephone terminal registered as the destination IP telephone terminal that is the callback destination in the callback request table. In this case, the terminal information of the destination IP telephone terminal is registered in the registration history table, the e-mail address of the destination IP telephone terminal is extracted, and the gatekeeper obtains the terminal information of the source IP telephone terminal from the callback request table. Extract and create a phone call file that includes this source terminal information, The gist of the keeper is to record, on a recording medium, a callback control program in an IP telephone system that transmits a callback mail with the telephone outgoing file as an attached file to the electronic mail address of the destination IP telephone terminal.
[0021]
In the present invention according to claim 3, when the gatekeeper receives the destination inquiry message from the source IP telephone terminal, it issues a callback email transmission inquiry message inquiring whether or not to send a callback email to the destination. When the caller email transmission request message is received from the sender, the registration history table is searched, and whether or not the destination e-mail address corresponding to the destination alias address is registered in the registration history table. If the call history file is registered in the registration history table, a phone call file including the terminal information of the caller is created, and the callback mail with the call call file as an attached file is set as the destination e-mail address. If the email address is not registered in the registration history table The terminal information of the destination IP telephone terminal that is the callback mail destination and the terminal information of the source IP telephone terminal that is the source of the callback mail transmission request message are registered in the callback request table, and this call When a registration message is received from an IP telephone terminal registered as a destination IP telephone terminal as a callback destination in the back request table, the terminal information of the destination IP telephone terminal is registered in the registration history table, and The e-mail address of the destination IP phone terminal is extracted, the terminal information of the caller IP phone terminal is extracted from the callback request table, a phone call file including the caller terminal information is created, and the phone call file is Send the callback mail as an attached file to the email address of the destination IP phone terminal Since recorded in the recording medium callback control program, using the recording medium, it is possible to enhance the flow properties.
[0022]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration of an IP telephone system that implements a callback control method according to an embodiment of the present invention. In the IP telephone system shown in the figure, an IP telephone terminal (A) 11 and an IP telephone terminal (B) 13 are connected to an IP network (LAN) 15, and the IP telephone terminal (A) 11 and the IP telephone terminal (B ) In addition to a microphone and a speaker connected to each of 13, IP telephone terminal software 11 a and 13 a and mail software 11 b and 13 b are installed. The IP network 15 is connected to a gatekeeper 17 and a mail server 19 which are servers for managing IP telephones. Each IP telephone terminal is, for example, a PC on which IP telephone terminal software is installed, or an IP telephone dedicated terminal.
[0023]
The IP address and the alias address of the IP telephone terminal (A) 11 are “10.20.30.40” and “ANDO”, respectively. The IP address and the alias address of the IP telephone terminal (B) 13 are respectively “10.20.30.50” and “MIYAZAKI”.
[0024]
As shown in detail in FIG. 2, the gatekeeper 17 includes a network interface unit 21 connected to the IP network 15, a control unit 23 that controls the operation of the entire gatekeeper, a callback mail destination e-mail address, and the like. A mail transmission unit 25 that transmits a callback mail, a callback mail generation unit 27 that generates a callback mail, and a telephone call file that includes terminal information of the IP telephone terminal that is the transmission source of the callback mail transmission request message. The telephone call file creation unit 29, a registration history table 35 and a callback request table 41, which will be described later, are searched, and the terminal information of the IP telephone terminal that is the transmission source of the callback transmission request message and the email address of the callback mail destination Terminal search unit 31 for extracting each I A terminal management table 33 that manages the alias address and IP address of each IP telephone terminal in association with each other based on a registration request from the telephone terminal, and a registration history table 35 that stores and manages terminal information of IP telephone terminal software that has been registered in the past. A command control unit 37 that performs command control, a communication control unit 39 that performs communication control, and terminal information of an IP telephone terminal that is a callback destination and terminal information of an IP telephone terminal that is a transmission source of a callback mail transmission request message Is formed from a callback request table 41 for storing and managing
[0025]
Next, the operation of this embodiment will be described with reference to the flowcharts and sequence diagrams in FIG.
[0026]
First, IP phone terminal registration processing in the gatekeeper 17 will be described with reference to the flowchart shown in FIG.
[0027]
When the gatekeeper 17 is in a standby state (step S11), when the IP telephone terminal, for example, the IP telephone terminal software 11a of the IP telephone terminal (A) 11 is activated, its own alias address (nickname, e-mail address, etc.) and IP address When the registration packet for registering the terminal information such as the terminal information to the gatekeeper 17 is transmitted to the gatekeeper 17, the gatekeeper 17 receives the registration packet (step S13), and reads the alias address and IP address set in the registration packet. And is registered in the terminal management table 33 (step S15).
[0028]
Further, the gatekeeper 17 refers to the registration history table 35 from the terminal management table 33 and determines whether or not terminal information such as an alias address set in the received registration packet is registered in the registration history table 35. If not registered, terminal information such as the alias address and IP address is newly registered in the registration history table 35. If already registered, the terminal information is updated to the latest information and the IP telephone terminal (A ) A reply packet indicating that the terminal information such as the alias address and the IP address of 11 is registered is returned to the IP telephone terminal (A) 11 (step S17). Then, the gatekeeper 17 returns to the standby state (step S19).
[0029]
When the gatekeeper 17 receives the registration deletion packet from the IP telephone terminal (step S21), it deletes the terminal information of the IP telephone terminal registered in the terminal management table 33 as described above (step S23), and waits again. Return to (step S25). As described above, the terminal information of each IP telephone terminal that has requested registration of terminal information by a registration packet is registered in the terminal management table 33 and the registration history table 35 of the gatekeeper 17.
[0030]
Next, callback processing will be described with reference to the flowchart shown in FIG. 4 and the sequence diagram shown in FIG. Note that the flowchart of FIG. 4 illustrates the operation of the gatekeeper 17. In this description, the sender of the callback transmission request message is referred to as a sender, and the callback mail destination is referred to as a partner.
[0031]
First, at the beginning of FIG. 5, as described with reference to FIG. 3, it is illustrated that the terminal information of the IP telephone terminal that has requested registration of terminal information by a registration packet is registered in the gatekeeper 17. That is, in FIG. 5, when the IP telephone terminal (A) 11 transmits a registration packet for registering terminal information such as its own alias address and IP address in the gatekeeper 17 (processing Z1), the gatekeeper 17 transmits the registration packet. The terminal information such as the alias address and IP address set in the registration packet is registered in the terminal management table 33, and a registration approval packet is returned to the IP telephone terminal (A) 11 (process Z3).
[0032]
As a precondition of this description, since the IP telephone terminal software 13a is not activated, the IP telephone terminal (B) 13 has the terminal information including the alias address and IP address of the IP telephone terminal (B) 13 as the gatekeeper. However, the IP telephone terminal (B) 13 has been registered with the gatekeeper 17 at least once in the past, and the IP telephone terminal (B) 13 registered in the past has been registered. Are stored in the registration history table 35.
[0033]
In such a state, it is assumed that the IP telephone terminal (A) 11 calls the IP telephone terminal (B) 13 using the alias address of the other party. Therefore, the IP telephone terminal (A) 11 inputs the alias address “MIYAZAKI” of the IP telephone terminal (B) 13 in the IP telephone terminal software 11 a and makes a telephone call. When the destination IP address inquiry packet for acquiring the IP address information of “MIYAZAKI” is transmitted, the gatekeeper 17 receives this IP address inquiry packet (step S33 in FIG. 4 and process Z5 in FIG. 5).
[0034]
When the gatekeeper 17 receives the IP address inquiry packet from the IP telephone terminal (A) 11, the gatekeeper 17 searches the terminal management table 33 with the alias address of the IP telephone terminal (B) 13 which is the other party set in the IP address inquiry packet. However, since it is not registered in the terminal management table 33 like the precondition mentioned above at this time, it cannot search. When the other party is not registered in the gatekeeper 17 as described above, a reply message notifying that is transmitted to the IP telephone terminal of the sender. If it cannot be searched because it is not registered, the registration history table 35 is searched with the same alias address, and the IP telephone terminal (B) 13 as the destination is searched from the terminal information registered in the past of the IP telephone terminal (B) 13. An e-mail address is extracted (step S35, process Z7). That is, if the destination IP telephone terminal has been registered in the gatekeeper 17 even once in the past, the terminal information of the destination IP telephone terminal is registered in the registration history table 35 of the gatekeeper 17, so E-mail address can be detected.
[0035]
When the gatekeeper 17 extracts the e-mail address of the destination IP telephone terminal (B) 13, the gatekeeper 17 sends an inquiry packet as to whether or not to transmit a callback mail to the destination IP telephone terminal (A) 11. (Step S37, Process Z9). When receiving the callback transmission inquiry packet, the source IP telephone terminal (A) 11 transmits a callback transmission request packet to the gatekeeper 17.
[0036]
When the gatekeeper 17 receives the callback transmission request packet from the source IP telephone terminal (A) 11 (processing Z11), the gatekeeper 17 acquires the terminal information of the source IP telephone terminal (A) 11 from the registration history table 35, The telephone call file creation unit 29 creates a telephone call file including terminal information such as the alias address of the IP telephone terminal (A) 11 that is the caller, and also creates a callback mail (process Z13). A telephone call file is attached (step S39). Then, as described above, the callback mail is addressed to the e-mail address corresponding to the destination alias address “MIYAZAKI” extracted from the terminal information of the registration history table 35 registered in the past of the IP telephone terminal (B) 13. It is transmitted from the mail transmitting unit 25 to the destination IP telephone terminal (B) 13 (step S41, process Z15). Here, the gatekeeper 17 once returns to the standby state (step S43).
[0037]
The phone call file created by the phone call file creation unit 29 is, as shown in FIG. 8 (a) as an example of the phone call file, the IP phone terminal (B) 13 that is the other party, the alias address “Alias @ It is assumed that information “ANDO” is described and the file extension is “.vlf”. In this case, instead of the alias address “Alias @ ANDO”, the IP address “IP@10.20.30.40” may be described as shown in FIG. 8B.
[0038]
When the callback mail transmitted from the gatekeeper 17 is transmitted via the mail server 19 and received by the mail software 13b of the destination IP telephone terminal (B) 13, the user of the IP telephone terminal (B) 13 Discover that the callback is requested from the received callback mail, and click the attached phone call file.
[0039]
In the present embodiment, as shown in FIG. 8, the extension “.vlf” of the telephone call file is used. However, in the IP telephone terminal (B) 13, the extension “.vlf” and the IP telephone terminal software 13a are used. Are associated by the function of associating the extension of Windows. That is, in a Windows terminal, a specific extension is generally associated with a specific application, and when a file with a certain extension is clicked, an application associated with the extension is activated. It has become. Therefore, in this embodiment, when a file with an extension of “.vlf” is clicked, settings are made so that a call is made to the parameter destination set in this file.
[0040]
Therefore, in the IP telephone terminal (B) 13, when the user who has received the callback mail clicks the telephone call file with the extension “.vlf” attached to the callback mail, the IP telephone terminal software 13a is attached. Upon receiving the alias address “Alias @ ANDO” or the IP address “IP@10.20.30.40” which is the terminal information of the caller included as a parameter in the telephone call file of the IP phone terminal (B ) 13 transmits a callback telephone call / call packet to the caller IP telephone terminal (A) 11 (process Z17). When the source IP telephone terminal (A) 11 receives the callback telephone outgoing call packet from the IP telephone terminal (B) 13, it transmits a connection packet to the IP telephone terminal (B) 13 (process Z 19). As a result, the IP telephone terminal (A) 11 and the IP telephone terminal (B) 13 are connected and a voice call is started (process Z21).
[0041]
Next, referring to the flowchart shown in FIG. 6 and the sequence diagram shown in FIG. 7, as another operation of the callback processing of the present embodiment, the terminal information of the IP telephone terminal (B) 13 is converted to the terminal management table 33 of the gatekeeper 17. In addition, the IP telephone terminal (B) 13 is not registered in the gatekeeper 17 and has not been registered in the registration history table 35 as a precondition. To do.
[0042]
The operation in this case is basically obtained from the terminal management table 33 and the registration history table 35 of the gatekeeper 17 as the terminal information of the IP telephone terminal (B) 13 which is the counterpart in the operation described with reference to FIGS. Therefore, the callback request table 41 of the gatekeeper 17 stores the terminal information of the destination IP telephone terminal (B) 13 that is the destination of the callback mail and the source IP telephone terminal (A) 11 that is the source of the callback request. The terminal information is saved, and it is recorded that there is a callback request from the IP telephone terminal (A) 11 to the IP telephone terminal (B) 13. When the destination IP telephone terminal (B) 13 has registered its own terminal information in the gatekeeper 17, a callback mail is sent to the destination IP telephone terminal (B) 13 based on this terminal information. It is what you want to send.
[0043]
Specifically, the processes Z31 and Z33 at the beginning of FIG. 7 are the same as the processes Z1 and Z3 of FIG. 5, and the terminal information of the IP telephone terminal (A) 11 is obtained by the registration packet from the IP telephone terminal (A) 11. Is registered in the gatekeeper 17, the gatekeeper 17 registers the terminal information of the IP telephone terminal (A) 11, and returns a registration approval packet to the IP telephone terminal (A) 11.
[0044]
Then, if the IP telephone terminal (A) 11 calls the IP telephone terminal (B) 13 by using the alias address of the other party, the IP telephone terminal (A) 11 is connected to the IP telephone terminal software 11a by the IP telephone terminal software 11a. The alias address “MIYAZAKI” of the telephone terminal (B) 13 is input to make a telephone call. When the IP telephone terminal (A) 11 transmits a destination IP address inquiry packet for acquiring the IP address information of the destination “MIYAZAKI” to the gatekeeper 17, the gatekeeper 17 receives the IP address inquiry packet. (Step S53 in FIG. 6 and process Z35 in FIG. 7).
[0045]
Upon receiving the IP address inquiry packet from the IP telephone terminal (A) 11, the gatekeeper 17 uses the terminal management table with the alias address “MIYAZAKI” of the IP telephone terminal (B) 13 that is the other party set in the IP address inquiry packet. However, since it is not registered in the terminal management table 33 at this time, it cannot be searched. Therefore, the gatekeeper 17 searches the registration history table 35 with the same alias address “MIYAZAKI”, and uses the terminal information registered in the past of the IP telephone terminal (B) 13 to send the e-mail of the IP telephone terminal (B) 13 that is the destination. Although the IP telephone terminal (B) 13 has not been registered in the gatekeeper 17 in the past as in the preconditions described above, the gatekeeper 17 also reads the alias address “MIYAZAKI” from the registration history table 35. The e-mail address corresponding to cannot be searched (step S55, process Z37).
[0046]
Therefore, the gatekeeper 17 sends a callback transmission inquiry packet as to whether or not to perform callback transmission when the destination IP telephone terminal (B) 13 has registered terminal information with the gatekeeper 17. This is transmitted to the IP telephone terminal (A) 11 (step S57, process Z39).
[0047]
The IP telephone terminal (A) 11 agrees with the callback transmission inquiry packet from the gatekeeper 17 and returns a callback transmission request packet to the gatekeeper 17, and the gatekeeper 17 transmits the callback transmission from the IP telephone terminal (A) 11. When receiving the request packet (process Z41), the gatekeeper 17 stores the terminal information of the destination IP telephone terminal (B) 13 that is the destination of the callback mail in the callback request table 41 and the source that is the request source of the callback. The terminal information of the IP telephone terminal (A) 11 is stored (step S59, process Z43). Then, the gatekeeper 17 enters a standby state until it receives a registration packet from the destination IP telephone terminal (B) 13 (step S61).
[0048]
When the gatekeeper 17 receives a registration packet in which terminal information including the alias address and IP address of the IP telephone terminal (B) 13 is set from the IP telephone terminal (B) 13 of the callback in the standby state (step) S63, process Z45), the alias address and IP address of the destination IP telephone terminal (B) 13 set in the received registration packet are registered in the terminal management table 33, and also newly registered in the registration history table 35. Register (step S65). When the registration is completed, the gatekeeper 17 returns a registration approval packet to the IP telephone terminal (B) 13 (process Z47).
[0049]
As described above, when receiving the terminal information of the IP telephone terminal (B) 13, the gatekeeper 17 searches the callback request table 41 with the terminal information of the received IP telephone terminal (B) 13 (processing Z49), When it is detected that the terminal information of the IP telephone terminal (B) 13 is stored in the callback request table 41 as the counterpart terminal information of the callback, the destination IP address is registered from the registration history table 35 or the terminal management table 33. The electronic mail address of the telephone terminal (B) 13 is retrieved and extracted (step S67).
[0050]
Further, the gatekeeper 17 extracts a source alias address which is the terminal information of the callback source IP telephone terminal (A) 11 from the callback request table 41, and makes a telephone call including the alias address of the source IP telephone terminal. A file is created by the telephone call file creation unit 29 (step S69). As shown in FIG. 8, the telephone call file includes information “Alias @ ANDO” or “IP@10.20.30.40”, and the extension of the file is “. vlf ".
[0051]
Further, the gatekeeper 17 creates a callback mail by the callback mail creating unit 27 (process Z53), and attaches a telephone call file to the callback mail (step S69). Then, the e-mail address of the destination IP telephone terminal (B) 13 extracted as described above is transmitted to the destination IP telephone terminal (B) 13 from the mail transmitting unit 25 (step). S71, process Z55). Here, the gatekeeper 17 once enters a standby state (step S73).
[0052]
When the callback mail transmitted from the gatekeeper 17 is transmitted via the mail server 19 and received by the mail software 13b of the destination IP telephone terminal (B) 13, the user of the IP telephone terminal (B) 13 Then, it is found that the callback is requested from the received callback mail, and the telephone call file with the extension “.vlf” attached to the callback mail is clicked.
[0053]
When a phone call file with an extension of “.vlf” is clicked, the IP phone terminal software 13a is an alias address “Alias @ ANDO” or IP address which is terminal information of the caller included as a parameter in the phone call file Upon receiving “IP@10.20.30.40”, the IP telephone terminal (B) 13 is activated and a callback telephone outgoing call packet is transmitted from the IP telephone terminal (B) 13 to the originating IP telephone terminal (A) 11 ( Process Z57). When the source IP telephone terminal (A) 11 receives the callback telephone outgoing call packet from the IP telephone terminal (B) 13, it transmits a connection packet to the IP telephone terminal (B) 13 (process Z 59). As a result, the IP telephone terminal (A) 11 and the IP telephone terminal (B) 13 are connected and a voice call is started (process Z61).
[0054]
In the above embodiment, as a method for realizing a telephone call file, an extension of a file is associated with an application that is started when the file is clicked on Windows, and the attached telephone call file is clicked. The IP phone terminal software is activated, and a function for making a phone call by passing it to a certain parameter in the file is installed in the IP phone terminal software. However, the present invention is not limited to such a method for realizing a telephone call file according to the present invention.
[0055]
The processing procedure of the callback control method in the IP telephone system of the above embodiment is recorded as a program on a recording medium, the recording medium is incorporated into a computer system, and the program recorded on the recording medium is downloaded to the computer system. Or, by installing and operating the computer system with the program, it is possible to function as a callback control system that implements the callback control method in the IP telephone system, and by using such a recording medium It is possible to improve the distribution.
[0056]
【The invention's effect】
As described above, according to the present invention, when the gatekeeper receives the destination inquiry message from the source IP telephone terminal, the gatekeeper transmits the callback mail transmission inquiry message to the source and sends the callback mail transmission request message to the source. If the destination e-mail address is received, it is determined whether or not the destination e-mail address is registered in the registration history table. If registered, a phone call file including the terminal information of the caller is created, and the phone call file is created. If you send a callback mail with the attached file to the recipient's email address, and the recipient's email address is not registered, the recipient's terminal information and sender's terminal information of the callback email will be displayed. Calls registered in the callback request table and registered in this callback request table When the registration message is received from the other party IP telephone terminal, the e-mail address of the other party IP telephone terminal is extracted, the terminal information of the source IP telephone terminal is extracted from the callback request table, and the terminal information is Since the call outgoing mail including the telephone outgoing file is sent to the e-mail address of the destination IP phone terminal, the destination IP phone terminal software is not activated. You can send a callback email with a phone call file attached to the recipient, and the recipient who received the callback email can click on the phone call file without entering the callback email address, Callback telephone calls can be made, and usability can be significantly improved. Also, since the other party's e-mail address is extracted from the registration history table in the gatekeeper, the user does not need to check the other party's e-mail address, which is efficient. Note that mail software is generally very highly used, and is usually almost activated on a PC. Therefore, when a callback mail is transmitted to the other party, it is received by the other party in a short time. Further, since the callback request is transmitted as a mail attached with a telephone outgoing mail, the capacity is extremely small as compared with the voice mail, and a load on a server such as a gatekeeper is not applied.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of an IP telephone system that implements a callback control method according to an embodiment of the present invention.
2 is a block diagram showing a detailed configuration of a gatekeeper used in the IP telephone system shown in FIG. 1. FIG.
3 is a flowchart showing registration processing of an IP telephone terminal in a gatekeeper in the embodiment shown in FIG.
FIG. 4 is a flowchart showing callback processing in the gatekeeper in the embodiment shown in FIG. 1;
FIG. 5 is a sequence diagram showing callback processing in the gatekeeper in the embodiment shown in FIG. 1;
6 is a flowchart showing another operation of callback processing in the gatekeeper in the embodiment shown in FIG. 1. FIG.
7 is a sequence diagram showing another operation of callback processing in the gatekeeper in the embodiment shown in FIG. 1; FIG.
8 is a diagram showing an example of a telephone call file in the embodiment shown in FIG. 1. FIG.
FIG. 9 is a diagram for explaining a conventional destination designation method in an IP telephone system.
FIG. 10 is a sequence diagram showing a conventional connection procedure in an IP telephone system.
[Explanation of symbols]
11, 13 IP phone terminal
11a, 11b IP phone terminal software
13a, 13b Mail software
15 IP network
17 Gatekeeper
19 Mail server
27 Callback Mail Creation Department
29 Phone call file creation department
33 Terminal management table
35 Registration history table
41 Callback request table

Claims (3)

In a callback control method in an IP telephone system in an IP network in which a plurality of IP telephone terminals and gatekeepers are accommodated with respective IP addresses,
The IP phone terminal sends a registration message for registering its own terminal information including the e-mail address to the gatekeeper,
The gatekeeper registers the terminal information of the registered IP telephone terminal based on the registration message received from the IP telephone terminal in the registration history table,
The source IP telephone terminal sends an addressee inquiry message to the gatekeeper to specify the alias address of the destination IP telephone terminal to make a call, and when the gatekeeper receives the destination inquiry message, the callback mail Send a callback mail sending inquiry message to the sender to inquire whether or not to send
The source IP telephone terminal returns a callback mail transmission request message to the gatekeeper in response to the callback mail transmission inquiry message,
When the gatekeeper receives the callback mail transmission request message, the gatekeeper searches the registration history table, and checks whether the destination e-mail address corresponding to the destination alias address included in the destination inquiry message is registered in the registration history table. Determine whether or not
As a result of the determination, if the destination e-mail address is registered in the registration history table, the gatekeeper creates a phone call file including the terminal information of the caller,
The gatekeeper sends a callback mail with the outgoing call file as an attachment to the email address of the other party,
As a result of the determination, if the gatekeeper determines that the other party's e-mail address is not registered in the registration history table, the terminal information and the callback mail transmission request of the other party IP telephone terminal that is the callback mail destination Register the terminal information of the source IP telephone terminal that is the message source in the callback request table,
When the gatekeeper receives a registration message from an IP telephone terminal registered as a destination IP telephone terminal as a callback destination in the callback request table, the gatekeeper registers terminal information of the destination IP telephone terminal in the registration history table. Along with extracting the e-mail address of the destination IP phone terminal,
The gatekeeper extracts the terminal information of the source IP telephone terminal from the callback request table, creates a telephone call file including the source terminal information,
A method for controlling a callback in an IP telephone system, wherein the gatekeeper transmits a callback mail having the telephone outgoing file as an attached file to an electronic mail address of the destination IP telephone terminal. In a callback control system in an IP telephone system in an IP network in which a plurality of IP telephone terminals and gatekeepers are accommodated with respective IP addresses,
The IP telephone terminal
A registration message transmitting means for transmitting a registration message for registering own terminal information including an e-mail address to the gatekeeper;
A partner inquiry message transmission means for transmitting a partner inquiry message to the gatekeeper in order to make a call by designating an alias address of the IP telephone terminal as a partner;
A callback mail transmission / reception means for receiving a callback mail transmission inquiry message from the gatekeeper and returning a callback mail transmission request message to the gatekeeper in response to the message;
The gatekeeper is
A registration history table for registering terminal information of the registered IP telephone terminal based on the registration message received from the IP telephone terminal;
When a destination inquiry message is received from the IP telephone terminal, a callback mail transmission inquiry message is transmitted to the source IP telephone terminal for inquiring whether or not to send a callback mail to the destination IP telephone terminal. A transmission means;
When the callback mail transmission request message is received from the source IP telephone terminal, the registration history table is searched, and the electronic mail address of the partner IP telephone terminal corresponding to the alias address of the partner included in the partner inquiry message is obtained. Partner registration determination means for determining whether or not registered in the registration history table;
As a result of the determination, if the e-mail address of the destination IP telephone terminal is registered in the registration history table, first telephone call file creation means for creating a telephone call file including the terminal information of the caller;
As a result of the determination, if it is determined that the e-mail address of the destination IP telephone terminal is not registered in the registration history table, the terminal information of the destination IP telephone terminal that is the callback mail destination and the callback mail transmission A callback request table for registering terminal information of a source IP telephone terminal that is a transmission source of a request message, and an IP telephone terminal registered as a destination IP telephone terminal that is a callback mail destination in the callback request table And receiving the registration message from the destination IP telephone terminal, registering the terminal information of the destination IP telephone terminal in the registration history table, and extracting the destination email address extracting means for extracting the email address of the destination IP telephone terminal;
Second telephone call file creation means for extracting terminal information of the caller IP telephone terminal from the callback request table and creating a telephone call file including the caller terminal information;
Callback mail transmission means for transmitting a callback mail having the telephone call file created by the first or second telephone call file creation means as an attached file to the e-mail address of the destination IP telephone terminal. A callback control system in an IP telephone system. In a recording medium recording a callback control program in an IP telephone system in an IP network in which a plurality of IP telephone terminals and gatekeepers are accommodated with IP addresses, respectively,
The IP phone terminal sends a registration message for registering its own terminal information including the e-mail address to the gatekeeper,
The gatekeeper registers the terminal information of the registered IP telephone terminal based on the registration message received from the IP telephone terminal in the registration history table,
The source IP telephone terminal sends an addressee inquiry message to the gatekeeper to specify the alias address of the destination IP telephone terminal to make a call, and when the gatekeeper receives the destination inquiry message, the callback mail Send a callback mail sending inquiry message to the sender to inquire whether or not to send
The source IP telephone terminal returns a callback mail transmission request message to the gatekeeper in response to the callback mail transmission inquiry message,
When the gatekeeper receives the callback mail transmission request message, the gatekeeper searches the registration history table, and checks whether the destination e-mail address corresponding to the destination alias address included in the destination inquiry message is registered in the registration history table. Determine whether or not
As a result of the determination, if the destination e-mail address is registered in the registration history table, the gatekeeper creates a phone call file including the terminal information of the caller,
The gatekeeper sends a callback mail with the outgoing call file as an attachment to the email address of the other party,
As a result of the determination, if the gatekeeper determines that the other party's e-mail address is not registered in the registration history table, the terminal information and the callback mail transmission request of the other party IP telephone terminal that is the callback mail destination Register the terminal information of the source IP telephone terminal that is the message source in the callback request table,
When the gatekeeper receives a registration message from an IP telephone terminal registered as a destination IP telephone terminal as a callback destination in the callback request table, the gatekeeper registers terminal information of the destination IP telephone terminal in the registration history table. Along with extracting the e-mail address of the destination IP phone terminal,
The gatekeeper extracts the terminal information of the source IP telephone terminal from the callback request table, creates a telephone call file including the source terminal information,
A recording medium storing a callback control program in an IP telephone system, wherein the gatekeeper transmits a callback mail having the telephone outgoing file as an attached file to an electronic mail address of the destination IP telephone terminal.

Images