@msmcknight wrote:
Hi everyone,
Another wierd problem here since I upgraded to v13...
I use ring groups to direct inbound calls to a bunch of extensions. This is nothing new, as I have been doing it for years. But....
After the upgrade, every extension is entered into the CDR log when an inbound call is received... even for the extensions that did not answer. For example, if I have 10 extensions in a ring group and a call comes in, each one of those extensions will be listed as a destination in the CDR and reported as NO ANSWER, except for the one extension that actually picked up, it shows ANSWERED.
Here's an example CDR report showing this behavior...
Call Date CallerID DID App Destination Disposition Duration
2016-10-01 21:54:58 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:58 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:58 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:58 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:57 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:57 "Shipping Dock" <5555551212> 18008888888 Dial 600 ANSWERED 01:39
2016-10-01 21:54:57 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:57 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:57 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:19
2016-10-01 21:54:57 "Shipping Dock" <5555551212> 18008888888 Dial 600 NO ANSWER 00:20This kind of noise in the CDR log is new and certainly unwanted. The inbound call was sent to a single ring group extension (600) -- there should have only been one entry reflecting a call to ext 600 and that the call was answered.
What happened to make this change, and how can I undo it/turn it off?
Thank you all,
-Michael
Posts: 2
Participants: 2