System information

$ asterisk -r
*CLI> module load res_calendar.so
*CLI> module reload
After loading the modules we can check to make sure our calendar has connected to
the server and been loaded into memory correctly, by executing calendar show
calendars:
*CLI> calendar show calendars
Calendar Type Status
-------- ---- ------
myGoogleCal caldav busy
Our status is currently set to busy (which doesn’t have any bearing on our dialplan at
the moment, but simply means we have an event that has marked us as busy in the
calendar), and we can see the currently loaded events for our time range by running
calendar show calendar <myGoogleCal> from the Asterisk console:
*CLI> calendar show calendar myGoogleCal
Name : myGoogleCal
Notify channel :
Notify context :
Notify extension :
Notify applicatio :
Notify appdata :
Refresh time : 15
Timeframe : 60
Autoreminder : 0
Events
------
Summary : Awesome Call With Russell
Description :
Organizer :
Location :
Cartegories :
Priority : 0
UID : [e-mail]
Start : 2010-09-28 08:30:00 AM -0400
End : 2010-09-28 09:00:00 AM -0400
Alarm : 2010-09-28 04:20:00 AM -0400
The first field in the top section is the Name of our calendar. Following that are several
Notify fields, which are used to dial a destination upon the start of a meeting, that we’ll
discuss in more detail shortly. The Refresh time and Timeframe fields are the values we
configured for how often to check for new events and how long of a range we should
look at for data, respectively. The Autoreminder field controls how long prior to an
event we should execute the Notify options.
Calendar Integration | 401