AMETHYST Webadmin and AMTMitel

[Belinda Frick]

Overview:

AmtMitel is used to collect call details from the Mitel 3300 ICP, in place of SMDR.

AmtMitel can run from a Windows PC or on the Amethyst Server. We usually run it on the AMETHYST server. It connects to the PABX and forwards the translated call data directly to AMETHYST on UDP port 27000.

In an CRE solution, the CRE connects to the AmtMitel and requests the information in real-time.

Please note that in newer versions of this application there will be a once-off fee payable to Mitel for the usage of the MiTAI API.

Required:

• Configuration on the Mitel PABX :
  Mitel: On the Mitel "Class of Service Option assignment" for all the phones and trunks that are used, these settings must be on :
  

  Code: Select all

  "HCI/CTI/TAPI Call Control Allowed"  = YES
"HCI/CTI/TAPI Monitor Allowed" = YES


  
  
• AMTMitel

If you are running the AmtMitel on Windows: DotNET2 redistributable must be installed on a Windows PC (usually already on most new Windows PCs)
Configuration required in AMETHYST Webadmin:

Log into AMETHYST Webadmin and from the Home Page select the Configure AMTMitel in the Configuration block (top right-hand side):

HomePage.jpg

Click on '+' next to 'Controller' to view the configuration for that controller:

MitelController.jpg

Multiple controllers can be added to AmtMitel to allow it it try and track calls accross controllers. When you add trunks and extensions, please only add the devices that are relevant to the controller you are working with.

Make sure that:

1. All the trunks being used is configured
2. All the extensions on the Mitel are configured

NOTE: Only monitored extension and trunks will provide call details.

Extension and Trunk Format:
The extensions and trunks use the same format when added to the configuration:

1. Single device = 3306 or 1 or 0506
   This will instruct Amtmitel to try and monitor just a single device for call information.
2. Range of devices = 1-30 or 3000-3099
   This will instruct AmtMitel to try and open all the devices in the range for monitoring.

Please don't add unnecessary ranges since this will increase the startup time dramatically; it will also put unnecessary load on the Mitel since it will be re-trying to open all the unopened extensions on regular intervals.

If a device fails to open an error message is printed in the AmtMitel.log.
Errors:
SXERR_INVALID_DEVICE = The device doesn't exist and will not be monitored
SXERR_DEVICE_ALREADY_MONITORED = The device is already monitored and will not be opened a second time.
SXERR_PRIVILEDGE_VIOLATION = the Class of service setting is not configured properly. This must be corrected on the Mitel Class of service settings.

If the device is opened correctly, the logs will not display any information for the device.

The AmtMitel will re-try to re-open any failed devices on a regular interval.

NOTE: to have access to the attachment, you need to be registered and logged in.

[Belinda Frick]

PLEASE NOTE:

AMTMitel needs to monitor the devices (trunks and extensions) per controller.

1. If you have more than one controller, only configure the trunks and/or extensions per controller.
   Do not add the trunks and/or extensions for each.
   
   
2. The trunk ranges for multiple controllers must not overlap.
   
   
3. If skillgroups are used, then this needs to be configured in AMTMitel to ensure the user names are received.
   
   Datatex must assist with skill group configuration, please provide skill group number.