News:

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

Main Menu

Need help with X_InboundCallRoute syntax

Started by JayDCarter, June 05, 2015, 08:30:04 AM

Previous topic - Next topic

JayDCarter

Hello,
  I am trying to configure an Obi v508 to route inbound calls placed to a specific DID, to a specific phone port. All other calls should go to a hunt group. I am using only one ITSP and SP1 . Outbound calls are working fine, and inbound calls will ring the huntgroup if I include the default {gp(1)} rule in X_InboundCallRoute .

Let's use DID 5085551234 as the example..The syntax I have tried is:
  X_InboundCallRoute {@>8055551234):ph3},{gp(1)}

...I test it first with just {@>8055551234):ph3} in place and no calls are answered at all.

I have also tried {@>8x.551234):ph3} - same result.

Can someone please point me in the right direction?

Thanks,
JDC

azrobert


azrobert

It didn't feel right giving my short response, so here is a detailed explanation.
There are 2 values (CallerID and AuthUserID from the provider) passed on an inbound call when registered to a provider.
This is the format to check for these values:
{ CallerID > AuthUserID : Dest }
Checking for the values is optional like:
{ > AuthUserID : Dest }  or {dest}

When the value is enclosed in parentheses it becomes a DigitMap.
In a DigitMap reserved characters have special meaning.
My above example the 1? is optionally checking for a 1 prefix, so it will work with 10 or 11 digit CallerIDs.

When the parentheses are omitted the value becomes a literal.
Your rule has a valid syntax, but you were check for a CallerID equal to the literal "@>8055551234)"

JayDCarter

Great! Thanks...I will be on-site with the device and try it out next week.

JDC