Is there any block list?
dealyanodeal:
I was using x.720####### as this was the way my rule 1 of inboundcallroute was setup by obitalk.As mentioned earlier I had 720####### set as a trusted phone no. on the obitalk and that probably setup the first rule to forward any call from x.720####### to AA. I have setup 720###### as trusted by behind the scene obi used it as x.720####### in the rule 1 of the inboundcallroute for line1. I belive x.720####### means 720####### preceeded by any digit and even if caller id is 1720####### it should still catch it.
Want to mention again ####### represent the actual digits from the cell phone no.
As you pointed out I didnt use the '(' and that might be causing the problem. I will try with '(' and also with 'x.' and post the results
thanks for all the help
MichiganTelephone:
Also, instead of outright blocking a number, I think it is possible to send them someplace else. For example, I believe that a rule like {?:sp1(12484345508)} would take a call with no caller ID (the question mark) and send it out sp1 to 12484345508 (if that number is still what it was two or three years ago, a telemarketer will not appreciate you sending them there!). Note, however, that the second leg of the call is on your nickle.
MichiganTelephone:
Quote from: dealyanodeal on March 16, 2011, 10:08:19 pm
As you pointed out I didnt use the '(' and that might be causing the problem. I will try with '(' and also with 'x.' and post the results
I found an example in the documentation using the leading x. and parenthesis (right under the previous one I quoted - guess I should have read a bit further):
{(x.4081113333|x.4152224444):aa},{ph}
So maybe it is just that you need parenthesis in your second rule:
{(x.720#######):aa},{(x.720#######|1888xx.|?):},{ph}
The actual section from the documentation says:
Quote
3) {(x.4081113333|x.4152224444):aa},{ph}
It says: Ring the AA for calls coming from any number that ends with 408 111 3333 or 415 222 4444, and ring the PHONE
Port for all other calls. Be sure to include the enclosing parentheses in this example since “x.” is a digit map specific syntax.
So yes, adding the parenthesis may indeed be the fix.
dealyanodeal:
ok..here are the results.Could only try with 1 cell no with caller id on and off.
This worked
{(x.720#######):aa},{(x.720#######):},{ph}
Above setting made the destination phone not to ring at all eventhough the caller was getting call rings. Caller eventually got forwared to voice mail. There was neither a missed call on the phone nor the call showed up in the call history of obi. Pretty cool.
This didnt
{(x.#######):aa},{?:},{ph}
no caller id showed up on the destination phone but the was no block.
Not sure why anonymous call block is not working.
I will next try to block multiple no's and also block call forward and post results
MichiganTelephone:
Quote from: dealyanodeal on March 16, 2011, 10:35:46 pm
This worked
{(x.720#######):aa},{(x.720#######):},{ph}
.....
This didnt
{(x.#######):aa},{?:},{ph}
no caller id showed up on the destination phone but the was no block.
Not sure why anonymous call block is not working.
Try adding |? in the blocking rule:
{(x.720#######):aa},{(x.720#######|?):},{ph}
The question mark might need to be enclosed in parenthesis, or we might have found a bug!
Navigation
[0] Message Index
[#] Next page
[*] Previous page