Method and system for transmitting audio data between computing devices

Information

  • Patent Grant
  • 9088641
  • Patent Number
    9,088,641
  • Date Filed
    Wednesday, January 9, 2008
    16 years ago
  • Date Issued
    Tuesday, July 21, 2015
    8 years ago
Abstract
The present disclosure relates to transmitting data between a plurality of computing devices such as mobile telephones and other electronic communications devices, where a request is associated with placing a call to a contact, and where information associated with the request is stored and a request for a SIP proxy is made, and an IP address associated with the SIP proxy is transmitted to allow redirecting the call to a server via the SIP proxy.
Description
BACKGROUND

Protocols often define ways in which computing devices connect to each other and to a network using Voice over IP (“VoIP”). Session Initiation Protocol (“SIP”) is a popular VoIP protocol that allows a user to communicate with one or more other users via the Internet. SIP cans placed over a broadband Internet connection are often of digital quality and usually provide features, such as voicemail and email, that are not available through traditional telephone calling methods.


Methods of communicating between two or more SIP phones and two or more computers are known in the art. These methods usually involve the flow of real-time transfer protocol (“RTP”) media, such as audio data, between two devices without the use of an intermediary. This communication is possible because both devices are configured to use RTP. However, if this is not possible, service providers may encounter difficulties in establishing communication between two or more devices.


SUMMARY

Before the present methods are described, it is to be understood that this invention is not limited to the particular systems, methodologies or protocols described, as these may vary. It is also to be understood that the terminology used herein is not intended to limit the scope of the present disclosure.


Generally, and in some preferred embodiments, the present disclosure relates to transmitting data between a plurality of computing devices, such as mobile telephones and other electronic communications devices, where a request is associated with placing a call to a contact, and where information associated with the request is stored and a request for a SIP proxy is made, and an IP address associated with the SIP proxy is transmitted to allow redirecting the call to a server via the SIP proxy.


Accordingly, one embodiment of the present invention is directed to a method of transmitting data between two computing devices, including acts of receiving, from a mobile device, a request associated with placing a call to a contact; storing at least a portion of information associated with the request; transmitting one or more of a data network identifier; receiving the call from the mobile device, wherein the call is initiated to the data network identifier; locating the stored portion of information associated with the request corresponding to the call; receiving a request for a SIP proxy; transmitting an IP address associated with the SIP proxy; and redirecting the call to a server via the SIP proxy.


In a related embodiment, receiving the request comprises receiving a request that comprises one or more of a session identification number and a contact identification number.


In another related embodiment, storing at least a portion of the information comprises storing one or more of a mobile network code, a mobile country code, a session identification number, a contact identification number, a mobile subscriber integrated services digital network number and a name associated with the contact.


In yet another related embodiment, receiving a call includes receiving the call comprising a dial-tone multi-frequency sequence.


In still another related embodiment, locating the stored portion of information includes determining whether the call comprises a mobile subscriber integrated services digital network number; if so, using the mobile subscriber integrated services digital network number to locate the stored portion of information; and if not, using the dial-tone multi-frequency sequence to locate the stored portion of information.


In another related embodiment, receiving a request for a SIP proxy includes receiving a request from a fat client.


Another related embodiment includes transmitting an IP address associated with the SIP proxy and transmitting an IP address associated with the SIP proxy to a fat client.


Yet another related embodiment includes redirecting the call to a server via the SIP proxy, including transmitting authentication information to the SIP proxy.


And another related embodiment includes redirecting the call to a server via the SIP proxy, and providing, by the SIP proxy, an audio channel by summoning an RTP; and initiating communication with a computing device associated with the contact over the RTP.





BRIEF DESCRIPTION OF THE DRAWINGS

Aspects, features, benefits and advantages of the present invention will be apparent with regard to the following description and accompanying drawings, of which:



FIG. 1 illustrates a flow chart for an exemplar method of transmitting data between two computing devices; and



FIG. 2 illustrates an exemplary fat server architecture.





DETAILED DESCRIPTION


FIG. 1 illustrates a flow chart for an exemplary method of transmitting data between two computing devices to enable communication between the two according to an embodiment. FIG. 2 illustrates an exemplary fat server architecture according to an embodiment and capable of carrying out the steps of FIG. 1.


A request to place a phone call may be received 100 by a server 200. In an embodiment, the request may be initiated by a mobile device 205 utilizing a VoIP network 210. For example, a subscriber may initiate a request by using his mobile device 205 to select a contact to call from an address book.


In an embodiment, the mobile device 205 may transmit a request to the server 200 via a gateway 215, such as a SIP Gateway. In an embodiment, the request may include a session identification number and/or a contact identification number. A session identification may be a unique identifier associated with a calling period. The session identification number may remain valid for the length of an entire calling period, which in an embodiment, may be the period of time from when the application is powered up and connected until the time that the application is powered down. A contact identification number may be a unique identifier associated with a certain contact in an address book. A contact identification number may be assigned to each contact, and may remain valid for the duration of a calling period. In an embodiment, the unique session identification number and the contact identification numbers may expire after the calling period has closed, thus rendering them invalid for subsequent calling sessions.


In an embodiment, one or more of a mobile network code (“MNC”), a mobile country code (“MCC”), the contact identification number, the session identification number, a Mobile Subscriber Integrated Services Digital Network Number (“MSISDN”) and the contact's name may be stored 105 in a database 220. An MNC may be used in combination with an MCC to identify a mobile operator or carrier using one or more mobile networks. In an embodiment, a MSISDN may be a number, such as a telephone number, that uniquely identifies a subscription in a mobile network 210.


In an embodiment, the server 200 may transmit 110 a data network identifier (“DNID”) and/or a dual-tone multi-frequency (“DTMF”) sequence to the mobile device 205. In an embodiment, a DTMF sequence may be a sequence of tones used for telephone signaling.


The mobile device 205 may initiate a call to the DNID and may transmit the DTMF sequence in an embodiment. The server 200 may receive 115 the call and may determine 120 whether a MSISDN is present. If so, the server 200 may identify 125 the subscriber and may retrieve the prepared call from the database 220. If a MSISDN is not present, the server 200 may use the DTMF sequence to locate a prepared call.


In an embodiment, the server 200 may be in communication with one or more clients 225, and, as such, may be considered a fat server. A fat server is a server that supports a plurality of clients, which may be referred to as fat clients. The fat server may be implemented on one or more physical server machines. In an embodiment, a fat client 225 may authorize and/or authenticate the subscriber using a MSISDN or DTMF sequence as discussed above.


In an embodiment, a server 200, such as a fat server, may receive 130 a request for a SIP proxy from a client 205, such as a fat client. The fat server 200 may respond by transmitting 135 an IP address of a SIP proxy 230 to the fat client 225. The server 200 may then redirect 140 the call to a second server 245 via the SIP proxy 230. In an embodiment, authentication and/or authorization information may be transmitted to the SIP proxy 230. As such, the SIP proxy 230 may be made aware of the contact with whom the subscriber wishes to communicate. In an embodiment, the SIP proxy 230 may summon an RTP 235 to provide an audio channel over which the subscriber can communicate. The subscriber's mobile device 205 may then communicate with the contact's computing device 240 over the RTP 235. As such, the server 200 provides a central location where a subscriber may be identified and authorized. In the past, communication may have occurred directly between the server 200 and the contact's computing device 240 because both the server 200 and the computing device 240 were configured to communicate. However, situations may exist where the server 200 is not configured to communicate directly with the contact's computing device 240. As such, the server 200 may require a translator to communicate with the contact's computing device 240. In an embodiment, this responsibility may be delegated to one or more proxies. The server 200 may request and receive a SIP proxy 230 which may in turn create an RTP proxy 235 for audio flow.


It will be appreciated that various of the above-disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. Also that various presently unforeseen or unanticipated alternatives, modifications variations or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.

Claims
  • 1. A method of transmitting data between two parties, the method comprising: receiving, from a mobile device, a request associated with placing a call to a contact;storing at least a portion of information associated with the request;transmitting one or more of a data network identifier and/or a sequence number to the mobile device;receiving the call from the mobile device, wherein the call is initiated to the data network identifier;locating, in response to the received call, the stored portion of information associated with the request corresponding to the call;receiving a request for a session initiation protocol (SIP) proxy from a client;transmitting an internet protocol (IP) address associated with the SIP proxy along with the stored portion of information and/or the sequence number to the client; andredirecting the call between the mobile device and the contact to a server via the SIP proxy.
  • 2. The method of claim 1, wherein receiving the SIP proxy request comprises receiving the SIP proxy request that comprises one or more of a session identification number and a contact identification number.
  • 3. The method of claim 1, wherein storing at least the portion of information comprises storing one or more of a mobile network code, a mobile country code, a session identification number, a contact identification number, a mobile subscriber integrated services digital network number and a name associated with the contact.
  • 4. The method of claim 1, wherein receiving the call comprises: receiving the call along with the sequence number.
  • 5. The method of claim 4, wherein locating the stored portion of information comprises: determining whether the call comprises a mobile subscriber integrated services digital network number;if so, using the mobile subscriber integrated services digital network number to locate the stored portion of information; andif not, using the sequence number to locate the stored portion of information.
  • 6. The method of claim 1, wherein the client corresponds to a fat client.
  • 7. The method of claim 1, comprising: authorizing and/or authenticating the mobile device for the received call based upon authentication and/or authorization information, the authentication and/or authorization information including the stored portion of information and/or the sequence number; andtransmitting the authentication information to the SIP proxy.
  • 8. The method of claim 1, wherein redirecting the call to a server via the SIP proxy comprises: providing, by the SIP proxy, an audio channel by summoning a real-time transfer protocol (RTP); andinitiating communication with a computing device associated with the contact over the RTP.
  • 9. The method of claim 1, wherein the sequence number corresponds to a dual-tone multi-frequency (DTMF) sequence.
  • 10. A first server configured to facilitate a transmission of data between two parties, comprising: means for receiving, from a mobile device, a request associated with placing a call to a contact;means for storing at least a portion of information associated with the request;means for transmitting one or more of a data network identifier and/or a sequence number to the mobile device;means for receiving the call from the mobile device, wherein the call is initiated to the data network identifier;means for locating, in response to the received call, the stored portion of information associated with the request corresponding to the call;means for receiving a request for a session initiation protocol (SIP) proxy from a client;means for transmitting an internet protocol (IP) address associated with the SIP proxy along with the stored portion of information and/or the sequence number to the client; andmeans for redirecting the call between the mobile device and the contact to a second server via the SIP proxy.
  • 11. The first server of claim 10, wherein the means for receiving the call comprises: means for receiving the call along with the sequence number.
  • 12. The first server of claim 11, wherein the means for locating the stored portion of information comprises: means for determining whether the call comprises a mobile subscriber integrated services digital network number;means for using the mobile subscriber integrated services digital network number to locate the stored portion of information, if available; andmeans for using the sequence number to locate the stored portion of information, if the mobile subscriber integrated services digital network number is not available.
  • 13. A non-transitory computer readable medium including instructions, which, when executed by a first server, cause the first server to perform operations to facilitate a transmission of data between two parties, the instructions comprising: instructions configured to receive, from a mobile device, a request associated with placing a call to a contact;instructions configured to store at least a portion of information associated with the request;instructions configured to transmit one or more of a data network identifier and/or a sequence number to the mobile device;instructions configured to receive the call from the mobile device, wherein the call is initiated to the data network identifier;instructions configured to locate, in response to the received call, the stored, portion of information associated with the request corresponding to the call;instructions configured to receive a request for a session initiation o protocol (SIP) proxy from a client;instructions configured to transmit an internet protocol (IP) address associated with the SIP proxy along with the stored portion of information and/or the sequence number to the client; andinstructions configured to redirect the call between the mobile device and the contact to a second server via the SIP proxy.
  • 14. The non-transitory computer readable medium of claim 13, wherein the instructions configured to receive the call comprises: instructions configured to receive the call along with the sequence number.
  • 15. The non-transitory computer readable medium of claim 14, wherein the instructions configured to locate the stored portion of information comprises: instructions configured to determine whether the call comprises a mobile subscriber integrated services digital network number;instructions configured to use the mobile subscriber integrated services digital network number to locate the stored portion of information, if available; andinstructions configured to use the sequence number to locate the stored portion of information, if the mobile subscriber integrated services digital network number is not available.
  • 16. A first server configured to facilitate a transmission of data between two parties, comprising at least one processor, the at least one processor being configured to: receive, from a mobile device, a request associated with placing a call to a contact;store at least a portion of information associated with the request;transmit one or more of a data network identifier and/or a sequence number to the mobile device;receive the call from the mobile device, wherein the call is initiated to the data network identifier;locate, in response to the received call, the stored portion of information associated with the request corresponding to the call;receive a request for a session initiation protocol (SIP) proxy from a client;transmit an internet protocol (IP) address associated with the SIP proxy along with the stored portion of information and/or the sequence number to the client; andredirect the call between the mobile device and the contact to a second server via the SIP proxy.
  • 17. The first server of claim 16, wherein the at least one processor is further configured to: receive the call along with the sequence number.
  • 18. The first server of claim 17, wherein the at least one processor is further configured to: determine whether the call comprises a mobile subscriber integrated services digital network number;use the mobile subscriber integrated services digital network number to locate the stored portion of information, if available; anduse the sequence number to locate the stored portion of information, if the mobile subscriber integrated services digital network number is not available.
CLAIM OF PRIORITY AND RELATED APPLICATIONS

This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Application No. 60/884,045 filed Jan. 9, 2007, the entirety of which is incorporated by reference herein.

US Referenced Citations (151)
Number Name Date Kind
4751728 Treat Jun 1988 A
4799253 Stern et al. Jan 1989 A
5570417 Byers Oct 1996 A
5577100 McGregor et al. Nov 1996 A
5635940 Hickman et al. Jun 1997 A
5848128 Frey Dec 1998 A
5878122 White et al. Mar 1999 A
5913162 Gourdin et al. Jun 1999 A
5946618 Agre et al. Aug 1999 A
6044263 Valentine et al. Mar 2000 A
6188762 Shooster Feb 2001 B1
6205126 Moon Mar 2001 B1
6333931 LaPier et al. Dec 2001 B1
6564261 Gudjonsson et al. May 2003 B1
6618590 Howe Sep 2003 B1
6678364 Ruckart Jan 2004 B2
6687362 Lindquist et al. Feb 2004 B1
6697858 Ezerzer et al. Feb 2004 B1
6707811 Greenberg et al. Mar 2004 B2
6751457 Martin Jun 2004 B1
6775375 Bhusri Aug 2004 B1
6850762 Ala-Luukko et al. Feb 2005 B1
6917610 Kung et al. Jul 2005 B1
6937873 Levy et al. Aug 2005 B2
7039164 Howe May 2006 B1
7085260 Karaul et al. Aug 2006 B2
7099652 Brown et al. Aug 2006 B2
7110772 Wu Sep 2006 B1
7127488 Scott et al. Oct 2006 B1
7130620 Forman et al. Oct 2006 B2
7139370 Tse Nov 2006 B1
7243075 Shaffer et al. Jul 2007 B1
7257837 Xu et al. Aug 2007 B2
7274786 Fleischer, III et al. Sep 2007 B2
7280652 Bocking et al. Oct 2007 B2
7369650 Bhusri May 2008 B1
7395057 Awasthi et al. Jul 2008 B2
7436820 Beck et al. Oct 2008 B2
7471692 Erickson Dec 2008 B1
7480723 Grabelsky et al. Jan 2009 B2
7529231 Soo et al. May 2009 B2
7548611 Howe et al. Jun 2009 B2
7620404 Chesnais et al. Nov 2009 B2
7634509 Onyon et al. Dec 2009 B2
7701883 Beckemeyer Apr 2010 B2
7738861 Fournier Jun 2010 B2
7974610 Nachum Jul 2011 B2
8116836 Ki Feb 2012 B2
20010038624 Greenberg et al. Nov 2001 A1
20020013163 O'Prey Jan 2002 A1
20020099670 Jakobsson Jul 2002 A1
20020120760 Kimchi et al. Aug 2002 A1
20020129103 Birkler et al. Sep 2002 A1
20020169984 Kumar et al. Nov 2002 A1
20020193107 Nascimento Dec 2002 A1
20030013441 Bhogal et al. Jan 2003 A1
20030046404 O'Neill et al. Mar 2003 A1
20030046405 O'Neill et al. Mar 2003 A1
20030050051 Vilander Mar 2003 A1
20030060211 Chern et al. Mar 2003 A1
20030091024 Stumer May 2003 A1
20030115138 Brown et al. Jun 2003 A1
20030118175 Hariri et al. Jun 2003 A1
20030148790 Pappalardo et al. Aug 2003 A1
20030190025 Okamura et al. Oct 2003 A1
20040019539 Raman et al. Jan 2004 A1
20040037396 Gray et al. Feb 2004 A1
20040044771 Allred et al. Mar 2004 A1
20040143669 Zhao et al. Jul 2004 A1
20040156394 Westman Aug 2004 A1
20040165714 Pinault Aug 2004 A1
20040202117 Wilson et al. Oct 2004 A1
20040203643 Bhogal et al. Oct 2004 A1
20040213209 O'Connor et al. Oct 2004 A1
20040229644 Heie et al. Nov 2004 A1
20040235509 Burritt et al. Nov 2004 A1
20050025043 Mussman et al. Feb 2005 A1
20050027867 Mueller Feb 2005 A1
20050033852 Tenhunen Feb 2005 A1
20050033985 Xu et al. Feb 2005 A1
20050036597 Kobrosly et al. Feb 2005 A1
20050059418 Northcutt Mar 2005 A1
20050070230 Das et al. Mar 2005 A1
20050102257 Onyon et al. May 2005 A1
20050138571 Keskar et al. Jun 2005 A1
20050157858 Rajagopalan et al. Jul 2005 A1
20050163065 Yule Jul 2005 A1
20050171799 Hull et al. Aug 2005 A1
20050182798 Todd et al. Aug 2005 A1
20050198031 Pezaris et al. Sep 2005 A1
20050198172 Appelman et al. Sep 2005 A1
20050198365 Wei Sep 2005 A1
20050221847 Brehler et al. Oct 2005 A1
20050249344 Mueller et al. Nov 2005 A1
20050273512 Cho Dec 2005 A1
20050287997 Fournier Dec 2005 A1
20060018306 Nishida et al. Jan 2006 A1
20060018311 Kobayashi et al. Jan 2006 A1
20060023701 Nishida et al. Feb 2006 A1
20060026288 Acharya et al. Feb 2006 A1
20060029042 Nishida et al. Feb 2006 A1
20060029043 Nishida et al. Feb 2006 A1
20060029046 Nishida et al. Feb 2006 A1
20060031368 DeCone Feb 2006 A1
20060040711 Whistler et al. Feb 2006 A1
20060077932 Takeda et al. Apr 2006 A1
20060159456 Gumaste et al. Jul 2006 A1
20060168326 Baldwin et al. Jul 2006 A1
20060173961 Turski et al. Aug 2006 A1
20060205400 Kiyomoto Sep 2006 A1
20060209690 Brooke et al. Sep 2006 A1
20060236388 Ying et al. Oct 2006 A1
20060246877 Kashanian et al. Nov 2006 A1
20060248146 Wilk Nov 2006 A1
20060270392 Scott et al. Nov 2006 A1
20060270400 DaSilva et al. Nov 2006 A1
20070005776 Hansen et al. Jan 2007 A1
20070016682 Hodgson Jan 2007 A1
20070060100 Watler et al. Mar 2007 A1
20070064607 Moon et al. Mar 2007 A1
20070071006 Bosch et al. Mar 2007 A1
20070112964 Guedalia et al. May 2007 A1
20070143397 Guedalia et al. Jun 2007 A1
20070162350 Friedman Jul 2007 A1
20070281676 Borras et al. Dec 2007 A1
20070287430 Hosain et al. Dec 2007 A1
20080003964 Alperin et al. Jan 2008 A1
20080013531 Elliott et al. Jan 2008 A1
20080037524 Koch et al. Feb 2008 A1
20080056208 Hinrikus et al. Mar 2008 A1
20080056235 Albina et al. Mar 2008 A1
20080070579 Kankar et al. Mar 2008 A1
20080076409 Hinrikus et al. Mar 2008 A1
20080096592 Waytena et al. Apr 2008 A1
20080139210 Gisby et al. Jun 2008 A1
20080159261 Bessis Jul 2008 A1
20080159515 Rines Jul 2008 A1
20080166999 Guedalia et al. Jul 2008 A1
20080167019 Guedalia et al. Jul 2008 A1
20080167020 Guedalia et al. Jul 2008 A1
20080167039 Guedalia et al. Jul 2008 A1
20080188227 Guedalia et al. Aug 2008 A1
20080192910 Guedalia et al. Aug 2008 A1
20080244023 Guedalia et al. Oct 2008 A1
20080248795 Petersen et al. Oct 2008 A1
20080263170 Caron et al. Oct 2008 A1
20080305782 Guedalia et al. Dec 2008 A1
20090190738 Guedalia et al. Jul 2009 A1
20100080376 Hartley et al. Apr 2010 A1
20110312308 Willey Dec 2011 A1
20130137421 Guedalia et al. May 2013 A1
Foreign Referenced Citations (22)
Number Date Country
10341737 Apr 2005 DE
1179941 Feb 2002 EP
1517256 Mar 2005 EP
1701569 Sep 2006 EP
2391135 Jan 2004 GB
9723083 Jun 1997 WO
WO 9847298 Oct 1998 WO
WO 9934628 Jul 1999 WO
0198867 Dec 2001 WO
0215030 Feb 2002 WO
0221779 Mar 2002 WO
0239237 May 2002 WO
WO 03032613 Apr 2003 WO
03094011 Nov 2003 WO
2005065296 Jul 2005 WO
2006039552 Apr 2006 WO
WO 2006044654 Apr 2006 WO
2007001850 Jan 2007 WO
2007005124 Jan 2007 WO
2007025373 Mar 2007 WO
2007109559 Sep 2007 WO
2008013642 Jan 2008 WO
Non-Patent Literature Citations (18)
Entry
Saravanan Shanmugham, et al., Daniel C. Burnett, “Media Resource Control Protocol Version 2(MRCPv2)”, IETF Standard-Working-Draft, Internet Engineering Task Force, IETF, vol. Speechsc, No. 6, pp. 1-176 (2005).
Sinnreich, et al., “SIP telephony device requirements and configuration draft-sinnreich-sipdev-req-07.txt”, IETF Standard-Working-Draft, Internet Engineering Task Force, No. 7, pp. 1-37 (2005).
Griffin et al., “Integrating SIP, presence and FTP to provide wireless multimedia messaging”, Wireless Communications and Networking Conference, IEEE Communications Society, 4:2581-2586 (2004).
Handley et al., “RFC 2543 SIP: Session Initiation Protocol”, IETF Standard, Internet Engineering Task Force, pp. 1-153 (1999).
Handley et al., “SIP: Session Initiation Protocol”, IETF, Standard-Working-Draft, Internet Engineering Task Force, vol. 4, pp. 1-83 (1997).
Petrie, Pingtel Corp., A Framework for SIP User Agent Profile Delivery draft-iet f-sipping-config-framework-02.txt., IETF Standard-Working-Draft, Internet Engineering Task Force, No. 2, pp. 1-22 (2004).
Colman Ho, “Voice Over Internet Protocol (VoIP) Overview”, Presentation to TSACC, Mar. 23, 2004; www.isacc.ca/isacc/—doc/Book%2017%20-%202004/TSACC-04-31305.ppt.
Alcatel-Lucent, “Alcatel-Lucent OmniPCX Enterprise Communication Server: Delivering powerful, reliable and scalable IP communications to drive your 21st century business”, 2007. http://www1.alcatel-lucent.com/com/en/appcontent/opgss/ENT—OmniPCX%20Enterprise—datasheet—1007—EN—tcm228-1353221635.pdf.
SIP Connect, “CableLabs Proposal for SIP Connect 1.1”, 2007; http://www.sipforum.org/component/option,com—docman/task,doc—view/gid,149/Itemid,75/.
NST, New Standard Telephony, Convergence Simplified, Company Profile, NST 2005; http://www.ns-tel.com/files/NST—Company—Profile.pdf.
Janne Lundqvist et al., Messaging-over-IP—A network for messaging and information services; http://www.ericsson.com/ericsson/corpinfo/publications/review/1999—03/files/1999035. pdf.
Case Study, Intel Centrino, Mobile Technology, Intel Xeon Processor MP, Shanghai GM, “Seamless Communications”, http://www.intel.com/netcomms/technologies/voice/310998.pdf.
Kundan Narendra Singh, Thesis, “Reliable, Sealable and Interoperable Internet Telephony”, Columbia University, 2006; http://www1.cs.columbia.edu/˜kns10/publication/thesis.pdf.
Intel Communications Alliance, “TeleSym and Intel Deliver Voice-over-Internet-Protocol (VoIP) Enterprise Communication Solution”, Jun. 2004; http://www.intel.com/network/csp/pdf/9003wp.pdf.
Sinnreich/Pulver Com H. et al.: “SIP Telephony Device Requirements and Configuration; draft-sinnreich-sipdev-req-08.txt”, IETF Standard-Working-Draft, Internet Engineering Task Force, IETF, CH, No. 8, Oct. 1, 2005, XP015043067 ISSN: 0000-0004.
Rosenberg, J. et al.: “SIP: Session Initiation Protocol” 20020601; 20020600; Jun. 1, 2002, pp. 1-269, XP015009039.
Schulzrinne Columbia University B. Volz Ericsson H: “Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers; rfc3319.txt”, IETF Standard, Internet Engineering Task Force, IETF, CH. Jul. 1, 2003, XP015009189; ISSN: 0000-0003.
International Search Report and Written Opinion—PCT/US2008/050615, International Searching Authority—European Patent Office, Nov. 18, 2008.
Related Publications (1)
Number Date Country
20080181165 A1 Jul 2008 US
Provisional Applications (1)
Number Date Country
60884045 Jan 2007 US