Blocking with InboundCallRoute & Forking Problem

[SeanC]

OBi200, v1.4, firmware v3.0.1 (Build: 4350)

Trying to add a blocklist to my inbound route and having difficulty in two areas:

1) my blocklist configuration isn't working, tried with both User Defined DigitMap (preferred) and directly adding the numbers into the InboundCallRoute field.  I have SP1 configured with SIP provider, SP2 configured with GVoice.

SP1's X_InboundCallRoute (the auto-attendant entry works fine):

Code Select Expand

{(x.5035551212):aa},{(MTelemarketers):},{ph}

User Defined Digit Map2:

Code Select Expand

Label: Telemarketers
DigitMap: (x.3035551234)


2) testing the config, my incoming calls not only ring through, but fork to both SP1 and SP2:

Call 1    From GT2(13035551234)
   Fork to:
    PH1
    GT2(mygoogleaccount@gmail.com/obidev.v10DCEAFA3C)
    Ringing (PH1)
    Ringing (GT2(mygoogleaccount@gmail.com/obidev.v10DCEAFA3C))

PHONE Port OutboundCallRoute:

Code Select Expand

{911:sp1},{933:sp1},{([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:><*67>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}

My AutoAttendant1 OutboundCallRoute is set to default (although appears to vary slightly from the listed default in the Device admin guide v01092013 / September 2013):

Code Select Expand

{([1-9]x?*(Mpli)):pp},{0:ph},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{(<**9:>(Mpp)):pp},{(Mpli):pli}


I feel so close but so far, what am I missing?   

Thanks in advance to you gurus!! 

[HDFLucky]

It looks like you modeled your block from Mango's guide, and if so, you have done it correctly. By any chance, is your SIP provider on sp1 Phonepower? I was never successful in getting a destination-less InboundCallRoute to work with them. If you point it to an actual destination (PSTN or SIP) or to another SIP-configured sp, it should work fine.