S0, DigitMaps, and OutboundCallRoutes

(1/3) > >>

MB..:
Could someone clarify for me the placement of the S0 option in a DigitMap?

I have both PSTN and SP1 set up to accept North American and international numbers, and the intention is to automatically route some calls via SP1 when they will be substantially cheaper than calling via PSTN. A user digit map Mvoip (itself defined in terms of other user defined digit maps) describes these cases.

As well as the North American pattern rules, the LINE digit map has a catch-all rule to accept any set of numbers.

1. Can S0 be placed as the last element of a rule in any digit map, including user defined maps?

2. Can it be placed in the OutboundRoutingMap (as in the two cases below), or is its use confined to the DigitMaps associated with LINE/SP1/SP2?
Code:

({(<#:>|[2-9]11S0):li},{**0:aa},{***:aa2},{(Mvoip)S0:sp1},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}


3. Also where is the best place to  put substitutions (such as 0<11:44>441..  which gives a lower cost routing on numbers starting 011441... )? Should they be in the OutboundCallRoute, in the DigitMap for a service provider?


Thanks for your help

RonR:
In my opinion, it's generally a bad idea to start modifying the PHONE Port DigitMap and OutboundCallRoute.  Instead, you should make every effort to accomplish your goal(s) in the ITSPx and LINE Port DigitMap's.

S0 is a DigitMap modifier and should not be used in an OutboundCallRoute.

Assuming you have SP2/ITSPB configured as your VoIP provider, I would recommend you either put the rules you currently have in the voip USER Defined DigitMap in ITSPB -> DigitMap, or set  ITSPB -> DigitMap to (Mvoip).

The changes you've made to the OutboundCallroute are unlikely to give you the desired results.

Substitutions should also be done in the DigitMap appropriate to the trunk they are associated with (i.e. ITSPB -> DigitMap if SP2/ITSPB is your VoIP provider).

MB..:
RonR, Thanks for your swift reply.

I don't have much option other than to modify the OutboundCallRoute / PHONE port DigitMap as one of the objectives is to make the phone behave like a POTS phone, but with least cost routing. (That way I can keep my wife happy!)

I'll try stripping the S0 out of the OutboundCallRoute (perhaps they were being ignored as it worked with them there).

RonR:
Quote from: MB.. on August 26, 2011, 07:46:33 pm

I don't have much option other than to modify the OutboundCallRoute / PHONE port DigitMap as one of the objectives is to make the phone behave like a POTS phone, but with least cost routing. (That way I can keep my wife happy!)


I don't know why you say that.  The least cost routing can be accomplished in the ITSPx DigitMap with no modifications to the PHONE Port DigitMap and OutboundCallRoute.  Why do you think you can't accomplish the subsitutions you need in ITSPx?

RonR:
If you'd like to give me the exact routing criteria you'd like to have followed between the PSTN and VoIP provider, I'll try to give you an example.

Navigation

[0] Message Index

[#] Next page