Reload causes DAHDI hangup (solved)

This is probably something specific to my install but I thought I’d ask to see if someone else had run into this. One of our call centers is on Asterisk 1.4 with FreePBX 2.8.1. We have a set of PRI’s in addition to our SIP/IAX trunks and previously they were handled by a Mediant Gateway but last night we switched them to a Digium Dahdi PRI board.

The problem I’m seeing is that whenever we make changes in FreePBX and do a reload, all the dahdi calls are disconnected. In the log, the events just before the reload look like this:

[Mar 3 16:19:09] VERBOSE[7697] logger.c: == End MixMonitor Recording DAHDI/2-1
[Mar 3 16:19:09] VERBOSE[7730] logger.c: == End MixMonitor Recording Local/129918706616891@qvcallpickup-97f9,1
[Mar 3 16:19:09] VERBOSE[7636] logger.c: == End MixMonitor Recording DAHDI/46-1
[Mar 3 16:19:09] VERBOSE[7759] logger.c: == End MixMonitor Recording DAHDI/6-1
[Mar 3 16:19:09] VERBOSE[7655] logger.c: == End MixMonitor Recording Local/129918701316825@qvcallpickup-25aa,1
[Mar 3 16:19:09] VERBOSE[7574] logger.c: == End MixMonitor Recording DAHDI/47-1
[Mar 3 16:19:09] VERBOSE[7860] logger.c: == Parsing ‘/etc/asterisk/manager.conf’: [Mar 3 16:19:09] VERBOSE[7860] logger.c: Found

We have other centers running on Asterisk 1.6 with FreePBX 2.8, that also have Dahdi boards interfacing with PRI’s and those centers don’t have this issue.

Is this something anyone has seen before? Could it be related to use of the FreePBX Dahdi module on the wrong version of Asterisk?

*** subsequent edit:

I upgraded dahdi and the problem resolved itself.

Thanks,

Jay