Quote:
|
Originally Posted by simon tahiti
My feedback/suggestion is this: Can you build in a setting for each calling card (like the existing 'Dial Intl. Access Code' check box) which enables the user to define whether the country code should be included in the dial string?
|
This is tricky for me to implement in the application because the Country Code varies in length, I mean number of digits. Like United States is "1," and India is "91," Costa Rica is "506." I don't think I will be able to parse them out, unless the you put a delimiter like "-" in the number in the address book.
But here is a thought, how do you currently store the US numbers in your address book. I store them as +1 (000) 123 4567. e.g. +1 (000) 123 4567 in case of US and +91 (100) 123 4567 for Indian numbers; you get the idea.
The GSM network is very smart. When a number like +1 000 123 4567 is dialed in US from your cell phone directly, the GSM network recognizes you are in US and ignores the +1.
Now if you were in Australia and you dialed the same number from your cell, then the GSM network in Australia will replace the + with whatever is the international access code in Australia (like US has 011). GSM network is smart. Not sure if the CDMA world can do the same (aka Verizon and Sprint/Nextel). BTW my calling card application is smart enough to recognize the + and replace that with the international access code, but it replaces the + with the intl. access code every time.
Long story short, I think setting up your US phone numbers as +1 000 123 4567 I believe will solve your problem. You will have a common address book and calling card for each country, no need to worry about removing the country code. ;-)
If the above is not true or if I got off on the wrong track. I need some examples, like a dummy phone number the way it is stored in your address book and how the calling card should dial it when you are in Australia/other places. Will be happy to help out.