Hi Eric,
There is a way to do this, but it's not something you'd want to undertake on a live system. You could do it if building a system from scratch, certainly not using CCA and requires a thorough understanding of inbound/outbound dial-peers, dial-peer matching, number translations and voice security. It would also help if the Service Provider could prefix all incoming numbers with an Alphanumeric character sting such as AAA or similar for easy identification. You would need to disable the "permission term" dial peer. I've used the technique in reverse where I wanted to route calls out of certain trunk groups, based on the extension number making the call and COR was not practical.
Start with a router with no dial-peers configured.
The procedure would be:
1. An incoming call would always match a known incoming dial peer you have configured.
2. Instead of the call being routed to an extension or AA, you would then send the call out of a dial-peer with an H323 target of itself (the same router). At the same time using number translations to prefix the dialled number with for-example "AD". Use codec transparent on the dial-peers
At this point there is no incoming dial peer that matches calls arriving on the router with called numbers starting AD.
3. Configure a set of incoming H323 dial-peers based on "answer address". If the Answer address passes certain constraints, use number translations to strip the AD from the called number and route the call to the correct place - i.e. AutoAttendant, DID etc
4. Have an incoming H323 dial-peer with an answer address that matches . Use number translations to route the call to your special voice mail box.
As I said certainly not one for a live enviroment but the technique is certainly valid.
An "Anonymous Block" keyword would be alot simpler!
Adam
