mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-29 18:19:30 +00:00
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: https://origsvn.digium.com/svn/asterisk/branches/1.4@139145 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
@@ -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([***])
|
||||
|
Reference in New Issue
Block a user