Answering machine records 30 seconds of dialtone
This is incredibly annoying and will eventually lead me to getting rid of Ooma altogether. Every time my answering machine records a call it doesn't recognize when the call ends, thusly it always records crap loads of dialtone.
In searching online I've seen several references to the "disconnect timeout" being the issue. I guess Ooma isn't allowing enough 'dead time' before starting a new dialtone after a call ends.
How can I increase this timeout? There are references to people increasing this timeout themselves but that was from posts dated a couple years ago, this ability seems to have been removed (as has every other useful feature it seems).
Quite frankly, we should be able to disable this behavior altogether. It should just cut the connection after the other party hangs up and not be able to start a new call until after my answering machine ALSO hangs up.
In searching online I've seen several references to the "disconnect timeout" being the issue. I guess Ooma isn't allowing enough 'dead time' before starting a new dialtone after a call ends.
How can I increase this timeout? There are references to people increasing this timeout themselves but that was from posts dated a couple years ago, this ability seems to have been removed (as has every other useful feature it seems).
Quite frankly, we should be able to disable this behavior altogether. It should just cut the connection after the other party hangs up and not be able to start a new call until after my answering machine ALSO hangs up.
Re: Answering machine records 30 seconds of dialtone
viewtopic.php?f=10&t=19714 ' Fix issue where a remote hangup triggers a flash on the line'. This fix disables 'Answering Machine Hangup' on telo2, but it can be re-enabled upon request. Just chat/call support and ask them to enable it in the customer config. Have done so for your account.
The only drawback is that the bug mentioned will return. For some this is not an issue though, so it's a tradeoff between one or the other. A final fix for this issue will be in the next release.
The only drawback is that the bug mentioned will return. For some this is not an issue though, so it's a tradeoff between one or the other. A final fix for this issue will be in the next release.
Re: Answering machine records 30 seconds of dialtone
Apotheosis, change applied.
Re: Answering machine records 30 seconds of dialtone
tomfox, change applied.
Re: Answering machine records 30 seconds of dialtone
lesh8210, change applied.
Re: Answering machine records 30 seconds of dialtone
Hello Tom B,
Recently went to Ooma Premier service and using two phone lines connected to my Panasonic Base/Answering machine.
I am noticing similar relating to messages left and 30 seconds of dial tone.
My Ooma Telo is on firmware version #156394.
Can you please help?
Recently went to Ooma Premier service and using two phone lines connected to my Panasonic Base/Answering machine.
I am noticing similar relating to messages left and 30 seconds of dial tone.
My Ooma Telo is on firmware version #156394.
Can you please help?
Pete
Automator
Automator
Re: Answering machine records 30 seconds of dialtone
Currently on a telo1 the disconnect param is not configurable. It's fixed at 650ms which works for most answering machines. Configure option will be available in the next release.
Re: Answering machine records 30 seconds of dialtone
Thank you Tom B.
I look forward to the next release of firmware.
I look forward to the next release of firmware.
Pete
Automator
Automator
Re: Answering machine records 30 seconds of dialtone
Hello Tom B,
I am also experiencing this issue. You can hear the dial tone for 10 seconds after the person calling hangs up. I have a GE phone with a built answering machine. I tried contacting chat support and they were unable to help. Also, when can we expect to see the next release?
Can you please help?
I am also experiencing this issue. You can hear the dial tone for 10 seconds after the person calling hangs up. I have a GE phone with a built answering machine. I tried contacting chat support and they were unable to help. Also, when can we expect to see the next release?
Can you please help?