Updated Idea:

Let's define a standard way for VSP to define needed settings to connect with them (protocol, codec, hosts, ecc...) This way they can publish an XML file with configuration guidelines and freePBX can parse them and build an on-the-fly wizard for users asking only needed info (e.g.: username, password and preferred codec).

sorry..., still working on it, will post soon my first beta

--Ed

---

A good way to implement this would be to have a DNS TXT entry that points to the URL of an XML file that defines the settings. In freePBX users would enter "myitsp.com" as their ITSP name, and then it would query the DNS for myitsp.com, get the xml file (say, "http://www.myitsp.com/freepbx.xml") and then download it, and ask for whatever info the XML specifies to ask for (probably username, password, codec).

Advanced stuff

I like the general features in #740 but freePBX cannot support one single ITSP like this. Perhaps we can draw from those ideas though, and implement certain services on the trunks screen that are ITSP-specific. This could range from simple things like allowing the XML to specify links (possibly including variables, like <link href="http://accounts.myitsp.com/add_did?user=%username%">Add a new DID</link>), to more complex things like actually having controls and doing REST/SOAP/XML-RPC calls to their server to allow querying time used, or adding DIDs or whatever.

--gregmac

---

Relevant tickets: #740