Outbound Call Route help
azrobert:
OutboundCallRoute:
{(911|933|1(226|519)xxxxxxx):sp1},{(Msp3):sp3},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
FYI the dialed number is validated by a combination of the Phone and Primary Line digit maps. Translation can occur during validation then the outbound route will route the call to a provider. Rule “<1>[2-9]xxxxxxxxx” in the SP2 digit map will convert 10 digits to 11, so the above will work for both 10 and 11 digit numbers.
azrobert:
Add "|933" after "911" in the phone DigitMap
sviv:
Quote from: azrobert on December 23, 2020, 08:17:32 pm
OutboundCallRoute:
{(911|933|1(226|519)xxxxxxx):sp1},{(Msp3):sp3},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
FYI the dialed number is validated by a combination of the Phone and Primary Line digit maps. Translation can occur during validation then the outbound route will route the call to a provider. Rule “<1>[2-9]xxxxxxxxx” in the SP2 digit map will convert 10 digits to 11, so the above will work for both 10 and 11 digit numbers.
azrobert,
thank you for your help, I will give it a try and report back.
I am trying to understand how all this work so maybe one day I can be more independent. Can you confirm if I understand the dialing process sequence correctly?
1. When you start dialing first thing being checked is Physical Interface PHONE 1 OutboundCallRoute
2. Next Physical Interface PHONE 1 DigitMap is verified
3. Next, if OutboundCallRoute request is within parameters set in PHONE 1 DigitMap then its directed to SPx DigitMap (based on OutboundCallRoute rule)
4. Next SPx DigitMap is checked against the dialed number and if the dialed number parameters are within parameters set in the SPx DigitMat the call is placed through that SP.
Does this even make sense?
Is there a document that explains this process I could refer to?
TIA
azrobert:
The Phone DigitMap gets control first and validates the dialed number.
The last rule, “(Mpli)” includes the Primary Line’s digit map rules.
Substitution can happen here.
If the number matches more than 1 rule, the “Best” rule will be used, not the 1st.
If the number doesn’t match a rule, you will get a busy.
If the number matches a rule, the outbound route gets control.
The outbound call route processes the rules between the “{ }” left to right.
If substitution occurred in the digit map, the OCR will see the transformed number, not the original dialed number. People get in trouble because they don’t understand this behavior.
If the dialed number matches a rule, the call is routed to a provider and processing stops.
Substitution can also happen in the OCR.
The last rule “(Mpli):pli” will route the call to the primary line.
If you want to route a call to a provider other than the primary line without “**n”, you must include additional code.
If the number doesn’t match a rule, you will get a No Routes Available error.
Trunk Groups can be used for automatic failover or just routing when you have multiple providers.
Trunk Groups work the same up to routing.
TG definition can be found at Voice Services/Gateways and TGs.
When the Primary line is set to TG1, rule “(Mpli):pli” routes the call to TG1.
The TG will process the SPs in the Trunk List left to right.
Substitution can also happen here.
If the dialed number matches the SP’s digit map, the call is routed to that provider.
If the call fails or the number doesn’t match the digit map, processing switches to the next SP in the List.
sviv:
Thank for clarification, I will have to process this over the holidays and see if I am capable of understanding all this stuff.
Navigation
[0] Message Index
[*] Previous page