I just got a robocall that crashes my AT&T 1740 answering machine by *apparently* having gotten Telo 2 to transmit a CallerID "telephone number" that the machine can't handle. Whenever the machine tries to read back that stored "number", it crashes and requires a power cycle. I was finally able to exit the crash loop by immediately following a power cycle with a toggling of the "save caller number" setting, which thankfully deleted the foul "number".
Could just have been a glitch or answering machine bug, but seems like it might be a good idea for an Ooma coder to review the Telo 2 CallerID code line by line and make absolutely sure it has all the data/type-checking necessary to guarantee it can only transmit valid CallerID telephone numbers. Just in case.