Route
partitions inherit the error-handling capabilities for the
Cisco Unified Communications
Manager software. This means that a console and SDI file trace are
provided for logging information and error messages. These messages will be
part of the digit analysis component of the traces. You must know how the
Partitions and Calling Search Spaces are configured and what devices are in
each partition and its associated calling search space to determine the source
of the problem. The Calling Search Space determines what numbers are available
for making a call. The Partition determines allowable calls to a device or
route list.
Refer to the route plan
chapters in the
System Configuration Guide for Cisco Unified Communications
Manager
for more information.
The following
trace shows an example of a dialed number that is in the device Calling Search
Space. For more detailed explanations about SDI traces, review the case studies
in this document.
08:38:54.968 CCM Communications Manager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x6b8802808:38:54.968 CCM CallManager|StationD - stationOutputDisplayText tcpHandle=0x6b88028, Display= 5000
08:38:54.968 CCM CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x6b88028
08:38:54.968 CCM CallManager|StationD - stationOutputCallState tcpHandle=0x6b88028
08:38:54.968 CCM CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x6b88028
08:38:54.968 CCM CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x6b88028
08:38:54.968 CCM CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x6b88028
08:38:54.968 CCM CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="")
In the Digit
Analysis component of the previous trace, the pss (Partition Search Space, also
known as Calling Search Space) gets listed for the device that is placing the
call.
In the
following trace, RTP_NC_Hardwood;RTP_NC_Woodland;Local_RTP represent the
partitions that this device is allowed to call.
08:38:54.968 CCM CallManager|Digit analysis: potentialMatches=PotentialMatchesExist08:38:54.968 CCM CallManager|StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x6b88028
08:38:55.671 CCM CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 5 tcpHandle=0x6b88028
08:38:55.671 CCM CallManager|StationD - stationOutputStopTone tcpHandle=0x6b88028
08:38:55.671 CCM CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x6b88028
08:38:55.671 CCM CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="5")
08:38:55.671 CCM CallManager|Digit analysis: potentialMatches=PotentialMatchesExist
08:38:56.015 CCM CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 0 tcpHandle=0x6b88028
08:38:56.015 CCM CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="50")
08:38:56.015 CCM CallManager|Digit analysis: potentialMatches=PotentialMatchesExist
08:38:56.187 CCM CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 0 tcpHandle=0x6b88028
08:38:56.187 CCM CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="500")
08:38:56.187 CCM CallManager|Digit analysis: potentialMatches=PotentialMatchesExist
08:38:56.515 CCM CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 3 tcpHandle=0x6b88028
08:38:56.515 CCM CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="5003")
08:38:56.515 CCM CallManager|Digit analysis: analysis results
08:38:56.515 CCM CallManager||PretransformCallingPartyNumber=5000
Be aware that
PotentialMatchesExist is the result of digit analysis of the numbers that were
dialed until the exact match is found and the call is routed accordingly.
The following
trace describes what happens when the Cisco Unified Communications Manager is
attempting to dial the directory number 1001 and it is not in the Calling
Search Space for that device. Again, be aware that the digit analysis routine
had potential matches until only the first digit was dialed. The route pattern
that is associated with the digit 1 resides in a partition that is not in the
device calling search space, RTP_NC_Hardwood;RTP_NC_Woodland;Local_RTP.
Therefore, the phone received a reorder tone (busy signal).
08:38:58.734 CCM CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x6b8802808:38:58.734 CCM CallManager|StationD - stationOutputDisplayText tcpHandle=0x6b88028, Display= 5000
08:38:58.734 CCM CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x6b88028
08:38:58.734 CCM CallManager|StationD - stationOutputCallState tcpHandle=0x6b88028
08:38:58.734 CCM CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x6b88028
08:38:58.734 CCM CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x6b88028
08:38:58.734 CCM CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x6b88028
08:38:58.734 CCM CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="")
08:38:58.734 CCM CallManager|Digit analysis: potentialMatches=PotentialMatchesExist
08:38:58.734 CCM CallManager|StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x6b88028
08:38:59.703 CCM CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x6b88028
08:38:59.703 CCM CallManager|StationD - stationOutputStopTone tcpHandle=0x6b88028
08:38:59.703 CCM CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x6b88028
08:38:59.703 CCM CallManager|Digit analysis: match(fqcn="5000", cn="5000", pss="RTP_NC_Hardwood:RTP_NC_Woodland:Local RTP", dd="1")
08:38:59.703 CCM CallManager|Digit analysis: potentialMatches=NoPotentialMatchesExist
08:38:59.703 CCM CallManager|StationD - stationOutputStartTone: 37=ReorderTone tcpHandle=0x6b88028
Route
partitions work by associating a partition name with every directory number in
the system. The directory number can be called only if the calling device
contains the partition within a list of partitions to which it is permitted to
place calls—its partition search space. This provides for extremely powerful
control over routing.
When a call
is being placed, digit analysis attempts to resolve the dialed address only in
those partitions that the partition search space specifies. Each partition name
comprises a discrete subset of the global dialable address space. From each
listed partition, digit analysis retrieves the pattern that best matches the
sequence of dialed digits. Then, from among the matching patterns, digit
analysis chooses the best match. If two patterns equally match the sequence of
dialed digits, digit analysis breaks the tie by choosing the pattern that is
associated with the partition that is listed first in the partition search
space.