Issue #1:
I'm assuming that if you dial 19002345678, then you get fast busy. However, if you dial **219002345678, then the call goes out on sp2 as shown by your Call History. I'm having to make some educated guesses here! I guess that looking at the sp2 DigitMap:
sp2: ((Mste)|<00:>xx.|<011:>xx.|xx.|(Mipd)|[^*#]@@.)
The OBi Digit Map Processor may be processing the xx. and/or the [^*#]@@. rules before processing (Mste). This would allow 19002345678 through the DigitMap. It would be interesting to see the results for the following tests:
1. Remove xx.|(Mipd)|[^*#]@@. from the sp2 DigitMap. Dial **219002345678 and see what happens.
2. Change sp2 DigitMap to:
((Mste)|!1900xxxxxxx|<00:>xx.|<011:>xx.|xx.|(Mipd)|[^*#]@@.)
Dial **219002345678 and see what happens.
You may well be adding to our forum knowledge base here
Issue #2:
sp1: ((Mste)|<**2>00xx.|<**2>011xx.|<00:>00xx.|<011:>011xx.)
This will not work due to conflicts with the **2 rules and the fact that OBi processes the DigitMap twice – first in the Phone Port DigitMap, then in the Phone Port OutboundCallRoute. So <00:>00xx. would result in only xx. going to sp1.
You could try something very unusual:
sp1: ((Mste)|<**2>00xx.|<**2>011xx.|<RAJ>09xx.|<RAJ09:>xx.)
Prefix your codes with 09, so you dial 0900xx, 09011xx. Any number starting with 09 willl have RAJ prepended to it when it is processed through the Phone Port DigitMap. Then when that number is processed through the Phone Port OutboundCallRoute the RAJ09 will be removed and the rest of the number sent to sp1.
Issue #3:
On the SP2 digitmap, <00:>xx. does strictly match numbers dialled that start with 00
Interesting questions! We can all learn something here