[cisco-voip] CUCM 8.1.3 > Blocking inbound calls

Eric Pedersen PedersenE at bennettjones.com
Tue May 12 17:48:24 EDT 2015


Do you have a bug ID for this? We have Attendant Console and haven’t seen this. I’m curious what the conditions are.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: 12 May 2015 3:11 PM
To: Brian Meade
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 8.1.3 > Blocking inbound calls

Calls come into operator using Attendant Console.  She looks up a name in client software does a transfer to an end user phone inside.  This is a CTI Redirect which fails (similar for CER).  We went up to BU and they have no current roadmap to resolve this.


From: bmeade90 at gmail.com<mailto:bmeade90 at gmail.com> [mailto:bmeade90 at gmail.com] On Behalf Of Brian Meade
Sent: Tuesday, May 12, 2015 5:00 PM
To: Jason Aarons (AM)
Cc: James Dust; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM 8.1.3 > Blocking inbound calls

The way I do it is create a new partition that only lives in the gateway CSS so it shouldn't have any impact on anything besides incoming calls from the gateway.

On Tue, May 12, 2015 at 3:26 PM, Jason Aarons (AM) <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>> wrote:
The Blocking Calls based on Calling Party Number has issues with CTI Redirects (UCCX/CER/Attendant Console) in that they won’t work on transfers to agent/phone/operator.  If you don’t use any CTI apps you would be good.

In IOS you can do a translation rule to reject but it’s limited to 100 rules.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Brian Meade
Sent: Tuesday, May 12, 2015 2:08 PM
To: James Dust
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM 8.1.3 > Blocking inbound calls


If you're using H.323 or SIP for the voice gateway, easiest to block inbound via translation-profile on the incoming dial-peer.

If you have a lot of numbers you want to block or are using MGCP, you can do it in CUCM- https://supportforums.cisco.com/document/71966/blocking-calls-based-calling-party-id?page=1<https://supportforums.cisco.com/document/71966/blocking-calls-based-calling-party-id?page=1>



On Tue, May 12, 2015 at 1:52 PM, James Dust <james.dust at charles-stanley.co.uk<mailto:james.dust at charles-stanley.co.uk>> wrote:
Evening all,

I have had a request to block a specific number from being able to dial into our cluster, but have nothing currently setup to accomplish this.

The gateway is a Cisco C2921 running SPA.154-2.T.bin

Is it achievable to block the call on the gateway, or configure this somehow on CUCM.

Any assistance appreciated.

Regards

James


Consider the environment - Think before you print

The contents of this email are confidential to the intended recipient and may not be disclosed. Although it is believed that this email and any attachments are virus free, it is the responsibility of the recipient to confirm this.

You are advised that urgent, time-sensitive communications should not be sent by email. We hereby give you notice that a delivery receipt does not constitute acknowledgement or receipt by the intended recipient(s).

Details of Charles Stanley group companies and their regulators (where applicable), can be found at this URL http://www.charles-stanley.co.uk/contact-us/disclosure/<http://www.charles-stanley.co.uk/contact-us/disclosure/>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://puck.nether.net/mailman/listinfo/cisco-voip>



itevomcid
 
 
The contents of this message may contain confidential and/or privileged 
subject matter. If this message has been received in error, please contact 
the sender and delete all copies. Like other forms of communication, 
e-mail communications may be vulnerable to interception by unauthorized 
parties. If you do not wish us to communicate with you by e-mail, please 
notify us at your earliest convenience. In the absence of such 
notification, your consent is assumed. Should you choose to allow us to 
communicate by e-mail, we will not take any additional security measures 
(such as encryption) unless specifically requested. 

If you no longer wish to receive commercial messages, you can unsubscribe 
by accessing this link:  http://www.bennettjones.com/unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150512/f38c0165/attachment.html>


More information about the cisco-voip mailing list