News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Predifined callroute calls being intercepted by Pli

Started by mrjoe, November 13, 2012, 01:53:02 PM

Previous topic - Next topic

mrjoe

I'm trying to call 079xxxxxxxx but it is being intercepted by my Pli which is ObiBT

DigitMap: (<*18>(Mvg8)|<*17>(Mvg7)|*054|*663|(Miln)|<**1>(Msp1)|<**4>(Msp4)|<*12>(Mvg2))

I dialled *14079xxxxxxxx it should remove *14 and put the call through vg5, but as you can see from the call history, it tried to get ObiBT to call *14079.

Call 1 11/13/2012    23:42:18  
23:42:18 From PH1 To BT1(*14079)  
23:42:24 Call Ended


Phone Port:

DigitMap: ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|**0|***|#|**1{t=di}(Msp1)|**2{t=di}(Msp2)|**3{t=di}(Msp3)|**4{t=di}(Msp4)|**8{t=di}(Mbt)|**9{t=di}(Mpp)|*11{t=di}(Mvg1)|*12{t=di}(Mvg2)|*13{t=di}(Mvg3)|*14{t=di}(Mvg4)|*15{t=di}(Mvg5)|*16{t=di}(Mvg6)|*17{t=di}(Mvg7)|*18{t=di}(Mvg8)|(Mpli))

OutboundCallRoute: {([1-9]x?*(Mpli)):pp},{(<#:>):ph2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**8:>(Mbt)):bt},{(<**9:>(Mpp)):pp},{(<*11:>(Mvg1)):vg1},{(<*12:>(Mvg2)):vg2},{(<*13:>(Mvg3)):vg3},{(<*14:>(Mvg4)):vg4},{(<*15:>(Mvg5)):vg5},{(<*16:>(Mvg6)):vg6},{(<*17:>(Mvg7)):vg7},{(<*18:>(Mvg8)):vg8},{(Mpli):pli}

I must have made some silly mistake but I can't figure it out.
Please could someone help.

mrjoe

Miln does contain *xxxxx but that shouldn't come in to the equation as the Phone port DigitMap should steer it away from that route.

ianobi

Mrjoe,

Your DigitMaps are always a challenge, although I think they may be getting a little more simple now you have an OBi202  :)

Your PhonePort DigitMap seems force any number not starting with a * into your Mpli. When you dialled 079xxxxxxxx, what does Call History show for Phone Port and whatever sp/vg it went out on? Is there a DigitMap within Mpli that will match 079xxxxxxxx numbers?

I think there may be a typo here:
QuoteI dialled *14079xxxxxxxx it should remove *14 and put the call through vg5, but as you can see from the call history, it tried to get ObiBT to call *14079.
*14 should have sent it to vg4. Either way it went the wrong way!

mrjoe

Hi ianobi,
Thanks for responding to my plea for help.

I do have 079xxxxxxxx in ObiBT's call route, they go through vg7, I wanted to use a different VG on that occasion and selected it by dialing *14 before the number.
VG4 does have mobile number is it's DigitMap.

ianobi

I cannot see any obvious problems with the DigitMaps etc that you posted. It would seem that 079xxxxxxxx is not getting matched in Mvg4, so some other DigitMap in Mpli is matching it.

It is odd that *14079 went out to BT. If Miln was involved, then I would expect the rule *xxxxx to become a Mis-Match after digit number six was dialled.

It might be worth deleting Miln then testing again to see if it is the problem, even though it does not look logical.

Another mystery to be solved  ::)