Log in

No account? Create an account

Dialing plan

« previous entry | next entry »
Nov. 11th, 2009 | 12:00 am

Thank you all for answering my survey.

Basically thanks to living in an area rich with Overlay Area Codes there's a good chance most people around me have mandatory 10 digit dialing. In some places the 1 prefix is required for calls that are billed as long distance, sometimes it's always required -- however the 1 prefix is rarely harmful.

As a result if you're able to use your mobile phone book to call out over a land line it's pretty likely to work if you enter things with the 1 + 10 digit format for phone book entries. (The only issue might be if the mobile phone caller id to name mapping would match an incoming 10 digit number to the 11 digit number in the phone book.)

Because of the feature of the 1+10 -- that it's the string likely to work on both mobile and land line phones, I've always wondered why PBX systems aren't using 1 as the indication a person is trying to make an outside call. Most of the office PBX I've used are set to dial internally, unless you dial 9 first for an "outside line", however there's no technical reason why 1 couldn't do the same job, and would have the advantage that you can always dial the same thing, regardless of what type of phone you're using.

For my own small scale PBX purposes I realized I could solve how to differentiate between "external numbers" and "internal extensions" by using digits for external and sip addresses like "desk@server" or "diane@server" as my internal phone numbers.

Alternatively VoIP hard phones support on hook dialing like a mobile phone, so I don't have to parse the digits being dialed one by one, I can parse the whole 3, 4 or 10 digit blob. However that requires that the user hit a "call" or "send" button to indicate they're done keying. Though as a big advantage using on-hook dialing gives you the chance to check what you typed in before the call connects.

Link | Leave a comment |

Comments {0}