Summary:	ASTERISK-14751: In CDR Disposition save NO ANSWER instead BUSY or FAILED
Reporter:	Maxim Struchaev (maximfs79)	Labels:
Date Opened:	2009-09-02 02:45:09	Date Closed:	2011-06-07 14:08:09
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	CDR/cdr_csv
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I have used Asterisk 1.6.0.9, all will be ok. After update to asterisk 1.6.1.5 I have problem with cdr. Same effect on asterisk 1.6.0.14.
Comments:	By: Leif Madsen (lmadsen) 2009-09-02 08:25:43 Can you provide the relative configuration in order to see what is going on, or at least the console output which causes the CDR disposition to appear as you see it? We have no information to really go on here, as there are many scenarios that could cause this. By: Maxim Struchaev (maximfs79) 2009-09-02 09:43:55 Configuration: There are three accounting records: 3000, 3001, 3002 extensions 3XXX I call with 3000 to 3001 Then with 3002 to 3001 In console the answer such: chan_sip.c:4959 update_call_counter: Call to peer ' 3001 ' rejected due to usage limit of 1 Or Got SIP response 486 "Busy Here" back from 10.102.38.104 Then: Everyone is busy/congested at this time cause code return 17 I think problem in cdr.c. By: Leif Madsen (lmadsen) 2009-09-22 09:01:12 This is not a bug -- it is a configuration issue. Per your console output: chan_sip.c:4959 update_call_counter: Call to peer ' 3001 ' rejected due to usage limit of 1 Or Got SIP response 486 "Busy Here" back from 10.102.38.104 You called from 3000 to 3001. That is 1 call. You called from 3002 to 3001.  That is another call -- counter is now 2. Your console shows that you've got call-limit set to 1 -- thus the 2nd call is rejected. Closing this issue due to a configuration problem.