Caller ID switches to "Name unavailable"

Discussion in 'ViP612/622/722/722K DVR Support Forum' started by jrmy, May 17, 2011.

  1. MattG@DISH Network

    MattG@DISH Network Member

    598
    3
    Jan 6, 2011
    I'm sure there's something in our customer agreement that covers it (I think section 7-B covers it)

    I did report the issue, but I could not give any ETA as to if/when it would be fixed.
     
  2. FarmerBob

    FarmerBob Godfather

    703
    14
    Nov 27, 2002
    DISH gear works just fine with at least ViaTalk, Vonage and VoIPO. This is not a "DISH needs to fix it" issue. It's an Ooma needs to use standard specs issue. If they are altering the type of CID that you get with whatever level of service that you have, that means that there is an altered CID signal happening. This is not a standard spec and not a DISH issue.
     
  3. jrmy

    jrmy Cool Member

    10
    0
    May 17, 2011
    I disagree. I remember GTE offering the option of number or name and number caller ID in the early 1990s. Just because different information is being passed does not mean that it's a different signal.

    The fact that I can't reproduce this issue on any caller ID capable device seems to point to the issue being with Dish.
     
  4. V35_Pilot

    V35_Pilot Cool Member

    21
    0
    Jun 7, 2011
    Cannot comment on the other two, but as a long-time Dish and ViaTalk customer I will again point out that the OP's problem definitely occurs with regular frequency on my VIP722 and ViaTalk as the VOIP provider. It is a nuisance.
     
  5. TulsaOK

    TulsaOK New Member

    3,469
    0
    Feb 23, 2004
    I respectfully disagree. Dish is decoding the Ooma stream correctly then, for whatever reason, decides the caller-id is unavailable. I think Dish, at least, needs to investigate how they handle caller-id.
     
  6. oldanbo

    oldanbo Cool Member

    32
    2
    May 20, 2004
    I wonder if Ooma is sending additional data in the caller id stream and that is what causes the problem? I've just been ignoring it. Might be a good idea to check the Ooma.com forums. Or I can just ignore it. Hmmmmm
     
  7. TulsaOK

    TulsaOK New Member

    3,469
    0
    Feb 23, 2004
    I tend to ignore it but it's an issue that Dish probably needs to investigate. It is annoying. If Dish won't contact Ooma to work this out I will submit a trouble ticket with Ooma.
     
  8. harsh

    harsh Beware the Attack Basset

    22,708
    425
    Jun 14, 2003
    Salem, OR
    For reference, I use Viatalk with a BYOD Linksys PAP2T SIP adapter and CID works just dandy.

    The preponderance of difficulty with Ooma devices suggests the problem is most likely there.

    CID isn't that complicated and all the data is supposed to come between the first and second ring at 75 baud.
     
  9. TulsaOK

    TulsaOK New Member

    3,469
    0
    Feb 23, 2004
    I have escalated this to Ooma Technical Support. I'm now convinced this is an Ooma issue and not a Dish problem. This doesn't happen with Ooma Hub; only the Ooma Telo system. The Name Unavailable only happens once it rolls to voice mail either naturally or manually sending via Ooma Telo Handset.
    Once I get a response from Ooma, I'll post it.
    I have a bottle of Frank's Hot Sauce that states "I put that $#@& on everything". I hope it goes with crow. :)
     
  10. 4bama

    4bama Godfather

    372
    8
    Aug 6, 2006
    Let me add my observations about the "Name Unavailable" issue...

    I have a 622 with the AT&T "all options" land line connected directly from a wall outlet to the receiver. I noticed this entry occasionally being stored in the caller ID history, but never seeing it pop-up on the screen real-time.

    I finally narrowed it down to where I could cause this to happen...it happens every time I am either watching a pre-recorded program, or if I pause a real-time program when the phone rings.

    The "real" caller ID will pop-up on the screen, I press the pause button, press select to clear the pop-up, answer the phone and after the call I hang up the phone and resume the program.

    Now when I check my caller-ID log I find the "real" caller ID and a "Name Unavailable" entry in the log, both with the exact same time/date stamps. The "Name Unavailable" entry never popped up on my screen, but is stored back-to-back with the actual caller ID.

    Seems like if you pause the receiver while the phone is still ringing I get two entries in the log...if I answer the phone without pausing the receiver only the "real" caller ID is stored....strange, but it is real...
     
  11. TulsaOK

    TulsaOK New Member

    3,469
    0
    Feb 23, 2004
    I got a call today from Ooma; not sure if it was a technical support person or not as she was rather vague as to her function. I explained the issue I had been reporting and she didn't seem to think it was an Ooma issue. I further explained that it only happened on the Telo and not the Hub and perhaps Engineering could determine what the difference in the two units might be. She told me if I wanted that feature to work I should buy the Hub. I politely thanked her and ended the conversation. I don't see this issue getting much traction with Ooma. I was rather disappointed in the response.
    I'm still convinced it's an Ooma issue.
    I also notice, on a separate issue, that the 722k does not recognize incoming calls on my second line.
     
  12. harsh

    harsh Beware the Attack Basset

    22,708
    425
    Jun 14, 2003
    Salem, OR
    Does the service/device support CID on line 2?

    IIRC, some of the "free second line" offerings don't support incoming calls on the second line and you're forced to use call waiting on line 1.
     

Share This Page

spam firewall

Advertisements