03-08-2014 07:35 AM
I am getting inconsistent results in scheduling meetings using URL API.
Here is my example:
Meeting 1: https://sgc.webex.com/sgc/m.php?AT=SM&MN=Mental Health Fitness Group&TC=1&IP=1&AJ=1&AJMI=15&DU=90&YE=2014&MO=3&DA=8&HO=20&MI=00&RO=5&Always=0&Days=1&UntilYE=2014&UntilMO=3&UntilDA=29&AF=1700&MF=167800831&MU=GoBack&BU=https://www.supportgroupscentral.com/admin/clt/clt_meetings_add_process_webex4.cfm
Meeting 2: https://sgc.webex.com/sgc/m.php?AT=SM&MN=One on One Mental Health Fitness Coaching&TC=1&IP=1&AJ=1&AJMI=15&DU=45&YE=2014&MO=3&DA=8&HO=20&MI=00&RO=5&Always=0&Days=1&UntilYE=2014&UntilMO=3&UntilDA=29&AF=1700&MF=167800831&MU=GoBack&BU=https://www.supportgroupscentral.com/admin/clt/clt_meetings_add_process_webex4.cfm
Meeting 1 is added correctly to the Webex calendar.
Meeting 2 is added to the Webex calendar, but ends one week early. So, instead of ending on March 29th as requested, the meeting on the Webex calendar shows an end date of March 22nd.
The only difference between these meetings are the name (MN) and the duration (DU).
What could be causing this problem?
I greatly appreciate your help!!!!
Solved! Go to Solution.
03-10-2014 09:51 AM
Hello,
I was able to duplicate this behavior for sessions shorter than 60 minutes and submitted a bug report for this URL API command. In the meantime, you can set duration to 60, set end date out a week further, or use XML API instead.
03-10-2014 09:51 AM
Hello,
I was able to duplicate this behavior for sessions shorter than 60 minutes and submitted a bug report for this URL API command. In the meantime, you can set duration to 60, set end date out a week further, or use XML API instead.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide