Been working with Yealink support on this and after confirming this happening with the T46G and the T42G phones, their support upped the severity and I got an answer back to add the below setting to the configuration files.
transfer.hang_up_after_success_trans = 3
I did so on the T46G, disabled the custom firewall rules, and had the operator repeat the transfer.
No ghost ringback.
I'll leave the custom firewall disabled and see if it stays good all day.
I'll test in more detail over the weekend or on Tuesday, whichever time I have a tech on site.
This was happening because for some reason the conbridge.conf file (or an include therein) was not being created correctly and thus because conf files were missing confbridge was never loaded. I believe this was because conferences was not originally included in the tarball for 13 but we fixed this so it should be OK???? Not sure...
It was fixed this week? It was just six days ago that we saw it, but it's not been re-run since then.
@scottalanmiller So since I posted the OP, I found out what the issue was. (or at least eliminated it by changing a setting.) On old versions of FreePBX, in Advanced SIP settings, in order to enable TCP connections, you had to manually type:
In new versions, there is now a button to enable TCP. Having both settings enabled seems to cause these issues. Most likely, the config file for sip.conf gets messed up having these similar/identical settings. Removing the old entry eliminates the errors.
@NetworkNerd & @JaredBusch - We would love to have you both. We can offer you 20% off this year's AstriCon registration with promo code "VUC" at checkout. Otherwise, make sure to check out the Early Bird pricing for next year's event (which ends in late June)
You can also block it at the SIP level with your provider. Do that along with international dialing, save yourself some headache.
If the SIP provider offers this, definitely. Using a route to do it stops your extensions (if compromised) from using them. Blocking them at the SIP carrier stops your PBX if compromised from calling them.
Neither stops you if the SIP provider is the one making the calls (looking at you, Megapath.)
Sounds like your Mitel just isn't up to snuff if it requires that and you are using a kludge to get around a hobbled system.
Now you're assuming facts not in evidence. I have no idea if the Mitel can have a one button transfer to a conference bridge (more likely two button, conference and the conference location).
As for the setup, I've never used a setup with a one button transfer to a conference bridge, so I couldn't reference it. I learned something :)
So if you haven't used the one button transfer, and you have a Mitel, is it because you've just not bothered to use it, even though it was the driver that brought you to the Mitel, or do you feel that the Mitel is not up to snuff? Or is there a third option I am missing?
The company was using Inter-Tel (bought my Mitel) when I joined the company. Conferencing at the phone level I'm sure was not why they went with Inter-Tel - it's just a feature they discovered and continued to use.
The default installation of Elastix has more services running than are typically needed or desired on a PBX. These services eat far more memory that is necessary and can very easily be cleaned up to improve memory utilization.
First we will stop a series of unnecessary services from starting at boot time (this will disable shared storage, local email handling, new hardware detection, etc. so be aware that this does stop some things but any service that proves to be needed is trivial to re-enable.)
chkconfig nfslock off
chkconfig cyrus-imapd off
chkconfig iscsi off
chkconfig iscsid off
chkconfig netfs off
chkconfig kudzu off
Further, if your system is like mine you likely use the web server very lightly but will find that the default configuration of Apache is set to spawn, by default, eight processes. This is far too many for a normal deployment. Each process uses memory. For an average deployment of Elastix, three is more than enough. You need only raise this number if web performance suffers. This will not impact telephony performance regardless.
In the file /etc/httpd/conf/httpd.conf we need to edit the section:
You can wait for the system to reboot or restart Apache manually:
service httpd restart
And finally, to control swapping activity on the box, assuming that you want to avoid swapping when unnecessary, which I do because my box is virtualized, simply add this line on to /etc/sysctl.conf:
vm.swappiness = 10
You’ll want to test that number carefully. A setting of “10” is quite standard for virtualized systems. The default is “60”. For a physical deployment the higher value is likely better as it allows CentOS to make better decisions about how to utilize memory for maximum throughput. But on a virtualized system we really want to avoid, typically, any additional contention at the storage IO layer.
[Testing on Elastix 2.0 and 2.3]
That makes sense. This is a FreePBX install from FreePBX ISO as far as I can tell from looking at it and all files come from the Schmooze repos and it is causing it to be very out of date compared to standard CentOS 6.
Wait, what? Does the FreePBX distro change what repos yum uses for base CentOS updates?
Yeah, it uses Schmooze repos instead of CentOS ones. I can change that, of course, but by default...
Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.