| Summary: | ASTERISK-08709: Bad CALLERID after ForkCDR | ||
| Reporter: | kokoskarokoska (kokoskarokoska) | Labels: | |
| Date Opened: | 2007-02-01 01:59:19.000-0600 | Date Closed: | 2011-06-07 14:03:23 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) callerid_bug.txt | |
| Description: | 1. After I use ForkCDR and then set CALLERID(name) and CALLERID(num), in CDR were written new values of CALLERID(name) to both: old CDR and also forked CDR. The CALLERID(num) stayed unchanged. Same behavior if I do it thru dilaplan or thru AGI. 1. After I use ForkCDR and then set CALLERID(name), CALLERID(num) and CALLERID(ANI), in CDR were written new values of all vars, but - like in previous case - to both: old CDR and also forked CDR. Same behavior if I do it thru dilaplan or thru AGI. In 1.2.4 it works fine, i.e. the original CALLERID values stayed intacted and only values for new (forked) CDR were changed... Complete debug is in attached file. Thanx! k.r. | ||
| Comments: | By: jmls (jmls) 2007-05-28 02:32:57 kokoskarokoska, could you check the latest 1.4 branch and see if this is still an issue ? There have been a load of cdr changes in the last few months in 1.4. Thanks. By: kokoskarokoska (kokoskarokoska) 2007-05-30 09:29:33 Of course :-) But I'm very busy now, so I can do it on Sunday evening. Thanx. k.r. By: Steve Murphy (murf) 2007-06-19 15:58:20 Uh, have you tried using CDR(varname|l), where 'l' says to use the 'last' CDR in the list? (Which is what you want when you ForkCDR, BTW) Try this, and let me know. By: Steve Murphy (murf) 2007-06-20 19:12:34 I'm closing this bug; if the l-option doesn't fix the issue, reopen and we'll investigate further. | ||