EP1293088A2 - Traitement d'informations sur des sessions de communication - Google Patents

Traitement d'informations sur des sessions de communication

Info

Publication number
EP1293088A2
EP1293088A2 EP01937746A EP01937746A EP1293088A2 EP 1293088 A2 EP1293088 A2 EP 1293088A2 EP 01937746 A EP01937746 A EP 01937746A EP 01937746 A EP01937746 A EP 01937746A EP 1293088 A2 EP1293088 A2 EP 1293088A2
Authority
EP
European Patent Office
Prior art keywords
message
information
data
web browser
query string
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.)
Withdrawn
Application number
EP01937746A
Other languages
German (de)
English (en)
Inventor
Andrew J. Prokop
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.)
Nortel Networks Ltd
Original Assignee
Nortel Networks Ltd
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
Application filed by Nortel Networks Ltd filed Critical Nortel Networks Ltd
Publication of EP1293088A2 publication Critical patent/EP1293088A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer

Definitions

  • This invention relates to network-based call sessions and, more particularly, to providing information in a web browser in response to messages communicated during call sessions.
  • Data networks are widely used to link various types of network elements, such as personal computers, servers, gateways, network telephones, and so forth.
  • Data networks may include private networks (such as local area networks or wide area networks), and public networks (such as the Internet).
  • private networks such as local area networks or wide area networks
  • public networks such as the Internet.
  • Popular forms of communications between network elements across such data networks include electronic mail, file transfer, web browsing, and other exchanges of digital data.
  • Voice and multimedia communications over data networks are unlike voice and multimedia communications in a conventional circuit-switched network such as the public switched telephone network (PSTN), which provides users with dedicated, end-to- end circuit connections for the duration of each call.
  • PSTN public switched telephone network
  • Communications over data networks such as IP (Internet Protocol) networks, are performed using packets or datagrams that are sent in bursts from a source to one or more destination nodes.
  • Voice data, and other forms of multimedia streaming data sent over a data network typically share network bandwidth with conventional non-streaming data (e.g., data associated with electronic mail, file transfer, web access, and other traffic).
  • SIP Session Initiation Protocol
  • a communications network may include a collection of different types of terminals, such as terminals coupled to packet-based networks (e.g., computers, network telephones, etc.) and terminals coupled to circuit-switched networks (e.g., standard analog or digital telephones). Inter-operation between different types of terminals may be possible, and may be accomplished by use of a gateway, such as a PSTN gateway, which converts between packet-based data and circuit-switched data in a call session. Advances in technology have thus improved inter-operability between packet-based telephony devices and circuit-switched telephony devices, increasing the practical reach of IP telephony to users.
  • packet-based networks e.g., computers, network telephones, etc.
  • circuit-switched networks e.g., standard analog or digital telephones
  • GUIs graphical user interfaces
  • a method includes receiving a message relating to a state of a call session over a data network, extracting information from the message, sending the information to a web browser, and updating data in the web browser based on the message information.
  • the message received may be according to a protocol defining real-time interactive sessions.
  • the data updated may be a web page in the web browser.
  • Advantages offered by some embodiments of the invention may include one or more of the following. By displaying a web page during a call session on a data network, valuable information about a caller may be provided in real time.
  • the web page may be related to the information supplied with the message.
  • the web page may be supplied automatically, thus avoiding distractions for the recipient of the call session message, who may then service the sender of the call session message with undivided attention.
  • FIG. 1 is a block diagram of a communications system according to one embodiment of the invention.
  • FIG. 2 is a block diagram of a user agent server according to one embodiment of the invention.
  • Figure 3 is a diagram of a web browser with a URL/query string combination according to one embodiment of the invention.
  • Figure 4 is a flow diagram of call session initiation according to one embodiment of the invention
  • Figure 5 is a flow diagram of call session termination according to one embodiment of the invention.
  • Figure 6 is a message flow diagram of system operation according to one embodiment of the invention.
  • a system may communicate messages from a user agent client (calling party) to a user agent server (called party) relating to various states of a call session.
  • the messages may be used to navigate to a web page, which may be located on a web server system accessible by the user agent server.
  • Information in the messages communicated to the user agent server may be used to retrieve information from a database located on the web server.
  • a web browser on the user agent server may communicate with the web server system to retrieve the data. The data may then be presented back to the called party by the web browser, as a web page, for example.
  • the web page thus displayed on the user agent client (called party) may be useful during the call session.
  • a user agent client (calling party) 10 is connected to a data network 12, which is a packet-based network.
  • the user agent client 10 includes a telephone 16.
  • the user agent client 10 may be a computer system with telephony capability, a standard telephone, a network phone, or a "soft" phone, as examples.
  • the user agent client 10 may also be capable of presenting video and other types of data during a call session, such as in a video conferencing session.
  • the user agent client 10 is the initiator of an Internet Protocol (IP) call session.
  • IP Internet Protocol
  • the designation of "server” and “client” in Figure 1 may be switched, since a system may be a "client” when initiating a call session and a "server” when receiving a request for a call session.
  • the user agent client 10 may also be capable of initiating a call to a Public
  • PSTN Switched Telephone Network
  • the call may be communicated through an intermediary, such as a PSTN gateway (not shown).
  • PSTN gateways provide a connection between circuit-switched networks, such as PSTNs, and packet- based networks, such as the data network 12.
  • the user agent client 10 may even be the PSTN gateway itself, which can route calls between a PSTN-connected telephone and the user agent server 20.
  • a user agent server (called party) 20 coupled to the data network 12 includes equipment 26 to enable communication in a network call session.
  • the user agent server 20 further includes a protocol-aware application program 22 and a web browser program 24.
  • the protocol- aware application 22 is able to process protocol information relating to a call session with the user agent client 10.
  • protocol information relates to messages exchanged between the end points of a call session.
  • Example messages include messages to initiate a call, messages indicating a status of a call, and messages terminating a call.
  • the protocol information may be used by the user agent server 20 to access other information for presentation in a web browser 24.
  • the user agent server 20 is coupled to a web server 40.
  • the web server 40 is part of a community 30 such that the user agent server 20 may access the web server 40 over a private network such as a local area network (LAN).
  • LAN local area network
  • a "community" may refer to any collection of systems that may be grouped together.
  • the community 30 may include an enterprise, such as a corporation or other organization.
  • User systems within the community 30 may be computer systems and the like.
  • the web server 40 may be remotely accessible to the user agent server 20, such as by connection to the data network 12.
  • the web server 40 includes a web server program 42 as well as server storage or database 32.
  • the database 32 is any collection of data elements.
  • the protocol information received by the protocol- aware application software 22 may be used to access the database 32 of the web server 40.
  • a "data network” or “network” may refer to one or more communications networks, channels, links, or paths, and systems or devices (such as routers) used to route data over such networks, channels, links, or paths.
  • Packet- based data networks communicate with packets, datagrams, or other units of data over the data networks. Unlike circuit-switched networks, such as the PSTN, which provide a dedicated end-to-end connection or physical path for the duration of a call session, a packet-based network is one in which the same path may be shared by several network elements.
  • Packet-based networks may be packet-switched networks, such as Internet Protocol (IP) networks, which are based on a connectionless internetwork layer. Packets or other units of data transmitted into a packet-switched data network may travel independently over any path (and possibly over different paths) to a destination point. The packets may even arrive out of order. Routing of the packets is based on one or more addresses carried in each packet. Packet-based networks may also be connection-oriented networks, such as Asynchronous Transfer Mode (ATM) and Frame Relay networks. In a connection-oriented packet-based network, a virtual circuit or connection is established between two end points. In such connection-oriented networks, packets are received in the same order in which they were transmitted.
  • ATM Asynchronous Transfer Mode
  • IP Internet Protocol
  • RFC Request for Comments
  • IPv6 Internet Protocol, Version 6 (IPv6) Specification
  • SIP Session Initiation Protocol
  • IETF Internet Engineering Task Force
  • a version of SIP is described in RFC 2543, entitled “SIP: Session Initiation Protocol," dated 1999.
  • SIP may be used to initiate call sessions as well as to invite members to a session that may have been advertised by some other mechanism, such as electronic mail, newsgroups, web pages, and other mechanisms.
  • Other standards may be employed in further embodiments for controlling call sessions over the data network 12.
  • Such other standards may be any other standard that provides for interactive, real-time streaming communications over the data network 12.
  • One alternate standard is the H.323 Recommendation from the International Telecommunication Union (ITU).
  • a "call” or “call session” refers generally to either an audio (e.g., voice), a video, or a multimedia session established between two or more network elements (and parties using those elements) coupled to the data network 12 (or any other packet-based data network).
  • a call session may also be a text- based chat session, such as an instant massaging session.
  • a "real-time" interactive call session refers to an exchange of data, such as audio and/or video data (or text data), on a substantially real-time basis between two terminals.
  • a session is substantially real time if interaction is occurring between two end points or parties, with a communication from one end point followed relatively quickly by a response or another communication from the other end point, typically within seconds, for example.
  • Interactive call sessions are contrasted with electronic mail messaging, for example, in which a first participant sends a message over a data network to a second participant. No indication is usually provided back to the first participant that the second participant has received the message or that the second participant is even at his or her terminal.
  • an interactive session involves a request followed by some acknowledgment that a called party has accepted the call request. This enables the interactive session in which participants exchange data (e.g., voice, video, and/or text).
  • the protocol-aware application 22 in the user agent server 20 extracts the content of messages relating to states of a call session between the server 20 and the client 22.
  • the content extracted may be used to access the database 32 of the web server 40 for data relevant to the call session.
  • the data may automatically be supplied to the called party as a web page.
  • SIP is utilized to pass telephony-style information or call control messages from the user agent client 10 to the user agent server 20 across the data network 12.
  • SIP is one of several possible protocols that may be used to initiate sessions between two or more entities on a network.
  • a SIP client system includes an application program that is capable of sending SIP requests to perform call requests.
  • a SIP server system includes a server application program that accepts SIP requests to service calls and to send back responses to SIP requests.
  • the user agent client 10 of Figure 1 is thus a SIP client system while the user agent server 20 is a SIP server system.
  • the designation of "client” and “server” may be switched, depending upon who initiates the call session.
  • the user agent server 20 includes a network interface 70 that may be coupled to the data network 12.
  • a network device driver layer 64 Above the network interface 70 are several software layers, including a network device driver layer 64, and transport and network stacks 62 and 68 (e.g., TCP/IP and UDP/IP stacks).
  • TCP is described in RFC 793, entitled “Transmission Control Protocol,” dated September 1981
  • UDP is described in RFC 768, entitled “User Datagram Protocol,” dated August 1980.
  • TCP and UDP are transport layers for managing connections between network elements on an IP network. In further embodiments, other types of transport and network stacks may be used.
  • RTP layer 60 The Real-Time Transport Protocol (RTP) is described in RFC 1889.
  • the RTP layer 60 processes and generates real-time data frames (containing data associated with an audio call, for example).
  • the RTP layer 60 may be connected to an audio coder/decoder (codec) 54, which is coupled to converters 56 (e.g., analog-to-digital and digital-to-analog converters).
  • codec audio coder/decoder
  • converters 56 are coupled to an audio interface 58 that may in turn be coupled to a speaker, headphone, and/or microphone (not shown) for presenting and receiving audio signals.
  • Packets received by the network interface 70 are passed up through the several layers 64, 62 and 68.
  • Control packets are transmitted by the TCP/IP or UDP/IP stack 62 or 68 through a SIP stack 66 to the protocol-aware application software 22.
  • Instructions and data associated with the protocol-aware application software 22 may be stored in a storage device 52, with the instructions executable on a control unit 72.
  • the protocol-aware application software 22 is described in more detail, below.
  • the SIP stack 66 is responsible for processing SIP message communications over the data network 12.
  • the SIP stack 66 is in communication with the protocol-aware application software 22.
  • the SIP stack 66 is generally a state machine that provides parsing, processing, and generation of SIP requests and responses.
  • the protocol-aware application 22 in one embodiment, is a SIP-aware application.
  • the SIP-aware application 22 is coupled to the SIP stack 66 to receive control signaling from the SIP stack 66 or to provide control signaling to the SIP stack 66 for generation of SIP messages.
  • the SIP-aware application 22 may thus make decisions on how to process and respond to received SIP messages.
  • such SIP messages may be messages inviting the user agent server 20 to participate in a call session as well as various response messages indicating various stages of the progress of a call session setup.
  • the protocol-aware application 22 may also receive input from a user, such as through a display 50. Based on the user input, the protocol-aware application 22 may send request or response messages through the SIP stack 66 to the data network 12 indicating initiation of a call, acceptance of a call request, or forwarding of the call to another device.
  • Such tasks performed by the protocol-aware application 22 are examples of call control and status tasks.
  • the protocol- aware application 22 Upon receiving SIP information from the user agent client 10, the protocol- aware application 22 builds a query string coupled with a uniform resource locator (URL).
  • URL uniform resource locator
  • the URL is essentially an address, which identifies a server on the data network 12.
  • the web server 40 may be identified by its URL.
  • An example of a URL/query string combination is illustrated in an address field 100 of Figure 3.
  • the query string includes the relevant SIP information with which the web server 40 may search its database 32.
  • the web server 40 may dynamically build a web page and send the web page to the user agent server 20, such as to be displayed on a web browser 74, viewable on the display 50.
  • the protocol-aware application software 22 is a SIP-based application. Accordingly, the user agent client 10 initiates a call session with the user agent server 20 by sending a SIP INVITE message. Upon receipt of the INVITE message (block 202), the user agent server 20 is notified of the initiation of the call session. In response to the SIP INVITE message, the protocol-aware application software 22 may initiate database retrieval from the web server 40.
  • Header information in the SIP message may be supplied to the protocol- aware application software 22.
  • Examples of information supplied in the SIP header include an identifier of the calling party, an identifier of the called party, and the language of the call session, to name a few.
  • the protocol-aware application software 22 converts the information extracted from the SIP header into a URL and query string combination (block 204), which is sent to the web browser software 24, also in the user agent server 20. Any or all of the supplied SIP header information may be used to create the query string.
  • the SIP information is translated to a format that the web browser software 24 may readily send to the web server software 42, located on the web server 40.
  • the web browser software 24 submits the URL/query string information to the web server 40, such as may be received by the web server software 42 (block 206).
  • the web server software 42 may then parse and use the information to retrieve data from the database 32.
  • the web server software 42 may dynamically build a web page that may convey this as well as information retrieved from the database 32 (block 208).
  • the web server software 42 generates a Hyper-Text Markup Language, or HTML, document.
  • HTML documents are script-like documents that allow web browsers to generate a web page.
  • other languages that enable web browsers to build web pages may be used, such as the Extensible Markup Language (XML).
  • XML Extensible Markup Language
  • the web server software 42 sends the web page, in HTML form, to the user agent server 20, to be retrieved by the web browser software 24 (block 210).
  • the web browser software 24 may then display the web page for viewing on the display 50 by the called party 20.
  • the operations of Figure 4 may be performed substantially simultaneously with the initiation of the call session by the user agent client (caller) 10. Alternatively, the operations of Figure 4 may be performed after the call session has been established. In one embodiment, by the time the caller 10 and called 20 parties are speaking, the web page is already displayed for the called party 20. Further, as the call progresses, additional information may be sent to the web page as needed, in some embodiments. Such additional information may include identification of the calling state (e.g., call on hold, call released, etc.). The change in call state may cause the web page to display different information or to perform further navigation of the database 32.
  • the calling state e.g., call on hold, call released, etc.
  • the language information supplied during the SIP transmission may also be used in generating a customized web page.
  • the web page may be displayed in the relevant language.
  • additional information may be displayed on the web page that is relevant to the particular language being communicated.
  • other information such as the calling party's area code may identify to the called party unique requirements or considerations that may be reflected in the web page.
  • a variety of implementations that associate the supplied information to the database 32 for creation of a customized web page may be possible.
  • the SIP requests IVITE, BYE, etc.
  • SIP responses may be possible.
  • RINGING, OK, etc. may be used as state values representing various states of a call session.
  • the state information may be passed to the web page along with the content of the SIP messages. For example, one web page may be supplied to the called party upon receiving a SIP INVITE message, while another web page may be supplied to the called party upon receiving a SIP BYE message.
  • the protocol-aware application software 22 receives a SIP BYE message (block 252), according to one embodiment.
  • the protocol- aware application 22 extracts information supplied with the BYE message and converts the information to a form understandable by the web browser software 24, e.g., a URL/query string combination (block 254).
  • the web browser software 24 sends the information to the web server software 42 (block 256).
  • the web server software 42 dynamically builds a web page, based upon the new information (block 258).
  • the web server software 42 sends the new web page, such as in HTML form, to the web browser software 24 (block 260).
  • the web browser software 24 may then send a web page to the display 50 on the user agent server 20.
  • the user agent server 20 may operate as part of a reservation system, such as for an airline, a hotel, car rental agency, or other suppliers of travel services.
  • the user agent server 20 may be a technical support department of a company, such as may be sought to diagnose computer problems for calling user agent clients 10.
  • additional information may be included in SIP messages such that more information is available with which to access the database 32.
  • additional information may be in the form of an extension to the SIP header or contained in the SIP message body.
  • a serial number such as of a user agent client's computer may be supplied along with the SIP information.
  • the revision number of a software program located on the user agent client 10 may be supplied with the SIP information.
  • the information transmitted using SIP, or other protocol may be customized to the desires of the user agent server 20. For example, if the call is from a customer seeking technical support, such information may be used to identify the product that the customer is calling about.
  • the user agent server 20 may receive an incoming SIP INVITE without having a web browser loaded.
  • a web browser may be launched in response to a SIP INVITE message, or, alternatively, a distinct graphical user interface may be presented instead of a web browser.
  • additional software may be necessary for communication between the user agent server 20 and the web server 40, since no web server/web browser environment exists.
  • the use of the SIP or other IP telephony protocol to transmit data that may be used to access a database is not dependent on the availability of web-based software.
  • example message flows involving the user agent client 10, the user agent server 20, and the web server 40 of Figure 1 are illustrated according to one embodiment.
  • the example flows are SIP messaging flows, as described in Figures 4 and 5.
  • other protocols such as H.323 may be employed.
  • the user agent client 10 sends an INVITE message (at 400) to the user agent server 20.
  • the INVITE message is defined by SIP and indicates that the user agent server 20 is being invited to participate in a call session.
  • the user agent server 20 Upon receiving the INVTTE message, the user agent server 20 sends the URL/query string combination to the web server 40 (at 414) to provoke access of the database 32 by the web server software 42.
  • the user agent server 20 Before acceptance of the call request, the user agent server 20 responds with a SIP RINGING message to the user agent client 10 (at 402). Once the call is accepted, the user agent server 20 may respond with a SIP OK message (at 404) to the user agent client 10 to indicate that the request has succeeded. Meanwhile, from the web server 40, an HTML web page is sent to the user agent server 20 (at 416). After receipt of the OK response, the user agent client 10 then sends (at 406) an ACK request, confirming that the user agent server 20 has received a final response to an INVITE request. Upon receipt of the ACK request, further exchanges of protocol messaging establishes a call session (at 408) in which exchanges between the user agent client 10 and the user agent server 20 may be made.
  • the HTML web page may already be displayed on the user agent server 20.
  • the user agent client 10 may send a BYE request (at 410).
  • a URL/query string may be communicated to the web server 40 by the user agent server 20 (at 418).
  • the user agent server 20 then returns an OK response (at 412) back to the user agent client 10 in response to the BYE request.
  • the web server 40 submits an HTML web page (at 420) to the user agent server 20.
  • the called party located at the user agent server 20, may be provided with a final web page associated with the calling party 10.
  • the storage device 52 of Figure 2 may include one or more machine-readable storage media for storing data and instructions.
  • the storage media may include different forms of memory including semiconductor memory devices such as dynamic or static random access memories (DRAMs or SRAMs), erasable and programmable read-only memories (EPROMs), electrically erasable and programmable read-only memories (EEPROMs) and flash memories; magnetic disks such as fixed, floppy and removable disks; other magnetic media including tape; and optical media such as compact disks (CDs) or digital video disks (DVDs).
  • DRAMs or SRAMs dynamic or static random access memories
  • EPROMs erasable and programmable read-only memories
  • EEPROMs electrically erasable and programmable read-only memories
  • flash memories such as fixed, floppy and removable disks
  • magnetic media such as fixed, floppy and removable disks
  • optical media such as compact disks (CDs) or digital video disks (DVDs).
  • the instructions of the protocol-aware application 22 as well as the other network layers 62, 68 and 66 of Figure 2 may be loaded or transported to the user agent server 20 in one of many different ways.
  • code segments including instructions stored on floppy disks, CD or DVD media, a hard disk, or transported through a network interface card, modem, or other interface device may be loaded into the system and executed as corresponding software routines, modules, or layers.
  • data signals that are embodied in carrier waves (transmitted over telephone lines, network lines, wireless links, cables, and the like) may communicate the code segments, including instructions, to the user agent server 20.
  • carrier waves may be in the form of electrical, optical, acoustical, electromagnetic, or other types of signals.

Abstract

Un serveur agent (20) reçoit un message relatif à une session de communication d'un client agent (10) relié à un réseau (12) de données. Le serveur agent (20) extrait des informations du message, les envoie à un navigateur sur le web (24) et actualise les données dudit navigateur (24) en fonction de ces informations. Ces données, qui peuvent être présentées dans une page du web ou comprendre des informations relatives à la session de communication, sont fournies automatiquement en temps réel.
EP01937746A 2000-05-25 2001-05-25 Traitement d'informations sur des sessions de communication Withdrawn EP1293088A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US57831600A 2000-05-25 2000-05-25
US578316 2000-05-25
PCT/US2001/017101 WO2001091433A2 (fr) 2000-05-25 2001-05-25 Traitement d'informations sur des sessions de communication

Publications (1)

Publication Number Publication Date
EP1293088A2 true EP1293088A2 (fr) 2003-03-19

Family

ID=24312344

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01937746A Withdrawn EP1293088A2 (fr) 2000-05-25 2001-05-25 Traitement d'informations sur des sessions de communication

Country Status (3)

Country Link
EP (1) EP1293088A2 (fr)
AU (1) AU2001263450A1 (fr)
WO (1) WO2001091433A2 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2838231B1 (fr) * 2002-04-08 2004-07-16 France Telecom Systeme de commande automatique d'affichage de pages d'information
EP1424824A1 (fr) * 2002-11-27 2004-06-02 Alcatel Système de voix-sur-Internet-Protocole avec capabilité de distribution d'information

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1093281A3 (fr) * 1999-10-15 2002-11-06 Nortel Networks Limited Réacheminement d'un appel à partir d'un appareil portable
US7139813B1 (en) * 1999-11-01 2006-11-21 Nokia Networks Oy Timedependent hyperlink system in videocontent

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0191433A3 *

Also Published As

Publication number Publication date
AU2001263450A1 (en) 2001-12-03
WO2001091433A3 (fr) 2002-07-18
WO2001091433A2 (fr) 2001-11-29

Similar Documents

Publication Publication Date Title
US9008294B2 (en) Providing calling party information in a request to establish a call session
EP1275239B1 (fr) Procede permettant de fournir des informations d'annonce sur commande afin d'etablir des sessions d'appel interactifs
US7266591B1 (en) Providing content delivery during a call hold condition
EP1266505B1 (fr) Communications textuelles via un reseau de donnees
EP1266516B1 (fr) Établissement d'appels audio interactifs en temps réel par un ordinateur pour le compte d'un téléphone d'un réseau de données à commutation de paquets
US9294518B2 (en) Method to process a call request
US7469299B2 (en) Bridging user agent and a proxy server for supporting network services
EP1102498B1 (fr) Services téléphoniques dans un réseau de communications
WO2005010712A2 (fr) Procede et systeme permettant de supprimer les flux multimedia anticipes dans un reseau de communication
US7463619B1 (en) Launching a web browser in response to a message relating to communications sessions
EP1139631A1 (fr) Procédé pour l'initiation d'un transfer de données d'un serveur vers un client
EP1293088A2 (fr) Traitement d'informations sur des sessions de communication
Mortada et al. Internet telephony signaling

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20021218

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB

17Q First examination report despatched

Effective date: 20050309

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20050729