How do I check PIN codes in AMTMitel?

[Belinda Frick]

AMTMitel STOP message does not contain pin codes:
refer to forum post: AMTMitel Stop string fields explained

If you AMTMitel is set to debug logging you can search for the pin code.

Here is examples of an example to trace if a pin code was used making a call.

Take the call details given and find the call in your TMS to ensure the call did take place.

If AMTMitel was installed on a Windows PC, the logs will be in the default folder:


Code: Select all

C:\Program Files\datatex\amtmitel\logs



Select the correct date folder and open the amtmitel.log file in a text edit that allows you to do searches.


1. Now use the phone number as a unique key to search for for the call. Note that debug logging will display the telephone number in various steps of the detailed logging. You also need the time of the call and the extension number to narrow your search further.
   
   Find the stop message for the call, for example:
   

   Code: Select all

   2013-05-22 12:52:19.090 [1.6.4.4]  TAPI|STOP|R:2621|0114587600||0:00:36||2013-05-22|12:51:42||1|O|LeeAndra Labuschagne||ANSWERED|

   
   NOTE: 'R:' will preceed the extension number from where the call was made. You can use the link for the AMTMitel Stop string fields explained for field allocation.
   
   If you are sure this is the correct call, where the pin code was used.: for example check it was an outgoing call - the call direction will be 'O', then check for entries in the log before the STOP string.
   
   
   • This is to see if any CLIRules were setup in AMTMitel to remove digits typed before the phone number.
     

     Code: Select all

     2013-05-22 12:52:19.090 [1.6.4.4]  DEBUG: CLIRules modified number from "**34909#00114587600" to "0114587600"

     
     In this example '**34909#0' was removed before the phone number, else the TMS cannot cost the call correct.
     
     CLI rules is configured in the AMTMitel.ini in the CLI rules section, for example:
     

     Code: Select all

     [CLIRULES]
;0=Number|starts with|00|replace with|0|False|INCOMING
1=Number|starts with|**300|replace with|0|False|OUTGOING
2=Number|starts with|**3|deletecount|9|True|OUTGOING
3=Extension|starts with|0|replaceFIELD|TRUNK|False|ANY
;3=Number|ends with|#|replace with||False|ANY

     
     
     In this example CLI rule 2 executed. Digits pressed started with **3 and it thus remove the first 9 characters from the digits pressed to dial out, which is '**34909#0'.
     
     If a pin code was used, then it should be the '4909' from the digits that was removed by the CLI rules.
     
     
   • You can also search for 'account code'. For this example I found:
     

     Code: Select all

     2013-05-22 12:52:36.453 [1.6.4.4]  DEBUG:   Event type: AccountCodeSetEvent
2013-05-22 12:52:36.453 [1.6.4.4]  DEBUG: AccountCodeSet on call 1040  "4909"  verified: 1

   
   To check if this is a valid pin code, make a test call using it. If it should not be in use, please contact your PABX vendor to disable it.
   
   
   
2. You can also use the keys you press for a pin code call to use to search for the string.
   
   For example if you press '**3' followed by the pin code, then '#0' followd by the phone number.
   Search for the telephone number and then look for entries where ''**3' preceeds the telephone number.
   
   The 4 digits in between should be the pin code.