# Asterisk Project : Configuring Asterisk Calendaring

Added by mdavenport , edited by mdavenport on Aug 31, 2010

All asterisk calendaring modules are configured through calender.conf. Each calendar module can define its own set of required parameters in addition to the parameters available to all calendar types. An effort has been made to keep all options the same in all calendaring modules, but some options will diverge over time as features are added to each module.
An example calendar.conf might look like:

    [calendar_joe]
    type = ical
    url = https://example.com/home/jdoe/Calendar
    user = jdoe
    secret = mysecret
    refresh = 15
    timeframe = 600
    autoreminder = 10
    channel = SIP/joe
    context = calendar_event_notify
    extension = s
    waittime = 30

### Module-independent settings

The settings related to calendar event notification are handled by the core calendaring API. These settings are:

- autoreminder - This allows the overriding of any alarms that may or may not be set for a calendar event. It is specified in minutes.

- refresh - How often to refresh the calendar data; specified in minutes.

- timeframe - How far into the future each calendar refresh should look. This is the amount of data that will be visible to queries from the dialplan. This setting should always be greater than or equal to the refresh setting or events may be missed. It is specified in minutes.

- channel - The channel that should be used for making the notification attempt.

- waittime - How long to wait, in seconds, for the channel to answer a notification attempt. There are two ways to specify how to handle a notification. One option is providing a context and extension, while the other is providing an application and the arguments to that application. One (and only one) of these options should be provided.

- context - The context of the extension to connect to the notification channel

- extension - The extension to connect to the notification. Note that the priority will always be 1.

- app - The dialplan application to execute upon the answer of a notification

- appdata - The data to pass to the notification dialplan application

### Module-dependent settings

Connection-related options are specific to each module. Currently, all modules take a url, user, and secret for configuration and no other module-specific settings have been implemented. At this time, no support for HTTP redirects has been implemented, so it is important to specify the correct URL-paying attention to any trailing slashes that may be necessary.