"Page All" stopped working after upgrading to CentOS 5.7, Asterisk 1.8.6

[Ramblin]

I recently (on the weekend) updated to CentOS 5.7 and Asterisk 1.8.6 using the update-source script. I also updated the php using update100.

I did this on a 64-bit install that was originally a Piaf 1.7.5.5 and on a 32-bit install that was originally a Piaf 1.7.5.6

All seemed to be working fine until someone pointed out that the "Page All" feature (on the 64-bit system) was not working anymore. I tested the other (32-bit) system and had the same problem.

Everything else is still working fine. I can directly intercom (using *80<ext> ) and it works fine. All other features work fine. But when I use "Page All", the phones briefly connect, just long enough for the "Ping" to be heard and then the phones disconnect.

I am using Aastra endpoints, 53i and 57i, with v2.6 (latest v2 firmware). The issue is the same across all phones. And it was working perfectly until the upgrade.

The new php version is working fine; I have SugarCRM installed on the same server and it continues to work great.

My Status output is: (I have no ZAP connections, all SIP)
PBX in a Flash PURPLE Status

│ Asterisk = ONLINE | Zap/Dahdi = UNKNOWN | MySQL = ONLINE │
│ SSH = ONLINE | Apache = ONLINE | Iptables = ONLINE │
│ Fail2ban = OFFLINE | Internet = ONLINE | Ip6Tables = ONLINE │
│ BlueTooth = ONLINE | Hidd = ONLINE | NTPD = ONLINE │
│ SendMail = ONLINE | Samba = OFFLINE | Webmin = ONLINE │
│ Ethernet0 = ONLINE | Ethernet1 = N/A | Wlan0 = N/A │
│ │
│ PBX in a Flash Version = 1.7.5.6 Running on *HARDWARE* │
│ FreePBX Version = 2.8.1.4 │
│ Running Asterisk Version = 1.8.6.0 │
│ Asterisk Source Version = 1.8.6.0 │
│ Zap/Dahdi Source Version = N/A │
│ Libpri Source Version = 1.4.12 │
│ IP Address = 192.168.1.225 on eth0 │
│ Operating System = CentOS release 5.7 (Final) │
│ Kernel Version = 2.6.18-274.7.1.el5 - 32 Bit │
│ │

I have double-checked and the Paging/Intercom feature is still enabled (which it would have to be for the Intercom to still work, which it does) and the "Page All" code is stll what it was and is still in properly programmed into the "Page All" softkey. I also tried manually dialing the extension for "Page All" and the exact same thing happened: a quick connection, announced by the Page ping and then a disconnect.

Any ideas?

 

[phoneguy]

You issue is this
Zap/Dahdi Source Version = N/A │

Paging uses app meet-me which requires dahdi to be installed and compiled.

 

[Ramblin]

Thanks for the quick reply

I was wondering about that.

How do I re-enable Zap/Dahdi?

It was working before the upgrade.

I also just realized that Conferencing, which also uses the meet-me app, is not now working, and it was working fine before.

It seems I am not alone in this. See
http://pbxinaflash.com/community/threads/anonymous-callerid-filtering-another-version.946/?t=9467

When I tried service dahdi start, I got
root@pbx:~ $ service dahdi start
Loading DAHDI hardware modules:
FATAL: Module dahdi not found.
wct4xxp: FATAL: Module wct4xxp not found. [FAILED]
wcte12xp: FATAL: Module wcte12xp not found. [FAILED]
wct1xxp: FATAL: Module wct1xxp not found. [FAILED]
wcte11xp: FATAL: Module wcte11xp not found. [FAILED]
wctdm24xxp: FATAL: Module wctdm24xxp not found. [FAILED]
wcfxo: FATAL: Module wcfxo not found. [FAILED]
wctdm: FATAL: Module wctdm not found. [FAILED]
wcb4xxp: FATAL: Module wcb4xxp not found. [FAILED]
wctc4xxp: FATAL: Module wctc4xxp not found. [FAILED]
xpp_usb: FATAL: Module xpp_usb not found. [FAILED]
Error: missing /dev/dahdi!

I'd really rather not have to go outside the Piaf modules and manually do something if I don't have to but am not sure what the options are right now.

Ideas?

Ah, the beauties of bleeding edge ...

 

[darmock]

The fact that status can't give you a dahdi version means that

/usr/src/dahdi is missing or not not named /usr/src/dahdi.

Also dahdi is not running because of this. Sounds like a failed install to me.

You can try running the experimental update-source and see if it will install dahdi and correctly compile it. It *should* beyond that you can can just download dahdi and install it by hand.

it is in the thread you referenced.


Tom

 

[Ramblin]

It is now working

With a slight edit to the posting (assume just passage of time and newer editions), the following commands from the CLI got it working. A re-run of update-source, update-programs and update-fixes did not get dahdi installed and running so instead:

from the CLI:

cd /usr/src
wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/releases/dahdi-linux-complete-2.5.0.2+2.5.0.2.tar.gz
mv dahdi dahdi.old
tar -xvf dahdi-linux-complete-2.5.0.2+2.5.0.2.tar.gz
mv dahdi-linux-complete-2.5.0.2+2.5.0.2 dahdi

cd /usr/src/dahdi
make all
make install
make config

cd /usr/src
service dahdi start

Also, go into Webmin and set dahdi to start on startup from now on.
You could also do this at the CLI by typing
chkconfig dahdi on
but I kike the visual confirmation in Webmin

All is now working.

 

[johnnyb440]

We built 2 test boxes using 1.7.5.7 and I can verify that it does not work with that install. Dahdi is not installed by default it looks like, so we need a workaround.

 

[darmock]

We built 2 test boxes using 1.7.5.7 and I can verify that it does not work with that install. Dahdi is not installed by default it looks like, so we need a workaround.

As usual not enough information

You built 2 boxes? So What! What version of asterisk did you install (1757 has 5)? Where is the status output from at least one of the boxes? Did you take the time to look in the /var/log/install-purple.log and see what the problem was? How come there are no relevant log snippets posted showing where the error occurred. Do not post the whole log! We are not interested in the whole thing just the relevant snippets not more that 15-20 lines.

This is equivalent to going to your mechanic and saying

"car broke"... "fix"

Can you imagine how much they would charge you?


Tom

 

[darmock]

Here is the status output from a reference system in the PIAF labs built Dec 12, 2011 @ 1323 ET. Notice that dahdi is present just fine. This was built using the 17572 ISO however a system built the day before that using the 17571 ISO is exactly the same. This of course has the latest version of asterisk running 1872 and the latest STABLE version of dahdi 2502.

Not sure where your problems are but looking thru the logs will probably tell you the error is somewhere on your system or your connectivity as opposed to a general fault with the PIAF installer.