hit counter script

Dial Plans - Cisco 30 VIP Troubleshooting Manual

For cisco callmanager release 3.0(1)
Hide thumbs Also See for 30 VIP:
Table of Contents

Advertisement

Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
15:22:23.848 Cisco CallManager|MediaCoordinator - wait_MediaCoordinatorAddResource -
CI=16777359 count=1
15:22:23.848 Cisco CallManager|MediaCoordinator - wait_MediaCoordinatorAddResource -
CI=16777359 count=2

Dial Plans

A Dial Plan is a list of numbers and groups of numbers that tell the Cisco CallManager what
devices (phones, gateways, and so on) to send calls to when a certain string of digits are
collected. It is analogous to a static routing table in a router. Please be certain your dial plan
concepts, basic call routing, and planning have been carefully considered and properly
configured before trying to troubleshoot a potential dial plan issue. Very often, the problem lies
with planning and configuration when a problem occurs.
Use the following tips to help troubleshoot dial plans problems:
What is the Directory Number (DN) that is originating the call?
What is the Calling Search Space of this DN?
If applicable, what is the Calling Search Space of the device (such as a Cisco IP Phone)
with which the DN is associated? Make sure that you identify the correct device; because
multiple line appearances are supported, it's possible to have a DN on multiple devices.
Note the device's Calling Search Space. If this is a Cisco IP Phone originating the call,
remember that a particular line (DN) and the device that line is associated with have
Calling Search Spaces. They will be combined when making a call. For example, if line
instance 1000 has a Calling Search Space of AccessLevelX and the Cisco IP Phone that
has extension 1000 configured on it has AccessLevelY as its Calling Search Space, then
when making a call from that line appearance, Cisco CallManager will search through
partitions contained in Calling Search Space AccessLevelX and AccessLevelY.
What Partitions are associated with the Calling Search Space(s)?
What is the Partition of the device to which the call should (or should not) go?
What is the number that is being dialed? Note if and when they are getting secondary
dial tone at any stage. Also what do they hear after all the digits have been entered (re-
order, fast-busy)? Do they get the progress tones before they expect to hear anything?
Make sure callers wait at least 10 seconds after typing the last digit, since they may have
to wait for the inter-digit timer to expire.
Generate a Route Plan Report in Cisco CallManager Administration, and use it to
examine all the route patterns for the partitions that are in the Calling Search Space for
the call.
If necessary, add or modify the Route Patterns or Route Filters.
If you can find the Route Pattern to which the call is being sent, note the Route List or
Gateway to which the pattern points.
If it's a Route List, check which Route Groups are part of the list and which Gateway(s)
is part of the Route Groups.
Verify that the applicable devices are registered with Cisco CallManager.
If there's no access to Cisco CallManager, get the "show tech" to capture this information
and verify.
© 2000 Cisco Systems, Inc.
37

Advertisement

Table of Contents
loading

This manual is also suitable for:

30

Table of Contents

Save PDF