From reading the documentation that came with dahdi-tools I gathered that the
second span should be span=2,2... designating it as a backup timing source
in case your primary span=1,1... should die. I am not sure that you can
designate two primary timing sources and have seamless failover in a
Hi list,
Ive got a server with 6 ports on it (4+2 port card) we have a DS3 delivering
all voice DS1's to us. Carrier has a trunkgroup for the first 8 span (we
only have the first 6 plugged in right now). Everything works fine until we
fail the primary D channel (D's are on 24,48) the secondary
On Mon, Dec 28, 2009 at 12:45 PM, Ron McCarthy ronmc...@gmail.com wrote:
Hi list,
Ive got a server with 6 ports on it (4+2 port card) we have a DS3
delivering all voice DS1's to us. Carrier has a trunkgroup for the first 8
span (we only have the first 6 plugged in right now). Everything
Steve Totaro wrote:
I would call Digium but last I knew, NFAS only worked across one card.
NFAS is implemented in libpri and Asterisk (chan_zap or chan_dahdi),
which means it has no concept of 'cards' at all. Cards are handled at
the Zaptel/DAHDI layer, and are presented as spans full of
Ill try another mx of libPRI, it has to be something goofy.
Thanks for the input guys.
On Mon, Dec 28, 2009 at 11:00 AM, Kevin P. Fleming kpflem...@digium.comwrote:
Steve Totaro wrote:
I would call Digium but last I knew, NFAS only worked across one card.
NFAS is implemented in libpri