December 29, 2011

Thomson ST2030 Feature Key Sheet Template

Category: Sysadmin.

Technicolor's (ex. Thomson's) ST2030 SIP phone features 10 feature keys that can be used as fast call keys to reach a configured number by a single key-press.

[ST2030 Feature Keys location]
Location of Feature Keys on the ST2030.

I finally decided to configure these keys with proper numbers instead of browsing my directory each time I want to make a call. But the phone only ships with a single paper sheet to hand-write the names corresponding to the configured numbers and my hand-writing is somewhat like what would produce a drunk cow with Creutzfeldt–Jakob disease. I browsed the Internet for a sheet template to fill-in, print and cut, but was unable to find some.

So, I took Inkscape and did one myself. For your convenience, I make it available as the original SVG file (so that you can fill-it before printing) and a PDF file for those who like hand-writing:

If you don't have a precise idea of which numbers you call often, you can extract this information from Asterisk's log file. In my case, my calls come from the internal context so I just did this to get the top-20 of the numbers I call:

% cat /var/log/asterisk/cdr-csv/Master.csv | grep 'internal' | cut -d, -f3 | \
    sed -e 's|+33|0|' | sort | uniq -c | sort -nr | head -n 20


On December 30, 2011, Jean-Marie Favreau wrote:

Since SVG is a text-based format (an XML language), you may create a script that inserts into an SVG template your top-20 numbers (you can have a black-list file to remove the unwanted numbers, the ones you don't want to flaunt on your desk).
The next step is to add a line in your crontab, that checks if your numbers has been modified, and print the new PDF in case of modification. :)

Merry Christmas!

On December 30, 2011, Romain Tartière wrote:

Hi JM!

Well, I though about writing a script for automagically filling-in the SVG document but I saw a few issues in my case and I don't think it worth the time (can be an amusing exam subject for students anyway):

  1. As you mentioned, there are some numbers I don't want to have as fast call keys (e.g. *1, 123);
  2. Another point is that the log only has the numbers, not the caller-id (i.e. real name) and in my LDAP directory, a single telephone-number can belong to multiple persons (I am considering to register places in addition to people to circumvent this limitation but I am not sure that this would really help making my life easier anyway). In such a situation, I can't rely on the directory information to retrieve the label corresponding to the number, and I have to pick a custom name myself;
  3. Some names in the LDAP directory are a bit too long and required to be shortened to fit in;
  4. A last point is grouping: I didn't want to order the numbers by how often I use them, but rather by the category they belong to (e.g. family, friends).

Taking all these rules into account would have required some non-trivial development, and as I don't plan to change these numbers every once a while, I stuck to filling-in the sheet myself.

However, in a company context, auto-filling-in the template definitively makes sense. In this case, using the same source to generate both the filled-in template (using XSLT) and the provisioning configuration files would make the fast call keys update for internal calls as easy as changing the sheet and rebooting the telephone!

Happy end of year season!

Comments RSS feed | Leave a Reply…