Worldwide Locations
102 Results Found
Where should you apply the CSS, and why are there two places to apply it? One approach is to pick one of the parameters and apply the permissions there. Quite often, an administrator will pick the phone-level CSS and configure it there so that it applies to all calls made from all lines. The goal is to specify what partitions are allowed to be called.
For smaller companies, configuring a dial plan to account for variations in dialed numbers is often not a problem. However, companies that are larger and more global in nature encounter a number of issues when designing their dial plan approach.
Border Gateway Protocol (BGP) is a fascinating protocol because there are a lot of things that can be done with BGP. However, there has always been an issue with BGP, which is convergence (the time the network or protocol takes to accept change). BGP was designed for scale, not speed, so it’s something that we’ve had to tolerate from its inception.
License provisioning has always been a bit of a challenge in the CUCM environment. Prior to CUCM v9.0, licensing was managed on a per-cluster basis with each cluster requiring its own license files that were tied to the media access control (MAC) address of the cluster’s publisher. This approach to license management was limiting in the fact that one cluster might have unused licenses while another cluster may be at its limit and sharing between clusters was not possible.
Occasionally I am asked to configure the ability to block calls based on Caller ID. Prior to Cisco Unified Communications Manager (CUCM) v8, the only way to block these calls was to configure voice translation rules and profiles on the gateway receiving the calls. This has changed in CUCM v8 with the introduction of an additional parameter in translation patterns: Route Next Hop By Calling Party Number.
While most organizations have not yet fully (or in many cases even partially) adopted cloud computing, the trend is growing in all but the smallest businesses.
Spanning Tree Protocol (STP) is dead, or at least it should be. It’s too slow to converge when there’s a change, and it causes issues with performance because there is only one forwarding path. It was developed in 1985 by Radia Perlman at Digital Equipment Corporation to allow for redundant paths within a Layer 2 topology, which was great in 1985. In fact, it was huge! So much so, that it was later standardized by the IEEE as 802.1D, and we’ve been living with it ever since.
RTMT provides a set of canned views of both system resources and application counters that provide you with a snapshot of your environment right out of the box. Read on to learn how you can make RTMT even more helpful by customizing it to show you different views of your resources and CUCM environment.
Many companies are already using VoIP while incorporating video capabilities into their portfolio of services. One question that I am often asked is, “How can we ensure that the voice and video quality is good and consistent when using VoIP?”
If you’re in IT, you’ve likely heard the saying, “In technology, the only thing constant is change itself,” and boy is that right! For technical companies, if you are not moving forward, then you’re falling behind. There is no such thing as standing still! A perfect example of this mindset is in Cisco’s evolution of video conferencing and telepresence.