My apologies for using acronyms.
As the UC 40 has two antenna ports on the back, it appeared to me that in some future form the UC 40 may also have a wireless access point embedded.
I believe I have also seem a photo that had two antennas on the back of the UC 40.
Thank you,
I have today gone to my FreePBX 14.0.1.4 machine and done my weekly maintenance of Admin - Updates and hit the System Updates and I have been presented with a list of errors the first of which is:
RPM command errored, tried to run '/usr/bin/rpm -q --queryformat "%{VERSION}.%{RELEASE}\n" alsa-lib.x86_64 audit.x86_64 audit-libs.x86_64 authconfig.x86_64 bash.x86_64 bind-libs.x86_64 bind-libs-lite.x86_64 bind-license.noarch bind-utils.x86_64 binutils.x86_64 biosdevname.x86_64 bluez-libs.x86_64 boost-filesystem.x86_64 boost-program-options.x86_64 boost-system.x86_64 boost-thread.x86_64 btrfs-progs.x86_64 ca-certificates.noarch cairo.x86_64 chkconfig.x86_64 chrony.x86_64 copy-jdk-configs.noarch cpio.x86_64 cpp.x86_64 cronie.x86_64 cronie-noanacron.x86_64 cryptsetup.x86_64 cryptsetup-libs.x86_64 cups-libs.x86_64 curl.x86_64 cyrus-sasl-lib.x86_64 cyrus-sasl-plain.x86_64 device-mapper.x86_64 device-mapper-event.x86_64 device-mapper-event-libs.x86_64 device-mapper-libs.x86_64 device-mapper-multipath.x86_64 device-mapper-multipath-libs.x86_64 device-mapper-persistent-data.x86_64 dhcp-common.x86_64 dhcp-libs.x86_64 dmidecode.x86_64 dnsmasq.x86_64 dos2unix.x86_64 dracut.x86_64 dracut-network.x86_64 e2fsprogs.x86_64 e2fsprogs-libs.x86_64 efibootmgr.x86_64 efivar-libs.x86_64 elfutils-libelf.x86_64 elfutils-libs.x86_64 ethtool.x86_64 fcoe-utils.x86_64 fipscheck.x86_64 fipscheck-lib.x86_64 firewalld.noarch firewalld-filesystem.noarch fontconfig.x86_64 freeradius.x86_64 freetype.x86_64 fuse.x86_64 fuse-libs.x86_64 gcc.x86_64 gcc-c++.x86_64 gdk-pixbuf2.x86_64 gettext.x86_64 gettext-libs.x86_64 gfs2-utils.x86_64 ghostscript.x86_64 glib2.x86_64 glibc.x86_64 glibc-common.x86_64 glibc-devel.x86_64 glibc-headers.x86_64 glibmm24.x86_64 gmp.x86_64 gnutls.x86_64 gobject-introspection.x86_64 grep.x86_64 grub2.x86_64 grub2-tools.x86_64 grubby.x86_64 gzip.x86_64 harfbuzz.x86_64 httpd.x86_64 httpd-tools.x86_64 hwdata.x86_64 initscripts.x86_64 iproute.x86_64 iprutils.x86_64 ipset.x86_64 ipset-libs.x86_64 iptables.x86_64 iptables-services.x86_64 iputils.x86_64 irqbalance.x86_64 iscsi-initiator-utils.x86_64
Am I the only one and is it possible to fix this issue?
Any help would be greatly appreciated.
I think from using both pjSip is easier 
setup is really assisted by the verbose logging
Hello all,
is there a solution for a hotel module to freepbx ?
Hello,
First time posting here.
I have set up IVR. Our Elastix has 3 inbound routes. Before we had as a destination Time Conditions- which pointed directly to a time group, same on three inbound routes. Now I have created a new time condition - which points to IVR.
When I update inbound routes destination to the new time condition, only one number works, other two point in old time condition, even though in freepbx it shows that it is pointing in the new one.
If I point the new time condition directly to a time group, all three inbound routes work fine. Also if I point old time condition to IVR, only one inbound route works. If i delete old time condition, two inbound routes don't work anymore at all.
It is a strange behavior which I can't figure it out. It seems that the IVR is causing the problem.
We are using Elastix 2.5.0 which comes with FreePBX 2.11.0 and Asteriks 11.17.1.
Any help would be greatly appriciated.
Thanks
Issue fixed : declaration of memcpy_from_msg function wanpipe driver was the issue . Current wanpipe driver is not compatible with kernel 3.10.0-693.2.2.el7
After installing a standby machine with Freepbx using a copy of the downloaded ISO from today I get excatly the same issue so I am certain this is nothing to do with my equipment or my install and I find it incredible that nobody else has encountered the issue?
There's a big long thread about it here:
https://community.freepbx.org/t/system-updates-gets-exception-even-after-reboot/44597. In summary:
Hi!
Current Wanpipe (7.0.20.13-1) for the FreePBX distro (from its repo) is. I am running 3.10.0-693.2.2.el7...
Whatever is needed to make Wanpipe works has already done, it just need to be published to wherever you got it from (where?).
Good luck and have a nice day!
Nick
I'm also running latest wanpipe on latest kernel without any issue:
[root@freepbx uk]# uname -r
3.10.0-693.2.2.el7.x86_64
[root@freepbx uk]# yum list *wanpipe*
Loaded plugins: fastestmirror, kmod, versionlock
Loading mirror speeds from cached hostfile
Installed Packages
kmod-wanpipe.x86_64 7.0.20.13-1.sng7 @sng-pkgs
wanpipe.x86_64 7.0.20.13-1.sng7 @sng-pkgs
Available Packages
wanpipe-devel.x86_64 7.0.20.13-1.sng7 sng-pkgs
[root@freepbx uk]#Hi chaser!
He is not using the FreePBX distro but a "real" Centos...
The package we use would quite likely be compatible (especially since Sangoma 7 is derived from Centos 7) but I am not sure I would start mix and matching packages like that... If something in the repo is ever meant solely for Sangoma 7 (s)he might break his system...
Have a nice day!
Nick
This is a question I have found so many posts on but nothing really has a comprehensive answer. Either I am over complicating this and looking at it from the wrong angle, or it's not as common a requirement as I first thought.
We have 2 inbound SIP trunks to our FreePBX server. Each with a main inbound DID. We ant to have a BLF key on each SIP handset that has the ability to show an incoming call and the ability to answer that call.
The inbound DID is directed to a Ring Group, but users outside the ring group want the ability to take external calls, without their phone ringing.
I have seen posts where suggestions have been made to use dummy extensions in the ring group, but in all of these instances, these extensions have had to be registered to a device.
Surely there is a simple way to achieve such a simple legacy requirement...
Any feedback or suggestion is welcome.
Thanks in advance
Hi,
I'm not using freepbx distro. I'm using centos 7 & wanpipe from ftp://ftp.sangoma.com/linux/current_wanpipe/wanpipe-current.tgz .
The issue i found was a duplicate declaration function in wanpipe wanpipe-7.0.21/kdrvtmp/af_wanpipe_src.c memcpy_from_msg(void *data, struct msghdr *msg, int len) . So i modified the file /usr/src/kernels/3.10.0-693.2.2.el7.x86_64/include/linux/skbuff.h and commented the function . It's working fine . Hope this will help some one until it get fixed
Thanks
Rong groups have no state information so their is no BLF to a ring group.
Thank you for pointing me in the right direction I will give that a try on my standby server and see if it resolves the issues I am having.
Hi!
The real solution would be to have the modifications that were done for the distro published on the FTP site...
I opened a ticket for this for the distro a few days ago (we needed a new package because of the kernel change) and it is still not closed because there is something else to take care of.
While this is not a FreePBX distro issue I am sure that the person who is taking care of the Wanpipe package for the FreePBX distro will know what to do so I will put a comment about your issue there...
Have a nice day!
Nick
Ps: I am currently writing this from my phone as I am currently on my way to work. It's possible I might have to wait until I get there to add that comment because it truly is a pain to write on the phone with the nice roads we have here...
Howdy community
Could you pls help me in the following matter, since I got blind for the solution after one day of inspection/trying/configuration/testing:
We want that the complete (internal) dialling number is shown on the callees side when doing external calls. Since our VoIP provider told me that he only sees the ´13´ (int. ext.) in the logs, this may be the reason that 'unknown' is shown and not the complete dialling number. I tried using the Set CallerID feature, the related outbound route to 'intra company' state, the trunks CID feature to Allow Any CID and also set the Outbond CID for the extension to the complete dailling number. But this does not show any dialling number at all on callee side; only an 'unknown' text. Additionally we have a problem that the CID of the SIP Trunk is no longer shown during external calls when set back to Force Trunk CID. Here we also get the 'unknown' hint.
Which additional info may you need? Just let me know.
Current Asterisk Version: 11.25.1
FreePBX 13.0.192.18
Any help will be highly appreciated and thanks in advance.
Kind regards,
Roger
The trunk should not be intra company, that sets it to use internal CID not external
Yes you are right; it is not the trunk, it is the outbound route which is set this way.