• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Implemented Intelligent phone template override system

Status
Not open for further replies.

iptechnology

Forum User
Joined
Jul 6, 2016
Messages
12
Reaction score
13
Please, give us a "linux style" intelligent phone template override system.
I try to explain it with an example:

- Yealink Phone with default template
Every customer want a different DSS Transfer type or ringtone, it means 2 lines config changes.

Now we have to duplicate the base template, edit it and apply the changes. If you update the base template, we have to find out the changes we previously made, duplicate the updated template, re-edit and apply it.

It takes long time and can create problems while it should take 2 minutes working.

My idea for simple changes like the one above, is to put them in a SEPARATE file that is pharsed AFTER the base one and it overrides the single changed values.
Config files of Linux service like apache works natively as described.

override file example:
------- yealink.override1----------
#Define the way of DSS key when configuring as a transfer key; 0-Display Number, 1-Attended Transfer, 2-Blind Transfer (default);
transfer.dsskey_deal_type = 1
distinctive_ring_tones.alert_info.2.ringer = 2
distinctive_ring_tones.alert_info.3.ringer = 2
distinctive_ring_tones.alert_info.4.ringer = 2
----------------------------------------

Thanks
Alessandro Coelli
IP Technology srl
www.iptechnology.it
 
Upvote 78
Nick,

Alot of great input from everyone. My BIGGEST ISSUE overall... parking Share park on cell phones! There needs to be an immediate change as to the way they park calls from Android and iPhones. Even after training - my clients join their customer calls into a park slot during busy times.

Second: the ability to copy and paste extensions built in the system.


Third: being able to "insert" a blank blf to add in without the need to change all the ones below it.

From inception you guys have come a long way. Keep up the good work my friend.
 
My suggestion:
1.) Real telephone book -> ODBC synchonisation, not only for incomming calls.
2.) Behavior -> external Application "Multiplexer"
If an incoming call is detect and the Windows-Client "lauch application" is on, there should be a option to make multiple external Apps as destination. It should open a new Windows with a button for each App are defined. A klick on the button open the selected App. Possible Apps are ERP, CRM, Supportdesk or any other APP who can recieve Parameters.
3.) If a call is forwarding, you should be able to set the incomming callerID as outgoing callerID. Sometimesi t is important for forewards to mobile phone (w/o 3CX App).
 

Attachments

  • upload_2017-6-6_16-58-20.png
    upload_2017-6-6_16-58-20.png
    2.6 KB · Views: 6
Excellent suggestion.

Along with common options configured via console, it would also make sense to have the config file over ride as per the first post giving users the best of both the worlds :)

Yes yes yes!
 
If the goal is to eliminate custom templates, these are the items we typically configure on our Yealinks, these were taken from a T23G template.......

remote_phonebook.data.1.name
We like to be able to customize phonebook name instead of 3cx Phonebook call it the company name or something else.

account.1.sip_server.2.address
account.1.sip_server.2.port

We typically need to be able to define a secondary PBX either for WAN survivability or 3cx survivability so being able to add this via web would be nice.

linekey.1 / linekey.2 / linekey.3
We usually customize the 3 side buttons on the yealink T23G as needed, being able to fully do this via the web would be nice.

phone_setting.predial_autodial
Our users coming from traditional PBX are used to phone auto-calling after dialing, by default you have to hit OK to start call after dialing.

phone_setting.lcd_logo.mode
By default this is ON, not sure why as most users wants to see homescreen with extension, time, etc. not the 3cx Logo branding.

account.X.label
Some users like to see extension number, name or other attributes displayed instead of the 3cx defaults.
 
additional suggestions:
custom URL\upload for company logo instead of 3CX logo
change Line display name to be extension number instead of users name.
Yealink "Intercom" BLF
 
  • Like
Reactions: countrycomp
When I think of global changes for telephone handsets... The most requested item from my end users is custom DSS Keys!

As we have been discussing you have to edit the template to get 10, 20 or more phones to have the same custom confirm configuration using DSS Keys (aka BLF tab in Extensions in 3CX Management Console). This is because using the BLF Page to edit lots of telephone handsets does not make sense when you want to standardized DSS Key layout.

NB: Should this tab in Extensions still be called BLF? Are they not really DSS or Programmable Keys?

Beyond what has already been discussed here is another part of the global change idea...

For the each phone you would have to choose which "base" template plus an optional "override" template you want.

When you view an extension with any setting assigned globally in either the "base" or "overridden" template the extension setting would be non-editable ("grayed" out) for end user! Of course the "overridden" value takes precedence over the "base" value.

Now let's use a DSS Keys as an example as this is my biggest area that could use improvement IMHO...

Say DSS Key 10 is undefined by the "base" template, however, its defined in the "override" template as "Shared Park" 0 so this is what would show up on the BLF tab in Extensions in 3CX Management Console for that KEY and it would be grayed out so that the end user has no ability to change it.

Another example is that the first two DSS Keys are assigned as line keys to the default account in the "base" template. In this case let's say its not in the "overridden" template. Then the result is the on the BLF tab in Extensions in 3CX Management Console the end user can see that the first two DSS Keys are Line Keys and they are not non-editable! This way you are not hiding theses DSS Key assignments! I generally add one or two more Line Keys to every phone doing this in the "override" template would make this a SNAP!

Going one step further... Yealink phones have the concept of making changes to the "programmable" keys or pre-defined keys like hold, or cancel. In this way we can expose these settings without having to worry that an end user will make an change.

Another step is to separate out DSS Key Expansion modules and define how may modules exist in a "override" template. Now with this in mind you can change the shown sort order of DSS Key features in the order you prefer either left to right, then top to bottom, or top to bottom using the left column first then the right column second. DSS Key Expansion modules numbering for Yealink start with 28 for Row 1, Column Left, and Group1; then 29 for Row 1, Column Right and Group 1. This is tricky because my customers like the DSS Keys on Expansion modules using alpha sort of extension with names top to bottom using the left column first then the right column second. Since, presently DSS Key 28, 29, 30 and so on are shown in order left to right, then top to bottom so getting an alpha sort right is tricky!

Another step is to have a check box as part of extension config to auto assign extensions to the DSS Key Expansion modules; then have a globally setting to choose how sort these auto assignments are sorted either by alpha AtoZ or ZtoA plus you also need a DSS Key assignment order left to right, then top to bottom, or top to bottom using the left column first then the right column second.

To get the above to happen a new field in the Extensions, under general tab, would need to be added to be called something like "DSS Key Exp Label" which would be initially set to a default to a string made up of First and Last Name. A global setting would control the default value -- options would be first name only, last name only, first name plus last initial or last name and first initial. Of course the default value can easily be typed over if you don't like one of the defined initial value choices.

Now with the ability to auto assign extensions to DSS Key Expansion modules when any an extension is added or the "DSS Ext Key Label" is changed then any phone that has an DSS Key Expansion module attached would automatically get their provisioning profiles updated with the new data. A simple reboot of the phone would cause the new data in the DSS Key Expansion modules to show up without manual intervention! One more step -- with Yealink you can have a telephones auto-reboot on a schedule to -- say once per day over night for example -- so then the extension changes appear the next day with no manual intervention!!

I have other ideas about nesting "Override" templates so a provisioning profile is "base" template + "Override" template 1 + "Override" template 2 + "Override" template 3 which are applied in that order. Of course if you have a setting in each of the "Override" templates then the last template applied (I this case #3) wins! This could be useful in that the "base" template could reference a "special" template for DSS Key Expansion modules to make re-provisioning easier.
 
Last edited:
  • Like
Reactions: Andrew Johnson
we finally found a way to make the system happy by downloading the template off linux, editing it, and re-uploading it back to the system. this retains full control over the phones on SBC and keeps the system from turning the extension red.

i'd like to see 12 hour clock by default, NO 3cx logo at all (we shut it off or upload a customer logo anyway if the phone has a color screen), no missed call busy flash, and all ringers are #2.
 
  • Like
Reactions: comms1
The BLF is the biggest for us. We have custom templates for certain groups and the BLF is the only part that is custom. If we can set a default BLF for a group that would be great.

On a side note, the ability to set specific MOH for a group would be great also.
Thanks,
Matt
 
+1 for ability to change logo on phone easily or stop the flashing back and forth on phones that don't have logos on the default screen. (T41 for example). The flashing back an forth drives people crazy.
 
Please add the ability to assign OTHER EXTENSIONS (not BLFs) in the drop down selection on line keys.

Example Your ext is 201 - this is assigned to line keys 1 & 2
Using the drop down allow the ability to assign ext 202, or 203 or ... to any other line keys.

This is invaluable to accommodating clients that have;
1. An extension that has a group or dept caller ID
2. Secretary/Boss scenario
3. Multi-company identity for out going caller ID

It's really frustrating that in 2017 this still hasn't happened. The only way to achieve this now to is manually edit each phone's template and include text based user ID and passwords which is insane.

Please for the love of anything good, make this happen.
 
  • Like
Reactions: 3CXDude and jed
The ability to configure the logo (such as adding a company logo) without having to add this manually to the provisioning folder.
 
Is shoot be nice to toggle status with BLF status in place of using 2 BLF keys with no BLF status.
 
  • Like
Reactions: 3CXDude
How about making changes to the template "persisting"?
For example if you guys don't want to include a ton of configurable parameters in your UI, why not giving the user a possibility to put in the respective changes in a window which then will be automatically integrated into the template file and migrated every time a template gets updated (instead of overwritten).
Besides that I have made these changes to our (Snom [D375]) template:

- backlight, idle and dim timer
- various default ringer settings
- global dnd key redirection
- background image (company logo)

Furthermore I have changed the default image when off hook (pasted our company logo over the 3CX one) for corporate identity reasons. Those image files will also be overwritten when updating/upgrading the PBC software...which is additional work for me :(
 
  • Like
Reactions: vancouvercom
I agree too. This is an excellent idea. For a long time we have been manually adjusting the Phones and then turning off Update on Reboot. It would be great to be able to make the changes and know they won't change on the next Auto-Provisioning Update.
We would love to see the ability to place the Extension Number on the phone beside the Line Key instead of the Name. The user knows their own name.
I know that Branding is important, but having the 3CX Logo on the Phone is too much. Customers get annoyed with this feature and we are asked to turn it off all of the time.
 
Here is the list of customisations we have made with snom handset templates.

<!--# The "use_backight" field specifies whether the LCD Backlight is always off, or whether the LCD Backlight turns off Automatically after a period of inactivity. Valid values are "on"==On but turns off after 20 seconds of inactivity, "off"==Always Off, "always"==Always On. The provisioning template sets the value to "on"==On but turns off after 20 seconds of inactivity.-->
Code:
    <use_backlight perm="">always</use_backlight>

    <!--# Specifies how incoming and outgoing calls are displayed -->
    <!--# Telis 26/07/14: Changed value from display_name to display_number_name -->
    <display_method perm="">display_number_name</display_method>

    <!--# You can block the dialing of SIP URLs by turning this setting on. In this case only numeric numbers will be allowed as input.  Valid values "on" or "off" -->  
    <!--# Telis 30/07/14: Added -->
    <block_url_dialing perm="">on</block_url_dialing>

    <!--# http://wiki.snom.com/Settings/call_screen_fkeys_on_connected -->
        <!--# Telis 01/08/14: Added -->
        <call_screen_fkeys_on_holding perm="">F_ADR_BOOK</call_screen_fkeys_on_holding>
        <call_screen_fkeys_on_connected perm="">F_TRANSFER F_HOLD</call_screen_fkeys_on_connected>
        <!--#<call_screen_fkeys perm="">F_ADR_BOOK</call_screen_fkeys>-->

        <!--# Telis 15/09/14: Added -->
    <!--# http://wiki.snom.com/Settings/gui_fkey -->
        <!--# There are 4 idle softkeys by default F_ADR_BOOK, F_SETTINGS, F_REDIRECT, F_DND -->
        <gui_fkey1 perm="">keyevent F_ADR_BOOK</gui_fkey1>
        <gui_fkey2 perm="">keyevent F_REDIRECT</gui_fkey2>
        <gui_fkey3 perm="">keyevent F_DND</gui_fkey3>
        <gui_fkey4 perm="">keyevent none</gui_fkey4>


Redirection at the handset is pretty hopeless (and confusing for admins and users).
Code:
     <!--# Telis 15/09/14: Added -->
    <!--# http://wiki.snom.com/Settings/Leds_Behavior_8.6.6 -->
        <led_call_indicator_usage perm="">PhoneHasCallInStateRinging PhoneHasCall PhoneHasMissedCalls CurrentIdentityHasVoiceMessages PhoneHasVoiceMessages</led_call_indicator_usage>
        <led_message_usage perm="">CurrentIdentityHasVoiceMessages PhoneHasVoiceMessages</led_message_usage>


For snom 710's we get rid of the two line appearance keys and the other key that take up the 3 or the 5 available soft keys.

<!--########################################################-->
<!--### BLF Settings ###-->
<!--########################################################-->

<!--# The different BLF keys are referred to using the "idx" paramer, which can have a value between 0 and 11. The first 2 BLF keys are programmed only for line operation to allow the phone to retain Hold, Resume, and Call Transfer functionality.-->
<!--# The "fkey" field for all keys from idx="2" to idx="11" must contain a string value to specify which extension number to monitor. The provisioning template sets the value to "blf<sip:blf1@%%pbx_ip%%;user=phone>|*20*" for the first usable key (idx="2"), "blf<sip:blf2@%%pbx_ip%%;user=phone>|*20*" for the second usable key (idx="3"), and so on - where the variables "blf1" to "blf10" will be replaced by the extension number chosen from the 3CX Management Console for that extension-->
Code:
  <functionkeys e="2">

    {IF blf1}
        <fkey idx="0" context="active" label="%%blffirstname1%% %%blflastname1%%" perm="">%%value%% &lt;sip:%%blf1%%@%%pbx_ip%%:%%param::sipport%%%%userphone%%&gt;</fkey>
    {ELSE}
        <fkey idx="0" context="active" perm="">none</fkey>
    {ENDIF}
    {IF blf2}
        <fkey idx="1" context="active" label="%%blffirstname2%% %%blflastname2%%" perm="">%%value%% &lt;sip:%%blf2%%@%%pbx_ip%%:%%param::sipport%%%%userphone%%&gt;</fkey>
    {ELSE}
        <fkey idx="1" context="active" perm="">none</fkey>
    {ENDIF}
    {IF blf3}
        <fkey idx="2" context="active" label="%%blffirstname3%% %%blflastname3%%" perm="">%%value%% &lt;sip:%%blf3%%@%%pbx_ip%%:%%param::sipport%%%%userphone%%&gt;</fkey>
    {ELSE}
        <fkey idx="2" context="active" perm="">none</fkey>
    {ENDIF}
    {IF blf4}
        <fkey idx="3" context="active" label="%%blffirstname4%% %%blflastname4%%" perm="">%%value%% &lt;sip:%%blf4%%@%%pbx_ip%%:%%param::sipport%%%%userphone%%&gt;</fkey>
    {ELSE}
        <fkey idx="3" context="active" perm="">none</fkey>
    {ENDIF}
    {IF blf5}
        <fkey idx="4" context="active" label="%%blffirstname5%% %%blflastname5%%" perm="">%%value%% &lt;sip:%%blf5%%@%%pbx_ip%%:%%param::sipport%%%%userphone%%&gt;</fkey>
    {ELSE}
        <fkey idx="4" context="active" perm="">none</fkey>
    {ENDIF}

  </functionkeys>
 
Timezone settings like on older 3CX versions where you could set daylight savings time. In South Africa we dont have DST but the Yealink and Fanvil phones still enable it
 
I have a custom template for EVERY phone model and for every paging area. Our paging is all done through multicast from the phone (not through a multicast paging group, which is always sent through the 3CX). Not a single 3CX option for this configuration so it has to be done through templates or manually. Allowing us to set a BLF to a multicast paging button and to set a multicast listening address or 3 would be my top pick. Though I can't believe VLAN isn't already in there as well...
 
The logo..........

Weve had clients switch because of that. When we told them we can change it but it would use something that would make the phone unsupported they let us know that is outright unethical business practice.

We told them its not us that has decided that but 3cx. They told alot of people about that...
 
One setting that forces custom templates for about nearly every phone:
BLF Buttons.

3CX default: First Name, Last Name
Many phones have quite short text lines like the Yealink T41S devices which means that 3 people called Michael will already fill up all visible space and the people can't be differentiated on the BLF buttons.
Displaying last name will make that so much easier.

Override: Last Name, First Name
This should be still a customizable setting since for Germany it is normally the better way of displaying last/first name where for example in Vietnam where loads of people share the same surname the current default display order is a better choice.
 
Last edited:
Most of the options in the poll are now in SP1... Copy extension feature to have default settings easy to copy to follow
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.