"Pressing one" issue

[rufuqobu]

Installed an OBi200 today, connected it to GV and it appears to work fine.
finally there is a tube where you can find porn with big tits beauties absolutely free https://bigtitstube.xxx/
However, I cannot use the Call Screening feature: pressing 1 on an incoming call does nothing.

[drgeoff]

Installed an OBi200 today, connected it to GV and it appears to work fine.
However, I cannot use the Call Screening feature: pressing 1 on an incoming call does nothing.

Please clarify.  Which of:

1.  You have enabled Call Screening in your settings at voice.google.com but pressing 1 on the phone plugged in to your OBi does nothing.

2.  You have not enabled Call Screening at voice.google.com so pressing 1 does nothing.

[RAMOSEL]

Since this thread is already started...

Starlink Internet
Netgate SG-4860
pfSense 21.05.1
Running the OBI202 in it's own DMZ, only device
OBI 3.2.2 (Build: 8680EX)
Using various handset in the house but primary is Panasonic KX-TGF383

Call screening on Google Voice is enabled, house handset rings with full caller ID.  Handset picks up call. Google Voice announces caller and instructs you to press 1.  Press 1, audibly hear tone for 1 being pushed. Nothing happens, no acknowledgement of the key push for 1.  recorded Google Voice message continues.  Try option 2, no response.
Try other handsets in house.  Same result.

[drgeoff]

Under the appropriate Service Providers, ITSP Profile, General if DTMFMethod is not set to Inband try changing to that.

[SteveInWA]

Sign into your OBiTALK dashboard:  http://www.obitalk.com/obinet/pg/obhdev

Look at the list of devices.  I assume you will see your OBi device.  If its list of SP1-- SP4 is not shown, click "expand" at the far right.  You should now see the list of SPs, and you should see your Google Voice number with a status of "Connected".

Click the device name, and it should take you to the device's main configuration page.  Click "OBi Expert Configuration", and click through the various confirmations to get into expert mode.  Once there, assuming Google Voice is on SP1, click "Service Providers"-->"ITSP Profile A General".  Look at the parameter "DTMFMethod".  It should be set to "Auto".  If not, un-check BOTH check boxes to the far right and select "Auto", then scroll down and save your settings.  Test the ability of Google Voice to recognize pressing 1.

If it still doesn't work, then go back to that setting and change it to "InBand", save your settings, and repeat the test.  Does it work now?

[RAMOSEL]

No, does not work.
Was in "Inband" mode when I found it.   Changed to Auto, saved and waited for the system to reset.  Confirmed in "Auto" mode.

Now inbound call rings on handset.  When you answer, nothing.  No google voice announcing press 1 or press 2.

Calling phone continues to ring.

Put it back in "Inband" and it reverted to google voice announcing caller and requesting to press 1 or 2 and again it just ignores input from handset.

Anything else to try?

Edit:  Just FYI:
looking at your picture:  Your signaling protocol shows SIP, mine is Google Voice
I have a StunServer as  stun.l.google.com
I have X_STUNServerPort at 19302
DigitMap is different as well

[SteveInWA]

My screenshot was actually from a different service provider, Callcentric, so it looks different.  But the DTMF setting is the same.

I don't know what you've done to mess up your configuration.  Rather than try to remotely troubleshoot it, it would be faster if you'd reset everything and start over.

See my instructions, here:  http://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076

[RAMOSEL]

Awesome, thank you!
I'll give it a try.

[RAMOSEL]

See my instructions, here:  http://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076

Thanks Steve.   Still the same issue.  Work-around for now is to turn off "Screen calls" under google voice.  Then it works both directions.

But...   now I can't access unit locally via its IP address.   That was working fine.   
"The requested URL was not found!"
used the *** , 1 to retrieve the IP and this matches my DHCP server stats.
I can ping it with a return time<1ms

[SteveInWA]

What the heck.

Is this an OBi 200 or 202?  If it's a 202, the recent firmware update disabled local access via the device's WAN port, and you need to re-enable it:  pick up the phone and key in *** then 0 then 30# then 1 then 1# to enable WAN access.

[SteveInWA]

OH, and do you understand that you must make the changes via the OBiTALK portal, and not via the local web UI?  Changes made on the web UI will be overwritten by the portal next time the devices reboots.

[RAMOSEL]

What the heck.

Is this an OBi 200 or 202?  If it's a 202, the recent firmware update disabled local access via the device's WAN port, and you need to re-enable it:  pick up the phone and key in *** then 0 then 30# then 1 then 1# to enable WAN access.

It's a 202

Hmmm... I guess it survived the update, just not the reset.

Done, fixed...

Any other gotchas from the firmware update?

[RAMOSEL]

OH, and do you understand that you must make the changes via the OBiTALK portal, and not via the local web UI?  Changes made on the web UI will be overwritten by the portal next time the devices reboots.

I do Sir, and thanks.
I'll live with the call screening turned off for now, I'll keep an eye on this thread and see if anyone else has the issue and a fix is found.

[RAMOSEL]

SteveInWA,

Just wanted to say thanks again for your help.  Although we didn't fix the precise issue I was having, it works.  That, and walking through your full reload process (twice) gave me a much better understanding of the workings of the interconnectivity of the Polycom/OBi 202, the Obitalk web page and Google Voice.

I felt comfortable enough in the process, I spun up the 2nd port as a my FAX line after I had Google Voice port the number over from my place holder mobile after dropping Suddenlink.

So far, so good.

Rick

[SteveInWA]

Great; I'm glad that was helpful.