Dial plan explanation
KenC_OB:
Quote from: zapattack on April 27, 2013, 01:15:12 am
Admin manual has everything.
http://www.obihai.com/OBiAdminGuide.htm#_Toc333506161
Thank you - that does seem to have what I need, will study up a bit later.
Quote
Try changing: |<1847>[2-9]xxxxxx|<1847478>xxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
to
|<1847>[2-9]xxxxxxS0|<1847478>xxxxS0|011xx.S2|xx.|(Mipd)|[^*#]@@.)
Quote from: ianobi on April 27, 2013, 02:43:55 am
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.
Yes, when I read the suggestion above to use S0, it did seem that would trigger a dial as soon as 4 digits were dialed and that would be a problem when dialing a full area code or exchange. I'll follow your examples below.
Quote
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!
Thanks, I will drop the |(Mipd)|[^*#]@@ since it is not needed and just confuses things. I assume this isn't needed for direct no-charge CallCentric-to-CallCentric calls (177xxxxxx #'s)? One often-called relative has CallCentric, so the free calling would be a plus.
Good point on the 4 digits and 311x, 411x, 611x or 911x conflict - I missed that possibility. So a call to someone with a 4 digit # like 6113 would match to 611 and go to cust service. I suppose a delay on the x11 would help, but probably best for that to be immediate. OTOH, their calling list is not large, I doubt there are any 311x, 411x, 611x or 911x numbers that they use, and I can check that. I suppose I could do "*" for four digit dialing? I'm not sure how to code that so the * isn't dialed, I'll check that admin guide for that.
update: "*" is already used by CallCentric for features, so I will try with "#" instead - see follow-up post
Thanks so much for the fast feedback, this really helps.
KenC
ianobi:
The Callcentric to Callcentric calls should be processed by the 1xxxxxxxxxxS0 rule.
You may wish to consider setting up speed dials for often used numbers. An OBi has 99 speed dials using single and double digits from 1 to 99. Speed dial 1 is reserved for a softphone.
KenC_OB:
Quote from: ianobi on April 27, 2013, 10:08:30 am
The Callcentric to Callcentric calls should be processed by the 1xxxxxxxxxxS0 rule.
You may wish to consider setting up speed dials for often used numbers. An OBi has 99 speed dials using single and double digits from 1 to 99. Speed dial 1 is reserved for a softphone.
Thanks for that validation. I have set up a few of the Obi100 speed dials, these are helpful. I'll see about setting up more for their other friends/family.
So I read up, and if I decide to go this route, it seems this could do the # plus 4 digit number to short-cut dial in the 847-478 exchange:
|<#:>1847478xxxx|
So dialing #xxxx will match, and the # will be removed and the 1847478 pre-pended, so 1847478xxxx will be dialed. Is that right? Since we are using the # as a 'trigger' no timeout should be required, it should be unique.
-KenC
ianobi:
I see how you are thinking. The rule you would need is:
|<#:1847478>xxxx|
Let's try to keep it simple. Using the digit map as I proposed, if you dial four digits followed by # then the rule |<1847478>xxxxS4| would be processed instantly.
Dialling # after any number of digits forces the interdigit timer to 0 and instantly executes the rule. So if your In-Laws are ok with that, then it's simple and can be applied to any number - four digits, seven digits etc. I suggest leaving the S4 in place in case they forget to dial the # at the end of the number.
KenC_OB:
Quote from: ianobi on April 27, 2013, 11:43:42 am
I see how you are thinking. The rule you would need is:
|<#:1847478>xxxx|
Let's try to keep it simple. Using the digit map as I proposed, if you dial four digits followed by # then the rule |<1847478>xxxxS4| would be processed instantly.
Dialling # after any number of digits forces the interdigit timer to 0 and instantly executes the rule. So if your In-Laws are ok with that, then it's simple and can be applied to any number - four digits, seven digits etc. I suggest leaving the S4 in place in case they forget to dial the # at the end of the number.
I gotcha, thanks - I see now I had the 1847478 in the wrong place.
I think I'll go with the # plus four digit rule for in the exchange calls. |<#:1847478>xxxx|
It seems the other one would still have the 311, 411, 611, 911 conflict? That's what I figured hitting # first would do - just in case someone has a number like 478-6113 it can't match 611 as they dial since it would be dialed as #6113.
They live in a retirement community, so lots of acquaintances are in the same exchange. This will make it similar to calling another room in the same hotel - I think they'll like that. We will also get them some phones with the BIG keypads on them, that helps with the sight and dexterity problems.
I think I have a handle on this, will try it out next week when I go over there to rewire them after their number is ported. Thanks so much for the help!
-KenC
Navigation
[0] Message Index
[#] Next page
[*] Previous page