Quote:
Originally Posted by mmorse Welcome to the forums,
Sometimes replies take more than 24hrs  |
Sorry, just anxious to figure out what's up.
Quote:
Originally Posted by mmorse
And the one your concerned about:
If it has 10 digits, prepend a "1"
[if (numStr.length == 10) {numStr = "1"+numStr;}]
You still want to change this?-let me know and I'll start you on the steps |
Yes. The thing is, more and more areas have 10 digit local dialing, as more and more areas get squashed. That is, it's hard to find free local prefixes, [ (XXX) NNN-YYYY <--- NNN = local prefix ] so most phone companies up here are forced to resort to 10 digit local dialing.
Honestly, I'm incredibly surprised that the Asterisk zimlet functions in such a way. I don't think you can find a high density urban area Canada wide, that doesn't have 10 digit dialing enforced. Many low density urban areas are also in the same boat. In fact, I think all of Ontario is.
I don't know how things sit in the US, but I would be surprised if it wasn't the same. Part of the issue here is that our Zimbra users are going to be syncing their mobile devices. Most of these users have hundreds of contacts, and some thousands. Prepending + to these is ... difficult.
One of the good ideas that cell phone providers have enacted here, is that if you dial a long distance number on your mobile, without prefixing it with 1, it will state
"The number you have called is a long distance call. In the future, please prefix this number with a 1. We are now connecting you, thanks".
As well, if you dial a number with a 1, and the number is a local call, the mobile provider will simply put the call through.
This allows for users to travel far and wide, and not prefix their numbers with 1 on any of their contacts... and then when syncing with their exchange (or Zimbra) server, they can still dial local numbers. After all, the 1 is not there.
Add to this turmoil the fact that many users have _multiple_ local areacodes. For example, this install is in the 613 areacode, and can locally call some local exchanges in both the 613 and 819 areacode.
Of course, there is no simple fix for this situation. A correct fix would be for the user to add their local area code + local prefixs for all instances of local area codes that are not to be prepended with a 1.
So, I guess a list of numbers such as:
613555
613552
613557
819555
819645
denoting local calls would be the only way to effectively have the 1 prepended at the right place.
I guess the only real way to do such a thing would be to make it part of the Asterisk zimlet setup. After all, one must put their Asterisk IP into the conf file when setting things up, so it is no worry to have an array with the same... I'm guessing. Perhaps a comma delimited variable, then split into an array?
Anyhow, if we move down the Zimbra path (it looks good for that, btw), I might take some time to code this myself. I'm not sure how interested people upstream are in this, though...
Thanks for the reply.