missed 1 digit when dialing US number 252- and I got connected to Somalia(252)!
Felix:
I realize I am late to this fascinating conversation...
Quote from: CoalMinerRetired on February 05, 2013, 12:01:04 pm
> ... I didn't dial "011" in any of those 3 calls... so how did the call go through as int'l calls?
That would seem to indicate GV's international dialing rules are broken. People will be complainig it in the GV Product Forums if this is happening.
When you call from GMail or Google Talk client, you have to select a country from dropdown box (USA is the default), so the problem is specific to OBi users. I guess, it explains why people in GV forum never mentioned it!
Quote from: infin8loop on February 05, 2013, 07:07:26 pm
It's amazing that Google Voice doesn't require the 011 prefix before routing a call as international.
I tried dialing my iNum 8835100xxxxxxxx through Google Voice from the OBi110 and the call went through.
Neither does Call With Us - and I like it this way. And Betamax requires 00 instead of 011...
I set up digit map on several adapters, so that dialing 1xxx routes to GV, and dialing [2-9]xxx routes to Call With Us. Google Voice caller ID shows without 1 (just 818-xxx or similar) - so I saw similar problem in my family as well. Fortunately 81 is Japan, and 31 is Netherlands (818 and 310 are Los Angeles area codes) - every mistake costs me a cent or two, so we just laugh it off.
However, just to practice setting up digit maps, I changed CWU route to be [2-9]xxxxxxxxxx. - in other words, 11 digits or more. Both Germany and UK would qualify. If you wanted to call Somalia or other strange countries that have 10 digits including country code, you would have a problem - but fortunately, that's a topic for another day :D
lhm.:
'The call goes through when the iNum is prefixed with 011 as well. This is probably by design so Google can fleece folks that make a mistake in dialing.'
Perhaps they have a dialplan/digitmap. I know they have more cash than just about everyone else.
Rick:
Quote from: ianobi on February 05, 2013, 05:31:40 am
I like to delete any rules not being used. xx. and [^*#]@@. can cause problems as they both match any number of any digits. None of these are useful in a GV DigitMap: xx.|(Mipd)|[^*#]@@.
To allow 7,10 and 11 digit numbers and genuine international numbers to go via GV, this seems to be the best DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.)
Replace aaa with your local code.
I've now removed xx.|(Mipd)|[^*#]@@. from both my DigitMaps. Thanks Ianobi!
ianobi:
@ Rick,
Quote
Ianobi, what would you do if you wanted to prevent ANY international calls? Remove the |011xx at the end?
A few days ago I would have said yes, removing "011xx." will stop all international calls. Now there seems to be some doubt about how GV handles calls that are not eleven digits starting with "1" and do not start with "011". All I can now say is that this DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.)
Only allows you to dial 7,10 and 11 digit numbers, which will all go to GV as 11 digit numbers starting with "1". Additionally, you can also call any number starting with "011".
ianobi:
@onepolarbear,
Quote
I think the best solution is to completely block int'l calling on my Google Voice
via Obi110. (except for two countries that I frequently call: Germany and UK)
Of course, I also need domestic U.S. calling as well.
This can be done using this digit map:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|01144xx.|01149xx.)
44 is the country code for UK, 49 for Germany. This would prevent you from calling any other country using GV. It does allow ten and eleven digit calling for North American numbers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page