> >> > 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
> >>
2012/6/26, Richard Mudgett :
>> > 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
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
--
___
2012/6/22, Olivier :
> 2012/6/21, 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-cor
2012/6/25, Tzafrir Cohen :
> 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 a
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.
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 hfcm
>> [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Olivier
>> Sent: Thursday, 21 June 2012 9:37 p.m.
>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>> Subject: Re: [asterisk-users] Asterisk 10/1.6.1 and
>> Dahdi/Libpri compatilities in
2012/6/21, 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. What i
ne 2012 9:37 p.m.
> 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 mo
> 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
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 sou
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
14 matches
Mail list logo
