Damian, Martin, For implementing XCF-2509(Add support for Aastra 560M Expansion Module <http://track.sipfoundry.org/browse/XCF-2509>), I have a few questions:
The web-ui for the Expansion module offers many features that can be configured for each key. If we were to implement configserver support using the same technique, then I can see a few issues with this: 1. Many of the phone-side configurations like ACD, Intercom, Park/Pickup code, XML, etc. do not make sense as ECS only supports server side settings for these features. 2. The expansion module has a total of 3 pages and each page has 20 keys. Displaying this on the configserver UI poses a problem in terms of usability. 3. Most important - We will not be able to take advantage of the configserver's speeddial / BLF implementation - as we are allowing the user to set the values for expansion module keys directly rather than allowing the configserver to set these values based on the speeddial entries. Therefore, in my opinion, it would be most ideal to implement the Expansion module support for the Aastra phones in such a way that the expansion module keys are set directly to speeddial entries (or BLF if 'subscribe to presence' is enabled). Please let me know if this is the correct approach. Thanks Raghu _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
