Scheduled Reporting - Additional Reports

Discussion in 'Ideas' started by PaulD, Dec 22, 2015.

Scheduled Reporting - Additional Reports 5 5 1votes
5/5, 1 vote

  1. PaulD

    Joined:
    Jul 4, 2010
    Messages:
    78
    Likes Received:
    8
    We need to share 3CX held data with other systems. The smart way would be for 3CX to publish its Entity Relationship Model & Data Dictionaries and to provide READ ONLY database connectivity but from the tenor of support requests, this isn’t going to happen.

    Would it be possible to have a new range of reports defined based around Extension Configuration and possibly other data not currently exposed? Much could be achieved just by making the Extension Export button in the console into a report. We could then schedule the reports to export CSV files daily and use SSIS/SSRS to process/pump that data into other systems. Examples of use would be:-

    1. To support our searchable web based ‘Contacts’ application
    2. To update AD with changes to ExtNo, Mobile Number, OCID etc (link on email address)
    3. To backfill other key systems with user/ExtNo/TelNo related info – Finance, HR, Estates
    4. The files themselves would be useful as snapshots of configuration long after subsequent changes have been made.
    5. Search/filter - identify users who do/don’t have particular features enabled – simple once in Excel
    6. Expose forwarding info - useful to tell which extensions are forwarding to a particular extension – no current way to do this that I am aware of

    The output file would need either a specific target location or some naming amendment to indicate which was which. This could then be quite a powerful tool for larger users.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. RogerS

    Joined:
    Dec 12, 2017
    Messages:
    13
    Likes Received:
    7
    We need also a regular/automated export of the 3CX extensions as source for the phone numbers to provision other central directories.