- Joined
- Apr 6, 2011
- Messages
- 92
- Reaction score
- 4
It's great that 3CX now mostly looks after phones for us directr from the console with no faffing about. Except for soft-keys.
BLFs are fine, but the other main reason we find users want soft keys programmed is speed-dials. Esp with expensive phones with lots of buttons. e.g. the Yealink T48. This has a touch-screen with 30 "keys" on it. The problem is that 3CX can configure a button as a custom speed dial, and take the number, but NOT the name. So we have a field of 30 buttons with numbers on them, and no clue as to what the numbers *are*.
The solution is to manually program each T48 from its own web GUI. It's mildly annoying to have to do this. It's infuriating that having done this, 3CX then over-writes the carefully uploaded data with the brain-dead entries from the 3CX console - or with "Blank buttons" if you havn't done any.
Does anyone know if 3CX will address this in future by adding control of the missing field, either by adding a new field to the table, or using a delimiter (e.g. type = "custom speed dial" - value = "01234567890; Pizza Shop" )
Does anyone know if I remove the section of the template XML file that deals with BLFs, the template will still work for everything else and just leave the BLFs as they *are* when it reconfigures the phone?
BLFs are fine, but the other main reason we find users want soft keys programmed is speed-dials. Esp with expensive phones with lots of buttons. e.g. the Yealink T48. This has a touch-screen with 30 "keys" on it. The problem is that 3CX can configure a button as a custom speed dial, and take the number, but NOT the name. So we have a field of 30 buttons with numbers on them, and no clue as to what the numbers *are*.
The solution is to manually program each T48 from its own web GUI. It's mildly annoying to have to do this. It's infuriating that having done this, 3CX then over-writes the carefully uploaded data with the brain-dead entries from the 3CX console - or with "Blank buttons" if you havn't done any.
Does anyone know if 3CX will address this in future by adding control of the missing field, either by adding a new field to the table, or using a delimiter (e.g. type = "custom speed dial" - value = "01234567890; Pizza Shop" )
Does anyone know if I remove the section of the template XML file that deals with BLFs, the template will still work for everything else and just leave the BLFs as they *are* when it reconfigures the phone?