Digit Map Help needed.
Ostracus:
If I was to hazard a guess (a big guess, I'm researching it now), if the call stays confined to your local LATA then it's local. If it goes to another LATA then it most likely is long distance.
azrobert:
If CallerID is a big concern, maybe you should consider another provider.
There are a lot of dirt cheap providers that can spoof CallerID.
Also, GV probably will not be free forever.
ianobi:
If it is only one number involved here, then your idea of using a speed dial seems like the answer.
No need to change digit maps. Use trunk format li(503678xxxx).
Using trunk format bypasses digit maps, which may also cut out any OBi dialling delays.
ianobi:
Sorry, I missed some of this:
Quote
Ianobi,
For some reason, as soon as I saw your post, I thought.... Why not put it as a Speed Dial. Hmmmm, If I put **8503-678-xxxx as a speed dial, it would go out on Li? I think the simple format of say "3#" would be acceptable with everyone in the office. But, I would still like it to work correctly if it were dialed too.
Will this add any delays to the call going out?
Add the speed dial as per my last reply using trunk format. The only delay will be OBi seizing the line, then dialling the digits.
My earlier reply about adding rules to digit maps will still work, but will add an extra 2 seconds delay compared to the speed dial.
ianobi:
A few notes concerning speed dials:
Trunk format is fastest as it involves no digit maps.
Trunk format is useful for putting numbers in speed dials that digit maps would reject. So only people who know that speed dial number can actually use it. (Child proofing?)
Drawback: Trunk format speed dials only work from the phone port. They do not work from Obion/Obiapp via the OBiTALK network. To work from all endpoints the **x format needs to be used.
Navigation
[0] Message Index
[#] Next page
[*] Previous page