The present invention relates to a third party call control (3PCC) application program interface (API). This invention does relate to novel uses of a web browser or other Internet capable software specifically. This invention relates to a program and method for third party control of a telephonic call.
Voice over Internet Protocol (VoIP) is a category of hardware and software that enables people to use the Internet as the transmission medium for telephone calls by sending voice data in packets using Internet Protocol (IP) rather than by traditional circuit transmissions of the Public Switch Telephone Network (PSTN). This allows the elimination of circuit switching and the associated waste of bandwidth. Instead, packet switching is used, where IP packets with voice data are sent over the network only when data needs to be sent, i.e. when a caller is talking.
The advantages of VoIP over traditional telephony include; by way of example, are the following: lower costs per call, especially for long-distance calls, and lower infrastructure costs: that is, once this IP infrastructure is installed, no or little additional telephony infrastructure is needed.
However, despite the technological flexibility of VoIP system, callers are still limited to initiating calls manually, that is by using the alphanumeric keypad on a telephone.
The art has a clear need for important third party control of telephonic calls. The present invention provides a rotation to that art-felt need.
The present invention, in one aspect, is a third party call control (3PCC) application program interface (API) that provides the capability for users to use a web browser or other Internet capable software to place a call, rather than using an alphanumeric keypad on a telephonic telephone. The open nature of the API also provides the capability to integrate 3PCC functionality with new or existing applications like customer relationship management (CRM), Contact management applications, and the like.
In one embodiment of the present invention, a third party call control application program interface comprises a first uniform resource locator operable over the Internet for causing a call between a first telephonic device and a second telephone device to be completed. The first uniform resource locator includes identification of the first telephonic device and identification of the second telephonic device.
In one aspect of the present invention, the first uniform resource locator may be generated on a computer system that is communicatively connected to a computer network, or public communication network such as the Internet. The call may be completed by initiating a call to the first telephonic device and then transferring the call, to complete the call, to the second telephonic device, at the time the call to the first telephonic device is answered. The call may be initiated to the first telephonic device using the Session Initiation Protocol INVITE method. The call may be transferred to the second telephonic device using the Session Initiation Protocol REFER method.
In one aspect of the present invention, the identification of the first telephonic device may include a telephone number of the first telephonic device, and the identification of the second telephonic device may include a telephone number of the second telephonic device. The third party call control application program may further include identification of an account to be billed. The identification of the first telephonic device may include a telephone number of the first telephone device, and the identification of the second telephonic device comprises a telephone number of the second telephonic device. The identification of the account to be billed may include the telephone number of the first telephonic device, the telephone number of the second telephonic device, or the telephone number of a third telephonic device.
In one aspect of the present invention, the third party call control application program may further include a second uniform resource locator operable over the Internet for obtaining information identifying an account to be billed. The information identifying an account to be billed may include at least one telephone number. At least one of the first uniform resource locator identification of the first telephonic device and the first uniform resource locator identification of the second telephonic device may include the at least one telephone number obtained by the second uniform resource locator.
In one aspect of the present invention, the third party call control application program may further include identification information and password information. The identification and password information is authenticated and validated before the completion of the call.
The third party call control (3PCC) application program interface (API) of the present invention provides the capability for users to use a web browser or other Internet capable software to place a call, rather than using a keypad on a telephone. The open nature of the API also provides the capability to integrate 3PCC functionality with new or existing applications like customer relationship management (CRM), Contact management applications, and the like.
A system in which the present invention may be implemented is shown in
&
This URL includes specification of the secure hyper-text transfer protocol (https:), the Internet address of web server 106 (secure.url.com), the action to be performed by web server 106 (makecall), the authorization credentials (username=aw&password=secret), the phone number of the telephone from which the call is to originate (fromnumber=17325551111) and the telephone number of the telephone to which the call is to be completed (tonumbe˜17325552222).
The HTTP URL activates a secure web server 106, which authenticates the user and passes the information to a CallController server system 108. Preferably, the information is passed from secure web server 106 to CallController 108 using a Remote Procedure Call (RPC) 110. The CallController 108 is a trusted peer of Session Initiation Protocol (SIP) proxy server 114.
The SIP 112 is a signaling protocol for Internet conferencing, telephony, presence, events notification and instant messaging. SIP provides the necessary protocol mechanisms so that end systems and proxy servers can provide services such as call completion, call forwarding, callee and calling “number” delivery, personal mobility, terminal-type negotiation and selection, terminal capability negotiation, caller and callee authentication, blind and supervised call transfer, invitations to multicast conferences.
A goal for SIP was to provide a superset of the call processing functions and features present in the public switched telephone network (PSTN). As such, features that permit familiar telephone-like operations are present: dialing a number, causing a phone to ring, hearing ringback tones or a busy signal. Implementation and terminology are different; for example, SIP refers to a device being in an “alerting state” rather than “ringing.”
In response to receiving the RPC 110 from secure web sewer 106, CallController 108 invokes a number of SIP methods 112 involving SIP proxy server 114. In response, SIP proxy server 114 invokes those SIP methods 116 to the appropriate target. In addition, SIP proxy server 114 monitors any calls that are initiated and completed, in order to handle the necessary billing functions.
In particular, CallController 108 initiates a call from CallController 108 to the “from” number 118, using the SIP INVITE method 116. SIP proxy server 114, in turn, invokes the SIP INVITE method 116 targeting the “from” telephone number 118. The technique used to invoke the SIP INVITE method 116 depends upon the type of “from” telephone 118 involved. For example, if the “from” telephone 118 is an Internet Protocol (IP) telephone, the SIP INVITE 120B method may be invoked directly on the “from” telephone 118, since the IP telephone is capable of performing the necessary functions in response to the invocation of the SIP INVITE method 120B. Alternatively, if the “from” telephone 118 is a standard Public Switched Telephone Network (PSTN) telephone, then the SIP INVITE method 120B is invoked using a PSTN gateway server 120A to initiate the call. In either case, a call to the “from” telephone 118 is initiated.
When the “from” telephone 118 answers, CallController 108 initiates a call transfer to transfer the call to the “from” telephone 118 from the origin of the call, CallController 108, to the “to” telephone 122 number, using the SIP REFER method. This terminates the initial call between the CallController and the “from” telephone 118, and triggers the “from” telephone 118 to initiate a new call to the “to” telephone 122. This call is billed to the appropriate account.
There are three possible numbers to which the call may be billed—the “from” number, the “to” number, or a third “billto” number. The number to which the call is billed must belong to a subscriber of the telephone service provider. Thus, if the “from” number belongs to the subscriber, the call is billed to the “from” number, if the “to” number belongs to the subscriber, the call is billed to the “to” number, if neither the “from” number nor the “to” number belong to the subscriber, a third number must be billed. This third number may be supplied in the URL 104 or it may be associated with the user name that was used to login. An example of a suitable URL including a “billto” number is:
&
Preferably, an additional HTTPS URL is exposed which allows an application to retrieve a list of phone numbers in a user's account. This URL is passed authorization credentials (login information) and returns the phone numbers associated with the account corresponding to that login information. This list can be presented to the user to select which number is to initiate the call (the “from” number), and/or to select which number is to be billed for the call (the “billto” number).
Although, typically, user computer system 102 is used to initiate the telephone calls, calls may also be initiated from a third party telephone 124. Third party telephone 124 would dial into an interactive voice response (IVR) system 126 and would be used to enter the information needed to initiate the telephone call. IVR 126 would pass the information to CallController 108 using RPC 128. The system would then initiate the call in a manner similar to that for a call initiated from user computer system 102.
The third party telephone configuration slightly changes the role of “from” telephone 118, as compared to the configuration involving only the “to” and “from” telephones. Both “to” telephone 122 and “from” telephone 118 become the “to” telephones. If the third party places a call to “from” telephone 118, SIP proxy server 114 invokes SIP INVITE methods 116, as discussed above. However, if third party telephone 124 is trying to reach “to” telephone 122, the inventive system may have an alternative and additional communication link 500 adaptively operable in response to invoking methods similar to SIP INVITE methods 116 by SIP Proxy Server 114.
As a further possibility, CALL CONTROLLER SERVER 108 can always directly call “to” telephone 122 using the link similar to communication link 500. One of possible scenarios involving such a direct connection may involve a situation when the caller operating the “from” telephone does not want experience any delays due to the busy line. Instructing the controller server to initiate contact with the “to” telephone and, once the operator of the “to” telephone answers the call from the controller server, actually connecting the “from” and “to” telephones may save the operator of the “from” telephone time.
The configuration of the inventive system involving third party telephone 124 may have numerous practical ramifications and be used in a variety of ways. For instance, one potential use may be similar to a “calling card”. The subscriber could initiate a call from any telephone, such as their hotel room telephone or a pay telephone, to any other phone, while billing the call to their own account.
Examples of users of the services provided by the present invention include business users who have a large phone book of users they need to call (e.g. sales calls), or by telemarketing operations. In this situation, the subscriber uses the “from” telephone and the calls are billed to the “from” number.
For example, this could be implemented in phone or address book software, such as using a plug-in to an email program such as MICROSOFT OUTLOOK@, or in contact manager software.
An example of such an implementation is shown in
In order to dial the telephone number 210A-C using the third party call control system shown in
Additional enhancement to this functionality includes the capability to scan pages and documents for character strings that appear to be telephone numbers. These telephone numbers may be highlighted for the user. The user may then dial any such telephone number by selecting the number and pressing the hotkey or other software control.
Preferably, the implementation includes sufficient intelligence to understand the formats of telephone numbers, including international telephone numbers, as well as the ability to filter the characters in the telephone number to strip characters such as parentheses, hyphens, etc.
In another embodiment, subscribers could distribute software objects that provide the capability for the recipient of the object to call the subscriber. Typically, the software object is distributed using email, but it may be distributed by download or any form of electronic communications. An example of such a software object is shown in
Included in or associated with vcard 302 and/or software control 314 is software that initiates a telephone call between the subscriber and the recipient of the vcard. When the recipient enters a telephone number in field 312 and activates software control 314, vcard 302 generates a URL and uses the URL to transmit information 316 to a vcard server 318. While the transmitted information 316 may include the identification and password information of the subscriber, preferably, transmitted information 316 does not include this information in an insecure form. For example, transmitted information 316 may include the identification and password information of the subscriber in an encrypted form, or transmitted information 316 may be a token that is used by vcard server 318 to obtain the identification and password information of the subscriber, such as by a database lookup.
Vcard server 318 receives the transmitted information 316 and generates a URL that is used to transmit information 320 to secure web server 106. This URL is similar to that generated by user computer system 102, shown in
Typically, vcard 302 includes information such as the network address of vcard server 318, token and/or encryption information, and information identifying the sender of the vcard. Alternatively, vcard 302 could include a unique token that identifies the particular call setup to be initiated, but which does not itself include information that identifies the subscriber account involved. Of course, various modifications are possible, such as including the identification information, but not the password, etc.
In the example shown in
In addition, the sender of software object may be allowed to specify conditions for use of the software object. For example, the sender may specify that the software object expires after a particular date, the sender may specify time of day restrictions on the calls, the sender may restrict international calls, etc. If the transmitted information is encrypted, this information may be included in the encrypted information. If the transmitted information is a token, the database may include the appropriate conditional information.
Although specific embodiments of the present invention have been described, it will be understood by those of skill in the art that there are other embodiments that are equivalent to the described embodiments. For example, the present invention may also be advantageously applied to three-way and/or multiple party conferencing. For three-way conferencing, the system shown in
In addition, it is important to note that while the present invention has been described in the context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the form of a computer readable medium of instructions and a variety of forms and that the present invention applies equally regardless of the particular type of signal bearing media actually used to carry out the distribution. Examples of computer readable media include recordable-type media such as floppy disc, a hard disk drive, RAM, and CD-ROM's, as well as transmission type media, such as digital and analog communications links.
Accordingly, it is to be understood that the invention is not to be limited by the specific illustrated embodiments, but only by the scope of the appended claims.
This application is a continuation of co-pending U.S. patent application Ser. No. 11/081,185, filed Mar. 16, 2005, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4100377 | Flanagan | Jul 1978 | A |
4748620 | Adelmann et al. | May 1988 | A |
4782485 | Gollub | Nov 1988 | A |
5018136 | Gollub | May 1991 | A |
5444707 | Cerna et al. | Aug 1995 | A |
5452289 | Sharma et al. | Sep 1995 | A |
5526353 | Henley et al. | Jun 1996 | A |
5623490 | Richter et al. | Apr 1997 | A |
5966427 | Shaffer et al. | Oct 1999 | A |
5995491 | Richter et al. | Nov 1999 | A |
6014437 | Acker et al. | Jan 2000 | A |
6067516 | Levay et al. | May 2000 | A |
6084956 | Turner et al. | Jul 2000 | A |
6091808 | Wood et al. | Jul 2000 | A |
6097516 | Almstrom | Aug 2000 | A |
6097804 | Gilbert et al. | Aug 2000 | A |
6104706 | Richter et al. | Aug 2000 | A |
6115460 | Crowe et al. | Sep 2000 | A |
6115468 | De Nicolo | Sep 2000 | A |
6118860 | Hillson et al. | Sep 2000 | A |
6122364 | Petrunka et al. | Sep 2000 | A |
6128379 | Smyk | Oct 2000 | A |
6137869 | Voit et al. | Oct 2000 | A |
6138072 | Nagai | Oct 2000 | A |
6167042 | Garland et al. | Dec 2000 | A |
6169741 | Lemaire et al. | Jan 2001 | B1 |
6175565 | McKinnon et al. | Jan 2001 | B1 |
6178239 | Kishinsky et al. | Jan 2001 | B1 |
6185285 | Relyea et al. | Feb 2001 | B1 |
6188762 | Shooster | Feb 2001 | B1 |
6195425 | Farris | Feb 2001 | B1 |
6226286 | Danne et al. | May 2001 | B1 |
6226361 | Koyama | May 2001 | B1 |
6243443 | Low et al. | Jun 2001 | B1 |
6249576 | Sassin et al. | Jun 2001 | B1 |
6266405 | Madour et al. | Jul 2001 | B1 |
6272126 | Strauss et al. | Aug 2001 | B1 |
6282281 | Low | Aug 2001 | B1 |
6282284 | Dezonno et al. | Aug 2001 | B1 |
6292553 | Fellingham et al. | Sep 2001 | B1 |
6298064 | Christie | Oct 2001 | B1 |
6304572 | Christie | Oct 2001 | B1 |
6304637 | Mirashrafi et al. | Oct 2001 | B1 |
6304653 | O'Neil et al. | Oct 2001 | B1 |
6310941 | Crutcher et al. | Oct 2001 | B1 |
6311182 | Colbath et al. | Oct 2001 | B1 |
6320951 | Shtivelman et al. | Nov 2001 | B1 |
6327572 | Morton et al. | Dec 2001 | B1 |
6330317 | Garfinkel | Dec 2001 | B1 |
6337889 | Mita et al. | Jan 2002 | B1 |
6337899 | Alcendor et al. | Jan 2002 | B1 |
6343115 | Foladare et al. | Jan 2002 | B1 |
6343143 | Guillemaud et al. | Jan 2002 | B1 |
6349132 | Wesemann et al. | Feb 2002 | B1 |
6351256 | Jones et al. | Feb 2002 | B1 |
6351464 | Galvin et al. | Feb 2002 | B1 |
6351526 | Shaffer et al. | Feb 2002 | B1 |
6366577 | Donovan | Apr 2002 | B1 |
6366661 | Devillier et al. | Apr 2002 | B1 |
6373836 | Deryugin et al. | Apr 2002 | B1 |
6373936 | Raniere et al. | Apr 2002 | B1 |
6373938 | Palacios et al. | Apr 2002 | B1 |
6381644 | Munguia et al. | Apr 2002 | B2 |
6385209 | Skirmont et al. | May 2002 | B1 |
6389119 | McBride | May 2002 | B1 |
6393476 | Barnhouse et al. | May 2002 | B1 |
6400820 | Edwards et al. | Jun 2002 | B1 |
6404746 | Cave et al. | Jun 2002 | B1 |
6404882 | Fellner et al. | Jun 2002 | B2 |
6404884 | Marwell et al. | Jun 2002 | B1 |
6408062 | Cave | Jun 2002 | B1 |
6408065 | O'Neil et al. | Jun 2002 | B1 |
6411697 | Creamer et al. | Jun 2002 | B1 |
6411704 | Pelletier et al. | Jun 2002 | B1 |
6415269 | Dinwoodie | Jul 2002 | B1 |
6421437 | Slutsman | Jul 2002 | B1 |
6422242 | Slautterback et al. | Jul 2002 | B1 |
6424707 | Chatterjee | Jul 2002 | B1 |
6430175 | Echols et al. | Aug 2002 | B1 |
6430176 | Christie, IV | Aug 2002 | B1 |
6430289 | Liffick | Aug 2002 | B1 |
6434143 | Donovan | Aug 2002 | B1 |
6442242 | McAllister et al. | Aug 2002 | B1 |
6446127 | Schuster et al. | Sep 2002 | B1 |
6449260 | Sassin et al. | Sep 2002 | B1 |
6452932 | Christie | Sep 2002 | B1 |
6456618 | Kozdon et al. | Sep 2002 | B2 |
6463052 | Christie | Oct 2002 | B1 |
6466570 | Low et al. | Oct 2002 | B1 |
6470010 | Szviatovszki et al. | Oct 2002 | B1 |
6473429 | Christie | Oct 2002 | B1 |
6480484 | Morton | Nov 2002 | B2 |
6480581 | Wu et al. | Nov 2002 | B1 |
6487200 | Fraser | Nov 2002 | B1 |
6493337 | Stevenson, III | Dec 2002 | B1 |
6493437 | Olshansky | Dec 2002 | B1 |
6496477 | Perkins et al. | Dec 2002 | B1 |
6504921 | Kotik et al. | Jan 2003 | B2 |
6510219 | Wellard et al. | Jan 2003 | B1 |
6519232 | Becher | Feb 2003 | B1 |
6519333 | Malik | Feb 2003 | B1 |
6539077 | Ranalli et al. | Mar 2003 | B1 |
6542589 | Baskin | Apr 2003 | B1 |
6553023 | Yamamiya et al. | Apr 2003 | B1 |
6557712 | Gruber et al. | May 2003 | B2 |
6564261 | Gudjonsson et al. | May 2003 | B1 |
6567398 | Aravamudan et al. | May 2003 | B1 |
6567419 | Yarlagadda | May 2003 | B1 |
6570010 | Ishida et al. | May 2003 | B2 |
6571212 | Dent | May 2003 | B1 |
6577712 | Larsson et al. | Jun 2003 | B2 |
6584094 | Maroulis et al. | Jun 2003 | B2 |
6584098 | Dutnall | Jun 2003 | B1 |
6584186 | Aravamudan et al. | Jun 2003 | B1 |
6584510 | Anttila | Jun 2003 | B2 |
6587836 | Ahlberg et al. | Jul 2003 | B1 |
6597685 | Miloslavsky et al. | Jul 2003 | B2 |
6614786 | Byers | Sep 2003 | B1 |
6614899 | Sollee et al. | Sep 2003 | B1 |
6621899 | Dezonno et al. | Sep 2003 | B2 |
6628760 | Mirashrafi et al. | Sep 2003 | B2 |
6633561 | Christie | Oct 2003 | B2 |
6636506 | Fan | Oct 2003 | B1 |
6650890 | Irlam et al. | Nov 2003 | B1 |
6665294 | Christie | Dec 2003 | B2 |
6665389 | Haste, III | Dec 2003 | B1 |
6665392 | Wellner et al. | Dec 2003 | B1 |
6668055 | Marwell et al. | Dec 2003 | B2 |
6681252 | Schuster et al. | Jan 2004 | B1 |
6690780 | Kotik et al. | Feb 2004 | B2 |
6694007 | Lang et al. | Feb 2004 | B2 |
6697475 | Melampy et al. | Feb 2004 | B1 |
6707811 | Greenberg et al. | Mar 2004 | B2 |
6707906 | Ben-Chanoch | Mar 2004 | B1 |
6711160 | Chan et al. | Mar 2004 | B2 |
6714988 | Takemoto et al. | Mar 2004 | B2 |
6718031 | Fellner et al. | Apr 2004 | B2 |
6724755 | Kim | Apr 2004 | B1 |
6731630 | Schuster et al. | May 2004 | B1 |
6731642 | Borella et al. | May 2004 | B1 |
6731741 | Fourcand et al. | May 2004 | B1 |
6741586 | Schuster et al. | May 2004 | B1 |
6748057 | Ranalli et al. | Jun 2004 | B2 |
6760429 | Hung et al. | Jul 2004 | B1 |
6763226 | McZeal, Jr. | Jul 2004 | B1 |
6765931 | Rabenko et al. | Jul 2004 | B1 |
6769020 | Miyazaki et al. | Jul 2004 | B2 |
6771637 | Suzuki et al. | Aug 2004 | B1 |
6775368 | Lee et al. | Aug 2004 | B1 |
6778661 | Yumoto et al. | Aug 2004 | B1 |
6798771 | Low et al. | Sep 2004 | B1 |
6798873 | Vardi et al. | Sep 2004 | B2 |
6819752 | Raniere et al. | Nov 2004 | B2 |
6822945 | Petrovykh | Nov 2004 | B2 |
6834106 | Pinard | Dec 2004 | B1 |
6839323 | Foti | Jan 2005 | B1 |
6839359 | Skirmont et al. | Jan 2005 | B2 |
6839421 | Esparza et al. | Jan 2005 | B2 |
6885746 | Hausman et al. | Apr 2005 | B2 |
6898569 | Bansal et al. | May 2005 | B1 |
6931007 | Jones | Aug 2005 | B2 |
6999583 | Valenti et al. | Feb 2006 | B2 |
7069309 | Dodrill et al. | Jun 2006 | B1 |
7177415 | Kim et al. | Feb 2007 | B1 |
7418509 | Koskelainen et al. | Aug 2008 | B2 |
7450565 | Suotula et al. | Nov 2008 | B2 |
7813335 | Terpstra et al. | Oct 2010 | B2 |
7839987 | Kirchhoff et al. | Nov 2010 | B1 |
7869941 | Coughlin et al. | Jan 2011 | B2 |
7873034 | Tucker | Jan 2011 | B2 |
7876743 | Garcia-Martin et al. | Jan 2011 | B2 |
7957517 | Ricciardi et al. | Jun 2011 | B2 |
8099089 | Sedlacek et al. | Jan 2012 | B2 |
8289885 | Cai et al. | Oct 2012 | B2 |
8300630 | Jaiswal et al. | Oct 2012 | B2 |
8433283 | Borislow et al. | Apr 2013 | B2 |
8462768 | Badger | Jun 2013 | B2 |
20010005412 | Light et al. | Jun 2001 | A1 |
20010005415 | Grunsted et al. | Jun 2001 | A1 |
20010014919 | Tzirin | Aug 2001 | A1 |
20010041560 | Tarkiainen et al. | Nov 2001 | A1 |
20020007391 | Suzuki | Jan 2002 | A1 |
20020046279 | Chung | Apr 2002 | A1 |
20020049815 | Dattatri | Apr 2002 | A1 |
20020049860 | Koistinen | Apr 2002 | A1 |
20020055879 | Wengrovitz et al. | May 2002 | A1 |
20020095516 | Nada | Jul 2002 | A1 |
20020112073 | MeLampy et al. | Aug 2002 | A1 |
20020114430 | Murata | Aug 2002 | A1 |
20020126818 | Cai | Sep 2002 | A1 |
20020129131 | Yamashita | Sep 2002 | A1 |
20020150083 | Fangman et al. | Oct 2002 | A1 |
20020191635 | Chow et al. | Dec 2002 | A1 |
20030005280 | Bobde et al. | Jan 2003 | A1 |
20030041132 | Lim et al. | Feb 2003 | A1 |
20030043787 | Emerson | Mar 2003 | A1 |
20030053446 | Kwon | Mar 2003 | A1 |
20030095541 | Chang et al. | May 2003 | A1 |
20030095542 | Chang et al. | May 2003 | A1 |
20030108064 | Bilke et al. | Jun 2003 | A1 |
20030162526 | Ogman et al. | Aug 2003 | A1 |
20030163526 | Clarisse et al. | Aug 2003 | A1 |
20030174695 | Lautenschlager et al. | Sep 2003 | A1 |
20030186676 | Ogman et al. | Oct 2003 | A1 |
20030202504 | Dhara et al. | Oct 2003 | A1 |
20040028025 | Chang | Feb 2004 | A1 |
20040028207 | Kato | Feb 2004 | A1 |
20040039938 | Katz et al. | Feb 2004 | A1 |
20040057415 | Colson et al. | Mar 2004 | A1 |
20040098507 | Thubert et al. | May 2004 | A1 |
20040114575 | Morita et al. | Jun 2004 | A1 |
20040148392 | Cotte | Jul 2004 | A1 |
20040190711 | Miyajima | Sep 2004 | A1 |
20040205209 | Wengrovitz et al. | Oct 2004 | A1 |
20040205777 | Zalenski et al. | Oct 2004 | A1 |
20040215770 | Maher et al. | Oct 2004 | A1 |
20040223606 | Enete et al. | Nov 2004 | A1 |
20040258021 | Kashimoto et al. | Dec 2004 | A1 |
20040258238 | Wong | Dec 2004 | A1 |
20040258239 | Gallant et al. | Dec 2004 | A1 |
20050018659 | Gallant et al. | Jan 2005 | A1 |
20050041793 | Fulton et al. | Feb 2005 | A1 |
20060072526 | Rasanen | Apr 2006 | A1 |
20060153102 | Kuure et al. | Jul 2006 | A1 |
20060200517 | Nelson et al. | Sep 2006 | A1 |
20060205436 | Liu et al. | Sep 2006 | A1 |
20060210041 | Citron et al. | Sep 2006 | A1 |
20060285672 | Levy et al. | Dec 2006 | A1 |
20070047529 | Ricciardi et al. | Mar 2007 | A1 |
20070100986 | Bagley et al. | May 2007 | A1 |
20090017856 | Albertsson et al. | Jan 2009 | A1 |
20090286516 | Sedlacek et al. | Nov 2009 | A1 |
20090323916 | O'Sullivan et al. | Dec 2009 | A1 |
20100312832 | Allen et al. | Dec 2010 | A1 |
20110103570 | Gao et al. | May 2011 | A1 |
20110280391 | Venugopal et al. | Nov 2011 | A1 |
Number | Date | Country |
---|---|---|
101529800 | Dec 2011 | CN |
2148489 | Jan 2010 | EP |
2934451 | Jan 2010 | FR |
WO-9722210 | Jun 1997 | WO |
WO-9818283 | Apr 1998 | WO |
WO-2004034679 | Apr 2004 | WO |
WO-2004034679 | Sep 2004 | WO |
WO-2009152162 | Dec 2009 | WO |
Entry |
---|
Johnston et al., “SIP Call Flow Examples”, IETF Standard-Working-Draft, Internet engineering Task Force (IETF), CH, vol. 4, pp. 1-72, Apr. 4, 2001. |
Fineberg, “A Practical Architecture for Implementing End-to-End QoS in an IP Network”, Communications Magazine, IEEE, vol. 40, Issue 1, pp. 122-130, Jan. 2002. |
Mahy et al., “STUN-aware NAT draft-simu-midcom-stun-aware-nat-00.txt”, IETF Standard-Working-Draft, Internet Engineering Task Force (IETF), CH, pp. 1-18, Apr. 10, 2002. |
Melvin et al., “Time Synchronization for VoIP Quality of Service”, Internet Computing, IEEE, vol. 6, Issue 3, pp. 57-63, 2002. |
Rosenberg et al., “STUN—Simple Traversal of UDP Through Network Address Translators”, IETF Standard-Working-Draft, Internet Engineering Task Force (IETF), CH, vol. 3, pp. 1-44, Oct. 14, 2002. |
Mahy et al., “Pre-Midcom Requirements for Traversal of NATs for traffic not supported by STUN draft-mahy-midcom-premidcom-relay-reqs-00.txt”, IETF Standard-Working-Draft, Internet Engineering Taskforce, IETF, CH, pp. 1-8, Feb. 2003. |
Rosenberg et al.,“Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)”, Network Working Group, Request for Comments: 3725, BCP: 85, pp. 1-32, Apr. 2004. |
Mahy et al., “Remote Call Control in SIP using the REFER method and the session-oriented dialog package draft-mahy-sip-remote-cc-02”, SIP WGInternet-Draft, pp. 1-40, Oct. 23, 2005. |
International Search Report and Written Opinion mailed Jul. 3, 2008 for PCT Application No. PCT/US06/09450. |
European Office Action dated Apr. 9, 2013 for Application No. 06 738 502.1-1858. |
European Search Report dated Apr. 23, 2013 for European application No. 06738509.61853/1869850, PCT/US2006009457. |
Number | Date | Country | |
---|---|---|---|
20140169225 A1 | Jun 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11081185 | Mar 2005 | US |
Child | 14164941 | US |