Auto Attendant based on number called

[Hortoristic]

I'm still trolling through the forums, but trying to see if only when I call one of my DID's on my OBI202, will it match my caller ID and answer with AA?

I have:
SP1 = GV
Sp2 = voip.ms DID
SP3 = Callcentric
SP4 = UK DID

I only want AA to prompt me when I call the specific Callcentric DID and match on a specific caller ID number.

This way I can continue call home which defaults to SP1 from my work, but if I call the Callcentric number, my AA will answer, and I can enter a new number to dial.

I'm using the web interface, not OBITalk - can someone direct what strings to change?

Thanks

[azrobert]

Voice Services -> SP3 service ->
Add to the beginning of X_InboundCallRoute:
{(4801234567):aa},

Any inbound call on SP3 (Callcentric) with CallerID 4801234567 will be routed to the AA.

[Hortoristic]

How do I do this if I'm using SIP instead of registering CC on my OBI?  Doesn't it just ring port 5061?

Also; to cut out the SIP Scanners, I have below in my X_InboundCallRoute
{(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph1}

How do I add your logic to the string, where do I insert the: {(4801234567):aa}

Does it end up like this:
{(19142960000):aa},(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph1}

[tvBilly]

Does it end up like this:
{(19142960000):aa},(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph1}

Looks like you're missing a { in your newly constructed string). I think* what you want is:

{(19142960000):aa},{(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph1}

*(I'm just getting started with my Obi200, so I could be wrong...)

[ianobi]

{(19142960000):aa},{(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph1}

Looks good to me.


You could convert to the Oleg method to defeat sip scanners and use:
{(19142960000):aa},{>(17770001234):ph}

17770001234 is whatever appears in this value:
Voice Services > SP3 Service > SIP Credentials > AuthUserName

[tvBilly]

What does the > signify in the {>(17770001234):ph} fragment?

[ianobi]

tvBilly,

The simplified format of an InboundCallRoute is:

{caller>callee:terminal}

If you omit the callee, which is a common situation, then you can omit the > thus:

{caller:terminal}

In this case we are not specifying any callers, so the > needs to be there to tell OBi the next item is a callee thus:

{>callee:terminal}


In practice both caller and callee can be lists or digit maps. There can be up to four terminals separated by commas.

[ianobi]

You could convert to the Oleg method to defeat sip scanners and use:
{(19142960000):aa},{>(17770001234):ph}

I don't know why, but we all seem to have got into the habit of using too many parentheses. They are only required if caller or callee is a digit map. The parentheses do no harm. This works fine:

{19142960000:aa},{>17770001234:ph}

If we can, then let's keep it simple!