just a couple things. i am gonna go heavy but at the same time i may be ignorant on some of the mechanics of snom one/attendant console integration. testing on 4 blues installed at diff locations ~40 phones at each... client requests:
1 - multiple domain level presence (i know, might be taxing)
2 - xml global phonebook (domain level privs)
3 - hardphone dial (i don't care if this even passes the calls via web url)
4 - incoming call notification (my clients are always looking at their screen and a popup with caller ID and a picture of a face is easier to identify than a phone number..pick up handset to answer)
and to stretch this out even more, one touch recording on calls to the local machine using sip headers and using the ethernet switch on the phone as a tap. a little birdie told me that you can set the ethernet ports to work in a non-switched state. of course i understand this will tangle the QoS. i know this may be a bit but the first 3 are trivially necessary.
it would be even better if you can integrate the recording cdr in the agents section to include all recorded calls from the local machine and can pull all the recordings to a local or remote area for archiving. if not, then i can write my own.
and WAY WAY out there is maybe a small "virtual" lcd screen with DSS keys around it to be able to write custom XML pages to create things like visual voicemail and what not. that would really be cool.
just some ideas that i have had while banging my head into a wall to get snom one to be as seamless as possible to my clients. so far, i have had to hand write most of the functionality needed and using third party apps like VOP.
also, you should put version #s on the download page, 'cause i don't know if i am downloading a new version or one that i did a couple weeks ago...also, maybe we can stem away from the m9 functionality in the attendant console (autoprovis/tftp) and make it act more like a 370 or 821?
just my 2 cents.