Page History

Alexander Feldt  I'd agree, for these reasons:

1. Snom phones (acting as UAS) already provide all information in NOTIFY body
2. It's cleaner, e.g. when the UAS goes offhook or calls somebody, currently "talking" is visualized, which is not true. 
3. It could be an advanced sales feature?

Alexander Feldt Technically, we could allow quick dial in any state, except ringing...

Zsolt Erdei Quick dial → Dial the configured extension happens only in Idle state; in Calling state does the button nothing to do, in connected state, when the party is different, the blf might blind transfer the call

Alexander Feldt I really question icons, that are so small, that there is no visible difference to the user, like  and , therefore - if we use them at all - I vote for better distinguishable icons.

Zsolt Erdei If possible reuse

Alexander Feldt Currently not within XML definitions, it has to be configured via settings.

Zsolt Erdei Using a new statename; that new name is added in xml definition to "state" variable and the string is configured in the led settings.

Alexander Feldt see label, but I haven't figured out how to define it correctly
with Zsolt Erdei  with the label variable
Initialisation:
 <variable name="label" value="Clock on"/>
During XML evaluation:

    <assign when="on press">
        <source value="Hello"/>
        <destination id="label"/>
    </assign>

Alexander Feldt see icon, but I haven't figured out how to define it correctly

Zsolt Erdei As I remember, same as label, value name is icon.

Alexander Feldt The topic is even more complex: I assume the PFK label is generally too short to show longer extension number or names, i.e. some kind of scrolling must be used. But is this really helpful for the customer at all?

Zsolt Erdei It is shorted by an ellipse in QT; I think it is enough if we display the label value and the state.

Alexander Feldt 

1. The colour of the LED and if it is blinking => very important
2. The label icon => basically not important, the LED is already showing everything, also the PFK label is not even shown by default
3. The label name => important when it comes to call pickup, less important for other scenarios, so is it worth adding scrolling or should we keep it simpler?
4. The label state => It is definitely an additional information, which cannot be shown with LED only, e.g. the difference between offhook, calling and talking
   
   
   Zsolt Erdei I say led + status on pfkey label
   
   

Tita Petre Is the above list of requirements enough input to create a proper testplan?

Clemens Cramer As the decision to move the default blf & extension configuration to a xml definition is based on customer requests to modify the behavior,  guides with working examples on how to change the labels, icons, led behavior, and handled dialog states should probably be a requirement (and as such covered by tests).