Communication endpoint supporting multiple provider models

Details Communication endpoint supporting multiple provider models Communication endpoint supporting multiple provider models

2002-01-24

2008-11-18

Caldwell, Andrew (Department: 2142)

Electrical computers and digital processing systems: multicomput

Computer-to-computer session/connection establishing

Reexamination Certificate

active

07454505

ABSTRACT:
A method for communication includes receiving a request from a first party, submitted via a first communication service provider to a telephony application, to place a call using the application to a second party. Responsive to a characteristic of the call placed by the first party, a second communication service provider is selected to carry the call between the application and the second party. The second party is then connected via the second communication service provider to communicate with the first party using the application.

REFERENCES:
patent: 6185289 (2001-02-01), Hetz et al.
patent: 6415148 (2002-07-01), Chiniga et al.
patent: 6597686 (2003-07-01), Smyk
patent: 6724780 (2004-04-01), Bhuyan et al.
patent: 6778652 (2004-08-01), Gaus et al.
patent: 6888937 (2005-05-01), Kurapati
patent: 6999448 (2006-02-01), Klein
U.S. Appl. No. 60/264,520, “Hybrid JTAPI Provider Model”, filed Jan. 25, 2001.
The Parlay Technical Team, “Parlay API's 2.1: Generic Call Control Service Interfaces”, Jun. 26, 2000.
U.S. Appl. No. 09/896,107, “Virtual Call Center”.
Java™ Telephony Specification, JTAPI version 1.3, Jun. 30, 1999.
Package javax.telephony, JTAPI version 1.3, Jun. 30, 1999.
“JAIN™ a set of Java™ APIs for integrated Networks”, Jain Java Call Control (JCC) Application Programming Interface (API), version 1.0, Overview of the API, Jan. 19, 2001.
JAIN™ JCC Specification, obtained from the internet on Jan. 17, 2002, from http://jcp.org.jsr/detail/21/prt.
“JTAPI Intriduction”,The Source for Java™ Technology, obtained from the internet on Dec. 27, 2001, from http://java.sun.com/products/jtapi/.
“An Introduction to JTAPI (Java Telephony API) Release 1.2, Rev. 0.7”, obtained from the Internet Dec. 27, 2001, from http://java.sun.com/products/jtapi/jtapi-1.2/JTAPIWhitePaper 0 7.html.
Microsoft, “Windows® Operating Systems: IP Telephony with TAPI 3.0”, 1997.
“The Java Telephony API: An Overview”, Version 1.2, Oct., 1997, obtained from the internet Dec. 27, 2001, from http://jaya.sun.com/products/jtapi/jtapi-1.2/Overview.html.
“Java Telephony API Call Control Extension Package”, Version 1.2, Oct., 1997, obtained from the internet Dec. 27, 2001, from http://java.sun.com/products/jtapi/jtapi-1.2/CallCtlOverview.html.
“User's Reference: Genetic JTAPI Reference Manual, Version 1.2”, IBM Haifa research Lab, Jul. 2001.
U.S. Appl. No. 09/885,578, “Service Application Architecture for Integrated Network Service Providers”.
U.S. Appl. No. 09/885,576, “Service Logic Execution Environment Connector to Client Interface”.
U.S. Appl. No. 09/885,577, “Service Logic Execution Environment for Telecommunications Service Components”.
“Jain™ Call Control API Enables Application Portability Across Heterogeneous Networks”, obtained from the internet on Jan. 17, 2002, from http://java.sun.com/pr/2000/06/pr000606-11.html.

Affiliated with

Also associated with

Rating

Communication endpoint supporting multiple provider models does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Communication endpoint supporting multiple provider models, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Communication endpoint supporting multiple provider models will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-4037759