Information Technology Reference
In-Depth Information
Mar 31 16:07:21.359: //-1/C64C50C58929/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
Mar 31 16:07:21.359: //-1/C64C50C58929/DPM/dpMatchSafModulePlugin:
dialstring=9160, saf_enabled=1, saf_dndb_lookup=0, dp_result=1
Mar 31 16:07:21.359: //-1/C64C50C58929/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
<...output omitted...>
Mar 31 16:07:23.843: //-1/C64C50C58929/DPM/dpMatchPeersCore:
Calling Number=, Called Number=916025551212, Peer Info
Type=DIALPEER_INFO_SPEECH
Mar 31 16:07:23.843: //-1/C64C50C58929/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=916025551212
Mar 31 16:07:23.843: //-1/C64C50C58929/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Mar 31 16:07:23.843: //-1/C64C50C58929/DPM/dpMatchSafModulePlugin:
dialstring=916025551212, saf_enabled=1, saf_dndb_lookup=0, dp_result=0
Mar 31 16:07:23.843: //-1/C64C50C58929/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=1200
The key areas in Example 15-2 are highlighted. Notice at the beginning of the debug out-
put that the CME router matches an incoming dial-peer when the IP phone with exten-
sion 1500 goes off-hook (incoming dial peer 20005 matched). Then, CME analyzes each
digit as it is dialed from the IP phone. The first digit dialed is a 9. The debug output shows
Partial Matches(1), indicating this dialed string partially matches one or more dial peers. The
output then continues along this path until the IP phone has dialed a complete string
(916025551212). At this point, CME realizes it has a full match on outgoing dial peer 1200.
This debug command can be useful to watch the CME router go through the dial peer
matching process in real time. This is where you might talk a user through dialing a num-
ber that is failing and watch how CME handles the digits as the user dials them.
QoS Issues
Troubleshooting QoS is a different skill set and strategy than troubleshooting dial-plan issues.
Instead of working with the routing table for voice, you're working with the voice traffic itself.
You might have heard the saying before, “If you have no goal, you'll hit it every time.” Be-
fore we can troubleshoot voice quality issues, we need to have a goal we're shooting for.
Table 15-2 shows the Cisco recommended parameters for high-quality voice calls.
Table 15-2
Requirements for High-Quality VoIP Calls
Key
To p i c
Parameter
Requirement
End-to-end (one-way) delay
150 ms or less
Jitter
30 ms or less
Packet loss
1% or less
