Critical mail:....PRI ...MORE THAN 10 UNMATCHED SMDR

[Belinda Frick]

--------------------- CRITICAL ERRORS START HERE ---------------------
2012-04-05 13:33:10 2012-04-05 13:36:46 PRI CHANNEL 135 HAS HAD MORE THAN 10 UNMATCHED SMDR ON CARDSERVER CARDSEVER.
---------------------- CRITICAL ERRORS END HERE ----------------------

AMTWebadmin.log:

[2012-04-05 13:33:21] Version [1.6.3.18]******Critical Errors sent to john@doe.co.za *******
[2012-04-05 13:33:21] Version [1.6.3.18]2012-04-05 13:33:10 2012-04-05 13:36:46 PRI CHANNEL 135 HAS HAD MORE THAN 10 UNMATCHED SMDR ON CARDSERVER CARDSEVER.
[2012-04-05 13:33:21] Version [1.6.3.18]
[2012-04-05 13:33:21] Version [1.6.3.18]******End Critical Section*******

AMTCards.log:

[2012-04-05 13:34:56.531] Version [1.6.4.1] WARNING: ProcessOneSMDR: Dropping SMDR data since no recording was found. 7221|INCOMING||0:00:02||2012-04-05|13:31:16||60|I|ASHWIN STOFFELS||ANSWERED|

This error could indicate:

• Call data was received from the PABX, but could not be matched to a recording.
  
  This could be caused by:
  
  
  • incorrect configuration, for example the wrong PRI number was configured in 'Configure Cardserver/CRE' for the recording channel.
    
    
  • No recording took place.
    
    Possible causes:
    
    
    • If PRI cable is not connect - thus no recordings.
      
      
    • If PRI cable connected incorrectly - see AMTCards logs for TONE entries. You will need to enable verbose logging: AMETHYST Webadmin -> Configure Cardserver/CRE, click on the '+' next to Options and then tick enable logging and click on APPLY.
  
  
• If number matching is enabled and could drop recordings if the number in the SMDR data does not match that received from the recording card.
  
  AMETHYST 1.6 and number matching
  
  Trunk side recording and AMTMitel:
  
  
  The Dropping SMDR is generated because of the number matching rules being enabled.
  The CLI numbers are not being supplied by the Mitel through the AmtMitel interface.
  The numbers are being picked up on the PRI by the recording cards.
  
  Since the numbers are now difference, the number matching is discarding the SMDR.
  
  For trunk side recording these calls will all be under the EXT extension in the Amethyst Supervisor.
  
  Suggestion: enable the CLI on the Mitel side, we should be able to match better and there will be less EXT calls.
  
  NOTE: The recording was made, but due to number matching the call details could not be tied to it and therefore the 'Dropping SMDR data since no recording was found.'
  
• Short calls or unanswered calls could also cause this error.
  
  In AMTCards you can set the trigger type for when the recordings must start. If you use TRIGGER TYPE 3 it will recording unanswered calls and you should not get UNMATCHED SMDR messages for unanswered calls details with no recording to tie it to. Note that if you use this trigger type you will have recordings for unanswered and/or short calls.
  
  If you use the other trigger types, you will get call details from the PABX for unanswered calls, but have no recording and it will generate the UNMATCHED SMDR critical e-mail.
  
  For trigger type settings see forum post:
  
  How do I set the trigger type in AMTCards?