Incorrect display of international #s and #s with extensions

[pmj]

On my Samsung Android phone, Fongo uses the phone's native contacts database. This is a good feature - it eliminates duplication, allows organized back-up, one-shot editing, etc.

I have several UK numbers, saved as +44-exchangecode-phonenumber. This allows me to use the phone anywhere - here, in the UK, or anywhere else - and the local system replaces the + sign with the appropriate international (or in the UK, internal) LD access number, and can thus dial the number.

I have a few UK numbers saved as 011-44-exchangecode-phonenumber. They will work from here - but they won't work from another country. Each time I find one I correct it.

Using Fongo, when I view "regular" Canadian numbers, it shows the call rate - mostly free, sometimes $0.02/min, etc. So far, so good.

When I view a 011-44 number, Fongo displays it as-is, and it shows the rate. It also knows about the higher rates to call UK cell numbers, etc - which is useful. But this number is not correctly formatted for dialling from another country (except the US).

However, when I view a correctly-formatted +44 number it displays it incorrectly as 1-44-exchangecode-phonenumber - and it doesn't know the rate. Although I don't have any credits, I also suspect that it won't dial - based on the following:

I have many Canadian numbers stored in the format (613) ###-#### x ###. The final ### is the extension - which I often need for some numbers.

The native phone dialler dials these numbers as 613#######, and it discards the trailing " x ###". I also use TAKEphONE, a powerful dialler that can also deal with pauses, extensions, PINs, etc - it also works.

Fongo displays these numbers as 1-613-###-####### - deleting all brackets, x's and spaces. It again doesn't know the rate - and it won't dial. This is a serious problem....

When I view these numbers in edit mode, they are displayed in their stored formats - so it's only when Fongo prepares the number for dialling that the problem arises.

Can you please look into this.

Peter

UPDATE 2012-11-26 13:50 As a follow-up - if I enter a +44-etc number directly into the dial pad, DV/Fongo correctly interprets it, and assgns the correct rate - so this problem relates only to the way in which numbers are transferred from the address book into the dialling process.

[pmj]

Any thoughts on this? Although the international number issue is a nuisance - the interpretation of numbers with extensions, pauses, etc is a much bigger problem. Surely I'm not the only person who uses a cellphone to call people who have extension numbers?

Peter

[cmc]

bump. i'm having the same issue with + prefix on DellVoice Android. My US/Canadian +12223334444 numbers are recognized correctly, while international +<countrycode><exchg><ph#> numbers aren't.

[Fongo Support]

Thanks for the feedback. I've sent this request through to our development team.

[pmj]

Has this issue made its way into the to-do list?
Peter

[FONGO_mike]

Has this issue made its way into the to-do list?
Peter

If it is with development, it is on the to-do list

[Bing Kol]

Has this issue made its way into the to-do list?
Peter

If it is with development, it is on the to-do list

pmj's question is a categorical question that begs a categorical answer!

The answer can only be 2-3 letters.

So, is it a NO, or a YES?

[FONGO_mike]

Has this issue made its way into the to-do list?
Peter

If it is with development, it is on the to-do list

pmj's question is a categorical question that begs a categorical answer!

The answer can only be 2-3 letters.

So, is it a NO, or a YES?

Sorry, did not say yes, but i thought i had made it clear is on the to-do list.

Yes.