Restore the ability to use -> as a parameter in call reports

Discussion in 'Ideas' started by fthomas_mcallen, May 24, 2017.

Restore the ability to use -> as a parameter in call reports 5 5 1votes
5/5, 1 vote

  1. fthomas_mcallen

    Joined:
    Jan 9, 2015
    Messages:
    4
    Likes Received:
    5
    In 3CX v11 (maybe 12 as well?) I could easily get a report of only calls that followed a very specific "path" through the system. For example, I could enter:

    Source: External
    Destination: 801 -> 100 -> 205

    The resulting report would contain only calls that originated externally, were routed to ring group 801, answered by extension 100, then transferred to extension 205. This was immensely useful. Please add this functionality back to future versions!