IPexpert and Unified FX are pleased to announce the availability of PhoneView version 2, PhoneView has already set the standard for endpoint management and now raises the bar with the latest release.

Experience the most powerful remote phone technology possible with multiple phones visible and controllable in a single application/window, all updating in real-time and responding instantly to your commands. Not only is this the best application for CCIE Voice study, it’s used by thousands of Cisco Voice Engineers globally including several systems with 10,000+ phones.
Read Full Entry »

Print Friendly

When dealing with High Availability features in the CCIE Voice Lab exam, candidates should be familiar with all of the SRST mechanisms that are available on a remote site  gateway.

Before we look into the 4 options for SRST- just a quick reminder. SRST (Survivable Remote Site Telephony) is an licensed IOS feature that is used to provide call control for phones when the UCM is unavailable. We are going to concentrate on SCCP SRST- SIP SRST has only one option (voice register) and therefore there is no discussion to be had when it comes to which option to use for SIP SRST.

An example of when SRST is going to be useful… Let’s assume we have two offices in our enterprise- our headquarters in San Jose and remote office in Dallas. The UCM cluster resides in San Jose and there are phones and gateways in Dallas. In the event that the phones in Dallas cannot connect to the UCM cluster in San Jose due to a network outage, the Dallas gateway is able to provide call control support using one of 4 options. The option you choose will depend on what features need to be preserved and what type of customization is required.
Read Full Entry »

Print Friendly

Introduction

This is the third and final part of the series of blogs covering all aspects of QoS related to the Catalyst 3750. (Part 1 covered classification and marking and  Part 2 covered Ingress queueing).

In this article we will focus on Egress Queuing, Dropping and Scheduling. Whereas on the ingress side traffic is being placed onto the backplane of the switch (ring), on the egress side traffic is being sent to the destination or egress port.

Read Full Entry »

Print Friendly

Introduction

This is the second posting that discusses the QoS aspects of the Catalyst 3750- the first part can be found here: “Campus QoS- part 1- classification and marking on the Catalyst 3750”.

In this article we will focus on Ingress Queuing and Scheduling. Congestion on the ingress side of the switch is far less likely to occur than on the egress side since the throughput of the internal ring of the switch is likely to be far greater than the aggregate rate at which traffic is being received. 
Read Full Entry »

Print Friendly

I have often wondered why the Catalyst 3750 QoS section is one of the most feared items on the CCIE Voice lab blueprint (the same might be said of the Catalyst 3560 with respect to the R&S blueprint) and I always come to the conclusion that it is due to the lack of validation which would prove that what you have configured is correct. Whereas in other areas of the lab one is able to make a call through a selected gateway or call voicemail and hear the appropriate greeting or possibly see changes in the routing table, with QoS nothing really changes! There is no tangible difference when comparing the before and after. The calls don’t sound any better and the ping tests are not improved since there is no actual need for QoS, as congestion on any interface in the lab does not exist (unless you are doing something really wrong!). A blog on this site discussing the QoS features has been a long time coming, mainly because it has taken me so long to work everything out! This is the first in a series of blog’s that will discuss all of the QoS features that are available in the Catalyst 3750 and 3560 switches.

Read Full Entry »

Print Friendly