Hi all,
I've been a nosey parkey for 8 years around these parts but rarely had the need to post as I find the information contained in this often answers my questions which can only be a good thing! I now need to throw this one out there as I have had little luck in finding any answers on the web or indeed from the vendor of my two products in question. Hopefully you guys may have some insight to my issue...
I'm charged with running a 6.2 Aura in physical hardware across core and ESS sites in the UK with 4 LSP sites in Europe and the US, centralised CMS 16.2 and MM v5. For call logging we use Oak Reportx ( which has been problematic since its inception but on the whole gives us what we need without being too costly on the opex. The biggest issue we've come across is with its ability to understand VDNs. After a lot of to and froing with Oak support it was understood that VDNs are actually recognised as DDI numbers in Reportx. We can now generate reports on VDNs but found that unlike the extensions and lines sections of the filter screens in Reportx, we cannot create custom filters with DDI numbers as this section simply does not work. If, as I do, have a random collection of VDNs that I want to create a compound report with, I cannot. I have to report on each VDN in isolation and manually add stuff together which is madness.
Oak tell me that the DDI feature was a late bolt-on and that it was never fully implimented nor is it possible to develop it further to add the custom filter like with the rest of the software. I simply cannot believe that their other Avaya customers (they have 'hundreds' apparently) have never had the need to use their call logger to produce VDN reports?!?! Obviously if they have got other unhappy customers like me I guess they'd hardly tell us that fact though.
Have any of you guys had experience with Oak Reportx and reporting on VDNs or would know of a Reportx user forum I can join that would enable me to ask this question?
Thanks in advance!
I've been a nosey parkey for 8 years around these parts but rarely had the need to post as I find the information contained in this often answers my questions which can only be a good thing! I now need to throw this one out there as I have had little luck in finding any answers on the web or indeed from the vendor of my two products in question. Hopefully you guys may have some insight to my issue...
I'm charged with running a 6.2 Aura in physical hardware across core and ESS sites in the UK with 4 LSP sites in Europe and the US, centralised CMS 16.2 and MM v5. For call logging we use Oak Reportx ( which has been problematic since its inception but on the whole gives us what we need without being too costly on the opex. The biggest issue we've come across is with its ability to understand VDNs. After a lot of to and froing with Oak support it was understood that VDNs are actually recognised as DDI numbers in Reportx. We can now generate reports on VDNs but found that unlike the extensions and lines sections of the filter screens in Reportx, we cannot create custom filters with DDI numbers as this section simply does not work. If, as I do, have a random collection of VDNs that I want to create a compound report with, I cannot. I have to report on each VDN in isolation and manually add stuff together which is madness.
Oak tell me that the DDI feature was a late bolt-on and that it was never fully implimented nor is it possible to develop it further to add the custom filter like with the rest of the software. I simply cannot believe that their other Avaya customers (they have 'hundreds' apparently) have never had the need to use their call logger to produce VDN reports?!?! Obviously if they have got other unhappy customers like me I guess they'd hardly tell us that fact though.
Have any of you guys had experience with Oak Reportx and reporting on VDNs or would know of a Reportx user forum I can join that would enable me to ask this question?
Thanks in advance!