[asterisk-bugs] [JIRA] (ASTERISK-25524) module reload res_calendar.so does not reload everything in calendar.conf

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25524:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> module reload res_calendar.so does not reload everything in calendar.conf
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-25524
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25524
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_calendar
>    Affects Versions: 11.18.0
>         Environment: CentOS 6.7
>            Reporter: Jesper
>            Severity: Minor
>              Labels: calendar
>
> if the url are changed from:
> url = https://www.google.com/calendar/ical/XXXXXXXXX/public/basic.ics
> to
> url = http://www.google.com/calendar/ical/XXXXXXXXX/public/basic.ics
> changes are not active after module reload res_calendar.so
> calendar.conf:
> [gcal1]
> type = ical
> url = https://www.google.com/calendar/ical/XXXXXXXXX/public/basic.ics
> user =
> secret =
> refresh = 5
> timeframe = 60



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