The number you dialed___ has not received a response from the service provider

<< < (3/16) > >>

gpslouis:
Quote from: bitstopjoe on January 17, 2019, 11:21:28 am

Quote from: Revived on January 17, 2019, 08:49:38 am

Any insight on why I'm hearing this the last few days? Rebooting my 200 using ***9 fixes it temporarily but it reverted back today.


 WOW I thought it was just me!! Sometimes a soft reboot fixes it for me, other times I have to pull the power plug, count to 10, and put it back in. I can make 2 calls in a row, no problem, hang up and try making another call and I get same no response error.
 Mine started earlier this week, but seems real bad today.
 Hopefully, someone here has some insight. If you find a fix, please post here.

 Thank you

Joe Sica



I'm seeing the EXACT same problem.  For what it's worth, I tried changing the DNS to 8.8.8.8 and 8.8.4.4 as another person had suggested, but that didn't help. 

ymcp:
me too google voice with optimum online internet

ljneureu:
This has happened to me a couple times in the past two weeks at only one of three sites (SITE 1 below).  The same GV number is set up to ring at all three sites.  All three sites use an Obi202.  All three sites are with Comcast as the service provider.  They use different cable modems/gateways or routers so perhaps that is where the difference lies.  Site 1 has the oldest equipment: 
  
1 Obi202, Comcast, Comcast Gateway (Netgear CG3000DCR) & router Cisco RV 180W
2 Obi202, Comcast, Comcast Wireless Gateway (Cisco DPC3941B)
3 Obi202, Comcast, Cable Modem (ARRIS SURFoard SB8200)



I will try changing the DNS to 8.8.8.8 and 8.8.4.4 as suggested by Zorlac above.

madhatter:
I am trying the following:

changing the DNS to 8.8.8.8 / 8.8.4.4
put the Obi on the DMZ

Obi support suggested:  Please try opening certain ports within your router for traffic flowing:  https://www.obitalk.com/info/faq/Troubleshooting-sec/ports-to-keep-open-on-my-router

ansh:
Having the same issue for the past week or 2. Using Obi200 with Google Voice. Restarting the device helps temporarily, but the problem occurs. Any help? Has changing port fix it? Exact instructions on how to do it?

Thanks!

Navigation

[0] Message Index

[#] Next page

[*] Previous page