understanding and troubleshooting call routing and · pdf fileunderstanding and...

44
Understanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager Contents Introduction Prerequisites Requirements Components Used Conventions Terminology Understand Call Flow Basic Call Routing and Dial Pattern Matching Notes for Using Traces Troubleshoot Planning Centralized Call Processing Distributed Call Processing Installation Checklist NANP Tags Full Text of Traces Call 1000 - 1111 (Short) Call 1000 - 1111 (Full) Call 1211 Call 1311 (Short) Call 1311 (Full) Related Information Introduction A dial plan essentially describes the number and pattern of digits that a user dials to reach a particular telephone number. Access codes, area codes, specialized codes, and combinations of the number of digits dialed are all part of a dial plan. For instance, the North American Public Switched Telephone Network (PSTN) uses a 10-digit dial plan that includes a 3-digit area code and a 7-digit telephone number. Most private branch exchanges (PBXs) support variable length dial plans that use 3 to 11 digits. Dial plans must comply with the telephone networks to which they connect. Only totally private voice networks that are not linked to the PSTN or to other PBXs can use any dial plan they choose. It is analogous to a static routing table in a router. Cisco CallManager Dial Plans are vastly improved in order to allow much greater scalability, flexibility, security, and ease of use. They require a significant amount of planning, in order to avoid the need to make drastic changes in the TAC Notice: What's Changing on TAC Web Help us help you. Please rate this document. Excellent Good Average Fair Poor This document solved my problem. Yes No Just browsing Suggestions for improvement: (256 character limit) Send

Upload: duongphuc

Post on 31-Jan-2018

248 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Understanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager

Contents Introduction Prerequisites Requirements Components Used Conventions Terminology Understand Call Flow Basic Call Routing and Dial Pattern Matching Notes for Using Traces Troubleshoot Planning Centralized Call Processing Distributed Call Processing Installation Checklist NANP Tags Full Text of Traces Call 1000-1111 (Short) Call 1000-1111 (Full) Call 1211 Call 1311 (Short) Call 1311 (Full) Related Information

Introduction A dial plan essentially describes the number and pattern of digits that a user dials to reach a particular telephone number. Access codes, area codes, specialized codes, and combinations of the number of digits dialed are all part of a dial plan. For instance, the North American Public Switched Telephone Network (PSTN) uses a 10-digit dial plan that includes a 3-digit area code and a 7-digit telephone number. Most private branch exchanges (PBXs) support variable length dial plans that use 3 to 11 digits. Dial plans must comply with the telephone networks to which they connect. Only totally private voice networks that are not linked to the PSTN or to other PBXs can use any dial plan they choose. It is analogous to a static routing table in a router. Cisco CallManager Dial Plans are vastly improved in order to allow much greater scalability, flexibility, security, and ease of use. They require a significant amount of planning, in order to avoid the need to make drastic changes in the

TAC Notice: What's Changing on TAC Web

Help us help you.

Please rate this document.

Excellent

Good

Average

Fair

Poor

This document solved my problem.

Yes

No

Just browsing

Suggestions for improvement:

(256 character limit)

Send

Page 2: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

future. This document helps explain the Dial Plan concepts, basic call routing, and planning considerations. Several examples are presented to illustrate these points.

Prerequisites

Requirements

Cisco recommends that you have knowledge of Cisco CallManager 3.x and 4.x.

Components Used

This document is not restricted to specific software or hardware versions.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Terminology Many of these concepts that relate to the Dial Plan are explained through examples in subsequent sections. Here are basic definitions of the terms as they apply to the Cisco CallManager.

Directory Number (DN)—The DN is the phone number of an end device. It can be a number assigned to an IP phone, a Cisco IP SoftPhone, a fax machine, or an analog phone attached to a gateway. Examples include 1000, 24231, and others.

Route Pattern—In Voice Over IP (VoIP), route patterns are the equivalent of static routes. The only difference is the route patterns point to E.164 numbers instead of the IP address. The Route Pattern is a specific number or, more commonly, a range of dialed numbers that are used to route calls to a device directly, such as a DT-24+ or a voice-capable router, or indirectly through a Route List. For example, 1XXX signifies 1000 through 1999. The X in 1XXX signifies a single digit, a placeholder or wildcard. There are other such placeholders that are to be introduced later, such as @, ., and !). A Route Pattern does not have to be unique within a Partition, as long as the Route Filter is different. In general, a Route Pattern matches the dialed number for external calls, performs digit manipulation(optional), and points to a Route List for routing.

Route List—Formerly called Route Point, the Route List allows Cisco CallManager to hunt through a list of Route Groups in a configured order of preference. A Route List consists of an ordered list of Route Groups. Route Lists expand the Route Groups concept and allow the user to order and prioritize your route groups. Multiple Route Lists can point to the same Route Groups. A Route List chooses a path for call routing and points to prioritized Route Groups.

Route Group—Route Groups and Route Lists work together to control and enhance external call routing. A Route Group is a list of one or more gateways, or ports on gateways, that are seen as equal access. It is analogous to a trunk group in traditional PBX terminology. For instance, one can have two Primary Rate Interface (PRI) circuits to the same carrier that can be used arbitrarily. A gateway, or a particular port on a gateway, can only be added to one Route Group.

Device—A device, in this sense, is a gateway that is Skinny-based (DT-24+, AS/AT, or Catalyst 6000 gateways), MGCP-based (VG200), or H.323-based (all Cisco IOS® gateways and other Cisco CallManagers). These are all devices to which a Route Group can point. They do not include Skinny-based or H.323-based endpoints, such as IP phones or NetMeeting clients.

Page 3: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Translation Pattern—A Translation Pattern is used in order to translate called (Dialed Number Identification Service [DNIS]) and calling (automatic number identification [ANI]) numbers before the call is routed. For example, you can have calls come into a set of numbers 919 392-3XXX that must be translated to a set of IP phones that are in the 2XXX range. In Cisco CallManager, you set up a Translation Pattern for 919 392-3XXX that changes the leading 919 392-3 to just 2, while the rest of the digits are left intact. Then, the call is routed to the appropriate IP phone. Translation Patterns are used only for true translations and must not be used as a simple way to strip or prefix digits.

Route Filter—A Route Filter can be used not only to restrict dialing but also to identify a subset of a pattern with a placeholder, when the @ placeholder is used in the North American Dialing Plan. Cisco CallManager identifies tags in each number, International-Access, Area code, and Office-Number. For example, you can use it to block 900 area codes. It can also be used in conjunction with Partitions and Calling Search Spaces in order to set up complex rules. For example, you could set up Route Filters that allow an Executive user group to dial any number, which includes international numbers, but restrict a Staff user group to only local numbers or long distance calls and restrict a Guest user group to only dial local numbers, 911, and 800 numbers.

Partition—A Partition is a logical group of Directory Numbers and Route Patterns with similar characteristics for reachability. For simplicity, these are usually named for their characteristics, such as "NYLongDistance" and "NY911." When a DN or Route Pattern is placed into a certain Partition, it creates a rule about who can call that device or Route List.

Calling Search Space—The Calling Search Space is a group of Partitions to search, when you make a call, that defines what numbers a device can call. For instance, an IP phone number that has an Executive Calling Search Space when it initiates a call might have "NYInternationalCall," "NYLongDistance," "NYLocalCall," and "NY911" Partitions available to search. An IP phone number that has a Guest Calling Search Space can only be allowed to search "NYLocalCall" and "NY911". If that number tries to dial an international number, it does not find a match and the call is not routed. The Calling Search Space defines what Directory Numbers and Route Patterns can be called.

Note: In terms of call routing, the main differences between Cisco CallManager 2.x and Cisco CallManager 3.x or 4.x are the concepts of Partitions and Calling Search Spaces and the replacement of the term "Route Point" with the term "Route List."

Hunting—Allows a call to be directed to a list of line groups where each group can independently use one of three algorithms, known as broadcast, top down, or circular:

Hunting commences when a hunt pilot number associated with a hunt list is called.

The hunt pilot can be called directly or can be reached through forwarding.

While hunting, the forwarding fields of the hunt parties are ignored. The determination of which phone to ring next is determined by the line groups within the hunt list.

Note: In Cisco CallManager Release 4.0, hunting stops either when one of the hunt parties answers the call or when the hunt list is exhausted. When hunting stops due to exhaustion, the caller receives a reorder tone or an equivalent announcement.

Call Forwarding—Allows users to specify how calls to their numbers can be redirected when a user fails to answer a call in a specified time interval, known as Call Forward No Answer, or when the user is busy, known as Call Forward Busy.

Page 4: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Understand Call Flow This diagram illustrates a typical call flow:

Basic Call Routing and Dial Pattern Matching Cisco CallManager performs Closest-Match Routing. This function is best explained in the examples in this section. If you try to troubleshoot a Dial Plan problem, first read the Troubleshooting section of this document before you enable any tracing.

The N placeholder is no longer permitted in Cisco CallManager 3.x and 4.x. Use [2-9] instead.

When you configure for a secondary dial tone, remember that you do not hear the dial tone until the Route Pattern is unambiguous. The . has nothing to do with the secondary dial tone.

Make sure that you do not use 9 as any telephone number, or additional digit collection is required before tone to 9.@ numbers is provided.

Page 5: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Digit Analysis is performed as a user dials a number and the router interprets the digits. For example, when a user dials 1000, it can match a pattern configured in Cisco CallManager that is 1XXX, or 100X, or 1!. There are a number of special characters that can be used to signify a range of dialed digits, as shown in this table:

Placeholder Explanation Examples

Digit A digit that is interpreted as its literal value.

0 matches 0, 1 matches 1, 2 matches 2, and so forth

X Any single digit in the range 0 through 9.

X matches 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9

[m-n] Any single digit in the range m through n.

[4-9] matches 4, 5, 6, 7, 8, or 9

[^m-n] Any single digit outside of the range m through n.

[^4-9] matches 0, 1, 2, 3, #, or *

!

One or more digits in the range 0 through 9. This placeholder can be very useful for variable length Dial Plans. The call is not routed until the # key is pressed or the inter-digit timeout expires (default 10 seconds).

9! matches 91, 911, or 912342, but not 9 only, as ! requires at least one digit for a match.

? Same as ! except that it can match zero or more digits.

9? matches 9, 91, 911, or 912342

+ One or more of the previous digits or a placeholder.

9+ matches 99, 999, or 9999

9X+ is equivalent to 9! and 9X?

.

A portion of the number that can be stripped after a pattern is matched.

Match Pattern: 9.8XXX

Discard digits instruction (DDI): PreDot

If the user dials 98111, the PreDot DDI is applied to the 9.8XXX route pattern, which strips the “9” from the dialed digits and sends only the

Page 6: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

There are two common problems that occur when you use the @ placeholder:

When a user dials a 7-digit number, the user has to wait for the inter-digit timeout to expire or has to press the # key.

Go to the Route Filter window and add a filter with LOCAL-AREA-CODE DOES-NOT-EXIST AND END-OF-DIALING DOES-NOT-EXIST. Apply it to your Route Pattern that contains the @ placeholder.

Users cannot dial a number where the office code is X11 (1 + Area Code + Office Code + Extension), for example the 11 in 1 800 611 4215 or 1 919 311 5432.

The workaround is to add another Route Pattern such as 9.1 [2-9]XX [2-9]11 XXXX to the same gateway or route list as the 9.@ pattern. Do not forget to add the same digit discard instructions, if any.

These are some sample Route Patterns:

8111 to the PBX.

@

References the North American Numbering Plan (NANP), which is actually a macro that contains about 300 individual patterns. You can use this placeholder to apply filtering rules, because an @ makes “Area Code” and “Service Code” available to filter checks.

Additional information on the tags is in the NANP Tags section of this document.

[2-9]11 matches 211, 311, 411, 511, 611, 711, 811, or 911

[2-9]XX XXXX matches 7-digit local numbers

[2-9]XX [2-9]XX XXXX matches 10-digit local numbers

1 [2-9]XX [2-9]XX XXXX matches 11-digit long distance numbers

011 3[0-469] ! matches international numbers

Pattern Matches

1111 1111 only

*1*1 *1*1 only

12XX 1200 through 1299 only

13[25-8]6 1326, 1356, 1366, 1376, 1386 only

Page 7: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Consider this Dial Plan:

If the user dials 1111, it waits for all four digits to be entered before it routes the call.

Notes for Using Traces

Before you enable any tracing for Dial Plan issues, read the Troubleshooting section of this document.

Set User Mask Bit 5 on the user mask to debug Dial Plan problems. Set User Mask Bit 11 for a System Trace in order to see further digit analysis information.

Caution: Set Bit 11 with caution, as it can create a load that affects performance on a heavily used system.

In order to see what IP address to which a tcpHandle maps, capture a keepalive message, which happens every 30 seconds, with a network analyzer. The tcpHandle for a phone remains the same as long as it is registered with a Cisco CallManager.

The StationD messages are always from the Cisco CallManager to the IP phone. The StationInit messages are from the phone to the Cisco CallManager.

The Instance is the line instance for that particular phone template. The Line(9) refers to a Line button, as opposed to Hold or some other type.

Refer to Set Up Cisco CallManager Traces for Cisco Technical Support for more information on the use of the trace facility. If you use Cisco CallManager 3.1, also refer to Trace for Cisco CallManager.

Note: Many of the procedures described in Trace for Cisco CallManager also apply to 3.0.

13[^3-9]6 1306, 1316, 1326, 13*6, 13#6 only

13!# Any number that begins with 13, that preceeds one or more digits, and that ends with #. 135# and 13579# are example matches.

Pattern Matches

1111 1111 only

1211 1211 only

1[23]XX 1200 through 1399 only

131 131 only

13[0-4]X 1300 through 1349 only

13! Any number that begins with a 13 that preceeds one or more digits.

Page 8: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

The next sample output is a trace snippet with only User Mask Bit 5 set. For the full trace (Bit 5 only) see the Call 1000-1111 (Short) section of this document. For the full trace with the System Trace also enabled, see the Call 1000-1111 (Full) section of this document.

Note: In this trace, tcpHandle 0x53563d0 is the calling phone and 0x53294d8 is the called phone (DN=1111).

!--- Output is suppressed. |StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x53563d0 |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |StationD - stationOutputStopTone tcpHandle=0x53563d0 |StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) |StationD - stationOutputCallState tcpHandle=0x53294d8 |StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53294d8 |StationD - stationOutputSetLamp stim: 9=Line instance=3 lampMode=LampBlin tcpHandle=0x53294d8 |StationD - stationOutputSetRinger: 2=InsideRing tcpHandle=0x53294d8 |StationD - stationOutputDisplayNotify tcpHandle=0x53294d8 |StationD - stationOutputDisplayPromptStatus tcpHandle=0x53294d8 |StationD - stationOutputSelectSoftKeys tcpHandle=0x53294d8 |StationD - stationOutputCallState tcpHandle=0x53563d0 |StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=, CalledParty=1111, tcpHandle=0x53563d0 |StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53563d0 |StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x53563d0 !--- Output is suppressed.

If the user dials 1211, it matches 1211 and 1[23]XX. Because 1211 matches only one potential dial string, while 1[23]XX matches 200, 1211 is the pattern that is selected. This selection process is the essence of closest-match call routing. See the Call 1211 section of this document for a full Serial Digital Interface (SDI) trace of this process.

!--- Output is suppressed. |StationInit - InboundStim - StimulusMessageID stimulus: Line(9) Instance: 1 tcpHandle=0x53563d0 |StationInit - InboundStim - OffHookMessageID tcpHandle=0x53563d0 |StationD - StimLine: OnHook --- OnHook |StationD - stationOutputSetSpeakerMode: 1 tcpHandle=0x53563d0 |StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display= 1000 |StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display= 1000 |StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x53563d0 |StationD - stationOutputCallState tcpHandle=0x53563d0

Page 9: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 |StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 |StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="") |Digit analysis: analysis results |PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern= |DialingRoutePatternRegularExpression= |DialingWhere= |PatternType=Unknown |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(0,0,0) |PretransformDigitString= |PretransformTagsList= |PretransformPositionalMatchList= |CollectedDigits= |TagsList= |PositionalMatchList= |RouteBlockFlag=BlockThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(1,82,1) |InterceptSsType=16777221 |InterceptSsKey=7864 |StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x53563d0 |CMProcMon - ------Entered Router Verification |CMProcMon - ----Exited Router Verification |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |StationD - stationOutputStopTone tcpHandle=0x53563d0 |StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="1") |Digit analysis: potentialMatches=PotentialMatchesExist |StationInit - InboundStim - KeypadButtonMessageID kpButton: 2 tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="12") |Digit analysis: potentialMatches=PotentialMatchesExist |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="121") |Digit analysis: potentialMatches=PotentialMatchesExist |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="1211") |Digit analysis: analysis results |PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern=1211 |DialingRoutePatternRegularExpression=(1211) |DialingWhere= |PatternType=Enterprise |PotentialMatches=NoPotentialMatchesExist |DialingSdlProcessId=(1,38,19) |PretransformDigitString=1211 |PretransformTagsList=SUBSCRIBER |PretransformPositionalMatchList=1211 |CollectedDigits=1211 |TagsList=SUBSCRIBER |PositionalMatchList=1211 |RouteBlockFlag=RouteThisPattern

Page 10: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

|InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(0,0,0) |InterceptSsType=0 |InterceptSsKey=0 |Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) |StationD - stationOutputCallState tcpHandle=0x56ca080 |StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=1211, CalledParty=1211, tcpHandle=0x56ca080 |StationD - stationOutputSetLamp stim: 9=Line instance=4 lampMode=LampBlin tcpHandle=0x56ca080 |StationD - stationOutputSetRinger: 2=InsideRing tcpHandle=0x56ca080 |StationD - stationOutputDisplayNotify tcpHandle=0x56ca080 |StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 |StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 |StationD - stationOutputCallState tcpHandle=0x53563d0 |StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=, CalledParty=1211, tcpHandle=0x53563d0 |StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=1211, CalledParty=1211, tcpHandle=0x53563d0 |StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x53563d0 !--- Output is suppressed.

If the user dials 1311, Cisco CallManager waits for the inter-digit timer to expire. Because of the 13! pattern, there is the potential that the user is not done entering numbers yet. Once the timer expires, there are three matches: 1[23]XX, 13[0-4]X, and 13!. Because 1[23]XX matches about 200 patterns, 13[0-4]X matches about 50 patterns, and 13! matches an infinite number of patterns, 13[0-4]X is selected. See the Call 1311 (Full) section of this document for an SDI trace of this, and see the Call 1311 (Short) section of this document for a trace with only Bit 5 set for debugging.

!--- Output is suppressed. |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |StationD - stationOutputStopTone tcpHandle=0x53563d0 |StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="1") |Digit analysis: potentialMatches=PotentialMatchesExist |StationInit - InboundStim - KeypadButtonMessageID kpButton: 3 tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="13") |Digit analysis: potentialMatches=PotentialMatchesExist |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="131") |Digit analysis: analysis results ||PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern=131 |DialingRoutePatternRegularExpression=(131) |DialingWhere= |PatternType=Enterprise |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(1,38,22) |PretransformDigitString=131

Page 11: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

|PretransformTagsList=SUBSCRIBER |PretransformPositionalMatchList=131 |CollectedDigits=131 |TagsList=SUBSCRIBER |PositionalMatchList=131 |RouteBlockFlag=RouteThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(0,0,0) |InterceptSsType=0 |InterceptSsKey=0 |StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 |Digit analysis: match(fqcn="", cn="1000", pss="", dd="1311") |Digit analysis: analysis results ||PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern=13[0-4]X |DialingRoutePatternRegularExpression=(13[0-4]X) |DialingWhere= |PatternType=Enterprise |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(1,38,21) |PretransformDigitString=1311 |PretransformTagsList=SUBSCRIBER |PretransformPositionalMatchList=1311 |CollectedDigits=1311 |TagsList=SUBSCRIBER |PositionalMatchList=1311 |RouteBlockFlag=RouteThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(0,0,0) |InterceptSsType=0 |InterceptSsKey=0 |Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) |StationD - stationOutputCallState tcpHandle=0x56ca080 !--- Output is suppressed.

Troubleshoot Cisco CallManager searches through the Calling Search Space of a line instance and of the device with which the line is associated.

If a device is not part of a Partition, it is said to be part of the Null or default Partition. Every user must be able to call that device. The Null Partition is always searched last.

If you dial an outside number that matches a 9.@ pattern and it takes ten seconds before the call goes through, check the filtering options. By default, with a 9.@ pattern, when a 7-digit number is dialed, it waits 10 seconds. You need to apply a filter to the pattern that says LOCAL-AREA-CODE DOES-NOT-EXIST.

After Cisco CallManager is upgraded, users receive a different secondary dial tone when 9 is pressed for an outside line. In order to resolve this issue, use the Cisco IP Telephony Locale Installer plugin from the Cisco CallManager Adminstration page. Or, this can be downloaded

Page 12: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

from Cisco Unified Communications Locale Installer ( registered customers only)

When you dial 9 and then a 0 in order to reach the local operator, if the call times out and goes to fast busy, it can be an issue with route patterns that overlap. If you have the 9.@ route pattern, 9.0 overlaps with the 9.@ . So, when you try to dial 9 in order to get an outside line, then 0 for the operator, the dial patterns expect you to dial more digits like the international number (011). Since you do not input any more digits, the call times out and goes to fast busy. In order to resolve this issue, add a new route pattern in the Cisco CallManager as shown here:

9.0# !--- Discard pre dot (if needed with your PSTN connection).

When you need to reach the operator, dial 9, and then 0, and then the pound key (#) in order to route the call immediately and not wait for more digits.

Refer to Configuring the Dial Plan in Cisco CallManager for more information on the configuration of route patterns.

It is not possible to suffix a number on a called party number using MGCP gateways because the called-party transformation works on XOR mechanism and there is no specific way to suffix a number as the logical relevance of each digit is from left to right. Therefore, you can only prefix. The only way to achieve this is using H323 gateway as it has the intelligence to mix-up calling/called party transformations and do the translations as needed.

It is not very easy to see a clear call flow to troubleshoot Dial Plan problems with the SDI trace facility. Before you use the SDI trace facility, try to apply these guidelines:

First, obtain this pertinent information:

What is the Directory Number that originates the call?

What is the Calling Search Space of this Directory Number? This information can be found under the line configuration.

What is the Calling Search Space of the device on which the Directory Number is configured? Make sure that you identify the correct device. Since Cisco CallManager supports multiple line appearances, you could have a Directory Number on multiple devices.

Note the Calling Search Space configured on the device. If an IP phone originates the call, remember that a particular line and the device with which the line is associated both have Calling Search Spaces. They are combined when a call is made. Suppose line instance 1000 has a Calling Search Space of AccessLevelX, and the IP phone that has extension 1000 configured on it has AccessLevelY as its Calling Search Space. When a call is made from that line appearance, the Cisco CallManager searches 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 they want, or do not want, the call to go?

What is the number that is dialed?

Page 13: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Note if and when they get a secondary dial tone at any stage. Also, what do they hear after all of the digits have been entered. Is it a re-order or fast-busy? Do they get the progress tones before they expect to hear anything? Make sure they wait at least ten seconds after they press the last digit, because they can have to wait for the inter-digit timer to expire.

Then, complete these steps:

1. Look through the Route Plan Report in order to examine all of 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.

2. If you can find the Route Pattern to which the call is sent, note the Route List or gateway to which the pattern points.

If it is a Route List, check which Route Groups are part of the list and which gateways are part of the Route Groups.

3. Verify that the applicable devices are registered with Cisco CallManager.

4. Watch out for the @ placeholder. This is a macro that can expand to include many different things. It is often used in combination with filtering options.

Planning When you design a Dial Plan, it is recommended that you use a 4-digit or 5-digit local Dial Plan. If you use anything less, it could be difficult to integrate Cisco Unity voice mail services.

Remember that Cisco CallManager or clusters have no way to share Dial Plans. They are independent units. All Dial Plan considerations and design issues, such as voice mail and conferencing or transcoding issues, must be taken into account for each individual Cisco CallManager or cluster.

When you construct a Dial Plan, the goals must be to keep the plan as simple as possible for the end user and to use the local PSTN gateway access code—such as 9 or 0—for locations that must be reached over the PSTN as well as for calls that might traverse the IP WAN. If the IP WAN becomes unavailable or has insufficient resources, it must be transparent to the end user.

The first consideration when you implement a Dial Plan is the network topology. If you have multiple sites, then you need to determine if each site has its own Cisco CallManager or if they are controlled through one centralized Cisco CallManager.

Centralized Call Processing

Page 14: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

In centralized call processing, one Cisco CallManager or Cisco CallManager cluster controls all of the IP Telephony devices. The benefit of this is that there is only one centralized point of administration. The disadvantage is that all IP phones and Skinny devices must be able reach this Cisco CallManager in order to make any call. So if IP connectivity is disrupted, for example, if the WAN goes down, users can be left stranded without the ability to make a call. Life-line services, such as 911, must be provided through some other mechanism. For this option, location-based call admission control is likely preferred.

From the previous diagram, you can see that it is important to remember that—when 9 is used to dial out—the Cisco CallManager selects a gateway based on the geographical location of the user. You can also set up a facility such that, if one of the gateways does not have any free resources to make a call through the PSTN, it uses a gateway at a remote site. Another consideration is to allow users to make long distance calls through the PSTN between the sites, if there is not enough bandwidth on the IP WAN to have a good quality Voice over IP (VoIP) call. Other things to consider are whether or not everyone has access to make calls, whether long distance, international, or interoffice. In order to avoid complications in the future, it is best to set up some basic user levels to start. It is then much easier to change rights. Because user access involves the set up of Partitions and Calling Search Spaces that are then applied to individual DN and devices, these user levels must be thought through very carefully. Later changes can result in the need to modify every device or DN.

Distributed Call Processing

Page 15: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

In distributed call processing, each IP phone or Skinny device is registered to a local Cisco CallManager or Cisco CallManager cluster. If each has a local gateway to get to the PSTN, even if the IP WAN goes down, a user still can call local numbers and call users at the other site across the PSTN. Only Cisco IOS-based Gatekeeper Call Admission Control is feasible here.

Each Cisco CallManager maintains its own Dial Plan and must therefore be managed and administered separately.

Suppose a user in RTP tries to dial 9 to get an outside PSTN line, but no circuits are available. It is inadvisable to route the call to a NY Cisco CallManager because the Dial Plan in NY can be inapplicable to a user that places a call in RTP. In such a situation, for instance, the RTP user must dial 1 plus the RTP area code to place a local call to RTP, but there is no way for the Cisco CallManager server to inform the user of this requirement. Although it might be possible to do called party transformations for every three digit prefix in the RTP area (to prepend the required 1 + area code) this is not a scalable solution.

Further, each Cisco CallManager (cluster) needs to have its own voice mail (Cisco Unity) instance. For this deployment model, a gatekeeper is required for admission control. Each site must have Cisco CallManager, voice mail, and digital signal processor (DSP) resources for transcoding, if compression is used across the WAN, and conferencing.

Installation Checklist Choose descriptive Partition Names. It is very difficult to troubleshoot a system that cannot place long distance calls when the Partition Names are meaningless terms like widget and foobar.

Keep in mind that features such as Call Park and Call Pickup are also part of a Partition. They are usually left to the Null or default Partition, so everyone has access to them. They can also be assigned to a basic user level, such as NYInternalCalls in the examples later in this

Page 16: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

document.

Blocking access to certain area codes and numbers is accomplished with a separate Partition, such as Block900 in the examples later in this document, for each pattern that must be denied access, such as 9.@ where AREA-CODE=900. Because this is a closer match than a simple 9.@ where AREA-CODE EXISTS, and the Route Pattern is configured to block instead of route anything that matches this Pattern, the filtering works.

These are some of the most common items that need to be considered before you start any configuration:

Which call processing model do you plan to use: centralized or distributed?

What type of Call Admission Control do you plan to use: Cisco IOS gatekeeper or location-based?

Has network Quality of Service (QoS) on the network been implemented? (Infastructure improvements to support real-time traffic, prioritization mechanisms, traffic-shaping, and fragmentation, if necessary.)

Are there existing PBXs in place that need to be interfaced, or are you connecting to a Local Exchange Carrier (LEC) or Inter-eXchange Carrier (IXC)? If so, what signaling mechanism do you plan to use: PRI, Q.SIG, or channel associated signaling (CAS)? Keep in mind that not all of these provide the same functionality (such as ANI or CallerID).

If you connect to a PBX, make note of any access codes that are required to call outside calls (local and long distance), as well any special access codes for extensions behind the PBX.

If you have multiple locations controlled by a single Cisco CallManager (such as in the centralized call processing model), decide if you need to have any of these fallbacks:

Local call fallback—If your local gateway is unavailable, route the call to a gateway at a remote site and make a long distance call.

Toll bypass fallback—If a remote gateway is unavailable to make a local call in the remote area-code, route the call as a long-distance call through your local gateway.

Long distance and international call fallback—If a local gateway is unavailable to make a long distance or international call, route the call through a gateway at a remote location.

Make note of all area codes in each location and whether or not they have 7-digit or 10-digit dialing.

Note the range of direct inward dial (DID) numbers that are assigned to the circuit(s) at each of the remote sites. Also note the 7-digit or 10-digit number that are used as the main access number (if any) at the location.

Make a note of the extensions serviced by each PBX (1XXX or 29XX).

What do you want to present to the PBX or PSTN as the Caller ID: attendant number, full number, or directory number?

List any special user groups that you want to differentiate (the examples later in this document

Page 17: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

include NYLocalCalls, NYTollFreeCalls, NYLongDistanceCalls, NYInternationalCalls, Block900Calls, RTPCallsOnly, NYInternalOnly, and NY911Calls). These special user groups become the Partitions and allow you to create access groups and levels. Make sure to consider these groups carefully, as you save a lot of time in the long run with well-planned groups.

Note: Make sure that you use descriptive names, including the site name and access privilege, even if you currently do not anticipate having multiple sites. For most scenarios it is recommended to use Partition Names in the form CompanyNameSiteNameAccessPrivilege . For example, use Partition Names like "CiscoRTP911Calls" or "AcmeNewYorkLongDistanceCalls."

Create "user access levels" that group the Partitions in the previous steps together. These become Calling Search Spaces, as shown in this table of examples:

Calling Search Space Partitions Assigned To

NYGuest

NY911Calls

NYInternalCalls

NYTollFreeCalls

Guest users, Lobby phones

Devices can only call 911, NY internal calls, or toll-free calls.

NYStaff

NY911Calls

NYInternalCalls

NYTollFreeCalls

NYLocalCalls

RTPInternalCalls

RTPLocalCalls

Staff in NY who can call 911, internal or local calls at either site, or toll-free long distance calls.

NYManager

NY911Calls

NYInternalCalls

NYLocalCalls

RTPInternalCalls

RTPLocalCalls

Block900

NYLongDistanceCalls

Manager-level group that has all the rights of NYStaff, as well as Long Distance Calls from NY. Calls to 900 numbers are blocked.

NY911Calls Executive-level group

Page 18: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

NYExecutive

NYInternalCalls

NYLocalCalls

RTPInternalCalls

RTPLocalCalls

Block900

NYLongDistanceCalls

RTPLongDistanceCalls

NYInternationalCalls

RTPInternationalCalls

that has all the rights of NYManager, as well as rights to make long distance calls from RTP—if NY is unavailable for some reason—and international calls from NY or from RTP, if necessary. Calls to 900 numbers are blocked.

RTPGuest

RTP911Calls

RTPInternalCalls

RTPTollFreeCalls

Same as NYGuest, but for RTP.

RTPStaff

RTP911Calls

RTPInternalCalls

RTPTollFreeCalls

RTPLocalCalls

NYInternalCalls

NYLocalCalls

Same as NYStaff, but for RTP.

RTPManager

RTP911Calls

RTPInternalCalls

RTPLocalCalls

NYInternalCalls

NYLocalCalls

Block900

RTPLongDistanceCalls

Same as NYManager, but for RTP.

RTP911Calls

Page 19: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Typically, in North America, it is recommended to use 1XXX or 29XXX in order to designate internal PBX extensions or other IP phones. For external calls, the @ placeholder would be used after the access code, such as 8.@ or 9.@.

Once you have taken all of these considerations into account, it is often easier to use the Dial Plan Wizard in order to initially develop a complex Dial Plan. Complete these steps in order to use this tool:

1. Start with a fresh machine that does not have any Partitions, Calling Search Spaces, Route Lists, Route Groups, Route Filters, or Route Patterns installed. If you already have created some, it is best to delete them first.

2. Create all of the gateways: H.323 gateways—which are Cisco IOS routers or, in a distributed model, are other Cisco CallManagers—and other analog or digital gateways.

3. Go to the Route Plan Wizard and complete the instructions. Review the previous list in order to prepare, in advance, to answer the questions. The Dial Plan is created automatically.

Note: The Wizard is not able to set up filtering. It is very easy to go back and add a Block900numbers filter, after the Wizard has created everything else.

NANP Tags

RTPExecutive

RTPInternalCalls

RTPLocalCalls

NYInternalCalls

NYLocalCalls

Block900

RTPLongDistanceCalls

NYLongDistanceCalls

RTPInternationalCalls

NYInternationalCalls

Same as NYExecutive, but for RTP.

Tag Name Example Number Description

AREA-CODE 1 214 555 1212

The area code in an 11-digit long distance call.

COUNTRY-CODE 01 1 33 123456 #

The country code in an international call.

END-OF-DIALING 01 1 33

The # key which cancels inter-digit

Page 20: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

123456 # timeout in international calls.

INTERNATIONAL-ACCESS

01 1 33 123456 #

The initial 01 of an international call.

INTERNATIONAL-DIRECT-DIAL

01 1 33 123456 #

The digit that denotes the direct-dial component of an international call.

INTERNATIONAL-OPERATOR 01 0

The digit that denotes the operator component of an international call.

LOCAL-AREA-CODE

214 555 1212

The area code in a 10-digit local call.

LOCAL-DIRECT-DIAL 1 555 1212

The initial 1 required by some 7-digit local calls.

LOCAL-OPERATOR 0 555 1212

The initial 0 required for operator-assisted direct-dial calls.

LONG-DISTANCE-DIRECT-DIAL

1 214 555 1212

The initial 1 required for long distance direct-dial calls.

LONG-DISTANCE-OPERATOR

0 214 555 1212

The initial 0 required for operator-assisted long distance calls.

NATIONAL-NUMBER

01 1 333 123456 #

The national number component of an international call.

OFFICE-CODE 1 214 555 1212

The office or exchange code of a North American call.

SATELLITE-SERVICE

01 1 881 4 1234 #

A specific value associated with calls to the satellite country code.

SERVICE 1 411 Access to local telephony provider services.

SUBSCRIBER 1 214 555 1212

A particular extension served by a given exchange.

101 0321 1

Page 21: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

Full Text of Traces

Call 1000-1111 (Short)

!--- Each timestamped line of output appears on one line. 12:44:24.625 Cisco CallManager|StationInit - InboundStim - StimulusMessageID stimulus: Line(9) Instance: 1 tcpHandle=0x53563d0 12:44:24.625 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x53563d0 12:44:24.625 Cisco CallManager|StationD - StimLine: OnHook --- OnHook 12:44:24.625 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 1 tcpHandle=0x53563d0 12:44:24.625 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 12:44:24.625 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 12:44:24.640 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x53563d0 12:44:24.640 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:44:24.640 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:44:24.640 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:44:24.640 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 12:44:24.640 Cisco CallManager|StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x53563d0 12:44:25.687 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:44:25.687 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 12:44:25.687 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:44:26.078 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:44:26.468 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:44:26.828 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:44:26.828 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:44:26.828 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:44:26.828 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53294d8 12:44:26.828 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=3 lampMode=LampBlink tcpHandle=0x53294d8 12:44:26.828 Cisco CallManager|StationD - stationOutputSetRinger:

TRANSIT-NETWORK

214 555 1212

Long distance carrier code.

TRANSIT-NETWORK-ESCAPE

101 0321 1 214 555 1212

The escape sequence used to enter a long distance carrier code.

Page 22: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

2=InsideRing tcpHandle=0x53294d8 12:44:26.828 Cisco CallManager|StationD - stationOutputDisplayNotify tcpHandle=0x53294d8 12:44:26.828 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53294d8 12:44:26.828 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53294d8 12:44:26.828 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:44:26.828 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=, CalledParty=1111, tcpHandle=0x53563d0 12:44:26.843 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53563d0 12:44:26.843 Cisco CallManager|StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x53563d0 12:44:26.843 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:44:26.843 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:44:26.843 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:44:27.937 Cisco CallManager|StationInit - New connection accepted. DeviceName=, TCPHandle=0x56b55f0, Socket=0x51c, IPAddr=10.120.99.52, Port=49818, Device Controller=[0,0,0] 12:44:28.078 Cisco CallManager|StationInit - Processing StationReg. regCount: 1 DeviceName=MTP00D097386420, TCPHandle=0x56b55f0, Socket=0x51c, IPAddr=10.120.99.52, Port=49818, Device Controller=[1,45,103] 12:44:28.078 Cisco CallManager|StationInit - InboundStim - IpPortMessageID: 0(0x0) tcpHandle=0x56b55f0 12:44:28.187 Cisco CallManager|StationInit - StationCloseReq received: 0x56b55f0 12:44:28.187 Cisco CallManager|***** StationInit - Socket Broken. DeviceName=, TCPHandle=0x56b55f0, Socket=0x51c, IPAddr=10.120.99.52, Port=0xc29a, Device Controller=[0,0,0] 12:44:28.187 Cisco CallManager|StationInit - Closing Station connection DeviceName=MTP00D097386420, TCPHandle=0x56b55f0, Socket=0x51c, IPAddr=10.120.99.52, Port=49818, Device Controller=[1,45,103] 12:44:28.187 Cisco CallManager|StationInit - StationCloseReq received: 0x56b55f0 12:44:28.843 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x53294d8 12:44:28.843 Cisco CallManager|StationD - stationOutputClearNotify tcpHandle=0x53294d8 12:44:28.843 Cisco CallManager|StationD - stationOutputSetRinger: 1=RingOff tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=3 lampMode=LampOn tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 12:44:28.859 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:44:28.859 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:44:28.859 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputOpenReceiveChannel

Page 23: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:44:28.859 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:44:28.859 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53294d8 12:44:28.859 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 12:44:28.859 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:44:28.859 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53563d0 12:44:28.859 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:44:28.859 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:44:29.015 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x53294d8, Status=0, IpAddr=0x3863780a, Port=20106, PartyID=4 12:44:29.015 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:44:29.015 Cisco CallManager|StationD - RemoteIpAddr: 3863780a (10.120.99.5 RemoteRtpPortNumber: 20106 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:44:29.046 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x53563d0, Status=0, IpAddr=0x3963780a, Port=17412, PartyID=3 12:44:29.046 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:44:29.046 Cisco CallManager|StationD - RemoteIpAddr: 3963780a (10.120.99.5 RemoteRtpPortNumber: 17412 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:44:29.062 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:44:29.062 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:44:31.203 Cisco CallManager|StationInit - InboundStim - OnHookMessageID tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=3 lampMode=LampOff tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputStationDefineTimeDate

Page 24: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53294d8 12:44:31.218 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:44:31.218 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:44:31.218 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:44:31.218 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:44:31.218 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:44:31.218 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:44:31.218 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOff tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 12:44:31.218 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 12:44:37.937 Cisco CallManager|StationInit - New connection accepted. DeviceName=, TCPHandle=0x56b5668, Socket=0x51c, IPAddr=10.120.99.52, Port=49819, Device Controller=[0,0,0] 12:44:37.953 Cisco CallManager|StationInit - Processing StationReg. regCount: 1 DeviceName=MTP00D097386420, TCPHandle=0x56b5668, Socket=0x51c, IPAddr=10.120.99.52, Port=49819, Device Controller=[1,45,104] 12:44:37.953 Cisco CallManager|StationInit - InboundStim - IpPortMessageID: 0(0x0) tcpHandle=0x56b5668 12:44:38.093 Cisco CallManager|StationInit - StationCloseReq received: 0x56b5668 12:44:38.093 Cisco CallManager|***** StationInit - Socket Broken. DeviceName=, TCPHandle=0x56b5668, Socket=0x51c, IPAddr=10.120.99.52, Port=0xc29b, Device Controller=[0,0,0] 12:44:38.093 Cisco CallManager|StationInit - Closing Station connection DeviceName=MTP00D097386420, TCPHandle=0x56b5668, Socket=0x51c, IPAddr=10.120.99.52, Port=49819, Device Controller=[1,45,104] 12:44:38.093 Cisco CallManager|StationInit - StationCloseReq received: 0x56b5668

Call 1000-1111 (Full)

!--- Each timestamped line of output appears on one line. 12:42:43.734 Cisco CallManager|StationInit - InboundStim - StimulusMessageID stimulus: Line(9) Instance: 1 tcpHandle=0x53563d0

Page 25: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

12:42:43.734 Cisco CallManager|StationD - StimLine: OnHook --- OnHook 12:42:43.734 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 1 tcpHandle=0x53563d0 12:42:43.734 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x53563d0 12:42:43.734 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 12:42:43.734 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 12:42:43.734 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x53563d0 12:42:43.734 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:42:43.734 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:42:43.734 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:42:43.734 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 12:42:43.734 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="") 12:42:43.734 Cisco CallManager|Digit analysis: analysis results 12:42:43.750 Cisco CallManager| |PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern= |DialingRoutePatternRegularExpression= |DialingWhere= |PatternType=Unknown |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(0,0,0) |PretransformDigitString= |PretransformTagsList= |PretransformPositionalMatchList= |CollectedDigits= |TagsList= |PositionalMatchList= |RouteBlockFlag=BlockThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(1,82,1) |InterceptSsType=16777221 |InterceptSsKey=7864 12:42:43.750 Cisco CallManager|StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x53563d0 12:42:45.093 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:42:45.093 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 12:42:45.093 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:42:45.093 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="1") 12:42:45.093 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 12:42:45.453 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:42:45.453 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="11") 12:42:45.453 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 12:42:45.609 Cisco CallManager|CMProcMon - ------Entered Router Verification

Page 26: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

12:42:45.609 Cisco CallManager|CMProcMon - ----Exited Router Verification 12:42:45.656 Cisco CallManager|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP003094C2635E, TCPHandle=0x53563d0, Socket=0x528, IPAddr=10.120.99.57, Port=50491, Device Controller=[1,85,4] 12:42:45.656 Cisco CallManager|StationD - stationOutputKeepAliveAck tcpHandle=0x53563d0 12:42:45.781 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:42:45.781 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="111") 12:42:45.781 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 12:42:45.984 Cisco CallManager|StationInit - New connection accepted. DeviceName=, TCPHandle=0x56b8cf0, Socket=0x544, IPAddr=10.120.99.52, Port=49807, Device Controller=[0,0,0] 12:42:46.031 Cisco CallManager|StationInit - Processing StationReg. regCount: 1 DeviceName=MTP00D097386420, TCPHandle=0x56b8cf0, Socket=0x544, IPAddr=10.120.99.52, Port=49807, Device Controller=[1,45,93] 12:42:46.031 Cisco CallManager|StationInit - InboundStim - IpPortMessageID: 0(0x0) tcpHandle=0x56b8cf0 12:42:46.109 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="1111") 12:42:46.156 Cisco CallManager|Digit analysis: analysis results 12:42:46.156 Cisco CallManager| |PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern=1111 |DialingRoutePatternRegularExpression=(1111) |DialingWhere= |PatternType=Enterprise |PotentialMatches=NoPotentialMatchesExist |DialingSdlProcessId=(1,38,15) |PretransformDigitString=1111 |PretransformTagsList=SUBSCRIBER |PretransformPositionalMatchList=1111 |CollectedDigits=1111 |TagsList=SUBSCRIBER |PositionalMatchList=1111 |RouteBlockFlag=RouteThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(0,0,0) |InterceptSsType=0 |InterceptSsKey=0 12:42:46.156 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:42:46.156 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:42:46.156 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53294d8 12:42:46.156 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=3 lampMode=LampBlink tcpHandle=0x53294d8 12:42:46.156 Cisco CallManager|StationD - stationOutputSetRinger: 2=InsideRing tcpHandle=0x53294d8 12:42:46.156 Cisco CallManager|StationD - stationOutputDisplayNotify tcpHandle=0x53294d8

Page 27: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

12:42:46.156 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53294d8 12:42:46.156 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53294d8 12:42:46.156 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=, CalledParty=1111, tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:42:46.156 Cisco CallManager|NodeId: 1, EventId: 1513 EventClass: 6 EventInfo: Device Initialization Failed, Device Name=<MTP00D097386420>, Protocol= 12:42:47.609 Cisco CallManager|CMProcMon - ------Entered Router Verification12:42:47.609 Cisco CallManager|CMProcMon - ----Exited Router Verification 12:42:48.000 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x53294d8 12:42:48.000 Cisco CallManager|StationD - stationOutputClearNotify tcpHandle=0x53294d8 12:42:48.000 Cisco CallManager|StationD - stationOutputSetRinger: 1=RingOff tcpHandle=0x53294d8 12:42:48.000 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=3 lampMode=LampOn tcpHandle=0x53294d8 12:42:48.000 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:42:48.000 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53294d8 12:42:48.000 Cisco CallManager|ConnectionManager - wait_AuConnectRequest(16777231,16777232): INFORM MEDIA LAYER 12:42:48.000 Cisco CallManager|ConnectionManager - storeMediaInfo(16777231): ADD NEW ENTRY, tail == 1 12:42:48.000 Cisco CallManager|ConnectionManager - storeMediaInfo(16777232): ADD NEW ENTRY, tail == 2 12:42:48.000 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest() 12:42:48.000 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest - starting MediaManager w/ existing (0) connections 12:42:48.015 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest - new MediaManager(44,1) started 12:42:48.015 Cisco CallManager|MediaManager(1) started 12:42:48.015 Cisco CallManager|MediaManager - wait_AuConnectRequest 12:42:48.015 Cisco CallManager|MediaManager - wait_AuConnectRequest - party1(16777231), party2(16777232), proxies=0, connections=1, current proxies=0 12:42:48.015 Cisco CallManager|MediaManager - wait_AuConnectRequest - normal connection 12:42:48.031 Cisco CallManager|MediaManager - wait_AuConnectReply 12:42:48.031 Cisco CallManager|MediaManager - wait_AuConnectReply - received 1 responses, fowarding reply for party1(16777231) and party2(16777232) 12:42:48.031 Cisco CallManager|MediaCoordinator - wait_AuConnectReply 12:42:48.031 Cisco CallManager|ConnectionManager - wait_AuConnectReply(16777231,16777232) 12:42:48.031 Cisco CallManager|StationD - stationOutputStopTone

Page 28: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53563d0 12:42:48.031 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:42:48.031 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:42:48.031 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53294d8 12:42:48.031 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:42:48.031 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:42:48.046 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53294d8 12:42:48.046 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:42:48.046 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53294d8 12:42:48.046 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53294d8 12:42:48.046 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53294d8 12:42:48.046 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 12:42:48.046 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:42:48.046 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=Dave (1111), CalledParty=1111, tcpHandle=0x53563d0 12:42:48.046 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 12:42:48.046 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:42:48.156 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x53563d0, Status=0, IpAddr=0x3963780a, Port=23706, PartyID=1 12:42:48.156 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:42:48.156 Cisco CallManager|StationD - RemoteIpAddr: 3963780a (10.120.99.5 RemoteRtpPortNumber: 23706 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:42:48.218 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x53294d8, Status=0, IpAddr=0x3863780a, Port=18218, PartyID=2 12:42:48.218 Cisco CallManager|MediaManager - wait_AuConnectInfo 12:42:48.218 Cisco CallManager|MediaManager - wait_AuConnectInfo - recieved response, fowarding 12:42:48.218 Cisco CallManager|MediaCoordinator - wait_AuConnectInfoInd 12:42:48.218 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:42:48.218 Cisco CallManager|StationD - RemoteIpAddr: 3863780a (10.120.99.5 RemoteRtpPortNumber: 18218 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 12:42:48.218 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:42:48.218 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:42:49.609 Cisco CallManager|CMProcMon - ------Entered Router Verification12:42:49.609 Cisco CallManager|CMProcMon - ----Exited Router Verification 12:42:50.765 Cisco CallManager|StationInit - InboundStim - OnHookMessageID tcpHandle=0x53294d8 12:42:50.765 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2

Page 29: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=3 lampMode=LampOff tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53294d8 12:42:50.781 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:42:50.781 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 12:42:50.781 Cisco CallManager|ConnectionManager - wait_AuDisconnectRequest(16777232,16777231): STOP SESSION 12:42:50.781 Cisco CallManager|ConnectionManager - storeMediaInfo(16777232): EXISTING ENTRY DISCOVERED, tail == 2 12:42:50.781 Cisco CallManager|ConnectionManager - storeMediaInfo(16777231): EXISTING ENTRY DISCOVERED, tail == 2 12:42:50.781 Cisco CallManager|MediaCoordinator - wait_AuDisconnectRequest 12:42:50.781 Cisco CallManager|MediaCoordinator - wait_AuDisconnectRequest - sending disconnect to MediaManager(1) 12:42:50.781 Cisco CallManager|MediaManager - wait_AuDisconnectRequest 12:42:50.781 Cisco CallManager|MediaManager - wait_AuDisconnectRequest - StopSession sending disconnect to (64,1) and remove connection from list 12:42:50.796 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:42:50.796 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 12:42:50.796 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:42:50.796 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x53294d8 myIP: 3863780a (10.120.99.56) 12:42:50.796 Cisco CallManager|MediaManager - wait_AuDisconnectReply 12:42:50.796 Cisco CallManager|MediaManager - wait_AuDisconnectReply - received all disconnect replies, forwarding a reply for party1(16777232) and party2(16777231) 12:42:50.796 Cisco CallManager|MediaCoordinator - wait_AuDisconnectReply 12:42:50.796 Cisco CallManager|MediaCoordinator - wait_AuDisconnectReply - removing MediaManager(1) from connection list 12:42:50.796 Cisco CallManager|ConnectionManager - wait_AuDisconnectReply(16777232,16777231): STOP SESSION 12:42:50.796 Cisco CallManager|ConnectionManager - deleteMediaInfoEntry(16777232): ENTRY DELETED, tail == 1 12:42:50.796 Cisco CallManager|ConnectionManager - deleteMediaInfoEntry(16777231): ENTRY DELETED, tail == 0 12:42:50.796 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 12:42:50.796 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x53563d0 12:42:50.796 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x53563d0 12:42:50.796 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 12:42:50.812 Cisco CallManager|StationD - stationOutputSelectSoftKeys

Page 30: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53563d0 12:42:50.812 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 12:42:50.812 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 12:42:50.812 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOff tcpHandle=0x53563d0 12:42:50.812 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 12:42:50.812 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0

Call 1211

!--- Each timestamped line of output appears on one line. 14:05:34.562 Cisco CallManager|StationInit - InboundStim - StimulusMessageID stimulus: Line(9) Instance: 1 tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|StationD - StimLine: OnHook --- OnHook 14:05:34.562 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 1 tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 14:05:34.562 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 14:05:34.562 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 14:05:34.562 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="") 14:05:34.562 Cisco CallManager|Digit analysis: analysis results 14:05:34.562 Cisco CallManager| |PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern= |DialingRoutePatternRegularExpression= |DialingWhere= |PatternType=Unknown |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(0,0,0) |PretransformDigitString= |PretransformTagsList= |PretransformPositionalMatchList= |CollectedDigits= |TagsList= |PositionalMatchList= |RouteBlockFlag=BlockThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(1,82,1)

Page 31: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

|InterceptSsType=16777221 |InterceptSsKey=7864 14:05:34.562 Cisco CallManager|StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x53563d0 14:05:34.671 Cisco CallManager|CMProcMon - ------Entered Router Verification14:05:34.671 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:05:35.671 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:05:35.671 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:05:35.671 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:05:35.671 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="1") 14:05:35.671 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 14:05:36.125 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 2 tcpHandle=0x53563d0 14:05:36.125 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="12") 14:05:36.125 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 14:05:36.578 Cisco CallManager|StationInit - New connection accepted. DeviceName=, TCPHandle=0x56c7818, Socket=0x5c0, IPAddr=10.120.99.52, Port=49542, Device Controller=[0,0,0] 14:05:36.578 Cisco CallManager|StationInit - Processing StationReg. regCount: 1 DeviceName=MTP00D097386420, TCPHandle=0x56c7818, Socket=0x5c0, IPAddr=10.120.99.52, Port=49542, Device Controller=[1,45,578] 14:05:36.578 Cisco CallManager|StationInit - InboundStim - IpPortMessageID: 0(0x0) tcpHandle=0x56c7818 14:05:36.640 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:05:36.671 Cisco CallManager|CMProcMon - ------Entered Router Verification14:05:36.671 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:05:36.703 Cisco CallManager|NodeId: 1, EventId: 1506 EventClass: 6 EventInfo: Device not started since a database error occurred when port 0.0 tried to retrieve its device settings 14:05:36.703 Cisco CallManager|StationInit - StationCloseReq received: 0x56c7818 14:05:36.703 Cisco CallManager|NodeId: 1, EventId: 1698 EventClass: 4 EventInfo: Station Connection Error. Device Name=<MTP00D0973864214:05:36.703 Cisco CallManager|***** StationInit - Socket Broken. DeviceName=, TCPHandle=0x56c7818, Socket=0x5c0, IPAddr=10.120.99.52, Port=0xc186, Device Controller=[0,0,0] 14:05:36.703 Cisco CallManager|StationInit - Closing Station connection DeviceName=MTP00D097386420, TCPHandle=0x56c7818, Socket=0x5c0, IPAddr=10.120.99.52, Port=49542, Device Controller=[1,45,578] 14:05:36.703 Cisco CallManager|StationInit - StationCloseReq received: 0x56c7818 14:05:36.703 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="121") 14:05:36.703 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 14:05:36.718 Cisco CallManager|NodeId: 1, EventId: 1513 EventClass: 6 EventInfo: Device Initialization Failed, Device Name=<MTP00D097386420>, Protocol= 14:05:36.843 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:05:36.843 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="1211") 14:05:36.843 Cisco CallManager|Digit analysis: analysis results 14:05:36.843 Cisco CallManager| |PretransformCallingPartyNumber=1000

Page 32: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

|CallingPartyNumber=1000 |DialingPartition= |DialingPattern=1211 |DialingRoutePatternRegularExpression=(1211) |DialingWhere= |PatternType=Enterprise |PotentialMatches=NoPotentialMatchesExist |DialingSdlProcessId=(1,38,19) |PretransformDigitString=1211 |PretransformTagsList=SUBSCRIBER |PretransformPositionalMatchList=1211 |CollectedDigits=1211 |TagsList=SUBSCRIBER |PositionalMatchList=1211 |RouteBlockFlag=RouteThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(0,0,0) |InterceptSsType=0 |InterceptSsKey=0 14:05:36.843 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:05:36.843 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:05:36.843 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=1211, CalledParty=1211, tcpHandle=0x56ca080 14:05:36.843 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=4 lampMode=LampBlink tcpHandle=0x56ca080 14:05:36.843 Cisco CallManager|StationD - stationOutputSetRinger: 2=InsideRin tcpHandle=0x56ca080 14:05:36.843 Cisco CallManager|StationD - stationOutputDisplayNotify tcpHandle=0x56ca080 14:05:36.843 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:05:36.859 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:05:36.859 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:05:36.859 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=, CalledParty=1211, tcpHandle=0x53563d0 14:05:36.859 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=1211, CalledParty=1211, tcpHandle=0x53563d0 14:05:36.859 Cisco CallManager|StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x53563d0 14:05:36.859 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:05:36.859 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:05:36.859 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:05:38.671 Cisco CallManager|CMProcMon - ------Entered Router Verification14:05:38.671 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:05:40.218 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x56ca080 14:05:40.218 Cisco CallManager|StationD - stationOutputClearNotify tcpHandle=0x56ca080 14:05:40.218 Cisco CallManager|StationD - stationOutputSetRinger: 1=RingOff tcpHandle=0x56ca080 14:05:40.218 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=4 lampMode=LampOn tcpHandle=0x56ca080

Page 33: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

14:05:40.218 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:05:40.218 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x56ca080 14:05:40.218 Cisco CallManager|ConnectionManager - wait_AuConnectRequest(16777273,16777274): INFORM MEDIA LAYER 14:05:40.218 Cisco CallManager|ConnectionManager - storeMediaInfo(16777273): ADD NEW ENTRY, tail == 1 14:05:40.218 Cisco CallManager|ConnectionManager - storeMediaInfo(16777274): ADD NEW ENTRY, tail == 2 14:05:40.218 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest() 14:05:40.218 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest - starting MediaManager w/ existing (0) connections 14:05:40.218 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest - new MediaManager(44,6) started 14:05:40.218 Cisco CallManager|MediaManager(6) started 14:05:40.218 Cisco CallManager|MediaManager - wait_AuConnectRequest 14:05:40.218 Cisco CallManager|MediaManager - wait_AuConnectRequest - party1(16777273), party2(16777274), proxies=0, connections=1, current proxies=0 14:05:40.218 Cisco CallManager|MediaManager - wait_AuConnectRequest - normal connection 14:05:40.234 Cisco CallManager|MediaManager - wait_AuConnectReply 14:05:40.234 Cisco CallManager|MediaManager - wait_AuConnectReply - received 1 responses, fowarding reply for party1(16777273) and party2(16777274) 14:05:40.234 Cisco CallManager|MediaCoordinator - wait_AuConnectReply 14:05:40.234 Cisco CallManager|ConnectionManager - wait_AuConnectReply(16777273,16777274) 14:05:40.234 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:05:40.234 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:05:40.234 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:05:40.234 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:05:40.234 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:05:40.234 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:05:40.234 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:05:40.234 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:05:40.234 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=1211, CalledParty=1211, tcpHandle=0x56ca080 14:05:40.234 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:05:40.234 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:05:40.234 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:05:40.234 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:05:40.234 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=1211, CalledParty=1211, tcpHandle=0x53563d0 14:05:40.234 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:05:40.234 Cisco CallManager|StationD - stationOutputDisplayPromptStatus

Page 34: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53563d0 14:05:40.375 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x56ca080, Status=0, IpAddr=0x3863780a, Port=18094, PartyID=12 14:05:40.375 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:05:40.375 Cisco CallManager|StationD - RemoteIpAddr: 3863780a (10.120.99.5 RemoteRtpPortNumber: 18094 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:05:40.437 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x53563d0, Status=0, IpAddr=0x3963780a, Port=29436, PartyID=11 14:05:40.437 Cisco CallManager|MediaManager - wait_AuConnectInfo 14:05:40.437 Cisco CallManager|MediaManager - wait_AuConnectInfo - recieved response, fowarding 14:05:40.437 Cisco CallManager|MediaCoordinator - wait_AuConnectInfoInd 14:05:40.437 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:05:40.437 Cisco CallManager|StationD - RemoteIpAddr: 3963780a (10.120.99.5 RemoteRtpPortNumber: 29436 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:05:40.437 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:05:40.437 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:05:40.671 Cisco CallManager|CMProcMon - ------Entered Router Verification14:05:40.671 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:05:42.421 Cisco CallManager|StationInit - InboundStim - OnHookMessageID tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=4 lampMode=LampOff tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:05:42.421 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:05:42.421 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:05:42.421 Cisco CallManager|ConnectionManager - wait_AuDisconnectRequest(16777274,16777273): STOP SESSION 14:05:42.421 Cisco CallManager|ConnectionManager - storeMediaInfo(16777274): EXISTING ENTRY DISCOVERED, tail == 2 14:05:42.421 Cisco CallManager|ConnectionManager - storeMediaInfo(16777273): EXISTING ENTRY DISCOVERED, tail == 2 14:05:42.421 Cisco CallManager|MediaCoordinator - wait_AuDisconnectRequest 14:05:42.421 Cisco CallManager|MediaCoordinator - wait_AuDisconnectRequest - sending disconnect to MediaManager(6) 14:05:42.421 Cisco CallManager|MediaManager - wait_AuDisconnectRequest 14:05:42.421 Cisco CallManager|MediaManager - wait_AuDisconnectRequest - StopSession sending disconnect to (64,6) and remove connection from list

Page 35: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

14:05:42.421 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:05:42.421 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:05:42.421 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:05:42.421 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:05:42.421 Cisco CallManager|MediaManager - wait_AuDisconnectReply 14:05:42.421 Cisco CallManager|MediaManager - wait_AuDisconnectReply - received all disconnect replies, forwarding a reply for party1(16777274) and party2(16777273) 14:05:42.421 Cisco CallManager|MediaCoordinator - wait_AuDisconnectReply 14:05:42.421 Cisco CallManager|MediaCoordinator - wait_AuDisconnectReply - removing MediaManager(6) from connection list 14:05:42.421 Cisco CallManager|ConnectionManager - wait_AuDisconnectReply(16777274,16777273): STOP SESSION 14:05:42.421 Cisco CallManager|ConnectionManager - deleteMediaInfoEntry(16777274): ENTRY DELETED, tail == 1 14:05:42.421 Cisco CallManager|ConnectionManager - deleteMediaInfoEntry(16777273): ENTRY DELETED, tail == 0 14:05:42.421 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOff tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 14:05:42.421 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0

Call 1311 (Short)

!--- Each timestamped line of output appears on one line. 14:39:04.296 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x53563d0 14:39:04.296 Cisco CallManager|StationD - StimLine: OnHook --- OnHook 14:39:04.296 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 1 tcpHandle=0x53563d0 14:39:04.296 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 14:39:04.296 Cisco CallManager|StationD - stationOutputDisplayText tcpHandle=0x53563d0, Display=1000 14:39:04.296 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x53563d0 14:39:04.296 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:39:04.296 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:39:04.296 Cisco CallManager|StationD - stationOutputSelectSoftKeys

Page 36: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53563d0 14:39:04.296 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 14:39:04.296 Cisco CallManager|StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x53563d0 14:39:05.109 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:39:05.109 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:39:05.109 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:39:05.656 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 3 tcpHandle=0x53563d0 14:39:06.125 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:39:06.453 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:39:09.453 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:39:09.453 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:39:09.453 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x56ca08014:39:09.453 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=2 lampMode=LampBlink tcpHandle=0x56ca080 14:39:09.453 Cisco CallManager|StationD - stationOutputSetRinger: 2=InsideRing tcpHandle=0x56ca080 14:39:09.453 Cisco CallManager|StationD - stationOutputDisplayNotify tcpHandle=0x56ca080 14:39:09.453 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:39:09.453 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:39:09.453 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:39:09.453 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=, CalledParty=1311, tcpHandle=0x53563d0 14:39:09.453 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x53563d014:39:09.453 Cisco CallManager|StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x53563d0 14:39:09.453 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:39:09.453 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:39:09.453 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:39:11.656 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x56ca080 14:39:11.656 Cisco CallManager|StationD - stationOutputClearNotify tcpHandle=0x56ca080 14:39:11.656 Cisco CallManager|StationD - stationOutputSetRinger: 1=RingOff tcpHandle=0x56ca080 14:39:11.656 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=2 lampMode=LampOn tcpHandle=0x56ca080 14:39:11.656 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:39:11.656 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x56ca080 14:39:11.671 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0

Page 37: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

14:39:11.671 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:39:11.671 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:39:11.671 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:39:11.671 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:39:11.671 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:39:11.671 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:39:11.671 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:39:11.671 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x56ca08014:39:11.671 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:39:11.671 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:39:11.671 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:39:11.671 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:39:11.671 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x53563d014:39:11.671 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:39:11.671 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:39:11.859 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x53563d0, Status=0, IpAddr=0x3963780a, Port=17594, PartyID=15 14:39:11.859 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:39:11.859 Cisco CallManager|StationD - RemoteIpAddr: 3963780a (10.120.99.5 RemoteRtpPortNumber: 17594 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:39:11.859 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x56ca080, Status=0, IpAddr=0x3863780a, Port=18540, PartyID=16 14:39:11.859 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:39:11.859 Cisco CallManager|StationD - RemoteIpAddr: 3863780a (10.120.99.5 RemoteRtpPortNumber: 18540 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:39:11.859 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:39:11.859 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:39:14.203 Cisco CallManager|StationInit - InboundStim - OnHookMessageID tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080

Page 38: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

14:39:14.203 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=2 lampMode=LampOff tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:39:14.203 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:39:14.203 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:39:14.203 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:39:14.203 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:39:14.203 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:39:14.203 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:39:14.203 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOff tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 14:39:14.203 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:39:15.359 Cisco CallManager|StationInit - InboundStim - KeepAliveMessage - Send KeepAlive to Device Controller. DeviceName=SEP003094C2635E, TCPHandle=0x53563d0, Socket=0x528, IPAddr=10.120.99.57, Port=50491, Device Controller=[1,85,4] 14:39:15.359 Cisco CallManager|StationD - stationOutputKeepAliveAck tcpHandle=0x53563d0

Call 1311 (Full)

!--- Each timestamped line of output appears on one line. 14:35:26.015 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOff tcpHandle=0x53563d0 14:35:26.015 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 14:35:26.015 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:35:26.093 Cisco CallManager|CMProcMon - ------Entered Router Verification14:35:26.093 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:35:26.500 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x53563d0 14:35:26.500 Cisco CallManager|StationD - stationOutputDisplayText

Page 39: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x53563d0, Display= 1000 14:35:26.500 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOn tcpHandle=0x53563d0 14:35:26.500 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:35:26.500 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:35:26.500 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:35:26.500 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 14:35:26.500 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="") 14:35:26.500 Cisco CallManager|Digit analysis: analysis results 14:35:26.500 Cisco CallManager| |PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern= |DialingRoutePatternRegularExpression= |DialingWhere= |PatternType=Unknown |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(0,0,0) |PretransformDigitString= |PretransformTagsList= |PretransformPositionalMatchList= |CollectedDigits= |TagsList= |PositionalMatchList= |RouteBlockFlag=BlockThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(1,82,1) |InterceptSsType=16777221 |InterceptSsKey=7864 14:35:26.500 Cisco CallManager|StationD - stationOutputStartTone: 33=InsideDialTone tcpHandle=0x53563d0 14:35:27.578 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:35:27.578 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:35:27.578 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:35:27.578 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="1") 14:35:27.578 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 14:35:27.890 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 3 tcpHandle=0x53563d0 14:35:27.890 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="13") 14:35:27.890 Cisco CallManager|Digit analysis: potentialMatches=PotentialMatchesExist 14:35:28.093 Cisco CallManager|CMProcMon - ------Entered Router Verification14:35:28.093 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:35:28.406 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:35:28.406 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="131") 14:35:28.406 Cisco CallManager|Digit analysis: analysis results 14:35:28.421 Cisco CallManager| |PretransformCallingPartyNumber=1000

Page 40: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

|CallingPartyNumber=1000 |DialingPartition= |DialingPattern=131 |DialingRoutePatternRegularExpression=(131) |DialingWhere= |PatternType=Enterprise |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(1,38,22) |PretransformDigitString=131 |PretransformTagsList=SUBSCRIBER |PretransformPositionalMatchList=131 |CollectedDigits=131 |TagsList=SUBSCRIBER |PositionalMatchList=131 |RouteBlockFlag=RouteThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(0,0,0) |InterceptSsType=0 |InterceptSsKey=0 14:35:28.718 Cisco CallManager|StationInit - New connection accepted. DeviceName=, TCPHandle=0x56d5278, Socket=0x64c, IPAddr=10.120.99.52, Port=49539, Device Controller=[0,0,0] 14:35:28.718 Cisco CallManager|StationInit - Processing StationReg. regCount: 1 DeviceName=MTP00D097386420, TCPHandle=0x56d5278, Socket=0x64c, IPAddr=10.120.99.52, Port=49539, Device Controller=[1,45,751] 14:35:28.718 Cisco CallManager|StationInit - InboundStim - IpPortMessageID: 0(0x0) tcpHandle=0x56d5278 14:35:28.828 Cisco CallManager|NodeId: 1, EventId: 1506 EventClass: 6 EventInfo: Device not started since a database error occurred when port 0.0 tried to retrieve its device settings 14:35:28.828 Cisco CallManager|StationInit - StationCloseReq received: 0x56d5278 14:35:28.828 Cisco CallManager|NodeId: 1, EventId: 1698 EventClass: 4 EventInfo: Station Connection Error. Device Name=<MTP00D0973864214:35:28.828 Cisco CallManager|***** StationInit - Socket Broken. DeviceName=, TCPHandle=0x56d5278, Socket=0x64c, IPAddr=10.120.99.52, Port=0xc183, Device Controller=[0,0,0] 14:35:28.828 Cisco CallManager|StationInit - Closing Station connection DeviceName=MTP00D097386420, TCPHandle=0x56d5278, Socket=0x64c, IPAddr=10.120.99.52, Port=49539, Device Controller=[1,45,751] 14:35:28.828 Cisco CallManager|StationInit - StationCloseReq received: 0x56d5278 14:35:28.828 Cisco CallManager|NodeId: 1, EventId: 1513 EventClass: 6 EventInfo: Device Initialization Failed, Device Name=<MTP00D097386420>, Protocol= 14:35:28.937 Cisco CallManager|StationInit - InboundStim - KeypadButtonMessageID kpButton: 1 tcpHandle=0x53563d0 14:35:28.937 Cisco CallManager|Digit analysis: match(fqcn="", cn="1000", pss="", dd="1311") 14:35:28.937 Cisco CallManager|Digit analysis: analysis results 14:35:28.937 Cisco CallManager| |PretransformCallingPartyNumber=1000 |CallingPartyNumber=1000 |DialingPartition= |DialingPattern=13[0-4]X |DialingRoutePatternRegularExpression=(13[0-4]X) |DialingWhere= |PatternType=Enterprise |PotentialMatches=PotentialMatchesExist |DialingSdlProcessId=(1,38,21) |PretransformDigitString=1311

Page 41: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

|PretransformTagsList=SUBSCRIBER |PretransformPositionalMatchList=1311 |CollectedDigits=1311 |TagsList=SUBSCRIBER |PositionalMatchList=1311 |RouteBlockFlag=RouteThisPattern |InterceptPartition= |InterceptPattern= |InterceptWhere= |InterceptSdlProcessId=(0,0,0) |InterceptSsType=0 |InterceptSsKey=0 14:35:30.093 Cisco CallManager|CMProcMon - ------Entered Router Verification14:35:30.093 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:35:31.937 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:35:31.937 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:35:31.937 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x56ca08014:35:31.937 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=2 lampMode=LampBlink tcpHandle=0x56ca080 14:35:31.937 Cisco CallManager|StationD - stationOutputSetRinger: 2=InsideRing tcpHandle=0x56ca080 14:35:31.937 Cisco CallManager|StationD - stationOutputDisplayNotify tcpHandle=0x56ca080 14:35:31.937 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:35:31.937 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:35:31.937 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:35:31.937 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=, CalledParty=1311, tcpHandle=0x53563d0 14:35:31.937 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x53563d014:35:31.937 Cisco CallManager|StationD - stationOutputStartTone: 36=AlertingTone tcpHandle=0x53563d0 14:35:31.937 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:35:31.937 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:35:31.937 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:35:32.093 Cisco CallManager|CMProcMon - ------Entered Router Verification14:35:32.093 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:35:33.421 Cisco CallManager|StationInit - InboundStim - OffHookMessageID tcpHandle=0x56ca080 14:35:33.421 Cisco CallManager|StationD - stationOutputClearNotify tcpHandle=0x56ca080 14:35:33.421 Cisco CallManager|StationD - stationOutputSetRinger: 1=RingOff tcpHandle=0x56ca080 14:35:33.421 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=2 lampMode=LampOn tcpHandle=0x56ca080 14:35:33.421 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:35:33.421 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x56ca080 14:35:33.421 Cisco CallManager|ConnectionManager - wait_AuConnectRequest(16777277,16777278): INFORM MEDIA LAYER 14:35:33.421 Cisco CallManager|ConnectionManager -

Page 42: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

storeMediaInfo(16777277): ADD NEW ENTRY, tail == 1 14:35:33.421 Cisco CallManager|ConnectionManager - storeMediaInfo(16777278): ADD NEW ENTRY, tail == 2 14:35:33.421 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest() 14:35:33.421 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest - starting MediaManager w/ existing (0) connections 14:35:33.421 Cisco CallManager|MediaCoordinator - wait_AuConnectRequest - new MediaManager(44,7) started 14:35:33.421 Cisco CallManager|MediaManager(7) started 14:35:33.421 Cisco CallManager|MediaManager - wait_AuConnectRequest 14:35:33.421 Cisco CallManager|MediaManager - wait_AuConnectRequest - party1(16777277), party2(16777278), proxies=0, connections=1, current proxies=0 14:35:33.421 Cisco CallManager|MediaManager - wait_AuConnectRequest - normal connection 14:35:33.421 Cisco CallManager|MediaManager - wait_AuConnectReply 14:35:33.421 Cisco CallManager|MediaManager - wait_AuConnectReply - received 1 responses, fowarding reply for party1(16777277) and party2(16777278) 14:35:33.421 Cisco CallManager|MediaCoordinator - wait_AuConnectReply 14:35:33.421 Cisco CallManager|ConnectionManager - wait_AuConnectReply(16777277,16777278) 14:35:33.421 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:35:33.437 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:35:33.437 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:35:33.437 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:35:33.437 Cisco CallManager|StationD - stationOutputOpenReceiveChannel tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:35:33.437 Cisco CallManager|StationD - ConferenceID: 0 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:35:33.437 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:35:33.437 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:35:33.437 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x56ca08014:35:33.437 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:35:33.437 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:35:33.437 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0 14:35:33.437 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:35:33.437 Cisco CallManager|StationD - stationOutputCallInfo CallingPartyName=Markus (1000), CallingParty=1000, CalledPartyName=13[0-4]X, CalledParty=1311, tcpHandle=0x53563d014:35:33.437 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:35:33.437 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:35:33.546 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x56ca080, Status=0, IpAddr=0x3863780a, Port=17190, PartyID=14 14:35:33.546 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:35:33.546 Cisco CallManager|StationD - RemoteIpAddr: 3863780a (10.120.99.5 RemoteRtpPortNumber: 17190 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k

Page 43: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

14:35:33.562 Cisco CallManager|StationInit - InboundStim - StationOpenReceiveChannelAckID tcpHandle=0x53563d0, Status=0, IpAddr=0x3963780a, Port=28532, PartyID=13 14:35:33.562 Cisco CallManager|MediaManager - wait_AuConnectInfo 14:35:33.562 Cisco CallManager|MediaManager - wait_AuConnectInfo - recieved response, fowarding 14:35:33.562 Cisco CallManager|MediaCoordinator - wait_AuConnectInfoInd 14:35:33.562 Cisco CallManager|StationD - stationOutputStartMediaTransmission tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:35:33.562 Cisco CallManager|StationD - RemoteIpAddr: 3963780a (10.120.99.5 RemoteRtpPortNumber: 28532 msecPacketSize: 20 compressionType:(4)Media_Payload_G711Ulaw64k 14:35:33.562 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:35:33.562 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:35:34.093 Cisco CallManager|CMProcMon - ------Entered Router Verification14:35:34.093 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:35:36.093 Cisco CallManager|CMProcMon - ------Entered Router Verification14:35:36.093 Cisco CallManager|CMProcMon - ----Exited Router Verification 14:35:36.093 Cisco CallManager|StationInit - InboundStim - OnHookMessageID tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=2 lampMode=LampOff tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x56ca080 14:35:36.093 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:35:36.093 Cisco CallManager|Locations: Orig=0 BW=-1 Dest=0 BW=-1 (-1 implies infinite bw available) 14:35:36.093 Cisco CallManager|ConnectionManager - wait_AuDisconnectRequest(16777278,16777277): STOP SESSION 14:35:36.093 Cisco CallManager|ConnectionManager - storeMediaInfo(16777278): EXISTING ENTRY DISCOVERED, tail == 2 14:35:36.093 Cisco CallManager|ConnectionManager - storeMediaInfo(16777277): EXISTING ENTRY DISCOVERED, tail == 2 14:35:36.093 Cisco CallManager|MediaCoordinator - wait_AuDisconnectRequest 14:35:36.093 Cisco CallManager|MediaCoordinator - wait_AuDisconnectRequest - sending disconnect to MediaManager(7) 14:35:36.093 Cisco CallManager|MediaManager - wait_AuDisconnectRequest 14:35:36.093 Cisco CallManager|MediaManager - wait_AuDisconnectRequest - StopSession sending disconnect to (64,7) and remove connection from list 14:35:36.093 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:35:36.093 Cisco CallManager|StationD - stationOutputStopMediaTransmission tcpHandle=0x53563d0 myIP: 3963780a (10.120.99.57) 14:35:36.093 Cisco CallManager|StationD - stationOutputCloseReceiveChannel tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:35:36.093 Cisco CallManager|StationD - stationOutputStopMediaTransmission

Page 44: Understanding and Troubleshooting Call Routing and · PDF fileUnderstanding and Troubleshooting Call Routing and Dial Pattern Problems with Cisco CallManager ... zUsers cannot dial

tcpHandle=0x56ca080 myIP: 3863780a (10.120.99.56) 14:35:36.093 Cisco CallManager|MediaManager - wait_AuDisconnectReply 14:35:36.109 Cisco CallManager|MediaManager - wait_AuDisconnectReply - received all disconnect replies, forwarding a reply for party1(16777278) and party2(16777277) 14:35:36.109 Cisco CallManager|MediaCoordinator - wait_AuDisconnectReply 14:35:36.109 Cisco CallManager|MediaCoordinator - wait_AuDisconnectReply - removing MediaManager(7) from connection list 14:35:36.109 Cisco CallManager|ConnectionManager - wait_AuDisconnectReply(16777278,16777277): STOP SESSION 14:35:36.109 Cisco CallManager|ConnectionManager - deleteMediaInfoEntry(16777278): ENTRY DELETED, tail == 1 14:35:36.109 Cisco CallManager|ConnectionManager - deleteMediaInfoEntry(16777277): ENTRY DELETED, tail == 0 14:35:36.109 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputSetSpeakerMode: 2 tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputClearStatus tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputCallState tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputSelectSoftKeys tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputDisplayPromptStatus tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputActivateCallPlane tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputSetLamp stim: 9=Line instance=1 lampMode=LampOff tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputStationDefineTimeDate tcpHandle=0x53563d0 14:35:36.109 Cisco CallManager|StationD - stationOutputStopTone tcpHandle=0x53563d0

Related Information Voice Technology Support Voice and Unified Communications Product Support Recommended Reading: Troubleshooting Cisco IP Telephony Technical Support & Documentation - Cisco Systems

Contacts & Feedback | Help | Site Map © 2008 - 2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of Cisco Systems, Inc.