All our issues with iBurst_Terminal Connect UTL

[ic]

Creating this thread so that we can document all the issues we have with the iBurst_Terminal Connect UTL software used to establish a connection.

Hopefully this might get back to Kyocera and the software will improved...

 

[ic]

Redial problems/Windows version

The software is inconsistent in the way that it tries to reconnect when set to redial xx number of times.

Depending on the problem it runs into, it usually throws up a dialog box that requires human intervention everytime, instead of just doing another attempt, or having a dialogbox timeout before it does another connection attempt.

 

[ic]

SysTray App only works with USB/iBurst_Terminal UTL v1.02 2004-09-28

It would be nice to be able to use the iBurst System Tray software when a connection is established via ethernet.

 

[aborg]

I tried that utl and it didn't work for me, for some reason the ethernet option performs much better and no utl reqiured. My connection has been quite stable lately under win, on suse it seems to disconnect itself - but that is just settings I have to tweak.

 

[ic]

There should be an iBurst software component that can be used to periodically record FER (Frame Error Rate) as well as Signal Strength in a logfile, and there should be an option to disable this if one decides to do so, this logging should be enabled on initial install (which is when new customers are likely to experience connectivity problems), when logging is enabled, a prominent notice in a textbox should be displayed - i.e. no popup dialogboxes.

This logging should be able to run independently of the Systray application (i.e. if that isn't running) that only displays current FER & Signal Strength, but does not record these to a logfile.

Related thread(s):
[post=155208]iBurst very slow[/post]