OBiTALK Community

Region Specific Technical / Service Provider Support => North America - Including Google Voice, Skype, etc. => Topic started by: digitellum on December 11, 2017, 02:31:07 PM

Title: New GVGW Obi110 user gets incomming calls and only outgoing call error message?
Post by: digitellum on December 11, 2017, 02:31:07 PM
Here's a kinda weird  issue...

Signed up for Simonics GV service.
Followed the getting started tutorial on this forum.
Got to the point where the Obi Dashboard SP1 entry looks like the example.
Says SP1 is registered.
Tried an outgoing call and got a voice error message that states
device configuration error? Go to Obitalk and configure your device.
Obitalk Dash looks correct.
Then checked the internal 110 web page. That looks correct.
Tried an incoming call to the GV number and 110 rang as expected.
Voice quality from calling number was really low level and noisy.
Tried another outbound call to a known working number same config error.
How do you configure the 110 device and not kill the Google Voice account?
In other words incoming calls should be the hard part, not outgoing ones...

Any suggestions would be welcome.

Digitellum,
Scottsdale, AZ


Title: Re: New GVGW Obi110 user gets incomming calls and only outgoing call error message?
Post by: mafak on December 15, 2017, 10:40:25 PM
Just signed up with Simonics on my obi110 and having a similar problem.  Incoming is fine, out going not working.  I ring like it is working, however calls are not getting through.  Any idea?
Title: Re: New GVGW Obi110 user gets incomming calls and only outgoing call error message?
Post by: billsimon on December 16, 2017, 05:30:17 AM
One thing to check is that you are using "GV" in your user name and not "gv". In other words your user name should look like GV18005551212 and not gv18005551212.

On our gateways the registration and outgoing call authentication are handled by different processes and the registration will accept your ID in lower case. This will result in outbound failing but incoming working. So make sure the user ID is upper case everywhere you enter it.