In
In
With respect to the Zoom meeting in
function formSubmit( ){
var confNo=Trim($(‘#join-confno’.val( );
var username=$(‘#join-username’).val( )
}
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
function_getLaunchCalendarMeetingFunc( ){
const elem=document.querySelector(“.meeting-join”)
return elem &&
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
const obj={
_next: function(n) {
}
}
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:
const obj={
_next: function(n) {
//
, u=_botName
, u=_botEmail
//
}
}
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
function ( ){
e.$broadcast(“Visitor.Join”, t.visitorNameCtrl.visitorName)
}
In 510, the function is given a new (e.g., global) name so that it can be referenced in a later window. For example:
JOINME_LOGIN_=function ( ){
e.$broadcast(“Visitor.Join”, t.visitorNameCtrl.visitorName)
}
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.
Number | Name | Date | Kind |
---|---|---|---|
7760865 | Awan et al. | Jul 2010 | B2 |
8064342 | Badger | Nov 2011 | B2 |
8631069 | Maes | Jan 2014 | B2 |
9256695 | Willis et al. | Feb 2016 | B1 |
9392122 | Sall | Jul 2016 | B2 |
9699409 | Reshef | Jul 2017 | B1 |
9992448 | Reshef et al. | Jun 2018 | B2 |
10218839 | Gupta et al. | Feb 2019 | B2 |
10325284 | Aggarwal et al. | Jun 2019 | B1 |
20070206759 | Boyanovsky | Sep 2007 | A1 |
20090274284 | Arsenault et al. | Nov 2009 | A1 |
20100135477 | Chen | Jun 2010 | A1 |
20100205543 | Von Werther | Aug 2010 | A1 |
20100223389 | Ananthanarayanan et al. | Sep 2010 | A1 |
20110228921 | Singh et al. | Sep 2011 | A1 |
20110271210 | Jones | Nov 2011 | A1 |
20120051267 | Ma et al. | Mar 2012 | A1 |
20120137367 | Dupont et al. | May 2012 | A1 |
20130076853 | Diao | Mar 2013 | A1 |
20130191719 | Underhill et al. | Jul 2013 | A1 |
20140006611 | Perez | Jan 2014 | A1 |
20150036810 | Rashid et al. | Feb 2015 | A1 |
20160212269 | Backhaus | Jul 2016 | A1 |
20160253314 | Pottier et al. | Sep 2016 | A1 |
20160381215 | Goyal et al. | Dec 2016 | A1 |
20170257598 | Reshef et al. | Sep 2017 | A1 |
20170345325 | Metts | Nov 2017 | A1 |
20180082208 | Comier et al. | Mar 2018 | A1 |
20180121828 | Keysers et al. | May 2018 | A1 |
20180176661 | Varndell et al. | Jun 2018 | A1 |
20180191901 | Aleksin et al. | Jul 2018 | A1 |
20180227339 | Rodriguez et al. | Aug 2018 | A1 |
20180239822 | Reshef et al. | Aug 2018 | A1 |
20180249007 | Seward et al. | Aug 2018 | A1 |
20180249122 | Reshef et al. | Aug 2018 | A1 |
20180268318 | Matam et al. | Sep 2018 | A1 |
20180330736 | Faulkner et al. | Nov 2018 | A1 |
20190068390 | Gross et al. | Feb 2019 | A1 |
20190068526 | Xie et al. | Feb 2019 | A1 |
20190102846 | Loschiavo | Apr 2019 | A1 |
20190182183 | Hubauer et al. | Jun 2019 | A1 |
20190205772 | Kohlmeier et al. | Jul 2019 | A1 |
20190318743 | Reshef et al. | Oct 2019 | A1 |
Entry |
---|
WebEx Meeting Center with Collaboration Meeting Rooms (CMR Cloud) User Guide, https://www.cisco.com/c/en/us/td/docs/collaboration/meeting_center/wbs2913/CMR_Cloud_User_Guide.pdf, total 24 pages, Publication Date: Aug. 1, 2014. |
Pexip Mobile App for Android Quick Guide, https://docs.pexip.com/files/v8/Pexip_Mobile_App_Android_Quickguide_v8.a.pdf, Total 4 pages, Publication Date: Feb. 2015. |
Lync conference invitations in SIP terms, http://blog.greenl.ee/2011/12/15/lync-conference-invitations/, Total 7 pages, Publication Date: Dec. 15, 2011. |
RFC4579—Session Initiation Protocol (SIP) Call Control—Conferencing for User Agents, https://datatracker.ietf.org/doc/rfc4579/ , pp. 3, Publication Date: Aug. 2006. |
U.S. Appl. No. 16/558,692. |
U.S. Appl. No. 16/524,653. |
U.S. Appl. No. 15/852,259, filed Dec. 22, 2017, Pending. |
U.S. Appl. No. 16/558,692, filed Jul. 22, 2019, U.S. Pat. No. 10,791,217. |
U.S. Appl. No. 16/524,653, filed Jul. 29, 2019, U.S. Pat. No. 10,742,695. |
U.S. Appl. No. 16/855,610, filed Apr. 22, 2020, Pending. |
U.S. Appl. No. 16/987,846, US 2021-00676226, filed Mar. 4, 2021, Pending. |
U.S. Appl. No. 15/852,259. |
U.S. Appl. No. 16/855,610. |
U.S. Appl. No. 16/897,846. |
U.S. Appl. No. 17/206,916. |