Device Provisioning

Top  Previous  Next

The Device Provisioning module allows AgileVoice to generate the appropriate file used by end-user VoIP telephones and adaptors.  The Device Provisioning module comes with templates for Linksys, Cisco, Grandstream, and Sipura.  By following one of the included templates, any additional adaptor template may be created.

 

NOTE: Certain devices require a template compiler provided by the manufacture and/or resellers. These compilers are not provided by Agileco and may involve additional costs and/or platform requirements.

 

Enabling Device Provisioning

 

To enable a certain VoIP adaptor or telephone, go to Admin -> VoIP -> VoIP Device Setup.  If the type you would like to enable is already present, then simply double-click the entry to bring up the edit configuration screen.

 

In order for the entry to be selected by end-users or the administrator while adding a service, the item must be active.  The manufacture and model should be filled in according to the selected Provisioning Plugin.  Additionally, the make and models maximum number of VoIP lines should be entered, allowing the system to automatically provision an adaptor with multiple DIDs.

 

The custom fields may be used for any variable you'd like to change within the configurations.  A typical use would be for line gains.  A general default may be set for the plug-in, while each customer's DID may be over-ridden to accommodate for each users needs.

 

Once an entry is configured, the product plug-in must allow for its selection.

 

Enabling Device Access

 

Once there are provisioned devices, the run-av.sh script is used to physically generate the output files used directly by the devices or as the input to the manufactures compiler.  The output is then stored in the configured directory, which is typically /tftpboot so that the TFTP service may be used to transfer the configurations to the end-user devices.  The actual process involved in the end-user device acquiring their configuration is device dependent, but usually requires a few supporting files and even router DHCP server configurations.  The details of this process are left as an exercise to the customer to design and implement.