Dial plan explanation
ianobi:
You would put it in the Phone Port DigitMap such as:
**1{t=od}(Msp1)
I would be careful about replacing **1 with 48. It may conflict with other numbers. If you do replace **1 with 48 in the Phone Port DigitMap, then remember in the Phone Port OutboundCallRoute to change **1 to 48 in this rule:
{(<**1:>(Msp1)):sp1}
zapattack:
Great. Did exactly as advertised!
I realize modifying default codes is rarely a good idea, but I really wanted to add my '48'.
Finally made this work:
|<48{t=od}S9:**1>|**1{t=od}(Msp1)|
48 & **1 go to my default SP2 of course, so further routed from there to SP1 (GV) successfully.
This code will work until this area has a '48x' local area code!
Strangely it was necessary to add the S9, as default timeing was 2 seconds in the substitution format.
KenC_OB:
Hopefully, this is simple, one line in/out, no Google Voice, nothing fancy - I just want to verify this, as I'm new to dial plans:
I have set up my In-Laws with an Obi100 and CallCenctric VOIP. I'm trying to keep things as simple as possible for my In-Laws, they are elderly with declining sight and hearing, and don't deal with change well.
I've tested the system, setting up the Obi100 manually per the CallCentric directions here:
http://www.callcentric.com/support/device/obihai/obi100
The port of their number is in process, so I want to tweak the dial plan when I go over there to disconnect their phone wires from the POTS and connect them to their Obi100.
Their Area Code and Exchange are 847-478-xxxx (great for dyslexics, right?) ;)
To goof-proof their dialing, and accommodate any combination they might do, I'd like the following input/responses:
I'll use AAA for Area Code, and EEE for Exchange -
They dial 11 digits - 1AAAEEExxxx - should go through as dialed
They dial 10 digits - AAAEEExxxx - Obi100 should add the 1 and dial 1AAAEEExxxx
They dial 7 digits - EEExxxx - Obi100 should add the 1847 and dial 1847EEExxxx
They dial 4 digits - xxxx - Obi100 should add the 1847478 and dial 1847478xxxx
This should allow them to just dial 4 digits to their local friends in the same exchange.
The default Callcentric Dial Map is (under Service Providers > ITSP Profile > General):
(*xx.|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
so I'm planning on (changes in BOLD):
(*xx.|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1847>[2-9]xxxxxx|<1847478>xxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
I'm not sure what the default timeout is, four seconds? Should I use Sx codes with this, they are pretty slow and I don't want the 4 digits to trigger a dial sequence if they are still dialing a different exchange or area code.
TIA for any help - KenC
PS - secondarily, is there a guide to these codes somewhere? I've read through most of this thread, and I've reverse engineered most of it, but it sure would be nice to see a syntax spelled out somewhere - thanks again.
zapattack:
Admin manual has everything.
http://www.obihai.com/OBiAdminGuide.htm#_Toc333506161
Default timeout is 9 or 10 seconds, which is why it is a good idea to specifically code 10 or 11 digit dialing with an S0 (capital S Zero) at the end. Otherwise, S2 works for most other codes.
Consider using the RonR configuration utility, although the 4-digit dialing is a bit unusual.
Try changing: |<1847>[2-9]xxxxxx|<1847478>xxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
to
|<1847>[2-9]xxxxxxS0|<1847478>xxxxS0|011xx.S2|xx.|(Mipd)|[^*#]@@.)
ianobi:
There are two interdigit timers 10 seconds and 2 seconds. In your digit map most of the dialled numbers will automatically be using the 2 second interdigit timer.
Be very careful of using S0 to force the interdigit timer to 0 seconds. A rule such as <1847478>xxxxS0 will match any number as soon as the first four digits have been dialled and no other rules can be used.
We can all be a bit slow dialling from the phone. I know I sometimes stop to re-read a number halfway through dialling! I suggest a 4 second interdigit timer where duplication of the first few digits is possible. You know them, so you might want to make that longer. I suggest for your In-Laws:
Service Providers > ITSP Profile A > General > DigitMap:
(*xx.|**275*x.|[3469]11|1xxxxxxxxxxS0|<1>[2-9]xxxxxxxxxS0|<1847>[2-9]xxxxxxS4|<1847478>xxxxS4|011xx.|xx.)
I’ve dropped |(Mipd)|[^*#]@@. From the digit map as these are for ip address and sip uri address calling, which I guess will not be needed here.
The four digit dialling is unusual. Is there a chance any of the four digit numbers starts 311x, 411x, 611x or 911x ? If so, there are obvious problems!
Navigation
[0] Message Index
[#] Next page
[*] Previous page