Changing background phone logo in bulk?

[jstamey]

I have an enterprise license for 3cx. I can go into a user and the IP phone tab to change the background logo for a phone. Is there a way to do this in bulk? Updating the logo and doing this one user at a time would be inconvenient.

 

[Lee Cramman]

Little can be done in bulk using the Web UI in V20 currently

 

[NicholasP_3CX]

Phone provisioning options are not options that can be configured in bulk in 3CX, due to the differing options available on phones.

The logo especially due to their differing logo sizes and formats.

 

[noord]

I would like to add the request to set-up some defaults again.
For example, we configure the screen timeout, date format, language and attended/blind transfer options for every phone.
It would be nice to set the default to this. And the same goes for the logo.
I understand it might be quite some work to implement this, but that's why it's called a wish of course

 

[NicholasP_3CX]

This is a long shot as the logo especially is a different format.

Each phone has different formats of the variables as well.

 

[SteveITS]

Each phone has different formats of the variables

For sake of discussion, then, it would be fine to have a page for each template...defaults for Yealink T5 series, etc. Right now it's easy to forget to set one of time, MW light, ring, etc. to match existing phones. It would both be easier to add 100, and to add one phone a year later. The defaults could store "permanent" or "stable" settings and not something that would change between 3CX versions. Just wishing.

 

[jstamey]

75 phones. all the same model. seems a template would be the solution.

 

[Ori Klein]

This is a long shot as the logo especially is a different format.

Each phone has different formats of the variables as well.

I do not at all view this as a problem. Perhaps because I am a tech-minded person?
To me it is all too simple: warn user different phone types differ and to consult the manual (https://www.3cx.com/docs/ip-phone-background-logo/), grant user power to change logo, assume user is intelligent enough to read instructions and know what they're doing.

Exempli gratia: assume case scenario of 7 different device types, over 100 phones.
Say we use the "Users" page of the admin console for this purpose.
Sort by IP Phone type -> select all phones of same type -> provision new custom logo.
Repeat per phone type.

Have I gone too far?

 

[NicholasP_3CX]

I do not at all view this as a problem. Perhaps because I am a tech-minded person?
To me it is all too simple: warn user different phone types differ and to consult the manual (https://www.3cx.com/docs/ip-phone-background-logo/), grant user power to change logo, assume user is intelligent enough to read instructions and know what they're doing.

Exempli gratia: assume case scenario of 7 different device types, over 100 phones.
Say we use the "Users" page of the admin console for this purpose.
Sort by IP Phone type -> select all phones of same type -> provision new custom logo.
Repeat per phone type.

Have I gone too far?

Yes.

Essentially a telephone could throw a hissy fit if it receives the wrong file.

You might be technically minded enough to be able to control this, but other people might go and just put any type of file there and have it replicated over different models could potentially cause issues with the phone itself.

Take a look at some of the file types!!!



Try loading a DOB file to a phone that requires a JPG. The phone will have a field day!

Or when the phone does not load it, it will be the fault of 3CX that it isnt loading. Noone ever blames the phones themselves.

Anything that isnt the same on all users is generally not defined by 3CX in the multi edit, for simplicity.

And honestly, a phones logo is only loaded once, and having the default logo of 3CX initially, the phone will work, allowing the admin to go and do this whenever they have time. This is not detrimental to the phone working.

 

[Ori Klein]

Yes, the amount of file types is definitely ludicrous (I had to prepare quite a few different logos in different formats so I know [crying] , by the by from my limited experience the DOB maker doesn't like GIFs so much and prefers BMPs) and I doubt anyone here expect you (3CX) to waste precious time/resources on generating exception handling contingencies for them, when there are so many more important things than a logo on a phone that we all need/want.

And I am certain consequences can be dire (which is why one should always backup before changing important/weird/quirky settings, and any sweeping changes, and make screenshots of settings panels) and I do understand that this is a business, and at the end of the day you have to manage expectations for the overall/median/average userbase and that no one wants to spend a weekend restoring a customer's system because someone did something incorrect and tanked the entire enchilada or set it on fire (or gotten Googleslashed ala UniSuper).

But like data protection/information security, compliance, at cetera, you can only go so far to protect users (or CEOs) from themselves.

Perhaps lock it under a submenu "advanced users only"-esque that you have to click to open the panel, display some legalese flavour text that you understand the risks et cetera your phone can be bricked and that you're on your own/your partner's liability, and then tick a box that you've read and understood and agreed it all, then another "are you sure you wish to proceed?" and then it'll display you the thing. And of course have it available to system owners only.

Or when the phone does not load it, it will be the fault of 3CX that it isnt loading. Noone ever blames the phones themselves.

Oh, I rue the day I met a certain Y-brand. I definitely love you guys. <3
I blame Panasonic for destroying themselves and thereby with exiting the market denying us decent phones and by proxy ruining it for all of us.

This is not detrimental to the phone working.

Couldn't agree with you more there. Unfortunately, it's the management's mood that's detrimental to IT admin working.
And management got told phones can have logos. So if they walk around and see some phones don't have logos then critical work has to halt for *ahem stupid ahem* logos.