JP2014003577A - Call connection device and communication method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make an extension call available by registering a terminal to a specific extension number by operation from the terminal.SOLUTION: A call connection device 10 performing call connection processing of an extension terminal 11 includes a call control unit 60 performing connection processing of a call, originated from an outside line terminal 21, between other call connection device 20 performing call connection processing of the outside line terminal 21, a registration request reception unit 61 for receiving a registration request of an extension transmitted from the outside line terminal 21 in a call to the outside line terminal 21 connected by the call control unit 60, a terminal registration unit 63 for registering an extension number including an identifier unique to the call connection device in the outside line terminal 21 that transmitted the registration request, and a notification unit 64 for notifying other call connection device 20 of the extension number registered in the outside line terminal 21.

Description

  The embodiments discussed herein relate to telephone call control.

  As a technology related to telephone call control, a user makes a call from a telephone terminal via an external line or dedicated line to a telephone number dedicated to login provided in a telephone exchange device that constitutes an extension network, and the terminal of the external line or dedicated line It is known to register a telephone terminal number in a telephone exchange device.

JP 2004-357208 A

  When trying to make an extension call with a specific extension number, there may be no telephone terminal at the user's hand that can make or receive an extension call with this extension number. In such a case, it is desirable to be able to make and receive calls with this extension number using another terminal at hand of the user.

  An object of the disclosed apparatus and method is to register the terminal to a specific extension number by an operation from the terminal, and to enable use of the extension call by the registered terminal.

According to one aspect of the apparatus, a call connection apparatus that performs call connection processing of an extension terminal is provided. The call connection device includes: a call control unit that performs connection processing of a call transmitted from the external line terminal with another call connection device that performs call connection processing of the external line terminal; and an external line terminal connected by the call control unit A registration request receiving unit that receives an extension registration request transmitted from an external terminal in a call, a terminal registration unit that registers an extension number including an identifier unique to the call connection device in the external terminal that has transmitted the registration request, and an external line A notifying unit for notifying another call connection device of the extension number registered in the terminal is provided.
With

  According to another aspect of the apparatus, there is provided a call connection apparatus that performs call connection processing of an external line terminal. The call connection device includes a call control unit that performs call connection processing between an external terminal and an extension terminal with another call connection device that performs call connection processing of the extension terminal, and an external terminal by the other call connection device. A receiving unit that receives an extension number including an identifier unique to another registered call connection device from another call connection device. The call control unit performs a call connection process for connecting a call with another call connection device identified by the extension number designated as the called party number of the outgoing line terminal.

  According to one aspect of the method, a call control method is provided. In the call control method, connection processing for a call originated from an external terminal is performed between a first call connection device that performs call connection processing of an extension terminal and a second call connection device that performs call connection processing of the external terminal. An extension registration request transmitted from an external terminal in a connected call is received by the first call connection device, and an identifier unique to the first call connection device is assigned to the external line terminal that has transmitted the registration request. Registering the extension number to be included, and notifying the extension number registered in the outside line terminal from the first call connection device to the second call connection device.

  According to the apparatus or method of the present disclosure, it is possible to register this terminal with a specific extension number by an operation from the terminal and use the extension call with the registered terminal.

It is a figure which shows the structural example of a communication system. It is a figure which shows an example of the hardware constitutions of a local server. It is a figure which shows an example of the hardware constitutions of a center server. It is a figure which shows an example of a function structure of a local server. It is a figure which shows an example of extension utilization data. It is a figure which shows the example of the header of the INVITE message to which the extension number of the transmission side was set. It is a figure which shows an example of use permission data. It is a figure which shows an example of a function structure of a center server. It is a figure which shows an example of profile data. It is a figure which shows an example of address data. It is a figure which shows an example of local network data. It is a figure which shows the 1st example of the signal sequence at the time of registration of an extension number. (A) shows an example of use permission data, and (B) and (C) show changes in profile data and extension use data by the registration processing of FIG. It is explanatory drawing of the incoming call operation | movement to the mobile telephone registered in FIG. It is explanatory drawing of the transmission operation | movement of the mobile telephone registered in FIG. It is a figure which shows the 1st example of the signal sequence at the time of cancellation | release of an extension number. (A) and (B) show changes in profile data and extension usage data due to the release processing of FIG. It is a figure which shows the 2nd example of the signal sequence at the time of registration of an extension number. (A) shows an example of usage permission data, and (B) and (C) show changes in profile data and extension usage data due to the registration processing of FIG. It is a figure which shows the 2nd example of the signal sequence at the time of cancellation | release of an extension number. (A) and (B) show changes in profile data and extension usage data due to the release processing of FIG. It is a figure which shows the 3rd example of the signal sequence at the time of registration of an extension number. (A) shows an example of use permission data, and (B) and (C) show changes in profile data and extension use data by the registration processing of FIG. It is explanatory drawing of the incoming call operation | movement to the extension terminal registered in FIG. It is explanatory drawing of the transmission operation | movement of the extension terminal registered in FIG. It is a figure which shows the 3rd example of the signal sequence at the time of cancellation | release of an extension number. (A) and (B) show changes in profile data and extension usage data due to the release processing of FIG. It is explanatory drawing of operation | movement of the center server at the time of switching the terminal registered into an extension number to a mobile telephone. It is explanatory drawing of operation | movement of the center server at the time of profile change request reception. It is explanatory drawing of operation | movement of the center server at the time of a telephone call in case a mobile telephone is a receiving side. It is explanatory drawing of operation | movement of the center server at the time of a telephone call in case a mobile telephone is a transmission side. It is explanatory drawing of operation | movement of a local server at the time of switching the terminal registered into an extension number to a mobile telephone. It is explanatory drawing of the registration process of FIG. It is explanatory drawing of the cancellation | release process of FIG. It is explanatory drawing of operation | movement of a local server at the time of switching the terminal registered into an extension number to an extension terminal. It is explanatory drawing of the automatic cancellation | release operation | movement of an extension number. It is explanatory drawing of operation | movement of a local server at the time of a telephone call in case an extension terminal is a receiving side. It is explanatory drawing of operation | movement of the local server at the time of a telephone call in case an extension terminal is a transmission side.

<1. Configuration example of communication system>
Hereinafter, preferred embodiments will be described with reference to the accompanying drawings. FIG. 1 is a diagram illustrating a configuration of an example of a communication system. The communication system 1 includes a local area network 2 and an operator network 3. The local network 2 includes a local server 10, extension terminals 11 a to 11 c, an Internet Protocol (IP) network 12, an access point 13 and a gateway device 14, and a local database 15. The local server 10 performs call control of extension calls between the extension terminals 11a to 11c connected to the IP network 12 via the access point 13 using a predetermined call control protocol.

  The carrier network 3 is an external communication network operated by a telecommunications carrier that provides a telephone communication service. The carrier network 3 includes a center server 20, mobile phones 21 a to 21 c, an IP network 22, a base station device 23, a gateway device 24, and a center database 25. User data generated by a telephone call performed by the mobile telephones 21 a to 21 c is transmitted and received by wireless communication with the base station apparatus 23 and transmitted through the gateway apparatus 24 via the IP network 22. The center server 20 performs call control of calls between the mobile telephones 21a to 21c in the carrier network 3 using a predetermined call control protocol.

  In the accompanying drawings and the following description, the gateway device, the database, and the base station device may be referred to as “gateway”, “DB”, and “base station”, respectively. Further, the extension terminals 11a to 11c may be collectively referred to as “extension terminal 11”. The mobile phones 21a to 21c may be collectively referred to as “mobile phone 21”. The extension terminal 11 and the mobile phone 21 may be collectively referred to as “terminal”.

  The IP network 12 of the local network 2 is connected to the operator network 3 via the gateway 14. The local server 10 and the center server 20 perform call control between the extension terminal 11 and the mobile telephone 21 by exchanging call control messages according to a predetermined call control protocol. The call control protocol used for call control between the extension terminal 11 and the mobile telephone 21 may be, for example, SIP (Session Initiation Protocol). In another embodiment, H.264 defined by MGCP (Media Gateway Control Protocol) or ITU-T (International Telecommunication Union Telecommunication Standardization Sector) is used for call control between the extension terminal 11 and the mobile telephone 21. H.323 may be used.

  In the following description, SIP is used as an example of a call control protocol used for call control between the extension terminal 11 and the mobile telephone 21. However, these illustrations are not intended that the call control described herein be applied only to those that use SIP.

  As will be described below, in the local area network 2, a terminal registered with one extension number is switched between a plurality of terminals. For this reason, the local area network 2 includes an internal area DB 15 for registering a terminal assigned with each extension number. The premises DB 15 is a database accessible from the premises server 10.

  The mobile telephone 21 may be registered in the extension number of the local network 2. Therefore, the operator network 3 includes a center DB 25 for registering identification information of the local network 2 in which the mobile phone 21 is registered as an extension. The center DB 25 is a database accessible from the center server 20.

<2. Hardware configuration example>
Next, a hardware configuration example of the local server 10 and the center server 20 illustrated in FIG. 1 will be described. FIG. 2 shows an example of the hardware configuration of the local server 10. The local server 10 includes a processor 40, a memory 41, an auxiliary storage device 42, a network interface circuit 43, and a medium reading device 44. In the following description and accompanying drawings, the network interface may be expressed as “NIF”.

  The processor 40 performs operation control of the local server 10 and call control processing described below. The auxiliary storage device 42 stores a computer program for causing the processor 40 to execute these processes. The auxiliary storage device 42 includes a nonvolatile storage device for storing a computer program. The non-volatile storage device may be, for example, a read only memory (ROM), a flash memory, or a hard disk. The memory 41 stores each data and temporary data used when the processor 40 executes the computer program. The memory 41 may include a random access memory (RAM).

  The NIF circuit 43 is a communication interface circuit for transmitting and receiving packet signals between the local server 10 and the IP network 12. The medium reader 44 reads data stored in a computer-readable portable recording medium. The medium reading device 44 may be, for example, a CD (Compact Disc) -ROM drive device, a DVD (Digital Versatile Disk) -ROM drive device, a flexible disk drive device, or a CD-R (Compact Disc Recordable) drive device. The medium reading device 44 may be a DVD-R (Digital Versatile Disk Recordable) drive device, an MO (Magneto-Optical disk) drive device, or an access device to a flash memory device. A computer program that causes the processor 40 to execute a call control process described below is stored in a computer-readable portable recording medium and distributed. The computer program is read from the portable recording medium by the medium reading device 44 and installed in the auxiliary storage device 42.

  FIG. 3 is a diagram illustrating an example of a hardware configuration of the center server 20. The center server 20 includes a processor 50, a memory 51, an auxiliary storage device 52, a network interface circuit 53, and a medium reading device 54. The processor 50 performs operation control of the center server 20 and call control processing described below. The auxiliary storage device 52 stores a computer program for causing the processor 50 to execute these processes.

  The auxiliary storage device 52 includes a non-volatile storage device for storing a computer program. The nonvolatile storage device may be, for example, a read only memory, a flash memory, or a hard disk. The memory 51 stores data and temporary data used when the processor 50 executes the computer program. The memory 51 may include a random access memory.

  The NIF circuit 53 is a communication interface circuit for transmitting and receiving packet signals between the center server 20 and the IP network 22. The medium reader 54 reads data stored in a computer-readable portable recording medium. The medium reading device 54 may be, for example, a CD-ROM drive device, a DVD-ROM drive device, a flexible disk drive device, or a CD-R drive device. The medium reading device 54 may be an access device to a DVD-R drive device, an MO drive device, or a flash memory device. A computer program that causes the processor 50 to execute call control processing described below is stored and distributed in a computer-readable portable recording medium. The computer program is read from the portable recording medium by the medium reading device 54 and installed in the auxiliary storage device 52.

  The hardware configurations shown in FIGS. 2 and 3 are merely examples for explaining the embodiments. As long as the operation described below is executed, the communication system described in this specification may adopt any other hardware configuration.

<3. Functional configuration example>
Next, functions realized by the hardware configuration will be described. FIG. 4 is a diagram illustrating an example of a functional configuration of the local server 10. The local server 10 includes a call control unit 60, a registration request receiving unit 61, an authentication unit 62, a terminal information registration unit 63, an extension information registration request unit 64, a message generation unit 65, and a voice signal analysis unit 66. The number information specifying unit 67 is provided. The operations of these components are executed by the processor 40 shown in FIG. The details of the operation of these components of the local server 10 will be described in “4. Examples of switching operation” below, but this section will give an overview.

  The call control unit 60 performs call control of extension calls within the local network 2. At that time, the call control unit 60 identifies the terminal currently registered in the extension number. The premises DB 15 stores extension use data 68 that is information on terminals registered in the extension number.

  FIG. 5 is a diagram illustrating an example of the extension usage data 68. The extension usage data 68 includes information elements “extension number”, “initial terminal”, “registration terminal”, “cancellation period”, and “registration time”. The information element “extension number” indicates a target extension number. The information element “initial terminal” indicates the extension number of the extension terminal 11 or the mobile phone number of the mobile phone 21 registered in the initial state in the target extension number. The information element “registered terminal” indicates the extension number of the extension terminal 11 currently registered in the target extension number or the mobile phone number of the mobile phone 21. The information element “cancellation period” designates a period until the registration is automatically canceled after the terminal is registered to the extension number. The registration of the extension number is automatically canceled after the cancellation period elapses from the registration time. The information element “registration time” indicates the time when the extension number for the registration terminal is registered.

  In the following description, the extension terminal 11 and the mobile phone 21 in which the extension number and the mobile phone number are registered in the information element “initial terminal” of the extension use data 68 may be referred to as an initial terminal. The extension terminal 11 and the mobile phone 21 in which the extension number and the mobile phone number are registered in the information element “registered terminal” of the extension usage data 68 may be referred to as a registered terminal.

  For example, the data in the first row in FIG. 5 indicates that the initial terminal and registered terminal registered with the extension number “711-1111” are the extension terminal 11 with the extension number “711-1111” and the mobile telephone number “090- This indicates that the mobile phone 21 is “1234-1111”. This data also indicates that the registration of the mobile phone 21 with the mobile phone number “090-1234-1111” is automatically canceled in 2 hours. This data also indicates that the registration time is “13:01:32”. That is, this registration is automatically canceled at 15: 1: 32.

  The data in the second row in FIG. 5 indicates that the initial terminal and the registered terminal registered with the extension number “711-3333” are the extension mobile phone 21 and the mobile phone number “0” of the mobile phone number “090-1234-3333”, respectively. 080-3456-2222 "indicates the mobile phone 21. This data also indicates that the registration of the mobile telephone 21 with the mobile telephone number “080-3456-2222” is automatically canceled in one hour. This data also indicates that the registration time is “14:11:54”. That is, this registration is automatically canceled at 15:11:54.

  Please refer to FIG. When the call from the extension terminal 11 designates the extension number registered in the mobile telephone 21 as the called party number, the call control unit 60 executes call connection processing with the center server 20. When the call control unit 60 generates an INVITE message as a session connection message, the call control unit 60 converts the destination identifier into a mobile telephone number registered in the extension usage data 68. Further, the call control unit 60 sets the extension number on the calling side in the header of the INVITE message. The call control unit 60 transmits an INVITE message to the center server 20.

  An example of the header of an INVITE message in which an extension number is set is shown in FIG. The local server 10 sets the extension number on the calling side in the special header indicated by reference numeral 100. The special header includes a tag “Special-headerA” indicating a special header including an extension number set on the local server 10 side, and a URL (Uniform Resource Locator) including an extension number “711-2222” on the calling side. Have.

  Please refer to FIG. In the call connection between the extension terminals 11, when the called extension terminal 11 is registered as a registered terminal, the call control unit 60 converts the called party number into the extension number of the registered terminal, and between the extension terminals. Connect the call.

  The registration request receiving unit 61 receives terminal transmissions to “registration number” and “cancellation number” which are predetermined telephone numbers. The registration number is used to start a registration process for registering a terminal in the extension usage data 68 as a registration terminal. The cancellation number is used to start a cancellation process for canceling registration of the terminal in the extension usage data 68.

  The authentication unit 62 performs authentication processing of the terminal that has transmitted to the registration number. The authentication unit 62 determines whether or not the terminal that has transmitted to the registration number is a terminal that is permitted to register to the extension number. The on-premises DB 15 stores use permission data 69 that is information on terminals that are permitted to register to the extension number.

  FIG. 7 is a diagram illustrating an example of the usage permission data 69. The use permission data 69 includes information elements “extension number”, “registrable terminal”, “password”, and “release period”. The information element “extension number” indicates a target extension number. The information element “registrable terminal” indicates an extension number or a mobile telephone number of a terminal that is permitted to be registered as a registered terminal to the target extension number. The information element “password” indicates a password to be input at the time of registration. The information element “cancellation period” designates a period until registration is automatically canceled after a terminal designated by “registrable terminal” is registered as an extension number.

  In the following description, the extension terminal 11 and the mobile phone 21 in which the extension number and the mobile phone number are registered in the information element “registerable terminal” of the extension usage data 68 may be referred to as a registerable terminal.

  For example, in the data in the first row of FIG. 7, the registerable terminal with the extension number “711-1111” is the mobile phone 21 with the mobile phone number “090-1234-1111”, and the password for registration is “ 1111 ". This data also indicates that the registration of the mobile phone 21 with the mobile phone number “090-1234-1111” is automatically canceled in 2 hours.

  The data in the second row of FIG. 7 shows that the registerable terminal with the extension number “711-3333” is the mobile phone 21 with the mobile phone number “080-3456-2222”, and the password for registration is “2222”. Indicates that This data also indicates that the registration of the mobile telephone 21 with the mobile telephone number “080-3456-2222” is automatically canceled in one hour.

  The data in the third row in FIG. 7 indicates that the registerable terminal with the extension number “711-3333” is the extension terminal 11 with the extension number “711-4444” and the password for registration is “4444”. Indicates. This data also indicates that the registration of the extension terminal 11 with the extension number “711-4444” is automatically canceled in 3 hours.

  The authentication unit 62 determines whether or not the terminal that has transmitted to the registration number is a registerable terminal in the terminal authentication process. In addition, the authentication unit 62 determines whether or not the password input from the terminal matches the password specified by the usage permission data. The authentication unit 62 allows the terminal to be registered only when the terminal that has transmitted to the registration number is a registerable terminal and the passwords match.

  The message generation unit 65 generates and transmits a message that prompts the terminal that has transmitted to the registration number to input the extension number and password of the registration destination. The message may be automatic voice guidance such as a talkie, or may be visible information displayed on a display device of the terminal. When the registered extension number and password are input as an audio signal such as DTMF (Dual-Tone Multi-Frequency), the audio signal analysis unit 66 gives the analysis result of the audio signal to the authentication unit 62.

  The terminal information registration unit 63 executes registration processing and cancellation processing of the registered terminal with respect to the extension usage data 68. The terminal information registration unit 63 registers the terminal that has transmitted to the registration number in the extension usage data 68 as a registration terminal. The terminal information registration unit 63 cancels the registration of the extension number for the terminal that has transmitted to the cancellation number, and returns the terminal registered in this extension number to the initial terminal. Also, the terminal information registration unit 63 cancels the registration of the extension number for the registered terminal when the period during which the registered terminal is registered in the extension usage data 68 reaches the period specified by the information element “release period”. The terminal registered with this extension number is returned to the initial terminal.

  Please refer to FIG. The extension information registration request unit 64 transmits a profile change request to the center server 20 to notify the change in the registration state of the extension number to the mobile phone 21 due to the registration process and the release process. An example of a registration process accompanied by a profile change request is a registration process for registering the mobile telephone 21 with an extension number. In this case, the extension information registration request unit 64 notifies the center server 20 of the extension number registered in the mobile telephone 21 by the profile change request. Further, when the initial terminal of the extension number to be registered is the extension mobile telephone 21, the extension information registration request unit 64 notifies the center server 20 of information for specifying the extension mobile telephone 21 by a profile change request. In the profile change request, the extension mobile phone 21 may be specified by the mobile phone number of the extension mobile phone 21, or the extension mobile phone 21 may be indirectly specified by the extension number registered in the extension mobile phone 21. .

  Another example of the registration process accompanied by the profile change request is a registration process for registering the extension terminal 11 to the extension number in which the extension mobile telephone 21 is registered as the initial terminal. In this case, the extension information registration request unit 64 notifies the center server 20 of information for specifying the extension mobile telephone that is the initial terminal by the profile change request.

  An example of the cancellation process with a profile change request is a cancellation process for canceling registration of an extension number to the mobile phone 21. In this case, the extension information registration request unit 64 notifies the center server 20 of information for specifying the mobile phone 21 by a profile change request. In the profile change request, the mobile phone 21 may be specified by the mobile phone number of the mobile phone 21, or the mobile phone 21 may be specified indirectly by the extension number registered in the mobile phone 21. Further, when the initial terminal of the extension number to be canceled is the extension mobile phone 21, the extension information registration request unit 64 notifies the center server 20 of information for specifying the extension mobile phone 21 by a profile change request.

  Another example of the cancellation process with a profile change request is a cancellation process for canceling the registration after the extension terminal 11 is registered at the extension number in which the extension mobile telephone 21 is registered as the initial terminal. In this case, the extension information registration request unit 64 notifies the center server 20 of information for specifying the extension mobile telephone 21 that is the initial terminal by the profile change request.

  When the mobile phone 21 registered as a registration terminal makes a call to an extension number, the number information designating unit 67 converts the calling party number into the extension number registered in the mobile telephone 21, and the calling party number for number display To the receiving terminal. The same applies to the case where the extension terminal 11 registered as the registration terminal sends a call to the extension number.

  Next, functions of the center server 20 will be described. FIG. 8 is a diagram illustrating an example of a functional configuration of the center server 20. The center server 20 includes a call control unit 70, an extension information registration unit 71, and a number information designation unit 72. The operation of these components is executed by the processor 50 shown in FIG. Details of the operation of these components of the center server 20 will be described in “4. Examples of switching operation” below, but this section will give an overview.

  The call control unit 70 performs call control of a call that passes through the carrier network 3. At that time, the call control unit 70 determines whether or not the mobile telephone 21 is registered in the extension number of the local network 2. The center DB 25 stores profile data 73 that is information of the mobile telephone 21 registered in the extension number of the local network 2.

  FIG. 9 is a diagram illustrating an example of the profile data 73. The profile data 73 includes information elements “mobile phone number”, “state”, “extension number”, “prefix”, “premises network ID”, and “premises server ID”. The information element “mobile phone number” indicates the mobile phone number of the target mobile phone 21. The information element “state” indicates whether the registration of the extension number to the target mobile telephone 21 is valid or invalid.

  The information element “extension number” indicates an extension number in which the target mobile phone 21 is registered. The information element “prefix” indicates an extension number prefix in which the target mobile phone 21 is registered. The prefix may be, for example, an upper digit number that is common among all extension numbers used in the local network 2. The information element “local network ID” indicates an identifier of the local network 2 in which the target mobile phone 21 is registered in the extension number. The information element “local server ID” indicates an identifier of the local server 10 in the local network 2 in which the target mobile phone 21 is registered in the extension number. In the following description, individual information registered in the profile data 73 for each mobile phone 21 may be referred to as “profile information” of the mobile phone 21.

  For example, the data in the first row of FIG. 9 is profile information of the mobile phone 21 with the mobile phone number “090-1234-1111”, and this mobile phone 21 is registered with the extension number “711-1111” and registered. Indicates that is valid. This profile information indicates that the prefix of the extension number “711-1111” in which the mobile phone 21 with the mobile phone number “090-1234-1111” is registered is the upper three digits “711” of the extension number. In this profile information, the identifier of the local network 2 in which the extension number is registered in the mobile telephone 21 of the mobile telephone number “090-1234-1111” and the identifier of the local server 10 in the local network 2 are “1” and Indicates “10”.

  The data in the second row in FIG. 9 is profile information of the mobile phone 21 with the mobile phone number “080-3456-2222”, and indicates that the registration of the extension number for this mobile phone 21 is currently invalid.

  The data in the third row in FIG. 9 is the profile information of the mobile phone 21 with the mobile phone number “090-1234-3333”. This mobile phone 21 is registered with the extension number “711-3333” and the registration is valid. Indicates that This profile information indicates that the prefix of the extension number “711-3333” in which the mobile phone 21 with the mobile phone number “090-1234-3333” is registered is the upper three digits “711” of the extension number. In this profile information, the identifiers of the local network 2 in which the extension number is registered in the mobile telephone 21 of the mobile telephone number “090-1234-3333” and the local server 10 in the local network 2 are “1” and “10”, respectively. ".

  Please refer to FIG. When the call from the mobile telephone 21 designates the extension number of the local network 2 as the called party number, the call control unit 70 refers to the profile data 73 and is the registration of the extension number for the mobile telephone 21 valid? Judge whether or not. When the registration of the extension number for the mobile phone 21 is valid, the call control unit 70 refers to the profile data 73 to identify the local network 2 and the local server 10. The call control unit 70 executes call connection processing with the local server 10 specified by the information element “local server ID” of the profile data 73.

  When the call control unit 70 generates the INVITE message, the call control unit 70 acquires the extension number registered in the mobile telephone 21 from the profile data 73 and sets it in the header of the INVITE message as the extension number on the calling side. With reference to FIG. 6, an example of the header of the INVITE message in which the extension number is set in the center server 20 will be described. The center server 20 sets the extension number on the calling side in the special header indicated by reference numeral 101. The special header has a tag “Special-headerB” indicating that it is a special header including an extension number set on the center server 20 side, and a URL including an extension number “711-1111” on the calling side.

  Please refer to FIG. The call control unit 70 transmits an INVITE message to the local server 10. The call control unit 70 specifies the address of the local server 10 that is the message transmission destination in accordance with the “local server ID” specified in the profile data 73. For example, the call control unit 70 identifies the address of the destination local server 10 according to the address data 74 as shown in FIG. The address data 74 includes information elements “premises server ID” and “address”. The information element “local server ID” indicates an identifier of the target local server 10. The address of the local server 10 of the information element “address” is shown. The address data 74 is accommodated in the center DB 25.

  Please refer to FIG. The call control unit 70 transmits an INVITE message for connecting a call between the mobile phone 21 and the local server 10 to the local server 10 when the called party number from the mobile phone 21 is a registration number or a cancellation number. By calling the registration number or the release number, a registration process for registering the terminal as the registration terminal in the extension usage data 68 or a cancellation process for canceling the registration of the extension usage data 68 starts.

  When the registration process or the cancellation process is completed, the extension information registration unit 71 receives from the local server 10 a profile change request for notifying a change in the registration state of the extension number to the mobile phone 21 due to the registration process and the cancellation process. When the profile change request is a request accompanying the registration process of the mobile phone 21 to the extension number, the extension information registration unit 71 is notified of the extension number registered in the mobile phone 21 by the profile change request. The extension information registration unit 71 registers the extension number and its prefix in the profile data 73, and sets the value of the information element “state” to “valid”.

  The extension information registration unit 71 specifies the identifier of the local network 2 in which the extension number is registered in the mobile telephone 21 and the identifier of the local server 10 in the local network 2 based on the prefix. The extension information registration unit 71 registers these identifiers in the profile data 73. The center DB 26 stores the identifier of the local server 10 in the local network 2 and the local network data 75 that is information on the extension number prefix.

  FIG. 11 is a diagram showing an example of the local network data 75. The local network data 75 includes information elements “local network ID”, “local server ID”, and “prefix”. The information element “local network ID” indicates an identifier of the target local network 2. The information element “local server ID” indicates an identifier of the local server 10 provided in the target local network 2. The information element “prefix” indicates an extension number prefix in the target local area network 2.

  For example, in the data on the first line in FIG. 11, the identifier value of the local server 10 provided in the local network 2 with the identifier “1” is “10”, and the extension prefix of the local network 2 is “711”. It shows that. In the second row of data in FIG. 11, the identifier value of the local server 10 provided in the local network 2 with the identifier “2” is “11”, and the extension prefix of the local network 2 is “712”. Indicates.

  The extension information registration unit 71 sets the local network 2 in which the extension number is registered in the mobile telephone 21 and the identifier of the local server 10 in the local network 2 in accordance with the prefix of the extension number notified in the profile change request. 75.

  When the profile change request is a request accompanying the cancellation processing of the extension number registration to the mobile phone 21, the extension information registration unit 71 is notified of information for specifying the mobile phone 21 by the profile change request. The extension information registration unit 71 deletes the extension number, the prefix, the local network 2 and the identifier of the local server 10 in the local network 2 registered in the profile data 73 for the mobile phone 21, and sets the value of the information element “state” to “ Set to Disable.

  When a registration process for registering a terminal with respect to an extension number in which the extension mobile telephone 21 is registered as an initial terminal is performed, the extension information registration unit 71 receives information for specifying the extension mobile telephone 21 in a profile change request. Be notified. The extension information registration unit 71 sets the value of the information element “state” registered in the profile data 73 for the extension mobile telephone 21 to “invalid”, and invalidates the profile information of the extension mobile telephone 21.

  After the extension mobile telephone 21 registers the terminal for the extension number registered as the initial terminal, when this registration cancellation processing is performed, the extension information registration unit 71 stores information for identifying the extension mobile telephone 21. Is notified by a profile change request. The extension information registration unit 71 sets the value of the information element “state” registered in the profile data 73 for the extension mobile telephone 21 to “valid”, and validates the profile information of the extension mobile telephone 21.

  When receiving a call for an extension call addressed to the mobile phone 21 registered as a registered terminal, the number information specifying unit 72 acquires the extension number on the caller side set in the header of the INVITE message. The number information specifying unit 72 notifies the terminal on the receiving side of the acquired extension number as the calling party number for number display.

  Note that the functional configuration diagrams of FIGS. 4 and 8 mainly illustrate configurations related to the functions of the local server 10 and the center server 20 described in this specification. The local server 10 and the center server 20 may include other components than the illustrated components.

<4. Example of switching operation>
Next, an example of a terminal switching operation registered in the extension number will be described. An example of setting the extension number and mobile telephone number used in this description is shown below.
Extension terminal 11a: extension number 711-1111
Extension terminal 11b: extension number 711-2222
Extension terminal 11c: extension number 711-4444
Mobile phone 21a: Mobile phone number 090-1234-1111
Mobile phone 21b: Mobile phone number 080-3456-2222
Extension mobile phone 21c: Mobile phone number 090-1234-3333
Extension 711-3333
The extension mobile phone is a mobile phone to which an extension number is assigned as an initial terminal.

<4.1. When switching the terminal registered with an extension number from an extension terminal to a mobile phone>
As an example of the first switching operation, it is assumed that the terminal registered with the extension number 711-1111 is switched from the extension terminal 11a to the mobile phone 21a. FIG. 12 shows a first example of a signal sequence when an extension number is registered. The series of operations described with reference to FIG. 12 may be interpreted as a method including a plurality of procedures. In this case, “operation” may be read as “step”. The operations shown in FIGS. 14 to 16, 18, 20, 20, 24 to 26, and 28 to 38 are the same.

  In operation AA, the registration number is dialed by the mobile telephone 21a. In operation AB, the call control unit 70 of the center server 20 transmits an INVITE message for connecting a call addressed to the registration number to the local server 10. In operation AC, the call control unit 60 of the local server 10 returns a 180 Ringing message indicating that a call is being made to the center server 20. When the registration request receiving unit 61 accepts the call, the call control unit 60 returns a 200 OK message, which is a response message to the INVITE message, to the center server 20 in operation AD. As a result, a call between the mobile telephone 21a and the local server 10 is established, and a voice call is possible.

  In operation AE, the message generation unit 65 transmits to the mobile phone 21a an acceptance message that prompts the mobile phone 21a to input an extension number to be registered for the authentication processing of the mobile phone 21a by the authentication unit 62. In operation AF, the mobile phone 21a inputs the extension number “711-1111” by DTMF. In operation AG, the message generator 65 transmits a password request message for prompting the input of a password to the mobile phone 21a. In operation AH, the mobile phone 21a inputs the password “1111” using DTMF.

  The authentication unit 62 refers to the use permission data 69 and determines whether or not the mobile phone 21a is permitted to register the extension number “711-1111”. FIG. 13A shows an example of use permission data. As shown in the figure, the mobile phone 21a with the mobile phone number “090-1234-1111” is designated in the use permission data 69 as a registerable terminal with the extension number “711-1111”. Next, the authentication unit 62 determines whether or not the input password matches the password “1111” specified for extension registration. The password “1111” input as shown in FIG. 13A matches the password specified in the usage permission data 69. As a result, the authentication unit 62 permits registration of the mobile phone 21a.

  In operation AI, the extension information registration request unit 64 transmits a profile change request accompanying registration of the mobile telephone 21a to the center server 20. The profile change request notifies the extension number “711-1111”. At this time, the extension information registration request unit 64 may include the call identifier Call-ID included in the header of the INVITE message of operation AB in the profile change request. The extension information registration unit 71 of the center server 20 can specify the mobile phone number “090-1234-1111” of the mobile phone 21a to be registered from the call identifier Call-ID.

  The extension information registration unit 71 of the center server 20 registers the profile information of the mobile phone 21 a in the profile data 73. The upper part of FIG. 13B shows the state of profile data 73 before registration of profile information. In this state, the value of the information element “state” of the profile information of the mobile phone 21a is “invalid”, and “extension number”, “prefix”, “premises network ID”, and “premises server ID” still have values. Not set.

  Based on the prefix “711” of the extension number “711-1111” notified by the profile change request, the extension information registration unit 71 uses the identifier “1” of the local network 2 and the internal network 2 identifier from the local network data 75. The identifier “10” of the local server 10 is acquired. The extension information registration unit 71 sets the information elements “extension number”, “state”, “prefix”, “premises network ID”, and “premises server ID” of the profile data 73 related to the mobile phone 21a to “711-1111”, Register “valid”, “711”, “1”, and “10”. The lower part of FIG. 13B shows the state of the profile data 73 after the registration of the profile information.

  When the registration of the profile information is completed, in operation AJ, the extension information registration unit 71 notifies the extension information registration request unit 64 of a registration result indicating whether the registration is correct. When the registration result is received, the terminal information registration unit 63 registers the mobile phone 21 a in the extension usage data 68. The upper part of FIG. 13C shows the state of the extension usage data 68 before information registration. In this state, the extension number “711-1111” of the extension terminal 11a which is the initial terminal is set in the information element “registered terminal” of the extension usage data 68 relating to the extension number “711-1111”.

  The terminal information registration unit 63 sets the mobile phone number “090-1234-1111” of the mobile phone 21 a and the release period “2 hours” specified in the use permission data 69 for the mobile phone 21 a to the information element of the extension use data 68. Register in “Registration Terminal” and “Release Period”. Further, the terminal information registration unit 63 registers the current time in the information element “registration time”. The lower part of FIG. 13C shows the state of the extension use data 68 after information registration.

  Thereafter, in operation AK, the message generator 65 transmits a registration completion message notifying the completion of registration of the mobile phone 21a to the mobile phone 21a. In operation AL, the call control unit 60 of the local server 10 transmits a BYE message requesting the end of the call to the center server 20. In operation AM, the call control unit 60 of the center server 20 transmits a 200 OK message to the local server 10 in response to the BYE message. In operation AN, the call control unit 60 disconnects the mobile telephone 21a. With the above operation, registration of the mobile telephone 21a to the extension number “711-1111” is completed, and it becomes possible to make and receive an extension call using the mobile telephone 21a.

<4.2. Making and receiving extension calls by mobile phone 21a>
Next, an operation when making and receiving an extension call with the registered mobile phone 21a will be described. FIG. 14 is an explanatory diagram of an incoming call operation to the mobile phone 21a registered in FIG.

  In operation BA, the extension number “711-1111” registered in the mobile telephone 21a is dialed in the extension terminal 11b of the extension number “711-2222”. In operation BB, the control unit 60 of the local server 10 receives a call for the called party number “711-1111”. The call control unit 60 refers to the extension use data 68 in the lower part of FIG. 13C and selects the mobile phone 21a having the mobile phone number “090-1234-1111” registered in the extension number “711-1111”. Identify. In operation BC, the call control unit 60 converts the called party number from “711-1111” to the mobile telephone number “090-1234-1111” registered in the extension usage data 68.

  In operation BD, the call control unit 60 transmits an INVITE message to the center server 20. The called party number specified in the INVITE message is “090-1234-1111”, and the calling party number is “711-2222”. The call control unit 60 sets the extension number “711-2222” on the calling side in the header of the INVITE message. The call control unit 70 of the center server 20 receives the INVITE message.

  The call control unit 70 refers to the profile data 73 in the lower part of FIG. 13B to determine whether or not the mobile phone 21a is registered in the extension number of the local network 2. When the mobile telephone 21a is registered in the extension number, the number information specifying unit 72 acquires the extension number “711-2222” on the caller side set in the header of the INVITE message.

  In operation BE, the call control unit 70 calls the mobile phone 21a. At this time, the number information specifying unit 72 notifies the mobile phone 21a of the extension number “711-2222” acquired from the INVITE message as the calling party number for number display. In operation BF, the call control unit 70 transmits a 180 Ringing message to the local server 10. When an off-hook operation is performed on the mobile telephone 21a in operation BG, the call control unit 70 transmits a 200 OK message to the local server 10 in operation BH. As a result, a call is established between the extension terminal 11b and the mobile phone 21a.

  Next, with reference to FIG. 15, the transmission operation of the mobile phone 21a will be described. In operation CA, the extension number “711-2222” is dialed in the mobile telephone 21a. In operation CB, the control unit 70 of the center server 20 receives a call for the called party number “711-2222”.

  In operation CC, the control unit 70 refers to the information element “state” of the profile data 73 in the lower part of FIG. 13B, and registers the extension number for the mobile phone 21a of the mobile phone number “090-1234-1111”. It is determined whether or not is valid. When the registration is valid, the control unit 70 acquires the identifier “1” of the local network 2 and the identifier “10” of the local server 10 based on the profile data 73. Based on these identifiers, the control unit 70 specifies the local network 2 and the local server 10 in which the extension number “711-1111” is registered in the mobile telephone 21a.

  In operation CD, the call control unit 70 transmits an INVITE message to the local server 10. The called party number specified in the INVITE message is “711-2222”, and the calling party number is “090-1234-1111”. The call control unit 70 sets the extension number “711-1111” on the calling side in the header of the INVITE message. The call control unit 60 of the local server 10 receives the INVITE message.

  In operation CE, the call control unit 60 refers to the extension use data 68 in the lower part of FIG. 13C and determines whether or not the mobile telephone 21a on the calling side is registered in the extension number. In the extension use data 68, the mobile telephone 21a is registered with the extension number "711-1111". Therefore, the number information specifying unit 67 converts the calling party number into the extension number “711-1111” registered in the mobile telephone 21 by the extension use data 68. At this time, the number information specifying unit 67 may acquire the extension number “711-1111” on the calling side from the header of the INVITE message. The number information specifying unit 67 may acquire the extension number “711-1111” in which the mobile phone 21 a is registered from the extension use data 68.

  In operation CF, the call control unit 60 calls the extension terminal 11b. At this time, the number information designating unit 67 notifies the extension terminal 11b of the converted extension number “711-1111” as the calling party number for number display. In operation CG, the call control unit 60 transmits a 180 Ringing message to the center server 20. When an off-hook operation is performed at the extension terminal 11b in operation CG, the call control unit 60 transmits a 200 OK message to the center server 20 in operation CI. As a result, a call is established between the extension terminal 11b and the mobile phone 21a.

<4.3. To cancel switching from an extension terminal to a mobile phone>
Next, an operation for canceling the extension registration registered in the mobile telephone 21a will be described. FIG. 16 is a diagram illustrating a first example of a signal sequence at the time of canceling an extension number.

  In operation DA, the release number is dialed by the mobile telephone 21a. In the operation DB, the call control unit 70 of the center server 20 transmits an INVITE message for connecting a call addressed to the registration number to the local server 10. In operation DC, the call control unit 60 of the local server 10 returns a 180 Ringing message to the center server 20. When the registration request receiving unit 61 receives a call in operation DD, the call control unit 60 returns a 200 OK message to the center server 20 in operation AD. As a result, a call between the mobile phone 21a and the local server 10 is established.

  In operation DE, the extension information registration request unit 64 transmits to the center server 20 a profile change request accompanying cancellation of registration of the extension number to the mobile telephone 21a. The profile change request notifies information for specifying the mobile telephone 21a that is the target of extension number registration cancellation.

  The extension information registration unit 71 of the center server 20 cancels the registration of the profile information of the mobile phone 21 a registered in the profile data 73. The upper part of FIG. 17A shows the state of the profile data 73 before the release of profile information. The upper profile data 73 in FIG. 17A is the same as the lower profile data 73 in FIG. The extension information registration unit 71 deletes the contents of the information elements “extension number”, “prefix”, “premises network ID”, and “premises server ID” of the profile information of the mobile phone 21a. Further, the extension information registration unit 71 sets the value of the information element “state” of the profile information of the mobile phone 21 a to “invalid”. The lower part of FIG. 17A shows the state of the profile data 73 after the release of the profile information.

  When the release of the profile information is completed, in operation DF, the extension information registration unit 71 notifies the extension information registration request unit 64 of a release result indicating whether the release is correct. When the cancellation result is received, the terminal information registration unit 63 cancels the registration of the mobile phone 21 a to the extension usage data 68. The upper part of FIG. 17B shows the state of the extension usage data 68 before the registration is canceled. The extension usage data 68 in the upper part of FIG. 17B is the same as the extension usage data 68 in the lower part of FIG.

  The terminal information registration unit 63 returns the terminal number registered in the information element “registered terminal” of the extension usage data 68 relating to the extension number “711-1111” to the extension number “711-1111” of the initial terminal. The terminal information registration unit 63 deletes the values of the information elements “release period” and “registration time”. The lower part of FIG. 17B shows the state of the extension usage data 68 after deregistration.

  In operation DG, the message generator 65 transmits a release completion message informing the mobile phone 21a of the completion of release of the mobile phone 21a. In operation DH, the call control unit 60 of the local server 10 transmits a BYE message to the center server 20. In operation DI, the call control unit 60 of the center server 20 transmits a 200 OK message to the local server 10 in response to the BYE message. In operation DJ, the call control unit 60 disconnects the mobile phone 21a. With the above operation, the registration of the mobile telephone 21a to the extension number “711-1111” is canceled.

<4.4. When switching the terminal to which an extension number is registered from an extension mobile phone to a mobile phone>
Subsequently, an example of the second switching operation will be described. As an example of the second switching operation, it is assumed that the terminal registered at the extension number 711-3333 is switched from the extension mobile telephone 21c to the mobile telephone 21b. FIG. 18 is a diagram showing a second example of a signal sequence at the time of registering an extension number.

  In operation EA, the registration number is dialed by the mobile telephone 21a. Operations EB to ED are the same as operations AB to ED in FIG. As a result of these operations, a call between the mobile telephone 21b and the local server 10 is established, and a voice call becomes possible.

  In operation EE, the message generator 65 transmits to the mobile phone 21a an acceptance message that prompts the user to input an extension number to be registered in the mobile phone 21b. In operation EF, the mobile telephone 21b inputs the extension number “711-3333” by DTMF. In operation EG, the message generator 65 transmits a password request message to the mobile phone 21b. In operation EH, the mobile phone 21b inputs the password “2222” using DTMF.

  The authentication unit 62 refers to the usage permission data 69 and determines whether or not the mobile phone 21b is permitted to register the extension number “711-3333”. FIG. 19A shows an example of use permission data. As shown in the figure, the mobile phone 21b with the mobile phone number “080-3456-2222” is designated in the use permission data 69 as a registerable terminal with the extension number “711-3333”. Next, the authentication unit 62 determines whether or not the input password matches the password “2222” specified for extension registration. The password “2222” input as shown in FIG. 19A matches the password specified in the usage permission data 69. As a result, the authentication unit 62 permits registration of the mobile phone 21b.

  In operation EI, the extension information registration request unit 64 transmits to the center server 20 a profile change request accompanying registration of the extension number “711-3333” to the mobile phone 21b. The profile change request notifies the extension number “711-3333”. The extension information registration unit 71 of the center server 20 registers the profile information of the mobile phone 21b in the profile data 73.

  The upper part of FIG. 19B shows the state of profile data 73 before registration of profile information. In this state, the extension mobile telephone 21c with the mobile telephone number “090-1234-3333” is registered in the extension number “711-3333”, and the mobile telephone 21b is not registered. Therefore, the value “711-3333” relating to the extension number “711-3333” is included in the information elements “extension number”, “prefix”, “premises network ID”, and “premises server ID” of the profile information of the extension mobile telephone 21c. , “711”, “1”, and “10” are set. In addition, the value of the information element “state” of the profile information of the extension mobile telephone 21c is “valid”. On the other hand, the value of the information element “state” of the profile information of the mobile phone 21b is “invalid”, and no value is set for the other information elements.

  Based on the prefix “711” of the extension number “711-3333” notified by the profile change request, the extension information registration unit 71 uses the identifier “1” of the local network 2 and the internal network 2 identifier from the local network data 75. The identifier “10” of the local server 10 is acquired. The extension information registration unit 71 sets the information elements “extension number”, “state”, “prefix”, “premises network ID”, and “premises server ID” of the profile data 73 related to the mobile phone 21b to “711-1111”, Register “valid”, “711”, “1”, and “10”. On the other hand, the extension information registration unit 71 sets the value of the information element “state” of the profile data 73 related to the mobile phone 21c to “invalid”. The lower part of FIG. 19B shows the state of the profile data 73 after the profile information is registered.

  When the registration of the profile information is completed, in operation EJ, the extension information registration unit 71 notifies the extension information registration request unit 64 of a registration result indicating whether the registration is correct. When the registration result is received, the terminal information registration unit 63 registers the mobile telephone 21 b in the extension usage data 68. The upper part of FIG. 19C shows the state of the extension usage data 68 before information registration. In this state, the mobile phone number “090-1234-3333” of the mobile phone 21c, which is the initial terminal, is set in the information element “registered terminal” of the extension usage data 68 relating to the extension number “711-3333”.

  The terminal information registration unit 63 sets the mobile phone number “080-3456-2222” of the mobile phone 21 b and the release period “1 hour” designated by the use permission data 69 for the mobile phone 21 b to the information elements of the extension use data 68. Register in “Registration Terminal” and “Release Period” Also, the terminal information registration unit 63 registers the current time in the information element “registration time” of the extension usage data 68. The lower part of FIG. 19C shows the state of the extension use data 68 after information registration.

  The subsequent operations EK to EN are the same as operations AK to AN in FIG. With the above operation, registration of the mobile telephone 21b to the extension number “711-3333” is completed, and it becomes possible to make and receive an extension call with the mobile telephone 21b.

<4.5. To cancel switching from an extension mobile phone to a mobile phone>
Next, an operation of canceling the extension registration registered in the mobile telephone 21b according to the above “4.4. When switching the terminal whose extension number is registered from the extension mobile telephone to the mobile telephone” will be described. FIG. 20 is a diagram illustrating a second example of a signal sequence when canceling an extension number.

  In operation FA, the release number is dialed by the mobile telephone 21b. Operations FB to FD are the same as operations DB to DD in FIG. As a result of these operations, a call between the mobile telephone 21b and the local server 10 is established, and a voice call becomes possible.

  In operation FE, the extension information registration request unit 64 transmits to the center server 20 a profile change request that accompanies deregistration of the extension number to the mobile phone 21b. The profile change request notifies the center server 20 of information for specifying the mobile phone 21b. The extension information registration unit 71 of the center server 20 cancels the registration of the profile information of the mobile phone 21 b registered in the profile data 73. The extension information registration unit 71 validates the registration of the profile information of the extension mobile telephone 21 c that is the initial terminal registered in the profile data 73.

  The upper part of FIG. 21A shows the state of the profile data 73 before the release of the profile information. The upper profile data 73 in FIG. 21A is the same as the lower profile data 73 in FIG. The extension information registration unit 71 deletes the contents of the information elements “extension number”, “prefix”, “premises network ID”, and “premises server ID” of the profile information of the mobile phone 21b. Further, the extension information registration unit 71 sets the value of the information element “state” of the profile information of the mobile phone 21b to “invalid”, and sets the value of the information element “state” of the profile information of the mobile phone 21c to “valid”. Set. The lower part of FIG. 21A shows the state of the profile data 73 after the release of the profile information.

  When the release of the profile information is completed, in operation FF, the extension information registration unit 71 notifies the extension information registration request unit 64 of a release result indicating whether the release is correct. When the cancellation result is received, the terminal information registration unit 63 cancels the registration of the mobile phone 21 b in the extension usage data 68. The upper part of (B) of FIG. 21 shows the state of the extension usage data 68 before deregistration. The extension usage data 68 in the upper part of FIG. 21B is the same as the extension usage data 68 in the lower part of FIG.

  The terminal information registration unit 63 uses the number of the terminal registered in the information element “registered terminal” of the extension usage data 68 relating to the extension number “711-3333” as the mobile phone number “090-” of the mobile extension telephone 21c that is the initial terminal. Return to 1234-3333 ". The terminal information registration unit 63 deletes the values of the information elements “release period” and “registration time”. The lower part of (B) of FIG. 21 shows the state of the extension usage data 68 after deregistration. In operation FG, the message generator 65 transmits a release completion message to the mobile phone 21b. Operations FH to FJ are the same as operations DH to DJ in FIG. With the above operation, the registration of the mobile telephone 21b with the extension number “711-3333” is cancelled.

<4.6. When switching the extension number from the extension mobile phone to the extension terminal>
Subsequently, an example of the third switching operation will be described. An example of the third switching operation is a case where the terminal registered with the extension number “711-3333” is switched from the extension mobile telephone 21c to the extension terminal 11c that is originally given another extension number “711-4444”. Is assumed. FIG. 22 shows a third example of a signal sequence when registering an extension number.

  In operation GA, the extension number is dialed at the extension terminal 11c. When the registration request receiving unit 61 of the local server 10 accepts the outgoing call, in operation GB, the message generating unit 65 transmits an acceptance message that prompts the extension terminal 11c to input the extension number to be registered. In operation GC, the extension terminal 11c inputs the extension number “711-3333” by DTMF. In operation GD, the message generator 65 transmits a password request message to the extension terminal 11c. In operation GE, the mobile phone 21a inputs the password “4444” using DTMF.

  The authentication unit 62 refers to the use permission data 69 and determines whether or not the mobile phone 21a is permitted to register the extension number “711-1111”. FIG. 23A shows an example of use permission data. As illustrated, the extension terminal 11c having the extension number “711-4444” is designated in the use permission data 69 as a registerable terminal having the extension number “711-3333”. Next, the authentication unit 62 determines whether or not the input password matches the password “4444” specified for extension registration. The password “4444” input as shown in FIG. 23A matches the password specified in the usage permission data 69. As a result, the authentication unit 62 permits registration of the extension terminal 11c.

  In operation GF, the extension information registration request unit 64 transmits a profile change request accompanying the registration of the extension terminal 11 c to the center server 20. The profile change request notifies the center server 20 of information for specifying the extension mobile telephone 21c whose registration is invalidated along with the registration of the extension terminal 11c.

  The extension information registration unit 71 of the center server 20 invalidates the profile information of the extension mobile telephone 21c. The upper part of FIG. 23B shows the state of the profile information before invalidation. In this state, the value of the information element “state” of the profile information of the extension mobile telephone 21c is “valid”, indicating that registration of the extension number “711-3333” to the extension mobile telephone 21c is valid. The extension information registration unit 71 sets the value of the information element “state” of the profile information of the extension mobile telephone 21c to “invalid”. The lower part of FIG. 23B shows the state of the invalid profile information.

  In operation GG, the extension information registration unit 71 notifies the extension information registration request unit 64 of the registration result. The terminal information registration unit 63 registers the extension terminal 11 c in the extension usage data 68. The upper part of FIG. 23C shows the state of the extension usage data 68 before information registration. In this state, the mobile telephone number “090-1234-3333” of the extension mobile telephone 21c, which is the initial terminal, is set in the information element “registered terminal” of the extension usage data 68 relating to the extension number “711-3333”. .

  The terminal information registration unit 63 sets the extension number “711-4444” of the extension terminal 11 c and the release period “3 hours” designated by the use permission data 69 for the extension terminal 11 c, the information element “registered terminal” of the extension use data 68 ”And“ Release period ”. Further, the terminal information registration unit 63 registers the current time in the information element “registration time”. The lower part of FIG. 23C shows the state of the extension usage data 68 after information registration.

  In operation GH, the message generator 65 transmits a registration completion message to the extension terminal 11c. In operation GI, the call control unit 60 disconnects the call with the extension terminal 11c. With the above operation, registration of the mobile phone 21a to the extension number “711-4444” is completed, and the extension number “711-4444” can be used by the mobile phone 11c.

<4.7. Making and receiving extension calls by extension terminal 11c>
Next, an operation when an extension call is made and received at the extension terminal 11c registered in "4.6. Switching destination of extension number from extension mobile phone to extension terminal" will be described. FIG. 24 is an explanatory diagram of an incoming call operation to the extension terminal 11c registered in FIG.

  In operation HA, the extension number “711-3333” registered in the extension terminal 11c is dialed in the extension terminal 11b of the extension number “711-2222”. In operation HB, the control unit 60 of the local server 10 receives a call for the called party number “711-3333”. The call control unit 60 refers to the extension use data 68 in the lower part of FIG. 23C, and is the extension terminal 11c of the extension number “711-4444” originally registered in the extension number “711-3333”. Is identified. In operation HC, the control unit 60 converts the called party number to the extension number “711-4444” registered in the extension usage data 68.

  In operation HD, the control unit 60 calls the extension terminal 11c using the extension number “711-4444”. When an off-hook operation is performed at the extension terminal 11c in operation HE, a call between the extension terminal 11b and the extension terminal 11c is established.

  Next, with reference to FIG. 25, the transmission operation of the extension terminal 11c will be described. In operation IA, the extension number “711-2222” is dialed in the extension terminal 11c. In operation IB, the control unit 60 of the local server 10 receives a call for the called party number “711-2222”.

  In the operation IC, the number information specifying unit 67 converts the calling party number into the extension number “711-3333” registered in the extension terminal 11 c with the extension use data 68. In the operation ID, the call control unit 60 calls the extension terminal 11b. At this time, the number information specifying unit 67 notifies the extension terminal 11b of the converted extension number “711-3333” as the calling party number for number display. When an off-hook operation is performed at the extension terminal 11b in operation IE, a call between the extension terminal 11b and the extension terminal 11c is established.

<4.8. To cancel switching from an extension mobile phone to an extension terminal>
Next, the operation of canceling the extension registration registered in the extension terminal 11c according to the above-mentioned “4.6. Switching the destination of extension number from extension mobile telephone to extension terminal” will be described. FIG. 26 is a diagram illustrating a third example of the signal sequence when canceling the extension number.

  In operation JA, the extension number is dialed at the extension terminal 11c. In operation JB, the extension information registration request unit 64 of the local server 10 transmits to the center server 20 a profile change request accompanying cancellation of registration with the extension terminal 11c. The profile change request notifies the center server 20 of information for specifying the extension mobile telephone 21c whose registration is validated with the cancellation of the registration with the extension terminal 11c.

  The extension information registration unit 71 of the center server 20 validates the profile information of the extension mobile telephone 21c. The upper part of FIG. 27A shows the state of profile information before validation. In this state, the value of the information element “state” of the profile information of the extension mobile telephone 21c is “invalid”, indicating that the registration of the extension number “711-3333” to the extension mobile telephone 21c is invalid. The extension information registration unit 71 sets the value of the information element “state” of the profile information of the extension mobile telephone 21c to “valid”. The lower part of FIG. 27A shows the state of the activated profile information.

  In operation JC, the extension information registration unit 71 notifies the extension information registration request unit 64 of the release result. The registration of the extension terminal 11c in the extension usage data 68 is canceled. The upper part of (B) in FIG. 27 shows the state of the extension usage data 68 before deregistration. The extension usage data 68 in the upper part of FIG. 27B is the same as the extension usage data 68 in the lower part of FIG.

  The terminal information registration unit 63 returns the terminal number registered in the information element “registered terminal” of the extension usage data 68 relating to the extension number “711-3333” to the mobile telephone number “090-1234-3333” of the initial terminal. . The terminal information registration unit 63 deletes the values of the information elements “release period” and “registration time”. The lower part of (B) of FIG. 27 shows the state of the extension usage data 68 after deregistration.

  In operation JD, the message generator 65 transmits a release completion message to the extension terminal 11c. In operation JE, the call control unit 60 disconnects the mobile phone 11c. With the above operation, the registration of the mobile telephone 21a to the extension number “711-3333” is released.

<5. Server operation>
<5.1. Operation of center server>
Next, operations of the center server 20 and the local server 10 will be described. First, the operation of the center server 20 will be described.

<5.1.1. Operation when switching>
FIG. 28 is an explanatory diagram of the operation of the center server 20 when the terminal registered in the extension number is switched to the mobile phone 21. In operation KA, the call control unit 70 receives a call from the mobile phone 21 registered to the extension number.

  In operation KB, the call control unit 70 determines whether or not the outgoing call destination number received from the mobile phone 21 is a registration number or a release number. If the receiver side number is a registration number or a cancellation number (operation KB: Y), the processing proceeds to operation KC. When the communication side number is neither the registration number nor the release number (operation KB: N), the center server 20 executes conventional processing.

  In operation KC, the call control unit 70 transmits an INVITE message for connecting a call between the mobile telephone 21 and the local server 10 to the local server 10. In operation KD, the call control unit 70 performs standby processing for a 180 Ringing message and a 200 OK message, which are response messages to the INVITE message. When the 200 OK message is received, the call control unit 70 ends the operation.

  Next, with reference to FIG. 29, it is an explanatory diagram of the operation of the center server 20 when a profile change request is received from the local server 10. In operation LA, the extension information registration unit 71 receives a profile change request from the local server 10. In operation LB, the extension information registration unit 71 determines whether the received profile change request is a request accompanying a terminal registration process for an extension number or a request accompanying a cancellation process. If the profile change request is a request accompanying the registration process (operation LB: Y), the process proceeds to operation LC. If the profile change request is a request accompanying the release process (operation LB: N), the process proceeds to operation LJ.

  In operation LC, the extension information registration unit 71 determines whether the registration target is the mobile phone 21 or not. When the registration target is the mobile phone 21 (operation LC: Y), the processing proceeds to operation LD. If the registration target is not the mobile phone 21 (operation LC: N), the processing proceeds to operation LG. In operation LD, the extension information registration unit 71 acquires the extension number to be registered notified by the profile change request. In operation LE, the extension information registration unit 71 specifies the mobile telephone number of the mobile telephone 21 to be registered. In operation LF, the extension information registration unit 71 registers the profile information of the mobile phone 21 to be registered in the profile data 73. Thereafter, the processing proceeds to operation LG.

  In operation LG, the extension information registration unit 71 determines whether or not the initial terminal of the extension number to be registered is an extension portable terminal. If the initial terminal is an extension mobile terminal (operation LG: Y), the processing proceeds to operation LH. If the initial terminal is not an extension mobile terminal (operation LG: N), the processing proceeds to operation LI. In operation LH, the extension information registration unit 71 invalidates the profile information of the extension mobile terminal. Thereafter, the processing proceeds to operation LI. In operation LI, the extension information registration unit 71 notifies the extension information registration request unit 64 of the registration result. Thereafter, the process ends.

  In operation LJ, it is determined whether or not the cancellation target is the mobile phone 21. When the cancellation target is the mobile phone 21 (operation LJ: Y), the processing proceeds to operation LK. If the cancellation target is not the mobile telephone 21 (operation LJ: N), the processing proceeds to operation LM. In operation LK, the extension information registration unit 71 specifies the mobile phone number of the mobile phone 21 to be canceled. In operation LL, the extension information registration unit 71 deletes the profile information of the mobile phone 21 to be canceled. Thereafter, the processing proceeds to operation LM.

  In operation LM, the extension information registration unit 71 determines whether or not the initial terminal of the extension number to be canceled is an extension mobile terminal. If the initial terminal is an extension mobile terminal (operation LM: Y), the processing proceeds to operation LN. If the initial terminal is not an extension mobile terminal (operation LM: Y), the processing proceeds to operation LO. In operation LN, the extension information registration unit 71 validates the profile information of the extension mobile terminal. Thereafter, the process proceeds to operation LO. In operation LO, the extension information registration unit 71 notifies the extension information registration request unit 64 of the release result. Thereafter, the process ends.

<5.1.2. Operation during a call>
Next, the operation of the center server 20 during a call when the mobile phone 21 is the receiving side will be described with reference to FIG. In operation MA, the call control unit 70 receives the INVITE message from the local server 10. In operation MB, the call control unit 70 determines whether or not the called party number specified in the INVITE message is the subscriber's telephone number. If the called party number is the subscriber's phone (operation MB: Y), the process proceeds to operation MC. In operation MC, the call control unit 70 determines whether or not the extension number registration to the mobile telephone 21 specified by the called party number is valid. If the registration is valid (operation MC: Y), the processing proceeds to operation MD. If the registration is invalid (operation MC: N), the processing proceeds to operation ME.

  In operation MD, the number information specifying unit 72 acquires the extension number on the calling side set in the header of the INVITE message. Thereafter, the process proceeds to operation ME. In operation ME, the call control unit 70 calls the mobile phone 21. At this time, the number information specifying unit 72 notifies the mobile phone 21 of the extension number acquired from the INVITE message as the calling party number for number display. Thereafter, the process ends.

  In operation MF, the call control unit 70 transmits a 404 message indicating that the terminal on the receiving side cannot be found to the local server 10. Thereafter, the process ends.

  Next, with reference to FIG. 31, it is explanatory drawing of operation | movement of the center server 20 at the time of a telephone call in case the mobile telephone 21 is a transmission side. In operation NA, the call control unit 70 receives the dial number transmitted from the mobile phone 21.

  In operation NB, the call control unit 70 determines whether or not the transmitted dial number is an extension number. If the dial number is an extension number (operation NB: Y), the processing proceeds to operation NC. When the dial number is not an extension number (operation NB: N), the center server 20 executes a conventional process. In operation NC, the call control unit 70 determines whether or not the registration of the extension number to the mobile telephone 21 on the caller side is valid. If the registration is valid (operation NC: Y), the processing proceeds to operation ND. If the registration is invalid (operation NC: N), the processing proceeds to operation NH.

  In operation ND, the call control unit 70 identifies the local network 2 of the extension on the called side and the local server 10 based on the profile data 73. In operation NE, the call control unit 70 sets the extension number “711-1111” on the calling side in the header of the INVITE message. In operation NF, the call control unit 70 transmits an INVITE message to the local server 10. In operation NG, the call control unit 70 performs a response message waiting process. When the 200 OK message is received, the call control unit 70 ends the operation.

  In operation NH, the call control unit 70 sends an invalid message to the mobile phone 21 to inform the user of the mobile phone 21 that the extension number on the receiving side is invalid. Thereafter, the operation ends.

<5.2. Operation of campus server>
<5.2.1. Operation when switching>
Next, the operation of the local server 10 will be described. FIG. 32 is an explanatory diagram of the operation of the local server 10 when the terminal registered in the extension number is switched to the mobile phone 21. In operation OA, the call control unit 60 receives an INVITE message from the center server 20. In operation OB, the call control unit 60 returns a 180 Ringing message to the center server 20. When the registration request receiving unit 61 accepts the call, the call control unit 60 returns a 200 OK message to the center server 20 in operation OC.

  In operation OD, the call control unit 60 determines whether or not the caller's mobile phone 21 number notification is in the INVITE message. When the number notification of the mobile phone 21 is in the INVITE message (operation OD: Y), the processing proceeds to operation OE. If the number notification of the mobile phone 21 is not included in the INVITE message (operation OD: N), the processing proceeds to operation OI.

  In operation OE, the call control unit 60 determines whether or not the called party number of the INVITE message is a registered number. If the called party number is a registered number (operation OE: Y), the processing proceeds to operation OF. If the called party number is not a registered number (operation OE: N), the process proceeds to operation OG. In operation OF, the registration request receiving unit 61 executes extension registration processing for the mobile telephone 21 on the transmission side. The registration process will be described later with reference to FIG. Thereafter, the process proceeds to operation OJ.

  In operation OG, the call control unit 60 determines whether or not the called party number of the INVITE message is a release number. If the called party number is a cancellation number (operation OG: Y), the processing proceeds to operation OH. When the called party number is not the cancellation number (operation OG: N), the local server 10 executes the conventional process. In operation OH, the registration request receiving unit 61 executes extension registration cancellation processing for the mobile telephone 21 on the transmission side. The release process will be described later with reference to FIG. Thereafter, the process proceeds to operation OJ.

  In operation OI, the message generator 65 sends a reconnection request message to the mobile phone 21 and prompts the user of the mobile phone 21 to turn on the number notification setting on the caller side to reconnect. Thereafter, the process proceeds to operation OJ. In operation OJ, the call control unit 60 transmits a BYE message to the center server 20. In operation OK, the call control unit 60 transmits a 200 OK message from the center server 20. Thereafter, the operation ends.

  Here, the registration process of FIG. 32 will be described with reference to FIG. In operation PA, the message generator 65 transmits a reception message to the registration target terminal. In operation PB, the registration request receiving unit 61 receives the extension number of the registration destination from the registration target terminal. In the operation PC, the authentication unit 62 determines whether or not registration of the registration target terminal is permitted to the received extension number. If registration is permitted (operation PC: Y), the processing proceeds to operation PD. If registration is not permitted (operation PC: N), the processing proceeds to operation PK.

  In operation PD, the message generation unit 65 transmits a password request message to the registration target terminal. In operation PE, the registration request receiving unit 61 receives a password from a registration target terminal. In operation PF, the authentication unit 62 determines whether or not the input password matches the password specified for extension registration. If the passwords match (operation PF: Y), the processing proceeds to operation PG. If the passwords do not match (operation PF: N), the processing proceeds to operation PL.

  In operation PG, the extension information registration request unit 64 transmits a profile change request accompanying terminal registration to the center server 20. In operation PH, the extension information registration request unit 64 receives the registration result from the center server 20. In operation PI, the terminal information registration unit 63 registers the terminal to the extension number. In operation PJ, the message generation unit 65 transmits a registration completion message informing the terminal registration completion to the terminal. Thereafter, the operation ends.

  In operation PK, the message generation unit 65 sends a reconnection request message to the terminal to be registered, and prompts the user of the terminal to specify the correct extension number and retry connection. Thereafter, the operation ends. In operation PL, the message generator 65 sends an authentication failure message to the terminal to be registered, and notifies the terminal user that the password is incorrect. Thereafter, the operation ends.

  Next, with reference to FIG. 34, the release process of FIG. 32 will be described. In operation QA, the terminal information registration unit 63 determines whether or not the terminal to be canceled is registered in the extension usage data 68 as a terminal that uses the extension. If the terminal to be canceled is registered (operation QA: Y), the processing proceeds to operation QB. If the terminal to be canceled is registered (operation QA: N), the process proceeds to operation QG.

  In operation QB, the extension information registration request unit 64 transmits a profile change request accompanying the release of the terminal to the center server 20. In operation QC, the extension information registration request unit 64 receives the release result from the center server 20. In operation QD, the terminal information registration unit 63 cancels the registration of the terminal to the extension number. In operation QE, the message generation unit 65 transmits a registration completion message notifying the completion of terminal release to the terminal to be released. In operation QF, the terminal information registration unit 63 registers the initial terminal of the extension number in which the released terminal is registered in the extension number. Thereafter, the operation ends.

  In operation QG, the message generator 65 sends a cancellation failure message to the terminal to be canceled to prompt the user of the terminal that the cancellation process has failed.

  Next, with reference to FIG. 35, it is explanatory drawing of operation | movement of the local server 10 at the time of switching the terminal registered into an extension number to the extension terminal 11. FIG. In operation RA, the call control unit 60 receives a call from the extension terminal 11. In operation RB, the call control unit 60 determines whether the number notification of the extension terminal 11 on the caller side is in the INVITE message. If there is a caller's number notification for outgoing calls from the extension terminal 11 (operation RB: Y), the processing proceeds to operation RC. If there is no caller's number notification for outgoing calls from the extension terminal 11 (operation RB: N), the processing proceeds to operation RH.

  In operation RC, the call control unit 60 determines whether or not the called party number is a registered number. If the called party number is a registered number (operation RC: Y), the processing proceeds to operation RD. If the called party number is not a registered number (operation RC: N), the processing proceeds to operation RE. In operation RD, extension registration processing to the extension terminal 11 on the transmission side is executed. The registration process is the same as the process described above with reference to FIG. Thereafter, the process proceeds to operation RH.

  In operation RE, the call control unit 60 determines whether or not the called party number is a release number. If the called party number is a release number (operation RE: Y), the processing proceeds to operation RF. When the called party number is not the cancellation number (operation RE: N), the local server 10 executes the conventional process. In operation RF, extension registration cancellation processing for the extension terminal 11 on the transmission side is executed. The release process will be described later with reference to FIG. Thereafter, the process proceeds to operation RH.

  In operation RG, the message generator 65 sends a reconnection request message to the extension terminal 11 and prompts the user of the extension terminal 11 to turn on the number notification setting on the calling side to reconnect. In operation RH, the call control unit 60 disconnects the call with the extension terminal. Thereafter, the operation ends.

<5.2.2. Automatic release action>
Next, the automatic extension number canceling operation will be described with reference to FIG. In operation SA, the terminal information registration unit 63 determines any extension number registered in the extension usage data 68 as a check target for automatic cancellation. In operation SB, the terminal information registration unit 63 determines whether the terminal currently registered with the extension number is an initial terminal. If the currently registered terminal is not the initial terminal (operation SB: Y), the process proceeds to operation SC. If the currently registered terminal is the initial terminal (operation SB: N), the process proceeds to operation SG.

  In operation SC, the terminal information registration unit 63 determines whether or not the period indicated by the information element “release period” has elapsed from the registration time of the target extension number indicated by the information element “registration time” of the extension usage data 68. . When the cancellation period has elapsed (operation SC: Y), the processing proceeds to operation SD. If the release period has not elapsed (operation SC: N), the processing proceeds to operation SG.

  In operation SD, the extension information registration request unit 64 transmits a profile change request accompanying the release of the terminal to the center server 20. In operation SE, the extension information registration request unit 64 receives the release result from the center server 20. In operation SF, the terminal information registration unit 63 cancels the registration of the terminal to the extension number.

  In operation SG, the terminal information registration unit 63 determines whether or not the check processes of operations SB to SF have been executed for all the extension numbers. When the check process is completed for all the extension numbers (operation SG: Y), the process ends. If there is an extension number that has not been checked (operation SG: N), the processing proceeds to operation SH. In operation SH, the terminal information registration unit 63 determines another extension number as a check target, and returns the process to operation SB.

<5.2.3. Operation during a call>
Next, the operation of the local server 10 during a call when the extension terminal 11 is the receiving side will be described with reference to FIG. In operation TA, the call control unit 60 receives the INVITE message from the center server 20. In operation TB, the call control unit 60 determines whether or not the called party number specified in the INVITE message is an extension number being registered in the extension usage data 68. If the called party number is the registered extension number (operation TB: Y), the processing proceeds to operation TC. If the called party number is not a registered extension number (operation TB: N), the local server 10 executes the conventional process.

  In operation TC, the call control unit 60 refers to the extension usage data 68 and determines whether or not the terminal on the calling side is registered in the extension number. If the calling terminal is registered in the extension number (operation TC: Y), the processing proceeds to operation TD. If the calling terminal is not registered in the extension number (operation TC: N), the processing proceeds to operation TE. In operation TD, the number information specifying unit 67 converts the calling party number into an extension number registered in the calling terminal with the extension usage data 68.

  In operation TE, the call control unit 60 calls the extension terminal 11. Thereafter, the process ends.

  Next, the operation of the local server 10 during a call when the extension terminal 11 is the calling side will be described with reference to FIG. In operation UA, the call control unit 60 receives the dial number transmitted from the extension terminal 11. In operation UB, the call control unit 60 determines whether or not the called party number is an extension number being registered in the extension usage data 68. If the called party number is registered (operation UB: Y), the processing proceeds to operation UC. When the called party number is not registered (operation UB: N), the local server 10 executes the conventional process.

  In operation UC, the call control unit 60 determines whether or not the called party number is an extension number. If the called party number is not an extension number (operation UC: N), the process proceeds to operation UD. If the called party number is an extension number, the process proceeds to the operation UI. In operation UD, the call control unit 60 designates the mobile telephone number of the incoming mobile telephone 21 registered in the extension usage data 68 as the incoming telephone number. In operation UE, the call control unit 60 sets the extension number “711-1111” on the calling side in the header of the INVITE message.

  In operation UF, the call control unit 60 transmits an INVITE message to the center server. In operation UG, the call control unit 60 performs a response message waiting process. When the 200 OK message is received, the call control unit 60 ends the operation. In operation UH, the call control unit 60 designates the extension number of the called extension terminal 11 registered in the extension usage data 68 as the called telephone number. In the operation UI, the call control unit 60 connects an extension call between the extension terminal 11 on the transmission side and the reception side. Thereafter, the operation ends.

<6. Effect of Example>
According to the present embodiment, even when a terminal registered for a specific extension number cannot be used, another terminal that can be currently used by the user is registered with this extension number, and an extension call is transmitted and received. be able to.

  Further, when an incoming call is received from the mobile telephone 21 with the extension number registered according to the present embodiment, the terminal on the receiving side is notified of the extension number registered in the mobile telephone 21 as the calling party number for number display. For this reason, when making a return call, the terminal on the receiving side can call the mobile phone 21 on the calling side as it is if it makes a call to the extension number notified as the calling party number as an extension call. For this reason, the user can make a return call to the mobile telephone 21 on the caller side by the same operation as that for making a call to the extension terminal 11 from the incoming call history.

  Further, according to the present embodiment, the registration of the extension number to a terminal other than the initial terminal is canceled when a certain release period has elapsed. For this reason, it is possible to prevent a call from being received by the mobile telephone 21 or other extension terminal 11 that is not originally intended by forgetting the release process.

The following additional notes are further disclosed with respect to the embodiment including the above examples.
(Appendix 1)
A call connection device for performing call connection processing of an extension terminal,
A call control unit that performs connection processing of a call that is transmitted from the external line terminal with another call connection device that performs call connection processing of the external line terminal;
A registration request receiving unit that receives an extension registration request transmitted from the external terminal in a call to the external terminal connected by the call control unit;
A terminal registration unit for registering an extension number including an identifier unique to the call connection device to an external terminal that has transmitted a registration request;
A notification unit for notifying the other call connection device of the extension number registered in the external terminal;
A call connection device comprising:
(Appendix 2)
The call control unit performs call connection processing for connecting a call of an extension terminal having an extension number registered in an external terminal as a called party number with the other call connection device. The call connection device described.
(Appendix 3)
The call connection device according to appendix 2, wherein the call control unit transmits a call connection request to which the extension number of the extension terminal on the transmission side is added to the other call connection device.
(Appendix 4)
As described in any one of appendices 1 to 3, further comprising a number notifying unit for notifying the extension terminal on the receiving side of the extension number registered in the outside line terminal as the calling party number of the outgoing terminal. Call connection device.
(Appendix 5)
The terminal registration unit registers the extension number registered in the other external terminal in the external terminal that has transmitted the registration request,
The call connection device according to any one of appendices 1 to 4, wherein the notification unit notifies the other call connection device of information for specifying the other external line terminal.
(Appendix 6)
The call connection device according to any one of appendices 1 to 5, wherein the terminal registration unit cancels registration after a predetermined period of time has elapsed after registering an extension number with an external terminal.
(Appendix 7)
The registration request receiving unit receives a registration request for an extension number registered in an external terminal from the extension number,
The terminal registration unit registers the extension number registered in the external terminal in the extension terminal that transmitted the registration request,
The notifying unit notifies the other call connection device of information for specifying an external terminal registered in the extension number in which the extension terminal is registered. The call connection device according to 1.
(Appendix 8)
The call connection device according to any one of appendix 7, wherein the terminal registration unit cancels the registration after a predetermined period of time has elapsed after registering the extension number in the extension terminal.
(Appendix 9)
A call connection device that performs call connection processing of an external terminal,
A call control unit for performing a call connection process between an external terminal and an extension terminal with another call connection apparatus for performing a call connection process for the extension terminal;
A receiving unit for receiving, from the other call connection device, an extension number including an identifier unique to the other call connection device registered in the external line terminal by the other call connection device;
The call control unit performs a call connection process for connecting the call with the other call connection device identified by the extension number specified as the called party number of the call of the external terminal.
A call connection device.
(Appendix 10)
Number notification for notifying the receiving-side external terminal of the extension number of the calling-side extension terminal added to the call connection request for connecting the call from the extension terminal to the external-line terminal as the calling-side extension number of the call The call connection device according to appendix 9, further comprising: a section.
(Appendix 11)
Between the first call connection device that performs the call connection processing of the extension terminal and the second call connection device that performs the call connection processing of the external line terminal, the connection processing of the call originating from the external terminal is performed,
An extension registration request transmitted from the external terminal in the connected call is received by the first call connection device;
Register an extension number including an identifier unique to the first call connection device to the external terminal that has transmitted the registration request;
Notifying the extension number registered in the external terminal from the first call connection device to the second call connection device;
A call control method comprising:

DESCRIPTION OF SYMBOLS 1 Communication system 2 Local network 3 Provider network 10 Local server 11, 11a-11c Extension terminal 12, 22 IP network 20 Center server 21, 21a-21c Mobile telephone

Claims (7)

A call connection device for performing call connection processing of an extension terminal,
A call control unit that performs connection processing of a call that is transmitted from the external line terminal with another call connection device that performs call connection processing of the external line terminal;
A registration request receiving unit that receives an extension registration request transmitted from the external terminal in a call to the external terminal connected by the call control unit;
A terminal registration unit for registering an extension number including an identifier unique to the call connection device to an external terminal that has transmitted a registration request;
A notification unit for notifying the other call connection device of the extension number registered in the external terminal;
A call connection device comprising:   2. The call control unit performs call connection processing for connecting a call of an extension terminal having an extension number registered in an external terminal as a called party number with the other call connection device. The call connection device according to 1.   The call connection device according to claim 2, wherein the call control unit transmits a call connection request to which the extension number of the extension terminal on the transmission side is added to the other call connection device.   The number notification part which notifies the extension number registered in the outside line terminal to the extension terminal of a receiving side as a calling party number of the call of an outside line terminal is provided, The number notification part characterized by the above-mentioned. Call connection device.   5. The call connection device according to claim 4, wherein the terminal registration unit cancels the registration after a predetermined period of time has elapsed after registering the extension number in the outside line terminal. A call connection device that performs call connection processing of an external terminal,
A call control unit for performing a call connection process between an external terminal and an extension terminal with another call connection apparatus for performing a call connection process for the extension terminal;
A receiving unit for receiving, from the other call connection device, an extension number including an identifier unique to the other call connection device registered in the external line terminal by the other call connection device;
The call control unit performs a call connection process for connecting the call with the other call connection device identified by the extension number specified as the called party number of the call of the external terminal.
A call connection device. Between the first call connection device that performs the call connection processing of the extension terminal and the second call connection device that performs the call connection processing of the external line terminal, the connection processing of the call originating from the external terminal is performed,
An extension registration request transmitted from the external terminal in the connected call is received by the first call connection device;
Register an extension number including an identifier unique to the first call connection device to the external terminal that has transmitted the registration request;
Notifying the extension number registered in the external terminal from the first call connection device to the second call connection device;
A call control method comprising:

Images