US20080137648A1 - System and Method for Facilitating Calls Between Packet-Based Networks - Google Patents

System and Method for Facilitating Calls Between Packet-Based Networks Download PDF

Info

Publication number
US20080137648A1
US20080137648A1 US12/024,284 US2428408A US2008137648A1 US 20080137648 A1 US20080137648 A1 US 20080137648A1 US 2428408 A US2428408 A US 2428408A US 2008137648 A1 US2008137648 A1 US 2008137648A1
Authority
US
United States
Prior art keywords
packet
connection information
call
device
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/024,284
Inventor
Robert Paul Lowmaster
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Intellectual Property I LP
Original Assignee
AT&T Intellectual Property I LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US10/668,616 priority Critical patent/US7356023B2/en
Application filed by AT&T Intellectual Property I LP filed Critical AT&T Intellectual Property I LP
Priority to US12/024,284 priority patent/US20080137648A1/en
Assigned to SBC KNOWLEDGE VENTURES, L.P. reassignment SBC KNOWLEDGE VENTURES, L.P. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LOWMASTER, ROBERT PAUL
Publication of US20080137648A1 publication Critical patent/US20080137648A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Interconnection arrangements between switching centres
    • H04M7/0024Services and arrangements where telephone services are combined with data services
    • H04M7/0057Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/02Communication control; Communication processing contains provisionally no documents
    • H04L29/06Communication control; Communication processing contains provisionally no documents characterised by a protocol
    • H04L29/0602Protocols characterised by their application
    • H04L29/06027Protocols for multimedia communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1013Network architectures, gateways, control or user entities
    • H04L65/1043MGC, MGCP or Megaco
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/10Signalling, control or architecture
    • H04L65/1066Session control
    • H04L65/1069Setup

Abstract

A method of facilitating calls includes receiving a message at a mediation server from a first device associated with a first packet-based network, the message relating to a second device associated with a second packet-based network. The method also includes identifying first connection information relating to the first device, where the first connection information includes a set of call receipt rules that relates to a format of packet-based data that is acceptable to the first device. The method also includes sending, in response to the message, second connection information related to the second device from the mediation server to the first device.

Description

    CLAIM OF PRIORITY
  • The present application is a continuation of and claims priority from U.S. patent application Ser. No. 10/668,616 filed on Sep. 23, 2003, the contents of which is expressly incorporated herein by reference in its entirety.
  • FIELD OF THE DISCLOSURE
  • The present disclosure relates to internetwork management, and more particularly to a system and method for facilitating calls between packet-based networks.
  • BACKGROUND OF THE DISCLOSURE
  • A network is made up of a series of nodes interconnected by communication paths. Networks often interconnect with computing devices of differing types and with other networks of various sizes. An enterprise network, for example, may interconnect with several local area networks (LANs) and one or more metropolitan area networks (MANs) or wide area networks (WANs).
  • In practice, many large networks with broad geographic coverage, like the Internet, are made by connecting some of the nodes on one network with nodes of another network. This intermingling of network assets actually helps create the broader network. Occasionally, some of the intermingled assets are part of a managed network as opposed to the public Internet.
  • A given network may be characterized by several factors like who can use the network, the type of traffic the network carries, the typical nature of the network's connections, and the transmission technology the network uses. For example, one network may be public and carry circuit switched voice traffic while another may be private and carry packet switched data traffic. Whatever the make-up, most networks facilitate the communication of information between at least two nodes, and as such act as communications networks.
  • A difficulty may arise, however, when users on one network attempt to communicate with a user on another network. Communication across the boundaries of the two networks may create challenges. For example, while one managed network operator may be able to offer packetized voice services between users on its network, the same operator may find it more difficult to allow internetwork voice calls. Often these calls are actually carried on a circuit switched telephone network, which, in many cases, requires the calls to be translated from a packetized format like voice over internet protocol (VoIP) to a time division multiplexed (TDM) format.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The present invention presents a technique for facilitating internetwork and intranetwork packetized calls and is pointed out with particularity in the appended claims. However, features are described in the following detailed description in conjunction with the accompanying drawings in which:
  • FIG. 1 shows a block diagram of a call facilitation system that incorporates teachings of the present disclosure; and
  • FIG. 2 depicts a simplified flow chart for a call facilitation method that incorporates teachings of the present disclosure.
  • DETAILED DESCRIPTION OF THE DRAWINGS
  • Vendors and carriers may begin to deploy or provide a packetized voice over internet protocol (VoIP) service on managed internet protocol (IP) networks. These managed networks may appear as communication islands and may permit IP data calls and VoIP calls to be delivered between electronic devices that may reside on or be associated with a particular managed network. To make an internetwork call, a user may need to know a great deal of information about the called device and the network associated with the called device.
  • Even if a calling party knows the connection information for the called device, the actual call and its quality may be adversely affected by some call manipulation occurring during the call. For example, a VoIP call may be converted into a time division multiplexing (TDM) format at the interface of the calling party's managed network and the public switched telephone network (PSTN). The TDM formatted call may be delivered to the called party's managed network via the PSTN, where it may be converted back into a VoIP format. This dual conversion process may be inefficient and may cause call quality degradation.
  • The present disclosure presents a system and method for facilitating packetized calls between managed networks. As mentioned above in the brief description of the drawings, FIG. 1 shows a block diagram of a call facilitation system 10 that incorporates teachings of the present disclosure. System 10 includes an independent connection manager (ICM 12) operating in a service bureau mode. As depicted, ICM 12 may be logically separated from the various networks it supports. In practice, ICM 12 may be physically located within one of the supported networks while maintaining a logical separation from the networks.
  • In the embodiment of FIG. 1, ICM 12 may include several different components performing functions that facilitate voice over internet protocol (VoIP) calls between disparate managed networks. The various components of ICM 12 may be implemented in forms that include hardware, software, firmware, combinations thereof, or other.
  • In the depicted embodiment, ICM 12 may include a mediation server 14, which may be communicatively coupled with and maintaining an information store 16. Information store 16 may be holding connection information for a collection of devices 18 associated with a managed internet protocol network 20 and additional connection information for other devices like telephone 30 associated with a different managed internet protocol network 22. Devices included in collection 18 may include computers like laptop 24, wireless telephones like cell phone 26, wireline telephones like telephone 28, or some other electronic device capable of receiving voice over internet protocol calls.
  • With voice calls and or data calls, the network and device types may affect how call information is communicated. Similarly, the connection or link type may impact delivery of call-related information. For example, a user may make a call from telephone 28 to telephone 30 across Public Switched Telephone Network 32. PSTN 32 may be made up of competitive local exchange carriers (CLECs), incumbent local exchange carriers (ILECs), which may be regional Bell operating companies (RBOCs), an interexchange carrier (IXC), or combinations thereof. In some cases, the entire call may be a plain old telephony service (POTS) call. As such, link 34 may communicatively connect telephone 28 to PSTN 32 across a twisted pair connection and some appropriate backhaul to a central office. Similarly, link 36 may communicatively connect telephone 30 to PSTN 32 across a twisted pair connection and some appropriate backhaul to a central office.
  • In some circumstances, a user may want to make a VoIP call from telephone 28 to telephone 30. During such a call, telephone 28 may send a signal representing the VoIP call to managed network 20. Managed network 20 may recognize that telephone 28 is attempting to call telephone 30. Managed network 20 may determine that telephone 30 is not connected to managed network 20 and may “ask” ICM 12 how to connect to telephone 30. Mediation server 14 of ICM 12 may determine that telephone 30 is associated with managed network 22. Mediation server 14 may direct the retrieval of appropriate connection information from an information store like information store 16 and communicate the connection information back to managed network 20.
  • Managed network 20 may then manipulate and route the packets of telephone 28's VoIP call in accordance with the connection information received from ICM 12. In some cases, managed network 20 may decide against continuing with the routing of the call as an IP routed call. Managed network 20 may instead route the call through a Media Gateway to PSTN 32. This may occur, for example, when managed network 20 determines that it cannot conform the call to the specifications received from ICM 12.
  • In one IP completed embodiment, the VoIP call may be routed through public Internet 38 to managed network 22 and onto telephone 30, effectively using public Internet 38 as the path for interconnecting the two managed IP networks. In another embodiment, a peering arrangement between the two managed IP networks may be established, allowing for direct or near-direct handoff between the managed networks 20 and 22. In preferred embodiments, ICM 12 may provide appropriate connection information to various managed networks and avoid being a point of interconnection for call signaling and/or bearer traffic.
  • As mentioned above, at least a portion of the call may be made across a network like public Internet 38. The call connection may involve the communication of a TCP/IP packet or some other packet or frame and may be pure data communication, pure voice communication, or a combination data and voice communication. The voice portion of a combined call may involve the creation of a derived voice channel, a VoIP call, an instant messenger (IM) connection, some other technique, or a combination thereof.
  • As depicted in FIG. 1, a user may initiate and/or receive a call with cell phone 26. Using cell phone 26 may involve communicating via a wireless network component 40, a portion of managed network 20, PSTN 32, public Internet 38, and/or combinations thereof. A wireless link type may depend on the electronic components associated with a given wireless access device and other wireless networking components like cellular towers or wireless local area network (LAN) hubs, like 802.11 hub 42.
  • The wireless access device, cellular tower and/or wireless hub (Wireless Enabled Devices) may include any of several different components. For example, a Wireless Enabled Device may have a wireless wide area transceiver, which may be part of a multi-device platform for communicating data using radio frequency (RF) technology across a large geographic area. This platform may be a GPRS, EDGE, or 3GSM platform, for example, and may include multiple integrated circuit (IC) devices or a single IC device.
  • A Wireless Enabled Device may also have a wireless local area transceiver, which may communicate using spread-spectrum radio waves in a 2.4 GHz range, 5 GHz range, or other suitable range. The wireless local area transceiver may be part of a multi-device or single device platform and may facilitate communication of data using low-power RF technology across a small geographic area. For example, if the wireless local area transceiver includes a Bluetooth transceiver, the transceiver may have a communication range with an approximate radius of one hundred feet. If the wireless local area transceiver includes an 802.11 (x) transceiver, such as an 802.11(a)(b) or (g), the transceiver may have a communication range with an approximate radius of one thousand feet.
  • As mentioned above, whatever the device and/or network type, the connection information for a given device and/or network may include a unique address and a call receipt rule. The unique address may take the form of a Media Access Control (MAC) address and/or an IP address, like an IPv6 address, or some other unique identifier. In some embodiments, a MAC address may identify a unique hardware number associated with a given electronic device. In some embodiments, a mapping engine like mapping engine 44 may maintain a correspondence table capable of relating an IP address to a MAC address. Preferably, a MAC address could be used by the Media Access Control sublayer of the Data-Link Layer (DLC) to help identify a physical device type, as there may be a different MAC sublayer for each physical device type.
  • Whatever the format of the unique address, a system like system 10 may employ static addresses, dynamic addresses, or combinations thereof. In addition, the uniqueness of an address may describe true uniqueness—in that a given device is the only device with that address or effective uniqueness. An effectively unique address may not be truly unique but may provide sufficient uniqueness to identify a given device.
  • As mentioned above, connection information may also include at least one receipt rule. A receipt rule may provide information relevant to the capabilities and preferences of a given device and/or network. For example, a receipt rule may include an IP header rule defining, for example, appropriate header sizes. A receipt rule may include a real time transport protocol/real time control protocol (RTP/RTCP) rule defining, for example, how a device constructs and/or reconstructs data and how codec bit streams are packetized. A receipt rule may include an allowable sample size rule defining, for example, appropriate sizes as 10, 20, or 30 milliseconds. A receipt rule may include a network access rule defining, for example, that a called network should be accessed via the public Internet and what addresses should be used for specific telephone numbers found on the mediation server. For example, in some embodiments, mapping engine 44 may maintain a table that links dialed telephone numbers to a unique address of a VoIP-capable device. A receipt rule may also include a supported coding protocol rule defining, for example, that the called network supports a G.711 or other protocol.
  • In operation, mediation server 14 may receive a query from managed network 22 seeking appropriate connection information for a called device associated with managed network 20. In one embodiment, mediation server 14 may collect the appropriate connection information from information store 16 and initiate communication of the appropriate connection information with communication engine 46 to an address associated with the received query. For example, the query may have a header that includes an indication of who or what device is making the request. Communication engine 46 may consider the information contained in the header when determining where to send the appropriate connection information.
  • In some embodiments, mediation server 14 may have a zoned information store including a first collection of connection information for a first plurality of callable devices associated with managed network 20 and a second collection of connection information for a second plurality of callable devices associated with managed network 22. As depicted in FIG. 1, the first collection may be located in information store 16 and the second collection may be located in information store 48. Though depicted as separate hardware components, zoning may be accomplished in software as well.
  • By zoning the information store, ICM 12 may allow a managed network or its administrator to access and modify the connection information maintained in the information store. For example, an administrator of managed network 20 may need to modify the connection information maintained in information store 16 for telephone 28. To allow for such modifications, ICM 12 may include a network interface engine like interface engine 50. Interface engine 50 may be communicatively coupled to mediation server 14 and may be capable of receiving a query seeking appropriate connection information or modifying connection information for a given device. In preferred embodiments, interface engine 50 may be designed such that it does not act as a point of interconnection for either signaling or bearer traffic between managed network 20 and managed network 22.
  • In light of the potential authority granted to a remotely located administrator, a system incorporating teachings of the present disclosure may elect to use some rights management technique. For example, a system like system 10 may employ a security engine 52, which may be made up of an authentication engine and an authorization engine. In practice, the authentication engine may be communicatively coupled to interface engine 50. The authentication engine may be able to compare an initial set of credentials received from the calling party against a maintained set of credentials. The credentials may include, for example, a user name and password combination. If the received credentials match the maintained credentials, the authorization engine may grant access to information store 16. In preferred embodiments, security engine 52 may recognize that the authorized administrator is administering managed network 20 and, as such, only grant the administrator access to information store 16—holding back from the administrator edit rights to the information in information store 48. Altering information in ICM 12 may also be accomplished locally. For example, ICM 12 may include a management console 54 from which a local administrator may manage ICM 12, mediation server 14, information stores 16 and 48, and/or all of these components.
  • In operation, mediation server 14 may also include a find and retrieval engine (FRE) 56. FRE 56 may be communicatively coupled to interface engine 50 and capable of determining if a called device is associated with managed network 20 or managed network 22. Making such a determination may “tell” FRE 56 which zone of the information store holds the appropriate connection information. In practice, FRE 56 may be associated with mediation server 14 and may be capable of directing collection of the appropriate connection information from information store 16.
  • Operation of a system like system 10 may be better understood in connection with a description of FIG. 2. As mentioned above, FIG. 2 depicts a simplified flow chart for a call facilitation method that incorporates teachings of the present disclosure. Routine 58 of FIG. 2 may start at step 60, at which point a managed network may receive a signal indicating a request for a call to a party associated with a telephone like telephone 30 of FIG. 1. The call may be deliverable as a voice over internet protocol call. As such, at step 62, the managed network may present the calling party with call options including call completion as a VoIP call or a POTS call. If the user selects POTS call completion, routine 58 may progress to step 64 and the call may be routed as a POTS call. If the call came in as a VoIP call, step 64 may involve sending the call to a media gateway, where the call may be converted to a TDM call.
  • If the user selects VoIP call completion, routine 58 may progress to step 66, where the managed network receiving the initial call request may determine whether or not the called device is part of its managed network. If the called device is on the same managed network as the calling device, routine 58 may progress to step 68 where the call is completed across the one managed network.
  • If the called device is not on the same managed network as the calling device, routine 58 may progress to step 70 where a query is sent to an information store maintained at an ICM like ICM 12 of FIG. 1. The query may effectively “ask” the ICM if the ICM “knows” how to connect to the called device. The called device may be identified by a telephone number or some other identifier, and the original managed network may need to have that telephone number converted into a unique IP and/or MAC address. The original managed network may also need to know what receipt rules, if any, exist for the called device and/or network associated with the called device.
  • At step 72, the ICM may determine whether it “knows” and/or can “find” an entry for the called device. In some embodiments, an ICM may zone its information stores to isolate the connection information of one managed network from the connection information of another managed network. In such an embodiment, step 72 may include determining which collection of connection information includes the appropriate connection information for the called device.
  • If the ICM cannot find the called device at 72, this condition may be reported back to the original managed network and routine 58 may progress to step 64 where the call is routed at least partially as a POTS call. If the ICM can find the called device, routine 58 may progress to step 74 where the ICM initiates retrieval of appropriate connection information for the called device. At step 76, the ICM may initiate communication of the appropriate connection information to the original managed network.
  • At step 78, the original managed network may manipulate and route packets of the VoIP call in accordance with the connection information received from the ICM. In one embodiment, the VoIP call may be routed through the public Internet to a different managed network and onto the called device. In preferred embodiments, the ICM may provide appropriate connection information to various managed networks and avoid being a point of interconnection for call signaling and/or bearer traffic.
  • As mentioned above, if the ICM cannot find the called device at step 72, this condition may be reported back to the original managed network and routine 58 may progress to step 64 where the call is routed at least partially as a POTS call. The not known determination may also indicate the need for a modification routine 90. At step 92 of modification routine 90, the ICM may receive a request to modify a collection of connection information. At step 94, the ICM may request and receive credentials from a party or administrator making the request. At step 96, the credentials may be compared against a maintained list of credentials and the party may be allowed editing access to an information store holding the to-be-changed connection information. If the credentials are not accepted, modification routine 90 may progress to step 98, where the routine stops.
  • If the credentials are accepted, modification routine may progress to step 100 where the party is granted editing access to an information store or a specific zone of the information store and the party modifies the appropriate connection information. In some embodiments, the information stores may be zoned such that allowing the party access to a first collection of connection information does not automatically allow the party access to all of the connection information maintained at the ICM. The party may then exit from the ICM system and modification routine 90 may progress to a stop at step 98.
  • The various managed networks may use the connection information provided by an ICM in several different ways. The information may simply be used to format and route information packets to their intended destination. In some embodiments, a system incorporating teachings of the present disclosure may be able to adapt information exchange to a given device, to a user preference, and/or network state or other condition. A managed network may include a format converter that can translate in accordance with the appropriate connection information at least a portion of a VoIP or data call into a signal and/or signal type receivable by a called device on a different managed network. There may be several mark-up languages and techniques employed in a system like system 10 to facilitate this and other capabilities. For example, a designer of system 10 may elect to use XHTML, SMIL or some other mark-up language in conjunction with a speech recognition engine. Other designers may elect to use VoiceXML, HTML, Voice Browser, Xforms, and/or others.
  • In preferred embodiments, a format converter, which may be a stand alone engine or an asset incorporated into another engine, may be capable of translating at least a portion of a first signal representing a call into a second signal that also represents the call, the second signal receivable by the called device and network.
  • In practice, the information communicated across the various links of FIG. 1 may be compressed and/or encrypted prior to communication. At least a portion of the communication may be via a circuit-switched network like most wireline telephony networks, a frame-based network like Fibre Channel, or a packet-switched network that may communicate using TCP/IP packets like public Internet 38 of FIG. 1. The physical medium making up at least a portion of the links may be coaxial cable, fiber, twisted pair, an air interface, other, or combination thereof. In some embodiments, at least one of the links may be a broadband connection facilitated by an xDSL modem, a cable modem, an 802.11x device, some other broadband wireless linking device, or combination thereof.
  • In some embodiments, various pieces of information in addition to or in lieu of voice call information may be communication in a format that facilitates display on a graphical user interface. The information may be sent as a file for download and play, as streaming content, as some other format, or some combination thereof. The information may include audio information, textual information, video information, some other type of information, or a combination thereof. As such, in some systems incorporating teachings of the present disclosure, an information store may include connection information that includes, among other things, information describing display capabilities and additional address information for different devices capable of receiving additional information.
  • If, for example, a called party is hearing impaired and employs a piece of customer premises equipment (CPE) capable of presenting a transcript of the verbal communication occurring, an information store may maintain connection information indicating the existence of that piece of CPE. In other embodiments, a piece of CPE may support packetized or POTS voice traffic while also supporting data traffic. The system may inform a calling party of this capability and facilitate the called party's receipt of audible information as voice traffic and graphical information as data traffic. As such, a system incorporating teachings of the present disclosure may “know” to convert a telephony portion of a call to audible information and a data portion of the call to graphical information.
  • Many of the above techniques may be provided by a computing device executing one or more software applications or engines. The software may be executing on a single computing platform or more than one. The platforms may be highly capable workstations, personal computers, microprocessors, servers, or other devices capable of performing the techniques. The platforms may execute commands maintained in a computer-readable medium. In one embodiment of an ICM, platform or collection of platforms may be executing commands described in computer-readable data to maintain an information store comprising a first collection of connection information for a first plurality of devices associated with a first managed internet protocol network and a second collection of connection information for a second plurality of devices associated with a second managed internet protocol network, to receive a query seeking appropriate connection information for a called device associated with the first managed internet protocol network; to collect the appropriate connection information from the first collection of connection information, and to initiate communication of the appropriate connection information to an address associated with the query.
  • It will be apparent to those skilled in the art that the disclosed embodiments may be modified in numerous ways and may assume many embodiments other than the particular forms specifically set out and described herein. For example, embodiments may be employed with voice networks, data networks, other communications networks, or combinations thereof.
  • Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims (20)

1. A method of facilitating calls, the method comprising:
receiving, at a mediation server, a message addressed to a first device associated with a first packet-based network, the message sent from a second device associated with a second packet-based network;
identifying first connection information relating to the first device, the first connection information including a set of call receipt rules related to a format of packet-based network data that is acceptable to the first device; and
sending, in response to the message, the first connection information from the mediation server to the second device.
2. The method of claim 1, further comprising storing, at the mediation server, the first connection information and second connection information, the first connection information including a unique address for each of a first plurality of devices associated with the first packet-based network and a first set of call receipt rules relating to calls to the first plurality of devices, and the second connection information including a unique address for each of a second plurality of devices associated with the second packet-based network and a second set of call receipt rules relating to calls to the second plurality of devices.
3. The method of claim 2, wherein the mediation server does not provide call signaling information or call data to the first plurality of devices, the second plurality of devices, or any combination thereof.
4. The method of claim 2, wherein the first call receipt rules include a packet-based header rule, an allowable sample size ratio, a network access rule, a real time transport protocol/real time control protocol (RTP/RTCP) rule, or any combination thereof.
5. The method of claim 1, further comprising:
receiving a request to modify the first connection information at the mediation server from a particular device associated with the first packet-based network;
receiving credentials at the mediation server from the particular device associated with the first packet-based network; and
modifying the first connection information according to commands received at the mediation server from the particular device associated with the first packet-based network.
6. The method of claim 5, wherein the credentials received at the mediation server from the particular device associated with the first packet-based network allow access to modify the first connection information, but do not allow access to modify the second connection information.
7. The method of claim 1, wherein the first connection information is stored at a first information store associated with the mediation server and second connection information is stored at a second information store associated with the mediation server.
8. A method of facilitating calls, the method comprising:
receiving, at a first device associated with a first packet-based network, a request to place a call to a second device associated with a second packet-based network;
identifying connection information relating to the second device, the connection information including a set of call receipt rules that relate to a format of packet-based data that is acceptable to the second device;
converting, at the first device, packet-based data associated with the call to the format of packet-based data that is acceptable to the second device; and
sending the converted packet-based data to the second device.
9. The method of claim 8, wherein the first device provides a calling party with an option to complete the call as a voice over Internet Protocol (VoIP) call or as a circuit switched call.
10. The method of claim 8, further comprising:
routing the call to a media gateway accessible to a public switched telephone network (PSTN) in response to receiving a selection from the calling party indicating the option to place the call as a circuit switched call; and
converting the packet-based data associated with the call at the first device in response to receiving a selection indicating the option to place the call as a VoIP call.
11. A system to facilitate calls, the system comprising:
a processor; and
a memory accessible to the processor, the memory including network interface logic executable by the processor to:
receive a message directed to a first device associated with a first packet-based network, the message sent from a second device associated with a second packet-based network; and
send first connection information to the second device, the first connection information including a format of packet-based data that is acceptable to the first device.
12. The system of claim 11, wherein the memory further comprises a communication engine executable by the processor to send the first connection information to the second device after receiving the message.
13. The system of claim 11, further comprising a network interface to communicate with the first packet-based network via a first private network and communicates with the second packet-based network via a second private network.
14. The system of claim 11, wherein the memory includes a find and retrieval engine executable by the processor to identify and retrieve the first connection information from an information store.
15. The system of claim 11, wherein the memory includes a mapping engine executable by the processor to link the unique packet-based addresses associated with telephony devices of the first packet-based network and the unique packet-based addresses associated with telephony devices of the second packet-based network with respective telephone numbers.
16. The system of claim 11, wherein the memory includes an authentication engine executable by the processor to compare a set of credentials received from a particular device associated with the first packet-based network with a maintained set of credentials stored at an information store.
17. The system of claim 16, wherein the memory includes an authorization engine executable by the processor to grant access to the information store when the received set of credentials matches the maintained set of credentials.
18. The system of claim 17, wherein the access to the information store includes editing of the first connection information.
19. A computer-readable medium, comprising:
operational instructions, that when executed by a processor, cause the processor to receive a message addressed to a first device associated with a first packet-based network, the message sent from a second device associated with a second packet-based network; and
operational instructions, that when executed by the processor, cause the processor to send first connection information to the second device, the first connection information related to the first device.
20. The computer readable medium of claim 19, further comprising operational instructions, that when executed by the processor, cause the processor to retrieve, at a mediation server, the first connection information and second connection information, the first connection information including a unique address for each of a first plurality of devices associated with the first packet-based network and a first set of call receipt rules relating to calls to the first plurality of devices, and the second connection information including a unique address for each of a second plurality of devices associated with the second packet-based network and a second set of call receipt rules relating to calls to the second plurality of devices, wherein the first set of call receipt rules relates to a first format of packet-based data that is acceptable to the first plurality of devices, and wherein the second set of call receipt rules relates to a second format of packet-based data that is acceptable to the second plurality of devices.
US12/024,284 2003-09-23 2008-02-01 System and Method for Facilitating Calls Between Packet-Based Networks Abandoned US20080137648A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10/668,616 US7356023B2 (en) 2003-09-23 2003-09-23 System and method for facilitating packetized calls between managed networks
US12/024,284 US20080137648A1 (en) 2003-09-23 2008-02-01 System and Method for Facilitating Calls Between Packet-Based Networks

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12/024,284 US20080137648A1 (en) 2003-09-23 2008-02-01 System and Method for Facilitating Calls Between Packet-Based Networks

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/668,616 Continuation US7356023B2 (en) 2003-09-23 2003-09-23 System and method for facilitating packetized calls between managed networks

Publications (1)

Publication Number Publication Date
US20080137648A1 true US20080137648A1 (en) 2008-06-12

Family

ID=34313523

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/668,616 Expired - Fee Related US7356023B2 (en) 2003-09-23 2003-09-23 System and method for facilitating packetized calls between managed networks
US12/024,284 Abandoned US20080137648A1 (en) 2003-09-23 2008-02-01 System and Method for Facilitating Calls Between Packet-Based Networks

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/668,616 Expired - Fee Related US7356023B2 (en) 2003-09-23 2003-09-23 System and method for facilitating packetized calls between managed networks

Country Status (3)

Country Link
US (2) US7356023B2 (en)
DE (1) DE112004001523T5 (en)
WO (1) WO2005033837A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070183423A1 (en) * 2006-02-03 2007-08-09 Radioframe Networks, Inc. Transporting call data via a packet data network

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6484027B1 (en) * 1998-06-15 2002-11-19 Sbc Technology Resources, Inc. Enhanced wireless handset, including direct handset-to-handset communication mode
US20040266425A1 (en) * 2003-06-24 2004-12-30 Sbc, Inc. Wireless wide area network charger and cradle
US7616950B2 (en) * 2003-09-04 2009-11-10 At&T Intellectual Property I, L.P. Call forwarding control device and method of call management
US20050064853A1 (en) * 2003-09-23 2005-03-24 Sbc Knowledge Ventures, L.P. Unified telephone handset for personal communications based on wireline and wireless network convergence
US7769392B2 (en) * 2003-09-23 2010-08-03 At&T Intellectual Property I, L.P. Method and system for forwarding wireless communications
US8526977B2 (en) * 2003-09-23 2013-09-03 At&T Intellectual Property I, L.P. Location based call routing for call answering services
US7577427B2 (en) * 2003-11-05 2009-08-18 At&T Intellectual Property I, L.P. System and method of transitioning between cellular and voice over internet protocol communication
US7483392B1 (en) * 2004-03-19 2009-01-27 Bbn Technologies Corp. Multinode arrangement
US20050277431A1 (en) * 2004-06-14 2005-12-15 Sbc Knowledge Ventures, Lp System and method for managing wireless data communications
US20060003806A1 (en) * 2004-07-02 2006-01-05 Sbc Knowledge Ventures, L.P. Phone synchronization device and method of handling personal information
US7580837B2 (en) 2004-08-12 2009-08-25 At&T Intellectual Property I, L.P. System and method for targeted tuning module of a speech recognition system
US7242751B2 (en) 2004-12-06 2007-07-10 Sbc Knowledge Ventures, L.P. System and method for speech recognition-enabled automatic call routing
US7751551B2 (en) 2005-01-10 2010-07-06 At&T Intellectual Property I, L.P. System and method for speech-enabled call routing
US8005204B2 (en) * 2005-06-03 2011-08-23 At&T Intellectual Property I, L.P. Call routing system and method of using the same
US7657020B2 (en) 2005-06-03 2010-02-02 At&T Intellectual Property I, Lp Call routing system and method of using the same
US20090003582A1 (en) * 2007-06-27 2009-01-01 Microsoft Corporation Optimized Replacement of Calls Using A Grid Parameter
JP5116398B2 (en) * 2007-08-06 2013-01-09 京セラ株式会社 Communication device, wireless communication apparatus and communication control method
US8340079B2 (en) 2007-09-28 2012-12-25 Centurylink Intellectual Property Llc Method and apparatus for selecting a network for telecommunication
US8559415B2 (en) * 2007-09-28 2013-10-15 Centurylink Intellectual Property Llc Method and apparatus for facilitating telecommunication network selection
US8818365B1 (en) * 2007-10-02 2014-08-26 Sprint Spectrum L.P. User-invoked re-routing of an incoming call via a stronger serving system
US8218745B2 (en) * 2008-04-29 2012-07-10 Embarq Holdings Company, Llc Method for selection and routing of an outbound voice call to an appropriate network for completion
US8180045B2 (en) * 2008-04-29 2012-05-15 Embarq Holdings Company, Llc Method for selection and routing of an inbound voice call to an appropriate network for completion
US20160248817A1 (en) * 2015-02-20 2016-08-25 Vonage Network, Llc Systems and methods for setting up a telephony communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6278697B1 (en) * 1997-07-29 2001-08-21 Nortel Networks Limited Method and apparatus for processing multi-protocol communications
US20040180646A1 (en) * 2003-03-10 2004-09-16 Donley Christopher J. Authentication mechanism for telephony devices
US6798767B1 (en) * 1999-11-16 2004-09-28 Cisco Technology, Inc. System and method for generating multiple line appearances in a communication network

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6069890A (en) * 1996-06-26 2000-05-30 Bell Atlantic Network Services, Inc. Internet telephone service
US6754181B1 (en) * 1996-11-18 2004-06-22 Mci Communications Corporation System and method for a directory service supporting a hybrid communication system architecture
US6064653A (en) * 1997-01-07 2000-05-16 Bell Atlantic Network Services, Inc. Internetwork gateway to gateway alternative communication
US6870827B1 (en) * 1997-03-19 2005-03-22 Verizon Services Corp. Voice call alternative routing through PSTN and internet networks
US6597686B1 (en) * 1997-04-22 2003-07-22 Telcordia Technologies, Inc. Apparatus and method for internet telephony routing
EP1021757A1 (en) * 1997-07-25 2000-07-26 Starvox, Inc. Apparatus and method for integrated voice gateway
US6829236B1 (en) * 1997-12-10 2004-12-07 Mci Communications Corporation System and method for providing automated directory assistance via the internet and corresponding call completion within a telecommunications system
US6275574B1 (en) * 1998-12-22 2001-08-14 Cisco Technology, Inc. Dial plan mapper
WO2000058480A1 (en) * 1999-03-29 2000-10-05 Kansai Technology Licensing Organization Co., Ltd. Novel cytidine deaminase
EP1641193A1 (en) * 1999-05-25 2006-03-29 Lucent Technologies Inc. Method for telecommunications using internet protocol
US7388953B2 (en) * 1999-09-24 2008-06-17 Verizon Business Global Llc Method and system for providing intelligent network control services in IP telephony
US6795429B1 (en) * 1999-09-27 2004-09-21 3Com Corporation System and method for associating notes with a portable information device on a network telephony call
JP3420150B2 (en) * 1999-12-27 2003-06-23 エヌイーシーインフロンティア株式会社 Capable of communicating via the Internet telephone communication device and the main telephone controller
US6870841B1 (en) * 2000-09-18 2005-03-22 At&T Corp. Controlled transmission across packet network
JP2002237907A (en) * 2001-02-09 2002-08-23 Yoji Takeuchi Internet ip telephone communication system enabling voice call between two parties through use of exclusive telephone set over the internet, and exclusive telephone set for internet ip telephone communication system, management method for ip address information used for basic data of internet ip telephone communication function, automatic reception transmission method for reception/transmission between the internet ip telephone communication exclusive set and general telephone, and computer-readable recording medium for recording internet ip telephone communication program
US6697357B2 (en) * 2001-08-10 2004-02-24 Emerson, Iii Harry E. Call management messaging system for integrating the internet with the public switched telephone network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6278697B1 (en) * 1997-07-29 2001-08-21 Nortel Networks Limited Method and apparatus for processing multi-protocol communications
US6798767B1 (en) * 1999-11-16 2004-09-28 Cisco Technology, Inc. System and method for generating multiple line appearances in a communication network
US20040180646A1 (en) * 2003-03-10 2004-09-16 Donley Christopher J. Authentication mechanism for telephony devices

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070183423A1 (en) * 2006-02-03 2007-08-09 Radioframe Networks, Inc. Transporting call data via a packet data network
US8774155B2 (en) * 2006-02-03 2014-07-08 Broadcom Corporation Transporting call data via a packet data network

Also Published As

Publication number Publication date
WO2005033837A3 (en) 2005-06-16
US7356023B2 (en) 2008-04-08
DE112004001523T5 (en) 2006-07-20
US20050063360A1 (en) 2005-03-24
WO2005033837A2 (en) 2005-04-14

Similar Documents

Publication Publication Date Title
US6243398B1 (en) System and method for personal multimedia communication over a packet switched network
JP4913209B2 (en) How to provide emergency access to the wlan to the guest terminal
AU2011201143B2 (en) Caller-callee association of a plurality of networked devices
CN1756280B (en) Telephone network interface bridge between data telephony networks and dedicated connection telephony networks
US7471653B2 (en) Method and system for imposing air interface service level
JP3820151B2 (en) Integrated communication center functions for Wap device
US6667971B1 (en) System and method for enhanced ADSL architecture and service concepts
AU2005232263B2 (en) Method and apparatus for signaling VoIP call based on class of service in VoIP service system
JP3880629B2 (en) Processing apparatus network
US7009984B2 (en) Mechanism for implementing Voice Over IP telephony behind network firewalls
US7092380B1 (en) Method and system for providing voice communication over data networks
US8077689B1 (en) Method and system for establishing VPN connections in response to wireless network identifiers
CA2256728C (en) A telephone doubler arrangement
EP0789470A2 (en) Gateway having connection to voice and data networks
US20140323103A1 (en) Caller-callee association of a plurality of networked devices with direct dial through thin client
CN100525258C (en) Improved calling service of VOIP device in VLAN environment
JP4261033B2 (en) Communication network and method and a communication system for processing a method and a communication connection request for providing secure transmission in it
KR100252120B1 (en) Internet telephone service apparatus and method in ip supported cable network
JP3686337B2 (en) Integrated telephony network that combines the packet data network and a private access network
US7274684B2 (en) Method and system for implementing and managing a multimedia access network device
US7596129B2 (en) Home gateway systems and methods to establish communication sessions
US20060018448A1 (en) Routing telephone calls via a data network
USH2051H1 (en) System and method for providing multiple quality of service classes
US6931011B2 (en) Method and systems for bandwidth management in packet data networks
US7924818B2 (en) Method and apparatus for providing integrated voice and data services over a common interface device

Legal Events

Date Code Title Description
AS Assignment

Owner name: SBC KNOWLEDGE VENTURES, L.P., NEVADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LOWMASTER, ROBERT PAUL;REEL/FRAME:020454/0562

Effective date: 20040205