Summary: | ASTERISK-12456: Asterisk 1.4 doesn't save file name of an agent recording in cdr userfield | ||
Reporter: | nik (kolian) | Labels: | |
Date Opened: | 2008-07-25 15:23:04 | Date Closed: | 2011-06-07 14:08:24 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | CDR/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Asterisk 1.4 doesn't losses file name of the recorded file somewhere along a way. this was removed in 1.4 ; Insert into CDR userfield a name of the the created recording ; By default it's turned off. ;createlink=yes in channels/chan_agent.c around line 450 ast_cdr_setuserfield(ast, tmp2); It's still set correctly but lost somewhere during CDR merge. | ||
Comments: | By: nik (kolian) 2008-07-25 15:26:55 Asterisk 1.4 doesn't save file name of an agent recording in cdr userfield. Its correctly set but lost somewhere along a way. By: Donny Kavanagh (donnyk) 2008-07-25 15:42:46 Which backend are you using to write the cdr's. By: Donny Kavanagh (donnyk) 2008-07-25 15:43:55 I ask because in most (all?) userfield & uniqueid are disabled by default. By: Tilghman Lesher (tilghman) 2008-07-30 18:19:34 No response from reporter. By: nik (kolian) 2008-08-02 05:41:13 I use cdr_mysql, userfield is enabled in .conf file. If i use setuserfield in dialplan the value will show up in the database in userfield column. The value is dropped somewhere if it's set in channels/chan_agent.c. The agents are logged in to a queue and calls originated through Originate in Manager API. By: Tilghman Lesher (tilghman) 2008-08-05 09:53:26 We'll need to see your dialplan, as well as the command output that you're using to originate the channel. By: Tilghman Lesher (tilghman) 2008-08-05 09:54:07 In other words, you need to provide enough information that we can replicate this issue on our systems. By: Steve Murphy (murf) 2008-10-15 15:45:19 kolian-- I'm closing this bug, as it's been in feedback for a couple months. When you get time, and have some more info for us to reproduce this bug, just re-open this bug, and attach the info. I'll take a look at it at my earliest opportunity. |