Routing according the timenframe
azrobert:
This would reduce the code.
OutboundCallRoute : {(<00:>xx.):sp1},{(Mli):li}
JOMA:
@drgeoff, thx for the info and comments. The numbers are emergency numbers for Europe or Belgium so it's not a problem to show them here. You can already find them on internet ;-)
@azrobert, thx for the comments. I'll apply them. I went through the whole conversation and I'm geting confused about xx.S3 . In one post you metionned that without S3, because of xx., there will be a 10s delay before the call is routed and in antoher post, you metionned that if the Digitmap contains xx. the obi110 will wait 2s for other rules. Can you explain the difference of the 2 statements?
Just two last points,
* Should I keep this default digit map: ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
and default route: {([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli} ?
What about the CallRetournDigitMap? Should I keep it?
* Should I also adapt the DigitMap in the Phone and ITSP Profile or only in the Line one?
Thanks a lot!
azrobert:
Quote
Can you explain the difference of the 2 statements?
Yes, my writing skills suck. LOL
Here is a more detail explanation:
The OBi analyzes each digit as they are received and will process the received digits immediately or wait for more digits depending on the rules in the DigitMap.
There are 2 timers.
The short timer is 2 seconds.
The long timer is 10 seconds.
If a dialed number only matches a rule ending with "x.", there will be a 10 second delay.
This is considered an Indefinite Match because "x." will match any number of digits and the long timer is used. The OBi doesn't know if you will enter additional digits, so it waits.
If the dialed number matches a rule without "x.", it will result in an Exact Match. If the dialed number can potentially match another rule if more digits are entered, the OBi will use the short timer of 2 seconds. If the dialed number cannot potentially match another rule if more digits are entered the OBi will process the call immediately and not wait for additional digits.
An S suffix on a DigitMap rule followed by a number will override the wait period.
The OBi2xx has the option to globally change the default short and long timers.
Quote
Should I keep this default digit map:
This is a personal option. I would guess that 99.9% keep it. I chose to remove all rules not used. I defined my OBi's slightly different than my suggestion to you. Don't forget the phone digit map always gets control first and includes the line digit map rules with a pointer.
Here is my new suggestion.
Define the trunk digit maps exactly how you want to process the dialed numbers for each trunk. This way you can look at the trunk digit map and know what's happening.
Line digit map:
(112S0|100S0|101S0|107S0|103S0|116000S0|070245245S0|0xxxxxxxx|04xxxxxxxx|xx.S3)
If the special format numbers do not begin with zero, you can use the S0 suffix on the other 2 rules.
SP1 digit map:
(<00:>xx.)
Define all numbers in the phone digit map, without altering anything. You don't need 00xx.S3 because of xx.S3 in the line digit map. You can eliminate the delay on international calls by defining each country code with the exact number of digits and the S0 suffix.
Phone digit map:
(***|00xx.S3|(Mli))
Phone outbound route:
{***:aa2},{(Msp1):sp1},{(Mli):li}
You can include # to get line dial tone or **0 for the Auto Attendant. You must also include rules in the phone digit map.
{(<#:>):li},{**0:aa},
Quote
What about the CallRetournDigitMap? Should I keep it?
Up to you. I don't use this function, but didn't remove any rules.
Edit:
If you want to force local calls out SP1, include a 00 prefix, so you would dial 3 zeroes followed by the local 8 digit number.
If you want to use an asterisk prefix, include rule *0xxxxxxxx in the phone digit map. You don't need the S0 suffix because the rule is unique. Then add <*:>0xxxxxxxx to the sp1 digit map
JOMA:
Thanks azrobert! It's getting more more clear.
Actually I like all to possibilities the device brings.
I still have question for you :)
What is the difference between aa and aa2? I checked the documents but I didn't find anything. I guess it's the auto attendant but I don't see the difference between both.
Thanks again for all the help you provided!
drgeoff:
aa (=aa1) does call handling things.
aa2, invoked by dialling ***, lets you configure many of the device's settings.
Navigation
[0] Message Index
[*] Previous page