dokucama

This is an old revision of the document!

To access all docs:
Log in to Cisco Learning Network Space using your Cisco.com ID: https://learningspace.cisco.com/
My Content' > CTCOLLAB - Student Guide # Also use local docs via cisco edoc reader

TROUBLESHOOTING TOOLS OVERVIEW

• RTMT: For traces and syslog + Real time graphs.
  • SDI, SDL (Signal Distr. Layer), Log4j
  • StationInit : Coming from the phone
  • ToD filter (time of the day (routing can change depending on time)
• CUCM-SERVICEABILITY
  • DNA (Dialled Number Analyser): To 'emulate' a call, giving source and destination, provides its route.
    • Don't forget to Activate the service!
    • Troubleshoots dial plans
    • MatchResult ; BlockthisPattern (might denote CoS issues)
  • CMR (Call Management Record): For call quality
  • Control Center: To check, start and stop services
• REPORTS
  • Call plan report
  • Route Plan Report
• CUCM cli
  • If UI unavailable, one of the first things to check is Tomcat running (# utils service list ; # show network {if} detail)

PARTITIONS AND CSS (Call Search Spaces)

• Partition: Partition is group of number with Same Reachability. In order to make and receive calls, Phones/lines need to be in a Common Partition. By default in 'none' partition (so anybody can get to them).
• CSS: Comprises a set of partitions. Two lines can communicate if their CSS share partitions.

CUCM-ADMINISTRATION > CALL ROUTING > Class of  Control  > Calling Search Space  # To see the CSS
CUCM-ADMINISTRATION > CALL ROUTING > Class of  Control  > Partition  # To see the Partition

To control the order a call is routed
A route pattern comprises a string of digits (an address) and a set of associated digit manipulations that route calls to a route list or a gateway.

• Route list contains Route groups (contain one or more devices)
• Route pattern -contains→ Route list –> Route groups # See it in Route plan report

CUCM-ADMINISTRATION > CALL ROUTING > Route/Hunt > Route Pattern
CUCM-ADMINISTRATION > CALL ROUTING > Route Plan Report # To see Route. Column on the right: 'route list' , 'route group' , trunk ..

• 1st route group is normally wan (trunk)
• 2nd route group is normally pstn/gateway (mgcp)
• Route group 'linked' to a trunk

CUCM-ADMINISTRATION > CALL ROUTING > RouteHunt > Route List   # This is listing the order of preference above

• digit manipulations/regex: (!) wildcard matches one or more digits in the range 0 through 9 ; Example: 1.0[1-9]XXXX # dot meaning 'ignore before' (example of 9 at the beginning)See this LINK

CUCM availability
Example of cucm cli command. (find all in Link

utils service list [page]
* 80ms is maximum recommended from cucm to cucm
* Tomcat is usually a service to be checked if UI is down

utils dbreplication repair

• DB replication IDS (IBM Informix db type). Replication happens from Publisher to Subscribers so in case PUB dies, the SUB can take over.
• Config happens on publisher and then replicated. So if former is down we only see it when we click 'save'!
  • Check via cli , rtmt or Unified Reporting. If replication fails, no New configurations are possible.
    • # utils dbreplication status
    • CUCM-UNIFIED-REPORTING > System Reports > Unified CM Database Status
  • The replication status must be in “2”. Any other Replicate_State value is no good.
• We should put server to server traffic in LLQ
• External + Internal DNS

LDAP

  CUCM-ADMINISTRATION > System > LDAP authentication # CN = {user in ldap used to authenticate cucm}

• If we lose ldap, as passwords are never copied down to cucm, phone users won't be able to login
• Subscribers do Not replicate with ldap server, only publisher does..
• Container in ldap: Directories are extensible, meaning that the type of information stored can be modified and extended. The term directory schema defines the type of information stored, its container (or attribute), and its relationship to users and resources.

IMP

• In the future Cisco will implement this just as another CUCM service.
  • messaging
  • calls
  • file transfer

VCS

• Video communication server
• On VCS, most cli commands start with

xcommand …

Telepresence endpoint initialization (with the VCS) Registration can be done via h.323 and SIP.
VCS Bandwidth control

• Subzones
• Links
• Pipes
• Search rules (VCS) : Mechanism that affect where (when calling) I search. Used when the call alias is not found in the local zone. Eg: do local calls always win?

LDAP and VCS:
Troubleshooting calls

• trunks, pipes, search groups.
• VCS > Status > Search History # To see how a number can be routed.
• If mixing h.323 and SIP, do Configuration > Protocols > Internetworking

CALL SETUP TROUBLESHOOTING
SINGLE CLUSTER:

• issues: dead air (ring works but no media) ; one way media; unexpected 2nd dial tone ; no ring-back (meaning 'no ring').
• Review sip messages
• causes (single site): bad digit manipulation, unregistered target, CoS.
• 1st things to check

CUCM-ADMINISTRATION > CALL ROUTING > Route Plan Report # **Route Planner**

• Show partitions. In the right Side : route list, route group
• Then we can check DNA (RouteThisPattern in the result means call is Good)

CUCM-SERVICEABILITY >  Tools > DNA

• If we don't find the cause, we can do a Trace. Uses RTMT to read the traces (Remember is a local client that needs to be installed in your machine: CUCM > ADMIN > Applications > (Select RTMT and Windows (as it goes to your desktop!))
  • RTMT : Trace Log Central Remote browse (for any closed traces)
    • Real Time trace (category: UCM ; Services: Cisco CallManager ; Trace type : sdl)

MULTI-CLUSTER:

• causes (on top of the single site ones): lack of MTP resources
  • Route group Route list/Route group. Check it.
  • Very frequently is a DNS issues. Remember we need internal (between express gws) and external dns.
  • CUBE configuration : It is used to interconnect voice and video networks of Separate Domains with each other.
  • SIP trunk configuration
  • cRTP (compressed RTP) mismatch. ! Note that the compression applies to the Header (udp, and rtp headers)

CUCM DIGIT MANIPULATION

• least wildcarded is preferred
  • matches the dialed string
  • matches the fewer strings other than the dialed string
• Addressing method:
  • sccp : digit by digit (some telcos still require being sent digit by digit)
  • sip : en bloc

CUCM-ADMINISTRATION > CALL ROUTING > Class of  Control  > Calling Search Space

• same wildcarded number in different partitions: 1st partition is selected (order is taken into account)
• There's a Default/none partition

ToD (Time of Day Routing)
Tracing CSS:

• Name of the station
• Handler number (for the whole time the phone is registered)
• Caller phone and IP address (IP might change!)
• ToDFilteredPss
• fqcn (fully qualified calling number)
• 'Reorder tone' field is bad.

Call forwarding: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/manual/cmeadm/cmetrans.html

NUMBER APPEARANCE
This is for the calling groups and to present the correct number when ringing:

CUCM-ADMINISTRATION > System > Service Parameters > Advanced # Set 'Apply transformation on remote number'
CUCM-ADMINISTRATION > System > Device Pool

Calling search space ←→ Partition

JABBER (IM&P (IMP))
Possible issues (review slides in “troubleshooting unified communications mobile and remote access issues”

• Config files not downloaded to the local client
• Jabber windows uses old configuration settings. delete %AppData\Cisco\Unified Communications\Jabber\CSF Folder
• …

Prime Collaboration Assurance:

Monitor > System View > Cisco Jabber Summary   # Current connecter jabber clients to each of the im pub or subs

MULTISITE CALLING ISSUES

• Review possible causes in diagram.
  • Local and remote CoS
  • No pstn backup
• Route patterns use regex. Example: 1.0[1-9]XXXX # dot meaning 'ignore before' (example of 9 at the beginning)
  • Useful for the 911 testing. Cucm should expect 911#911. Otherwise 911# wont work
• In this scenario, both cucm don't share neither CSS nor Partition names.
• Important, again, is digit manipulation.
• Early offer vs Delayed offer (SIP) . Slow vs Fast start in h.323
• CUBE elements are used. This is the Session/Border controller. (analogous to the Avaya Session Manager)
  • Dial peers
  • Debug commands # debug h225 asn1 ! For h.323-sip scenarios)

debug ccsip all
show voip rtp connections

Example of dial-peer configuration in CUBE:

dial-peer voice 1 voip
 destination dpg 10000
 incoming calling e164-pattern-map 100
 dtmf-relay rtp-nte
 codec g711ulaw

• From CUCM to the local CUBE, we have SIP trunk.

OFF-NET CALLING ISSUES

• E.164 : This is The international public telecommunication numbering plan (ITU-T recommendation).
• MGCP gateway
• Cisco IOS gateways Collects Digits (from the calling party) until and match them with a Dial Peer
• dial-peer concept in cisco ios : like static routes. They define where calls originate and terminate and the path that the calls use through the network.
• Incoming number transformation pattern considerations
  • http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/3_3_2/ccmcfg/ccmcfg/b03spchr.pdf
  • DDI can be confusing in cisco jargon as it also means 'discard digits instruction'.
• Voice translation profiles (made of Voice translation Rules). Regex
  • Voice Translation Rules
  • 'caret' inside square brackets is 'exclude'.
  • /^123456/ /+4930&/ The 'ampersand' is used in the replace set to bring over anything that was matched in the match set.
• Troubleshoot Cisco Ios gateway dial plan:

show dial-peer voice ! this will show me also the destination/translation pattern

show dial-peer voice summary
show dualplan number  

* Troubleshoot SIP gateway issues
  * verify call setup in sip leg

show sip service
show sip-ua status   ! ua meaning user agent
debug ccsip calls

ILS (Intercluster Lookup System): This is to distribute URIs, numbers and patters among cucm CLUSTERS (cluster is publisher and subscribers)

• ILS is used to distribute directory, uris.. “I am the cluster and this is how you get to me”. Gatekeeper retrieve and register phone numbers. Provides the custer ips.
• Hub and spokes concept.
• Over TLS. Password and certificate needs to be distributed.

Another way is by h323 gatekeepers

CUCM Mobility issues

• Example is a softphone moving from ip to ip. The new ip will be associated to a new device pool.
• Concept of Mobility groups.

CISCO EXTENSION MOBILITY

• To be able to log into any phone.
• My user has a profile. Profile is associated to a line.
• A common error is user unable to Log Out. The Cisco Extension Mobility service is unavailable and the user is not offered the option to log out. This happens when the device profile to which the user is associated. Does not subscribe to the Cisco Extension Mobility service.

CUCM-ADMINISTRATION > DEVICE > Device Settings > Device Profile # verify the user device profile and subscribe it to the Cisco Extension Mobility Service.

* Also common are CoS broken with mobility
* If I make a call, you look at a route group. cucm says who is going to dial, looks at the pool and points to whatever route pool.
* Line CSS with Local Route Group

MOBILITY CONNECT: (in case we are remote and we don't even have Internet connectivity) Dial a public number, authenticate (that would be on a router) and be able to make calls from my office phone.

TelePresence Management suite (TMS)

• Is an application to Schedule conferences and to Control. Not required for VC to work!.
• Centralizes configuration management
• FindMe feature
  • Issues: FindMe Directory URI Call is disconnected

MTP Issues

• Media Termination Point (aka Voice Quality issues)
• alaw to ulaw
  • We can bridge both codecs by using payload and different sample sizes.
• H.323 outbound and fast start (for inbound mtp not required)
• NTEs are used for sending DTMF
• Skinny is used for cucm to allocate the resource.

• Put my email here: www.metricsthatmatter.com/glkukGerry Manunder CTCOLLAB
  • Gerry Manunder CTCOLLAB