Host-based device to terminate a modem relay channel directly to an IP network

Abstract

A modem data aggregating gateway that supports modem relay functionality for permitting reliable switching of modem traffic between a VoIP network and a data packet switch Internet Protocol (IP) network, s.a. the Internet. The modem relay aggregator may receive modem data encapsulated as Voice over IP (VoIP) data packets in accordance with a Simple Reliable Protocol Transport (SRPT) mechanism. The packet data may be error corrected and/or decompressed before being repackaged for forwarding to the ultimate destination. In the event that the destination is itself an IP device, the modem relay aggregator may forward the packets directly over the IP network. As a result, if the destination of a modem call is an IP device (such as a Web site or other Internet-enabled device) the technique eliminates two points from a processing path in which digital signal processing (DSPs) would otherwise have to perform modem protocol processing. Otherwise, minimal modem reformatting can be performed at the aggregation point.

Description

BACKGROUND OF THE INVENTION

[0001] Most home computer users are now connected to a network such as the Internet in one way or another. The most popular connection technique still is to use the Public Switched Telephone Network (PSTN) and a device called a modem. As is now quite familiar to even the general population, a modem makes a connection by dialing a telephone number of an Internet Service Provider (ISP), who maintains equipment that connects to the Internet. Digital signals generated by the user's computer are converted to analog signals and vice versa by the modem such that they may be carried over the telephone lines accurately.

[0002] What is less familiar to the public at large is the configuration of the ISP equipment and how it provides connections to the Internet. ISPs such as America Online (AOL) maintain a very large number of dial-up access points. These access points permit a user to dial a local telephone number, which then connects the call to a local central office. The central office switch, which may be a so-called Class 5 switch, then directs the call to a dial termination point. The dial termination point may be located in or behind the central office, such as at a computer network Point of Presence (POP). At the POP, a device called a Remote Access Server (RAS) terminates the connection. There, Terminating Modems (TM) at the RAS are often aggregated together. In particular, the RAS contains a large number of modem devices that are used to connect to transmit and receive modem signals to and from the user Originating Modems (OM).

[0003] From the RAS, which converts signals back to digital form, the signals may be carried through a packet based network, such as an Internet Protocol (IP) network, to the Internet. In some instances, large service providers such as AOL contract with network service providers such as Genuity or UUNet to carry traffic from local central office switches to remote access server locations over high-speed digital lines.

[0004] However, other paradigms are resulting in fundamental changes in the nature of the telephone network. Most notably is the change to carry voice traffic from central offices over digital transport networks using technologies originally intended for carrying data traffic such as Internet Protocol (IP). So-called Voice-over-IP (VoIP) packet networks are envisioned to be the architecture of choice of the future for voice transport.

[0005] In this architecture, shown at a high level in FIG. 1, a Central Office (CO) 12 can aggregate multiple Plain Old Telephone Service (POTS) type voice connections 10, multiplexing them into a digital Time Division Multiplex (TDM) transport 14 format such as T1 or E1 carriers. This permits the use of digital technologies to transport voice signals to a transit location in which is installed a Voice Gateway (VoIP GW) 20. The VoIP GW converts the TDM signals to a packet switched transport format, forwarding them to an IP network 30. At the other side of the IP network, a second VoIP GW 40 receives the signals, converts them back to TDM format, and forwards them to a far end Central Office (CO) 42 which then further forwards signal to individual far end POTS connections 44.

[0006] As telecom networks migrate to a VoIP architecture, it becomes important to support various types of calls that a user wishes to make over the TDM network. At present, there are standards for carrying voice, touch tone (Dual-Tone, Multi-Frequency (DTMF)) dialed digits, and fax signaling over IP connections. While there remains an effort to develop standards for carrying modem traffic over TDM connections, there is no standard yet adopted to date for reliable transport of modem signals over IP connections.

[0007] One effort towards solving this problem is so-called modem relay transport. Modem relay is being considered by the International Telecommunications Union (ITU) and Internet Engineering Task Force (IETF), with an aggressive schedule to ratify standards in the near future.

[0008] The basic idea behind this architecture is to insert “modem relay” capability into the VoIP GW. Such an architecture is shown in FIG. 2. Here, the dial modem 14 acts as an origin point for a call to a destination point which may be an Internet Service Provider (ISP) 60. The modem call is first typically forwarded to a Class 5 or other central office switch in the standard fashion over a circuit switched PSTN 18. The Class 5 switch (not shown in FIG. 2) connects the call through the PSTN 18 to an Originating Voice Gateway (OGW) 20, which supports modem relay.

[0009] The OGW 20 implements some amount of modem intelligence (i.e., converting data between analog and digital form) so as to be carried over an IP network 30 to a Terminating Gateway (TGW) 40. This may consist of, for example, (de)modulating the modem protocol data (such as V.34), applying an error correction protocol (V.42), and encapsulating the resulting data modem as a Simple Packet Relay Transport (SPRT) packet.

[0010] The TGW 40 receives this “Modem over IP” (MoIP) formatted packet and then converts it back to a TDM format so that it can be transported over another PSTN 44 connection to a Remote Access Server (RAS) 50. This involves stripping off the SPRT formatting, performing error correction V.42 and data modulation protocol (e.g., V.90, V.34, V.32, V.22 etc.) formatting. From the Remote Access Server, the packet is then passed over a pure TDM network 44 to the ISP 60. Here, the data is (de)modulated and error corrected by the terminating modem (RAS).

[0011] In this modem relay architecture, both the OGW 20 and the TGW 40 must include some amount of modem intelligence in order to permit proper transport of the modem signals over the IP network. In particular, they should perform basic portions of a modem protocol stack processing, as shown. A Digital Signal Processor (DSP) located in each of the gateways 20 and 40 and at the RAS 50 performs the required protocol translations. At the lowest layer of the protocol stack, this includes a physical layer performing modulation/demodulation or data “modem pump” functions in accordance with modem standards (V.90, V.34, V.32, V.22, and the like). The modem enabled gateways 20 and 40 also perform secondary physical layer functions such as error detection and error correction as specified by V.42 or V.44, for example.

[0012] The gateways 20 and 40 also perform tasks associated with network layer tasks. This may, for example, consist of layering a Simple Packet Relay Transport (SPRT) over UDP to format data signals so that they may be properly transported over the IP network 30. Note that the SPRT packets are still compressed (per V.42 bis or V.44) when so forwarded.

SUMMARY OF THE INVENTION

[0013] Basically, the present invention comes about from realizing that one can eliminate one of the PSTN legs of the modem relay call and consequently eliminate a large part of the modem process. Consider that only certain portions of the physical layer modem processing need be performed by the Terminating Gateway (TGW) in order to make the signals compatible for transport over the Internet. Specifically, at an originating point, the users' data is formatted as modem signals and transported to an Originating Gateway (OGW), as with prior art modem relay operations. However, we have noted that the modem signals are already formatted as digital data when they arrive at the Terminating Gateway. Thus, when the destination is ultimately an Internet node, the final PSTN leg can be eliminated, and modem modulation/demodulation signal processing need not be performed at all. The Terminating Gateway (TGW) can therefore simply forward packets to the destination IP network, and with a small amount of processing, can replace the other modem relay functions associated with prior art TGWs and RAS.

[0014] With this architecture, a new device called a Modem Relay Aggregator (MRA) is used. The OGW functions as it does in a modem relay (MR) call, forwarding the modem-over-IP (MoIP) packets to a TGW location. However, the Modem Relay Aggregator (MRA) replaces the functionality of both the Terminating Gateway and the RAS, performing decompression and any application layer processing required, such as PPP termination.

[0015] The MRA therefore replaces the Terminating Gateway, and communicates directly with destination IP devices. This technique provides a much simpler termination for a modem relay solution.

[0016] As a result, an MRA provides a reliable transport for modem traffic across a packet network. It avoids demodulating the modem signal for delivery to the PSTN side of the interface, and then simply sends the encapsulated data to the packet network, eliminating the final PSTN leg. The other system components do not have to complete the aspects of traditional modem relay call processing.

[0017] Using the invention, Internet Service Providers (ISPs) can terminate subscribers' modem sessions transported over a VoIP network using MR. The voice gateway at the originating site need only be modified to support capabilities such as data modulation, error detection, and error correction.

[0018] Several other advantages occur as a result. For example, if the destination of a modem call is an IP device such as a web site, this technique eliminates the need to implement Digital Signal Processing (DSP) to modulate or demodulate signals in at least two locations (namely the TGW and the RAS). This creates the opportunity for more efficient network architectures.

[0019] Indeed, a RAS is also not required. A single device with relatively simple requirements can therefore replace both the RAS and the Terminating Gateway in a conventional modem relay network. An example of a single device may be a computing device having a general purpose or application-specific processor executing software, interfaces(s) to communicate with other network devices, and memory unit to store the software and data packets.

BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention.

[0021] FIG. 1 is a block diagram of a prior art telecommunications network for handling modem traffic;

[0022] FIG. 2 is a block diagram of a prior art modem relay network;

[0023] FIG. 3 is a diagram of a modem relay network in accordance with the present invention;

[0024] FIG. 4 is a generalized block diagram of a modem relay aggregator (MRA) used in the modem relay architecture of FIG. 3;

[0025] FIG. 5 is a generalized flow diagram of an embodiment of a process executed by a processor in the MRA of FIG. 4;

[0026] FIG. 6 is a flow diagram of a process used to transfer data from an originating gateway (OGW) in the network to the MRA of FIG. 4;

[0027] FIG. 7 is a flow diagram of an example data exchange between the MRA of FIG. 4, OGW, and an originating modem using a V.8 modem protocol;

[0028] FIG. 8 is a flow diagram of a process in the MRA of FIG. 4 used for a dial-out session;

[0029] FIG. 9 is a network diagram of the MRA of FIG. 4 being used in alternative locations in the computer network;

[0030] FIG. 10 is a block diagram of a general purpose computer executing software as described in FIGS. 5-8 providing the functionality of the MRA of FIG. 4; and

[0031] FIG. 11 is a schematic diagram of the general purpose computer system of FIG. 10 capable of executing a host-processor-based embodiment of the MRA.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

[0032] A description of a preferred embodiment of the invention follows.

[0033] FIG. 3 is a block diagram of a telecommunications network that implements modem relay in a Voice over internet Protocol (VoIP) network. In such a network, a customer has a telephone that receives and places voice calls to and from another telephone 27. Voice signals are caused to travel over a Public Switched Telephone Network (PSTN) 18 through one or more local central offices (not shown). The central offices include switching equipment such as a Class 5 (C5) switch to aggregate such calls onto a digital Time Division Multiplex (TDM) carrier such as a T1 carrier signal, in a manner that is well known in the art.

[0034] According to well known telephone VoIP voice call control signaling techniques, a voice call is set up by providing a connection through a transport network, such as a Time Division Multiplex (TDM) transport network 19, to an Originating VoIP Gateway 20. The Voice over IP (VoIP) Gateway (VoIP GW) is typically used for carrying voice traffic. In this instance, the TDM voice signals are converted to packet format so that they may be carried over IP network 30 to a Terminating Gateway 24. The Terminating Gateway 24 in turn converts the modem signals to a TDM format (PCM) to be transported feeds signals to a distant Central Office via the PSTN 26. This in turn provides a connection to the destination telephone 27. Voice traffic may thus be carried in this way over the IP network 30 in a manner that is well known in the art.

[0035] The present invention is related to the transmission of modem signals through the VoIP network or so-called Modem over IP (MoIP) transmission. Computer modem signals originating at a customer modem 14, for example, are fed through the carrier IP transit network 30 through a modem relay aggregator 55 to reach Internet connections available such as through an internet Service Provider (ISP) 60. The ISP 60 in turn provides connections to computer networks 70 such as the internet, to obtain data, view World Wide Web sites, and the like.

[0036] In accordance with the principles of the present invention, the terminating gateway device (in this instance, the Modem Relay Aggregator (MRA) 55) requires no conversion to Time Division Multiplex (TDM) format for transport over a second PSTN connection as in the case with the prior art modem relay architecture of FIG. 2. Rather, the present invention takes advantage of implementing modem relay functionality and Internet gateway functionality in the same device. The MRA 55 is thus a new category of telecommunication devices that may operate at the destination end of the carrier IP transit network 30. Here, the MRA 55 completes termination of the modem protocol stack and acts as a gateway to the Internet 70 without the need to traverse the PSTN a second time.

[0037] At the time the modem call is set up, control signaling recognizes the call as a modem call and makes the call destination a modem-relay-aggregator (MRA) enabled VoIP GW 20 rather than a Remote Access Server (RAS) (as in the case with the prior art modem relay network shown in FIG. 2). In practice, modem functionality 220 is supported in the OGW, specifically the ability to perform physical layer modulation/demodulation processing (data modem pump). Thus, when modem signals are received from the customer modem 14 at the Originating Gateway (OGW) 20, only a demodulation function is performed. Likewise, signals to be sent to the customer modem 14 originating from the IP network 30 are remodulated and sent over the TDM network 19. However, that is all the processing that the OGW 20 must perform.

[0038] The OGW 20 thus makes a call to a Modem Relay Aggregator 55, setting up a connection through the IP network 30. The connection may be made through standardized call control signaling (e.g., via an H.323 network 31) in a manner that is well known in the art. After opening the call connection to the MRA 55, the modem data can then be transported over the IP network 30 in compressed form, arriving at the MRA 55.

[0039] Other than demodulating the modem signal and performing error detection and correction, the OGW 20 does not need to complete the remaining aspects of traditional modem termination. For example, decompression and PPP or other transport layer protocols need not be provided by the modem functionality 40 in the Originating Gateway 20. The IP network 30 then carries the compressed and still frame formatted data over the IP network 30 to the MRA 55. It should be noted that a single MRA 55 can perform modem traffic aggregation for a number of different connections.

[0040] The destination IP device 70 may be any IP enabled device such as an Internet gateway, router, IP switch, or other internetworking device that is IP addressable.

[0041] The Modem Relay Aggregator (MRA) 55 may typically perform a number of functions once in a modem relay state. For example, after negotiating an MR session with the OGW 20, the MRA 55 can remove the IP-based encapsulation implemented by a Simple Packet Relay Transport protocol (SPRT) added at the Originating Gateway (OGW) 20. In a next step, the data is decompressed and any application layer processing, such as PPP processing, may be performed, if needed.

[0042] The resulting new IP packet having a destination address for the IP device 70 may then be created. Once this is complete, the MRA 55 may then forward the packet over the packet switched network such as represented by the ISP 60 where it is routed to the destination device 70.

[0043] FIG. 4 is a generalized block diagram of an embodiment of the MRA 55. The MRA 55 includes at least one processor 61 executing software 62, at least one interface 64 connected to the processor(s) 61, at least one memory unit 68 connected to the interface(s) 64 and processor(s) 61, and a display driver 69 connected to the processor(s) 61. The interface(s) 64 may include an ethernet transceiver 66 for data traffic.

[0044] The interface(s) 64 input/output IP packets 65a to and from the originating gateway 20. The interface(s) 64 also communicate IP packets 65b to and from a local or remote computer (not shown).

[0045] The software 62 executed by the processors 61 provides processing for the IP packets 65a, 65b in both the forward and reverse directions (i.e., from the originating gateway 20 to an end node computer or vice versa). The software effectively provides the functionality of the terminating gateway and remote access server of the prior art, and, because of this collapsed functionality, the software allows the elimination of the previously redundant functions of remodulating the data (i.e., terminating voice gateway function) and demodulating the data (i.e., remote access server function). Thus, the MRA 55 does not need to include a digital signal processor (DSP) to perform its operations since the Layer 1 modulation/demodulation processing need not be done in the MRA 55. A flow diagram of the generalized software is shown in FIG. 5.

[0046] Referring to FIG. 5, the MRA 55 executes a process 71, which is part of the software 62 (FIG. 4), when receiving IP packets 65a from the originating gateway 20 in the form of encapsulated data (Step 72) possibly in a PPP session. The process 71 removes the encapsulation (Step 74) and provides termination for a modem session to transport data across a VoIP network using a modem relay technique. For example, the modem session may employ a Simple Packet Relay Transport (SPRT) (Step 75). The process 71 may decompress the data (Step 76), terminate a point-to-point protocol (PPP) session (Step 78), both, or neither.

[0047] Once all the data is collected, the process 71 encapsulates the compressed or uncompressed data in a new IP packet with the destination address of the end node IP device (Step 80). The process 71 ends when the data in the new IP packets have been delivered to the data network for receipt by the end node IP device.

[0048] FIG. 6 is a detailed flow diagram of a process 82 conducted between the MRA 55 and the originating gateway 20. The process 82 may be used when data is sent from the originating gateway 20 through the MRA 55 to the end node (not shown). The process 82 includes (i) a first subprocess 84 executed by the originating gateway 20, referred to as the OGW subprocess 84, and (ii) a second subprocess 86, which is part of the software 62 (FIG. 4) executed by the processor(s) 61 in the MRA 55 and referred to as the MRA subprocess 86.

[0049] The process 82 begins with the OGW subprocess 84 sending a request for a VoIP call (Step 88) to the MRA 55. The MRA subprocess 86 responds to the request for the VoIP call (Step 90). Each of the subprocesses 84, 86 performs a capabilities exchange (CE) (Steps 92a and 92b, respectively). During the capabilities exchange, the OGW 20 and MRA 55 exchange information regarding the signaling methods supported, codec type, and redundancy.

[0050] Following the capabilities exchange (Steps 92a and 92b), the subprocesses 84, 86 determine whether the OGW 20 is Modem Relay Aggregator (MRA) aware or only knows of traditional terminating gateway and Remote Access Server (RAS) technology (Steps 94 and 96). If the newer technology is known to the OGW 20, then the processes advance directly to data transfer (Steps 112 and 114). If working in a traditional technology state, handshaking is performed, starting with the MRA subprocess 86 sending an ANSam tone or indication (Step 100) to the OGW 20, which is detected by the OGW subprocess 84 (Step 104).

[0051] The OGW subprocess 84 receives the ANSam indication and generates a corresponding ANSam tone (Step 104) to its client device (Step 106) and the OGW receives the client modem response such as a Call Menu (CM) tone or response from its client device (Step 107). The CM response is sent (Step 108) by the OGW 20 to the MRA 55, where it is received (Step 110) by the MRA 55.

[0052] At this point in the subprocesses 84, 86, both the OGW subprocess 84 and the MRA subprocess 86 work together to send and receive data packets (Steps 112 and 114). The call is completed (Steps 116 and 118) through a ‘release’ message and ‘release complete’ message, respectively, or some other manner commonly known in the art.

[0053] The handshaking described above may include additional, equivalent, or other steps. For example, after the voice call establishment and capabilities exchange, the OGW 20 and MRA 55 may establish the way to send ANSam indication. The methods possible for sending ANSam indications may include RFC2822 events or Voice Band Data (VBD) indications.

[0054] To illustrate the processes just discussed, FIG. 7 is a flow diagram of a process of a high speed V.8 modem protocol used to transfer data using the MRA 55. Operation is conceptually similar for other modulations, although specific modem events are different for other modulations.

[0055] Referring to FIG. 7, the OGW 20 sends an ANSam tone (Step 120) to the originating modem 14, which detects the ANSam tone (Step 122). The originating modem 14 generates a ‘call menu’ message (Step 124) that is sent back to the OGW 20 (assuming it is a V.8 modem, which includes V.34, V.90, and V.92). Once the CM message is detected by the OGW 20, the OGW 20 can switch to Modem Relay mode (Step 126). Following the transition to Modem Relay mode, the OGW 20 begins a training sequence with the originating modem 14 (Steps 132 and 130, respectively).

[0056] When the originating modem 14 and the OGW 20 reach a data transfer state, data received from the originating modem 14 (Steps 136 and 138) is passed to the MRA 55. The MRA 55 performs data processing on the received data packets (step 140). This data processing includes removing any headers associated with the IP transport layer (e.g. Simple Packet Relay Transport (SPRT)), decompresses the data (if needed) and strips any PPP framing associated with the packet stream, as discussed above in reference to FIG. 5.

[0057] Continuing to refer to FIG. 7, when the MRA 55 begins to receive data packets, it performs some preliminary data processing, including: authentication, dynamic host configuration protocol (DHCP) processing, and IP assignment of the user. When this data processing is complete, the user sends data to the MRA 55. The MRA 55 strips any transport headers, decompresses the data (if needed), and encapsulates the data in new IP packets before directing it to the IP data network (Step 142). When the OGW 20 detects a ‘no carrier’ signal, the session is complete (Step 144), the call is “torn down”, the management and accounting fields are updated (Step 146), and the process ends (Step 148).

[0058] FIG. 8 provides a flow diagram of a process for a case in which the MRA 55 acts as the originating device for a dial-out session initiated by an end user having an IP computing device. The scenario is used to originate calls for dial sessions (to access the remote telemetry information from pay phones and home security systems, for example).

[0059] When a device (e.g., personal computer) requests a dial-out session) (Step 150), it uses an application to communicate with the MRA 55. The MRA 55 receives a dial-out request (Step 152) from the application, parses the request for a destination phone number (Step 154), and refers to a dial plan to determine the route to the destination (Steps 156 and 158). Alternatively, the MRA 55 may obtain the route through a dial-plan maintained by a call agent (Step 160).

[0060] The MRA 55 establishes a voice call (Steps 162 and 164) with the terminating gateway (referred to as the OGW 20 in the dial-in direction), which places a PSTN call to a destination modem (Step 166), as defined by the destination phone number. Once the destination modem/generates an answer tone and the terminating gateway detects the answer tone (Step 168), the same process described above (Step 170) takes place, only the devices and handshaking directions are reversed.

[0061] FIG. 9 is an architectural diagram of a network having two sub-networks, a dial network 172 and a modem relay network 174. The modem relay network 174 has an architecture as discussed above where a modem relay user 180 connects to the originating gateway 20 via the PSTN 16, and the OGW 20 has a Layer 1 modem termination. The MRA 55 receives VoIP packets via the IP transit network 30 from the OGW 20. The MRA 55 provides modem (de)compression, PPP termination, port policy management, AAA, and NMS functions. The MRA 55 is employed by the ISP 182 to provide digital service to end users (not shown).

[0062] As discussed above, the modem relay network 174 can use as few as one digital signal processor to support the transmission of modem data from the modem relay user 180 to an end user at the ISP 182, where the DSP is located at the OGW 20 to support the modulation/demodulation processing of the modem signals.

[0063] Referring now to the dial network 172, a traditional dial user 178 connects to an associated Remote Access Server. This represents the traditional method of terminating modem sessions in which dedicated data networks transport the user's data to the Internet. With modem relay, a voice network can transport the modem session, which is a more efficient use of one network. The MRA reduces the number of DSPs used in the voice network from three to as few as one.

[0064] It should be understood that the MRA 55 can be moved to the edge of the IP transit network 30, as shown. In this case, a voice carrier network provider would be responsible for the MRA 55 instead of an Internet service provider. The decision of where to place the MRA 55 is thus a business decision.

[0065] FIG. 10 is a network diagram in which the MRA 55 is employed in a personal computer (PC) 184 or other general computing device that is capable of providing host-based functionality. The MRA 55, in this particular embodiment, may be implemented entirely in software, executed by a general purpose processor (not shown) in the PC 184. The network to which the PC 184 is connected may be as discussed above in reference to the modem relay network 174 (FIG. 9) or dial network 172.

[0066] Alternatively, the MRA 55 may be implemented in hardware or firmware in a plug-in card installed in the PC 184 or may be some combination of software executable by a general purpose processor, custom processor, or plug-in card solution. The software may be stored locally in the memory unit(s) 68 (FIG. 4), which may include RAM, ROM, CD-ROM, magnetic or optical disk, etc., or may be stored remotely and downloaded via network communications.

[0067] FIG. 11 is a schematic diagram of the computer system 184 that includes a central processing module 186, a memory system 188 and a Peripheral Component Interconnect (PCI) chip set 190 connected by a processor bus 192. The PCI chip set 190 is further connected to an I/O system 194 and a co-processor module 196 by a system bus 198. The central processing module 186 loads and executes the modem relay aggregator software 62 (FIG. 4) from the memory system 188, where the modem relay aggregator software 62 is host-processor-based in this particular embodiment. The I/O system 194 provides an interface to the IP/ATM network 30.

[0068] While this invention has been particularly shown and described with references to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.

Claims

1. A method for terminating a modem session to transport data across a voice-over-Internet Protocol (VoIP) network using a modem relay (MR) technique, the method provided as host-processor-based software executed on a general purpose computing device, the method comprising: removing encapsulation information from a data packet used to support network transport of the data; acting as a termination point for the session; encapsulating the data in an Internet Protocol (IP) packet with a destination address of an IP device; and delivering the IP packet to the computer network for delivery to the IP device.

2. The method according to claim 1 wherein the data is modem data.

3. The method according to claim 1 wherein the data link protocol is a point-to-point protocol (PPP).

4. The method according to claim 1 further including decompressing the data after removing the encapsulation.

5. The method according to claim 1 including receiving the data from a gateway across an IP packet transport network.

6. The method according to claim 1 further including receiving the data from a gateway across a local area network.

7. The method according to claim 1 further including receiving the data packet from a first computer network and wherein delivering the IP packet to the IP device causes the IP packet to travel across a second computer network.

8. The method according to claim 1 absent supporting physical layer protocol processing.

9. The method according to claim 8 wherein physical layer protocol processing includes error detection and error correction processing.

10. An apparatus for transporting data across a voice-over-Internet Protocol (VoIP) network using a modem relay (MR) technique, the apparatus provided as host-processor-based software executed on a general purpose computing device, the apparatus comprising: a filter to remove encapsulation information from a data packet used to support network transport of the data; a termination unit coupled to the filter to receive the data and to act as a termination point for the data link protocol; an encapsulation unit coupled to the termination unit to encapsulate the data in an Internet Protocol (IP) packet with a destination address of an IP device; and a transmit unit coupled to the encapsulation unit to deliver the new IP packet to the data network for delivery to the IP device.

11. The apparatus according to claim 10 wherein the data is modem data.

12. The apparatus according to claim 10 wherein the data link protocol is a point-to-point protocol (PPP).

13. The apparatus according to claim 10 further including a decompression unit coupled to the filter to decompress the data after the encapsulation is removed.

14. The apparatus according to claim 10 further including a receiver to receive the packetized data from a gateway across an IP packet transport network.

15. The apparatus according to claim 10 further including a receiver to receive the packetized data from a gateway across a local area network.

16. The apparatus according to claim 10 further including a receiver to receive the data packet from a first computer network and wherein the transmit unit delivers the IP packet to a second data network.

17. The apparatus according to claim 10 absent a signal processor to support physical layer protocol processing.

18. The apparatus according to claim 17 wherein the physical layer protocol processing includes error detection and error correction processing.

19. An apparatus for terminating a modem session to transport data across a voiceover-Internet Protocol (VoIP) network using a modem relay (MR) technique, the apparatus provided as host-processor-based software executed on a general purpose computing device, the apparatus comprising: means for removing encapsulation information from a data packet used to support network transport of the data; means for acting as a termination point for the session; means for encapsulating the data in an Internet Protocol (IP) packet with a destination address of an IP device; and means for delivering the new IP packet to the computer network.

20. A general purpose computing device executing host-processor-based software for terminating a modem session to transport data across a voice-over-Internet Protocol (VoIP) network using a modem relay (MR) technique, the computing device comprising: an interface coupled to the network to receive data encapsulated with information used to support network transport of the data; a memory unit storing software to operate on the received encapsulated data; and a processor coupled to the interface and the memory unit, the processor loading the software and executing the software to: remove the encapsulation information; act as a termination point for the session; encapsulate the data in an Internet Protocol (IP) packet with a destination address of an IP device; and deliver the new IP packet to the computer network for delivery to the IP device.

21. A computer-readable medium having stored thereon sequences of instructions for host-processor based software executed on a general purpose computing device, the sequences of instructions, when executed by a digital processor, causes the processor to: remove encapsulation information used to support network transport of data transported across a network in a session using a data link protocol designed for transporting data over circuit switched networks; act as a termination point for the session; encapsulate the data in an Internet Protocol (IP) packet with a destination address of an IP device; and deliver the new IP packet to the computer network for delivery to the IP device.

22. A method for providing dial-out service for an end node requesting a session, the session using a data link protocol designed to transport data across a voice-over-Internet Protocol (VoIP) network using a modem relay (MR) technique, the method provided as host-processor-based software executed on a general purpose computing device, the method comprising: receiving a request and a destination phone number from the end node; retrieving network route information associated with the destination phone number; establishing a voice call with a terminating gateway, the terminating gateway establishing a circuit switched call to a node at the destination phone number; and sending data received from the end node to the terminating gateway in the session.

23. The method according to claim 22 wherein the data is modem data.

24. The method according to claim 22 wherein the session is a point-to-point protocol session.

25. The method according to claim 22 further including compressing the data and encapsulating it for sending to the terminating gateway.

26. An apparatus for providing dial-out service for an end node requesting a session, the session using a data link protocol designed to transport data across a voiceover-Internet Protocol (VoIP) network using a modem relay (MR) technique, the apparatus provided as host-processor-based software executed on a general purpose computing device, the apparatus comprising: an interface to receive a request and destination phone number from the end node; and a processor coupled to the interface to retrieve network route information associated with the destination phone number and to establish the session with a terminating gateway.

27. The apparatus according to claim 26 wherein the data is modem data.

28. The apparatus according to claim 26 wherein the session is a point-to-point protocol session.

29. The apparatus according to claim 26 wherein the processor includes a compression unit to compress the data and an encapsulation unit to encapsulate the compressed data for sending it to the terminating gateway.

30. An apparatus for providing dial-out service for an end node requesting a session, the session using a data link protocol designed to transport data across a voice-over-Internet Protocol (VoIP) network using a modem relay (MR) technique, the apparatus provided as host-processor-based software executed on a general purpose computing device, the apparatus comprising: means for receiving a request and a destination phone number from the end node; means for retrieving network route information associated with the destination phone number; means for establishing the session with a terminating gateway, the terminating gateway establishing a circuit switched call to a node at the destination phone number; and means for sending data received from the end node to the terminating gateway in the session.

31. A general purpose computing device executing host-processor-based software for providing dial-out service for an end node requesting a session, the session using a data link protocol designed to transport data across a voice-over-Internet Protocol (VoIP) network using a modem relay (MR) technique, the computing device comprising: an interface coupled to the network to receive a request and a destination phone number from the end node; a memory unit storing software to assist in transporting the packetized data; and a processor coupled to the interface and the memory unit, the processor loading the software and executing the software to: receive a request and a destination phone number from the end node; retrieve network route information associated with the destination phone number; establish the session with a terminating gateway, the terminating gateway establishing a circuit switched call to a node at the destination phone number; and send data received from the end node to a terminating gateway in the session.

32. A computer-readable medium having stored thereon sequences of instructions for host-processor-based software executed on a general purpose computing device, the sequences of instructions, when executed by a digital processor, causes the processor to: receive a request and a destination phone number from an end node in a computer network; retrieve network route information associated with the destination phone number; establish a session using a data link protocol designed to transport data over circuit switched networks with a terminating gateway, the terminating gateway establishing a circuit switched call to a node at the destination phone number; and send data received from the end node to the terminating gateway in the session.