WarmTransfer Chicago: why the calls from (555) 010-0142 ended
3 calls from (555) 010-0142 · 15 January 2026 · 10:16, 10:19 and 10:31
Source: Webex Calling detailed CDR · Webex Contact Center
Nobody answered. Each call reached voicemail and the caller hung up during the greeting.
All three calls took the same route: the external IVR held the call for 51 seconds and sent it back, the front desk (ext 100) rang 18 seconds with no answer, the hunt group 199 rang three phones for 18 seconds with no answer, and the call went to voicemail 198. The Releasing party on the first leg to end was Remote each time, so the caller ended the call, 4 to 7 seconds into the greeting. No person spoke to the caller.
- As expected: Front desk rang the configured 18 s
- Problem: No phone in hunt group 199 answered
- Problem: Caller hung up in the voicemail greeting
- Note: Outside Webex for 51 s on Trunk 1
How the call was routed
Caller dials (555) 010-0100
The main number for the Chicago site. Arrival on the Webex side at 10:16:04.
Arrival · 10:16:04
External IVR
The call left Webex on Trunk 1 to the IVR at (555) 010-0190 and came back on the same trunk 51 seconds later with ext 100 as the target.
Outbound trunk= Trunk 1 · 51 sFront desk, ext 100
Rang for 18 seconds.
Answered= false,Call outcome reason=NoAnswer. Call forwarding on no answer sent it on.Rang 18 s · no answer
Hunt group 199
Simultaneous ring to ext 102, 103 and 107 for 18 seconds. None answered. The hunt group's no-answer action is voicemail 198.
102 ✕ · 103 ✕ · 107 ✕ · 18 s
Voicemail 198
The system answered with the greeting.
Answered= true on a voicemail leg means the greeting played, not that a person spoke.Greeting played
Caller hangs up
The external leg released first with
Releasing party=Remote, 6 seconds into the greeting. No message was left.Release at 10:17:37 ·
Remote
What each caller experienced, second by second
- Outside Webex
- Hunt group
- Person
- Voicemail
- Hang-up
How we know
Who ended it
On every call the first leg to release was the external one, with Releasing party = Remote. The Webex side had not released anything yet. That is the caller hanging up.
leg:c1:5leg:c2:5leg:c3:5
How each leg ended
Ext 100 and hunt group 199: Answered = false, Call outcome = Success, Call outcome reason = NoAnswer, ring 18 s. Voicemail 198: Answered = true, User type = VoiceMailRetrieval, duration 4–7 s.
leg:c1:3leg:c1:4leg:c1:5
Why it moved on
Redirect reason = NoAnswer on the hunt-group leg and Original reason = CallForwardNoAnswer on the voicemail leg. Hunt group 199 is configured to ring 3 times (18 s) before its no-answer action.
leg:c1:4cfg:hg1:noAnswerRingscfg:hg1:noAnswerAction
Changes that would alter this outcome
Add a phone that is staffed to hunt group 199
Three phones rang for 18 seconds on all three calls and none answered. A member who is at a desk during the morning, or a longer ring time, changes the outcome before voicemail.
leg:c1:4cfg:hg1:members
Shorten the IVR hop
The caller spent 51 of 93 seconds in the external IVR before any phone rang. If the IVR only plays a greeting and routes, a Webex auto attendant does the same without leaving on Trunk 1.
leg:c1:2
Send no-answer calls to a queue with an announcement
Callers hung up 4 to 7 seconds into the voicemail greeting. A call queue with "your call will be answered" and a wait estimate holds callers longer than a mailbox greeting does.
leg:c1:5leg:c2:5leg:c3:5
What this data can't tell you
- Why the caller hung up: the records show when, not what the caller heard or intended.
- What the external IVR did during the 51 seconds; only the trunk legs out and back are recorded.
- Whether the three hunt-group phones were in use, unplugged or simply not picked up. CDR records a ring with no answer either way.
- Audio quality. Detailed call history carries no media statistics.