How do I know AMTMitel is receiving call details?

[Belinda Frick]

• Check the AMTMitel configuration.
  
  See: How to configure AmtMitel
  
  
• To see the AMTMitel log:
  
  AMETHYST Webadmin Home page, click on 'View Logs' and select todays date (or date of investigation). Click on the link to view AMTMitel. There is also an option to download the log file.
  
  When AMTMitel starts up it will:
  
  

  Code: Select all

  2010-10-03 13:59:42.594 [1.2.10.30]  Starting Amethyst Mitel Interface
2010-10-03 13:59:43.211 [1.2.10.30]  Amethyst Mitel Interface started successfully


  
  
  
  1. attempt to connect to the Mitai (Mitel PABX).
     
     

     Code: Select all

     2010-10-03 13:59:43.098 [1.2.10.30]  DEBUG: MiTAI libraries loaded - version MITEL Telephony Application Interface - Version 13.0.1.9_SP9 REMOTE.  Initialising...
2010-10-03 13:59:43.129 [1.2.10.30]  DEBUG: MiTAI libraries initialised.
2010-10-03 13:59:43.129 [1.2.10.30]  DEBUG: Connecting to MiTAI servers...
2010-10-03 13:59:43.144 [1.2.10.30]  DEBUG:   Connecting to 192.168.0.220
2010-10-03 13:59:43.191 [1.2.10.30]  Error in MiTAIController.Open: SXOpenPBX 192.168.0.220: SXERR_CANNOT_CONNECT_SERVICE
2010-10-03 13:59:43.191 [1.2.10.30]  Error connecting to 192.168.0.220
2010-10-03 13:59:43.211 [1.2.10.30]  Amethyst Mitel Interface started successfully wrapped

2010-10-03 14:00:43.150 [1.2.10.30]  Error in MiTAIController.Open: SXOpenPBX 192.168.0.220: SXERR_CANNOT_CONNECT_SERVICE
2010-10-03 14:01:43.163 [1.2.10.30]  Error in MiTAIController.Open: SXOpenPBX 192.168.0.220: SXERR_CANNOT_CONNECT_SERVICE
2010-10-03 14:02:43.164 [1.2.10.30]  Error in MiTAIController.Open: SXOpenPBX 192.168.0.220: SXERR_CANNOT_CONNECT_SERVICE
2010-10-03 14:03:43.508 [1.2.10.30]  DEBUG: MiTAIController.Open: SXFeatureMonitor starting
2010-10-03 14:03:44.186 [1.2.10.30]  DEBUG: MiTAIController.Open: SXFeatureMonitor finished
2010-10-03 14:03:44.296 [1.2.10.30]  DEBUG: SX_NumberOfMembers 9600 = 1
2010-10-03 14:03:44.406 [1.2.10.30]  DEBUG: SX_NumberOfMembers 9601 = 1
2010-10-03 14:03:44.464 [1.2.10.30]  Error in MiTAI_DN.Open: SXMonitor 9602: SXERR_INVALID_DEVICE
2010-10-03 14:03:44.585 [1.2.10.30]  DEBUG: SX_NumberOfMembers 9603 = 1
2010-10-03 14:03:44.726 [1.2.10.30]  DEBUG: SX_NumberOfMembers 9604 = 1
2010-10-03 14:03:44.864 [1.2.10.30]  DEBUG: SX_NumberOfMembers 9605 = 1

     
     
  2. Get the list of extensions, as per configuration in AMTMitel.
     If you added a range and not all the extension is setup on the
     Mitel as per requirements, it will list these extensions with errors.
     
     This is example of a devices either not configured or that it does not exist.
     

     Code: Select all

     2010-10-18 16:36:13.543 [1.6.3.5]  Error in MiTAI_DN.Open: SXMonitor 6980: SXERR_INVALID_DEVICE

     
     
     In the Mitel "Class of Service" Option assignment the following settings is required:
     "HCI/CTI/TAPI Call Control Allowed" and
     "HCI/CTI/TAPI Monitor Allowed" to YES for all trunks.
     
     This is a example of a valid device:
     

     Code: Select all

     2010-10-03 14:03:45.425 [1.2.10.30]  DEBUG: SX_NumberOfMembers 9609 = 1

     
     
  3. Once the devices has been listed, it will list the interfaces was started successfully:
     
     

     Code: Select all

     2010-10-18 16:38:15.703 [1.6.3.5]  DEBUG:   Successfully connected to 172.16.1.2
2010-10-18 16:38:15.710 [1.6.3.5]  Amethyst Mitel Interface started successfully


     
     
     it will start giving events for the configured devices
     
     

     Code: Select all

     2010-10-04 09:45:25.093 [1.2.10.30]  DEBUG:   Event type: CallOriginatedEvent
2010-10-04 09:45:25.093 [1.2.10.30]  DEBUG: Processing event 119
2010-10-04 09:45:25.090 [1.2.10.30]  DEBUG: Controller: 192.168.0.220
2010-10-04 09:45:25.090 [1.2.10.30]  DEBUG: Received event 119
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG:
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG:   Cause: ClearInvoked
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG:   Event State: IdleState
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG:   Call ID: 26
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG: Received event on trunk 43
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG:   Event time: 2010-10-04 07:19:38.000
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG:   Event type: CallClearedEvent
2010-10-04 09:19:38.533 [1.2.10.30]  DEBUG: Processing event 118
2010-10-04 09:19:38.532 [1.2.10.30]  DEBUG: Controller: 192.168.0.220
2010-10-04 09:19:38.531 [1.2.10.30]  DEBUG: Received event 118
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG: TRACKER: FinishTrunkCall: Call ID 26 on trunk 43
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:     DeviceNetworkExt: 0586231836
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:       Name: E1
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:       Network number:
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:         Type: voice data trunk private
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:         Trunk: 43
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:       Number:
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:     Trunk info:
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:     IsANIComplete: 3
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:     Call ID: 0
2010-10-04 09:19:38.475 [1.2.10.30]  DEBUG:     Advisory msg:


     
     
  4. AMTMitel will translate these events into TAPI START and STOP messages.
     

     Code: Select all

     2010-10-18 17:18:39.698 [1.2.10.30]  TAPI|START|9608|41|0219135943||O|
2010-10-18 17:18:30.811 [1.2.10.30]  TAPI|STOP|R:9608|021913||0:00:04||2010-10-18|17:18:26||40|O|Jeanne||ANSWERED|


  
  NOTE:If you use virtual extensions/login codes and you are using a central installation of AmtClient, like a Terminal Server or Citrix Server, you need to enable the settting 'SendVirtual' to tie the physical and virtual extension number in the data that is sent for popups.
  
  
  • If you have TAPI START and STOP messages AMTMitel is receiving call data from the PABX and translating it.
    
  • If AMTMitel is sending to AMETHYST, then you should get call details with the recordings.