Grandstream Phones - More settings

[Evolute IT]

Hi,

As all of you know, Grandstream phones are back in business and seemed to be working great.

However, looking through the configuration template, I see a lot of potential settings that should be there also. Here's the list:

• Weather settings : city, degrees (C or F)
• Wallpaper choice
• Softkeys settings (choose or hide)

There are more but these are the ones we'd all like to configure per device.

 

[YonNomNom]

+1

 

[cloudactive]

I'm not really sure how to vote, but +1

 

[YonNomNom]

There needs to be a way to set the ring volume for the phone. Every time the phone is re-provisioned it will reset to the default ring volume. It either needs to not reset the volume or we need to be able to set it.

<!--  Speaker Ring Volume  -->
 <!--  Number: 0-7. Default is 5.  -->
 <!--  Mandatory  -->
<P8352>3</P8352>

 

[charly]

+1

 

[NickHill]

+1 plus some additional changes that are mainly just allowing us to control variables in the template.

Force BLF Call-pickup by prefix
Publish for Presence (if presence will ever work from the phone instead of dial codes?)
Ability to set auto answer
Keypad lock controls
Transfer on Conference Hangup
On Hold Reminder Tone
More control over ring tones used for external, queue, ivr, etc and a place to upload .bins to be provisioned onto the phone to replace standard ringtones.
Off-hook auto dial and delay
Mute key functionality (DND vs Idle Mute vs Disabled)
Disable conference/transfer/etc options
Enable BLF pickup screen and sound
Set Call Waiting Tone gain higher, it's difficult to hear as is on Grandstreams
As mentioned before, speaker and notification volumes programmable

VPK changes:
Use Long Label
Key Mode - Line vs Account appearances (limit to one Line BLF instead of 2+)
More VPK options:
- BLF customize-able or include IVRs in options available on web
- Intercom
- Record (if it'll work with start/stop of server recordings)
- DND (single button will toggle instead of having to use multiple presence options which then use dial codes)


Make phone book default to local or give option
Multiple SIP accounts would be nice too ... but understandable that that isn't as simple to tackle necessarily.

 

[jkauffman]

+1
Settings for volume and ringtone would be a welcomed feature for all of the Grandstream models or at least the ability to set them at the endpoint level

 

[midtherm]

+1
Volume, and Attended Transfer Mode (Dynamic) are the two that would prevent me having to use custom templates, phonebook default to local would be nice.

 

[Evolute IT]

After thinking a lot about this, I think they should simply use the Grandstream ZeroConfig principle of provisioning.

FIRST, provide a basic template for supported phones which contains only the necessary parameters to make it work.

SECOND, provide a way to set config templates globally per phone models (ex.: for logo, weather, model-specific features).

THIRD, provide a way to set global templates of configs to be assigned to users (ex.: ringtones, volume, etc.).

THEN, give us a field or table to add our own params for each user's phones.

This way, we have 4 levels:

1. The 3CX base to make it work
2. A global config for the phone model
3. A template-styled global config for extensions group or device groups.
4. A user-level field to add custom params for each users.

Also, being able to provision multiple accounts per phone would be nice.

All these enhancements can be applied to all supported brands of phones so I think it's the best way to go to keep it fair between manufacturers.

 

[AWS2P]

+1

 

[Evolute IT]

After thinking a lot about this, I think they should simply use the Grandstream ZeroConfig principle of provisioning.

FIRST, provide a basic template for supported phones which contains only the necessary parameters to make it work.

SECOND, provide a way to set config templates globally per phone models (ex.: for logo, weather, model-specific features).

THIRD, provide a way to set global templates of configs to be assigned to users (ex.: ringtones, volume, etc.).

THEN, give us a field or table to add our own params for each user's phones.

This way, we have 4 levels:

1. The 3CX base to make it work
2. A global config for the phone model
3. A template-styled global config for extensions group or device groups.
4. A user-level field to add custom params for each users.

Also, being able to provision multiple accounts per phone would be nice.

All these enhancements can be applied to all supported brands of phones so I think it's the best way to go to keep it fair between manufacturers.

I wanna add that many PBX have this, like Yeastar, Grandstream, FreePBX, PBXact, etc.

@admin : please change the title accordingly since this now concerns the provisioning system completely.

 

[midtherm]

Hi

The Volume setting is causing me a bit of a headache, we are almost fully setup with 84 Grandstream phones, total will be 100.

As this is spread over several usage scenarios, it is important to be able to set the volume correctly for the environment, from quiet office to noisy production.

Currently the template overrides any user changes and does not allow for a per extension volume setting, without creating a custom template, and to do this centrally i need around 4 different custom templates.

The ideal situation would be the ability to set volumes on the provisioning page, on a per extension basis. however, it would also work if i could allow the user to set their own volume without it being changed by provisioning.

This and the attended transfer option (other than just blf behaviour) would be really useful,

Thanks

 

[Evolute IT]

@JohnS_3CX @Nick Galea : please change the title accordingly since this now concerns the provisioning system completely, not just Grandstream phones.

 

[Louj]

Hi

The Volume setting is causing me a bit of a headache, we are almost fully setup with 84 Grandstream phones, total will be 100.

As this is spread over several usage scenarios, it is important to be able to set the volume correctly for the environment, from quiet office to noisy production.

Currently the template overrides any user changes and does not allow for a per extension volume setting, without creating a custom template, and to do this centrally i need around 4 different custom templates.

The ideal situation would be the ability to set volumes on the provisioning page, on a per extension basis. however, it would also work if i could allow the user to set their own volume without it being changed by provisioning.

This and the attended transfer option (other than just blf behaviour) would be really useful,

Thanks

If i am not mistaken you can juste delete the volume settings parameter in the provisioning file and it should keep the user value.

 

[dkeethler]

+1

 

[WBS]

+1

 

[cparker_RCT]

Coming from sipx to 3CX. I really miss the ability to have nearly full control over every tidbit in the config XMLs. (They had super super strong coverage with Polycom) I really love 3CX, but I feel for an enterprise solution, there needs to be greater and more granular control over officially supported phones.