Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: SARK devs on June 08, 2009, 02:16:36 PM

Title: 2.2.3-8 and 2.3.1-10
Post by: SARK devs on June 08, 2009, 02:16:36 PM

Both up in their respective http folders.

http://sarkpabx.com/sail

new documentation on PCI card detection for 2.3.1-10 - see the docs wiki

http://sarkpbx.com/twiki

Kind Regards

S

Title: Re: 2.2.3-8 and 2.3.1-10
Post by: soprom on June 08, 2009, 08:39:33 PM

Is there something special to know or can I "rpm -Uvh..." new version?

Got it: http://sarkpbx.com/twiki/bin/view/Main/DocChapter03c

Title: Re: 2.2.3-8 and 2.3.1-10
Post by: SARK devs on June 08, 2009, 09:16:32 PM

Hi Sophie

You should not use rpm -Uvh, because it won't run the post-install updates correctly.  Instead you should use yum localinstall.

Best

S

Title: Re: 2.2.3-8 and 2.3.1-10
Post by: soprom on June 08, 2009, 10:42:40 PM

I followed the procedure on the wiki but I had to manually remove zaptel.

Everything installed correctly but PCI device from the server-manager is not working. The error message is "Couldn't open DAHDI channels File - ending"

dmesg says:

Code: [Select]

dahdi: Telephony Interface Registered on major 196
dahdi: Version: 2.1.0.4
ACPI: PCI Interrupt 0000:05:04.0[A] -> GSI 16 (level, low) -> IRQ 169
Freshmaker version: 73
Freshmaker passed register test
Module 0: Installed -- AUTO FXO (FCC mode)
Module 1: Installed -- AUTO FXS/DPO
Module 2: Installed -- AUTO FXS/DPO
Module 3: Not installed
Found a Wildcard TDM: Wildcard TDM400P REV I (3 modules)
dahdi: Registered tone zone 0 (United States / North America)
/etc/init.d/dahdi restart returns

Code: [Select]

Unloading DAHDI hardware modules: ERROR: Module dahdi is in use
errorLoading DAHDI hardware modules:
 wctdm:                        [  OK  ]
Running dahdi_cfg:      [  OK  ]
open error on /dev/dahdi/1: No such file or directory
There is also a pci known to zap:

Code: [Select]

pbx*CLI> zap show status
Description                              Alarms     IRQ        bpviol     CRC4     
Wildcard TDM400P REV I Board 5           UNCONFIGUR 0          0          0   

and to dahdi:

Code: [Select]

pbx*CLI> dahdi show status
Description                              Alarms     IRQ        bpviol     CRC4     
Wildcard TDM400P REV I Board 5           UNCONFIGUR 0          0          0        

Title: Re: 2.2.3-8 and 2.3.1-10
Post by: SARK devs on June 08, 2009, 11:59:10 PM

Yes - we have just found this bug.  It is because no sample file for /etc/dahdi/system.conf is installed with the ATrpms.  Fortunately, the cure is simple and we have already added an update to svn...

at the console type

Code: [Select]

dahdi_genconf
Now run PCI again.  and you should be fine.  Please note that we have also added an update to the Wiki PCI card notes in the step-by-step section and to the comments upon dahdi_genconf regarding an error condition which it creates.

Kind Regards

S 

Title: Re: 2.2.3-8 and 2.3.1-10
Post by: soprom on June 09, 2009, 12:00:50 AM

It works now. Don't know what I did to get it working tho... One of the following:
/usr/sbin/dahdi_genconf
dahdi_tool
dahdi_cfg -vvv

oups... our posts are almost at the same time.

Title: Re: 2.2.3-8 and 2.3.1-10
Post by: soprom on June 09, 2009, 12:35:48 AM

post deleted...