Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width70%

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.

 

Image Added

 

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).

 

API

The API consists of a single function:

Info
iconfalse

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

ParameterDescription
ip_local

internal device IP, as string, to be stored for DynDNS requests

part_numberDevice part number (device group factory identifier)
macPhysical address of device WAN interface
noHandsetsNumber of handsets registered to the basestation
response.code

Result of server operation, non-negative values for success, negative for error. Currently following
values are supported:
• 0—successful update
• -1—internal error

response.message

textual description for response.code (internal and non-localized, should never be reported to end
user)

 

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,

 

Column
width30%

Table of Contents