EPM - Background Image Path on Grandstream Phones Wrong

I have uploaded an image using Image Management in EPM. I used an image with no spaces in the filename. I have applied that Background Image to a Grandstream template within EPM. When I provision a GXP-2170 phone with that template, the setting is applied to the phone incorrectly. The setting ends up as “https://https://pbx.mycompany.com:1443/images/formatted/bg-grandstream-GXP-2170-mycompany.jpg” instead of “https://pbx.mycompany.com:1443/images/formatted/bg-grandstream-GXP-2170-mycompany.jpg”. If I adjust that setting in the phone after provisioning (remove the extra “https://”), the background is displayed fine on the phone. Why is EPM adding that extra text to the setting? A bug?

FreePBX 17
EPM Version: 17.0.1.94 (Current as of today)
Phone Model: Grandstream GXP-2170
Phone Firmware: 1.0.11.85

If there is https twice, then I think it’s a bug indeed.
@kgupta can you check this issue please?

Hi @ppgstanner

First https is appended in the code based on the type of provisioning protocol in the template so can you please ensure you are not adding https in your provisioning url manually? If yes then please remove that and try again ?

Wishing you and your family a very Happy New Year 2025(in advanced)!
Best regards,
Kapil

1 Like

Maybe improve the code removing http: and https: if set. Just for avoid to get confuse.
Just an idea like that.

I wish you an Happy New Year 2025 in advance too @kgupta

As I understand it, https/http is set automatically depending on the general provisioning settings.
So everything is correct…?!
If there is a field for the URL, one could add a help text.

Yes, I think so.
I can’t test on 17.
I noticed that the Sangoma S series phones are no longer listed, but the older Digium phones are still there. Crazy. :rofl:

1 Like

For clarification, I never entered the url, so I don’t know of any way to remove one of the https:// tags. I upload the image through “Image Management” in EPM. Then I select that image when setting up the phone template. EPM creates the url and sets it in the phones during provisioning. I think that the EPM code is adding the second https://, which breaks the url.

After original reply, it occurred to me that perhaps the phone is adding the first https://. I can do some testing in that area. These phones that I am provisioning are either brand new out of the box from Grandstream or they are factory reset immediately prior to provisioning. I’ve seen the same behavior on at least 6 phones. When I get back to the office, I will look at a brand new phone to see if it starts with a “https://” on the beginning of the url. Another thought - I wonder if there is a setting in the custom base file section that would allow me to get around this issue.

Usually this is done with the image manager that downloads and formats it in the right place.
I did it on FreePBX 16 with grandstream 2170, it works fine.

If on 17 there is the same way to define an image. then I wonder how it is possible to enter a URL.
In this case it is a bug.

Anyway, on 16, there is no prob.

P2917 = https://xxxxxxxxxxx:[email protected]:1443/images/formatted/bg-grandstream-GXP-2170-lune.jpg

1 Like

I did some additional tests over the weekend. I provisioned a Sangoma S700 phone on the same system. The wallpaper setting was fine with that phone and in the provisioning config file. I also looked at the provision config files on the PBX. /tftpboot/{mac address}.cfg. The double “https://” exists in that file, so I’m pretty sure that EPM / FreePBX17 is generating that incorrect url. Let me know if you would like me to test anything else.

1 Like

Thanks @ppgstanner , @franckdanard

will try to reproduce the issue locally with freepbx 17.

Regards
Kapil

2 Likes

Any luck with testing? I’ve seen the same failure on 3 independent FreePBX 17 installations with EPM.

1 Like

Yes we can see with GS template using https in custom provisioning url generating background image url with twice https://https:// .

Raised internal jira to keep track of this issue, will try to prioritize this issue to get it fix but can not comment on ETA as of now.

Regards,
Kapil

1 Like

hi @ppgstanner can you please try with below release.

fwconsole ma downloadinstall endpoint --tag=17.0.2.1
1 Like

I just tested EPM 17.0.2.1 and it is generating the correct url for the provisioning file. Thanks for the fix.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.