On Thu, Jun 18, 2009 at 10:12 AM, Scott Lawrence<[email protected]> wrote: > On Thu, 2009-06-18 at 13:14 +0100, Christopher Parfitt wrote: >> I was thinking of adding this as an improvement Jira issue : >> The ability to export and import ITSP SIP Gateway Templates (of course >> without the User registration security information) >> The community could share new Templates that they have proved to work >> with newer ITSP's. Also new Templates that have been tried and tested in >> QA could be distributed and imported easily. >> Comments? > > 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 > > > _______________________________________________ > 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/ > -- M. Ranganathan _______________________________________________ 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/
