I’m an old guy with the attitude, if it isn’t broken, don’t fix it!
That’s why we are running FreePBX 2.4.0 with Trixbox 184.108.40.206 with 6 SIP SNOM phones and 4 Zap channels. No problems until now (see below).
ADVICE ON UPGRADE
The PBX window advising on available upgrades says:
core 220.127.116.11 (current: 18.104.22.168)
conferences 22.214.171.124 (current: 126.96.36.199)
paging 188.8.131.52 (current: 184.108.40.206)
framework 220.127.116.11 (current: 18.104.22.168)
queues 22.214.171.124 (current: 126.96.36.199)
recordings 188.8.131.52 (current: 184.108.40.206)
music 220.127.116.11 (current: 18.104.22.168)
But I’m too scared to download anything in case it goes wrong!
Can anyone suggest an order to install the updates, to minimise problems please??
And do we do Trixbox first then PBX??
ADVICE ON PROBLEM
On some days the phones now behave erratically. The symptoms are…
Trixbox CE shows physical memory is >95% (normally <40%).
This error is reported with the Cron Manager: “The following commands failed with the listed error /var/lib/asterisk/bin/module_admin listonline (255)
Added 25 minutes ago (cron_manager.EXECFAIL).”
The error log files show:
[Feb 19 08:57:51] WARNING chan_sip.c: Remote host can’t match request BYE to call ‘[email protected]’. Giving up.
[Feb 19 09:03:12] WARNING app_macro.c: Context ‘macro-dialout-trunk-predial-hook’ for macro ‘dialout-trunk-predial-hook’ lacks ‘s’ extension, priority 1.
Feb 19 10:56:54 trixbox1 yum-updatesd-helper: error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: trixbox. Please verify its path and try again
Feb 19 10:58:17 trixbox1 smbd: [2010/02/19 10:58:17, 0] smbd/nttrans.c:call_nt_transact_ioctl(2481)
Feb 19 10:58:17 trixbox1 smbd: call_nt_transact_ioctl(0x900eb): Currently not implemented.
Feb 19 11:00:17 trixbox1 smbd: [2010/02/19 11:00:17, 0] lib/util_sock.c:get_peer_addr(1232)
A reboot of Trixbox seems to fix things for a few days, with immediate return of CPU memory.
However, now Trixbox fails on the shutdown and displays this message: "Starting killall: unloading zaptel. Hardware drivers: error module wctdm is in use, module zaptel is in use by wctdm."
On hard reboot, everything loads OK but at the final stage of loading Asterix, the Trixbox server gives the message “error fetching interface information”.
I am an IT novice. This is all strange to me.
Can anyone make any sense of it please???