Whitelisting and blacklisting numbers @ MGCP gateway

[Wayne Ficklin]

We have 2 MGCP gateways, controlling 3 PRI cards each.  We own an entire block of numbers.  Is there a way using the MGCP gateway to

1. only accept calls TO our block of numbers? (###-###-XXXX, where we own all of ###-###)  We're experiencing a T(elephony)DoS event for the 2nd time where calls that don't belong to us are being sent to us via PRI.  The call comes in, UCM sees that its to a number that's not registered to UCM, and sends the call out.
2. block calls FROM our block of numbers INBOUND?  (That is to say, at no point should one of our numbers REACH US from the PRIs, so we'd like to drop that call at the gateway.)

[Jaime Valencia]

MGCP just passes the information to CUCM to determine what to do with the call, so, there's no way you can drop anything at the GW if you use MGCP, you would need to migrate to SIP to actually do some call processing at the GW and drop calls there.

If you get a call for a DN that doesn't belong to you, and you route it back to the PSTN, check your CSS and partitions, most likely your inbound CSS has access to route patterns going to the PSTN and that would be caused by whoever configured that. Usually the inbound CSS should only allow internal DNs or other call controls agents for things like toll bypass. I'd also discuss with your telco exactly how they're letting that happen, as inbound routing on those PRIs is your telco's responsibility.

[Roger Kallberg]

Apart from the great advice given by Java you should have a look at this great document by Dan Keller. Blocking Inbound calls to Cisco Unified Communications Manager based on Caller ID 

[Nithin Eluvathingal]

Regarding the point number 1, Open a ticket with ISP. it seems they have some routing issues. They should never send calls to your PRI other than your DID range.

Regarding the point number 2 refer the doc @Roger Kallberg  shared.

2.12.0.0