Calls are not recorded

From Kolmisoft Wiki
Revision as of 14:43, 18 April 2013 by Aisteb (talk | contribs) (→‎See also)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Troubleshooting

  • Check recording log: /var/log/mor/record_file.log

Make sure you have correct Recordings_Folder in /home/mor/config/environment.rb file




Wrong permissions, missing files

On Asterisk server check /var/spool/asterisk/monitor for files

If you do not see them here do:

chmod 777 /var/spool/asterisk/monitor
ln -s /var/spool/asterisk/monitor /home/mor/public/recordings
cp -u /usr/src/mor/scripts/mor_wav2mp3 /bin/




Call not answered

  • Calls should be answered to be recorded.




Recording is not enabled

  • If recordings are still failing, check call logs, find these lines:
2011-09-21 16:01:41] NOTICE[1163] app_mor_authentication.c: User's data retrieved: id: 62, lcr_id: 3, balance: -1772.886929,
frozen_balance: 0.000000, credit: -1.000000, blocked: 0, lcr_order: price, tariff_id: 8, postpaid: 1, day type: WD, exchange rate:
1.000000, ani: 0, tell balance: 0, time: 0, when left: 60s, every: 60s, user currency: ILS, def.curr: ILS, tariff type:  
user_wholesale, allow loss calls: 1, cid from dids: 0, cid from did: 972772285205, record: 1, owner: 0, sipchaninfo: 0, allow 
duplicate calls: 0, user call limit: 0, device call limit: 0, device active calls: 1, user active calls: 0, is_trunk: 0, 
vat_percent:  0.000000, originator_ip: 192.116.76.150, canreinvite: 0, record_forced: 0, recording_forced_enabled: 0, fake_ring: 0,
save_call_log:    0, warning balance(wb) active: 0, wb value: 0.000000, wb call: 0, wb file id: 0, grace time: 0, 
reseller_allow_loss_calls: 0, lang: en, lcr_first_prov_perc: 0.000000, change_failed_code_to: 0, device_max_timeout: 0
  • And these values are 0:
record_forced: 0, recording_forced_enabled: 0,

This means recordings are still not enabled, update your GUI to fix this problem.



Not enough space

Check recording log: /var/log/mor/record_file.log

And if you see something like this:

1345914805.33 - SRC quota: 104, taken: 68859 -> NOT ENOUGH space to store current recording
1345914805.33 - DST quota: 0, taken: 0 -> ENOUGH space to store current recording
1345914805.33 - SRC No email to which send recording.
1345914805.33 - UPDATE recordings SET visible_to_user = 0 WHERE uniqueid = 1345914805.33;

This means, that there is not enough space for recordings, and recording is deleted from the server and sent to email (if email is present - if not - recording is gone).




Recording is deleted after sending it over email

Check recording log: /var/log/mor/record_file.log

And if you see something like this:

1346335843.18 - Device (src) details retrieved: email1: , email2: , email3: somemail@gmail.com, quota: 3145728, send: 1, keep: 0, sum: 494187, call date: 2012-08-30 17:10:43, billsec: 15, src: 40060, dst: 37060064753, mp3 size: 58723, user_forced: 1, device_forced: 1, device_record: 1
...
1346335843.18 - UPDATE recordings SET visible_to_user = 0 WHERE uniqueid = 1346335843.18;

That means that recording is sent to email and deleted from server - as requested by settings.

Login to the user and change setting Keep Recordings on Server after sent to Email: YES if yo want to keep recording on the server after it is send to email.



See also