-23-
v7.0
Callback Server
<VirtualHost *:80>
ServerAdmin webmaster@localhost
ServerName my_server.com
ServerAlias my_server.com
DirectoryIndex index.html index.php
DocumentRoot /path/zip/extracted
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
<Directory /path/zip/extracted>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
</VirtualHost>
Check the right owner/group and permissions of all the files extracted in order to be accessible.
Usually using
www-data
group is default in Ubuntu environment.
Check the permissions of all folders and files.
Usually using 0770 for directories and 0660 for files is default in Ubuntu environment.
Enable this new configuration site created and restart the Apache server.
9.3. Making the server accessible from anywhere
Compulsory for Sigfox and Actility platfoms.
Optimal deployment includes a server name pointing to a public and static IP, using dynamic DNS could be done with services
like no-ip which has a free package http://www.noip.com/. No-ip has also a client application responsible for updating any IP
address changes in the background, more information in:
http://www.noip.com/download
Finally, the URL to configure the SigFox and LoraWAN platforms to send the callback request to will be conformed with the
server name and the paths:
https://my_server.com/path/zip/extracted/
9.4. Remote node configuration web
The remote node configuration tool is available in the URL you established in your configuration file previously
(http://my_server.
com/)
. This tool is used to configure the nodes in a remote way when received messages require an specific answer. Similar to
the Java application, this web form can modify some parameters of the parking nodes remotely. The aim of this remote manager
is to generate a binary file with the configuration selected:
1. Response to the Start Frame number 1, transmitted by the node in the activation process. This response frame allows the
initial time synchronization of the internal clock. In normal conditions, the activation process happens only once.
2. Response to the Daily Update Frame with a timestamp, in order to perform a time synchronization of the internal clock. This
will happen once per day and helps to keep the node’s time drift to minimum.
