Syntax for InboundCallRoute

<< < (2/2)

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.

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.

Navigation

[0] Message Index

[*] Previous page