Multiple ZAPTEL /DAHDI Releases AND Wanpipe Crashing


On systems, where ZAPTEL has been upgraded from old releases, it is possible for a kernel module directory to contain MULTIPLE ZAPTEL drivers.

Old Zaptel install dir: /lib/modules/$(uname -r)/zaptel

New Zaptel install dir: /lib/modules/$(uname -r)/misc

If the old zaptel installation was NOT removed, the new installation would NOT overwrite the old kernel modules.  In this case the OLD modules would continue to be loaded, even though the new ones were installed.

Check:
The check if this condition exists on your machine run:

#>modprobe -l  | grep zaptel.*o 

     jika dahdi maka

    #> modprobe -l | grep dahdi.*.0

IMPORTANT: If multiple zaptel modules are found, the problem must be fixed before starting WANPIPE!

In this scenario, if a customer starts WANPIPE drivers based on NEW ZAPTEL sources, the WANPIPE will crash. The WANPIPE driver shares structures with ZAPTEL, thus, a result of mismatched structures is a kernel panic.

Solution:

The solution in this case is to REMOVE the old zaptel modules.

     #>modprobe -l | grep zaptel | xargs rm
#>depmod -a 

dahdi

     #>modprobe -l | grep dahdi| xargs rm
#>depmod -a 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

shisdew

Listens until think alike

moses.spaceku@yahoo.com / voip ipbx

Hosted PBX, IP-PBX SOHO/ CALL CENTER, VOICE GATEWAY, VOICE CARD, COST EFECTIVE SOLUTIONS (LCR), GSM/CDMA GATEWAY

%d bloggers like this: