And one more question: How 3.1.4-SNAPSHOT behaves in this situation? On Tue, Dec 13, 2016 at 1:43 PM, Maxim Solodovnik <[email protected]> wrote:
> Hello Hemant, > > could you please provide more details on issue: > 1) Is email being received by meeting attendee has correct start/end > date/time? > 2) Is attendee is able to attend? > > I'll try to check your scenario, but additional setup will be required ... > will take some time > > On Tue, Dec 13, 2016 at 1:11 PM, Coscend@OM <[email protected]> > wrote: > >> Dear OpenMeetings Developers, >> >> >> >> We are facing the following issue with Period invitation. One-time and >> Endless work fine. Environment: OM 3.1.2. Any browser. >> >> >> >> 1. When an organizer sends an invitation from a timezone which is the >> same as the zone in which the OM server is located, everything works fine. >> >> 2. When an organizer sends an invitation from a timezone different >> from >> the zone in which the OM server is located, the invitation hash code >> generated is INCORRECT and does not let attendee join the session. >> >> >> >> Here is an example: >> >> OM server is in America/Chicago >> >> Organizer is in Asia/Kolkata. >> >> Attendee is in America/Chicago. >> >> Invitation Valid from: Sun Dec 11 10:34:08 2016 >> Valid to: Sun Dec 11 13:39:08 2016 >> >> >> >> >> >> For the attendee in America/Chicago zone, the hash code combines OM >> server's >> timezone (America/Chicago) with Organizer's (Asia/Kolkata) time >> >> Invitation Valid from: Sun Dec 11 10:34:08 CST 2016 >> Valid to: Sun Dec 11 13:39:08 CST 2016 >> >> >> >> SOLUTION >> >> The correct one should be: >> Attendee Timezone: America/Chicago >> Valid from: Sat Dec 10 23:04:08 CST 2016 >> Valid to: Sun Dec 11 02:09:08 CST 2016 >> >> >> >> The attendee's correct time value "Corrected Time" = Current equation - >> [Mod(Organizer's Time zone - Attendee's Time zone)] >> >> >> >> >> >> InvitationManager.java >> >> case Period: >> >> >> LocalDateTime now = >> ZonedDateTime.now(getZoneId(i.getInvitee().getTimeZoneId())) >> .toLocalDateTime >> (); >> >> >> LocalDateTime from = CalendarHelper.getDateTime(i.getValidFrom(), >> i.getInvitee().getTimeZoneId()); >> >> >> LocalDateTime to = CalendarHelper.getDateTime(i.getValidTo(), >> i.getInvitee().getTimeZoneId()); >> >> >> >> CalendarHelper.java >> >> public static ZonedDateTime getZoneDateTime(Date d, String >> tzId) >> { >> >> if (d == null) { >> >> d = new Date(); >> >> } >> >> return >> Instant.ofEpochMilli(d.getTime()).atZone(getZoneId(tzId)); >> >> } >> >> >> >> >> >> Thank you. >> >> >> >> Sincerely, >> >> >> >> Hemant K. Sabat >> >> >> >> Coscend Communications Solutions >> >> Web site: <http://www.coscend.com/> www.Coscend.com >> >> ------------------------------------------------------------------ >> >> Real-time, Interactive Video Collaboration, Tele-healthcare, >> Tele-education, >> Telepresence Services, on the fly. >> >> ------------------------------------------------------------------ >> >> CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail >> Messages from Coscend Communications Solutions' posted at: >> <http://www.coscend.com/Terms_and_Conditions.html> >> http://www.Coscend.com/Terms_and_Conditions.html >> >> >> >> >> >> >> >> > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
