> >> >> Sounds like a pretty good idea to me. >> >> [Chris - don't reply to an unrelated message when posting to the list - >> it messed up the threading] > >This has come up from time to time. The current scheme requires that >we distribute a new version of sipxconfig each time we have a new >template. This is problematic. I like this scheme. It would be great >if we could have people just post it to the sipx-users mailing list >with a special title perhaps and a tool that just walks through the >list picking up hints for ITSP configuration. The easier we make it, >the more it will get used. > >Ranga
We should make sure we distinguish between stable things and experimental things. This is not just true for ITSP templates, but also phone, device and other plugins. Users very often seem to be getting confused whether something is really supported, tested, and therefore works or whether we added experimental support. Making e.g. a phone procurement decision this becomes kind of important. Therefore, I suggest we start to clearly split this up in drop-down menus so that it is clear. --martin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
