Once an error is triggered, the recording software will keep checking the framers to see when the error is cleared.
If the error Framer thread on board 0 will not be able to report alarms occurs, the recording card will not be able to detect any further errors to pass them on to Amethyst.
Here is some examples of the errors as reported in the Amethyst Webadmin.
- Code: Select all
[2012-04-25 15:20:07] Version [1.6.4.2]******Critical Errors sent to genius@support.com *******
[2012-04-25 15:20:07] Version [1.6.4.2]2012-04-25 15:19:59 2012-04-25 15:39:24 ERROR ON FRAMER THREAD ON BOARD 0: MTGETFRAMERALARMSTATUS RETURNED M
T_TIMEOUT (WAIT FOR EVENT TIMED OUT)
[2012-04-25 15:20:07] Version [1.6.4.2]2012-04-25 15:19:59 2012-04-25 15:39:24 WARNING: FRAMER THREAD ON FRAMER THREAD ON BOARD 0 WILL NOT BE ABLE
TO REPORT ALARMS.
[2012-04-25 15:20:07] Version [1.6.4.2]
[2012-04-25 15:20:07] Version [1.6.4.2]******End Critical Section*******
This critical e-mail indicates that the recording card cannot report on any alarm messages. It may stop recording and will not be able to report 'errors'. The only option is to stop/start AMTCards service on the AMETHYST Cardserver. This will stop all recordings on all cards on this server. Please schedule with the client if there are other cards that are recording other trunks.
Checking if the Amethyst Cardserver is recording:
There must be events like this, showing the recorded information
- Code: Select all
Recorded(DT2)=>EXT:EXT,USER:AMTCARDS,LINE:033,NUMBER:INCOMING,DURATION:0:00:17,INCOMING(00131_07DC2B73FA671.ZLB)
Recorded(DTA)=>EXT:123,USER:Leon,LINE:033,NUMBER:0215921234,DURATION:0:01:17,INCOMING(00131_07DC2B73FA672.ZLB)
If there a number of "Dropping SMDR" error messages in the Cardserver logs with the Line number of the PRI where the errors occured, htere is a good chance that there are still calls going through the PRI and the card can't record them. You need to restart the service. This is what the errors look like(This is errors one Line 001 and 002):
- Code: Select all
WARNING: ProcessOneSMDR: Dropping SMDR data since no recording was found. 9411|0219131000||0:00:25|R0.00|2012-05-15|07:39:00||001|I||||
WARNING: ProcessOneSMDR: Dropping SMDR data since no recording was found. 9411|0219152004||0:01:24|R0.00|2012-05-15|07:42:01||002|I||||
If the Cardserver is in Debug mode and there are call events but it is not recording events, the service has to be restarted.
This is the PRI Events that are received:
- Code: Select all
Processing event 2972: EVT_CC_CALL_IN_PROGRESS on PRI channel 0 (trk/ext: 001)
Processing event 2973: EVT_CC_CALL_ALERTING on PRI channel 0 (trk/ext: 001)
Processing event 2974: EVT_CC_CALL_CONNECTED on PRI channel 0 (trk/ext: 001)
NOTE: If the AmtCards on version 1.6.1.59 or older, please note:
A bug was fixed in the newer versions; We strongly suggest to upgrade if you are using a DP recording card.
Fixed bug where DP alarms stop working, and channel cannot be brought out of faulty status. MTGetFramerAlarmStatus can apparently return MT_TIMEOUT (indicating the card did not respond in time). This was not being handled, and the framer thread for that framer would stop checking for alarms.
If the card recovers, you will receive the following critical e-mail:
- Code: Select all
[2012-04-25 16:21:11] Version [1.6.4.2]******Critical Errors sent to genius@support.com *******
[2012-04-25 16:21:11] Version [1.6.4.2]2012-04-25 16:21:08 2012-04-25 16:40:33 NOTICE: FRAMER THREAD ON FRAMER THREAD ON BOARD 0 IS ABLE TO REPORT ALARMS AGAIN.
[2012-04-25 16:21:11] Version [1.6.4.2]
[2012-04-25 16:21:11] Version [1.6.4.2]******End Critical Section*******
This critical e-mail means the card can report alarms again. This means no restart of AMTCards is needed.