Meta Description: Learn how to retrieve User and Phone details, Route Patterns (Dial Plan), Hunt Groups, and Auto Attendant information in Cisco CUCM and Unity Connection, with Microsoft Teams mapping.
This detailed guide explains how to retrieve and understand User & Phone details, Route Patterns (Dial Plan), Hunt Groups, and Auto Attendant (AA) information in Cisco CUCM and Cisco Unity Connection, along with a comparison to Microsoft Teams Direct Routing.
1. How to Retrieve User and Phone Details in Cisco CUCM
Path: Cisco CUCM Administration → Device → Phone
Filters to Use
- Device Pool Filter: Retrieve phones from a specific site or location.
- Directory Number (DN) Filter: Search using a specific extension or DID.
Information You Can Retrieve
- Phone Model (Cisco 7841, 8851, Jabber, CSF, etc.)
- MAC Address
- Description
- Device Pool
- Location
- Calling Search Space (CSS)
- Directory Number (DN)
- Partition
- Call Forward Settings (CFA, CFB, CFNA)
User Mapping Path: User Management → End User → Associated Devices / Lines
| Cisco CUCM | Microsoft Teams |
|---|---|
| End User | Azure AD User |
| Phone | Teams Client / IP Phone |
| Directory Number | Line URI |
| Device Pool | Location |
| CSS | Voice Routing Policy |
2. Route Pattern in Cisco CUCM (Dial Plan Equivalent)
Path: Call Routing → Route/Hunt → Route Pattern
Filters
- Partition Filter
- Description Filter
Route Pattern Fields
- Pattern (example:
9.XXXXXXXXXX) - Partition
- Gateway / Route List / SIP Trunk
- Calling Search Space (CSS)
- Discard Digits / Prefix Digits (number manipulation)
| Cisco CUCM | Microsoft Teams |
|---|---|
| Route Pattern | Dial Plan |
| Partition | Voice Route |
| Gateway | SBC |
| CSS | Voice Routing Policy |
3. Hunt Group Configuration in Cisco CUCM
Path: Call Routing → Route/Hunt → Hunt Pilot
Hunt Group Components
- Hunt Pilot – Main hunt number
- Hunt List – Routing logic
- Line Group – Agent extensions
Call Distribution Algorithms
- Top Down
- Circular
- Longest Idle
- Broadcast
| Cisco CUCM | Microsoft Teams |
|---|---|
| Hunt Pilot | Call Queue |
| Line Group | Agents |
| Hunt List | Routing Method |
4. Auto Attendant (AA) in Cisco Unity Connection
Path: Call Management → Call Handler
Filters
- Directory Number Filter
- Description Filter
Auto Attendant Information
- Call Handler Number
- Greetings (Standard, Closed, Holiday)
- Menu Options (Press 1 for Sales, Press 2 for Support)
- Transfer Destination (Extension, Hunt Pilot, or another Call Handler)
Schedule
- Business Hours
- After Hours
- Holiday Schedules
| Cisco Unity | Microsoft Teams |
|---|---|
| Call Handler | Auto Attendant |
| Greeting | Audio Prompt |
| Menu | Voice Menu |
| Schedule | Business Hours |
Best Practices for Cisco Voice Engineers
- Always use meaningful Description fields.
- Maintain documentation for Route Patterns and Hunt Pilots.
- Export regular reports for Phones, Directory Numbers, Route Patterns, Hunt Pilots, and Call Handlers.
Frequently Asked Questions (FAQ)
What is a Route Pattern in Cisco CUCM?
A Route Pattern defines how outbound calls are routed to a gateway, SIP trunk, or carrier. It is similar to a Dial Plan in Microsoft Teams.
What is a Hunt Group in Cisco CUCM?
A Hunt Group distributes incoming calls to multiple agents using algorithms such as Top Down, Circular, or Longest Idle.
What is Auto Attendant in Cisco Unity?
Auto Attendant is configured using Call Handlers in Cisco Unity Connection and provides IVR menu options like “Press 1 for Sales”.
How is Cisco CUCM mapped to Microsoft Teams?
CUCM Route Patterns map to Teams Dial Plans, Hunt Groups map to Call Queues, and Unity Call Handlers map to Auto Attendants.
Category: Cisco Voice, MS Teams Direct Routing
Tags: Cisco CUCM, Route Pattern, Hunt Group, Auto Attendant, MS Teams Direct Routing
