Possible Bug

I believe that there is a bug cause the work around seems a little bit strange. I’m happy to put in the bug report but wanted to confirm that it isn’t actual behavior. I am using Grandstream GXP-2140 phone, endpoint manager, Hosted CyberLynk FreePBX. I want to be able to setup auto provision and auto firmware upgrade via Authenticated HTTPs (I feel this is a requirement due to SIP secrets potentially being exposed, but this could be incorrect). Anyways there is no option for provision server for Grandstream Phones for https. So I go the custom portion and enter in the following string in the following format https://user:password@IPorFQDN:port. When I factory reset the phone it picks up the string from DHCP of https://user:password@IPorFQDN:port gets initial config and looks good. If I make a change, for example with that same phone, and change the extension mapping to use line 2 instead of line 1 and reboot the phone it will not get the change. Also it will not be able to get the firmware off the server. When reviewing the phone settings in provision I see the string in the following format https://user:password@IPorFQDN:port:83 where 83 is the http provisioning port. I’ve worked around it by changing the base file P192 = https://user:password@IPorFQDN:port/grandstream/1 and P237 = https://user:password@IPorFQDN:port. While this could be normal behavior I don’t understand why it would appended :83 when the custom string specifically states to put in the port number.

Looks like a bug to me. File it.


1 Like

Last I was told by @tonyclewis HTTPS provisioning is only supported in Sangoma phones. Will be added to future phones manufacturers that have been certified with FreePBX “eventually.”

Correct HTTPS provisioning is only supported on sangoma phones at this time. The user here is trying to use the custom URL and that is creating problems as again we don’t support HTTPS provisioning for any other manufacturers at this time.

Got it. Still seems odd that the documentation specifically state to use the port number. So if I opted to go the supported HTTP route (I’m assuming that is supported) it would add 83 to my custom string and would not work. Maybe update the documentation to not include port number?

Negative. Custom prov string is ENTIRELY user generated and needs to be pushed unmodified to the phone. If I understand the report, EPM is always tacking :83 to the end of the user provided, custom provisioning URL (for Grandstream) which already has a port. This is a bug.

There should be a clear notice somewhere under the provisioning tab, or people won’t know.
I spent an hour lately trying to make it work with Yealinks.

Clear warning where? We do not provide HTTPS as a option in EPM besides Sangoma phones. If you setup custom HTTPS should work but their appears to be a bug that port is out in at the end like Lorne said and asked someone to report the bug.


Yes that is where you setup username and password for http providing and HTTPS. Doesn’t mean it supported on all phones. Inside EPM their are tabs under each brand on what protocol we support. Some don’t support TFTP. Others don’t support other things. Not every brand in EPM is equally supported. It’s clean inside each brand what protocols we support.