Regardless of the vendor, when we discuss call routing in a telephony platform we’re almost always focused on the destination of the call. Similar to how the postal service operates, when the system is delivering the call or message, we are rarely focused on who the originator is. Keeping that in mind, it doesn’t take much imagination to come up with a few scenarios where it may be beneficial to block specific numbers, or ranges of numbers from reaching your end users.

In this blog post, I’ll show you how to implement a check on the calling party number (CPN) in a Cisco voice solution and keep those pesky spam calls at bay.

In order to illustrate the logic, let’s define some key components and run through a few examples.

Cisco Systems flagship contact center, Unified Contact Center Enterprise or UCCE, has long been heralded as one of the best in its class for resiliency and redundancy. The system has been fully fault tolerant with the capability of being geographically dispersed between two data centers. Well, for the most part that is, because there has…

On October 14, 2015, Cisco released Field Notice 64029 with updates on November 3, 2015. Here’s everything you need to know about this issue that affects Cisco UCS C220 M4 and C240 M4 servers. The field notice addresses and expands upon Cisco Bug CSCuv33991

While every organization’s priority for technology consumption is different, this solution offers up flexibility and customization to meet your needs.  Along with what everyone uses (dial tone and voicemail); Cisco Unified Communications Manager Business Edition 6000 includes many applications to wet your appetite. Starting with as few as 25 end users, the solution can scale…