Quantcast
Channel: FreePBX Community Forums - Latest posts
Viewing all 227999 articles
Browse latest View live

Newbie: Configuration of Bandwidth.com on FreePBX 14

$
0
0

Hello all! I recently was tasked with setting up an Asterisk system utilizing FreePBX and Bandwidth.com service. I've set up my trunking but it's not working right unfortunately.

I configured manually my IP settings for local and public (I bought a device with 2 RJ45 ports for this) and am running them separately, one on local and the other bypassing my router direct to the inet for public. My trunking is set up as best I could figure but it doesn't seem to be working right.

The two issues I seem to be having are as follows. I'll include any information I think to be related for diagnostic purposes. Thanks in advance for taking a look.

1: out of my 4 trunks (Bandwidth.com wants you to set up redundant trunking, in and outbound) only two are shown as online - unmonitored. The other two are offline Regardless, when I attempt to make an oubtound call or inbound call, I only recieve dead air. No message, no ring.

My trunk configuration is as follows:

  • in the prefix for all dial plans to accomodate Bandwidth's E.164

Outbound
allow=ulaw
dtmfmode=rfc2833
host=216.82.224.202
nat=yes
port=5060
type=peer
canreinvite=yes

Inbound
User Context is my DID, formatted as 10 digit
canreinvite=yes
context=from-trunk
dtmfmode=rfc2833
insecure=very
nat=yes
port=5060
type=peer

The second issue I'm having is that the internet connection doesn't seem to be up and running. Oddly, my trunk is showing as oline, but when I try to activate or download dial plans it doesn't connect probably and throws up an error

My ethernet config files (ifcfg-eth0/1)are as follows

TYPE=Ethernet
BOOTPROTO=no
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=NO
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=eth1
UUID=(Removed for privacy)
DEVICE=eth1
ONBOOT=yes
IPADDR= (Removed, but set up as my public IP)
NETMASK=255.255.255.240
GATEWAY=(Removed, but set up as my publlic Gateway)
ZONE=external
DESCRIPTION="In/Out to world"

TYPE=Ethernet
BOOTPROTO=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=no
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eth0
UUID=(Removed for privacy)
DEVICE=eth0
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
NETMASK=255.255.255.0
IPADDR=192.168.0.77
GATEWAY=192.168.0.1
ZONE=internal
DESCRIPTION="unset"

Am I missing something in my config files? it's all set up according to what I've read on the wiki.

Thanks in advance. Any more tips for a noob like me, especially for another user using Bandwidth.com would be appreciated!


Upgrade from 13 to 14 Error on phase 2

$
0
0

Just checking--so run those commands and start over at
yum -y install ...package1.sangoma.net/distro-upgrade-1707-12.sng7.noarch.rpm

Is that correct?

Strange DND issue between phone and UCP

$
0
0

It looks like using a BLF (busy lamp field) is theoretically how I do this - it should allow me to use the system feature code, but still toggle the notification light on the phone. First attempt didn't work, but not 100% sure I'm doing it right. Will continue to play.

Hmmmm....occurs to me though, that this issue still would've happened if I do that. Assuming they use the keys they're fine, but they'd have been fine if they used the keys in this instance too. Either way, if they manually dial the feature code (whether deliberately or accidentally), then the light won't be on and we'll be confused. :slight_smile: I think I'm just going to leave the key as is (or maybe get BLF working, mostly out of curiosity), but change the feature code to something that won't be accidentally dialed.

Upgrade from 13 to 14 Error on phase 2

$
0
0

My system is up and running now but the GUI doesn't work in the browser.

Repeat IVR recording

$
0
0

Hi guys,
I have an IVR with multiple recordings (each line is 1 file):
Pre IVR
1. Welcome to blablabla
2. Please listen carefully as our menu has changed
3. If you know your party’s blablabla

IVR
4. for blablabla press 1
5. for blablabla press 2
6. for blablabla press 3
7. To hear this message again, press *

Post IVR
8. Thank you for calling blablabla, and have a great day

My question:
When the * is pressed, how do I set the IVR recording to repeat itself without the "Pre IVR" and "Post IVR" ?

Thanks

Strange DND issue between phone and UCP

$
0
0

No if you setup a BLF if they dial the feature code the BLF would update.

Strange DND issue between phone and UCP

$
0
0

Really? Interesting. However, I realised once I got the BLF to work - it's just the little LED directly next to the key. When using the phone's built in DND, it not only lights that, but the big LED at the top of the phone, plus it actually says "DND On" on the screen. People are used to this, so for now I'll just change the feature code so it's less likely to be dialled by accident, and see how it goes for a while. Will keep this in the back pocket in case there are issues with that, though.

Thanks!

Every Monday all of our phones are down saying "invalid account"

$
0
0

The update ran just after midnight Saturday night. We were closed all day Sunday. When we arrived to work Monday morning all the phones were not working with the message on the display saying "invalid account". This is an exact repeat of what happened the week before. More than 24 hours after the update, the phones still say "invalid account". We have to reboot FreePBX to get them to start working again.


Upgrade from 13 to 14 Error on phase 2

$
0
0

How did you get it to work? I keep hitting this new wall:

Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory : 107 M RSS (499 MB VSZ)
Started: Mon Aug 14 16:08:50 2017 - 00:13 ago
State : Running, pid: 2134

Thanks for any suggestions.

My solution for implementing Flowroute SMS into Asterisk

$
0
0

Yes, the callbacks are authenticated, using an access key and security key.

And you have a very valid point regarding SSL - I am looking into that today. I knew letsencrypt existed, but never really had a need for an SSL cert in the past.

I do have restrictions in place in Apache that only allow access from Flowroute's specified IPs, but I suppose that it wouldn't be that hard for a hacker to spoof the IP.

Voxbeam Inbound route issue

$
0
0

Can anyone please help me configure my inbound route with voxbeam. I called the company and they said that my system does not accept the invite from them. I spent hours trying to figure it out. I learned a lot. Both trunks do not register but the outbound trunk sends audio and I can make calls. However my DID is not working for me. Voxbeam have configuration instruction for Asterisk but not for freepbx. I am running Freepbx on 64 bit machine. Please help

Upgrade from 13 to 14 Error on phase 2

$
0
0

What do you mean a miracle. This is a beta upgrade script and says not to do it in production. Please tell me you did not do this in production.

If you just wait after running the yum command it should work after a minute or two. Make sure you are updating to the correct fail2ban. Version .131 not 1.30

Responsive firewall constantly blocking remote users

$
0
0

What could be an exploit that doesn't require a login attempt? Can there be anything else that hackers can attack with other than trying to login to the server? Do you have any examples?

I'm afraid ddns and openvpn aren't good options for mobile users. It's a bit too much.

Upgrade to FreePBX 14 from 13 failing

$
0
0

Right. I've managed to make some good progress thanks to the 'issues' link provided by Marbled:

https://issues.freepbx.org/browse/FREEPBX-15500

From here I downloaded and ran the post_update script, which ran until it got to modifying the httpd.conf file, where it then hung up. After waiting an age, I gave up and reset the machine.

I can now access FreePBX via the GUI :slight_smile:

Only problem I now have is that I can't get DAHDI to work. It looks like I might be running an old version:

[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-firmware-xorcom.noarch                      1.0-1                                                        @anaconda-CentOS-201207061011.x86_64/6.3
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-linux-kmod-debuginfo.x86_64                 2.11.1-22_centos6.2.6.32_642.6.2.el6.x86_64                  @pbx/6
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-22_centos6.2.6.32_642.6.2.el6.x86_64                  @pbx/6
schmooze-dahdi.noarch                             1.0.0-2                                                      @pbx/6
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]#

How can I fix this???

Upgrade from 13 to 14 Error on phase 2

$
0
0

Banners and links say 14 will help with several speed issues and other things we have fought with for the last year. I arrived at work this morning to a notice on the dashboard: new module available for installation. I go to modules, and sure enough, there is a new module to upgrade to 14. I install it. A new menu item is available to upgrade the system. It says it’s a FreePBX distro, so I must click here. I stepped my way through several notes of encouragement, none of which showed a skull and crossbones. Then on the last page it says it’s Beta. Good one.

Yes, it’s all my fault. I’m rebuilding overnight.


Upgrade from 13 to 14 Error on phase 2

$
0
0

Hi!

You mean as in not accessible, not responding?

If so, if you issue

wget -qO- http://localhost | grep FreePBX

this from the command line of your system, what does this give you?

If you see something which has "FreePBX Administration" on the first line, the GUI actually works but is not accessible from the outside and I had that problem but thought it was related to my setup.

Are you using the FreePBX firewall? Is your system protected by another firewall?

In my case I am not using the FreePBX firewall and it is protected by another firewall... If you are in the same situation, please let me know and i will have something for you to try...

Good luck and have a nice day!

Nick

FreePBX 13 -> 14 Upgrade Script kills DAHDI

$
0
0

I can't get dahdi to run either, and also noticed that I appear to have some of the el6 packages. Were you able to fix this, and if so, how?

[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-firmware-xorcom.noarch                      1.0-1                                                        @anaconda-CentOS-201207061011.x86_64/6.3
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-linux-kmod-debuginfo.x86_64                 2.11.1-22_centos6.2.6.32_642.6.2.el6.x86_64                  @pbx/6
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-22_centos6.2.6.32_642.6.2.el6.x86_64                  @pbx/6
schmooze-dahdi.noarch                             1.0.0-2                                                      @pbx/6
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]#

Upgrade from 13 to 14 Error on phase 2

Upgrade from 13 to 14 Error on phase 2

$
0
0

Hi!

I didn't know the upgrade script could be offered as a module but if this is indeed how you run this it should NOT have been made available as it is undergoing Beta testing.

@GameGamer43, @tm1000, @tonyclewis, @lgaetz any idea what is happening here?

Good luck and have a nice day!

Nick

FreePBX 13 -> 14 Upgrade Script kills DAHDI

Viewing all 227999 articles
Browse latest View live