Hi
OK, here's how our provisioning works...
We get a manual from the manufacturer (in this case sipura/linksys) and we use it to set up a "reasonable-fits-most-cases" provisioning template in the device definition. Then, when you actually create an instance of the device (i.e. an extension), it inherits whatever provisioning is in the the device template and then updates it with extension specific data, like extension number, caller name and so on.
You can read about device definitions in our manual here
http://www.selintra.com/docs/cgi-bin/view/Main/DocChapter082Now you can do one of two things...
You can create your own device definition - call it something like "my942"or whatever you like. Then you can copy the template from our 941/942 definition as a starter or you can provide your own from scratch.
OR...
You can modify our 941/942 definition to suit your needs.
We would strongly recommend the first option because our update rpms run a routine which updates our definitions to keep them current and you could conceivably have a situation where we inadvertently walk all over your nice definition if you change the existing one.
There are some notes in our manual about our universal provisioning which you can find here
http://www.selintra.com/docs/cgi-bin/view/Main/DocChapter255We also have the sipura/linksys provisioning manuals, however they are restricted release (heaven knows why) but we can help if you are trying to do something which has you stumped.
Kind Regards
Selintra
15 Replies
6072 Views