Call Waiting problems: no ringback, no CID

[moji]

My problem is similar, though a little different. If I am speaking on first call, that caller is disconnected if I receive a second call. I have been back and forth with tech support. Their solution is that it is not an Ooma problem, but more a problem with the first caller---they believe first caller must have been on cell phone when he was disconnected and the disconnection is not because of Ooma, but because the wireless system faulted. This has happened more than I care to think. I use AT&T dsl. my download speed is 2.59 Mb/s and my upload speed is 0.43 Mb/s. I only connected the hub, did not connect the scout.

Any ideas?

[cclauset]

For the no call-waiting caller-ID issue, we're tracking this one in " 5984: Telo: call waiting caller-id is not displayed" This feature was working before, but it seems to have stopped working properly in the latest builds. We're actively working on the fix now.

Any update or ETA on fixing the no call-waiting caller-ID? It's been almost two months since you posted this bug tracking note…

[cclauset]

For the no call-waiting caller-ID issue, we're tracking this one in " 5984: Telo: call waiting caller-id is not displayed" This feature was working before, but it seems to have stopped working properly in the latest builds. We're actively working on the fix now.

It's ~3 months since you starting tracking this issue... Any update or ETA on fixing the no call-waiting caller-ID?

[cclauset]

Although I see a note about CWCID compatibility in the 35170 release notes, but I'm still not seeing any CWCID on my AT&T DECT phones (SL82418).

Better call-waiting caller-id compatibility on FXS (still not perfect)

[amoney]

Although I see a note about CWCID compatibility in the 35170 release notes, but I'm still not seeing any CWCID on my AT&T DECT phones (SL82418).

Better call-waiting caller-id compatibility on FXS (still not perfect)

There is another thread with a off topic post regarding all of this, apparently its obviously still not fixed but there have been improvements (I can confirm my Panasonic intermitently displayed the CWCID sometimes), but anyways they apparently have one more update they are waiting to push out that looks to finally resolve the issue (so the test appear).