News:

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

Main Menu

Syntax for InboundCallRoute

Started by onmyword, September 29, 2012, 12:45:31 PM

Previous topic - Next topic

onmyword

I've searched the web and just cannot find the syntax for the special chars used in the InboundCallRoute string.  Must be some keyword I'm not sure of but I'm stumped...

anyways I was wondering what these meant or if someone has a developer syntax link to share.



(x|xx|xxx|xxxx|xxxxx|xxxxxx|xxx555|555|000|un@@.|anon@@.|restri@@.|UN@@.|ANON@@.|RESTRI@@.|?)   


x = digit
? = i'm guessing means empty
@ = no idea
. = no idea




Goal:  Catch bad people from waking me up and send them straight to voice mail without ringing my phone.

Side question: Would there be a way to do the above, but then say whitelist a specific number?

Thank you!
Howard

ianobi

This post explains the basic idea:

http://www.obitalk.com/forum/index.php?topic=4067.msg27103#msg27103

x = digit
? = blank or no Caller ID
@ = any number or letter
@@. any number or letter followed by one or more numbers or letters

Black listing is easier that white listing, unless you really only have a few numbers you wish to allow calls from and you are happy to ban all other calls.

onmyword

#2
Thanks ianobi, In your previous post it mentions Peer Number.

Does that InboundCallRoute string try to match against both peer name and number ?

The main purpose of my filtering is to also block something like so:

(Taken from a POTS Caller ID Phone)

Caller Name:
Caller Number: 416-142-2342

Note:  Where the Caller Name is Blank but the rest is valid

Would this soultion also fit that bill ?


ianobi

If you look in your OBi Call History, it shows Peer Name and Peer Number. All call routing, call barring etc depends on using what is shown in Peer Number. Peer Name has no effect.

In your example if the Peer Number shows as 4161422342, then adding that to the list would ban that number. Your InboundCallRoute might look something like:

{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|4161422342|un@@.|anon@@.):},{ph}

This method sends the call to the "bit-bucket". That is your OBi appears to not exist. Callers should get fast busy, "number unavailable" etc.

Busthead

Quote from: ianobi on September 29, 2012, 01:20:47 PM
This post explains the basic idea:

http://www.obitalk.com/forum/index.php?topic=4067.msg27103#msg27103

x = digit
? = blank or no Caller ID
@ = any number or letter
@@. any number or letter followed by one or more numbers or letters

Black listing is easier that white listing, unless you really only have a few numbers you wish to allow calls from and you are happy to ban all other calls.

Hello,

I would like to deny all / block all incoming calls excluding a very select list (basically only mum and mum-in-law call the home phone).

PrimaryLine = PSTN
Google Voice is configured as SP1

My understanding is that I must purchase the Caller ID service from my PSTN provider and configure the LINE-InboundCallRoute to:

{(MInboundWhiteList):ph)},{(x.|un@@.|anon@@.):}

where InboundWhiteList is a User Defined DigitMap such as (mums#|mum-in-laws#)

Is this correct?

Thanks!

Lavarock7

Could you use an Automated attendant that offers option 1 and 2 and tell your family to use "9"? That would route the call and all other digits could go to voicemail or a null connection.
My websites: Kona Coffee: http://itskona.com and Web Hosting: http://planetaloha.info<br />A simplified Voip explanation: http://voip.planet-aloha.com

ianobi

Busthead,

There is one too many ) in your rule.

{(MInboundWhiteList):ph}

On its own will do what you want. It is very restrictive, but if that suits you then fine. You can put up to 512 digits into a DigitMap, so there's room for more numbers.


Busthead

Quote from: ianobi on December 07, 2012, 06:52:26 AM
Busthead,

There is one too many ) in your rule.

{(MInboundWhiteList):ph}

On its own will do what you want. It is very restrictive, but if that suits you then fine. You can put up to 512 digits into a DigitMap, so there's room for more numbers.



Much thanks. Am I understanding correctly that the phone may ring once before any number that is not included in InboundWhiteList is blocked?

If so, is there a way to delay the routing of all calls so that blocked calls never ring and whitelisted calls don't ring the phone until the second ring?

Thanks!

ianobi

There should be no problem. The Line Port RingDelay delays the OBi phone being rung until after the CallerId has been processed, so unwanted CallerID calls should be rejected before the OBi phone rings.

I would say, that I have not heard of anyone doing this on the incoming PSTN line, so it would be interesting if you would post the results here.