Abstract:
This invention is to provide a technology for preventing information from being leaked from a mobile phone. For this purpose, this invention includes: receiving a request for data to select a calling destination from a first mobile phone capable of executing voice communication and data communication; identifying calling destination candidates registered in a data storage in association with a user of the first mobile phone by identification information other than telephone numbers of the calling destination candidates; and transmitting data to specify and select anyone of the identified calling destination candidates by the identification information other than the telephone numbers of the calling destination candidates, to the first mobile phone. Because the telephone number of the client is not sent to the mobile phone, the leakage of the client information is prevented, even if the mobile phone is stolen.

Description:
TECHNICAL FIELD OF THE INVENTION  
       [0001]     The present invention relates to an information leakage prevention technology.  
       BACKGROUND OF THE INVENTION  
       [0002]     The utilization of mobile phones in business increases, and personal mobile phones may also be used in business in some cases. When such a mobile phone is lost, client information of a company could flow out, and this will raise a problem.  
         [0003]     In order to solve the problem, there exists a mechanism in which a server on the side of a telephone company is provided with a telephone directory, and the server transmits telephone directory data to a mobile phone, if necessary, and on receiving a calling request for a specific calling destination from the mobile phone, the server calls both of the mobile phone and the specific calling destination and connects them. This will enable to prevent leakage of the telephone directory or client information registered in an outgoing/incoming calling history by securely controlling an access to the telephone directory, even if the mobile phone is lost, and in addition, because the server calls both of the mobile phone and the specific calling destination, a trouble of dividing a telephone rate into an individual and a corporate may reduced, even if the mobile phone belongs to the individual.  
         [0004]     Moreover, for example, in US 2002/0018547, there is provided a disclosure of a mechanism in which, on receiving an instruction of a change notice of a phone number, changer telephone directory information searching means acquires telephone directory information of a changer from backup data, registrant information extracting means extracts information of a registrant registered in the telephone directory, registrant telephone directory information searching means acquires registrant&#39;s telephone directory information from the backup data, phone number change target extracting means extracts the registrant of the telephone directory information in which the changer is registered, phone number changing means rewrites the changer&#39;s phone number existed in the telephone directory information of the registrant, and change notifying means transmits a mail of a change notice of a phone number to the registrant. However, the present publication relates to a telephone directory information change apparatus, which enables to mutually carry out an operation accompanying the change of the phone number by using the backup data of the data center, which backs up the telephone directory information of the mobile phone. Therefore, it cannot deal with the aforementioned problem.  
         [0005]     In the aforementioned related arts, countermeasures against the information leakage are insufficient, and some of them are insufficient in incidental services. Especially, because telephone directory data should be transferred to a telephone company side, there is uncertainty in management on the telephone company side. Moreover, if such a mechanism that a target phone number is simply notified to the mobile phone on receiving a call is adopted, this results in the information leakage.  
       SUMMARY OF THE INVENTION  
       [0006]     Therefore, an object of the present invention is to provide a technology for preventing information from being leaked from a mobile phone.  
         [0007]     Furthermore, another object of the present invention is to provide a telephone communication technology, which enables improvement of usability.  
         [0008]     An information processing method according to a first aspect of the present invention includes: receiving a request for data to select a calling destination from a first mobile phone capable of executing voice communication and data communication; identifying calling destination candidates registered in a data storage in association with a user of the first mobile phone by identification information other than telephone numbers of the calling destination candidates; and transmitting data to specify and select anyone of the identified calling destination candidates by the identification information other than the telephone numbers of the calling destination candidates, to the first mobile phone.  
         [0009]     Thus, because client data managed on a server side is also transmitted as the data, which can be specified and selected by the identification information other than the telephone number, the outflow of the telephone numbers can be prevented.  
         [0010]     Moreover, the information processing method according to the first aspect of the present invention may further include: receiving, from the first mobile phone, a calling request including the identification information of the specified calling destination and a recording request via the data communication; securing a first port to carry out the voice communication with the first mobile phone, a second port to carry out the voice communication with a second phone relating to the specified calling destination, and a third port for recording; establishing a link for the voice communication with the first mobile phone to carry out the voice communication via the first port; establishing a link for the voice communication with the second phone to carry out the voice communication via the second port; relaying voice data received from the first mobile phone to the second phone via the first port, and relaying the voice data received from the second phone to the first mobile phone via the second port; and recording the voice data transmitted via the first and second ports by use of the third port. Even in such a call between two parties, it becomes possible to record a call by securing three ports.  
         [0011]     Furthermore, an information processing method according to a second aspect of the present invention is an information processing method executed by a computer, to which a specific telephone number is assigned, and includes: receiving from a first phone a calling to a direct inward dial number; establishing a link of voice communication with the first phone; identifying a transfer destination telephone number corresponding to the direct inward dial number by using a user information table; carrying out a calling from the specific telephone number to the transfer destination telephone number; receiving acknowledgment of receipt from the second phone relating to the transfer destination telephone number; establishing a link for the voice communication with the second phone in response to receipt of the acknowledgment of receipt; and transmitting a guidance including information on a calling source as voice data to the second phone. Thus, the information on the calling source is notified to the second phone on a calling destination side, as the voice data, not as a calling source number notice, web page data or the like. Therefore, it is possible to lower a possibility of client information leakage of the calling source.  
         [0012]     Moreover, in the second aspect of the present invention, the guidance may include a message requesting a predetermined dial tone multi frequency (DTMF) signal to be returned when the voice communication will be carried out with the first phone. Moreover, the information processing method according to the second aspect of the present invention may further include: receiving the predetermined DTMF signal from the second phone; and relaying the voice data received from the first phone to the second phone, and relaying the voice data received from the second phone to the first phone in response to receipt of the predetermined DTMF signal. Because this enables a user who uses the second phone on the calling destination side to make a telephone call with the client of the calling source after making preparations, usability can be improved.  
         [0013]     Furthermore, in the second aspect of the present invention, the information processing method according to the second aspect of the present invention may further include: detecting that the predetermined DTMF signal is not received within a predetermined time after execution of the transmitting the guidance; transmitting a guidance indicating inaccessibility of the voice data to the first phone after the detecting; and disconnecting the link for the voice communication with the first phone. As stated, even if the second phone on the calling destination cannot receive the calling, and the calling is switched to, for example, an answering machine, an appropriate voice guidance can be transmitted to the first phone of the calling source.  
         [0014]     It is possible to create a program for causing a computer to execute the information processing method according to this invention, and this program is stored in a storage medium or a storage device such as a flexible disk, a CD-ROM, an optical magnetic disk, a semiconductor memory, and a hard disk. Further, the program may be distributed as a digital signal through a network. Incidentally, intermediate processing results are temporarily stored in a storage device such as a main memory.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0015]      FIG. 1  is a diagram showing a system outline in an embodiment of the present invention;  
         [0016]      FIG. 2  is a diagram showing one example of a session management table;  
         [0017]      FIG. 3  is a diagram showing one example of a telephone directory data table;  
         [0018]      FIG. 4  is a diagram showing one example of a history management data table;  
         [0019]      FIG. 5  is a diagram showing one example of a user information table;  
         [0020]      FIG. 6  is a flowchart showing a login processing;  
         [0021]      FIG. 7  is a diagram showing one example of a login screen;  
         [0022]      FIG. 8  is a diagram showing one example of a top menu screen;  
         [0023]      FIG. 9  is a flowchart showing a processing when registering a telephone number in a telephone directory;  
         [0024]      FIG. 10  is a diagram showing one example of a telephone directory registration screen;  
         [0025]      FIG. 11  is a diagram showing one example of a registration completion screen;  
         [0026]      FIG. 12  is a diagram showing a first part of a processing flow in a case where a calling is carried out from a registered mobile phone;  
         [0027]      FIG. 13  is a diagram showing one example of a telephone directory list screen;  
         [0028]      FIG. 14  is a diagram showing a second part of the processing flow in the case where the calling is carried out from the registered mobile phone;  
         [0029]      FIG. 15  is a diagram showing one example of a transmission completion screen;  
         [0030]      FIG. 16  is a diagram showing a third part of the processing flow in the case where the calling is carried out from the registered mobile phone;  
         [0031]      FIG. 17  is a diagram showing a fourth part of the processing flow in the case where the calling is carried out from the registered mobile phone;  
         [0032]      FIG. 18  is a diagram showing a fifth part of the processing flow in the case where the calling is carried out from the registered mobile phone  
         [0033]      FIG. 19  is a diagram showing a sixth part of the processing flow in the case where the calling is carried out from the registered mobile phone;  
         [0034]      FIG. 20  is a diagram showing a first part of a processing flow in a first example in a case where the calling is carried out from the registered mobile phone but is failed;  
         [0035]      FIG. 21  is a diagram showing a second part of the processing flow in the first example in the case where the call is carried out from the registered mobile phone but is failed;  
         [0036]      FIG. 22  is a diagram showing a processing flow in a second example in a case where the calling is carried out from the registered mobile phone but is failed;  
         [0037]      FIG. 23  is a diagram showing a first part of a processing flow in a case where the registered mobile phone responds to a calling at receiving the calling from a general phone;  
         [0038]      FIG. 24  is a diagram showing a second part of the processing flow in the case where the registered mobile phone responds to a calling at receiving the call from the general phone;  
         [0039]      FIG. 25  is a diagram showing a first part of a processing flow in a case where the registered mobile phone cannot respond to a calling at receiving the call from the general phone;  
         [0040]      FIG. 26  is a diagram showing a second part of the processing flow in the case where the registered mobile phone cannot respond to the calling at receiving the call from the general phone;  
         [0041]      FIG. 27  is a flowchart of a calling processing from an outgoing/incoming call history;  
         [0042]      FIG. 28  is a diagram showing one example of an outgoing/incoming call history screen;  
         [0043]      FIG. 29  is a flowchart showing a processing for logout; and  
         [0044]      FIG. 30  is a functional diagram of a computer. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0045]     There will be provided a description of a system outline in one embodiment of the present invention with reference to  FIG. 1 . A network  1  is, for example, a mobile phone network, and voice and data communications are carried out. The network  1  is connected to a network  2  such as a public circuit network, and a network  4  such as the Internet. The network  1  is connected to a plurality of mobile phones ( FIG. 1  only shows mobile phones A and B), which carry out wireless communication with anyone of plural base stations connected to the network  1 . The mobile phone of the present embodiment is a wireless communication device having at least a web browser function and a voice communication function. In addition, a special client application to carry out a processing according to the present embodiment may be executed in the mobile phone. The network  2  is connected to plural phones ( FIG. 1  only shows a phone C) having a voice communication function.  
         [0046]     The network  4  is connected to a session initiation protocol (SIP)-SIP-gateway (GW)  3  and a mobile connection server  7  installed in the present embodiment. The SIP-SIP-GW  3  is connected to a media management server  5  and an SIP server  9  via a network  8 . The mobile connection server  7  is also connected to the network  8 . Voice data is exchanged between the networks  8  and  4 , mainly via the SIP-SIP-GW  3 . The normal data is usually processed in the mobile connection server  7 , and necessary data is outputted to the media management server  5  or the like.  
         [0047]     The media management server  5  has a teleceonference function, a voice data relay function, a voice recording function and the like, and manages a recording data storage  51  and a user information table  52 . The SIP server  9  is a server, which carries out a communication control in accordance with the SIP. The mobile connection server  7  has a user session manager  71 , a telephone directory manager  72 , a calling request processor  73 , and a history manager  74 , and manages a session management table  75 , a telephone directory data table  76 , and a history management data storage  77 .  
         [0048]     In the aforementioned example, although there is provided an indication of a configuration example in which the network  4  is bridged to the network  8  via the SIP-SIP-GW  3  and the mobile connection server  7 , it is possible to adopt a network configuration in which all the servers are connected to the network  4  and the network  8  is not used.  
         [0049]      FIG. 2  shows a constitution example of the session management table  75 . In the example of  FIG. 2 , a user ID, a password, a telephone number of the mobile phone, and a session ID are associated. The user ID, the password, and the telephone number of the mobile phone are registered beforehand. The session ID is assigned every login from the mobile phone, and registered in the session management table  75 .  
         [0050]      FIG. 3  shows a constitution example of the telephone directory data table  76 . In the example of  FIG. 3 , a name, a user ID, a telephone number, and a telephone number of a registrant who has registered the name and the telephone number are associated. The name and the telephone number are registered in accordance with an instruction from the user. The user ID is uniquely generated and registered, when the registration instruction is received. The registrant&#39;s telephone number is extracted and registered, when the registration instruction is received.  
         [0051]      FIG. 4  shows a constitution example of a history management data table stored in the history management data storage  77 . In the example of  FIG. 4 , a calling date and time, a caller&#39;s telephone number, and a receiver&#39;s telephone number are associated. Incidentally, detailed history data is registered in the history management data storage  77 , in addition to the history management data table. The detailed history data includes a caller&#39;s telephone number, a receiver&#39;s telephone number, presence or absence of recording, a calling receipt date and time, a calling start date and time, a calling end date and time, a calling time, success/failure of a call and the like.  
         [0052]      FIG. 5  shows a constitution example of the user information table  52 . In the example of  FIG. 5 , a direct inward dial (DID) number and a telephone number of the mobile phone are associated. In the present embodiment, the DID is assigned to each employee, and an incoming call is transferred to the mobile phone used by the employee. Incidentally, the telephone number of the phone other than the mobile phone may be registered.  
         [0053]     The recording data storage  51  stores a recording data file generated by the recording function of the media management server  5 . For example, the file is managed by a file name such as (date and time)—(telephone number of the mobile phone).  
         [0054]     Next, there will be provided a description of a processing of the system shown in  FIG. 1  with reference to FIGS.  6  to  29 . First, a login processing will be described with reference to FIGS.  6  to  8 . First, the user of the mobile phone A instructs a client application (web browser (hereinafter referred to simply as the browser) in some case, and a special client application in the other case, and the client application will be described as the browser hereinafter) of the mobile phone A to transmit a login request to the mobile connection server  7  (step S 1 ). The user session manager  71  of the mobile connection server  7  receives the login request from the mobile phone A (step S 3 ), and transmits login page data to the mobile phone A (step S 5 ). The browser of the mobile phone A receives the login page data from the mobile connection server  7 , and displays the data on a display device (step S 7 ). For example, a screen shown in  FIG. 7  is displayed. In a screen example of  FIG. 7 , input columns of the user ID and the password, and a send button are provided.  
         [0055]     The user of the mobile phone A inputs the user&#39;s user ID and password, and clicks the send button. In this case, the browser of the mobile phone A accepts the inputs of the user ID and the password from the user, and transmits the user ID and password to the mobile connection server  7  (step S 9 ). The user session manager  71  receives the user ID and the password from the mobile phone A (step S 11 ), and searches the session management table  75  by using the received user ID, and reads out the password registered in association with the received user ID, and compares the received password with the read password to carry out a user authentication processing (step S 13 ). When this user authentication fails, for example, the authentication failure is notified to the mobile phone A.  
         [0056]     On the other hand, when the user authentication is successful, the user session manager  71  generates a session ID, registers the session ID in a pertinent record of the session management table  75  (step S 15 ), and transmits top menu page data and the session ID to the mobile phone A (step S 17 ).  
         [0057]     The browser of the mobile phone A receives the top menu page data and the session ID from the mobile connection server  7 , stores them into a storage device such as a main memory, and displays a top menu screen on the display device (step S 19 ). For example, a screen shown in  FIG. 8  is displayed. In the screen example of  FIG. 8 , a “register telephone directory” button, a “call from telephone directory” button, a “call from outgoing call history” button, a “call from incoming call history” button, and a “logout” button are provided.  
         [0058]     Hereinafter, a processing when this top menu screen is displayed, and any of the buttons is clicked will be described.  
         [0059]     Incidentally, the session ID is generated in this manner, and is used as identification information to identify the mobile phone A between the login and logout.  
         [0060]     First, there will be provided a description of a processing in a case where the “register telephone directory” button is clicked with reference to FIGS.  9  to  11 . When the user of the mobile phone A clicks the “register telephone directory” button on the top menu screen, the browser of the mobile phone A accepts the selection input of the telephone directory registration (step S 21 ), and transmits a registration screen display request to the mobile connection server  7  (step S 23 ). The telephone directory manager  72  of the mobile connection server  7  receives the registration screen display request from the mobile phone A (step S 25 ), and transmits telephone directory registration page data to the mobile phone (step S 27 ).  
         [0061]     The browser of the mobile phone A receives the telephone directory registration page data from the mobile connection server  7  and displays the data on the display device (step S 29 ). For example, a screen as shown in  FIG. 10  is displayed. In the display example of  FIG. 10 , input columns of a registered client name and telephone number and a “register” button are provided.  
         [0062]     The user of the mobile phone A inputs the name and the telephone number into the input columns, and clicks the “register” button. In this case, the browser of the mobile phone A accepts the inputs of the name and the telephone number (step S 31 ), and transmits a registration request including the input name and telephone number and the held session ID to the mobile connection server  7  (step S 33 ).  
         [0063]     The telephone directory manager  72  of the mobile connection server  7  receives the registration request including the name, the telephone number, and the session ID from the mobile phone A (step S 35 ), and stores the request in a storage device such as a main memory. Then, the telephone directory manager  72  generates a telephone number search request including the session ID and outputs the telephone number search request to the user session manager  71  (step S 37 ).  
         [0064]     The user session manager  71  receives the telephone number search request including the session ID from the telephone directory manager  72  (step S 39 ), searches the session management table  75  by the session ID, reads out the telephone number registered in association with the session ID from the session management table  75 , and outputs the telephone number to the telephone directory manager  72  (step S 41 ).  
         [0065]     The telephone directory manager  72  receives the telephone number corresponding to the session ID from the user session manager  71 , and stores the telephone number in a storage device such as the main memory (step S 43 ). Then, the telephone directory manager  72  generates the user ID of a client relating to the registration request (step S 45 ), and stores a record including the received name, the generated user ID, the received client telephone number, and the registrant telephone number (telephone number received from the user session manager  71 ) into the telephone directory data table  76  (step S 47 ). Then, it transmits registration completion notice page data to the mobile phone A (step S 49 ). The browser of the mobile phone A receives the registration completion notice page data, and displays the data on the display device (step S 51 ).  
         [0066]     For example, a screen as shown in  FIG. 11  is displayed. In the screen example of  FIG. 11 , a message stating, “Registration has been completed” and a link to return to TOP screen (top menu screen:  FIG. 8 ) are provided.  
         [0067]     Thus, by providing the telephone directory on a mobile connection server  7  side instead of the mobile phone, client information can be prevented from being accumulated in the mobile phone A, and this enables to prevent leakage of the client information.  
         [0068]     Next, there will be provided a description of a processing in a case where the “call from telephone directory” button is clicked in the top menu screen with reference to FIGS.  12  to  22 . First, the user of the mobile phone A clicks the “call from telephone directory” button in the top menu screen. The browser of the mobile phone A accepts the selection input of the “call from telephone directory” from the user (step S 501 ), and transmits a telephone directory request including the held session ID to the mobile connection server  7  (step S 503 ).  
         [0069]     When receiving the telephone directory request including the session ID from the mobile phone A (step S 505 ), the telephone directory manager  72  of the mobile connection server  7  generates a telephone number search request including the session ID and outputs the request to the user session manager  71  (step S 507 ). The user session manager  71  receives the telephone number search request including the session ID from the telephone directory manager  72  (step S 509 ), searches the telephone directory data table  76  by the received session ID, reads out the telephone number registered in association with the session ID from the telephone directory data table  76 , and outputs the read telephone number to the telephone directory manager  72  (step S 511 ).  
         [0070]     The telephone directory manager  72  receives the telephone number from the user session manager  71  (step S 513 ), searches the telephone directory data table  76  by using the received telephone number as a registrant telephone number, extracts the name and user ID from the pertinent record, and generates a telephone directory list composed of the name and user ID (step S 515 ). Then, the telephone directory manager  72  generates telephone directory list page data from the telephone directory list composed of the name and user ID, and transmits the data to the mobile phone A (step S 517 ).  
         [0071]     The browser of the mobile phone A receives the telephone directory list page data from the mobile connection server  7 , and displays the data on the display device (step S 519 ). For example, a screen as shown in  FIG. 13  is displayed. In the screen example of  FIG. 13 , each name is provided with a corresponding call button without any recording and a corresponding call button with recording. The user ID itself is not displayed, and it is associated with the call button together with the corresponding recording flag (ON/OFF) in the telephone directory list page data.  
         [0072]     The user of the mobile phone A clicks the call button corresponding to the client name of the calling destination. In this case, the user clicks the call button in the column of “with recording” in a case where the recording should be carried out, and clicks the call button in the column of “without recording” in a case where the recording does not have to be carried out. Here, it is assumed that the call button of “with recording” is clicked with respect to a specific calling destination (here, phone C. However, the mobile phone B may also be selected). In this case, the browser of the mobile phone A accepts the selection input “with recording” with respect to the specific calling destination (step S 61 ). The subsequent processing will be described with reference to  FIG. 14 .  
         [0073]     The description shifts to the description of the processing of  FIG. 14 . The browser of the mobile phone A transmits, to the mobile connection server  7 , a calling request including the session ID, the user ID of a call receiver relating to the selection and a recording flag (ON in this case) (step S 63 ). The calling request processor  73  of the mobile connection server  7  receives the calling request including the session ID, the user ID of the call receiver and the recording flag (ON) from the mobile phone A, and stores the calling request into a storage device such as the main memory (step S 65 ). Furthermore, the calling request processor  73  outputs the telephone number search request on a calling side, including the received session ID to the user session manager  71  (step S 67 ). The user session manager  71  receives the telephone number searching request on the calling side, including the session ID from the calling request processor  73  (step S 69 ). Then, the user session manager  71  searches the session management table  75  by the session ID, reads out a telephone number on the calling side, and outputs the telephone number on the calling side to the calling request processor  73  (step S 71 ).  
         [0074]     The calling request processor  73  receives the telephone number on the calling side from the user session manager  71 , and stores the telephone number into a storage device such as the main memory (step S 73 ). Furthermore, the calling request processor  73  outputs a telephone number search request on a call receiver side, including the receiver&#39;s user ID (step S 75 ). The telephone directory manager  72  receives the telephone number search request on the call receiver side, including the receiver&#39;s user ID (step S 77 ). The telephone directory manager  72  searches the telephone directory data table  76  by the receiver&#39;s user ID, reads out the telephone number on the call receiver side, and outputs the telephone number to the calling request processor  73  (step S 79 ).  
         [0075]     The calling request processor  73  receives the telephone number on the call receiver side from the telephone directory manager  72 , and stores the received telephone number into a storage device such as the main memory (step S 81 ). Then, it transmits, to the media management server  5 , a calling request including the session ID, the telephone number on the calling side, which was received in the step S 73 , the telephone number on the call receiver side, which was received in the step S 81 , and the recording flag (ON) (step S 83 ). In addition, it also transmits Web page data including a calling completion notice to the mobile phone A (step S 87 ). The browser of the mobile phone A receives the web page data including the calling completion notice from the mobile connection server  7 , and displays the data on the display device (step S 89 ). For example, a screen as shown in  FIG. 15  is displayed. In the screen example of  FIG. 15 , a message stating, “Calling has been completed” and the link to return to the TOP screen (top menu screen) are provided.  
         [0076]     On the other hand, the media management server  5  receives, from the mobile connection server  7 , the calling request including the session ID, the telephone number on the calling side, the telephone number on the call receiver side, and the recording flag (ON) (step S 85 ). The subsequent processing will be described with reference to  FIG. 16 .  
         [0077]     The description shifts to that of the processing of  FIG. 16 . In response to the calling request including the recording flag (ON), the media management server  5  acquires two calling ports, one recording port, and a teleconference resource to conduct a teleconference by connecting these ports (step S 91 ). Incidentally, the recording port is unnecessary in case of the recording flag (OFF). Next, the media management server  5  transmits a calling request for a calling source, which includes the telephone number on the calling side and the telephone number assigned to the media management server  5  as caller&#39;s telephone number to the SIP server  9  (step S 93 ). The SIP server  9  receives the calling request for the calling source, which includes the telephone number on the calling side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number from the media management server  5 , and transmits a call request for the telephone number on the calling side to the SIP-SIP-GW  3  in response to the calling request (step S 95 ).  
         [0078]     The SIP-SIP-GW  3  receives the call request for the telephone number on the calling side, which includes the telephone number on the calling side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the SIP server  9 , and transfers the call request to the mobile phone A (step S 97 ). Furthermore, it returns a message indicating that the call is being made to the SIP server  9  (step S 99 ). The SIP server  9  receives the message indicating the call is being made from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 101 ). The media management server  5  receives the message indicating the call is being made (step S 103 ), and starts time measurement by a response timer (step S 105 ).  
         [0079]     The mobile phone A receives the call request from the SIP-SIP-GW  3  (step S 107 ), and outputs a ring tone. Because the call request includes the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, the mobile phone A displays the telephone number assigned to the media management server  5  as the caller&#39;s telephone number on the display device. When the user of the mobile phone A pushes a call button in response to this display, the mobile phone A accepts such a call instruction (step S 109 ), and returns a call success message to the SIP-SIP-GW  3  (step S 111 ). The SIP-SIP-GW  3  receives the call success message from the mobile phone A, and transfers the message to the SIP server  9  (step S 113 ). Furthermore, the SIP server  9  receives the call success message from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 115 ).  
         [0080]     The media management server  5  receives the call success message from the SIP server  9  (step S 117 ), and stops the time measurement by the response timer in response to the receipt of the call success message (step S 119 ). There will be provided later a description of a case that the call success message is not received within a predetermined time. It is assumed here that the call success message is received within the predetermined time. By the processing up to this step, a link of the voice communication between the media management server  5  and the mobile phone A has been established, and it enables to exchange voice data with the mobile phone A via a first calling port. The subsequent processing will be described with reference to  FIG. 17 .  
         [0081]     The description shifts to that of processing of  FIG. 17 . The media management server  5  transmits a voice guidance stating, “This is an incoming call from a telephone directory service. Please push “#” when you start” to the mobile phone A (step S 121 ). Moreover, the time measurement starts by a push button (PB) timer in response to the transmission of the voice guidance (step S 123 ). The mobile phone A receives the aforementioned voice guidance, and outputs the guidance from a speaker (step S 125 ). Here, because the user of the mobile phone A is in a state capable of responding immediately, the user pushes the button “#”. The mobile phone A accepts the push of the key “#” by the user, and transmits a dial tone multi frequency (DTMF) signal (push button (PB) signal) of “#” (step S 127 ).  
         [0082]     The media management server  5  receives the DTMF signal of “#” from the mobile phone A (step S 129 ). In this case, the time measurement by the PB timer is stopped, and it is judged whether or not the DTMF signal of “#” has been received within the predetermined time. It is assumed here that the DTMF signal of “#” is received within the predetermined time. Then, the teleconference is started with a first speaker (the user of the mobile phone A) by using the teleconference resource acquired in the step S 91  (step S 131 ). After that, the media management server  5  transmits, to the SIP server  9 , the calling request for the call receiver, which includes the telephone number on the call receiver side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number (step S 133 ). When receiving the calling request for the receiver, which includes the telephone number on the call receiver side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, the SIP server  9  transmits, to the SIP-SIP-GW  3 , a call request with respect to the telephone number on the call receiver side in response to the calling request (step S 135 ).  
         [0083]     The SIP-SIP-GW  3  receives the call request, which includes the telephone number on the call receiver side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number from the SIP server  9 , and transfers the request to the phone C (step S 137 ). Furthermore, the SIP-SIP-GW  3  returns a message including the call is being made to the SIP server  9  (step S 141 ). The SIP server  9  receives the message indicating the call is being made from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 143 ). The media management server  5  receives the message indicating the call in being made (step S 145 ), and starts the teleconference with a second speaker (a user of the phone C) by using the teleconference resource acquired in the step S 91  (step S 147 ).  
         [0084]     On the other hand, the phone C receives the call request from the SIP-SIP-GW  3  (step S 139 ), and outputs the ringing tone. Because the call request includes the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, the phone C displays the telephone number assigned to the media management server  5  as the caller&#39;s telephone number on the display device, if possible. When the user of the phone C picks up a phone receiver, or pushes a call button, the phone C accepts the call instruction (step S 149 ), and returns the call success message to the SIP-SIP-GW  3  (step S 151 ). The SIP-SIP-GW  3  receives the call success message from the phone C, and transfers the message to the SIP server  9  (step S 153 ). Furthermore, the SIP server  9  receives the call success message from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 155 ). The media management server  5  receives the call success message from the SIP server  9  (step S 157 ). By the processing up to this step, a link of the voice communication between the media management server  5  and the phone C has been established, and it enables to exchange the voice data with the phone C via the second calling port. The subsequent processing will be described with reference to  FIG. 18 .  
         [0085]     The description shifts to that of processing of  FIG. 18 . The media management server  5  generates a recording file, and starts the recording of a voice conversation (step S 159 ). Then, the voice data from the mobile phone A and the phone C are relayed to another phone based on the teleconference function (step S 161 ). The recording is simultaneously carried out. The mobile phone A receives a voice input from a microphone, transmits the voice data of the input voice to the media management server  5 , receives the voice data from the media management server  5 , and outputs the data from the speaker (step S 163 ). The phone C similarly accepts the voice input from the microphone, transmits the voice data of the input voice to the media management server  5 , receives the voice data from the media management server  5 , and outputs the data from the speaker (step S 165 ). The voice communication is carried out between the mobile phone A and the phone C in this manner.  
         [0086]     Next, a processing in disconnection will be described. Here, there will be provided a description of an example in which an instruction for the disconnection is issued from the user of the phone C. However, this also applies to the instruction from the user of the mobile phone A. First, when the user of the phone C hangs up or pushes a disconnection button, the phone C accepts the instruction for the disconnection from the user, and transmits the disconnection instruction to the SIP-SIP-GW  3  (step S 167 ). The phone C disconnects the link with the media management server  5 . When receiving the disconnection instruction from the phone C, the SIP-SIP-GW  3  transfers the disconnection instruction to the SIP server  9  (step S 169 ). Furthermore, the SIP server  9  receives the disconnection instruction from the SIP-SIP-GW  3 , and transfers the disconnection instruction to the media management server  5  (step S 171 ). The media management server  5  receives the disconnection instruction from the SIP server  9  (step S 173 ), and releases the ports and teleconference resource for the teleconference, which are acquired in the step S 91  (step S 175 ). Furthermore, the media management server  5  transmits, to the SIP server  9 , a disconnection notice to the mobile phone A (step S 177 ). The SIP server  9  receives the disconnection notice from the media management server  5 , and transfers the disconnection notice to the SIP-SIP-GW  3  (step S 179 ). Furthermore, the SIP-SIP-GW  3  receives the disconnection notice from the SIP server  9 , and transfers the disconnection notice to the mobile phone A (step S 181 ). The mobile phone A receives the disconnection notice from the SIP-SIP-GW  3 , and disconnects the link with the media management server  5 . The subsequent processing will be described with reference to  FIG. 19 .  
         [0087]     The description shifts to that of the processing of  FIG. 19 . The media management server  5  terminates the recording, and stores the recording file into the recording data storage  51  (step S 183 ). The recording file name is constituted as, for example, (date and time)—(mobile phone number). If necessary, the user of the mobile phone A can reproduce later the designated recording file stored in the recording data storage  51  by the media management server  5 .  
         [0088]     Moreover, the media management server  5  generates outgoing call history (calling source&#39;s telephone number, call receiver&#39;s telephone number, presence or absence of recording (present here), calling date and time, call start date and time, call end date and time, call time, and calling success code), and transmits a registration request of the outgoing call history to the history manager  74  of the mobile connection server  7  (step S 185 ). The history manager  74  of the mobile connection server  7  receives the registration request of the outgoing call history from the media management server  5 , stores the outgoing call history data into the history management data storage  77 , and updates a history management data table by using the calling date and time, calling source&#39;s telephone number, and call receiver&#39;s telephone number (step S 187 ).  
         [0089]     Although the processing in the normal mode has been described above, because some of the messages according to SIP are not directly related to the present embodiment, such messages are omitted from the description. This also applies to the following description.  
         [0090]     Next, there will be provided a description of a processing in a case where a calling request is issued from the mobile phone A, but the call conversation becomes impossible immediately after the calling request is issued because of a certain reason, with reference to FIGS.  20  to  22 . Incidentally, because the processing before the step S 91  is the same, the description is omitted. First, the media management server  5  acquires two calling ports, one recording port, and a teleconference resource to carry out the teleconference by connecting these ports in response to the calling request including a recording flag (ON) (step S 191 ). Next, the server transmits a calling request for a calling source, which includes the telephone number on the calling source side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, to the SIP server  9 , (step S 193 ). The SIP server  9  receives the calling request for the calling source, which includes the telephone number on the calling source side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the media management server  5 , and transmits the call request with respect to the telephone number on the calling source side to the SIP-SIP-GW  3  in response to the calling request (step S 195 ).  
         [0091]     The SIP-SIP-GW  3  receives the call request for the telephone number on the calling source side, which includes the telephone number on the calling source side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the SIP server  9 , and transfers the call request to the mobile phone A (step S 197 ). Furthermore, the SIP-SIP-GW  3  returns a message indicating the calling is being made to the SIP server  9  (step S 201 ). The SIP server  9  receives the message indicating the calling is being made from the SIP-SIP-GW  3 , and transfers the call message to the media management server  5  (step S 203 ). The media management server  5  receives the message indicating the calling is being made (step S 205 ), and starts the time measurement by the response timer (step S 207 ).  
         [0092]     The mobile phone A receives the call request from the SIP-SIP-GW  3  (step S 199 ), and outputs the ring tone. Because the call request includes the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, the mobile phone A displays the telephone number assigned to the media management server  5  as the caller&#39;s telephone number on the display device. However, as described above, the user of the mobile phone A cannot pushes the call key, and the call request is transferred to a telephone answering service center via a known mechanism in the network  1  after elapse of a predetermined time.  
         [0093]     When receiving the call request, as usual, the telephone answering service center carries out a receiving processing (step S 209 ), and returns a call success message to the SIP-SIP-GW  3  (step S 211 ). The SIP-SIP-GW  3  receives the call success message from the telephone answering service center, and transfers the call success message to the SIP server  9  (step S 213 ). Furthermore, the SIP server  9  receives the call success message from the SIP-SIP-GW  3 , and transfers the call success message to the media management server  5  (step S 214 ).  
         [0094]     The media management server  5  receives the call success message from the SIP server  9  (step S 215 ), and stops the time measurement by the response timer in response to receiving the call success message (step S 217 ). It is also assumed here that the call success message is received within a predetermined time. By the processing up to this step, the link of the voice communication between the media management server  5  and the telephone answering service center has been established, and the exchange of the voice data with the telephone answering service center can be carried out through the first calling port. Incidentally, the telephone answering service center starts transmitting a predetermined voice message to the media management server  5  in one way. The subsequent processing will be described with reference to  FIG. 21 .  
         [0095]     The description shifts to that of the processing of  FIG. 21 . The media management server  5  transmits, to the telephone answering service center, the voice guidance stating, “This is an incoming call from the telephone directory service. Please input “#” when you start” (step S 219 ). The time measurement starts with the PB timer in response to the transmission of the voice guidance (step S 221 ). The telephone answering service center receives the aforementioned voice guidance (step S 223 ). However, because the telephone answering service center does not respond to the voice guidance, the DTMF signal of “#” is not sent.  
         [0096]     That is, the time measurement by the PB timer results in time-out, and this time-out is detected (step S 225 ). Then, the media management server  5  releases three ports and the teleconference resource acquired in the step S 191  (step S 227 ). Furthermore, it transmits a disconnection notice for the telephone answering service center to the SIP server  9  (step S 229 ). The SIP server  9  receives the disconnection notice from the media management server  5 , and transfers the disconnection notice to the SIP-SIP-GW  3  (step S 231 ). Furthermore, the SIP-SIP-GW  3  receives the disconnection notice from the SIP server  9 , and transfers the disconnection notice to the telephone answering service center (step S 233 ). The telephone answering service center receives the disconnection notice from the SIP-SIP-GW  3 , and disconnects the link with the media management server  5  (step S 235 ).  
         [0097]     Furthermore, the media management server  5  generates a calling history (calling source&#39;s telephone number, call receiver&#39;s telephone number, presence or absence of the recording (present), calling date and time, call start date and time (none), call end date and time (none) call time (none) and calling failure code), and transmits a registration request of the calling history to the history manager  74  of the mobile connection server  7  (step S 237 ). The history manager  74  of the mobile connection server  7  receives the registration request of the calling history from the media management server  5 , and stores the calling history into the history management data storage  77  (step S 239 ). Incidentally, the history management data table is also updated.  
         [0098]     Such a processing can appropriately terminate the communication, even if a situation in which the link is connected to the telephone answering service center occurs.  
         [0099]     Next, there will be described processing in a case where the calling request is issued from the mobile phone A, but the call conversation cannot be made immediately after the calling request is issued for a certain reason, and the calling request is not transferred to the answering phone center, with reference to  FIG. 22 . Incidentally, because the processing before the step S 91  is the same, the description is omitted.  
         [0100]     First, the media management server  5  acquires two calling ports, one recording port, and the teleconference resource to carry out the teleconference by connecting these ports in the media management server  5  in response to the calling request including the recording flag (ON) (step S 241 ). Next, the media management server  5  transmits the calling request for the calling source, which includes the telephone number on the calling source side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, to the SIP server  9 , (step S 243 ). The SIP server  9  receives the calling request for the calling source, which includes the telephone number on the calling source and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the media management server  5 , and transmits the call request for the telephone number on the calling source side to the SIP-SIP-GW  3  in response to the calling request (step S 245 ).  
         [0101]     The SIP-SIP-GW  3  receives the call request for the telephone number on the calling source side, which includes the telephone number on the calling source side and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the SIP server  9 , and transfers the call request to the mobile phone A (step S 247 ). Furthermore, it returns a message indicating the calling is being made to the SIP server  9  (step S 251 ). The SIP server  9  receives the message indicating the calling is being made from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 253 ). The media management server  5  receives the message indicating the calling is being made (step S 255 ), and starts the time measurement by the response timer (step S 257 ).  
         [0102]     The mobile phone A receives the call request from the SIP-SIP-GW  3  (step S 249 ), and outputs the ring tone. Because the call request includes the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, the mobile phone A displays the telephone number assigned to the media management server  5  as the caller&#39;s telephone number on the display device. However, as described above, the user of the mobile phone A cannot press the call key. Therefore, the call success message is not indefinitely transmitted to the media management server  5 .  
         [0103]     Thus, the time measurement by the response timer results in time-out, and this time-out is detected (step S 259 ). Then, the media management server  5  releases three ports and the teleconference resource acquired in the step S 241  (step S 261 ).  
         [0104]     Furthermore, the media management server  5  generates the outgoing calling history (calling source&#39;s telephone number, call receiver telephone number, presence or absence of the recording (present), call date and time, call start date and time (none), call end date and time (none), call time (none), and calling failure code) and transmits a registration request of the outgoing calling history to the history manager  74  of the mobile connection server  7  (step S 263 ). The history manager  74  of the mobile connection server  7  receives the registration request of the outgoing calling history from the media management server  5 , stores the outgoing calling history into the history management data storage  77  (step S 265 ), and also updates the history management data table.  
         [0105]     Such a processing can appropriately terminate the communication even if a situation in which the user of the mobile phone A cannot respond and the telephone answering service center is not connected occurs.  
         [0106]     Next, there will be provided a description of a processing in a case where there is an incoming call from the phone (e.g., phone C) whose telephone number is not registered in the user information table  52 , with reference to FIGS.  23  to  26 .  
         [0107]     First, the user of the phone C operates the phone C, and instructs the calling to a specific number (direct inward dial number of the user of the mobile phone B here). The phone C accepts a calling instruction to the specific number from the user (step S 271 ), and carries out a calling to the specific number (step S 273 ). Incidentally, a caller&#39;s telephone number is notified, and the telephone number of the phone C is notified to the media management server  5 . For example, the calling from telephone C is transferred based on the specific number by an exchanger or the like in the network  2 .  
         [0108]     The SIP-SIP-GW  3  receives, from the phone C, the calling to the specific number, including the telephone number of the phone C as the caller&#39;s telephone number notice, and transmits, to the SIP server  9 , a receipt notice for the specific number (step S 275 ). The SIP server  9  receives, from the SIP-SIP-GW  3 , the receipt notice for the specific number, and transfers the receipt notice to the media management server  5  (step S 277 ). The media management server  5  receives, from the SIP server  9 , the receipt notice for the specific number (step S 279 ), and acquires two incoming/outgoing ports, one recording port, and the teleconference resource to carry out teleconference by connecting these ports in the media management server  5  in response to receiving the receipt notice (step S 281 ). The teleconference starts with the first speaker (user of the phone C) by using the teleconference resource.  
         [0109]     Then, the media management server  5  transmits the call success message to the SIP server  9  (step S 283 ). The SIP server  9  receives the call success message from the media management server  5 , and transfers the message to the SIP-SIP-GW  3  (step S 285 ). The SIP-SIP-GW  3  receives the call success message from the SIP server  9 , and transfers the message to the phone C (step S 287 ). Furthermore, the phone C receives the call success message from the SIP-SIP-GW  3  (step S 289 ). By the processing up to this step, the link of the voice communication has been established between the media management server  5  and the phone C through a first link.  
         [0110]     The media management server  5  searches the user information table by the specific number, separately from the step S 283 , and extracts the telephone number (telephone number of mobile phone B) of the user corresponding to the specific number (step S 291 ). Then, it transmits a predetermined voice guidance to the phone C (step S 293 ). The phone C receives the predetermined voice guidance from the media management server  5 , and outputs the guidance from the speaker (step S 295 ). The voice guidance is, for example, a message stating, “The person in charge of you is called just now, so please wait for a while”. The subsequent processing will be described with reference to  FIG. 24 .  
         [0111]     The description shifts to that of the processing of  FIG. 24 . The media management server  5  transmits the calling request for the call receiver, which includes the telephone number of the call receiver (telephone number of the mobile phone B) and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, to the SIP server  9 , (step S 297 ). The SIP server  9  receives the calling request for the call receiver, which includes the telephone number of the call receiver and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the media management server  5 , and transmits a call request for the telephone number of the call receiver to the SIP-SIP-GW  3  in response to the calling request (step S 299 ).  
         [0112]     The SIP-SIP-GW  3  receives the call request for the telephone number of the call receiver, which includes the telephone number of the call receiver and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the SIP server  9 , and transfers the call request to the mobile phone B (step S 301 ). Furthermore, it replies a message indicating the calling is being made to the SIP server  9  (step S 303 ). The SIP server  9  receives the message indicating the calling is being made from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 305 ). The media management server  5  receives the message indicating the calling is being made (step S 307 ), and starts the time measurement by the response timer (step S 309 ).  
         [0113]     The mobile phone B receives the call request from the SIP-SIP-GW  3  (step S 311 ), and outputs the ring tone. Because the call request includes the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, the mobile phone B displays the telephone number assigned to the media management server  5  as the caller&#39;s telephone number on the display device. When the user of the mobile phone B pushes the call key in response to this display, the mobile phone B accepts the call receiving input (step S 313 ), and returns the call success message to the SIP-SIP-GW  3  (step S 315 ). The SIP-SIP-GW  3  receives the call success message from the mobile phone B, and transfers the message to the SIP server  9  (step S 316 ). Furthermore, the SIP server  9  receives the call success message received from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 317 ).  
         [0114]     The media management server  5  receives the call success message from the SIP server  9  (step S 319 ), and stops the time measurement by the response timer in response to receipt of the call success message (step S 321 ). There will be provided later a description in a case where the call success message is not received within a predetermined time. It is assumed here that the call success message is received within the predetermined time. By the processing up to this step, the link of the voice communication between the media management server  5  and the mobile phone B has been established, and the exchange of the voice data with the mobile phone B is possible through the second calling port.  
         [0115]     Moreover, the media management server  5  transmits, to the mobile phone B, the voice guidance stating, “This is an incoming call from XX-XXXX-XXX (telephone number of the phone C). Please input “1” when you start the call, input “2” when you record the call, and input “#” when you reject the call” (step S 323 ). The time measurement starts with the PB timer in response to the transmission of the voice guidance. The mobile phone B receives the aforementioned voice guidance, and outputs the guidance from the speaker (step S 325 ). Here, the user of the mobile phone B judges that he or she is in a state of being able to make an immediate response, and that the recording is necessary, and then presses a button“2”. The mobile phone B accepts the depression of the key “2” by the user and sends out the DTMF signal of “2” (step S 327 ). The media management server  5  receives the DTMF signal of “2” from the mobile phone B (step S 329 ). Then, the media management server  5  stops the time measurement by the PB timer, and judges whether or not the DTMF signal of “2” is received within the predetermined time. It is assumed here that the DTMF signal of “2” is received within the predetermined time. The teleconference with the second speaker (user of the mobile phone B) starts. There will be provided a description later in a case where the DTMF signal is not received within the predetermined time.  
         [0116]     In this manner, the user of the mobile phone B does not have to talk with the user of the phone C immediately after the receipt of the call, and can make a conversation after the user becomes ready and presses the button designated by the voice guidance. Incidentally, because an original caller&#39;s (phone C) telephone number is notified by the voice guidance, it is possible to know from whom the phone received the call. In addition, according to such a method, there is no case in which the telephone number of the phone C, which is an original caller, is notified without notifying the telephone number assigned to the media management server  5  as the caller&#39;s telephone number. Therefore, any false telephone number of the caller is not given, and any legal problem does not occur. Furthermore, because the original caller is notified by the voice guidance, the caller&#39;s telephone number (phone C) does not remain in the mobile phone B, and the leakage of the information is prevented.  
         [0117]     Because the subsequent processing is similar to that after the step S 159  of  FIG. 18 , the description is omitted. Incidentally, when the key “1” is depressed on the mobile phone B, there is not any recording, and therefore, the processing of the recording by using the recording port is skipped. When the key “#” is depressed, the processing after step S 377  ( FIG. 26 ), which is described later, is carried out.  
         [0118]     Moreover, although the telephone number of the phone C as the original caller is notified by the voice guidance, a client database may be searched in which a client name is registered in association with the telephone number of the client, as preprocessing, and the client name may be notified to the user of the mobile phone B instead of the telephone number.  
         [0119]     Next, there will be provided a description of a processing in a case where the mobile phone B cannot respond, with reference to  FIGS. 25 and 26 . Because the processing up to  FIG. 23  is the same, the description is omitted.  
         [0120]     First, the media management server  5  transmits, to the SIP server  9 , the calling request for the call receiver, which includes the telephone number of the call receiver and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number (step S 331 ). The SIP server  9  receives the calling request for the call receiver, which includes the telephone number of the call receiver and the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, from the media management server  5 , and transmits a call request for the telephone number of the call receiver to the SIP-SIP-GW  3  in response to the calling request (step S 333 ).  
         [0121]     The SIP-SIP-GW  3  receives the call request for the telephone number of the call receiver, which includes the telephone number of the call receiver and the telephone number assigned to the media management server  5  as the caller&#39;s telephone numbers, from the SIP server  9 , and transfers the call request to the mobile phone B (step S 335 ). Furthermore, it replies the message indicating the calling is being made to the SIP server  9  (step S 337 ). The SIP server  9  receives the message indicating the calling is being made from the SIP-SIP-GW  3 , and transfers the message to the media management server  5  (step S 339 ). The media management server  5  receives the message indicating the calling is being made (step S 341 ), and starts the time measurement by the response timer (step S 343 ).  
         [0122]     The mobile phone B receives the call request from the SIP-SIP-GW  3  (step S 345 ), and outputs the ring tone. Because the call request includes the telephone number assigned to the media management server  5  as the caller&#39;s telephone number, the mobile phone B displays the telephone number assigned to the media management server  5  as the caller&#39;s telephone number on the display device. However, as described above, the user of the mobile phone B cannot pushes the call key, and the call request is transferred to the telephone answering service center through a known mechanism in the network  1  after elapse of a predetermined time.  
         [0123]     When receiving the call request, as usual, the telephone answering service center carries out the call receiving processing (step S 347 ), and returns a call success message to the SIP-SIP-GW  3  (step S 349 ). The SIP-SIP-GW  3  receives the call success message from the telephone answering service center, and transfers the call success message to the SIP server  9  (step S 351 ). Furthermore, the SIP server  9  receives the call success message from the SIP-SIP-GW  3 , and transfers the call success message to the media management server  5  (step S 353 ).  
         [0124]     The media management server  5  receives the call success message from the SIP server  9  (step S 355 ), and stops the time measurement by the response timer in response to receipt of the call success message (step S 357 ). It is also assumed here that the call success message is received within the predetermined time. By the processing up to this step, the link of the voice communication between the media management server  5  and the telephone answering service center has been established, and the exchange of the voice data with the telephone answering service center becomes possible through the second port. Incidentally, the telephone answering service center starts sending a predetermined voice message in one way. The subsequent processing will be described with reference to  FIG. 26 .  
         [0125]     The description shifts to that of the processing of  FIG. 26 . The media management server  5  transmits, to the telephone answering service center, a voice guidance stating, “This is an incoming call from XX-XXXX-XXX (telephone number of the phone C). Please input “1” when you start the call, input “2” when you record the call, and input “#” when you reject the call” (step S 359 ). The time measurement starts by the PB timer in response to the transmission of the voice guidance (step S 363 ). The answering phone center receives the aforementioned voice guidance (step S 361 ). However, because the telephone answering service center does not respond to the voice guidance, the designated DTMF signal is not sent out.  
         [0126]     That is, the time measurement by the PB time results in time-out, and this time-out is detected (step S 265 ). Then, the media management server  5  releases three ports and the teleconference resource acquired in the step S 281  (step S 367 ). Furthermore, it transmits a disconnection notice for the telephone answering service center to the SIP server  9  (step S 369 ). The SIP server  9  receives the disconnection notice from the media management server  5 , and transfers the disconnection notice to the SIP-SIP-GW  3  (step S 371 ). Furthermore, the SIP-SIP-GW  3  receives the disconnection notice from the SIP server  9 , and transfers the disconnection notice to the telephone answering service center (step S 373 ). The telephone answering service center receives the disconnection notice from the SIP-SIP-GW  3 , and disconnects the link with the media management server  5  (step S 375 ).  
         [0127]     Moreover, the media management server  5  transmits, to the phone C, a voice guidance stating, “We are very sorry, but we cannot connect” (step S 377 ). The phone C receives the aforementioned voice guidance, and outputs the guidance through the speaker (step S 379 ). Accordingly, the user of the phone C knows that the call cannot be made for a certain reason at present.  
         [0128]     Furthermore, the media management server  5  transmits the disconnection notice for the phone C to the SIP server  9  (step S 383 ). The SIP server  9  receives the disconnection notice from the media management server  5 , and transfers the disconnection notice to the SIP-SIP-GW  3  (step S 385 ). Furthermore, the SIP-SIP-GW  3  receives the disconnection notice from the SIP server  9 , and transfers the disconnection notice to the phone C (step S 387 ). The phone C receives the disconnection notice from the SIP-SIP-GW  3 , and disconnects the link with the media management server  5  (step S 389 ). In the subsequent processing, for example, the step S 237  and S 239  of  FIG. 21  are executed.  
         [0129]     By carrying out such a processing, the communication can be appropriately terminated, even if a situation in which the telephone answering service center is connected occurs.  
         [0130]     Incidentally, in a case where the call is not transferred to the telephone answering service center, but the user of the mobile phone B does not answer the call, the processing stops at the step S 345 , and the time-out of the response timer is detected. Therefore, in such a case, the processing shifts to the step S 377 .  
         [0131]     Next, there will be provided a description of a processing in a case where the “call from outgoing calling history” button or the “call from incoming calling history” button is clicked on the top menu screen, with reference to  FIG. 27 . First, the user of the mobile phone A clicks the “call from outgoing calling history” button or the “call from incoming calling history” button, and the mobile phone A accepts the selection input of “call from the outgoing calling history” or “call from incoming calling history” (step S 401 ), and transmits the outgoing or incoming calling history request including the session ID to the mobile connection server  7  (step S 403 ).  
         [0132]     The history manager  74  of the mobile connection server  7  receives the outgoing or incoming calling history request including the session ID (step S 405 ) from the mobile phone A, and outputs the telephone number search request including the received session ID to the user session manager  71  (step S 407 ). The user session manager  71  receives the telephone number search request including the session ID (step S 409 ) from the history manager  74 , and searches the session management table  75  by the session ID, reads out the corresponding telephone number, and outputs the telephone number to the history manager  74  (step S 411 ).  
         [0133]     The history manager  74  receives the telephone number (telephone number of the mobile phone A) corresponding to the session ID from the user session manager  71  (step S 413 ), and extracts a corresponding history record from the history management data storage  77  (step S 415 ). In a case where the “call from outgoing calling history” is instructed, the history record is extracted in which the telephone number corresponding to the session ID is registered in the column of the caller&#39;s telephone number in the history management data table. In a case where “call from outgoing calling history” is instructed, the history record is extracted in which the telephone number corresponding to the session ID is registered in the column of the receiver&#39;s telephone number in the history management data table.  
         [0134]     Then, the history manager  74  generates a telephone number list by using telephone numbers (telephone numbers other than the telephone number corresponding to the session ID) included in the corresponding history records, and outputs a name search request including the telephone number list to the telephone directory manager  72  (step S 417 ). The telephone directory manager  72  receives the name search request including the telephone directory list from the history manager  74  (step S 419 ), and searches the telephone directory data table  76  by the telephone numbers included in the telephone directory list to extract the corresponding names and user IDs. Then, the telephone directory manager  72  outputs a list of the names and user IDs to the history manager  74  (step S 421 ).  
         [0135]     The history manager  74  receives the list of the names and user IDs from the telephone directory manager  72 , and stores the list into a storage device such as the main memory (step S 423 ). Then, it generates outgoing or incoming calling history page data from the list of the names and user IDs and the history records extracted in the step S 415 , and transmits such page data to the mobile phone A (step S 425 ).  
         [0136]     The browser of the mobile phone A receives the outgoing or incoming calling history page data from the mobile connection server  7  and displays the data on the display device (step S 427 ). For example, a screen shown in  FIG. 28  is displayed. In the screen example of  FIG. 28 , a calling date column, a caller or receiver name column, call buttons corresponding to the history records without recording, and call buttons corresponding to the history records with recording are provided. The user ID itself is not displayed, and it is associated with the call button in the outgoing or incoming calling history page data together with the corresponding recording flag (ON/OFF).  
         [0137]     The user of the mobile phone A clicks the call button corresponding to the client name of the calling destination. At this time, the user clicks the call button in the column with recording in a case where the recording is carried out, or clicks the call button in the column without recording in a case where the recording is not carried out. It is assumed here that the call button with recording is clicked with respect to the specific calling destination (here the phone C, but it may be the mobile phone B). Then, the browser of the mobile phone A accepts the selection input of the specific calling destination with recording (step S 429 ). Because the subsequent processing is the same as that of  FIG. 14 , the description is omitted here.  
         [0138]     Because the outgoing or incoming calling history does not remain in the mobile phone in the same manner as in case of the call from the telephone directory, the leakage of the information is prevented. Furthermore, because the web page data including client data with the user IDs with which the telephone number is substituted is transmitted to the mobile phone, the security is also improved in this respect.  
         [0139]     Next, there will be provided a description of a processing in a case where “logout” is selected on the top menu screen, with reference to  FIG. 29 . First, when the user of the mobile phone A clicks a logout button, the mobile phone A accepts the selection input of the logout (step S 431 ), and transmits a session deletion request including the session ID to the user session manager  71  of the mobile connection server  7  (step S 433 ).  
         [0140]     The user session manager  71  of the mobile connection server  7  receives the session deletion request including the session ID from the mobile phone A (step S 435 ), searches the session management table  75  by the session ID, deletes the session ID from the pertinent record (step S 437 ), and transmits a session deletion notice to the mobile phone A (step S 439 ). Alternatively, login page data is transmitted.  
         [0141]     The browser of the mobile phone A receives the session deletion notice from the mobile connection server  7  (step S 441 ), and displays the login screen ( FIG. 7 ) on the display device (step S 443 ). Moreover, the browser discards the session ID, which it held. In this manner, the state of the browser returns to a state before the login.  
         [0142]     According to the aforementioned processing, it is not necessary to register the client telephone number or the like in the mobile phone. In addition, even if the mobile phone falls into the hands of anyone else by robbery or the like, information such as the client telephone number does not leak. Because the client telephone number is not notified as data other than voice data to the mobile phone, information such as the client telephone number does not remain in the mobile phone, unless intended. Furthermore, because information is transmitted from the media management server  5 , it is not necessary any more to divide a telephone rate even if the mobile phone itself belongs to an individual, and it enables to reduce an administrative work load.  
         [0143]     Furthermore, because the call is not simply transferred, usability is improved for the client and the user in that the call can be started at the time when preparations are made in incoming call from the client or the like, the recording becomes possible, and the call can be appropriately terminated even if the incoming call switches to the answering machine.  
         [0144]     Although the embodiment of the present invention has been described above, the present invention is not limited to this embodiment. That is, the functional blocks shown in  FIG. 1  do not necessarily correspond to actual program modules. Furthermore, the server configuration indicated is also an example, and it is possible to adopt a method of realizing the invention using more servers by further dividing functions in charge, and the servers maybe further integrated.  
         [0145]     In addition, the SIP-SIP-GW  3 , the media management server  5 , the mobile connection server  7 , the SIP server  9  and the like are computer devices as shown in  FIG. 30 . That is, a memory  2501  (storage device), a CPU  2503  (processor), a hard disk drive (HDD)  2505 , a display controller  2507  connected to a display device  2509 , a drive device  2513  for a removal disk  2511 , an input device  2515 , and a communication controller  2517  for connection with a network are connected through a bus  2519  as shown in  FIG. 28 . An operating system (OS) and an application program for carrying out the foregoing processing in the embodiment, are stored in the HDD  2505 , and when executed by the CPU  2503 , they are read out from the HDD  2505  to the memory  2501 . As the need arises, the CPU  2503  controls the display controller  2507 , the communication controller  2517 , and the drive device  2513 , and causes them to perform necessary operations. Besides, intermediate processing data is stored in the memory  2501 , and if necessary, it is stored in the HDD  2505 . In this embodiment of this invention, the application program to realize the aforementioned functions is stored in the removal disk  2511  and distributed, and then it is installed into the HDD  2505  from the drive device  2513 . It may be installed into the HDD  2505  via the network such as the Internet and the communication controller  2517 . In the computer as stated above, the hardware such as the CPU  2503  and the memory  2501 , the OS and the necessary application program are systematically cooperated with each other, so that various functions as described above in details are realized.  
         [0146]     Although the present invention has been described with respect to a specific preferred embodiment thereof, various change and modifications may be suggested to one skilled in the art, and it is intended that the present invention encompass such changes and modifications as fall within the scope of the appended claims.