JP2005269407A - Registration of terminal identification on server on intranet from external network through dmz - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent the information about the device on intranet from unnecessarily flowing out on the Internet. <P>SOLUTION: An information processor (120), which is a first device and connectable to an intranet (140) and a second device (110) of DMZ, establishes connection or link with the second device, and receives a registration massage (610) from the second device. The registration massage which is received is altered and transferred to a third device (150) on the intranet. On the established connection or link, a registration completion massage (618) is received from the third device (150). The received registration completion massage is altered and transferred to the second device by a transfer means (1131). <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to communication between an intranet and an external network, and more particularly to communication for registering a terminal identification for VoIP communication between an intranet having a firewall and an external network in a server on the intranet via a DMZ.

  Telephone communication between two personal computers (PCs) via a local area network (LAN) is known. In addition, VoIP (Voice over IP) communication that provides Internet telephone communication between two PCs via the Internet is also known.

JP 2003-324485, published on November 14, 2003 by Noda, et al., Terminates calls of both intranet terminals and Internet terminals in a DMZ between the intranet and the Internet, and calls both calls. It is described that VoIP communication is realized between the two terminals by associating.
JP 2003-324485 A

  In order to perform VoIP communication in accordance with SIP (Session Initiation Protocol) between an intranet terminal and an Internet terminal via a DMZ between the intranet and the Internet, the Internet terminal uses an additional header in a registration message on the intranet. Own terminal identification must be registered in advance in the SIP server. For this purpose, in accordance with the RFC 3261 of SIP, in addition to the existing VoIP communication function, an additional function for that purpose must be installed in the Internet terminal. However, in the registration completion (200 OK) message from the SIP server, information on the intranet is unnecessarily leaked outside on the Internet.

  In order to perform VoIP communication between the intranet terminal and the internet terminal via the DMZ between the intranet and the internet, the inventor previously assigned the terminal identification to the SIP server on the intranet without using an additional function. We realized that it would be advantageous to be able to register.

  One object of the present invention is to prevent information regarding devices on the intranet from being unnecessarily leaked on the Internet in messages from the intranet to the Internet.

  Another object of the present invention is to enable an Internet terminal to register its own terminal identification in advance in a SIP server on an intranet without using an additional function.

  According to one aspect of the present invention, an information processing device as a first device that can be connected to a second device in an DMZ and an intranet establishes a connection or link with the second device, and Receiving a registration message from the second device, modifying the received registration message and forwarding it to a third device on the intranet from the third device over the established connection or link; Transfer means for receiving a registration completion message, modifying the received registration completion message and transferring it to the second device.

  According to another feature of the present invention, an information processing device as a first device that can be connected to a second device on an intranet and an external network and can be arranged in a DMZ is connected to the second device. Or establish a link, receive a registration message from a third device on the external network, modify the received registration message and forward it to the second device on the intranet; First means for receiving a registration completion message from the device, modifying the received registration completion message and transferring it to the third device.

  The present invention further relates to a program and a method for realizing the above information processing apparatus.

  ADVANTAGE OF THE INVENTION According to this invention, it can prevent the information regarding the apparatus on an intranet from flowing out on the internet unnecessarily in the message from an intranet to the internet.

  Embodiments of the present invention will be described with reference to the drawings. In the drawings, similar components are given the same reference numerals.

  FIG. 1 shows a system configuration including an intranet 140 connected to a server and a terminal and an external network 40 connected to an external terminal according to an embodiment of the present invention. The intranet 140 is a local area network (LAN) in the call center 10. The external network 40 is typically the Internet and may include ISDN, PSTN, ADSL or cable television network.

  In the call center 10, a firewall (FW) 80 is connected between the DMZ 100 and the external network 40, and a firewall 85 is connected between the DMZ 100 and the intranet 140. Multimedia communication (MM.C.) as a SIP proxy server compliant with the standard SIP (Session Initiation Protocol) for extended VoIP recommended by IETF to the hub 82 on the communication line in the DMZ 100 between the firewalls 80 and 85 A server 110 and other servers 130 to 131 are connected. A multimedia communication (MM.C.) relay server 120 as a SIP proxy server compliant with SIP is connected to the intranet 140 and the firewall 85.

  In the intranet 140, a SIP server 150 as a call control device compliant with SIP, a terminal identification or IP telephone number for VoIP communication, a registration database 152 for registering a corresponding IP address, and a plurality of terminals 162 compliant with SIP ˜166 and a customer database 170 for authentication and the like are connected. Customer database 170 is referenced by servers 110 and 130-131, and by operators or agents on terminals 162-166 when talking to customers. A plurality of terminals 240 and 250 compliant with the local SIP are connected to the external network 40 via a NAT (Network Address Translation) router 210, and a single terminal 270 compliant with the SIP is connected.

  FIG. 2 illustrates another system configuration that includes an intranet 140 and an external network 40 according to another embodiment of the present invention. In this figure, in the call center 10, a single firewall 90 is connected to the DMZ 100 between the external network 40 and the intranet 140. The MM. C. A server 110 and other servers 130 to 131 are connected. The communication line between the intranet 140 and the firewall 90 is connected to the MM. C. A relay server 120 is connected.

  Firewalls 80 and 85 in FIG. 1 and firewall 90 in FIG. 2 filter connection requests received via external network 40 and intranet 140 according to their rules, and server 110 in DMZ 100 only for connection requests that conform to the rules. , 130,... Or 131 is permitted, and connection requests that do not conform to the rules are rejected. The firewalls 80, 85, and 90 further filter packets received via the external network 40 and the intranet 140 according to a predetermined filtering rule, and only packets that conform to the rule are intranet 140, the external network 40, and the server 110 and The packet that does not conform to the rule is discarded.

  FIG. 3 shows yet another system configuration including an intranet 140 connected to a server and a terminal and an external network 40 connected to an external terminal according to still another embodiment of the present invention. In this figure, the intranet 140 is MM. C. Relay server 120, MM. C. The server 110, the hub 83 on the communication line, and the firewall 80 are connected to the external network 40. MM. C. Relay server 120 and MM. C. The server 110 uses, for example, a cable 640 according to a non-IP (non-Internet protocol) based on the USB standard or the IEEE 1394 standard, or based on a wireless LAN standard such as the Bluetooth standard or the IEEE 802.11 standard. Communicate with each other using RF signals 642 according to non-IP.

  FIG. 4 illustrates yet another system configuration that includes an intranet 140 and an external network 40 according to yet another embodiment of the present invention. In this figure, in the call center 10, the intranet 140 and the external network 40 are connected via the communication path according to the non-IP as shown in FIG. C. Relay server 120 and MM. C. They are connected to each other via the server 110 and are connected to the other servers 130 to 131 in the DMZ 100 via communication lines according to IP in a normal form. In the call center 10, a firewall 80 is connected between the DMZ 100 and the external network 40, and another firewall 85 is connected between the DMZ 100 and the intranet 140.

  Other servers 130 to 131 are connected to the hub 82 on the communication line in the DMZ 100 between the firewalls 80 and 85. MM. C. A relay server 120 is connected to the intranet 140.

  MM. C. An L3 switch 81 is provided between the hub 83 to which the server 110 is connected and the hub 82 to which the other servers 130 to 131 are connected to the firewall 80. The switch 81 is an MM. C. The connection is switched between the server 110 and the other servers 130-131. The switch 81 supplies normal packets from the external terminal 240 or 270 to the other servers 130 to 131, and transmits packets from the external terminal 240 or 270 to devices other than the other servers 130 to 131 with the MM. C. Operate to supply to server 110. The switch 81 is an MM. C. Packets from the server 110 and other servers 130 to 131 to external devices on the external network 40 are sent to the external network 40.

  FIG. C. A configuration of the server 110 is shown. MM. C. The server 110 includes a processor 1110 and a storage device 1112, and is physically connected to the hub 82 or 83 via a network interface (NW I / F), and is further connected to the network interface (NW I / F) or non- MM. Via the IP interface (non-IP I / F). C. Connected to the relay server 120. The storage device 1112 handles (processes) a registration message and a registration completion message requesting registration of the terminal identification and IP address from the external terminal 240 or 270, and further handles signaling communication and multimedia communication. Stores a program for connecting a call or connection via the intranet 140 and a call or connection via the external network 40. A processing generator 112 is mounted (implemented) on the processor 1110 according to the program. The processing generator 112 includes registration communication (REG.C.) components 1131, 1132,..., And 1134 having the same configuration as the registration communication (REG.C.) unit 113, and a plurality of signaling communication components. Dynamic signaling communication (SIG.C.) unit 114 and multimedia communication (MM.C.) unit 116 that may include a corresponding plurality of multimedia communication components. A management component 118 is further mounted on the processor 1110 according to the program. SIG. C. Part 114 and MM. C. The detailed configuration and operation of the unit 116 and the like are described in the aforementioned Japanese Patent Application Laid-Open No. 2003-324485 and Japanese Patent Application No. 2003-10424, which are incorporated herein by reference.

  REG. C. The components 1131 to 1134 are connected from the external network terminals 240 to 270 to the SIP server 150 based on standard SIP on TCP (Transmission Control Protocol) or UDP (User Datagram Protocol) created by IETF (Internet Engineering Task Force). Handles registered communication, MM. C. Handles registration communication with the relay server 120. SIG. C. Unit 114 handles signaling communication with external network terminals 240 to 270 on the basis of SIP over TCP or UDP. C. Handles signaling communications with the relay server 120. MM. C. Unit 116 is based on the standard protocol RTP (Real Time Protocol) / RTCP (Real Time Control Protocol) stipulated in the RFC1889 specifications on TCP or UDP. C. It handles multimedia communications for audio, video and / or text etc. with the relay server 120.

  6 shows the MM. C. MM. C. The configuration of the relay server 120 is shown. MM. C. The relay server 120 includes a processor 1210 and a storage device 1212, and is physically connected to the intranet 140 via a network interface (NW I / F). MM. Via the IP interface (non-IP I / F). C. It is connected to the server 110. The storage device 1212 stores a program for appropriately relaying registration communication, signaling communication, and multimedia communication. A processing generator 122 is mounted on the processor 1210 according to the program, and the processing generator 122 is a registered communication (REG.C.) relay component having the same configuration as the registered communication (REG.C.) relay unit 123. 1231, 1232, ... and 1234, a signaling communication (SIG.C.) relay unit 124 that may include a plurality of signaling communication relay components, and a multimedia communication that may include a corresponding plurality of multimedia communication relay components (MM.C.) The relay unit 126 is dynamically generated.

  REG. C. The relay components 1231 to 1234 are connected to the SIP server 150 on the intranet 140 and the MM. C. Conversion between the communication protocols of the server 110 and modification or conversion of the registration message and the registration completion message are performed. SIG. C. The relay unit 124 includes terminals 162 to 166 on the intranet 140 and MM. C. Convert between server 110 signaling protocols. MM. C. The relay unit 126 includes a multimedia communication protocol RTP / RTCP on UDP used by the terminals 162 to 166 on the intranet 140, MM. C. Conversion between the multimedia communication protocol RTP / RTCP on UDP realized on TCP used by the server 110 is performed.

  Returning to FIG. C. Server 110 and MM. C. Manages calls in the relay server 120. The management component 118 is connected to the SIG. C. Part 114 and MM. C. The correspondence relationship with the unit 116 is controlled. The management component 118 is SIG. C. Relay unit 124 and MM. C. The correspondence relationship with the relay unit 126 is controlled.

  MM. C. All the functions of the relay server 120 are arranged in the DMZ 100 in the MM. C. The server 110 may be incorporated as one server.

  The SIP server 150 receives from the terminals 162 to 166 and 240 to 270 a registration message requesting registration of the terminal identification and IP address, and stores the terminal identification and IP address of the terminal in the registration database 152; A registration complete (200 OK) message is sent back to the terminal, and then a call is made between any two or more of those terminals in response to a request from any of the registered terminals For example, MM. C. The SIG. C. One of the components 1141-1144 and the MM. C. Relay server 120 SIG. C. A call is established between one of terminals 240-270 and one of terminals 162-166 on intranet 140 via one of relay components 1241-1244.

  Referring to FIG. C. The REG. C. The component 1131 includes a protocol conversion unit 11309, a protocol check (determination) unit 11310, a receiver / transmitter unit 11312 connected to the terminals 240 to 270 via the network 40, and the MM. C. The corresponding SIG. C. And a transmitter / receiver unit 11314 connected to the receiver / transmitter unit (12312) of the relay component 1231. The receiver / transmitter unit 11312, the protocol check unit 11310, the protocol conversion unit 11309, and the transmitter / receiver unit 11314 are connected in cascade. In the configuration of FIGS. 1 and 2, the protocol conversion unit 11309 processes the registration message with the external network 40 and the MM. C. Conversion between the protocols of the relay server 120 is performed. 3 and 4, the protocol conversion unit 11309 performs conversion between the IP protocol for the external network 40 and the non-IP standard protocol for the cable 640 or the RF signal 642. The protocol check unit 11310 checks the connection request and the registration message in accordance with a predetermined communication protocol, and sends a connection response, sends a connection request, or forwards a message in response thereto.

  MM. C. The SIG. C. Unit 114 includes a signaling protocol conversion unit 11409, a protocol check unit 11410, a receiver / transmitter unit 11412 connected to the terminals 240 to 270 via the network 40, and the MM. C. The corresponding SIG. C. A transmitter / receiver unit 11414 connected to the receiver / transmitter unit (12412) of the relay unit 124 and a connection management information transmitting / receiving unit (CMI) 11418 are included. The receiver / transmitter unit 11412, the protocol check unit 11410, the signaling protocol conversion unit 11409, and the transmitter / receiver unit 11414 are connected in cascade. In the configuration of FIGS. 1 and 2, the protocol conversion unit 11309 is connected to the external network 40 and the MM. C. Conversion between the protocols of the relay server 120 is performed. 3 and 4, the protocol conversion unit 11409 performs conversion between the IP signaling protocol for the external network 40 and the non-IP standard signaling protocol for the cable 640 or the RF signal 642. The protocol check unit 11410 checks the connection request and the signaling message according to a predetermined communication protocol, and sends a connection response or a connection request in response thereto.

  MM. C. 4 includes a multimedia communication protocol converter 11609, a protocol check unit 11610, a receiver / transmitter unit 11612 connected to the terminals 240-270 via the network 40, and the MM. C. The corresponding MM. C. A transmitter / receiver unit 11614 connected to the receiver / transmitter unit (12612) of the relay unit 126 and a connection management information transmitting / receiving unit 11618 are included. The receiver / transmitter unit 11612, the protocol check unit 11610, the multimedia communication protocol conversion unit 11609, and the transmitter / receiver unit 11614 are connected in cascade. In the configuration of FIGS. 1 and 2, the protocol conversion unit 11609 is connected to the external network 40 and the MM. C. Conversion between the protocols of the relay server 120 is performed. 3 and 4, the protocol conversion unit 11609 performs conversion between the IP standard multimedia communication protocol for the external network 40 and the cable 640 or the non-IP standard multimedia communication protocol for the RF signal 642. The protocol check unit 11610 checks the connection request and the received packet of the multimedia data stream according to a predetermined protocol, and in response, sends a connection response, passes the matching packet, and discards the non-matching packet. Or

  Referring to FIG. C. The REG. C. The relay component 1231 includes a protocol conversion unit 12309, a protocol check unit 12310, a message modification unit 12311, and the MM. C. The corresponding REG. C. A receiver / transmitter unit 12312 connected to the transmitter / receiver unit 11314 of the component 1131 and a transmitter / receiver unit 12314 connected to the terminals 162 to 166 via the intranet 140 are included. The receiver / transmitter unit 12312 and the protocol conversion unit 12309 are coupled to each other. The protocol check unit 12310 is coupled to the message modification unit 12311. Message modification unit 12311 is coupled to protocol conversion unit 12309 and transmitter / receiver unit 12314. The protocol conversion unit 12309 and the transmitter / receiver unit 12314 are coupled to the protocol check unit 12310. In the configuration of FIGS. 1 and 2, the protocol conversion unit 12310 is configured to transfer the registration message with the MM. C. Protocol conversion between the server 110 and the intranet 140 is performed. In the configuration of FIGS. 3 and 4, the protocol conversion unit 12310 performs MM. C. The protocol conversion between the server 110 and the intranet 140 is performed, and further the conversion between the IP standard protocol for the external network 40 and the non-IP standard protocol for the cable 640 or the RF signal 642 is performed.

  The protocol check unit 12310 checks a connection request, registration, and registration completion message according to a predetermined protocol, and in response, sends a connection response, passes a matching packet, and discards a non-matching packet. The message modification unit 12311 modifies the registration request message from the external terminals 240 to 270 to be compatible with transmission to the SIP server 150, and adapts the registration completion message from the SIP server 150 to transmission to the external terminals 240 to 270. To be modified.

  MM. C. Relay server 120 SIG. C. The relay unit 124 includes a protocol conversion unit 12410 and the MM. C. The corresponding SIG. C. Receiver / transmitter unit 12412 connected to the transmitter / receiver unit 11414 of the unit 114, transmitter / receiver unit 12414 connected to the terminals 162 to 166 via the intranet 140, and a connection management information transmitting / receiving unit 12418. The receiver / transmitter unit 12412, the protocol conversion unit 12410, and the transmitter / receiver unit 12414 are connected in cascade. In the configuration of FIGS. 1 and 2, the protocol conversion unit 12410 performs MM. C. Protocol conversion between the server 110 and the intranet 140 is performed. In the configuration of FIGS. 3 and 4, the protocol conversion unit 12410 performs MM. C. Protocol conversion between the server 110 and the intranet 140 is performed, and further, conversion is performed between the IP standard signaling protocol for the external network 40 and the non-IP standard signaling protocol for the cable 640 or the RF signal 642.

  MM. C. Similarly, the relay unit 126 includes the protocol conversion unit 12610 and the MM. C. The corresponding MM. C. Receiver / transmitter unit 12612 connected to the transmitter / receiver unit 11614 of the unit 116, transmitter / receiver unit 12614 connected to the terminals 162 to 166 via the intranet 140, and a connection management information transmitting / receiving unit 12618. The receiver / transmitter unit 12612, the protocol conversion unit 12610, and the transmitter / receiver unit 12614 are connected in cascade. 1 and 2, the protocol conversion unit 12610 is configured to receive a connection request and a multimedia data stream received packet from the MM. C. Protocol conversion between the server 110 and the intranet 140 is performed. In the configuration of FIGS. 3 and 4, the protocol conversion unit 12610 performs MM. C. Performs protocol conversion between the server 110 and the intranet 140, and further converts between the IP standard multimedia communication protocol for the external network 40 and the non-IP standard multimedia communication protocol for the cable 640 or RF signal 642. .

  FIG. 7 shows the MM. C. A modification of the server 110 is shown. 8 shows the MM. C. A variation of the relay server 120 is shown. 7, the message modification unit 11311 corresponding to the message modification unit 12311 in the registered communication component 1231 in FIG. 6 is coupled to the transceiver 11312 and the protocol conversion unit 11309 in FIG. 5, and the protocol check unit 11310 is the message modification unit 11311. The protocol conversion unit 11309 and the transceiver 11312 are coupled to the protocol check unit 11310. In FIG. 8, the message modification unit 12311 in FIG. 6 does not exist, and the transceiver 12312, the protocol converter 12309, the protocol check unit 11310, and the transceiver 12314 are cascade-connected.

  FIG. 9 shows a basic configuration of the intranet terminals 162 to 166 and the external network terminals 240 to 270 in FIGS. Each terminal includes a processor 1621, a storage device 1622, an audio circuit 1623, a display device 1624 and an input device 1625. The storage device 1622 stores a program for signaling communication and multimedia communication used in a terminal-to-terminal communication application such as an IP telephone application executed by the processor 1621. Audio circuit 1623 is coupled to microphone 1632 and speaker 1634. Terminals 162 to 166 and 240 to 270 have a registration communication unit, a signaling unit, and a multimedia communication unit mounted on processor 1621 according to a program. External network terminals 240 and 250 or NAT router 210 and terminal 270 may be assigned a fixed terminal identification or IP telephone number in the form of an e-mail address and may further be assigned a fixed IP address.

  FIG. 10 shows the registration communication of the external network terminal 240 or 270 over TCP when the user of the external network terminal 240 or 270 registers the terminal identification and IP address in the SIP server 150 of the call center 10 in FIGS. Part 2432, MM. C. The REG. C. Component 1131, MM. C. The REG. C. The procedure of terminal identification and IP address registration executed between the relay component 1231 and the registration communication unit (REG.) 1531 of the SIP server 150 is shown. In this figure, REG. Of the intranet terminal 162 and the SIP server 150 are displayed. C. A procedure for registration of terminal identification executed between the units 1531 is also shown. FIG. 11 shows an alternative terminal identification registration procedure executed between them in FIGS. 1 and 2 on TCP and UDP.

  10 and 11, the procedure includes a phase I at startup and a phase II for registration. In phase I, MM. C. The REG. C. The relay component 1231 is MM. C. The REG. C. A TCP connection 602 with the component 1131 is established in advance, that is, REG. C. The relay component 1231 initiates a TCP connection and REG. C. A TCP connection request is sent to the component 1131 and then a TCP connection response is received. Next, REG. C. Relay component 1231 and REG. C. The components 1131 send and receive a send / receive ready message 604 to each other, and REG. C. The relay component 1231 enters a registration message waiting state.

  In phase II of FIG. 10, when the user of the external network terminal 240 or 270 activates the registered communication application on the terminal and connects to the call center 10, the terminal 240 or 270 (registration unit 2432) C. The TCP connection 606 with the server 110 (REG.C. component 1131) is established first, and then the MM. C. A registration message 608 representing a terminal identification and IP address registration request is sent to the server 110 (component 1131) based on SIP.

  MM. C. The server 110 (component 1131) checks the received registration message 608 for the protocol, and if appropriate, converts the protocol if necessary, and converts the MM. C. The registration message 612 is sent to the relay server 120 (REG.C. relay component 1231) based on SIP.

  As an alternative configuration, in the registration procedure of FIGS. C. Instead of establishing the TCP connection 602 in phase I at startup, the relay server 120 (component 1231) does not use the MM. C. In response to the registration message 608 detected by the server 110 in the intermittent or periodic monitoring period in Phase II, REG. C. Another TCP connection 609 is established with the component 1131, and the REG. C. A registration message 612 may be received from the component 1131. Registration messages 608 and 612 include MM. C. Internal information related to the relay server 120 is not included.

  MM. C. The relay server 120 (component 1231) converts and checks the received registration message 609 with respect to the protocol if necessary, and if appropriate, responds to reception of the registration message 612 and modifies the registration message according to SIP. Then, the TCP connection 614 with the SIP server 150 (registration communication unit 1531) is established first, and then the modified registration message 616 is sent. The registration message 616 includes an MM. C. Internal information related to the relay server 120 is included.

  The SIP server 150 registers the terminal identification and IP address in the message in the registration database 152 based on the registration message from the terminals 240 to 270.

  In response to the registration message 616, the SIP server 150 (registration communication unit 1531) stores the terminal identification and IP address of the terminal 240 or 270 in the registration database 152, thereby completing the registration. Thereafter, the SIP server 150 (registration communication unit 1531) makes the MM. C. A registration completion message 618 indicating completion of registration is transmitted to the relay server 120 and returned. The registration completion message 618 includes an MM. C. Internal information related to the relay server 120 is included.

  MM. C. In response to receiving the registration completion message 618, the relay server 120 (component 1231) checks the received registration completion message 618 for the protocol, modifies it if appropriate, and converts the protocol if necessary. The modified registration completion message 620 is sent to the MM. C. Send to server 110 (component 1131). The registration completion message 620 includes an MM. C. Internal information related to the relay server 120 is not included, so that the MM. C. The risk that the intranet 140 or the like may be illegally accessed via the relay server 120 can be reduced.

  MM. C. In response to receiving the completion message 620, the server 110 (component 1131) converts the protocol as necessary, and sends a registration completion message 622 to the terminal 240 or 270 (signaling unit 2432). The registration completion message 622 includes an MM. C. Internal information related to the relay server 120 is not included.

  MM. C. Instead of modifying the registration message 612 by the relay server 120 (component 1231), the MM. C. The registration message 608 may be modified by the server 110 (component 1131). In this case, the registration completion message 612 includes an MM. C. Internal information related to the relay server 120 is included. MM. C. Instead of modifying the registration completion message 618 by the relay server 120 (component 1231), the MM. C. The registration completion message 620 may be modified by the server 110 (component 1131). In this case, the registration completion message 620 includes an MM. C. Internal information related to the relay server 120 is included.

  The terminal 240 or 270 responds to the reception of the registration completion message 622 and enables a subsequent call or call connection request. In this way, the user of the terminal 240 or 270 and the operator or agent of the terminal 162 of the call center 10 can perform multimedia communication (for example, IP telephone). Thereafter, the communication procedure continues to the signaling and multimedia communication described in JP-A-2003-324485 and illustrated in FIGS. When the IP address of the terminal 240 or 270 is changed, the terminal 240 or 270 transmits the registration message again to register the terminal identification and the IP address in the SIP server 150. In this case, the SIP server 150 overwrites the terminal identification and IP address of the terminal 240 or 270 stored in the registration database 152.

  On the other hand, the intranet terminal 162 establishes a TCP connection 652 in the normal form with the SIP server 150 on the intranet 140 and sends a registration message 654. In response to receiving the registration message 654, the SIP server 150 stores the terminal identification or IP telephone number of the terminal 162 and the private IP address in the registration database 152. When the private IP address of the terminal 162 is changed, the terminal 162 transmits the registration message to the SIP server 150 again.

  In FIG. C. The REG. C. Component 1131 and MM. C. The REG. C. The registration communication with the relay component 1231 is performed on the TCP, but the registration communication unit 2432 of the external network terminal 240 or 270 and the MM. C. The REG. C. Registration communication between the components 1131 and MM. C. The REG. C. Registration communication between the relay component 1231 and the registration communication unit (REG.) 1531 of the SIP server 150 is performed on UDP. Phase I in FIG. 11 is the same as that in FIG. In phase II of FIG. 11, the terminal 240 or 270 (registration unit 2402) replaces the TCP connection 606 of FIG. C. A UDP connection 607 is established with the server 110 (SIG.C. component 1131). Similarly, MM. C. The relay server 120 (component 1231) establishes a UDP connection 615 with the SIP server 150 (registered communication unit 1531) instead of the TCP connection 614.

  In FIG. 11, the terminal 162 establishes a UDP connection 653 in a normal form with the SIP server 150 on the intranet 140 instead of establishing a TCP connection in FIG. 10. Other procedures in FIG. 11 are the same as those in FIG.

  FIG. 12 shows the signaling unit 2402, MM. Of the external network terminal 240 or 270 on the TCP and link when the user of the external network terminal 240 or 270 places a call to the call center 10 in FIGS. C. The SIG. C. Component 1131, MM. C. Relay server 120 SIG. C. A terminal identification registration procedure executed between the relay component 1231 and the registration communication unit 1531 of the SIP server 150 is shown. In this case, MM. C. The SIG. C. Component 1131 and MM. C. Relay server 120 SIG. C. The relay component 1231 is connected with the non-IP link 640 or 642 as described above. FIG. 13 shows an alternative terminal identity registration procedure performed between FIGS. 3 and 4 over UDP and link.

  The terminal 240 or 270 (registered communication unit 2432) can receive the MM. C. The TCP connection 606 with the server 110 (REG.C. component 1131) is established first, and then the MM. C. A message 608 representing a registration request is sent to the server 110 based on SIP. MM. C. The server 110 (component 1131) checks the received registration request message 608 regarding the protocol, and if it is appropriate, the MM. C. A link 706 is established with the relay server 120 (REG.C. relay component 1231) and a registration message 612 is sent on the established link 706 based on non-IP. In this case, MM. C. Server 110 (component 1131) and MM. C. Both relay servers 120 (REG.C. relay component 1231) perform at least IP-to-IP protocol conversion for communication over non-IP link 640 or 642. Other procedures in FIG. 12 are the same as those in FIG.

  In FIG. C. The REG. C. Component 1131 and MM. C. The REG. C. Registration communication with the relay component 1231 is performed on the link 640 or 642, but the registration communication unit 2432 of the external network terminal 240 or 270 and the MM. C. The REG. C. Registration communication between the components 1131 and MM. C. The REG. C. Registration communication between the relay component 1231 and the registration communication unit (REG.) 1531 of the SIP server 150 is performed on UDP. The terminal 240 or 270 (registration unit 2402) is configured so that the MM. C. A UDP connection 607 is established with the server 110 (SIG.C. component 1131). Similarly, MM. C. The relay server 120 (component 1231) establishes a UDP connection 615 with the SIP server 150 (registered communication unit 1531) instead of the TCP connection 614. Other procedures in FIG. 13 are the same as those in FIG.

  FIG. 14 shows examples of a registration message 608, a modified registration message 616, a registration completion message 618 and a modified registration completion message 622. If the message is modified at the MMC relay server 120, the registration message 612 is the same as the registration message 608, and the modified registration completion message 620 is the same as the modified registration completion message 622. When the message modification is performed at the MMC server 110, the modified registration completion message 612 is the same as the modified registration completion message 616, and the modified registration completion message 620 is the same as the modified registration completion message 622. is there.

  The registration message 608 includes a request line “REGISTER sip: 10.254.33.12 SIP / 2.0” indicating registration (Register, register) and a Via header “Via: SIP / 2.0 / UDP 10.2.3.4:5060; z9hG4bKnashds7 ”, To header“ To: UserA <sip: UserA@example.jp> ”, From header“ From: UserA <sip: UserA@example.jp>; tag = 456248 ”, A Contact header “Contact: <sip: UserA@10.2.3.4>” is included. Here, “10.254.33.12” in the Register request line is REG. C. This represents the IP address of the component 1131. “10.2.3.4” in the Via header and Contact header represents the IP address of the terminal 240 that is the initiator that transmitted the registration message. “: 5060” in the Via header represents the port of the terminal 240. “UserA@example.jp” in the To header and From header represents the terminal identification of the terminal 240 or the IP telephone number.

  The modified registration message 616 includes a Register request line “REGISTER sip: 192.168.0.5 SIP / 2.0”, a Via header “Via: SIP / 2.0 / UDP 192.168.0.10:5060; branch = z9hG4bKnashds7”, and a To header “To: UserA <sip: UserA@example.jp> ”, From header“ From: UserA <sip: UserA@example.jp>; tag = 456248 ”, and Contact header“ Contact: <sip: UserA@10.2.3.4> ” And a Path header “Path: <sip: 192.168.0.10>” and a Supported header “Supported: path”. Here, REG. C. The IP address of the component 1131 is replaced with the IP address “192.168.0.5” of the SIP server 150 as the call connection control device, and the IP address “10.2.3.4” of the terminal 240 or 270 in the Via header is changed to REG. C. The IP address “192.168.0.10” of the relay component 1231 is replaced, and a Path header and a Supported header are added. Therefore, the terminal 240 does not need to create a Path header and a Supported header. “192.168.0.10” in the Path header is REG. C. This is the IP address of the component 1231.

  The registration completion message 618 includes a 200 OK (registration completion) status line “SIP / 2.0 200 OK”, a Via header “Via: SIP / 2.0 / UDP 192.168.0.10:5060; branch = z9hG4bKnashds7”, and a To header “To: UserA <sip: UserA@example.jp>; tag = 251077 ”, From header“ From: UserA <sip: UserA@example.jp>; tag = 456248 ”, and Contact header“ Contact: <sip: UserA@10.2 ” .3.4> ”and a Path header“ Path: <sip: 192.168.0.10> ”. Here, REG. C. The IP address “192.168.0.10” of the component 1231 is included.

  The modified registration completion message 622 includes a 200 OK status line “SIP / 2.0 200 OK”, a Via header “Via: SIP / 2.0 / UDP 10.2.3.4:5060; branch = z9hG4bKnashds7”, and a To header “To: UserA <sip: UserA@example.jp>; tag = 251077 ”, the From header“ From: UserA <sip: UserA@example.jp>; tag = 456248 ”, and the Contact header“ Contact: <sip: UserA@10.2. 3.4> ”and a Path header“ Path: <sip: 192.168.0.10> ”. Here, REG. C. The IP address of the component 1231 is replaced with “10.2.3.4” of the terminal 240 or 270, and the Path header is deleted. Therefore, the terminal 240 does not need a function for processing the Path header and the Supported header in the 200 OK message, and the MM. C. REG. C. It is prevented that the IP address of the component 1231 is unnecessarily transmitted to the external network 40.

  FIG. 15 shows the signaling unit 2402, MM., Etc. of the external network terminal 240 or 270 when the user of the external network terminal 240 or 270 places a call to the call center 10 in FIGS. C. The SIG. C. Component 1141, MM. C. Relay server 120 SIG. C. The signaling procedure executed between the relay component 1241 and the signaling unit 1642 of the intranet terminal 162 is illustrated.

  The procedure includes Phase I at startup and Phase III for call establishment. In phase I, MM. C. Relay server 120 SIG. C. The relay component 1241 is an MM. C. The SIG. C. The TCP connection 702 with the component 1141 is established in advance, that is, SIG. C. The relay component 1241 initiates a TCP connection and SIG. C. A TCP connection request is sent to the component 1141, and then a TCP connection response is received. Then, SIG. C. Relay component 1241 and SIG. C. The components 1141 send and receive the transmission / reception ready message 704 to each other, and both enter the incoming call request waiting state.

  16 shows the multimedia communication unit 2404, MM., Etc. of the external network terminal 240 or 270 in FIGS. C. The MM. C. Component 1161, MM. C. The MM. C. The multimedia communication procedure executed between the relay component 1261 and the multimedia communication unit 1644 of the intranet terminal 162 is illustrated.

  In FIG. 16, the procedure includes the above-described phase I at startup and phase IV for multimedia communication after phase III. In phase I, MM. C. The MM. C. The relay component 1261 is an MM. C. The MM. C. A TCP connection 802 with the relay component 1161 is established in advance. Then, MM. C. Relay component 1261 and MM. C. The relay components 1161 send and receive a transmission / reception ready message 804 to each other, and both enter a multimedia data stream reception waiting state.

  In phase III of FIG. 15, when the user of the external network terminal 240 or 270 activates the multimedia communication application on the terminal and places a call to the call center 10, the terminal 240 or 270 (signaling unit 2402) C. The TCP or UDP connection 706 with the server 110 (SIG.C. component 1141) is established first, and then the MM. C. A signaling message 708 representing a call or call connection request or call initiation request is sent to the server 110 (component 1141) based on SIP.

  MM. C. Server 110 (component 1141) checks its received signaling message 708 for the protocol and, if appropriate, MM. C. An incoming call request or signaling request message 711 is sent to the relay server 120 (SIG.C. relay component 1241) based on SIP.

  Instead of establishing a TCP connection 702 in phase I at startup, MM. C. In response to the signaling message 708 detected by the server 110 in the intermittent or periodic monitoring period in Phase III, the SIG. C. Another TCP connection 709 is established between the component 1141 and the SIG. C. An incoming call request message 711 may be received from the component 1141.

  MM. C. In response to receiving the incoming call request message 711, the relay server 120 (component 1241) first establishes a TCP or UDP connection 712 with the intranet terminal 162 (signaling unit 1642) via the SIP server 150, and then A signaling message 714 representing an incoming call or call connection request according to SIP is sent to the terminal 162 (signaling unit 1642).

  The SIP server 150 refers to the registration database 152 to determine which of the terminals 162 to 166 receives the call, and the TCP or UDP connection 712 is connected to the MM. C. It may be established between the relay server 120 and the determined terminal 162. The call control function of the SIP server 150 is changed to MM. C. It may be incorporated in the relay server 120.

  In response to the signaling message 714, the terminal 162 (signaling unit 1642) can call MM. C. A signaling completion message 716 indicating completion of incoming call or call connection is sent to the relay server 120 to establish a call. MM. C. In response to receiving the signaling completion message 716, the relay server 120 (component 1241) sends an incoming call completion message 718 to the MM. C. Send to server 110 (component 1141). MM. C. In response to reception of the incoming call completion message 718, the server 110 (component 1141) sends a signaling completion message 720 indicating call connection completion to the terminal 240 or 270 (signaling unit 2402). In response to receiving the signaling completion message 720, the terminal 240 or 270 establishes the call.

  The signaling messages 708, 711, and 714 to 720 include information necessary for performing media communication, that is, an IP address and a port number, and a type of a call or communication media (for example, voice only, voice and video, etc.) And are included.

  In this way, the user of the terminal 240 or 270 and the operator or agent of the terminal 162 of the call center 10 can perform multimedia communication. Thereafter, the communication procedure continues to Phase IV in FIG.

  Referring to FIG. 16, in phase IV, the terminal 240 or 270 (multimedia communication unit 2404) transmits the MM. C. A UDP connection 832 is established with the server 110 (MM.C. component 1161). Next, the terminal 240 or 270 (communication unit 2404) and the MM. C. A multimedia data stream 814 is transmitted and received between the servers 110 (component 1161). MM. C. The relay server 120 (component 1261) and the terminal 162 (multimedia communication unit 1644) establish a UDP connection 806 with each other using the respective UDP ports determined by the signaling. MM. C. A multimedia data stream 818 is transmitted and received according to RTP between the relay server 120 (component 1261) and the terminal 162 (communication unit 1644). MM. C. Server 110 (component 1161) and MM. C. A multimedia data stream 816 is transmitted / received between the relay server 120 (component 1261) over a TCP connection 802 established in advance.

  17 shows the signaling unit 2402, MM., Etc. of the external network terminal 240 or 270 in FIGS. C. The SIG. C. Component 1141, MM. C. Relay server 120 SIG. C. FIG. 9 illustrates another signaling procedure performed between the relay component 1241 and the signaling unit 1642 of the intranet terminal 162.

  The terminal 240 or 270 (signaling unit 2402) is connected to the MM. C. The TCP or UDP connection 706 with the server 110 (SIG.C. component 1141) is established first, and then the MM. C. A signaling message 708 is sent to the server 110 (component 1141) based on SIP.

  MM. C. Server 110 (component 1141) checks its received signaling message 708 for the protocol and, if appropriate, MM. C. A link 710 is established with the relay server 120 (SIG.C. relay component 1241) to send a signaling request message 711 based on non-IP.

  MM. C. In response to receiving the incoming call request message 711, the relay server 120 (component 1241) first establishes a TCP or UDP connection 712 with the intranet terminal 162 (signaling unit 1642) via the SIP server 150, and then A signaling message 714 according to SIP is sent to the terminal 162 (signaling unit 1642). The subsequent procedure is the same as that of the procedure of FIG.

  18 shows the multimedia communication unit 2404, MM., Etc. of the external network terminal 240 or 270 in FIGS. C. The MM. C. Component 1161, MM. C. The MM. C. 6 illustrates another multimedia communication procedure executed between the relay component 1261 and the multimedia communication unit 1644 of the intranet terminal 162.

  18, the MM. C. The SIG. Component 1141 is MM. C. Relay server 120 SIG. When the link 710 with the component 1241 is established, the MM. C. The MM. C. The component 1161 is an MM. C. The MM. C. Establish link 805 with relay component 1261. MM. C. Relay server 120 (component 1261) and MM. C. A multimedia data stream 816 is transmitted and received between the server 110 (component 1161) over the established link 805 according to non-IP. Other procedures in FIG. 18 are the same as those in FIG.

  The embodiments described above are merely given as typical examples, and it is obvious to those skilled in the art to combine the components of each embodiment, and variations and variations thereof will be apparent to those skilled in the art. Obviously, various modifications may be made to the above-described embodiments without departing from the scope of the invention as set forth in the scope.

Regarding the embodiment including the above examples, the following additional notes are further disclosed.
(Supplementary Note 1) An information processing apparatus as a first apparatus connectable to a second apparatus and an intranet in a DMZ,
Establishing a connection or link with the second device, receiving a registration message from the second device, modifying the received registration message and transferring it to a third device on the intranet; An information processing apparatus comprising transfer means for receiving a registration completion message from the third device over the established connection or link, modifying the received registration completion message, and transferring the message to the second device.
(Supplementary note 2) The transfer means modifies the registration message by incorporating a path header into the registration message, and modifies the registration completion message by deleting the path header from the registration completion message. The information processing apparatus according to attachment 1.
(Supplementary note 3) The information processing apparatus according to supplementary note 1, wherein the transfer unit establishes the connection with the second device in a direction from the intranet to the external network.
(Supplementary Note 4) Further, a connection with the second device is established, a connection is established on the intranet, and a signal is transmitted or received on the intranet, and the second device and a terminal on the intranet The information processing apparatus according to claim 1, further comprising signaling means for establishing a call between the two.
(Supplementary Note 5) An information processing apparatus as a first apparatus that can be connected to a second apparatus on an intranet and an external network and can be arranged in a DMZ.
Establishing a connection or link with the second device, receiving a registration message from a third device on the external network, modifying the received registration message to the second device on the intranet And a first means for receiving a registration completion message from the second device, modifying the received registration completion message, and transferring it to the third device.
(Supplementary Note 6) A program for an information processing device as a first device connectable to a second device and an intranet in a DMZ,
Establishing a connection or link with the second device;
Receiving a registration message from the second device over the established connection or link, modifying the received registration message and transferring it to a third device on the intranet;
Receiving a registration completion message from the third device on the established connection or link, modifying the received registration completion message and transferring it to the second device;
A program that is operable to run
(Supplementary note 7) A program for an information processing device as a first device that can be connected to a second device on an intranet and an external network and can be arranged in a DMZ,
Establishing a connection or link with the second device;
Receiving a registration message from a third device on the external network over the established connection or link, modifying the received registration message and transferring it to the second device on the intranet; When,
Receiving a registration completion message from the second device over the established connection or link, modifying the received registration completion message and transferring it to the third device;
A program that is operable to run
(Supplementary note 8) A communication method in an information processing apparatus as a first apparatus connectable to a second apparatus and an intranet in a DMZ,
Establishing a connection or link with the second device;
Receiving a registration message from the second device on the established connection or link, modifying the received registration message and transferring it to a third device on the intranet;
Receiving a registration completion message from the third device over the established connection or link, modifying the received registration completion message and transferring it to the second device;
Including methods.
(Supplementary Note 9) A communication method in an information processing apparatus as a first apparatus that can be connected to a second apparatus on an intranet and an external network and can be arranged in a DMZ,
Establishing a connection or link with the second device;
Receiving a registration message from a third device on the external network on the established connection or link, modifying the received registration message and transferring it to the second device on the intranet; When,
Receiving a registration completion message from the second device over the established connection or link, modifying the received registration completion message and transferring it to the third device;
Including methods.

FIG. 1 shows a system configuration including an intranet connected to a server and a terminal and an external network connected to an external terminal according to an embodiment of the present invention. FIG. 2 illustrates another system configuration including an intranet and an external network, according to another embodiment of the present invention. FIG. 3 shows yet another system configuration including an intranet connected to a server and a terminal and an external network connected to an external terminal according to still another embodiment of the present invention. FIG. 4 illustrates yet another system configuration including an intranet and an external network, according to yet another embodiment of the present invention. 5 shows the configuration of a multimedia communication (MM.C.) server. 6 shows the MM. C. Fig. 2 illustrates a configuration of a multimedia communication relay server coupled to a server. FIG. 7 shows the MM. C. Shows a variant of the server. 8 shows the MM. C. A variation of the relay server is shown. FIG. 9 shows a basic configuration of the intranet terminal and the external network terminal in FIGS. FIG. 10 shows the registration communication unit of the external network terminal, MM. C. Server, MM. C. The procedure of terminal identification and IP address registration executed between the relay server and the SIP server is shown. FIG. 11 shows the registration communication unit of the external network terminal, MM. C. Server, MM. C. Fig. 5 illustrates an alternative terminal identification registration procedure performed between a relay server and a SIP server. FIG. 12 shows the registration communication unit of the external network terminal, MM. C. Server, MM. C. The terminal identification registration procedure performed between a relay server and a SIP server is shown. FIG. 13 shows the registration communication unit of the external network terminal, MM. C. Server, MM. C. Fig. 6 shows an alternative terminal identification registration procedure performed between a relay server and a SIP server. FIG. 14 shows an example of a registration message, a modified registration message, a registration completion message, and a modified registration completion message. FIG. 15 shows an external network terminal, MM. C. Server, MM. C. Fig. 3 illustrates a signaling procedure performed between a relay server and an intranet terminal. FIG. 16 shows an external network terminal, MM. C. Server, MM. C. Fig. 3 illustrates a multimedia communication procedure executed between a relay server and an intranet terminal. FIG. 17 shows an external network terminal, MM. C. Server, MM. C. Fig. 6 illustrates another signaling procedure performed between a relay server and an intranet terminal. FIG. 18 shows an external network terminal, MM. C. Server, MM. C. Fig. 4 illustrates another multimedia communication procedure performed between a relay server and an intranet terminal.

Explanation of symbols

40 External network 80, 85, 90 Firewall 100 DMZ
DESCRIPTION OF SYMBOLS 110 Multimedia communication server 120 Multimedia communication relay server 140 Intranet 150 SIP server 162-166, 240-270 Terminal 1231-1234 Registration communication relay component 12309 Protocol conversion part 12310 Protocol check part 12311 Message modification part 124 Signaling communication relay Part 126 Multimedia Communication Relay Part

Claims (5)

An information processing apparatus as a first apparatus connectable to a second apparatus and an intranet in a DMZ,
Establishing a connection or link with the second device, receiving a registration message from the second device, modifying the received registration message and transferring it to a third device on the intranet; An information processing apparatus comprising transfer means for receiving a registration completion message from the third device over the established connection or link, modifying the received registration completion message, and transferring the message to the second device. An information processing apparatus as a first apparatus that can be connected to a second apparatus on an intranet and an external network and can be arranged in a DMZ,
Establishing a connection or link with the second device, receiving a registration message from a third device on the external network, modifying the received registration message to the second device on the intranet And a first means for receiving a registration completion message from the second device, modifying the received registration completion message, and transferring it to the third device. A program for an information processing device as a first device connectable to a second device and an intranet in a DMZ,
Establishing a connection or link with the second device;
Receiving a registration message from the second device over the established connection or link, modifying the received registration message and transferring it to a third device on the intranet;
Receiving a registration completion message from the third device on the established connection or link, modifying the received registration completion message and transferring it to the second device;
A program that is operable to run A communication method in an information processing apparatus as a first apparatus connectable to a second apparatus and an intranet in a DMZ,
Establishing a connection or link with the second device;
Receiving a registration message from the second device on the established connection or link, modifying the received registration message and transferring it to a third device on the intranet;
Receiving a registration completion message from the third device over the established connection or link, modifying the received registration completion message and transferring it to the second device;
Including methods. A communication method in an information processing apparatus as a first apparatus that can be connected to a second apparatus on an intranet and an external network and can be arranged in a DMZ,
Establishing a connection or link with the second device;
Receiving a registration message from a third device on the external network on the established connection or link, modifying the received registration message and transferring it to the second device on the intranet; When,
Receiving a registration completion message from the second device over the established connection or link, modifying the received registration completion message and transferring it to the third device;
Including methods.

Images