Help setting up call routes for OBi202
azrobert:
I don't see the problem.
There isn't a rule in the ITSP A DigitMap that will match an 11 digit number beginning with "9", so it shouldn't get routed to SP1.
It does have a rule that will match 933, but it shouldn't match an 11 digit number starting with 933.
Try dialing a number that doesn't begin with 933 and see what happens.
jadog:
Same thing. Here's the log.
From PH1 To SP1(92608441605)
Ok, how about this instead. Not sure if it's possible, but can we adjust the failover so that SP1 fails over to SP4? In other words if Anveo has a disruption in service, it will failover to GV. That's basically the only reason I have GV setup anway. Then I can always still use the **4 in front to force it through instead of the 9.
azrobert:
Anveo is already setup to failover to GV. ITSP A and D both have a rule to match 11 digits. When dialing 11 digits the TG will process the trunk list left to right. It will match 1xxxxxxxxxx in ITSP A first and try to route the call to SP1. If SP1 fails, the TG will try the next entry in the trunk list (SP4). It will match 1xxxxxxxxxx in ITSP D and try to route the call to SP4. The config I gave you will only failover 11 digit numbers. 10 digits will also work because it will be converted to 11 digits before this process begins. If you want to failover international calls, add 011xx.S3 to the ITSP D DigitMap.
I removed the **4 code because I didn't think you would need it. Instead of adding back **4, let's try to fix the 9 prefix by processing it outside of the TG.
Use the following Phone Outbound Route:
{([19]900xxxxxxx):},{(<9:1>xxxxxxxxxx):sp4},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<#:>):ph2},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Now try 9 followed by 10 digits.
jadog:
Ok, so that works perfectly and the call was routed through Google Voice. What does that mean?
azrobert:
The call is routed to the TG by the last rule in the outbound route, {(Mpli):pli}
pli points to the Primary Line, so the above rule gets translated to: {(Mtg1):tg1}
TG1 wasn't processing GV calls correctly, so I fixed the problem by adding another rule before the last rule to process GV calls outside the TG.
I can only think of 3 possibilities:
1. I don't see the coding error
2. I don't understand how trunk groups work
3. There is a bug in the firmware
What firmware level are you running?
If you're not at the current firmware level, you can try upgrading.
Navigation
[0] Message Index
[#] Next page
[*] Previous page