US20210297408A1 - Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser - Google Patents

Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser Download PDF

Info

Publication number
US20210297408A1
US20210297408A1 US17/339,069 US202117339069A US2021297408A1 US 20210297408 A1 US20210297408 A1 US 20210297408A1 US 202117339069 A US202117339069 A US 202117339069A US 2021297408 A1 US2021297408 A1 US 2021297408A1
Authority
US
United States
Prior art keywords
sip
web application
application server
server address
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US17/339,069
Inventor
Eleni Saridaki
Elias Balafoutis
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.)
RingCentral Inc
Original Assignee
RingCentral Inc
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 RingCentral Inc filed Critical RingCentral Inc
Priority to US17/339,069 priority Critical patent/US20210297408A1/en
Assigned to UNIFY PATENTE GMBH & CO. KG reassignment UNIFY PATENTE GMBH & CO. KG ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: UNIFY GMBH & CO. KG
Assigned to RINGCENTRAL, INC. reassignment RINGCENTRAL, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: RINGCENTRAL IP HOLDINGS, INC.
Assigned to RINGCENTRAL IP HOLDINGS, INC. reassignment RINGCENTRAL IP HOLDINGS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: UNIFY SOFTWARE AND SOLUTIONS GMBH & CO. KG AND UNIFY PATENTE GMBH & CO. KG
Assigned to UNIFY GMBH & CO. KG reassignment UNIFY GMBH & CO. KG ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BALAFOUTIS, Elias, SARIDAKI, ELENI
Publication of US20210297408A1 publication Critical patent/US20210297408A1/en
Assigned to BANK OF AMERICA, N.A., AS COLLATERAL AGENT reassignment BANK OF AMERICA, N.A., AS COLLATERAL AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: RINGCENTRAL, INC.
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1108—Web based protocols, e.g. webRTC
    • H04L61/309—
    • H04L65/1006—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1053—IP private branch exchange [PBX] functionality entities or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H04L65/608—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/39—Globally routable user-agent uniform resource identifier [GRUU] for the session initiation protocol [SIP]

Definitions

  • Embodiments relate to methods and systems for creating a virtual SIP user agent by use of a webRTC enabled web browser.
  • Voice and video communication over the web emerges as a new real time communication technology in both a consumer as well as enterprise communication environment (open source projects such as Web Real Time Communication (“WebRTC”)).
  • WebRTC Web Real Time Communication
  • Reuse of user resources such as a telephone number across legacy/VoIP communication devices as well as web based terminals is essential for the seamless integration of web based real time communication into an existing legacy telephony or VoIP environment.
  • a method for creating a virtual SIP user agent by use of a webRTC enabled web browser 200 .
  • the method comprises a user logging in to a web application server 400 via a webRTC enabled web browser 200 .
  • the method further comprises that the web application server 400 uses the logged on user identity to lookup an associated SIP user identity along with a registrar server address; and that the web application server 400 initiates a SIP registration procedure using its IP address as the registered contact.
  • web browser (or webbrowser or browser) shall refer to any kind of software, by which a user may communicate with a web application server. More specifically this term comprises any kind of software application for retrieving, presenting, and traversing information resources on the World Wide Web.
  • An information resource is identified by a Uniform Resource Identifier (URI) and may be a web page, image, video, or other piece of content.
  • URI Uniform Resource Identifier
  • Hyperlinks present in resources enable users easily to navigate their browsers to related resources.
  • a web browser can also be defined as an application software or program designed to enable users to access, retrieve and view documents and other resources on the Internet.
  • browsers are primarily intended to use the World Wide Web, they can also be used to access information provided by web servers in private networks or files in file systems. Important examples of web browsers are Firefox, Google Chrome, Internet Explorer, Opera, and Safari.
  • WebRTC Web Real-Time Communication
  • W3C World Wide Web Consortium
  • IETF World Wide Web Consortium
  • the goal of WebRTC is to enable applications such as voice calling, video chat and P2P file sharing without plugins.
  • the method is characterized by a login using a username and password authentication.
  • a user is typically required to authenticate oneself with a password or other credentials for the purposes of accounting, security, logging, and resource management.
  • the method is characterized by an authentication with a single sign-on, e.g. with a corporate entitlement system.
  • Single sign-on SSO is a property of access control of multiple related, but independent software systems. With this property a user logs in once and gains access to all systems without being prompted to log in again at each of them.
  • Single sign-off is the property whereby a single action of signing out terminates access to multiple software systems. As different applications and resources support different authentication mechanisms, single sign-on has to internally translate to and store different credentials compared to what is used for initial authentication.
  • the method is characterized in that the associated SIP user identity or the registrar server addresses are at least partly supplied by the user.
  • a SIP user agent (UA) is a logical network end-point used to create or receive SIP messages and thereby manage a SIP session.
  • a SIP UA can perform the role of a User Agent Client (UAC), which sends SIP requests, and the User Agent Server (UAS), which receives the requests and returns a SIP response. These roles of UAC and UAS only last for the duration of a SIP transaction.
  • UAC User Agent Client
  • UAS User Agent Server
  • a SIP phone is a SIP user agent that provides the traditional call functions of a telephone, such as dial, answer, reject, hold/unhold, and call transfer.
  • SIP phones may be implemented as a hardware device or as a soft phone.
  • SIP Session Initiation Protocol
  • SIP registrars are logical elements, and are commonly co-located with SIP proxies.
  • SIP is a text-based protocol with syntax similar to that of HTTP.
  • requests and responses There are two different types of SIP messages: requests and responses.
  • the first line of a request has a method, defining the nature of the request, and a Request-URI, indicating where the request should be sent.
  • the first line of a response has a response code.
  • RFC 3261 defines the following methods:
  • REGISTER Used by a UA to indicate its current IP address and the URLs for which it would like to receive calls.
  • INVITE Used to establish a media session between user agents.
  • CANCEL Terminates a pending request.
  • BYE Terminates a session between two users in a conference.
  • OPTIONS Requests information about the capabilities of a caller, without setting up a call.
  • the method is characterized in that the associated SIP user identity or the registrar server addresses are at least partly retrieved by a user identity management system.
  • An identity management system refers to an information system, or to a set of technologies that can be used for enterprise or cross-network Identity management.
  • Identity management describes the management of individual identities, their authentication, authorization, roles, and privileges within or across system and enterprise boundaries with the goal of increasing security and productivity while decreasing cost, downtime, and repetitive tasks.
  • Identity Management and “Access and Identity Management” (or AIM) are terms that are frequently used interchangeably under the title of Identity management while Identity management itself falls the umbrella of IT Security.
  • Identity management systems, products, applications, and platforms are commercial Identity management solutions implemented for enterprises and organizations.
  • the method is characterized in that the web application services 400 assume and maintains in the database 500 user SIP credentials 001 (e.g. SIP registrar address, E.164 number or SIP username, digest authentication password) and propagate this information to the user SIP SBC/Proxy/Registrar 700 via an appropriate SIP request interface, e.g. a REGISTER message 003 .
  • user SIP credentials 001 e.g. SIP registrar address, E.164 number or SIP username, digest authentication password
  • the present invention may also be implemented by a system for using a method according to the present invention or one of its embodiments, the system comprising a web client running on a webRTC enabled web browser 200 , a web application server 400 , a SIP registrar server and a SIP server 700 .
  • FIG. 1 illustrates a preferred system configuration and/or network architecture of a system according to the present invention.
  • FIG. 2 illustrates the WebRTC authentication via SIP message sequence according to a preferred embodiment of the invention.
  • FIG. 3 illustrates the SIP initiated connection to a WebRTC/SIP destination according to a preferred embodiment of the invention.
  • FIG. 4 illustrates the WebRTC initiated connection to a SIP destination according to a preferred embodiment of the invention.
  • a user logs in to the web application server 400 via the web client interface 200 .
  • this may be a username and password authentication.
  • authentication may be done with single sign-on with a corporate entitlement system.
  • the web application server preferably uses the logged on user identity to lookup an associated SIP user identity along with a registrar server address.
  • this information can be partly supplied by the user (self management).
  • this information is retrieved by a user identity management system.
  • the web application server 400 will preferably initiate a SIP registration procedure using its IP address as the registered contact.
  • SIP users authentication and authorization methods e.g. via REGISTER and SUBSCRIBE requests, can be used implicitly for web based communication enablement especially if the user already owns a SIP address/E.164 number.
  • the identity of the web media client user and validation of user accessibility options is preferably covered indirectly in the SIP domain, simply if the web application services 400 assume and maintains in the database 500 user SIP credentials 001 (e.g. SIP registrar address, E.164 number or SIP username, digest authentication password) and propagate this information to the user SIP SBC/Proxy/Registrar 700 via the appropriate SIP request interface (REGISTER message) 003 at user web login on a secure session. Addressing the user is feasible through E.164 numbering convention or SIP URI, or other valid URL identifiers like email etc, as each individual usually is the owner of various system accounts and identifiers.
  • E.164 numbering convention or SIP URI or other valid URL identifiers like email etc, as each individual usually is the owner of various system accounts and identifiers.
  • the web server will preferably be registered as another contact for the authenticated user, as long as the web server belongs to a trusted domain to the SIP domain. Therefore a new call received against this SIP user identity can also reach and be handled at the user's web application enriched with WebRTC capabilities, in parallel to other existing authorized contacts that are registered against this SIP user identity such as IP phone device or IP soft client or GWs (SIP Forking feature) ( FIG. 3 ).
  • the user preferably has the choice to select his preferred medium for audio or video communication: browser 200 or SIP endpoint ( 300 ) or even a smart phone/tablet 100 , as incoming traffic will preferably reach both SIP 300 and WebRTC 100 , 200 enabled clients, due to this parallel registration and subscription on SIP services.
  • the web application server 400 receives the incoming call it preferably extracts the media description and offers the call to the user at the web browser 200 just as if this call is a normal webRTC offer as defined in the respective W3C draft. From this point on, the role of the web application server is preferably that of a SIP user agent in the sense that it is responsible for the handling of the communication session.
  • negotiation on the media description as well as connectivity (ICE) remains a responsibility of the web browser. Once the negotiation succeeds an RTP communication between the web browser and the initiating device is preferably started.
  • WebRTC session could reach this way another VoIP 900 or PSTN telephony user 1000 and have the originator user's SIP identifiers (names and numbers) presented to the other side as shown in FIG. 4 .
  • Device selection may be still a user's choice, but in addition can be system defined based on user's selected destination: WebRTC destination 600 will preferably be receiving WebRTC based calls, while SIP destinations 900 will preferably be reached though SIP session establishment initiated by the web application.
  • the web application server media management services 400 work similar to a Session Board Controller or Gateway supporting the transition from the WebRTC domain to the SIP domain.
  • the user may seamlessly perform SIP or webRTC calls without experiencing any difference in the user interface.
  • the disclosure of the present invention focuses on the aspect of integration methods of a pure web browser media communication based on WebRTC standardization and existing session based communication interfaces like SIP.
  • An example architecture shown in FIG. 1 comprises basically of a web client running on a webRTC enabled web browser 200 , a web application server 400 , a SIP registrar server and a SIP server 700 .
  • a single server may have the role of both the SIP server and the SIP registrar server.
  • the web application server may include media reception and transmission facilities.
  • Voice and video communication over the web emerges as a new real time communication technology in both a consumer as well as enterprise communication environment (open source projects such as Web Real Time Communication (“WebRTC”)).
  • WebRTC Web Real Time Communication
  • the reuse of user resources such as a telephone number across legacy/VoIP communication devices as well as web based terminals is essential for the seamless integration of web based real time communication into an existing legacy telephony or VoIP environment.
  • the present invention discloses methods and procedures that allow the reuse of a user identity such as a telephone number or a user URL in both web based real time communication and legacy/VoIP Communication systems.
  • the user of a web application that offers web based real time communication services is offered the option to answer an incoming call against a given telephone number via a web based client interface while this call is also offered to other VoIP or legacy devices of this user.
  • a call that is initiated via a web browser towards other users shows a dialable user identity that can be called back.
  • potential media codec incompatibilities between web media-enabled clients and existing VoIP or legacy telephony clients are also an important aspect to cover.
  • This goal is preferably achieved without a need for special network configuration such routing rules in any of the existing communication infrastructure.
  • the web browser (via html/js client application) has the role of a media termination endpoint while of the role of the web server preferably is to pass on the media description that is required prior to the initiation of a media stream between two peers.
  • a web application server is considered a communication domain that may interface with other communication domains including legacy telecommunication domains via standard or proprietary protocols.

Abstract

A method for creating a virtual SIP user agent by use of a webRTC enabled web browser comprises a user logging in to a web application server via a webRTC enabled web browser. The web application server uses the logged on user identity to lookup an associated SIP user identity along with a registrar server address and the web application server initiates a SIP registration procedure using its IP address as the registered contact.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is the United States national stage under 35 U.S.C. § 371 of PCT International Application No. PCT/EP2012/004403, filed on Oct. 19, 2012.
    • BACKGROUND OF THE INVENTION Field of the Invention
  • Embodiments relate to methods and systems for creating a virtual SIP user agent by use of a webRTC enabled web browser.
    • Background of the Related Art
  • Voice and video communication over the web emerges as a new real time communication technology in both a consumer as well as enterprise communication environment (open source projects such as Web Real Time Communication (“WebRTC”)). Reuse of user resources such as a telephone number across legacy/VoIP communication devices as well as web based terminals is essential for the seamless integration of web based real time communication into an existing legacy telephony or VoIP environment.
    • BRIEF SUMMARY OF THE INVENTION
  • According to the present invention a method is provided for creating a virtual SIP user agent by use of a webRTC enabled web browser 200. The method comprises a user logging in to a web application server 400 via a webRTC enabled web browser 200. The method further comprises that the web application server 400 uses the logged on user identity to lookup an associated SIP user identity along with a registrar server address; and that the web application server 400 initiates a SIP registration procedure using its IP address as the registered contact.
  • In connection with the present description of the invention or preferred embodiments of the invention, the term web browser (or webbrowser or browser) shall refer to any kind of software, by which a user may communicate with a web application server. More specifically this term comprises any kind of software application for retrieving, presenting, and traversing information resources on the World Wide Web. An information resource is identified by a Uniform Resource Identifier (URI) and may be a web page, image, video, or other piece of content. Hyperlinks present in resources enable users easily to navigate their browsers to related resources. A web browser can also be defined as an application software or program designed to enable users to access, retrieve and view documents and other resources on the Internet. Although browsers are primarily intended to use the World Wide Web, they can also be used to access information provided by web servers in private networks or files in file systems. Important examples of web browsers are Firefox, Google Chrome, Internet Explorer, Opera, and Safari.
  • WebRTC (Web Real-Time Communication) is an API definition being drafted by the World Wide Web Consortium (W3C), with a mailing list created in April 2011 and jointly in the IETF with a working group chartered in May 2011. It is also the name of framework that was open sourced on Jun. 1, 2011, which implements early versions of the standard and allows web browsers to conduct real-time communication. The goal of WebRTC is to enable applications such as voice calling, video chat and P2P file sharing without plugins.
  • According to a preferred embodiment of the invention, the method is characterized by a login using a username and password authentication. To log in to an account, a user is typically required to authenticate oneself with a password or other credentials for the purposes of accounting, security, logging, and resource management.
  • According to a preferred embodiment of the invention, the method is characterized by an authentication with a single sign-on, e.g. with a corporate entitlement system. Single sign-on (SSO) is a property of access control of multiple related, but independent software systems. With this property a user logs in once and gains access to all systems without being prompted to log in again at each of them. Conversely, Single sign-off is the property whereby a single action of signing out terminates access to multiple software systems. As different applications and resources support different authentication mechanisms, single sign-on has to internally translate to and store different credentials compared to what is used for initial authentication.
  • According to a preferred embodiment of the invention, the method is characterized in that the associated SIP user identity or the registrar server addresses are at least partly supplied by the user. A SIP user agent (UA) is a logical network end-point used to create or receive SIP messages and thereby manage a SIP session. A SIP UA can perform the role of a User Agent Client (UAC), which sends SIP requests, and the User Agent Server (UAS), which receives the requests and returns a SIP response. These roles of UAC and UAS only last for the duration of a SIP transaction. A SIP phone is a SIP user agent that provides the traditional call functions of a telephone, such as dial, answer, reject, hold/unhold, and call transfer. SIP phones may be implemented as a hardware device or as a soft phone. As vendors increasingly implement SIP as a standard telephony platform, often driven by 4G efforts, the distinction between hardware-based and software-based SIP phones is being blurred and SIP elements are implemented in the basic firmware functions of many IP-capable devices.
  • A server that accepts REGISTER requests and places the information it receives in those requests into the location service for the domain it handles which registers one or more IP addresses to a certain SIP URI, indicated by the sip: scheme, although other protocol schemes are possible (such as tel:). More than one user agent can register at the same URI, with the result that all registered user agents will receive a call to the SIP URI. SIP registrars are logical elements, and are commonly co-located with SIP proxies.
  • SIP is a text-based protocol with syntax similar to that of HTTP. There are two different types of SIP messages: requests and responses. The first line of a request has a method, defining the nature of the request, and a Request-URI, indicating where the request should be sent. The first line of a response has a response code. For SIP requests, RFC 3261 defines the following methods:
  • REGISTER: Used by a UA to indicate its current IP address and the URLs for which it would like to receive calls.
  • INVITE: Used to establish a media session between user agents.
  • ACK: Confirms reliable message exchanges.
  • CANCEL: Terminates a pending request.
  • BYE: Terminates a session between two users in a conference.
  • OPTIONS: Requests information about the capabilities of a caller, without setting up a call.
  • According to a preferred embodiment of the invention, the method is characterized in that the associated SIP user identity or the registrar server addresses are at least partly retrieved by a user identity management system. An identity management system refers to an information system, or to a set of technologies that can be used for enterprise or cross-network Identity management. Identity management (IdM) describes the management of individual identities, their authentication, authorization, roles, and privileges within or across system and enterprise boundaries with the goal of increasing security and productivity while decreasing cost, downtime, and repetitive tasks. The terms “Identity Management” and “Access and Identity Management” (or AIM) are terms that are frequently used interchangeably under the title of Identity management while Identity management itself falls the umbrella of IT Security. Identity management systems, products, applications, and platforms are commercial Identity management solutions implemented for enterprises and organizations.
  • According to a preferred embodiment of the invention, the method is characterized in that the web application services 400 assume and maintains in the database 500 user SIP credentials 001 (e.g. SIP registrar address, E.164 number or SIP username, digest authentication password) and propagate this information to the user SIP SBC/Proxy/Registrar 700 via an appropriate SIP request interface, e.g. a REGISTER message 003.
  • The present invention may also be implemented by a system for using a method according to the present invention or one of its embodiments, the system comprising a web client running on a webRTC enabled web browser 200, a web application server 400, a SIP registrar server and a SIP server 700.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 illustrates a preferred system configuration and/or network architecture of a system according to the present invention.
  • FIG. 2 illustrates the WebRTC authentication via SIP message sequence according to a preferred embodiment of the invention.
  • FIG. 3 illustrates the SIP initiated connection to a WebRTC/SIP destination according to a preferred embodiment of the invention.
  • FIG. 4 illustrates the WebRTC initiated connection to a SIP destination according to a preferred embodiment of the invention.
    •  DETAILED DESCRIPTION OF THE INVENTION
  • According to a preferred embodiment of the present invention, a user logs in to the web application server 400 via the web client interface 200. In some embodiments this may be a username and password authentication. In other embodiments authentication may be done with single sign-on with a corporate entitlement system. The web application server preferably uses the logged on user identity to lookup an associated SIP user identity along with a registrar server address. In this embodiment this information can be partly supplied by the user (self management). In other embodiments of the present invention this information is retrieved by a user identity management system.
  • Once the SIP user identity for the logged on user is found the web application server 400 will preferably initiate a SIP registration procedure using its IP address as the registered contact. SIP users authentication and authorization methods e.g. via REGISTER and SUBSCRIBE requests, can be used implicitly for web based communication enablement especially if the user already owns a SIP address/E.164 number.
  • So the identity of the web media client user and validation of user accessibility options is preferably covered indirectly in the SIP domain, simply if the web application services 400 assume and maintains in the database 500 user SIP credentials 001 (e.g. SIP registrar address, E.164 number or SIP username, digest authentication password) and propagate this information to the user SIP SBC/Proxy/Registrar 700 via the appropriate SIP request interface (REGISTER message) 003 at user web login on a secure session. Addressing the user is feasible through E.164 numbering convention or SIP URI, or other valid URL identifiers like email etc, as each individual usually is the owner of various system accounts and identifiers.
  • This way the web server will preferably be registered as another contact for the authenticated user, as long as the web server belongs to a trusted domain to the SIP domain. Therefore a new call received against this SIP user identity can also reach and be handled at the user's web application enriched with WebRTC capabilities, in parallel to other existing authorized contacts that are registered against this SIP user identity such as IP phone device or IP soft client or GWs (SIP Forking feature) (FIG. 3). The user preferably has the choice to select his preferred medium for audio or video communication: browser 200 or SIP endpoint (300) or even a smart phone/tablet 100, as incoming traffic will preferably reach both SIP 300 and WebRTC 100, 200 enabled clients, due to this parallel registration and subscription on SIP services.
  • Once the web application server 400 receives the incoming call it preferably extracts the media description and offers the call to the user at the web browser 200 just as if this call is a normal webRTC offer as defined in the respective W3C draft. From this point on, the role of the web application server is preferably that of a SIP user agent in the sense that it is responsible for the handling of the communication session. Negotiation on the media description as well as connectivity (ICE) remains a responsibility of the web browser. Once the negotiation succeeds an RTP communication between the web browser and the initiating device is preferably started.
  • Vice versa a WebRTC session could reach this way another VoIP 900 or PSTN telephony user 1000 and have the originator user's SIP identifiers (names and numbers) presented to the other side as shown in FIG. 4. Device selection may be still a user's choice, but in addition can be system defined based on user's selected destination: WebRTC destination 600 will preferably be receiving WebRTC based calls, while SIP destinations 900 will preferably be reached though SIP session establishment initiated by the web application.
  • In this case, the web application server media management services 400 work similar to a Session Board Controller or Gateway supporting the transition from the WebRTC domain to the SIP domain. The user may seamlessly perform SIP or webRTC calls without experiencing any difference in the user interface.
  • The disclosure of the present invention focuses on the aspect of integration methods of a pure web browser media communication based on WebRTC standardization and existing session based communication interfaces like SIP. Two main aspects exist covering for the smooth interoperability with existing networks in a trusted network environment and seamless user experience:
  • 1) Supporting in a WebRTC enabled communication application 400 users that already own one or more existing SIP accounts (E.164 numbers potentially as well) and
  • 2) Establishing a real time audio and video communication between web applications and other VoIP or even legacy PSTN systems through stream trans-coding mechanics.
  • An example architecture shown in FIG. 1 comprises basically of a web client running on a webRTC enabled web browser 200, a web application server 400, a SIP registrar server and a SIP server 700. In some embodiments a single server may have the role of both the SIP server and the SIP registrar server. Also in some embodiments the web application server may include media reception and transmission facilities.
  • Voice and video communication over the web emerges as a new real time communication technology in both a consumer as well as enterprise communication environment (open source projects such as Web Real Time Communication (“WebRTC”)). The reuse of user resources such as a telephone number across legacy/VoIP communication devices as well as web based terminals is essential for the seamless integration of web based real time communication into an existing legacy telephony or VoIP environment.
  • The present invention discloses methods and procedures that allow the reuse of a user identity such as a telephone number or a user URL in both web based real time communication and legacy/VoIP Communication systems.
  • In particular the user of a web application that offers web based real time communication services is offered the option to answer an incoming call against a given telephone number via a web based client interface while this call is also offered to other VoIP or legacy devices of this user. In addition, a call that is initiated via a web browser towards other users (either web or VoIP or legacy) shows a dialable user identity that can be called back. On this topic, potential media codec incompatibilities between web media-enabled clients and existing VoIP or legacy telephony clients are also an important aspect to cover.
  • In addition due to the nature of web real time transmission, peer to peer connectivity, video teleconference connections or general multi-party connections can be established up to a certain number of participants. The mesh topology and personal pc media processing performance limitations for media stream handling. Lastly there is no defined connection between the international public telecommunication numbering plan E.164 and WebRTC (address reference is purely URL defined).
  • This goal is preferably achieved without a need for special network configuration such routing rules in any of the existing communication infrastructure.
  • The use of web based real time communication with voice and video has been very limited in the prior art for numerous reasons including the lack of native support by the web browsers and the diversity of implementation of web browser plug-ins. Standardization activities along with prototype implementation of the early standardization steps are ongoing but the interworking between web application servers that offer web based real time communication services and other telecommunication equipment such as VoIP switch and GW have been left outside the standardization activities up to now.
  • In this architecture, the web browser (via html/js client application) has the role of a media termination endpoint while of the role of the web server preferably is to pass on the media description that is required prior to the initiation of a media stream between two peers.
  • In overall a web application server is considered a communication domain that may interface with other communication domains including legacy telecommunication domains via standard or proprietary protocols.
  • In this environment the users of a web based real time communication platform can be reached from external or reach external parties depending on the configured networking and routing rules. The potential of reuse of resources such as a telephone number is greatly reduced and requires configuration of networking and routing rules.
    • LIST OF REFERNCE SYMBOLS USED IN THE DRAWINGS
    • 001 transmission of user SIP credentials (e.g. SIP registrar address, E.164 number or SIP username, digest authentication password), user login
    • 002 retrieve user SIP credentials
    • 003 SIP request interface (Register message), SIP: register (user SIP credentials)
    • 004 SIP: 200 OK
    • 005 user registered in SIP
    • 006 successful SIP registration
    • 007 new peer connection media offer
    • 008 retrieve user A SIP credentials
    • 009 SIP: INVITE/SDP offer
    • 010 SIP: 180/200 OK/SDP Answer
    • 011 Check media compatibility
    • 012 Signaling message: Media Answer
    • 013 SIP: INVITE/SDP offer (from A to B)
    • 014 SIP: INVITE/SDP offer (from A to B)
    • 015 SIP: INVITE/SDP offer (from A to B)
    • 016 Retrieve user B data
    • 017 new peer connection media offer
    • 018 Signaling Message: Media Answer
    • 019 check media compatibility
    • 020 SIP: 1810/200 OK/SDP Answer
    • 021 SIP: 1810/200 OK/SDP Answer
    • 022 SIP: Cancel
    • 023 webRTC
    • 024 SIP
    • 025 ISDN
    • 026 media stream
    • 100 smart phone or tablet, WebRTC enabled client
    • 200 WebRTC enabled web browser, web client interface, user browser WebRTC application, user browser B, WebRTC enabled client
    • 300 SIP endpoint, SIP device B
    • 400 WebRTC enabled communication application, web application server, web application server media management services, web media server
    • 401 authentication service
    • 402 data management
    • 403 webRTC SIP mediation service
    • 404 webRTC service
    • 500 database (of user SIP credentials)
    • 600 WebRTC destination
    • 700 SIP server, SIP (SBC/Proxy/) registrar
    • 800 SIP/PSTN GW
    • 900 VoIP telephony user, SIP destination, SIP device A
    • 1000 PSTN telephony user, traditional device

Claims (21)

1-7. (canceled)
8. A computer-implemented method, comprising:
receiving, using a web application server, a user login sent via an WebRTC-enabled web browser of a first device;
identifying a Session Initiation Protocol (SIP) user identity associated with the user login;
in response to identifying the SIP user identity, initiating a SIP registration procedure using a web application server address as a registered contact; and
initiating a communication session between the WebRTC-enabled web browser of the first device and a second device.
9. The computer-implemented method of claim 8, wherein initiating a communication session comprises initiating a SIP communication session.
10. The computer-implemented method of claim 8, further comprising:
identifying a SIP registrar server address; and
wherein initiating the SIP registration procedure is in response to identifying the SIP registrar server address.
11. The computer-implemented method of claim 8, further comprising:
receiving the SIP user identity or a SIP registrar server address from a user; and
storing the SIP user identity or the SIP registrar server address in a database associated with the web application server.
12. The computer-implemented method of claim 8, wherein identifying the SIP user identity or a SIP registrar server address comprises identifying using a user identity management system.
13. The computer-implemented method of claim 8, further comprising:
registering the web application server address as the registered contact.
14. The computer-implemented method of claim 8, further comprising:
selecting, using the web application server, one or more devices to which to route an incoming call based on a pre-selected destination;
extracting a media description associated with the incoming call; and
offering the incoming call through the WebRTC-enabled web browser.
15. A non-transitory, computer-readable medium storing instructions that, when executed by a processor, cause:
receiving, using a web application server, a user login sent via an WebRTC-enabled web browser of a first device;
identifying a Session Initiation Protocol (SIP) user identity and a SIP registrar server address associated with the user login;
in response to identifying the SIP user identity and the SIP registrar server address, initiating a SIP registration procedure using a web application server address as a registered contact; and
initiating a communication session between the WebRTC-enabled web browser of the first device and a second device.
16. The non-transitory, computer-readable medium of claim 15, wherein initiating a communication session comprises initiating a SIP communication session.
17. The non-transitory, computer-readable medium of claim 15, storing further instructions that, when executed by the processor, cause:
identifying a SIP registrar server address; and
wherein initiating the SIP registration procedure is in response to identifying the SIP registrar server address.
18. The non-transitory, computer-readable medium of claim 15, storing further instructions that, when executed by the processor, cause:
receiving the SIP user identity or a SIP registrar server address from a user; and
storing the SIP user identity or the SIP registrar server address in a database associated with the web application server.
19. The non-transitory, computer-readable medium of claim 15, wherein identifying the SIP user identity or a SIP registrar server address comprises identifying using a user identity management system.
20. The non-transitory, computer-readable medium of claim 15, storing further instructions that, when executed by the processor, cause:
registering the web application server address as the registered contact.
21. The non-transitory, computer-readable medium of claim 15, storing further instructions that, when executed by the processor, cause:
selecting, using the web application server, one or more devices to which to route an incoming call based on a pre-selected destination;
extracting a media description associated with the incoming call; and
offering the incoming call through the WebRTC-enabled web browser.
22. A web application server, comprising:
a processor; and
a memory storing instructions that, when executed by the processor, cause:
receiving a user login sent via an WebRTC-enabled web browser of a first device;
identifying a Session Initiation Protocol (SIP) user identity associated with the user login;
in response to identifying the SIP user identity, initiating a SIP registration procedure using a web application server address as a registered contact; and
initiating a communication session between the WebRTC-enabled web browser of the first device and a second device.
23. The web application server of claim 22, wherein initiating a communication session comprises initiating a SIP communication session.
24. The web application server of claim 22, wherein the memory stores further instructions that, when executed by the processor, cause:
identifying a SIP registrar server address; and
wherein initiating the SIP registration procedure is in response to identifying the SIP registrar server address.
25. The web application server of claim 22, wherein the memory stores further instructions that, when executed by the processor, cause:
receiving the SIP user identity or a SIP registrar server address from a user; and
storing the SIP user identity or the SIP registrar server address in a database associated with the web application server.
26. The web application server of claim 22, wherein the memory stores further instructions that, when executed by the processor, cause:
registering the web application server address as the registered contact.
27. The web application server of claim 22, wherein the memory stores further instructions that, when executed by the processor, cause:
selecting, using the web application server, one or more devices to which to route an incoming call based on a pre-selected destination;
extracting a media description associated with the incoming call; and
offering the incoming call through the WebRTC-enabled web browser.
US17/339,069 2012-10-19 2021-06-04 Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser Abandoned US20210297408A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/339,069 US20210297408A1 (en) 2012-10-19 2021-06-04 Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
PCT/EP2012/004403 WO2014060008A1 (en) 2012-10-19 2012-10-19 Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser
US201514422089A 2015-02-17 2015-02-17
US15/715,796 US10135806B2 (en) 2012-10-19 2017-09-26 Method and system for creating a virtual SIP user agent by use of a WEBRTC enabled web browser
US16/162,525 US11057365B2 (en) 2012-10-19 2018-10-17 Method and system for creating a virtual SIP user agent by use of a webRTC enabled web browser
US17/339,069 US20210297408A1 (en) 2012-10-19 2021-06-04 Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US16/162,525 Continuation US11057365B2 (en) 2012-10-19 2018-10-17 Method and system for creating a virtual SIP user agent by use of a webRTC enabled web browser

Publications (1)

Publication Number Publication Date
US20210297408A1 true US20210297408A1 (en) 2021-09-23

Family

ID=47115742

Family Applications (4)

Application Number Title Priority Date Filing Date
US14/422,089 Abandoned US20150229635A1 (en) 2012-10-19 2012-10-19 Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser
US15/715,796 Active US10135806B2 (en) 2012-10-19 2017-09-26 Method and system for creating a virtual SIP user agent by use of a WEBRTC enabled web browser
US16/162,525 Active 2032-12-04 US11057365B2 (en) 2012-10-19 2018-10-17 Method and system for creating a virtual SIP user agent by use of a webRTC enabled web browser
US17/339,069 Abandoned US20210297408A1 (en) 2012-10-19 2021-06-04 Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US14/422,089 Abandoned US20150229635A1 (en) 2012-10-19 2012-10-19 Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser
US15/715,796 Active US10135806B2 (en) 2012-10-19 2017-09-26 Method and system for creating a virtual SIP user agent by use of a WEBRTC enabled web browser
US16/162,525 Active 2032-12-04 US11057365B2 (en) 2012-10-19 2018-10-17 Method and system for creating a virtual SIP user agent by use of a webRTC enabled web browser

Country Status (4)

Country Link
US (4) US20150229635A1 (en)
EP (1) EP2909995B1 (en)
CN (1) CN104704795B (en)
WO (1) WO2014060008A1 (en)

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9363133B2 (en) 2012-09-28 2016-06-07 Avaya Inc. Distributed application of enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions, and related methods, systems, and computer-readable media
US10164929B2 (en) 2012-09-28 2018-12-25 Avaya Inc. Intelligent notification of requests for real-time online interaction via real-time communications and/or markup protocols, and related methods, systems, and computer-readable media
US9294458B2 (en) 2013-03-14 2016-03-22 Avaya Inc. Managing identity provider (IdP) identifiers for web real-time communications (WebRTC) interactive flows, and related methods, systems, and computer-readable media
US9571529B2 (en) 2013-03-15 2017-02-14 Avaya Inc. Browser-based communications enhanced with enterprise communication features
GB2512970B (en) * 2013-03-15 2015-10-07 Avaya Inc Browser-based communications enhanced with enterprise communication features
US9282489B2 (en) 2013-05-17 2016-03-08 Avaya Inc. Media escalation with use of endpoint adapter
US10205624B2 (en) 2013-06-07 2019-02-12 Avaya Inc. Bandwidth-efficient archiving of real-time interactive flows, and related methods, systems, and computer-readable media
US9065969B2 (en) 2013-06-30 2015-06-23 Avaya Inc. Scalable web real-time communications (WebRTC) media engines, and related methods, systems, and computer-readable media
US9525718B2 (en) * 2013-06-30 2016-12-20 Avaya Inc. Back-to-back virtual web real-time communications (WebRTC) agents, and related methods, systems, and computer-readable media
US9112840B2 (en) 2013-07-17 2015-08-18 Avaya Inc. Verifying privacy of web real-time communications (WebRTC) media channels via corresponding WebRTC data channels, and related methods, systems, and computer-readable media
US9614890B2 (en) 2013-07-31 2017-04-04 Avaya Inc. Acquiring and correlating web real-time communications (WEBRTC) interactive flow characteristics, and related methods, systems, and computer-readable media
US9531808B2 (en) 2013-08-22 2016-12-27 Avaya Inc. Providing data resource services within enterprise systems for resource level sharing among multiple applications, and related methods, systems, and computer-readable media
GB2517760B (en) * 2013-08-30 2019-11-06 Metaswitch Networks Ltd Linking web sessions with telephone calls
US10225212B2 (en) 2013-09-26 2019-03-05 Avaya Inc. Providing network management based on monitoring quality of service (QOS) characteristics of web real-time communications (WEBRTC) interactive flows, and related methods, systems, and computer-readable media
US10263952B2 (en) 2013-10-31 2019-04-16 Avaya Inc. Providing origin insight for web applications via session traversal utilities for network address translation (STUN) messages, and related methods, systems, and computer-readable media
US9769214B2 (en) * 2013-11-05 2017-09-19 Avaya Inc. Providing reliable session initiation protocol (SIP) signaling for web real-time communications (WEBRTC) interactive flows, and related methods, systems, and computer-readable media
US9635524B2 (en) * 2013-12-17 2017-04-25 Cellco Partnership Mobile device pass through for signaling messages
US10129243B2 (en) 2013-12-27 2018-11-13 Avaya Inc. Controlling access to traversal using relays around network address translation (TURN) servers using trusted single-use credentials
US10581927B2 (en) 2014-04-17 2020-03-03 Avaya Inc. Providing web real-time communications (WebRTC) media services via WebRTC-enabled media servers, and related methods, systems, and computer-readable media
US9749363B2 (en) 2014-04-17 2017-08-29 Avaya Inc. Application of enterprise policies to web real-time communications (WebRTC) interactive sessions using an enterprise session initiation protocol (SIP) engine, and related methods, systems, and computer-readable media
US9912705B2 (en) * 2014-06-24 2018-03-06 Avaya Inc. Enhancing media characteristics during web real-time communications (WebRTC) interactive sessions by using session initiation protocol (SIP) endpoints, and related methods, systems, and computer-readable media
EP3016341B1 (en) 2014-10-27 2018-12-12 Deutsche Telekom AG Method and arrangement for the efficient design of web-based communication services
EP3016344B1 (en) 2014-10-27 2017-08-16 Deutsche Telekom AG Intelligent media gateway switch for transparent routing and concatenating media streams
KR20160057873A (en) * 2014-11-14 2016-05-24 삼성전자주식회사 Communication method, electronic apparatus and storage medium
US10542082B2 (en) * 2015-01-29 2020-01-21 Ntt Communications Corporation Communication control apparatus, communication control method and communication control program
US9571480B1 (en) * 2015-04-08 2017-02-14 Sonus Networks, Inc. Authentication methods and apparatus
DE102016109938B4 (en) 2016-05-30 2022-05-25 Unify Patente Gmbh & Co. Kg Method for integrating a communication terminal device as a preferred device in a static configuration of a communication system and a communication system designed for this purpose
CN106850399B (en) * 2016-12-30 2022-04-26 深圳市潮流网络技术有限公司 Communication method based on WebRTC technology instant message
CN111917895B (en) * 2017-07-17 2022-01-11 华为技术有限公司 Alias management method and device
US10165109B1 (en) 2018-02-20 2018-12-25 Ploytech Ipco Pty Ltd. Telephony software control via web application
CN110958206A (en) * 2018-09-26 2020-04-03 山东华软金盾软件股份有限公司 Data security method for mobile equipment application based on virtualization
US11561997B2 (en) 2019-03-13 2023-01-24 Oracle International Corporation Methods, systems, and computer readable media for data translation using a representational state transfer (REST) application programming interface (API)
US11050798B2 (en) * 2019-05-31 2021-06-29 Mitel Networks Corporation Methods for establishing peer-to-peer communications using distributed call ledgers
US11095691B2 (en) * 2019-06-26 2021-08-17 Oracle International Corporation Methods, systems, and computer readable media for establishing a communication session between a public switched telephone network (PSTN) endpoint and a web real time communications (WebRTC) endpoint
EP4101153A4 (en) * 2020-02-05 2024-02-21 Jpmorgan Chase Bank Na System and method for implementing a softphone emergency dialing architecture
CN113132376B (en) * 2021-04-14 2022-11-22 腾讯科技（深圳）有限公司 Media data processing method, device and system, electronic equipment and storage medium

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030097456A1 (en) * 2001-11-08 2003-05-22 Huh Mi Young Method for synchronizing registration information within intra-domain
US20030135569A1 (en) * 2002-01-15 2003-07-17 Khakoo Shabbir A. Method and apparatus for delivering messages based on user presence, preference or location
WO2006038950A1 (en) * 2004-09-30 2006-04-13 Siemens Communications, Inc. Sip user agent with simultaneous multiple registrations
US20060098624A1 (en) * 2004-11-10 2006-05-11 Morgan David P Using session initiation protocol
US20070022289A1 (en) * 2005-07-20 2007-01-25 Mci, Inc. Method and system for providing secure credential storage to support interdomain traversal
US20070168521A1 (en) * 2006-01-18 2007-07-19 Tadashi Kaji Mediating system and method to establish communication session, allowing private information to be protected
US20080313265A1 (en) * 2004-07-02 2008-12-18 Greg Pounds CSIP Proxy for Translating SIP to Multiple Peer-to-Peer Through Network Resources
US20090191869A1 (en) * 2008-01-24 2009-07-30 At&T Labs System and method of providing a user with a registration review in ims system
US20100232402A1 (en) * 2006-06-09 2010-09-16 Hubert Przybysz Handling Multiple User Interfaces in an IP Multimedia Subsystem
US20100278322A1 (en) * 2009-04-30 2010-11-04 Microsoft Corporation User-based authentication for realtime communications
US20110072144A1 (en) * 2008-02-29 2011-03-24 Ioannis Fikouras Technique for performing signaling conversion between http and sip domains
US20110149956A1 (en) * 2005-07-20 2011-06-23 Verizon Business Global Llc Method and system for providing secure media gateways to support interdomain traversal
US20130227663A1 (en) * 2010-10-08 2013-08-29 Telefonica S.A. Method, a system and a network element for ims control layer authentication from external domains
US8695077B1 (en) * 2013-03-14 2014-04-08 Sansay, Inc. Establishing and controlling communication sessions between SIP devices and website application servers

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0322877D0 (en) * 2003-09-30 2003-10-29 British Telecomm Search system and method
KR100605806B1 (en) * 2004-06-10 2006-08-01 삼성전자주식회사 A phone-based mobile internet protocol, voice over internet protocol, and session initiation protocol, session initiation protocol server, and routing path control method and system for session initiation protocol service
US20050277431A1 (en) * 2004-06-14 2005-12-15 Sbc Knowledge Ventures, Lp System and method for managing wireless data communications
CN101069402B (en) * 2004-10-26 2010-11-03 意大利电信股份公司 Method and system for transparently authenticating a mobile user to access web services
FI20041659A0 (en) * 2004-12-23 2004-12-23 Nokia Corp Method of routing communications to a VoIP terminal in a mobile communication system
KR20060105064A (en) * 2005-04-01 2006-10-11 삼성전자주식회사 Method and system for transporting information from responding poc clients using tbcp message through established sip session of poc network
WO2006102943A1 (en) * 2005-04-01 2006-10-05 Telefonaktiebolaget Lm Ericsson (Publ) Method for initiating ims based communications
EP1892940A1 (en) * 2006-08-23 2008-02-27 Thomson Telecom Belgium Device and method for enabling SIP DECT terminal mobility
JP2009290329A (en) * 2008-05-27 2009-12-10 Toshiba Corp Ip communication system, server unit, terminal device and authentication method
US8305983B2 (en) * 2008-11-03 2012-11-06 At&T Intellectual Property I, L.P. Method and apparatus for enabling registration of endpoint devices through provisioning
US9380102B2 (en) * 2011-03-02 2016-06-28 Verizon Patent And Licensing Inc. Secure management of SIP user credentials
US10084848B2 (en) * 2012-10-16 2018-09-25 At&T Intellectual Property I, L.P. Centralized control of user devices via universal IP services registrar/hub

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030097456A1 (en) * 2001-11-08 2003-05-22 Huh Mi Young Method for synchronizing registration information within intra-domain
US20030135569A1 (en) * 2002-01-15 2003-07-17 Khakoo Shabbir A. Method and apparatus for delivering messages based on user presence, preference or location
US20080313265A1 (en) * 2004-07-02 2008-12-18 Greg Pounds CSIP Proxy for Translating SIP to Multiple Peer-to-Peer Through Network Resources
WO2006038950A1 (en) * 2004-09-30 2006-04-13 Siemens Communications, Inc. Sip user agent with simultaneous multiple registrations
US20060098624A1 (en) * 2004-11-10 2006-05-11 Morgan David P Using session initiation protocol
US20070022289A1 (en) * 2005-07-20 2007-01-25 Mci, Inc. Method and system for providing secure credential storage to support interdomain traversal
US20110149956A1 (en) * 2005-07-20 2011-06-23 Verizon Business Global Llc Method and system for providing secure media gateways to support interdomain traversal
US20070168521A1 (en) * 2006-01-18 2007-07-19 Tadashi Kaji Mediating system and method to establish communication session, allowing private information to be protected
US20100232402A1 (en) * 2006-06-09 2010-09-16 Hubert Przybysz Handling Multiple User Interfaces in an IP Multimedia Subsystem
US20090191869A1 (en) * 2008-01-24 2009-07-30 At&T Labs System and method of providing a user with a registration review in ims system
US20110072144A1 (en) * 2008-02-29 2011-03-24 Ioannis Fikouras Technique for performing signaling conversion between http and sip domains
US20100278322A1 (en) * 2009-04-30 2010-11-04 Microsoft Corporation User-based authentication for realtime communications
US20130182832A1 (en) * 2009-04-30 2013-07-18 Microsoft Corporation User-based authentication for realtime communications
US20130227663A1 (en) * 2010-10-08 2013-08-29 Telefonica S.A. Method, a system and a network element for ims control layer authentication from external domains
US8695077B1 (en) * 2013-03-14 2014-04-08 Sansay, Inc. Establishing and controlling communication sessions between SIP devices and website application servers

Also Published As

Publication number Publication date
US11057365B2 (en) 2021-07-06
US10135806B2 (en) 2018-11-20
CN104704795A (en) 2015-06-10
EP2909995B1 (en) 2018-01-24
WO2014060008A1 (en) 2014-04-24
EP2909995A1 (en) 2015-08-26
US20150229635A1 (en) 2015-08-13
CN104704795B (en) 2018-04-27
US20180026966A1 (en) 2018-01-25
US20190068579A1 (en) 2019-02-28

Similar Documents

Publication Publication Date Title
US20210297408A1 (en) Method and system for creating a virtual sip user agent by use of a webrtc enabled web browser
US10819757B2 (en) System and method for real-time communication by using a client application communication protocol
US10454762B2 (en) System and method of processing media traffic for a hub-based system federating disparate unified communications systems
JP5735016B2 (en) System and method for peer-to-peer hybrid communication
US9571529B2 (en) Browser-based communications enhanced with enterprise communication features
US8055778B2 (en) SIP user agent with simultaneous multiple registrations
US7899168B2 (en) Controlling or monitoring PBX phone from multiple PC endpoints
US8761160B2 (en) Service path routing between session border controllers
US8515388B2 (en) Performing operations on IP telephony device from a remote client
WO2013155939A1 (en) Method for sharing internet and operator network services, service provider, and webpage gateway
US20110040833A1 (en) Methods and Arrangements for Interactive Caller Information Services in a Communication Network
JP2017510116A (en) Method and server for enabling a first user to automatically detect a second user's social network identifier and the respective status of this second user in those social networks
Ali et al. Session initiation protocol
WO2016179538A1 (en) System and method of processing media traffic for a hub-based system federating disparate unified communications systems
Wu et al. Migration of VOIP/SIP enterprise solutions towards IMS
Abouabdalla et al. SIP–Functionality and structure of the protocol
Sun et al. VoIP Signalling—SIP
GB2525783A (en) Browser-based communications enhanced with enterprise communication features

Legal Events

Date Code Title Description
AS Assignment

Owner name: UNIFY PATENTE GMBH & CO. KG, GERMANY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UNIFY GMBH & CO. KG;REEL/FRAME:056479/0279

Effective date: 20140930

Owner name: RINGCENTRAL, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RINGCENTRAL IP HOLDINGS, INC.;REEL/FRAME:056442/0564

Effective date: 20200702

Owner name: RINGCENTRAL IP HOLDINGS, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UNIFY SOFTWARE AND SOLUTIONS GMBH & CO. KG AND UNIFY PATENTE GMBH & CO. KG;REEL/FRAME:056442/0506

Effective date: 20191230

Owner name: UNIFY GMBH & CO. KG, GERMANY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SARIDAKI, ELENI;BALAFOUTIS, ELIAS;REEL/FRAME:056442/0362

Effective date: 20150303

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

AS Assignment

Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA

Free format text: SECURITY INTEREST;ASSIGNOR:RINGCENTRAL, INC.;REEL/FRAME:062973/0194

Effective date: 20230214

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION