2012/6/26, Richard Mudgett rmudg...@digium.com:
This is the option I will try.
I'll report my findings here.
My findings, after setting layer1_presence=ignore in chan_dahdi.conf
are :
== Starting D-Channel on span 1
== Starting D-Channel on span 2
== Primary D-Channel on span 1 up
This is the option I will try.
I'll report my findings here.
My findings, after setting layer1_presence=ignore in
chan_dahdi.conf
are :
== Starting D-Channel on span 1
== Starting D-Channel on span 2
== Primary D-Channel on span 1 up
== Primary D-Channel on span 2
2012/6/22, Olivier oza_4...@yahoo.fr:
2012/6/21, Richard Mudgett rmudg...@digium.com:
My previous message was incomplete.
On thing to note is I had to forbid hfcmulti in modprobe.d in the
second box to comply with a warning from dahdi. Without that, I could
see this line in the output of
As basically Asterisk 1.8 requires libpri1.4.11 and up, I had to
downgrade Asterisk to 1.6 and libpri to 1.4.10.2 to get pri show
spans working back again.
Having a 1.4.13 published with complete PtmP support will be much appreciated.
Regards
--
This is the option I will try.
I'll report my findings here.
My findings, after setting layer1_presence=ignore in chan_dahdi.conf
are :
== Starting D-Channel on span 1
== Starting D-Channel on span 2
== Primary D-Channel on span 1 up
== Primary D-Channel on span 2 up
foo*CLI
On Fri, Jun 22, 2012 at 08:07:54PM +1200, Alec Davis wrote:
Have a look at the latest blacklist sample in dahdi trunk
http://svnview.digium.com/svn/dahdi/tools/trunk/blacklist.sample?view=log
file: blacklist.sample
...
# Some mISDN drivers may try to attach to cards supported by DAHDI. If
2012/6/25, Tzafrir Cohen tzafrir.co...@xorcom.com:
On Fri, Jun 22, 2012 at 08:07:54PM +1200, Alec Davis wrote:
Have a look at the latest blacklist sample in dahdi trunk
http://svnview.digium.com/svn/dahdi/tools/trunk/blacklist.sample?view=log
file: blacklist.sample
...
# Some mISDN drivers
.
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Asterisk 10/1.6.1 and
Dahdi/Libpri compatilities in BRI /PtmP
My previous message was incomplete.
On thing to note is I had to forbid hfcmulti in modprobe.d in
the second box to comply with a warning from
2012/6/21, Richard Mudgett rmudg...@digium.com:
My previous message was incomplete.
On thing to note is I had to forbid hfcmulti in modprobe.d in the
second box to comply with a warning from dahdi. Without that, I could
see this line in the output of lsmod:
mISDN-core hfcmulti
1. What
.
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Asterisk 10/1.6.1 and
Dahdi/Libpri compatilities in BRI /PtmP
My previous message was incomplete.
On thing to note is I had to forbid hfcmulti in modprobe.d in
the second box to comply with a warning from dahdi
Am 21.06.2012 um 18:05 schrieb Richard Mudgett:
My previous message was incomplete.
On thing to note is I had to forbid hfcmulti in modprobe.d in the
second box to comply with a warning from dahdi. Without that, I could
see this line in the output of lsmod:
mISDN-core hfcmulti
1.
Hi,
After an upgrade, I discovered yesterday strange things I would like
to share here.
Basically, I'me comparing platforms:
The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk
1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3
and 2.5, I think).
The second one is a
My previous message was incomplete.
On thing to note is I had to forbid hfcmulti in modprobe.d in the
second box to comply with a warning from dahdi. Without that, I could
see this line in the output of lsmod:
mISDN-core hfcmulti
1. What is the root cause that makes a board change its sync
My previous message was incomplete.
On thing to note is I had to forbid hfcmulti in modprobe.d in the
second box to comply with a warning from dahdi. Without that, I could
see this line in the output of lsmod:
mISDN-core hfcmulti
1. What is the root cause that makes a board change
14 matches
Mail list logo
