Got something else to discuss that is not covered by the previous forums? Post it here!
#61312 by calkid4ever
Mon Aug 02, 2010 10:13 am
CWCID does NOT work with my Vtech DECT 6.0 DS6321-3 system which is directly connected to an OOMA Telo. I hear the beep interrupt, but nothing shows on the phone display, nor does the missed call show up in the call log on My Ooma. The only indication of a missed call is if the caller leaves a voicemail.

I see many posts re: CWCID not working and followed them back to your post 4 months ago stating that OOMA was waiting on a firmware update from one of your vendors.

Dennis P wrote:351570/35452 are better at CWCID then 32829/33190, but not perfect yet. The final fix requires a firmware update from one of our vendors. We've tested an engineering build which looks like it truly fixes the problem, so are just waiting for an official build to trickle down to us.


I agree with others -- this is a major annoyance, especially since CWCID has worked flawlessly with virtually all voice providers and telephone manufacturers I have used over the last 10 years (Vonage, Sprint/Embarq/CenturyLink, AT&T CLEC, and SBC/PacBell --- Vtech, Panasonic, AT&T, Uniden, and Polycom).

Please provide a current status of this fix. When will be deployed to the Telo?
#61332 by philw132
Mon Aug 02, 2010 1:57 pm
I agree with you calkid4ever,

They have put out two firmware updates since I was promised a fix. I haven't seen anything yet.
I also have the same vtech phone system.
Hope ooma responds quickly to our requests.

Phil

calkid4ever wrote:CWCID does NOT work with my Vtech DECT 6.0 DS6321-3 system which is directly connected to an OOMA Telo. I hear the beep interrupt, but nothing shows on the phone display, nor does the missed call show up in the call log on My Ooma. The only indication of a missed call is if the caller leaves a voicemail.

I see many posts re: CWCID not working and followed them back to your post 4 months ago stating that OOMA was waiting on a firmware update from one of your vendors.

Dennis P wrote:351570/35452 are better at CWCID then 32829/33190, but not perfect yet. The final fix requires a firmware update from one of our vendors. We've tested an engineering build which looks like it truly fixes the problem, so are just waiting for an official build to trickle down to us.


I agree with others -- this is a major annoyance, especially since CWCID has worked flawlessly with virtually all voice providers and telephone manufacturers I have used over the last 10 years (Vonage, Sprint/Embarq/CenturyLink, AT&T CLEC, and SBC/PacBell --- Vtech, Panasonic, AT&T, Uniden, and Polycom).

Please provide a current status of this fix. When will be deployed to the Telo?
#63657 by philw132
Tue Aug 31, 2010 8:12 am
Just to let everyone know this issue has been fixed and will be pushed in a firmware update sometime in september.

I'm sure excited about it
#63915 by philw132
Sat Sep 04, 2010 12:00 pm
In an email from one of our well informed mods

BobbyB via email wrote:Hi Phil,

Bug 5984 appears to be fixed in the latest beta build, according to our Beta testers. We're aiming to get this release out sometime in September.

Thanks,
Bobby
philw132 via email wrote:On Aug 28, 2010, at 10:09 AM, Phil wrote:

> Bobby,
>
> Is there an ETA on bug 5984 yet? This is a very annoying bug i would love to be able to stop multi-ringing my cellphone just cause of the caller id.


cbking02 wrote:philw132 where did you learn that CWCID would be fixed in September?
#65085 by alanrf
Mon Sep 20, 2010 9:07 am
I note with disappointment that BobbyB posted in another thread that the next release is unlikely to appear now until October. Many of us must go on with this basic telephone service feature still crippled or totally unavailable.

With threads going back more than nine months on this issue and apparently at least 2 releases with failed attempts at fixing it I have to wonder if the reported latest and greatest will fix it properly. Would it not make sense to allow a few more of us with the problem to preview the latest release to provide better certainty of success?
#65136 by southsound
Mon Sep 20, 2010 4:48 pm
Please pardon the rather terse comment, but "pull up your big boy underwear and get over it". We get great phone service. We don't pay anything but minimal regulatory fees and taxes. And did I mention we get great phone service? Most phones have CWCID - my Uniden's have never lost it. But even if they didn't show the interrupting caller information, I wouldn't feel ripped off. Did I mention we get great phone service?

Image
#65160 by alanrf
Tue Sep 21, 2010 12:11 am
southsound,

I have taken the trouble to read a number of your posts in this forum. I am not a technical newbie and you come across as an apologist for Ooma and I will treat your posts as such henceforth.

Perhaps (though I doubt) you can provide the technical support for the following facts that are often treated in these forums as being phone provider specific:

I can demonstrate fully repeatable alternate configurations for my given phone manufacturer using the Ooma service where:

1) CWCID never works (where the Ooma Telo is behind the router and even when the Telo is in the DMZ of the router). Router in question if you want to discuss is Linksys WRT54GL using up to date DD-WRT firmware.

2) CWCID works every time during a call to/from for a specific service provider of the primary call connection

3) CWCID never works during a call to/from a different specific service provider of the primary call connection

4) The service provider of the CW call appears to be totally irrelevant

Items (2), (3) and (4) have been confirmed by tests conducted by another (recent - like myself) Ooma customer known to me and using a different telephone product in the home.

If you have valuable technical input please put up - or else please avoid further apologist comments.
#65162 by alanrf
Tue Sep 21, 2010 1:16 am
In case there should be anyone wondering ...

Prior to porting my telephone number to Ooma I had no issues with CWCID with the same home phone VOIP service provided by Comcast. Since I was experiencing this CWCID problem with Ooma, after porting my number to Ooma, I also went to Comcast and switched my older cable modem with EMTA for a regular non-EMTA cable Internet modem. The change has made no impact to the issues I reported in the post above.

Who is online

Users browsing this forum: Google [Bot] and 11 guests