You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

1.0 Introduction

Primary goal of DynDNS service is to simplify access to device web-based configuration interface for end users not familiar with IP addresses and/or local network configuration. The device submits its local IP address to the service,
and this information, along with external IP of the device (discovered from incoming request), is stored in the DB. When user wants to access web-based configuration interface, gigaset-config.com page shows a list of devices registered
from given external IP, and it is enough to click the proper device name to log in.

In typical DSL-like configuration case, there is only one gigaset phone registered for given external IP and user gets redirected to device’s web UI automatically.


Apart from supporting DynDNS functionality with local IP information, the service gathers additional information about device identity—such as partnumber (device group number), or MAC address. Those additional information can be
used to identify device and/or to update gigaset.net device database. Number of handsets registered in user’s basestation is provided for statistical purposes.
Please also note that further device-specific information can be discovered using device User-Agent string (device type and software version information).


The API consists of a single function:

DynDNS.notify(string ip_local, string part_number, string mac, int noHandsets) :
struct response { i4 code; string message; }

 

Notification has to be sent after any handset IP address change, and periodically - once per 24h. Periodical notification randomization is necessary (24h ±33%) to avoid possible traffic flood,

 

  • No labels