What's new in FW 3.0.1 (Build: 3878)?
Ostracus:
I noted syslog has a TAG field. DnsLookupType in Auto firmware update. Also look at star code 31. FaxPayloadType in codec.
CoalMinerRetired:
Quote from: Ostracus on May 11, 2013, 08:25:31 pm
I noted syslog has a TAG field. DnsLookupType in Auto firmware update. Also look at star code 31. FaxPayloadType in codec.
I got curious why these fields didn't show in the comparison I did. In the 3741 export I have, all those fields are present, note that I did not look at the actual device interface web pages to confirm, only the XML export.
Quote from: QBZappy on May 11, 2013, 03:36:53 pm
...
What other changes did you note?
Nothing else. Four more rows in the 3878 export (vs. 3741) being these four fields, one in each ITSP profile account. Only checked the basic exports made with no options included, did not look at anything in the screens, for example new values in drop down lists or any changes to default values, etc.
It is curious that Obi is not mentioning this in any announcement or blog posting. Would you conclude from that it's all routine maintenance fixes not worthy of any formal announcement?
QBZappy:
Obihai is one of the few hardware/software devs that I know that find it to be a "chore" to post any changes. There must be a chief software developer in charge. How hard would it be for him to write up a few lines detailing the changes. How hard would it be for the marketing people to handle this if they feel it must pass their screening. That little effort would add positively to their rep. Instead, Obi users are constantly bad mouthing their inattention to this detail. Given the possibility of both outcomes, where would a well intentioned company put the effort. Obihai has not understood a basic concept of task management. The task is not complete until all the steps are complete. They have not identified that advising the customer is a component in the task of building firmware. If I was the software dev I would ask myself why am I making this effort. Am I doing this to serve my needs, or the needs of others? If you can identify whose needs you are serving then you must inform them, otherwise you are creating these conditions perpetually.
It surprises me every time when they make changes to the firmware why they don't document it and reap the accolades of the user base for a job well done. It's all win/win. Why is this so hard to understand!
AAABen:
Quote from: QBZappy on May 12, 2013, 06:07:22 am
Obihai is one of the few hardware/software devs that I know that find it to be a "chore" to post any changes. There must be a chief software developer in charge. How hard would it be for him to write up a few lines detailing the changes. How hard would it be for the marketing people to handle this if they feel it must pass their screening. That little effort would add positively to their rep. Instead, Obi users are constantly bad mouthing their inattention to this detail. Given the possibility of both outcomes, where would a well intentioned company put the effort. Obihai has not understood a basic concept of task management. The task is not complete until all the steps are complete. They have not identified that advising the customer is a component in the task of building firmware. If I was the software dev I would ask myself why am I making this effort. Am I doing this to serve my needs, or the needs of others? If you can identify whose needs you are serving then you must inform them, otherwise you are creating these conditions perpetually.
It surprises me every time when they make changes to the firmware why they don't document it and reap the accolades of the user base for a job well done. It's all win/win. Why is this so hard to understand!
eh.... small company? no dev process?
CoalMinerRetired:
I noticed in another thread there's a new Obi202 firmware out there (yellow icon in the portal next to a '202 device), firmware version 3292 3932.
Applied the update, then did an XML export comparison. In moving from 3878 to 3292 3932, noticed one new field, RandomDelayRange, defaulting to 30 ("the range of delay in seconds before the first attempt only, minimum 0"), in the section for Auto Firmware Update under Auto Provisioning under System Management.
I presume the real meat and potatoes of the difference in the firmware is something to do with the recent Google Voice/Google+ Hangouts changes, and is not apparent in any one particular new field.
Edit: 3292 to 3932.
Navigation
[0] Message Index
[#] Next page
[*] Previous page