Version: 1:1.8.3.3-1 contains this fix.
** Changed in: asterisk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/507007
Title:
make dahdi a suggests
** Changed in: asterisk (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/507007
Title:
make dahdi a suggests or recommends
To manage notifications about thi
@herb: Like the upstream issue mentions, we will loose a fair bit of
functionally removing DAHDI from Asterisk. Specifically,
res_musiconhold.so. As for ConfBridge, yes it does not depend on DAHDI,
however it also does not support the same functionality as MeetMe.
I do agree, a meta package woul
** Changed in: asterisk (Debian)
Status: Unknown => New
--
make dahdi a suggests or recommends
https://bugs.launchpad.net/bugs/507007
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
** Bug watch added: Debian Bug tracker #590558
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590558
** Also affects: asterisk (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590558
Importance: Unknown
Status: Unknown
--
make dahdi a suggests or recommends
https:/
@Dave as of 1.6.1 you no longer need timing for dahdi. See
http://www.russellbryant.net/blog/2008/06/16/asterisk-16-now-with-a-new-
timing-api/
@Mattias, from the Ubuntu Policy Manual: "The Recommends field should
list packages that would be found together with this one in all but
unusual installa
> dahdi_dummy for a timing device
Well, asterisk uses the RTC when that isn't available.
Anyway, isn't Recommends: meant to imply "if you deselect this, OK, but
you better know what you're doing"?
--
make dahdi a suggests or recommends
https://bugs.launchpad.net/bugs/507007
You received this bu
I was under the impression that most installations at least used
dahdi_dummy for a timing device.. The packages should target the
majority of use cases, and I can see the frustration with having to pull
in additional stuff your setup doesn't require.
I'm not sure really how to progress with this.
** Changed in: asterisk (Ubuntu)
Status: New => Confirmed
--
make dahdi a suggests or recommends
https://bugs.launchpad.net/bugs/507007
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
On second thought, MeetMe needs /dev/dahdi/dummy or it simply won't
work.
So a note in the README (or even the package description) and a
Recommends: for the dahdi driver are the minimum requirement.
Conflicting goals, but then if you set up Asterisk as a SIP-only PBX on
a resource-limited small
Seconded. I ended up using equivs to build a dummy package which Provides:
dahdi.
(Of course equivs also drags in the whole build environment, but I can do that
on a machine that happens to not be our production VOIP gateway!)
--
make dahdi a suggests or recommends
https://bugs.launchpad.net/bu
I concur on this. All my asterisk PBXs are IP only and having to drag in
build-essential is non-optimal
--
make dahdi a suggests or recommends
https://bugs.launchpad.net/bugs/507007
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
12 matches
Mail list logo
