[asterisk-bugs] [JIRA] (ASTERISK-27174) res_calendar_icalendar: Recurring events not being loaded from Google calendar using ical

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238158#comment-238158 ] 

Friendly Automation commented on ASTERISK-27174:
------------------------------------------------

Change 6244 merged by Jenkins2:
res_calendar_icalendar: Properly handle recurring events

[https://gerrit.asterisk.org/6244|https://gerrit.asterisk.org/6244]

> res_calendar_icalendar: Recurring events not being loaded from Google calendar using ical
> -----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27174
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27174
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_calendar_icalendar
>    Affects Versions: 13.15.0
>         Environment: IncrediblePBX 13-12.3 for Ubuntu 14, Linux  3.13.0-125-generic #174-Ubuntu SMP Mon Jul 10 18:51:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Mark Thompson
>            Assignee: Sean Bright
>            Severity: Minor
>
> type = ical
> Calendar functions okay with single events. All single events in the configured timeframe are listed in "calendar show calendar <calendar name>". For recurring events only the initial event is listed. All other events in the series are omitted. This problem has been reported at least twice in the Asterisk forums:
> https://community.asterisk.org/t/google-calendar-integration-missing-periodic-events/48338
> https://community.asterisk.org/t/google-calendar-integration-repeat-events-not-retrieved/69957
> Note that I had a workaround of switching calendar type from "ical" to "caldav" (along with the appropriate url). However, caldav no longer works due to unknown certificate rejection errors.



--
This message was sent by Atlassian JIRA
(v6.2#6252)