A free, simple, easy-to-implement, standards-based,
feature-rich dialtone for your SIP hardware or softphone...

Engineers Testing or Implementing Plug-N-Dial

Provisioning Method:

Live Examples

The following live examples have been developed to assist in the development of a plugndial compatible device

1: HTTP

This is a plaintext response of the configuration file. This is not recommended for security reasons.

Example:http://aps01.sipphone.com/test/app?class=Test;proc=provision;mac_address=ffffffffffff

2: HTTPS

A more secure version, the return file is the same plaintext file.

Example:https://aps01.sipphone.com/test/app?class=Test;proc=provision;mac_address=ffffffffffff

3: HTTP w/ Encryption

This is a good solution to use for auto provisioning your devices.
All encrypted files also include the XML tags <UNENC> and <key> which will not be included in a normal encrypted transaction. The key used for the encryption should be negotiated between the Manufacturer and the Provisioning Service.

Example:http://aps01.sipphone.com/testenc/app?class=TestEnc;proc=provision;mac_address=ffffffffffff

4: HTTPS w/ Encryption

This is a better solution to use for auto provisioning your devices, as a secure channel is generated, and the contents are encrypted.
All encrypted files also include the XML tags <UNENC> and <key> which will not be included in a normal encrypted transaction. The key used for the encryption should be negotiated between the Manufacturer and the Provisioning Service.

Example:https://aps01.sipphone.com/testenc/app?class=TestEnc;proc=provision;mac_address=ffffffffffff

5: TFTP

The following TFTP request for md5 file and corresponding txt file are a minimum test to check if your device is able to autoprovision itself.

Example:
tftp aps.plugndial.com GET /ffff/ffff/ffffffffffff.md5
tftp aps.plugndial.com GET /ffff/ffff/ffffffffffff.txt