missed 1 digit when dialing US number 252- and I got connected to Somalia(252)!
onepolarbear:
I have several relatives living in North Carolina. The area code is (252).
Let's say my cousin's number is (252) 555-1212.
When I tried to call him, I always just dial the 10-digit number, (252)555-1212.
Obi110 DigitMap setting just automatically adds the +1 in front of it.
Below is what my current DigiMap looks like: (the default setting, I believe)
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
However, I discovered that I had several calls to Somali when reviewing my
Google Voice billing history. It turns out that I must have dialed (252)555-121
and miss the last digit. On a normal landline phone, this is not a problem.
It will just tell me to check the number and dial again.
Obi110, on the other hand, just dials it as +1-252-555-121 which connects me
to someone in Somalia. The country code there just happens to be 252.(just
like North Carolina's area code) Google Voice charges 50 cents(or more)
per minute to country code 252, Somalia!!! :(
What can I do to prevent this from happening again? I do make other intl
calls regularly, so I cannot just block all int'l calls.
This is not just limited to North Carolina 252 area code. There are many US
cities with area code that are the same as foreign country codes. If I'm not
careful, I end up with paying for 1 minute of int'l call just by missing one digit.
(or dialing one extra digit at the end)
I can't be the only one to have had this happen, right? :) Tried to search
the forums, but not sure what keywords I should use to find the right results.
Any advice appreciate!
Rick:
I can think of several easy fixes.
1) Program your cousin's number into your phone so it dials properly, and dial infrequently called numbers more carefully.
2) Remove the international dialing defaults from the digitmaps, so that you are required to enter the preceding digits when you intentionally want to call internationally. I don't play with digitmaps, but that seems like a no-brainer.
ianobi:
It would be interesting to see your Call History, which would show what you dialled and what went out to GV. With your digitmap a "1" would only be prepended if you dialled a ten digit number. I would expect (252)555-121 to be picked up by the xx. rule which matches any number of any digits.
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.
Rick:
Ianobi, what would you do if you wanted to prevent ANY international calls? Remove the |011xx at the end?
CoalMinerRetired:
Quote from: Rick on February 05, 2013, 05:42:26 am
Ianobi, what would you do if you wanted to prevent ANY international calls? Remove the |011xx at the end?
I know you meant to write it this way, but for everyone else's reference it's the period after the second x that makes the difference, eg., "011xx."
§ x - a wild card digit that matches any digit from 0-9. x is CASE SENSITIVE
§ x. - matches 0 or more x
Given that the country code in question is 252, I'd suggest an alternative approach. Just disable calls to that country code, as in a barring rule for calls to 011252x. I haven't tested it but the syntax should be !011252x.| inserted ahead of the 011xx. This will bar any calls that start with 011252 and continue with zero or more digits after the 252.
I'll second ianobi idea, it would be interesting to see your Call History. Because somewhere you would have had to dial 011 before you dialed the digits 252.
Navigation
[0] Message Index
[#] Next page