Populate callid fields for mivoice internal smdr records
The Mitel Mivoice smdr does not populate the callid field for smdr for internal calls.
This significantly complicates the algorithm for parsing of these records as compared to records for external calls. On most modern PBXs (eg Avaya IPO and 3cx) this is the norm (see attachments).
I propose that Mitel enhance the smdr for internal calls by populating the callid , associated callid and sequence number fields as is currently the case for external calls smdr.
These are valid calls that customers may need to process in call accounting applications (such as Call Tracker by ICNS) for productivity analysis, auditing and operational reporting.
This particular limitation in the internal smdr becomes particularly significant for processing internal transfers, conferences, call forwarding, repeated calls between the same extensions and calls spanning clustered controllers.
I trust that due consideration for this feature enhancement would be given to make a great product even better.
My contact info is 1-868-688-5686. Please feel free to call or email me if further clarification is required. Thank you for your cooperation.
Brian D Browne
shared this idea
Thank you for submitting to Mitel’s UserVoice. We appreciate that you have taken the time to document your new product idea or product enhancement for us. The UserVoice community and the Mitel Product team will begin evaluation of your idea and follow up with progress along the way.
To learn more about the UserVoice policy, forums and product categories that are configured within as well as the general process behind, visit UserVoice Policy Document.
The Mitel Product Management Team