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.
Okay -- if it's not clock slip (also my first inclination): Your observation that the problem goes away after the card is disabled and re-enabled, then returns after the maintenance routine runs, is a major clue. Here's what you need to find out: -Where does the card get its configuration at start time? -What is in that configuration? -What procedures does the maintenance routine perform? In this case, you want as much detail as you can get. Talk to Nortel if necessary. As an experiment -- can you disable the maintenance routine entirely? If so, do it -- see whether the problem "remains gone" the following day. You want to confirm that it's that routine that is causing the change, and not something else. -Stephen- _______________________________________________ --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
