[simon tahiti]

Hi Kris,

I store all my numbers in the standard international format, i.e.

+[COUNTRY CODE][AREA CODE][NUMBER]

As you know, this works fine to and from everywhere in the world as long as you dial directly via the GSM network.

The issue here is that I'm only using the GSM network to gain access to AT&T's back end system calling card system...and their back-end system is nowhere near as smart. It treats US numbers differently than all other numbers. If you include the country code in the dial string for a US number then the call won't go through via the calling card.

I guess they do it to save people from entering 3 digits ("01" and "1") when dialling the USA - makes sense given that they are a US company and the vast majority of their card users' calls would be to the USA.

However, it means that it doesn't work with CCDialer. :?

I guess it's no big deal to take out the "+1" from my US-based contact records...but it just feels wrong to store their numbers in an incomplete format like that....and of course they will no longer work if dialled directly via the GSM network.

[simon tahiti]

Hi Kris,

I store all my numbers in the standard international format, i.e.

+[COUNTRY CODE][AREA CODE][NUMBER]

As you know, this works fine to and from everywhere in the world as long as you dial directly via the GSM network.

The issue here is that I'm only using the GSM network to gain access to AT&T's back end system calling card system...and their back-end system is nowhere near as smart. It treats US numbers differently than all other numbers. If you include the country code in the dial string for a US number then the call won't go through via the calling card.

I guess they do it to save people from entering 3 digits ("01" and "1") when dialling the USA - makes sense given that they are a US company and the vast majority of their card users' calls would be to the USA.

However, it means that it doesn't work with CCDialer. :?

I guess it's no big deal to take out the "+1" from my US-based contact records...but it just feels wrong to store their numbers in an incomplete format like that....and of course they will no longer work if dialled directly via the GSM network.

[simon tahiti]

I'd hoped that the WM5 devices might store the country code, area code and local number in separate fields - that way you wouldn't have to parse out the country code and get stuck with the whole issue of the codes being different lengths. But if the whole number is stored in just one field then that is impossible. Oh, well...no big deal really.

By the way, I had one other suggestion: it would be good to have the option of using CCDialer to call a number that isn't in your contacts list, but which you just key in. For example, say if someone leaves a note on my desk with a number to call back...or someone leaves me their return number in a voicemail. It would be great to be able to just key that number into a field in CCDialer.

[Kris Kumar]

Originally Posted by simon tahiti

I guess they do it to save people from entering 3 digits ("01" and "1") when dialling the USA - makes sense given that they are a US company and the vast majority of their card users' calls would be to the USA.

Thanks for explaining. Let me see what can be done. I might have to build a table of Country Codes and detect the +1 (US) and +91 (India) etc, and take it out. This way the application will be generic.

Of course the other option is to make an AT&T specific one. Or introduce a setting that enables the application to take out the country code for only one country of your choice. Instead of a generic removal for all country codes. The application is capable of sensing only one country code and removing it. In this case, I can have prompt the user to enter the country code that needs to be removed in the settings. This way the app is generic for at least country. And seems like this "country code not required" exclusion is only for one country.

Thanks for taking time to explain things.

[Kris Kumar]

Originally Posted by simon tahiti

I'd hoped that the WM5 devices might store the country code, area code and local number in separate fields - that way you wouldn't have to parse out the country code and get stuck with the whole issue of the codes being different lengths. But if the whole number is stored in just one field then that is impossible. Oh, well...no big deal really.

I was thinking the same too after I posted my thoughts last night. (Similar to the way the address is stored in Outlook.)

Originally Posted by simon tahiti

By the way, I had one other suggestion: it would be good to have the option of using CCDialer to call a number that isn't in your contacts list, but which you just key in. For example, say if someone leaves a note on my desk with a number to call back...or someone leaves me their return number in a voicemail. It would be great to be able to just key that number into a field in CCDialer.

Cool idea. This one I will definitely put on my list of things to do.

[zmanuel]

I installed the application with no problems (Cingular 2125, WM5 aka Qtek 8310).
First, I would like to thank Kris a lot for the excellent application.
The only suggestions for improvement that I have are:
- in the T9 search, it only checks for the last name (e.g. a contact named John Stuart will be displayed if you press 9 (for s), 8(for t), and not for 5(for J) and 6 (for o).
- also, in the T9 search, the special characters present in some languages (e.g. French and Romanian accents) are not recognized. For example, the name "Şerban" will not be located at all.

Thanks again and I hope you don't mind the feedback.
Manuel

[Kris Kumar]

The SmartList control that I am using to enable contact lookup is provided by the fine folks at OpenNETCF.org and it seems to be searching only the begining of each line. Let me see if I can improve it.

Will also look into the non-english characters.

BTW: I have the kept aside few hours this weekend to fix some of the issues with the application and put out hopefully the final version.

Keep suggesting the improvements/bugs. :-)

[nuguy]

Perhaps you could help me with a problem...

This is one of my biggest disappointments on the 6700's (apache) and win mobile devices in general WinMobile5 in particular.

In northern Illinois even if you are calling within your area code, you need to dial the area code.

Being as I dial most of my clients only once from my cell, I don't want them all to be added to my contacts. And since I am calling while driving a truck and looking at a piece of paper dialing on the screen. I WANT TO HAVE A PREPEND OPTION for my area code (unless I specificly dial a different one).

Most $39 phones have this option, and most palm phones have this option.

It can't be that hard to program it (can it?).

After doing much searching, and not getting much closer, it seems (per MS website http://www.microsoft.com/windowsmobi....mspx#settings ) there may be a phone setting that is not enabled that would enable "dialing rules".

These would be in the same area of settings as network time synch, and voicemail notification, etc..

But these phone settings are not available (not even any reg hacks I can find).

What I'm looking for is specificly "dialing rules".

Yes, I know they are listed in network settings, but these do not affect voice dialing.

It seems that you may be onto a possible solution to this.

I think your ap would satisfy an even larger audience with this as a feature (two different end user types - 1 aplication)!

Any thoughts???

[rcgroup]

Kris, I am also a PPC Phone user and wanted something like this... Nice but a little difficult to use as i have quite a few contacts and scrolling thru was a problem...

i can suggest 3 things
1. a small text box at the bottom that will search/filter contacts as you type there
2. somehow link it into the contacts that have some rules defined.. I was earlier a treo 650 user and had a program called TAKEPHONE, that had a nice feature to setup calling cards. What i woudl do is create a rule for all numbers starting with +91 rule applies, and i would make it look like this
+91 ----> translaets to 18880000000pin+91 and the rest of the # continues...
3. another thought is create rules on page 1 of interface ; lets say i am interested in calling someone in india i will have a rule for India that will show me all contacts that have a # starting with +91 and will use calling card 1
another rule that is US will show me all #;s starting with +1 and use a card
and so forth.

[Amidsin]

Thanks, it is a great application. I have been lookiing for something like this. At some point was thinking about coding something myself. Again, thank you very much for it.

I'm using it on the i-mate JAMin. It works just fine. So, it is one more confirmed compatible device.

I hope to see the version with integration with UI of of the Pocket Outllok (selecting contact not from special list, but from Contacts application). I think that this feature would make this application truely invaluable.

[Duke7211]

I may have invited this error by installing incorrectly but I thought that I would let you know anyway.

Because my computer is still running 98se, I went ahead and tried to download and install using T-Mobile SDA II.

It installed without a hitch and I was able to input calling card info. When I tried to select contact however, there were no contacts to select from (may be because I have not figured out how to get them off of sim card). I went back to screen which has the contact and calling card info and repeated the -menu, select contact- steps and received an error message......
=====================

CCDialer.exe
ArgumentOutOfRangeException

Application::Run+Oxf
DialerMain::Main+Oxa
====================

Sounds like quite the handy program although I might end up forgetting my pin