Summary:	ASTERISK-12140: CALLERID is not logged correctly into cdrs
Reporter:	Alisher (licedey)	Labels:
Date Opened:	2008-06-04 15:14:37	Date Closed:	2011-06-07 14:02:53
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	CDR/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I can set my callerid using the CALLERID function and this works great on the dialplan. I can read and write to it,the callerid is applied, but inside the cdr records it is the first callerid that has been provided and not the one that i defined. If I modify my CALLERID it should be logged to the cdr table. ****** ADDITIONAL INFORMATION ****** This problem was first mentioned in ASTERISK-1171774 bug http://bugs.digium.com/bug_view_advanced_page.php?bug_id=11774&history=1#history The bug was closed unresolved and still wasn't fixed. This bug happens with both PRI ISDN PSTN and SIP/VOIP, from several providers.
Comments:	By: Donny Kavanagh (donnyk) 2008-06-04 15:36:57 Could you post a short dialplan which will recreate this issue.  It may seem simplistic, but using a command such as forkcdr for example could lock the CDR record. By: Alisher (licedey) 2008-06-06 01:29:38 [incoming-calls] exten=>s,1,Set(CALLERID(num)=0${CALLERID(num)}) exten=>s,2,Dial(SIP/2000) exten=>s,3,Hangup [incoming-voip-calls] exten=>_X.,1,Set(CALLERID(num)=0${CALLERID(num)}) exten=>_X.,2,Dial(SIP/2000) exten=>_X.,3,Hangup Then if you check the CDR record, the cdr record is supposed to have 0 at the begining but it doesn't. By: Tilghman Lesher (tilghman) 2008-06-19 17:25:32 Please change the first step in this dialplan to: exten => s,1,Wait(1) exten => _X.,1,Wait(1) and see if the problem is still reproduceable. By: Tilghman Lesher (tilghman) 2008-07-14 16:58:44 No response from reporter.