Is there any block list?
dealyanodeal:
I tried the above mentioned config change and it doesnt seem to be working. I used following in the inbound call route for line port.
{(x.720#######):aa},{x.720#######|1888xx.|?:},{ph}
(for privacy replaced digits of my actual phone no by #s).
I tried to put one of my cell phone as blocked and another cell phone is a trusted one and gets picked up by AA. When it didnt work, I tried to play with first rule (e.g changed the no) and that did have the desired effect so that tells me the first rule is correctly configured to route the call to AA. Not sure why 2nd rule is not working correctly.
any suggestions?
dealyanodeal:
Did another test.
1)
on my cellphone that goes directly to AA, chose the option not to send the caller id
dialed obi from the cell phone and it didnt send the call to AA as obi didnt get the caller id.
I did that to make sure caller id(and absence of it) was working correctly with obi.
then
2)
Switched the blocked no with the no that goes to AA. that means the phone no that was used in step 1 is now blocked.
called obi again. obi should have blocked the call because of anonymous call block but it didnt
RonR:
This is a total guess (and probably not the answer), but try:
{(x.720#######|1888xx.|?):}
I've not used the ? operator, so this is shooting from the hip.
QBZappy:
RonR,
1) I waS thinking about your call block strategy. Your strategy picks up the CID and drops them in a void. This approach makes a lot of sense. To make it interesting for telemarketers that make it on the block list, we could redirect them to a FCC phone number. That would certainly confuse them. If there was an IVR which we could record sound we could then direct them to recorded busy sounds, etc... Can you think of a way to deliberately send a call to a broken call path which could reproduce a busy or other tone?
2) How about the opposite of that. We might want to block out going numbers from being dialed. In an earlier thread I had discussed using the "!" character in front of a phone number. This character will block numbers from being dialed out. I had used it in this way: (Taken out of context)
{(x.218xxxxxxx|x.809xxxxxxx|!x.514xxxxxxx|!x.450xxxxxxx):sp1}
This particular strategy was to block any numbers with area code 514 & 450 from going over the SP1. I later allowed them to go over to SP2 as per the design of the user.
MichiganTelephone:
My first question is, why are you using x.720####### as a pattern? I may be wrong but I don't think that will match anything. You probably should be using 1720####### unless I'm missing something here. Try changing that, and if it still doesn't work, then just as a test try changing the order of the rules to put your block list first:
In other word, sticking with your examples, first try:
{1720#######:aa},{1720#######|1888xx.|?:},{ph}
And if that doesn't work...
{1720#######|1888xx.|?:},{1720#######:aa},{ph}
One other point, I think that you and RonR may be making the same error, in that you're confusing InboundCallRoute syntax with DigitMap syntax. They are similar in many respects, but not exactly the same. Oh, and the question mark matches "no Caller ID."
Navigation
[0] Message Index
[#] Next page
[*] Previous page