DigiMap Question
ianobi:
azrobert,
Quote
Test 1 (Repeat of above)
Star Code#11: *62(35941000)
Phone Port DigitMap: *6235941000
Phone Port OutboundCallRoute: {(<*:1>6235941000):sp1}
Dialed *6235941000 and call was routed out SP1
Test 2
Star Code#11: *62(35941000)
Phone Port DigitMap: *6235941000
With OutboundCallRoute rule removed I received error message "There is no call route to complete your call".
I don't think these tests are testing like with like. Try:
Test 1 (Repeat of above)
Star Code#11: *6235941000
Phone Port DigitMap: *6235941000
Phone Port OutboundCallRoute: {(<*:1>6235941000):sp1}
That way the DMP is looking at two identical numbers, which must both somehow be in the Phone Port DigitMap.
You do raise an interesting point - if there are two identical numbers in the Phone Port DigitMap (ignoring Star Codes for now) how does the DMP decide which has priority?
azrobert:
We know that the Phone Port OutboundCallRoute gets priority over the Star Code because that's what happens with our testing.
Try this test:
Test 4
Star Code#11: *6235941000
Phone Port OutboundCallRoute: {<*:1>6235941000:sp1}
If your theory is correct about the Star Code as a hidden DigitMap entry, removing the Phone Port DigitMap entry will still leave the hidden entry from the Star Code definition. You would expect the call to still be routed to SP1, but that's not what happens. I get the Star Code tone. I think this proves the Star Code is not a hidden entry in the DigitMap and the dialed number must fail the DigitMap before the Star Code processor gets control.
ianobi:
Quote
We know that the Phone Port OutboundCallRoute gets priority over the Star Code because that's what happens with our testing.
This depends entirely on how fast you dial. Pause for two seconds after *nn and the Star Code gets the priority.
Quote
Test 4
Star Code#11: *6235941000
Phone Port OutboundCallRoute: {<*:1>6235941000:sp1}
This is more interesting. It does show that only number formats allowed in the Phone Port DigitMap (visible to us) can make it to the Phone Port OutboundCallRoute. Any number matched by a Star Code will be sent to the "Star Code OutboundCallRoute"
I think we are still guessing somewhat here :) Either way we should move the debate back to the "Star Code" subject at:
http://www.obitalk.com/forum/index.php?topic=6740.msg42502#msg42502
twinclouds:
Quote from: azrobert on March 10, 2014, 07:01:57 pm
Phone Port DigitMap: (*(Mvg3)|*(Mvg4)|......current rules....)
Phone Port OutBoundCallRoute:
{(<*:>(Mvg3)):vg3},{(<*:>(Mvg4)):vg4},......current rules.......
VG3 DigitMap: (1[2-9]xxxxxxxxx)
VG4 DigitMap: (011xxxxxxxxxxxx)
You have to update the Phone Port DigitMap also.
Msp1 points to ITSP A DigitMap
Msp2 points to ITSP B DigitMap
I assumed these were coded a certain way and was trying to save some code.
Try the above.
The VG4 DigitMap will only match 011 followed by exactly 11 digits.
Is that what you want?
Hi,
I thought it worked last time. However, when I try repeat it today, the method does not work now.
I did as you said, in phone port digimap, I added (*(Mvg3)|*(Mvg4)|...original), in the phone port OutboundCallRoute I added {(<*:>(Msp1)):vg3},{(<*:>(Msp2)):vg4},{.....original}. Only the first one works, i.e., in this case, only * plus local number works but the international one does not work. If swap the order of vg3 and vg4, then the * plus 011xx...., will work but the local number does not work. I also tried to add *(Msp1)|*(Msp2)|... as you said first time. The results are the same. Any suggestions? Thanks.
BTW, in the phone port digimap, do I need to add *(Mvg3)|*(Mvg4)|... or *(Mvg3)|*(Mvg4)|*(Msp1)|*(Msp2)|...?
azrobert:
You said
Quote
in the phone port OutboundCallRoute I added {(<*:>(Msp1)):vg3},{(<*:>(Msp2)):vg4},{.....original}.
Check my instructions again. I said:
{(<*:>(Mvg3)):vg3},{(<*:>(Mvg4)):vg4}
Only add *(Mvg3)|*(Mvg4)|
Edit:
{(<*:>(Msp1)):vg3},{(<*:>(Msp2)):vg4},
The above was from my 1st suggestion that failed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page