CCIE Voice Study

Call Pickup Group Notifications (Audio/Visual) only operate within a directory number's own group. Associated Call Pickup Groups do not trigger a notification event. For example, lets say:

• Phone A and Phone B have diretory numbers in the same call pickup group (Pickup group 1)
• Phone C is in a call pickup group with Phone D (Pickup group 2)
• Pickup group 1 has Pickup group 2 as an associated call pickup group
• If Phone E calls phone C, either Phone A or Phone B can use the "OPickup" button to pickup the call
  • Phone D receives the Call Pickup Group Notification
  • Phones A and B receive no Notification; they have no way of knowing that Phone C was ringing without the convenience of physical proximity

Associated ...

Click here to read the whole article and view images

Under the Hunt Group Pilot number configuration (Call Routing > Route/Hunt > Hunt Pilot), forwarding options for call delivery in No Answer and Busy scenarios are set. In many situations, it is desirable for an administrator to control where a call is delivered in forwaded scenarios - for example, to voicemail, or to an overflow destination. In some situations, however, users may require or request control over how calls are overflowed. Say a small hunt group of 3 users needs to forward calls to a mobile device during a team meeting - this can be achieved using Personal Preferences.

In the Hunt Group Pilot configuration, under Hunt Forward Settings, "Use Personal Preferences" can be ticked for either/or both Forward Hunt No Answer and Forward Hunt Busy. The only caveat is that ...

Click here to read the whole article and view images

The "first digit timer" controls the time between when a phone is taken off hook until the first digit is dialed. Increasing the timer gives users more time between going off-hook to enter digits to make a phone call. It is different to the T302 (inter-digit) timer. The "Off Hook to First Digit Timer" is configured under the SIP profile and applied to the physical IP handset. The default profile cannot be modified - the profile must be copied and then applied to specific phones.

The first digit timer comes into play whenever a new line is seized. For example:

• When the receiver is taken off-hook
• When the speaker button is pressed
• When "Transfer" is pressed and the party performing the transfer searches for the destination party (for example, ...

  Click here to read the whole article and view images

User-specific security parameters such as PIN number length (for Extension Mobility), password complexity and aging (i.e. for CCM User access) are applied in CUCM on a per-user basis using credential policies. The policies are defined under "User Management" ==> "Credential Policy", and assigned under "User Management" ==> "End Users".

The security parameters and enforcement levels available to the administrator are quite granular: in the example below, the following characteristics are set:

• minimum PIN length of 5 digits
• require a complex (i.e. non-trivial) sequence of digits
• disable EM login after 3 successive failures

This new security policy is applied on a per-credential, per-user basis. The credentials are now assigned under end user configuration. ...

Click here to read the whole article and view images

Like many of us I'm quite curious by nature, and when I saw a few references to Web Dialer in Cisco documentation (most notably the Features and Services Guide), my curiosity was aroused. Cisco Web Dialer is sort of a simplified Remote Call Control (or RCC, for those familiar with CUPS and OCS integration). Essentially it allows an end user the ability to CTI control their telephony device. In a single cluster environment, getting Web Dialer to work is surprisingly simple; here's how:

1. Enable the Web Dialer Service in Cisco Unified Serviceability
2. Configure the Webdialer servlet (or the Web Dialer Service parameters in Service Parameter Configuration). In a single cluster environment the Application Dial Rules and the List of Webdialer Servlets are not used, and the other ...

   Click here to read the whole article and view images

To enable DND visual display for BLF assigned to speed-dials, specify True for BLF Status Depicts DND (CallManager Service Parameters, System - Presence group). This applies both to line appearances and directory listings (if BLF on call lists is configured). The default configuration is that BLF does not display DND status.

Click here to read the whole article and view images

When CallManager translates a number, the Dialed number displayed on the user's phone is translated according to rules on the translation pattern. By setting the Always Display Original Dialed Number parameter to True (in Service Parameters > CallManager > Device - General), the number displayed to the end user will always be the number dialed.

One particular application of this function is Manager/Assistant scenarios. Consider the scenario where the Assistant shares a line with the Manager, and the Manager has a private line on which to receive transferred calls. In this situation, if the Assistant fields a call for the manager and transfers the call to the Manager's private line, normally the private line would be visible to the Calling Party - the private line, is therefore, no ...

Click here to read the whole article and view images

Hold reversion notifies a user who has placed a call on hold that the call is still on hold. Hold reversion is a Clusterwide parameter, defined under the Call Manager service in Service Parameters.

To remind a user after 5 seconds, and then every 15 seconds thereafter, set Hold Reversion Duration to 5, and Hold Reversion Notification Interval to 15.

Click here to read the whole article and view images