Dial plan explanation
Gennady:
Thanks Ron. Works Ok. Could you please explain me sequence of events, other words, what OBI analyzed first (Phone DigitMap, Line Digitmap, CallRoute.., etc....)???? Thanks in advance.
RonR:
Quote from: Gennady on February 20, 2012, 04:27:54 pm
Could you please explain me sequence of events, other words, what OBI analyzed first (Phone DigitMap, Line Digitmap, CallRoute.., etc....)?
When a number is dialed from the PHONE Port, the OBi DigitMap Processor evaluates it digit-by-digit using the PHONE Port DigitMap:
Physical Interfaces -> PHONE Port -> DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
With your Primary Line set to PSTN Line, pli gets replaced by li, making the actual PHONE Port -> DigitMap:
([1-9]x?*(Mli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mli))
Mli is a reference to the LINE Port Digit:
Physical Interfaces -> LINE Port -> DigitMap:
([2-9]11S0|[2-9]xxxxxx|1xxxxxxxxxx|011xx.|<8044:**2>xxxxxxx)
Each of these rules matches as follows:
[2-9]11S0 matches 211/311/.../811/911. The S0 forces the interdigit timer to 0 if any of these are matched.
[2-9]xxxxxxx matches any 7-digit number starting with 2 through 9.
1xxxxxxxxxx matches any 11-digit number starting with 1.
011xx. matches any number starting with 011.
<8044:**2>xxxxxxx matches any 7-digit number starting with 8044 and replaces the 8044 with **2.
Once a match is found, the resulting number is evaluated using the PHONE Port OutboundCallRoute:
Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
With your Primary Line set to PSTN Line, pli gets replaced by li, making the actual PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mli):li}
As before, Mli is a reference to the LINE Port Digit. Msp2 is a reference to the SP2 Service DigitMap.
In all the cases except where 8044 was replaced by **2, the number will again match one of the rules in the LINE Port DigitMap, resulting in the call being placed through the LINE Port.
In the case where 8044 was replaced by **2, the number will match one of rules in the SP2 Service DigitMap, resulting in the call being placed through the SP2 Service after first removing **2.
Gennady:
Thanks Ron, now it's clear.
Gennady:
Ron, after implementing your changes suddenly I lost ability to switch lines on my PSTN line by phone flash button. HookFlashHandling is set to "Handle Hook Flash Localy" (default) and Flash time on the phone is 700ms. Any idea?
RonR:
Quote from: Gennady on February 22, 2012, 04:57:21 pm
Ron, after implementing your changes suddenly I lost ability to switch lines on my PSTN line by phone flash button. HookFlashHandling is set to "Handle Hook Flash Localy" (default) and Flash time on the phone is 700ms. Any idea?
DigitMap and OutboundCallroute settings should not affect Hook Flash handling.
From the OBi Device Administration Guide:
Handle Hook Flash Locally
This is the normal setting, where the device intercepts all the hook flash events detected on the PHONE port, and acts on them accordingly, such as:
- Hold current call and start second dial tone for 3-way calls
- Start a 3-way conference
- End call with 2nd conferencee in a 3-way conference
- Swap between two calls in a call-waiting situation
Send Hook Flash Signal to PSTN
Device does not act on hook flash events detected on the PHONE port. It either ignores hook flash events OR regenerates similar hook flash events on the PSTN line if the phone user is currently in a call using the PSTN line service when the hook flash event happens. This option may be useful in cases where the user has traditional call-waiting or 3-way calling services on his PSTN line service; hence he can control those PSTN supplementary services using hook flash signals. However, the OBi in this case would automatically disables its own call-waiting function on the PHONE port, and the user would have no means to tell OBi to make 3-way calls.
Note that an alternative way to let OBi generate a hook flash signal to the PSTN line is to use a double hook flash event by hook flashing twice within 700 ms. See the description of the parameter EnableDoubleHookFlash in this table. With this enabled, you can still let the device handle normal hook flash event locally and preserve the call-waiting and 3-way calling functionalities.
Navigation
[0] Message Index
[#] Next page
[*] Previous page