@Droojo wrote:

Hi i’ve swicthed to freepbx 14 a couple months ago, everything works flawlessly: sip phones, pjsip phones, https, external phones, video calling and so on. Recently a customer of mine choose to use ucp since the new look is really appealing, anyway he also wants to have his pbx local only. I knew from your wiki and my tests that the in-browser phone requires a secure connection with a valid certificate, which normally i would ensure with let’s encrypt, but this is not the case. Do i have a way or workaround to make it work with self-signed? or should i just give him an external softphone which handles calls and chat while disabling the ucp phone and xmpp?

Best regards and thanks for your time.

Posts: 1

Participants: 1

Read full topic

@tonyg wrote:

hi, i used the following command to get devel distro updates (specifically for libsrtp). everything seems ok, and i want to check for updates, but I want to go back to the production repo’s, can i do that and still retain my libsrtp 1.6? if so, how do i switch back to production?

thanks

this is the command i used
yum -y install sangoma-devel

Posts: 5

Participants: 2

Read full topic

@dayala wrote:

Some background:

• We don’t use voicemail
• Extensions are grouped by pickupgroup(s).

Issue:

When a call comes in, either internally or from outside and the destination extension is not answered (about after 5 or 6 rings), the caller stops hearing the ring on the call, the actual extension still rings and the other extensions in the pickup group start ringing too.

Because the caller stops hearing the ring they assume the call is lost and hang up.

Any help is appreciated,

Dennis

Posts: 1

Participants: 1

Read full topic

@nimeth wrote:

Hi there,

I’m having high-level of configuration problem with my FreePBX Distro - CentOS 7 installed on different network of a LAN that supposed to receive incoming call from another asterisk server version 11 on another network.

Below is simple trunk setting using GUI.
type=friend
qualify=yes
port=5060
insecure=port,invite
host=xxx.xxx.xxx.xxx
dtmfmode=rfc2833
disallow=all
context=9292-ivr
canreinvite=no
allow=ulaw
;username=userid
;secret=password
;context=from-trunk

Status of the sip trunk seems ok as below
Name/username Host Dyn Forcerport Comedia ACL Port Status Description
1000 (Unspecified) D No No A 0 UNKNOWN
CamGSM 172.16.100.117 Yes Yes 5060 OK (1 ms)

Inbound route configured as screen shot below.

Screen Shot 2017-12-13 at 4.15.26 PM.png2464x1024 194 KB

My custom destination was setup as below.

Screen Shot 2017-12-13 at 4.17.19 PM.png2470x706 62.9 KB

My dialplan was setup to handle incoming call with DID 9292 as below.

Screen Shot 2017-12-13 at 4.20.06 PM.png2398x1160 258 KB

When I called to a number that supposed to be routed by another asterisk server to this asterisk server with ‘9292’ as DID, the call seemed reach this server because I could the caller number xxxxxxxxx but ended immediately and this asterisk server logged error as below.
[2017-12-13 16:22:35] NOTICE[169955]: res_pjsip/pjsip_distributor.c:649 log_failed_request: Request ‘OPTIONS’ from ‘“asterisk” sip:asterisk@xxx.xxx.xxx.xxx’ failed for ‘172.16.100.117:5060’ (callid: 148cec020a1b470d739cfb9a4236fb1e@xxx.xxx.xxx.xxx:5060) - No matching endpoint found
[2017-12-13 16:22:40] NOTICE[169955]: res_pjsip/pjsip_distributor.c:649 log_failed_request: Request ‘INVITE’ from ‘“012551622” sip:xxxxxxxxx@xxx.xxx.xxx.xxx’ failed for ‘172.16.100.117:5060’ (callid: 6066013c4e8cb65027b5c2ca62c5b3b3@xxx.xxx.xxx.xxx:5060) - No matching endpoint found

Please somebody help me!

Thanks in advance.
Nimeth

Posts: 1

Participants: 1

Read full topic

@mhetterm wrote:

I used the now-production, latest script to upgrade from 10.13.66.22 to SNG7.

Everything went somewhat smoothly (had some modules that I needed to manually re-install, but nothing too bad.)

Extension-to-extension calls work, outgoing calls through our SIP trunk work, but incoming calls through our SIP trunk get a “this call cannot be completed” message. All calls (both directions) worked fine on 10.13.66.22.

Our SIP trunk provider is Broadvoice, and they use IP address authentication (no need to use user/secret). Approx 6 months ago I tried to get the trunk working on 10.13.x with pjsip, but was unable to, so I left it on chan_sip. All of the extensions are on the local LAN and are using pjsip.

My sip Settings for outgoing are:

type=peer
trustrpid=yes
sendrpid=yes
qualify=yes
nat=never
minexpiry=30
maxexpiry=3600
insecure=port,invite
host=206.15.150.13
dtmfmode=rfc2833
disallow=all
detectfax=yes
context=from-trunk
canreinvite=nonat
allow=ulaw&g729

Incoming:

User Context: default
User Details: [empty]
Register String [empty]

Again, those settings worked perfectly for both in and out on 10.13, but incoming does not work on SNG7 while outgoing does work.

Any advice is greatly appreciated, and am also happy to share any info/logs if they would be helpful!

Posts: 2

Participants: 1

Read full topic

@mhetterm wrote:

a) Had about 15 modules being reported as invalid - had to re-download/install. Could not do it via GUI (errors in reload process), had to do it via command line (fwconsole ma)

b) Under 10.13, I had a hybrid pjsip/chan_sip setup (trunks on chan_sip, extensions on pjsip). The upgrade switched me to a chan_sip only setup. Had to go into advanced settings and turn back on pjsip driver.

c) Trunks under chan_sip refused to accept incoming calls. Details here: Incoming calls to SIP Trunk not working after 10.13.66.22 -> SNG7 upgrade

d) Upgrade changed the centos rp_filter config. This messed up my somewhat rare dual NIC configuration. Had to fix by following these directions: http://jensd.be/468/linux/two-network-cards-rp_filter (short explanation: I need two NICs on the same subnet, with different IP addresses.)

Posts: 1

Participants: 1

Read full topic

@GSnover wrote:

Not good that they haven’t let us update in 2 years, but still damn impressive stability and uptime!

Posts: 2

Participants: 2

Read full topic

@sorento65 wrote:

Hi all

Outgoing call are not working, icoming working fine.
I’m useing Freepbx 14.0.1.19, Asteriks version 13.17.2 and my SIP Channel driver is chan_pjsip.

If I make a outgoing call, the asterisk is setting in the contact vield the username “asterisk”.
My sip trunk provider says that this is not valid.
But how can I change it?
I tried to change it by setting the field - pjsip settings, advanced, contact user, the SIP trunk username. But if I put this there, then nothing has changed at the next call.

An other way to find a solution was, that I change my SIP Channel driver to chan_sip, then the pbx will no longer send any register to my trunk provider. 

Have anybody any idea, what do I make wrong?

Thanks in advanced
Thomas

Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:2171001@xx.xx.xx.xx:5083 SIP/2.0
Message Header
Via: SIP/2.0/UDP xx.xx.xx.xx:5083;rport;branch=z9hG4bKPj2dccfcff-68c8-4549-b051-d1b856dcb725
From: sip:2171140@192.168.33.11;tag=ae49fdf0-2dd5-4230-826d-feb7ccee7118
To: sip:2171001@xx.xx.xx.xx
Contact: sip:asterisk@xx.xx.xx.xx:5083
Contact URI: sip:asterisk@xx.xx.xx.xx:5083
Call-ID: 68b2025f-e073-41f7-bb2c-a70069053d5a
CSeq: 29351 INVITE
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, MESSAGE, REFER
Supported: 100rel, timer, replaces, norefersub
Session-Expires: 1800
Min-SE: 90
Max-Forwards: 70
User-Agent: FPBX-14.0.1.19(13.17.2)
Content-Type: application/sdp
Content-Length: 309
Message Body

Posts: 1

Participants: 1

Read full topic

@tim007 wrote:

I am in the process of attempting to upgrade my FreePBX 10.13.66 system to SNG7. I installed what is listed as the current upgrade RPM in the Wiki (https://wiki.freepbx.org/display/PPS/Upgrading+from+FreePBX+10.13.66+to+SNG7).

“yum -y install http://package1.sangoma.net/distro-upgrade-1712-5.sng7.noarch.rpm”

And then started the upgrade: “distro-upgrade”

It makes it past the reboot, but then gets stuck at “######### Repairing areminder #########”. The last entry in “post_sngupdate” is “Running fwconsole ma downloadinstall areminder”.

I found an Issue that had been closed that was referencing this for a previous version of the upgrade script, but said that it had been fixed. https://issues.freepbx.org/browse/FREEPBX-16220

I tried running the script to repair from a failed upgrade, but it is getting stuck at the same step.

Any help would be appreciated; I would prefer not to have to roll back!

Posts: 2

Participants: 1

Read full topic

@adamskalicky wrote:

Hi All,

I was running a report today and long calls from the conference app are reporting as “00:02” when the actual call us over 3 hours. I am thinking it is a presentation issue with CDR, but am wondering if there is any way of fixing it for better reporting.

Posts: 1

Participants: 1

Read full topic

@dkmortensen wrote:

Running a new install of FreePBX distro SG7. Should we be regularly installing system & module updates?

Posts: 2

Participants: 2

Read full topic

@xrobau wrote:

I’ve just published a new ISO, with the release notes here:

https://wiki.freepbx.org/display/PPS/SNG7+PBX+Release+Notes

The new hotness is that we’re now enabling G729 by default. If you install a new machine with the 1712 ISO (or newer), the open source G729 codec will be installed and activated. Note that this is only on a NEW install. If you’re upgrading, you’ll need to manually enable g729 by running the (hopefully, obviously named) ‘g729’ command, which will then let you enable it.

Saying that, G729 is old technology. It sounds bad, it uses a huge amount of CPU, and is only really useful if you’re using dialup, or other extremely limited bandwidth connections. If your internet connection is that slow, you have many other problems 8)

Please, use G722 or Opus! It’s much faster, it sounds better, and it handles packet loss much MUCH better.

Posts: 1

Participants: 1

Read full topic

@MAA wrote:

Hello,

I need a Queue Reports module that shows stats and reports for the past period (the last few months).
(I tried Asternic Call Center Stats Lite 1.5, but it shows reports only after the installation date).
What can you recommend?

Posts: 2

Participants: 2

Read full topic

@assos40 wrote:

Hi,
I am trying to istall latest freepbx distro (14) on a brand new computer.
AMD RYZEN 5 1500X
Gigabyte GA-AB350M-HD3
Memory Corsair DDR4 2666Mhz.
Installation hangs on this screen

20171220_203441.jpg3264x1836 2.44 MB

Posts: 1

Participants: 1

Read full topic

@iceget wrote:

dear community,

i have a question:
if i call out from regional city, then i always must dial the local regional prefix number for this city.
how i can do that, that if i call only the main number (without prefix) that always the prefix for the regional city will be added on the outgoing call?

thank you very much, many greets

Posts: 2

Participants: 2

Read full topic

@bjtrammell wrote:

To be honest, I seem to have nothing but problems with this version of FreePBX. I’m having a problem now with one of the repo’s failing to download an update because of a “conflict”, but I’ve not installed anything outside of the normal FreePBX repositories, and I’ve not added any additional software to it.

Here is the error:

[root@sip yum.repos.d]# yum update -y
Loaded plugins: fastestmirror, versionlock
sng-base | 3.6 kB 00:00:00
sng-epel | 4.7 kB 00:00:00
sng-updates | 3.4 kB 00:00:00
(1/6): sng-base/7/x86_64/group_gz | 156 kB 00:00:00
(2/6): sng-epel/7/x86_64/group_gz | 266 kB 00:00:00
(3/6): sng-epel/7/x86_64/updateinfo | 857 kB 00:00:00
(4/6): sng-base/7/x86_64/primary_db | 5.7 MB 00:00:01
(5/6): sng-updates/7/x86_64/primary_db | 4.5 MB 00:00:01
(6/6): sng-epel/7/x86_64/primary_db | 6.1 MB 00:00:02
Determining fastest mirrors
Resolving Dependencies
–> Running transaction check
—> Package systemd.x86_64 0:219-30.el7_3.9 will be updated
—> Package systemd.x86_64 0:219-42.el7_4.1 will be updated
—> Package systemd.x86_64 0:219-42.el7_4.4 will be an update
—> Package systemd-libs.x86_64 0:219-30.el7_3.9 will be updated
—> Package systemd-libs.x86_64 0:219-42.el7_4.1 will be updated
—> Package systemd-libs.x86_64 0:219-42.el7_4.4 will be an update
—> Package systemd-sysv.x86_64 0:219-30.el7_3.9 will be updated
—> Package systemd-sysv.x86_64 0:219-42.el7_4.1 will be updated
—> Package systemd-sysv.x86_64 0:219-42.el7_4.4 will be an update
–> Processing Conflict: systemd-219-42.el7_4.4.x86_64 conflicts dracut < 033-499
–> Finished Dependency Resolution
Error: systemd conflicts with dracut-033-463.el7_3.2.x86_64
You could try using --skip-broken to work around the problem
[root@sip yum.repos.d]#

Again I have not changed anything on the core OS. So there should not be any conflicts with anything, or at least I would hope. Either way, here is what was done and what I’ve done so far to troubleshoot:

What I’ve done so far:

• Attempted to skip the broken packages Failed, same message as above
• Attempted to disable all repos and enabled them one by one ** Error only occurs on “UPDATES” repo **
• Searched for old packages (suggest by these forums, none exist)

About the machine:

• The Official FreePBX ISO was used to install this system
• It is a virtual machine, and has already been reimaged 4 times because of other issues
• All DID’s are working with the exception of one provider (may be firewall issue).
• It is running FreePBX 14.0.1.1 (updated it today, issue existed well before today [ going on like 2 weeks])
• cat /etc/centos-release-upstream states Derived from Red Hat Enterprise Linux 7.4 (Source)
• cat /etc/sangoma-release states Sangoma Linux release 7.4.1712 (Core)

If I missed some key information, please let me know and I will provide it. Thank you to anyone who helps, and happy holidays (merry christmas)

Posts: 1

Participants: 1

Read full topic

@assos40 wrote:

Hi,
Try to run latest Freepbx 14 distro on gigabyte-ryzen system.
AMD RYZEN 5 1500X
Gigabyte GA-AB350M-HD3
Memory Corsair DDR4 2666Mhz.
I had trouble installing the ditro ,which i resolved by updating the bios.
Now freepbx is installed but it randomly freezes/hangs all the time.
Googling around i find that number of people had experienced similar issues and the solution turned out to be to install centos 7 with kernel version 4.12 and above.
Is there a possibility in near future that the Freepbx distro has this kernel version. ?
Or should i go for another mb and cpu ?
Thanks

Posts: 1

Participants: 1

Read full topic

@FN_GM wrote:

Hello,

I am running FreePBX Distro10.13.66-22 I would like to use FreePBX 14. This is a production system. Am I right in assuming I use this method to upgrade to SNG7 please? -
https://wiki.freepbx.org/display/PPS/Upgrading+from+FreePBX+10.13.66+to+SNG7

I am assuming this upgrade isn’t a Beta upgrade and is safe to do on a production system please? (will have backups and VM snapshot)

Many thanks for your help.

Posts: 3

Participants: 2

Read full topic

@FN_GM wrote:

Hello,

I am looking to update to SNG7 on 2 PBX. I followed this page - https://wiki.freepbx.org/display/PPS/Upgrading+from+FreePBX+10.13.66+to+SNG7

One server passed the prerequisite check no problem. The second is reporting i686 RPMs have been installed. This is a much older installation and someone else supported it for a couple of years in my absence, so might have been tinkered with.

Can anyone please give some pointers or tips as to what will happen if I push through the upgrade? Are we expecting everything to work ok please?

Below is a result from the command.

Thanks for your help, much appreciated.

Checking prerequsites…
Checking FreePBX Version [ ] - 13.0.192.19
Checking bitsize of machine [ ] - x86_64
Checking for 32 bit packages [ ✘ ]
i686 RPMs have been found on this machine. This will cause upgrade
issues. The offending RPMs are below. They must be removed or upgraded
to 64 bit packages.

openssl-1.0.1e-30.el6.11.i686
mongodb-server-2.4.14-4.el6.i686
incron-0.5.9-2.el6.rf.i686
libcom_err-1.41.12-21.el6.i686
libselinux-2.0.94-5.8.el6.i686
boost-program-options-1.41.0-25.el6.centos.i686
libgcc-4.4.7-11.el6.i686
libicu-4.2.1-9.1.el6_2.i686
ncurses-libs-5.7-3.20090208.el6.i686
glibc-2.12-1.166.el6_7.7.i686
zlib-1.2.3-29.el6.i686
bzip2-libs-1.0.5-7.el6_0.i686
krb5-libs-1.10.3-37.el6_6.i686
readline-6.0-4.el6.i686
pcre-7.8-6.el6.i686
nss-softokn-freebl-3.14.3-22.el6_6.i686
boost-iostreams-1.41.0-25.el6.centos.i686
v8-3.14.5.10-9.el6.i686
libstdc+±4.4.7-11.el6.i686
boost-filesystem-1.41.0-25.el6.centos.i686
snappy-1.1.0-1.el6.i686
boost-system-1.41.0-25.el6.centos.i686
keyutils-libs-1.4-5.el6.i686
boost-thread-1.41.0-25.el6.centos.i686

    The Distro Upgrader may be able to repair this for you automatically.
    However, there may be an outage whilst it is doing it.

Posts: 1

Participants: 1

Read full topic

@juesor wrote:

Every time i run “fwconsole restart” i need to change timing and agents from 30 to 35 seconds on queue timing.

I can repeat this trouble.

cat /etc/schmooze/pbx-version

10.13.66-17

FreePBX 13.0.192.19 is licensed under the GPL

Queues Pro 13.0.27

Connected to Asterisk 13.17.1

Has anyone had this issue lately ?

Posts: 2

Participants: 2

Read full topic