METHODS AND SYSTEMS FOR CALLING INTO MEETING
Systems and methods for joining a video conference. A first function can be found, wherein the first function can interact with a user interface element and can be used to call a video conference bot. The first function can be replaced with a second function; wherein the second function can be used to call the video conference bot but may not interact with the user interface element. The second function can be used to join the video conference without interacting with the DOM.
Latest SALESLOFT, INC Patents:
- Methods and systems for determining cadences
- Methods and systems for cascading model architecture for providing information on reply emails
- SYSTEMS AND METHODS FOR ELECTRONIC NOTETAKING AND CALLING INTO ELECTRONIC MEETINGS
- Methods and systems for joining a conference
- METHODS AND SYSTEMS FOR PLACING CALLS
The present application is a continuation to U.S. application Ser. No. 16/518,367 filed on Jul. 22, 2019, titled “METHODS AND SYSTEMS FOR CALLING INTO MEETING.” This application is herein incorporated by reference in its entirety.
DESCRIPTION OF DRAWINGSIn
In
With respect to the Zoom meeting in
In 210, the found underlying function can be modified so that it takes parameters instead of referencing the DOM (or GUI). For example, the following can be used instead of the two lines above in bold that reference the DOM:
- function formSubmit(confNo, userName)
In 215, the modified function can be invoked with values obtained from our system instead of from the DOM (or GUI) in order to join the meeting bot. For example:
- joinmeeting.formSubmit(callInNumber, botName)
With respect to the WebEx meeting in
In 310, a differently named reference to Webex's smartLaunchMeeting function can be obtained:
- const launchCalendarMeetingFunc=_getLaunchCalendarMeetingFunc( );
In 315, Webex's smartLaunchMeeting function can be invoked to start the meeting without interacting with the GUI (e.g., clicking any buttons):
- launchCalendarMeetingFunc(‘thinclientjoin’);
With respect to the UberConference meeting in
In 410, the code can be modified so that it no longer references the GUI. For example, see how the code in bold changes from the code illustrated for 405:
In 415, the modified code can be invoked to launch the UberConference meeting:
- this._next( )
With respect to the to the Join.me meeting in
In 510, the function is given a new (e.g., global) name so that it can be referenced in a later window. For example:
In 515, the new reference can be used to invoke the underlying function in a later window. For example:
JOINME_LOGIN_( )
With respect to the GoToMeeting in
function ( ) {e.submit( )}
In 610, the function is given a new (e.g., global) name so that it can be referenced in a later window. For example:
- submitMyForm=function ( ) {e.submit( )}
In 615, the new reference can be used to invoke the underlying function in a later window. For example:
submitMyForm( )
While various embodiments have been described above, it should be understood that they have been presented by way of example and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail may be made therein without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above-described embodiments.
In addition, it should be understood that any figures which highlight the functionality and advantages are presented for example purposes only. The disclosed methodology and system are each sufficiently flexible and configurable such that they may be utilized in ways other than that shown. For example, the steps and/or limitations may be performed in a different order then that shown in the specification and/or claims.
Although the term “at least one” may often be used in the specification, claims and drawings, the terms “a”, “an”, “the”, “said”, etc. also signify “at least one” or “the at least one” in the specification, claims and drawings.
Additionally, the terms “including”, “comprising” or similar terms in the specification, claims and drawings should be interpreted as meaning “including, but not limited to.”
Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 212, paragraph 6. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 212, paragraph 6.
Claims
1. A method for joining a video conference, comprising:
- finding a first function, wherein the first function interacts with a user interface element and is used to call a video conference bot;
- replacing the first function with a second function; wherein the second function is used to call the video conference bot but does not interact with the user interface element; and
- using the second function to join the video conference without interacting with the document object model (DOM).
Type: Application
Filed: Mar 19, 2021
Publication Date: Jul 8, 2021
Applicant: SALESLOFT, INC (Atlanta, GA)
Inventors: Austin BROWN (Atlanta, GA), Matt FINNERAN (Atlanta, GA)
Application Number: 17/206,916