Differences

This shows you the differences between two versions of the page.

--- unified_communications [2016/12/04 18:33] – jotasandoku
+++ unified_communications [2023/11/02 14:38] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+**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)
+  * 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 [[http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/3_3_2/ccmcfg/ccmcfg/b03spchr.pdf|LINK]]
@@ Line 26: / Line 57: @@
   * 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'!
@@ Line 34: / Line 67: @@
   * We should put server to server traffic in LLQ
   * External + Internal DNS
-  utils dbreplication repair
 ----
@@ Line 41: / Line 74: @@
 \\
     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..
@@ Line 46: / Line 80: @@
 ----
+**IMP**
+  * In the future Cisco will implement this just as another CUCM service.
+    * messaging
+    * calls
+    * file transfer
+----
 **VCS**
-On the vcs, most cli commands start with
+  * Video communication server
+  * On VCS, most cli commands start with
   xcommand ...
@@ Line 74: / Line 118: @@
   * 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)
@@ Line 99: / Line 147: @@
 \\
   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
@@ Line 116: / Line 165: @@
 ----
 **NUMBER APPEARANCE**\\
-This is for the calling groups and to present the correct number when ringing:\\
+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
+  CUCM-ADMINISTRATION > System > Service Parameters > Advanced # Set 'Apply transformation on remote number'
-  * Calling search space <--> Partition
+  CUCM-ADMINISTRATION > System > Device Pool
+Calling search space <--> Partition
 ----
+** JABBER - PRESENCE (IM&P (IMP))**\\
+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**
-**JABBER:**\\
+Service status
-Possible issues (review slides in "troubleshooting unified communications mobile and remote access issues"
+  CUIM > CUIM & Presence Serviceability >
-  * Config files not downloaded to the local client
+To see currently connected jabber clients to each of the im pub or subs:
-  * Jabber windows uses old configuration settings. delete %AppData\Cisco\Unified Communications\Jabber\CSF Folder
+  CISCO PRIME COLLABORATION A. > Monitor > System View > Cisco Jabber Summary  # Prime Collaboration Assurance
-  * ...
+  CUIM > CUIM & Presence Administration > System > Presence Topology
+To see where presence users are logged in and, if needed, move them overriding the Redundancy Groups:
+  CUCM > Administration > User Management > Assign Presence Users
 ----
 **MULTISITE CALLING ISSUES**
   * Review possible causes in diagram.
@@ Line 142: / Line 201: @@
     * Dial peers
     * Debug commands # debug h225 asn1 ! For h.323-sip scenarios)
   debug ccsip all
   show voip rtp connections
@@ Line 170: / Line 230: @@
   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
@@ Line 179: / Line 241: @@
 ----
 **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.
@@ Line 184: / Line 247: @@
 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.
+  * 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.
+  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 Groupe
+  * 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!.
@@ Line 206: / Line 281: @@
   * FindMe feature
     * Issues: FindMe Directory URI Call is disconnected
 ----
 **MTP Issues**
   * Media Termination Point (aka Voice Quality issues)
@@ Line 216: / Line 294: @@
 ----
   * Put my email here: www.metricsthatmatter.com/glkukGerry Manunder CTCOLLAB
     * Gerry Manunder CTCOLLAB

dokucama

User Tools

Site Tools

Differences

Page Tools