diff options
| author | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-08-20 19:35:59 +0000 |
|---|---|---|
| committer | kpfleming <kpfleming@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-08-20 19:35:59 +0000 |
| commit | 892056dbc69137f78a8036fcda23ec6fcf1808b2 (patch) | |
| tree | 884204c3d034ed74e2e06101cb1af869b925c391 /configure.ac | |
| parent | 1643fa63cf953401a1d7dc6f5117e6cddbe6724a (diff) | |
Backport support for Zaptel/DAHDI channel-level alarms from trunk/1.6, because not doing so just makes it difficult for people with channels that are in alarm when Asterisk starts up to get them going once the alarm is cleared
(closes issue #12160)
Reported by: tzafrir
Patches:
asterisk-chanalarms_14.patch uploaded by tzafrir (license 46)
Tested by: tzafrir
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@139145 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configure.ac')
| -rw-r--r-- | configure.ac | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/configure.ac b/configure.ac index e7f91a3d9..6bc07331b 100644 --- a/configure.ac +++ b/configure.ac @@ -1458,6 +1458,15 @@ if test "${USE_ZAPTEL}" != "no" && test "x${PBX_DAHDI}" != "x1"; then fi PBX_ZAPTEL=1 AC_DEFINE([HAVE_ZAPTEL], 1, [Define if your system has the Zaptel headers.]) + saved_cppflags="${CPPFLAGS}" + CPPFLAGS="${CPPFLAGS} ${ZAPTEL_INCLUDE}" + AC_CHECK_MEMBER([ZT_PARAMS.chan_alarms],,,[#include <zaptel/zaptel.h>]) + CPPFLAGS="${saved_cppflags}" + if test "${ac_cv_member_ZT_PARAMS_chan_alarms}" = "yes"; then + AC_DEFINE([HAVE_ZAPTEL_CHANALARMS], 1, [Define if your Zaptel drivers have chan_alarms.]) + else + AC_DEFINE([HAVE_ZAPTEL_CHANALARMS], 0, [Define if your Zaptel drivers have chan_alarms.]) + fi elif test -n "${ZAPTEL_MANDATORY}"; then AC_MSG_NOTICE([***]) |