Versions Compared

Old Version 76

changes.mady.by.user Alexander Feldt

Saved on

compared with

New Version 77

changes.mady.by.user Clemens Cramer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

QuestionOutcome
Shall we visualize all possible translation states?

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?

Shall we allow quick dial only in idle state?

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

Shall we create new icons or reuse those already existing ones?

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.

How can a specific LED behaviour be addressed using XML definitions?

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

How can a specific label be addressed using XML definitions?

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

How can a specific icon be addressed using XML definitions?

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

How shall the D8XX:PFK-mapping:BLF-XML:Monitoring:Visualization:Label:name-area be configured to use either number or display name?

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?

From the UX point of view: which visual aid is more important for the customer: LED or PFK label?

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

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).


Not Doing