On the picture below, you can see the result of the real server respond after valid XML – file uploading:
Here, by pressing the “Result” button marked by red square, you can get XML – file containing the same information as presented on the picture, in other words, XML – file, containing – MAC – address, provider name, URL and date of registration.
5.1 List devices name This is an a sub-option of the method presented above. Basically, you will get the same information (after uploading your XML – file), but for a specific provider. General structure of the XML – file:
<?xml version='1.0'?>
<methodCall>
<methodName>autoprov.listDevices</methodName>
<params>
<param>
<value><string>Daryna</string></value>
</param>
</params>
</methodCall> |
- you can specify as many providers as you wish
General structure of the XML – file:
Server response description: Return value (0-n)
(Object[])
[MAC,NAME,URL,DATE] |
The result of usage valid XML -file after successful uploading (only one provider was specified):
6 Check device(s) This option allow its requester to check either the device is registered or not. Along with information that device is registered, requester will get a provider name, URL and date of registration. General structure of an XML file will look like this:
<?xml version='1.0'?>
<methodCall>
<methodName>autoprov.checkDevice</methodName>
<params>
<param>
<value><string>7C2F80820EC0-55DF</string></value>
</param>
</params>
</methodCall> |
XML template can be downloaded here:
Several server's responses are possible:
Return value (1) (Boolean) 1 | 0
1 = true, 0 = false
Return value (2) (String)
if true: [MAC]
if false: mac_not_found
mac_invalid
Return value (3)
if true: [NAME]
Return value (4)
if true: [DATE]
Return value (5)
if true: [URL] |
Below, you can see the real server respond based on the valid MAC – ID:
The real server respond based on the invalid MAC – ID:
7 Usage of XML-RPC script
7.1 Registration of the single device using ap-client.py script First thing which has to be done (for this steps and all the steps below): - Make sure Python is installed on your OS. If not, please do install.
- Under console change your working to the directory in which ap-client.py file is saved.
- Run necessary command.
After all the described steps above were done, please run 1st command for the device registration:
python ap-client.py Auth-Name Auth-Pass prov.gigaset.net autoprov.registerDevice s:MAC-ID s:URL s:Provider-Name |
In case of the successful registration, server will answer:
And in prov.gigaset.net your device will be recognized as the registered one:
7.2 Check - status In order to check status of the device, you have to run next command: python ap-client.py Auth-Name Auth-Pass prov.gigaset.net autoprov.listDevices s:Provider-Name |
On the picture below, command in use within server response can be seen:
7.3 Device deregistration In order to deregister device, you have to run next command: python ap-client.py Auth-Name Auth-Pass prov.gigaset.net autoprov.deregisterDevice s:MAC-ID |
On the picture below, command in use within server response can be seen:
7.4 Deregistration of the list of devices In order to deregister list of the devices, you have to run next command (specify here all MAC-ID which you want to deregister): python ap-client.py Auth-Name Auth-Pass prov.gigaset.net autoprov.deregisterDeviceList sl:MAC-ID1,MAC-ID2,MAC-IDN |
On the picture below, command in use within server response can be seen:
7.5 Registration of the list of devices In order to register list of the devices, you have to run next command (specify here all MAC-ID which you want to register): python ap-client.py Auth-Name Auth-Pass prov.gigaset.net autoprov.registerDeviceList sl:MAC-ID1,MAC-ID2,MAC-IDN s:URL, s:Provider-Name |
On the picture below, command in use within server response can be seen:
ap-client.py is an exemplary script, we not guarantee that this solution is stable enough for sharing it with customers. Examplary code can be requested from the 2nd Level Support as well as from Bakker, Bas. |
DX800 enabling Redirect ServerDependent on the DX800 variant, it can be that the redirect server option is disabled. This can only be enabled via special configuration, for this you need a patch. The patch is based on the variant and contains the following settings to enable redirect server.
BS_IP_Data1.ucB_HAS_PROVISIONING_CODE=1 BS_IP_Data1.ucB_SHOW_PROVISIONING_CODE_IN_HS=1 BS_IP_Data1.ucB_AUTOPROVISIONING=0 BS_IP_Data1.ucI_AUTOPROVISIONING_STYLE=0 BS_IP_Data1.ucB_AUTO_UPDATE_PROFILE=1 BS_IP_Data3.ucI_ONESHOT_PROVISIONING_MODE_1=1 BS_IP_Data1.aucS_AUTOPROVISIONING_CODE=0x34,0x34,0x34 |
Via the restore option, you can activate the patch below. If you variant is not listed you need to request this from Gigaset.
|