IOS Dial-Peer Destination-Pattern Commands

Below are the following destination-pattern operators that can be used in IOS dial-peers for voice:

Standard Operators

  • Asterisk (*) and pound sign (#)—Keys that appear on standard touchtone dial pads.
  • Brackets ([ ])—Range of digits. Digits (0 to 9) are enclosed in brackets. Similar to a regular expression rule.
  • Parentheses (( ))—Define specific pattern. Same as the regular expression rule—for example, 408(555). Use parentheses in conjunction with symbols ? or %.
  • Period (.)—Match to any entered digit (used as a wildcard).
  • Comma (,)—Pause between digits.

“Repeating” Operators

  • Percent sign (%)—The previous digit or pattern zero or multiple times, similar to wildcard usage in the regular expression.
  • Question mark (?)—The previous digit occurred zero or one time.

Other Operators

  • Circumflex (^)—Match to the beginning of the string.
  • Dollar sign ($)—Match to the null string at the end of the input string.
  • Backslash (\)—Is followed by a single character matching that character or used with a single  character having no other significance (matching that character).
  • T—Control character indicating that the destination-pattern value is a variable-length dial string.

Shutting Down and Enabling VoIP Services

This is just a thought, but I wouldn’t be surprised to see the proctor try to “pull a fast one” by shutting down VoIP services on an H.323 gateway.  I suppose this could be easily identified by executing a “show gateway” or “show run.”  I came across this while reading the Cisco IOS H.323 Configuration Guide.

Continue Reading…

Close to Violating the NDA?

Good ol’ Jerry from IBM wrote a nice post on the “Ask the Expert” forum with Ben Ng.  He came close to violating the NDA, in my opinion.  The wording of his questions help shed some light on the mysterious exam that I’m prepping for.

Here’s what I gathered:

  1. There will be three voice gateways on the lab (SIP, MGCP, and H.323?)
  2. The dial-plan section may be “small” on words, but big in configuration requirements.
  3. Understand configuration and impact of TEHO in the environment.
  4. Understand how codec selection and CAC interact with one another.

Continue Reading…

CUCM 7.0 Port List Reference

Attached to this post if the CUCM 7.0 port list reference sheet.  If you ever wanted to know what port is used for attendant console (1103-1129 TCP), you can now find this and plenty of other port numbers.  Enjoy!  Yah, right.

CUCM 7.0 Port List (PDF – Right click, “Save As”)

JTAPI Subsystem Errors in UCCX

During a season where I worked for a Cisco partner, the support guys affectionately referred to JTAPI as “J-crappy.”  While that assessment still holds true, Cisco has come a long way in developing that nuisance of a plugin for integrating CUCM with IP-IVRs, UCCE, and (our favorite…gag me with a wooden spoon) UCCX.  Oh joy, could it be?  UCCX is on the blueprint for the exam.

Rant: I have no idea why they chose UCCX and not UCCE.  If we’re pushing the limits of advanced features, why not use the enterprise-class contact center solution?  I digress…

When you check the MIVR logs in UCCX for JTAPI subsystem problems, there are relatively few errors you will find.  Here are some of those errors and easy solutions for fixing them.  Please note, these errors are described in terms of CRS, which is Cisco IP-IVR solution.  However, if you have ever touched a CRS server, you will understand that a UCCX box is essentially a CRS server with contact center capabilities.  The software architecture is the same.

Continue Reading…

Page 29 of 33« First...1020«2728293031»...Last »