Skip to main content

Internal Timing Causes Playback to Fail

Posted by ryan.tuttle on Tue, 05/25/2010

I'm currently running asterisk 1.4.26 with DAHDI 2.1.0 and I have internal timing enabled using DAHDI_Dummy. Also, my system has a Heartbeat/DRBD setup with a failover server for redundancy. My issue is when I have DRBD enabled playback of audio files fail. From what I'm gathering in my troubleshooting when the DRBD utilization goes up Asterisk is unable to connect to the DAHDI timing source. In this state asterisk will not even start until DRBD has been disabled. I'm planning on upgrading DAHDI and DRBD tonight to see if this fixes this issue and I just want to go over the process to make sure I get this right. First, I will compile the new version of DAHDI and install. Then I will go to my Asterisk source and do a make distclean, ./configure, make menuselect, make, then make install. Am I missing anything or should all be well.


Submitted by eeman on Tue, 05/25/2010 Permalink

your DRBD load should not be that high for a simple PBX.. some things to check into is your syncer rate. It might be trying to push at a rate higher than that network segment can maintain.

On the systems I built I used a dell 5424 gigabit switch with jumbo frames enabled. I created a seperate port-based vlan for the backside network with the MTU set to 9000

my syncer rate for a single shared block device is 65M

drbd version is 8.2.6

drbd82-8.2.6-1.el5.centos

Submitted by eeman on Tue, 05/25/2010 Permalink

whenever you first set up these drbd block devices its a good idea to throw bonnie-++ at it to see how the system responds under a heavy write and read.

Submitted by ryan.tuttle on Tue, 05/25/2010 Permalink

I've had Linbit in the system and all seems to be working just fine. Actually DBRD is working great and all other services are unaffected. For some reason Asterisk is unable to connect to the timing source and the only way to recover is to either stop and start DAHDI and Asterisk or stop DRBD and unplug the network cable connecting the two servers. From what we can tell there really isn't any major load on the system, DRBD or otherwise, it acts more like an IRQ conflict but I have no Digium hardware installed, just the dummy channel

The servers themselves are connected via a crossover cable, I can try increasing the MTU to 9000 on the interfaces themselves to see if that helps solve the issue.

Submitted by eeman on Tue, 05/25/2010 Permalink

the most recent version of dahdi (2.3?) doesnt use a dummy driver any more.. it has a different method of timing ... make sure you make distclean.