00 · Header
Calling Analytics & CDR
T2-R08. Control Hub Calling analytics, the Detailed Call History tab, and why a KPI call is not the same object as a call-leg row. n0rlwxe header September 29, 2026. Retrieved 2026-10-14.
01 · TL;DR
One dashboard, two grains
- The Calling analytics sentence is 13 months with Pro Pack and 3 months without, for calls based in Webex App. [cite:1]
- The January 27, 2026 picker change limits a selection to 3 months. History access is a separate sentence. [cite:1]
- Detailed Call History does not include the Call on Webex option. [cite:1]
- Voicemail answers count as answered, on the KPI and on the leg. [cite:1]
- The worst-experience name opens Troubleshooting, still capped at 21 days. [cite:1]
02 · Map
Where a Calling number is born
The flow is a study diagram. The sentences on it are from n0rlwxe. Troubleshooting hops stay in T1-R06. [cite:1]
03 · Core
Keep the grains apart
n0rlwxe, header September 29, 2026, says you use the Analytics page in Control Hub to see historical Webex Calling data. You have access to 13 months of data for calls based in Webex App if the organization has Pro Pack. Without Pro Pack, that access is 3 months. The same article’s January 27, 2026 note says the maximum date range you can select becomes 3 months at a time, while 13 months of historical data remains available if you run more than one report. [cite:1]
A media session is categorized as good if both the video stream and the audio stream had jitter below 150 ms, latency below 400 ms, and packet loss below 5%. Clicking a name in Users with worst calling experience opens Troubleshooting for the media sessions that user made in the selected range, up to 21 days. [cite:1]
Detailed Call History KPIs are generated on a per call basis. Alice calling Bob counts as a single call. The table entries are individual call legs, and each Webex Calling call is comprised of an originating record and a terminating record when both people are registered Webex Calling users. If Alice is a PSTN user, Webex Calling logs only the terminating entry for Bob. [cite:1]
On the call-queue stats table, handle time includes talk time, hold time, and ring time. On the call-queue agents table, handle minutes are calculated as total talk time plus total hold time. Those sentences are both in n0rlwxe. Do not collapse them into one formula. [cite:1]
| Surface | Grain | What answered means | Cite |
|---|---|---|---|
| Detailed Call History KPI | One call | Hunt group answered by the 10th agent counts as answered. Voicemail counts as answered. | [cite:1] |
| Detailed Call History table | One leg | Answered if that leg was answered. Voicemail service still counts as answered. | [cite:1] |
| External calls KPI | Call | Unknown call type is accounted as external. | [cite:1] |
| Total Calls by Location | Leg | Alice and Bob both at location A produce 2 entries. Different locations produce 1 each. | [cite:1] |
| Call queue stats handle time | Queue call | Talk + hold + ring. | [cite:1] |
| Call queue agent handle time | Agent | Talk + hold. Declined calls are not bounced. | [cite:1] |
The Direction filter works only when Call classification is set to External. The detailed call history tab does not include the Call on Webex option. Consultative transfer, call park, and call retrieve are counted as an additional internal call because those CDRs have a different correlation id. The Country field populates for international calls with the country code of the caller ID, and the article says that field may appear empty for some admins. [cite:1]
Call-queue incoming KPIs on that page are total answered calls, total abandoned calls, percentage of abandoned calls, and average wait time. Abandoned means the caller hung up or left a message before an agent became available. Overflow - Busy is the queue limit. Overflow - Timed out is the wait past the maximum configured limit. Live queue KPIs are active calls, calls waiting, and held calls. [cite:1]
Partner Hub article n5zr85e says multi-tenant partners can set a webhook to gather Webex Calling records for customers they manage, and that the webhook delivers detailed call history records every 5 minutes. Header August 13, 2026. [cite:2]
04 · Ecosystem
Ecosystem and sister technologies
Calling analytics is not Analyzer, not CUIC, and not the 21-day hop view.
- Pro Pack window
- 13 months of Calling analytics for calls based in Webex App. Without Pro Pack, 3 months. [cite:1]
- 3-month picker
- From January 27, 2026 the maximum selectable range is 3 months at a time. Longer history still requires multiple reports. [cite:1]
- Per-call KPI
- Alice calling Bob is one call for Detailed Call History KPIs, even when the call has several legs. [cite:1]
- Originating record
- The leg from the calling registered user’s point of view. [cite:1]
- Terminating record
- The leg from the called registered user’s point of view. A PSTN caller produces only this row for the called user. [cite:1]
- Good media session
- Both audio and video under 150 ms jitter, 400 ms latency, and 5% packet loss. [cite:1]
- Bounced call
- Presented to an agent and not answered. A declined call is not counted as bounced. [cite:1]
- Call on Webex
- Not included on the detailed call history tab. [cite:1]
- External unknown
- CDRs with unknown call type are accounted as external calls. [cite:1]
- Correlation id split
- Consultative transfer, call park, and call retrieve count as an additional internal call because the correlation id differs. [cite:1]
- 21-day cross-launch
- Worst calling experience opens Troubleshooting for at most 21 days. [cite:1]
- Partner CDR webhook
- n5zr85e: multi-tenant partners receive detailed call history records every 5 minutes. Header August 13, 2026. [cite:2]
Mind map source
mindmap
Calling analytics
History window
Detailed Call History
KPI per call
Table per leg
Media quality
Call queues
Partner webhookSister-technology matrix
| Sister | What it is | Why it matters | Config touchpoint | Typical failure | Cite |
|---|---|---|---|---|---|
| Calling analytics | Control Hub historical Calling charts | 13 or 3 months, then a 3-month picker. | Analytics, Calling | Teaching 13 months as one selection after January 27, 2026. | [cite:1] |
| Detailed Call History | Cloud calling records | KPI versus leg. | Detailed Call History tab | Counting two table rows as two KPI calls. | [cite:1] |
| Media quality | Jitter, latency, loss | Good requires both streams inside the three thresholds. | Calling media charts | Calling a call good because audio alone was clean. | [cite:1] |
| Troubleshooting | 21-day hop view | Cross-launch from the worst-experience table. | Monitoring, Troubleshooting | Expecting 13 months of hops. | [cite:1] |
| Call queues | Calling queue charts, not WxCC queues | Answered, abandoned, overflow busy, overflow timed out. | Calling analytics call queues | Pasting Analyzer refresh onto these charts. | [cite:1] |
| Partner webhook | Records for managed customers | Every 5 minutes in n5zr85e. | Partner Hub | Using it as the customer’s on-screen table. | [cite:2] |
| Analyzer | WxCC reporter | Different product. Clocks live in tajemk. | Do not open it to explain a Calling leg. | Quoting 5 seconds as this dashboard’s refresh. | [cite:3] |
| CUIC | Unified CCE web reports | Data source in the serviceability guide is AW-HDS. | Not Control Hub. | Calling a Calling CSV a CUIC stock report. | [cite:4] re-check |
| Recording | Calling provider retention is a different article | A chart window is not storage. | nhvl4hw when the question is storage | Using 13 months as Dubber Go retention. | [cite:5] |
Integration edges
| From | To | Mechanism | What moves | Cite |
|---|---|---|---|---|
| Webex App call | Calling analytics | Historical aggregation | 13 months with Pro Pack, 3 without | [cite:1] |
| Registered user pair | Detailed Call History table | Two legs | Originating and terminating | [cite:1] |
| PSTN caller | Called user | One leg | Terminating record only | [cite:1] |
| Worst-experience row | Troubleshooting | Cross-launch | Up to 21 days | [cite:1] |
| Partner Hub | Customer callback URL | Detailed call records webhook | Records every 5 minutes | [cite:2] |
| Call queue | Analytics charts | Answered, abandoned, overflow | Busy versus timed out are different columns | [cite:1] |
Cross-platform bridges
Unified CM CDR and CAR are a different database. n0rlwxe does not print a field map onto them. Keep the Control Hub leg names (originating, terminating, correlation id) when the source is Calling. [cite:1]
Microsoft Teams call analytics is not this tab. help.webex.com article n0rlwxe does not publish a parity matrix. Orientation only.
Webex Contact Center Analyzer is the contact-center reporter. A Calling call-queue chart is still a Calling object. [cite:3]
Future-integration hooks
- Canon planning: when an integrator adds flashcards, keep the per-call KPI and the per-leg table as two cards.
- n5zr85e’s delivery interval is every 5 minutes. Header August 13, 2026. [cite:2]
- The Country-field defect is printed in n0rlwxe. Do not invent a fix date. [cite:1]
- Uncited product futures stay TODO-verify.
Ecosystem troubleshooting
| Symptom | Likely sister-system cause | Check | Fix | Cite |
|---|---|---|---|---|
| A quarter view is refused | The picker is 3 months at a time after January 27, 2026. | Whether Pro Pack history still exists. | Run two ranges. Do not tell the admin the history was deleted. | [cite:1] |
| Location A shows 2 for one internal call | Total Calls by Location is leg-oriented. | Whether both users are at A. | Explain the Alice and Bob example before you call it double counting. | [cite:1] |
| Analyzer 5-second refresh quoted for Calling | That clock is tajemk. | Which product the chart belongs to. | Stay on n0rlwxe for Calling. | [cite:3] |
05 · Flow
Read a Calling report in order
| Step | From | To | Protocol or mechanism | Notes | Cite |
|---|---|---|---|---|---|
| 1 | Admin | Analytics | Control Hub | Open Calling historical data. | [cite:1] |
| 2 | Picker | Range | Calendar | At most 3 months in one selection after the January 27, 2026 change. | [cite:1] |
| 3 | Call | KPI | Per call | Several legs can still be one KPI call. | [cite:1] |
| 4 | Call | Table | Per leg | Two rows if both users are registered. One terminating row if the caller is PSTN. | [cite:1] |
| 5 | Media session | Good or poor | Thresholds | Both streams, three thresholds. | [cite:1] |
| 6 | Worst user | Troubleshooting | Cross-launch | 21 days. | [cite:1] |
06 · Config
Paths the articles name
- Analytics page in Control Hub for historical Webex Calling data. [cite:1]
- Detailed Call History filters: Answered, Call Classification, Call Type, Direction, Location, User Name, Email, Endpoint Type, Device Type. Direction only when classification is External. [cite:1]
- Time zone follows the profile at the top right. Data populates for the chosen zone. [cite:1]
- Users with worst calling experience: click the name to open Troubleshooting, up to 21 days. [cite:1]
- Partner webhook setup is n5zr85e, header August 13, 2026, not the customer Analytics tab. [cite:2]
07 · Limits
Numbers worth memorizing
| Item | Value | Source | Verified? |
|---|---|---|---|
| Webex App call history, Pro Pack | 13 months | n0rlwxe, header September 29, 2026 | Quoted [cite:1] |
| Webex App call history, no Pro Pack | 3 months | n0rlwxe | Quoted [cite:1] |
| Selectable range | 3 months at a time from January 27, 2026 | n0rlwxe | Quoted [cite:1] |
| Good media | Jitter below 150 ms, latency below 400 ms, loss below 5%, both streams | n0rlwxe | Quoted [cite:1] |
| Cross-launch | Up to 21 days | n0rlwxe | Quoted [cite:1] |
| Partner webhook cadence | Every 5 minutes | n5zr85e, header August 13, 2026 | Quoted [cite:2] |
| Hunt-group example | Unanswered by the first 9, answered by the 10th, still one answered call | n0rlwxe | Quoted [cite:1] |
08 · Trouble
Trouble
| Symptom | Wrong story | What the source supports | Do this | Cite |
|---|---|---|---|---|
| The table has two rows and the KPI says one | Someone thinks the KPI is broken. | KPIs are per call. The table is per leg. | Say both grains. | [cite:1] |
| A PSTN inbound shows only one row | A leg was dropped. | A PSTN caller produces the terminating record for the called user. | Do not expect an originating Calling user row. | [cite:1] |
| Voicemail is marked answered | The report is wrong. | The article counts voicemail as answered. | Train that sentence. | [cite:1] |
| Direction filter does nothing | The control is broken. | Direction applies only when classification is External. | Set classification first. | [cite:1] |
| Parked calls inflated internal volume | Users placed extra calls. | Park, retrieve, and consultative transfer add an internal call because the correlation id changes. | Read the correlation-id sentence. | [cite:1] |
| Country is blank on an international call | The dial plan stripped the code. | n0rlwxe says the Country field may appear empty for some admins. | Treat it as the printed defect, not a dial-plan bug, until Cisco says otherwise. | [cite:1] |
| Handle time formulas disagree | One of the tables is stale. | Queue stats include ring. The agent table prints talk plus hold. | Quote the table you are looking at. | [cite:1] |
| A declined call is in bounced | Every refusal is a bounce. | Declined calls are not counted as bounced. | Separate decline from no answer. | [cite:1] |
| 13 months of hop detail | Analytics retention was copied onto Troubleshooting. | The cross-launch is 21 days. | Open T1-R06 for hops. | [cite:1] |
| Call on Webex is missing | The export filtered it out. | The tab does not include Call on Webex. | Stop searching this tab for that option. | [cite:1] |
09 · Self-question
Oral ladder
L1What history does Calling analytics keep for Webex App calls?
13 months with Pro Pack. 3 months without. [cite:1]
L2What did January 27, 2026 change?
The maximum range you select is 3 months at a time. The 13-month history sentence stays. [cite:1]
L3How many KPI calls is Alice calling Bob?
One. [cite:1]
L4How many table rows is that when both are registered?
Two. Originating and terminating. [cite:1]
L5What row exists when Alice is PSTN?
The terminating record for Bob. [cite:1]
L6When is a media session good?
Both audio and video under 150 ms jitter, 400 ms latency, and 5% loss. [cite:1]
L7Does voicemail count as answered?
Yes, on the KPI example and on the leg. [cite:1]
L8When does the Direction filter apply?
Only when Call classification is External. [cite:1]
L9What is a bounced call?
Presented and not answered. A decline is not a bounce. [cite:1]
L10Why do park and consultative transfer add an internal call?
Those CDRs have a different correlation id. [cite:1]
L11How often does n5zr85e say the partner webhook delivers records?
Every 5 minutes. The extract had no header date. [cite:2]
L12Is Analyzer this page?
No. Analyzer is the contact-center reporter in tajemk. [cite:3]
10 · Lab
Separate the grains on paper
11 · Quiz
Quiz
Pro Pack Calling analytics for Webex App calls keeps:
Answer
13 months. Without Pro Pack, 3 months. [cite:1]
After January 27, 2026, one selection can span:
Answer
3 months. Longer history means more than one report. [cite:1]
Alice and Bob are both registered. The table shows two rows and the KPI shows one. What is true?
Answer
Both. KPIs are per call. The table is per leg. [cite:1]
Alice is on the PSTN and calls Bob. The table logs:
Answer
The terminating record for Bob. [cite:1]
A good media session requires:
Answer
Audio and video each under 150 ms jitter, 400 ms latency, and 5% packet loss. [cite:1]
Does voicemail count as answered?
Answer
Yes. The KPI example and the leg row both say so. [cite:1]
Unknown call type on the external KPI is counted as:
Answer
External. [cite:1]
The Direction filter is disabled. What has to be true first?
Answer
Call classification set to External. [cite:1]
A declined call is:
Answer
Not a bounced call. Bounced means presented and unanswered. [cite:1]
Queue-stats handle time includes:
Answer
Talk, hold, and ring. The agent table’s formula is talk plus hold. [cite:1]
Draw KPI grain and table grain for one internal call.
Answer
One KPI box. Two leg boxes, originating and terminating. [cite:1]
The partner webhook in n5zr85e delivers records every:
Answer
5 minutes. Header date was not in the extract used here. [cite:2]
12 · Audio
Studio fills these
Transcript slot
Studio fills this. The prompt is the spoken outline.
Transcript slot
Studio fills this. The prompt is the spoken outline.
Transcript slot
Studio fills this. The prompt is the spoken outline.
13 · Interview
Oral-ready
1. 30 seconds. Calling analytics keeps 13 months with Pro Pack and 3 without, for Webex App calls. Since January 27, 2026 I select 3 months at a time. [cite:1]
1. 2 minutes. I then separate KPI grain from table grain. Alice to Bob is one KPI call and two legs when both are registered. A PSTN caller leaves only the terminating row. Voicemail is answered. Unknown type counts as external. [cite:1]
2. 30 seconds. Good media means both streams under 150 ms jitter, 400 ms latency, and 5% loss. [cite:1]
2. 2 minutes. The worst-experience click opens Troubleshooting for at most 21 days. I do not promise hop detail for the 13-month window. [cite:1]
3. 30 seconds. Declined is not bounced. Bounced is presented and unanswered. [cite:1]
3. 2 minutes. Queue-stats handle time includes ring. The agent table prints talk plus hold. I name the table before I say the formula. [cite:1]
4. 30 seconds. Call on Webex is not on the detailed call history tab. [cite:1]
4. 2 minutes. Park, retrieve, and consultative transfer add an internal call because the correlation id changes. Direction filters only when classification is External. [cite:1]
5. 30 seconds. The partner webhook in n5zr85e, header August 13, 2026, is every 5 minutes for customers that partner manages. [cite:2]
5. 2 minutes. That webhook is not the on-screen table, not Analyzer, and not CUIC. Analyzer’s clocks stay in tajemk. CUIC’s data source in the 15.0(1) serviceability guide is an AW-HDS. [cite:3] [cite:4]
14 · Citations
Ledger
Retrieved 2026-10-14. Mirrors cites/T2-R08.md. Facts older than 12 months, and pages whose header date was not in the extract, stay marked re-check.
- Analytics for Your Cloud Collaboration Portfolio — help.webex — article n0rlwxe — help.webex.com article n0rlwxe — header September 29, 2026, retrieved 2026-10-14. Calling history 13/3 months, January 27, 2026 picker, media thresholds, Detailed Call History grains, voicemail answered, Direction filter, correlation-id calls, call-queue and agent tables, 21-day cross-launch, Call on Webex excluded, Country field defect.
- Detailed call records webhook for Webex Calling in Partner Hub — help.webex — article n5zr85e — help.webex.com article n5zr85e — retrieved 2026-10-14 from the article extract. Multi-tenant partner webhook delivers detailed call history records every 5 minutes. header August 13, 2026.
- Cisco Webex Contact Center Analyzer User Guide — help.webex — article tajemk — help.webex.com article tajemk — boundary only. Analyzer is not Calling analytics. Clocks are taught in T3-R07.
- Serviceability Guide for Cisco Unified Contact Center Enterprise, Release 15.0(1), Product Architecture — cisco.com — Product Architecture — updated April 30, 2025. CUIC standard deployment uses AW-HDS. re-check
- Manage call recording for Webex Calling — help.webex — article nhvl4hw — help.webex.com article nhvl4hw — boundary. Recording retention is not an analytics window. Taught in T2-R06.
15 · Re-engineer later
Open
- Open questions: live picker versus the January 27, 2026 sentence. T1-R06 already says re-check the control.
- n5zr85e header August 13, 2026 confirms the 5-minute cadence.
- Facts still TODO-verify: none of the n0rlwxe sentences above. Uncited futures stay marked in the hooks list.
- Assets missing: hero image, audio, exported SVG files.
- Next review date: 2027-04-14, or sooner if n0rlwxe’s header moves.
Sources and go deeper
Checked links were opened this month. A confirm row has no address because that page was not opened.
- Wikipedia Webex (Wikipedia) last checked 2026-10
- Vendor doc Webex Help Center last checked 2026-10
- DevDocs Webex developer documentation last checked 2026-10
- DevDocs Webex developer getting started last checked 2026-10
- Community Webex community last checked 2026-10
- SRND Cisco Collaboration design zone last checked 2026-10
- RFC RFC 3261 SIP: Session Initiation Protocol last checked 2026-10
- Port table IANA service name and port number registry last checked 2026-10
- Port table Port reference for Webex Calling last checked 2026-10
- RFC RFC 3263 Locating SIP Servers last checked 2026-10
- RFC RFC 3264 An Offer/Answer Model with SDP last checked 2026-10
- Wikipedia Session Initiation Protocol (Wikipedia) last checked 2026-10
- RFC RFC 3550 RTP last checked 2026-10
- RFC RFC 3711 SRTP last checked 2026-10
- RFC RFC 4566 SDP last checked 2026-10
- RFC RFC 4733 RTP payload for DTMF last checked 2026-10
- Wikipedia Real-time Transport Protocol (Wikipedia) last checked 2026-10
- Release notes What's new in Webex Calling last checked 2026-10
- Vendor doc help.webex.com article n0rlwxe last checked 2026-10
- Vendor doc help.webex.com article n5zr85e last checked 2026-10
- Vendor doc help.webex.com article tajemk last checked 2026-10
- Vendor doc Product Architecture last checked 2026-10
- Vendor doc help.webex.com article nhvl4hw last checked 2026-10
sources.json for this page.