News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Unanswered Email

Started by RonR, August 25, 2011, 10:12:49 AM

Previous topic - Next topic

RonR

Quote from: OBiSupport on September 27, 2011, 05:44:33 PM
Quote from: RonR - Today at 02:35:09 PM
I've repeatedly tried to use your suggested work-around.  If it's used, NO outgoing calls can be made.
As the suggested work-around does not work for your application, there is no solution.

The problem isn't that your suggested work-around doesn't work for MY application.  The problem is your suggested work-around doesn't work for ANY application.  Simply adding your suggested work-around to ANY DigitMap prevents an OBi from making ANY outgoing calls.  The use of your suggested work-around in ANY manner disables an OBi's outbound calling capability ENTIRELY.  That alone should make you curious enough to further investigate this issue.

It's extremely disappointing that Obihai Technology is not interested in investigating and correcting problems encountered by its customers.  Worse yet is that you would try to sweep the problem under the carpet with a work-around that was never tested and obviously still hasn't been tested.  Such a tactic shows nothing but disrespect for your customers.

tome

Quote from: OBiSupport on September 27, 2011, 05:44:33 PM
Yes.  We read your posts and e-mails.  We really appreciate the thought and effort you expend to help the OBi user community.

As the suggested work-around does not work for your application, there is no solution.

Here, we are stating the current functionality.  At this time, there is no date as to when the current functionality will be modified.

Thank you your support.

Give up RonR.  They have no intention of being forthright on this issue.  Boo Obihai. ???
Tom

earthtoobi

Ronr: its pretty obvious that obihai wants to look in the other direction.
comments like "We really appreciate the thought and effort you expend to help the OBi user community" appears to be just lip service.

Ostracus

Does the latest firmware address the current bugs?

RonR


RonR

This problem was not corrected and is 100% reproducible in Software Version : 1.3.0 (Build: 2586)