I have a question to pass by you guys. I have an Obi200 connected to a Panasonic Dect 6 multi-phone / answering machine system. I'm on FW version 3.1.1.5577. I noticed that recently after upgrading the fw, my answering machine will pick up correctly after 4 rings, but after playing the greeting, just beeps (single beep, 2-3 second delay, repeat) and will not let the caller leave a message.
Do you think this has anything to do with the latest firmware, or is it just a strange coincidence? I've had Obi for more than a year and the phone system for longer than that. I never had any issues before this version. I upgraded from v3.1.1.5463EX. Just wondering if the Obi needs to somehow sense the greeting is complete before the line is release to the caller to leave a message.
I think your idea of how an answering machine works does not accord with reality.
There is no "release" or any other action that the Obi needs to do between the answering machine playing the greeting and it starting to record.
My first guess is that it is nothing to do with the OBi but that the memory of your answering machine is full. Whatever, your first course of action should be to read the manual for the Panasonic phone. That should inform you what the repeating beep means.
Well, I did some further testing this evening with different versions of the firmware. I mentioned in my previous note that everything was working fine with 5463EX before I upgraded to 5577. So I reinstalled 5463EX and low and behold the answering machine started working fine again.
So I reinstalled 5577 just to test and it stopped working again. I tried the latest 5589 and that did not work. So I started working backwards from 5577 to 5562, and 5562 did not work. I then tried 5491 and that worked fine. So something broke after 5491, at least as far as the interaction of the firmware and my answering machine.
I guess I'll stick with 5491 until there is a later version after 5589 that fixes the issue. Is there a formal channel for me to report the issue to Obihai for them to address?
I see that there was a new firmware release, 5657. I tested this version and and my answering machine will still not accept new messages after playing the greeting. The last good working version was 5491. Maybe someone at Obi Support could take a look to see what changed after that version that may be the root cause of the issue.
Anyone else still using an "old school" answering machine that's having the same problem? My wife still likes just walking in the door and looking at the message waiting light on the phone when there's a message.
What DrGeoff said. This has nothing to do with your OBi. As far as the OBi is concerned, someone or something answered the call. It finished its job. From there on, it is just a telephone conversation. The answering machine is "talking" to the caller.
If this is a "spousal approval factor" issue, then switch to a SIP VoIP ITSP that has its own voicemail server, which supports VMWI and MWI (the blinking light, and the stutter tone), and get rid of the answering machine.
Thanks for the replies. I'm am struggling with the assessment that the issue doesn't have anything to do with the Obi. I can directly correlate the issue to the firmware release version. Recent releases up to and including 5491 worked fine, meaning the greeting plays fine and the callers can leave messages. Releases after 5491 and up to and including 5657 don't work, meaning the greeting plays fine but the callers cannot leave messages. As soon as I revert back to 5491 from any release after 5491, messages can be received without issue.
I wonder if the issue has something to do with the Obi detecting an end of call, or treating it like a fax call. The intermittent tone that I hear after the greeting is played sounds like one a fax machine would play while it waits for the fax on the other end to start the communication link. Looking through the admin guide, I see there are some line settings that detect end of calls, eg. DetectCPC, DetectDisconnectTone, etc. I might try turning some of these on/off to see if they make a difference.
Correlation is not causation.
We've already explained that, as far as the OBi is concerned, someone or something answered the call. Turn off the answering machine. Call the number from some other phone and let it ring at least 4 times. Answer the call yourself. Can you have a two-way conversation with the other party? If so, then there is nothing wrong with the OBi settings.
If you let the answering machine grab the call, then whatever happens after that is up to the answering machine that answered that call. If the answering machine can't do its job, then either fix the answering machine (go find out exactly what those beeps mean), or get rid of that 1980s technology and use voicemail.
You are correct, causation and correlation are different. Upgrading to firmware to 5562 causes a tone to be played on the line and prevents callers from leaving messages. I noticed in WelshPaul's release notes for 5562 here: https://www.ukvoipforums.com/viewtopic.php?f=25&t=987 a new feature added called "FaxDetectionMethod now supports CNG or V.21 preamble". It seems that the fax detection method was changed in that release. I suspect that's what is causing the issue.
If you would consider another question, is there a way to disable fax detection in the Obi settings? I don't ever expect to receive faxes through the Obi ATA since I don't have a fax machine. If there was a way to disable fax detection altogether, I could try that to see if it makes a difference. Thanks again for your help.
WHY won't you perform the diagnostic test I described?
If the caller does, in fact, hear a 0.5 second, 1100Hz tone, followed by 3 seconds of silence, followed by another tone, , and so on, then that is the fax CNG tone sent by the device that is placing the call to the OBi's phone number. It is telling the caller that a fax machine is calling. Then, the fax machine emits the ANS tone, at 2100Hz. I seriously doubt that your Panasonic phone/answering device would emit those tones.
It would cause havoc. You have some sort of fax machine connected to the same telephone line as the Panasonic phones. It could be a HP, Canon, Epson or Brother all-in-one, or an actual fax machine, or even a PC with a fax modem.
Enter 1100 and 2100 into this website to hear the tones: http://onlinetonegenerator.com/ (http://onlinetonegenerator.com/)
Find the problem. It is not inside the OBi.
Reference: http://what-when-how.com/voip/fax-and-modem-tones-basics-voip/ (http://what-when-how.com/voip/fax-and-modem-tones-basics-voip/)
Dear chilirock you saved my life, I had the same problem, I had no idea what happened, thanks to your advice to return to "5491" everything returned to normal.
I recently updated to v5695EX and I'm still having the same issue with the answering machine. In my current config, I have my Google Voice number forwarded to my CallCentric number in order to get CNAM.
I tried unchecking the call forwarding to CC and having my GV forwarded to Google Chat, i.e. picked up by the Obi200 directly. In that configuration the answering machine works as expected. When I switch the call forwarding back to my CC number, it stops working again.
I created a support ticket with CallCentric, and they weren't aware of any issues.
Update: I created a new support ticket with CallCentric when I found that the issue with the answering machine occurs with inbound calls to CallCentric, but not inbound calls to Google Voice. They had me send them the date/time stamps of a couple of calls where I had the issue.
CallCentric support was able to review the call logs from their end and determine that the reason that I am hearing the beeps is that about 30 seconds into the call (e.g. after the Obi answers the call and after the answering machine plays the outgoing message) the Obi device sent a Re-INVITE packet back to CC to re-invite the call as a T.38 fax call. This explains why I'm hearing an intermittent beep tone on the line because the Obi is trying to establish a fax connection with the inbound call.
So it looks like the theories presented here that the issue had nothing to do with the Obi device are not correct. The Obi is sending a re-INVITE packet back to CallCentric after the call has been answered. All calls I have tested are coming in from a standard mobile phone, not from a fax machine.
The CallCentric support team was not able to determine why the re-INVITE message is being sent, they could just confirm that it was sent from the device. They sent me a couple of suggested configuration settings to see if it would resolve the problem. After making the suggested settings (see below),
I no longer have the issue, even with the latest v5695EX firmware. The answering machine is working fine again.
If anyone is interested in trying the settings to see if it resolves the issue with your answering machine, here they are. I only had to change a couple of these as a couple of them were already set the way they suggested. Based on the suggested settings, I'm guessing that the fax capability will no longer work. For me that's not an issue as I never use the line for faxes. But it may be an issue for others, so fair warning.
---Codec Profile A & B---
FAX Event Section
- Enable: unchecked (mine was already unchecked)
Codec Settings Section
- T38Enable: Unchecked (mine was checked)
- T38Redundancy: 0 (mine was set to 2)
---ITSP Profile X (The Callcentric one eg. ITSP B)---
SIP Sub-section
- X_SessionRefresh: Unchecked (mine was already unchecked)
- X_FaxPassThroughSignal: None (mine was set to ReINVITE)
What I still need to determine is "why" the Obi is sending the packet trying to re-establish the call as a fax. I will try creating a support ticket with Obihai to see if they can determine what might have changed in the recent firmware versions that is causing the issue. I'll post here again if I find anything new.
Update: 11/08/17: Since this post is getting referenced many times now, I figured I would provide an update based on the most recent v5757EX firmware experience. With the recent Google Voice backing off issues, I installed the v5757EX firmware and performed a factory reset. After the factory reset and fresh new configuration I tested my answering machine. The fax Re-INVITE issue is still there. Changing the following one setting corrected the issue. I didn't need to change all of the settings I listed above.
---Codec Profile A & B---
Codec Settings Section
- T38Enable: Unchecked (mine was checked)
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.
Update: 03/30/18: I wanted to close the loop on this issue by providing another update. Obi Support has resolved the answering machine issue with a firmware update. They pushed a beta version (v5801) to my Obi200 that included the fix. I confirmed that after reverting back all changes, including the most recent T38Reinvite setting above, the answering machine was functioning properly with the new beta firmware.
After testing the beta firmware for more than 8 weeks without issue, I updated my Obi200 device using the generally available firmware v5804. I've been using v5804 for three days without issue. All firmware versions including v5804 and after should include the fix. The following is an excerpt from the v5804 release notes:
- Some answering machines emit a beep of around 1100Hz lasting 0.5 seconds. This resembles one cycle of the fax CNG tone, triggering the OBi to switch to fax mode. If T.38 is enabled, this might cause the call to drop
So just to clarify, after applying firmware v5804 (or later), you can revert back all previously recommended settings listed above in this post to their factory defaults and the answering machine should just work.
Quote from: chilirock on August 07, 2017, 07:20:34 PM
Update: I created a new support ticket with CallCentric when I found that the issue with the answering machine occurs with inbound calls to CallCentric, but not inbound calls to Google Voice. They had me send them the date/time stamps of a couple of calls where I had the issue.
CallCentric support was able to review the call logs from their end and determine that the reason that I am hearing the beeps is that about 30 seconds into the call (e.g. after the Obi answers the call and after the answering machine plays the outgoing message) the Obi device sent a Re-INVITE packet back to CC to re-invite the call as a T.38 fax call. This explains why I'm hearing an intermittent beep tone on the line because the Obi is trying to establish a fax connection with the inbound call.
So it looks like the theories presented here that the issue had nothing to do with the Obi device are not correct. The Obi is sending a re-INVITE packet back to CallCentric after the call has been answered. All calls I have tested are coming in from a standard mobile phone, not from a fax machine.
The CallCentric support team was not able to determine why the re-INVITE message is being sent, they could just confirm that it was sent from the device. They sent me a couple of suggested configuration settings to see if it would resolve the problem. After making the suggested settings (see below), I no longer have the issue, even with the latest v5695EX firmware. The answering machine is working fine again.
If anyone is interested in trying the settings to see if it resolves the issue with your answering machine, here they are. I only had to change a couple of these as a couple of them were already set the way they suggested. Based on the suggested settings, I'm guessing that the fax capability will no longer work. For me that's not an issue as I never use the line for faxes. But it may be an issue for others, so fair warning.
---Codec Profile A & B---
FAX Event Section
- Enable: unchecked (mine was already unchecked)
Codec Settings Section
- T38Enable: Unchecked (mine was checked)
- T38Redundancy: 0 (mine was set to 2)
---ITSP Profile X (The Callcentric one eg. ITSP B)---
SIP Sub-section
- X_SessionRefresh: Unchecked (mine was already unchecked)
- X_FaxPassThroughSignal: None (mine was set to ReINVITE)
What I still need to determine is "why" the Obi is sending the packet trying to re-establish the call as a fax. I will try creating a support ticket with Obihai to see if they can determine what might have changed in the recent firmware versions that is causing the issue. I'll post here again if I find anything new.
I had the same situation, but the issue appeared only like 2 weeks ago without doing any changes. Everything was good before.
Solution provided works and now my answering records messages again.
Thank you for providing this solution.
Thank you, chilirock!
I had the same problem, only I'm using the PhonePower service.
I really appreciate that you took the time to post the solution. It is a big help. I also appreciate your calmness above as other posters were completely disregarding your experience in favor of their own incorrect guesses. Nice job.
Have a great day, and thanks again!
Steven
Thank you too, chilrock. This solution works. OBIhai owes you an apology, and an update to firmware to fix this problem. There response was obviously wrong - something changed in their firmware.
Thank You Guys. I Had received a replacement Obi 200 and after that my Panasonic answering machine stopped working. I put in a very old Panasonic answering machine and it worked fine, so i thought there was an issue with the phone. I returned the phone to Panasonic under warranty, (I had to pay 1 way shipping), and they sent me a new one with 2 additional handsets. But it had the same problem. I have a theory that the exact answer tone on this model is triggering a fax response.
This solution, to change the setting worked. But interestingly enough I was trying to see which one's were important, bec i use fax sometimes, and I ended up putting all the settings back to default and it still works. ???
Chilirock,
The recommended changes did not solve my issue. Do you by chance have the other options that were suggested by your voice provider?
Thanks - Eric
erichadssorensen,
Sorry to hear that the changes didn't resolve your issue. Can you tell me which changes specifically that you tried? Did you try reverting back to firmware v5491(http://fw.obihai.com/OBi202-3-1-1-5491.fw) to see if that resolves the issue? Or did you try changing the codec setttings using the latest firmware v5695EX?
If the older firmware works, you can try flashing to the latest firmware, then performing a factory reset on the Obi, then configuring the Obi from scratch, and finally making the codec settings to disable T.38 fax. That's what I did on my Obi200 device. BTW, what Obi device and answering machine are you using? If you post these, others might be able to weigh in on what worked for them.
Hi Chilirock,
I've got an OBI200 and currently a Panasonic Dect6.0 (KX-TG572) phone. I had an AT&T phone and tried replacing it thinking it may be the culprit. The fax sound occurs when the answering maching/phone answers on the 4th ring. If I set it to pickup on the 2nd or 3rd ring it's fine. So, I first tried updating the Codec and SIP changes with the OBI having the most recent firmware. No Luck.
I then reverted back to firmware 3.1.1 (Build: 5491) and tried again though I didn't default all the settings for Codec/SIP. Still no luck.
Thoughts anyone?
erichadssorensen,
I'm no sure why reverting back to the older firmware didn't help. My only thought is that when you revert back to older firmware, that the Obi may be trying to map the current settings to the older firmware. If you want to try to reproduce my results, first upgrade to the latest, then perform a factory reset and start the config again like you did when it was new.
Who is your service provider? When I was testing various combinations I tried calling my Google Voice number directly without having it forwarded to CallCentric. When I did this, I didn't have the issue. It was only with my Google Voice number forwarded to my CallCentric number that I had the issue.
Hi Chilirock,
So I did a factory reset and rebuilt everything. No difference. Same fax sound. I have Google Voice. It sounds fax machine on 4th ring. Any answering machine or manual pickup before the 4th ring. No problemo!
I can't figure it out!!! Uggg
Quote from: chilirock on August 07, 2017, 07:20:34 PM
Update: I created a new support ticket with CallCentric when I found that the issue with the answering machine occurs with inbound calls to CallCentric, but not inbound calls to Google Voice. They had me send them the date/time stamps of a couple of calls where I had the issue.
CallCentric support was able to review the call logs from their end and determine that the reason that I am hearing the beeps is that about 30 seconds into the call (e.g. after the Obi answers the call and after the answering machine plays the outgoing message) the Obi device sent a Re-INVITE packet back to CC to re-invite the call as a T.38 fax call. This explains why I'm hearing an intermittent beep tone on the line because the Obi is trying to establish a fax connection with the inbound call.
So it looks like the theories presented here that the issue had nothing to do with the Obi device are not correct. The Obi is sending a re-INVITE packet back to CallCentric after the call has been answered. All calls I have tested are coming in from a standard mobile phone, not from a fax machine.
The CallCentric support team was not able to determine why the re-INVITE message is being sent, they could just confirm that it was sent from the device. They sent me a couple of suggested configuration settings to see if it would resolve the problem. After making the suggested settings (see below), I no longer have the issue, even with the latest v5695EX firmware. The answering machine is working fine again.
If anyone is interested in trying the settings to see if it resolves the issue with your answering machine, here they are. I only had to change a couple of these as a couple of them were already set the way they suggested. Based on the suggested settings, I'm guessing that the fax capability will no longer work. For me that's not an issue as I never use the line for faxes. But it may be an issue for others, so fair warning.
---Codec Profile A & B---
FAX Event Section
- Enable: unchecked (mine was already unchecked)
Codec Settings Section
- T38Enable: Unchecked (mine was checked)
- T38Redundancy: 0 (mine was set to 2)
---ITSP Profile X (The Callcentric one eg. ITSP B)---
SIP Sub-section
- X_SessionRefresh: Unchecked (mine was already unchecked)
- X_FaxPassThroughSignal: None (mine was set to ReINVITE)
What I still need to determine is "why" the Obi is sending the packet trying to re-establish the call as a fax. I will try creating a support ticket with Obihai to see if they can determine what might have changed in the recent firmware versions that is causing the issue. I'll post here again if I find anything new.
I normally don't post on forums, but I had to get on and send a
BIG thanks to chilirock. I have the exact same setup as you, with Callcentric taking in Inbound calls for CNAME and a Dect.6.0 Panasonic phone with an answering machine. The setup was for my elderly parents, who rely on the old school answering machine. I spent several days trying different solutions, and I was about to throw in the towel and just get a new phone until I came across this thread.
LIFE SAVER
Hi
I just received my Obi200 and am having the same problem you mentioned. I also have a Panasonic DECT 6.0 phone/answering machine.
My firmware is 5735EX.
I want to hook up my FAX machine so I do not want to change settings on the Obi.
Have you any luck besides making the changes that you posted? It might be time for a new answering phone system.
PS: After the changes you posted, all is working great!
Thanks again !!!!!!!!!!!!!!
Hi Chilirock:
Thanks for helping me out. I had an Obihai 110 with Phone Power as servicer and the Panasonic Phone/Answering machine TX-TG6531 working for a couple years without an issue. I just upgraded to an Obi202 and immediately after the upgrade I had the same Beep problem with the Phone/Answering machine. I did a Google Search and found this post. I made the config changes you received from Callcentric and everything works - no Beeping. Thanks for being persistent and sharing your solution.
Chilirock, thank you for posting your experience. I had the same problem using an Obi202, with Phone Power and a Panasonic answering machine, after upgrading to firmware version 5757. I unchecked the T38Enable setting in the Codec Settings Section, as you described, and my answering machine is working again.
Thank you so much.
Quote from: Mooselord on November 11, 2017, 07:08:13 AM
Chilirock, thank you for posting your experience. I had the same problem using an Obi202, with Phone Power and a Panasonic answering machine, after upgrading to firmware version 5757. I unchecked the T38Enable setting in the Codec Settings Section, as you described, and my answering machine is working again.
I also want to thank Chilirock (and Callcentric) for persevering and finding out the solution to this problem. Exact same thing happened to me. Bought a Panasonic DECT 6 "amplified" phone with answering machine for my elderly father. When trying to leave a message the caller would just hear fax tones and nothing was recorded.
Unchecking T38Enable fixed the problem. I would have never figured this out on my own. Sure glad I read this thread.
This is definitely a bug in the firmware.
Thank you Chilirock, the issue is fixed for me as well. You rock!
HUGE thank you to chilirock!!!
I have a Obi202 connected to a Panasonic Dect 6.0 phone answering system. Unfortunately didn't find this thread until after I disposed of my previous Panasonic phone system (after much testing trying to solve the issue, including using my google voice number with no issues). I replaced it with a new Panasonic answering system which has the exact same issue (Caller calls, answering machine picks up, the greeting plays, and then beeping like a fax machine ensues. Caller is unable to leave a message.) I have Phone Power as my VOIP, and my firmware version is 5757EX.
After making the suggested change:
---Codec Profile A & B---
Codec Settings Section
- T38Enable: Unchecked (mine was checked)
NO MORE BEEPING and callers are able to leave a message! Again thank you chilirock, and shame on those of you who gave him/her a hard time, weren't even willing to listen and resorted to making fun of someone who wanted an answering system, regardless of their reasons.
Fax initiation tones after beep after greeting message. Old ATT answering machine and new VTech.
Worked for almost two years, then two weeks ago FAX beeps started
Obi200, build 5757EX accessed through its IP address on my LAN
Codecs
T38 Enable at bottom of codec profiles
Codec Profile A, T38Enable, Uncheck default, uncheck enable
Submit, OK
Codec Profile B, T38Enable, Uncheck default, uncheck enable
Submit, OK
Reboot - no more beeps, answering system works
Re-enabled T38 in both codec profiles, FAX beeps back. Disabled again.
Fix per Chilirock - thank you!
chillirock, huge thanks for getting to the bottom of this, unchecking the T38Enable setting did the trick.
AWESOME Chilirock...you rock! I've been banging my head against the wall, even bought a new Panasonic phone (as their tech support was useless and rude). A PhonePower rep actually suggested to me that it might be the fax signal triggering which caused me to google and find your post. Most of my setting were already defaulted to the settings you describe, but the last one about the re-invite seems to be the ticket for me (with PhonePower and a Panasonic phone). New phone being returned and you just saved me a 100 bucks!
Thanks for not listening to the others, your troubleshooting was sound and you stayed the course to find a solution.
Much appreciated!
Dear chilirock,
You are indeed the BEST! My friend and I have searched all over the net looking for a solution - we have 3 different sets of phones experiencing this very frustrating issue! We have even bought a new set of phones thinking the voicemail unit on the phone was wonky, but it didn't fix the problem.
Very thankful you've detailed this and how to get the voicemail to work again. Can the techs at Obihai PLEASE read this and fix this codec ???
Kudos to you chilirock. Thank you so much!
I have been having the same problem and assumed it was my phone, as I haven't changed anything. I bought a new Panasonic cordless phone and the problem still persists. I just made the Codec changes and it seems to be working.
Thanks!
Good going chilirock! I thought this didn't solve my problem, but I forgot to change both the A and B caller profiles. Your repeated updates months later is a thing to admire, my friend. Thanks so much for not recreating this scenario for me! https://xkcd.com/979/
Was having the same problem on my call centric line, disabled the T38Enable and it fixed it...
Thanks so much!!! :)
Thank to chilirock I was at wit's end trying to figure out why my panasonic phone answering machine record only beeping sound.
unchecking both
Codec Profile A, T38Enable,
Codec Profile B, T38Enable
does the trick !
Thanks chilirock!!!!
My answering machine started recording beeps and it was driving me crazy. Definitely firmware issue!!! >:(
Thanks again!
PS. We should make it sticky with reference to Panasonic systems!
Hi All,
I've been exchanging emails recently with Obi Support. I have made an update to my previous post modifying the recommended settings based on input from Obi Support. Let me know if you have any questions.
http://www.obitalk.com/forum/index.php?topic=12530.msg82522#msg82522
My OBihai died after 3 years. :-\ My new ObiHai200 with Build 5794EX sent FAX tones and broker my Panasonic Dect 6.0 ability to record messages. ???
Altering T38Reinvite to: "Callee only" fixed it. ;D Apparently ignores the Panasonic tone now.
Solve for me with 3.2.1 5794EX and Panasonic DECT 6.0 by changing to "Callee Only".
Good job tracking down the problem!
Quote from: chilirock on March 18, 2017, 10:06:14 AM
I have a question to pass by you guys. I have an Obi200 connected to a Panasonic Dect 6 multi-phone / answering machine system. I'm on FW version 3.1.1.5577. I noticed that recently after upgrading the fw, my answering machine will pick up correctly after 4 rings, but after playing the greeting, just beeps (single beep, 2-3 second delay, repeat) and will not let the caller leave a message.
Do you think this has anything to do with the latest firmware, or is it just a strange coincidence? I've had Obi for more than a year and the phone system for longer than that. I never had any issues before this version. I upgraded from v3.1.1.5463EX. Just wondering if the Obi needs to somehow sense the greeting is complete before the line is release to the caller to leave a message.
I have this exact same problem. Panasonic 6 handsets, with answering machine on Panasonic turned on, with Phone Power and Google Voice, and Obi 202.
When the answering machine answers it plays the recording...people hear it. Then when it tells them to leave a message after the beep...I hear what sounds like regular tones through out the house...like a fax machine.
Quote from: Matthew999 on February 13, 2018, 09:57:46 AM
I have this exact same problem.
QuoteThe 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")
http://www.obitalk.com/forum/index.php?topic=12530.msg82522#msg82522 (http://www.obitalk.com/forum/index.php?topic=12530.msg82522#msg82522)
Quote from: chilirock on August 07, 2017, 07:20:34 PM
---Codec Profile A & B---
FAX Event Section
- Enable: unchecked (mine was already unchecked)
Codec Settings Section
- T38Enable: Unchecked (mine was checked)
- T38Redundancy: 0 (mine was set to 2)
- T38Reinvite: “Callee only” (mine was set to “Caller or callee”)
---ITSP Profile X (The Callcentric one eg. ITSP B)---
SIP Sub-section
- X_SessionRefresh: Unchecked (mine was already unchecked)
- X_FaxPassThroughSignal: None (mine was set to ReINVITE)
...
I know that this thread is a little old, but I wanted to thank you Chilirock for your efforts. This fixed my phone answering machine issue too (like many others here).
Thanks so much Chilirock!! This issue was driving me crazy for months. This should really be posted to the top of the forums!
Hello ladies and Gents, i was facing the same issue as you and i have found a fix!!
underExpert Config -> Voice Services -> Auto Attendant -> Auto Attendant 1 -> Disable
Cheers!! ;)
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.
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.
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.
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.
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.
The issue that prompted me to create the original post in this thread has been resolved by Obi Support. I've posted another update to my Obi configuration settings message updating the guidance for resolving this issue. You can find the updated post here: http://www.obitalk.com/forum/index.php?topic=12530.msg82522#msg82522
Thanks Chillirock! 😀
I know this is an old post,but Just had the same problem today, glad I found this post.
Changing T38reinvite worked for my Panasonic answering machine too !