Hi @Aaron After setting the port in mysql you need to the run the port update hook.

php /var/www/html/admin/modules/sysadmin/hooks/update-ports

Thanks for your reply, and I bookmarked the issue tracker for (possible) future issues.
However, I think I have solved my problem.
I untared my backup and looked around, but could not find any information about my pjsip endpoints.
So I checked the modules and yes, there are some missing module updates including Backup&Restore. Updated it, ran backup again and now it includes: ./customdir/etc/asterisk/pjsip.endpoint.conf with endpoint informations.
I will try to import it later and see if it really works. But looks good to me.

thanks

Hello
Queue log files are present and working.
I would like to be able to analyze answered calls and I think it’s easier from the cdr database.
Is it complex to have queue_log table filled ?
thx

Am I wrong if I think that FreePBX is handling disabled call waiting wrong? Or is this more a Asterisk thing? To my knowledge disabled call waiting should work like this:

1. Caller calls extension
2. FreePBX sends busy message to the caller if some of the extensions SIP devices is busy
3. FreePBX sends missed call message to all of the extensions SIP devices

But in FreePBX step 3 does not happen. So for example if a user has two SIP devices, e.g. a deskphone and a softphone and disables call waiting for his extension in the UCP, the user won’t get any information if someone tried to call him while he was on the phone.
I would be really interested in other opinios to this topic. Maybe I am missing something here.

Because at the PBX level, disabling call waiting is for the extension itself not the devices that are connected to it. The PBX will look at the current state of the endpoint at the PBX level.

So if you turn off Call Waiting and an incoming call comes in, the PBX will look at the state of the extension. If it returns IN_USE, meaning there is an active call it will attempt to send the call to the devices registered/listed contacts for the extension. If the state returns BUSY the call is routed to the BUSY destination, no attempt to dial the phone(s) are made because the extension is busy, it isn’t accepting more calls.

The deprecated function warnings are internal technical debt warnings. A long time ago FreePBX used classless functions for everything then PHP5.x hit and OOP was the way to do things. I.e. use class based functions.

So these warnings are reminders that these functions need to be moved to the class based functions for the module.

How can I remove them to class based?

Makes sense. Thank your for your explanation. I was thinking that there is maybe some rfc that allows the pbx to send a SIP notify message to the phone about missed calls or something like that.
This sounds to me that call waiting should be better handled on the client site instead of FreePBX. Sadly our softphone “Sangoma Phone Desktop” has no setting for call waiting.

All you need to do is update the modules and code across the board in all modules to remove using classless functions and moving them into the class functions.

Our edge device was updated last year about this time & when it was, the Cisco 7960 phones (flashed to SIP) we’ve used for years began having troubles. Meraki update happened and the very next day, the phones started playing silence for 2-5 seconds at the beginning of random calls. Nothing changed on either the phones or the PBX. I fought to understand and fix this, but it turned out to be hopeless. Gave the SCCP module a whirl, but that has it’s own problems & sadly the bug report I made had no responses after several months. Management finally decided that I could spend the money to replace all 70+ phones in our building, despite our people loving the 7960 phones.

I’ve heard good things about Polycom phones, so bought a small number of VVX400, VVX410, and VVX500 phones, testing each with a few different people to get their opinions on them and if they’d work well for us. After working through a few quirks, they behaved well and I decided on the VVX410. I ordered a bunch of them from ebay and over the course of a few weeks, replaced all of our old Cisco 7960 phones with VVX410 phones.

While I was doing this, I didn’t really pay any attention to the firmware revision that was on the phones themselves… figured that I could address it if there were issues, but they were likely all the same or similar given that the phones were pulled from a corporate environment. Things worked well, but I have received a few reports of goofiness that’s directly related to the phone’s firmware & has been fixed by upgrading it to the latest 5.9.8.5760. I decided that I was going to migrate all of our phones to this revision, but do this after hours so as to create as little disruption as possible. This is when I ran into a problem.

The phones have a wide mix of firmware revisions on them. So far, I’ve found phones with versions ranging from 5.2.2.1522 to 5.9.6.2996. Here’s the kicker - any phone with a firmware older than 5.5.3.2169 flat out refuses to upgrade. Even a phone running version 5.5.2.8571 will not apply the update. It affects all the phones I have - VVX400, VVX410, and VVX500 - with older firmware. Tried looking for a change log for modifications made between these two revisions in the 5.5 branch, but haven’t been able to find anything as HP seems to have removed most of the Polycom resources from the internet.

So far, I’ve tried upgrading the phones firmware through the phone’s GUI to the latest version hosted by Polycom (now owned by HP). They have a slightly older version on there as well, but the phones won’t apply this either. Found a third party telco that hosts a wide variety of firmware versions for these phones and tried updating to 5.7 through there, but it also would not work - phone says that there’s no firmware available for the phone. (I take this to indicate that there’s a problem with the XML.) I tried loading the latest firmware available on my PBX onto the tftp drive of the PBX using the Firmware Management feature & assigning this to the template for a single phone, but this also does not work. Also set the custom firmware version in the Firmware Management tool, but this also did not work to update a phone’s firmware. Finally, I downloaded the firmware archive for 5.7.something & loaded this on my PC, extracted it into the main apache directory, allowed incoming connections from the phone in my firewall, verified through a browser that everything was readable, and told the phone to use this location as a ‘custom server’ when looking for firmware. Unfortunately, I cannot get the phones to recognize that there’s firmware there for it - depending on exactly what I put in for custom server, it tells me either that it cannot read the XML or there is not firmware available for it. I feel that the latter is likely a problem with whatever XML the phone is looking for on the server, but this is nothing more than a hunch really. Also tried loading 5.9.8.5760 on my PC in a different directory, but with the same result. I’ve also tried threatening as well as yelling & swearing at the phones, but this had about as much effect as the rest of what I’ve tried.

Does anyone know how I could update the phones with the older firmware revisions, even just to an intermediate version that I could then jump to the latest from Polycom?

My hunch is that HP disabled communications using older SSL versions after they took over Polycom… because you know it’d be an absolute tragedy if anyone were to intercept communications, be able to decrypt it because an older version of SSL was in use, and find out that we downloaded a firmware updates for old IP phones. Here is the type of thing in a phone’s log when triggering an update through the GUI:

Default settings (TLS1.0) -

0628003751|cfg  |*|00|RT|Changed prov general
0628003751|cfg  |*|00|Prov|Starting to provision
0628003751|cfg  |*|00|Prov|Starting to update 
0628003752|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003752|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003752|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003753|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003753|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003753|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003754|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003754|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003754|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003755|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003755|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003755|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003755|cfg  |*|00|Prov|Starting to update 
0628003756|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003756|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003756|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003757|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003757|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003757|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003758|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003758|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003758|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003759|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003759|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003759|copy |4|00|SSL_connect error SSL connect error.error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version
0628003759|cfg  |5|00|Prov|cfgProvStatusSet: Unknown status 52

If I enable SSL2/3 in the network options of the phone & then attempt to update -

0628004507|cfg  |*|00|RT|Changed prov general
0628004507|cfg  |*|00|Prov|Starting to provision
0628004507|cfg  |*|00|Prov|Starting to update 
0628004507|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004507|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004507|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004508|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004508|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004508|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004508|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004509|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004509|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004509|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004509|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004510|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004510|cfg  |*|00|Prov|Starting to update 
0628004510|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004510|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004510|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004511|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004511|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004511|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004511|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004512|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004512|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004512|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004512|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004513|copy |4|00|SSL_connect error SSL connect error.Unknown SSL protocol error in connection to downloads.polycom.com:443 
0628004513|cfg  |5|00|Prov|cfgProvStatusSet: Unknown status 53

I’ve had no issues upgrading those phones from 5.2 all the way to 5.9. Keep in mind the 400s and 410s cannot upgrade to any firmware that starts with 6.

Based on your logs, it looks like you are dealing with SSL errors and not firmware errors. I don’t know how EPM applies firmware so I can’t help you there, but you can also login to the phone directly in a web browser using the devices IP address and go to Utilities > Software Upgrade and do it from there.

Happy Friday all. Today marks my final day as an employee at Sangoma.

Nothing major, just looking to have a bit of a rest and consider some options while I enjoy some summer weather.

If you are running FreePBX ‘In the cloud’ then we can presume you have a routable IP and a controllable ‘name service’

If so, consider moving from HTTP-01 to DNS-01 protocol for your chosen acme client. if you do that no ports need to be managed or opened (or closed) , just DNS TXT records added/removed, and that could easily be automatic and hands off with modern acme clients and an API string or two

A big thank-you Lorne from me. (Bet you get more)

Thank you Tom. But all modules are updated to latest version unless I should update to edge.

That’s exactly how I started updating it and how I would like to do it, but like I said it just refuses to download for versions if the revision on the phone is older than 5.5.3.2169. My hunch is that something was changed between 5.5.2.8571 & 5.5.3.2169 that allows the phone to connect using whatever is different. Everything I’ve tried has been to try to get it to a version that could then be bumped to 5.9.8.5760 using the phone’s GUI.

It’s interesting that you say you can update phones with older firmware without issues… how recently have you done this? (Wondering if it’s related to HP’s takeover of Polycom.) Don’t see how, but maybe it’s something with our ISP or the Meraki is being stupid again??? I’ll bring a phone home next time I’m in the office and see if it’ll upgrade when on my home network to eliminate that as a possibility.

You’re not understanding. The warnings you are seeing are for internal developers warning them that out dated/old methods are still being used by the system.

This is the legacy function ivr_get_details(), it used to have all the needed code for getting an IVR’s details. Notice how all it does now is call the deprecatedFunction() method (which is throwing the error you see) and it calls on the IVR class function getDetails().

//replaces ivr_list(), returns all details of any ivr
function ivr_get_details($id = '') {
    FreePBX::Modules()->deprecatedFunction();
	return FreePBX::Ivr()->getDetails($id);
}

Now all that needs to be done is any where in the entire code based that calls on ivr_get_details() needs to be updated to use FreePBX::Ivr()->getDetails() then once that is done, ivr_get_details() needs to be removed from functions.inc.php in the IVR module.

This step needs to be repeated for any function that is throwing a deprecation error. So there needs to be updates made to the code base of FreePBX.

Do y’all know the effort and amount of maple syrup it took to get @lgaetz to be on the team? Me neither there is an NDA but I have a hint

Any way all the best and know FreePBX is better with you.

Ok I get this now. Thank you. I will try it.

I have appreciated your positive, thoughtful contributions to forum discussion, your code & dialplan snippets and hacks, and your leadership of the project. Thanks, @lgaetz !