Incoming calls to unallocated numbers

[Michael Horton]

We are getting calls routed from our service provider to numbers that they provide us but are not configured in our CallManager (10.5.2).  No translation patterns or any other programming is attached to these numbers.  The calls are jamming up the RTMT logs and are just a nuisance to wade through.  Is there a practical and somewhat painless way to block these calls from getting logged?  There are well over a hundred potential numbers that this could involve, so creating individual translations to block them would not be painless!  Thanks.

[Brandon Buffin]

Are there blocks of numbers that would allow you to create only a few translation patterns? Such as 11122234XX to cover numbers 1112223400 to 1112223499.

Brandon

[Venkatesh Perumal]

Hi Michael,

i dont think we can stop the calls being logged in rtmt, but certainly as stated can apply the call blocking in cucm on the basis of calling party number. you can refer the below link for the same.

http://www.netcraftsmen.com/cisco-cucm-blocking-calls-by-calling-party-number-id/

or you can speak to your SP once if they can stop routing the calls.

-Venkatesh

[Nadeem Ahmed]

How is Gateway is being controlled by Call_manager. If its h.323 simply creating the Translation pattern for range . You can check the Range of the number and can block on GW itslef rather than doing CUCM.

If its MGCP then you need to apply on CUCM method would be the same but can defined MASK of the range of the number which is being routed by your Service provider.

Br,
Nadeem

[devils_advocate]

You can block incoming calls on your Voice Gateway, assuming that is how the calls route in.

voice translation-rule 1
rule 1 reject /^01234111222/
!
voice translation-profile Block
translate called 1
!
dial-peer voice 1 voip
call-block translation-profile incoming Block
call-block disconnect-cause incoming invalid-number
!

This would need to be applied on the inbound dial peer.
Obviously adjust it to suit your needs.

Thanks

[Roger Kallberg]

Hi,

A option would be to add a partition that holds a translation pattern that matched your entire DID range with the route option set to "Block this pattern: Unallocated number. You put this PT in a new CSS that has this PT and also the PT for your DNs in the order below.

Incoming_GW_CSS
 Unallocated_PT
 DN_PT

Set this CSS as the incoming CSS on your GW or trunk if you use SIP as the control protocol for your voice gateway.

The TP will only be in use if CM can't find a more exact match, ie if there is no DN that has this number. This way you don't need to worry about any administration for this when you add or remove extensions.

Sincerely

Roger