On Thu, Feb 19, 2009 at 5:00 PM, Dave Fullerton < [email protected]> wrote:
> Hello all, > > I have two machines I'm connecting with TDMOE (dahdi dynamic spans) and > I have a question about timing parameters. By my understanding one > machine should be the source of the timing and the other a slave of that > timing. > > So on machine A I have the following in system.conf: > dynamic=eth,eth0/00:0C:29:55:89:7E,24,0 > > On machine B I have this is system.conf: > dynamic=eth,eth0/00:18:8B:C7:F6:94,24,1 > > So machine A is the source of timing and B is slave to it. If both of > these machines also have a digium (TDM400P in one and a TE110P in the > other) card in them is this configuration still correct or should I use > 0 for timing on both? > > The reason I ask is if I boot both machines fresh and I execute > dahdi_cfg on machine A first and then machine B I either get a kernel > oops (with 2.6.27.11) or complete freeze (with 2.6.23.17) on machine B > pretty much without fail. If I do machine B first and then A everything > works fine. I'm using dahdi_linux 2.1.0.4 on both. > > I know I can just use SIP or IAX or anything else to connect these two > machines, but I'm using this as a learning experience to play with PRI > setups. > > Thanks > > -Dave > > I cannot speak about DAHDI but I can tell you that the timing provided by the card is different than the timing of a PRI Span. I suspect that DAHDI has a bug in TDMoE because the spans should either not come up but Asterisk should run and the Kernel should not bomb out, at least I have never seen this with Zaptel. If nobody answers your question with a real answer, I suggest opening a bug report. -- Thanks, Steve Totaro +18887771888 (Toll Free) +12409381212 (Cell)
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
