iServer the xAP UDP/TCP Gateway

o2-joggler-tablet.jpg

As Flash does not include general UDP support the iServer provides a TCP tunnel for the O2_Joggler to receive xAP messages.

It is also very useful for devices attached over WiFi as it provides guaranteed message delivery.

When xAPFlash attaches to iServer at startup it registers all the xAP devices in which it has an interest in receiving updates from based on the <source> tags within the xAPconfig.xml file. iServer then filters out all the xAP traffic from other devices ensuring the clients only receive relevant messages. However if a message from any xAP device is targeted directly, without wildcarding, at a named xAPFlash client it will still be forwarded correctly.

The O2_Joggler units have been discontinued by O2. However they can still be purchased on the 2nd hand market if you search www.ebay.co.uk

An old thread thread on the xAPFlash application.

The xAPFlash application now has it own Forum
http://www.automatedhome.co.uk/vbulletin/forumdisplay.php?f=29

The HAH iServer can be enabled via the HAH web GUI.

  • Client authentication mode - The Windows iServer, by default, runs in an authentication mode, however most people using this do so on their own LAN so the HAH iServer implementation can ignore the password and authenticate regardless, thus easing integration.
  • BSC Query Pacing - When a client registers its filters, the iServer, on detecting the first heartbeat from the client, will send a BSC query to each filter. If it does this too quickly, the responses might not be processed quickly enough by slower clients to catch them all. To solve this problem, a delay can be introduced on sending each BSC query when the client initially registers.
  • FD - (file descriptor) of the client socket - mostly people won't know what this is for (that's ok). If you have two connections from the same IP both identifying themselves with the same SOURCE you'll see this as they have different FD's.
  • Status Rx/Tx - These are the count of xAP frames received and transmitted by the client, respectively.
  • /min - The number of xAP frames received and transmitted by the iServer to the client per minute.

See below for the configuration parameters in /etc/xap.d/iserver.ini that iServer honours. These can also be updated via the WEB interface. If the option isn't present in your .INI file it means the default is being used.

[iserver]
enable=1       -- 1 automatic startup, 0 disabled
authmode=0     -- 1 enabled, 0 disabled
port=9996
pacing=20
passwd=
uid=00DE

Go get yourself a livebox and try it. Once you're impressed, stop by the shop and grab some other goodies for it.

Protocol

TBD