Dial plan explanation

<< < (23/41) > >>

RonR:
Quote from: jimates on March 25, 2012, 08:14:44 pm

ITSP Profile
Digit Map - (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1814>[2-9]xxxxxx|011xx.)


This is an optimzed DigitMap for most service providers with US/Canada calling (11/10/7 digits and 011+).

Since this DigitMap is typically needed in multiple places, a good idea is to place it in a User Defined DigitMap where it can be shared instead of replicated:

User Defined Digit MapX
Label: ste
DigitMap : (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1814>[2-9]xxxxxx|011xx.)

Then it can be used in multiple places:

Services Providers -> ITSP Profile A -> General -> DigitMap : (<411:18002464411>|(Mste))

Services Providers -> ITSP Profile B -> General -> DigitMap : (Mste)

Adding 411 number substitution support to SP1 is shown in the example above.

Quote from: jimates on March 25, 2012, 08:14:44 pm

SP1 - X_InboundCallRoute - {ph,pp(290xxxxxx|290xxxxxx|290xxxxxx)}


This is not valid syntax and should be:

Voice Services -> SP1 Service -> X_InboundCallRoute : {ph,pp(ob290xxxxxx),pp(ob290xxxxxx),pp(ob290xxxxxx)}

Quote from: jimates on March 25, 2012, 08:14:44 pm

Obitalk Service
Digit Map
(<ob>xxxxxxxxx|obxxxxxxxxx)


This is correct.

Quote from: jimates on March 25, 2012, 08:14:44 pm

InboundCallRoute – (3 Obion softphone numbers with this Obi set as the default gateway and direct dialing, same as from the phone port)
{(290xxxxxx|290xxxxxx|290xxxxxx)>(xx.):SP1},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**2:>xx.):SP2},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**8:>xx.):LI},{(290xxxxxx|290xxxxxx|290xxxxxx):aa},{ph}


This should be:

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(290xxxxxx|290xxxxxx|290xxxxxx)>(Msp1):sp1},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**2:>(Msp2)):sp2},
{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**8:>(Mli)):li},{(290xxxxxx|290xxxxxx|290xxxxxx):aa},{ph}

For a more elegant approach, you might consider Single-Stage Dialing Through Any OBi Trunk.  The result is more consistent with PHONE Port dialing and much easier to maintain.  If you don't need to call out through other OBi's, the only change required is:

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (290123002|290123003|290123004)

Quote from: jimates on March 25, 2012, 08:14:44 pm

Phone Port -  (I know I should move the 411 to the digit map and out of the call route. This was done long long ago when we first got Obi’s, and since it worked I didn’t worry about it.)
Digit Map
 ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|411|**0|***|#|**1{t=di2}(Msp1)|**2{t=di2}(Msp2)|**8{t=od}(Mli)|**9{t=di2}(Mpp)|(Mpli))

OutboundCallRoute –
{(<411:18002464411>):sp1}, {([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 411 moved to the SP1 DigitMap, these would become:

Physical Interfaces -> PHONE Port -> DigitMap:

([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1{t=di2}(Msp1)|**2{t=di2}(Msp2)|
**8{t=od}(Mli)|**9{t=di2}(Mpp)|(Mpli))

Physical Interfaces -> PHONE Port -> OutboundCallRoute : Default

jimates:
Thanks so much. I made the changes for a much cleaner config.

even with the invalid syntax the call forking was working before.

but the "single stage dialing" isn't really single stage dialing, is it?

since I have a single Obi set as the default gateway for all 3 of my Obion numbers I can dial from the app just like from the phone port. True single stage dialing, nothing extra like speed dials to direct the calls through a certain Obi.

With the elaborate single stage dialing setup don't you have to direct the call to the Obi using extra digit inputs?

RonR:
What I proposed (since you don't use more than one OBi):

Voice Services -> OBiTALK Service -> InboundCallRoute:

{(Mcot)>(Msp1):sp1},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}

User Settings -> User Defined Digit Maps -> User Defined Digit MapX:

Label : cot
DigitMap : (290123002|290123003|290123004)

adds support for **1 that you didn't have (I reaslize it isn't necessary since SP1 is your PrimaryLine).

The main improvement is a more streamlined approach, with all the trusted callers in a single DigitMap once instead of being repeated four or five times in the InboundCallRoute.

No extra dialing is required.  The extra digits are only needed to address other OBi's (this is stipped out of the example above).

jimates:
OK, if I didn't have them assigned to the gateway (or if I were going to use more than the one Obi, I would need the slight extra dialing just to direct the call to an Obi. Right?

I will make the changes to that also.

RonR:
An OBiON App always needs to be assigned to a gateway OBi.  Default dialing (normal single-stage dialing with no extra digits) will go to the gateway OBi and use its service providers.

If you also want the capability to place calls though an alternate OBi's providers, you need to use the full blown 'Single-Stage Dialing Through Any OBi Trunk' configuration and dial the extra digits to address that alternate OBi.  In that case, the OBiON App call is routed to the alternate OBi to use the alternate OBi's providers.

Navigation

[0] Message Index

[#] Next page

[*] Previous page