[root@$HOSTNAME freepbx]# wget -P /etc/yum.repos.d/ http://yum.schmoozecom.net/schmooze-commercial/schmooze-commercial.repo
--2017-01-03 15:50:32--  http://yum.schmoozecom.net/schmooze-commercial/schmooze-commercial.repo
Resolving yum.schmoozecom.net (yum.schmoozecom.net)... 199.102.239.168, 162.253.134.138
Connecting to yum.schmoozecom.net (yum.schmoozecom.net)|199.102.239.168|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 287 [text/plain]
Saving to: ‘/etc/yum.repos.d/schmooze-commercial.repo’

100%[================================================================================================================================>] 287         --.-K/s   in 0s

2017-01-03 15:50:33 (27.0 MB/s) - ‘/etc/yum.repos.d/schmooze-commercial.repo’ saved [287/287]

[root@$HOSTNAME freepbx]#
[root@HOSTNAME freepbx]# yum clean all
Loaded plugins: fastestmirror, langpacks
Cleaning repos: base extras schmooze-commercial updates
Cleaning up everything
Cleaning up list of fastest mirrors
[root@$HOSTNAME freepbx]# yum -y install php-5.3-zend-guard-loader sysadmin fail2ban incron ImageMagick
Loaded plugins: fastestmirror, langpacks
base                                                                                                                                               | 3.6 kB  00:00:00
extras                                                                                                                                             | 3.4 kB  00:00:00


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: schmooze-commercial/7/x86_64