System information

If you are planning on compiling the res_calendar_ews module, you will
need to have a version of neon greater than or equal to 0.29. Currently
CentOS is shipping with 0.25, so you will have to compile the neon
library and link to it from the configure script. This can be done via ./
configure --with-neon29=<path to neon>.
The next step is to install the libical-devel dependency. Unfortunately, this module
is not shipped with CentOS and requires a third-party repository (see “Third-Party
Repositories” on page 46). In this case, we need to install libical-devel from the EPEL
(Extra Packages for Enterprise Linux) repository:
$ sudo yum --enablerepo=epel install libical-devel
After installing our dependencies, we can run the configure script in our Asterisk source
directory and enable both the res_calendar and res_calendar_caldav modules from
within the Resource Modules section of menuselect.
Ubuntu dependencies
Because all the modules require the neon development library, we’re going to install
that first. On Ubuntu, you will typically be given several different versions (e.g., on
10.04 we have the option of libneon 2.5, 2.6, and 2.7). We’re going to install the latest
version available to us:
$ sudo apt-get install libneon27-dev
If you are planning on compiling the res_calendar_ews module, you will
need to have neon 0.29 or greater. Currently Ubuntu is shipping with
0.27, so you will have to compile the neon library and link to it from the
configure script. This can be done via ./configure --with-neon29=<path
to neon>.
With libneon installed, we can now install the libical-dev package and its dependencies
with apt-get:
$ sudo apt-get install libical-dev
After installing our dependencies, we can run the configure script in our Asterisk source
directory and enable both the res_calendar and res_calendar_caldav modules from
within the Resource Modules section of menuselect.
Configuring Calendar Support for Asterisk
In this section we’re going to discuss how to connect your Asterisk system to a Google
calendar. We’re using calendars from Google for the simple reason that they don’t
require any other configuration (such as setting up a calendaring server), which gets us
Calendar Integration | 399