Question: Standard Answering Machine Not Allowing For Messages After Greeting
Martnel:
Thank you, Chilirock! I had the same issue crop up recently and finally thought of searching the Obitalk Forum. This setting from your 1/28/2018 update solved the issue for me. I really appreciate the amount of effort you put into following up on this!
Quote from: chilirock on August 07, 2017, 07:20:34 pm
Update: 01/28/18: I have more to share based on recent discussion with Obi Support on this issue. The following is a quote from Obi Support… “the answering machine is sending a tone that the OBi misconstrued to be the fax CNG tone. In older firmware, the OBi reacts to fax answering tone (CED) but not the fax originating tone (CNG)”. They confirmed that the issue started with firmware v5562 and a change to the fax detection method.
The Obi Support team is currently working on a solution they hope will resolve this issue. In the meantime, they recommended changing the following setting:
---Codec Profile A & B---
Codec Setting Section:
- T38Reinvite: “Callee only” (mine was set to “Caller or callee”)
Obi indicated that this setting is a “more correct, common-practice setting”. The “Caller or callee” setting is there for backward compatibility. I can confirm that changing this one setting, my answering machine works properly.
I reverted the T38Enable setting back to “Checked” (from Unchecked) thus re-enabling the T38 fax codec. Even with the T38 codec re-enabled, the change to the T38Reinvite setting allows the answering machine to work properly. I will let everyone know when/if this issue is resolved with a firmware update.
tsak:
thank you chilirock, same problem. My father actually got rid of his old machine thinking it was broken. The new panasonic machine had the same beeping issue. Thank you for following through and dealing with the others who thought you were an idiot. The follow ups were terrific too.
jellyfish:
I just upgraded an old obi110 to obi200 and immediately had this same problem; guess Obihai hasn't made any fixes yet.
Thanks for the fix and followups, Chillirock! changing T38reinvite worked like a charm.
tsak:
The only way to do this mod is by logging into the Obitalk locally via the web interface. I tried doing it remotely by changing the Codex XML file in the advanced user dashboard of Obitalk, but it isn't the same as the Obitalk Web Interface. The options aren't the same and it doesn't seem to save after you try to restore the settings, so save yourself the trouble.
I attached the last known working firmware version if anyone wanted to simply revert their firmware. Note: The Obitalk maybe autoupdate if a newer firmware is released.
Eastwood77:
Quote from: tsak on March 14, 2018, 11:00:07 am
The only way to do this mod is by logging into the Obitalk locally via the web interface...
Makes no sense. Did you mean login to Obi200 device locally?
That will fail as ObiHai is overwritten by ObiTALK config. From Obihai:
Quote
Please be advice, any changes within the OBi200 device local web-portal will automatically be over-write by the OBiTALK configurations. Always apply changes and updates within the OBiTALK portal for the OBi Expert Configuration portal (to lock changes), for the OBi Expert Configuration page. Log into your OBiTALK account at www.obitalk.com:
Click OBi number 510700665 for Device Configuration page
Click the OBi Expert Configuration blue button
Click OK
Click Enter OBi Expert blue button
And make your updates/changes.
Navigation
[0] Message Index
[#] Next page
[*] Previous page