Steve Totaro wrote: > Eric "ManxPower" Wieling wrote: >> Gleim, Jason wrote: >> >> >>> I thought that might be an issue too... and it was originally. When we >>> started out, I had the Sangoma card generating the timing for the span >>> but we could never get the d-channel to come up. Turns out that since we >>> were connected to the PSTN, we had to let the Nortel set the timing on >>> the span because it was receiving the timing from the CO. (Essentially >>> the timing needed to 'flow' away from the CO) >>> >>> But, since we got that fixed and the span started working, I felt that >>> timing wasn't the source of the problem. Plus, if we dump the error >>> counters on both ends, they are not incrementing... even if the span is >>> up for several days and we clearly have the audio problems. The slip >>> counters, framing error, etc all stay at 0 and you would figure that if >>> it was timing slip, those would be incrementing on at least one of the >>> sides. >>> >> Does "cat /proc/interrupts" show any interrupt sharing with the Digium card? >> >> > > I hope not since he has a Sangoma card which I believe does not suffer > from the same IRQ woes that Digium cards do.
Silly me. Samgoma cards seem LESS prone to IRQ latency issues, but they are not immune from it. _______________________________________________ --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
