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!
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.
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.
Ianobi, what would you do if you wanted to prevent ANY international calls? Remove the |011xx at the end?
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.
Date Time Type Destination Duration Charge Deposit Balance
2/4/13 10:50 PM Call +252275451 1 minute $0.53 $4.55
1/25/13 7:35 PM Call +25232**56531 1 minute $0.53 $5.35
1/16/13 5:50 PM Call +252256562 2 minutes $1.06 $5.88
Above is from my Google Voice billing history.
Call #1 & #3: I must have left out a digit and dialed just 9 digits... call went to Somalia, billed at 53 cents/minute. I probably realized it too late and the call went through. I remember on call #3, there was a recording of some type of weird music.
Call #2: I used my cordless phone's redial button. Unfortunately, the number that I dialed was going to an office and I had to press "3" and "1" to get to the person. My cordless phone's redial remember the whole 10-digit number plus the 3 and 1 at the end. When it redialed, it dialed 25232**56531. Not sure why it also went to Somalia.
That's what I'm confused... I didn't dial "011" in any of those 3 calls... so how did the call go through as int'l calls?
This is one of those cases where something like VOPI.MS works well. You can specifically block country by country or allow only certain countries.
Of course a wrong number may only cost you a few cents, but some countries are dollars to call a mobile number.
OOPS! I meant VOIP.MS a Voip provider.
I'm still a newbie to this... what is a VOPI.MS? :)
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. :)
Is there a way to selectively block out all countries except two?
Thanks! :)
> ... 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.
Check into the call histiory in your Obi, see if it confirms the no "011" prefix?
I'm trying to figure out a barring rule (temporary) that will bar calls to 252x. or 1252x. but allow "1xxxxxxxxxx|" and "<1>[2-9]xxxxxxxxx|".
The only way I can see to do this is "!252xxxxxx|" and "!1252xxxxxx|", note that are six x's after the !252, this bars six digits after 1252 or 252 are dialed, but with the existing rules will allow 10 and 11-digit calls to 1252-nnx-xxxx. "!252xxxxxx|" and "!1252xxxxxx|" go after the "<1>[2-9]xxxxxxxxx|" and before the "011xx."
Factoring in the continuted use of "011xx." means the dial plan for calls to the US 252 area code depend on the inter digit timers and matching rules. So you have to complete the 10 or 11-digit dialing before the timers and matching rules declare a match on the 9-digit "!252xxxxxx" barring rule. This is what you want, the Obi to catch a 9-digit call when you really want to make a 10 or 11-digit call. At least without testing this is how I see it will work.
We'll see if anyone else jumps in here.
onepolarbear,
Lazy way to do it is to program those numbers in the OBi speed dial.
It looks like GV doesn't require 011 to dial International Calls and just requires a valid country code.
Change your DigitMap to:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.)
The Obi will now reject any international calls without 011.
Edit:
I did it again.
ianobi already gave you the DigitMap fix.
There is e very simple solution to this problem which may save you some money- stop using GV for international calls. Sign up and set up Localphone.com as a second provider on your Obi110 ( you will have to dial **2) which has far better rates than GV and many other interesting features and services and you are all set. :)
+1 for Carl's idea. Also includes a free UK DID/CallerID
Otherwise, numba onepolarbear should have numba twopolarbear do the dialing. ;D
thanks for EVERYONE who replied! I really appreciate the help.
in the end, I took the advice and changed my setting
to (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.)
Just tested it... now my call doesn't go to Somalia (252) :)
It just occured to me that some pirates out there may
have gotten my call in the last month or two. :D :D :D
Thanks again! :)
It's amazing that Google Voice doesn't require the 011 prefix before routing a call as international. This is probably by design so Google can fleece folks that make a mistake in dialing.
I tried dialing my iNum 8835100xxxxxxxx through Google Voice from the OBi110 and the call went through.
In this case 883 is the "Global" or "Earth" country code and 5100 is iNum (Voxbone). Obviously there's enough digits that it's not a U.S. number. 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. You could ask for a credit from Google for the erroneously dialed calls. Imagine if the PSTN networks suddenly removed the 011 prefix requirement for international calls and decided to route calls international if the area code happened to match a country code and the number of digits dialed was a bit short or long for a U.S. call.
I don't maintain a $ balance with Google Voice... and now I know why. I think Lavarock7 meant voip.ms (not vopi.ms). Voip.ms is a real voip company (well as real as it could be, run by a bunch of Canadians). Voip.ms has a lot of granularity when limiting international calls including allowing only specific countries and a maximum acceptable per minute rate that applies across the board (which helps prevent getting a surprise when dialing certain "toll" type numbers or inflated cell phones).
Updated: Repositioned a line of text to clarify what I think I meant and corrected a typo.
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
'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.
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!
@ Rick,
QuoteIanobi, 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".
@onepolarbear,
QuoteI 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.
Thanks! :)
That should put a stop to all my bad dialing to int'l calls, at least to numbers that require 011.
I looked into my billing history and discovered that I also had
several calls to area code (242) which I believe is the Bahamas.
Billed at 10 cents/minute. I must have dialed 242 instead of
252(North Carolina) as intended and hung up.
Since there are many foreign country codes within North America,
can the digimaps to be programmed to restrict calls to all of them?
These are mostly Carribean countries, plus PR and Guam. I looked
it up and there are about 25 3-digit foreign country codes in North
America:
Source: http://www.nanpa.com/pdf/NANP_Member_Country_Maps.pdf
242
246
264
268
284
340
345
441
473
649
664
670
671
684
721
758
787
939
767
784
809
829
849
868
869
876
Thanks! :)
Using this DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|01144xx.|01149xx.)
Calls leaving your OBi going to GV will be eleven digits starting with "1" or international calls starting with 01144 or 01149.
Rather than banning certain numbers, this DigitMap only allows the above formats / numbers. The important thing is to remove rules xx.|(Mipd)|[^*#]@@. from GV DigitMaps, then nine or ten digit numbers cannot get to GV to allow them to send them around the world :)
I have already updated my digimap with the one you provided. :) Thanks!
However, if I make a mistake and dial 242-327-6000(a hotel in the Bahamas)
instead of 252-327-6000(North Carolina), the call will go to the Bahamas
and be billed at 10 cents.(assuming someone picks up before I realize the mistake)
Just tried it and that's exactly what happened. :)
Probably time for me to find a new cordless phone with bigger keypad for my giant fingers! :D
Quote from: onepolarbear on February 07, 2013, 11:18:31 AM
However, if I make a mistake and dial 242-327-6000(a hotel in the Bahamas)
Now that you have narrowed it down considerably, block 242 numbers on the OBi.
You could be very restrictive on your ten digit dialling and use a DigitMap such as:
(1xxxxxxxxxx|<1>252xxxxxxx|01144xx.|01149xx.)
This means only ten digit numbers starting with 252 would have "1" prepended, then sent to GV. Any other ten digit number would be rejected by the OBi. All other North American numbers would need to be dialled as eleven digit numbers starting with "1".
onepolarbear,
Try this:
(1) Pick an unconfigured Voice Gateway. I chose VG5 in Gateways and Trunk Groups:
Enable: unchecked (must uncheck default box)
Name: Route misdialed calls here (must uncheck default box)
AccessNumber: leave default box checked
DigitMap:
(1?(242|246|264|268|284|340|345|441|473|649|664|670|671|684|721|758|787|939|767|
784|809|829|849|868|869|876)xx.)
AuthUserID: leave default box checked
AuthPassword: leave default box checked
(2) Add this parameter to the beginning of your PHONE Port OutboundCallRoute: {(Mvg5):vg5},
(change the 5 to the actual VGx slot # you used in step 1)
Now whenever any of the 26 (I counted 26, not 25 in your list) "toll" area codes in North America are dialed with or without a "1" prefix you should hear a message from the OBi like "No service configured error...". You will get the message because the VGx (in this example VG5) is not enabled or configured with a service provider. This will be your cue that you misdialed.
I have implemented and tested this on my primary OBi110. I chose VG5 because I use RonR's method (mentioned elsewhere in this forum) and have VG3, VG4, VG6, and VG7 configured as dialing prefixes **3, **4, **6 and **7 respectively. **5 cannot be used in this method because it conflicts with the **5code dialed to register an OBi so I had the VG5 slot free.
The misdials do not show up in the OBi call history. This is good because you won't lose good call history but could be a pain if you need to debug.
I don't have a balance in my GV account so I could test and not worry that a priced call would go through. You might want to add 252 (NC) to the list in the DigitMap shown above and place calls to 1252xxxxxxx and 252xxxxxxx numbers to ensure you have it setup correctly. Then remove the 252.
Hopefully this and whatever DigitMap you choose will help keep you get from getting nicked by toll charges when misdialing.
Updated: I split the VGx DigitMap up on multiple lines. It did not display like the "preview" and displayed a scrollbar within the post. Please ensure the complete DigitMap is entered in the OBi VGx slot with no embedded spaces.
Update: Changed DigitMap to start with 1? instead of 1. as ianobi pedantically pointed out. Either works. The 1? is clearer and more accurate. Everything sounds so much more important in a British accent as found here:
http://dictionary.cambridge.org/dictionary/british/pedantic Click on UK speaker. LOL
Quote from: onepolarbear on February 07, 2013, 11:18:31 AM
However, if I make a mistake and dial 242-327-6000(a hotel in the Bahamas)
I have stayed at that hotel and the front desk has been wondering why people call and hang up :-)
Quote from: QBZappy on February 07, 2013, 11:28:47 AM
Quote from: onepolarbear on February 07, 2013, 11:18:31 AM
However, if I make a mistake and dial 242-327-6000(a hotel in the Bahamas)
Now that you have narrowed it down considerably, block 242 numbers on the OBi.
If onepolarbear has set up the digit map to the recommended
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|01144xx.|01149xx.)
why dialing 242-327-6000 would call the hotel in the Bahamas ?
Dialing 242-327-6000 would make OBi to dial +12423276000 and not +2423276000
So, with this digit map the OBi should not call the Bahamas.
or am I wrong?
@ infin8loop,
I like that idea. It provides a good filter without complicating the basic digit maps.
I see that at the start of your DigitMap you use the format "1." to mean 0 or more "1"s. A very pedantic person might use "1?" to mean 0 or one "1".
Now everyone is thinking "ianobi, get a life" :D
Quote from: ateo on February 08, 2013, 04:00:41 AM
Quote from: QBZappy on February 07, 2013, 11:28:47 AM
Quote from: onepolarbear on February 07, 2013, 11:18:31 AM
However, if I make a mistake and dial 242-327-6000(a hotel in the Bahamas)
Now that you have narrowed it down considerably, block 242 numbers on the OBi.
If onepolarbear has set up the digit map to the recommended
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|01144xx.|01149xx.)
why dialing 242-327-6000 would call the hotel in the Bahamas ?
Dialing 242-327-6000 would make OBi to dial +12423276000 and not +2423276000
So, with this digit map the OBi should not call the Bahamas.
or am I wrong?
I also thought the same at first. Actually "242" is an
area code in the "1" North America prefix (or country code). If you can trust wikipedia there is an explanation here: http://en.wikipedia.org/wiki/Area_code_242. The 26 three-digit numbers in the list onepolar bear posted are apparently all
area codes in the "1" prefix. Since none of the area codes are in the continental U.S. or Canada, then they are probably treated as toll calls (long distance) when dialed in Google Voice.
This is what led my to the VGx solution to block these area codes by routing them to an unconfigured VGx. While I'm posting again, the DigitMap I gave ended in "xx.". The "xx." means one or more digits after the 3 digit area code in the list. I tried dialing 1242 and received a busy signal and not the Google voice message indicating I needed funds in my account to place the call. The OBi call log shows call connected (about 1 sec). I don't know if this would have resulted in a toll charge if I had funds available. It might be safer to end the DigitMap with "x." (none or more digits) instead of "xx." (the whole DigitMap enclosed in parenthesis of course) but I have not tried it.
Quote from: ianobi on February 08, 2013, 07:54:12 AM
A very pedantic person might use "1?" to mean 0 or one "1".
I had to look up "pendantic". Now I have to use it in a sentence. He's not
pendantic, he's just
British.
I agree, "1?" is probably more clear and accurate than "1." Forgive me, I'm an American.
Whether you are indeed British or not, play along to make this joke work. LOL
You're probably the kid in class that always wrecked "the curve". ;D
No need to play along - you are correct, I am indeed British, living in England. Here we know how to speak this language like wot it should be spoke wiv dead good grammar and stuff :D
Tomorrow I shall be mostly watching cricket and drinking tea :)
QuoteYou're probably the kid in class that always wrecked "the curve".
I did not understand this reference. Is it an Americanism of some sort?
And now for something completely different:
"Hello.... Hello.... [tap tap] is this thing on? Hello??"
A Priest, a Rabbi, and a Minister walk into bar. The bartender looks up and asks "What is this, some kind of joke?"
Cheers.
(https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcSMTu-r8beEDWVhiCevtD15-6bEjsimAFWbD5DCfMUBPhFDgMbbGQ)
@ianobi
It was a compliment of a sort.
http://en.wikipedia.org/wiki/Grading_on_a_curve
Ahhh, now I see :)
Thanks lhm.
Quote from: ianobi on February 08, 2013, 09:30:38 AM
Here we know how to speak this language like wot it should be spoke wiv dead good grammar and stuff :D
Ian you do a good Texas accent.
@QBZappy, Thanks for the bottle of virtual Crown Royal but it's just not the same. No taste and less intoxicating.
@ianobi, I didn't think about "the curve" not being international. I meant it in a good way as ihm. indicated. In the 60's I attended a British primary school for two years on a RAF base in Germany. The RAF base has been closed and is now the site of: http://goo.gl/T9s9M
You guys all make me laugh. Thanks.
Quote from: infin8loop on February 08, 2013, 08:07:40 AM
Quote from: ateo on February 08, 2013, 04:00:41 AM
Quote from: QBZappy on February 07, 2013, 11:28:47 AM
Quote from: onepolarbear on February 07, 2013, 11:18:31 AM
However, if I make a mistake and dial 242-327-6000(a hotel in the Bahamas)
Now that you have narrowed it down considerably, block 242 numbers on the OBi.
If onepolarbear has set up the digit map to the recommended
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|01144xx.|01149xx.)
why dialing 242-327-6000 would call the hotel in the Bahamas ?
Dialing 242-327-6000 would make OBi to dial +12423276000 and not +2423276000
So, with this digit map the OBi should not call the Bahamas.
or am I wrong?
I also thought the same at first. Actually "242" is an area code in the "1" North America prefix (or country code). If you can trust wikipedia there is an explanation here: http://en.wikipedia.org/wiki/Area_code_242. The 26 three-digit numbers in the list onepolar bear posted are apparently all area codes in the "1" prefix. Since none of the area codes are in the continental U.S. or Canada, then they are probably treated as toll calls (long distance) when dialed in Google Voice.
242 is officially the area code for the Bahamas. So says the "North American Numbering Plan Administration", see here for the list of Caribbean area codes: http://www.nanpa.com/pdf/NANP_Member_Country_Maps.pdf
Removing xx. from GV dial plan will disable iNum calling. (ie: +883510000000093)
It just goes to show how personal digit maps are!
How about we delete the xx. rule and replace with:
x.88351x.
The number can be dialed three ways through GV, +8835100xxxxxxxx , 0118835100xxxxxxxx or 8835100xxxxxxxx . Would x.88351x. work dialing 8835100xxxxxxxx ?
I don't use GV as it's not free where I live, so it's good that you feed me this info :)
x. means none or more digits. Only digits, so it would not include "+". Trying again:
@.88351x.
This means none or more alphanumeric characters, followed by 88351, followed by none or more digits. It should cover all the cases you mentioned.
It may seem like a lot of trouble, but that xx. rule can create a lot of problems! Of course, if you do not use iNum, then there's no need to replace the xx. rule with anything.
If you don't have to dial 8 digit numbers of some other type then another DigitMap to handle iNum numbers:
<0118835100>xxxxxxxx
Just dial the last 8 digits of the iNum and let this DigitMap prepend the rest to save key strokes on the number pad. I included the '011' because it works on both GV and voip.ms.
Good alternative, as the xx. is picked up from |011xx.|.
@ infin8loop - Using <0118835100>xxxxxxxx there is a small danger of the first eight digits of ten or eleven digit numbers being matched to this rule. If your memory is as bad as mine and you look at the number written down somewhere after the first eight digits, then after two seconds this rule will match.
You could add a delay such as <0118835100>xxxxxxxxS4 which would give memory challenged people like me four seconds to continue dialling my ten or eleven digit number.
Yes, I know I'm being pedantic. Please don't throw your newly aquired bomb at me :D
I have a sudden urge to throw some tea into the nearest harbour and then throw a pint back at the local pub. ;D
Yeah, yeah, add whatever "S" delay allows enough time to have a nice cup of tea and crumpets. An ending "#" sign after 8 digits would still speed up the dialing I guess.
I having VG7 configured for iNum via a **7 prefix and 8 digits suggested elsewhere by RonR.