Upgrade from 13 to 14 Error on phase 2

August 14, 2017, 4:40 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: FreePBX 13 -> 14 Upgrade Script kills DAHDI

Tony,

I ran "yum install http://yum.schmoozecom.net/schmooze-commercial/6/x86_64/RPMS/fail2ban/fail2ban-0.8.14-1.shmz65.1.131.noarch.rpm" (I changed it from .130 to 131 based on your last post) and that seemed to run fine, it showed it updated.

I ran the "rpm -e "asterisk-sounds-extra-en-gsm asterisk-sounds-core-en-gsm" --nodeps" cmd but that came back as "error: package asterisk-sounds-extra-en-gsm asterisk-sounds-core-en-gsm is not installed"

Rebooted the server and the same issue is occurring, same error as before.

I found the issue ticket tied to my post (15569) and I ran the follow cmds that seemed to get me past the loop.

"yum remove asterisk-sounds-core-en-gsm-1.4.25-94_centos5.noarch"

I'll post if i have any other issues.

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 4:43 pm

≫ Next: Upgrade from 13 to 14 Error on phase 2

≪ Previous: Upgrade from 13 to 14 Error on phase 2

I replied in the other post you replied to...

Looks like you need to apply

https://issues.freepbx.org/browse/FREEPBX-15491?focusedCommentId=108399&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-108399

(this was the ticket I opened, I had, amongst other things, DAHDI issues...)

Don't install the sangoma-devel package, you don't want to use that repo under normal circumstances and the package is now available from the usual repos...

Good luck and have a nice day!

Nick

↧

Upgrade from 13 to 14 Error on phase 2

August 14, 2017, 4:56 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: Upgrade to FreePBX 14 from 13 failing

It is not a module. There is the normal FreePBX 13 to 14 upgrade module for users not on the distro but when you install it and try to use it says you have a FreePBX Distro and need to follow the wiki and link to wiki which at the very top says it's beta.

The reason you need to use the upgrade scripts is FreePBX requires PHP 5.6 that is only available on SNG7 and not the old unsupported SHMZ OS 6 so we need to first upgrade the OS and all the packages.

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 5:16 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: Upgrade from 13 to 14 Error on phase 2

Thanks. That was useful. DAHDI is now updated, but unfortunately, it still hasn't fixed my problem:

[root@freepbx dev]# yum list *dahdi*
Loaded plugins: fastestmirror, kmod, versionlock
Loading mirror speeds from cached hostfile
Installed Packages
asterisk13-dahdi.x86_64                                         13.17.0-3.sng7                                 @sng-pkgs
dahdi-firmware.noarch                                           3.0.0-1.sng7                                   @sng-pkgs
dahdi-linux.x86_64                                              2.11.1-1.26.sng                                installed
dahdi-linux-devel.x86_64                                        2.11.1-1.26.sng                                @sng-pkgs
dahdi-tools.x86_64                                              2.11.1-1.23.sng                                @sng-pkgs
dahdi-tools-doc.x86_64                                          2.11.1-1.23.sng                                @sng-pkgs
kmod-dahdi-linux.x86_64                                         2.11.1-9.sng7                                  @sng-pkgs
Available Packages
asterisk11-dahdi.x86_64                                         11.25.1-1.sng7                                 sng-pkgs
asterisk14-dahdi.x86_64                                         14.6.0-3.sng7                                  sng-pkgs
dahdi-firmware-a4a.noarch                                       a0017-1.3.sng                                  sng-pkgs
dahdi-firmware-a4b.noarch                                       d001e-1.3.sng                                  sng-pkgs
dahdi-firmware-a8a.noarch                                       1d0017-1.3.sng                                 sng-pkgs
dahdi-firmware-a8b.noarch                                       1f001e-1.3.sng                                 sng-pkgs
dahdi-firmware-hx8.noarch                                       2.06-1.3.sng                                   sng-pkgs
dahdi-firmware-oct6114-032.noarch                               1.07.01-1.3.sng                                sng-pkgs
dahdi-firmware-oct6114-064.noarch                               1.05.01-1.3.sng                                sng-pkgs
dahdi-firmware-oct6114-128.noarch                               1.05.01-1.3.sng                                sng-pkgs
dahdi-firmware-oct6114-256.noarch                               1.05.01-1.3.sng                                sng-pkgs
dahdi-firmware-oct6126-128.noarch                               01.07.04-1.3.sng                               sng-pkgs
dahdi-firmware-tc400m.noarch                                    MR6.12-1.3.sng                                 sng-pkgs
dahdi-firmware-te133.noarch                                     780019-1.3.sng                                 sng-pkgs
dahdi-firmware-te134.noarch                                     780017-1.3.sng                                 sng-pkgs
dahdi-firmware-te435.noarch                                     e0019-1.3.sng                                  sng-pkgs
dahdi-firmware-te436.noarch                                     10017-1.3.sng                                  sng-pkgs
dahdi-firmware-te820.noarch                                     1.76-1.3.sng                                   sng-pkgs
dahdi-firmware-vpmoct032.noarch                                 1.12.0-1.3.sng                                 sng-pkgs
[root@freepbx dev]# modprobe wctdm24xxp
modprobe: FATAL: Module wctdm24xxp not found.
[root@freepbx dev]#

and lspci -vv reports (amongst other things):

03:00.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
        Subsystem: ATCOM Technology co., LTD. AX400P 4-port analog card
        Flags: bus master, medium devsel, latency 64, IRQ 11
        I/O ports at cc00 [size=256]
        Memory at fe7ff000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2
        Kernel modules: netjet, hisax

Any other pointers?

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 5:24 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: Upgrade to FreePBX 14 from 13 failing

That is not a supported card in DAHDI. You must of hand complied DAHDI at one point before for that card. Digium only provides DAHDi for Digium cards.

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 5:28 pm

≫ Next: Upgrade from 13 to 14 Error on phase 2

≪ Previous: Upgrade to FreePBX 14 from 13 failing

This card definitely worked out of the box with FreePBX 13 / CentOS 6.x and stock DAHDI. These are the instructions I got with the card, when I first got it, and they worked fine:

Here is the simple instruction as the card is Plug-&-Play installation once Dahdi has installed. In the Linux CLI; please run the below commands:
1) modprobe wctdm24xxp
2) service asterisk stop
3) service asterisk start
4) amportal restart
5) dahdi_genconf
6) dahdi_cfg -vvvv
7) lsdahdi (you should see all your ports)
8) reboot (reboot your system, & all the ports should be in service)

This is the card: http://www.nicherons.com/TDM410P.html

↧

Upgrade from 13 to 14 Error on phase 2

August 14, 2017, 5:30 pm

≫ Next: FreePBX 14 Release Candidate

≪ Previous: Upgrade to FreePBX 14 from 13 failing

Michael

You dont need to rebuild. What are your current logs showing is the problem. We just published a new RPM that resolves all open bugs.

If you run the following commands.

yum install http://yum2.schmoozecom.net/schmooze-commercial/6/x86_64/RPMS/fail2ban/fail2ban-0.8.14-1.shmz65.1.131.noarch.rpm

rpm -e "asterisk-sounds-extra-en-gsm asterisk-sounds-core-en-gsm" --nodeps

Now this command will restart the upgrade.

rm /var/run/post_sngupdate && /usr/sbin/post_upgrade

↧

FreePBX 14 Release Candidate

August 14, 2017, 5:36 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: Upgrade from 13 to 14 Error on phase 2

Awesome, thanks! :smiley: Would it also be possible to get the links on the downloads page updated to reflect its availability?

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 5:46 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: FreePBX 14 Release Candidate

Not sure. I am not familiar with the card and only worked with Digium and Sangoma cards before. Maybe something changed in newer DAHDI to not support it.

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 5:47 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: Upgrade to FreePBX 14 from 13 failing

Hi!

Can you do a

locate wctdm24xxp

and post the result here?

If it doesn't work, issue a /etc/cron.daily/mlocate before...

Can you also issue a

uname -r

and once again post the results here?

I am no expert in the naming of modules relative to the kernel version but I am expecting a mismatch...

Somehow a weak-updates folder seems to fix things for me here (looks like it's its purpose to do that), it is as if the mismatch got self corrected on my box?

Modprobing that module works on my system but I have an A200 so I cannot say if things actually work for a Digium card..

Good luck and have a nice day!

Nick

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 5:52 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: Upgrade to FreePBX 14 from 13 failing

Thanks for the help, guys. Here's the results of the tests:

[root@freepbx dev]# locate wctdm24xxp
[root@freepbx dev]# /etc/cron.daily/mlocate
[root@freepbx dev]# locate wctdm24xxp
/usr/lib/modules/3.10.0-514.2.2.el7.x86_64/extra/dahdi/wctdm24xxp
/usr/lib/modules/3.10.0-514.2.2.el7.x86_64/extra/dahdi/wctdm24xxp/wctdm24xxp.ko
[root@freepbx dev]# uname -r
3.10.0-514.26.2.el7.x86_64
[root@freepbx dev]#

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 5:59 pm

≫ Next: Upgrade to FreePBX 14 from 13 failing

≪ Previous: Upgrade to FreePBX 14 from 13 failing

Hi!

This is what I get

[root@jester admin]# locate wctdm24xxp
/usr/lib/modules/3.10.0-514.2.2.el7.x86_64/extra/dahdi/wctdm24xxp
/usr/lib/modules/3.10.0-514.2.2.el7.x86_64/extra/dahdi/wctdm24xxp/wctdm24xxp.ko
/usr/lib/modules/3.10.0-514.26.2.el7.x86_64/weak-updates/dahdi/wctdm24xxp
/usr/lib/modules/3.10.0-514.26.2.el7.x86_64/weak-updates/dahdi/wctdm24xxp/wctdm24xxp.ko

And those entries in weak-updates are symbolic links back to /usr/lib/modules/3.10.0-514.2.2.el7.x86_64/extra/...

I think, like I said no guru in this, that there is some sort of kernel version mismatch...

I will post about it in the ticket I opened since it did deal with DAHDI issues after the update (amongst other things...).

Good luck and have a nice day!

Nick

↧

Upgrade to FreePBX 14 from 13 failing

August 14, 2017, 6:15 pm

≫ Next: Upgrade from 13 to 14 Error on phase 2

≪ Previous: Upgrade to FreePBX 14 from 13 failing

If you feel adventurous and have nothing to lose, apparently running

weak-modules --add-kernel

would take care of adding those symlinks...

Only do this as a last resort, I tested this and it seems to works fine but less than an hour ago I didn't know about this and I might be wrong about it...

Good luck and have a nice day!

Nick

↧

Upgrade from 13 to 14 Error on phase 2

August 14, 2017, 6:29 pm

≫ Next: Upgrade from 13 to 14 Error on phase 2

≪ Previous: Upgrade to FreePBX 14 from 13 failing

Now i am getting an httpd start error.

Aug 14 21:08:22 MyServer httpd[5983]: (98)Address already in use: AH00072: make_sock: could not bind to ad...:]:80
Aug 14 21:08:22 MyServer httpd[5983]: (98)Address already in use: AH00072: make_sock: could not bind to ad....0:96
Aug 14 21:08:22 MyServer httpd[5983]: no listening sockets available, shutting down
Aug 14 21:08:22 MyServer httpd[5983]: AH00015: Unable to open logs
Aug 14 21:08:22 MyServer systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Aug 14 21:08:22 MyServer kill[5994]: kill: cannot find process ""
Aug 14 21:08:22 MyServer systemd[1]: httpd.service: control process exited, code=exited status=1
Aug 14 21:08:22 MyServer systemd[1]: Failed to start The Apache HTTP Server.
Aug 14 21:08:22 MyServer systemd[1]: Unit httpd.service entered failed state.
Aug 14 21:08:22 MyServer systemd[1]: httpd.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

When I run a netstat --proto=inet,inet6 -pnl i do not see anything on those two ports.

↧

Upgrade from 13 to 14 Error on phase 2

August 14, 2017, 6:33 pm

≫ Next: Upgrade from 13 to 14 Error on phase 2

≪ Previous: Upgrade from 13 to 14 Error on phase 2

lsof -i :80 lsof -i :96

↧

Upgrade from 13 to 14 Error on phase 2

August 14, 2017, 6:55 pm

≫ Next: Upgrade from 13 to 14 Error on phase 2

≪ Previous: Upgrade from 13 to 14 Error on phase 2

Both reported back blank

↧

Upgrade from 13 to 14 Error on phase 2

August 14, 2017, 6:55 pm

≫ Next: FreePBX 14 Release Candidate

≪ Previous: Upgrade from 13 to 14 Error on phase 2

Try running the following to get apache back

mv /etc/httpd/conf.d/schmoozecom.conf /etc/httpd/conf.d/schmoozecom.conf.bak service httpd restart`

↧

FreePBX 14 Release Candidate

August 14, 2017, 6:59 pm

≫ Next: Why register multiple lines on same phone to same extension?

≪ Previous: Upgrade from 13 to 14 Error on phase 2

@joelfreeman If you access freepbx.org via https://www.freepbx.org these links should be reflected moving forward.

↧

Why register multiple lines on same phone to same extension?

August 14, 2017, 7:17 pm

≫ Next: Best way to alert agents to calls in a queue?

≪ Previous: FreePBX 14 Release Candidate

I'm also using Grandstream and chansip. If I want a second call to come through I just turn on CW call waiting on the extension, the second call comes right through.

↧

Best way to alert agents to calls in a queue?

August 15, 2017, 7:02 am

≫ Next: Upgrade from 13 to 14 Error on phase 2

≪ Previous: Why register multiple lines on same phone to same extension?

There are two parts to this:
1) Asterisk needs to put the information into hint that your phone will interpret.
2) Setting up the phone to respond to the hint's value and programming a response based on what the button should do.

Note that these are independent actions. Asterisk doesn't actually talk to the phone's BLF at all, and every phone is going to handle these differently.

Most phones allow BLFs respond to Hints, so adding a hint when there are calls in the queue (or the number of people in a queue) should be a reasonably simple change. You could submit a feature request to track the number of people in a queue and put it in a hint (or pay Sangoma to support you).

The problem in the second part of the question is having people picking up calls for queues that they aren't logged in to. Dynamic agents in a queue are a reasonably simple extension to the system, and adding a soft button (even one associated with a BLF) that logged the agent into the queue should be pretty simple.

↧

Latest Images