SMDR processing from Mitel MiVoice Business in Tariscope
SMDR data processing from Mitel MiVoice Business in the Tariscope telephone call accounting system is performed for the following SMDR parameter settings in this type of PBX:
| DASS II - Call Charge Information Provided: | No |
| Extended Digit Length: | No |
| MCD - Report Transfers: | No |
| Network Format: | Yes |
| Report Account Codes: | No |
| Report Incoming Calls: | Yes |
| Report Internal Calls: | Yes |
| Report Meter Pulses: | No |
| Report Outgoing Calls: | Yes |
| SMDR Meter Unit Per Station: | Yes |
| SMDR Record Transfer: | No |
| System Identification: | |
| Time Change Reporting: | No |
| Twenty-four Hour Time Reporting: | No |
| ANI/DNIS/ISDN/CLASS Number Delivery Reporting: | No |
| SMDR Real Time Reporting: | No |
| OLI Node ID Format for Incoming Trunk Calls: | No |
| Extended Time To Answer: | Yes |
| SMDR File Transfer: | Yes |
| Standardized Network OLI: | No |
| Standardized Call ID Format: | No |
| Suite Services Reporting: | No |
| Report Internal Unanswered Calls: | No |
| SMDR Extended Reporting Level 1: | No |
| Report Attendant Name: | No |
| Account Code Reporting for Internal Calls: | No |
| Tag Call Reporting: | No |
| Tag Call Identifier: | |
| Path Reporting for Internal ACD2 Calls: | No |
| Number of destination address digits to mask: | 0 |
| SMDR Extended Reporting Level 2: | No |
| Two B-Channel Transfer Reporting: | No |
| External Hot Desk User Reporting: | No |
| Suppress Initial SMDR Record with Account Code Entered Timer | 5 |
| Location Information Reporting: | No |
| SMDR Port Enabled: | Yes |
We recommend configuring the Mitel MiVoice Business PBX in this way.
Mitel MiVoice Business (3300) uses data transfer from IP port 1752. On the Tariscope side, to receive SMDR data, you should use Tariscope Observer, which uses a TCP client as the data source.
A feature of the Mitel 3300 (MiVoice Business) parser is that the Project Code field for calls using transfer contains the following information: for the first stage of transfer the field contains information about the extension to which the call was transferred, and for the second stage of transfer the field contains information about the extension from which the call was received. An example of this can be seen in the figure below.
This figure shows the stages of a call using a transfer. If you select a row in the view for calls that contains one of the transfer stages and click the Show related records icon on the toolbar, the view will display all stages of that call, as shown in the figure above.
